DICOM PS3.18 2021d - Web Services

10.4.4 Media Types (Current)
Prev | 10.4 Retrieve Transaction | Next

### 10.4.4 Media Types

The origin server shall support the media types specified as default or required in Table 10.4.4-1.

The application/dicom Media Type (without the "multipart/related; type="" prefix) specifies a single encoded object and shall only be used for individual Instance Resources.

The origin server shall support the Transfer Syntax and Character Set media type parameters. See Section 8.7.3.5.2 and Section 8.7.3.5.3.

For further details on each Target Resource, see Section 10.4.1.1.

For further details on each media type and associated transfer syntaxes, see the Section in the Media Type Reference column.

Table 10.4.4-1. Default, Required, and Optional Media Types

Target Resource | Media Type | Usage | Section
--- | --- | --- | ---
Instance Resources | multipart/related; type="application/dicom" | Default | Section 8.7.3.1
multipart/related; type="application/octet-stream" (See Note 2) | Required | Section 8.7.3.3.1
application/dicom | Optional | Section 8.7.3.1
Compressed Bulkdata Media Types | Optional | Section 8.7.3.3.2
Metadata Resources | application/dicom+json (See Note 1) | Default | Section 8.7.3.2
multipart/related; type="application/dicom+xml" | Required | Section 8.7.3.2
multipart/related; type="application/octet-stream" | Required | Section 8.7.3.3.1
Bulkdata Resources and Pixel Data Resources | multipart/related; type= a Compressed Bulkdata Media Type | Optional | Section 8.7.3.3.2
Rendered Resources | multipart/related; type= a Compressed Bulkdata Media Type | Optional | Section 8.7.4
Compressed Bulkdata Media Types (See Note 3) | Optional | Section 8.7.3.3.2
Thumbnail Resources | image/jpeg | Default | Section 8.7.4
Other Rendered Media Types | Optional | Section 8.7.4

### Note

1. The media type for application/dicom+json does not include “multipart/related” because, per Section F.2.1, JSON metadata for multiple instances is encoded in a single top-level array of JSON objects, rather than multiple parts with top-level arrays containing single JSON objects. This is also true when the media type compresses the JSON in a zip container.

2. Requesting Instance Resources (Study, Series, or Instance) with a Media Type of multipart/related; type="application/octet-stream" is retained for historical reasons. Such a request is equivalent to requesting the corresponding Bulkdata Resource (Study, Series, Instance).

3. The use of a single part Media Type is permitted for a Rendered Instance Resource that is a single frame instance and for a Rendered Frames Resource that is an individual frame in a multi-frame instance. The origin server is expected to ignore single part Media Types for other resources and if that means no Media Types remain, it will return a 406 (Not Acceptable) error, per Section 8.7.8.1. E.g., if a user agent requests a Rendered Study resource and only lists single part Media Types in the Accept header, it should expect an error, even if the study happens to only contain one single frame instance.

Prev | Up | Next
10.4.3.3.6 Instance Resource Payload | Home | 10.4.5 Conformance Statement

DICOM PS3.18 2021d - Web Services