01 /About
Doctor, builder, ethicist, architect — in that order of arrival, all still in use.
My relationship with technology did not begin with the recent generative-AI cycle. I studied IT unusually early, worked in design and visual communication, and kept building — websites, brands, presentations, tools — alongside everything that followed. That making habit never left.
I trained as a doctor at the University of Southampton, after a biomedical-science degree, and have practised across surgery, general medicine, renal medicine, emergency care and orthopaedics in the NHS. Frontline clinical work is where I learned how decisions are actually made — under pressure, with incomplete information, by people carrying knowledge that has never been written down.
An intercalated first-class degree in Clinical Ethics and Law gave me formal grounding in the questions that now sit at the centre of clinical AI: accountability, consent, judgement, and what it means to delegate a decision. I treat governance as an engineering input, not paperwork.
In the NHS I moved from using digital tools to building them: a renal workflow system I designed, deployed and handed over; contributions to hospital handover transformation and an emergency-attendance analysis; clinical input to AI pilots; Microsoft 365 and Power Platform implementation on real wards with real nurses at 3 a.m.
I co-developed a medical-imaging method for reconstructing 3D vascular anatomy from 2D ultrasound — I am co-inventor of the published UK patent application — acting as the project's architect across concept, methodology, code and synthetic-data production. I also design and deliver teaching that helps clinicians use AI safely.
The work I now do sits deliberately between worlds: translating clinical judgement into architectures technical teams can build, organisations can govern and clinicians can trust. Before an organisation can automate or augment a decision, it needs to understand how that decision is actually made. That understanding is what I build.