JiveX Enterprise PACS Solutions JiveX DICOM Worklist Broker Conformance Statement - DICOM Version: 4.7.2 As of 2015-08-03 VISUS Technology Transfer GmbH Universitätsstr. 136 D-44799 Bochum Germany Phone: +49 (0) 234 93693 0 Fax: +49 (0) 234 93693 199 E-Mail: info@visus.com Internet: http://www.visus.com
JiveX is a class 2b product within the scope of directive 93/42/EEC. JiveX has Section 510(k) clearance under the following number: K142750 Prescription statement for users in the United States of America: Caution: Federal law restricts this device to sale by or on the order of a physician Copyright VISUS Technology Transfer GmbH, Germany -- www.visus.com JiveX is an internationally registered trademark. All rights, including those of translation, reserved. No part of this book may be reprinted or reproduced or utilized in any form by any electronic, mechanical, or other means, now known or hereafter invented, including photocopying and recording, or in any information storage or retrieval system, without permission from VISUS Technology Transfer GmbH. The author and publisher have taken care in the preparation of this document, but do not issue any expressed or implied warranty of any kind and assume no responsibility for errors or omissions. No liability is assumed for incidental or consequential damages in connection with or arising out of the use of the information or programs contained herein. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this text and VISUS Technology Transfer GmbH was aware of a trademark claim, the designations have been printed in initial caps or all caps.
Table of contents 1 Conformance Statement Overview 5 2 Introduction 6 2.1 Revision History 6 2.2 Audience 6 2.3 Remarks 6 2.4 Definitions, Terms and Abbreviations 6 3 Networking 7 3.1 Implementation Model 7 3.1.1 Application Data Flow 7 3.1.2 Functional Definition of AEs 8 3.1.2.1 Functional Definition of "DICOM Worklist SCP Service" 8 3.1.3 Sequencing of Real World Activities 8 3.2 Application Entity Specifications 8 3.2.1 DICOM Worklist SCP Service 8 3.2.1.1 SOP Classes 8 3.2.1.2 Association Policies 8 3.2.1.3 Association Initiation Policy 9 3.2.1.4 Association Acceptance Policy 9 3.3 Network Interfaces 14 3.3.1 Physical Network Interface 14 3.3.2 Additional Protocols 14 3.4 Configuration 14 3.4.1 AE Title/Presentation Address Mapping 15 3.4.1.1 Local AE Titles 15 3.4.1.2 Remote AE Title/Presentation Address Mapping 15 3.4.2 Parameters 15 4 Media Interchange 16 5 Support of Character Sets 16 6 Security 16 6.1 Security Profiles 17 6.2 Association Level Security 17 6.3 Application Level Security 17 7 Annexes 17 7.1 IOD Contents 17 7.1.1 Created SOP Instance(s) 17 7.1.2 Usage of Attributes from received IODs 17 7.1.3 Attribute Mapping 17 7.1.4 Coerced/Modified fields 17 7.2 Data Dictionary of Private Attributes 18 7.3 Coded Terminology and Templates 18 JiveX DICOM Worklist Broker 4.7.2 3 Conformance Statement - DICOM
7.4 Grayscale Image Consistency 18 7.5 Standard Extended/Specialized/Private SOP Classes 18 7.6 Private Transfer Syntaxes 18 JiveX DICOM Worklist Broker 4.7.2 4 Conformance Statement - DICOM
1 Conformance Statement Overview The "DICOM Worklist SCP Service" is part of the DICOM Worklist Broker application. It allows modalities to query for worklists of procedures to be performed and for patient and procedure demographics. Table 1 provides an overview of the network services supported by the "DICOM Worklist SCP Service". SOP Classes User of Service (SCU) Provider of Service (SCP) Workflow Management Modality Worklist Information Model - FIND No Yes Table 1: Network Services JiveX DICOM Worklist Broker 4.7.2 5 Conformance Statement - DICOM
2 Introduction This DICOM Conformance Statement documents the conformance of the DICOM Worklist Broker software with the Digital Imaging and Communications in Medicine (DICOM) standard. This document is essential in order to evaluate whether or not another DICOM compliant device can communicate with this software product. This statement is conform to the recommended format as described in PS 3.2 of the DICOM standard. 2.1 Revision History Revision 1.0 Kleber/Ströter 2002-08-10 Draft Revision 1.0 Kleber/Ströter 2002-08-15 Draft for official review Revision 4.0 Eichelberg/Stroeter 2004-11-29 Adapted to PS3.2:2004 2.2 Audience This document is intended for hospital staff, health system integrators, software designers or implementers. It is assumed that the reader has a working understanding of DICOM. 2.3 Remarks If another device matches this Conformance Statement when compared with its own Conformance Statement, there is a chance but no guarantee that they might interoperate. DICOM only deals with communication; it is not a standard which specifies what is needed for certain applications to run on a device. 2.4 Definitions, Terms and Abbreviations ASCII AE ANSI CR CT DICOM IE American Standard Code for Information Interchange Application Entity American National Standards Institute Computed Radiography Computed Tomography Digital Imaging and Communications in Medicine Information Entity JiveX DICOM Worklist Broker 4.7.2 6 Conformance Statement - DICOM
IOD ISO NEMA OSI PDU SCP SCU SOP TCP/IP UID VM VR Information Object Definition International Standards Organization National Electrical Manufacturers Association Open Systems Interconnection Protocol Data Unit Service Class Provider Service Class User Service Object Pair Transmission Control Protocol / Internet Protocol Unique Identifier Value Multiplicity Value Representation 3 Networking 3.1 Implementation Model 3.1.1 Application Data Flow local Worklist DICOM Worklist SCP Service Worklist Request C-Find Echo Request C-Echo Server-Application DICOM Interface Local Environment Diagram 1: Application Data Flow Diagram The DICOM Worklist Broker consists of a set of parallel, communicating but independent services that deal with the DICOM communication. There may be one or more "DICOM Worklist SCP Services" that allow modalities and other applications to request a worklist. JiveX DICOM Worklist Broker 4.7.2 7 Conformance Statement - DICOM
3.1.2 Functional Definition of AEs 3.1.2.1 Functional Definition of "DICOM Worklist SCP Service" The "DICOM Worklist SCP Service" Application Entity acts as a SCP for the Verification Service Class and the DICOM Basic Modality Worklist Service Class. 3.1.3 Sequencing of Real World Activities This is not applicable. 3.2 Application Entity Specifications 3.2.1 DICOM Worklist SCP Service The "DICOM Worklist SCP Service" is an application entity that can be automatically started together with the DICOM Worklist Broker, or manually by an administrator. When the DICOM Worklist Broker is terminated, the "DICOM Worklist SCP Service" stops accepting any further associations and aborts all currently active associations. The administrator is allowed to stop the "DICOM Worklist SCP Service". The "DICOM Worklist SCP Service" stops accepting any further associations and terminates as soon as all currently active associations are closed. 3.2.1.1 SOP Classes This application provides Standard Conformance to the following DICOM SOP Classes: SOP Class Name SOP Class UID SCU SCP Modality Worklist Information Model - FIND 1.2.840.10008.5.1.4.31 No Yes Verification Service Class 1.2.840.10008.1.1 No Yes Table 2: SOP Classes for the DICOM Worklist SCP Service 3.2.1.2 Association Policies JiveX DICOM Worklist Broker 4.7.2 8 Conformance Statement - DICOM
3.2.1.2.1 General The DICOM standard application context name is always proposed and is as follows: Application context name 1.2.840.10008.3.1.1.1 3.2.1.2.2 Number of Associations The number of parallel associations can be configured. It should be limited by the resources of the underlying operating system. 3.2.1.2.3 Asynchronous Nature An asynchronous mode is not supported. 3.2.1.2.4 Implementation Identifying Information The "Implementation Class UID" is "1.2.276.0.50.20100301.4.6". The "Implementation Version Name" is "JIVEX_TK4.6". 3.2.1.3 Association Initiation Policy The "DICOM Worklist SCP Service" does not initiate associations. 3.2.1.4 Association Acceptance Policy The "DICOM Worklist SCP Service" application entity accepts an association after receiving an association request from a valid DICOM Basic Modality Worklist or Verification Service Class User. The application entity accepts incoming association requests on a single IP address and a single port number as defined in the configuration file. It accepts any association for which at least one presentation context is accepted. The calling and the called application entity titles are ignored if they are not explicitly configured. The responding application entity name can be configured in the configuration file; the default name is "JIVEX". The "DICOM Worklist SCP Service" creates a new thread for each incoming DICOM association request. The association remains open until one of the following events takes place: JiveX DICOM Worklist Broker 4.7.2 9 Conformance Statement - DICOM
the remote application entity closes the application, or an error condition leading to an association abort occurs, or a timeout occurs, or the administrator manually stops the "DICOM Worklist SCP Service". 3.2.1.4.1 Activity: Echo Request 3.2.1.4.1.1 Description and Sequencing of Activities A remote AE sends an Echo Request to verify that the "DICOM Worklist SCP Service" is awake and listening. The "DICOM Worklist SCP Service" responds with success status as long as the request can be parsed. 3.2.1.4.1.2 Accepted Presentation Contexts Abstract Syntax Transfer Syntax Role Extended Name UID Name UID Negotiation Verification SOP Class 1.2.840.10008.1.1 Implicit VR Little Endian 1.2.840.10008.1.2 SCP None Table 3: Presentation Context Table for Echo Request The application entity will accept all presentation contexts that contain one of the supported SOP classes and one of the supported transfer syntaxes. The default behavior for the selection of the transfer syntax is to choose the first supported transfer syntax for each presentation context. 3.2.1.4.1.3 SOP Specific Conformance for Verification SOP Class The "DICOM Worklist SCP Service" provides standard conformance to the DICOM Verification SOP Class. 3.2.1.4.2 Activity: Worklist Request 3.2.1.4.2.1 Description and Sequencing of Activities When a Modality Worklist SCU queries the "DICOM Worklist SCP Service", the queries run against the local worklist in the database. The figure below is a possible sequence of messages between a "Modality Worklist SCU" and the "DICOM Worklist SCP Service": The modality opens an association with the "DICOM Worklist SCP Service" to query for a Modality Worklist and it sends an MWL C-FIND query. The "DICOM Worklist SCP Service" queries its database using the attributes from the C- FIND Request and returns 0 to N C-FIND responses depending on matches returned from the database. The "DICOM Worklist SCP Service" checks for a C-FIND Cancel Request. If such is received, then no further Pending responses are sent. The "DICOM Worklist SCP Service" sends the final C-FIND response when no more responses are pending. Finally, the modality closes the association. JiveX DICOM Worklist Broker 4.7.2 10 Conformance Statement - DICOM
Modality DICOM Worklist SCP Service Open Association (1) MWL C-FIND Request (2) 0 to N Pending C-FIND Responses (3) 1 Final C-FIND Response (4) Check for C-FIND Cancel Request (3) Close Association (5) Diagram 2: Sequencing Diagram for Activity Echo Request 3.2.1.4.2.2 Accepted Presentation Contexts Abstract Syntax Transfer Syntax Role Extended Name UID Name UID Negotiation Modality Worklist Information Model - FIND 1.2.840.10008.5.1.4.31 Implicit VR Little Endian 1.2.840.10008.1.2 SCP None Table 4: Presentation Context Table for Worklist Request The application entity will accept all presentation contexts that contain one of the supported SOP classes and one of the supported transfer syntax. The default behavior for the selection of the transfer syntax is to choose the first supported transfer syntax for each presentation context. 3.2.1.4.2.3 SOP Specific Conformance for Modality Worklist SOP Class The "DICOM Worklist SCP Service" provides standard conformance to the DICOM Modality Worklist Information Model - FIND SOP Class. The following matching types are supported: Single Value Matching (SV) Universal Matching (UM) Wild Card Matching (WC) Range Matching (RM) List of UID Matching (LU) The following table lists the supported attributes and their matching and return types: JiveX DICOM Worklist Broker 4.7.2 11 Conformance Statement - DICOM
Description Tag Match Key SOP Common Remark Specific Character Set (0008,0005) Value is always ISO_IR 100 Scheduled Procedure Step Scheduled Procedure Step Sequence (0040,0100) Scheduled Station AE (0040,0001) SV Scheduled Procedure Step Start Date Scheduled Procedure Step Start Time (0040,0002) SV/RM (0040,0003) SV/RM Modality (0008,0060) SV Scheduled Performing Physician's Name Scheduled Procedure Step Description (0040,0006) SV Always zero length (0040,0007) SV Always zero length Scheduled Station Name (0040,0010) SV Always zero length Scheduled Procedure Step Location Scheduled Action Item Code Sequence Code Value (0008,0100) Coding Scheme Version (0008,0103) Coding Scheme Designator (0008,0102) Code Meaning (0008,0104) Scheduled Procedure Step ID (0040,0009) (0040,0011) Always zero Length (0040,0008) Always zero length Pre-Medication (0040,0012) Always zero length Requested Contrast Agent (0032,1070) Always zero length Requested Procedure Requested Procedure ID (0040,1001) Requested Procedure Description Requested Procedure Code Sequence Scheduled Action Item Code Sequence (0032,1060) SV (0032,1064) Always zero length (0040,0008) Code Value (0008,0100) Coding Scheme Version (0008,0103) Coding Scheme Designator (0008,0102) Code Meaning (0008,0104) Study Instance UID (0020,000D) Requested Procedure Priority (0040,1003) Always zero length Requested Procedure Priority (0040,1003) Always zero length Patient Transport Arrangements (0040,1004) Always zero length Current Patient Location (0038,0300) Always zero length JiveX DICOM Worklist Broker 4.7.2 12 Conformance Statement - DICOM
Reason for the Requested Procedure (0040,1002) Always zero length Requested Procedure Location (0040,1005) Always zero length Imaging Service Request Accession Number (0008,0050) SV/WC Requesting Physician (0032,1032) Always zero length Referring Physician's Name (0008,0090) Requesting Service (0032,1033) Always zero length Reason for the Imaging Service Request Issue Time of Imaging Service Request Placer Order Number Imaging Service Request Visit Identification (0040,2001) Always zero length (0040,2005) Always zero length (0040,2016) Always zero length Admission ID (0038,0010) Always zero length Visit Status Current Patient Location (0038,0300) Always zero length Visit Status ID (0038,0008) Always zero length Patient Institution Residence (0038,0400) Always zero length Visit Comments (0038,4000) Always zero length Visit Relationship Referenced Patient Sequence (0008,1120) Always zero length Referenced SOP Class UID (0008,1150) Referenced SOP Instance UID (0008,1155) Visit Admission Admitting Diagnosis Code Sequence Admitting Diagnosis Description Patient Identification (0008,1084) Always zero length (0008,1080) Always zero length Patient's Name (0010,0010) SV/WC Patient ID (0010,0020) SV/WC Other Patient IDs (0010,1000) Always zero length Patient Demographic Patients Birth Date (0010,0030) SV Patient's Sex (0010,0040) SV Confidentiality constraint on patient data (0040,3001) Always zero length Patient Comments (0010,4000) Always zero length Patient Medical Patient State (0038,0500) Always zero length Pregnancy Status (0010,21C0) Always zero length Medical Alerts (0010,2000) Always zero length Contrast Allergies (0010,2110) Always zero length Special Needs (0038,0050) Always zero length JiveX DICOM Worklist Broker 4.7.2 13 Conformance Statement - DICOM
Table 5: Keys for the Basic Modality Worklist Service Class The query operation may be canceled through a C-CANCEL request by the remote application at any time. The following error/warning status codes can be sent in the context of a C-FIND-RSP message: Code Name Severity Description A700 Refused Out of Resources C000 Error, cannot understand C401 Connection to database failed Refused Failure Failure The maximum number of database connections is reached. The object cannot be parsed correctly. The connection to the database was aborted. FE00 Cancel Cancel Matching terminated due to "Cancel" process. 0000 Success Success Matching is complete - No final Identifier is supplied. FF00 Pending Pending Pending Matches are continuing - Current Match is supplied and any Optional Keys were supported in the same manner as Required Keys. FF01 Warning Pending Matches are continuing - Warning that one or more Optional Keys were not supported. Table 6: Error Status of the C-FIND-RSP message 3.3 Network Interfaces 3.3.1 Physical Network Interface The application is indifferent to the physical medium over which TCP/IP executes. 3.3.2 Additional Protocols When host names rather than IP addresses are used in the configuration file to specify presentation addresses for remote AEs, the application depends on the name resolution mechanism of the underlying operating system. 3.4 Configuration JiveX DICOM Worklist Broker 4.7.2 14 Conformance Statement - DICOM
3.4.1 AE Title/Presentation Address Mapping 3.4.1.1 Local AE Titles The local application entity name can be configured in the configuration file (not at runtime). The called application entity title is ignored if not explicitly configured. Application Entity Default AE Title Default TCP/IP Port Workflow Management DICOM Worklist SCP Service JIVEX 4488 Table 7: AE Title Configuration Table 3.4.1.2 Remote AE Title/Presentation Address Mapping The AE Title, host names and port numbers of remote applications can be configured in the configuration file (not at runtime). If they are not configured explicitly, the calling application entity title is ignored in incoming associations. 3.4.2 Parameters The "DICOM Worklist SCP Service" configuration parameters related to DICOM communications are listed below. A blank cell under the "Default Value" heading indicates that there is no default value for the specific configuration attribute. JiveX DICOM Worklist Broker 4.7.2 15 Conformance Statement - DICOM
Parameter Configurable Default Value General Parameters Time-out waiting for acceptance or rejection Response to an Association Open Request. (Application Level timeout) No None General DIMSE level time-out values No None Time-out waiting for response to TCP/IP connect request. (Low-level timeout) Time-out waiting for acceptance of a TCP/IP message over the network. (Low-level timeout) Time-out for waiting for data between TCP/IP packets. (Low-level timeout) Any changes to default TCP/IP settings, such as configurable stack parameters. No No No No Modality Worklist Parameters None None None None Maximum PDU size the AE can receive Yes 16 kb Maximum PDU size the AE can send No Unlimited AE specific DIMSE level time-out values No None Number of simultaneous Associations Yes Unlimited SOP Class support No All supported SOP Classes always accepted Transfer Syntax support No All supported Transfer Syntaxes always accepted Other parameters that are configurable No None Table 8: Configuration Parameters Table 4 Media Interchange This is not supported. 5 Support of Character Sets The "DICOM Worklist SCP Service" supports the following Character Set: ISO_IR 100 (ISO 8859-1:1987 Latin Alphabet No. 1 supplementary set). 6 Security JiveX DICOM Worklist Broker 4.7.2 16 Conformance Statement - DICOM
6.1 Security Profiles These are not supported. 6.2 Association Level Security A list of calling application entity titles may be configured. If this list is not explicitly configured, any calling application entity title may open an association. 6.3 Application Level Security This is not supported. 7 Annexes 7.1 IOD Contents 7.1.1 Created SOP Instance(s) This application does not create any SOP Instances. 7.1.2 Usage of Attributes from received IODs The usage of attributes received via Modality Worklist requests is described in section 3.2.1.4.2. 7.1.3 Attribute Mapping This is not applicable. 7.1.4 Coerced/Modified fields No coercion is performed. JiveX DICOM Worklist Broker 4.7.2 17 Conformance Statement - DICOM
7.2 Data Dictionary of Private Attributes Private Attributes are not used. 7.3 Coded Terminology and Templates Codes and Controlled Terminology are not used. 7.4 Grayscale Image Consistency The Grayscale Standard Display Function is not supported. 7.5 Standard Extended/Specialized/Private SOP Classes No Standard Extended/Specialized/Private SOP Classes are supported. 7.6 Private Transfer Syntaxes No Private Transfer Syntaxes are supported. JiveX DICOM Worklist Broker 4.7.2 18 Conformance Statement - DICOM