Mirth went commercial.Your path is open source.
NextGen discontinued open-source Mirth Connect in March 2025. The community built the path forward: OIE reads your Mirth database directly, so your channels, extensions, and API all carry over.
NextGen ended open-source Mirth Connect.
In March 2025, NextGen Healthcare discontinued the open-source release of Mirth Connect, the industry-standard healthcare integration engine used by thousands of organizations worldwide for nearly two decades.
Version 4.5.2 is the last open-source release. Starting with version 4.6, Mirth Connect requires a commercial license with recurring fees.
For organizations that built their integration infrastructure on Mirth Connect's open-source foundation, this created an urgent question: what now?
The community answered.
Mirth Connect released as open-source healthcare integration engine
Quality Systems Inc. (later NextGen Healthcare) acquires Mirth Corporation
Open-source discontinued at v4.5.2. Commercial-only from v4.6.
OIE community fork launched, open source continues
Why this matters for your organization.
Running unsupported software in a regulated industry creates compounding risk.
No security patches
Open-source Mirth Connect 4.5.2 will not receive security updates. Vulnerabilities discovered after March 2025 remain unpatched, a growing risk for organizations handling PHI.
No community fixes
Bugs in 4.5.2 will remain unfixed. The open-source community that contributed patches and improvements for two decades has moved on to the forks.
Vendor lock-in risk
Mirth Connect 4.6+ requires a commercial license with recurring fees. Upgrading for security patches means accepting proprietary terms and ongoing costs.
Compliance gaps
Auditors will ask about your patching cadence. Running end-of-life software in a healthcare environment creates documentation and compliance challenges.
The community built the Open Integration Engine.
Within months of NextGen's announcement, the community ensured Mirth Connect's open-source legacy would continue.
Open Integration Engine (OIE)
Community Fork- What it is
- The community fork of Mirth Connect, created when NextGen ended the open-source line at 4.5.2. Same channels, extensions, API, and database schema, so an existing Mirth install carries over.
- License
- MPL 2.0. No license fee.
- Current release
- OIE 4.6.0, generally available since July 2026: Java 17 minimum, 24 CVEs remediated through dependency upgrades.
- Governance
- A non-profit steering committee and a separate maintainer group; development happens in the open on GitHub.
- Support
- Independent vendors offer commercial support and services, Saga IT among them.
- Where it lives
- openintegrationengine.org, the documentation, and GitHub.
- With OpenShare
- Create a free account, connect your engine, and administer it from the browser. Console, Gateway, Monitoring, and Drivers are free forever.
OpenShare works with all open-source forks.
OIE, BridgeLink, or any Mirth Connect-compatible engine. The OpenShare Gateway is fork-agnostic, install it on whichever engine you choose.
OIE
Mirth ConnectThen modernize with OpenShare.
The experience layer your integration engine was missing.
Administer from your browser.
OpenShare Console replaces the legacy Java desktop client with a full browser-based administration console. Channel editing, message browsing, monitoring, and DICOM viewing, from any device.
Reach your servers from anywhere.
The OpenShare Gateway gives your engine secure remote access without VPNs or open ports. Your data stays in your data center. You administer it from wherever you are.
Join something bigger.
Every OpenShare Gateway installation adds a node to the direct transfer network. Find organizations in the Contact Directory, exchange data directly, and grow the ecosystem with every connection.
Migration is a plugin install, not a rip-and-replace.
Three steps. Minimal downtime. No data loss.
Create your free account
Get the Open Integration Engine with the OpenShare Gateway pre-installed. OIE is binary-compatible with Mirth Connect, same Java runtime, same database schema.
Move your channels
Point OIE at your existing Mirth Connect database, or export and import your channels. All channels, code templates, and extensions carry over directly.
Connect from your browser
Open OpenShare Console and access your server. No Java client, no VPN. Manage channels, monitor messages, and exchange data directly on the network.
Already on Mirth Connect or OIE? The OpenShare Gateway works with any Mirth-compatible engine. You don't have to migrate to OIE to use OpenShare. See our documentation to get started on your existing engine.
Compare your options.
See how the migration paths stack up.
| Feature | Mirth OSS 4.5.2 | Mirth Commercial 4.6+ | OIE / Fork (standalone) | OIE / Fork + OpenShare |
|---|---|---|---|---|
| Security patches | None | |||
| Browser-based admin | ||||
| Remote access (no VPN) | ||||
| Direct data transfer | ||||
| DICOM viewer | ||||
| Analytics | Basic | |||
| Cost | Free | Paid license | Free | Free |
| License type | MPL 2.0 | Proprietary | MPL 2.0 | MPL 2.0 + Free SaaS |
| Vendor lock-in | None | Yes | None | None |
Weighing a different engine instead? See how OIE + OpenShare compares with Rhapsody, Corepoint, Cloverleaf, and Iguana, or browse every engine comparison.
Frequently asked questions.
Yes. OIE reads Mirth Connect's database schema directly. Your existing channels, extensions, API integrations, and configuration all carry over. Same Java runtime, same database, same deployment model.
No. The OpenShare Gateway works with Mirth Connect, OIE, or any Mirth Connect-compatible fork. You can use OpenShare with your existing Mirth Connect 4.5.2 installation without migrating to OIE.
Yes. OIE reads Mirth Connect's database schema directly. You can point OIE at your existing Mirth Connect database and all channels, code templates, and extensions will be available immediately. You can also export and import channels between instances.
Yes. Contact Saga IT for enterprise support, implementation services, and Business Associate Agreements (BAAs). Saga IT are active contributors to the OIE project and have completed hundreds of healthcare integration projects.
Mirth Connect 4.5.2 will continue to run indefinitely, it is installed software on your servers. However, it will not receive security patches, bug fixes, or community updates. Over time, this creates increasing risk for organizations in regulated industries like healthcare. Migrating to an actively maintained fork like OIE ensures continued security patching and community support.
Ready to move forward?
Create a free account and connect your engine. Console, Gateway, Monitoring, and Drivers are always free.
