N.5.3.7 Modality Scheduled Procedure Step Web Service

N.5.3.7 Modality Scheduled Procedure Step Web Service (Current)
Prev	N.5.3 DICOM Web Services	Next

This section provides details regarding the Modality Scheduled Procedure Step Web Service. For an overview of supported Transactions and resources see Table N.1.3.6-1 Modality Scheduled Procedure Step Service.

N.5.3.7.1 Search Transaction - Modality Scheduled Procedure Step Service

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

N.5.3.7.1.1 User Agent

The Search Transaction user agent can request resources listed in Table N.5.3.7.1.1-1.

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

Resource	Comments
	See Resources path in Table 14.1.1-1 in PS3.18
modality-scheduled-procedure-steps

The Search Transaction user agent supports Header Fields listed in Table N.5.3.7.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.7.1.1-2. Header Fields for Search 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.7.1.2 Origin Server

The Search Transaction origin server receives GET requests to search for modality scheduled procedure steps.

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.6.

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

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

Table N.5.3.7.1.2-1. Resources for Search Transaction - Origin Server

Resource	Comments
	See Resources path in Table 14.1.1-1 in PS3.18
modality-scheduled-procedure-steps

The Search Transaction origin server supports Header Fields listed in Table N.5.3.7.1.2-2.