DICOM PS3.18 2017e - Web Services

6.10.3.3 Store Transaction
Prev | 6.10.3 Transactions | Next

#### 6.10.3.3 Store Transaction

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 Instance UIDs.

##### 6.10.3.3.1 Request

Transactions in this service use the POST method. The request syntax is:

        POST SP /{npi-name} {/uid} SP version CRLF
        Content-Type: dicom-media-type CRLF
        *(header-field CRLF)
        CRLF
        payload

###### 6.10.3.3.1.1 Resources

The target URL shall reference one of the resources shown in Table 6.10.3.3.1.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 6.10.3.3.1.1-1. Resources and URI Templates

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.

###### 6.10.3.3.1.2 Query Parameters

There are no additional Query Parameters.

###### 6.10.3.3.1.3 Request Header Fields

Table 6.10.3.3.1.3-1. Store Request Header Fields

Header Field | Value | Usage | Requirements
--- | --- | --- | ---
Content-Type | dicom-media-type | M |
Accept | dicom-media-type | M |
Content-Length | uint | C | Shall be present if no transfer coding has been applied. Shall be absent otherwise.
Transfer-Encoding | encoding | C | Shall be present if a transfer coding has been applied. Shall be absent otherwise.

###### 6.10.3.3.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
6.10.3.2.3 Response | Home | 6.10.3.3.2 Behavior

DICOM PS3.18 2017e - Web Services