6.5.4.2 Response
Prev | 6.5.4 WADO-RS - RetrieveFrames | Next

#### 6.5.4.2 Response

The Server shall provide the document(s) indicated in the request. In order to parse the bulk data items it is necessary to also retrieve the corresponding metadata for the specified Study, Series, or Instance.

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 has a content type of multipart/related with a message boundary separator.

##### 6.5.4.2.1 Pixel Data Response

- Content-Type:

  - multipart/related; type=application/octet-stream; boundary={MessageBoundary}

  - multipart/related; type={MediaType}; boundary={MessageBoundary}

- The entire multipart response contains all requested Frames for the specified Instance.

- Each item in the response is one of:

  - an uncompressed frame encoded in Little Endian binary format with the following headers:

    - Content-Type: application/octet-stream

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

  - a compressed frame encoded in a single-frame media type with the following headers:

    - Content-Type: {MediaType}

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

  - a set of compressed frames encoded in a multi-frame media type with the following headers:

    - Content-Type: {MediaType}

    - Content-Location: {BulkDataURL}[/frames/{FrameList}]

      - {FrameList} is a list of frames separated by %2C (comma). It may be omitted if the message part includes all frames for the specified bulk pixel data object.

- The frames will be returned in the order specified by the Frame List.

Prev | Up | Next
6.5.4 WADO-RS - RetrieveFrames | Home | 6.5.5 WADO-RS - RetrieveBulkdata