| DICOM PS3.18 2025e - Web Services |
|---|
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:
an image could be rendered into the image/jpeg, image/jph, image/jxl, image/png, or image/gif Rendered Media Types.
a Multi-frame Image in a lossless Transfer Syntax could be rendered into a video/mpeg, video/mp4, video/H265, or image/jxl Rendered Media Type.
a Structured Report could be rendered into a text/html, text/plain, or application/pdf Rendered Media Type.
Rendered Media Types are usually consumer format Media Types. Some of the same non-DICOM Media Types are also used as Bulk Data Media Types, that is, for encoding Bulk Data extracted from Encapsulated Pixel Data (used with compressed Transfer Syntaxes), without applying a rendering process. See Section 8.7.3.3.
The rendering of Presentation States is specified in Section 8.3.5.1.
Origin servers shall support rendering Instances of different Resource Categories into Rendered Media Types as specified in Table 8.7.4-1.
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].
When an image/jph Media Type is returned, the image shall be encoded with the JP2 box being present.
This representation is different from that of the stored HTJ2K Transfer Syntaxes, which do not contain the JP2 box.
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 2025e - Web Services |
|---|