Draft Status
Draft - team will hold off on page creation
Category
DICOM
Key Investigators
- Deepa Krishnaswamy (Brigham and Women's Hospital, USA)
- Andrey Fedorov (Brigham and Women's Hospital, USA)
- Chris P. Bridge (Massachusetts General Hospital, USA)
- Dave Dinh (Brigham and Women's Hospital, USA)
- Tina Kapur (Brigham and Women's Hospital, USA)
Project Description
Our team has built a 3D Slicer extension for ultrasound anonymization, annotation, and adjudication (https://github.com/SlicerUltrasound/SlicerUltrasound). We are currently trying to port the functionality of these tools to OHIF in order to make the processing more streamlined for clinicians and avoid the downloading of additional tools.
However, we currently store all of our annotations as JSON. This can be problematic as JSON can be prone to misinterpretation; we had to write specialized software to load these annotations into Slicer, and we are missing much of the metadata to associate the file with the referenced image.
In this project, I want to see if using DICOM Structured Reports (SR) will help our use case. Having our files as SRs would help us to utilize the cloud and retain all important metadata. But it might also make processing more complicated. Therefore, the goal of this week is to see how much effort is needed to add functionality to Slicer/OHIF for Ultrasound Multi-frame Image Storage.
Objective
- Create support for Ultrasound Multi-frame Image Storage in Slicer and OHIF
Approach and Plan
- Create a DICOM Structured Report for our annotations using Ultrasound Multi-frame Image Storage (both pleura line and B-line points/lines, and manual annotations like pleural percentage)
- Add functionality to 3D Slicer core for loading, parsing, and viewing these SRs.
- Make sure that the SR can be loaded into the official OHIF viewer.
- Add functionality to the OHIF
usAnnotation extension to save the annotations as an SR
- Deploy OHIF with
usAnnotation to connect to the cloud (Google Healthcare DICOM datastore)
Progress and Next Steps
- Converted our JSON annotation file to a DICOM SR
- Confirmed the DICOM SR can load in OHIF
- Started implementing changes to Slicer core to view this type of annotation SR
Illustrations
Current workflow:
Successfully loaded the converted annotations in OHIF!
https://github.com/user-attachments/assets/dd84c277-2fd6-47e2-a331-e47ff4af16ad
Background and References
No response
Draft Status
Draft - team will hold off on page creation
Category
DICOM
Key Investigators
Project Description
Our team has built a 3D Slicer extension for ultrasound anonymization, annotation, and adjudication (https://github.com/SlicerUltrasound/SlicerUltrasound). We are currently trying to port the functionality of these tools to OHIF in order to make the processing more streamlined for clinicians and avoid the downloading of additional tools.
However, we currently store all of our annotations as JSON. This can be problematic as JSON can be prone to misinterpretation; we had to write specialized software to load these annotations into Slicer, and we are missing much of the metadata to associate the file with the referenced image.
In this project, I want to see if using DICOM Structured Reports (SR) will help our use case. Having our files as SRs would help us to utilize the cloud and retain all important metadata. But it might also make processing more complicated. Therefore, the goal of this week is to see how much effort is needed to add functionality to Slicer/OHIF for Ultrasound Multi-frame Image Storage.
Objective
Approach and Plan
usAnnotationextension to save the annotations as an SRusAnnotationto connect to the cloud (Google Healthcare DICOM datastore)Progress and Next Steps
Illustrations
Current workflow:
Successfully loaded the converted annotations in OHIF!
https://github.com/user-attachments/assets/dd84c277-2fd6-47e2-a331-e47ff4af16ad
Background and References
No response