DICOM PS3.17 2016c - Explanatory Information

HHH.3.3 Description of The Use Cases
Prev | HHH.3 Uses For WADO-WS, WADO-RS and STOW-RS Services | Next

### HHH.3.3 Description of The Use Cases

The use cases described above in terms of clinical scenarios correspond to the following technical implementation scenarios. In each case the use is distinguished by the capabilities of the requesting system:

- Does it prefer the URI based requests, or the web-services based requests.

- Does it have the ability to decode and utilize the DICOM PS3.10 format or not.

- Does it need the metadata describing the image and its acquisition, and/or does it need an image to be displayed.

These then become the following technical use cases.

#### HHH.3.3.1 URI Based WADO Use Case

1. The requesting system is Web Browser or other application that can make simple HTTP/HTTPS requests,

2. Reference information is provided as URL or similar information that can be easily converted into a URL.

3. The request specifies:

   1. Individual SOP Instance

   2. Desired format and subset selection for information to be returned

4. The Response provides

   1. SOP instance, reformatted and subset as requested. This may be encoded as a DICOM PS3.10 instance, or rendered into a generic image format such as JPEG.

Prev | Up | Next
HHH.3.2 Analysis of Use Cases | Home | HHH.3.3.2 DICOM (Encoded Content) Requester

DICOM PS3.17 2016c - Explanatory Information