Mirth Went Proprietary. Here’s What Comes Next.

In March 2025, NextGen Healthcare moved Mirth Connect from open-source to proprietary commercial licensing.

Version 4.5.2 was the last free release. No more patches. No more community updates. No more fixes for the edge cases your team has been filing for years.

If you run Mirth Connect, you already know this. You’ve probably been in meetings about it. You may still be in meetings about it. The 91,000+ users worldwide who relied on that open-source licence are all facing the same question, whether you’re a health tech startup in the UK or one of the 3,000 US organisations that built their entire integration layer on it.

A year on, three paths have emerged. None of them are great.

Path 1: Pay NextGen

NextGen now offers tiered commercial licensing: Enterprise, Silver, Gold, Platinum. Pricing isn’t public, but industry estimates reportedly put it at tens of thousands per year, per instance. Per-server, not per-interface.

For organisations that built their integration layer on a free tool, this is a significant new line item. And the product underneath is largely the same Mirth you’ve been running. Same architecture. Same interface. Same limitations. You’re paying for continued support on something you used to support yourself.

If your Mirth deployment is stable, well-documented and doing exactly what you need, this might be the pragmatic choice. But it’s not a step forward. It’s a subscription to stand still.

Path 2: Fork it

Two community forks appeared in 2025. BridgeLink (from Innovar Healthcare, now on AWS Marketplace, adopted by several New York HIEs) and Open Integration Engine (OIE, community-driven, support via NovaMap Health). Both are free under MPL 2.0.

Forks are reassuring in principle. The code lives on. The community carries it.

In practice, forks carry risk that’s easy to underestimate. Who maintains security patches? Who certifies compliance when the regulatory landscape shifts? Who do you call at 2am when an ADT feed stops and your ED is flying blind?

BridgeLink and OIE are community-maintained projects with dedicated contributors. But for many procurement teams, the question “who is contractually accountable for this software?” needs a clearer answer than a community can provide.

The forks keep Mirth alive. They don’t move the model forward.

Path 3: Do nothing

Stay on 4.5.2. It works today. It worked yesterday. It’ll probably work tomorrow.

This is the most popular path and the most dangerous one. Unpatched software in a healthcare environment is a compliance liability that grows every month. Known vulnerabilities don’t get fixed. New HL7 and FHIR requirements go unsupported. Your integration layer slowly fossilises while everything around it evolves.

The longer you wait, the more expensive the eventual migration becomes. Technical debt compounds like interest. And unlike interest, it comes due without warning.

The question nobody’s asking

All three paths assume the same thing: that the answer is more time spent on your integration layer. More configuration, more mapping, more maintenance. More of your team’s capacity absorbed by plumbing.

But the landscape has changed since Mirth was designed.

95% of healthcare still runs on HL7. That’s not going away. But FHIR adoption is accelerating (71% of organisations report active use, up from 66% a year ago). Regulatory mandates are tightening. The UK Data Use and Access Act is pushing standardised frameworks across the NHS. CMS-0057 hits in January 2027 in the US.

The volume and complexity of health data exchange is increasing. The integration engine model, where every organisation runs its own translation and routing infrastructure, was designed for a simpler time. It worked when you had a handful of point-to-point connections. It breaks when you need to connect to dozens of partners across multiple protocols, each with their own message formats and delivery requirements.

What if your engine could stay exactly where it is, and someone else handled the hard part?

What if you kept Mirth and stopped spending on it?

Synura doesn’t replace your integration engine. It sits alongside it.

Synura handles secure routing, internet connectivity and FHIR conversion before your Mirth instance is even involved. Your existing setup stays simple. You stop building and maintaining the connections that eat your team’s time. You stop mapping fields at 11pm on a Thursday.

You connect your system to Synura. Your partner connects theirs. Synura handles the translation (HL7 to FHIR, FHIR to HL7, or any combination), the routing, the delivery and the audit trail. Self-serve. Live in minutes, not the months you’re used to. Pricing starts at £49 per connection per month.

Your Mirth instance still does what it does well. Synura handles the part that was costing you engineering time.

Who this is for

If you’re a health tech startup trying to connect to your first hospital, you don’t need to hire an integration engineer or stand up your own infrastructure. You need a connection that works.

If you’re evaluating what comes after the Mirth licence change, you don’t have to choose between paying and forking. Keep your Mirth setup for internal routing and let Synura handle the external connections that cost you the most time.

If you’re an NHS trust or mid-size provider drowning in point-to-point connections that nobody fully understands, there’s a way to simplify without ripping everything out.

What comes next

The Mirth disruption forced a conversation that was overdue. Healthcare integration has been stuck in the same model for twenty years: install an engine, hire specialists, build and maintain every connection yourself. That model worked when it had to. It doesn’t have to any more.

The organisations that move first won’t just save money. They’ll move faster. Connect to new partners in days instead of months. Support new standards without a rewrite. Spend their integration team’s time on problems that actually matter instead of maintaining external connections.

Mirth going proprietary wasn’t the end of open-source integration. It was the moment that made everyone look at what they were actually spending their engineering time on.

There’s a forward path now. Your Mirth setup stays. The burden around it doesn’t have to.