Open Integration Engine (OIE) Consulting & Migration
Open Integration Engine (OIE) is the vendor-neutral, MPL 2.0 community fork of Mirth Connect — same channel format, same Java runtime, no commercial license. Saga IT delivers full lifecycle OIE services: migration from Mirth Connect, channel development across HL7 v2 / FHIR R4 / DICOM / EDI, AWS and Azure cloud deployment, channels-as-code DevOps, and 24/7 managed support.
OIE Consulting Services
From Mirth Connect migration to greenfield OIE deployments on Kubernetes, our team covers the full lifecycle of the Open Integration Engine — the vendor-neutral, MPL 2.0 community fork. Pick a capability to see what the work looks like.
Migrate from Mirth Connect to OIE without losing a message
OIE shares the same channel format, JavaScript runtime, and connector architecture as Mirth Connect — channels export from Mirth and import directly into OIE without modification. Our 5-phase migration methodology runs both engines in parallel, compares output message-by-message, and cuts over only when validation confirms full parity. Most migrations complete in 6-11 weeks.
- Full channel inventory + compatibility audit against OIE runtime
- Custom Java library + JavaScript transform validation
- Parallel-run cutover with message-comparison reconciliation
- Documented rollback plan + 2-week post-cutover monitoring
Production-grade OIE channels
We build OIE channels for every major healthcare standard — HL7 v2, FHIR R4, DICOM, EDI X12, and database/file/web-service transports. OIE shares Mirth Connect's connector architecture, so channel patterns we've refined across hundreds of Mirth deployments transfer directly to OIE.
- HL7 v2 (ADT, ORM, ORU, SIU, MDM, DFT) over MLLP/TCP
- FHIR R4 REST with OAuth2 + US Core validation
- DICOM C-STORE / C-FIND / C-MOVE / Modality Worklist
- EDI X12 claims + eligibility workflows
OIE on containers, AWS, Azure
OIE's open-source MPL 2.0 license eliminates per-channel fees, which makes container-first deployments dramatically more cost-effective than commercial Mirth Connect at scale. We deploy OIE on AWS EKS, Azure AKS, or self-hosted Kubernetes with autoscaling, RDS PostgreSQL Multi-AZ, helm-managed releases, and HIPAA-compliant network isolation.
- Kubernetes deployments on EKS / AKS with autoscaling
- Docker images with health checks + auto-restart
- Terraform / Pulumi modules for repeatable cloud infra
- VPN, Direct Connect, ExpressRoute for on-premise integration
We run your OIE environment 24/7 — with the same DevOps you'd use for Mirth
Our OIE managed-services tier mirrors what we deliver on Mirth Connect: MirthSync-driven Git workflows for channel-as-code, GitHub Actions or Jenkins CI/CD, MDDS Console AI-assisted diagnostics, and 24/7 SLA-backed monitoring. MirthSync works on OIE without any configuration changes beyond the server URL — same REST API, same workflows.
- MirthSync CLI + GitHub Actions CI/CD for OIE channels
- MDDS Console diagnostics for failed-message triage
- Channel-level uptime SLAs (99.95% on critical feeds)
- Version upgrade management + staged rollouts
Channel Types
OIE Speaks Every Major Healthcare Standard
OIE inherits Mirth Connect's full connector architecture — every channel type below runs identically on either engine.
HL7 v2
ADT, ORM, ORU, SIU, MDM, DFT over MLLP/TCP with ACK/NAK retries and Z-segment coverage.
FhFHIR R4
RESTful FHIR with OAuth2, Bundle transactions, US Core profile validation, Bulk $export.
DcDICOM
C-STORE, C-FIND, C-MOVE, WADO-RS for PACS, modalities, and VNA integration.
EXEDI X12
837/835 claims, 270/271 eligibility, 276/277 status workflows.
DbDatabase
PostgreSQL, SQL Server, Oracle, MySQL — readers, writers, stored-procedure execution.
FsFile / SFTP
CSV, XML, JSON, flat files over SFTP/SCP/SMB with locking + dedup.
WsWeb Service
SOAP and REST endpoints — webhooks, AWS API Gateway, third-party APIs.
Migrating from Mirth Connect? MirthSync exports your channels into a Git repo and imports them into OIE without modification.
Planning a Mirth Connect to OIE migration, or running a greenfield OIE deployment? Let's scope your project.
Talk to an OIE ExpertFree, Vendor-Neutral, Mirth-Compatible
OIE replaces commercial Mirth Connect with a community-governed, MPL 2.0 open-source build that runs your existing Mirth channels without modification.
No per-channel fees. No per-server fees. No enterprise license. Run as many channels as you need under MPL 2.0.
Stewarded by a non-profit Steering Committee, with contributors and supporting vendors from multiple healthcare IT companies — including Saga IT.
Channels exported from Mirth Connect 4.x import directly into OIE. Same JavaScript runtime, same connectors, same admin console.
OIE forked from a post-fix Mirth Connect codebase, so it's clear of the CVE-2023-43208 CISA-KEV RCE that affects every Mirth Connect installation before 4.4.1.
OIE vs Mirth Connect vs BridgeLink
Open Integration Engine, commercial Mirth Connect, and BridgeLink all serve the healthcare integration engine market. OIE and BridgeLink are both open-source MPL 2.0 forks of Mirth Connect; commercial Mirth Connect 4.6+ is NextGen's proprietary path. 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 | Open Source (MPL 2.0) |
| Core Engine | Mirth Connect fork | Mirth Connect 4.x | Mirth Connect fork |
| Maintainer | Non-profit Steering Committee (vendor-neutral) | NextGen Healthcare | Commercial vendor |
| HL7 v2 | |||
| FHIR R4 | |||
| DICOM | |||
| Open Source | |||
| Channel Compatibility | Mirth-compatible | Native | Mirth-compatible |
| Cloud Deployment | Partial | ||
| MirthSync Support | |||
| Community | Multi-vendor, growing | Large | Single-vendor-led |
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.
Open Integration Engine on AWS, Azure, and GCP
OIE inherits Mirth Connect's Java-based architecture, so it deploys cleanly into the same HIPAA-eligible cloud baselines we use for commercial Mirth Connect — multi-AZ failover, encrypted PostgreSQL, infrastructure-as-code, and cloud-native observability — minus the per-channel license cost.
OIE on AWS
Our reference Open Integration Engine on AWS deployment runs OIE on EC2 (m6i auto-scaling across multiple Availability Zones) backed by RDS PostgreSQL Multi-AZ. Application Load Balancer terminates TLS 1.3; CloudWatch handles observability; S3 archives audit logs with lifecycle policies. Stack is HIPAA-eligible, BAA-covered, and provisioned via Terraform — channel deploys flow through MirthSync GitOps.
- EC2 Auto Scaling + ALB
- RDS PostgreSQL Multi-AZ + KMS
- CloudWatch + S3 audit
- Terraform + AWS SSM
- BAA-covered services only
OIE on Azure
Our Open Integration Engine on Azure baseline uses Virtual Machine Scale Sets for the OIE application tier and Azure Database for PostgreSQL Flexible Server (zone-redundant HA) for persistence. Application Gateway handles TLS + WAF; Key Vault stores secrets and certificates; Private Endpoints isolate the database. Bicep IaC, Azure-native HIPAA controls, HITRUST-eligible regions.
- VMSS + Application Gateway (WAF)
- Azure DB for PostgreSQL Flex
- Azure Monitor + Log Analytics
- Bicep / Terraform + DevOps
- HIPAA / HITRUST regions
OIE on GCP
Our Open Integration Engine on Google Cloud baseline runs OIE on GCE Managed Instance Groups (or GKE for container-native deployments) with Cloud SQL for PostgreSQL Enterprise Plus for regional HA. HTTPS Load Balancer fronts the cluster; Cloud Logging + Monitoring handle observability; Private Service Connect isolates Cloud SQL. Requires enrollment in Google's HIPAA program with a signed BAA covering in-scope services.
- GCE MIG or GKE Autopilot
- Cloud SQL PG Enterprise Plus
- Cloud Logging + Monitoring
- Terraform / Config Connector
- HIPAA-covered regions + BAA
Cloud deployment for OIE is delivered as part of our broader healthcare cloud services practice — same HIPAA-eligible AWS, Azure, and Google Cloud landing zones, FinOps optimization, and 24/7 managed services we apply to every healthcare workload. Container deployments are equally supported (see the OIE Docker image for ECS / EKS / AKS / GKE / Kubernetes), and Mirth Connect on AWS SQS covers asynchronous queue patterns that apply identically to OIE.
Engagement Patterns We Deliver
Pick a pattern to see how Saga IT runs OIE engagements in production. Four repeatable engagement shapes that anchor every OIE project — implementation, migration, day-2 administrator services, and 24/7 managed support.
OIE implementation services
Greenfield OIE implementation — from server install through channel design, transformer development, and production cutover. We deliver the open-source integration engine your hospital or vendor needs without the 12-month learning curve, and without NextGen Healthcare's commercial license. Includes HL7 v2, FHIR R4, and device interface scaffolding.
- OIE 4.x
- MPL 2.0
- Mirth-compatible
- AWS / Azure / K8s
- OIE server install on Linux, Windows, AWS, Azure, or Kubernetes with HA configuration
- Channel design with source/destination connectors and JavaScript transformers (Mirth-compatible format)
- HL7 v2 ADT, ORM, ORU, SIU, MDM, DFT message handling with ack patterns
- FHIR R4 REST connectors with OAuth 2.0 token management
- Production cutover plan with parallel-run validation and rollback procedures
Mirth Connect → OIE migration
Migration paths for organizations escaping NextGen Healthcare's March 2025 commercial license change, plus engine consolidation onto OIE. We move multi-hospital Mirth Connect clusters with channel inventories of 200+ interfaces while keeping HL7 traffic flowing — no message loss, no clinical downtime, no per-channel license fees on the other side.
- Mirth → OIE
- NextGen escape
- Engine consolidation
- Zero message loss
- Mirth Connect → OIE migration with channel-compatibility validation (MPL 2.0, channel-format identical)
- NextGen Healthcare commercial license evaluation and contract-exit support
- Multi-engine consolidation onto OIE (Rhapsody, Corepoint, Iguana → OIE)
- Multi-hospital cluster migration with parallel-run cutover (zero message loss)
- Custom JAR, code-template, and connector compatibility review against the OIE runtime
OIE administrator services
Day-2 OIE administration for health-system IT teams that don't have a dedicated integration engineer. Server tuning, channel deployment, queue health, JVM management, and version-controlled change management via MirthSync — our open-source CLI that brings Git workflows to OIE (and Mirth Connect, since the channel format is identical).
- MirthSync
- Git workflows
- Channel review
- JVM tuning
- JVM heap, garbage-collection, and database connection-pool tuning for sustained throughput
- Channel deployment workflows with MirthSync — version-controlled, environment-aware, peer-reviewed
- Queue health monitoring, error-channel triage, and dead-letter remediation
- OIE user, role, and channel-permission administration mapped to clinical IT RBAC
- Patch management, backup/restore validation, and DR drill execution
OIE managed services & support
24/7 managed support for OIE environments — proactive monitoring via MDDS Console, on-call interface engineering response within SLA, channel-level alerting tuned for clinical-criticality tiers, and post-incident root-cause analysis. Saga IT is an OIE-supporting vendor in the project's multi-vendor support ecosystem; the team that built MirthSync answers your pages.
- MDDS Console
- 24/7 on-call
- Healthcare SLAs
- RCA reports
- 24/7 on-call interface engineering response with healthcare-grade SLAs
- MDDS Console proactive monitoring — channel health, queue depth, error trends, throughput KPIs
- Clinical-criticality alerting (ADT vs DFT vs SIU tiers with separate escalation paths)
- Quarterly OIE health reports — capacity planning, JVM trends, channel risk register
- Post-incident RCA with documented remediation and OIE-config hardening
OIE in Production
Real-world Open Integration Engine engagements — from multi-state migrations to greenfield Kubernetes deployments to reference-lab routing networks.
Mirth Connect → OIE Migration (zero-downtime cutover)
A multi-state health system migrating production Mirth Connect 4.x channels to OIE with zero downtime — custom Java library validation and message-by-message parallel-run reconciliation across a multi-week cutover window.
channels: "production set"
custom_libs: "validated"
version: "4.5.x"
Running the Open Integration Engine on AWS? Buy our services through AWS Marketplace.
Procure through AWS Marketplace and draw down your committed AWS spend (EDP) — no new vendor onboarding, no new paperwork.
Links to the AWS Marketplace listing ↗ Common Questions
Open Integration Engine (OIE) is an open-source healthcare integration engine stewarded by a non-profit, vendor-neutral Steering Committee with a multi-vendor community of contributors and supporting vendors (including Saga IT). 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 a vendor-neutral open-source community project governed by a non-profit Steering Committee. 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 a multi-vendor ecosystem including 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 among the most widely deployed integration engines in healthcare. In March 2025, NextGen Healthcare — whose predecessor Quality Systems Inc. acquired Mirth Corporation in 2013 (and rebranded as NextGen Healthcare in 2019) — 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, a community of healthcare IT practitioners launched the Open Integration Engine (OIE) as a vendor-neutral, MPL 2.0 community fork governed by a non-profit Steering Committee. A second MPL 2.0 fork, BridgeLink, is supported by its maintaining vendor. Organizations now have several options: adopt NextGen's commercial Mirth Connect licensing, migrate to OIE or BridgeLink for continued open-source access, or evaluate alternative integration engines like Rhapsody, Corepoint, or Iguana.
Related Services
Explore More Services
Keep reading
Related resources
Talk to an OIE Expert
Whether you're migrating to OIE or need ongoing support — the MirthSync team has you covered.
- 15 min conversation
- Healthcare IT engineers, not sales
- Reply within one business day
Book a 30-min call · or email us and we'll reply within one business day.