Mirth Connect is a integration engine for healthcare. Selecting the appropriate version of NextGen Mirth Connect can sometimes be a challenging decision.
The versioning system of Mirth Connect #
Understanding the version numbering system is the first step to making an informed choice. Each version is identified by three numbers in the format X.Y.Z, which increment with each new release. The first two numbers change in versions that introduce new features and functionalities, such as 4.4.0, 4.1.0, 3.9.0, 3.7.0, etc. In contrast, versions that only address bug fixes and issues change only the last number, like 4.4.2 or 3.7.1.
Choosing the right version of Mirth Connect #
Our rule of thumb is to always choose the most recent version that doesn’t end in zero. For instance, if you’re deciding between 3.6.2, 3.7.1, and 3.8.0, you should opt for 3.7.1.
This approach ensures selecting the version with the most advanced functionality (as represented by the first two numbers), but one in which major bugs and issues have been addressed (indicated by the third number being non-zero). This ensures that you are using a version of Mirth Connect that is both feature-rich and stable.
Sometimes released versions have no updates identified by the third number. For instance, versions 4.2.0 and 4.3.0 were not followed by a 4.2.1 or 4.3.1, respectively. This occurs when no bugs or problems are discovered in these versions that justify releasing an update. In these cases, we can consider different options:
- Continue using the version that fulfills the rule of being the most recent version not ending in zero, and do not update until there is another version that meets our rule.
- If the zero-ending version has been published for several months, and no known problems or bugs have emerged, we might consider using this version.
Newly released versions are great for testing, experimenting with new features, and learning, but for real integrations, we should only use well-tested versions we can trust.
Understand Mirth Connect versions licensing #
Mirth Connect previously utilized an open-source friendly licensing model. However, with version 4.6, Mirth Connect transitioned to a proprietary, closed-source license. This is a key change to note: if you do not have a commercial license for Mirth Connect, you retain the option to use any version up to 4.5.
Learn more about Mirth Connect license change.
Read the release documentation for each new version #
With each new version of Mirth Connect, several useful documents are published:
- What’s New: A document informing us about new features, major changes, improvements, and fixes. It’s informative and not meant to be exhaustive, but it helps us discover the main highlights of each version.
- Upgrade Guide: This guide contains important information related to upgrading from a previous version of Mirth Connect. We should consider it if we want to upgrade to this new version.
- Release Notes: This document details all the changes, fixes, and improvements in the new version. So, it is key to evaluating the impact and how it affects Mirth Connect’s evolution.
These documents not only help us get to know the new versions but also contain information about bugs, resolved issues, and improvements regarding previous versions that may affect versions we are using and help us plan the update strategies for our integrations.
You can find all this information in the GitHub releases page. Also, we publish an article with each new version of Mirth Connect where we summarize and clarify all this information. You can find these articles in the Mirth Connect versions articles category and in the related versions to download in our Mirth Connect downloads page.
Pay Attention to Known Security Alerts #
Mirth Connect is comprised of a large amount of code and uses many third-party libraries. Occasionally, a problem arises in the code or in one of the libraries that affects one or several versions of Mirth Connect and poses a security risk for our integrations.
It’s always crucial to ensure that the version we are using is not affected by any known vulnerabilities. If you are responsible for the security of the installation, it might be a good idea to subscribe to a source of information that provides published CVEs for Mirth Connect.
For example, a serious security alert was known as CVE-2023-43208 which affects all versions of Mirth Connect prior to version 4.4.1.
Conclusions for choosing a version of Mirth Connect #
When selecting a version of Mirth Connect, it’s important to balance the latest features with proven stability. Here are key takeaways to guide your decision:
- Test thoroughly: Before fully integrating a new version into your system, rigorously test it in a controlled environment.
- Stay informed: Keep up to date of the latest releases, updates, and security alerts. Knowledge is power, especially in maintaining a secure and efficient integration environment.
- Choose stability over novelty: While it’s tempting to immediately adopt the latest version, prioritize stability and reliability, especially for critical healthcare integrations.
- Take into account the license: versions up to 4.5 are open-source, from version 4.6 onward Mirth uses a proprietary license.
Remember, the right version of Mirth Connect for your organization is one that aligns with your specific needs, ensures data integrity, and maintains the highest security standards. Stay informed, stay secure, and choose wisely.
Additional resources:
