DICOM Conformance Statement

Transcription

1 DICOM Conformance Statement SagiPlan 2.0 Concerned Product: SagiPlan Version 2.0 Document Date: November 26, 2015 Document Version: 01

2 Overview SagiPlan is a software product to perform the dosimetry for the treatment of cancerous tissue with temporarily applied radioactive radiation sources, i.e. high dose rate (HDR) brachytherapy. SagiPlan uses DICOM services to import images and structures and to export structures, treatment plans and dose information. Furthermore SagiPlan allows to Query/Retrieve other DICOM compliant applications for specific DICOM Objects. SagiPlan imports the images and structures from DICOM Media Files, which may be located on local disk or on exchangeable media such as CD or DVD. A TCP/IP Network Handler (called SagiPlanDS) can be set up to handle the import of images and structures from remote applications to the SagiPlan Application via network. This TCP/IP Handler acts as a receiver for DICOM Objects from network and stores these incoming files as DICOM Media Files on local disk. Once saved, these Files may be accessed by the Sagi- Plan application. SagiPlan exports the structures, treatment plans and dose information to DICOM Media Files or transfers these information objects to other systems via network by launching the Store SCU service. 2/179

3 1 Table Of Contents OVERVIEW TABLE OF CONTENTS INTRODUCTION REVISION HISTORY AUDIENCE REMARKS LEGAL AND COPYRIGHT INFORMATION TERMS AND DEFINITIONS BASICS OF DICOM COMMUNICATION ABBREVIATIONS REFERENCES NETWORKING IMPLEMENTATION MODEL Application Data Flow Diagram Functional Definition of AE s Functional Definition of SagiPlanDS Functional Definition of SagiPlan Sequencing of Real World Activities AE SPECIFICATIONS SagiPlanDS Application Entity SOP Classes Association Policies General Number of Associations Asynchronous Nature Implementation Identifying Information Association Initiation Policy Association Acceptance Policy Real World Activity Remote Storage SCU SagiPlan Application Entity SOP Classes Association Policies General Number of Associations Asynchronous Nature Implementation Identifying Information Association Initiation Policy Activity Send Files (Store SCU) / Export RT files Activity Query/Retrieve Association Acceptance Policy NETWORK INTERFACES Physical Network Interface Supported communication stacks TCP/IP stack Physical media support CONFIGURATION AE Title/Presentation Address Mapping /179

4 Local AE Titles Remote AE Title/Presentation Address Mapping SagiPlanDS SagiPlan Storage SCU SagiPlan Query/Retrieve SCU Find Parameters MEDIA INTERCHANGE IMPLEMENTATION MODEL Application Data Flow Diagram Functional definitions of AE s Sequencing of Real World Activities File Meta Information for Implementation Class and Version AE SPECIFICATIONS Application Entity SagiPlan File Meta Information for the SagiPlan Application Entity Real-World Activities Real-World Activity Export DICOM RT Files Real-World Activity Import DIOCOM RT Struct Real-World Activity Import DICOM Images AUGMENTED AND PRIVATE APPLICATION PROFILES MEDIA CONFIGURATION SUPPORT OF CHARACTER SETS SECURITY SECURITY PROFILES ASSOCIATION LEVEL SECURITY APPLICATION LEVEL SECURITY ANNEXES IOD CONTENTS Created SOP Instances RT Plan IOD RT Structure Set IOD RT Dose IOD Patient Module General Study Module Frame Of Reference Module General Equipment Module General Image Module Image Plane Module Image Pixel Module Multi Frame Module RT Series Module RT Dose Module Dose Summation Type Referenced Fraction Group Sequence RT DVH Module Structure Set Module Structure Set Module for the RT Structure Set IOD: Structure Set Module for the RT Dose IOD: ROI Contour Module Structure Set Module for the RT Structure Set IOD: Structure Set Module for the Dose IOD: RT Dose ROI Module Dose Value RT ROI Observations Module /179

5 RT General Plan Module RT Fraction Scheme Module RT Brachy Application Setups Module SOP Common Module Approval Module RT Prescription Module Usage of Attributes from received IOD s Computed Tomography Image IOD Magnetic Resonance Image IOD Positron Emission Tomography Image IOD RT Image IOD Secondary Capture Image IOD Ultrasound Image IOD Computed Radiography Image IOD X-Ray RF Image IOD X-Ray Angiographic Image IOD Digital X-Ray Image IOD Patient Module General Study Module General Series Module Frame Of Reference Module General Image Module Image Plane Module Image Pixel Module CT Image Module SOP Common Module RT Series Module RT Image Module SC Image Module CR Image Module X-Ray Image Module X-Ray Acquisition Module DX Detector Module DX Image Module DATA DICTIONARY OF PRIVATE ATTRIBUTES /179

6 List Of Tables Table 3-1 SOP CLASSes for SagiPlanDS Table 3-2 Number of Associations as an association acceptor for SagiPlanDS Table 3-3 DICOM Implementation Class and Version for SagiPlanDS Table 3-4 SagiPlanDS accepted Presentation Contexts Table 3-5 Storage C-STORE Response Status Table 3-6 SOP Classes for SagiPlan Storage SCU Table 3-7 SOP Classes for SagiPlan Query/Retrieve SCU Table 3-8 Number of Associations as an association initiator for SagiPlan Table 3-9 DICOM Implementation Class and Version for SagiPlan Table 3-10 Proposed Presentation Contexts for SagiPlan AE as Store SCU Table 3-11 SagiPlan AE as Store SCU Response Status Handling Table 3-12 Proposed Presentation Contexts for SagiPlan AE as Query/Retrieve SCU Table 3-13 SagiPlan AE as Query/Retrieve SCU Response Status Handling for C-FIND Requests Table 3-14 SagiPlan AE as Query/Retrieve SCU Response Status Handling For C-MOVE Requests Table 3-15 AE Title Configuration Table Table 3-16 Configuration Parameters Table for SagiPlanDS Application Entity Table 4-1 File Meta Information for Implementation Class and Version Table 4-2 AE Related Application Profiles, Real-World Activities, and Roles Table 4-3 Supported SOP Classes and Transfer Syntaxes for Export DICOM RT Files 33 Table 4-4 Supported SOP Classes and Transfer Syntaxes for Import DICOM RT Struct Table 4-5 Supported SOP Classes and Transfer Syntaxes for Import DIOCOM Images 34 Table 7-1 RT PLAN IOD MODULES Table 7-2 RT STRUCTURE SET IOD MODULES Table 7-3 RT DOSE IOD MODULES Table 7-4 PATIENT MODULE ATTRIBUTES Table 7-5 GENERAL STUDY MODULE ATTRIBUTES Table 7-6 FRAME OF REFERENCE MODULE ATTRIBUTES Table 7-7 GENERAL EQUIPMENT MODULE ATTRIBUTES Table 7-8 GENERAL IMAGE MODULE ATTRIBUTES Table 7-9 IMAGE PLANE MODULE ATTRIBUTES Table 7-10 IMAGE PIXEL MODULE ATTRIBUTES Table 7-11 MULTI-FRAME MODULE ATTRIBUTES Table 7-12 RT SERIES MODULE ATTRIBUTES Table 7-13 RT DOSE MODULE ATTRIBUTES Table 7-14 Dose Summation Type Table 7-15 Referenced Fraction Group Sequence Table 7-16 RT DVH MODULE ATTRIBUTES Table 7-17 STRUCTURE SET MODULE ATTRIBUTES Table 7-18 STRUCTURE SET MODULE ATTRIBUTES Table 7-19 ROI CONTOUR MODULE ATTRIBUTES Table 7-20 ROI CONTOUR MODULE ATTRIBUTES Table 7-21 RT DOSE ROI MODULE ATTRIBUTES Table 7-22 RT ROI OBSERVATIONS MODULE ATTRIBUTES Table 7-23 RT GENERAL PLAN MODULE ATTRIBUTES Table 7-24 RT FRACTION SCHEME MODULE ATTRIBUTES Table 7-25 RT BRACHY APPLICATION SETUPS MODULE ATTRIBUTES Table 7-26 SOP COMMON MODULE ATTRIBUTES /179

7 Table 7-27 Approval MODULE ATTRIBUTES Table 7-28 Approval MODULE ATTRIBUTES Table 7-29 CT IMAGE IOD MODULES Table 7-30 MR IMAGE IOD MODULES Table 7-31 PET IMAGE IOD MODULES Table 7-32 RT IMAGE IOD MODULES Table 7-33 SC IMAGE IOD MODULES Table 7-34 US IMAGE IOD MODULES Table 7-35 CR IMAGE IOD MODULES Table 7-36 XRF IMAGE IOD MODULES Table 7-37 X-RAY ANGIOGRAPHIC IMAGE IOD MODULES Table 7-38 DIGITAL X-RAY IMAGE IOD MODULES Table 7-39 PATIENT MODULE ATTRIBUTES Table 7-40 GENERAL STUDY MODULE ATTRIBUTES Table 7-41 GENERAL SERIES MODULE ATTRIBUTES Table 7-42 FRAME OF REFERENCE MODULE ATTRIBUTES Table 7-43 GENERAL IMAGE MODULE ATTRIBUTES Table 7-44 IMAGE PLANE MODULE ATTRIBUTES Table 7-45 IMAGE PIXEL MODULE ATTRIBUTES Table 7-46 CT IMAGE MODULE ATTRIBUTES Table 7-47 SOP COMMON MODULE ATTRIBUTES Table 7-48 Table C RT SERIES MODULE ATTRIBUTES Table 7-49 Table C.8-38 RT IMAGE MODULE ATTRIBUTES Table 7-50 SC IMAGE MODULE ATTRIBUTES Table 7-51 BASIC PIXEL SPACING CALIBRATION MACRO ATTRIBUTES Table 7-52 CR IMAGE MODULE ATTRIBUTES Table 7-53 X-RAY IMAGE MODULE ATTRIBUTES Table 7-54 X-RAY ACQUISITION MODULE ATTRIBUTES Table 7-55 DX DETECTOR MODULE ATTRIBUTES Table 7-56 DX IMAGE MODULE ATTRIBUTES Table 7-57 DATA DICTIONARY OF PRIVATE ATTRIBUTES /179

8 List of Figures Figure 3-1 Application Data Flow Diagram Figure 4-1 APPLICATION DATA FLOW DIAGRAM /179

9 2 Introduction 2.1 Revision History SagiPlan Version 2.0: Rev 01 September 29, Audience This document is written for users that need to understand how SagiPlan will integrate into their healthcare facility. This includes both those responsible for overall imaging network policy and architecture, as well as integrators who need to have a detailed understanding of the DICOM features of the product. This document contains some basic DICOM definitions so that any reader may understand how this product implements DICOM features. However, integrators are expected to fully understand all the DICOM terminology, how the tables in this document relate to the product s functionality, and how that functionality integrates with other devices that support compatible DICOM features. 2.3 Remarks The scope of this DICOM Conformance Statement is to facilitate integration between SagiPlan and other DICOM products. The Conformance Statement should be read and understood in conjunction with the DICOM Standard. DICOM by itself does not guarantee interoperability. The Conformance Statement does, however, facilitate a first-level comparison for interoperability between different applications supporting compatible DICOM functionality. This Conformance Statement is not supposed to replace validation with other DICOM equipment to ensure proper exchange of intended information. In fact, the user should be aware of the following important issues: The comparison of different Conformance Statements is just the first step towards assessing interconnectivity and interoperability between the product and other DICOM conformant equipment. Test procedures should be defined and executed to validate the required level of interoperability with specific compatible DICOM equipment, as established by the healthcare facility. It is the responsibility of the user (or the user s agent) to verify DICOM connectivity within the environment in which the SagiPlan application shall be used. It is the responsibility of the user to specify the appropriate test suite and to carry out the additional validation tests. Another device matching this Conformance Statement based on the comparison with its own Conformance Statement, will have a chance, but no guarantee that they will interoperate. DICOM only deals with communication, it is not a standard which specifies what is needed for certain applications to run on a device. 9/179

10 2.4 Legal and Copyright Information This document and the information therein are proprietary to Eckert & Ziegler BEBIG GmbH, Robert-Rössle-Str.10, Berlin, Germany. The document and the information therein shall not be reproduced in whole or in part without the express written permission of Eckert & Ziegler BEBIG GmbH. The information in this document may be altered or modified at any time without prior notice to the user. Eckert & Ziegler BEBIG GmbH does not assume any responsibility for any kind of errors in this manual or for any kind of damages caused by such errors. 2.5 Terms and Definitions Informal definitions are provided for the following terms used in this Conformance Statement. The DICOM Standard is the authoritative source for formal definitions of these terms. Abstract Syntax the information agreed to be exchanged between applications, generally equivalent to a Service/Object Pair (SOP) Class. Examples : Verification SOP Class, Modality Worklist Information Model Find SOP Class, Computed Radiography Image Storage SOP Class. Application Entity (AE) an end point of a DICOM information exchange, including the DICOM network or media interface software; i.e., the software that sends or receives DICOM information objects or messages. A single device may have multiple Application Entities. Application Entity Title the externally known name of an Application Entity, used to identify a DICOM application to other DICOM applications on the network. Application Context the specification of the type of communication used between Application Entities. Example: DICOM network protocol. Association a network communication channel set up between Application Entities. Attribute a unit of information in an object definition; a data element identified by a tag. The information may be a complex data structure (Sequence), itself composed of lower level data elements. Examples: Patient ID (0010,0020), Accession Number (0008,0050), Photometric Interpretation (0028,0004), Procedure Code Sequence (0008,1032). Information Object Definition (IOD) the specified set of Attributes that comprise a type of data object; does not represent a specific instance of the data object, but rather a class of similar data objects that have the same properties. The Attributes may be specified as Mandatory (Type 1), Required but possibly unknown (Type 2), or Optional (Type 3), and there may be conditions associated with the use of an Attribute (Types 1C and 2C). Examples: MR Image IOD, CT Image IOD, Print Job IOD. Media Application Profile the specification of DICOM information objects and encoding exchanged on removable media (e.g., CDs) 10/179

11 Module a set of Attributes within an Information Object Definition that are logically related to each other. Example: Patient Module includes Patient Name, Patient ID, Patient Birth Date, and Patient Sex. Negotiation first phase of Association establishment that allows Application Entities to agree on the types of data to be exchanged and how that data will be encoded. Presentation Context the set of DICOM network services used over an Association, as negotiated between Application Entities; includes Abstract Syntaxes and Transfer Syntaxes. Protocol Data Unit (PDU) a packet (piece) of a DICOM message sent across the network. Devices must specify the maximum size packet they can receive for DICOM messages. Security Profile a set of mechanisms, such as encryption, user authentication, or digital signatures, used by an Application Entity to ensure confidentiality, integrity, and/or availability of exchanged DICOM data Service Class Provider (SCP) role of an Application Entity that provides a DICOM network service; typically, a server that performs operations requested by another Application Entity (Service Class User). Examples: Picture Archiving and Communication System (image storage SCP, and image query/retrieve SCP), Radiology Information System (modality worklist SCP). Service Class User (SCU) role of an Application Entity that uses a DICOM network service; typically, a client. Examples: imaging modality (image storage SCU, and modality worklist SCU), imaging workstation (image query/retrieve SCU) Service/Object Pair (SOP) Class the specification of the network or media transfer (service) of a particular type of data (object); the fundamental unit of DICOM interoperability specification. Examples: Ultrasound Image Storage Service, Basic Grayscale Print Management. Service/Object Pair (SOP) Instance an information object; a specific occurrence of information exchanged in a SOP Class. Examples: a specific x-ray image. Tag a 32-bit identifier for a data element, represented as a pair of four digit hexadecimal numbers, the group and the element. If the group number is odd, the tag is for a private (manufacturer-specific) data element. Examples: (0010,0020) [Patient ID], (07FE,0010) [Pixel Data], (0019,0210) [private data element] Transfer Syntax the encoding used for exchange of DICOM information objects and messages. Examples: JPEG compressed (images), little endian explicit value representation. Unique Identifier (UID) a globally unique dotted decimal string that identifies a specific object or a class of objects; an ISO-8824 Object Identifier. Examples: Study Instance UID, SOP Class UID, SOP Instance UID. 11/179

12 Value Representation (VR) the format type of an individual DICOM data element, such as text, an integer, a person s name, or a code. DICOM information objects can be transmitted with either explicit identification of the type of each data element (Explicit VR), or without explicit identification (Implicit VR); with Implicit VR, the receiving application must use a DICOM data dictionary to look up the format of each data element. 2.6 Basics of DICOM Communication This section describes terminology used in this Conformance Statement for the nonspecialist. The key terms used in the Conformance Statement are highlighted in italics below. This section is not a substitute for training about DICOM, and it makes many simplifications about the meanings of DICOM terms. Two Application Entities (devices) that want to communicate with each other over a network using DICOM protocol must first agree on several things during an initial network handshake. One of the two devices must initiate an Association (a connection to the other device), and ask if specific services, information, and encoding can be supported by the other device (Negotiation). DICOM specifies a number of network services and types of information objects, each of which is called an Abstract Syntax for the Negotiation. DICOM also specifies a variety of methods for encoding data, denoted Transfer Syntaxes. The Negotiation allows the initiating Application Entity to propose combinations of Abstract Syntax and Transfer Syntax to be used on the Association; these combinations are called Presentation Contexts. The receiving Application Entity accepts the Presentation Contexts it supports. For each Presentation Context, the Association Negotiation also allows the devices to agree on Roles which one is the Service Class User (SCU - client) and which is the Service Class Provider (SCP - server). Normally the device initiating the connection is the SCU, i.e., the client system calls the server, but not always. The Association Negotiation finally enables exchange of maximum network packet (PDU) size, security information, and network service options (called Extended Negotiation information). The Application Entities, having negotiated the Association parameters, may now commence exchanging data. Common data exchanges include queries for worklists and lists of stored images, transfer of image objects and analyses (structured reports), and sending images to film printers. Each exchangeable unit of data is formatted by the sender in accordance with the appropriate Information Object Definition, and sent using the negotiated Transfer Syntax. There is a Default Transfer Syntax that all systems must accept, but it may not be the most efficient for some use cases. Each transfer is explicitly acknowledged by the receiver with a Response Status indicating success, failure, or that query or retrieve operations are still in process. Two Application Entities may also communicate with each other by exchanging media (such as a CD-R). Since there is no Association Negotiation possible, they both use a Media Application Profile that specifies pre-negotiated exchange media format, Abstract Syntax, and Transfer Syntax. 12/179

13 2.7 Abbreviations AE Application Entity AET Application Entity Title CD-R Compact Disk Recordable CR Computed Radiography CT Computed Tomography DICOM Digital Imaging and Communications in Medicine FSC File-Set Creator FSU File-Set Updater FSR File-Set Reader IOD Information Object Definition LUT Look-up Table MPEG Moving Picture Experts Group MR Magnetic Resonance Imaging NTP Network Time Protocol PET Positron Emission Tomography RT Radiotherapy SC Secondary Capture SCP Service Class Provider SCU Service Class User SOP Service-Object Pair TCP/IP Transmission Control Protocol/Internet Protocol U Unique (Key Attribute) US Ultrasound VL Visible Light 2.8 REFERENCES 1. NEMA The DICOM Standard Digital Imaging and Communications in Medicine (DICOM) Standard, available free at 2. SagiPlan-2.0.chm SagiPlan User s Guide 13/179

14 3 Networking 3.1 Implementation Model Application Data Flow Diagram The diagram below illustrates the Data Flow Diagram of the SagiPlan and SagiPlanDS Application Entities. 14/179

15 DICOM Media File (Temporary Object Storage on local disk for later import to the SagiPlan Application Entity) Application Entity SagiPlanDS (Storage SCP) Remote Storage SCU Real World Activity Query / Retrieve Application Entity SagiPlan Remote Query / Retrieve SCP Real World Activity Send Files and Export RT files Remote Storage SCP DICOM Media File (probably created by invoking the Export Functionality of the SagiPlan Application Entity) DICOM Standard Interface Figure 3-1 Application Data Flow Diagram 15/179

16 3.1.2 Functional Definition of AE s Functional Definition of SagiPlanDS The SagiPlanDS Application Entity implements a Service Class Provider (SCP) for the Storage Service Class. It listens on a specific TCP/IP port for incoming association requests from a Storage SCU and can receive images and other DICOM Information Objects according to the Storage Service Class. Received objects will be stored as DICOM Media Files on local disk, from which they can be imported later on to the SagiPlan Application. The SagiPlanDS Application Entity also supports the Verification Service Class as an SCP. The SagiPlanDS runs continuously as a service and may be setup via the SagiPlan application Functional Definition of SagiPlan The SagiPlan Application Entity implements the following functions: A Service Class User (SCU) for the Storage Service Class. In this role it initiates an association to a Remote AE as a Storage Service Class Provider to send DICOM Information Objects. If the remote AE accepts the association, SagiPlan will send the selected Information Object(s) by invoking a C-STORE request for each object on the same association. A Service Class User (SCU) for the Query / Retrieve Service Class. In this role it initiates an association to a Remote AE to Query for a list of DICOM objects. If the remote AE accepts the association, SagiPlan will send C-FIND requests to the remote AE to query for certain Patients, Studies or Series. Once the responses are received and the user has selected one or more of these Patients, Studies or Series, the SagiPlan AE will send C-MOVE requests to the remote AE to transfer the DICOM objects to a Store SCP. SagiPlan can be configured to choose the Sagi- PlanDS AE as the Store SCP destination of the C-MOVE requests Sequencing of Real World Activities Not applicable. 3.2 AE Specifications SagiPlanDS Application Entity SOP Classes The SagiPlanDS AE provides Standard Conformance to the following SOP Classes: 16/179

17 Table 3-1 SOP CLASSes for SagiPlanDS SOP Class Name SOP Class UID SCU SCP Verification SOP Class No Yes Stored Print Storage No Yes Hardcopy Grayscale Image Storage No Yes Hardcopy Color Image Storage No Yes Computed Radiography Image Storage No Yes Digital X-Ray Image Storage - For No Yes Presentation Digital X-Ray Image Storage - For Processing No Yes Digital Mammography X-Ray Image No Yes Storage For Presentation Digital Mammography X-Ray Image No Yes Storage For Processing Digital Intra Oral X-Ray Image Storage No Yes For Presentation Digital Intra Oral X-Ray Image Storage No Yes For Processing Standalone Modality LUT Storage No Yes Encapsulated PDF Storage No Yes 1 Standalone VOI LUT Storage No Yes Grayscale Softcopy Presentation State No Yes Storage Color Softcopy Presentation State Storage No Yes Pseudo Color Softcopy Presentation No Yes State Storage Blending Softcopy Presentation State No Yes Storage X-Ray Angiographic Image Storage No Yes Enhanced XA Image Storage No Yes X-Ray Fluoroscopy Image Storage No Yes Enhanced XRF Image Storage No Yes 1 PET Image Storage No Yes PET Curve Storage No Yes CT Image Storage No Yes Enhanced CT Image Storage No Yes 17/179

18 Nuclear Medicine Image Storage No Yes Ultrasound Multiframe Image Storage No Yes MR Image Storage No Yes Enhanced MR Image Storage No Yes MR Spectroscopy Storage No Yes RT Image Storage No Yes 1 RT Dose Storage No Yes 2 RT Structure Set Storage No Yes 3 RT Beams Treatment Record Storage No Yes 4 RT Plan Storage No Yes 5 RT Brachy Treatment Record Storage No Yes 6 RT Treatment Summary Record Storage No Yes 7 Ultrasound Image Storage No Yes Raw Data Storage No Yes Spatial Registration Storage No Yes Spatial Fiducials Storage No Yes Real World Value Mapping Storage No Yes Secondary Capture Image Storage No Yes Multiframe Single Bit Secondary Capture Image Storage No Yes Multiframe Grayscale Byte Secondary No Yes Capture Image Storage Multiframe Grayscale Word Secondary No Yes Capture Image Storage Multiframe True Color Secondary Capture No Yes Image Storage VL Endoscopic Image Storage No Yes 1 Video Endoscopic Image Storage No Yes 1.1 VL Microscopic Image Storage No Yes 2 Video Microscopic Image Storage No Yes VL Slide Coordinates Microscopic No Yes Image Storage 3 18/179

19 VL Photographic Image Storage No Yes 4 Video Photographic Image Storage No Yes Ophthalmic Photography 8 Bit Image No Yes Storage 5.1 Ophthalmic Photography 16 Bit Image No Yes Storage 5.2 Stereometric Relationship Storage No Yes 5.3 Standalone Overlay Storage No Yes Basic Text SR No Yes 1 Enhanced SR No Yes 2 Comprehensive SR No Yes 3 Procedure Log Storage No Yes 0 Mammography CAD SR Storage No Yes 0 Key Object Selection Document No Yes 9 Chest CAD SR Storage No Yes 5 X-Ray Radiation Dose SR Storage No Yes 7 Standalone Curve Storage No Yes Twelve Lead ECG Waveform Storage No Yes General ECG Waveform Storage No Yes Ambulatory ECG Waveform Storage No Yes Hemodynamic Waveform Storage No Yes Cardiac Electrophysiology Waveform No Yes Storage Basic Voice Audio Waveform Storage No Yes Notice: Although the SagiPlanDS supports many SOP Classes, only some of them are supported by the SagiPlan application via the SagiPlan Application Entity for later import (see Application Entity ) Association Policies General The maximum PDU length of the AE is bytes. The AE does not support any SOP class extended negotiations. 19/179

20 Number of Associations Table 3-2 Number of Associations as an association acceptor for SagiPlanDS Maximum number of simultaneous associations SagiPlanDS will attempt only one association at a time Asynchronous Nature Asynchronous mode of operation is not supported Implementation Identifying Information Table 3-3 DICOM Implementation Class and Version for SagiPlanDS Implementation Class UID Implementation Version Name SagiPlanDS Association Initiation Policy The SagiPlanDS Application Entity never initiates associations Association Acceptance Policy When SagiPlanDS accepts an association, it will answer a C-ECHO request or receive any DICOM Information Objects transmitted on that association and store the Objects on disk. It places no limitations on how may connect to it Real World Activity Remote Storage SCU Description and Sequencing of Activities Not applicable Accepted Presentation Contexts 20/179

21 The SagiPlanDS Application Entity will accept presentation contexts for all of the above mentioned supported SOP Classes using any of the transfer syntaxes: Table 3-4 SagiPlanDS accepted Presentation Contexts Abstract Syntax Transfer Syntax Role Extended Name UID Name UID Negotiation See See Explicit VR SCP None note note Little Endian See See Explicit VR SCP None note note Big Endian See See Implicit VR SCP None note note Little Endian Note: This applies to all supported Storage Abstract Syntaxes, i.e. to all supported SOP Classes The SagiPlanDS prefers the transfer syntaxes in the following order: 1. Explicit VR Little Endian 2. Implicit VR Little Endian 3. Explicit VR Big Endian The SagiPlanDS application does not support extended negotiation SOP Specific Conformance for SOP Classes Service Status Failure Further Meaning Refused: Out of Resources Error: Data Set does not match SOP Class Error: Cannot understand Table 3-5 Storage C-STORE Response Status Error Code A700 A900 C000 Success Success 0000 All o.k. Reason Application out of memory, file system or database write error (e. g. file system full) SOP class or instance UID in C-STORE-RQ does not match UIDs in the received dataset Received dataset without SOP class or instance UID; received Presentation State that failed syntax check; internal application error 21/179

22 3.2.2 SagiPlan Application Entity SOP Classes The SagiPlan AE as a Storage SCU provides Standard Conformance to the following SOP Classes: Table 3-6 SOP Classes for SagiPlan Storage SCU SOP Class Name SOP Class UID Computed Radiography Image Storage Digital XRay Image Storage For Presentation Digita lxray Image Storage For Processing Digital Mammography XRay Image Storage For Presentation Digital Mammography XRay Image Storage For Processing Digital Intra Oral XRay Image Storage For Presentation Digital Intra Oral XRay Image Storage For Processing Encapsulated PDF Storage Grayscale Softcopy Presentation State Storage Color Softcopy Presentation State Storage Pseudo Color Softcopy Presentation State Storage Blending Softcopy Presentation State Storage XRay Angiographic Image Storage Enhanced XA Image Storage XRay Fluoroscopy Image Storage Enhanced XRF Image Storage PET Image Storage PET Curve Storage CT Image Storage Enhanced CT Image Storage Nuclear Medicine Image Storage Ultrasound Multiframe Image Storage MR Image Storage Enhanced MR Image Storage MR Spectroscopy Storage RT Image Storage RT Dose Storage RT Structure Set Storage RT Beams Treatment Record Storage RT Plan Storage RT Brachy Treatment Record Storage RT Treatment Summary Record Storage Ultrasound Image Storage Raw Data Storage Spatial Registration Storage /179

23 Spatial Fiducials Storage Real World Value Mapping Storage Secondary Capture Image Storage Multiframe Single Bit Secondary Capture Image Storage Multiframe Grayscale Byte Secondary Capture Image Storage Multiframe Grayscale Word Secondary Capture Image Storage Multiframe True Color Secondary Capture Image Storage VL Endoscopic Image Storage VL Microscopic Image Storage VL Slide Coordinates Microscopic Image Storage VL Photographic Image Storage Ophthalmic Photography 8 Bit Image Storage Ophthalmic Photography 16 Bit Image Storage Stereometric Relationship Storage Basic Text SR Enhanced SR Comprehensive SR Procedure Log Storage Mammography CAD SR Key Object Selection Document Chest CAD SR XRay Radiation Dose SR Twelve Lead ECG Waveform Storage General ECG Waveform Storage Ambulatory ECG Waveform Storage Hemodynamic Waveform Storage Cardiac Electrophysiology Waveform Storage Basic Voice Audio Waveform Storage The SagiPlan AE as a Query / Retrieve SCU provides Standard Conformance to the following SOP Classes: SOP Class Name Table 3-7 SOP Classes for SagiPlan Query/Retrieve SCU SOP Class UID Study Root Query/Retrieve Information Model FIND Patient Root Query/Retrieve Information Model MOVE Study Root Query/Retrieve Information Model MOVE Association Policies General The maximum PDU length of the AE is bytes. The AE does not support any SOP class extended negotiations. 23/179

24 Number of Associations Table 3-8 Number of Associations as an association initiator for SagiPlan Maximum number of simultaneous associations SagiPlan will attempt only one association at a time Asynchronous Nature Asynchronous mode of operation is not supported Implementation Identifying Information Table 3-9 DICOM Implementation Class and Version for SagiPlan Implementation Class UID Implementation Version Name SagiPlan Association Initiation Policy Activity Send Files (Store SCU) / Export RT files Description and Sequencing of Activities The user can select one or more DICOM information objects to be transferred via the Store SCU service to another DICOM AE. The information objects might be DICOM Media files stored on hard disc or DICOM RT Plan, RT Dose and RT Struct information objects directly created from the plan data of a SagiPlan study. The SagiPlan AE as a Storage SCU will try to initiate an association to a remote Storage SCP. The user has to select a destination DICOM peer for that. If multiple objects shall be transferred then multiple C- STORE requests will be issued over the association Proposed Presentation Contexts Table 3-10 Proposed Presentation Contexts for SagiPlan AE as Store SCU Abstract Syntax Transfer Syntax Role Extended Name UID Name UID Negotiation See See Explicit VR SCU None note note Little Endian 24/179

25 See note See note See note See note Explicit VR Big Endian Implicit VR Little Endian SCU None SCU None Note: This applies to all supported Storage Abstract Syntaxes, i.e. to all supported SOP Classes SOP Specific Conformance for SOP Classes Service Status Failure Warning Table 3-11 SagiPlan AE as Store SCU Response Status Handling Further Meaning Refused: Out of Resources Error: Data Set does not match SOP Class Error: Cannot understand Coercion of Data Elements Data Set does not match SOP Class Elements Discarded A7xx A9xx Cxxx Error Code B000 B007 B006 Behaviour The user is informed that the C-STORE request has failed. All outstanding C-STORE requests are cancelled. The SCP has stored the SOP Instance. The user is informed that the C-STORE request has been performed with warnings. Success Success 0000 The SCP has successfully stored the SOP Instance. The user is informed that the C-STORE request has been performed successfully Activity Query/Retrieve Description and Sequencing of Activities The user may enter values into a search mask for querying a Query/Retrieve SCP. The search mask is based on entries for Patient Names, Patient Registration Numbers, Patient Birthdates, Study IDs or Study Dates. After the user invokes the Query command, an association will be initiated to a remote Query/Retrieve SCP. The user has to define/select the AE Address, AE Title and port of the remote Query/Retrieve SCP. After association establishment a C-FIND request will be performed at the STUDY Level for querying all Studies which attributes match those of the search mask. For every received response at STUDY level a new C-FIND request will be performed at the SERIES Level for querying all Series of the related Study. All responses are arranged and displayed in a hierarchical list (Patient with one or more studies, consisting of one or more series). The user has to select at least one Patient, Study or Series in this list in order to invoke the Transfer command. After that an association to the remote Query/Retrieve SCP will be initiated. For every selected patient a C-MOVE request at PATIENT level will be per- 25/179

26 formed, for every selected Study a C-MOVE request at STUDY level and for every selected series a C-MOVE request at SERIES level. The AE Title of the move destination has to be selected by the user. It is even possible to select the SagiPlanDS AE as the move destination in order to make the transferred objects accessible by the SagiPlan application Proposed Presentation Contexts Study Root Query/Retriev e Information Model FIND Explicit VR Little Endian SC U Table 3-12 Proposed Presentation Contexts for SagiPlan AE as Query/Retrieve SCU Abstract Syntax Transfer Syntax Role Name UID Name UID Extended Nego tiation None Study Root Query/Retriev e Information Model FIND Explicit VR Big Endian SC U None Study Root Query/Retriev e Information Model FIND Implicit VR Little Endian SC U None Patient Root Query/Retriev e Information Model MOVE Explicit VR Little Endian SC U None Patient Root Query/Retriev e Information Model MOVE Explicit VR Big Endian SC U None Patient Root Query/Retriev e Information Model MOVE Implicit VR Little Endian SC U None Study Root Query/Retriev e Information Model MOVE Explicit VR Little Endian SC U None Study Root Explicit SC None 26/179

27 Query/Retriev e Information Model MOVE 2 VR Big Endian U Study Root Query/Retriev e Information Model MOVE Implicit VR Little Endian SC U None SOP Specific Conformance for SOP Classes Table 3-13 SagiPlan AE as Query/Retrieve SCU Response Status Handling for C-FIND Requests Service Status Failure Cancel Further Meaning Refused: Out of Resources Identifier does not match SOP Class Unable to process Matching terminated due to Cancel request Error Code A700 A900 Cxxx FE00 Behaviour The user is informed that the C-FIND request has failed. No results are displayed in the Query/Retrieve results list. No more results are displayed. Success Matching is complete No final Identifier is supplied. Pending 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 sup The SCP has completed the matches. Results are displayed in the Query/Retrieve results list. FF00 FF01 The result transferred with this C-FIND Response is collected for display in the Query/Retrieve results list once the C-FIND operation is completed. 27/179

28 ported for existence and/or matching for this Identifier. A C-CANCEL-FIND request is issued after 1000 responses per C-FIND request have been received. Relational-queries are not supported. Table 3-14 SagiPlan AE as Query/Retrieve SCU Response Status Handling For C-MOVE Requests Service Status Failure Cancel Further Meaning Refused: Out of Resources Unable to calculate number of matches Refused: Out of Resources Unable to perform sub-operations Refused: Move Destination unknown Identifier does not match SOP Class Unable to Process Sub-operations terminated due to Cancel Indication Error Code A701 A702 A801 A900 Cxxx FE00 Behaviour None of the requested SOP Instances could be transferred (moved). The user will be informed about the failure. No more SOP Instances are transferred. Warning Success Pending Sub-operations Complete One or more Failures Sub-operations Complete No Failures Sub-operations are continuing B000 Some or all SOP Instances have not been transmitted successfully. The user will be informed about the Warning response All SOP Instances have successfully been transmitted. The user is informed that all FF00 objects have been retrieved successfully. Transferring requested SOP Instances is continuing. No C-CANCEL-MOVE requests are ever issued. 28/179

29 Association Acceptance Policy The SagiPlan Application Entity as a Query/Retrieve SCU never accepts associations. 3.3 Network Interfaces Physical Network Interface Supported communication stacks The Application provides TCP/IP Network Communication Support as defined in PS 3.8 (part 8 of the DICOM standard) TCP/IP stack The Application uses the TCP/IP stack of Microsoft Windows Operating System, which is the underlying operating system of the application Physical media support The Application can run on any physical network media that is supported by the underlying hardware and operating system (i.e. standard PCs and Windows operating system). 3.4 Configuration AE Title/Presentation Address Mapping Local AE Titles The local AE Titles for the SagiPlan as well as the SagiPlanDS Application Entities are configurable. The configuration is performed via the SagiPlan Setup Dialog and via the SagiPlanDS Service Controller Window, respectively. Table 3-15 AE Title Configuration Table Application Entity Default AE Title Default TCP/IP Port SagiPlan SagiPlan Not Applicable SagiPlanDS SagiPlanDS 104 (configurable) 29/179

30 Remote AE Title/Presentation Address Mapping SagiPlanDS Not Applicable SagiPlan Storage SCU The TCP/IP Address, the AE Title and the Port Number of the remote Storage SCP are configurable. Multiple configurations can be prepared via the corresponding SagiPlan setup menu. These can then be selected in the subsequent Send Files requests SagiPlan Query/Retrieve SCU Find The TCP/IP Address, the AE Title and the Port Number of the remote Query/Retrieve SCP are configurable. Multiple configurations can be prepared via the appropriate SagiPlan setup menu. These can then be selected in the subsequent Query requests. The AE Title of the move destination for the Query/Retrieve Move request is configurable too. Multiple AE Titles can be prepared via the appropriate SagiPlan setup menu. These can then be selected for the subsequent Transfer requests Parameters The following table shows DICOM relevant configuration parameters. Parameter Table 3-16 Configuration Parameters Table for SagiPlanDS Application Entity Configurable (Yes/No) General Parameters Time-out waiting for acceptance or rejection Response No to an Association Open Request. (Application Level timeout) Default Value 30 seconds General DIMSE level time-out values No Unlimited Time-out waiting for response to TCP/IP connect No Unlimited request. (Low-level timeout) Max PDU Size No /179

31 4 Media Interchange 4.1 Implementation Model Application Data Flow Diagram Export DICOM RT Files Application Entity SagiPlan FSC DICOM Media File (on any Windows Volume) Import DICOM Images Import DICOM RT Struct Application Entity SagiPlan FSR DICOM Standard Interface DICOM Media File (on any Windows Volume) Figure 4-1 APPLICATION DATA FLOW DIAGRAM Functional definitions of AE s The SagiPlan Application Entity is responsible for the import of DICOM Information objects (images and structure sets) to the SagiPlan application. It is also responsible for the export of DICOM Information Objects (treatment plans, dose information and structure sets) to other applications. Those functions are operated by the user invoking the Import / Export commands in the SagiPlan application. The SagiPlan Application Entity acts as a FSC for the export of DICOM Information Objects and as a FSR for the import of DICOM Information Objects. The SagiPlan Application Entity can write DICOM RT Plan, RT Dose and RT Struct Information Objects to any attached Windows Volume as a DICOM File which conforms to the 31/179

32 DICOM File Format as described in PS 3.10 of the DICOM standard. It can read DICOM Files (which conforms to the DICOM File Format) from any Windows Volume Sequencing of Real World Activities All FSR and FSC activities are sequentially initiated in the user interface of the SagiPlan application, and another activity may not be initiated until the prior activity has completed File Meta Information for Implementation Class and Version Table 4-1 File Meta Information for Implementation Class and Version File Meta Information Version 00, 01 Implementation Class UID Implementation Version Name Not Implemented 4.2 AE Specifications The SagiPlan AE provides standard conformance to the DICOM Interchange Option of the Media Storage Service Class Application Entity SagiPlan Table 4-2 AE Related Application Profiles, Real-World Activities, and Roles Supported Application Profile Real-World Activity Roles STD-GEN-CD Export DICOM RT Files FSC STD-GEN-DVD-RAM Import DICOM RT Struct FSR Import DICOM Images FSR File Meta Information for the SagiPlan Application Entity The SagiPlan Application Entity Title is not stored. 32/179