Release Date: 13Jun24
Features:
-
Hotfix -Implemented a fallback for TransferSyntaxUID when it's missing in DICOM metadata, allowing images with unknown TransferSyntax to still be displayed.
Known limitations:
- Saving measurements requires STOW endpoint which may not be supported by some DICOMWeb datasources;
- Some datasources (ie Amazon HeathImaging) may not support all search queries and therefore search or filter on the study list will return no matches.
- Not yet recommended for use on mobile devices
Known anomalies:
- 231 Stack image sync toolbar is out of sync with actual sync state
- Description: When displaying a study with series that are auto-image synced, if user turns “off” the stack sync, it will turn “on” instead. Selecting it a second time will actually turn it “off”. When dragging display sets into view, that are syncable, the image stack sync is will be “on” in the new viewports, even though stack sync is “off”.
- Impact to User: No impact to users in current versions as auto-image sync could only be enabled in a hanging protocol and it is not in use for any hanging protocols in FlexView Diagnostic. Hanging protocols are not configurable by users. Thus, the end user can not create this state. The issue exists, but there is no way for an end user to experience this.
- Workaround:This anomaly does not affect users of FlexView Diagnostic. Thus, no user workaround is required.
- 537 Rounding Error in onscreen display of some calibrated measurements
- Description: There is a slight discrepancy in the displayed measurements due to a computational rounding error. This occurs when the software calculates the length of a line in pixels and then converts this measurement into millimeters, based on the predefined pixel-to-millimeter ratio. The original and entered spacing values used in this calculation can introduce small rounding errors.
- Impact: This issue does not occur consistently but may be more noticeable with certain levels of image zoom. The rounding error is minimal, generally within +/- 1% of the actual line length. For example, a calibrated measurement of 10mm might display as 9.99mm.
- Workarounds: No workaround needed as this anomaly will be fixed before the device is available to users.