Skip to content

Orrery Health

One patient record across forty-one clinical systems

Orrery Health runs diagnostics and outpatient care across twenty-three sites on forty-one clinical systems that had grown up separately. We put a single FHIR R4 gateway in front of all of them, so a clinician sees one patient history instead of six logins.

Client
Orrery Health
Sector
Healthcare
Run
7 months · Jun 2024 – Jan 2025
Filed
2025-03-11
Capability
Systems integration · Data engineering · Security and compliance
Stack
TypeScript · Node.js 22 · HL7 FHIR R4 · SNOMED CT · Azure · Azure API Management · PostgreSQL 16 · Redis · OpenTelemetry

Impact

  • 1.9 s

    Median full-record assembly, down from 22 seconds

  • 268

    Point-to-point HL7 v2 interfaces retired

  • £480k

    Annual interface maintenance taken out of the IT budget

Challenge

Healthcare
7 months · Jun 2024 – Jan 2025

Assembling a full patient record meant opening six applications and reading across them by hand; the median was twenty-two seconds of waiting per system, and clinicians were printing results to avoid it. Underneath sat 268 bespoke HL7 v2 feeds built one at a time over eleven years, four of which had no owner left in the organisation. A 2023 data audit found roughly 31,000 duplicate patient identities, and nobody could say which record a given department was writing to.

Solution

We built a FHIR R4 gateway rather than another point-to-point feed, and wrote one adapter per source system so no clinical application had to change. A master patient index resolved identities with deterministic matching on NHS number first and probabilistic matching second, with every uncertain merge queued for a named data steward instead of resolved silently — that cleared 29,400 duplicates and referred 1,600 for human review. Terminology mapping normalised local codes to SNOMED CT so results from different labs became comparable. Access is role-scoped with break-glass emergency entry that pages an audit reviewer within sixty seconds, which is what carried the DSPT submission and the ISO 27001 surveillance audit in the same quarter.

Plates

  • Integration map showing forty-one clinical source systems on the left connecting through per-system adapters into a central FHIR R4 gateway, which serves a single patient record to clinical workstations on the right.
    Plate 01One gateway, forty-one adapters, no changes to source systems.
  • Master patient index review screen showing two candidate patient records side by side with matching fields highlighted, a confidence score of 0.86, and merge and reject controls for the data steward.
    Plate 02Uncertain merges go to a named steward, never to an algorithm.
  • Consolidated clinician view of a single patient showing observations, medications, referrals and imaging results in one chronological timeline, with each entry labelled by its originating source system.
    Plate 03Every field still carries the system it came from.

Testimony

The cutover itself took a weekend. The eleven months before it went on proving, record by record, that 2.3 million patient files would land intact. Given the same choice I would spend the eleven months again.

Thandiwe Mbeki · Director of Clinical Systems, Orrery Health5 out of 5