DICOMweb is the core direct-access contract for modern web viewers
A universal viewer needs a way to discover studies, retrieve the right objects or frames, and sometimes store derived results. DICOMweb gives web-native access patterns for those jobs without forcing a browser app to behave like a classic DIMSE node.
Representative DICOMweb access path
A universal viewer usually starts with study discovery and then narrows into a specific series or instance path for retrieval.
Request
GETANNOTATIONS
Response
DICOM Part 18: Web Services
Official DICOMweb specification covering QIDO-RS, WADO-RS, and STOW-RS.
Read the DICOMweb specificationOHIF DICOMweb data source configuration
Official OHIF documentation showing how a browser viewer is configured to consume DICOMweb endpoints.
Read the OHIF DICOMweb configuration guideCross-enterprise exchange and direct viewer access solve different layers of the problem
A viewer may retrieve images directly through DICOMweb while the health system participates in broader sharing workflows through XDS-I.b. Those are complementary patterns: one is direct application access, the other is organized sharing and discovery across enterprises.
Two related but distinct interoperability layers
| Pattern | Primary job | Viewer implication |
|---|---|---|
| DICOMweb direct access | Let the viewer search and retrieve imaging content directly | Best fit for the active image-delivery path into a browser or viewer service |
| XDS-I.b sharing | Coordinate cross-enterprise discovery and sharing of imaging information | Adds a broader exchange workflow above the viewer-access path |
| FHIR ImagingStudy and related resources | Link imaging context into the clinical record | Helps EHRs, reports, and viewers reason about the same study context |
Direct access and exchange are adjacent but not identical
Loading diagram...
FHIR ImagingStudy example
A simplified ImagingStudy resource showing patient context, scale, and the endpoint relationship a viewer can use.
Click on an annotation to highlight it in the JSON
XDS.b integration profile
Official IHE IT Infrastructure profile for registry-repository document sharing, which is the narrower cross-enterprise pattern a viewer stack often complements.
Read the XDS.b profileFHIR ImagingStudy
Official HL7 resource describing the study-level clinical representation used around image access and chart context.
Read the ImagingStudy resourceFHIR DiagnosticReport
Official HL7 resource for linking clinical interpretation to a study or imaging workflow.
Read the DiagnosticReport resourceReport-linked image display only works when report, study, and endpoint contracts stay explicit
A report hyperlink is only durable if it resolves through explicit study identity, endpoint metadata, and optionally a portable selection or image-region reference. Blind viewer URLs age badly because they assume one routing model, one archive contract, and one viewer state model forever.
Report-linked display path from report text to viewer context
Loading diagram...
Current standards reality
IHE Interactive Multimedia Report 1.1.0 is now a published profile, but many deployments still implement only part of the contract. The important lesson for universal viewers is that durable report-linked display depends on explicit image references and display actors, not on one brittle deep link.
IHE Interactive Multimedia Report (Volume 1)
Official IHE profile describing report-driven interactive image viewing, including advanced measurement viewing and display-capable report links.
Read the IMR profile overviewIHE RAD-142 Display Multimedia Report
Current IHE transaction page describing how a report reader launches display of multimedia report content and related image references.
Read the RAD-142 transactionKnowledge Check
Test your understanding with this quiz. You need to answer all questions correctly to mark this section as complete.