Computer Science (Biomedical Informatics), MS postgraduate personal statement example

Personal statement example

Most mornings in the pathology reception where I work, a few specimen tubes arrive whose labels do not quite agree with the electronic request: a date of birth with two digits transposed, a surname spelt differently, a request coded for the wrong panel. My job as a data clerk is to catch these before samples reach the analysers, and to record why each one was rejected or corrected. After a year of doing this, I have become less interested in the individual errors and more interested in the systems that produce them. That is why I want to study computer science with a focus on biomedical informatics.

My first degree was in biomedical science. I enjoyed clinical biochemistry and haematology, but the module that changed my direction was a short statistics and data handling course in my second year, where we cleaned a messy dataset in R before analysing it. I found the cleaning more absorbing than the analysis. For my dissertation I carried out a retrospective audit, using anonymised records supplied by my supervisor, of how often HbA1c tests for people with diabetes were repeated sooner than local guidance recommended. Much of the work turned out to be reconciling inconsistent date formats and duplicate entries, and I wrote Python scripts with pandas to do this reproducibly rather than by hand. The finding was modest: early repeats were concentrated in a small number of requesting locations. But the project taught me that clinical questions often depend on whether data can be trusted at all.

Since graduating, I have tried to build the computing foundations my degree did not give me. I completed an online introductory course in data structures and algorithms, worked through exercises in SQL, and began reading about health data standards. Learning how HL7 messages and coded terminologies such as SNOMED CT are meant to carry meaning between systems helped me understand why a request can leave a GP surgery in one form and arrive at our laboratory in another. At work, with my manager's agreement, I built a simple spreadsheet tracker that categorises rejection reasons by week. It is not sophisticated, but it showed that one recurring error came from a default field in an ordering screen, which the team raised with the IT department. That experience showed me both what data can reveal and the limits of what I can do without stronger technical skills.

I am aware that my programming is still self-taught and uneven. I can write working scripts, but I want to understand software design, databases and machine learning properly, including how to evaluate models honestly when data are incomplete or biased. I am particularly interested in the quality of clinical data and in record linkage, because the problems I see daily are, at heart, problems of matching imperfect records. I would also value studying the ethics and governance of patient data, since at work I handle identifiable information under strict rules and have seen how carefully consent and access need to be managed.

Outside work, I volunteer most Saturday mornings at my local parkrun, usually on the timing and results desk. Matching finish tokens to barcodes, and fixing the occasional runner who scanned twice, is a pleasingly small version of the same reconciliation problem. I also play the cello in an amateur orchestra, which has given me patience with slow, steady practice.

I bring a grounding in laboratory medicine, a practical understanding of how clinical data are created and corrupted, and a habit of building my own tools when I need them. A master's degree would give me the rigorous computing training to turn that habit into skill, and to work in future on making health information more reliable for the people who depend on it.