July to September 2026
Hospital at Night: FHIR API and the Trust's first OAuth2 server
The Hospital at Night service needed its clinical alerting supplier to find a patient and see their current ward, bay and bed. I designed and built a FHIR R4 facade API that answers those questions from the Trust's own systems, and stood up a Keycloak OAuth2 server to protect it.
Requests arrive at a reverse proxy in the DMZ, which validates the access token before passing them over TLS to Mirth Connect. Mirth queries SQL Server and MySQL sources and returns standard FHIR Patient and Encounter resources.
Tested end to end, signed off in UAT and prepared for production.
Built with FHIR R4, Keycloak, OAuth2 client credentials, Apache, Mirth Connect, SQL Server, MySQL
2022 to present
Patient engagement interfaces, built from scratch
Patients at the Trust receive digital appointment notifications and can reschedule through the NHS App or an online portal. I built the interfaces that make that possible, feeding the DrDoctor patient engagement platform from outpatients and patient administration, radiology (Soliton), endoscopy and cardiology (Tomcat).
The work continues: I have added queueing so a database outage no longer drops messages, and I am moving the connections from certificate-based MLLP to token-authenticated HTTPS ahead of shorter TLS certificate lifetimes.
Four clinical areas connected, running in production since 2022.
Built with HL7 v2 (ADT, SIU, ORU), MLLP over TLS, Auth0, Mirth Connect, JavaScript transformers. Systems: DrDoctor, Soliton, Tomcat
Infrastructure
Moving four live integration engines to RHEL 9
Migrated all four of the Trust's live integration engines from CentOS to Red Hat Enterprise Linux 9, including the Mirth Connect instances, their databases and the legacy MESH messaging service.
RHEL 9, Mirth Connect 4.5, MariaDB, SELinux, systemd
2026, in progress
A Dorset-wide integration engine and MESH API
Built a new integration engine to serve organisations across Dorset, with an NHS MESH API connection secured by mutual TLS. Its first job is sending clinical letters to GP surgeries.
MESH API, mutual TLS, Mirth Connect, NHS England onboarding
2026
Point-of-care results into the patient record
Blood glucose results arrive as HL7 from bedside devices, are rendered to PDF and filed to the electronic patient record. I rebuilt the pipeline on a new server and added error capture so failures can no longer pass silently.
HL7 ORU, headless Chromium, Mirth Connect, Linux