Mirth Connect™ got you here. OIE takes you further.
When NextGen took Mirth Connect™ proprietary, the community built OIE — an open source fork that preserves everything you've already built. Your channels, your templates, your skills — they all carry forward.
In March 2025, NextGen Healthcare announced that Mirth Connect™ would move from a dual-license model to a fully proprietary, commercial license starting with version 4.6. That means rising costs, closed source code, and a roadmap controlled by a single vendor.
For organizations that chose Mirth Connect™ because it was open, affordable, and flexible — that deal changed.
OIE is Mirth Connect™ — without the lock-in
The Open Integration Engine is a community-driven fork of Mirth Connect, built by the people who relied on the open source version and weren't willing to lose it. OIE is licensed under the Mozilla Public License 2.0 — free to use, free to modify, and not controlled by any single vendor.
OIE is governed by its community, with transparent decision-making and a long-term path toward non-profit stewardship. Multiple organizations contribute to its development, and a growing ecosystem of commercial vendors — including NovaMap — provide support, plugins, and services around it.
Your existing work doesn't start over
OIE is a direct fork of the Mirth Connect™ codebase. That means high compatibility with your existing setup.
Channels and configurations
Export your channels from Mirth Connect™, import them into OIE. The same XML-based format, the same channel architecture.
Code templates and scripts
Your JavaScript code templates, global scripts, and configuration maps carry over. The code you've written still works.
Connectors and protocols
HL7, FHIR, DICOM, database connectors — the core integration capabilities are the same.
Migration tooling
Open source tools like mirthSync and Mirth Migrator support moving channels, templates, and configurations between Mirth Connect™ and OIE.
Your team's skills
If your team knows Mirth Connect™, they know OIE. The interface, the channel model, the development workflow — it's the same foundation.
You don't have to do this alone
NovaMap offers managed migration services to help you move from Mirth Connect™ to OIE with confidence. We handle the planning, execution, and validation — so your team can focus on running integrations, not managing a migration project.
Assessment
We review your current Mirth Connect™ environment — instances, channels, plugins, dependencies — and build a migration plan tailored to your setup.
Execution
We handle the migration: provisioning OIE instances, transferring channels and configurations, verifying connectivity, and testing end-to-end.
Ongoing support
Once you're running on OIE, NovaMap provides the platform and support to manage it in production — monitoring, alerts, team management, and expert help when you need it.
Get your team up to speed — fast
Whether your team has years of Mirth Connect™ experience or is picking up OIE for the first time, NovaMap's training courses bridge the gap.
Mirth Connect™ to OIE Conversion Course
A focused course for teams migrating from Mirth Connect™. Covers what's different in OIE, how to work with the NovaMap Portal, and best practices for running OIE in production.
OIE Fundamentals
Starting fresh? This course covers the core concepts — channels, connectors, transformers, and deployment — from the ground up.
Platform Training
Learn how to use the NovaMap Portal for engine management, monitoring, team administration, and support workflows.
The cost of staying is going up
Mirth Connect™ 4.6+ requires a commercial license. That means license fees, renewal negotiations, and a roadmap you don't control. As the open source version ages without updates, you're choosing between paying more or falling behind on security and features.
OIE gives you a path forward that preserves your investment, keeps your code open, and puts the community — not a single vendor — in control of the roadmap.
