Материал: part02

I Conformance Statement Sample WADO​

Service (Informative)​

Disclaimer:​

This document is an example DICOM Conformance Statement for a fictional application service called EXAMPLE-WADO-SERVICE​ produced by a fictional vendor called EXAMPLE-PACS-PRODUCTS.​

As stated in the annex title, this document is truly informative, and not normative. A conformance statement of an actual product might​ implement additional services and options as appropriate for its specific purpose. In addition, an actual product might implement the​ servicesdescribedinadifferentmannerand,forexample,withdifferentcharacteristicsand/orsequencingofactivities.Inotherwords,​ this conformance statement example does not intend to standardize a particular manner that a product might implement DICOM​ functionality.​

I.0 Cover Page​

Company Name: EXAMPLE-PACS-PRODUCTS.​

Product Name: EXAMPLE-WADO-SERVICE​

Version: 1.0-rev. A.1​

Internal document number: 4226-xxx-yyy-zzz rev 1​

Date: YYYYMMDD​

I.1 Conformance Statement Overview​

This fictional product EXAMPLE-WADO-SERVICE implements the WADO-URI services and the WADO RS services for access to​ DICOM SOP Instances that are stored on an EXAMPLE-PACS-ARCHIVE. The EXAMPLE-WADO-SERVICE is only available as a​ plug in option for the EXAMPLE-PACS-ARCHIVE. All of the networking, database, and other services are provided by the EXAMPLE-​ PACS-ARCHIVE. This conformance claim refers to the conformance claim for the EXAMPLE-PACS-ARCHIVE for all such services.​

Table I.1-1 provides an overview of the network services supported by EXAMPLE-WADO-SERVICE.​

Table I.1-1. Network Services​

I.2 Table of Contents​

A table of contents shall be provided to assist readers in easily finding the needed information.​

- Standard -​

I.3 Introduction​

I.3.1 Revision History​

Table I.3.1-1. Revision History​

I.3.2 Audience, Remarks, Terms and Definitions, Basics of DICOM Communication, Abbrevi-​ ations, References​

See example text in Section A.3.​

I.3.3 Additional Remarks for This Example​

ThisdocumentisasampleDICOMConformanceStatementcreatedforDICOMPS3.2.Itistobeusedsolelyasanexampletoillustrate​ howtocreateaDICOMConformanceStatementforanacquisitionmodality.Thesubjectofthedocument,EXAMPLE-WADO-SERVICE,​ is a fictional product.​

I.4 Networking​

I.4.1 Implementation Model​

I.4.1.1 Application Data Flow​

Figure I.4.1-1. Application Data Flow Diagram​

The WADO Service Application receives WADO requests from a remote AE. These requests may be either over the URI, WS or RS​ interfaces. It is associated with the local real-world activity "Retrieve Images". It converts these requests into internal lookup functions​ to find the matching SOP Instances. It then obtains these matching SOP Instances and composes a response back to the requesting​ remote AE.​

I.4.1.2 Functional Definition of AEs​

I.4.1.2.1 Functional Definition of WADO Service Application​

The reception of a WADO request will activate the AE. An internal request is sent to the search capabilities of the EXAMPLE-WADO-​ SERVICE. This request is based upon the request parameters or the URL resource end point from the WADO request. The response​ is a list of all SOP instances stored on the EXAMPLE-PACS-ARCHIVE that match the request parameters. If there are no matching​ instances, the AE will indicate this in the WADO response. For all matching instances, the AE will utilize the internal image transfer​

- Standard -​

request to obtain a copy of each instance. If the request was for retrieval of instances, these instances will be returned. If the request​ was for retrieval of rendered instances, then the AE will render each instance and return the rendered results.​

I.4.2 AE Specifications​

This AE complies with Chapter 6 in PS3.18, specifications for RS and URI access.​

I.4.2.1 WADO-WS Specifications​

DICOM has retired the WADO-WS Service. See PS3.2-2017b. This product still supports this service as described here.​

I.4.2.1.1 WADO-WS Retrieve Imaging Document Set​

Table I.4.2-1. WADO-WS Retrieve Imaging Document Set Specification​

I.4.2.1.2 WADO-WS Retrieve Rendered Imaging Document Set​

Table I.4.2-3. WADO-WS Retrieve Rendered Imaging Documents Specification​

I.4.2.1.3 WADO-WS Retrieve Imaging Document Set Metadata​

Not supported​

- Standard -​

I.4.2.1.4 Connection Policies​

I.4.2.1.4.1 General​

All standard WS connection policies apply. There are no extensions for WS options.​

I.4.2.1.4.2 Number of Connections​

EXAMPLE-WADO-SERVICE limits the number of simultaneous WS requests. Additional requests will be queued after the TCP con-​ nection is accepted. When an earlier request completes, a pending request will proceed.​

Table I.4.2-4. Number of WS Requests Supported​

EXAMPLE-WADO-SERVICE does not support WS asynchronous response.​

I.4.2.2 WADO-URI Specification​

I.4.2.2.1 WADO-URI Retrieve Imaging Document Set​

Table I.4.2-5. WADO-URI Retrieve Imaging Documents Specification​

If the URI Retrieve specifies no transfer syntax that is supported by the archive, the SOP Instance will be returned using the Implicit​ VR Little Endian Transfer Syntax.​

I.4.2.2.2 WADO-URI Retrieve Rendered Imaging Document Set​

Table I.4.2-6. WADO-URI Retrieve Rendered Imaging Documents Specification​

- Standard -​

I.4.2.2.3 WADO-URI Retrieve Imaging Document Set Metadata​

Not supported.​

I.4.2.2.4 Connection Policies​

I.4.2.2.4.1 General​

AllURIconnectionsarelimitedtoHTTPGETrequests.TheEXAMPLE-WADO-SERVICEignoresallunknownHTTPheaderparameters.​

I.4.2.2.4.2 Number of Connections​

EXAMPLE-WADO-SERVICE limits the number of simultaneous HTTP connections.​

Table I.4.2-7. Number of HTTP Requests Supported​

EXAMPLE-WADO-SERVICE supports HTTP pipelined requests and responses.​

I.4.2.3 WADO-RS Specifications​

I.4.2.3.1 WADO-RS Retrieve Study​

Table I.4.2.3-1. WADO-RS Retrieve Study​

- Standard -​