Closed jbocce closed 6 months ago
@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.
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)
Need to add ultrasound bidirectional tool to More Tools menu
Need icon for More Menu. @dan-rukas to update
We need more test data for this. Need images that can measure velocity
See icon in #3819
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.
What feature or change would you like to see made?
Changes to make include...
Why should we prioritize this feature?
By supporting this, measurements on ultrasounds will be calibrated properly and the correct units will be displayed.