All case studies
HealthTech · Confidential — under NDA

An EHR integration that legacy systems could live with.

A hospital network where three legacy EHRs did not speak to each other, and clinicians paid for it in charting time. We built a HIPAA-compliant integration layer over FHIR — no rip-and-replace, and every record access auditable.

Discovery to production rollout2 min read
HIPAA
FHIR R4 ready
Admin time
−40%
Today · 12 hospitals
Patient Roster
847
Active
23
Critical
2.1d
Avg LOS
04
P-204
ICU-2A
stable
87
P-187
OPD-3B
review
12
P-512
WD-7
stable
91
P-091
ICU-1
critical
14 appointments today
The Challenge · 01

What was breaking

A hospital network running three different legacy EHR systems with no interoperability between them. Patient records were duplicated across sites, billing reconciliation ran on manual review, and clinician time went into data entry rather than care. The integration had to be FHIR-compliant, had to leave the legacy systems as systems of record, and had to produce a HIPAA-aligned audit trail a compliance officer could sign off on.

Our Approach · 02

The technical bets we made

  • 1

    Built a FHIR-compliant integration layer that translated between three legacy EHR formats and a unified internal patient model. No 'rip and replace' — the legacy systems remained the source of truth.

  • 2

    Designed a real-time deduplication engine using fuzzy patient matching on date of birth, name, phone and address — with a manual review queue for low-confidence matches, because a wrong merge in healthcare is far worse than a missed one.

  • 3

    Automated appointment scheduling with conflict detection across facilities, and SMS reminders sent through a HIPAA-compliant channel rather than a general-purpose gateway.

  • 4

    Streamlined billing reconciliation: claims auto-routed against insurance coverage rules, with anomaly detection flagging outliers before submission rather than after payout.

  • 5

    Set up immutable audit logging (cryptographically chained) for HIPAA compliance — every patient data access logged, queryable, exportable for audits.

Tech Stack · 03

What powers this system

React
TypeScript
Python
FastAPI
FHIR R4
PostgreSQL
Azure
HL7
Redis
Timeline · 04

From kickoff to production

Week 1-2
Discovery

Hospital walk-throughs, clinician shadowing, compliance officer interviews. FHIR mapping plan delivered week 2.

Week 3-5
Design

Integration architecture, FHIR resource model, HIPAA threat model. Compliance sign-off before code started.

Week 6-22
Build

Hospital-by-hospital phased rollout. 1-hospital pilot in week 8, full network live by week 22.

Week 23-26
Stabilise

Adoption support, runbook handover, SLA monitoring setup. Final HIPAA audit passed week 26.

Engineering outcome · 05

What the architecture changed

Interoperability stopped being a project and became a property of the system: a new site joins by mapping to the FHIR model rather than by another point-to-point integration. Deduplication moved patient identity from a per-hospital guess to a network-wide record. And because every access is logged into an immutable chain, HIPAA audit preparation became a query rather than a reconstruction.

Need something similar?

Book a free 30-min architecture audit. We'll sketch the system you need.

Book a 30-min Architecture Audit