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 / Transfer-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 transfer encoding has not been applied to the payload
Transfer-Encoding	encoding	C	M	Shall be present if a transfer 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 consistent with the Content-Type Header Field. The representations shall conform to Media Types described in Section 8.7.3 DICOM Media Type Sets. The payload shall conform to Section 8.6 Payloads.

The payload may contain representations of SOP 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 representations of SOP Instances, or
Metadata and Bulkdata representations of SOP Instances.

PS3.10 representations of SOP Instances shall be encoded with one representation per DICOM Instance.

Metadata and Bulkdata representations of SOP Instances shall be encoded in the following manner (see Figure 8.6-1 Mapping between IOD and HTTP message parts):

XML representations of Metadata shall be encoded as described in the Native DICOM Model defined in PS3.19 with one representation per XML object.
JSON representations of Metadata shall be encoded as an array of DICOM JSON Model Objects defined in Annex F in a single representation.
Representations of Metadata may omit Attributes of the Image Pixel Description Macro for referenced pixel data whose representation is encoded in one of the Media Types specified in Table 10.5.2-1.
The Metadata shall include only the DICOM Dataset (without Bulkdata), and in particular shall not include any Group 0002 File Meta Information Data Elements. The origin server shall create appropriate File Meta Information depending on the Media Type of the supplied compressed pixel data, if it happens to internally store the Dataset in a PS3.10 File.
Uncompressed Bulkdata (including pixel data but with the exception of the Encapsulated Document (0042,0011) element) shall be encoded as application/octet-stream with one representation per Bulkdata item.
Compressed pixel data for a Single Frame Image shall be encoded as one compressed Bulkdata representation.
Compressed pixel data for a Multi-Frame Image shall be encoded as multiple Single Frame Image compressed Bulkdata representations.
Compressed pixel data for a Video shall be encoded as one compressed Bulkdata representation.
The 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 representation per document.

Prev	Up	Next
10.4.5 Conformance Statement	Home	10.5.2 Behavior