12.5 Store Transaction

12.5 Store Transaction (Current)
Prev	12 Non-Patient Instance Service and Resources	Next

This transaction requests that the origin server store the representations of the NPIs contained in the request payload so that they may be retrieved in the future using the SOP Instance UIDs.

12.5.1 Request

The request shall have the following syntax:

POST SP /{npi-name} {/uid} SP version CRLF

Content-Type: dicom-media-type CRLF

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

CRLF

payload

12.5.1.1 Target Resources

The Target URI shall reference one of the resources shown in Table 12.5.1-1.

An origin server shall specify all supported npi-names in its Conformance Statement and in its response to the Retrieve Capabilities transaction.

Table 12.5.1-1. Store Transaction Resources

Resource	URI Template	Description
All Instances	/{npi-name}	Stores representations of a set of Instances.
Instance	/{npi-name} {/uid}	Stores a representation of a single Instance with a UID equal to uid.

12.5.1.2 Query Parameters

The user agent shall supply, and the origin server shall support, the Common Query Parameters in Section 12.1.2.

12.5.1.3 Request Header Fields

Table 12.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.
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.

12.5.1.4 Request Payload

The request payload shall be present and shall contain one or more representations in the DICOM Media Type specified by the Content-Type header field of the message, or for multipart payloads the Content-Type header field of each part.

Prev	Up	Next
12.4.3.3 Response Payload	Home	12.5.2 Behavior