Relevant prior exams identified through fuzzy (low‑confidence) patient matching are now included when determining comparison relevancy. 

• Clinically relevant priors are no longer excluded due to minor identifier discrepancies. 

• Fuzzy‑matched exams continue to be clearly labeled, while behaving the same as other relevant comparisons. 

The image‑to‑order matching experience has been streamlined to reduce ambiguity and support more flexible workflows. 

• Matching can now be initiated from either:  

  • An unmatched HL7 order.

  • Images without an HL7 association. 

• The matching interface adjusts based on how the workflow is initiated. 

• Once a match is completed:  

  • HL7 data becomes authoritative.

  • Exam details and associated metadata are updated automatically. 

• All matching actions are fully audited for traceability. 

Reading physicians can now manage and reorganize structured statement sections more efficiently. 

• Individual line items containing numbered or bulleted content (e.g., Impression, Recommendations, Assessment) can be reordered. 

• Statements can be dragged, moved up/down, or removed. 

• Numbering automatically updates as changes are made.

Order Processing Rules (OPRs) now respond to later‑arriving DICOM data, not just exam creation.

• Rules can fire when new DICOM series arrive after an exam is created. 

• Triggering behavior is configurable per rule. 

• Safeguards protect exams that are locked, already reported, or manually validated. 

• This reduces the need for manual reprocessing when images arrive asynchronously. 

The OPR authoring experience has been improved for readability and transparency.

• DICOM tags now display human‑readable descriptions. 

• A new Source column indicates whether a rule is based on DICOM or HL7 data. 

• Rules can be filtered by source.

• The “Add Tag” action has been renamed to reflect support for both tags and tasks. 

• Newly created rules automatically scroll into view. 

The platform now supports seamless, context‑aware Epic integration for supported facilities. 

• Opening a study can automatically launch the corresponding Epic patient chart. 

• Patient context remains synchronized between the platform and Epic during reading.

• Epic integration is configured at the facility level. 

• The launch process runs in the background and does not block clinical workflows. 

Version 11.0.0 introduces a new numeric date format in the default speech engine. The existing month-name format is unchanged and continues to work alongside the new format. 

Users can now dictate dates using month number, day, and year — without saying the month name. Speak the month as a number (1–12), followed by the day, followed by the year as a two-digit pair. 

“ten twenty two twenty nineteen” → 22-OCT-2019

Tip: Always say the month number first, then the day, then the year — for example, “ten” (October), “twenty two” (22nd), “twenty nineteen” (2019).

The original month-name format continues to work exactly as before:

“April fifteenth twenty twenty three” → 15-APR-2023 

“April fifteenth two thousand twenty three” → 15-APR-2023

Month Name → April fifteenth twenty twenty three → Existing 

Numeric (MM DD YY…) → ten twenty two twenty nineteen → New in 11.0.0

Building on the PowerScribe integration introduced in version 10.0.0, the platform now supports bidirectional communication via an inbound connector, allowing PowerScribe to drive study navigation and status updates within the Workflow and Reporting Platform. 

• PowerScribe can open or close a specific study in the platform directly, keeping both applications in sync without manual navigation. 

• Study status updates initiated in PowerScribe are automatically reflected in the platform — Final signings trigger the standard sign workflow, while Preliminary or Dictated statuses return the user to the worklist. 

• The platform confirms active connectivity to PowerScribe when queried, ensuring the integration remains responsive throughout the reading session. 

• All inbound connector interactions are fully audited, and multi-window behavior is preserved so that only the primary window responds to inbound requests. 

The electron-based reporting only workflow now supports bi-directional integration with the Radiology Station application of Change Healthcare Radiology Solutions using the Change Healthcare Radiology Solutions Inbound Connector. Radiologists can launch images directly in Radiology Station from the workflow and reporting platform into the Radiology Station. 

• Clicking the eye icon in the reporting application automatically issues an OpenStudy command to the Inbound Connector, opening the selected exam in the Radiology Station by accession number. 

• When the user exits an exam via Sign, Close, or Return to Worklist, a CloseStudy command is automatically sent to Change Healthcare Radiology Solutions to keep both systems in sync. 

• If the viewer launch fails, a clear error message is displayed, and the event is recorded in the exam audit trail for troubleshooting. 

• All image launch events are fully audited on the exam record, capturing the user, study accession number, Study Instance UID, date and time, and source system. 

• This integration applies exclusively to the Electron app workflow; web-based workflows are unaffected. 

Referring physicians can now open studies directly from an EMR without requiring a separate login. The launch experience is secure, context-aware, and designed to support referring-physician workflows in line with modern enterprise imaging platform expectations. 

• Selecting a “View Images” action in the EMR launches the platform and opens directly to a modified exam details page and exam list for the correct patient. 

• From the exam details page, the referring physician can launch images in the viewer for the selected exam and relevant priors, with no additional authentication required. 

• Access is restricted to the intended patient and exam context; invalid, expired, or unauthorized launch requests are rejected. 

• All access events are fully audited on the exam, capturing the user, Order ID, accession number, date and time, source system (EMR), and IP address. 

• The initial release supports end-to-end integration with Epic. If the viewer fails to launch, an error is displayed in the UI and captured in the audit trail. 

The platform now supports automatic archiving of studies to one or more configured destinations, triggered when an exam reaches a specified status. This eliminates the need for manual archiving and ensures studies are reliably sent to archive targets as part of the standard workflow. 

• Each DICOM destination can be configured with an auto-archive status (Pending, Inflight, or Completed); an archive job is automatically created the first time an exam reaches that status. 

• Automatic archiving can be enabled independently per destination; a single exam may be archived to multiple destinations, each with its own configured trigger status. 

• The system maintains archive state per exam and destination (Archived, Failed, Unknown), ensuring that subsequent changes to an archived exam trigger IOCM messages rather than duplicate archive jobs. 

• Archive jobs are routed via a dedicated Gateway Pub/Sub channel per destination; the Gateway performs a C-FIND check before pushing to transmit only missing instances. 

• A new Jobs tab in Gateway Management displays archive, DICOM, and IOCM job history with timestamps, status, failure reasons, and a retry action, filterable by job type and date.