Mirth Connect (also called NextGen Connect) is an integration engine that many hospitals and clinics use. It moves HL7 v2, FHIR, and other data between clinical systems.
A note on licenses: starting with version 4.6 (2025), Mirth Connect moved to a commercial license. The last open-source release is 4.5.2. Open Integration Engine continues as open source.
Open Integration Engine (OIE) is the community, open-source continuation of Mirth Connect. It uses the same channel format as Mirth 4.5.2.
Still on free Mirth 4.5.2? Read this.
On 10 September 2026, three high-severity security bugs in Mirth Connect were made public. They affect version 4.5.2, the last free version. NextGen fixed them only in the paid version 4.7.2.
If your server runs 4.5.2, you need a plan. You have four paths.
Your four paths
- A. Pay for Mirth 4.7.2. You buy a license from NextGen, upgrade, and test every channel again. This has the highest yearly cost. It fits large organizations that want a vendor contract.
- B. Move to OIE. This is our advice for most teams. OIE is free and open source. OIE 4.7.0 (October 2026) fixes all three bugs. It uses the same channel format, so most channels move over with little change. OIE 4.7.0 needs Java 17 or newer and has a few breaking changes, so we test every channel before the switch.
- C. Move to BridgeLink. We also support BridgeLink, another free engine based on Mirth.
- D. Move to another engine, such as Rhapsody or Iguana. Every channel must be built again. This is the most work. It makes sense only when you have another reason to change.
Cannot move at once? Protect your server now.
A move takes planning. Until then, a short “protect now” step lowers the risk:
- Close network access to the engine. Only the systems that need it can reach it.
- Give the engine’s database user only the rights it needs.
- Switch off risky features that you do not use.
- Then plan the move.
Mirth 4.5.2 Security Check: $900 fixed
We check one Mirth server and tell you what to do next. You get:
- A check of the version you run
- A check of network exposure: who can reach the engine and its admin ports
- A list of risky features that are switched on
- A written action plan: what to fix now, and which path fits you
Many teams follow the check with a move to OIE (from $2,500) and a monthly support plan ($300 per month). See Pricing.
Mirth to OIE migration
- A review of all your channels, code templates, and settings
- A side-by-side trial on OIE
- Every channel tested with your sample messages before the switch
- A cutover plan, so no message is lost or sent twice
- A rollback plan, in case something goes wrong
Plugins and extensions
We build plugins and extensions in Java and JavaScript. Our plugins work on Mirth, OIE and BridgeLink. We test one build on all three engines.
- Custom connectors and transformers for systems that the engine does not support well.
- Code templates. Shared code for parsing, mapping, and checks, so all your channels work the same way.
- Monitoring and alerting. You get an alert when a channel stops, a queue grows, or errors go up.
- Clear documentation: the source code, a build guide, and a short runbook for your team.
Channel audits and upgrades
We review your channels, find errors and slow points, and give you a clear list of fixes. We also upgrade engines to newer versions safely.
How we work
- Your message. You tell us your engine, its version, and what you need. If a call helps, we schedule a short one.
- Review and quote. We look at your current setup. You get a fixed price, or an estimate for larger work.
- Build. We do the work in a test environment and keep it under version control.
- Test. We test with your sample messages, including messages with errors.
- Go live. We make the change with your team and watch it closely in the first days.
- Support. An optional monthly plan keeps your engine and extensions up to date.
Your data stays with you
Patient data stays on your systems. We work through your secure remote access. We use test data whenever we can. The code we write for you is yours. We follow HIPAA-style privacy practices: the least access needed, no copies on personal devices, and a clean handover at the end.
InfoGleam is independent. We are not part of NextGen Healthcare or the Open Integration Engine project.
Need new interfaces too? See HL7 & FHIR Interfaces. Example prices are on the Pricing page.
Request a quote
Tell us which engine and version you use, and what you need. We usually reply within one business day.