The End of Open Source Mirth Connect – What’s Next?

Mirth Connect 4.5.2 is the last open-source version published by NextGen Healthcare. In a statement released in March 2025, NextGen confirmed that they will no longer maintain the dual license model for Mirth Connect.

Starting from Mirth Connect 4.6, the platform will become closed source and only available as a commercial product. This marks a significant shift for a tool that has been a cornerstone in healthcare integration for years.

NextGen has published a seven-page FAQ document outlining the reasons for this change and answering common concerns. You can find a link to the document at the end of this post.

Mirth Connect has long been an excellent integration engine, and it’s disappointing to see the open-source version discontinued. However, since all the source code for version 4.5.2 is still available—and given how widely used Mirth is in healthcare IT—there is reason to be optimistic.

It’s likely that a community fork will emerge, with developers continuing to build on top of the 4.5.2 base. Ideally, such a fork would provide feature updates, bug fixes, and security patches, ensuring that the open ecosystem lives on.

If you’re aware of any active forks or community-led projects continuing Mirth Connect development, please share them in the comments below. I’d love to hear more.

Thanks for reading!

You can also see my video on the topic here

Probably old news, but the open source fork is here: https://openintegrationengine.org (Open Integration Engine · GitHub)

Cheers

1 Like

Welcome to the community and thanks for sharing the link!
I think it will be useful for people for looking for the open source version.

1 Like

I did some research and indeed it seems the most viable option to move to after next gens Mirth Connect is https://openintegrationengine.org/ as linked by @uarmstrong previously.

If you do some online research the only other viable options would seem to be GitHub - Innovar-Healthcare/BridgeLink: The open-source backbone of healthcare interoperability. but this seems to be a partially commercial approach forked already 3 years ago.

Checking the other Mirth Connect forks you can find several but the one listed here with the most stars is BridheLink

So personally based on this research I would go with the https://openintegrationengine.org/

There is a free TLS plugin for Mirth Connect available now as well