Mirth Connect 3.5.2, released on March 29, 2018, is a maintenance release that fixes some bugs present in Mirth Connect versions 3.5.1 and 3.5.0. We explain all the new features and how to download this update.
Mirth Connect is a well-known integration engine for healthcare systems, used by thousands of customers around the world, which allows the development of integrations and healthcare interoperability solutions in an agile and scalable way. Mirth Connect 3.5 brought with it many new features, improvements and fixes:
- Improvements in the management of channels, after the groups (appeared in 3.4), 3.5 allows labeling and filtering.
- Iterators for filters and transformers.
- Improvements in the handling of attachments.
- Other new features: REST API, DICOM Listener, security enhancements, etc.
Mirth Connect 3.5.2 is a maintenance update that fixes several bugs and brings other new features.
Changes in Mirth® Connect 3.5.2 #
This release fixes four bugs present in Mirth Connect versions 3.5.0 and 3.5.1. In all cases these are minor bugs that should not affect the operation of a production system.
In addition, along with the fixes, a new commercial extension Duo Multi-Factor Authentication has been released.
Bugs fixed #
The bugs that have been fixed in Mirth Connect 3.5.2 are:
Channel filtering in the Settings>Tags configuration does not work. #
The channel list is not filtered in the settings: Settings > Tags.
- This problem only affected Mirth Connect version 3.5.1.
- More information in: Filter in Mirth Connect Settings>Tags does not work.
If a channel ID does not exist, the command line can undeploy all channels. #
Because of this problem, when using the Mirth command line, if the channel ID does not exist, all channels are undeployed.
- This issue affected Mirth Connect versions 3.5.0 and 3.5.1.
- More information in: CLI can undeploy all channels if channel ID doesn’t exist.
Channels in the default group are not displayed on the dashboard until the channel cache is updated. #
As can be read in the description of the bug, the steps to reproduce it are:
- Start a new instance of Mirth Connect with no channels or groups, just the default empty group.
- Start two instances of the Administrator.
- Make sure that both are in Group mode.
- Leave an instance of the Administrator in the dashboard refreshing.
- In the other instance of the Administrator, create a new channel in the default group and deploy it.
- In the first instance of Administrator, the newly deployed channel should appear, but it does not.
This bug has been fixed, so the default group channels will be updated correctly from this version onwards.
- This bug affected Mirth Connect versions 3.5.0 and 3.5.1.
- More information in: Channels in the default group don’t show on the dashboard until channel cache is updated.
Intermittent crashing of the Derby database while vacuuming the tables #
It is important to remember that the Derby database should NOT be used in production. With this in mind, this bug caused the database to crash intermittently when vacuuming tables.
- This bug affected Mirth Connect versions 3.5.0 and 3.5.1.
- More information in: Intermittent deadlock with Derby while vacuuming tables.
New Duo Multi-Factor Authentication commercial extension #
Along with Mirth Connect 3.5.2 the new commercial extension Duo Multi-Factor Authentication is released. This extension adds an additional layer of security to user accounts by allowing an additional device such as a mobile, tablet or phone line to be required for login.
How to upgrade to Mirth Connect 3.5.2 #
No specific upgrade instructions have been published for Mirth Connect 3.5.2 so no special action is required. In any case, it is always a good idea to review the update guides.
You can also review the release notes.
Download Mirth Connect 3.5.2 #
You can download Mirth Connect 3.5.2 from our Mirth Connect download page or from the NextGen® Healthcare website.
