Open Integration Engine Consulting
Expert consulting and support for Open Integration Engine (OIE) — the open-source community fork of Mirth Connect. Migration planning, channel development, cloud deployment, and CI/CD with MirthSync.
OIE Consulting Services
Full lifecycle support for Open Integration Engine — from Mirth Connect migration and channel development to cloud-native deployment and 24/7 managed services.
Since NextGen Healthcare transitioned Mirth Connect to commercial licensing in 2025, many organizations are evaluating Open Integration Engine as a cost-effective, fully compatible alternative. Our migration team handles the complete transition from Mirth Connect 4.x to OIE — including channel export, compatibility testing, custom library validation, and production cutover. OIE maintains full channel format compatibility with Mirth Connect, which means your existing channels, code templates, JavaScript transforms, and configuration maps transfer without modification.
- Full channel inventory and compatibility assessment against OIE runtime
- Automated channel export from Mirth Connect and validated import into OIE
- Custom Java library and JavaScript transform testing on OIE's Java runtime
- Parallel-run validation with message comparison between Mirth Connect and OIE
- Zero-downtime production cutover with documented rollback plan
We build custom OIE channels for every major healthcare data standard — HL7 v2, FHIR R4, DICOM, and EDI X12. Each channel is designed with production-grade error handling, message persistence, and retry logic from day one. Our team follows the same channel architecture patterns on OIE that we have refined across hundreds of Mirth Connect deployments, ensuring your interfaces are maintainable, performant, and well-documented.
- HL7 v2 channels for ADT, ORM, ORU, SIU, MDM, and DFT message types over MLLP/TCP
- FHIR R4 REST channels with OAuth2 security, Bundle transactions, and US Core validation
- DICOM channels for C-STORE, C-FIND, C-MOVE, and Modality Worklist operations
- EDI X12 channels for 837/835 claims processing and eligibility (270/271) workflows
- Database, SFTP, and web service channels with configurable polling and retry patterns
We deploy OIE on AWS and Azure with production-grade infrastructure designed for healthcare workloads. Every cloud deployment includes high-availability clustering, encrypted database backends, network isolation for HIPAA compliance, and infrastructure-as-code templates for repeatable, auditable provisioning. OIE's open-source licensing eliminates per-channel fees, which makes cloud-native deployment significantly more cost-effective than commercial Mirth Connect for organizations running dozens or hundreds of interfaces.
- AWS deployment on EC2 with RDS PostgreSQL, ALB, CloudWatch, and Multi-AZ failover
- Azure deployment on VM Scale Sets with Azure Database for PostgreSQL and Monitor
- Docker and Kubernetes container deployment options with health checks and auto-restart
- Infrastructure-as-code templates (Terraform and CloudFormation) for repeatable provisioning
- VPN, Direct Connect, and ExpressRoute connectivity for secure on-premise integration
Open Integration Engine is fully compatible with MirthSync — Saga IT's open-source tool for managing integration engine channels as version-controlled code. MirthSync connects to your OIE instance via the REST API, serializes channels into human-readable files, and enables Git-based workflows including branch development, pull-request code reviews, and automated CI/CD promotion across environments. This is the same DevOps toolchain we use across all our Mirth Connect and OIE managed service clients.
- MirthSync CLI pull/push operations for OIE channel synchronization with Git
- GitHub Actions and Jenkins CI/CD pipelines for automated channel promotion
- Pull-request workflows with diff-based code reviews for JavaScript transforms
- Multi-environment promotion (dev → staging → production) with automated validation
- MirthSync VS Code Extension for direct channel editing in your IDE
Our managed services team provides 24/7 monitoring and administration for OIE environments. We handle version upgrades, JVM performance tuning, database maintenance, SSL certificate rotation, and proactive channel troubleshooting so your integration team can focus on new development. Monitoring is powered by MDDS Console — our AI-assisted diagnostics platform — which provides real-time visibility into channel throughput, message errors, queue depth, and system health across all your OIE instances.
- 24/7 monitoring with alerting on channel errors, queue backup, and system health
- MDDS-powered diagnostics with AI-assisted root cause analysis for message failures
- JVM optimization including heap sizing, garbage collection tuning, and thread pool configuration
- Database maintenance with index optimization, message pruning, and backup verification
- Version upgrade management with compatibility testing and staged rollout procedures
We provide hands-on OIE training for integration teams who want to build in-house capability. Our training program covers OIE administration, channel development patterns, JavaScript transform authoring, MirthSync workflows, and production troubleshooting. Whether your team is new to integration engines or migrating from another platform like Rhapsody, Cloverleaf, or Corepoint, we accelerate their OIE proficiency with structured training modules and real-world exercises.
- OIE Administrator training covering installation, configuration, and user management
- Channel development workshops for HL7 v2, FHIR, and database channel types
- JavaScript transform authoring with debugging techniques and performance patterns
- MirthSync workflow training for Git-based channel management and CI/CD pipelines
- Production troubleshooting labs with real-world message failure scenarios
OIE vs Mirth Connect vs BridgeLink
Open Integration Engine, Mirth Connect, and BridgeLink all serve the healthcare integration engine market — but they differ significantly in licensing, protocol support, and ecosystem compatibility. This comparison helps you evaluate the right platform for your organization.
| Feature | Open Integration Engine | Mirth Connect (NextGen) | BridgeLink |
|---|---|---|---|
| License | Open Source (MPL 2.0) | Commercial | Commercial |
| Core Engine | Mirth Connect fork | Mirth Connect 4.x | Custom |
| HL7 v2 | |||
| FHIR R4 | |||
| DICOM | |||
| Open Source | |||
| Channel Compatibility | Mirth-compatible | Native | Proprietary |
| Cloud-Native Deployment | Partial | ||
| MirthSync Support | |||
| Community | Growing | Large | Small |
Mirth Connect to OIE Migration
Our proven five-phase migration methodology ensures zero downtime and full channel compatibility. Most migrations complete in 6-11 weeks depending on channel inventory size and custom library complexity.
Channel Audit & Compatibility Assessment
We inventory every channel, code template, custom Java library, and configuration map in your Mirth Connect environment. Each component is tested against OIE's runtime to identify any compatibility gaps — particularly custom JAR files, third-party connectors, or deprecated API calls that may require adjustment. The assessment report includes a risk-scored migration plan with effort estimates per channel.
OIE Environment Setup
We provision a production-grade OIE environment in parallel with your existing Mirth Connect instance. This includes the OIE application server, PostgreSQL database backend, network configuration, TLS certificates, and HIPAA-compliant access controls. If deploying to cloud, we use Terraform or CloudFormation templates for repeatable infrastructure provisioning.
Channel Migration & Testing
Channels are exported from Mirth Connect using MirthSync and imported into the OIE environment. Each channel undergoes functional testing with real message samples — including edge cases, error conditions, and high-volume throughput scenarios. Custom JavaScript transforms and Java libraries are validated to ensure identical processing behavior on both platforms.
MirthSync CI/CD Configuration
We configure MirthSync-based CI/CD pipelines for the new OIE environment, including Git repository structure, branch policies, pull-request workflows, and automated deployment pipelines. This establishes the DevOps foundation for all future channel development and ensures your team can manage OIE channels with the same Git-based workflows used in modern software development.
Parallel Run & Production Cutover
Both Mirth Connect and OIE run simultaneously processing the same message traffic. We compare output messages between platforms to verify identical processing behavior. Once validation confirms full parity, production traffic is switched to OIE with a documented rollback procedure in place. Post-cutover monitoring runs for a minimum of two weeks to catch any edge cases.
Get the Open Integration Engine
Free under MPL 2.0 — no per-server fees, no per-channel costs. The same engine, now community-maintained.
View All DownloadsOIE Installer
Full integration engine for Linux, Windows, and macOS — a free, drop-in replacement for Mirth Connect.
MirthSync Plugin
Git-based version control and CI/CD deployment for OIE and Mirth Connect channels.
Docker Image
Containerized OIE for cloud-native deployments — pull and start in seconds.
Common Questions
Open Integration Engine (OIE) is an open-source healthcare integration engine maintained by Qvera. It was forked from the Mirth Connect codebase after NextGen Healthcare transitioned Mirth Connect to a commercial-only licensing model in March 2025. OIE provides the same core capabilities as Mirth Connect — channel-based routing, JavaScript transforms, HL7 v2/FHIR/DICOM support, and a web-based administrator console — under the Mozilla Public License 2.0 (MPL 2.0). This means organizations can deploy and run OIE without per-channel or enterprise licensing fees. OIE is designed to be a drop-in replacement for Mirth Connect, maintaining full compatibility with existing channels, code templates, and configuration maps.
OIE and Mirth Connect share the same foundational codebase, but they are now separate products maintained by different organizations. Mirth Connect is developed and sold by NextGen Healthcare as a commercial product (also branded as NextGen Connect). OIE is maintained by Qvera as an open-source community project. Both platforms support the same channel formats, JavaScript transform engine, and connector types, which means channels built on one platform can be exported and imported into the other without modification. The key differences are licensing (OIE is free under MPL 2.0, Mirth Connect requires a commercial agreement), support model (OIE is supported by Qvera and consulting partners like Saga IT, Mirth Connect by NextGen), and long-term roadmap (each platform is evolving independently with different feature priorities).
Migration from Mirth Connect to OIE is straightforward because both platforms share the same channel architecture and Java runtime. The process involves five phases: first, audit your existing Mirth Connect environment to inventory all channels, code templates, custom Java libraries, and configuration maps. Second, provision an OIE environment in parallel with your Mirth Connect instance. Third, export channels using MirthSync or Mirth Connect's built-in export and import them into OIE. Fourth, validate each channel with functional testing using real message samples. Fifth, run both platforms in parallel, compare output, and cut over to OIE when testing confirms full parity. Most migrations complete in 6-11 weeks depending on the number of channels and complexity of custom transforms. Saga IT provides full migration services including planning, execution, and post-cutover support.
Yes. OIE supports FHIR R4 through the same HTTP sender and listener connectors available in Mirth Connect. You can build OIE channels that consume and produce FHIR resources using RESTful APIs — including Patient, Encounter, Observation, DiagnosticReport, and other resource types. OIE channels can handle FHIR Bundle transactions, support OAuth2 and SMART on FHIR authentication flows, and validate resources against US Core profiles. Since OIE shares the same connector architecture as Mirth Connect, any FHIR channel built on Mirth Connect will run on OIE without modification. Saga IT builds FHIR-native OIE channels for clinical data exchange, patient access APIs (CMS-9115), and TEFCA connectivity workflows.
Yes. MirthSync is fully compatible with OIE because both MirthSync and OIE communicate through the same REST API that Mirth Connect exposes. MirthSync connects to your OIE instance, pulls channel definitions into a local Git-tracked directory structure, and pushes changes back — exactly as it does with Mirth Connect. This enables the same DevOps workflows: branch-based channel development, pull-request code reviews for JavaScript transforms, automated CI/CD deployment pipelines, and multi-environment promotion (dev, staging, production). The MirthSync CLI, MirthSync VS Code Extension, and MirthSync Plugin all work with OIE without any configuration changes beyond the server URL. Saga IT includes MirthSync CI/CD setup as part of every OIE deployment and migration engagement.
Mirth Connect was available as open-source software under the Mozilla Public License (MPL) for over a decade, making it the most widely deployed integration engine in healthcare. In March 2025, NextGen Healthcare — which had acquired the Mirth Connect product through its purchase of Mirth Corporation — discontinued the free open-source distribution and transitioned to a commercial per-channel or enterprise licensing model. This change affected thousands of organizations that had been running Mirth Connect without a commercial agreement. In response, Qvera released Open Integration Engine (OIE) as a community-maintained fork that preserves the original open-source licensing terms. Organizations now have three options: adopt NextGen's commercial Mirth Connect licensing, migrate to OIE for continued open-source access, or evaluate alternative integration engines like Rhapsody, Corepoint, or Iguana.
Related Services
Explore More Services
Resources
Talk to an OIE Expert
Whether you're migrating to OIE or need ongoing support — the MirthSync team has you covered.