4.2.4. STOW-RS Specifications

4.2.4.1. STOW-RS Store Instance

Table 4.45 STOW-RS Store Instances Specification

Category

Restrictions

Media Types Supported (Accept header)

Restricted to application/dicom or application/dicom+xml

Transfer Syntaxes Supported (Media Type parameter)

See - Transfer Syntaxes for Image Storage SOP Classes, Transfer Syntax for Video Storage SOP Classes, Transfer Syntaxes for SR Storage SOP Classes and Transfer Syntaxes for Other Storage SOP Classes

SOP Class Restrictions

See - SOP Classes for Storage Application Entity (SCP)

4.2.4.2. Connection Policies

4.2.4.2.1. General

All standard RS connection policies apply. There are no extensions for RS options.

4.2.4.2.2. Number Of Connections

The maximal number of simultaneous HTTP Requests is configurable. It is unlimited by default.

Table 4.46 Number of HTTP Requests Supported

Maximum number of simultaneous HTTP requests

No Maximum Limit (Configurable)

4.2.4.2.3. SOP Specific Conformance for SOP Class(es)

The DCM4CHEE-STOW-SERVICE response message header contains status codes indicating success, warning, or failure as shown in the “HTTP Standard Response Codes” below. No additional status codes are used.

Table 4.47 HTTP Standard Response Codes

Service Status

HTTP Status Code

STOW-RS Description

Failure

400 - Bad Request

This indicates that the STOW-RS Service was unable to store any instances due to bad syntax.

401 - Unauthorized

This indicates that the STOW-RS Service refused to create or append any instances because the client is not authenticated.

403 - Forbidden

This indicates that the STOW-RS Service understood the request, but is refusing to fulfill it (e.g., an authenticated user with insufficient privileges).

409 - Conflict

This indicates that the STOW-RS Service request was formed correctly but the service 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 a STOW-RS Service was unable to store any instances for a mixture of reasons. Additional information regarding the instance errors can be found in the XML response message body.

503 - Busy

This indicates that the STOW-RS Service was unable to store any instances because it was out of resources.

Warning

202 - Accepted

This indicates that the STOW-RS Service stored some of the instances but warnings or failures exist for others. Additional information regarding this error can be found in the XML response message body.

Success

200 - OK

This indicates that the STOW-RS Service successfully stored all the instances.

The following table indicates the meaning of values returned in FailureReason (0008,1197) tag in any of the above STOW-RS error responses

Table 4.48 STOW-RS Error Response Status Return Reasons

Service Status

Further Meaning

Error Code (Hex)

Error Code (Decimal)

Error Comment

Behaviour

Refused

Out of Resources

A700

42752

Indicates that there was not enough disk space to store the image. Error message is output to the Service Log. The SOP Instance will not be saved.

Duplicate Rejection Note

A770

42864

Rejection Note [uid={SOP Instance UID}] already received.

Indicates that rejection note was already received.

Subsequent Occurrence of Rejected Object

A771

42865

Subsequent occurrence of rejected Object [uid={SOP Instance UID}, rejection={Rejection Note Code}]

Indicates that there was a subsequent occurrence of a rejected object during store operation.

Rejection Failed - No Such Instance

A772

42866

Failed to reject Instance[uid={SOP Instance UID}] - no such Instance.

Indicates that one or more objects were not previously stored in archive to be rejected.

Rejection Failed - Class Instance Conflict

A773

42867

Failed to reject Instance[uid={SOP Instance UID}] - class-instance conflict.

Indicates that there was a conflict in SOP Class UIDs of object (between that of the previously received object and the one referenced in the current rejection note) to be rejected.

Rejection Failed - Already Rejected

A774

42868

Failed to reject Instance[uid={SOP Instance UID}] - already rejected.

Indicates that the rejected object was already rejected.

Rejection for Retention Policy Expired not Authorized

A775

42869

Rejection for Retention Policy Expired not authorized.

Indicates that rejection of objects with type as Retention Expired are not allowed by LDAP configuration.

Retention Period of Study not yet Expired

A776

42870

Retention Period of Study not yet expired.

Indicates that rejection of objects is not allowed as Study Retention Period has not expired yet.

No Patient ID (from trusted Assigning Authority) in object.

A777

42871

Storage denied as Patient ID missing in object.

Indicates that the Patient ID is missing in the object or is not from a trusted Assigning Authority.

Conflicting Patient ID in Object

A778

42872

Patient ID in incoming object does not match with that of patient associated with study.

Indicates that the Patient ID in incoming object does not match with that of patient associated with study.

Conflicting Patient Attributes in Object

A779

42873

Patient differs from previous received object in attribute {Keyword <Tag>}.

Indicates that the Patient in incoming object has differing attributes with that of same patient associated with previous received object.

Missing Bulkdata

A922

43298

Bulkdata missing in STOW-RS request payload.

Indicates that no bulkdata file was sent in the request body.

Different Study Instance UID

C409

50185

Study Instance UID differs from Accepted Study Instance UID.

Indicates that Accepted Study Instance UID varies from the Study Instance UID received in the request body.

Failed to parse DICOM stream

C499

50329

Receive of non(-valid) DICOM stream

Indicates that non(-valid) DICOM stream was received in the request body.

Not Authorized

0124

292

Storage denied.

Indicates that the storage is denied.

Error

Data Set does not match SOP Class

A900

43264

Indicates that the Data Set does not encode a valid instance of the SOP Class specified. This status is returned if the DICOM Object stream can be successfully parsed but does not contain values for one or more mandatory Elements of the SOP Class. The STORAGE-SCP AE does not perform a comprehensive check, as it only checks a subset of required Elements. In addition, if the SOP Class is for a type of image but the SOP Instance does not contain values necessary for its display then this status is returned. Error message is output to the Service Log. The system can be configured to temporarily save such Data Sets in order to aid problem diagnosis.

Cannot understand

C000

49152

Indicates that the STORAGE-SCP AE cannot parse the Data Set into Elements. Error message is output to the Service Log. The system can be configured to temporarily save such Data Sets in order to aid problem diagnosis.

Failed to parse DICOM stream

C499

50329

Indicates that the STORAGE-SCP AE failed to parse received object.

Warning

Coercion of Data Elements

B000

45056

Indicates that one or more Element values were coerced. Refer to the Attributes defined in Annex for a list of those that can be coerced. Note that return of this status is disabled by default, as some SCUs treat it as an Error code rather than a Warning.

4.2.4.2.4. Web Service Endpoint URL

http[s]://<host>:<port>/dcm4chee-arc/aets/{AETitle}/rs

Replace {AETitle} in the URL with the configured AE title.