Set DICOM on FHIR: metadata and images in FHIR workflows
summary
Redox maps DICOM web (using QIDO-RS, STOW-RS, WADO-RS) into FHIR by translating PACS queries to FHIR imagingStudy resource entries, returning FHIR Endpoint URLs and rewriting retrieval links so images or raw DICOM can be pulled via the same API. Demo uses a PACS + SDK to show messy DICOM tags vs. FHIR-friendly JSON. Not yet implemented: structured measurement reports, multi‑PACS fan‑out is unsolved (Redox is exploring EMPI via Verato), and production uptake is still limited despite a ~$47B imaging market projection.
AI-written summary · about
chapters (9)
- 0:00Introduction and agenda
- 1:30DICOM background and history
- 8:11DICOM workflows and message types
- 12:33Challenges of direct DICOM interaction
- 16:09DICOM web and RESTful APIs
- 19:18Why FHIR for DICOM metadata
- 21:23Redox’s FHIR imaging study flow
- 23:28Redox’s mission and integration approach
- 24:33Q&A session
related talks
46mDICOM and FHIR
40mDICOM web concepts: an introduction
38mIntroduction to DICOM Imaging and FHIR
14mConnecting the dots: FHIR, DICOM and IHE AIR
46mPost-Acute Care Interoperability work group - outcomes
47mBuilding a Standard Health Record for oncology using FHIR
21mFrom CDA to FHIR: Responding to COVID19
41mStructured Data Capture