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/prune events.

For the DELETE /channels/{channelId}/messages/{messageId} (Remove Message) API request, we changed the patient_id query parameter to patientId.

We renamed the User Authorization extension to the more standard name, Role-Based Access Control. All references to "User Authorization" in the User and Extension Guides, in-app UI elements, and the GitHub Wiki have been changed to "Role-Based Access Control". Going forwards, the User Authorization extension will be referred to as the Role-Based Access Control extension. Please note, the extension artifacts will still be named "auth".

The JAVA_HOME environment variable will now be higher in the list when launching the server.

If you only have one version of Java installed on your system then this doesn't matter. But if you have multiple versions installed, you may want to check to see that the Mirth Connect server is using the version of Java that you expect. You'll be able to see what version is being used in the server logs upon startup.

Note that you can also set the INSTALL4J_JAVA_HOME_OVERRIDE environment variable to have the server always use a specific Java installation regardless of what other environment variables may be set. On macOS/Linux, you can also edit the mcserver/mcservice file and uncomment INSTALL4J_JAVA_HOME_OVERRIDE at the top instead of setting it as an environment variable.