New and Updated Features |
May 15, 2025 Release |
| Account | The URL has changed to https://<ip_address>/app/#/account. It is no longer ...ui/#/account/. |
| The account page has been updated to a more recent framework. As a result, some minor cosmetic changes have occurred; for example, some buttons have changed their appearances. |
| Security questions have been removed because they are no longer required for signing in. |
| Subscription alerts have been removed. |
| If the organization has been configured for it, the user may add their email address for the forgot password workflow. |
| Admin: Access Tokens | Other than the token ID, all fields can now be edited. |
| The provider field has been removed. |
| Admin: Configuration | Configuration is updated to match available files and sections. All 8.x-specific documentation has been moved to the 8.x documentation section. |
| MaintenanceMode temporarily prevents all users except script writers and admins from logging into the system while under maintenance. |
| Admin: Data Management | There are some cosmetic changes to data management. |
| Store Name and Store Number columns are reversed. |
| A Sort By Number toggle is added. |
| The Builds tab has been removed. |
| The side details pane has been updated. |
The records screen can now handle viewing files over 5 MB.
|
| Admin: Groups | Group Type is added to identify the purpose of the group. |
| Several of the searchappliance_* roles have changed. |
| A new group, clinical_reports, has been added. It grants access to measures sets. These sets allow users to see the measures reports. |
| Admin: Launchpads | Dashboards has been renamed to Launchpads. |
| Admin: License | A license page is added to provide the status. |
| Admin: Running Reports | Running Reports allows administrators to abort and view currently running reports. |
| Admin: Set Definitions | Labels have been updated for better clarity. |
The table and the side details pane now read Set Created and Set Status.
|
| The Delete Set button has changed to Delete Built Set to clarify that you're removing only the set, not the set definition. |
The Save and Create button has changed to Save and Run.
|
| Admin: Sharing | It is now possible to search by the report ID. |
| The list of reports has been split into two tabs—Reports and Queries. |
| We've added a reminder box at the top of the edit sharing screen to remind those sharing reports to review the report for security vulnerabilities that may open the system to malicious attacks. |
| Admin: Symbols | The Apply Changes option has been removed from the drop-down, and changes are automatically applied. |
| Admin: Uploader | You can change file names through the gear icon, so all file names can (and should) be unique. |
| Errors now have a message pop-up at the bottom of the screen instead of the file line being highlighted. |
| JSON files can now be uploaded. |
| File sizes can now be up to 10 MB. |
| Admin: Users | A list of password requirements is provided to help reduce the number of tries to create or reset a password. |
| You can now add a script user for those who only need access to IMAT APIs. |
| Administrators cannot unlock a user; they must use Disable instead. Accounts are now only locked if users enter an incorrect password six times. |
| There are cosmetic changes to the detail pane that appears when a user is clicked. |
| Disabling a user will close the user's session immediately. |
| API | APIs periodically delete old unnamed results, and the middleware runs without a cron job. |
| Session handler timeout now requires a value of five minutes or greater. |
| Branding | The same logo location is used across all application parts. This means that all logos for all applications now match. |
| Clinical Reports | Report Help has been added to the user menu. It will take you directly to the Query Syntax guide. |
| Configuration | Configuration files use Git, and file-based backups are no longer needed. |
| The JSON configuration file formatting now indents four spaces to prevent Git merge conflicts due to spacing differences. |
| Documentation | Documentation is removed from the product and moved to its own platform. All documentation is for the most recent release unless otherwise noted in the article. The help links will still direct you to the correct documentation page. |
Launchpad
(formerly known as Dashboard) | The Dashboard name has been renamed to Launchpad. All occurrences of "Dashboard" are automated to update to read "Launchpad." |
| The list of tiles that can be selected has been modified to reflect the apps available—all beta labels have been removed, and available tiles have been updated. |
| When a new cluster with no launchpads on it yet exists, a button providing a link to Admin: Launchpads appears. |
| Login/Keycloak | The sign-in page can be themed, but you should contact professional services for help. |
| User password recovery through email is configured through Keycloak. Contact professional services if you want to enable this feature. |
| MPI | MPI-related searches have updated paging to use onspace, onref, and onshard headers.
|
| Platform Services | You can tombstone records in batches based on search query results.
|
| Reports | There is an artifact URL update when using get_url(). The path changed from /api/reports/results/{result_id}/output/{path} to /api/reports/result/{result_id}/output/{path} (the s from results has been removed). However, no change is required when writing reports unless you are hard-coding artifact links. |
The VHR lib code is refactored to avoid running VHR init code when importing from the lib directory in reports. |
| ROI Management | Part 2 consent records use random URIs instead of hashing data to create them. This prevents overriding a revoked consent and forces a new consent record to be created. |
| ROI | Both ROI Management and ROI Setup are now internationalization-ready. |
| SearchServer | Relevant sets are deleted when a store’s data is deleted.
|
Using Kafka, stores can be taken offline and brought back online.
|
| Usage Logs | Fluentd is no longer used to process API usage logs because the API directly interfaces with a Kafka topic. |