Health informatics postgraduate personal statement example

Personal statement example

My final-year computing project was meant to be a straightforward data visualisation exercise: a dashboard showing referral-to-treatment waiting times from an open, anonymised NHS England dataset. The coding was the easy part. What took me most of a term was understanding what the numbers actually described. Pathways were counted at different stages, some trusts reported incomplete months, and a figure that looked like a sudden improvement often turned out to be a change in how a category was recorded. I ended up writing almost as much about data definitions and caveats as about the tool itself, and I graded higher for the honesty of those caveats than for the interface. That project is the reason I want to study health informatics formally rather than drift into general software work.

My degree gave me the technical grounding: relational databases and SQL, Python for data handling, and a module on information security that covered access control and anonymisation techniques. A group coursework on systems analysis, where we interviewed a university administrator about a clunky room-booking process, taught me more than any lecture about how badly designed systems get worked around rather than used. I also took an optional statistics module and, since graduating, have been working through material on study design and confounding, because I can see that interpreting routinely collected health data needs more than programming. Reading around the subject, I found Eric Topol's Deep Medicine useful less for its optimism about algorithms than for its insistence that clinical time is the scarce resource any new system should protect.

My part-time job on a community pharmacy counter has been an unexpectedly good education in health information. I dispense nothing and make no clinical judgements, but I handle prescription queries, register people for repeat services, and see daily how information moves badly between general practice, the pharmacy and patients. A prescription arrives with a dose the patient insists was changed at a hospital appointment; someone cannot access their online account and has no printed list of medicines; an item is out of stock and the substitution has to be communicated back up the chain. Much of my day is spent on the telephone reconciling records that should already agree. It has made me sceptical of solutions that assume clean, complete data at the point of entry, and interested in interoperability standards and how coding systems such as SNOMED CT and dm+d underpin something as ordinary as a medicines list.

I am also membership secretary for a small running club that meets on Saturday mornings. When I took over, membership was tracked in three overlapping spreadsheets and renewal reminders were sent when someone remembered. I consolidated them into one structured record, added a simple check for expiring memberships, and wrote a one-page note on what data we hold and why, after reading the club's obligations under data protection guidance. Renewals now happen on time and our committee treasurer can reconcile subscriptions in an evening rather than a weekend. It is a modest piece of work, but it involved persuading volunteers to change habits, which I suspect is closer to real implementation work than anything I did in a lab.

From the MSc I want the structured grounding I currently lack: health data standards and terminologies, information governance, evaluation methods for digital interventions, and enough epidemiology to judge what routine data can and cannot support. My aim afterwards is an analyst or informatics role within a health service or public health team, ideally on data quality and clinical coding, where careful definitions matter as much as code. I would rather spend my career making one dataset trustworthy than build ten dashboards on shaky foundations.

Review this personal statement

Latest reviews