The response shall have the following syntax:
version SP status-code SP reason-phrase CRLF
[Content-Type: media-type CRLF]
[(Content-Length: uint CRLF / Transfer-Encoding: encoding CRLF) ]
*(header-field CRLF)
CRLF
store-instances-response-module
The response shall contain an appropriate status code.
If any element is coerced or corrected, the Original Attribute Sequence (0400,0561) shall be included in the DICOM Object that is stored and may be included in the Store Instances Response Module (see Annex I) in the response.
Table 10.5.3-1 shows some common status codes corresponding to this transaction. See also Section 8.5 for additional status codes.
Table 10.5.3-1. Status Code Meaning
|
Status
|
Code
|
Meaning
|
|
Success
|
200 (OK)
|
The origin server successfully stored all Instances.
|
|
202 (Accepted)
|
The origin server stored some of the Instances but warnings or failures exist for others.
Additional information regarding this error may be found in the response message body.
|
|
Failure
|
400 (Bad Request)
|
The origin server was unable to store any Instances due to bad syntax.
|
|
409 (Conflict)
|
The request was formed correctly but the origin server was unable to store any Instances due to a conflict in the request (e.g., unsupported SOP Class or Study Instance UID mismatch).
This may also be used to indicate that the origin server was unable to store any Instances for a mixture of reasons.
Additional information regarding the Instance errors may be found in the payload.
|
|
415 (Unsupported Media Type)
|
The origin server does not support the media type specified in the Content-Type header field of the request.
|