| DICOM PS3.18 2025a - Web Services |
|---|
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
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.
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).
The use of a single part Media Type is permitted for resources which are a single response item. 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.
| DICOM PS3.18 2025a - Web Services |
|---|