Health informatics postgraduate personal statement example

Personal statement example

In a second-year statistics seminar, our tutor handed out a spreadsheet with a third of its cells blank and asked what the gaps were telling us. Most of us treated them as a nuisance to delete. She showed that the blanks clustered among older participants and late-evening survey slots, so deleting them would quietly change who the dataset described. That idea, that missing information has a shape and a cause, has shaped most of what I have done since. It is why I want to study health informatics.

My undergraduate degree in psychology gave me a grounding in research methods, questionnaire design and statistics in R. For my dissertation I compared two ways of collecting sleep data from forty student volunteers over two weeks: a paper diary and a free smartphone diary app. I expected the app to produce cleaner records. It did produce fewer illegible entries, but participants skipped whole days more often, and the gaps were not random. They followed weekends and nights out, exactly when sleep patterns were most irregular. Paper diaries were messier but more often completed retrospectively, which brought its own recall problems. Neither method was simply better. I learned how much a recording tool's design affects what ends up being analysable, and I learned to document every cleaning decision so another reader could follow it. The project received a first-class mark, and writing it up was the most absorbing work of my degree.

Since graduating I have worked as a dispensing assistant in a busy community pharmacy. I label and assemble prescriptions, process electronic prescriptions arriving from GP surgeries, and handle queries at the counter. The work has shown me health data from the other end. An electronic prescription is far quicker than a handwritten one, but when a dose instruction arrives as free text, or a medicine is coded in a way our system displays awkwardly, the pharmacist has to check by phone. I do not make clinical decisions, but I see where those checks cluster. I have started keeping a simple tally of the reasons for queries I pass on, which our pharmacist now uses when raising recurring issues with local surgeries.

This experience led me to read more widely. Robert Wachter's The Digital Doctor helped me understand why introducing electronic records into hospitals created new frustrations as well as solving old ones, and why usability is a safety question rather than a cosmetic one. I have also worked through introductory material on clinical terminologies such as SNOMED CT and on the HL7 FHIR standard for exchanging health information. My understanding is still at a beginner's level, but it gave me words for what I see at work: two systems can both be accurate and still fail to share meaning.

Outside work I ring church bells with a local band and have kept the tower's practice rota for two years. Bell-ringing is unexpectedly mathematical. Methods are sequences of permutations, and learning them taught me patience with structured systems that only make sense once you see the underlying pattern. Running the rota, juggling people's availability so each practice has enough ringers, has made me practical about coordination and clear communication.

I want postgraduate study to give me the technical and theoretical depth I currently lack: data standards, database design, health information systems and the evaluation of digital tools in real care settings. I bring sound quantitative methods, an instinct for asking why data is missing, and daily experience of how information moves between parts of a health system. I would like to use these to help build systems that record what clinicians and patients actually need, in a form others can trust and reuse.