N.5.3.8.3 Retrieve Transaction - Modality Performed Procedure Step Service

N.5.3.8.3 Retrieve Transaction - Modality Performed Procedure Step Service (Current)
Prev	N.5.3.8 Modality Performed Procedure Step Web Service	Next

[If your system does not support the Modality Performed Procedure Step Web Service Retrieve Transaction, you can indicate that this section is not applicable and remove the subsections below.]

N.5.3.8.3.1 User Agent

The Retrieve Transaction user agent can request to retrieve resources listed in Table N.5.3.8.3.1-1.

[List the supported resources for your Modality Performed Procedure Step Retrieve 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.8.3.1-1. Resources for Retrieve Transaction - User Agent

Resource	Comments
	See Resources path in Table 15.1.1-1 in PS3.18
modality-performed-procedure-steps

The Retrieve Transaction user agent supports Header Fields listed in Table N.5.3.8.3.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.8.3.1-2. Header Fields for Retrieve Transaction - User Agent

Header Field	Supported Values	Comments
Content-Type	application/dicom+json (Default) 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]

Header Field

Supported Values

Comments

Content-Type

application/dicom+json (Default)

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.8.3.2 Origin Server

The Retrieve Transaction origin server receives GET requests to retrieve a modality performed procedure step.

The user agent specifies the Target Resource as part of the URI and the acceptable Content-Type in the HTTP header (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.7.

The Retrieve Transaction origin server supports resources listed in Table N.5.3.8.3.2-1.

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

Table N.5.3.8.3.2-1. Resources for Retrieve Transaction - Origin Server

Resource	Comments
	See Resources path in Table 15.1.1-1 in PS3.18
modality-performed-procedure-steps

The Retrieve Transaction origin server supports Header Fields listed in Table N.5.3.8.3.2-2.