10.5 Store Transaction

10.5 Store Transaction (Current)
Prev	10 Studies Service and Resources	Next

This transaction uses the POST method to Store representations of Studies, Series, and Instances contained in the request payload.

The Store transaction supports only DICOM resources. The resource can be supplied as a single Instance, or as separate Metadata and Bulkdata.

10.5.1 Request

The request shall have the following syntax:

POST SP "/" {/resource} SP version CRLF

Accept: 1#media-type CRLF

Content-Type: dicom-media-type CRLF

(Content-Length: uint / Content-Encoding: encoding) CRLF

*(header-field CRLF)

CRLF

payload

10.5.1.1 Target Resources

10.5.1.1.1 DICOM Resources

Table 10.5.1-1 defines the resources used to store Instances.

Table 10.5.1-1. Store Transaction DICOM Resources

Resource	URI Template	Description
Studies	/studies	Stores a set of representations that may have different Study Instance UIDs.
Study	/studies/{study}	Stores a set of representations that belong to the same Study, i.e., each representation shall have the same Study Instance UID.

10.5.1.2 Query Parameters

The Store transaction has no Query Parameters.

10.5.1.3 Request Header Fields

The origin server shall support Header Fields as required in Table 10.5.1-2.

The user agent shall supply in the request Header Fields as required in Table 10.5.1-2.

Table 10.5.1-2. Request Header Fields

Name	Values	Usage		Description
Name	Values	User Agent	Origin Server	Description
Content-Type	media-type	M	M	The DICOM Media Type of the request payload Shall be present if the request has a payload
Content-Length	uint	C	M	Shall be present if a content encoding has not been applied to the payload
Content-Encoding	encoding	C	M	Shall be present if a content encoding has been applied to the payload

10.5.1.4 Request Payload

The request payload shall be present and shall contain one or more representations specified by the Content-Type header field.

The payload may contain Instances from more than one Study if the Study Instance UID is not specified in the Target URI.

The request payload shall consist of either:

PS3.10 SOP Instances, or
Metadata accompanied by Bulkdata.

PS3.10 binary instances shall be encoded with one message part per DICOM Instance.

Metadata and Bulkdata requests will be encoded in the following manner (see Figure 8.6-1 Mapping between IOD and HTTP message parts):

All XML request messages shall be encoded as described in the Native DICOM Model defined in PS3.19 with one message part per XML object; the Attributes of the Image Pixel Description Macro may be omitted for the media types specified in Table 10.5.2-1.
All JSON request messages shall be encoded as an array of DICOM JSON Model Objects defined in Annex F in a single message part; the Attributes of the Image Pixel Description Macro may be omitted for the media types specified in Table 10.5.2-1.
Bulkdata (with the exception of Encapsulated Document (0042,0011) element) and uncompressed pixel data shall be encoded in a Little-Endian format using the application/octet-stream media type with one message part per Bulkdata item.
Compressed pixel data shall be encoded in one of two ways:
- single-frame pixel data encoded using a single-frame media type (one message part);
- multi-frame or video pixel data encoded using a multi-frame media type (multiple frames in one message part).

Uncompressed Bulkdata shall be encoded as application/octet-stream.

An Encapsulated Document (0042,0011) Bulkdata element shall be encoded using the media-type from the MIME Type of the Encapsulated Document (0042,0012) Attribute with one message part per document.

Prev	Up	Next
10.4.5 Conformance Statement	Home	10.5.2 Behavior