DICOM Conformance Statement

Transcription

1 SafeCT TM Product Line DICOM Conformance Statement Medic Vision Imaging Solutions Ltd. February 2010 All rights reserved. Tel: Fax:

2 Contents 1 Introduction General Information References Definitions Symbols and Abbreviations Important Considerations for the Reader Implementation Model Application Data Flow Diagram Functional Definition of Application Entity (AE) Store (SCU) Real-World Activities Store (SCP) Real-World Activities Sequencing of Real-World Activities Features AE Specifications AE Specification for SAFECT SCU AE Association Establishment Policies Association Initiation by Real-World Activity AE Specification for SAFECT SCP AE Association Establishment Policies Association Initiation for SAFECT SCP Association Acceptance Policy for SAFECT SCP AE Communication Profiles Supported Communication Stacks TCP/IP Stack Physical Media Support Extensions/Specializations/Privatizations Standard Extended/Specialized/Private SOP s Private Transfer Syntaxes Configuration DICOM Network Configuration DICOM Store Configuration Tel: Fax: contact@medicvision.com 2

3 1 Introduction 1.1 General Information This document is the DICOM Conformance Statement for the SafeCT TM product line of Medic Vision Imaging Solutions Ltd. The purpose of this document is to describe how the product collaborates in a DICOM network with other Medical Imaging applications that conform to the DICOM 3.0 standard. 1.2 References See Digital Imaging and Communications in Medicine (DICOM), parts 1 through 18 (NEMA PS (2008)). 1.3 Definitions See Digital Imaging and Communications in Medicine (DICOM), parts 1 through 18 (NEMA PS (2008)). 1.4 Symbols and Abbreviations AE - Application Entity DICOM - Digital Imaging and Communications in Medicine HIS - Hospital Information System NEMA - National Electrical Manufacturers Association PDU - Protocol Data Unit SCP - Service Class Provider SCU - Service Class User SOP - Service-Object Pair TCP/IP - Transmission Control Protocol/Internet Protocol UID - Unique Identifier The name Medic Vision as used in this document refers to Medic Vision Imaging Solutions Ltd.; the name SafeCT as used in this document refers to the SafeCT product, operating with Software Version 1.03 or higher. 1.5 Important Considerations for the Reader The DICOM Conformance Statement by itself is not sufficient to guarantee successful connectivity between the SafeCT and equipment from other vendors. The following considerations should also be made: The integration of equipment from different vendors (including Medic Vision) goes beyond the scope of the DICOM 3.0 standard and the DICOM Conformance Statement from Medic Vision and other vendors. It is the responsibility of the user (or the user s agent) to assess the application requirements and to design a solution that integrates Medic Vision s equipment with equipment from other vendors. Tel: Fax: contact@medicvision.com 3

4 When the comparison of this DICOM Conformance Statement with a similar document produced by another vendor indicates that connectivity should be possible, it is the responsibility of the user (or user s agent) to verify this by carrying out the necessary validation tests and to check whether all the required functionality is met. Medic Vision reserves the right to make changes in the SafeCT architecture in order to assure compliance with future DICOM requirements. The user (or user s agent) should ensure that any equipment connected via DICOM to Medic Vision s equipment also follows the future evolution of the DICOM 3.0 standard. Failure to do so may result in partial loss of connectivity. Tel: Fax: contact@medicvision.com 4

5 2 Implementation Model The SafeCT product contains an implementation of a DICOM Storage Class provider (SCP), and as such, is capable of receiving DICOM images from a DICOM Storage Service Class user (SCU). In addition, the SafeCT contains an implementation of a DICOM SCU, and is therefore capable of transferring DICOM images to DICOM SCP s. 2.1 Application Data Flow Diagram Local Remote Transfer images SAFECT SCU AE STORE Remote Storage Service Class provider Association initiation Received images SAFECT SCP AE STORE Remote Storage Service Class user Association acceptance DICOM standard interface Figure 1: SafeCT application data flow diagram. Tel: Fax: contact@medicvision.com 5

6 2.2 Functional Definition of Application Entity (AE) All communications and image transfer with the remote application are accomplished utilizing the DICOM protocol over a network using the TCP/IP protocol stack Store (SCU) Real-World Activities The SAFECT SCU AE application entity performs all the functions to transmit images and associated data to network servers and/or workstations. It therefore performs the following tasks: Establishes a DICOM association with a remote DICOM device Performs storage of DICOM Information Object to a DICOM device Closes the association after each Information Object is transferred Image transfer to remote station SAFECT SCU AE C-STORE-REQ C-STORE-RSP DICOM STORE SCP Figure 2: Store SCU model Store (SCP) Real-World Activities The SAFECT SCP AE application entity performs all the functions to receive images and associated data from network servers and/or workstations. It therefore performs the following tasks: SAFECT SCP AE will respond, if asked, with the Verification SOP Class UID as an SCP for one of its implemented SOP classes. SAFECT SCP AE waits for an association to accept at the TCP/IP port number that is configured at the time the SafeCT system is initiated. When an association request is received with valid connections criteria, SAFECT SCP AE responds with a list of SOP class UID s that it will accept. It then waits for a Store request. If a Store is received, then all incoming images that are conformant to the association are forwarded to the SafeCT processing module. Received image SAFECT SCP AE C-STORE-REQ DICOM STORE SCU C-STORE-RSP Figure 3: Store SCP model. Tel: Fax: contact@medicvision.com 6

7 2.3 Sequencing of Real-World Activities Features Automatic Receiving of DICOM Images The SafeCT system operates as a DICOM Store SCP, and accepts Store requests from DICOM Store SCU s Automatic Transfer of Processing Results The processing results are automatically transferred once processing is complete. Tel: Fax: contact@medicvision.com 7

8 3 AE Specifications 3.1 AE Specification for SAFECT SCU AE SAFECT SCU AE provides Standard Conformance to the following DICOM V3.0 Service Object Pair (SOP) Classes as a Storage Service Class User (SCU). SOP Class UID SOP Class Name Verification SOP Class CT Image Storage Enhanced CT Image Storage Table 1: Valid SCU Storage SOP Classes for SAFECT SCU AE Association Establishment Policies General The SAFECT SCU AE will initiate an association as an SCU of Storage Services when the SafeCT system requests to send images over the network to a remote Storage Service Class provider. The maximum PDU size is 16 Kbyte Number of Associations The SAFECT SCU AE opens only one Store association at a time, independent of the number of destinations configured Asynchronous Nature The SAFECT SCU AE supports asynchronous communication (multiple outstanding transactions over a single association) Implementation Identifying Information The Implementation Class Unique Identifier (UID) for the SAFECT SCU Application Entity is: The Implementation Version Name for the SAFECT SCU Application Entity is: MV_SAFECT Association Initiation by Real-World Activity The SAFECT SCU AE initiates an association for the appropriate Storage Services Class that corresponds to the set of images requested to be transferred. The association is closed when all images have been sent to the remote DICOM network node. The client is also able to abort the association when an error occurs Real-world Activity for Send Image Operations The SAFECT SCU AE initiates associations for the transfer of images to a DICOM Image Storage Server. Tel: Fax: contact@medicvision.com 8

9 Associated Real-World Activity for Send Image Operations Once the Store Image association has been established, an Image Store message is sent by SAFECT SCU Proposed Presentation Contexts for Send Image Operations The presentation contexts that are proposed by SAFECT SCU AE for the Send Image operation are specified in Table 2. Abstract Syntax Transfer Syntax Role Extended Name UID Name List UID List Negotiation SCU None All Services Listed In Table 1 All Services Listed In Table 1 Explicit VR Little Endian Implicit VR Little Endian Explicit VR Big Endian All these SOP classes conform to the standard Storage Services as specified in the DICOM Standard. Table 2: Send Image Presentation Contexts of SAFECT SCU 3.2 AE Specification for SAFECT SCP AE SAFECT SCP AE provides Standard Conformance to the following DICOM V3.0 Service Object Pair (SOP) Classes as a Verification Service Class Provider (SCP). As an SCP it sends out an Echo response after it receives an Echo request from a remote AE. SOP Class UID SOP Class Name Verification SOP Class Table 3: Valid SCP Verification SOP Class for SAFECT SCP AE SAFECT SCP AE provides Standard Conformance to the following DICOM V3.0 Service Object Pair (SOP) Classes as a Storage Service Class Provider (SCP). SOP Class UID SOP Class Name CT Image Storage Enhanced CT Image Storage Table 4: Valid SCP Storage SOP Classes for SAFECT SCU AE Association Establishment Policies General The SAFECT SCP AE application will wait for an association as an SCP of Storage Services. When a Store request is received, the corresponding images are forwarded to the SafeCT processing module. The maximum PDU size is 16 Kbyte. Tel: Fax: contact@medicvision.com 9

10 Number of Associations The SAFECT SCP AE allows multiple simultaneous Store associations. There is no maximum number of associations Asynchronous Nature The SAFECT SCP AE supports asynchronous communication (multiple outstanding transactions over a single association) Implementation Identifying Information The Implementation Class Unique Identifier (UID) for the SAFECT SCP Application Entity is: The Implementation Version Name for the SAFECT SCP Application Entity is: MV_SAFECT Association Initiation for SAFECT SCP The SAFECT SCP does not initiate any associations Association Acceptance Policy for SAFECT SCP AE The SAFECT SCP client application accepts an association for the Verification and Storage Service Class. SAFECT SCP is able to abort the association when an error occurs Real-World Activity for Echo Response The SAFECT SCP Application Entity waits for an association request and accepts associations to do, among other things, the Verification Service. The association is closed after an error or when the initiator requests that it be closed Presentation Context Table for Echo Response Operation Only the presentation context listed in Table 5 will be accepted by the SAFECT SCP for the Verification Service Class. Abstract Syntax Transfer Syntax Role Extended Name UID Name List UID List Negotiation SCP None Verification Service Class Explicit VR Little Endian Implicit VR Little Endian Explicit VR Big Endian Table 5: Echo Check Presentation Contexts of SAFECT SCP Real-world Activity for Receive Image Operations SAFECT SCP waits for an association and offers to do the Image Storage service. The association is closed after an error or when the initiator requests that it be closed. Tel: Fax: contact@medicvision.com 10

11 Associated Real-World Activity for Receive Image Operations Once the association has been established, the SAFECT SCP waits for transmission of conformant Storage Service messages Presentation Context Table for Receive Image Operations Abstract Syntax Transfer Syntax Role Extended Name UID Name List UID List Negotiation All Services All Services SCP None in Table 4 in Table 4 Explicit VR Little Endian Implicit VR Little Endian Explicit VR Big Endian Table 6: Receive Image Presentation Contexts of SAFECT SCP SOP Specific Conformance for all Storage SOP Classes The SAFECT SCP AE responds to a C-STORE request with one of these response codes: Service Status Status Description Status Code (0000,0900) Related Fields Refused Out of Resources - There were insufficient resources to process the request. The request was not processed A765 (0000,0902) contains a short description of the condition. Error Data Set does not match SOP Class - A required attribute is not present in the message. The request was not processed A965 (0000,0901) contains a listing of attribute tags missing. (0000,0902) contains a short description of the condition. Cannot understand - The message was not properly DICOM-encoded. The request was not processed. C065 (0000,0902) contains a short description of the condition None Success 0000 None Presentation Context Acceptance Criterion for Receive Image Operations Not applicable since only a single presentation context for each Storage Service Class is supported. Tel: Fax: contact@medicvision.com 11

12 Transfer Syntax Selection Policies for Receive Image Operations When executing on a Little Endian machine, transfer syntaxes are accepted in the following order: Transfer Syntax UID Transfer Syntax Name Explicit Little Endian Syntax Implicit Little Endian Syntax Explicit Big Endian Syntax When executing on a Big Endian machine, transfer syntaxes are accepted in the following order: Transfer Syntax UID Transfer Syntax Name Explicit Big Endian Syntax Implicit Little Endian Syntax Explicit Little Endian Syntax Tel: Fax: contact@medicvision.com 12

13 4 Communication Profiles 4.1 Supported Communication Stacks The SafeCT provides DICOM V3.0 TCP/IP Network Communication Support as defined in PS TCP/IP Stack The SafeCT system communicates over the TCP/IP protocol stack on any physical interconnection media supporting the TCP/IP stack Physical Media Support The SafeCT system is indifferent to the physical medium over which TCP/IP executes. Tel: Fax:

14 5 Extensions/Specializations/Privatizations 5.1 Standard Extended/Specialized/Private SOP s None supported. 5.2 Private Transfer Syntaxes None supported. Tel: Fax: contact@medicvision.com 14

15 6 Configuration The SafeCT Networking and DICOM parameters can be configured through the product s DICOM Configuration files (available to the Service Engineer only). The files are the standard files used by MergeCOM DICOM libraries. The following configuration options are supported: Network DICOM Store. 6.1 DICOM Network Configuration The SafeCT network parameters are configurable. The following network parameters can be configured for the SafeCT system: Host Name IP Address DICOM Application Entity (for each service) Network Time Out (for each service). 6.2 DICOM Store Configuration Remote DICOM Storage service class providers (up to 64) are provided through the DICOM Configuration files (available to the Service Engineer only). The following parameters can be configured: Number of Remote Servers Local AE Communication Time Out Remote Station Displayed Name Remote AE Host Address Remote Port Number. Images are automatically transferred to any of the configured remote stations upon completion of processing by the SafeCT product. Tel: Fax: contact@medicvision.com 15