Материал: part02

UID or assign a new UID if the received image data is lossy​ compressedbytheQUERY-RETRIEVE-SERVERpriortoarchival.​

Note​

Note that only overlay information contained in the 6000 Group will be used for display. Overlay information contained in the​ other possible Groups (6002, 6004, etc.) will be ignored for display purposes. Such information will still be archived however.​

F.8.1.2 STORAGE-SCU AE Element Modification​

The following table contains a list of all Elements that can have a value modified by the STORAGE-SCU at the time of export using​ the Storage Service depending on the capabilities of the receiver:​

Table F.8.1-3. Significant Elements in Exported Composite SOP Instances​

- Standard -​

- Standard -​

G Conformance Statement Sample​ ImageViewer with Hanging Protocol Support​ (Informative)​

Disclaimer:​

This document is an example DICOM Conformance Statement for a fictional image display device for DICOM images and Hanging​ Protocol objects obtained over the network.​

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

G.0 Cover Page​

Company Name: EXAMPLE-ViewingPRODUCTS.​

Product Name: SAMPLE ImageViewer with Hanging Protocol Support​

Version: 1.0-rev. A.1​

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

Date: YYYYMMDD​

G.1 Conformance Statement Overview​

TheapplicationsupportsacceptingImagesandPresentationStatesfromremotesystems,andqueryingaremotesystemforHanging​ Protocol Instances that may then be retrieved to the local system. It also supports sending locally loaded images and created​ Presentation State and Hanging Protocol Instances across the network to remote systems.​

Table G.1-1. Network Services​

G.2 Table of Contents​

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

- Standard -​

G.3 Introduction​

G.3.1 Revision History​

Table G.3.1-1. Revision History​

G.3.2 Audience, Remarks, Terms and Definitions, Basics of DICOM Communic-​ ation, Abbreviations, References​

See example text in Section A.3.​

G.3.3 Additional Remarks for This Example​

ThisdocumentisasampleDICOMConformanceStatementcreatedforDICOMPS3.2.Itistobeusedsolelyasanexampletoillustrate​ howtocreateaDICOMConformanceStatementforaworkstationsupportingavarietyoftypesofDICOMimagesandDICOMHanging​ Protocol objects. The subject of the document, SAMPLE IMAGE VIEWER, is a fictional product.​

G.4 Networking​

G.4.1 Implementation Model​

G.4.1.1 Application Data Flow​

Figure G.4.1-1. Implementation Model​

The application provides both a user interface, internal database and network listener that spawns additional threads as necessary​ to handle incoming connections.​

- Standard -​

Conceptually the network services may be modeled as the following separate AEs, though in fact all the AEs share a single (config-​ urable) AE Title:​

•​STORAGE-SCP, which receives incoming Image, Presentation State, and Hanging Protocol Instances​

•​STORAGE-SCU, which sends outbound Image, Presentation State, and Hanging Protocol Instances​

•​FIND-SCU, which queries remote AEs for Hanging Protocol Instances​

•​MOVE-SCU, which retrieves Hanging Protocol Instances​

G.4.1.2 Functional Definitions of AEs​

G.4.1.2.1 STORAGE-SCP​

STORAGE-SCP waits in the background for connections, will accept associations with Presentation Contexts for SOP Classes of the​ Storage Service Class and Hanging Protocol Storage Service Class, and will store the received instances to the local database where​ they may subsequently be listed and viewed through the user interface.​

G.4.1.2.2 STORAGE-SCU​

STORAGE-SCUisactivatedthroughtheuserinterfacewhenauserselectsinstancesfromthelocaldatabase,orthecurrentlydisplayed​ instance, and requests that they be sent to a remote AE (selected from a pre-configured list).​

G.4.1.2.3 FIND-SCU​

FIND-SCU is activated in the background when images for a study are received, to query for matching Hanging Protocols if an appro-​ priate Hanging Protocol Instance is not available in the local database.​

G.4.1.2.4 MOVE-SCU​

MOVE-SCUisactivatedinthebackground,toretrieveHangingProtocolInstancesidentifiedinthequeryresultsreturnedtotheFIND-​ SCU.AconnectiontotheremoteAEisestablishedtoinitiateandmonitortheretrieval,andtheSTORAGE-SCPAEreceivestheretrieved​ instances.​

G.4.1.3 Sequencing of Real-World Activities​

All SCP activities are performed asynchronously in the background and not dependent on any sequencing.​

Storage SCU activities are sequentially initiated in the user interface, and another activity may not be initiated until the prior activity​ has completed. Find and Move SCU activities are performed asynchronously in the background, where Move activities are triggered​ by the results of Find activities.​

G.4.2 AE Specifications​

G.4.2.1 STORAGE-SCP​

G.4.2.1.1 SOP Classes​

STORAGE-SCP provide Standard Conformance to the following SOP Class(es) :​

Table G.4.2-1. SOP Classes Supported By STORAGE-SCP​

- Standard -​