Legacy EHR to Epic Digital Transformation Program
See how we helped a multi-state healthcare provider replace 10+ legacy EHRs, unify patient access, and modernize interoperability at scale.
01 Summary
Executive Summary
One of the Fortune 500 healthcare organizations we supported faced a highly fragmented technology environment following a series of mergers and acquisitions. The resulting multibillion-dollar nonprofit health system was operating with more than 10 different electronic
health record (EHR) platforms across multiple regions, including several separate instances of the same EHR system.
To address these challenges, the organization launched a large-scale transformation initiative focused on consolidating its EHR landscape into a single platform while creating a unified digital access experience for patients. This effort became one of the largest healthcare IT modernization programs in the nonprofit sector, impacting more than 60 hospitals, hundreds of clinics, and over 1,200 healthcare interfaces.
The program helped streamline operations, improve interoperability, reduce complexity, and create a more connected experience for both patients and care teams.
Research context: CommonSpirit’s South region ($7.2B revenue) completed its first Epic golive in June 2025, following a successful pilot across 45 Utah outpatient departments. The multi-year consolidation roadmap targets a single enterprise EHR and ERP by 2026 under the ‘One CommonSpirit’ strategy.
02 Overview
Client & Program Overview
03 Challenge
The Challenge
The scale of fragmentation was extraordinary. Following the merger, the health system inherited a mix of legacy EHR platforms operating independently across hospitals and regions, with multiple systems and separate instances operating in silos. Patient data, clinical workflows, and revenue cycle processes were often disconnected, creating significant complexity across the organization.
As a result, teams worked in fragmented environments, information was spread across multiple systems, and processes varied from one location to another, making it difficult to deliver a consistent experience for patients, clinicians, and administrative staff while also driving operational inefficiencies at scale.
Technology fragmentation
- 10+ distinct EHR systems across five regions, including 4 separate Epic instances
- 1,200+ active healthcare interfaces, many built as brittle point-to-point connections
- No unified patient identity or master person index (MPI) across hospital markets
- Siloed ancillary systems: PACS, LIS, Pharmacy, and Imaging each running independently
- Different revenue cycle platforms with no shared charge capture or claims workflow
Clinical & operational impact
- Clinicians could not access patient records across hospital markets
- Duplicate patient registrations and fragmented care histories across systems
- Manual re-entry of data between EHR and ancillary systems driving errors and delays
- Inconsistent clinical workflows: registration → lab → radiology → pharmacy varied by site
- Appointment scheduling fragmented — no system-wide unified booking experience
Financial & regulatory risk
- Revenue cycle inefficiencies driving claim denials and delayed reimbursements
- Inability to leverage scale across 60+ hospitals for payer contract negotiation
- Emerging 21st Century Cures Act FHIR mandates requiring API-based interoperability
- High operational cost of maintaining 10+ EHR vendor relationships and support contracts
04 Solution
Solution Architecture
The EAI team designed and implemented a layered integration hub model to serve as the backbone of the entire transformation. Rather than replacing all interfaces simultaneously, the architecture established a central interoperability bus that could broker HL7 v2 messages from legacy systems while simultaneously building FHIR R4 API channels for Epic and new integrations.
Tier 1 | Edge systems
Legacy EHRs (Cerner, Meditech, Optum), ancillary apps (PACS, LIS, Pharmacy), medical devices, ServiceNow
Tier 2 | Integration bus
IBM ACE (HL7 v2 routing), MuleSoft Anypoint (API-led connectivity), Axway B2Bi (EDI/B2B), Connexion framework
Tier 3 | Core EHR
Epic system of record - Bridges (HL7), Interconnect (FHIR APIs), Resolute (revenue cycle)
Platform
Microsoft Azure cloud - CI/CD pipelines, Sentinel monitoring, CMDB, automated alerting
Tier
Components & role
Tier 1 | Edge systems
Legacy EHRs (Cerner, Meditech, Optum), ancillary apps (PACS, LIS, Pharmacy), medical devices, ServiceNow
Tier 2 | Integration bus
IBM ACE (HL7 v2 routing), MuleSoft Anypoint (API-led connectivity), Axway B2Bi (EDI/B2B), Connexion framework
Tier 3 | Core EHR
Epic system of record – Bridges (HL7), Interconnect (FHIR APIs), Resolute (revenue cycle)
Platform
Microsoft Azure cloud – CI/CD pipelines, Sentinel monitoring, CMDB, automated alerting
Clinical workflow and patient journey across integrated systems
One of the program’s core objectives was to ensure that the entire patient care journey, from registration through discharge and billing, could move seamlessly across Epic and all connected ancillary systems without requiring manual data entry or creating information gaps.
Interface migration workflow from legacy systems to Epic
Migrating more than 1,200 active healthcare interfaces required a structured and carefully managed approach. The process followed multiple phases, including discovery, gap analysis, build, testing, and cutover, with a strong focus on maintaining data integrity in live clinical environments. Before migration began, every interface was evaluated based on its HL7 message type, data flow direction, system dependencies, and business criticality to ensure a smooth transition and minimize operational risk.
OneConnect patient scheduling workflow
The OneConnect platform transformed patient access by replacing fragmented, region specific scheduling tools with a single, unified digital front door. Patients could schedule appointments through one centralized system, with availability and bookings updated in real time through Epic using FHIR APIs. This streamlined approach helped eliminate duplicate scheduling, reduced the burden on call center teams, improved scheduling accuracy, and significantly shortened patient wait times
Revenue cycle integration module
Revenue cycle management (RCM) was one of the highest-value integration workstreams. By connecting Epic’s billing engine with ancillary charge-capture systems, clearinghouses, and payer platforms, the program automated charge flow, reduced claim denials, and enabled AIdriven coding suggestions. Research confirms organizations see 10–15% RCM improvement from reduced administrative overhead and faster claims processing through such integrations.
05 Impact & Outcomes
Business Impact & Outcomes
- 60+ hospitals standardized on a single Epic instance, eliminating 10+ legacy EHR environments
- Quality and safety metrics improved by 5–35 percentile points across the health system.
- $2B in merger synergy targets reached, partly driven by IT consolidation and EHR standardization
- Net Promoter Score reached 68 points, reflecting improved patient digital scheduling experience
- Revenue grew $2.8B (8.2%) year-over-year, supported by optimized revenue cycle integrations
- 10–15% RCM improvement from automated charge capture and claims processing workflows
- Lowered operational cost through platform consolidation and decommission of redundant systems
- FHIR R4 compliance positions system for 21st Century Cures Act interoperability mandates
06 Technology stack
Integration & interoperability
HL7 v2, FHIR R4, IBM ACE, MuleSoft Anypoint, Axway B2Bi, Connexion
EHR systems
Epic (target) Cerner, Meditech, Optum
Backend & microservices
Java, Python, REST APIs, Microservices
Cloud & DevOps
Microsoft Azure, CI/CD pipelines, Git
Monitoring & ITSM
Microsoft Sentinel, ServiceNow, CMDB, Automated alerts
Ready to modernize your health
platform?
Let’s discuss how we can bring enterprise-grade resilience to your mission-critical
applications.