Loading...
Recommendations
Explore
After the Upgrade
Java JVM parameters:
Restore the changes in your backed up "
*.vmoptions"
files to the corresponding
*.vmoptions
files in "
mirth_home"
.
CLI configuration:
Restore the changes in your backed up "
mirth_home
/conf/mirth-cli-config.properties"
file.
Start/Restart the server
.
Custom extensions:
Install new versions of any custom extensions.
After the Upgrade
Mirth® Connect by NextGen Healthcare User Guide
Before You Upgrade
Before upgrading, NextGen Healthcare highly recommends that you backup both your Mirth® Connect Server Configuration and your Mirth® Connect database using the following steps. Note: mirth_home directory. Backup server configuration: Before proceeding, it is important that you backup your existing server configuration. This can be done through the Mirth Connect Administrator (Settings>Server Tab>Server Tasks – Backup Config). The server configuration includes channels, code templates, alerts, and global scripts. User accounts and stored messages will not be backed up. Backup database: If you use the embedded Derby database, create a backup of the "mirth_home/appdata/mirthdb" folder. Note that appdata is the database folder as defined in the "mirth_home/conf/mirth.properties" file. For additional information, see mirth.properties File. If you use an external database (for example, PostgreSQL, MySQL), create a backup of your database using your preferred database administration tool (for
Mirth® Connect by NextGen Healthcare User Guide
4.2.0 Upgrade Notes
Updates for the 4.2.0 release. Removed the Remove All Events Button We removed the Remove All Events button in the Events screen to comply with Cures certification security requirements. If developers need to remove all events, they can use the Prune Events in the Data Pruner tab of the Settings screen. This is the preferred method to remove or prune events. Changed the patient_id Query Parameter Naming Scheme for the Remove Message API Request For the DELETE /channels/{channelId}/messages/{messageId} (Remove Message) API request, the patient_id query parameter is changed to patientId. Renamed the User Authorization Extension to Role-Based Access Control The User Authorization extension is changed to the more standard name, Role-Based Access Control. All references to "User Authorization" in the user and extension guides, application user interface elements, and the GitHub Wiki, are changed to "Role-Based Access Control". Going forward, the User Authorization extension will be referred
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
3.5.0 Upgrade Notes
Important: Mirth® Connect by NextGen Healthcare 3.5 and above now require a minimum version of Java Runtime Environment (JRE) 8. Please ensure that you have Java 8 (or later) installed first before attempting to upgrade. Due to the recent SWEET32 vulnerability, we have disabled cipher suites using Triple DES. If for any reason you need to use one of these cipher suites to communicate with a legacy system, you can re-enable it in mirth.properties with the https.ciphersuites setting. If you are using the SSL Manager extension, then you can choose to enable these cipher suites on a specific channel / connector rather than for the entire server. If you have any connectors using the SSL Manager that are not using the server default cipher suites, then you will want to update these connectors and deselect any cipher suites containing "3DES". To address the secondary "nation state resources" theoretical use-case of the Logjam vulnerability, in 3.5 we're now setting the ephemeral Diffie-Hellma
Mirth® Connect by NextGen Healthcare User Guide
Version-Specific Upgrade Instructions
If you are upgrading to one of the versions listed in the following sections, view the version-specific upgrade instructions. If you are upgrading through multiple versions, be sure to review all version upgrade instructions that you are upgrading through. 4.6.1 Upgrade Notes This topic covers the improvements and new features included in Mirth® Connect version 4.6.1. Parent topic: Upgrade Guide
Mirth® Connect by NextGen Healthcare User Guide
To Edit the mcserver.vmoptions file
Access the folder in which Mirth® Connect is installed. Note: The mcserver.vmoptions file can typically be found in the following location: Windows: C:\Program Files\Mirth® Connect\mcserver.vmoptions MacOS: /Applications/Mirth® Connect/mcserver.vmoptions Open the mcserver.vmoptions file. Set -Djava.awt.headless=false. Save the updated file. Parent topic: Mirth Connect Debugger
