Advanced Visualisation (AV) integrations are presented to users in two places: the Third-Party Integrations multi-select in facility details, and the “Launch in native app” menu on the exam detail page. The delivered labels carried vendor company prefixes, and integrations that were not requested for the 14.0.x releases were still visible in the list. 

AV integration labels have been aligned with the requested naming, and the list has been limited to the integrations requested for 14.0.x. 

• Canon Vitrea is now displayed as Vitrea. 

• Segami Oasis is now displayed as OASIS. 

• Brainlab TraumaCad is now displayed as TraumaCad. 

• CARPL AI is now displayed as CARPL. 

• AIDOC is now displayed as Aidoc. 

• TeraRecon is unchanged. 

• The Third-Party Integrations option list in facility details reads exactly: Aidoc, CARPL, OASIS, TeraRecon, TraumaCad, Vitrea — in that order. 

• Integrations that were not requested for 14.0.x — Orthoview, DynaCAD and Mirada XD — are no longer shown in the user interface. 

• The “Launch in native app” menu on the exam detail page displays the same names, in the same order, as the facility settings list. 

• Saved configuration is unaffected. Selecting and deselecting an integration continues to store the same underlying values, and existing facility configurations carry over without any change or reconfiguration. 

With Allow Manual Query Retrieve enabled in Facility Settings, requesting images for an unmatched exam using the cloud download icon left the in-progress indicator displayed indefinitely and no images were delivered to the exam. 

The retrieval requests were being raised and processed correctly by the platform. The requests were not being routed onward because routing for DICOM prefetch is configured per facility on the gateway, and the required configuration was not in place. That configuration has been added and manual retrieval has been confirmed working end to end. 

• The in-progress icon remains displayed until images are retrieved, rather than remaining in progress indefinitely. 

• Once images arrive, the eye icon becomes active and the file count on the exam is updated. 

• Configuration note: DICOM prefetch routing is set per facility on the gateway. Any newly created facility that will use manual query and retrieve must have this routing configured before the feature is available to its users. 

The backend platform version identifier has been updated to 14.0.3 so that the version reported by the platform matches the released build. This is an internal change with no impact on user-facing functionality. 

When a radiologist sent an exam to Support Request status from the Electron app, a success message was displayed and immediately followed by the error “Order cannot be reassigned in support tab”. The user was not returned to the worklist, and every subsequent action on the exam produced the same error, leaving the exam effectively unusable until the application was restarted. 

The Electron app previously released the exam assignment whenever a user left an exam without changing the report. Exams in Support Request cannot be unassigned, which is what produced the error. The application no longer attempts to release the assignment when an exam is in, or is moving into, Support Request status. 

• Sending an exam to Support Request now produces the success message only. No error message is displayed.

• The user is redirected to the Worklist page (Inflight tab) as expected. 

• The exam remains fully actionable after the status change. 

• The issue was specific to the Electron app; the same workflow in the browser was not affected and is unchanged. 

Under Accounts → Facility Group → Connections, the Environment MS status panel returned no entries, so microservice status, working pod counts and versions could not be reviewed from the interface. The Group MS status panel alongside it was unaffected. 

The cause was environment configuration rather than application logic, and it has been corrected. No application changes were required.

• The Environment MS status panel again lists each microservice with its name, status, working pods, timestamp and version. 

• No changes have been made to the Connections tab itself or to the way status is reported. 

The Electron app opens with a prefilled user email configured on the server. If that email was replaced with a different valid user, sign-in succeeded but exams opened from the CHRS study list did not open in the Electron app. 

Open-exam requests are now validated against the user signed in to the session. Exams open normally when a user signs in with an account other than the prefilled one, including after signing out and signing back in as a different user. 

Recurring database statement timeout errors were being recorded in the backend, associated with elevated latency on exam event requests. The load originated primarily from DICOM ingest activity and from worklist queries sorted by turnaround time. 

This release reduces the database and cache load generated by those operations. These are performance changes only — worklist behaviour, sorting results and exam data are unchanged. Further improvements are planned for a subsequent release. 

When a finding was written as a numbered list item and the radiologist ran the AI Report Assistant, a correction applied within that list item could break the sentence into several separate list items. 

Corrections are now applied inline, within the list item they belong to. A sentence that occupied one list item before the AI run remains one list item afterwards, regardless of how many corrections were applied to it. All other Report Assistant behaviour is unchanged.