Release notes: Workflow and reporting
Unresolved Anomalies - Workflow and Reporting
The following limitations and anomalies have been identified as of the current release. Limitations and anomalies can include known errors, flaws, failures, or faults that cause the product to behave in an unintended manner or produce an incorrect or unexpected result or known inconsistencies in its behavior that potentially may limit its applicability in specific workflows or usages.
Unresolved Anomalies Register
Summary | Description | User Impact |
|---|---|---|
Uploading a prior report to an existing exam creates a duplicate prior card in the comparison exam list. | This results in the same exam appearing across multiple prior cards with report data split between them. | Exam data may appear split across cards – i.e. one card for images and one for the report. There is no workaround available at this time. This issue does not affect image integrity or patient safety, but it may cause some disruption during report review workflows and prior exam navigation. |
Exams closed from the Completed tab in PowerScribe One (PSOne) may become locked with the message "system is currently processing the exam." | When a user closes an exam from the Completed tab in PSOne (i.e., after it has been reported), the exam may become incorrectly locked and no further action can be taken. | Users should avoid selecting Cancel in PowerScribe One after viewing a completed exam. Instead, users are requested to navigate to another case or exam, or close the exam from PACS. Locked exams require manual intervention by technical support to remove the lock from the database. |
Users without save permissions can view and configure the Presentation State save option in the Hanging Protocol modal, but no save occurs. | If a user's Create/Update ACL for Save GSPS/Annotations is disabled, the "Save Image Edits" toggle in the Hanging Protocol modal may still appear visible and configurable in some configurations. The toggle is non-functional in this state — no Presentation State is created or updated — but the UI does not currently reflect the disabled permission. | Users without save permissions may attempt to configure and save Presentation States via the Hanging Protocol modal without receiving an error. The save action will silently fail. No image data or Presentation State is affected. Users who need to save Presentation States should confirm with their administrator that the appropriate permission is assigned to their role. This will be corrected in a future release. |
Annotations are not displayed after a user removes all Presentation States and creates a new one. | If a user has previously saved a Presentation State and subsequently hides or removes all Presentation States to begin a new one, annotations from the newly created Presentation State are not displayed until the user explicitly selects or toggles a Presentation State from the Available Presentation States panel. | Users may incorrectly conclude that their annotations were not saved. Annotations are retained and intact. To restore display, the user should open the Presentation States panel and select the desired Presentation State. No data loss occurs. |