BridgeLink: The Open-Source Mirth Connect Fork (2026 Guide to Releases and Migration)
Digital Growth Lead
Writes about healthcare technology, interoperability, and AI-driven transformation across modern care systems.

Updated October 2026
BridgeLink is an open-source healthcare integration engine from Innovar Healthcare, built as a fork of the last open-source release of Mirth Connect (4.5.2) and licensed under the Mozilla Public License 2.0. It runs Mirth Connect channels, so teams that do not want a commercial Mirth license can move their HL7, FHIR, X12 and database interfaces to BridgeLink and keep getting updates.
This guide covers what BridgeLink is today, how its releases changed in 2026, how it compares with Open Integration Engine (OIE) and licensed Mirth, and how to migrate. For the bigger picture, start with our guide to Mirth Connect. If you want a team to run the move, our Mirth Connect integration services cover BridgeLink assessments and migrations.
What BridgeLink is
BridgeLink is a Mirth Connect fork that a company maintains, rather than a volunteer community alone. Innovar Healthcare, led by founder and CEO Loyd Bittle, started it after NextGen Healthcare moved Mirth Connect 4.6 to a closed-source enterprise license on 19 March 2025.
- License: Mozilla Public License 2.0, the same license as the original open-source Mirth Connect (shown on the BridgeLink GitHub repository).
- Code base: forked from Mirth Connect 4.5.2, so Mirth channels, code templates and the Administrator workflow carry over.
- Who uses it: one public example is the New York HIE HEALTHeLINK, whose technology partner Technology By Design chose to move from Mirth Connect to BridgeLink (Healthcare IT Today, August 2025).
- Where to get it: installers for Windows, macOS and Linux and Docker images from Innovar's download page and Docker Hub, and three editions on AWS Marketplace. The desktop Administrator opens through the BridgeLink Administrator Launcher, which Innovar publishes as open source on GitHub and which also opens open-source Mirth Connect servers.
We ran the same channel on Mirth Connect, OIE and BridgeLink side by side:
Watch: Mirth Connect vs Open Integration Engine vs BridgeLink: One Channel, Three Engines (2:30).
BridgeLink releases in 2026: from 4.6.1 to 26.9.0
BridgeLink began on Mirth's numbering (4.5.4 in July 2025, 4.6.1 in January 2026) and then switched to year.month versions. Read the notes before skipping releases, because several 2026 releases change Java, web server and driver requirements on purpose.
| Release | Date | What matters for an upgrade |
|---|---|---|
| 4.6.1 | 8 January 2026 | Last release on Mirth's version numbering |
| 26.3.0 | 7 April 2026 | Requires Java 17 or later; Jetty upgraded from 9.4 to 12.0; dependency upgrades for a list of CVEs; SMTP OAuth 2.0; configurable HTTP listener header size |
| 26.6.0 and 26.6.1 | 22 July and 16 September 2026 | Continued CVE work; 26.6.1 is a security patch |
| 26.9.0 | 1 October 2026 | Built-in Derby needs Java 21; jTDS driver removed, so SQL Server channels must switch to the Microsoft driver; Sybase dropped; WebAdmin ships with the server |
Two changes in 26.9.0 can stop a server from starting. If your server uses the built-in Derby database on Java 17, it will not start until you move to Java 21 or an external database. If any channel uses a jdbc:jtds:sqlserver:// connection string, change it to jdbc:sqlserver://host:port;databaseName=db with the driver class com.microsoft.sqlserver.jdbc.SQLServerDriver before you upgrade, because nothing rewrites it for you.
BridgeLink editions and add-ons
The engine itself is free and open source. Innovar sells cloud editions, add-ons, training and support around it.
- AWS Marketplace editions: Developer, Standard and Enterprise. Innovar's Standard listing describes production hardening such as integrated SSL and multi-factor authentication; the Enterprise listing adds AI-powered automation, OpenAI integration and auto-scaling with high availability.
- Add-ons listed on the download page: WebAdmin (browser-based administration), OIDC single sign-on, Lookup Manager for lookup tables, and SIEM event log forwarding.
- Support and training: sold by Innovar. Ask Innovar for current support terms; we did not find published support prices in October 2026.
BridgeLink vs Open Integration Engine vs licensed Mirth
All three run the same kind of channels. The difference is who stands behind the code and what you pay.
| BridgeLink | Open Integration Engine | Mirth Connect 4.6+ | |
|---|---|---|---|
| License | MPL 2.0, open source | MPL 2.0, open source | Commercial enterprise license, closed source |
| Who leads it | Innovar Healthcare, with community contributions | A vendor-neutral community, in Eclipse incubation since September 2026 | NextGen Healthcare |
| Latest release (Oct 2026) | 26.9.0 (1 Oct 2026) | 4.7.0 (21 Oct 2026) | 4.7.x |
| Java | 17+, and 21 with built-in Derby from 26.9.0 | 17 from 4.6.0 | 17 from 4.7.0 |
| Paid support | From Innovar | From independent partners | From NextGen |
| Fits best | Teams that want open source with a company and cloud editions behind it | Teams that want a community project and slower, steadier changes | Teams that want the original vendor and its commercial extensions |
If you are still deciding whether to leave 4.5.2 at all, our guide for teams still on Mirth Connect 4.5.2 walks through every path. For engines outside the Mirth family, see the Mirth Connect alternatives comparison.
How to migrate from Mirth Connect to BridgeLink
Moving from Mirth to BridgeLink is mostly an export, a Java and database check, an import and a careful test. The steps below are the order we follow.
1. Inventory and export
Export every channel, code template, global script and server configuration from the Mirth Administrator, and back up the database. List custom libraries, extensions and every database connection string, because jTDS strings and Java 8 only libraries are what break first.
# check the export is complete
find exported_channels -name "*.xml" | wc -l # should match your channel count
grep -rl "jdbc:jtds" exported_channels/ # channels to fix before BridgeLink 26.9.0 2. Choose Java and the database
Install Java 17 or later. If you plan to run 26.9.0 on the built-in Derby database, use Java 21; for production, prefer an external database such as PostgreSQL or SQL Server.
3. Install BridgeLink
Use the installer for your platform, an AWS Marketplace edition, or the Docker image. Docker Hub tags follow the release and Java version, for example innovarhealthcare/bridgelink:26.9.0-dhi-slim-jdk17, which suits an external database.
docker pull innovarhealthcare/bridgelink:26.9.0-dhi-slim-jdk17 4. Import and fix
Import code templates and global scripts first, then channel groups and channels, and keep them undeployed. Change jTDS connection strings to the Microsoft driver, and update any custom code that used removed libraries.
5. Replay real messages
Deploy channels one at a time on a test server and replay de-identified copies of real traffic. Compare every output with what Mirth produced for the same input.
6. Run in parallel, then cut over
Where partners allow it, run Mirth and BridgeLink side by side on live traffic for an agreed period. Cut over in a quiet window, watch ACKs and volumes closely for the first days, and keep the Mirth server ready to restart until the rollback window closes.
Running Mirth and BridgeLink side by side
Large estates rarely move in one weekend. Run both engines, each with its own internal database, and move channels in batches from the lowest risk (file and database polling) to the highest (real-time ADT and results feeds). Use different admin and listener ports if both run on one host, and change one endpoint at a time so a problem points to one channel.
Is BridgeLink right for you?
BridgeLink fits teams that want to stay open source, need a vendor they can buy support and cloud editions from, and can keep up with release notes that change Java and drivers. Teams that want slower, community-led change often prefer OIE, and teams that want NextGen's own support stay on licensed Mirth.
Planning a BridgeLink move? Our integration team has built more than 350 interfaces on Mirth Connect. Tell us your Mirth version, channel count and the systems you connect, and we will send back a free written risk review of what is likely to break and which path fits. Request a free Mirth risk review, or explore our wider healthcare interoperability work.
Moving off Mirth 4.5.2? Get a free written risk review.
Share your Mirth version, channel count and connected systems. We send back what is likely to break on Java 17 and OIE 4.6, and which path fits: OIE, BridgeLink or licensed Mirth. From a team that has built 350+ Mirth Connect interfaces.
Frequently Asked Questions
What is BridgeLink?
Is BridgeLink a fork of Mirth Connect?
Does BridgeLink run Mirth channels and HL7 interfaces?
Is there a BridgeLink Docker image?
What is the latest BridgeLink release?
What is the BridgeLink Administrator Launcher?
Is BridgeLink free?
How is BridgeLink different from Open Integration Engine?


