Skip to content

Health records:
One connected view of each patient

We connected a regional health provider's separate EHR systems with a shared record format, live data sharing and patient matching across sites. Records became 100% consistent, and response times fell 85%.

Industry: HealthcareService: SaaS & SoftwareUpdated

Record consistency
100%
Faster access to patient data
85%
Data leaks
Zero

Overview

Project
at a glance

Industry
HealthcareA regional health provider with 14 clinical sites, each running its own older version of an EHR.
How we worked
Dedicated product teamA health IT architect, data streaming engineers and a HIPAA compliance lead worked inside the client's clinical informatics team.
Goal
One reliable patient recordConvert each site's HL7 v2 data into one shared FHIR-based record, so clinicians at any site can coordinate care.
What we built
Health data integration layerA translation, streaming and patient-matching layer that sits between the sites' existing EHRs, so no site had to replace its system.

The challenge

What was getting
in the way

Each clinical site ran its own older EHR, from Epic and Cerner to custom SQL databases. Clinicians could not see a patient's full medical history in real time, and staff matched patients across sites by hand, which left records split and incomplete.

When a patient moved between sites, their data could take 4-24 hours to follow. Every new connection between systems needed custom code.

  • Patient safety

    Allergy and medication lists did not match across sites, which raised the chance of preventable drug reactions.

  • Wasted tests

    Clinicians repeated diagnostic tests because they could not see earlier results, at an estimated cost of $2.4M a year.

  • Audit workload

    The older systems had no shared logging, so 21 CFR Part 11 and HIPAA audits were slow, manual and prone to error.

The solution

What
we built

  1. 01

    Translation into one record format

    A translation layer converts older HL7 v2 and SQL data into the FHIR R4 health-record standard as soon as it arrives.

    Standard
    FHIR R4
    Inbound
    HL7 v2/MLLP
    Mapping
    Jolt transforms
  2. 02

    Live updates across every site

    A live event stream shares admissions, lab results and medication orders with all sites in under a second.

    Backbone
    Cloud event streaming
    Availability
    Multiple availability zones
    Throughput
    10k Msg/Sec
  3. 03

    Accurate patient matching

    A Master Patient Index (MPI) uses consistent matching rules to confirm each patient's identity across systems before any records are merged.

    Accuracy
    99.9% Match
    Audit
    Built to HIPAA requirements
    Storage
    Encrypted

Before and after

How the work
changed

Data format

Before

Mismatched HL7 feeds

Non-standard data structures meant custom code for every new system connection.

After

One FHIR record

Standard FHIR R4 resources work with any compatible application from day one.

Privacy

Before

Site-by-site controls

Privacy controls lived inside each separate EHR, with no single view of who accessed patient data.

After

Shared controls

One set of HIPAA-aligned access controls, with a traceable record of every data request.

Data delays

Before

Batch transfers

Patient data often arrived 4-24 hours late when a patient moved between sites.

After

Live streams

Clinical events reach every site in < 500ms.

Key features

What made it
useful

  • Live updates

    Clinical event history

    Every change is stored as a traceable event, so the team can replay a record's history to fix issues or answer an audit.

    Business impact

    Zero inconsistent records

  • HIPAA

    Role-based data redaction

    Patient health information is filtered out of data streams based on each user's role, which also lets researchers use the data safely.

    Business impact

    100% regulatory alignment

  • Cost control

    Adapters that scale down

    Each EHR adapter runs in a container that scales with message volume, cutting cloud spend during quiet night shifts.

    Business impact

    30% infrastructure cost savings

Results

The business
difference

  1. Interoperability

    100% Record Consistency

    Records in the standard format

    All 14 data sources now feed one schema, and not a single record was rejected along the way.

    Before: 0% StdAfter: 100% Std

  2. Speed

    6x Faster Onboarding

    Time to connect a new site

    Connecting a new clinical site now takes 2 weeks instead of 12.

    Before: 12 WeeksAfter: 2 Weeks

  3. Access

    85% Data Access Response Time

    Patient data access time

    Live auditing and redaction give authorised clinicians patient data in under 50ms, where requests used to take hours.

    Before: HoursAfter: < 50ms

Faster delivery

Built on tested foundations

These components saved about 12 weeks of setup work. The team used the time for site-specific mappings and patient matching.

  • HIPAA access module

    Provided tested sign-in and role-based permissions for clinicians and researchers using the shared record.

  • Health-record transformation module

    Supplied ready-made HL7 v2 to FHIR mappings, which we adapted to each site's EHR version.

  • Integration monitoring platform

    Showed message flow and errors for every site connection, so failed feeds were caught quickly.

  • Data residency module

    Kept patient data inside the approved AWS regions from the first release.

Trust and control

How we kept it
safe and reliable

  • 01

    Data stays in-region

    Multi-region AWS residency keeps all patient health information within the required regulatory boundaries.

    HIPAA
  • 02

    Encryption throughout

    Data is encrypted with AES-256 at rest and TLS 1.3 in transit across the whole streaming system.

    Encrypted
  • 03

    Lab results always available

    Self-healing cloud clusters keep critical lab results available 99.99% of the time.

    High availability
  • 04

    Adapters you own

    On completion, the client owns 100% of the health-record adapters and translation logic.

    100% owned

FAQ

Straight
answers

Have a different question? Ask it on a 30-minute call.

Book a call

Each of its 14 clinical sites ran its own older EHR, including Epic, Cerner and custom SQL databases. Records moved between sites in batches that took 4-24 hours, and patients were matched by hand. Allergy and medication lists did not line up, and duplicate tests cost an estimated $2.4M a year.

Give clinicians one view of each patient

If your sites run different EHRs that do not talk to each other, we can help you connect them into one shared record without replacing any system.