4.2.4. STOW-RS Specifications

4.2.4.1. STOW-RS Store Instance

Table 4.42 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.43 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.44 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.

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.