Viewers
Viewers copied to clipboard
OHIF
[Feature Request] OHIF should support US Region Calibration - Sequence Of Ultra Sound Regions (0018,6011)
What feature or change would you like to see made?
Changes to make include...
- parsing each region
- when the length tool is applied, the region of each end point should be looked up and the appropriate measurement calculated and units displayed
Why should we prioritize this feature?
By supporting this, measurements on ultrasounds will be calibrated properly and the correct units will be displayed.
@sedghi to reach out during office hours/post to request ultrasound users for more data to help support use case
@sedghi to give @james-hanks contact info to schedule user interview
is there an update on this? its weird that OHIF viewer display correctly the measurement (mm) when using dicomlocal but when the same file is being used by dicomjson, it returned back to pixels
@beavermml Is your data ultrasound? have you read this? https://docs.ohif.org/faq#what-are-the-list-of-required-metadata-for-the-ohif-viewer-to-work
Based on our interviews with users, here is our plan
Based on different types that (https://dicom.innolitics.com/ciods/us-image/us-region-calibration/00186011/00186014) we will target for now two types, the Tissue and Velocity type since they are the most common types.
Region Data Type Tissue
- the calibrations will get added to handle correct scaling for each region if the full annotation lies within the same region, and the unit will get properly calculated (mm)
- If there are multiple regions and the measurement crosses the region it should be identified and gives pixel measurement
Region Data Type Velocity
The probe tool will get augmented to be able to give the y axis coordinate on the region based on the locations and baseline
Another tool will get implemented (USRegionClickTool) that has two modes, vertical or horizontal which requires two clicks and give either horizontal or vertical measurements of the unit (often time)
We just release the OHIF 3.8, you can find more details here https://ohif.org/release-notes/3p8/ If you still encounter this issue in 3.8, please re-open this.