Материал: part02

J.4.2.1 STOW-RS Specifications​

J.4.2.1.1 STOW-RS Store Instance​

Table J.4.2-1. STOW-RS Store Instances Specification​

J.4.2.2.4 Connection Policies​

J.4.2.2.4.1 General​

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

J.4.2.2.4.2 Number of Connections​

EXAMPLE-STOW-SERVICE limits the number of simultaneous RS requests. Additional requests will be queued after the HTTP​ connection is accepted. When an earlier request completes, a pending request will proceed.​

Table J.4.2-4. Number of HTTP Requests Supported​

EXAMPLE-STOW-SERVICE does not support RS asynchronous response.​

J.4.2.2.4.4 SOP Specific Conformance for SOP Class(Es)​

The EXAMPLE-STOW-SERVICE response message header contains status codes indicating success, warning, or failure as shown​ in the "HTTP Standard Response Codes" below. No additional status codes are used.​

Table J.4.2.2.4.4-1. HTTP Standard Response Codes​

This may also be used to indicate that a STOW-RS Service was unable to store any​ instances for a mixture of reasons.​

Additional information regarding the instance errors can be found in the XML response​ message body.​

- Standard -​

The EXAMPLE-STOW-SERVICE response message body (PS3.18 XML Store Instances Response Module) contains the DICOM​ status codes for individual SOP Instances indicating success, warning, or failure as defined below. No additional status codes are​ used.​

For the following semantics the associated value are used for the Warning Reason (0008,1196):​

B000​Coercion of Data Elements​

The STOW-RS Service modified one or more data elements during storage of the instance.​

B006​Elements Discarded​

The STOW-RS Service discarded some data elements during storage of the instance.​

B007​Data Set does not match SOP Class​

The STOW-RS Service stored the instance despite the Data Set not matching the constraints of the SOP Class.​

Additional codes may be used for the Warning Reason (0008,1196) to address the semantics of other issues.​

In the event that multiple codes may apply, the single most appropriate code is used.​

For the following semantics the associated value are used for the Failure Reason (0008,1197).​

A700​Refused out of Resources​

The STOW-RS Service did not store the instance because it was out of memory.​

A710​Refused out of Resources​

The STOW-RS Service did not store the instance because it was out of storage space.​

A900​Error: Data Set does not match SOP Class​

The STOW-RS Service did not store the instance because the SOP Class of an element in the Referenced SOP Instance​ Sequence did not correspond to the SOP class registered for this SOP Instance at the STOW-RS Service.​

C000​Error: Cannot understand​

The STOW-RS Service did not store the instance because it cannot understand certain Data Elements.​

C122​Referenced Transfer Syntax not supported​

The STOW-RS Service did not store the instance because it does not support the requested Transfer Syntax for the instance.​

0110​ Processing failure​

The STOW-RS Service did not store the instance because of a general failure in processing the operation.​

0122​Referenced SOP Class not supported​

- Standard -​

The STOW-RS Service did not store the instance because it does not support the requested SOP Class.​

Additional codes may be used for the Failure Reason (0008,1197) to address the semantics of other errors.​

In the event that multiple codes may apply, the single most appropriate code shall be used.​

J.4.3 Network Interfaces​

J.4.3.1 Physical Network Interface​

EXAMPLE-STOW-SERVICE uses the network interface from the hosting EXAMPLE-PACS-ARCHIVE. See its conformance claim​ for details.​

J.4.3.2 Additional Protocols​

EXAMPLE-STOW-SERVICE uses the network services from the hosting EXAMPLE-PACS-ARCHIVE. See its conformance claim for​ details.​

J.4.3.3 IPv4 and IPv6 Support​

This product supports both IPv4 and IPv6 connections.​

J.4.4 Configuration​

J.4.4.1 STOW-RS Interface​

The EXAMPLE-STOW-SERVICE is configured to respond to TLS protected traffic. The TLS port will refuse any connection from a​ system that is not recognized as authenticated by a known authority.​

J.5 Media Interchange​

Not applicable​

J.6 Support of Character Sets​

All EXAMPLE-STOW-SERVICEs support Unicode UTF-8 for all RS transactions.​

TheEXAMPLE-STOW-SERVICEdoesnotconvertcharactersetswhenstoringPS3.10binaryInstances.TheoriginalDICOMencoded​ character sets are preserved.​

J.7 Security​

The EXAMPLE-STOW-SERVICE supports the following transport level security measures:​

•​HTTP BASIC Authorization over SSL​

•​Digest Authorization​

•​SSL Client Certificates​

The transport level security measures support bi-directional authentication using TLS connections. The EXAMPLE-STOW-SERVICE​ can provide its certificate information, and can be configured with either a direct comparison (self-signed) certificate or a chain of trust​ certificates.​

The EXAMPLE-STOW-SERVICE will refuse a connection over TLS from a source that does not have a recognized authentication.​ For example, a certificate authenticated by "Big Hospital Provider" will not be accepted unless the EXAMPLE-STOW-SERVICE has​ been configured to accept authentications from "Big Hospital Provider". The list of acceptable certificates for EXAMPLE-STOW-​ SERVICE is not shared with certificates used by other system applications and must be maintained independently.​

The EXAMPLE-STOW-SERVICE can optionally be configured to use the following session authentication mechanisms:​

- Standard -​

•​Kerberos Local Domain Sessions​

•​Shibboleth Cross Domain Sessions (using SAML2.0)​

•​OAuth 2.0 complying with IHE ITI Internet User Authentication (IUA)​

J.8 Annexes​

J.8.1 IOD Contents​

See conformance claim for the EXAMPLE-PACS-ARCHIVE.​

J.8.2 Data Dictionary of Private Attributes​

No data dictionary for private attributes is provided. Private attributes are stored as received without modification.​

J.8.3 Coded Terminology and Templates​

See conformance claim for EXAMPLE-PACS-ARCHIVE.​

J.8.4 Standard Extended / Specialized / Private SOP Classes​

See conformance claim for EXAMPLE-PACS-ARCHIVE.​

J.8.5 Private Transfer Syntaxes​

Private transfer syntaxes are not supported.​

- Standard -​

K Conformance Statement Sample QIDO-RS​

Provider (Informative)​

Disclaimer:​

This document is an example DICOM Conformance Statement for a fictional application service called EXAMPLE-QIDO-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.​

K.0 Cover Page​

Company Name: EXAMPLE-PACS-PRODUCTS​

Product Name: EXAMPLE-QIDO-SERVICE​

Version: 1.0-rev. A.1​

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

Date: YYYYMMDD​

K.1 Conformance Statement Overview​

This fictional product EXAMPLE-QIDO-SERVICE implements QIDO-RS, which allow the client to search for studies, series or SOP​ instances stored in an EXAMPLE-PACS-ARCHIVE. The EXAMPLE- QIDO-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 K.1-1 provides an overview of the network services supported by EXAMPLE-QIDO-SERVICE.​

Table K.1-1. Network Services​

K.2 Table of Contents​

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

- Standard -​