Digital Imaging and Communications in Medicine (DICOM) is the communication standard for imaging and related metadata in healthcare.
Sounds nice to have one standard, right? But DICOM can be complex, and it may not give you the holistic view of the patient you’re hoping for. As an alternative, you can leverage our Redox FHIR® API to translate DICOM messages to FHIR® for a modern, easier way to interact with medical imaging and metadata.
Just a note that translating DICOM to FHIR® isn’t supported with data on demand.
Redox can benefit customers on the receiving side of the DICOM data exchange for different scenarios, including:
We use the FHIR® ImagingStudy resource to translate imaging metadata to FHIR®. Redox serves as the intermediary for passing the information, but Redox doesn’t process the original images so that we can avoid latency on our end. But here’s how the DICOM to FHIR® queries generally go:
Redox can translate these DICOM operations:
DICOM Operation | Description |
---|---|
WADO-RS | This operation exchanges PS3.10 files or separated metadata and bulk data, which gives you the ability to retrieve entire studies and series rather than needing to send multiple queries for individual instances. With Redox, this is the operation we translate when you query for the location of a patient’s imaging results. |
QIDO-RS | This operation exchanges databases or registries of DICOM objects. With Redox, this is the operation we translate when you query an endpoint URL for the original imaging results. |
-WS
or STOW
operations