6.5.6.2 Response
Prev | 6.5.6 WADO-RS - RetrieveMetadata | Next

#### 6.5.6.2 Response

The Server shall provide the document(s) indicated in the request. The Server shall return the document(s) or an error code when the document(s) could not be returned.

The response has a content type of either:

- multipart/related; type=application/dicom+xml, as described in the Native DICOM Model defined in PS3.19, or

- application/json, as described in Annex F.

The response must include the URL attribute for each BulkData element.

### Note

The metadata is consistent with the characteristics of the bulk data on the server. If bulk data is requested using specified Transfer Syntaxes or media types, it is possible that the bulk data retrieved may be inconsistent with the metadata. For example, for a Study whose DICOM Tag (0028,2110) "LossyImageCompression" is set to "00", indicating no lossy compression, calling RetrieveStudy and requesting a lossy compression media type will provide pixel data that is inconsistent with the metadata. It is the responsibility of the client to deal with these inconsistencies appropriately.

##### 6.5.6.2.1 XML Metadata Response

- Content-Type:

  - multipart/related; type=application/dicom+xml

- The entire multipart response contains all XML metadata for the specified Study, Series, or Instance.

- Each item in the response is the XML encoded metadata for an Instance with the following http headers:

  - Content-Type: application/dicom+xml; transfer-syntax={TransferSyntaxUID}

    Where {TransferSyntaxUID} is the UID of the DICOM Transfer Syntax used to encode the inline binary data in the XML metadata.

Prev | Up | Next
6.5.6 WADO-RS - RetrieveMetadata | Home | 6.5.6.2.2 JSON Metadata Response