N.5.3.6 Storage Commitment Web Service

N.5.3.6 Storage Commitment Web Service (Current)
Prev	N.5.3 DICOM Web Services	Next

This section provides details regarding the Storage Commitment Web Service. For an overview of suppported Transactions and resources see Table N.1.3.5-1 Storage Commitment Service

N.5.3.6.1 Request Transaction - Storage Commitment Service

N.5.3.6.1.1 User Agent

The Request Transaction user agent can request resources listed in Table N.5.3.6.1.1-1.

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

Table N.5.3.6.1.1-1. Resources for Request Transaction - User Agent

Resource	Comments
	See Resources path in Table 13.1.1-1 in PS3.18
Commitment-requests

The Request Transaction user agent supports Header Fields listed in Table N.5.3.6.1.1-2.

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

Table N.5.3.6.1.1-2. Header Fields for Request Transaction - User Agent

Header Field	Supported Values	Comments
Content-Type	application /dicom+json application /dicom+xml multipart/related; type="application/dicom+json" multipart/related; type="application/dicom+xml"
Content-Length		[If Content-Encoding is not present]
Content-Encoding		[If Content-Length is not present]

N.5.3.6.1.2 Origin Server

The Request Transaction origin server receives POST requests for storage commitment of the referenced SOP Instances.

The user agent specifies the Target Resource as part of the URI and specifies the UIDs of the SOP Instances as part of the data in the request body with an appropriate Content-Type (i.e., XML or JSON).

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

The Request Transaction origin server supports resources listed in Table N.5.3.6.1.2-1.

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

Table N.5.3.6.1.2-1. Resources for Request Transaction - Origin Server

Resource	Comments
	See Resources path in Table 13.1.1-1 in PS3.18
commitment-requests

The Request Transaction origin server supports Header Fields listed in Table N.5.3.6.1.2-2.

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

Table N.5.3.6.1.2-2. Header Fields for Request Transaction - Origin Server

Header Field	Supported Values	Comments
Content-Type	application /dicom+json application /dicom+xml multipart/related; type="application/dicom+json" multipart/related; type="application/dicom+xml"
Content-Length		[If Content-Encoding is not present]
Content-Encoding		[If Content-Length is not present]

Prev	Up	Next
N.5.3.5 Notification Web Service	Home	N.5.3.6.2 Result Check Transaction - Storage Commitment Service