DICOM PS3.17 2016a - Explanatory Information

HHH.2 Web and Rest Services Implementation
Prev | HHH Evolution of WADO to Web and Rest Services (Informative) | Next

## HHH.2 Web and Rest Services Implementation

The implementation architecture has to maximize interoperability, preserve or improve performance and minimize storage overhead.

The Web and REST Services technologies have been selected to:

1. be firewall friendly and supporting security,

2. be supported by and interoperable between multiple development environments, and

3. have sufficient performance for both large and small text and for binary data.

The XML implementation of the messages uses the CamelCase parameter style used in SOAP 1.2 (element names starting with an upper case character, e.g., ElementOne, attribute names starting with a lower case character e.g., attributeOne).

The WADO-WS response will be provided as list of instances in MTOM/XOP ("DICOM" or "Rendered" Requesters), XML encoded additional information resulting from the XPath filters applied on every objects selected ("Information Requester")

The WADO-RS response will be provided as a list of XML and/or binary instances in a multipart/related response. The type of response depends on the media types listed in the Accept header.

The STOW-RS response is a standard HTTP/1.1 status line and possibly an XML response message body. The meaning of the success, warning, or failure statuses are defined in PS3.18.

Prev | Up | Next
HHH Evolution of WADO to Web and Rest Services (Informative) | Home | HHH.3 Uses For WADO-WS, WADO-RS and STOW-RS Services

DICOM PS3.17 2016a - Explanatory Information