worklist conformance statement v3 001 - qui sommes-nous -edl · edl xplore gestion worklist...
TRANSCRIPT
XPLORE GESTION
SCP WORKLIST
CONFORMANCE STATEMENT
Version 3.00
Mars 2009
EDL Xplore Gestion Worklist Conformance Statement Page - 2 -
Contents
1. Introduction 4
1.1 Scope and Field of Application 4
1.2 References 4
1.3 Definitions 5
Conformance Statement ....................................................................5 User Conformance Profile..................................................................5 Other definitions.................................................................................6
1.4 Symbols and Abbrevations 7
2. Implementation model 9
2.1 Application Data Flow Diagram 9
2.2 Functional Definition of Application Entities (AE) 9
2.3 Sequencing of Real World Activities 10
3. Application Entity Specifications 11
3.1 Xplore AE Specifications 11
3.2 Association Establishment Policies 11
General............................................................................................11 Number of Associations ...................................................................11 Asynchronous Nature ......................................................................11
3.3 Association Initiation by Real-World Activity 12
3.31 Verify Communication with a remote system.........................12
Associated Real World Activity....................................................12
Accepted Presentation Contexts .................................................12
3.32 Response to a Worklist Query...............................................12
Associated Real World Activity....................................................12
EDL Xplore Gestion Worklist Conformance Statement Page - 3 -
Accepted Presentation Contexts .................................................12
Transfert syntax selection policies...............................................13
4. Communication Profiles 14
4.1 Supported Communication Stacks 14
4.2 OSI Stack 14
4.3 TCP/IP Stack 14
4.4 API 14
4.5 Physical Media support 14
4.6 Point-to-Point Stack 14
5. Extensions/Specializations/ Privatizations 15
5.1 Private SOP Classes 15
5.2 Private Transfer Syntaxes 15
6. Configuration 16
6.1 AE Title/Presentation Address Mapping 16
6.2 Configurable Parameters 16
7. Support for Extended Characters Sets 17
EDL Xplore Gestion Worklist Conformance Statement Page - 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 - 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 - 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 - 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 : American College of Radiology
• AE : Application Entity
• CR : Computed Radiography
• DICOM : Digital Imaging and Communications in Medicine
• DIMSE : DICOM Message Service Element
• DIMSE- : C DICOM Message Service Element-Composite
• DIMSE- : N DICOM Message Service Element-Normalized
• HIS : Hospital Information System
• IOD : Information Object Definition
• LUT : Look-up Table
• MDIS : Medical Diagnostic Imaging Support
• NEMA : National Electrical Manufacturers Association
• OSI : Open Systems Interconnection
• PACS : Picture Archive and Communication System
• PDU : Protocol Data Unit
• RIS : Radiology Information System
• SCP : Service Class Provider
• SCU : Service Class User
• SOP : Service-Object Pair
EDL Xplore Gestion Worklist Conformance Statement Page - 8 -
• TCP/IP : Transmission Control Protocol/Internet Protocol
• UCP : User Conformance Profile
• UID : Unique Identifier
• VR : Value Representation
EDL Xplore Gestion Worklist Conformance Statement Page - 9 -
2. Implementation model
2.1 Application Data Flow Diagram
DICOM Standard
interface
User Seach
RemoteModality
Worklist SCU
Modality WorklistSCP
RemoteLocal
Find
Association Initiation
Response
Figure 1 - Application Flow Diagram for Modality Worklist SCP
This Xplore DICOM Service is implemented as a Microsoft Windows NTTM
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 - 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 1.2.840.10008.1.1
Modality Worklist Find 1.2.840.10008.5.1.4.31
3.2 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.
3.31 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 1.2.840.10008.1.1 Implicit VR,
Little Endian
1.2.840.10008.1.2 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
1.2.840.10008.5.1.4.31 Implicit VR,
Little Endian
1.2.840.10008.1.2 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 1.2.840.10008.1.2
Explicit Little Endian syntax 1.2.840.10008.1.2.1
Explicit Big Endian syntax 1.2.840.10008.1.2.2
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 1.2.840.10008.1.2.2
Explicit Little Endian syntax 1.2.840.10008.1.2.1
Explicit Little Endian syntax 1.2.840.10008.1.2
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 NTTM
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