The Challenge

The health system faced a convergence of three pressures that made migration unavoidable.

ONC compliance deadline. The 21st Century Cures Act and ONC interoperability mandates required the health system to support FHIR R4 APIs for patient access and provider data exchange. The legacy HL7v2-only infrastructure could not meet this requirement. TEFCA participation — increasingly important for the system’s HIE connectivity — also required FHIR support.

Mirth Connect licensing change. The system was running Mirth Connect 3.12 (open-source). With NextGen Healthcare’s transition to commercial licensing starting with version 4.6, the open-source edition would no longer receive security updates or new features. The system needed to either upgrade to the commercial enterprise edition or find an alternative — and either path required a migration effort.

Technical debt. Twelve years of incremental channel development by multiple integration engineers had created 200+ channels with inconsistent naming conventions, undocumented transformation logic, redundant message routing, and no centralized monitoring. Some channels had not been modified in 8 years but were still processing messages daily. Nobody fully understood what every channel did, and the team was afraid to touch anything for fear of breaking downstream systems.

Specific technical challenges included HL7v2 messages with site-specific customizations that deviated from standard segment usage, no canonical data model — each channel transformed data independently using different logic, multiple HL7v2 versions in use (2.3, 2.4, 2.5.1) across different interfaces, no automated testing for integration channels, monitoring was limited to checking whether Mirth was running — no message-level visibility, and the 3-person integration team spent 80% of their time on break-fix maintenance rather than new development.

The Solution

Taction designed and executed a phased migration strategy that converted the health system’s integration infrastructure from legacy HL7v2 on open-source Mirth to a modern FHIR-capable architecture on Mirth Connect Enterprise — without any service interruption.

Phase 1: Discovery and Architecture (Weeks 1–4)

Channel inventory and documentation. Taction audited all 200+ channels, documenting source systems, destination systems, message types, transformation logic, volume, and criticality. Each channel was classified as critical (patient safety impact if disrupted), important (operational impact), or low-priority (reporting, archival).

Canonical data model. Instead of migrating each channel’s transformation logic as-is (preserving the inconsistencies), Taction designed a canonical FHIR-based data model. All incoming messages — regardless of source format (HL7v2.3, v2.4, v2.5.1) — would be transformed to FHIR R4 resources at the integration hub. Outbound delivery would then transform from FHIR to whatever format the destination system required. This canonical approach meant each source system needed one inbound transformation (to FHIR), and each destination system needed one outbound transformation (from FHIR) — rather than every channel having its own unique transformation logic.

Migration sequencing. Channels were grouped into 5 migration waves based on criticality, complexity, and system dependencies. Each wave could be migrated, tested, and validated independently.

Phase 2: Infrastructure Upgrade (Weeks 3–6)

Upgraded from Mirth Connect 3.12 (open-source) to Mirth Connect Enterprise (latest version) with NextGen commercial license. Deployed on AWS (HIPAA BAA) with high-availability configuration across two availability zones. Implemented Mirth Command Center for centralized monitoring, channel analytics, and performance metrics. Configured automated alerting for channel errors, message queue depth, and processing latency.

Phase 3: Channel Migration (Weeks 5–22)

Wave 1: ADT feeds (4 weeks) — The highest-volume, highest-criticality channels. ADT messages (admission, discharge, transfer, registration) flowing between all 8 hospitals and downstream systems. Migrated 38 channels. Each channel was rebuilt with the canonical FHIR model, tested in staging with production message replays, validated by the clinical systems team, and cut over during a maintenance window with the legacy channel maintained in parallel for 72 hours.

Wave 2: Lab orders and results (4 weeks) — ORM and ORU messages between EHRs and laboratory information systems. Migrated 52 channels. Lab result delivery was the most transformation-heavy category due to site-specific OBX segment variations.

Wave 3: Scheduling and clinical documents (3 weeks) — SIU scheduling messages and CDA/C-CDA clinical document routing. Migrated 34 channels.

Wave 4: Pharmacy, billing, and claims (3 weeks) — Medication orders, pharmacy dispensing, billing transactions, and X12 claims. Migrated 41 channels.

Wave 5: Public health reporting, archival, and miscellaneous (3 weeks) — Immunization registry submissions, syndromic surveillance, quality reporting, and legacy archival channels. Migrated 37 channels. Some archival channels were decommissioned entirely after confirming they served no active purpose.

Phase 4: FHIR API Layer (Weeks 18–24)

With the canonical FHIR data model in place, Taction built a FHIR R4 API layer on top of the integration hub. This provided a Patient Access API (21st Century Cures Act compliance) enabling patients to access their health data through third-party apps, a Provider Directory API for care coordination, Bulk FHIR Data Access for population health analytics and quality reporting, and SMART on FHIR authorization for third-party application integration.

This API layer — built on the same canonical FHIR model that powered the internal integration channels — meant the health system achieved ONC compliance as a natural byproduct of the migration, not as a separate project.

Phase 5: Decommissioning and Optimization (Weeks 23–26)

Legacy Mirth 3.12 instance shut down after all channels were confirmed stable on the new platform. 14 redundant or orphaned channels identified during migration were decommissioned permanently. Channel naming conventions standardized across the entire estate. Runbook documentation created for every active channel. Integration team trained on Mirth Connect Enterprise features and the canonical FHIR architecture.

Results

Metric	Before	After	Change
Data Exchange Speed	Baseline (HL7v2)	60% faster (FHIR REST)	+60%
Integration Channels	200+ (inconsistent)	186 (standardized, documented)	14 decommissioned
ONC Interoperability Compliance	Non-compliant	Fully compliant	Achieved
Migration Downtime	N/A	Zero unplanned downtime	Target met
Maintenance Effort (Team Time)	80% break-fix	40% break-fix, 60% new development	-40% maintenance
Mean Time to Resolve (Channel Errors)	4.2 hours	1.1 hours	-74%
Monitoring Visibility	Binary (running/not running)	Full message-level analytics	Complete visibility
Message Processing (Daily)	2.5M HL7v2 messages	2.5M+ (mixed HL7v2 + FHIR)	Same volume, modern architecture

The 40% reduction in maintenance effort freed the integration team to focus on new development work — including connecting 6 new ambulatory clinics acquired during the migration period, a project that would have taken months on the old infrastructure but was completed in 3 weeks using the canonical FHIR model.

Timeline and Team

Phase	Duration
Discovery & Architecture Design	4 weeks
Infrastructure Upgrade	3 weeks (overlapped)
Wave 1: ADT Feeds	4 weeks
Wave 2: Lab Orders & Results	4 weeks
Wave 3: Scheduling & Documents	3 weeks
Wave 4: Pharmacy, Billing, Claims	3 weeks
Wave 5: Public Health & Miscellaneous	3 weeks
FHIR API Layer	5 weeks (overlapped with waves 4–5)
Decommissioning & Optimization	3 weeks
Total	~6 months

Team composition: Project manager, integration architect, 3 Mirth Connect developers, 1 FHIR API developer, 1 QA engineer, HIPAA compliance lead. The client’s 3-person integration team worked alongside Taction throughout the migration and received full training on the new architecture.

Client Testimonial

We had 200 channels built over 12 years by 6 different engineers. Nobody understood the full picture. Taction came in, documented everything, designed a canonical FHIR model, and migrated the entire estate in 6 months with zero downtime. Our team now spends 60% of their time on new work instead of firefighting. And we achieved ONC compliance as a side effect of the migration — not as a separate million-dollar project. — VP of Information Services.

Technologies Used

Mirth Connect Enterprise (upgraded from open-source 3.12), FHIR R4 (canonical data model + API layer), HL7v2 (2.3, 2.4, 2.5.1), C-CDA, X12 (837/835/270/271), HAPI FHIR Server, SMART on FHIR (OAuth 2.0), AWS (HIPAA BAA, multi-AZ), Mirth Command Center, ELK Stack (supplemental monitoring), PostgreSQL

CTA: Assess Your Integration Needs Running legacy HL7v2 interfaces? Facing ONC compliance deadlines? Schedule a free integration assessment and we will map your migration path. Assess Your Integration Needs →

Related Resources:

Portfolios – Taction Software®