DICOM Conformance Statement Radiotherapy Document Revision 2 July 1, Copyright Brainlab AG

Transcription

1 Document Revision 2 July 1, Copyright Brainlab AG

2

3 1 Conformance Statement Overview This is a Conformance Statement for the Brainlab system. This system dependent from purchased licenses and configuration consists of several applications and performers. Applications Content Manager DICOM DICOM Proxy Application 1... Performers Application N Performer 1... Performer N Figure 1-1: Overview of a Brainlab system running applications and performers The Brainlab system is based on the following common management applications: Management Application Content Manager DICOM Proxy Description Manages applications on Brainlab systems. It allows a user to create and read screenshots. The interface between the Brainlab system and the outside DICOM world. No application or performer communicates directly with any remote DICOM node, but all communication will be done through the DICOM Proxy. If necessary the DICOM Proxy adjusts the DI- COM communication to the capabilities and known specialties of the remote DICOM nodes. The DICOM Proxy itself (see [1] for its Conformance Statement) as well as the internal communication between the DICOM Proxy and the applications and performers is not part of this Conformance Statement. Table 1-1: Common Management Applications Applications have a user interface. The following applications are documented in this Conformance Statement: Application Patient Selection Image Viewer Fusion Smartbrush Description Allows the user to browse, load or save data in/to DICOM archives or on/to media (e.g., CD-ROM) Allows the user to display any kind of DICOM image data. Allows the user to overlap two different DICOM data sets Allows the user to create, read and update segmentations based on DICOM image data. July 1, 2014 Document Revision 2 Page 3 of 89

4 Content Manager Patient Selection Image Viewer Fusion Smartbrush Brain Metastases Dose Review AHSA Auto Segmentation DICOM RT Export DICOM Conformance Statement Application Brain Metastases Dose Review Adaptive Hybrid Surgery Analysis (AHSA) Description Reads images and segmentations and allows to create an indication-driven radiotherapy treatment plan for multiple brain metastases. Final treatment plans can be exported to third-party systems for treatment or evaluation. Enables the user to review therapeutic volume dose based on image and structure information. Reads images, segmentations and registrations and allows the user to evaluate intraoperative data. Table 1-2: Applications Performers don t have a user interface and perform their tasks in the background. The following performers are documented in this Conformance Statement: Performer Auto Segmentation DICOM RT Export Description Performs segmentation tasks in the background. Conversion of 3D objects and registration (fusion) data to DICOM RT compliant format. Table 1-3: Performers The table below addresses all supported network services used by the different surgery application entities. For the SOP Classes in the Transfer section SCU and SCP have special meanings. Entities consuming data (e.g., for displaying images) are marked as SCP. Applications producing data (e.g., like spatial registrations) are marked as SCU. All created data will be initially stored to the DICOM Proxy, which then is responsible to forward created data to configured remote DICOM nodes. Symbol: Meaning: User of Service (SCU) Provider of Service (SCP) Both (SCU/SCP) SOP Classes Transfer Breast Tomosynthesis Image Storage Computed Radiography Image Storage CT Image Storage Digital Intra-oral X-Ray Image Storage - For Presentation Digital Intra-oral X-Ray Image Storage - For Processing Digital Mammography X-Ray Image Storage - For Presentation Digital Mammography X-Ray Image Storage - For Processing Digital X-Ray Image Storage - For Presentation Digital X-Ray Image Storage - For Processing Page 4 of 89 Document Revision 2 July 1, 2014

5 Content Manager Patient Selection Image Viewer Fusion Smartbrush Brain Metastases Dose Review AHSA Auto Segmentation DICOM RT Export DICOM Conformance Statement SOP Classes Encapsulated PDF Storage Enhanced CT Image Storage Enhanced MR Color Image Storage Enhanced MR Image Storage Enhanced PET Image Storage Enhanced US Volume Storage Enhanced XA Image Storage Enhanced XRF Image Storage Grayscale Softcopy Presentation State Storage Intravascular Optical Coherence Tomography Image Storage - For Presentation Intravascular Optical Coherence Tomography Image Storage - For Processing Key Object Selection Document Storage MR Image Storage MR Spectroscopy Storage Multi-frame Grayscale Byte Secondary Capture Storage Multi-frame Grayscale Word Secondary Capture Storage Multi-frame Single Bit Secondary Capture Storage Multi-frame True Color Secondary Capture Storage Nuclear Medicine Image Storage Nuclear Medicine Image Storage (Retired) Ophthalmic Photography 16 Bit Image Storage Ophthalmic Photography 8 Bit Image Storage Ophthalmic Tomography Image Storage Positron Emission Tomography Image Storage Raw Data Storage RT Dose Storage RT Plan Storage RT Structure Set Storage Secondary Capture Image Storage Segmentation Storage Spatial Fiducials Storage Spatial Registration Storage Surface Segmentation Storage Ultrasound Image Storage Ultrasound Image Storage (Retired) Ultrasound Multi-frame Image Storage Ultrasound Multi-frame Image Storage (Retired) Video Endoscopic Image Storage July 1, 2014 Document Revision 2 Page 5 of 89

6 Patient Selection Content Manager Patient Selection Image Viewer Fusion Smartbrush Brain Metastases Dose Review AHSA Auto Segmentation DICOM RT Export DICOM Conformance Statement SOP Classes Video Microscopic Image Storage Video Photographic Image Storage VL Endoscopic Image Storage VL Microscopic Image Storage VL Photographic Image Storage VL Slide-Coordinates Microscopic Image Storage VL Whole Slide Microscopy Image Storage X-Ray 3D Angiographic Image Storage X-Ray 3D Craniofacial Image Storage X-Ray Angiographic Bi-Plane Image Storage (Retired) X-Ray Angiographic Image Storage X-Ray Radiofluoroscopic Image Storage Query/Retrieve Patient Root Query/Retrieve Information Model - FIND Patient Root Query/Retrieve Information Model - GET Study Root Query/Retrieve Information Model - FIND Study Root Query/Retrieve Information Model - GET Table 1-4: Supported network services The next table addresses all supported Media Storage Application Profiles used by the different application entities. Symbol: Meaning: Read Files (FSR) Write Files (FSC or FSU) Both (FSR/FSC or FSU) Media Storage Application Profile Brainlab General Purpose Media Interchange Table 1-5: Supported media profiles Page 6 of 89 Document Revision 2 July 1, 2014

7 2 Table of Contents 1 Conformance Statement Overview 3 2 Table of Contents 7 3 Introduction Revision History Audience Remarks Abbreviations References Networking Implementation Model Application Data Flow Diagram Functional Definition of Application Entity (AE) Sequencing Of Real World Activities Application Entity Specifications Common Specifications Content Manager Specification Patient Selection Specification Image Viewer Specification Fusion Application Specification SmartBrush Application Specification Brain Metastases Application Specification Dose Review Application Specification Adaptive Hybrid Surgery Analysis (AHSA) Application Specification Auto Segmentation Performer Specification DICOM RT Export Performer Specification Network Interfaces Physical Network Interface Additional Protocols Media Interchange Implementation Model Application Data Flow Diagram Functional Definitions of AEs Sequencing of Real-World Activities File Meta Information Options AE Specifications Patient Selection Application Entity Specification Augmented and Private Application Profiles Augmented Application Profiles Private Application Profiles Support of Character Sets 49 7 Security Profiles Security Profiles Association Level Security Application Level Security Annexes IOD Contents July 1, 2014 Document Revision 2 Page 7 of 89

8 8.1.1 Supported SOP Instances Supported Modules Usage of Attributes from Received IODs Attribute Mapping Coerced/Modified fields Data Dictionary of Private Attributes Group Group 320B Group Group Group Coded Terminology and Templates TID 2010 Key Object Selection CID 7020 Document Titles CID 7151 Segmentation Property Types Grayscale Image Consistency Standard Extended/Specialized/Private SOP Classes Private Transfer Syntaxes Indexes Index of Tables Index of Figures Page 8 of 89 Document Revision 2 July 1, 2014

9 3 Introduction 3.1 Revision History Document Revision Date of Issue Author Description 2 April 2014 For review 3.2 Audience This document is intended for hospital staff, health system integrators, software designers or implementers. It is assumed that the reader has a working understanding of DICOM. 3.3 Remarks 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. The Conformance Statement should be read and understood in conjunction with the DICOM Standard [2]. However, by itself it is not guaranteed to ensure the desired interoperability and a successful interconnectivity. The user should be aware of the following important issues: The comparison of different Conformance Statements is the first step towards assessing interconnectivity between Brainlab and non Brainlab equipment. This Conformance Statement is not intended to replace validation with other DICOM equipment to ensure proper exchange of information intended. The DICOM standard will evolve to meet the users future requirements. Brainlab reserves the right to make changes to its products or to discontinue its delivery. July 1, 2014 Document Revision 2 Page 9 of 89

10 3.4 Abbreviations There are a variety of terms and abbreviations used in the document that are defined in the DI- COM Standard. Abbreviations and terms are as follows: AE AET CD CD-R DVD FSC FSU FSR HD IOD ISO MOD PDU Q/R RT SCU SCP SOP DICOM Application Entity Application Entity Title Compact Disk Compact Disk Recordable Digital Versatile Disc File-Set Creator File-Set Updater File-Set Reader Hard Disk (DICOM) Information Object Definition International Standard Organization Magneto Optical Disk DICOM Protocol Data Unit Query and Retrieve DICOM Service Class User (DICOM client) DICOM Service Class Provider (DICOM server) DICOM Service-Object Pair 3.5 References [1] Brainlab, DICOM Conformance Statement DICOM Proxy 3.2, Feldkirchen: Brainlab, [2] Digital Imaging and Communications in Medicine (DICOM) 3.0, vol. PS 3, NEMA, [3] Brainlab, DICOM Conformance Statement DICOM Proxy 3.1, Feldkirchen: Brainlab, [4] IHE, IHE RO Technical Framework: Multimodality Image Registration for Radiation Oncology, IHE, [5] Varian, Varian System Server DICOM Conformance Statement, Varian, Page 10 of 89 Document Revision 2 July 1, 2014

11 4 Networking 4.1 Implementation Model Application Data Flow Diagram DICOM Proxy Query for Patients, Studies and Series Patient Selection Remote Performs Query/Retrieve DICOM Standard Interface Figure 4-1: Patient Selection Application Data Flow Diagram Brainlab applications in general support several data flows. Either they receive any DICOM data to display it, to process it and/or to create new DICOM data. Display DICOM Proxy Remote Sends Data Process Brainlab Application Remote Receives Data Create DICOM Standard Interface Figure 4-2: General Application Data Flow Diagram July 1, 2014 Document Revision 2 Page 11 of 89

12 Brainlab Performers only have one data flow. They process received DICOM data and create new DICOM data out of it. DICOM Proxy Process Remote Sends Data Brainlab Performer Create Remote Receives Data DICOM Standard Interface Figure 4-3: General Performer Data Flow Diagram Functional Definition of Application Entity (AE) All communication is done through the DICOM Proxy except for the Brain Metastases Application that can directly send data to a remote node, configured within the application s export platforms. If there is an appropriate configuration for a remote node any DICOM command or message may be forwarded to the configured remote node. In this case the DICOM Proxy may act as protocol converter, i.e., it converts DICOM commands and messages in a DICOM format the remote node understands. If there is no remote node configured the data will be retrieved from and stored in the local storage of the DICOM Proxy Applications Management Applications Content Manager It allows the user to create screenshots. It stores them via the DICOM Storage Service Class as DICOM Secondary Capture Applications Patient Selection It allows the user to query remote archives using the DICOM Query/Retrieve FIND SOP Classes and to retrieve data using the DICOM Query/Retrieve GET SOP Class to generate previews. Page 12 of 89 Document Revision 2 July 1, 2014

13 Image Viewer It displays all kind of DICOM image data received via the DICOM Storage Service Class. Additionally it is able to save changes, e.g., changes to the VOI LUT as Grayscale Presentation State. Fusion It allows the user to create or change spatial registrations between different volumetric image sets received via the DICOM Storage Service Class. Smartbrush It allows the user to create or change DICOM Segmentation instances based on loaded image sets received via the DICOM Storage Service Class. Additionally, it can save volumetric reports as DICOM Encapsulated PDF. Brain Metastases The Brain Metastases application provides optimized planning and display for cranial multimetastases radiation planning. It requests DICOM image, Segmentation and Registration instances received via the DICOM Storage Service Class. It creates DICOM RT Structure Set, RT Plan and RT Dose instances and sends these along the image instances to a defined target system. Dose Review The Dose Review application contains features for review of isodose lines, review of DVHs, dose comparison and summation. It requests DICOM image, Registration, RT Structure Set, RT Plan and RT Dose instances received via the DICOM Storage Service Class. It does not create any new DICOM instances. Adaptive Hybrid Surgery Analysis The Adaptive Hybrid Surgery Analysis application simulates an automated template-based radiation treatment plan based on DICOM image, Segmentation and Registration instances received via the DICOM Storage Service Class Performer Auto Segmentation Background service to create organ segmentations based on DICOM volumetric image sets received via the DICOM Storage Service Class. DICOM RT Export Background service to create vessel segmentations based on DICOM volumetric image sets received via the DICOM Storage Service Class. July 1, 2014 Document Revision 2 Page 13 of 89

14 4.1.3 Sequencing Of Real World Activities Standard Interactive Use Case In the standard use case normally the user selects a patient in the Patient Selection Application or some data to work with (1). Afterwards, the application is started (2) and requests the data (3). The DICOM Proxy retrieves from the configured remote nodes 1 the requested data (4) and passes it through to the requesting application (5). If the application creates any data it optionally will be sent to a remote system (6). Patient Selection Application DICOM Proxy Remote System (1) Query/Retrieve C-FIND (2) Invoke Application (3) Query/Retrieve C-GET (4) Query/Retrieve C-MOVE/GET loop (5) Storage C-STORE Whether created instances shall be stored depends on the application opt (6) Storage C-STORE Figure 4-4: Simplified sequencing of the standard interactive use case. The sequencing is not only possible between the Patient Selection and an Application but also between two or more different applications, i.e., it is possible to build a chain of applications, each performing a special task. This chain then is controlled by the Content Manager Performer In general a performer is invoked as soon as new data arrives at the DICOM Proxy (1). Via internal communication (not part of this Conformance Statement) the Performer is informed about the new data and - if it is able to process the data requests it (3,4). The Performer processes the data (5) and, if the Performer creates new instances, it can send the created data to the DI- COM Proxy, which may automatically forward it to a remote node (6). 1 The DICOM Proxy adjusts all queries to the addressed remote node, e.g., it automatically converts Query/Retrieve C-GET requests for nodes not supporting this command to C-MOVE requests. Page 14 of 89 Document Revision 2 July 1, 2014

15 Performer DICOM Proxy Remote System 1 Remote System 2 (1) Storage C-STORE ref (2) Notification (3) Query/Retrieve C-GET Internal mechanisms beyond the scope of this Conformance Statement loop (4) Storage C-STORE (5) Any Performer Action opt (6) Storage C-STORE Figure 4-5: Simplified sequencing of Performer activities. July 1, 2014 Document Revision 2 Page 15 of 89

16 4.2 Application Entity Specifications Common Specifications This section describes the specifications valid for all application entities in this Conformance Statement. In successive application entity sections only the differences or additional information will be described SOP Classes and Transfer Syntaxes This section only describes commonly used SOP Classes and Transfer Syntaxes. Whether they supported as SCU or SCP will be described in the sub sections of the appropriate application entity. In the following table all transfer syntaxes supported by any of the applications are listed: List Name / Transfer Syntax Name Transfer Syntax List With No Compression List Short Name / Transfer Syntax UID NOCOMP DICOM Explicit VR Little Endian DICOM Explicit VR Big Endian DICOM Implicit VR Little Endian Transfer Syntax List With Lossless Compression Include Transfer Syntax List NOCOMP COMP JPEG Lossless, Non-Hierarchical, First-Order Prediction (Process 14) RLE Lossless Transfer Syntax List with RLE Compression RLE Lossless Include Transfer Syntax List NOCOMP RLE IMPL DICOM Implicit VR Little Endian Transfer Syntax List With Lossy Compression Include Transfer Syntax List NOCOMP LOSSY JPEG Baseline (Process 1) Table 4-1: Commonly supported Transfer Syntaxes (for association negotiation) The transfer syntaxes are organized in so-called transfer syntax lists. For each presentation context specified by an application or performer, the name respectively short sign of the transfer syntax list is mentioned instead of repeating all the transfer syntaxes. Some applications and performers support the DICOM Storage Service Class. The following table contains the superset of supported Storage SOP Classes with the mapping to the accepted respectively proposed transfer syntax list. SOP Class Name Image Storage SOP Classes SOP Class UID Transfer Syntax List Breast Tomosynthesis Image Storage COMP Page 16 of 89 Document Revision 2 July 1, 2014

17 SOP Class Name SOP Class UID Transfer Syntax List Computed Radiography Image Storage COMP CT Image Storage COMP Digital Intra-oral X-Ray Image Storage - For Presentation COMP Digital Intra-oral X-Ray Image Storage - For Processing COMP Digital Mammography X-Ray Image Storage - For Presentation COMP Digital Mammography X-Ray Image Storage - For Processing COMP Digital X-Ray Image Storage - For Presentation COMP Digital X-Ray Image Storage - For Processing COMP Enhanced CT Image Storage COMP Enhanced MR Color Image Storage COMP Enhanced MR Image Storage COMP Enhanced PET Image Storage COMP Enhanced US Volume Storage COMP Enhanced XA Image Storage COMP Enhanced XRF Image Storage COMP Intravascular Optical Coherence Tomography Image Storage - For Presentation Intravascular Optical Coherence Tomography Image Storage - For Processing COMP COMP MR Image Storage COMP MR Spectroscopy Storage COMP Multi-frame Grayscale Byte Secondary Capture Storage COMP Multi-frame Grayscale Word Secondary Capture Storage COMP Multi-frame Single Bit Secondary Capture Storage COMP Multi-frame True Color Secondary Capture Storage LOSSY Nuclear Medicine Image Storage COMP Nuclear Medicine Image Storage (Retired) COMP Ophthalmic Photography 16 Bit Image Storage COMP Ophthalmic Photography 8 Bit Image Storage COMP Ophthalmic Tomography Image Storage COMP Positron Emission Tomography Image Storage COMP Secondary Capture Image Storage COMP Ultrasound Image Storage COMP Ultrasound Image Storage (Retired) COMP Ultrasound Multi-frame Image Storage COMP Ultrasound Multi-frame Image Storage (Retired) COMP Video Endoscopic Image Storage MPEG2 Video Microscopic Image Storage MPEG2 Video Photographic Image Storage MPEG2/MPEG4 VL Endoscopic Image Storage COMP VL Microscopic Image Storage COMP July 1, 2014 Document Revision 2 Page 17 of 89

18 SOP Class Name SOP Class UID Transfer Syntax List VL Photographic Image Storage COMP VL Slide-Coordinates Microscopic Image Storage COMP VL Whole Slide Microscopy Image Storage COMP X-Ray 3D Angiographic Image Storage COMP X-Ray 3D Craniofacial Image Storage COMP X-Ray Angiographic Bi-Plane Image Storage (Retired) COMP X-Ray Angiographic Image Storage COMP X-Ray Radiofluoroscopic Image Storage COMP Non-Image Storage SOP Classes Encapsulated PDF Storage NOCOMP Grayscale Softcopy Presentation State Storage NOCOMP Key Object Selection Document Storage NOCOMP Raw Data Storage NOCOMP RT Dose Storage IMPL RT Plan Storage IMPL 2 RT Structure Set Storage IMPL 2 Segmentation Storage RLE Spatial Fiducials Storage NOCOMP Spatial Registration Storage NOCOMP Surface Segmentation Storage NOCOMP Table 4-2: Commonly supported Storage SOP Classes with Transfer Syntax mapping Some applications and performers support the DICOM Query/Retrieve Service Class. The following table contains the superset of supported Query/Retrieve SOP Classes with the mapping to the accepted respectively proposed transfer syntax list. SOP Class Name FIND SOP Classes SOP Class UID Transfer Syntax List Patient Root Query/Retrieve Information Model FIND NOCOMP Study Root Query/Retrieve Information Model FIND NOCOMP GET SOP Classes Patient Root Query/Retrieve Information Model GET NOCOMP Study Root Query/Retrieve Information Model GET NOCOMP Table 4-3: Commonly supported Query/Retrieve SOP Classes with Transfer Syntax mapping The usage of these SOP Classes is specified in the sections with the detailed application specifications. 2 RT Dose, RT Plan and RT Structure Set Instances contain attributes with a VR of DS and a VM of 1-n (e.g., Contour Data (3006,0050) in RT Structure Sets). Implicit Little Endian transfer syntax allows storing of those attributes with a doubled length in comparison to explicit transfer syntax (4 byte length field vs. 2 byte length field). Page 18 of 89 Document Revision 2 July 1, 2014

19 Association Policies General The DICOM standard application context name for DICOM 3.0 is always proposed: Application Context Name Table 4-4: Commonly proposed Application Context Name Number of Associations Maximum number of simultaneous Associations (Initiator) Maximum number of simultaneous Associations (Acceptor) 10 (configurable) 10 (configurable) Table 4-5: Commonly supported number of associations Asynchronous Nature Applications or performers by default do not support asynchronous communication (multiple outstanding transactions over a single association). However if it is supported it is mentioned in the section of the affected application entity Implementation Identifying Information The implementation information for the application entities described in this document normally is hidden by the Brainlab DICOM Proxy (see [1] for its implementation identifying information). Therefore this information in the sections of the different application entities is purely informational Association Initiation Policy Brainlab applications and performers initiate associations in these cases: Find Studies, Series and Instances Initiated by applications and performers to find related studies, series and instances Get Studies, Series and Instances Initiated by applications and performers to retrieve related studies, series and instances If one of these activities is supported it is mentioned in the subsection of the appropriate application entity Activity Find Studies, Series and Instances Description and Sequencing of Activities Brainlab applications or performers initiate an association with the intention to find studies, series or instances and to retrieve them, e.g., because they are related to or referenced by a loaded data set. July 1, 2014 Document Revision 2 Page 19 of 89

20 Proposed Presentation Contexts Patient Root Query/Retrieve Information Model - FIND Study Root Query/Retrieve Information Model FIND Presentation Context Table Abstract Syntax Transfer Syntax Role Ext. Neg See Table 4-3 for the SOP Class / Transfer Syntax mapping Table 4-6: Commonly proposed Presentation Contexts - Find Studies, Series and Instances. SCU None SOP Specific Conformance Brainlab applications and performers provide standard conformance to the Patient and Study Root Query/Retrieve Information Model FIND SOP Classes. No extended negotiation is implemented. A C-FIND can be executed on all levels. On a lower level, all key attributes of the higher levels are included in the query (i.e. no relational queries are performed). Attribute Name Tag Types of Matching Patient Level (Patient Root Q/R Information Model) / Study Level (Study Root Q/R Information Model) Patient s Name (0010,0010) S, *, U Patient ID (0010,0020) S, *, U Patient's Birth Date (0010,0030) U Patient's Sex (0010,0040) U Study Level Study Date (0008,0020) S, R, U Accession Number (0008,0050) S, *, U Referring Physician's Name (0008,0090) S, *, U Study Instance UID (0020,000D) UNIQUE Study Time (0008,0030) U Study Description (0008,1030) U Modalities in Study (0008,0061) U SOP Classes in Study (0008,0062) U Number of Study Related Series (0020,1206) U Series Level Series Instance UID (0020,000E) UNIQUE Series Number (0020,0011) U Series Description (0008,103E) U Series Date (0008,0020) U Series Time (0008,0021) U Modality (0008,0060) U No. of Series Rel. Instances (0020,1209) U Instance Level SOP Instance UID (0008,0018) UNIQUE SOP Class UID (0008,0016) U Page 20 of 89 Document Revision 2 July 1, 2014

21 Attribute Name Tag Types of Matching Instance Number (0020,0013) U Instance Creation Date (0008,0012) U Instance Creation Time (0008,0013) U Arbitrary Search Keys as Requested by the Client * U Table 4-7: Patient Root and Study Root Request Identifier for FIND-SCU The types of Matching supported by the C-FIND SCU: S Single value matching R Range matching * Wildcard matching U Universal matching L UID list matching UNIQUE The unique key for the query level, (i.e. single value matching for levels below the current query level, either universal or single value matching for the current query level) Activity Get Studies, Series and Instances Description and Sequencing of Activities If the find operation doesn t provide icons for queried instances the Patient Selection automatically retrieves the instances and creates previews Proposed Presentation Contexts Patient Root Query/Retrieve Information Model - GET Study Root Query/Retrieve Information Model - GET Presentation Context Table Abstract Syntax Transfer Syntax Role Ext. Neg See Table 4-3 for the SOP Class / Transfer Syntax mapping All SCP Storage SOP Classes and SOP Class UIDs as defined in the respective application or performer specification See Table 4-2 for the SOP Class / Transfer Syntax mapping SCU SCP Table 4-8: Patient Selection proposed Presentation Contexts Find Patient None None SOP Specific Conformance The Patient Selection provides standard conformance to the DICOM Patient and Study Root Query/Retrieve - GET SOP Class and to the DICOM Storage SOP Classes. No extended negotiation is implemented Association Acceptance Policy Brainlab applications and performers do not directly accept associations. All external communication is handled by the DICOM Proxy (see [3] for details). Nevertheless in the sub sections of the different application entities the association acceptance will be described to define the SOP Classes they support. July 1, 2014 Document Revision 2 Page 21 of 89

22 Transfer Syntax Selection Policy Brainlab applications and performers in general accept transfer syntaxes in with no compression (explicit before implicit) before those with lossless compression and at least those with lossy compression. At least the order of the transfer syntaxes in the assigned transfer syntax list is the order of acceptance. Page 22 of 89 Document Revision 2 July 1, 2014

23 4.2.2 Content Manager Specification The Content Manager manages applications on Brainlab systems. It allows a user to create and read screenshots SOP Classes and Transfer Syntaxes The Content Manager provides standard conformance to the following SOP Classes: SOP Class Name SOP Class UID SCU SCP Multi Frame True Color SC Image Yes No Table 4-9: SOP Classes supported by the Content Manager Association Policies Implementation Identifying Information The implementation information for this Application Entity is: Implementation Class UID Implementation Version Name <version> ContentManager Current possible versions are: <version> = Association Initiation Policy The Content Manager initiates an association in this case: Save Instances: Initiated to store created screenshots as secondary capture Activity Save Instances Description and Sequencing of Activities The user creates a screenshot. This screenshot is saved to the DICOM Proxy as Multi-frame True Color SC Image Proposed Presentation Contexts Presentation Context Table Abstract Syntax Transfer Syntax Role Ext. Neg Multi Frame True Color SC Image See Table 4-2 for the SOP Class / Transfer Syntax mapping Table 4-10: Content Manager proposed Presentation Contexts Save Instances SCU None SOP Specific Conformance The Content Manager provides standard conformance to the DICOM Storage SOP Classes. July 1, 2014 Document Revision 2 Page 23 of 89

24 4.2.3 Patient Selection Specification The Patient Selection allows the user to browse, import or export data in/to DICOM archives or on/to media (e.g., CD-ROM) SOP Classes and Transfer Syntaxes The Patient Selection provides standard conformance to the following SOP Classes: SOP Class Name SOP Class UID SCU SCP Storage All Image Storage SOP Classes and associated SOP Class UIDs as listed in Table 4-2 No Yes Key Object Selection Document Yes Yes Segmentation Storage No Yes Query/Retrieve Patient Root Query/Retrieve Information Model - FIND Yes No Patient Root Query/Retrieve Information Model - GET Yes No Study Root Query/Retrieve Information Model FIND Yes No Study Root Query/Retrieve Information Model GET Yes No Table 4-11: SOP Classes supported by the Patient Selection Association Policies Implementation Identifying Information The implementation information for this Application Entity is: Implementation Class UID Implementation Version Name <version> PatientSelection Current possible versions are: <version> = Association Initiation Policy The Patient Selection initiates an association in these cases: Find Patient The user searches for a patient and related data. Display Preview During the search, for all queried instances, previews will be generated. If the find operation doesn t provide an appropriate preview icon, the instances will be retrieved and a preview will be created. Store Series Information: Key Object Selection instances are created to persist either plan information for a group of series or internal information about one series. Page 24 of 89 Document Revision 2 July 1, 2014

25 Activity Find Patient See Error! Reference source not found., section (Activity Find Studies, Series and Instances) Activity Display Preview See Error! Reference source not found., section (Activity Get Studies, Series and Instances), using Patient and Study Root Query/Retrieve Information Model GET and restricted to all SCP Storage SOP Classes and SOP Class UIDs as listed in Error! Reference source not found Activity Store Series Information Description and Sequencing of Activities For each series in a patient selected for further treatment the Patient Selection creates a Key Object Selection instance containing internal information. This KOS instance then is stored in the DICOM Proxy to be available for other applications and performers Proposed Presentation Contexts Presentation Context Table Abstract Syntax Transfer Syntax Role Ext. Neg Key Object Selection Document See Table 4-2 for the SOP Class / Transfer Syntax mapping Table 4-12: Patient Selection proposed Presentation Contexts Store Series Information SCU None SOP Specific Conformance The Patient Selection provides standard conformance to the DICOM Storage SOP Classes July 1, 2014 Document Revision 2 Page 25 of 89

26 4.2.4 Image Viewer Specification The Image Viewer Allows the user to display any kind of DICOM image data SOP Classes and Transfer Syntaxes The Image Viewer accepts the following SOP Classes for viewing: SOP Class Name SOP Class UID SCU SCP Storage All Image Storage SOP Classes and associated SOP Class UIDs as listed in Table 4-2 No Yes Encapsulated PDF No Yes Grayscale Softcopy Presentation State Yes Yes Key Object Selection Document No Yes Raw Data Yes Yes Segmentation Storage No Yes Spatial Registration Yes Yes Surface Segmentation Storage Yes Yes Query/Retrieve Study Root Query/Retrieve Information Model FIND Yes No Study Root Query/Retrieve Information Model GET Yes No Table 4-13: Image Viewer supported SOP Classes Association Policies Implementation Identifying Information The implementation information for this Application Entity is: Implementation Class UID Implementation Version Name <version> ImageViewer Current possible versions are: <version> = Association Initiation Policy The Image Viewer initiates an association in these cases: Find Studies, Series and Instances Initiated to find related studies, series and instances Get Studies, Series and Instances Initiated to retrieve related studies, series and instances Save Instances: The user created a new instance Activity Find Studies, Series and Instances See Error! Reference source not found., section Page 26 of 89 Document Revision 2 July 1, 2014

27 Activity Get Studies, Series and Instances See Error! Reference source not found., section , restricted to Study Root Query/Retrieve Information Model GET and to all SCP Storage SOP Classes and SOP Class UIDs as listed in Table Activity Save Instances Description and Sequencing of Activities The user created a new instance: A new VOI LUT for a series. Will be stored as Grayscale Presentation State. A new Spatial Registration. A kind of nd-presentation State to re-display a series in 3D. Will be stored as Raw Data. A new trajectory. Will be stored as Surface Segmentation Proposed Presentation Contexts Presentation Context Table Abstract Syntax Transfer Syntax Role Ext. Neg All SCU Storage SOP Classes and SOP Class UIDs as listed in Table 4-13 See Table 4-2 for the SOP Class / Transfer Syntax mapping Table 4-14: Patient Selection proposed Presentation Contexts Store Instances SCU None SOP Specific Conformance The Image Viewer provides standard conformance to the DICOM Storage SOP Classes Activity Find Studies, Series and Instances See section July 1, 2014 Document Revision 2 Page 27 of 89

28 4.2.5 Fusion Application Specification The Fusion Application allows the user to overlap two different DICOM data sets SOP Classes and Transfer Syntaxes The Fusion Application accepts the following SOP Classes: SOP Class Name SOP Class UID SCU SCP Volumetric Images CT Image No Yes Enhanced CT Image No Yes Enhanced MR Image No Yes Multi Frame Grayscale Byte SC Image No Yes Multi Frame Grayscale Word SC Image No Yes Multi Frame Single Bit SC Image No Yes Multi Frame True Color SC Image No Yes MR Image No Yes NM Image No Yes NM Image Retired No Yes PET Image No Yes X-Ray 3D Angiographic Image No Yes X-Ray 3D Craniofacial Image No Yes Volumetric Other Spatial Registration Yes Yes Other Grayscale Softcopy Presentation State No Yes Key Object Selection Document No Yes Query/Retrieve Study Root Query/Retrieve Information Model FIND Yes No Study Root Query/Retrieve Information Model GET Yes No Table 4-15: Fusion Application supported SOP Classes Association Policies Implementation Identifying Information The implementation information for this Application Entity is: Implementation Class UID Implementation Version Name <version> ImageFusion Current possible versions are: <version> = Association Initiation Policy The Fusion Application initiates an association in these cases: Page 28 of 89 Document Revision 2 July 1, 2014

29 Find Studies, Series and Instances Initiated to find related studies, series and instances Get Studies, Series and Instances Initiated to retrieve related studies, series and instances Save Fusion: The user created a new spatial registration Activity Find Studies, Series and Instances See Error! Reference source not found., section Activity Get Studies, Series and Instances See Error! Reference source not found., section , restricted to Study Root Query/Retrieve Information Model GET and to all SCP Storage SOP Classes and SOP Class UIDs as listed in Table Activity Save Fusion Description and Sequencing of Activities The user created a spatial registration Proposed Presentation Contexts Presentation Context Table Abstract Syntax Transfer Syntax Role Ext. Neg Spatial Registration See Table 4-2 for the SOP Class / Transfer Syntax mapping Table 4-16: Fusion Application proposed Presentation Contexts Save Fusion SCU None SOP Specific Conformance The Fusion Application provides standard conformance to the DICOM Storage SOP Classes. July 1, 2014 Document Revision 2 Page 29 of 89

30 4.2.6 SmartBrush Application Specification The SmartBrush Application allows the user to create, read and update segmentations based on DICOM image data SOP Classes and Transfer Syntaxes The SmartBrush Application accepts the following SOP Classes: SOP Class Name SOP Class UID SCU SCP Volumetric Images CT Image No Yes Enhanced CT Image No Yes Enhanced MR Image No Yes MR Image No Yes Multi Frame Grayscale Byte SC Image No Yes Multi Frame Grayscale Word SC Image No Yes Multi Frame Single Bit SC Image No Yes Multi Frame True Color SC Image No Yes NM Image No Yes NM Image Retired No Yes PET Image No Yes X-Ray 3D Angiographic Image No Yes X-Ray 3D Craniofacial Image No Yes Volumetric Other Segmentation Storage Yes Yes Spatial Registration No Yes Other Encapsulated PDF Storage Yes Yes Grayscale Softcopy Presentation State No Yes Key Object Selection Document No Yes Query/Retrieve Study Root Query/Retrieve Information Model FIND Yes No Study Root Query/Retrieve Information Model GET Yes No Table 4-17: SmartBrush Application supported SOP Classes Association Policies Implementation Identifying Information The implementation information for this Application Entity is: Implementation Class UID Implementation Version Name <version> Smartbrush Current possible versions are: <version> = 2.0 Page 30 of 89 Document Revision 2 July 1, 2014

31 Association Initiation Policy The SmartBrush Application initiates an association in these cases: Find Studies, Series and Instances Initiated to find related studies, series and instances Get Studies, Series and Instances Initiated to retrieve related studies, series and instances Save Segmentation: The user created a new or updated an existing segmentation and/or creates a volumetric report Activity Find Studies, Series and Instances See Error! Reference source not found., section Activity Get Studies, Series and Instances See Error! Reference source not found., section , restricted to Study Root Query/Retrieve Information Model GET and to all SCP Storage SOP Classes and SOP Class UIDs as listed in Table Activity Save Segmentation Description and Sequencing of Activities New instances will be created if the user draws new or updates existing objects in an image set. Will be stored as Segmentation. creates a volumetric report. Will be stored as Encapsulated PDF Proposed Presentation Contexts Presentation Context Table Abstract Syntax Transfer Syntax Role Ext. Neg Segmentation Storage See Table 4-2 for the SOP Class / Transfer Encapsulated PDF Storage Syntax mapping Table 4-18: SmartBrush Application proposed Presentation Contexts Save Segmentation SCU None SOP Specific Conformance The SmartBrush Application provides standard conformance to the DICOM Storage SOP Classes. July 1, 2014 Document Revision 2 Page 31 of 89

32 4.2.7 Brain Metastases Application Specification The Brain Metastases application provides optimized planning and display for cranial multimetastases radiation planning. It requests DICOM image, Segmentation and Registration instances from the DICOM Proxy. It creates DICOM RT Structure Set, RT Plan and RT Dose instances and sends these along the image instances to a defined target system SOP Classes and Transfer Syntaxes The Brain Metastases Application accepts the following SOP Classes: SOP Class Name SOP Class UID SCU SCP Storage CT Image Yes Yes MR Image No Yes PET Image No Yes Volumetric Other Segmentation Storage No Yes Spatial Registration No Yes RT Dose Yes No RT Plan Yes No RT Structure Set Yes No Query/Retrieve Study Root Query/Retrieve Information Model FIND Yes No Study Root Query/Retrieve Information Model GET Yes No Table 4-19: Brain Metastases Application supported SOP Classes Association Policies Implementation Identifying Information The implementation information for this Application Entity is: Implementation Class UID Implementation Version Name <version> BrainMets1.0 Current possible versions are: <version> = Association Initiation Policy The Brain Metastases Application initiates an association in these cases: Find Studies, Series and Instances Initiated to find related studies, series and instances Get Studies, Series and Instances Initiated to retrieve related studies, series and instances Page 32 of 89 Document Revision 2 July 1, 2014

33 Save Instances The user created a new radiotherapy treatment plan Activity Find Studies, Series and Instances See Error! Reference source not found., section Activity Get Studies, Series and Instances See Error! Reference source not found., section , restricted to Study Root Query/Retrieve Information Model GET and to all SCP Storage SOP Classes and SOP Class UIDs as listed in Table Activity Save Instances Description and Sequencing of Activities After creating a radiotherapy treatment plan the user requests storage of this plan Proposed Presentation Contexts Presentation Context Table Abstract Syntax Transfer Syntax Role Ext. Neg All SCU Storage SOP Classes and SOP Class UIDs as listed in Table 4-19 See Table 4-2 for the SOP Class / Transfer Syntax mapping SCU None Table 4-20: Brain Metastases Application proposed Presentation Contexts Save Instances SOP Specific Conformance The Brain Metastases Application provides standard conformance to the DICOM Storage SOP Classes. July 1, 2014 Document Revision 2 Page 33 of 89

34 4.2.8 Dose Review Application Specification The Dose Review application contains features for review of isodose lines, review of DVHs, dose comparison and summation. It requests DICOM image, Registration, RT Structure Set, RT Plan and RT Dose instances from the DICOM Proxy. It does not create any new DICOM instances SOP Classes and Transfer Syntaxes The Brain Metastases Application accepts the following SOP Classes: SOP Class Name SOP Class UID SCU SCP Storage CT Image Yes Yes MR Image No Yes PET Image No Yes Volumetric Other Spatial Registration No Yes RT Dose No Yes RT Plan No Yes RT Structure Set No Yes Query/Retrieve Study Root Query/Retrieve Information Model FIND Yes No Study Root Query/Retrieve Information Model GET Yes No Table 4-21: Dose Review Application supported SOP Classes Association Policies Implementation Identifying Information The implementation information for this Application Entity is: Implementation Class UID Implementation Version Name <version> DoseReview1.0 Current possible versions are: <version> = Association Initiation Policy The Brain Metastases Application initiates an association in these cases: Find Studies, Series and Instances Initiated to find related studies, series and instances Get Studies, Series and Instances Initiated to retrieve related studies, series and instances Activity Find Studies, Series and Instances See Error! Reference source not found., section Page 34 of 89 Document Revision 2 July 1, 2014