DICOM PS3.17 2016e - Explanatory Information

HHH.3.2 Analysis of Use Cases
Prev | HHH.3 Uses For WADO-WS, WADO-RS and STOW-RS Services | Next

### HHH.3.2 Analysis of Use Cases

Examples of use cases / clinical scenarios, as the basis to develop the requirements, include:

- Providing access to images and reports from a point-of-service application e.g., EMR.

- Following references to significant images used to create an imaging report and displaying those images.

- Following references / links to relevant images and imaging reports in email correspondence or clinical reports e.g., clinical summary.

- Providing access to anonymized DICOM images and reports for clinical research and teaching purposes.

- Providing access to a DICOM encoded imaging report associated with the DICOM IE (patient/study/series/objects) to support remote diagnostic workflows e.g., urgent medical incidents, remote consultation, clinical training, teleradiology/telemedicine applications.

- Providing access to summary or selected information from DICOM objects.

- Providing access to complete studies for caching, viewing, or image processing.

- Storing DICOM SOP Instances using HTTP over a Network from PACS to PACS, from PACS to VNA, from VNA to VNA, from clinical application to PACS, or any other DICOM SCP.

- Web clients, including mobile ones, retrieving XML and bulk data from a WADO-RS Service and adding new instances to a study.

Examples of the use cases described in 1 above are:

1. The EMR displays in JPEG one image with annotations on it (patient and/or technique related), based upon information provided in a report.

2. The EMR retrieves from a "Manifest" document all the referenced objects in DICOM and launches a DICOM viewer for displaying them (use case addressed by the IHE XDS-I.b profile).

3. The EMR displays in JPEG one image per series with information describing every series (e.g., series description).

4. The EMR displays in JPEG all the images of a series with information describing the series as well as every image (e.g., instance number and slice location for scanner images).

5. The EMR populates in its database for all the instances referred in a manifest (KOS) the relevant information (study ID/UID/AccessionNumber/Description/DateTime, series UID/Modality/Description/DateTime, instance UID/InstanceNumber/SliceLocation).

6. The EMR displays patient demographics and image slices in a browser by accessing studies through URLs that are cached and rendered in a remote data center.

7. A hospital transfers a DICOM Study over a network to another healthcare provider without needing special ports opened in either firewall.

8. A diagnostic visualization client, during post-processing, adds a series of Instances containing measurements, annotations, or reports.

9. A healthcare provider transfers a DICOM Study to a Patient Health Record (PHR) at the request of the patient.

As an example, the 1c use case is decomposed in the following steps (all the other use cases can be implemented through a similar sequence of basic transactions):

1. The EMR sends to the DICOM server the list of the objects ("selection"), asking for the object content.

2. The DICOM server sends back the JPEG images corresponding to the listed objects.

3. The EMR sends to the DICOM server the "selection" information for obtaining the relevant information about the objects retrieved.

4. The DICOM server sends back the corresponding information in the form of a "metadata" document, converted in XML.

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

DICOM PS3.17 2016e - Explanatory Information