Technical Publications

Transcription

1 g GE Medical Systems Technical Publications Direction Revision 1 Precision 500D for DICOM V3.0 Copyright 2002 By General Electric Co. Do not duplicate

2 THIS PAGE LEFT INTENTIONALLY BLANK

3 i

4 TABLE OF CONTENTS 1. INTRODUCTION OVERVIEW OVERALL DICOM DOCUMENT STRUCTURE INTENDED AUDIENCE SCOPE AND FIELD OF APPLICATION IMPORTANT REMARKS REFERENCES DEFINITIONS SYMBOLS AND ABBREVIATIONS NETWORK INTRODUCTION IMPLEMENTATION MODEL AE SPECIFICATIONS COMMUNICATION PROFILES EXTENSIONS / SPECIALIZATIONS / PRIVATIZATIONS CONFIGURATION SUPPORT OF EXTENDED CHARACTER SETS MEDIA STORAGE INTRODUCTION IMPLEMENTATION MODEL AE SPECIFICATIONS AUGMENTED AND PRIVATE APPLICATION PROFILES EXTENSIONS, SPECIALIZATIONS, PRIVATIZATIONS OF SOP CLASSES AND TRANSFER SYNTAXES CONFIGURATION ii

5 GE MEDICAL SYSTEMS 3.7 SUPPORT OF EXTENDED CHARACTER SETS PATIENT ROOT QUERY/RETRIEVE INFORMATION MODEL DEFINITION INTRODUCTION PATIENT ROOT INFORMATION MODEL DESCRIPTION PATIENT ROOT INFORMATION MODEL ENTITY-RELATIONSHIP MODEL INFORMATION MODEL KEYS STUDY ROOT QUERY/RETRIEVE INFORMATION MODEL DEFINITION INTRODUCTION STUDY ROOT INFORMATION MODEL DESCRIPTION STUDY ROOT INFORMATION MODEL ENTITY-RELATIONSHIP MODEL INFORMATION MODEL KEYS PATIENT/STUDY ONLY QUERY/RETRIEVE INFORMATION MODEL DEFINITION INTRODUCTION PATIENT/STUDY ONLY INFORMATION MODEL DESCRIPTION PATIENT/STUDY ONLY INFORMATION MODEL ENTITY-RELATIONSHIP MODEL INFORMATION MODEL KEYS MODALITY WORKLIST INFORMATION MODEL DEFINITION INTRODUCTION MODALITY WORKLIST INFORMATION MODEL DESCRIPTION MODALITY WORKLIST INFORMATION MODEL ENTITY-RELATIONSHIP MODEL INFORMATION MODEL MODULE TABLE INFORMATION MODEL KEYS PRIVATE DATA DICTIONARY X-RAY ANGIOGRAPHY (XA) INFORMATION OBJECT IMPLEMENTATION INTRODUCTION iii

6 GE MEDICAL SYSTEMS 8.2 XA IOD IMPLEMENTATION XA ENTITY-RELATIONSHIP MODEL IOD MODULE TABLE INFORMATION MODULE DEFINITIONS X-RAY RF (XRF) INFORMATION OBJECT IMPLEMENTATION INTRODUCTION XRF IOD IMPLEMENTATION XRF ENTITY-RELATIONSHIP MODEL IOD MODULE TABLE INFORMATION MODULE DEFINITIONS NETWORK PRINT SCU INTRODUCTION IMPLEMENTATION MODEL AE SPECIFICATIONS PRINT MANAGEMENT SOP CLASS DEFINITION INTRODUCTION PRINT MANAGEMENT SOP CLASS DEFINITIONS STORAGE COMMITMENT PUSH MODEL SOP CLASS DEFINITION INTRODUCTION STORAGE COMMITMENT PUSH MODEL SOP CLASS DEFINITION PERFORMED PROCEDURE STEP INTRODUCTION IMPLEMENTATION MODEL AE SPECIFICATION COMMUNICATION PROFILES EXTENSIONS/SPECIALIZATION/PRIVATIZATION iv

7 GE MEDICAL SYSTEMS 13.6 CONFIGURATION SUPPORT OF EXTENDED CHARACTER SETS N-CREATE & NSET REQUEST MESSAGE ERROR HANDLING AND RECOVERY USE OF SPECIFIC DICOM DATA v

8 1. INTRODUCTION 1.1 OVERVIEW This DICOM Conformance Statement is divided into Sections as described below: Section 1 (Introduction), which describes the overall structure, intent, and references for this Conformance Statement Section 2 (Network Conformance Statement), which specifies the GEMS equipment compliance to the DICOM requirements for the implementation of Networking features. Section 3 (Media Storage Conformance Statement), which specifies the GEMS equipment compliance to the DICOM requirements for the implementation of Media Storage features. Section 4 (Patient Root Query/ Retrieve Information Model), which specifies the GEMS equipment compliance to DICOM requirements for the implementation of the Patient Root Query/Retrieve Information Model feature. Section 5 (Study Root Query/ Retrieve Information Model), which specifies the GEMS equipment compliance to DICOM requirements for the implementation of the Study Root Query/Retrieve Information Model feature. Section 6 (Patient Study Only Query/ Retrieve Information Model), which specifies the GEMS equipment compliance to DICOM requirements for the implementation of the Patient Study Only Query/Retrieve Information Model feature. Section 7 (Modality Worklist Information Model Definition), which specifies the GEMS equipment compliance to DICOM requirements for the implementation of the Basic Worklist Management Service feature. Section 8 (XA Information Object Implementation), which specifies the GEMS equipment compliance to DICOM requirements for the implementation of a XA Information Object. Section 9 (XRF Information Object Implementation), which specifies the GEMS equipment compliance to DICOM requirements for the implementation of a XRF Information Object. Section 10 (Network Print SCU Conformance Statement), which specifies the GEMS equipment compliance to DICOM requirements for the implementation of the Network Print feature. Section 11 (Network Print Management SOP Class Definition), which specifies the GE1MS equipment compliance to DICOM requirements for the implementation of the Network Print Management SOP Class. Section 12 (Storage Commitment Push Model), which specifies the GEMS equipment compliance to DICOM requirements for the implementation of the Storage Commitment Push Service feature. 1 1

9 GE MEDICAL SYSTEMS Section 13 (Modality Performed Procedure Step), which specifies the GEMS equipment compliance to DICOM requirements for the implementation of the Modality Performed Procedure Step feature. 1 2

10 GE MEDICAL SYSTEMS 1.2 OVERALL DICOM DOCUMENT STRUCTURE The Documentation Structure of the GEMS Conformance Statements and their relationship with the DICOM v3.0 Conformance Statements is shown in the Illustration below. ID/Net v3.0 Introduction to the Integrated DICOM/Network v3.0 (ID/Net v3.0) Conformance Statement Direction: APPLICATION ENTITY SPECIFICATION (SERVICE CLASSES, INFORMATION OBJECTS, MESSAGE EXCHANGES, ETC.) Product Implementation: CT Advantage Conformance MR Advantage Statement Conformance Precision Direction: Statement 500D Conformance Direction: Statement Direction: Conformance Statement Direction:... DICOM STANDARD Standard Specification: DICOM V 3.0 DICOM V 3.0 Part 1 DICOM V 3.0 Part 2 DICOM V 3.0 Part 3 Part 4 DICOM V 3.0 Part

11 GE MEDICAL SYSTEMS This document specifies the DICOM v3.0 implementation. It is entitled: 1.3 INTENDED AUDIENCE Precision 500D Conformance Statement for DICOM v3.0 Direction This DICOM Conformance Statement documents the DICOM v3.0 Conformance Statement and Technical Specification required to interoperate with the GEMS network interface. Introductory information, which is applicable to all GEMS Conformance Statements, is described in the document: Introduction to the Integrated DICOM/Network v3.0 (ID/Net v3.0) Conformance Statement Direction: This Introduction familiarizes the reader with DICOM terminology and general concepts. It should be read prior to reading the individual products' GEMS Conformance Statements. The GEMS Conformance Statement, contained in this document, also specifies the Lower Layer communications which it supports (e.g., TCP/IP). However, the Technical Specifications are defined in the DICOM v3.0 Part 8 standard. For more information including Network Architecture and basic DICOM concepts, please refer to the Introduction. For more information regarding DICOM, copies of the Standard may be obtained on the Internet at Comments on the standard may be addressed to: DICOM Secretariat NEMA 1300 N. 17 th Street, Suite 1847 Rosslyn, VA USA The reader of this document is concerned with software design and/or system integration issues. It is assumed that the reader of this document is familiar with the DICOM v3.0 Standards and with the terminology and concepts which are used in those Standards. If readers are unfamiliar with DICOM v3.0 terminology they should first refer to the document listed below, then read the DICOM v3.0 Standard itself, prior to reading this DICOM Conformance Statement document. Introduction to the Integrated DICOM/Network v3.0 (ID/Net v3.0) Conformance Statement Direction: SCOPE AND FIELD OF APPLICATION It is the intent of this document, in conjunction with the Introduction to the Integrated DICOM/Network v3.0 (ID/Net v3.0) Conformance Statement, Direction: , to provide an unambiguous specification for GEMS implementations. This specification, called a 1 4

12 GE MEDICAL SYSTEMS Conformance Statement, includes a DICOM v3.0 Conformance Statement and is necessary to ensure proper processing and interpretation of GEMS medical data exchanged using DICOM v3.0. The GEMS Conformance Statements are available to the public. The reader of this DICOM Conformance Statement should be aware that different GEMS devices are capable of using different Information Object Definitions. For example, a GEMS CT Scanner may send images using the CT Information Object, MR Information Object, Secondary Capture Object, etc. Included in this DICOM Conformance Statement are the Module Definitions which define all data elements used by this GEMS implementation. If the user encounters unspecified private data elements while parsing a GEMS Data Set, the user is well advised to ignore those data elements (per the DICOM v3.0 standard). Unspecified private data element information is subject to change without notice. If, however, the device is acting as a "full fidelity storage device", it should retain and re-transmit all of the private data elements which are sent by GEMS devices. 1.5 IMPORTANT REMARKS The use of these DICOM Conformance Statements, in conjunction with the DICOM v3.0 Standards, is intended to facilitate communication with GE imaging equipment. However, by itself, it is not sufficient to ensure that inter-operation will be successful. The user (or user's agent) needs to proceed with caution and address at least four issues: Integration - The integration of any device into an overall system of interconnected devices goes beyond the scope of standards (DICOM v3.0), and of this introduction and associated DICOM Conformance Statements when interoperability with non-ge equipment is desired. The responsibility to analyze the applications requirements and to design a solution that integrates GE imaging equipment with non GE systems is the user's responsibility and should not be underestimated. The user is strongly advised to ensure that such an integration analysis is correctly performed. Validation - Testing the complete range of possible interactions between any GE device and non GE devices, before the connection is declared operational, should not be overlooked. Therefore, the user should ensure that any non GE provider accepts full responsibility for all validation required for their connection with GE devices. This includes the accuracy of the image data once it has crossed the interface between the GE imaging equipment and the non GE device and the stability of the image data for the intended applications. Such a validation is required before any clinical use (diagnosis and/or treatment) is performed. It applies when images acquired on GE imaging equipment are processed/displayed on a non- GE device, as well as when images acquired on non-ge equipment is processed/displayed on a GE console or workstation. Future Evolution - GE understands that the DICOM Standard will evolve to meet the user's growing requirements. GE is actively involved in the development of the DICOM v3.0 Standard. DICOM v3.0 will incorporate new features and technologies and GE may follow the evolution of the Standard. The GEMS protocol is based on DICOM v3.0 as specified in each DICOM Conformance Statement. Evolution of the Standard may require changes to devices which have implemented DICOM v3.0. In addition, GE reserves the right to discontinue or make changes to the support of communications features (on its products) reflected on by these DICOM Conformance Statements. The user should ensure that any non GE provider, which connects with GE devices, also plans for the future evolution of the DICOM Standard. Failure to do so will likely result in the loss of function and/or connectivity as the DICOM Standard changes and GE Products are enhanced to support these changes. 1 5

13 GE MEDICAL SYSTEMS Interaction - It is the sole responsibility of the non GE provider to ensure that communication with the interfaced equipment does not cause degradation of GE imaging equipment performance and/or function. 1.6 REFERENCES A list of references which is applicable to all GEMS Conformance Statements is included in the Introduction to the Integrated DICOM/Network v3.0 (ID/Net v3.0) Conformance Statement, Direction: The information object implementation refers to DICOM PS 3.3 (Information Object Definition). 1.7 DEFINITIONS A set of definitions which is applicable to all GEMS Conformance Statements is included in the Introduction to the Integrated DICOM/Network v3.0 (ID/Net v3.0) Conformance Statement, Direction: SYMBOLS AND ABBREVIATIONS A list of symbols and abbreviations which is applicable to all GEMS Conformance Statements is included in the Introduction to the Integrated DICOM/Network v3.0 (ID/Net v3.0) Conformance Statement, Direction:

14 2. NETWORK 2.1 INTRODUCTION This section of the DICOM Conformance Statement specifies the compliance to DICOM conformance requirements for the relevant Networking features on this GEMS product. Note that the format of this section strictly follows the format defined in DICOM Standard PS 3.2 (Conformance). Please refer to that part of the standard while reading this section. The details of the DICOM conformance related to other Information Objects and Information Models supported by the product are included in subsequent sections of this DICOM Conformance Statement. Precision 500D is an Integrated Radiography & Fluoroscopy Imaging System: It uses DICOM services to export/import images to/from remote workstations and archives. It uses DICOM Storage Commitment service to transfer ownership of images to a remote workstation supporting storage commitment such as an archive system. It allows a user to query for and display DICOM Modality worklist information from a remote hospital or radiology department information system computer. For example, a user may wish to query for all procedures scheduled to be performed on the system. In this situation, Precision 500D is providing the DICOM Modality Worklist SOP Class service as a service class user (SCU). 2.2 IMPLEMENTATION MODEL Application Data Flow Diagram The Basic and Specific Application models for this device are shown in the following Illustration : 2-1

15 Modality Worklist Request Manual or Automatic Transfer of Studies Manual Query/Retrieve Association Initiation DICOM SERVER AE Association Acceptance Remote Worklist SCP Image Stored Remotely Image Sent Remotely Storage Commitment Study flagged as Committed in local Database DICOM Print of Images Verification (C-Echo) Query/Retrieve SCP Images Committed Remotely DICOM Print SCP Verification (C-Echo) DICOM Standard Interface Functional Definition of AE's DICOM Server AE: The DICOM Server Application Entity (AE) is an application which handles DICOM protocol communication. DICOM SERVER AE is automatically brought up when the Precision 500D system is powered on. All remote DICOM AE s must be manually configured on the Precision 500D by an operator or field engineer. 2-2

16 GE MEDICAL SYSTEMS The declaration of remote DICOM AE s is done through the Service User Interface (SUIF). The DICOM SERVER AE is invoked by the following Real World Activities: I. Manual Transfer of Patients/Studies from the Precision 500D system to a Remote Host. For this operation, the operator selects patient/studies on the Patient List and then selects the device(s) to send to using the drop down list of stations (maximum of two at once). The user then presses the Send Study button on the Patient List screen to initiate the transfer. II. Automatic Transfer of Patients/Studies from the Precision 500D system to a Remote Host. For this operation, the transfer of images is triggered automatically. When Auto-Send is Enabled, all images generated during an acquisition session are automatically sent to the defined auto-push remote host(s) (maximum of 2) when the user closes the exam. The enabling of the Auto-Send is done from the acquisition screen on the IUI by checking the Auto-send check box. The default state of the Auto-send (On/Off) can be set in the User Preference tab. III. Images Sent Remotely from a Remote DICOM AE to Precision 500D system. When images are installed in the local database, they are displayed in the Precision 500D Patient List screen. Only images created on a Precision 500D system will be viewable on the Precision 500D system. IV. Manual Query/Retrieve For this operation, the operator presses the Query/Retrieve button on the Patient List screen then selects the station to query from the drop-down list and presses the Perform Query button. The Precision 500D system then queries a remote database to obtain a list of Patient/Studies available on that Remote Host. To retrieve a Patient/Study the user selects the patient from the list and presses the Retrieve Patient Button. The patient is then transferred into the local patient database and is displayed on the Patient List screen. V. Worklist Query For this operation, the operator needs to press the Worklist button on the IUI. The Digital will transition to the Worklist screen and perform the default query. The user can then select the exam from the worklist and start the exam by pressing Start Exam button on IUI. The Worklist Query criteria are defined in the configuration of the system. VI. Storage Commitment For this operation, the operator performs a Manual or Automatic transfer of images to a Storage SCP. Once images are sent a Storage Commitment Request is automatically queued and sent after a short delay. 2-3

17 2.2.3 Sequencing of Real-World Activities DICOM Server AE: Worklist Query: I. The user presses the Worklist button on the IUI and the digital transitions to the worklist screen and automatically queries for a worklist with a default query. II. III. IV. The modality worklist SCP returns responses which match the query parameters. The worklist patients are displayed to the user in the Worklist screen on the system. The user selects the exam to perform and presses the Start Exam button on the IUI. V. MPPS information is sent to the Worklist provider with status information (see Section 13). Note: The worklist can be manual queried once in the worklist screen by pressing one of the three default presets along with any parameters entered (Patient Name, Accession Number, etc.). Automatic Transfer of Patients/Studies: I. Service configures the devices to automatically send images to (maximum of 2 devices). II. III. IV. User Starts an exam. User Acquires images. User verifies the Auto-send checkbox is checked. (Default state can be set to On/Off in User Preferences). V. User presses Close button and MPPS information is sent (see Section 13). VI. Manual Query/Retrieve: Images acquired for the study/exam are automatically sent to the remote host. I. The user presses the Query/Retrieve button on the Patient List screen. II. III. IV. Manual Send of Images: The user selects the Query criteria and presses the Perform Query button. The user selects the patient to retrieve and presses the Retrieve Patient button. The images are retrieved and put into the local database and the Patient List is updated with the patient/study. I. The user selects the patients to transfer from the Patient List screen and then selects the destinations to transfer to using the drop down list of destinations. II. Storage Commitment: The user then presses the Send Selected Studies button to transfer to the Remote DICOM Storage SCP. 2-4

18 GE MEDICAL SYSTEMS If the selected device the user has sent an exam/study too is configured for Storage Commitment the following happens after an automatic or manual image send: I. Once the exam/study has been successfully sent the system queues a Storage Commitment request to be sent after a delay. II. III. After the delay the Storage Commitment for the transferred images is sent to the Storage SCP. If the Storage Commitment is successful the study is marked as committed on the Patient List screen. 2.3 AE SPECIFICATIONS DICOM Server AE Specification This Application Entity provides Standard Conformance to the following DICOM V3.0 SOP Classes as an SCU: SOP Class Name SOP Class UID Secondary Capture Image Storage X-Ray Angiographic Image Storage X-Ray Radiofluoroscopic Image Storage Patient Root Query/Retrieve Information Model - FIND Patient Root Query/Retrieve Information Model - MOVE Study Root Query/Retrieve Information Model - FIND Study Root Query/Retrieve Information Model - MOVE Patient/Study Only Query/Retrieve Information Model - FIND Patient/Study Only Query/Retrieve Information Model - MOVE Modality Worklist Information Model - FIND Storage Commitment Push Model Verification SOP Class This Application Entity provides Standard Conformance to the following DICOM V3.0 SOP Classes as an SCP : SOP Class Name SOP Class UID X-Ray Angiographic Image Storage X-Ray Radiofluoroscopic Image Storage

19 Secondary Capture Image Storage Verification SOP Class Association Establishment Policies General The DICOM Application Context Name (ACN), which is always proposed, is: Application Context Name The Maximum Length PDU negotiation is included in all association establishment requests. The maximum length PDU for an association initiated by the DICOM Server AE is: Maximum Length PDU No Limitation for Maximum PDU Size The SOP Class Extended Negotiation is not supported. SOP Class Extended Negotiation shall NOT be supported for Storage Commitment associations The user information Items sent by this product are : Maximum PDU Length Implementation UID Implementation Version Name Number of Associations The DICOM Server AE can support a maximum of 32 simultaneous associations Asynchronous Nature Asynchronous mode is not supported. All operations will be performed synchronously. DICOM Server AE allows a single outstanding operation on any association. Therefore, DICOM Server AE does not support asynchronous operations window negotiation, other than the default as specified by the DICOM specification. 2-6

20 Implementation Identifying Information The Implementation UID for this DICOM v3.0 Implementation is: Precision 500D Implementation UID The Implementation Version Name for this DICOM v3.0 Implementation is: PRECISION_500_D Association Initiation Policy Real-World Activity: Manual Transfer of Patients/Studies Associated Real-World Activity The operator does the following: This will cause: I. Select from the Patient List screen the Patients/Studies to be sent. Selects the Destinations to send to from the two drop down lists of Storage SCP s and presses the Send Selected Studies button. II. III. IV. The Precision 500D to retrieve the Patients/Studies from the local database and convert them to DICOM images. The DICOM Server AE will initiate a DICOM association, negotiate with the Remote DICOM Storage SCP an appropriate Transfer Syntax. Send the images if the negotiation is successful Proposed Presentation Context Table Presentation Context Table - Proposed Abstract Syntax Transfer Syntax Role Extended Name UID Name List UID List Negotiation Secondary Capture Image Storage X-Ray Angiographic Image Storage Implicit VR Little Endian Explicit VR Little Endian Explicit VR Big Endian JPEG Lossless Hierarch., First-order prediction Implicit VR Little Endian SCU None SCP None 2-7

21 X-Ray Radiofluoroscopic Image Storage Explicit VR Little Endian Explicit VR Big Endian JPEG Lossless Hierarch., First-order prediction Implicit VR Little Endian Explicit VR Little Endian Explicit VR Big Endian JPEG Lossless Hierarch., First-order prediction SCU None SOP Specific DICOM Conformance Statement for all Storage SOP Classes Following are the status codes that are more specifically processed when receiving messages from a Storage SCP equipment : Service Status Status Codes Further Meaning Application Behavior When receiving Status Codes Related Fields Processed if received Refused A7xx Out of resources Association is closed with Remote AE. Error is logged. Job status is set to retry SOP Class not Supported Association is closed with Remote AE. Error is logged. Job status is set to retry. Error Cxxx Cannot Understand Association is closed with Remote AE. A9xx Data Set does not match SOP Class Error is logged. Job status is set to retry. Association is closed with Remote AE. Error is logged. Job status is set to retry. Warning B000 Coercion of Data Elements Association is closed with Remote AE. Error is logged. Job status is set to retry. (0000,0902) (0000,0902) (0000,0901) (0000,0902) (0000,0901) (0000,0902) (0000,0901) (0000,0902) B007 Data Set does not match SOP Class Association is closed with Remote AE. Error is logged. Job status is set to retry. (0000,0901) (0000,0902) B006 Elements Discarded Association is closed with Remote AE. Error is logged. Job status is set to retry. (0000,0901) (0000,0902) Success 0000 None 2-8

22 Real-World Activity Automatic Transfer of Patients/Studies Associated Real-World Activity The operator does the following: I. Open a patient for an exam. II. III. Acquire series/images for the patient. Verify the Auto-send checkbox is checked and closes the study. This will cause: IV. The Precision 500D to retrieve the Patients/Studies from the local database and convert them to DICOM images. V. The DICOM Server AE will initiate a DICOM association, negotiate with the Remote DICOM Storage SCP(s) (maximum of 2 for autosend) an appropriate Transfer Syntax. VI. Send the images if the negotiation is successful Proposed Presentation Context Table Same as Real World Activity Manual Transfer of Patients/Studies SOP Specific DICOM Conformance Statement for all Storage SOP Classes Same as Real World Activity Manual Transfer of Patients/Studies Real-World Activity Manual Query/Retrieve Associated Real-World Activity The operator does the following: I. Presses the Query/Retrieve button on the patient list screen. II. III. Selects the query criteria and presses the Perform Query button. Selects the patient to retrieve and presses the Retrieve Patient button. This will cause: IV. The DICOM Server AE to initiate a DICOM association. V. The DICOM Server AE to emit a C-FIND request to get a list of patients meeting the query criteria. 2-9

23 VI. The DICOM Server AE to emit a C-MOVE request to retrieve the selected patient(s). Note: When the retrieved patients are viewed, some fields are displayed differently than during normal review of a non-retrieved study on the system Date and Time are displayed in DICOM Format, and FPS is displayed on single-shot images with no value Proposed Presentation Context Table Presentation Context Table - Proposed Abstract Syntax Transfer Syntax Role Extended Name UID Name List UID List Negotiation Patient Root Query/Retrieve Information Model - FIND Patient Root Query/Retrieve Information Model - MOVE Study Root Query/Retrieve Information Model - FIND Study Root Query/Retrieve Information Model - MOVE Patient/Study Only Query/Retrieve Information Model - FIND Patient/Study Only Query/Retrieve Information Model - MOVE Implicit VR Little Endian SCU None Implicit VR Little Endian SCU None Implicit VR Little Endian SCU None Implicit VR Little Endian SCU None Implicit VR Little Endian SCU None Implicit VR Little Endian SCU None SOP Specific DICOM Conformance Statement for the Patient Root Query/Retrieve Information Model - FIND, Study Root Query/Retrieve Information Model - FIND and Patient/Study Only Query/Retrieve Information Model - FIND SOP Classes Following are the status codes that are more specifically processed when receiving messages from a Query SCP equipment : Service Status Status Codes Further Meaning Application Behavior When receiving Status Codes Related Fields Processed if received Refused A700 Out of resources Association is closed. Job set to Retry status SOP Class not Supported Association is closed. Failed A900 Identifier does not match SOP Class Error logged in log file. (0000,0902) (0000,0902) Association is closed. (0000,0901) ( ) 2-10

24 GE MEDICAL SYSTEMS Class Job set to Retry status. (0000,0902) Cxxx Unable to process Association is closed. Job set to Retry status. (0000,0901) (0000,0902) Cancel FE00 Matching terminated due to cancel Success 0000 Matching is complete - No final identifier is supplied Pending FF00 Matches are continuing - Current Match is supplied and any Optional Keys were supported in the same manner as Required Keys. FF01 Matches are continuing - Warning that one or more Optional Keys were not supported for existence and/or matching for this Identifier Association is closed. Error logged to log file. None None Identifier Identifier SOP Specific DICOM Conformance Statement for the Patient Root Query/Retrieve Information Model - MOVE, Study Root Query/Retrieve Information Model - MOVE and Patient/Study Only Query/Retrieve Information Model - MOVE SOP Classes Following are the status codes that are more specifically processed when receiving messages from a Retrieve SCP equipment : Service Status Status Codes Further Meaning Application Behavior When receiving Status Codes Related Fields Processed if received Refused A701 Out of resources - Unable to calculate number of matches Association is closed. Job set to Retry status. (0000,0902) A702 Out of resources - Unable to perform sub-operations Association is closed. Job set to Retry status. (0000,1021) (0000,1022) (0000,1023) A801 Move Destination Unknown Association is closed. Job set to Retry status SOP Class not Supported Association is closed. Job set to Retry status. (0000,0902) (0000,0902) Failed A900 Identifier does not match SOP Class Association is closed. (0000,0901) (0000,0902) 2-11

25 Job set to Retry status. Cxxx Unable to process Association is closed. Job set to Retry status. (0000,0901) (0000,0902) Cancel FE00 Sub-operations terminated due to a Cancel indication Association is closed. Error logged to log file. (0000,1020) (0000,1021) (0000,1022) (0000,1023) Warning B000 Sub-operations Complete - One or more Failures. Success 0000 Sub-operations Complete - No Failure. Error logged to log file. (0000,1021) (0000,1022) (0000,1023) (0000,1021) (0000,1022) (0000,1023) Pending FF00 Sub-operations are continuing - (0000,1020) (0000,1021) (0000,1022) (0000,1023) Real-World Activity Worklist Query Associated Real-World Activity The operator does the following: I. Presses the Worklist button on the IUI. II. III. The system automatically queries the Worklist Provider to obtain a Worklist with the default query constraints. User selects the Scheduled Procedure Step to acquire images for and presses Start Exam. This will cause: IV. The DICOM Server AE to initiate a DICOM association. V. The DICOM Server AE to emit a C-FIND request to get a list of patients meeting the query criteria. Note: For more information on the details of the Modality Worklist Query please see Section Proposed Presentation Context Table 2-12

26 Presentation Context Table - Proposed Abstract Syntax Transfer Syntax Role Extended Name UID Name List UID List Negotiation Modality Worklist Information Model - FIND Implicit VR Little Endian SCU None SOP Specific DICOM Conformance Statement for the Modality Worklist Information Model - FIND SOP Class Following are the status codes that are more specifically processed when receiving messages from a Modality Worklist SCP equipment : Service Status Status Codes Further Meaning Application Behavior When receiving Status Codes Related Fields Processed if received Refused A700 Out of resources Association is closed. Error logged in log file SOP Class not Supported Association is closed. Failed A900 Identifier does not match SOP Class Error logged in log file. Association is closed. Error logged in log file. Cxxx Unable to process Association is closed. Error logged in log file. (0000,0902) (0000,0902) (0000,0901) (0000,0902) (0000,0901) (0000,0902) Cancel FE00 Matching terminated due to cancel Success 0000 Matching is complete - No final identifier is supplied Pending FF00 Matches are continuing - Current Match is supplied and any Optional Keys were supported in the same manner as Required Keys. FF01 Matches are continuing - Warning that one or more Optional Keys were not supported for existence for this Identifier Association is closed. None None Identifier Identifier 2-13

27 Real-World Activity Storage Commitment Associated Real-World Activity The operator does the following: I. Select from the Patient List screen the Patients/Studies to be sent. Selects the Destinations to send to from the two drop down lists of Storage SCP s and presses the Send Selected Studies button. II. Once the transfer is complete and the device is configured for Storage Commitment the Storage Commitment is sent. This will cause: III. IV. The DICOM Server AE will initiate a DICOM association, negotiate with the Remote DICOM Storage SCP an appropriate Transfer Syntax for the Storage Commitment. The DICOM Server AE emits a N-ACTION request. Only one N-ACTION Request is sent for all images to be committed Proposed Presentation Context Table Presentation Context Table - Proposed Abstract Syntax Transfer Syntax Role Extended Name UID Name List UID List Negotiation Storage Commitment Push Model Implicit VR Little Endian SCU None SOP Specific DICOM Conformance Statement for the Storage Commitment Push Model SOP Class If the association negotiation is not successful the DICOM Server AE retries the association 3 times (after a timeout period). After the 3 tries the job is set to Failure status in the Network Queue. After the N-ACTION request, if the received N-ACTION Response from the Storage Commitment Provider has a failure status, an error file is logged and the Storage Commitment is abandoned. After the N-ACTION request, if the received N-ACTION Response from the Storage Commitment Provider has a success status, the DICOM Server AE can receive the N-EVENT- REPORT from the Storage Commitment Provider at any time Service Class User Behavior N-ACTION N-ACTION is sent when the images are successfully sent to a remote host declared as Storage Commitment Provider on the Precision 500D. 2-14

28 GE MEDICAL SYSTEMS Storage Commitment can be requested for XA Image SOP Class and RF Image SOP Class. The Referenced Study Component Sequence Attribute is not supported. The transaction UID is applicable until we receive the N-EVENT-REPORT. Storage Media File-Set ID & UID Attributes in the N-ACTION are not supported. When receiving an unsuccessful N-ACTION Response Status Code from the SCP an error is logged in the log file, and the job is set to retry status Service Class User Behavior N-EVENT-REPORT When receiving the N-EVENT-REPORT, the system looks first for the SOP Instance UID successfully committed. It records them in a log file and flags them in the local database as Committed. The status of any of the studies can be seen by looking at the Status column on the Patient List Screen (C = Committed). Secondly, the system looks for the SOP Instance UID for which the commit failed and records them in the log file Real-World Activity Verification (C-Echo) SCU Associated Real-World Activity I. Enter the SUIF screens on the IUI. II. III. IV. Select Config button, and then select C-ECHO button. Select the DICOM Device to C-ECHO and press the Initiate C-ECHO button. Display is updated with status of the C-ECHO. Success or Failure is displayed to the user Accepted Presentation Context Table Presentation Context Table Abstract Syntax Transfer Syntax Role Extended Name UID Name List UID List Negotiation Verification SOP Class Implicit VR Little Endian SCU None SOP Specific DICOM Conformance Statement for all Verification SOP Classes Precision 500D provides standard Conformance to the DICOM Verification Service Class. 2-15

29 Association Acceptance Policy Real-World Activity Verification (C-ECHO) SCP Associated Real-World Activity I. A Remote DICOM Device initiates a C-ECHO. II. The DICOM Server AE negotiates a transfer syntax and responds to the C- ECHO request with the appropriate status Accepted Presentation Context Table Presentation Context Table - Accepted Abstract Syntax Transfer Syntax Role Extended Name UID Name List UID List Negotiation Verification SOP Class Implicit VR Little Endian SCP None SOP Specific DICOM Conformance Statement for all Verification SOP Classes Following are the status codes the Application may send back to the SCU Equipment after performing the requested: Service Status Status Codes Further Meaning Status Code sending explanation Related Fields sent back to the SCU Success 0000 Operation Performed properly. None Real-World Activity Image Install Associated Real-World Activity I. A Remote DICOM SCU requests image storage. II. III. Depending on if the station is configured to be able to send to the DICOM Server AE the DICOM Server AE accepts or rejects the association. If the association is accepted then the images are transmitted and stored in the Local Database Accepted Presentation Context Table 2-16

30 Presentation Context Table - Accepted Abstract Syntax Transfer Syntax Role Extended Name UID Name List UID List Negotiation X-Ray Radiofluoroscopic Image Storage Implicit VR Little Endian Explicit VR Little Endian Explicit VR Big Endian SCU Note 4 JPEG Lossless Hierarch., Firstorder prediction X-Ray Angiographic Image Storage Implicit VR Little Endian Explicit VR Little Endian SCP Note 4 Explicit VR Big Endian JPEG Lossless Hierarch., Firstorder prediction Secondary Capture Image Storage Implicit VR Little Endian Explicit VR Little Endian SCP None Explicit VR Big Endian JPEG Lossless Hierarch., Firstorder prediction NOTE 4 Storage Extended Negotiation is supported. DICOM Server AE negotiates with the following information : Field Name Value Description of Field Level of Support 2 Level 2 (FULL) SCP Level of Digital Signature Support 0 Unspecified Element Coercion 0 Does not coerce any Data Element SOP Specific DICOM Conformance Statement for all Storage SOP Classes Following are the status codes the Application may send back to the SCU Equipment after performing the requested Storage : Service Status Status Codes Further Meaning Status Code sending explanation Related Fields sent back to the SCU Refused A700 Out of resources Indicates that there was not enough storage space to store the image. Recovery from this condition is left to the administrative functions. (0000,0902) 2-17

31 Error C000 Failed The operation was not successful. (0000,0901) (0000,0902) C005 Unable to register object, study locked; no new objects allowed. Indicates that no new objects can be added to this study because it has been locked. (0000,0901) (0000,0902) C008 Cannot Understand Indicates that the Data Set cannot be parsed into elements. (0000,0901) (0000,0902) A900 Data Set does not match SOP Class Indicates that the data set does not encode an instance of the SOP Class specified. (0000,0901) (0000,0902) Warning B007 Data Set does not match SOP Class Indicates that the data Set does not match the SOP Class, but that the image was stored anyway. (0000,0901) (0000,0902) Success 0000 None Presentation Context Acceptance Criterion The DICOM Server AE will accept any number of Storage Presentation Contexts per association request. Any one Abstract Syntax may be specified more than once in an association request, if the Transfer Syntaxes differ between the Presentation Contexts SOP Specific DICOM Conformance Statement for the Storage Commitment Push Model SOP Class SCU Failure Reason The DICOM Server AE will only accept the SCU role (which must be proposed via SCP/SCU Role Selection Negotiation) within a Presentation Context for the Storage Commitment Push Model SOP Class. Upon receiving a Storage Commitment N-EVENT-REPORT (Storage Commitment Result), the DICOM Server AE will validate the Transaction UID against its list of outstanding Storage Commitment Request Transaction UIDs. If it matches an outstanding Request, the AE will mark all SOP Instances for which a success status is indicated with an Archived flag, shown on the patient list as C in the status column. If the Storage Commitment Result indicates any failure status the error will be written to the error log. Any retry is automatically reinitiated as a new Storage Commitment Request. The AE will process specific Failure Reason Codes as described in the table: Meaning Application Behavior When Receiving Reason Code 0110H Processing failure Error logged in log file and automatically set to retry status 0112H No such object instance Error logged in log file and automatically set to retry status 0213H Resource limitation Error logged in log file and automatically set to retry status 0122H Referenced SOP Class not supported Error logged in log file. 2-18

32 0119H Class / Instance conflict Error logged in log file and automatically set to retry status 0131H Duplicate transaction UID Error logged in log file. The AE always returns a Success Status 0000 to a Storage Commitment N-EVENT- REPORT. 2.4 COMMUNICATION PROFILES Supported Communication Stacks (PS 3.8, PS 3.9) DICOM Upper Layer (PS 3.8) is supported using TCP/IP OSI Stack OSI stack not supported Physical Media Support Not Applicable TCP/IP Stack The TCP/IP stack is inherited from the Operating System API Not applicable to this product Physical Media Support DICOM is indifferent to the Physical medium over which TCP/IP executes (e.g. Ethernet V2.0,IEEE 802.3, ATM, FDDI) Note: For more information about the Physical Media available on Precision 500D, please refer to the Product Data Sheet Point-to-Point Stack A 50-pin ACR-NEMA connection is not applicable to this product. 2.5 EXTENSIONS / SPECIALIZATIONS / PRIVATIZATIONS Standard Extended /Specialized/Private SOPs Not Supported. 2-19

33 2.5.2 Private Transfer Syntaxes Not Supported. 2.6 CONFIGURATION AE Title/Presentation Address Mapping DICOM Server AE: AE Title is user Configurable Configurable Parameters The following fields are configurable for this AE (local): Local AE Title Local IP Address Local Listening Port Number Local IP Netmask Default Router IP. Only one default router can be configure for all remote nodes. The following fields are configurable for every remote DICOM AE: Remote AE Title Remote IP Address Listening TCP/IP Port Number The following fields are configurable: Association Establishment Timer Maximum Length PDU 2.7 SUPPORT OF EXTENDED CHARACTER SETS The Precision 500D will support only the ISO_IR 100 (ISO :1987 Latin alphabet N 1. supplementary set) as extended character sets. Any incoming SOP instance that is encoded using another extended character set will not be installed in the local database. 2.8 CODES AND CONTROLLED TERMINOLOGY The product uses no coded terminology. 2-20

34 2.9 SECURITY PROFILES The product does not conform to any defined DICOM Security Profiles. It is assumed that the product is used within a secured environment. It is assumed that a secured environment includes at a minimum: 1. Firewall or router protections to ensure that only approved external hosts have network access to the product. 2. Firewall or router protections to ensure that the product only has network access to approved external hosts and services. 3. Any communications with external hosts and services outside the locally secured environment use appropriate secure network channels (such as a Virtual Private Network (VPN)) 2-21

35 3. MEDIA STORAGE 3.1 INTRODUCTION This section of the conformance statement (CS) specifies the Precision 500D compliance to DICOM Media Interchange. It details the DICOM Media Storage Application Profiles and roles which are supported by this product. This Station provides the capabilities to DICOM interchange on CD-R s (Compact Disc Recordable). The Precision 500D works with XA and XRF Image Types. Note that the format of this section strictly follows the format defined in DICOM Standard PS 3.2 (Conformance). Please refer to that part of the standard while reading this section. 3.2 IMPLEMENTATION MODEL Application Data Flow Diagram The Basic and Specific Application models for this device are shown in the following Illustration : ILLUSTRATION 3 1 SPECIFIC AE APPLICATION MODEL User requests archive on CD-R User Requests Media Browsing DICOM Media Server AE FSC FSR CD-R User Requests retrieve from CD-R I. Description of the data flow diagram for the CDROM device. 3-1

36 GE MEDICAL SYSTEMS The User selects patients from the patient list screen to be archived and press the Archive to CD button on the Digital Patient List Screen. The images are saved on a single session disk in a one shot operation. The user can request the reading of a DICOM file set written on a CD by selecting the CD Import from the Query/Retrieve screen. The user can restore the study/patient by selecting from the Query/Retrieve screen and press the Retrieve Patient button. Note: When archiving to a CD each unique patient must have a unique Patient ID. If the Patient ID is the same between two patients when browsing the CD, the patients will be listed under the same name. When the patients are retrieved the correct names, etc. will be retrieved for the patient Functional Definition of AE s The CD-R DICOM Media Server AE supports the following functions: I. Has access to patient demographics and pixel data in the local database. II. III. IV. Can generate a DICOM File Set (FSC) for XA or XRF Images in a one shot activity. Can read a DICOM File Set (FSR) on a CD. Can retrieve Patients/Studies from a CD Sequencing Requirements Not applicable File Meta Information Options (See PS3.10) The File Meta-Information for this implementation is : File Meta-Information Version 1 Precision 500D Implementation UID Implementation Version Name PRECISION_500_D 3.3 AE SPECIFICATIONS DICOM CD-R Server AE Specification The DICOM CD-R Server Application Entity provides standard conformance to DICOM Interchange Option of the Media Storage Service Class. The application Profiles and roles are listed below. Supported Application Profile Real World Activity Role Description STD-GEN-CD Archive FSC Interchange 3-2

37 GE MEDICAL SYSTEMS STD-GEN-CD Browse FSR Interchange STD-GEN-CD Retrieve FSR Interchange File Meta Information for the DICOM CD-R Server Application Entity Following are the values set in the File Meta Information for this AE Title : Source Application Entity Title MVF_ARCHIVE Real-World Activities for the DICOM CDR Server Application Entity Real-World Activity (RWA) Archive CD The CD-R DICOM Media Server acts as a FSC using the interchange option when requested to copy SOP Instances from the local database to the CD-R. The user has to insert a blank CD into the CD-R drive. Then, the user selects the Patients/Studies from the Patient List Screen that he wants the CD-R DICOM Media Server to copy onto the CD and presses the Archive to CD button. Before writing the CD, the DICOM Media Server checks for the following conditions: I. The inserted media is blank and writable. If the condition is not met, an error is displayed to the user and the CD is ejected. II. The number of images to archive is 300 or less. If the condition is not met, a prompt is displayed to the user that over 300 images are selected and the patients to be archived are automatically reduced to obtain 300 images or less. Once these checks are successful the CD-R writing process begins with the selected patients Media Storage Application Profile for the RWA Archive CD : For the list of Application Profiles that invoke this AE for the RWA Archive CD, see the Table in Section Archive CD AE Specification Options : Following are the SOP Classes supported by the RWA Archive CD: Information Object Definition SOP Class UID Transfer Syntax Transfer Syntax UID Media Storage Directory Storage Explicit VR Little Endian X-Ray Angiographic Image Storage Explicit VR Little Endian