DICOMweb

The STOW-RS service enables clients to store DICOM instances (images, reports, etc.) on a remote server using a simple HTTP POST request.

• Uses the multipart/related media type to encapsulate DICOM binary data.
• Returns an XML or JSON payload confirming successful storage or detailing failures.
• Replaces the legacy DICOM C-STORE service for web environments.

QIDO-RS provides a RESTful mechanism to search for DICOM studies, series, and instances using HTTP GET requests with query parameters.

• Queries are constructed as key-value pairs in the URL, matching DICOM attributes like PatientName or Modality.
• Returns results as a DICOM JSON array, making it easily parsable by web clients.
• Enables building dynamic worklists and zero-footprint viewers without a proprietary query language.

WADO-RS allows clients to retrieve individual DICOM instances, frames, or metadata using a simple HTTP GET request.

• Supports content negotiation to request data as application/dicom (binary) or application/dicom+json (metadata).
• Enables retrieval of a single frame from a multi-frame image using the frame query parameter.
• Forms the backbone of streaming image viewers that fetch pixel data on demand.

WADO-URI is an older, non-RESTful service that retrieves DICOM objects using a single HTTP GET request with all parameters encoded in the URL query string.

• Unlike WADO-RS, it does not follow RESTful resource-oriented design principles.
• Still widely supported for backward compatibility with older PACS and viewers.
• DICOMweb implementations should prioritize WADO-RS for new development.

UPS-RS provides a RESTful interface for managing imaging worklists and tracking the status of scheduled tasks across distributed systems.

• Allows a system to create, search, update, and cancel work items via HTTP methods (POST, GET, PUT).
• Enables tight integration between radiology information systems (RIS), PACS, and acquisition modalities.
• Supports subscription mechanisms to notify clients of worklist changes in real-time.

A DICOMweb server advertises its supported services and options through a Capability resource, enabling automated client discovery.

• Clients perform a GET request to the server's root to retrieve a JSON document listing available services.
• Eliminates the need for manual configuration of endpoints for STOW-RS, QIDO-RS, and WADO-RS.
• Promotes plug-and-play interoperability between compliant imaging systems and viewers.

The Fast Healthcare Interoperability Resources (FHIR) standard provides the ImagingStudy resource to create a patient-centric view of imaging data. While DICOMweb manages the binary objects and metadata at the study level, FHIR references these objects via WADO-RS endpoints. This integration allows a clinician's EHR interface to display a list of radiology exams and launch a DICOMweb viewer directly, bridging the gap between imaging informatics and the broader clinical record.