DICOM PS3.18 2019a - Web Services

6.5.5.2 Response (Current)
Prev | 6.5.5 WADO-RS - RetrieveBulkdata | Next

#### 6.5.5.2 Response

The Server shall provide the document(s) indicated in the request.

The server shall always return the same bulk data for a specified BulkData URL if the data is available.

If the resource specified by the BulkData URL is not available, the server shall return:

- 404 - Not Found, if the server expects to be able to return the resource again in the future

- 410 - Gone, if the server does not expect the resource to be valid in the future

The server determines the period of time a BulkData URL resource is available.

The Server shall return the document(s) or an error code when the document(s) cannot be returned. If the server cannot encode the pixel data using any of the requested media types, then an error status shall be returned.

All response formats have a media type of multipart/related with a message boundary separator. The response format depends on the Accept header specified in the request.

##### 6.5.5.2.1 Bulk Data Response

- Content-Type:

  - multipart/related; type="application/octet-stream"; boundary={MessageBoundary} [dcm-parameters]

  - multipart/related; type="{media-type}"; boundary={MessageBoundary} [dcm-parameters]

    where {media-type} is of compressed pixel data encoded as specified in Table 6.1.1.8-3b.

  See Section 6.1.3.

- The entire multipart response contains all bulk data that can be converted to one of the requested media types.

- Each part in the response is one of:

  - an uncompressed bulk data element encoded in Little Endian binary format with the following headers:

    - Content-Type: application/octet-stream [dcm-parameters]

    - Content-Location: {BulkDataURI}

  - an Encapsulated Document (0042,0011) bulk data element from a SOP Instance in the Study encoded in the media type specified in MIME Type of Encapsulated Document (0042,0012) in the Instance with the following header fields:

    - Content-Type: {media-type}

    - Content-Location: {BulkDataURI}

  - a compressed bulk data element from a SOP Instance encoded in a single-frame media type with the following headers:

    - Content-Type: {media-type} [dcm-parameters]

      where {media-type} is of compressed pixel data encoded as specified in Table 6.1.1.8-3b.

    - Content-Location: {BulkDataURI}

  - a compressed frame from a multi-frame SOP Instance encoded in a single-frame media type with the following headers:

    - Content-Type: {media-type} [dcm-parameters]

      where {media-type} is of compressed pixel data encoded as specified in Table 6.1.1.8-3b.

    - Content-Location: {BulkDataURL}/frames/{FrameNumber}

    ### Note

    Each frame will come in a separate part.

  - all of the compressed frames from a SOP Instance encoded in a video media type with the following headers:

    - Content-Type: {media-type} [dcm-parameters]

      where {media-type} is of compressed pixel data encoded as specified in Table 6.1.1.8-3b.

    - Content-Location: {BulkDataURL}

- If the Range header is specified in the request, the server shall return only the specified bytes of the bulk data object. See [RFC7233] Section 4.

Prev | Up | Next
6.5.5 WADO-RS - RetrieveBulkdata | Home | 6.5.6 WADO-RS - RetrieveMetadata

DICOM PS3.18 2019a - Web Services