DxServer for Windows NT DICOM 3.0 Conformance Statement Document Reference (Référence du document): 00/ Dec28/ABA/MM100/410A
Table of Contents (Table des Matières) 1 INTRODUCTION... 5 1.1 SCOPE AND AUDIENCE... 5 1.2 REFERENCES... 5 1.3 ACRONYMS AND ABBREVIATIONS... 5 2 IMPLEMENTATION MODEL... 6 2.1 APPLICATION DATA FLOW DIAGRAM... 6 2.2 FUNCTIONAL DEFINITION OF APPLICATION ENTITIES... 7 2.3 SEQUENCING OF REAL WORLD ACTIVITIES... 7 3 DXDCMSERVER AE SPECIFICATIONS... 8 3.1 ASSOCIATION ESTABLISHMENT POLICIES... 9 3.1.1 General... 9 3.1.2 Number of Associations... 9 3.1.3 Asynchronous Nature... 9 3.1.4 Implementation Identifying Information... 9 3.2 ASSOCIATION INITIATION POLICY... 10 3.2.1 Storage... 10 3.2.1.1 Associated Real-World Activity... 10 3.2.1.2 Proposed Presentation Contexts... 10 3.2.1.3 Specific SOP Class Conformance... 10 3.3 ASSOCIATION ACCEPTANCE POLICY... 11 3.3.1 Storage... 11 3.3.1.1 Associated Real-World Activity... 11 3.3.1.2 Proposed Presentation Contexts... 11 3.3.1.3 Specific SOP Class Conformance... 11 3.3.2 Query/Retrieve... 12 3.3.2.1 Associated Real-World Activity... 12 3.3.2.2 Proposed Presentation Contexts... 12 3.3.2.3 Specific SOP Class Conformance... 12 3.3.3 Verification... 12 3.3.3.1 Associated Real-World Activity... 12 3.3.3.2 Proposed Presentation Contexts... 12 3.3.3.3 Specific SOP Class Conformance... 12 4 DXDCMCLIENT AE SPECIFICATIONS... 13 4.1 ASSOCIATION ESTABLISHMENT POLICIES... 13 4.1.1 General... 13 4.1.2 Number of Associations... 13 4.1.3 Asynchronous Nature... 13 4.1.4 Implementation Identifying Information... 13 4.2 ASSOCIATION INITIATION POLICY... 14 2/16
4.2.1 Storage... 14 4.2.1.1 Associated Real-World Activity... 14 4.2.1.2 Proposed Presentation Contexts... 14 4.2.1.3 Specific SOP Class Conformance... 14 4.2.2 Verification... 15 4.2.2.1 Associated Real-World Activity... 15 4.2.2.2 Proposed Presentation Contexts... 15 4.2.2.3 Specific SOP Class Conformance... 15 4.3 ASSOCIATION ACCEPTANCE POLICY... 15 5 COMMUNICATION PROFILES... 16 5.1 SUPPORTED COMMUNICATIONS STACKS... 16 5.2 TCP/IP STACK... 16 5.3 PHYSICAL MEDIA SUPPORT... 16 6 EXTENSIONS / SPECIALIZATIONS / PRIVATIZATIONS... 16 7 CONFIGURATION... 16 3/16
Document History (Historique du Document) Indice Date Modification Author A 00/12/28 Creation for DxServer V4.0.2 ABA 4/16
1 INTRODUCTION 1.1 Scope and Audience This document is a DICOM Conformance Statement for DxServer. DxServer is a DICOM server that can store DICOM images from modalities and DICOM clients can access it to retrieve these images. This document has been written using the guidelines provided in the DICOM standard [2 part 2]. Note: The French ISO member body AFNOR has provided Medasys Digital Systems with an UID root. This UID root is only in numerical form as following: 1.2.250.1.38 1.2 References [1] DxServer Installation and Configuration Guide [2] ACR/NEMA Standards Publications, No PS3, DICOM Standards: Part 1 - Introduction Part 2 - Conformance Part 3 - Information Object Definitions Part 4 - Service Class Specifications Part 5 - Data Structures and Encoding Part 6 - Data Dictionary Part 7 - Message Exchange Part 8 - Network Communication Support Part 9 - Point to Point Communication Support for Message Exchange Part 10 - Media Storage and File Format for Media Interchange Part 11 - Media Storage Application Profiles Part 12 - Storage Functions and Media Formats for Data Interchange Part 13 - Print Management Point-to-Point Communication Support 1.3 Acronyms and abbreviations The following symbols and abbreviations are used in this conformance statement: AE: DICOM: DIMSE: SCP: SCU: SOP: TCP/IP: UID Application Entity Digital Imaging and Communication in Medicine DICOM Message Service Element Service Class Provider Service Class User Service-Object Pair Transmission Control Protocol / Internet Protocol Unique Identifier 5/16
2 IMPLEMENTATION MODEL The application Entity DxDCMserver is the part of the DxServer application that is responsible for the DICOM server side information exchanges. The application Entity DxDCMclient is the part of the DxServer application that is responsible for the DICOM client side information exchanges. 2.1 Application Data Flow Diagram Find, move, get, store, echo, remote request DxDCMserver Find, move, get, store, echo, local execution Store, remote execution Store, local execution DICOM Standard Interface Figure 1: DxDCMserver Application Data Flow Diagram As depicted in figure 1, a remote real-world activity for image handling (e.g. image storage/retrieval/query), will cause DxDCMserver local application entity to accept an association, for the purpose of causing equivalent remote real-world activity to occur. Store, echo, remote execution DxDCMclient Store, echo, local request DICOM Standard Interface Figure 2: DxDCMclient Application Data Flow Diagram As depicted in figure 2, a remote real-world activity for image handling (e.g. image storage), will cause DxDCMclient local application entity to initiate an association for the purpose of causing equivalent real-world activity to occur. 6/16
2.2 Functional Definition of Application Entities DxDCMserver application entity acts as a Service Class Provider (SCP) for the following service classes: Verification Service Class Storage Service Class Query/Retrieve Service Class DxDCMclient application entity acts as a Service Class User (SCU) for the following service classes: Verification Service Class Storage Service Class 2.3 Sequencing of Real World Activities Not applicable. 7/16
3 DXDCMSERVER AE SPECIFICATIONS The DxDCMserver application entity provides Standard Conformance to the following DICOM V3.0 SOP Classes as an SCP: Table 1: Storage SOP Classes SOP Class Name SOP Class UID CR Image Storage 1.2.840.10008.5.1.4.1.1.1 CT Image Storage 1.2.840.10008.5.1.4.1.1.2 US Multi-frame Image Storage 1.2.840.10008.5.1.4.1.1.3 US Multi-frame Image Storage 1.2.840.10008.5.1.4.1.1.3.1 MR Image Storage 1.2.840.10008.5.1.4.1.1.4 NM Image Storage 1.2.840.10008.5.1.4.1.1.5 NM Image Storage 1.2.840.10008.5.1.4.1.1.20 US Image Storage 1.2.840.10008.5.1.4.1.1.6 US Image Storage 1.2.840.10008.5.1.4.1.1.6.1 Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7 XA Image Storage 1.2.840.10008.5.1.4.1.1.12.1 RF Image Storage 1.2.840.10008.5.1.4.1.1.12.2 XA Bi-Plane Image Storage 1.2.840.10008.5.1.4.1.1.12.3 Table 2: Query/Retrieve SOP Classes SOP Class Name SOP Class UID Patient Root Query/Retrieve Information Model 1.2.840.10008.5.1.4.1.2.1.1 FIND Patient Root Query/Retrieve Information Model 1.2.840.10008.5.1.4.1.2.1.2 MOVE Patient Root Query/Retrieve Information Model 1.2.840.10008.5.1.4.1.2.1.3 GET Study Root Query/Retrieve Information Model 1.2.840.10008.5.1.4.1.2.2.1 FIND Study Root Query/Retrieve Information Model 1.2.840.10008.5.1.4.1.2.2.2 MOVE Study Root Query/Retrieve Information Model 1.2.840.10008.5.1.4.1.2.2.3 GET Table 3: Verification SOP Class SOP Class Name SOP Class UID Verification SOP Class 1.2.840.10008.1.1 8/16
3.1 Association Establishment Policies 3.1.1 General DxDCMserver application entity accepts associations for the following purposes: Supports the C-ECHO service to allow end-to-end verifications. Supports the C-STORE service to store images into the database. Supports the C-FIND service to query the database. Supports the C-MOVE service to retrieve images from the database. Supports the C-GET service to retrieve images from the database. DxDCMserver application entity initiates associations for the following purpose: Invokes the C-STORE service to send images (as sub-operations of a remote C-MOVE service request). The maximum length PDU negotiation shall be included in all association establishments. The SCU/SCP Role Negotiation is not supported. Refer to the following paragraph for extensions, specializations, and privatizations management. 3.1.2 Number of Associations The number of simultaneous DICOM associations that is accepted is theoretically unlimited, but is actually limited by the Windows NT operating system. A new process is created for each new association. 3.1.3 Asynchronous Nature Not applicable 3.1.4 Implementation Identifying Information By default, DxDCMserver will be identified by: Implementation Class UID: 1.2.250.1.38.1.3.1.1.1 Implementation Version Name: DxDCMserver4.0 9/16
3.2 Association Initiation Policy DxDCMserver AE initiates associations for the purpose of image transfers from the database, as sub-operations of a remote real-world activity of image retrieval. 3.2.1 Storage 3.2.1.1 Associated Real-World Activity DxDCMserver AE initiates associations to remote systems in order to transfer to those systems images using the C-STORE DIMSE-C service. 3.2.1.2 Proposed Presentation Contexts Abstract Syntax Transfer Syntax Name UID Name list UID list Role DICOM Implicit VR Little Endian 1.2.840.10008.1.2 Little Endian 1.2.840.10008.1.2.1 Big Endian 1.2.840.10008.1.2.2 See See Little Endian, JPEG Note Note baseline encoded 1.2.840.10008.1.2.4.50 SCU Little Endian, JPEG 1.2.840.10008.1.2.4.70 lossless encoded Little Endian, RLE 1.2.840.10008.1.2.5 lossless Table 4: DxDCMserver Storage Presentation Context Note: Abstract syntaxes of Storage SOP Classes listed into Table 1. 3.2.1.3 Specific SOP Class Conformance The following DIMSE Service is supported: C-STORE Extended Negotiation None 10/16
3.3 Association Acceptance Policy DxDCMserver AE accepts associations for the purpose of communication verification or image storage/retrieval, or database query requests of remote real-world activities. 3.3.1 Storage 3.3.1.1 Associated Real-World Activity DxDCMserver AE accepts associations from remote systems that want to store images into DxServer database using the C-STORE DIMSE-C service. 3.3.1.2 Proposed Presentation Contexts Abstract Syntax Transfer Syntax Name UID Name list UID list Role DICOM Implicit VR Little Endian 1.2.840.10008.1.2 Little Endian 1.2.840.10008.1.2.1 Big Endian 1.2.840.10008.1.2.2 See See Little Endian, JPEG Note Note baseline encoded 1.2.840.10008.1.2.4.50 SCP Little Endian, JPEG 1.2.840.10008.1.2.4.70 lossless encoded Little Endian, RLE 1.2.840.10008.1.2.5 lossless Table 5: DxDCMserver Storage Presentation Context Note: Abstract syntaxes of Storage SOP Classes listed into Table 1. 3.3.1.3 Specific SOP Class Conformance Extended Negotiation None The following DIMSE Service is supported: C-STORE DxDCMserver application entity provides full level 2 conformance to the Storage SOP Class as an SCP, although some of the attributes may be converted in order to meet the current implementation of the DxServer application. If private dictionary from other vendors are made available, and if possible, some of private elements may be also converted in order to meet the current implementation of the DxServer application, and may be made accessible to this application. Nevertheless, all of the attributes could be retrieved (identical or possibly modified) by remote applications (e.g. using C-MOVE service) and if necessary following private data elements encoding rules described into the paragraph 7.8 of the PS 3.5 part of the DICOM standard, a DICOM message related to storage SOP Class being kept with its original format into the DxServer database. 11/16
3.3.2 Query/Retrieve 3.3.2.1 Associated Real-World Activity DxDCMserver application entity accepts associations from remote systems that want to query the DxServer database using the C-FIND DIMSE-C service, and retrieve the images using the C-MOVE or C-GET DIMSE-C service, all services can be based on Standard Patient-Root Information Model, or on Standard Study-Root Information Model are support 3.3.2.2 Proposed Presentation Contexts Abstract Syntax Transfer Syntax Extended Name UID Name list UID list Role Negotiation See See DICOM Implicit VR 1.2.840.10008.1.2 SCP None Note Note Little Endian Table 6: DxDCMserver Query/Retrieve Presentation Context Note: Abstract syntaxes listed into table 2 are supported. 3.3.2.3 Specific SOP Class Conformance The following DIMSE Services are supported: C-FIND C-MOVE C-GET Optional keys are not supported. Relational-query is supported. Priority handling is not supported. 3.3.3 Verification 3.3.3.1 Associated Real-World Activity DxDCMserver application entity accepts associations from remote systems that want to verify application level communication using the C-ECHO DIMSE-C server. 3.3.3.2 Proposed Presentation Contexts Abstract Syntax Transfer Syntax Extended Name UID Name list UID list Role Negotiation See See DICOM Implicit VR 1.2.840.10008.1.2 SCP None Note Note Little Endian Table 7: DxDCMserver Verification Presentation Context Note: Abstract syntax listed in table 3 is supported. 3.3.3.3 Specific SOP Class Conformance The following DIMSE Service is supported: C-ECHO 12/16
4 DXDCMCLIENT AE SPECIFICATIONS The DxDCMclient application entity provides Standard Conformance to the following DICOM V3.0 SOP Classes as an SCU: Table 8: Storage SOP Classes SOP Class Name SOP Class UID CR Image Storage 1.2.840.10008.5.1.4.1.1.1 CT Image Storage 1.2.840.10008.5.1.4.1.1.2 US Multi-frame Image Storage 1.2.840.10008.5.1.4.1.1.3 US Multi-frame Image Storage 1.2.840.10008.5.1.4.1.1.3.1 MR Image Storage 1.2.840.10008.5.1.4.1.1.4 NM Image Storage 1.2.840.10008.5.1.4.1.1.5 NM Image Storage 1.2.840.10008.5.1.4.1.1.20 US Image Storage 1.2.840.10008.5.1.4.1.1.6 US Image Storage 1.2.840.10008.5.1.4.1.1.6.1 Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7 XA Image Storage 1.2.840.10008.5.1.4.1.1.12.1 RF Image Storage 1.2.840.10008.5.1.4.1.1.12.2 XA Bi-Plane Image Storage 1.2.840.10008.5.1.4.1.1.12.3 Table 9: Verification SOP Class SOP Class Name SOP Class UID Verification SOP Class 1.2.840.10008.1.1 4.1 Association Establishment Policies 4.1.1 General DxDCMclient AE initiates associations for the following purposes: Invokes the C-ECHO service to allow end-to-end verifications. Invokes the C-STORE service to store images into a remote database. The maximum length PDU negotiation shall be included in all association establishments. The SCU/SCP Role Negotiation is not supported. Refer to the following paragraph for extensions, specializations, and privatizations management. 4.1.2 Number of Associations Not applicable. 4.1.3 Asynchronous Nature Not applicable. 4.1.4 Implementation Identifying Information By default, DxDCMclient will be identified by: Implementation Class UID: 1.2.250.1.38.1.3.1.1.1 Implementation Version Name: DxDCMclient4.1 13/16
4.2 Association Initiation Policy DxDCMclient AE initiates associations for the purpose of communication verification or image transfers to a remote database. 4.2.1 Storage 4.2.1.1 Associated Real-World Activity DxDCMclient AE initiates associations to remote systems in order to transfer to those systems images using the C-STORE DIMSE-C service. 4.2.1.2 Proposed Presentation Contexts Abstract Syntax Transfer Syntax Name UID Name list UID list Role DICOM Implicit VR Little Endian 1.2.840.10008.1.2 Little Endian 1.2.840.10008.1.2.1 Big Endian 1.2.840.10008.1.2.2 See See Little Endian, JPEG Note Note baseline encoded 1.2.840.10008.1.2.4.50 SCU Little Endian, JPEG 1.2.840.10008.1.2.4.70 lossless encoded Little Endian, RLE 1.2.840.10008.1.2.5 lossless Table 10: DxDCMclient Storage Presentation Context Note: Abstract syntaxes of Storage SOP Classes listed into Table 8. 4.2.1.3 Specific SOP Class Conformance The following DIMSE Service is supported: C-STORE Extended Negotiation None 14/16
4.2.2 Verification 4.2.2.1 Associated Real-World Activity DxDCMclient application entity initiates associations to remote systems in order to verify application level communication using the C-ECHO DIMSE-C service. 4.2.2.2 Proposed Presentation Contexts Abstract Syntax Transfer Syntax Extended Name UID Name list UID list Role Negotiation See See DICOM Implicit VR 1.2.840.10008.1.2 SCU None Note Note Little Endian Table 11: DxDCMclient Verification Presentation Context Note: Abstract syntax listed in table 9 is supported. 4.2.2.3 Specific SOP Class Conformance The following DIMSE Service is supported: C-ECHO 4.3 Association Acceptance Policy DxDCMclient AE does not accept association. 15/16
5 COMMUNICATION PROFILES 5.1 Supported Communications Stacks Both DxDCMserver and DxDCMclient provide DICOM V3.0 TCP/IP Network Communication Support as defined in PS 3.8. 5.2 TCP/IP Stack DxDCMserver and DxDCMclient inherit their TCP/IP stack from the MS Windows system upon which they execute. 5.3 Physical Media Support DxDCMserver and DxDCMclient are indifferent to the physical medium over which TCP/IP executes; they inherit this from the MS Windows system upon which they execute. 6 EXTENSIONS / SPECIALIZATIONS / PRIVATIZATIONS Not applicable. 7 CONFIGURATION See [1] for full details. 16/16