XPLORE GESTION SCP WORKLIST CONFORMANCE STATEMENT

Transcription

1 XPLORE GESTION SCP WORKLIST CONFORMANCE STATEMENT Version 3.00 Mars 2009

2 Contents 1. Introduction Scope and Field of Application References Definitions 5 Conformance Statement...5 User Conformance Profile...5 Other definitions Symbols and Abbrevations 7 2. Implementation model Application Data Flow Diagram Functional Definition of Application Entities (AE) Sequencing of Real World Activities Application Entity Specifications Xplore AE Specifications Association Establishment Policies 11 General...11 Number of Associations...11 Asynchronous Nature Association Initiation by Real-World Activity Verify Communication with a remote system...12 Associated Real World Activity...12 Accepted Presentation Contexts Response to a Worklist Query...12 Associated Real World Activity...12 EDL Xplore Gestion Worklist Conformance Statement Page - 2 -

3 Accepted Presentation Contexts...12 Transfert syntax selection policies Communication Profiles Supported Communication Stacks OSI Stack TCP/IP Stack API Physical Media support Point-to-Point Stack Extensions/Specializations/ Privatizations Private SOP Classes Private Transfer Syntaxes Configuration AE Title/Presentation Address Mapping Configurable Parameters Support for Extended Characters Sets 17 EDL Xplore Gestion Worklist Conformance Statement Page - 3 -

4 1. Introduction 1.1 Scope and Field of Application This document is the DICOM Conformance Statement of the Worklist Service of the Xplore Gestion 4.0 product line of EDL. The purpose of this document is to describe how the Xplore Gestion application interacts in a DICOM network with other DICOM applications using the Worklist service Class. Xplore is a product developed by EDL. 1.2 References See the following documents : ACR-NEMA V3.0 - Digital Image and Communications in Medicine (DICOM) - PART 1: Introduction and Overview ACR-NEMA V3.0 - Digital Image and Communications in Medicine (DICOM) - PART 2: Conformance ACR-NEMA V3.0 - Digital Image and Communications in Medicine (DICOM) - Part 3: Information Object Definitions Part 3 Addendum Basic Worklist Management ACR-NEMA V3.0 - Digital Image and Communications in Medicine (DICOM) - Part 4: Service Class Definitions Part 4 Addendum Basic Worklist Management Service Class ACR-NEMA V3.0 - Digital Image and Communications in Medicine (DICOM) - Part 5: Data Structures and Encoding EDL Xplore Gestion Worklist Conformance Statement Page - 4 -

5 ACR-NEMA V3.0 - Digital Image and Communications in Medicine (DICOM) - Part 6: Data Dictionary Part 6 Addendum Basic Worklist Management ACR-NEMA V3.0 - Digital Image and Communications in Medicine (DICOM) - Part 7: Message Exchange ACR-NEMA V3.0 - Digital Image and Communications in Medicine (DICOM) - PART 8 Network Communication Support for Message Exchange : ACR-NEMA V3.0 - Digital Image and Communications in Medicine (DICOM) - PART 9: Network Protocols ACR-NEMA V3.0 - Digital Image and Communications in Medicine (DICOM) - PART 10: Media Services ACR-NEMA V3.0 - Digital Image and Communications in Medicine (DICOM) - PART 11: Application Profiles ACR-NEMA V3.0 - Digital Image and Communications in Medicine (DICOM) - PART 12: Physical Media 1.3 Definitions Conformance Statement A formal statement associated with a specific implementation of the DICOM Standard. It specifies the Service Classes, Information Objects, and Communication Protocols supported by the implementation. User Conformance Profile A formal statement of requirements defined by a potential user of DICOM conformant equipment that must be satisfied by a specific implementation of the DICOM Standard. It specifies the Service Classes, Information Objects, and Communication Protocols to be supported by the implementation. EDL Xplore Gestion Worklist Conformance Statement Page - 5 -

6 Other definitions See also the following documents : ACR-NEMA V3.0 - Digital Image and Communications in Medicine (DICOM) - PART 1: Introduction and Overview ACR-NEMA V3.0 - Digital Image and Communications in Medicine (DICOM) - PART 2: Conformance ACR-NEMA V3.0 - Digital Image and Communications in Medicine (DICOM) - Part 3: Information Object Definitions ACR-NEMA V3.0 - Digital Image and Communications in Medicine (DICOM) - Part 4: Service Class Definitions ACR-NEMA V3.0 - Digital Image and Communications in Medicine (DICOM) - Part 5: Data Structures and Encoding ACR-NEMA V3.0 - Digital Image and Communications in Medicine (DICOM) - Part 6: Data Dictionary ACR-NEMA V3.0 - Digital Image and Communications in Medicine (DICOM) - Part 7: Message Exchange ACR-NEMA V3.0 - Digital Image and Communications in Medicine (DICOM) - PART 8: Network Communication Support for Message Exchange ACR-NEMA V3.0 - Digital Image and Communications in Medicine (DICOM) - PART 9: Network Protocols ACR-NEMA V3.0 - Digital Image and Communications in Medicine (DICOM) - PART 10: Media Services ACR-NEMA V3.0 - Digital Image and Communications in Medicine (DICOM) - PART 11: Application Profiles ACR-NEMA V3.0 - Digital Image and Communications in Medicine (DICOM) - PART 12: Physical Media EDL Xplore Gestion Worklist Conformance Statement Page - 6 -

7 1.4 Symbols and Abbrevations The name Xplore used in this document refers to Xplore Gestion application from EDL. The following symbols and abbreviations are used in this conformance specification. ACR : AE : CR : DICOM : DIMSE : DIMSE- : DIMSE- : HIS : IOD : LUT : MDIS : NEMA : OSI : PACS : PDU : RIS : SCP : SCU : SOP : American College of Radiology Application Entity Computed Radiography Digital Imaging and Communications in Medicine DICOM Message Service Element C DICOM Message Service Element-Composite N DICOM Message Service Element-Normalized Hospital Information System Information Object Definition Look-up Table Medical Diagnostic Imaging Support National Electrical Manufacturers Association Open Systems Interconnection Picture Archive and Communication System Protocol Data Unit Radiology Information System Service Class Provider Service Class User Service-Object Pair EDL Xplore Gestion Worklist Conformance Statement Page - 7 -

8 TCP/IP : UCP : UID : VR : Transmission Control Protocol/Internet Protocol User Conformance Profile Unique Identifier Value Representation EDL Xplore Gestion Worklist Conformance Statement Page - 8 -

9 2. Implementation model 2.1 Application Data Flow Diagram Local Remote Association Initiation User Seach Modality Worklist SCP Find Response Remote Modality Worklist SCU DICOM Standard interface Figure 1 - Application Flow Diagram for Modality Worklist SCP This Xplore DICOM Service is implemented as a Microsoft Windows NT TM Service that run as background processes. 2.2 Functional Definition of Application Entities (AE) All communication is accomplished utilizing the DICOM protocol over anetwork using the TCP/IP protocol stack. Xplore will respond, if asked, with the Verification SOP Class UID as an SCP for one of its implemented SOP Classes. The SCP waits for an association to accept at the TCP/IP port number that is configured at the time this application is initiated. When an association request is received with valid connection criteria, The SCP responds with a list of SOP Class UIDs that it will accept. It then waits for an Echo, or Find request to determine what specific function it has to perform. If an Echo is received, then an appropriate Echo response is sent back to the initiator. If a Find request is received, then the archive is searched for the requested information and a Find response is returned with all the found information. EDL Xplore Gestion Worklist Conformance Statement Page - 9 -

10 2.3 Sequencing of Real World Activities Not applicable. EDL Xplore Gestion Worklist Conformance Statement Page

11 3. Application Entity Specifications 3.1 Xplore AE Specifications The Xplore DICOM services provide support for the following DICOM V3.0 SOP Classes as an SCP : SOP Class Name SOP Class UID Verification Modality Worklist Find Association Establishment Policies General The Xplore Worklist SCP application will wait for an association as an SCP for the Modality Worklist Service Class. When a Find request is received, a search is done in the Xplore database for the data with the requested attributes, and a list of found attributes is returned to the remote requester. Number of Associations The Xplore Worklist Service accepts a number of associations which is configured at the time of system initialization. It should be noted that responses time for an association degrades with increasing simultaneous associations. This slow response time may trigger timers in remote systems. Asynchronous Nature Not supported EDL Xplore Gestion Worklist Conformance Statement Page

12 3.3 Association Initiation by Real-World Activity The SCP application initiates an association for the appropriate Modality Worklist Service Class that corresponds to the data requested and returned. The association is closed when all data has been sent to the remote DICOM network node. The client is also able to abort the association through an operator requested abort or when an error occurs Verify Communication with a remote system Associated Real World Activity The Xplore Verification SCU Service sends out a request to test DICOM communication with a remote DICOM system. Accepted Presentation Contexts Presentation Context Table Abstract Syntax Transfer Syntax Role Extended Name UID Name UID Negociation Verification Implicit VR, Little Endian SCU None 3.32 Response to a Worklist Query Associated Real World Activity Once the association has been established, the SCP waits for transmission of conforment Modality Worklist Service messages. If a valid Find is received, then the Xplore database is searched and the requested information is returned to the requester. The association is closed after an error or when the initiator request that it be closed. Accepted Presentation Contexts EDL Xplore Gestion Worklist Conformance Statement Page

13 Presentation Context Table Abstract Syntax Transfer Syntax Role Extended Name UID Name UID Negociation Modality Worklist Find Implicit VR, Little Endian SCP None Transfert syntax selection policies When executing on a Little Endian machine, transfer syntaxes are accepted in the following order : SOP Class Name SOP Class UID Implicit Little Endian syntax Explicit Little Endian syntax Explicit Big Endian syntax When executing on a Big Endian machine, transfer syntaxes are accepted in the following order : SOP Class Name SOP Class UID Implicit Big Endian syntax Explicit Little Endian syntax Explicit Little Endian syntax EDL Xplore Gestion Worklist Conformance Statement Page

14 4. Communication Profiles 4.1 Supported Communication Stacks The Xplore DICOM services provide DICOM V3.0 TCP/IP Network Communication Support as defined in Part 8 of the DICOM Standard. 4.2 OSI Stack Not supported. 4.3 TCP/IP Stack The Xplore DICOM services uses the TCP/IP stack from the Microsoft Windows NT TM operating system upon which it executes. 4.4 API Not applicable to this product. 4.5 Physical Media support The Xplore services are not dependent on the physical medium over which the TCP/IP executes, for example, Ethernet, ATM or FFDI. 4.6 Point-to-Point Stack Not applicable to this product. EDL Xplore Gestion Worklist Conformance Statement Page

15 5. Extensions/Specializations/ Privatizations 5.1 Private SOP Classes Not applicable to this product. 5.2 Private Transfer Syntaxes Not applicable to this product. EDL Xplore Gestion Worklist Conformance Statement Page

16 6. Configuration The Xplore DICOM Service references four configuration files. The first, xplore.ini,is found through the XPLORE_INI environnement variable. They are as follows: xplore.ini : Specifies the names of of the other three configuration files and also contains message logging parameters. xplorecom.pro : Specifies run-time parameters for the applications. xplorecom.app : Defines applications on other network nodes, to wich connections are possible. xplorecom.srv : Service and sequence definitions. 6.1 AE Title/Presentation Address Mapping Presentation address mapping is configured in the xplorecom.app file. this is where the host name, Port Number and Application title map an Application Entity (AE) Title to a Presentation Address in TCP/IP for the provider to wich you wish to connect. 6.2 Configurable Parameters The xplorecom.pro configuration file can be used to set or modify other lower-level communication parameters. This includes time-outs and other parameters. Some information about supported SOP Classes is also stored here. EDL Xplore Gestion Worklist Conformance Statement Page

17 7. Support for Extended Characters Sets Not supported EDL Xplore Gestion Worklist Conformance Statement Page