Enhanced Comparison Relevancy with Fuzzy Matching |
|---|
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.
|
Match Images to Order — Improved Matching Workflow |
|---|
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.
|
Reorder Impression Statements in the Report Editor |
|---|
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 Triggered by New DICOM Series |
|---|
Order Processing Rules (OPRs) now respond to late‑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.
|
OPR UI Enhancements for Clarity and Usability |
|---|
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.
|
Epic Patient Chart Launch from Synthesis |
|---|
Synthesis 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 Synthesis 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.
|