Varian System Server. DICOM Conformance Statement

Transcription

1 Varian System Server DICOM Conformance Statement P/N VA8203D3CS March 2009

2 General Information Abstract This document provides information about the DICOM Conformance of the Varian System Server product family, i.e. ARIA, Eclipse and Acuity 8.2/8.6. Manufacturer and European Representative Manufacturer: Varian Medical Systems, Inc. Ltd Hansen Way, Bldg. 4A Palo Alto, CA , U.S.A. European Representative: Varian Medical Systems UK Ltd. Gatwick Road, Crawley West Sussex RH10 9RG United Kingdom Notice Trademarks Information in this document is subject to change without notice and does not represent a commitment on the part of Varian. Varian is not liable for errors contained in this document or for incidental or consequential damages in connection with the furnishing or use of this material. This document contains proprietary information protected by copyright. No part of this document may be reproduced, translated, or transmitted without the express written permission of Varian Medical Systems, Inc. ARIA, Varian, VMS are registered trademarks ARIA is trademark of Varian Medical Systems, Inc. Microsoft, Windows NT and Windows are registered trademarks of Microsoft Corporation. All other trademarks or registered trademark are the property of their respective owners. 2 of 398 Varian System Server DICOM Conformance Statement, VA8203D3CS

3 General Information Contacting Support Support services are available without charge during the initial warranty period. If you seek information not included in this publication, call Varian Medical Systems support at the following locations: United States and Canada telephone support United States and Canada Direct telephone support European telephone Support Fax (US) Fax (Service Europe) All other countries please call your local service office To contact the support location nearest you for Service, Parts or Support, see the list at the Varian Medical Systems website: Worldwide Listing Communicating Via the World Wide Web If you have access to the Internet, you will find Varian Medical System support at the following location: Oncology Systems If you have a Varian account, enter your username and password. Otherwise, first click create new account to get a username and password. From MyVarian home page, click Contact Us from the Support list along the left side of the window. If possible, please send all inquires through the my.varian.com web site at otherwise, use the following s addresses for support: Sending North America (North America support-americas@varian.com and Canada) Central & South America soporte.al@varian.com Europe (Europe, Middle East, support-emea@varian.com Africa) Australia (Australian, New support-anz@varian.com Zealand, Australasia) China / Asia (China, Asia) support-china@varian.com Japan support-japan@varian.com Brachy Therapy Systems brachyhelp@varian.com Copyright 2009 Varian Medical Systems Inc., Oncology Systems All rights reserved. Varian System Server DICOM Conformance Statement, VA8203D3CS 3 of 398

4 General Information Document History Mar 30, 2009 Updated to reflect changes in 8.2 & Jul 07, 2007 Initial Version for of 398 Varian System Server DICOM Conformance Statement, VA8203D3CS

5 Contents Contents Contents...5 List of Figures...9 List of Tables Introduction Audience Overview Remarks References Abbreviations Networking Implementation Model Application Data Flow Functional Definition of AE s Sequencing of Real World Activities AE Specifications RadOnc Client Application Entity File Daemon Application Entity DB Daemon Application Entity Network Interfaces Physical Network Interfaces Additional Protocols Configuration AE Title/Presentation Address Mapping Parameters Media Interchange Support of Character Sets Overview Display Behavior Security Security Profiles Association Level Security RadOnc Client File Daemon and DB Daemon Application Level Security RadOnc Client File Daemon and DB Daemon...69 Appendix A Specialization...71 A.1 IOD Contents...71 Varian System Server DICOM Conformance Statement, VA8203D3CS 5 of 398

6 Contents A.1.1 Created SOP Instances A.1.2 Usage of Attributes from received IOD s A.1.3 Attribute Mapping A.1.4 Coerced/Modified Fields A.2 Data Dictionary of Private Attributes A.2.1 Private Attributes used by all Application Entities A.2.2 Private Attributes used by DB Daemon Application Entity in Archive Service Mode A.3 Coded Terminology and Templates A.3.1 Context Groups A.3.2 Template Specifications A.3.3 Private Code Definitions A.4 Grayscale Image Consistency A.5 Standard Extended/Specialized/Private SOP Classes A.5.1 Standard Extended SOP Classes A.5.2 Standard Private SOP Classes A.6 Private Transfer Syntaxes Appendix B Object Matching Criteria...79 B.1 General Matching Criteria B.1.1 Manual Import using RadOnc Client Query/Retrieve SCU B.1.2 Manual Import of DICOM Media Files B.1.3 Automatic Import using DB Daemon Storage SCP B.2 IOD Specific Matching Criteria B.2.1 RT Plan and RT Ion Plan B.2.2 RT Beams Treatment Record and RT Ion Beams Treatment Record Appendix C IOD Details...84 C.1 Supported IODs C.1.1 Computed Radiography Image A C.1.2 Computed Tomography Image A C.1.3 Magnetic Resonance Image A C.1.4 Ultrasound Image A C.1.5 Secondary Capture Image A C.1.6 X-Ray Angiographic Image A C.1.7 RT Image A C.1.8 RT Dose A C.1.9 RT Structure Set A C.1.10 RT Plan A C.1.11 Positron Emission Tomography Image A C.1.12 RT Beams Treatment Record A C.1.13 RT Treatment Summary Record A C.1.14 Spatial Registration A C.1.15 RT Ion Plan A C.1.16 RT Ion Beams Treatment Record A C.1.17 Tracking Protocol (Private) C.1.18 Tracking Waveform (Private) of 398 Varian System Server DICOM Conformance Statement, VA8203D3CS

7 Contents C.2 Modules and Attributes...99 C.2.1 Patient C C.2.2 General Study - C C.2.3 General Series C C.2.4 Frame of Reference C C.2.5 General Equipment C C.2.6 General Image C C.2.7 Image Plane C C.2.8 Image Pixel C C.2.9 Contrast/Bolus C C.2.10 Cine C C.2.11 Multi-Frame C C.2.12 CR Series C C.2.13 CR Image C C.2.14 CT Image C C.2.15 MR Image C C.2.16 SC Equipment C C.2.17 SC Image C C.2.18 X-Ray Image C C.2.19 RT Series C C.2.20 RT Image C C.2.21 RT Dose C C.2.22 RT DVH C C.2.23 Structure Set C C.2.24 ROI Contour C C.2.25 RT ROI Observations C C.2.26 RT General Plan C C.2.27 RT Prescription C C.2.28 RT Tolerance Tables C C.2.29 RT Patient Setup C C.2.30 RT Fraction Scheme C C.2.31 RT Beams C C.2.32 RT Brachy Application Setups C C.2.33 Approval C C.2.34 RT General Treatment Record C C.2.35 RT Treatment Machine Record C C.2.36 RT Beams Session Record C C.2.37 RT Treatment Summary Record C C.2.38 RT Ion Tolerance Tables C C.2.39 RT Ion Beams C C.2.40 RT Ion Beams Session Record C C.2.41 PET Series C C.2.42 PET Image C C.2.43 Curve C C.2.44 Waveform Identification C Varian System Server DICOM Conformance Statement, VA8203D3CS 7 of 398

8 Contents C.2.45 Waveform C C.2.46 Modality LUT C C.2.47 VOI LUT C C.2.48 SOP Common C C.2.49 Common Instance Reference C C.2.50 Spatial Registration Series C C.2.51 Spatial Registration C C.2.52 Extended Interface Private C.2.53 Tolerance Private C.2.54 Tracking Protocol Private C.2.55 Tracking Protocol Series Private C.2.56 Tracking Waveform Series Private Appendix D Extended Interface D.1 RT Plan / RT Ion Plan D.2 RT Beams Treatment Record of 398 Varian System Server DICOM Conformance Statement, VA8203D3CS

9 List of Figures List of Figures Figure 2-1: SCU Role Application Data Flow Diagram...18 Figure 2-2: SCP Role Application Data Flow Diagram...19 Figure 2-3: Sequencing of Activities RadOnc Client Query/Retrieve...27 Figure 2-4: Sequencing of Activities RadOnc Client Print Images...36 Figure 2-5: Sequencing of Activities DB Daemon Handling Query Requests...55 Figure 2-6: Sequencing of Activities DB Daemon Handling Retrieval Requests...56 List of Tables Table 1-1: Network Services...14 Table 1-2: Media File SOP Classes...15 Table 2-1: SOP Classes for RadOnc Client Application Entity...22 Table 2-2: DICOM Application Context for RadOnc Client Application Entity...23 Table 2-3: Number of Associations initiated for RadOnc Client Application Entity...23 Table 2-4: DICOM Implementation Class and Version for RadOnc Client Application Entity...23 Table 2-5: Object Categories used by RadOnc Client Storage SCU Application Entity...24 Table 2-6: Proposed Presentation Contexts for RadOnc Client Storage SCU Application Entity...25 Table 2-7: RadOnc Client C-STORE Response Status Handling Behavior...25 Table 2-8: RadOnc Client Storage SCU Communication Failure Behavior...26 Table 2-9: Proposed Presentation Contexts for RadOnc Client Q/R SCU Application Entity...28 Table 2-10: RadOnc Client C-FIND Response Status Handling Behavior...29 Table 2-11: RadOnc Client Q/R C-FIND SCU Communication Failure Behavior...30 Table 2-12: Study Root Request Identifier for RadOnc Client Q/R C-FIND SCU...31 Table 2-13: RadOnc Client C-MOVE Response Status Handling Behavior...32 Table 2-14: RadOnc Client Q/R C-MOVE SCU Communication Failure Behavior...33 Table 2-15: Study Root Request Identifier for RadOnc Client Q/R C-MOVE SCU...33 Table 2-16: Acceptable Presentation Contexts for RadOnc Client Temporary Storage SCP Application Entity and Receive Storage Request...33 Table 2-17: Response Status of RadOnc Client Temporary Storage SCP and Receive Storage Request...34 Table 2-18: Proposed Presentation Contexts for RadOnc Client Print SCU Application Entity...37 Table 2-19: Printer SOP Class N-EVENT-REPORT Behavior...38 Table 2-20: Basic Film Session SOP Class N-CREATE Request Attributes...38 Table 2-21: Basic Film Session SOP Class N-CREATE Response Status Handling Behavior...39 Table 2-22: Basic Film Session SOP Class N-DELETE Response Status Handling Behavior...39 Varian System Server DICOM Conformance Statement, VA8203D3CS 9 of 398

10 List of Tables Table 2-23: Basic Film Session SOP Class N-ACTION Response Status Handling Behavior Table 2-24: Basic Film Box Session SOP Class N-CREATE Request Attributes Table 2-25: Basic Film Box SOP Class N-CREATE Response Status Handling Behavior Table 2-26: Basic Film Box SOP Class N-DELETE Response Status Handling Behavior Table 2-27: Basic Film Box SOP Class N-ACTION Response Status Handling Behavior Table 2-28: Basic Grayscale Image Box SOP Class N-SET Request Attributes Table 2-29: Basic Grayscale Image Box SOP Class N-SET Response Status Handling Behavior Table 2-30: SOP Classes for File Daemon Application Entity Table 2-31: DICOM Application Context for File Daemon Application Entity Table 2-32: Number of Associations accepted for File Daemon Application Entity Table 2-33: DICOM Implementation Class and Version for File Daemon Application Entity Table 2-34: DICOM Implementation Class and Version for Media Files Table 2-35: Acceptable Presentation Contexts for File Daemon Application Entity and Receive Storage Request Table 2-36: Response Status of File Daemon Storage SCP and Receive Storage Request Table 2-37: SOP Classes for DB Daemon Application Entity Table 2-38: DICOM Application Context for DB Daemon Application Entity Table 2-39: Number of Associations accepted for DB Daemon Application Entity Table 2-40: DICOM Implementation Class and Version for DB Daemon Application Entity Table 2-41: Acceptable Presentation Contexts for DB Daemon Application Entity and Receive Storage Request Table 2-42: Response Status of DB Daemon Storage SCP and Receive Storage Request Table 2-43: Portal Dose Image Type Values and their Meaning Table 2-44: Acceptable Presentation Contexts for DB Daemon Application Entity and Query/Retrieve Table 2-45: Study Root C-FIND SCP Supported Elements for DB Daemon Table 2-46: Response Status of DB Daemon Storage SCP and Receive Query Request Table 2-47: Response Status of DB Daemon Storage SCP and Receive Retrieval Request Table 2-48: AE Title Configuration Table Table 2-49: Configuration Parameters Table 3-1: Transfer Syntaxes used in DICOM Media Files Table A-1: Coerced/Modified Fields Table A-2: Private Creator Identification Strings Table A-3: Private Attributes used in all Application Entities Table A-4: Private Attributes used by DB Daemon Application Entity in Archive Service Mode Table A-5: Standard Attributes added to CT Image Module Table A-6: LTArchive RT Treatment Record Storage SOP Class Table A-7: Tracking Protocol Storage SOP Class Table A-8: Tracking Protocol Storage SOP Class of 398 Varian System Server DICOM Conformance Statement, VA8203D3CS

11 List of Tables Table B-1: Patient Matching Criteria for Storage SCP of RadOnc Client Q/R SCU...80 Table B-2: Patient Matching Criteria for DB Daemon Storage SCP...80 Table B-3: RT Plan and RT Ion Plan Component Matching...82 Table B-4: RT Plan and RT Ion Plan Component Matching...83 Table C-1: Computed Radiography Image IOD Modules Support...85 Table C-2: Computed Tomography Image IOD Modules Support...85 Table C-3: Magnetic Resonance Image IOD Modules Support...86 Table C-4: Ultrasound Image IOD Modules Support...87 Table C-5: Secondary Capture Image IOD Modules Support...87 Table C-6: X-Ray Angiographic Image IOD Modules Support...88 Table C-7: RT Image IOD Modules Support...89 Table C-8: RT Dose IOD Modules Support...90 Table C-9: RT Structure Set IOD Modules Support...90 Table C-10: RT Plan IOD Modules Support...91 Table C-11: Positron Emission Tomography Image IOD Modules Support...92 Table C-12: RT Beams Treatment Record IOD Modules Support...93 Table C-13: RT Treatment Summary Record IOD Modules Support...93 Table C-14: Spatial Registration Image IOD Modules Support...94 Table C-15: RT Ion Plan IOD Modules Support...94 Table C-16: RT Ion Beams Treatment Record IOD Modules Support...95 Table C-17: Tracking Protocol IOD Modules Support...96 Table C-18: Tracking Waveform IOD Modules Support...97 Table D-1: RT Plan / RT Ion Plan Extended Interface XML Structure Table D-2: RT Beams Treatment Record Extended Interface XML Structure Varian System Server DICOM Conformance Statement, VA8203D3CS 11 of 398

12 List of Tables (This page is intentionally left blank.) 12 of 398 Varian System Server DICOM Conformance Statement, VA8203D3CS

13 Introduction 1. Introduction 1.1 Audience This document is intended for the following groups of persons: Customers and hospital staff who want to use DICOM with Varian System Server applications System integrators of medical equipment Other vendors offering interfacing via DICOM Marketing and sales persons It is assumed, that the reader is familiar with the DICOM standard. The document is structured along the template definition as specified in Part 2 of the DICOM standard. 1.2 Overview The Varian System Server product family is a comprehensive suite of integrated applications which cover all aspects of radiotherapy. This includes especially treatment planning, virtual simulation, simulation, electronic chart and treatment review. To support those functions the following DICOM services for receiving and sending diagnostic imaging modalities as well as all radiotherapy objects are supported by all applications of this product family. Table 1-1 lists network services supported by the Varian System Server product family. SOP Classes User of Service (SCU) Provider of Service (SCP) Transfer Computed Radiography Image Storage Option (see Note 1) Option (see Note 4) CT Image Storage Option (see Note 1) Option (see Note 4) MR Image Storage Option (see Note 1) Option (see Note 4) Ultrasound Image Storage No Option (see Note 4) Secondary Capture Image Storage Option (see Note 1) Option (see Note 4) X-Ray Angiographic Image Storage No Option (see Note 4) Spatial Registration Storage No Option (see Note 4) Positron Emission Tomography Image Storage No Option (see Note 4) RT Image Storage Option (see Note 1) Option (see Note 4) RT Dose Storage Option (see Note 1) Option (see Note 4) RT Structure Set Storage Option (see Note 1) Option (see Note 4) RT Beams Treatment Record Storage Option (see Note 1) Option (see Note 4) Varian System Server DICOM Conformance Statement, VA8203D3CS 13 of 398

14 Introduction SOP Classes User of Service (SCU) Provider of Service (SCP) LTArchive RT Treatment Record Storage Option (see Note 6) Option (see Note 6) RT Plan Storage Option (see Note 1) Option (see Note 4) RT Treatment Summary Record Storage Option (see Note 5) RT ION Plan Storage Option (see Note 1) Option (see Note 4) RT Ion Beams Treatment Record Storage No Option (see Note 1) Option (see Note 4) Tracking Protocol (Private) Option (see Note 1) Option (see Note 4) Tracking Waveform (Private) Option (see Note 1) Option (see Note 4) Query/Retrieve Study Root Query/Retrieve Information Model FIND Study Root Query/Retrieve Information Model MOVE Option (see Note 2) Option (see Note 5) Option (see Note 2) Option (see Note 5) Print Management Basic Grayscale Print Management Meta SOP Class Table 1-1: Network Services Option (see Note 3) No Table 1-2 lists Media File SOP Classes supported for file based export and import by. SOP Classes DICOM Media File Export DICOM Media File Import Computed Radiography Image Storage Option (see Note 7) Option (see Note 8) CT Image Storage Option (see Note 7) Option (see Note 8) MR Image Storage Option (see Note 7) Option (see Note 8) Ultrasound Image Storage No Option (see Note 8) Secondary Capture Image Storage Option (see Note 7) Option (see Note 8) X-Ray Angiographic Image Storage No Option (see Note 8) Spatial Registration Storage Option (see Note 7) Option (see Note 8) Positron Emission Tomography Image Storage No Option (see Note 8) RT Image Storage Option (see Note 7) Option (see Note 8) RT Dose Storage Option (see Note 7) Option (see Note 8) RT Structure Set Storage Option (see Note 7) Option (see Note 8) RT Beams Treatment Record Storage Option (see Note 7) Option (see Note 8) 14 of 398 Varian System Server DICOM Conformance Statement, VA8203D3CS

15 Introduction SOP Classes DICOM Media File Export DICOM Media File Import RT Plan Storage Option (see Note 7) Option (see Note 8) RT Treatment Summary Record Storage Option (see Note 7) Option (see Note 8) RT Ion Plan Storage Option (see Note 7) Option (see Note 8) RT Ion Beams Treatment Record Storage Tracking Protocol (Private) Tracking Waveform (Private) Table 1-2: Media File SOP Classes Option (see Note 7) Option (see Note 8) Note 1 Note 2 Note 3 Note 4 Note 5 Note 6 Note 7 Note 8 Requires Storage SCU Export Filter and associated licenses or DB Daemon configured as Query/Retrieve SCP. Requires Query/Retrieve Import Filter and associated licenses. Requires DICOM printer configuration set up. Requires DB Daemon or File Daemon that is configured as Storage SCP. Requires DB Daemon that is configured as Query/Retrieve SCP. Requires DB Daemon that is configured for Archive Service Mode (Varian proprietary) Requires DICOM Media File Export Filter. Requires DICOM Media File Import Filter. The following products are in the scope of this Conformance Statement: RadOnc Client (including ARIA and Eclipse) DB Daemon File Daemon The Varian System Server product family runs on Microsoft Windows 2000, Windows XP, Windows Server 200 and Windows Server 2003 platforms. 1.3 Remarks The scope of this Conformance Statement is to facilitate communication with Varian System Server applications and other vendor s medical equipment. The Conformance Statement should be read and understood in conjunction with the DICOM standard [1]. The DICOM standard in the current version evolved in 1993 with DICOM 3.0. The definition of DICOM standard for radiotherapy data started in 1994 and has now reached a productive state. Nowadays DICOM is the primary choice for exchanging data with an open standard protocol for the majority of vendors and institutions. Varian Medical Systems is committed to this notion of standard-based cross-vendor interoperability as well as making use of the DICOM protocol among its own products. Varian System Server DICOM Conformance Statement, VA8203D3CS 15 of 398

16 Introduction DICOM, by itself, does not guarantee interoperability. However, the Conformance Statement facilitates a first-level validation for interoperability between different applications supporting the same DICOM functionality. This Conformance Statement is not intended to replace validation with other DICOM equipment to ensure proper exchange of information intended. Because the DICOM standard is subject to ongoing changes, enhancements and improvements, Varian Medical Systems reserves the right to advance their products by making use of upcoming DICOM features without prior announcement. 1.4 References [1] Digital Imaging and Communications in Medicine (DICOM), Parts 1-18 (2008) National Electrical Manufacturers Association (NEMA) Rosslyn, VA United States of America 1.5 Abbreviations This section provides the definitions of terms, acronyms, and abbreviations which are used throughout the document. An arrow sign ( ) left of a word indicates that it can be looked up in this table. AE ALWAYS ANAP Daemon DB DICOM DIMSE DNS EMPTY IE IOD Management System Multi-frame Image NEMA PDU RadOnc SCU SCP SOP Application Entity ( DICOM term) Attribute Always Present with a value Attribute Not Always Present Collective term for Windows services accepting DICOM Associations Database Digital Imaging and Communications in Medicine, a standard on image communications in medical applications DICOM Message Service element Domain Name System Attribute is sent without a value Information Entity Information Object Definition ( DICOM term) Collective term including Daemon and RadOnc Client Image that contains multiple two-dimensional pixel planes National Electrical Manufacturers Association Protocol Data Unit ( DICOM term) Radiation Oncology Client Applications, including Eclipse Service Class User ( DICOM term) Service Class Provider ( DICOM term) Service-Object-Pair, a definition of an information object (like an image) and of a service (like storage) that can be performed for the object ( DICOM term) 16 of 398 Varian System Server DICOM Conformance Statement, VA8203D3CS

17 Introduction TCP/IP UID VNAP VR Transmission Control Protocol / Internet Protocol, a widely used computer networking protocol Unique Identifier used to identify an object by a worldwide unique identifier ( DICOM term) Value Not Always Present (attribute sent zero length if no value is present) Value Representation, a data encoding method in DICOM Varian System Server DICOM Conformance Statement, VA8203D3CS 17 of 398

18 Networking 2. Networking 2.1 Implementation Model Application Data Flow Export object Storage SCU (RadOnc Client) Remote Store SCP receives object Search and Retrieve object Query/Retrieve SCU (RadOnc Client) Remote Q/R SCP receives Query or Retrieve command Import object Temporary Storage SCP (RadOnc Client) Remote Storage SCU sends requested objects Print images Print SCU (RadOnc Client) Remote DICOM Print SCP receives and prints selected images DICOM Standard Interface Figure 2-1: SCU Role Application Data Flow Diagram 18 of 398 Varian System Server DICOM Conformance Statement, VA8203D3CS

19 Networking Figure 2-2: SCP Role Application Data Flow Diagram RadOnc Client Storage SCU Application Entity The Storage SCU Application Entity is invoked by the user from within a RadOnc Client Application to export selected images and RT objects or to export all objects of a whole patient to any configured remote Application Entity. RadOnc Client Query/Retrieve SCU Application Entity The Query/Retrieve Application Entity is invoked by the user from within a RadOnc Client Application to import images or RT objects from any configured remote Application Entity, typically a PACS. Varian System Server DICOM Conformance Statement, VA8203D3CS 19 of 398

20 Networking RadOnc Client Temporary Storage SCP Application Entity A temporary Storage SCP Application Entity is created by the Query/Retrieve SCU Application Entity to receive objects requested from a remote Query/Retrieve SCP. It is tightly coupled with the Query/Retrieve Application Entity. RadOnc Client Print SCU Application Entity The Print SCU Application Entity is invoked by the user from within a RadOnc Client Application to send a single image or any number of selected images to a DICOM printer. Various options for layout and scaling of these images can be selected. File Daemon/DB Daemon Storage SCP Application Entity Two different Storage SCPs are part of the Varian System Server product family. File Daemon provides a simple Storage SCP that saves any incoming object of known type as DICOM Media File to a configurable directory on the file system (see Table 1-1). A DICOM Media File header is therefore prepended to the incoming DICOM stream. DB Daemon can optionally be configured to work as Storage SCP. As opposed to File Daemon it is connected to the Varian System Database and inserts received objects directly to the database. File Daemon s and DB Daemon s Storage SCPs are invoked by a remote Storage SCU. DB Daemon Query/Retrieve SCP Application Entity DB Daemon can optionally be configured to work as Query/Retrieve SCP. It provides access to all DICOM objects stored in the Varian System Database. DB Daemon s Query/Retrieve SCP is invoked by a remote Query/Retrieve SCU searching for and retrieving objects. DB Daemon Storage SCU Application Entity DB Daemon s Storage SCU is invoked by DB Daemon s Query/Retrieve SCP to transfer requested objects to a remote Storage SCP Functional Definition of AE s Functional Definition of RadOnc Client Application Entity The RadOnc Client Application Entity can serve as Storage SCU, Query/Retrieve SCU and Print SCU. Any of those SCUs mentioned above are invoked by user interaction. Storage SCU and Query/Retrieve SCU are available as DICOM Storage Service export filter and DICOM Query Retrieve Service import filter. Parameters for the desired remote AE have to be configured when setting up such a filter. Multiple different configurations of the same import or export filter can exist in parallel, allowing the user to quickly access any previously configured remote SCP. Storage SCU and Query/Retrieve SCU can handle objects of types listed in Table 1-1. The user can send images to any DICOM Printer SCP via the print menu entry. In the print dialog the user can select among various layout and display options. Connection Settings for any number of remote DICOM Print SCPs have to be configured in advance Functional Definition of File Daemon Application Entity The File Daemon Application Entity is running continuously as a service and is responsible for handling incoming association requests of other Application Entities. It accepts Storage requests of SOP Classes listed in Table 1-1. When receiving data, objects are stored as DICOM Media 20 of 398 Varian System Server DICOM Conformance Statement, VA8203D3CS

21 Networking files in a configurable directory from which they can be imported to the Varian System Database via the RadOnc Client s import function later on. Multiple File Daemons can be running in parallel when configured as different Application Entities, listening on different TCP/IP ports Functional Definition of DB Daemon Application Entity The DB Daemon Application Entity is running continuously as a Windows service and is responsible for handling incoming association requests of other Application Entities. It accepts Storage and Query/Retrieve requests of SOP Classes listed in Table 1-1. Received objects are stored directly to the Varian System Database, queries for objects are answered based on objects stored in the Varian System Database, and requested objects are extracted from the Varian System Database and sent to the requestor. However, only copies of objects are exported, they will not be removed from the database. Storage SCP and Query/Retrieve SCP services can be configured and activated/deactivated separately and are designed to be supported in parallel by the same Application Entity which technically is identical to the same instance of the DB Daemon service. Multiple DB Daemons can be running in parallel when configured as different Application Entities, listening on different TCP/IP ports Sequencing of Real World Activities Not applicable because importing and exporting objects can happen in any sequence and independent of each other. Varian System Server DICOM Conformance Statement, VA8203D3CS 21 of 398

22 Networking 2.2 AE Specifications RadOnc Client Application Entity SOP Classes The RadOnc Client Application Entity provides Standard Conformance to the following SOP Classes. SOP Class Name SOP Class UID SCU SCP (Note 1) Computed Radiography Image Storage Yes Yes CT Image Storage Yes Yes MR Image Storage Yes Yes Secondary Capture Image Storage Yes Yes Spatial Registration Storage No Yes RT Image Storage Yes Yes RT Dose Storage Yes Yes RT Structure Set Storage Yes Yes RT Beams Treatment Record Storage No Yes RT Plan Storage Yes Yes RT Ion Plan Storage Yes Yes RT Ion Beams Treatment Record Storage No Yes Tracking Protocol (Private) Yes Yes Tracking Waveform (Private) Yes Yes Study Root Query/Retrieve Information Model FIND Study Root Query/Retrieve Information Model MOVE Basic Grayscale Print Management Meta SOP Class Yes No Yes No Yes No Table 2-1: SOP Classes for RadOnc Client Application Entity Note 1 Temporary Storage SCP used to receive Instances requested by Query/Retrieve SCU. 22 of 398 Varian System Server DICOM Conformance Statement, VA8203D3CS

23 Networking Association Policies General The DICOM standard application context name for DICOM 3.0 is always proposed. Application Context Name Table 2-2: DICOM Application Context for RadOnc Client Application Entity Number of Associations RadOnc Client Application Entity initiates one Association at a time because this happens only through a user interface action. Only one Association can be handled at a time and no new Association will be initiated as long as another Association is still active. Maximum number of simultaneous Associations 1 Table 2-3: Number of Associations initiated for RadOnc Client Application Entity RadOnc Client Application Entity does not accept any Associations Asynchronous Nature RadOnc Client Application Entity does not support asynchronous communication Implementation Identifying Information The implementation information for this Application Entity is defined in the following table. Storage SCU Implementation Class UID Query/Retrieve SCU Implementation Class UID Print SCU Implementation Class UID Implementation Version Name (not used) Table 2-4: DICOM Implementation Class and Version for RadOnc Client Application Entity Association Initiation Policy Activity Store Description and Sequencing of Activities The user can select one or more objects to be exported. The Storage SCU will be invoked and attempts to initiate a new Association. If multiple objects shall be transferred then multiple C- STORE requests will be issued over the Association. Objects to be transferred are sorted among their category as defined in Table 2-5 and transferred in the following order (object categories as defined in Table 2-5): 1. Objects in category Plan 2. Objects in category Image 3. Objects in category Structure Set Varian System Server DICOM Conformance Statement, VA8203D3CS 23 of 398

24 Networking 4. Objects in category Dose 5. Objects in category Treatment Record Object Category SOP Class Name SOP Class UID Plan RT Plan Storage RT Ion Plan Storage Structure Set RT Structure Set Storage Dose RT Dose Storage Treatment Record RT Beams Treatment Record Storage RT Ion Beams Treatment Record Storage Image Remaining objects SOP Class * Table 2-5: Object Categories used by RadOnc Client Storage SCU Application Entity Proposed Presentation Contexts RadOnc Client Storage SCU is capable of proposing the Presentation Contexts shown in the following table. Presentation Context Table Abstract Syntax Transfer Syntax Name UID Name UID Role Ext. Neg. Computed Radiography Image Storage DICOM Implicit VR Little Endian SCU None CT Image Storage DICOM Implicit VR Little Endian SCU None MR Image Storage DICOM Implicit VR Little Endian SCU None Secondary Capture Image Storage Spatial Registration Storage DICOM Implicit VR Little Endian SCU None DICOM Implicit VR Little Endian SCU None RT Image Storage DICOM Implicit VR Little Endian SCU None RT Dose Storage DICOM Implicit VR Little Endian SCU None RT Structure Set Storage RT Beams Treatment Record Storage DICOM Implicit VR Little Endian SCU None DICOM Implicit VR Little Endian SCU None RT Plan Storage DICOM Implicit VR Little Endian SCU None RT Ion Plan Storage DICOM Implicit VR Little Endian SCU None RT Ion Beams Treatment Record Storage DICOM Implicit VR Little Endian SCU None 24 of 398 Varian System Server DICOM Conformance Statement, VA8203D3CS

25 Networking Presentation Context Table Abstract Syntax Transfer Syntax Name UID Name UID Role Ext. Neg. Tracking Protocol DICOM Implicit VR Little Endian SCU None Tracking Waveform DICOM Implicit VR Little Endian SCU None Table 2-6: Proposed Presentation Contexts for RadOnc Client Storage SCU Application Entity When requesting an Association, only the Presentation Contexts of a selection of Abstract Syntaxes will be proposed to the SCU, corresponding to the SOP Classes of objects to be transferred SOP Specific Conformance for all Storage SOP Classes The behavior of RadOnc Client Storage SCU when encountering status codes in a C-FIND response is summarized in Table 2-7 below. Service Status Further Meaning Error Code Behavior Refused Out of Resources A7xx Failure Data Set does not A9xx match SOP Class Warning Cannot understand Coercion of Data Elements Data Set does not match SOP Class Elements Discarded Cxxx B000 B007 B006 The user is informed that the C-STORE request has failed. Status (0000,0900) and Status Comment (0000,0902) are logged and displayed along with additional error information. The SCP has successfully stored the SOP Instance. The user is informed that the C- STORE request has been performed successfully with warnings. Status (0000,0900) and Status Comment (0000,0902) are logged and displayed along with additional information. Success Success 0000 The SCP has successfully stored the SOP Instance. If all SOP Instances that have been selected to be transferred together have been stored successfully the user gets a success message. * * Any other status code. Depending on the type of the Error Code it is either handled like a Failure or Warning. However, Error Codes other than listed above in this table should not occur, as they are not defined for C-STORE (see [1], PS 3.4, Table B.2-1). Table 2-7: RadOnc Client C-STORE Response Status Handling Behavior Varian System Server DICOM Conformance Statement, VA8203D3CS 25 of 398

26 Networking After sending all SOP Instances, either successfully or not, the Association is released using A- RELEASE and the results are presented to the user. All events required for extracting SOP Instances from the Varian System Database and sending them to the SCP are logged. Timeout Exception Association aborted by the SCP or network layers Behavior The Association is released using A-RELEASE and the whole task of sending SOP Instances is aborted. The user is informed about the timeout and available information about it is logged. The whole task of sending SOP Instances is aborted. Table 2-8: RadOnc Client Storage SCU Communication Failure Behavior SOP Specific Conformance for RT Structure Set Storage See section SOP Specific Conformance for RT Dose Storage See section SOP Specific Conformance for RT Plan Storage See section Planned Verification Image Because the size of a verification image to be taken is not known in advance a width and height of zero pixels is assumed; as a consequence for RT Image Position (3002,0012), in Planned Verification Image Sequence (300A,00CA), the position of the image receptors center is used. This is because these coordinates are the same as those of the upper left hand corner of an image with zero number of pixels in x and y directions SOP Specific Conformance for RT Image Storage See section of 398 Varian System Server DICOM Conformance Statement, VA8203D3CS

27 Networking Activity Query/Retrieve Description and Sequencing of Activities The user invokes the DICOM Query/Retrieve Service import filter. At this time an Association is requested. When closing the dialog the Association is released again using A-RELEASE. Figure 2-3: Sequencing of Activities RadOnc Client Query/Retrieve Varian System Server DICOM Conformance Statement, VA8203D3CS 27 of 398

28 Networking A possible sequence of interactions between RadOnc Client Query/Retrieve SCU and a remote Query/Retrieve Server (e.g. retrieving SOP Instances of a patient) is illustrated in Figure 2-3: 1. The RadOnc Client Query/Retrieve SCU opens an Association with the Query/Retrieve Server. If it succeeds a temporary local Storage SCP is created. 2. A first C-FIND command with Query Level STUDY is issued containing, possibly empty, Patient Name and Patient ID. The result of this query is used to show a list of available patients matching the Patient Name and Patient ID query entered by the user. 3. The user selects a patient and again a C-FIND command with Query Level STUDY is issued containing the full Patient Name and Patient ID. This query is used to retrieve a list of all Studies of the selected patient. 4. The user selects a Study which triggers a C-FIND command with Query Level SERIES to get all Series that are contained in the selected Study. This step may be repeated for other Studies if user actions require retrieving information about another sub-tree of the object hierarchy. 5. The user selects a Series which triggers a C-FIND command with Query Level IMAGE to get all Series that are contained in the selected Series. This step may be repeated for other Series if user actions require retrieving information about another sub-tree of the object hierarchy. 6. The user selects one or more objects to be retrieved. When initiating retrieve operation a C- MOVE command for every SOP Instance to be retrieved is sent to the remote Query/Retrieve Server. 7. Upon receipt of a C-MOVE command the remote Query/Retrieve Server will open a new Association with the local Storage SCP. 8. For every C-MOVE command received from RadOnc Client Query/Retrieve SCU the remote Query/Retrieve Server will send via the remote Storage SCU a C-STORE command to the local Storage SCP. 9. When all objects have been transferred, whether successfully or not, and the user did not cancel the transfer then RadOnc Client Query/Retrieve SCU will release the Association using A-RELEASE and also shutdown it s temporary local Storage SCP. 10. The temporary local Storage SCP releases the Association using A-RELEASE if not already done by the remote Storage SCU Proposed Presentation Contexts RadOnc Client Query/Retrieve SCU is capable of proposing the Presentation Contexts shown in the following table. Presentation Context Table Abstract Syntax Transfer Syntax Name UID Name UID Role Ext. Neg. Study Root Query/Retrieve information model FIND Study Root Query/Retrieve information model MOVE DICOM Implicit VR Little Endian DICOM Implicit VR Little Endian SCU None SCU None Table 2-9: Proposed Presentation Contexts for RadOnc Client Q/R SCU Application Entity 28 of 398 Varian System Server DICOM Conformance Statement, VA8203D3CS

29 Networking SOP Specific Conformance for C-FIND SOP Classes The behavior of RadOnc Client Query/Retrieve SCU when encountering status codes in a C- FIND response is summarized in Table 2-10 below. Service Status Further Meaning Error Code Behavior Refused Out of Resources A7xx Failure Cancel Success Pending Data Set does not match SOP Class Cannot understand Matching terminated due to Cancel Request Matching is complete No final Identifier is supplied Matches are continuing Current Match is supplied and any Optional Keys were supported in the same manner as Required Keys. Matches are continuing Warning that one or more Optional Keys were not supported for existence and/or matching for this Identifier. A9xx Cxxx FE00 No results are displayed in the Query/Retrieve object browser. Cancel is handled like Failure, i.e. no results are displayed The SCP has completed the matches. Results are displayed in the Query/Retrieve object browser. FF00 FF01 * * Any other status code. The result transferred with this C-FIND Response is collected for display in the Query/Retrieve object browser once the C- FIND operation is completed. No results are displayed in the Query/Retrieve object browser. Table 2-10: RadOnc Client C-FIND Response Status Handling Behavior No C-CANCEL-FIND requests are ever issued. Relational-queries are not supported. Specific Character Set is not supported. It is not included in a query and will be ignored when present in the response. Varian System Server DICOM Conformance Statement, VA8203D3CS 29 of 398

30 Networking Exception Behavior Timeout The user is informed that the operation (C-FIND or C- MOVE) has timed out and can choose to retry the operation. Association aborted by the SCP or network layers When the Association is aborted during a C-MOVE operation the user is informed and failure details are displayed. The user can choose to retry the operation. Table 2-11: RadOnc Client Q/R C-FIND SCU Communication Failure Behavior Table 2-12 below lists the Attributes supported by the C-FIND SCU. Only a subset of the Attributes in this table will be sent in a specific C-FIND request, depending on Query Level and, if applicable, Modality. Name Tag VR Type Types of Matching Study Level Study Date (0008,0020) DA R U Study Time (0008,0030) TM R U Accession Number (0008,0050) SH R U Patient's Name (0010,0010) PN R U, S, W Patient ID (0010,0020) LO R U, S, W Study ID (0020,0010) SH R U Study Instance UID (0020,000D) UI U U, S Study Description (0008,1030) LO O U Patient s Birth Date (0010,0030) DA O U Series Level Modality (0008,0060) CS R U Series Number (0020,0011) IS R U Series Instance UID (0020,000E) UI U U, S Series Date (0008,0021) DA O U Series Time (0008,0031) TM O U Composite Object Level (all modalities) Instance Number (0020,0013) IS R U SOP Instance UID (0008,0018) UI U U SOP Class UID (0008,0016) UI O U 30 of 398 Varian System Server DICOM Conformance Statement, VA8203D3CS

31 Networking Name Tag VR Type Types of Matching Composite Object Level (all image modalities) Content Date (0008,0023) DA O U Content Time (0008,0033) TM O U Acquisition Number (0020,0012) IS O U Composite Object Level (RT (Ion) Beams Treatment Record) Treatment Date (3008,0250) DA O U Treatment Time (3008,0251) TM O U Composite Object Level (RT Dose) Dose Summation Type (3004,000A) CS O U Composite Object Level (RT Image) RT Image Label (3002,0002) SH O U Composite Object Level (RT (Ion) Plan) RT Plan Label (300A,0002) SH O U Plan Intent (300A,000A) CS O U Composite Object Level (RT Structure Set) Structure Set Label (3006,0002) SH O U Composite Object Level (Spatial Registration) Content Date (0008,0023) DA O U Content Time (0008,0033) TM O U Composite Object Level (Tracking Protocol, Tracking Waveform) Content Date (0008,0023) DA O U Content Time (0008,0033) TM O U Waveform Label (3283,1050) SH O U Table 2-12: Study Root Request Identifier for RadOnc Client Q/R C-FIND SCU The Types of Matching column in the above table should be read as follows: S Single Value Matching Varian System Server DICOM Conformance Statement, VA8203D3CS 31 of 398

32 Networking L List of UID Matching U Universal Matching W Wild Card Matching R Range Matching One or more matching types of the above list may be supported per Attribute SOP Specific Conformance for C-MOVE SOP Classes The behavior of RadOnc Client Query/Retrieve SCU when encountering status codes in a C- MOVE response is summarized in the following table. Service Status Further Meaning Error Code Behavior Refused Failure Cancel Warning Success Pending Out of Resources Unable to calculate number of matches Out of Resources Unable to perform sub-operations Move Destination unknown Identifier does not match SOP Class Unable to Process Sub-operations terminated due to Cancel Indication Sub-operations complete One or more Failures Sub-operations complete No Failures Sub-operations are continuing A701 A702 A801 A900 Cxxx FE00 B000 None of the requested SOP Instances could be retrieved. The user will be informed about the failure and can choose to retry retrieval. Cancel is handled like Failure. Some or all SOP Instances have not been transmitted successfully. The user is informed and can choose to retry retrieval of the remaining SOP Instances All SOP Instances have successfully been transmitted. The user is informed that all objects have been retrieved successfully. FF00 * * Any other status code. Transferring requested SOP Instances is continuing. This message is ignored. Any other status code is handled like Failure. Table 2-13: RadOnc Client C-MOVE Response Status Handling Behavior After having received all requested SOP Instances or when the user aborts the operation the Association is released using A-RELEASE. All events occurring during querying and retrieving SOP Instances are logged. If any log entries are marked with internal category Warning or Error they will be shown to the user automatically. No C-CANCEL-MOVE requests are ever issued. 32 of 398 Varian System Server DICOM Conformance Statement, VA8203D3CS

33 Networking Exception Behavior Timeout The user is informed that the operation (C-FIND or C- MOVE) has timed out and can choose to retry the operation. Association aborted by the SCP or network layers When the Association is aborted during a C-MOVE operation the user is informed and failure details are displayed. The user can choose to retry the operation. Table 2-14: RadOnc Client Q/R C-MOVE SCU Communication Failure Behavior The table below lists the Attributes that will be sent by the C-MOVE SCU. Only a subset of the Attributes in this table will be sent in a specific C-MOVE request, depending on Query Level. Name Tag VR Study Level Study Instance UID (0020,000D) UI Series Level Series Instance UID (0020,000E) UI Composite Object Level SOP Instance UID (0008,0018) UI Table 2-15: Study Root Request Identifier for RadOnc Client Q/R C-MOVE SCU Activity Receive Storage Request Description and Sequencing of Activities For a sequence diagram and complete sequencing of activities in the Query/Retrieve context see Figure 2-3. Received Instances are saved to temporary files and will be converted to the internal data model and imported to the Varian System Database in a separate step Accepted Presentation Contexts RadOnc Client Temporary Storage SCP Application Entity accepts Presentation Contexts shown in the following table. Presentation Context Table Abstract Syntax Transfer Syntax Name UID Name UID Role Ext. Neg. All Storage SOP Classes in Table 2-1 All Storage SOP Classes in Table 2-1 DICOM Implicit VR Little Endian DICOM Explicit VR Little Endian SCP None Table 2-16: Acceptable Presentation Contexts for RadOnc Client Temporary Storage SCP Application Entity and Receive Storage Request Varian System Server DICOM Conformance Statement, VA8203D3CS 33 of 398