4.1.0 Upgrade Notes

Mirth® Connect by NextGen Healthcare User Guide

3.9.0 Upgrade Notes

SMB Versions in a File Reader/Writer We added support for SMB versions 2 and 3 when using a File Reader/Writer. With "smb" as the selected method, select the wrench icon to view the SMB settings. There you can select the minimum and maximum supported SMB versions. When upgrading Connect, existing channels will use "SMB v1" as the minimum version and "SMB v3.1.1" as the maximum version, in order to preserve functionality. However, SMB v1 is outdated and poses security risks, so we recommend updating your channels to use later versions of SMB. This may require also updating your SMB servers accordingly. DICOM Sender Storage Commitment In 3.9.0 we changed the functionality of the DICOM Sender option "Request Storage Commitment". Before 3.9.0, if a DICOM Sender with this option set to "Yes" failed to get a response to its storage commitment request, the sender would log an error to the server log but the message would still be considered successful. Now, in 3.9.0, if a DICOM Sender with th

Mirth® Connect by NextGen Healthcare User Guide

4.3.0 Upgrade Notes

Application upgrades for the 4.3.0 release. New Functionality for the Mirth® Connect Setup Wizard New features are added to the Mirth® Connect Setup Wizard that include, but are not limited to, the following: Added more information on the screens with links to the What's New, Upgrade Guide, and documentation. This helps users understand what information to enter on the screens. Added the ability to install your extensions at the time the application is installed or upgraded. This simplifies the process so that users no longer have to install extensions manually and restart the service. Added the ability to enter your license key for extensions. This will default to the license.key value from your mirth.properties file during an upgrade. Added the updated logo and a list of each dialog screens so that users know exactly where they are in the process. Resource Classloaders Load Classes Child-First By Default Resources now load classes "child-first" instead of "parent-first" by default. I

Mirth® Connect by NextGen Healthcare User Guide

4.6.0 Upgrade Notes

This topic coveres the improvements and the new features included in Mirth® Connect version 4.6.0. Change in Licensing Model With the release of 4.6, Mirth® Connect has transitioned from a dual license model (open-source and commercial) to a single Enterprise license model that is closed-source and proprietary. This change is designed to enhance the quality and reliability of our product, ensuring that you receive the best possible experience. Upgrading to Mirth® Connect 4.6 is similar to previous releases. However, if you are using an open-source version, you need to contact our sales team at mirthconnectsales@nextgen.com to obtain a license, this allows you to download the software. For current clients, you can download the software from the Success Community and proceed with the upgrade as usual. For more details about this change please refer to our FAQs. Updating Custom Extensions To update the custom extensions, refer to the topic 4.6.0 Updating Custom Extensions. New Docker Imag

Mirth® Connect by NextGen Healthcare User Guide

3.7.0 Upgrade Notes

Commercial License Key As of 3.7 commercial extensions now require a license key to be set in mirth.properties. The machine running Connect also must have outbound internet access so that our licensing server can be reached. Before upgrading, contact the help desk through our NextGen Healthcare Success Community to get your license key. Using Mirth Appliance When installing the 3.7.0 update, a wizard will prompt you to enter the license key: Standalone Installation Edit conf/mirth.properties Add a setting with key "license.key" and your license key for the value Restart the Connect service Database Connection Pools In previous versions, there was a connection pool dedicated to the Donkey engine (message processing), and a separate pool dedicated to everything else, like Administrator or API actions. In 3.7, this has been changed somewhat. You have two options: Option 1: Use two pools, one read/write and one read-only This is the default in 3.7. To enable, set this in mirth.properties:

Mirth® Connect by NextGen Healthcare User Guide

3.8.0 Upgrade Notes

In version 3.8 we upgraded the MySQL JDBC driver to version 8.0.16, so that the latest MySQL 8.x can be used. However the new driver doesn't support versions of MySQL older than 5.6. Since these older versions are over 10 years old and are already listed as End-Of-Life by Oracle, we have made the decision to adjust our system requirements to reflect that 5.6+ is now the minimum supported version for MySQL. If you still need to connect to an older version of MySQL, do not worry you still can! Connecting via a Database Reader/Writer or in JavaScript Download the appropriate MySQL JDBC Driver JAR for the version of MySQL you need to connect to. Place this JAR into a folder of your choice on the system running Mirth Connect. Create a new library resource (Settings -> Resources tab) pointing to that folder. Link your connector/channel to your new resource (Summary tab -> Set Dependencies). Make sure you are using the old driver class name, "com.mysql.jdbc.Driver". Using an Old Version of My

Mirth® Connect by NextGen Healthcare User Guide

3.0.2 Upgrade Notes

Channel Updates The Database Reader no longer prepends table name to the column name or alias regardless of how many tables are used in the query. Each element name in the generated XML will be the alias if one exists, otherwise it will be the column name. Users connecting to Postgres or Oracle databases with the Database Reader connector should not be required to make any changes. Users connecting to other databases should update their channels accordingly if needed. It is recommended to always use a unique alias. Note: Code templates in 3.0.0 and 3.0.1 were not being restricted from certain JavaScript scopes based on their context. Users upgrading from these versions to 3.0.2+ should check their code templates to ensure their contexts are correctly set. See MIRTH-3150 for more information. Parent topic: Upgrade Guide

4.1.0 Upgrade Notes

Warning: Open issue with SMB File Reader/Writer

Update log4j Library

Recommendations

3.9.0 Upgrade Notes

4.3.0 Upgrade Notes

4.6.0 Upgrade Notes

3.7.0 Upgrade Notes

3.8.0 Upgrade Notes

3.0.2 Upgrade Notes

3.9.0 Upgrade Notes

4.3.0 Upgrade Notes

4.6.0 Upgrade Notes

3.7.0 Upgrade Notes

3.8.0 Upgrade Notes

3.0.2 Upgrade Notes