DICOM PS3.18 2019c - Web Services

7 Overview of DICOM Web Services (Informative)

7.1 DICOM Web Service Types

This Part of the Standard defines DICOM Web Services. Each service allows a user agent to interact with an origin server to manage a set of DICOM Resources. Each DICOM Web Service operates on a set of resources and defines a set of Transactions that operate on those resources. All Transactions are defined in terms of HTTP request/response message pairs.

When used in this Part of the Standard, the term HTTP refers to the family of HTTP protocols including: HTTP/1.1, HTTPS/1.1, HTTP/2, and HTTPS/2, as defined by the relevant IETF RFCs, but does not include HTTP/1.0 or HTTPS/1.0. The HTTP standards are normative for all aspects of HTTP message format and transmission.

There are two general types of DICOM Web Services: URI and RESTful. This distinction is based on the type of web service protocol used to specify resources and transactions.

7.1.1 URI Web Service

The URI Web Service retrieves representations of its resources, those resources being Composite SOP Instances (Instance). The URI service defines two transactions that retrieve Instances in different media types. All URI transactions use the query component of the URI in the request message to specify the transaction.

The functionality of the URI Web Service Transactions is similar to, but more limited than, the Retrieve Transaction of the Studies Web Service.

7.1.2 RESTful Web Services and Resources

Each RESTful Web Service defines the set of resources, and the transactions that can be applied to those resources.

The defined RESTful Web Services are:

Studies Web Service

Enables a user agent to manage Studies stored on an origin server.

Worklist Web Service

Enables a user agent to manage the Worklist containing Workitems stored on an origin server.

Non-Patient Instance Web Service

Enables a user agent to manage Non-Patient Instances, e.g., Color Palettes, stored on an origin server.

DICOM PS3.18 2019c - Web Services