DICOM PS3.2 2024c - Conformance |
---|
The Search Transaction user agent can request resources listed in Table N.5-82.
[List the supported resources for your Search Transaction user agent. Remove the non-supported resources rows. Fill in specific details of your implementation if available in the "Comments" column.]
Table N.5-82. Resources Search Transaction - User Agent
See resource path in Table 10.6.1-1 in PS3.18 |
|
The Search Transaction user agent supports query parameters listed in Table N.5-83.
[Indicate the supported parameters and their supported Values. For detail on the implementation possibilities see Table 8.3.4-1 in PS3.18. Fill in specific details of your implementation if available in the "Comments" column.]
Table N.5-83. Query Parameters for Search Transaction - User Agent
Attribute Values to address the search (matching key). See the supported DICOM Attribute in the Table N.5-84 |
||
Attributes to be included in the response (return key). See the supported DICOM Attributes in the Table N.5-84 |
||
[Number of results the server skips before the first returned result.] |
[Indicate which DICOM query Attributes are supported and if they are supported as Matching and/or Return (include) key. Add or remove Attributes according to your implementation. If the tables are the same as used in DIMSE Services, you can enter a reference to Table N.5-17 and remove the text and table below. Otherwise provide the following text and Table N.5-84.]
Table N.5-84 lists the DICOM query Attributes supported by the Search Transaction user agent.
Table N.5-84. Supported Query Attributes User Agent
The Search Transaction user agent supports Header Fields listed in Table N.5-85.
[List the supported Header Fields and their supported Values. Fill in information on your implementation in the "Comments" column when necessary.]
Table N.5-85. Header Fields for Search Transaction - User Agent
See Section N.5.7 for supported Values |
The Search Transaction origin server receives GET requests to search for studies, series or instances.
[Specify here if this is a native or a DIMSE proxy implementation.]
The user agent specifies the Target Resource as part of the URI and the acceptable response Content-Type in the HTTP Header (i.e., dicom+xml or dicom+json).
The URI is composed by a Base URI: see Base URI for the origin server in Section A.6.3.2.3.
The Search Transaction origin server supports resources listed in Table N.5-86.
[Fill in information on your implementation in the Comments column when necessary.]
Table N.5-86. Resources Search Transaction - Origin Server
See resource path in Table 10.6.1-1 in PS3.18 |
||
The Search Transaction origin server supports query parameters listed in Table N.5-87.
[List the supported parameters and their supported Values. For detail on the implementation possibilities see Table 8.3.4-1 in PS3.18. Fill in information on your implementation in the "Comments" column when necessary.]
Table N.5-87. Query Parameters for Search Transaction - Origin Server
Attribute Values to address the search (matching key). See the supported DICOM Attributes provided in the response in the Table N.5-89 |
||
Attributes to be included in the response (return key). See the supported DICOM Attributes provided in the response in the Table N.5-89 |
||
Number of results the server skips before the first returned result |
The Search Transaction origin server supports Header Fields listed in Table N.5-88.
[List the supported Header Fields and their supported Values. Fill in information on your implementation in the "Comments" column when necessary.]
Table N.5-88. Header Fields for Search Transaction - Origin Server
[Indicate which DICOM query Attributes are supported / returned in the response and if they are supported as Matching and/or Return (include) key. If the tables are the same as used in DIMSE Services, you can enter a reference to Table N.5-18 and remove the text and table below. Otherwise provide the following text and Table N.5-89, and add or remove Attributes according to your implementation. In the table below, Attributes / matching /return keys in regular font style are mandatory to be supported.]
Table N.5-89 lists the DICOM query / returned Attributes supported by the Search Transaction origin server.
Table N.5-89. Query / Return Key Search Transaction - Origin Server
DICOM PS3.2 2024c - Conformance |
---|