DICOM Conformance Statement



Similar documents
g GE Medical Systems Advantage Cluster Storage / Archive System Release 1 v Conformance Statement Direction number: Revision: 2

Dx MM DICOM 3.0 Conformance Statement

DICOM Conformance Statement Merge Eye Care PACS v. 4.0

DICOM Conformance Statement. Version: 1.0

DigitizingStation. DICOM V3.0 Conformance Statement

Candelis, Inc. DICOM Conformance Statement. ImageGrid Storage Server

ONIS 2.0 DICOM CLIENT. DICOM 3 Conformance statement

GE PACS Conformance Statement for DICOM v3.0

DICOM 3.0 CONFORMANCE STATEMENT

DOLPHIN DICOM IMAGING DICOM CONFORMANCE STATEMENT

DICOM CONFORMANCE STATEMENT STORAGE SCU, Q/R SCP, PRINT SCU & STORAGE COMMITMENT SCU FOR TOSHIBA SUPERCONDUCTING MRI SYSTEMS (MIIMR0001EAB)

HP Medical Archive Solutions DICOM Conformance Statement. January 2007 (Third Edition) Part Number T

Medflow Imaging DICOM Server

Version 8 DICOM Conformance Statement. Version 3.04, September 2014

DICOM Conformance Statement FORUM

Technical Publication. DICOM Conformance Statement. DICOM Proxy 2.0. Document Revision 3. October 20, Copyright Brainlab AG

DICOM 3.0 Conformance Statement

Infinity Medical Image Server

DICOM Conformance Statement

MiPACS Storage Server Conformance Statement Version

Hologic Physician s Viewer 7.0 DICOM Conformance Statement

AGFA MEDICAL IMAGING DICOM Conformance Statement

DICOM Conformance Statement For Diagnostic Review Workstation Software Version 5-x MAN-00546

DICOM Conformance Statement CBS Images and Worklist Version 2.01

Technical Publications

DICOM Conformance Statement

Philips Medical Systems DICOM Conformance Statement

MammoView 1.5. DICOM Conformance Statement 1.0. medigration GmbH All rights reserved

Xeleris 2.0 Conformance Statement for DICOM V3.0

Technical Publications

DICOM 3.0 Conformance Statement

DICOM CONFORMANCE STATEMENT FOR ZIOSTATION 2.0

Technical Publications

Digital Imaging and Communications in Medicine (DICOM) Part 4: Service Class Specifications

AquariusNET DICOM Conformance Statement. DICOM Conformance Statement. AquariusNET 4.4. Rev B

DICOM CONFORMANCE STATEMENT FOR ZIOCUBE 1.0

Printlink5-ID_IV. DICOM 3.0 Conformance Statement PRINT MANAGEMENT SYSTEM CODE NO Manufacturer:

HDI 4000 Ultrasound System

GENIE Acquisition R3.1 Conformance Statement for DICOM v3.0

Technical Publications

Centricity TM RISi DICOM Conformance Statement

DICOM Conformance Statement

CARESTREAM PACS Suite (Client, Server, and CD Direct) Version DICOM Conformance Statement

DICOM Conformance Statement

DICOM. Conformance Statement. Envisor Software Version C.0

How To Write A Dicom Dicoma Dicomm Test Article

DICOM Conformance Statement

AGFA HEALTHCARE DICOM Conformance Statement

ClearCanvas ImageServer DICOM Conformance Statement

DICOM Conformance Statement

Varian System Server. DICOM Conformance Statement

Digital Imaging and Communications in Medicine (DICOM) Supplement 119: Frame Level Retrieve SOP Classes

DICOM Conformance Statement

ConnectPro for CT/i 4.0 Systems Conformance Statement for DICOM v3.0

Technical Publications

DICOM Correction Proposal

Table of Contents. Version History

DICOM Conformance Statement

Technical Publications

DICOM Conformance Statement. DICOMscope 3.5. Software developed by: M. Eichelberg 1, K. Kleber 2, J. Riesmeier 1, A. Schröter 2, A.

Introduction CDR Dicom for Windows is designed as a fully functional DICOM (Digital Imaging Communications of Medicine) based client-server

DICOM: Definitions and Testing

DICOM Conformance Statement

DICOM Conformance Statement

QueryRetrieveSCU Queries image archives and controls remote retrieve of images to specified destination. (= SCU of Query/Retrieve SOP classes).

DICOM Conformance Statement. Veradius Unity

SIGNA PROFILE CONFORMANCE STATEMENT

NETWORK MANAGEMENT FOR PICTURE ARCHIVING AND COMMUNICATION SYSTEMS

CT RADIATION DOSE REPORT FROM DICOM. Frank Dong, PhD, DABR Diagnostic Physicist Imaging Institute Cleveland Clinic Foundation Cleveland, OH

SwissVision TR4000. DICOM Conformance Statement File Media Storage Services. Program Version 9.3 or later Document Revision 1.2.

DICOM Conformance Statement

DICOM Conformance Statement Print Management Service Class FUJI NETWORK PRINT SERVER FN-PS551

PARCA Certified PACS Interface Analyst (CPIA) Requirements

Digital Imaging and Communications in Medicine (DICOM) Part 1: Introduction and Overview

OpenEMR: Achieving DICOM Interoperability using Mirth

Digital Imaging and Communications in Medicine (DICOM) Supplement 44: Clarification of network addressing

Medical Imaging in IDL

DICOM Conformance Statement. GDxPRO

MiPACS Storage Server

Centricity Enterprise Web 3.0 DICOM Conformance Memo DOC

Medical Imaging in IDL

DV5950 DICOM Conformance Statement. Product: DryView 5950 Laser Imaging System

Implementation of DICOM Modality Worklist at Patient Registration Systems in Radiology Unit

How To Connect Ifa Dicom To An Ophthalmology System

Philips Medical Systems DICOM Conformance Statement

Cenova Image Analytics Server DICOM Conformance Statement

Workstation, Server Hosted

DICOM Conformance Statement. CT Tomoscan M/EG/EG Compact Release 4.0. Document Number March 2000

MedDream SendToPACS USER S MANUAL (version 1.15)

Digital Imaging and Communications in Medicine (DICOM) Part 1: Introduction and Overview

FUJIFILM MEDICAL SYSTEMS

Kodak PACS Link Medical Image Manager 200 Kodak PACS Link 25 Print Server as Print Server (SCP) Software Version 6.1.1

ACR Triad Site Server Click Once Software System

Liberate Your Image Data

9 Working With DICOM. Configuring the DICOM Option

SmartPTT File Transfer User's Guide. Version 2.0

Patient Database and PACS Communication Manual

Exodus User Manual. Providing DICOM Connectivity for the Medical Community. Laurel Bridge Software, Inc

Digital Imaging and Communications in Medicine (DICOM) Part 10: Media Storage and File Format for Media Interchange

Technical Publications ADVANTAGE SIM 3.0. Conformance Statement. Revision 1. do not duplicate. Copyright 1997 by General Electric Co.

Transcription:

Inter Medical Medizintechnik GmbH Daimlerstr. 34-36 D-32312 Lübbecke Tel. (0 57 41) 23 59-0 Fax (0 57 41) 23 59-10 E-Mail Contact @Intmed.de www.intmed.de Doc. Rev. 1 GammaXP DICOM Conformance Statement Version 4.0 All rights reserved Inter Medical Medizintechnik GmbH 32312 Lübbecke

Seite 2 von 26 Table of Contents 1 INTRODUCTION 5 1.1 Purpose 5 1.2 Scope 5 1.3 Abbreviations 5 1.4 References 5 PART A DICOM STORAGE...6 A.1 IMPLEMENTATION MODEL 6 A.1.1 Application data flow diagram 6 A.1.2 Functional definition of Application Entities (AE s) 6 A.1.3 Sequencing of real-world activities 7 A.2 AE SPECIFICATIONS 7 A.2.1 AE specification for GammaXP 7 A.2.1.1 Association establishment policies 7 A.2.1.2 Association initiation Policy 7 A.2.1.3 Association acceptance Policy 8 A.3 COMMUNICATION PROFILES 9 A.3.1 Supported Communication Stacks 9 A.3.2 TCP/IP Stack 9 A.3.3 Physical Media Support 9 A.3.4 Point-to-Point Stack 9 A.4 EXTENSIONS / SPECIALIZATIONS / PRIVATIZATIONS 9 A.4.1 Standard Extended/Specialized/Private SOPs 9 A.5 CONFIGURATION 9 A.5.1 AE Title/Presentation Address Mapping 9 A.5.2 Configurable Parameters 9 A.6 SUPPORT OF EXTENDED CHARACTER SETS 10 PART B DICOM QUERY RETRIEVE...11 B.1 IMPLEMENTATION MODEL 11 B.1.1 Application data flow diagram 11 B.1.2 Functional definition of Application Entities (AE s) 12 B.1.3 Sequencing of real-world activities 12 B.2 AE SPECIFICATIONS 13 B.2.1 Query/Retrieve Service AE specification for GammaXP_administrator 13 B.2.1.1 Association establishment policies 13 B.2.1.2 Association initiation Policy 14 B.2.1.3 Association acceptance Policy 15 B.3 COMMUNICATION PROFILES 16 B.3.1 Supported Communication Stacks 16 B.3.2 TCP/IP Stack 16 B.3.3 Physical Media Support 16 B.3.4 Point-to-Point Stack 17

Seite 3 von 26 B.4 EXTENSIONS / SPECIALIZATIONS / PRIVATIZATIONS 17 B.4.1 Standard Extended/Specialized/Private SOPs 17 B.5 CONFIGURATION 17 B.5.1 AE Title/Presentation Address Mapping 17 B.5.2 Configurable Parameters 17 B.6 SUPPORT OF EXTENDED CHARACTER SETS 17 PART C DICOM BASIC PRINT...18 C.1 IMPLEMENTATION MODEL 18 C.1.1 Application data flow diagram 18 C.1.2 Functional definition of Application Entities (AE s) 18 C.1.3 Sequencing of real-world activities 18 C.2 AE SPECIFICATIONS 18 C.2.1 AE specification for GammaXP 18 C.2.1.1 Association establishment policies 19 C.2.1.2 Association initiation Policy 19 C.3 COMMUNICATION PROFILES 20 C.3.1 Supported Communication Stacks 20 C.3.2 TCP/IP Stack 20 C.3.3 Physical Media Support 20 C.3.4 Point-to-Point Stack 20 C.4 EXTENSIONS / SPECIALIZATIONS / PRIVATIZATIONS 20 C.4.1 Standard Extended/Specialized/Private SOPs 20 C.5 CONFIGURATION 21 C.5.1 AE Title/Presentation Address Mapping 21 C.5.2 Configurable Parameters 21 C.6 SUPPORT OF EXTENDED CHARACTER SETS 21 PART D DICOM MODALITY WORKLIST AND MODALITY PERFORMED PROCEDURE STEP...22 D.1 IMPLEMENTATION MODEL 22 D.1.1 Application data flow diagram 22 D.1.2 Functional definition of Application Entities (AE s) 22 D.1.3 Sequencing of real-world activities 23 D.2 AE SPECIFICATIONS 23 D.2.1 AE specification for GammaXP 23 D.2.1.1 Association establishment policies 23 D.2.1.2 Association initiation Policy 23 D.2.2.1 Association establishment policies 24 D.2.2.2 Association initiation Policy 24 D.3 COMMUNICATION PROFILES 25 D.3.1 Supported Communication Stacks 25 D.3.2 TCP/IP Stack 25 D.3.3 Physical Media Support 25 D.3.4 Point-to-Point Stack 25

Seite 4 von 26 D.4 EXTENSIONS / SPECIALIZATIONS / PRIVATIZATIONS 25 D.4.1 Standard Extended/Specialized/Private SOPs 25 D.5 CONFIGURATION 26 D.5.1 AE Title/Presentation Address Mapping 26 D.5.2 Configurable Parameters 26 D.6 SUPPORT OF EXTENDED CHARACTER SETS 26

Seite 5 von 26 1 INTRODUCTION 1.1 Purpose This DICOM conformance statement describes CompArt Medical Systems implementation of DICOM 3.0 standard in GammaXP. This conformance statement adheres to the specifications detailed in DICOM PS 3.2-1993. The GammaXP DICOM network implementation acts as: SCU and SCP for the C-Store DICOM network service SCP and SCU for the DICOM Query/Retrieve network service SCU for the Basic Print Management network service SCU for the Modality Worklist Management network service SCU for the Modality Performed Procedure Step network service 1.2 Scope The scope and format of this document are defined by the Part 2 of the DICOM V3.0 standard. 1.3 Abbreviations ACR American College of Radiology AE DICOM PDU SCU SCP SOP UID DICOM Application Entity Digital Imaging and Communications in Medicine DICOM Protocol Data Unit DICOM Service Class User (DICOM client) DICOM Service Class Provider (DICOM server) DICOM Service-Object Pair Unique IDentifier 1.4 References [1] Digital Imaging and Communications in Medicine DICOM 3.0 PS 3.1-13-1993

Seite 6 von 26 PART A DICOM Storage A.1 IMPLEMENTATION MODEL The GammaXP_administrator system utilizes the Storage and Verification services of DICOM. A.1.1 Application data flow diagram In Manual Transfer the operator selects the studies from GammaXP_administrator database console interface for transfer to a selected destination. The GammaXP_administrator network implementation is a Windows XP/2000/NT application and acts as SCU for the C-STORE network service. The GammaXP_administrator initiates association negotiation with a storage server over the network. If the association is accepted by the server, images are then transferred from the storage client to the storage server over the association. When the transfer is completed, the GammaXP_administrator closes the association. DICOM Standard Interface Transfer Images from Database GammaXP_ administrator Remote Storage SCP Write File Into Import Image Bin GammaXP_ administrator Remote Storage SCU Figure 1: Application data flow diagram A.1.2 Functional definition of Application Entities (AE s) All communication with remote applications is accomplished using the DICOM protocol over an Ethernet network running the TCP/IP protocol stack. The GammaXP_administrator application is a Service Class Provider (SCP) and a Service Class User (SCU) for the GammaXP product. Storage SCP: when an association request is received with valid connection criteria (taken from the local configuration) GammaXP_administrator waits for an C-ECHO or C-STORE request. When an ECHO is received an appropriate ECHO response is sent back to the initiator. If a STORE request is received all incoming objects are imported to the database specified by the system administrator. Storage SCU: upon request the selected images from the local database may be transferred to a predetermined DICOM-compliant image storage device. The GammaXP_administrator DICOM application initiates an association at the remote DICOM network node AE title, TCP/IP address and port number are

Seite 7 von 26 taken from the local configuration. When initiating an association with a requested DICOM network node the GammaXP_administrator provides a list of SOP Class UIDs that it will send. A.1.3 Sequencing of real-world activities Not applicable. A.2 AE SPECIFICATIONS A.2.1 AE specification for GammaXP This application Entity provides Standard Conformance to the following DICOM V.3.0 SOP Classes as a SCU and as a SCP. SOP Class Name SOP Class UID Verification 1.2.840.10008.1.1 NM Image Information Storage 1.2.840.10008.5.1.4.1.1.20 A.2.1.1 Association establishment policies A.2.1.1.1 General The GammaXP_administrator will act as an SCU of Storage Services when an image transfer request to a remote DICOM network node has been invoked. The GammaXP_administrator stores its AE title and TCP/IP listening port in the configuration file. The GammaXP_administrator uses a DICOM application profile files (Dnodes) which contains a list of all client nodes. Their respective configuration files contain the AEs, their TCP/IP addresses (or their host names), listening ports and additional configuration information. The PDU size proposed in an association request by the GammaXP_administrator will default to 32K bytes. A.2.1.1.2 Number of associations The GammaXP_administrator will open and maintain single associations. If a valid association is open, it must first be closed before a new association can be opened. A.2.1.1.3 Asynchronous nature The GammaXP_administrator does not support asynchronous communication (multiple outstanding transactions over a single association). A.2.1.1.4 Implementation identifying information for GammaXP Application Entity The Implementation Class Unique Identifier (UID) for the GammaXP is obtained from the Gvs.ini file. The Implementation Version Name will correspond to the software revision number. A.2.1.2 Association initiation Policy GammaXP_administrator attempts to initiate a new association due to the Manual Transfer initiated by the operator, If a previous association is still open when a new input session is begun, that association will be closed before a new association is initiated. The GammaXP_administrator applies a configurable time-out to determine the acceptance of the association negotiation. The time-out value is configurable the CommunicationProfile section of Gvs.ini file.

Seite 8 von 26 A.2.1.2.1. Real-world activity Send ImageObject A.2.1.2.1.1 Associated real-world activity for Send Image operations Once the association has been established, an image store message (C_STORE request) is sent by the GammaXP_administrator over the network. The remote server must either accept or reject the request. If the GammaXP_administrator receives a C-STORE response with a success or warning status, it will initiate the next C-STORE operation over the association if required, or close the association (A-RELEASE_RQ) if all images have been transferred. The GammaXP_administrator will log any warnings to the DICOM_OUT.LOG file. This log file resides in the directory /Tmp The association will be aborted (A-ABORT-RQ) if a failure is detected by the GammaXP_administrator during transfer. Failures can occur due to various reasons including: time-out, input failures or operator intervention. If the application receives an unsuccessful C-STORE response status, the association is immediately closed. The GammaXP_administrator will log the error status to the DICOM_OUT.LOG file. A.2.1.2.1.2 Proposed presentation contexts The presentation contexts that can be proposed by GammaXP_administrator for the send image operation are specified in the following table: Presentation Context Table Abstract Syntax Transfer Syntax Role Extended Negotiation Name UID Name List UID List NM Image Storage Service Class 1.2.840.10008.5.1.4.1.1.20 DICOM Implicit VR Little Endian 1.2.840.10008.1.2. SCU None All of these SOP classes conform to the Standard Storage Services as specified in the DICOM Standard A.2.1.2.1.2.1 SOP specific conformance for all storage SOP Classes The GammaXP_administrator provides Standard Conformance to the contexts listed above. The GammaXP_administrator Storage SCP Application Entity conforms to the SOP s of the Storage Service Class at Level 2 (Full). Extended negotiation is not supported. A.2.1.3 Association acceptance Policy The GammaXP_administrator DICOM application accept a new association for DIMSE-C-ECHO and DIMSE- C-STORE service operations. A.2.1.3.1. Real-world activity Receive Image Object A.2.1.3.1.1 Associated real-world activity The Storage SCP will accept an association and will receive any objects transmitted on that association are imported to the database specified by the system administrator. If the application receives an unsuccessful response status, the association is immediately closed. The GammaXP_administrator will log the error status to the DCM_IMP.LOG file. A.2.1.3.1.2 Proposed presentation contexts

Seite 9 von 26 The presentation contexts that can be proposed by GammaXP_administrator for the send image operation are specified in the following table: Presentation Context Table Abstract Syntax Transfer Syntax Role Extended Negotiation Name UID Name List UID List NM Image Storage Service Class 1.2.840.10008.5.1.4.1.1.20 DICOM Implicit VR Little Endian 1.2.840.10008.1.2. SCP None All of these SOP classes conform to the Standard Storage Services as specified in the DICOM Standard A.2.1.3.1.2.1 SOP specific conformance for all storage SOP Classes The GammaXP_administrator provides Standard Conformance to the contexts listed above. The GammaXP_administrator Storage SCP Application Entity conforms to the SOP s of the Storage Service Class at Level 2 (Full). No elements are discarded or coerced. In the event of successful C_STORE operation, the DICOM object has successfully been written to disk as a file; the GammaXP_administrator will never delete a file that it has received; the user of GammaXP determines the duration of the storage of the object. Extended negotiation is not supported. A.3 COMMUNICATION PROFILES A.3.1 Supported Communication Stacks GammaXP_administrator supports the DICOM upper layer using TCP/IP. A.3.2 TCP/IP Stack The TCP/IP stack is inherited from the Windows XP/2000/NT operating system upon which it executes. A.3.3 Physical Media Support The GammaXP DICOM application is indifferent to the physical medium through which TCP/IP executes. A.3.4 Point-to-Point Stack The 50 pin ACR-NEMA connection is not applicable to this product. A.4 EXTENSIONS / SPECIALIZATIONS / PRIVATIZATIONS A.4.1 Standard Extended/Specialized/Private SOPs Not applicable A.5 CONFIGURATION A.5.1 AE Title/Presentation Address Mapping The Local AE Title is configurable in the Gvs.ini file during an installation. If absent the default NT_GVS is used. A.5.2 Configurable Parameters Time-out for accepting/rejecting an association request Time-out for responding to an association open/close request

Seite 10 von 26 Time out for accepting a message over network The following fields are configurable for every remote DICOM node: Remote AE Title Remote IP Address Responding TCP/IP Port A.6 SUPPORT OF EXTENDED CHARACTER SETS No extended character sets are supported

Seite 11 von 26 PART B DICOM Query Retrieve B.1 IMPLEMENTATION MODEL The query/retrieve service class defines an application-level class of services which enables the management of patient and image data incorporated within the DICOM information model and enable a DICOM AE to retrieve images from a remote DICOM node. The GammaXP_administrator DICOM query/retrieve application support the query/retrieve services to act as SCU and SCP. B.1.1 Application data flow diagram The GammaXP_administrator network implementation is a Windows XP/2000/NT application and acts as SCU and SCP for the query/retrieve network service. Query/Retrieve SCU DICOM Standard Interface User Interface Query/Retrieve SCU GammaXPadmini strator C-FIND C-MOVE Query/ Retrieve SCP Storage SCU C-STORE Storage SCU

Seite 12 von 26 DICOM Standard Interface Query/Retrieve SCP Database Query/Retrieve SCP GammXPadministrator C-FIND C-MOVE Query/ Retrieve SCU Storage SCU C-STORE Storage SCP Figure 1: Application data flow diagram B.1.2 Functional definition of Application Entities (AE s) The query/retrieve SCU request the query/retrieve SCP to perform a match to the keys specified in the request and a C-Move DIMSE service initiates a C_Store operation to transfer an image from a storage SCU to a Storage SCP. The query/retrieve SCP responses to C-Find DIMSE services and C-Move involves the GammaXP_administrator DICOM query/retrieve SCP application to initiate a C-Store operation to a Storage SCP. The GammaXP_administrator query/retrieve SCP application operate as background daemon process which exists whenever the computer is switched on and responds to queries based on the records stored in its database. B.1.3 Sequencing of real-world activities Not applicable.

Seite 13 von 26 B.2 AE SPECIFICATIONS B.2.1 Query/Retrieve Service AE specification for GammaXP_administrator This application Entity provides Standard Conformance to the following DICOM V.3.0 SOP Classes as a SCU. SOP Class Name Patient Root Query/Retrieve Information Model - FIND Patient Root Query/Retrieve Information Model - MOVE SOP Class UID 1.2.840.10008.5.1.4.1.2.1.1 1.2.840.10008.5.1.4.1.2.1.2 This application Entity provides Standard Conformance to the following DICOM V.3.0 SOP Classes as a SCP. SOP Class Name Patient Root Query/Retrieve Information Model - FIND Patient Root Query/Retrieve Information Model - MOVE Patient/Study Only Query/Retrieve Information Model - FIND Patient/Study Only Query/Retrieve Information Model - MOVE SOP Class UID 1.2.840.10008.5.1.4.1.2.1.1 1.2.840.10008.5.1.4.1.2.1.2 1.2.840.10008.5.1.4.1.2.3.1 1.2.840.10008.5.1.4.1.2.3.2 B.2.1.1 Association establishment policies B.2.1.1.1 General The GammaXP_administrator stores its AE title and TCP/IP listening port in the GammaXP.ini configuration file. The GammaXP_administrator uses a DICOM application profile files (Qnodes) which contains a list of all client nodes which respond to Query/Retrieve services. Their respective configuration files contain the AEs, their TCP/IP addresses (or their host names), listening ports and additional configuration information. The PDU size proposed in an association request by the GammaXP_administrator will default to 32K bytes. B.2.1.1.2 Number of associations The GammaXP_administrator will open and maintain single associations. If a valid association is open, it must first be closed before a new association can be opened. B.2.1.1.3 Asynchronous nature The GammaXP_administrator does not support asynchronous communication (multiple outstanding transactions over a single association). B.2.1.1.4 Implementation identifying information for GammaXP Application Entity The Implementation Class Unique Identifier (UID) for the GammaXP is obtained from the GammaXP.ini file. The Implementation Version Name will correspond to the software revision number.

Seite 14 von 26 B.2.1.2 Association initiation Policy The Query/Retrieve SCU and SCP establish an association by using the DICOM association services. During association establishment the Query/Retrieve Application Entities negotiate the supported SOP classes to exchange information on capabilities of the SCP and SCU. The following DIMSE-C operations are supported as SCU: C-FIND C-MOVE B.2.1.2.1. Real-world activity Find SCU B.2.1.2.1.1 Associated real-world activity for Send Image operations The associated Real-World activity is to initiate query request to a SCP with the query model Patient Root. B.2.1.2.1.2 Proposed presentation contexts The presentation contexts that can be proposed by GammaXP_administrator are specified in the following table: Presentation Context Table Abstract Syntax Transfer Syntax Role Extended Negotiation Name UID Name List UID List Patient Root Query/ Retrieve Information Model - FIND 1.2.840.10008.5.1.4.1.2.3.1 DICOM Implicit VR Little Endian 1.2.840.10008.1.2 SCU No All of these SOP classes conform to the Standard Storage Services as specified in the DICOM Standard B.2.1.2.1.2.1 SOP specific conformance for all storage SOP Classes B.2.1.2.2. Real-world activity MOVE SCU B.2.1.2.2.1 Associated real-world activity for MOVE SCU operation The associated Real-World activity is to generate retrievals to a SCP using the C-MOVE operation with the query model Patient Root. B.2.1.2.2.2 Proposed presentation contexts The presentation contexts that can be proposed by GammaXP_administrator are specified in the following table: Presentation Context Table Abstract Syntax Transfer Syntax Role Extended Negotiation Name UID Name List UID List

Seite 15 von 26 Patient Root Query/ Retrieve Information Model - MOVE 1.2.840.10008.5.1.4.1.2.1.2 DICOM Implicit VR Little Endian 1.2.840.10008.1.2 SCU No All of these SOP classes conform to the Standard Storage Services as specified in the DICOM Standard B.2.1.2.2.2.1 SOP specific conformance for all storage SOP Classes If the DICOM software is unable to open an association with the selected destination AE, an error message is printed in the station window. B.2.1.3 Association acceptance Policy The Query/Retrieve SCU and SCP establish an association by using the DICOM association services. During association establishment the Query/Retrieve Application Entities negotiate the supported SOP classes to exchange information on capabilities of the SCP and SCU. The following DIMSE-C operations are supported as SCP: C-FIND C-MOVE B.2.1.3.1. Real-world activity Find SCP B.2.1.3.1.1 Associated real-world activity for FIND SCP The associated Real-World activity is to respond to query request to a ACU with the query model Patient Root and Patient/Study Only. B.2.1.3.1.2 Proposed presentation contexts The presentation contexts that can be proposed by GammaXP_administrator are specified in the following table: Presentation Context Table Abstract Syntax Transfer Syntax Role Extended Negotiation Name UID Name List UID List Patient Root Query/ Retrieve Information Model - FIND Patient/Stu dy Only Query/Retr ieve Information Model - FIND 1.2.840.10008.5.1.4.1.2.1.1 DICOM Implicit VR Little Endian 1.2.840.10008.5.1.4.1.2.3.1 DICOM Implicit VR Little Endian 1.2.840.10008.1.2 SCP No 1.2.840.10008.1.2 SCP No All of these SOP classes conform to the Standard Storage Services as specified in the DICOM Standard

Seite 16 von 26 B.2.1.3.1.2.1 SOP specific conformance for all storage SOP Classes No optional keys or relational queries are implemented. Selectable fields for building queries are: patient name, Patient ID (patient level) and study data range (study level). It is possible to use wildcards (*) and '?'. B.2.1.3.2. Real-world activity MOVE SCP B.2.1.3.2.1 Associated real-world activity for Send Image operations The associated Real-World activity is to respond to retrieve requested to a SCU. The SCP supports the query model Patient Root and Patient/Study Only. The Storage Service Class Conformance Statement describes the C-STORE service which is generated by the C-MOVE service B.2.1.3.2.2 Proposed presentation contexts The presentation contexts that can be proposed by GammaXP_administrator are specified in the following table: Presentation Context Table Abstract Syntax Transfer Syntax Role Extended Negotiation Name UID Name List UID List Patient Root Query/ Retrieve Information Model - FIND Patient/Stu dy Only Query/ Retrieve Information Model - FIND 1.2.840.10008.5.1.4.1.2.1.2 DICOM Implicit VR Little Endian 1.2.840.10008.5.1.4.1.2.3.2 DICOM Implicit VR Little Endian 1.2.840.10008.1.2 SCP No 1.2.840.10008.1.2 SCP No All of these SOP classes conform to the Standard Storage Services as specified in the DICOM Standard B.2.1.3.2.2.1 SOP specific conformance for all storage SOP Classes B.3 COMMUNICATION PROFILES B.3.1 Supported Communication Stacks GammaXP_administrator supports the DICOM upper layer using TCP/IP. B.3.2 TCP/IP Stack The TCP/IP stack is inherited from the Windows XP/2000/NT operating system upon which it executes. B.3.3 Physical Media Support The GammaXP DICOM application is indifferent to the physical medium through which TCP/IP executes.

Seite 17 von 26 B.3.4 Point-to-Point Stack The 50 pin ACR-NEMA connection is not applicable to this product. B.4 EXTENSIONS / SPECIALIZATIONS / PRIVATIZATIONS B.4.1 Standard Extended/Specialized/Private SOPs Not applicable B.5 CONFIGURATION B.5.1 AE Title/Presentation Address Mapping The Local AE Title is configurable in the Gvs.ini file during an installation. If absent the default NT_GVS is used. B.5.2 Configurable Parameters Time-out for accepting/rejecting an association request Time-out for responding to an association open/close request Time out for accepting a message over network The following fields are configurable for every remote DICOM node: Remote AE Title Remote IP Address Responding TCP/IP Port B.6 SUPPORT OF EXTENDED CHARACTER SETS No extended character sets are supported

Seite 18 von 26 PART C DICOM Basic Print C.1 IMPLEMENTATION MODEL The print management service classes define an application-level class of services which enable the printing of images on a hardcopy medium. The GammaXP clinical application program DICOM basic print application support the print management DIMSE services to act as SCU. C.1.1 Application data flow diagram The GammaXP clinical application program DICOM Print implementation is a Windows XP/2000/NT application and acts as SCU for the print management network service. GVCON requests image storage services of a DICOM server over an association. DICOM Standard Interface User Interface DICOM Print GammaXP application DICOM Printer Print SCP Figure 1: Application data flow diagram C.1.2 Functional definition of Application Entities (AE s) All communication with remote applications is accomplished using the DICOM protocol over an Ethernet network running the TCP/IP protocol stack. The GammaXP clinical application program application is a Service Class User (SCU) for the GammaXP DICOM printing. Upon request the selected reports may be transferred to a predetermined DICOM-compliant printer. The GammaXP clinical application program DICOM application initiates an association at the remote DICOM network node AE title, TCP/IP address and port number are taken from the local configuration. When initiating an association with a requested DICOM printer node the GammaXP clinical application program provides a list of SOP Class UIDs that it will send. C.1.3 Sequencing of real-world activities Not applicable. C.2 AE SPECIFICATIONS C.2.1 AE specification for GammaXP This application Entity provides Standard Conformance to the following DICOM V.3.0 Basic Print Management SOP Classes as a SCU. META SOP Classes SOP Class Name SOP Class UID

Seite 19 von 26 Basic Grayscale Print Management Meta SOP Class 1.2.840.10008.5.1.1.9 Basic Color Print Management Meta SOP Class 1.2.840.10008.5.1.1.18 Grayscale Print Management SOP Classes SOP Class Name SOP Class UID Basic Film Session SOP Class 1.2.840.10008.5.1.1.1 Basic Film Box SOP Class 1.2.840.10008.5.1.1.2 Basic Grayscale Image Box SOP Class 1.2.840.10008.5.1.1.4 Printer SOP Class 1.2.840.10008.5.1.1.16 Color Print Management SOP Classes SOP Class Name SOP Class UID Basic Film Session SOP Class 1.2.840.10008.5.1.1.1 Basic Film Box SOP Class 1.2.840.10008.5.1.1.2 Basic Color Image Box SOP Class 1.2.840.10008.5.1.1.4.1 Printer SOP Class 1.2.840.10008.5.1.1.16 C.2.1.1 Association establishment policies C.2.1.1.1 General The GammaXP clinical application program will act as an SCU when an image printout transfer request to a remote DICOM printer has been invoked. The GammaXP clinical application program stores its AE title and TCP/IP listening port in the configuration file. The GammaXP clinical application program uses a DICOM application profile files (DPrinters) which contains a list of all printer nodes. Their respective configuration files contain the AEs, their TCP/IP addresses (or their host names), listening ports and additional configuration information. The PDU size proposed in an association request by the GammaXP clinical application program will default to 32K bytes. C.2.1.1.2 Number of associations The GammaXP clinical application program will open and maintain single associations. If a valid association is open, it must first be closed before a new association can be opened. C.2.1.1.3 Asynchronous nature The GammaXP clinical application program does not support asynchronous communication (multiple outstanding transactions over a single association). C.2.1.1.4 Implementation identifying information for GammaXP Application Entity The Implementation Class Unique Identifier (UID) for the GammaXP is obtained from the Gvs.ini file. The Implementation Version Name will correspond to the software revision number. C.2.1.2 Association initiation Policy GammaXP clinical application program attempts to initiate a new association due to the DICOM Print option initiated by the operator. If a previous association is still open when a new input session is begun, that association will be closed before a new association is initiated. The GammaXP applies a configurable time-out to determine the acceptance of the association negotiation. The time-out value is configurable the CommunicationProfile section of Gvs.ini file.

Seite 20 von 26 C.2.1.2.1.1 Associated real-world activity The associated Real-Word activity is to print over a network a set of images on a paper or film. If the application receives an unsuccessful response status, the association is immediately closed. The GammaXP clinical application program will log the error status to the DCM_EXP.LOG file. C.2.1.2.1.2 Proposed presentation contexts The presentation contexts that can be proposed by GammaXP clinical application program for the print operation are specified in the following table: Presentation Context Table Abstract Syntax Transfer Syntax Role Extended Negotiation Name UID Name List UID List Basic Grayscale Print Management Meta SOP Class Basic Color Print Management Meta SOP Class 1.2.840.10008.5.1.1.9 DICOM Implicit VR Little Endian 1.2.840.10008.5.1.1.18 DICOM Implicit VR Little Endian 1.2.840.10008.1.2. SCU None 1.2.840.10008.1.2. SCU None C.2.1.2.1.2.1 SOP specific conformance statement If the GammaXP print software is unable to open an association with the selected destination AE, an error message is printed in the station window. C.3 COMMUNICATION PROFILES C.3.1 Supported Communication Stacks GammaXP clinical application program supports the DICOM upper layer using TCP/IP. C.3.2 TCP/IP Stack The TCP/IP stack is inherited from the Windows XP/2000/NT operating system upon which it executes. C.3.3 Physical Media Support The GammaXP clinical application program DICOM Print application is indifferent to the physical medium through which TCP/IP executes. C.3.4 Point-to-Point Stack The 50 pin ACR-NEMA connection is not applicable to this product. C.4 EXTENSIONS / SPECIALIZATIONS / PRIVATIZATIONS C.4.1 Standard Extended/Specialized/Private SOPs Not applicable

Seite 21 von 26 C.5 CONFIGURATION C.5.1 AE Title/Presentation Address Mapping The Local AE Title is configurable in the Gvs.ini file during an installation. If absent the default NT_GVS_PRINT is used. C.5.2 Configurable Parameters Time-out for accepting/rejecting an association request Time-out for responding to an association open/close request Time out for accepting a message over network The following fields are configurable for every remote DICOM node: Remote AE Title Remote IP Address Responding TCP/IP Port C.6 SUPPORT OF EXTENDED CHARACTER SETS No extended character sets are supported

Seite 22 von 26 PART D Step DICOM Modality Worklist and Modality Performed Procedure D.1 IMPLEMENTATION MODEL This implementation provides for simple transfer of patient demographic and procedure information using the DICOM Basic Modality Worklist SOP Class as a Service Class User (SCU). D.1.1 Application data flow diagram The GammaXP_Scheduler DICOM Modality Worklist implementation a Windows XP/2000/NT application and acts as SCU for the worklist management network service. GVCONN requests image storage services of a DICOM server over an association. DICOM Standard Interface GammaXP Scheduler User Modality Worklist SCP GammaXP Modality Worklist SCP (HIS/RIS) GammaXP acquisition MPPS SCP GammaXP ACQ MPPS SCP (HIS/RIS) Figure 1: Application data flow diagram D.1.2 Functional definition of Application Entities (AE s) GammaXPscheduler Worklist AE The GammaXPscheduler AE initiates an Association with a user selected remote AE and acts as a SCU of the Basic Worklist Management Service Class. The operator can initiate the Worklist Query operation, for the purpose of getting an immediate update of the patient schedule, by clicking on the Get worklist from button on the Modality Worklist Management section. The GammaXPscheduler program sends a C-FIND request based on parameters set by the user. The user can configure the Worklist AE to query for any/all modalities supported by the GammaXP system. The user can configure the Worklist to query for exams scheduled for any AE configured in the system as a Worklist SCU. GammaXPacquisition Modality Performed Procedure Step AE: The GammaXPAcquisition MPPS AE initiates an Association with the Worklist AE that provided the procedure information and acts as a SCU of the Modality Performed Procedure Step Service Class. The GammaXPAcquisition program creates a MPPS object when a patient file is opened for acquisition of images and updates the MPPS object (Completed or Discontinued) when the patient file is closed.

Seite 23 von 26 D.1.3 Sequencing of real-world activities When the operator clicks on the Get worklist from button on the Modality Worklist Management section, an association is established with the appropriate Worklist SCP, and a Query is generated for all NM procedures satisfied the query table. All of the responses are recorded in a database D.2 AE SPECIFICATIONS D.2.1 AE specification for GammaXP This application Entity provides Standard Conformance to the following DICOM V.3. Management SOP Classes as a SCU. Management SOP Classes SOP Class Name SOP Class UID Modality Worklist Management Query Find 1.2.840.10008.5.1.4.31 D.2.1.1 Association establishment policies D.2.1.1.1 General The GammaXP_Scheduler will act as an SCU when an query request to a remote DICOM worklist node has been invoked. The GammaXP_Scheduler stores its AE title and TCP/IP listening port in the configuration file. The GammaXP_Scheduler uses a DICOM application profile files (Wnodes) which contains a list of all worklist nodes. Their respective configuration files contain the AEs, their TCP/IP addresses (or their host names), listening ports and additional configuration information. The PDU size proposed in an association request by the GammaXP_Scheduler will default to 32K bytes. D.2.1.1.2 Number of associations The GammaXP_Scheduler will open and maintain single associations. If a valid association is open, it must first be closed before a new association can be opened. D.2.1.1.3 Asynchronous nature The GammaXP_Scheduler does not support asynchronous communication (multiple outstanding transactions over a single association). D.2.1.1.4 Implementation identifying information for GammaXP Application Entity The Implementation Class Unique Identifier (UID) for the GammaXP is obtained from the GammaXP.ini file. The Implementation Version Name will correspond to the software revision number. D.2.1.2 Association initiation Policy GammaXP_Scheduler attempts to initiate a new association due to the DICOM Print option initiated by the operator. If a previous association is still open when a new input session is begun, that association will be closed before a new association is initiated. The GammaXP applies a configurable time-out to determine the acceptance of the association negotiation. The time-out value is configurable the CommunicationProfile section of Gvs.ini file. D.2.1.2.1.1 Associated real-world activity The associated Real-Word activity is to print over a network a set of images on a paper or film. If the application receives an unsuccessful response status, the association is immediately closed. The GammaXP_Scheduler will log the error status to the DCM_EXP.LOG file.

Seite 24 von 26 D.2.1.2.1.2 Proposed presentation contexts The presentation contexts that can be proposed by GammaXP_Scheduler for the print operation are specified in the following table: Presentation Context Table Abstract Syntax Transfer Syntax Role Extended Negotiation Name UID Name List UID List Modality Worklist Query Find SOP Class 1.2.840.10008.5.1.4.31 DICOM Implicit VR Little Endian 1.2.840.10008.1.2. SCU None D.2.1.2.1.2.1 SOP specific conformance statement If the GammaXP worklist software is unable to open an association with the selected destination AE, an error message is printed in the station window. D.2.2 GammaXP_acquisition AE specification for Modality Performed Procedure Step The GammaXP_acquisition MPPS AE provides Standard Conformance to the following DICOM V3.0 SOP Classes as a SCU: SOP Classes SOP Class Name SOP Class UID Modality Performed Procedure Step SOP Class 1.2.840.10008.3.1.2.3.3 D.2.2.1 Association establishment policies D.2.2.1.1 General GammaXP_acquisition MPPS AE establishes an association under the following conditions: 1. When the system creates an MPPS object. 2. When the system updates an MPPS object. GammaXP_acquisition MPPS AE uses a DICOM application profile files (Wnodes) which contains a list of all MPPS SCPunits. Their respective configuration files contain the AEs, their TCP/IP addresses (or their host names), listening ports and additional configuration information. The PDU size proposed in an association request by the GammaXPscheduler will default to 32K bytes. D.2.2.1.2 Number of associations The GammaXP_acquisition will open and maintain single associations. If a valid association is open, it must first be closed before a new association can be opened. D.2.2.1.3 Asynchronous nature The GammaXP_acquisition does not support asynchronous communication (multiple outstanding transactions over a single association). D.2.2.1.4 Implementation identifying information for GammaXP Application Entity The Implementation Class Unique Identifier (UID) for the GammaXP is obtained from the GVS.ini file. The Implementation Version Name will correspond to the software revision number. D.2.2.2 Association initiation Policy

Seite 25 von 26 GammaXP_acquisition MPPS AE attempts to initiate a new association when a MPPS object is created and when a MPPS object is updated. The Association is closed after the N-CREATE-RSP or N-SET-RSP messages are received. D.2.2.2.1.1 Associated real-world activity GammaXP_acquisition MPPS AE initiates associations when a patient image acquistion is started and when the patient image acquisition file is terminated. At the acquisition start system creates an MPPS object from the information that was provided by a Worklist SCP. Once the MPPS association has been established, the GammaXP_acquisition MPPS AE sends a N-CREATE-RQ message to the MPPS SCP. When the N-CREATE-RSP message is received the association is closed. D.2.2.2.1.2 Proposed presentation contexts The presentation contexts that can be proposed by GammaXPacquisition for the MPPS operation are specified in the following table: Presentation Context Table Abstract Syntax Transfer Syntax Role Extended Negotiation Name UID Name List UID List Modality Performed Procedure Step SOP Class 1.2.840.10008.3.1.2.3.3 DICOM Implicit VR Little Endian 1.2.840.10008.1.2. SCU None D.2.2.2.1.2.1 SOP specific conformance statement If any GammaXP AE software is unable to open an association with the selected destination AE, an error message is printed in the station window. D.3 COMMUNICATION PROFILES D.3.1 Supported Communication Stacks GammaXP_Scheduler/ GammaXPacquisition support the DICOM upper layer using TCP/IP. D.3.2 TCP/IP Stack The TCP/IP stack is inherited from the Windows XP/2000/NT operating system upon which it executes. D.3.3 Physical Media Support The GammaXP_Scheduler DICOM Modality Worklist and GammaXPacquisition application are indifferent to the physical medium through which TCP/IP executes. D.3.4 Point-to-Point Stack The 50 pin ACR-NEMA connection is not applicable to this product. D.4 EXTENSIONS / SPECIALIZATIONS / PRIVATIZATIONS D.4.1 Standard Extended/Specialized/Private SOPs Not applicable

Seite 26 von 26 D.5 CONFIGURATION D.5.1 AE Title/Presentation Address Mapping The Local AE Title is configurable in the Gvs.ini file during an installation. If absent the default NT_GVS is used. D.5.2 Configurable Parameters Time-out for accepting/rejecting an association request Time-out for responding to an association open/close request Time out for accepting a message over network The following fields are configurable for every remote DICOM node: Remote AE Title Remote IP Address Responding TCP/IP Port D.6 SUPPORT OF EXTENDED CHARACTER SETS No extended character sets are supported