DICOM PS3.2 2023a - Conformance
N.5.3.2.3 Store Transaction (STOW-RS)
N.5.3.2.3.1 User Agent

For details regarding the IODs created by the system, see Annex7.8N.9.

The Store Transaction user agent can request resources listed in Table N.5-78.

[List the supported resources for your Store Transaction user agent. Remove the non-supported resources rows.Fill in information on your implementation in the Comments column when necessary.]

Table N.5-78. Resources Store Transaction - User Agent

Resource

Comments

See resource path in Table 10.5.1-1 in PS3.18

All Studies

Study


The Store Transaction user agent supports Header Fields listed in Table N.5-79.

[List the supported Header Fields and their supported Values. Fill in information on your implementation in the "Comments" column when necessary.]

Table N.5-79. Header Fields for Store Transaction - User Agent

Header Field

Supported Values

Comments

Content-Type

multipart/related; type="application/dicom"; transfer-syntax={uid}

See in the Overview section Table N.1-1 the supported DICOM SOP Classes / Transfer syntaxes (look for "Y" in the "UA" column)

multipart/related; type="application/dicom+xml"; boundary={messageBoundary}

multipart/related; type="application/dicom+json"; boundary={messageBoundary}

Uncompressed:

multipart/related; type="application/octet-stream"

Compressed:

multipart/related; type="{media-type}"

supported {media-type} being

<<Image/jpeg

image/x-dicom-rle

image/x-jls

image/jp2

image/jpx

video/mpeg2

video/mp4>>

See details in Section N.5.3.2.1.2.

Content-Length

[If Content-Encoding is not present]

Content-Encoding

[If Content-Length is not present]


N.5.3.2.3.2 Origin Server

The Store Transaction origin server receives POST requests to store or append to an existing resource on the server.

The user agent specifies the Target Resource as part of the URI and encapsulates the data in a multipart request body with a proper Content-Type (i.e., BINARY, XML or JSON).

The URI is composed by a Base URI: See Base URI for the origin server in Section N.6.3.2.2.

The Store Transaction origin server can request resources listed in Table N.5-80.

[Fill in information on your implementation in the Comments column when necessary.]

Table N.5-80. Resources Store Transaction - Origin Server

Resource

Comments

See resource path in Table 10.5.1-1 in PS3.18

All Studies

Study


The Store Transaction origin server supports Header Fields listed in Table N.5-81.

[List the supported Header Fields and their supported Values. Fill in information on your implementation in the "Comments" column when necessary.]

Table N.5-81. Header Fields for Store Transaction - Origin Server

Header Field

Supported Values

Comments

Content-Type

multipart/related; type="application/dicom"; boundary={messageBoundary}

multipart/related; type="application/dicom+xml"; boundary={messageBoundary}

multipart/related; type="application/dicom+json"; boundary={messageBoundary}

multipart/related; type="application/octet-stream"

See in the Overview section Table N.1-1 the supported DICOM SOP Classes / Transfer syntaxes (look for "Y" in the "OS" column)

multipart/related; type="application/dicom+xml"; boundary={messageBoundary}

multipart/related; type="application/dicom+json"; boundary={messageBoundary}

Uncompressed:

multipart/related; type="application/octet-stream"

Compressed:

multipart/related; type="{media-type}"

supported {media-type} being

<<Image/jpeg

image/x-dicom-rle

image/x-jls

image/jp2

image/jpx

video/mpeg2

video/mp4>>

See details in Section N.5.3.2.1.2.

Content-Length

[If Content-Encoding is not present.]

Content-Encoding

[If Content-Length is not present.]


DICOM PS3.2 2023a - Conformance