Why we replaced Mirth Connect

Mirth Connect has been the standard for healthcare integration for over 15 years. Thousands of hospitals worldwide rely on it — and for good reason. But the world has changed, and what you need from an integration server in 2026 is no longer what you needed in 2010.

The problem with Mirth

We ran Mirth in production for years. We know it. We like it. And we know exactly where it hurts:

• Configuration in a database, not versionable. Who changed the channel last night? Which version was running in week 23? Mirth doesn’t know — and neither do you.
• No live testing. Want to change a transformer? Have fun spinning up a test environment with real production traffic.
• Performance limits under high throughput. At 500 msg/s the air gets thin. At 3,000 msg/s Mirth is out.
• Command Center not available in the EU. For German hospitals, a showstopper.

Our answer: Brio-IO

Brio-IO takes everything that’s good about Mirth — the channel architecture, the scripting flexibility, the protocol coverage — and makes it radically better:

• Git as the Single Source of Truth. Every change with author, timestamp and diff. Branch protection. Pull requests. Real version control, not database snapshots.
• Live-Shadowing. Mirror real traffic into a shadow channel and compare the result — before you deploy to production.
• 3,500+ msg/s full pipeline. Scales horizontally without you having to rebuild your channels.
• DE/EN/ES out of the box. UI, error messages, docs — all localized.

What comes next

Brio-IO is in Early Access. If you want to replace or connect real interfaces, write to us — we’ll set you up with access. Over the coming weeks we’ll follow up with tutorials, migration guides from Mirth, and deep dives into individual features.

If healthcare integration is your thing — stay tuned.