Stream: implementers
Topic: DICOM-RT and FHIR
Radhika Verma (Apr 17 2019 at 15:12):
Hello,
Just wondering if anyone can shed some light on the DICOM RT implementation and the use of FHIR resources to support the additional attributes that DICOM RT requires.
Many thanks!
Lloyd McKenzie (Apr 17 2019 at 15:32):
@Elliot Silver ?
Elliot Silver (Apr 17 2019 at 16:42):
To date, DICOM and HL7 Imaging have taken the view that the specialized DICOM RT structure is the best vehicle for conveying RT information, accessed in FHIR through the ImagingStudy resource.
We recognize that there is certain information that might be useful in an EMR or reporting context which could be exposed as extensions to ImagingStudy, or as Observations, but we lack engagement from the medical physicists and registry owners who could identify what is important to capture and how to express it. A simple, single “dose” on a study incorrect.
On the other hand, if your question is about extracting information from FHIR, instead of HL7 v2, that can be used to populate DICOM RT objects, I expect most of the capability is already there, but no one has profiled it. I’m sure HL7 Imaging Integration would be happy to work with you to pursue that.
One final note, another obvious gap is the lack of a FHIR equivalent to IHE SWF. @René Spronk was asking about that recently. If that is a priority, I suggest connecting with him and IHE Radiology to see where that idea is.
@Brad Genereaux, @Jonathan Whitby, @Kevin O'Donnell
Radhika Verma (Apr 17 2019 at 18:20):
Thanks a lot Elliot for providing the insights. For now, my question was just FHIR related and I was also looking into the ImageStudy resource with extensions (for DICOM RT specific attributes that cannot be directly mapped to a FHIR resource).
The extraction capability from FHIR that you've mentioned is quite interesting. I would like to dig into this further.
Thank you once again for your quick response. Have a nice day ahead!
Last updated: Apr 12 2022 at 19:14 UTC
