Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] OHIF should support US Region Calibration - Sequence Of Ultra Sound Regions (0018,6011) #3721

Closed
jbocce opened this issue Oct 12, 2023 · 9 comments
Assignees
Labels
Design Added fixed-in-dev-await-release This issue is fixed in master (viewer-dev) but we are pending testing for release (viewer.ohif.org)

Comments

@jbocce
Copy link
Contributor

jbocce commented Oct 12, 2023

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.

@james-hanks
Copy link

james-hanks commented Oct 25, 2023

@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

@beavermml
Copy link

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

@sedghi
Copy link
Member

sedghi commented Nov 18, 2023

@sedghi
Copy link
Member

sedghi commented Nov 28, 2023

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

  1. 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)

image

  1. If there are multiple regions and the measurement crosses the region it should be identified and gives pixel measurement

Region Data Type Velocity

image

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)

@james-hanks
Copy link

Need to add ultrasound bidirectional tool to More Tools menu

@james-hanks
Copy link

Need icon for More Menu. @dan-rukas to update

@james-hanks
Copy link

We need more test data for this. Need images that can measure velocity

@james-hanks
Copy link

See icon in #3819

@sedghi sedghi added the fixed-in-dev-await-release This issue is fixed in master (viewer-dev) but we are pending testing for release (viewer.ohif.org) label Apr 10, 2024
@sedghi
Copy link
Member

sedghi commented May 1, 2024

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.

@sedghi sedghi closed this as completed May 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Design Added fixed-in-dev-await-release This issue is fixed in master (viewer-dev) but we are pending testing for release (viewer.ohif.org)
Projects
None yet
Development

No branches or pull requests

6 participants