DICOM PS3.17 2016e - Explanatory Information

HHH.3.3.3 Rendered (JPEG/PDF) Requester
Prev | HHH.3.3 Description of The Use Cases | Next

#### HHH.3.3.3 Rendered (JPEG/PDF) Requester

1. The requesting system: application capable of making Web Service requests. System is not capable of decoding DICOM PS3.10 formats. The system is capable of processing images in JPEG or other more generic formats.

2. Reference information may come in a wide variety of forms. It is expected to include at least the Study UID, Series UID, and Individual SOP instance information. This may be encoded as part of an HL7 reference within a CDA document, a DICOM SOP Instance reference, or other formats.

3. Request information

   1. Requested Data set

      1. Study UID

      2. List of Series UID

      3. List of SOP Instance UIDs

   2. Desired format and subset information

      1. JPEG/PDF/etc. selection, subset area, presentation information

      2. Frame selection for subsets of multi-frame objects

      3. What should be done for requests where image shapes and SOP classes vary and a subset is requested?

      4. Anonymize or not.

4. Response information

   1. JPEGs

      1. Should JPEGs include tag information within the JPEG? If so, what information?

      2. How will JPEGs be related to multi-frame and multi-instance requests? Order? Tag?

   2. PDFs

      1. How will PDFs be related to multi-frame and multi-instance requests? One per frame? One per instance? One for entire set?

   3. Other encodings?

Prev | Up | Next
HHH.3.3.2 DICOM (Encoded Content) Requester | Home | HHH.3.3.4 Metadata (XML Without Pixel Data, Waveform Data, etc.) Requester

DICOM PS3.17 2016e - Explanatory Information