DICOM PS3.2 2023d - Conformance |
---|
This section provides details regarding the URI Web Service. For an overview of the supported transactions see Table N.1-8 URI Service.
The supported DICOM Storage SOP Classes / Transfer Syntaxes are listed in Section N.1.1 of this document.
[Provide requirements for display and processing of instances received via Web Services. This could either be done by referencing Section N.5.2.5.2 if the same requirements apply, or by copying the tables from Section N.5.2.5.2 and filling them appropriately, if the requirements for Web Services differ.]
Table N.5-61 lists the supported rendered Media types depending on the Media Type category.
[Indicate which category / Media types are supported by your system by marking the cells with Y or N. Remove rows for Media Types neither supported as user agent nor as Origin Server].
[Provide requirements for display and processing of instances retrieved via URI Web Service. This could either be done by referencing Section N.5.2.5.2 (as indicated below), if the same requirements apply, or by copying the tables from Section N.5.2.5.2 and filling them appropriately if requirements for retrieved instances differ.]
In order to display or process DICOM instances retrieved via URI Web Service, see Section N.5.2.5.2.
The URI Web Service user agent supports the Query Parameters listed in Table N.5-62.
[List the supported parameters and their supported Values. Fill in information on your implementation in the "Comments" column when necessary.]
Table N.5-62. Query Parameters for Retrieve DICOM Instance URI Web Service - User Agent
[Must be compatible with the acceptable Media Types in the HTTP Header] See in the Overview section Table N.1-1 the supported DICOM SOP Classes / Transfer Syntaxes. Look for "Y" in the "UA" column |
||
The URI Web Service User Agent supports the Header Fields listed in Table N.5-63:
[List the supported Header Fields and their supported Values. Fill in information on your implementation in the "Comments" column when necessary.]
Table N.5-63. Header Fields for Retrieve DICOM Instance URI Web Service - User Agent
See in the Overview section Table N.1-1 the supported DICOM SOP Classes / Transfer Syntaxes. Look for "Y" in the "UA" column |
||
The URI Web Service origin server receives GET requests for studies, series and instances containing query parameters and headers fields. Supported Values are listed in the query parameters and header fields tables (Table N.5-64 and Table N.5-65).
The URI is composed by a Base URI: see Section N.6.3.1 for the Base URI of the Origin Server.
The URI Web Service origin server supports the Query Parameters listed in Table N.5-64.
[List the supported parameters and their Values. Fill in information on your implementation in the "Comments" column when necessary.]
Table N.5-64. Query Parameters for Retrieve DICOM Instance URI Web Service - Origin Server
See in the Overview section Table N.1-1 the supported DICOM SOP Classes / Transfer Syntaxes. Look for "Y" in the "OS" column |
||
The URI Web Service origin server supports the Header Fields listed in Table N.5-65.
[List the supported Header Fields and their supported Values. Fill in information on your implementation in the "Comments" column when necessary.]
Table N.5-65. Header Fields for Retrieve DICOM Instance URI Web Service - Origin Server
See in the Overview section Table N.1-1 the supported DICOM SOP Classes / Transfer Syntaxes. Look for "Y" in the "OS" column |
||
[Provide requirements for display and processing of instances retrieved via URI Web Service. This could either be done by referencing section 5.2.5.2 (as indicated below), if the same requirements apply, or by copying the tables from Section 5.2.5.2 and filling them appropriately if requirements for retrieved instances differ.]
To display or process DICOM instances retrieved via URI Web Service, see Section N.5.2.5.2.
The URI Web Service user agent supports the Query Parameters listed in Table N.5-66.
[List the supported parameters and their supported Values. Fill in information on your implementation in the "Comments" column when necessary.]
Table N.5-66. Query Parameters for Retrieve Rendered Instance URI Web Service - User Agent
See Section N.5.3.1.1.2 for details |
||
[if presentationUID specified then presentationSeriesUID must be present.] |
The URI Web Service user agent supports Header Fields listed in Table N.5-67.
[List the supported Header Fields and their supported Values. Fill in information on your implementation in the "Comments" column when necessary.]
Table N.5-67. Header Fields for Retrieve Rendered Instance URI Web Service - User Agent
See Section N.5.3.1.1.2 for details |
||
The URI Web Service origin server receives GET requests for studies, series and instances containing query parameters and headers fields. Supported Values are listed in the query parameters and header fields tables (Table N.5-68 and Table N.5-69).
The URI is composed by a Base URI: see Section N.6.3.1 for the Base URI of the origin server.
The URI Web Service origin server supports Query Parameters listed in Table N.5-68.
[List the supported parameters and their supported Values. Fill in information on your implementation in the "Comments" column when necessary.]
Table N.5-68. Query Parameters for Retrieve Rendered Instance URI Web Service - Origin Server
See details in Section N.5.3.1.1.2 |
||
[if presentationUID specified then presentationSeriesUID must be present.] |
The URI Web Service origin server supports Header Fields listed in Table N.5-69.
[List the supported Header Fields and their supported Values. Fill in information on your implementation in the "Comments" column when necessary.]
Table N.5-69. Header Fields for Retrieve Rendered Instance URI Web Service - Origin Server
See details in Section N.5.3.1.1.2 Rendered Media Types |
DICOM PS3.2 2023d - Conformance |
---|