DICOM PS3.18 2019a - Web Services
6.10.3.3.3 Response

The response shall have the following syntax:

    version SP status-code SP reason-phrase CRLF
    *(header-field CRLF)
    CRLF
    [Status Report]
6.10.3.3.3.1 Status Codes

The response shall have an appropriate status code. Table 6.10.3.3.3.1-1 contains the most common status codes for this transaction.

Table 6.10.3.3.3.1-1. Common Status Codes

Status Code

Description

200 (OK)

Indicates that the origin server successfully stored or created at least one of the representations contained in the request payload and is returning a response payload.

201 (Created)

Indicates that the origin server successfully created at least one of the representations contained in the request payload and may be returning a response payload.

202 (Accepted)

Indicates that the origin server successfully validated the request message, but has not yet stored or created the representations in the request payload. The origin server may or may not have validated the payload.

The user agent can use a Query or Retrieve transaction later to determine if the request has completed.

204 (No Content)

Indicates that the origin server successfully stored all the representations contained in the request payload without any modifications and is not returning a response payload.

400 (Bad Request)

Indicates that the origin server did not store any of the representations contained in the request payload because of errors in the request message. For example, an invalid Query Parameter or an invalid SOP instance.

404 (Not Found)

Indicates that the origin server did not find a current representation for the target resource or is not willing to disclose that one exists. For example, an unsupported IOD, or SOP Instance not on server.

409 (Conflict)

Indicates that the request could not be completed due to a conflict with the current state of the target resource.

415 (Unsupported Media Type)

Indicates that the origin server does not support the media type specified in the Content-Type header field of the request, and none of the representations contained in the request were processed or stored.


6.10.3.3.3.2 Response Header Fields

Table 6.10.3.3.3.2-1. Store Response Header Fields

Header Field

Value

Usage

Requirements

Content-Type

dicom-media-type

M

Content-Length

uint

C

Shall be present if no transfer coding has been applied. Shall be absent otherwise.

Transfer-Encoding

encoding

C

Shall be present if a transfer coding has been applied. Shall be absent otherwise.


6.10.3.3.3.3 Response Payload

If the origin server failed to store or modified any representations in the request payload, the response payload shall contain a Status Report describing any additions, modifications, or deletions to the stored representations. The Status Report may also describe any warnings or other useful information.

DICOM PS3.18 2019a - Web Services