DICOM PS3.18 2019c - Web Services

8.7.4 Rendered Media Types

DICOM Instances may be converted by a rendering process into non-DICOM Media Types. This can be useful to display or process them using non-DICOM software, such as browsers.

For example, an Instance containing:

  1. an image could be rendered into the image/jpeg or image/png Rendered Media Types.

  2. a multi-frame image in a lossless Transfer Syntax could be rendered into a video/mpeg or video/mp4 Rendered Media Type.

  3. a Structured Report could be rendered into a text/html, text/plain, or application/pdf Rendered Media Type.

Note

Rendered Media Types are usually consumer format media types. Some of the same non-DICOM Media Types are also used as Bulkdata Media Types, that is, for encoding Bulkdata extracted from Encapsulated Pixel Data (used with compressed Transfer Syntaxes), without applying a rendering process. See Section 8.7.3.3.

Rendered images shall contain no more than 8 bits per channel.

Origin servers shall support rendering Instances of different Resource Categories into Rendered Media Types as specified in Table 8.7.4-1.

Table 8.7.4-1. Rendered Media Types by Resource Category

Category

Media Type

URI

RESTful

Single Frame Image

image/jpeg

D

D

image/gif

O

R

image/png

O

R

image/jp2

O

O

Multi-frame Image

image/gif

O

O

Video

video/mpeg

O

O

video/mp4

O

O

video/H265

O

O

Text

text/html

D

D

text/plain

R

R

text/xml

O

R

text/rtf

O

O

application/pdf

O

O


When an image/jpeg media type is returned, the image shall be encoded using the JPEG baseline lossy 8-bit Huffman encoded non-hierarchical non-sequential process defined in [ISO/IEC 10918-1].

The origin server may support additional Rendered Media Types, which shall be documented in the Conformance Statement and, if the service supports it, the Retrieve Capabilities response.

A Transfer Syntax media type parameter is not permitted for Rendered Media Types.

DICOM PS3.18 2019c - Web Services