- Reading time: 3 minutes
- Price: Free download
- Published: 18th September 2026
- Word count: 618 words
- File format: Text
Personal statement example
My interest in biomedical informatics began with a spreadsheet that would not open. During my final-year project I was given a public gene expression dataset of around thirty samples and asked to test whether a set of candidate genes differed between disease and control groups. My supervisor suggested R, which I had barely used. The first fortnight was spent learning why my file had the wrong delimiters and why a misplaced sample label quietly reversed my results. By the end I had a reproducible script, a short report on normalisation choices, and a much clearer sense that the biology I had studied for three years now reaches me almost entirely as data. I wanted to understand the pipeline rather than trust its output.
My degree gave me the biological grounding: molecular genetics, immunology, pathology and a research methods module that covered study design and statistical testing. It did not offer much computing beyond basic statistics, and my university had no bioinformatics pathway. I have worked to close that gap myself. Over the past two years I have completed free online courses in Python and SQL, and I read widely around the field; The Art of Statistics by David Spiegelhalter was particularly useful in making me think about how data is generated and communicated rather than only how it is analysed.
To practise on something real, I built a small project using open NHS prescribing data, which is published monthly by practice and drug. Working on a second-hand laptop, I loaded a year of records into a local SQLite database because the files were too large for a spreadsheet, then used Python to compare antibiotic prescribing rates across practices in one region, adjusting crudely for list size. The findings were unsurprising, and I am cautious about interpreting them, since I had no access to case-mix or deprivation data. The value was in the process: writing queries that ran in seconds rather than minutes, discovering that drug names are recorded inconsistently enough to need a mapping table, and learning to document every cleaning decision so that I could reproduce a figure weeks later. I keep the code and notes in a public repository, mainly so that I have to write clearly enough for a stranger to follow.
My job has shaped my thinking as much as my studies. I work full time as a dispensing assistant in a community pharmacy, handling prescriptions, stock and patient queries. I see how clinical information actually travels: electronic prescriptions that arrive with the wrong quantity, patients whose repeat records do not match what they are taking, the time the pharmacist spends phoning a surgery to reconcile a list. It has made me sceptical of the idea that better algorithms alone improve care, and interested in data quality, coding standards and how systems are used under pressure. I also volunteer on the committee of a local community allotment, where I organise the rota and the seed order, which is unglamorous but has taught me something about getting people to record things consistently.
I am applying for a master's because self-teaching has taken me to the edge of what I can check for myself. I want formal grounding in machine learning and statistical inference, clinical data standards and terminologies, and the ethical and governance frameworks around patient records. For my dissertation I would like to work with routinely collected primary care or prescribing data, ideally on medicines use. In the longer term I hope to work as a health data analyst within the NHS or a research group, contributing to the less visible work of making clinical data usable. I would rather be the person who understands why the file will not open.
Review this personal statement
Latest reviews
There are no reviews yet. Be the first one to write one.