HL7 Integration
HL7 v2 interface development and legacy system connectivity.
Explore HL7 IntegrationMirth Connect Consulting & Development Services
Expert channel development, cloud deployment, and managed services for Mirth Connect (now NextGen Connect) and Open Integration Engine — the most widely deployed healthcare integration engines.
What We Offer
Mirth Connect Integration & Channel Development
From initial setup to enterprise-scale managed services, we cover the full Mirth Connect lifecycle.
Channel Development
Custom HL7 v2, FHIR R4, DICOM, and EDI X12 channel development built to your exact specifications. We handle source and destination connector configuration, JavaScript and XSLT transforms, message filtering, and end-to-end integration testing with comprehensive documentation for your team.
Cloud Deployment
Production-grade Mirth Connect deployment on AWS or Azure with high-availability clustering, auto-scaling groups, and automated disaster recovery. Our cloud architectures include encrypted RDS backends, CloudWatch or Azure Monitor alerting, and infrastructure-as-code templates for repeatable deployments.
Administration & Support
24/7 monitoring, proactive performance tuning, and dedicated support from certified Mirth Connect specialists. We manage version upgrades, JVM optimization, database maintenance, SSL certificate rotation, and channel troubleshooting so your integration team can focus on new development.
Legacy Migration
Migrate from legacy interface engines like Cloverleaf, Rhapsody, eGate, or Corepoint to Mirth Connect with zero downtime. Our migration methodology includes full channel mapping, parallel-run validation, and phased cutover with rollback plans to eliminate risk during the transition.
MirthSync DevOps
Version control, CI/CD pipelines, and team collaboration for Mirth Connect using our open-source MirthSync tools. Track every channel change in Git, enable pull-request code reviews for transforms, and deploy channel updates across environments with automated promotion workflows.
OIE Support
Full consulting and support for Open Integration Engine (OIE) — the open-source community fork of Mirth Connect maintained by Qvera. We provide the same channel development, cloud deployment, and managed services for OIE as we do for Mirth Connect, with seamless migration between platforms.
Channel Pipeline
HL7-to-FHIR Transformation
Mirth Connect transforms legacy HL7 v2 messages into modern FHIR R4 resources — bridging decades of healthcare infrastructure with RESTful APIs.
MSH|^~\&|EPIC|MAIN_HOSP|FHIR_GW|SAGA|20260301120000||ADT^A01|MSG20260301001|P|2.5.1
EVN|A01|20260301120000
PID|||MRN-98765^^^MAIN_HOSP||DOE^JANE^M||19851220|F|||456 OAK AVE^^CHICAGO^IL^60601
PV1||I|MED^0312^01||||ATT^SMITH^ROBERT^^^MD
IN1|1|BCBS001|BLUE CROSS|PO BOX 8000^^SPRINGFIELD^IL^62701{
"resourceType": "Patient",
"identifier": [{
"system": "http://main-hosp.example.com/mrn",
"value": "MRN-98765"
}],
"name": [{ "family": "Doe", "given": ["Jane", "M"] }],
"gender": "female",
"birthDate": "1985-12-20"
} Technical Expertise
Mirth Connect Capabilities
Deep expertise across channel types, cloud deployment architectures, and DevOps tooling for Mirth Connect.
We build channels across every major healthcare data transport and protocol. Each channel type is purpose-built for its data format with optimized connectors, message validation, and error handling.
HL7 v2 TCP/MLLP
Traditional HL7 v2 messaging over TCP with MLLP framing. ADT, ORM, ORU, SIU, MDM, and DFT message types with acknowledgment handling, retry logic, and message persistence for guaranteed delivery.
FHIR R4 HTTP
RESTful FHIR R4 API channels for Patient, Encounter, Observation, and other resources. OAuth2-secured HTTP sender and listener connectors with Bundle transaction support and US Core profile validation.
DICOM
Medical imaging channels for DICOM C-STORE, C-FIND, C-MOVE, and WADO-RS operations. Connect PACS, modalities, and VNA systems with TLS encryption and DICOM conformance validation.
Database
Direct database reader and writer channels for PostgreSQL, SQL Server, Oracle, and MySQL. Poll for new records, execute stored procedures, and synchronize data between clinical databases in real time.
File / SFTP
Batch file processing channels for CSV, XML, JSON, and flat-file formats. SFTP, SCP, and SMB connectors with file-locking, deduplication, and automated archive management for high-volume workflows.
Web Service
SOAP and REST web service channels for third-party API integration. Custom HTTP listeners for webhooks, AWS API Gateway integration, and outbound REST calls with retry and circuit-breaker patterns.
We deploy Mirth Connect on AWS and Azure with production-grade infrastructure designed for healthcare workloads. Every deployment follows HIPAA security requirements with encryption at rest and in transit, audit logging, and network isolation.
AWS Architecture
Our AWS reference architecture uses EC2 instances behind an Application Load Balancer with RDS PostgreSQL for the Mirth database. Channels run in a private VPC subnet with NAT gateway egress. CloudWatch dashboards provide real-time visibility into channel throughput, message errors, and JVM health metrics.
Azure Architecture
On Azure, we deploy Mirth Connect on Virtual Machine Scale Sets with Azure Database for PostgreSQL. Azure Monitor and Log Analytics capture channel metrics, while Azure Key Vault manages SSL certificates and database credentials. Private endpoints keep all traffic within the Azure backbone.
Cloud Capabilities
- High-availability clustering with automatic failover
- Auto-scaling based on message queue depth
- CloudWatch / Azure Monitor alerting and dashboards
- Automated disaster recovery with cross-region replication
- Infrastructure-as-code (Terraform / CloudFormation)
- Docker and Kubernetes deployment options
- Encrypted RDS / Azure PostgreSQL backends
- VPN and Direct Connect / ExpressRoute connectivity
- HIPAA BAA-eligible infrastructure
- Automated backup with point-in-time recovery
MirthSync is Saga IT's open-source tool for managing Mirth Connect channels as code. It extracts channels, code templates, and configuration maps from a running Mirth Connect instance into a structured file format that can be tracked in Git. This enables pull-request workflows, diff-based code reviews, and automated deployments across environments — capabilities that Mirth Connect's built-in version history does not provide.
How MirthSync Works
MirthSync connects to your Mirth Connect instance via the REST API, pulls channel definitions into a local directory structure, and pushes changes back. Each channel is serialized into human-readable files — JavaScript transforms, XML configuration, and metadata — so your team can review every change before it reaches production.
MirthSync Ecosystem
- MirthSync CLI — command-line tool for pull/push operations
- MirthSync Plugin — admin console extension for in-browser sync
- MirthSync VS Code Extension — edit channels directly in VS Code
mirthsync-cli
# Pull channels from Mirth Connect
$ mirthsync -s https://mirth.example.com \
-u admin -p ****** pull
Pulling channels...
ADT-A01-to-FHIR ............ OK
Lab-Orders-ORM ............. OK
Radiology-DICOM-Router ..... OK
Claims-EDI-837 ............. OK
# Push changes back to Mirth
$ mirthsync -s https://mirth.example.com \
-u admin -p ****** push
Pushing channels...
ADT-A01-to-FHIR (modified).. OK
Done. 1 channel updated. Frequently Asked Questions
Common Questions
Mirth Connect's open-source status changed significantly in March 2025 when NextGen Healthcare transitioned the product to a commercial licensing model. Prior to that change, Mirth Connect had been available under an open-source MPL license for over a decade. The community fork — Open Integration Engine (OIE) by Qvera — continues to be available under an open-source license. Organizations that relied on Mirth Connect's free licensing now have the option to either adopt NextGen's commercial terms or migrate to OIE, which maintains full channel compatibility with Mirth Connect.
In March 2025, NextGen Healthcare discontinued the free open-source distribution of Mirth Connect and moved to a commercial per-channel or enterprise licensing model. This change affected organizations that had been running Mirth Connect without a commercial agreement. NextGen continues to develop and support Mirth Connect (also branded as NextGen Connect) as a commercial product with enterprise features. In response, Qvera released Open Integration Engine (OIE) as a community-maintained fork that preserves the original open-source licensing terms.
Open Integration Engine (OIE) is a community-maintained fork of Mirth Connect created by Qvera after NextGen Healthcare changed Mirth Connect's licensing in 2025. Both platforms share the same core codebase and are fully channel-compatible — you can export channels from Mirth Connect and import them directly into OIE. The key differences are licensing (OIE is open source under MPL 2.0, Mirth Connect is commercial), support (OIE is supported by Qvera and consulting partners like Saga IT, Mirth Connect by NextGen), and roadmap (each platform is now evolving independently). Saga IT provides full consulting and support for both platforms.
Migration from Mirth Connect to OIE is straightforward because both platforms share the same channel format and Java-based architecture. The process involves deploying an OIE instance in parallel, exporting channels and code templates from Mirth Connect, importing them into OIE, and running a parallel validation period before cutting over production traffic. Custom Java libraries, JavaScript transforms, and database configurations transfer without modification. Saga IT's migration methodology includes full compatibility testing, performance benchmarking, and a documented rollback plan to ensure zero downtime during the transition.
Mirth Connect and NextGen Connect Integration Engine are the same product. NextGen Healthcare acquired Mirth Corporation in 2015 and rebranded the open-source Mirth Connect as NextGen Connect Integration Engine. Despite the name change, the community and most healthcare organizations still refer to it as Mirth Connect. In 2024, NextGen Healthcare changed the licensing model, making versions 4.6 and later commercial-only (no longer open source). The open-source community forked the last open-source version (4.5.2) as the Open Integration Engine (OIE), while NextGen also developed BridgeLink as a managed cloud offering. Saga IT supports all variants — commercial Mirth Connect, the open-source OIE fork, and migration between platforms.
The most direct alternative to Mirth Connect is Open Integration Engine (OIE) by Qvera, which is a fork of the same codebase with full channel compatibility. For organizations evaluating other integration engines entirely, the healthcare market includes Rhapsody (by Rhapsody), Corepoint Integration Engine, Iguana by iNTERFACEWARE, and Cloverleaf by Infor. Each has different strengths — Rhapsody and Corepoint offer polished enterprise UIs, Iguana focuses on rapid development, and OIE maintains the open-source flexibility that made Mirth Connect popular. The best choice depends on your existing channel inventory, budget, and team familiarity.
Deploying Mirth Connect on AWS requires an EC2 instance (or ECS container) running the Mirth Connect application server, an RDS PostgreSQL or MySQL database for the configuration and message store, and VPC networking with private subnets for HIPAA compliance. A production deployment should include an Application Load Balancer for TLS termination, CloudWatch for monitoring and alerting, and S3 for log archival. For high availability, deploy across multiple Availability Zones with auto-scaling groups and database Multi-AZ failover. Saga IT provides Terraform templates and managed deployment services for AWS Mirth Connect environments.
MirthSync is Saga IT's open-source tool for managing Mirth Connect channels as version-controlled code. It connects to a Mirth Connect instance via the REST API, serializes channels, code templates, and configuration maps into a structured file format, and stores them in a Git repository. This enables pull-request code reviews for channel changes, diff-based auditing of transform logic, and automated CI/CD promotion across development, staging, and production environments. MirthSync is available as a CLI tool, a Mirth Connect admin console plugin, and a VS Code extension.
Mirth Connect includes a built-in revision history that tracks changes within the application database, but it lacks key capabilities that modern DevOps workflows require. MirthSync stores channels as files in Git, enabling branch-based development, pull-request reviews, merge conflict resolution, and integration with CI/CD pipelines like GitHub Actions or Jenkins. Mirth Connect's native history is limited to a single timeline per channel with no branching, no cross-channel diffs, and no mechanism for promoting changes between environments. MirthSync fills these gaps by treating Mirth channels the same way development teams treat application source code.
Yes. NextGen Healthcare continues to offer commercial support for Mirth Connect under their enterprise licensing agreements. For organizations that prefer the open-source path, Qvera provides commercial support for Open Integration Engine (OIE). Saga IT offers consulting, managed services, and 24/7 support for both Mirth Connect and OIE regardless of your licensing arrangement. Our team has been working with the Mirth Connect codebase since 2016 and can provide the same level of channel development, cloud deployment, and administration support on either platform.
Production costs for Mirth Connect include the software license (now commercial under NextGen, or free with OIE), infrastructure (cloud compute, database, networking), and operational support. On AWS, a typical single-node deployment costs $300-800/month for EC2 and RDS, while a high-availability multi-AZ cluster runs $800-2,000/month. NextGen's Mirth Connect licensing is priced per-channel or as an enterprise agreement — contact NextGen directly for current pricing. OIE eliminates the software license cost entirely. Saga IT offers managed services that bundle infrastructure, monitoring, and 24/7 support into a predictable monthly fee.
Related Services
Explore More Services
Resources
Talk to a Mirth Connect Expert
From channel development to cloud migration — let's optimize your integration engine.