EHR Integration Case Study | 12-Hospital Network

Project Type: Healthcare System Integration Industry: Multi-Hospital Health Network

Results at a Glance:
47 clinical systems connected through a centralized Mirth Connect integration hub
2,000+ staff hours saved per month in eliminated manual data entry
78% reduction in data transcription errors
Full ONC interoperability compliance achieved
Zero unplanned downtime during the 6-month implementation

Client Overview

A 12-hospital health network operating across three states, with a combined 3,200 beds, 850+ physicians, and over 1.2 million patient encounters annually. The network had grown through acquisitions over a 15-year period — each acquired hospital brought its own EHR platform, lab systems, radiology PACS, pharmacy systems, and billing engines.

The Challenge

The network operated 47 distinct clinical and administrative systems across its 12 hospitals. Four different EHR platforms were in use (Epic at 5 hospitals, Oracle Health/Cerner at 4, Allscripts at 2, and MEDITECH at 1). Each hospital also ran its own lab information system, pharmacy system, radiology PACS, and billing platform.

The consequences were severe. A patient transferred from one hospital to another within the same network had no continuity of records — the receiving hospital could not see the sending hospital’s clinical data. Lab orders placed in the EHR at one facility could not route to the lab system at another. Discharge summaries were faxed between facilities. Clinical staff spent an estimated 2,000+ hours per month on manual data re-entry, chart lookups, and phone-based coordination. Transcription errors from manual re-entry contributed to an estimated 340 adverse events per year across the network.

Additionally, ONC interoperability mandates required the network to support FHIR-based data exchange and patient access — capabilities that did not exist in the legacy infrastructure.

The Solution

Taction designed and implemented a centralized integration hub using Mirth Connect that connected all 47 systems through a single, manageable integration architecture.

Integration Architecture

Hub-and-spoke model: Mirth Connect served as the central hub. Every clinical system connected to Mirth — not to each other. This reduced the connection count from a potential 1,081 point-to-point interfaces (47×46/2) to just 47 connections.

Protocol transformation: Mirth Connect handled bidirectional transformation between HL7v2 (the lingua franca for legacy systems), FHIR R4 (for modern API-based integrations and ONC compliance), CDA/C-CDA (for clinical document exchange between facilities), and X12 (for claims and eligibility transactions with payers).

Enterprise Master Patient Index (EMPI): A critical component — the network had no unified patient identity. The same patient could exist in 4 different EHRs with different MRNs. Taction implemented an EMPI that matched and linked patient identities across all 12 hospitals using probabilistic matching algorithms, creating a single longitudinal view of each patient regardless of which facility they visited.

Integration Channels Built

ADT (Admission, Discharge, Transfer): Real-time patient movement notifications across all 12 hospitals. When a patient is admitted at any facility, every other facility in the network receives the notification — enabling care coordination and preventing duplicate registrations.

Order and Result Routing: Lab and radiology orders placed in any EHR route to the correct departmental system regardless of which hospital originated the order. Results flow back to the ordering EHR automatically. Cross-facility ordering (a physician at Hospital A ordering a lab at Hospital B’s reference lab) was enabled for the first time.

Clinical Document Exchange: Discharge summaries, progress notes, operative reports, and consultation notes shared between facilities via C-CDA documents. Eliminated fax-based document exchange entirely.

Medication Reconciliation: Medication lists synchronized across all facilities. When a patient presents at any hospital in the network, the complete medication history from all facilities is available — reducing medication reconciliation errors.

FHIR Patient Access API: A unified FHIR R4 endpoint giving patients access to their complete health records across all 12 hospitals through a single patient portal. Compliant with 21st Century Cures Act and ONC requirements.

HIPAA and Security

All data exchange encrypted in transit (TLS 1.2+) and at rest (AES-256). HIPAA compliance validated across all integration channels. Comprehensive audit logging of every message transaction (sender, receiver, timestamp, message type, patient identifier). Role-based access to the Mirth Connect administration console. BAAs executed with all infrastructure and connectivity providers.

Results

Metric	Before	After	Change
Manual Data Entry Hours (Monthly)	2,000+ hours	~180 hours	-91%
Transcription Errors (Annual)	~1,400 documented	~310 documented	-78%
Adverse Events from Data Errors (Annual)	~340 estimated	~72 estimated	-79%
Time to Access Transfer Patient Records	4–24 hours (fax/phone)	Real-time	-99%
Cross-Facility Order Turnaround	Not possible	Same-day	New capability
ONC Interoperability Compliance	Non-compliant	Fully compliant	Achieved
Integration Maintenance FTEs	8 (distributed across hospitals)	3 (centralized)	-63%

The financial impact was substantial. The 2,000+ hours of monthly manual data entry represented approximately $780,000 annually in labor costs. The centralized integration team of 3 replaced 8 distributed integration staff, saving approximately $350,000 annually. The reduction in adverse events from data errors — while difficult to quantify precisely — represented both patient safety improvement and risk reduction conservatively estimated in the millions.

Timeline and Team

Phase	Duration
Discovery & Assessment (all 47 systems)	4 weeks
Integration Architecture Design	3 weeks
EMPI Implementation	6 weeks
Phase 1: Epic Hospitals (5 facilities, 22 systems)	8 weeks
Phase 2: Oracle Health Hospitals (4 facilities, 14 systems)	6 weeks
Phase 3: Allscripts + MEDITECH (3 facilities, 11 systems)	5 weeks
FHIR Patient Access API	4 weeks
Testing & Validation (ongoing per phase)	Parallel
Total	~9 months

The phased approach ensured zero unplanned downtime. Each phase was validated in a staging environment before production cutover. Legacy interfaces were maintained in parallel until the new Mirth Connect channels were confirmed stable.

Team composition: Project manager, integration architect, 3 Mirth Connect developers, 1 FHIR API developer, 1 EMPI specialist, 2 QA engineers, HIPAA compliance lead.

Client Testimonial

We had 12 hospitals that could not share a patient record. Now every provider in our network can see the complete picture for any patient, at any facility, in real time. Taction delivered this across four different EHR platforms in 9 months with zero downtime. The 2,000 hours of monthly manual data entry we eliminated — that alone paid for the project within the first year — CIO,

Technologies Used

Mirth Connect (Enterprise), HL7v2 (ADT, ORM, ORU, SIU, MDM), FHIR R4, C-CDA, X12 (837/835), Epic (Open Epic + HL7v2), Oracle Health/Cerner (Millennium FHIR + HL7v2), Allscripts (Unity API + HL7v2), MEDITECH (HL7v2), PostgreSQL (EMPI), AWS (HIPAA BAA), ELK Stack (integration monitoring)

CTA: Schedule an Integration Assessment Running multiple EHR platforms or disconnected clinical systems? Schedule a free integration assessment and we will map your data flows and recommend the right architecture. Schedule Free Assessment →

Related Resources: