Compass is a software application which receives and optionally sends medical instances. It implements the necessary DICOM services to receive those ...
Compass DICOM Conformance Statement - v3.3.1 – Page 2 of 47 LAUREL BRIDGE SOFTWARE, INC. 500 CREEK VIEW ROAD SUITE 200 NEWARK, DE 19711 TEL: 302-453-0222 FAX: 302-453-9480 WWW.LAURELBRIDGE.COM
DICOM 3.0 Conformance Statement for Compass Orchestrating Medical Imaging Workflow Laurel Bridge Software, Inc. 302-453-0222 500 Creek View Rd, Suite 200 Newark, DE 19711 info@laurelbridge.com www.laurelbridge.com Document Version: 3.3.1 Document Number: LBDC-000078-030301 Last Saved: 8/13/2021 10:22:00 AM Copyright 2021, Laurel Bridge Software, Inc. All Rights Reserved LAUREL BRIDGE SOFTWARE, INC. 500 CREEK VIEW ROAD SUITE 200 NEWARK, DE 19711 TEL: 302-453-0222 FAX: 302-453-9480 WWW.LAURELBRIDGE.COM Compass DICOM Conformance Statement - v3.3.1 Page 2 of 47 1. Conformance Statement Overview Compass is a software application which receives and optionally sends medical instances. It implements the necessary DICOM services to receive those instances from other DICOM entities, and then send those instances to other DICOM entities. Table 1-1 provides an overview of the DICOM network services supported by Compass. Table 1-1 Network Services SOP Classes User of Service (SCU) Provider of Service (SCP) Transfer Computed Radiography Image Storage Yes Yes Digital X-Ray Image Storage - For Presentation Yes Yes Digital X-Ray Image Storage - For Processing Yes Yes Digital Mammography X-Ray Image Storage - For Yes Yes Presentation Digital Mammography X-Ray Image Storage - For Yes Yes Processing Digital Intra-oral X-Ray Image Storage - For Yes Yes Presentation Digital Intra-oral X-Ray Image Storage - For Yes Yes Processing CT Image Storage Yes Yes Enhanced CT Image Storage Yes Yes Ultrasound Multi-frame Image Storage Yes Yes MR Image Storage Yes Yes Enhanced MR Image Storage Yes Yes MR Spectroscopy Storage Yes Yes Nuclear Medicine Image Storage Yes Yes Ultrasound Image Storage Yes Yes Secondary Capture Image Storage Yes Yes Multi-frame Single Bit Secondary Capture Image Yes Yes Storage Multi-frame Grayscale Byte Secondary Capture Yes Yes Image Storage Multi-frame Grayscale Word Secondary Capture Yes Yes Image Storage Multi-frame True Color Secondary Capture Image Yes Yes Storage Standalone Overlay Storage (Retired) Yes Yes Standalone Curve Storage (Retired) Yes Yes Standalone Modality LUT Storage (Retired) Yes Yes LAUREL BRIDGE SOFTWARE, INC. 500 CREEK VIEW ROAD SUITE 200 NEWARK, DE 19711 TEL: 302-453-0222 FAX: 302-453-9480 WWW.LAURELBRIDGE.COM Compass DICOM Conformance Statement - v3.3.1 Page 3 of 47 SOP Classes Standalone VOI LUT Storage (Retired) User of Service (SCU) Provider of Service (SCP) Grayscale Softcopy Presentation State Storage Yes Yes SOP Class Color Softcopy Presentation State Storage SOP Yes Yes Class Pseudo-Color Softcopy Presentation State Storage Yes Yes SOP Class Blending Softcopy Presentation State Storage SOP Yes Yes Class X-Ray Angiographic Image Storage Yes Yes X-Ray Radiofluoroscopic Image Storage Yes Yes Raw Data Storage Yes Yes Spatial Registration Storage Yes Yes Spatial Fiducials Storage Yes Yes Twelve Lead ECG Waveform Storage Yes Yes General ECG Waveform Storage Yes Yes Ambulatory ECG Waveform Storage Yes Yes Hemodynamic Waveform Storage Yes Yes Cardiac Electrophysiology Waveform Storage Yes Yes Basic Voice Audio Waveform Storage Yes Yes VL Endoscopic Image Storage Yes Yes Video Endoscopic Image Storage Yes Yes VL Microscopic Image Storage Yes Yes Video Microscopic Image Storage Yes Yes VL Slide-Coordinates Microscopic Image Storage Yes Yes VL Photographic Image Storage Yes Yes Video Photographic Image Storage Yes Yes Ophthalmic Photography 8 Bit Image Storage Yes Yes Ophthalmic Photography 16 Bit Image Storage Yes Yes Stereometric Relationship Storage Yes Yes Basic Text SR Storage Yes Yes Enhanced SR Storage Yes Yes Comprehensive SR Storage Yes Yes Procedure Log Storage Yes Yes Mammography CAD SR Storage Yes Yes Key Object Selection Document Storage Yes Yes Chest CAD SR Storage Yes Yes LAUREL BRIDGE SOFTWARE, INC. 500 CREEK VIEW ROAD SUITE 200 NEWARK, DE 19711 TEL: 302-453-0222 FAX: 302-453-9480 WWW.LAURELBRIDGE.COM SOP Classes X-Ray Radiation Dose SR Storage Positron Emission Tomography Image Storage Standalone PET Curve Storage (Retired) 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 Enhanced XA Image Storage Enhanced XRF Image Storage Encapsulated PDF Storage Enhanced MR Color Image Storage Enhanced US Volume Storage General Audio Waveform Storage Arterial Pulse Waveform Storage Respiratory Waveform Storage XA/XRF Grayscale Softcopy Presentation State Storage Breast Tomosynthesis Image Storage Surface Segmentation Storage Lensometry Measurements Storage Autorefraction Measurements Storage Keratometry Measurements Storage Subjective Refraction Measurements Storage Visual Acuity Measurements Storage Spectacle Prescription Reports Storage Macular Grid Thickness and Volume Report Storage Colon CAD SR Storage Enhanced PET Image Storage Basic Structured Display Storage Color Palette Storage Intravascular Optical Coherence Tomography Image Storage - For Presentation Compass DICOM Conformance Statement - v3.3.1 Page 4 of 47 User of Service (SCU) Yes Provider of Service (SCP) Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes LAUREL BRIDGE SOFTWARE, INC. 500 CREEK VIEW ROAD SUITE 200 NEWARK, DE 19711 TEL: 302-453-0222 FAX: 302-453-9480 WWW.LAURELBRIDGE.COM SOP Classes Intravascular Optical Coherence Tomography Image Storage - For Processing VL Whole Slide Microscopy Image Storage Ophthalmic Axial Measurements Storage Intraocular Lens Calculations Storage Ophthalmic Visual Field Static Perimetry Measurements Storage Implantation Plan SR Storage DICOS CT Image Storage DICOS Digital X-Ray Image Storage - For Presentation DICOS Digital X-Ray Image Storage - For Processing DICOS Threat Detection Report Storage Eddy Current Image Storage Eddy Current Multi-frame Image Storage RT Beams Delivery Instruction Storage Generic Implant Template Storage Implant Assembly Template Storage Implant Template Group Storage Query/Retrieve Patient Root Query/Retrieve Information Model FIND Patient Root Query/Retrieve Information Model MOVE Patient Root Query/Retrieve Information Model GET Study Root Query/Retrieve Information Model FIND Study Root Query/Retrieve Information Model MOVE Study Root Query/Retrieve Information Model GET Patient/Study Only Query/Retrieve Information Model - FIND (Retired) Patient/Study Only Query/Retrieve Information Model - MOVE (Retired) Workflow Management Storage Commitment Modality Worklist Information Model - FIND Modality Performed Procedure Step SOP Class Compass DICOM Conformance Statement - v3.3.1 Page 5 of 47 User of Service (SCU) Yes Provider of Service (SCP) Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes LAUREL BRIDGE SOFTWARE, INC. 500 CREEK VIEW ROAD SUITE 200 NEWARK, DE 19711 TEL: 302-453-0222 FAX: 302-453-9480 WWW.LAURELBRIDGE.COM SOP Classes Verification Print Management Basic Grayscale Print Management Meta SOP Class Print Job SOP Class Basic Annotation Box SOP Class Printer SOP Class Basic Color Print Management Meta SOP Class Presentation LUT SOP Class Basic Print Image Overlay Box SOP Class (Retired) Compass DICOM Conformance Statement - v3.3.1 Page 6 of 47 User of Service (SCU) Yes Provider of Service (SCP) Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes LAUREL BRIDGE SOFTWARE, INC. 500 CREEK VIEW ROAD SUITE 200 NEWARK, DE 19711 TEL: 302-453-0222 FAX: 302-453-9480 WWW.LAURELBRIDGE.COM Compass DICOM Conformance Statement - v3.3.1 Page 7 of 47 2. Table of Contents 1. Conformance Statement Overview........................................................................................................................2 2. Table of Contents .................................................................................................................................................. 7 3. Introduction ............................................................................................................................................................ 8 3.1. Revision History...........................................................................................................................................8 3.2. Audience......................................................................................................................................................8 3.3. Remarks ...................................................................................................................................................... 8 3.4. Terms and Definitions..................................................................................................................................8 3.5. Basics of DICOM Communication .............................................................................................................10 3.6. Abbreviations .............................................................................................................................................10 3.7. References ................................................................................................................................................11 4. Networking ...........................................................................................................................................................12 4.1. Implementation Model ...............................................................................................................................12 4.1.1. Application Data Flow ...........................................................................................................................12 4.1.2. Functional Definition of AE's .................................................................................................................13 4.1.2.1. Functional Definition of SCU Application Entity (SCU AE)...........................................................13 4.1.2.2. Functional Definition of SCP Application Entity (SCP AE) ...........................................................13 4.1.3. Sequencing of Real-World Activities .....................................................................................................14 4.1.3.1. Store and Forward Workflow for C-Store and Storage Commitment ...........................................14 4.1.3.2. Store and Forward Workflow for Q/R C-Find ...............................................................................14 4.1.3.3. Store and Forward Workflow for Q/R C-Move..............................................................................15 4.1.3.4. Direct Routing Workflow ...............................................................................................................15 4.2. AE Specifications.......................................................................................................................................16 4.2.1. SCP Application Entity (SCP AE) Specification ....................................................................................16 4.2.1.1. SOP Classes ................................................................................................................................16 4.2.1.2. Association Policies......................................................................................................................23 4.2.1.3. Association Initiation Policy ..........................................................................................................24 4.2.1.4. Association Acceptance Policy.....................................................................................................26 4.2.2. SCU Application Entity (SCU AE) Specification....................................................................................33 4.2.2.1. SOP Classes ................................................................................................................................33 4.2.2.2. Association Establishment Policies ..............................................................................................40 4.2.2.3. Association Initiation Policy ..........................................................................................................41 4.2.2.4. Association Acceptance Policy.....................................................................................................44 4.3. Network Interfaces.....................................................................................................................................44 4.3.1. Physical Network Interface....................................................................................................................44 4.3.2. Additional Protocols ..............................................................................................................................44 4.3.3. IPv4 and IPv6 Support ..........................................................................................................................44 4.4. Configuration .............................................................................................................................................44 4.4.1. AE Title/Presentation Address Mapping ...............................................................................................44 4.4.1.1. Local AE Titles..............................................................................................................................44 4.4.2. Parameters............................................................................................................................................45 5. Media Interchange ...............................................................................................................................................46 6. Support of Extended Character Sets ...................................................................................................................46 7. Security ................................................................................................................................................................ 47 7.1. Security Profiles.........................................................................................................................................47 7.1.1. TLS Security..........................................................................................................................................47 7.1.2. Anonymization.......................................................................................................................................47 7.2. Association Level Security.........................................................................................................................47 LAUREL BRIDGE SOFTWARE, INC. 500 CREEK VIEW ROAD SUITE 200 NEWARK, DE 19711 TEL: 302-453-0222 FAX: 302-453-9480 WWW.LAURELBRIDGE.COM Compass DICOM Conformance Statement - v3.3.1 Page 8 of 47 3. Introduction 3.1. Revision History Document Version 1.0 1.1 Date of Issue 13 Dec 2010 10 Jan 2011 1.2 12 Apr 2011 1.3 15 Feb 2013 1.4 11 Sep 2015 1.5 1.6 1.7 1.8 3.0.0 3.3.1 08 Apr 2016 16 Nov 2016 6 Sep 2018 10 Apr 2019 12 Aug 2020 13 Aug 2021 Author JTB EMG BRH JTB JTB, BRH JTB JTB JTB JTB JTB JTB Description Initial creation Updated Table 4.2.2.3.1.2-1: STORAGE-SCU AE C-STORE Response Status Handling Behavior Updated tables, version, titles, formatting. Updated DCF version Updated DCF version. Updated and added security profile section. Updated DCF version Updated DCF version. Updated SOP classes. Added description for Direct Routing functionality. Updated DCF version. Added description and updated figures for Cache functionality. Updated DCF version. Updated corporate address. Updated DCF version. Updated DCF version. 3.2. Audience This document is written for the people that need to understand how Compass 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. 3.3. Remarks The scope of this DICOM Conformance Statement is to facilitate integration between Compass 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 firstlevel 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. 3.4. 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. LAUREL BRIDGE SOFTWARE, INC. 500 CREEK VIEW ROAD SUITE 200 NEWARK, DE 19711 TEL: 302-453-0222 FAX: 302-453-9480 WWW.LAURELBRIDGE.COM Compass DICOM Conformance Statement - v3.3.1 Page 9 of 47 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. Joint Photographic Experts Group (JPEG) a set of standardized image compression techniques, available for use by DICOM applications. Media Application Profile the specification of DICOM information objects and encoding exchanged on removable media (e.g., CDs) 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. 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. LAUREL BRIDGE SOFTWARE, INC. 500 CREEK VIEW ROAD SUITE 200 NEWARK, DE 19711 TEL: 302-453-0222 FAX: 302-453-9480 WWW.LAURELBRIDGE.COM Compass DICOM Conformance Statement - v3.3.1 Page 10 of 47 3.5. Basics of DICOM Communication This section describes terminology used in this Conformance Statement for the non-specialist. 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 "prenegotiated" exchange media format, Abstract Syntax, and Transfer Syntax. 3.6. Abbreviations AE AET CSE DHCP DICOM DNS GSDF GSPS HIS HL7 IHE IOD IPv4 Application Entity Application Entity Title Customer Service Engineer Dynamic Host Configuration Protocol Digital Imaging and Communications in Medicine Domain Name System Grayscale Standard Display Function Grayscale Softcopy Presentation State Hospital Information System Health Level 7 Standard Integrating the Healthcare Enterprise Information Object Definition Internet Protocol version 4 LAUREL BRIDGE SOFTWARE, INC. 500 CREEK VIEW ROAD SUITE 200 NEWARK, DE 19711 TEL: 302-453-0222 FAX: 302-453-9480 WWW.LAURELBRIDGE.COM IPv6 ISO JPEG LDAP LUT MPEG MPPS MR MSPS MTU MWL NTP O OSI PACS PDU R RIS SCP SCU SOP SPS TCP/IP U UL VL VR Compass DICOM Conformance Statement - v3.3.1 Page 11 of 47 Internet Protocol version 6 International Organization for Standards Joint Photographic Experts Group Lightweight Directory Access Protocol Look-up Table Moving Picture Experts Group Modality Performed Procedure Step Magnetic Resonance Imaging Modality Scheduled Procedure Step Maximum Transmission Unit (IP) Modality Worklist Network Time Protocol Optional (Key Attribute) Open Systems Interconnection Picture Archiving and Communication System Protocol Data Unit Required (Key Attribute) Radiology Information System. Service Class Provider Service Class User Service-Object Pair Scheduled Procedure Step Transmission Control Protocol/Internet Protocol Unique (Key Attribute) Upper Layer Visible Light Value Representation 3.7. References NEMA PS3 Digital Imaging and Communications in Medicine (DICOM) Standard, available for free at http://medical.nema.org/dicom LAUREL BRIDGE SOFTWARE, INC. 500 CREEK VIEW ROAD SUITE 200 NEWARK, DE 19711 TEL: 302-453-0222 FAX: 302-453-9480 WWW.LAURELBRIDGE.COM 4. 4.1. Implementation Model 4.1.1. Application Data Flow Compass DICOM Conformance Statement - v3.3.1 Page 12 of 47 Networking Figure 1- Store and Forward Workflow LAUREL BRIDGE SOFTWARE, INC. 500 CREEK VIEW ROAD SUITE 200 NEWARK, DE 19711 TEL: 302-453-0222 FAX: 302-453-9480 WWW.LAURELBRIDGE.COM Compass DICOM Conformance Statement - v3.3.1 Page 13 of 47 Figure 2 - Direct Routing Workflow 4.1.2. Functional Definition of AE's 4.1.2.1. Functional Definition of SCU Application Entity (SCU AE) 4.1.2.1.1. Store and Forward Workflow The SCU AE can be invoked by the SCP AE's receipt of images (or by a MOVE request for images), triggering the transfer of specific images to a remote destination AE. The SCU AE must be correctly configured with the host and port number of any external DICOM AE's that are to be C-STORE retrieval destinations. The Presentation Contexts to use are determined from the headers of the DICOM files to be transferred, as well as the configuration in Compass. Some conversion of the DICOM image objects is possible if the original Presentation Context is not supported by the remote destination AE or if a transfer syntax change is preferred. 4.1.2.1.2. Direct Routing Workflow The SCU AE can be invoked by the SCP AE's receipt of a DIMSE message, triggering the transfer of that DIMSE message to a remote destination AE. The SCU AE must be correctly configured with the host and port number of any external DICOM AE's that are to be destinations. The presentation contexts to use are determined by a combination of the presentation contexts originally accepted by the SCP AE and the current DIMSE message. Some conversion of the DICOM DIMSE message is possible if the original Presentation Context is not supported by the remote destination AE or if a transfer syntax change is preferred. 4.1.2.2. Functional Definition of SCP Application Entity (SCP AE) 4.1.2.2.1. Store and Forward Workflow The SCP AE waits for another application to connect at the presentation address configured for its Application Entity Title. When another application connects, the SCP AE expects it to be a DICOM application. The SCP AE will accept Associations with Presentation Contexts for SOP Classes of the Transfer, Query/Retrieve, and Workflow Management (Verification and Storage Commitment only) service classes. Any images received on such Presentation Contexts for Transfer may be added to the Compass database (depending on configuration). 4.1.2.2.2. Direct Routing Workflow The SCP AE waits for another application to connect at the presentation address configured for its Application Entity Title. When another application connects, the SCP AE expects it to be a DICOM application. The SCP AE will accept Associations with Presentation Contexts for SOP Classes of the Transfer, Query/Retrieve, Workflow Management, and Print Management service classes. Any DIMSE messages received on such Presentation Contexts will be handed to the SCU AE. LAUREL BRIDGE SOFTWARE, INC. 500 CREEK VIEW ROAD SUITE 200 NEWARK, DE 19711 TEL: 302-453-0222 FAX: 302-453-9480 WWW.LAURELBRIDGE.COM Compass DICOM Conformance Statement - v3.3.1 Page 14 of 47 4.1.3. Sequencing of Real-World Activities 4.1.3.1. Store and Forward Workflow for C-Store and Storage Commitment 4.1.3.2. Store and Forward Workflow for Q/R C-Find LAUREL BRIDGE SOFTWARE, INC. 500 CREEK VIEW ROAD SUITE 200 NEWARK, DE 19711 TEL: 302-453-0222 FAX: 302-453-9480 WWW.LAURELBRIDGE.COM 4.1.3.3. Store and Forward Workflow for Q/R C-Move Compass DICOM Conformance Statement - v3.3.1 Page 15 of 47 4.1.3.4. Direct Routing Workflow LAUREL BRIDGE SOFTWARE, INC. 500 CREEK VIEW ROAD SUITE 200 NEWARK, DE 19711 TEL: 302-453-0222 FAX: 302-453-9480 WWW.LAURELBRIDGE.COM Compass DICOM Conformance Statement - v3.3.1 Page 16 of 47 4.2. AE Specifications 4.2.1. SCP Application Entity (SCP AE) Specification 4.2.1.1. SOP Classes Compass provides Standard Conformance to the following DICOM V3.0 SOP Classes: SOP Classes Transfer Computed Radiography Image Storage Digital X-Ray Image Storage - For Presentation Digital X-Ray Image Storage - For Processing Digital Mammography X-Ray Image Storage - For Presentation Digital Mammography X-Ray Image Storage - For Processing Digital Intra-oral X-Ray Image Storage - For Presentation Digital Intra-oral X-Ray Image Storage - For Processing CT Image Storage Enhanced CT Image Storage Ultrasound Multi-frame Image Storage MR Image Storage Enhanced MR Image Storage MR Spectroscopy Storage Nuclear Medicine Image Storage Ultrasound Image Storage Secondary Capture Image Storage Multi-frame Single Bit Secondary Capture Image Storage Multi-frame Grayscale Byte Secondary Capture Image Storage Multi-frame Grayscale Word Secondary Capture Image Storage Multi-frame True Color Secondary Capture Image Storage Standalone Overlay Storage (Retired) Table 4.2.1.1-1 SOP Classes for AE Storage SOP Class UID SCU 1.2.840.10008.5.1.4.1.1.1 No 1.2.840.10008.5.1.4.1.1.1.1 No 1.2.840.10008.5.1.4.1.1.1.1.1 No 1.2.840.10008.5.1.4.1.1.1.2 No 1.2.840.10008.5.1.4.1.1.1.2.1 No 1.2.840.10008.5.1.4.1.1.1.3 No 1.2.840.10008.5.1.4.1.1.1.3.1 No 1.2.840.10008.5.1.4.1.1.2 No 1.2.840.10008.5.1.4.1.1.2.1 No 1.2.840.10008.5.1.4.1.1.3.1 No 1.2.840.10008.5.1.4.1.1.4 No 1.2.840.10008.5.1.4.1.1.4.1 No 1.2.840.10008.5.1.4.1.1.4.2 No 1.2.840.10008.5.1.4.1.1.20 No 1.2.840.10008.5.1.4.1.1.6.1 No 1.2.840.10008.5.1.4.1.1.7 No 1.2.840.10008.5.1.4.1.1.7.1 No 1.2.840.10008.5.1.4.1.1.7.2 No 1.2.840.10008.5.1.4.1.1.7.3 No 1.2.840.10008.5.1.4.1.1.7.4 No 1.2.840.10008.5.1.4.1.1.8 No SCP Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes LAUREL BRIDGE SOFTWARE, INC. 500 CREEK VIEW ROAD SUITE 200 NEWARK, DE 19711 TEL: 302-453-0222 FAX: 302-453-9480 WWW.LAURELBRIDGE.COM Compass DICOM Conformance Statement - v3.3.1 Page 17 of 47 SOP Classes SOP Class UID SCU SCP Standalone Curve Storage (Retired) 1.2.840.10008.5.1.4.1.1.9 No Yes Standalone Modality LUT Storage 1.2.840.10008.5.1.4.1.1.10 No Yes (Retired) Standalone VOI LUT Storage 1.2.840.10008.5.1.4.1.1.11 No Yes (Retired) Grayscale Softcopy Presentation 1.2.840.10008.5.1.4.1.1.11.1 No Yes State Storage SOP Class Color Softcopy Presentation State 1.2.840.10008.5.1.4.1.1.11.2 No Yes Storage SOP Class Pseudo-Color Softcopy Presentation 1.2.840.10008.5.1.4.1.1.11.3 No Yes State Storage SOP Class Blending Softcopy Presentation State 1.2.840.10008.5.1.4.1.1.11.4 No Yes Storage SOP Class X-Ray Angiographic Image Storage 1.2.840.10008.5.1.4.1.1.12.1 No Yes X-Ray Radiofluoroscopic Image 1.2.840.10008.5.1.4.1.1.12.2 No Yes Storage Raw Data Storage 1.2.840.10008.5.1.4.1.1.66 No Yes Spatial Registration Storage 1.2.840.10008.5.1.4.1.1.66.1 No Yes Spatial Fiducials Storage 1.2.840.10008.5.1.4.1.1.66.2 No Yes Twelve Lead ECG Waveform 1.2.840.10008.5.1.4.1.1.9.1.1 No Yes Storage General ECG Waveform Storage 1.2.840.10008.5.1.4.1.1.9.1.2 No Yes Ambulatory ECG Waveform Storage 1.2.840.10008.5.1.4.1.1.9.1.3 No Yes Hemodynamic Waveform Storage 1.2.840.10008.5.1.4.1.1.9.2.1 No Yes Cardiac Electrophysiology Waveform 1.2.840.10008.5.1.4.1.1.9.3.1 No Yes Storage Basic Voice Audio Waveform Storage 1.2.840.10008.5.1.4.1.1.9.4.1 No Yes VL Endoscopic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.1 No Yes Video Endoscopic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.1.1 No Yes VL Microscopic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.2 No Yes Video Microscopic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.2.1 No Yes VL Slide-Coordinates Microscopic 1.2.840.10008.5.1.4.1.1.77.1.3 No Yes Image Storage VL Photographic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.4 No Yes Video Photographic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.4.1 No Yes Ophthalmic Photography 8 Bit Image 1.2.840.10008.5.1.4.1.1.77.1.5.1 No Yes Storage Ophthalmic Photography 16 Bit 1.2.840.10008.5.1.4.1.1.77.1.5.2 No Yes Image Storage Stereometric Relationship Storage 1.2.840.10008.5.1.4.1.1.77.1.5.3 No Yes Basic Text SR Storage 1.2.840.10008.5.1.4.1.1.88.11 No Yes LAUREL BRIDGE SOFTWARE, INC. 500 CREEK VIEW ROAD SUITE 200 NEWARK, DE 19711 TEL: 302-453-0222 FAX: 302-453-9480 WWW.LAURELBRIDGE.COM SOP Classes Enhanced SR Storage Comprehensive SR Storage Procedure Log Storage Mammography CAD SR Storage Key Object Selection Document Storage Chest CAD SR Storage X-Ray Radiation Dose SR Storage Positron Emission Tomography Image Storage Standalone PET Curve Storage (Retired) 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 Enhanced XA Image Storage Enhanced XRF Image Storage Encapsulated PDF Storage Enhanced MR Color Image Storage Enhanced US Volume Storage General Audio Waveform Storage Arterial Pulse Waveform Storage Respiratory Waveform Storage XA/XRF Grayscale Softcopy Presentation State Storage Breast Tomosynthesis Image Storage Surface Segmentation Storage Lensometry Measurements Storage Autorefraction Measurements Storage Keratometry Measurements Storage Compass DICOM Conformance Statement - v3.3.1 Page 18 of 47 SOP Class UID SCU SCP 1.2.840.10008.5.1.4.1.1.88.22 No Yes 1.2.840.10008.5.1.4.1.1.88.33 No Yes 1.2.840.10008.5.1.4.1.1.88.40 No Yes 1.2.840.10008.5.1.4.1.1.88.50 No Yes 1.2.840.10008.5.1.4.1.1.88.59 No Yes 1.2.840.10008.5.1.4.1.1.88.65 No Yes 1.2.840.10008.5.1.4.1.1.88.67 No Yes 1.2.840.10008.5.1.4.1.1.128 No Yes 1.2.840.10008.5.1.4.1.1.129 No Yes 1.2.840.10008.5.1.4.1.1.481.1 No Yes 1.2.840.10008.5.1.4.1.1.481.2 No Yes 1.2.840.10008.5.1.4.1.1.481.3 No Yes 1.2.840.10008.5.1.4.1.1.481.4 No Yes 1.2.840.10008.5.1.4.1.1.481.5 No Yes 1.2.840.10008.5.1.4.1.1.481.6 No Yes 1.2.840.10008.5.1.4.1.1.481.7 No Yes 1.2.840.10008.5.1.4.1.1.12.1. No Yes 1.2.840.10008.5.1.4.1.1.12.2.1 No Yes 1.2.840.10008.5.1.4.1.1.104.1 No Yes 1.2.840.10008.5.1.4.1.1.4.3 No Yes 1.2.840.10008.5.1.4.1.1.6.2 No Yes 1.2.840.10008.5.1.4.1.1.9.4.2 No Yes 1.2.840.10008.5.1.4.1.1.9.5.1 No Yes 1.2.840.10008.5.1.4.1.1.9.6.1 No Yes 1.2.840.10008.5.1.4.1.1.11.5 No Yes 1.2.840.10008.5.1.4.1.1.13.1.3 No Yes 1.2.840.10008.5.1.4.1.1.66.5 No Yes 1.2.840.10008.5.1.4.1.1.78.1 No Yes 1.2.840.10008.5.1.4.1.1.78.2 No Yes 1.2.840.10008.5.1.4.1.1.78.3 No Yes LAUREL BRIDGE SOFTWARE, INC. 500 CREEK VIEW ROAD SUITE 200 NEWARK, DE 19711 TEL: 302-453-0222 FAX: 302-453-9480 WWW.LAURELBRIDGE.COM Compass DICOM Conformance Statement - v3.3.1 Page 19 of 47 SOP Classes SOP Class UID SCU SCP Subjective Refraction Measurements 1.2.840.10008.5.1.4.1.1.78.4 No Yes Storage Visual Acuity Measurements Storage 1.2.840.10008.5.1.4.1.1.78.5 No Yes Spectacle Prescription Reports 1.2.840.10008.5.1.4.1.1.78.6 No Yes Storage Macular Grid Thickness and Volume 1.2.840.10008.5.1.4.1.1.79.1 No Yes Report Storage Colon CAD SR Storage 1.2.840.10008.5.1.4.1.1.88.69 No Yes Enhanced PET Image Storage 1.2.840.10008.5.1.4.1.1.130 No Yes Basic Structured Display Storage 1.2.840.10008.5.1.4.1.1.131 No Yes Color Palette Storage 1.2.840.10008.5.1.4.39.1 No Yes Intravascular Optical Coherence 1.2.840.10008.5.1.4.1.1.14.1 No Yes Tomography Image Storage - For Presentation Intravascular Optical Coherence 1.2.840.10008.5.1.4.1.1.14.2 No Yes Tomography Image Storage - For Processing VL Whole Slide Microscopy Image 1.2.840.10008.5.1.4.1.1.77.1.6 No Yes Storage Ophthalmic Axial Measurements 1.2.840.10008.5.1.4.1.1.78.7 No Yes Storage Intraocular Lens Calculations Storage 1.2.840.10008.5.1.4.1.1.78.8 No Yes Ophthalmic Visual Field Static 1.2.840.10008.5.1.4.1.1.80.1 No Yes Perimetry Measurements Storage Implantation Plan SR Storage 1.2.840.10008.5.1.4.1.1.88.70 No Yes DICOS CT Image Storage 1.2.840.10008.5.1.4.1.1.501.1 No Yes DICOS Digital X-Ray Image Storage 1.2.840.10008.5.1.4.1.1.501.2.1 No Yes - For Presentation DICOS Digital X-Ray Image Storage 1.2.840.10008.5.1.4.1.1.501.2.2 No Yes - For Processing DICOS Threat Detection Report 1.2.840.10008.5.1.4.1.1.501.3 No Yes Storage Eddy Current Image Storage 1.2.840.10008.5.1.4.1.1.601.1 No Yes Eddy Current Multi-frame Image 1.2.840.10008.5.1.4.1.1.601.2 No Yes Storage RT Beams Delivery Instruction 1.2.840.10008.5.1.4.34.7 No Yes Storage Generic Implant Template Storage 1.2.840.10008.5.1.4.43.1 No Yes Implant Assembly Template Storage 1.2.840.10008.5.1.4.44.1 No Yes Implant Template Group Storage 1.2.840.10008.5.1.4.45.1 No Yes Query/Retrieve Patient Root Query/Retrieve 1.2.840.10008.5.1.4.1.2.1.1 No Yes Information Model - FIND LAUREL BRIDGE SOFTWARE, INC. 500 CREEK VIEW ROAD SUITE 200 NEWARK, DE 19711 TEL: 302-453-0222 FAX: 302-453-9480 WWW.LAURELBRIDGE.COM Compass DICOM Conformance Statement - v3.3.1 Page 20 of 47 SOP Classes SOP Class UID SCU SCP Patient Root Query/Retrieve 1.2.840.10008.5.1.4.1.2.1.2 No Yes Information Model - MOVE Patient Root Query/Retrieve 1.2.840.10008.5.1.4.1.2.1.3 No Yes Information Model - GET Study Root Query/Retrieve 1.2.840.10008.5.1.4.1.2.2.1 No Yes Information Model - FIND Study Root Query/Retrieve 1.2.840.10008.5.1.4.1.2.2.2 No Yes Information Model - MOVE Study Root Query/Retrieve 1.2.840.10008.5.1.4.1.2.2.3 No Yes Information Model - GET Patient/Study Only Query/Retrieve 1.2.840.10008.5.1.4.1.2.3.1 No Yes Information Model - FIND (Retired) Patient/Study Only Query/Retrieve 1.2.840.10008.5.1.4.1.2.3.2 No Yes Information Model - MOVE (Retired) Workflow Management Storage Commitment 1.2.840.10008.1.20.1 No Yes Modality Worklist Information Model - 1.2.840.10008.5.1.4.31 No Yes FIND Modality Performed Procedure Step 1.2.840.10008.3.1.2.3.3 No Yes SOP Class Verification 1.2.840.10008.1.1 No Yes Print Management Basic Grayscale Print Management 1.2.840.10008.5.1.1.9 No Yes Meta SOP Class Print Job SOP Class 1.2.840.10008.5.1.1.14 No Yes Basic Annotation Box SOP Class 1.2.840.10008.5.1.1.15 No Yes Printer SOP Class 1.2.840.10008.5.1.1.16 No Yes Basic Color Print Management Meta 1.2.840.10008.5.1.1.18 No Yes SOP Class Presentation LUT SOP Class 1.2.840.10008.5.1.1.23 No Yes Basic Print Image Overlay Box SOP 1.2.840.10008.5.1.1.24.1 No Yes Class (Retired) These are the default SOP Classes supported. By altering the configuration it is possible to support additional or fewer SOP Classes. 4.2.1.1.1. Accepted Presentation Contexts Compass can accept or receive a presentation context consisting of any SOP class listed in Table 4.2.1.1-1 and any transfer syntax listed in Table 4.2.1.1.1-1 below: Abstract Syntax Name Table 4.2.1.1.1-1 Transfer Syntax Transfer Syntax UID Name SCU SCP Ext. Neg. LAUREL BRIDGE SOFTWARE, INC. 500 CREEK VIEW ROAD SUITE 200 NEWARK, DE 19711 TEL: 302-453-0222 FAX: 302-453-9480 WWW.LAURELBRIDGE.COM Abstract Syntax Name * * * * * * * * * * * * * * * * * * Compass DICOM Conformance Statement - v3.3.1 Page 21 of 47 Transfer Syntax Transfer Syntax UID Name SCU Explicit VR Little 1.2.840.10008.1.2.1 No Endian Implicit VR Little 1.2.840.10008.1.2 No Endian Explicit VR Big 1.2.840.10008.1.2.2 No Endian JPEG Baseline 1.2.840.10008.1.2.4.50 No (Process 1) JPEG Extended 1.2.840.10008.1.2.4.51 No (Process 2 & 4) JPEG Lossless, 1.2.840.10008.1.2.4.57 No Non-Hierarchical (Process 14) JPEG Lossless, 1.2.840.10008.1.2.4.70 No NonHierarchical, First-Order Prediction (Process 14 [Selection Value 1]) JPEG-LS Lossless 1.2.840.10008.1.2.4.80 No JPEG-LS Lossy 1.2.840.10008.1.2.4.81 No (Near-Lossless) JPEG 2000 1.2.840.10008.1.2.4.90 No (Lossless Only) JPEG 2000 1.2.840.10008.1.2.4.91 No JPEG 2000 Part 1.2.840.10008.1.2.4.92 No 2 Multi- component (Lossless Only) JPEG 2000 Part 1.2.840.10008.1.2.4.93 No 2 Multi- component JPIP Referenced 1.2.840.10008.1.2.4.94 No JPIP Referenced 1.2.840.10008.1.2.4.95 No Deflate MPEG2 Main 1.2.840.10008.1.2.4.100 No Profile @ Main Level MPEG2 Main 1.2.840.10008.1.2.4.101 No Profile @ High Level MPEG-4 1.2.840.10008.1.2.4.102 No AVC/H.264 Stereo High Profile / Level 4.1 SCP Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Ext. Neg. None None None None None None None None None None None None None None None None None None LAUREL BRIDGE SOFTWARE, INC. 500 CREEK VIEW ROAD SUITE 200 NEWARK, DE 19711 TEL: 302-453-0222 FAX: 302-453-9480 WWW.LAURELBRIDGE.COM Abstract Syntax Name * * * * * * * * * * Compass DICOM Conformance Statement - v3.3.1 Page 22 of 47 Transfer Syntax Name MPEG-4 AVC/H.264 BDCompatible High Profile / Level 4.1 MPEG-4 AVC/H.264 High Profile / Level 4.2 for 2D Video MPEG-4 AVC/H.264 High Profile / Level 4.2 for 3D Video MPEG-4 AVC/H.264 Stereo High Profile / Level 4.2 HEVC/H.265 Main Profile / Level 5.1 HEVC/H.265 Main 10 Profile / Level 5.1 RLE Lossless SMPTE ST 2110-20 Uncompressed Progressive Active Video SMPTE ST 2110-20 Uncompressed Interlaced Active Video SMPTE ST 2110-30 PCM Digital Audio Transfer Syntax UID 1.2.840.10008.1.2.4.103 1.2.840.10008.1.2.4.104 1.2.840.10008.1.2.4.105 1.2.840.10008.1.2.4.106 1.2.840.10008.1.2.4.107 1.2.840.10008.1.2.4.108 1.2.840.10008.1.2.5 1.2.840.10008.1.2.7.1 1.2.840.10008.1.2.7.2 1.2.840.10008.1.2.7.3 SCU No No No No No No No No No No SCP Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Ext. Neg. None None None None None None None None None None * Indicates any SOP class from Table 4.2.1.1-1. NOTE: A SOP Class can be accepted in any of the following transfer syntaxes from the table below, so long as it is sent out in that same transfer syntax; i.e., Compass cannot decompress it or recompress it into a different transfer syntax. Table 4.2.1.1.1-2 Transfer Syntax Name Transfer Syntax UID JPEG 2000 Part 2 Multi-component (Lossless Only) 1.2.840.10008.1.2.4.92 JPEG 2000 Part 2 Multi-component 1.2.840.10008.1.2.4.93 JPIP Referenced 1.2.840.10008.1.2.4.94 JPIP Referenced Deflate 1.2.840.10008.1.2.4.95 LAUREL BRIDGE SOFTWARE, INC. 500 CREEK VIEW ROAD SUITE 200 NEWARK, DE 19711 TEL: 302-453-0222 FAX: 302-453-9480 WWW.LAURELBRIDGE.COM MPEG2 Main Profile @ Main Level MPEG2 Main Profile @ High Level MPEG-4 AVC/H.264 Stereo High Profile / Level 4.1 MPEG-4 AVC/H.264 BD-Compatible High Profile / Level 4.1 MPEG-4 AVC/H.264 High Profile / Level 4.2 for 2D Video MPEG-4 AVC/H.264 High Profile / Level 4.2 for 3D Video MPEG-4 AVC/H.264 Stereo High Profile / Level 4.2 HEVC/H.265 Main Profile / Level 5.1 HEVC/H.265 Main 10 Profile / Level 5.1 SMPTE ST 2110-20 Uncompressed Progressive Active Video SMPTE ST 2110-20 Uncompressed Interlaced Active Video SMPTE ST 2110-30 PCM Digital Audio Compass DICOM Conformance Statement - v3.3.1 Page 23 of 47 1.2.840.10008.1.2.4.100 1.2.840.10008.1.2.4.101 1.2.840.10008.1.2.4.102 1.2.840.10008.1.2.4.103 1.2.840.10008.1.2.4.104 1.2.840.10008.1.2.4.105 1.2.840.10008.1.2.4.106 1.2.840.10008.1.2.4.107 1.2.840.10008.1.2.4.108 1.2.840.10008.1.2.7.1 1.2.840.10008.1.2.7.2 1.2.840.10008.1.2.7.3 4.2.1.2. Association Policies 4.2.1.2.1. General The SCP AE can both accept and propose Association Requests. The SCP AE will accept Association Requests for the Transfer, Query/Retrieve, Workflow Management, and Print Management services. It will propose Associations only for the Storage Commitment Push service (but may trigger the SCU to propose associations after receiving a Patient Root MOVE or Study Root MOVE request). The DICOM standard Application Context Name for DICOM 3.0 is always accepted and proposed: Table 4.2.1.2.1-1 DICOM Application Context For STORAGE-SCP AE Application Context Name 1.2.840.10008.3.1.1.1 4.2.1.2.2. Number of Associations The SCP AE can support multiple simultaneous Associations requested by peer AEs. Each time the SCP AE receives an Association, a child process will be spawned to process the Transfer, Query/Retrieve, Workflow Management, or Print Management service requests. The maximum number of child processes, and thus the maximum number of simultaneous Associations that can be processed, is set by configuration. The default maximum number is 25 in total. This maximum number of simultaneous Associations can be either an absolute number or a maximum number for each requesting external Application Entity. The latter flexibility can be useful if communication with one external AE is unreliable and one does not wish `hung' connections with this AE to prevent Associations with other client AEs. Table 4.2.1.2.1-2 Number Of Simultaneous Associations For SCP AE Maximum number of simultaneous Associations requested by peer AEs 25 (Configurable) 4.2.1.2.3. Asynchronous Nature The SCP AE does not support asynchronous communication (multiple outstanding transactions over a single Association). The SCP AE does permit an SCU to send multiple Storage Commitment Push Model Requests before it has sent back any N-EVENT-REPORT Notifications. However, the SCP AE must send an N-ACTION LAUREL BRIDGE SOFTWARE, INC. 500 CREEK VIEW ROAD SUITE 200 NEWARK, DE 19711 TEL: 302-453-0222 FAX: 302-453-9480 WWW.LAURELBRIDGE.COM Compass DICOM Conformance Statement - v3.3.1 Page 24 of 47 Response before permitting another N-ACTION Request to be received so the DICOM communication itself is not truly asynchronous. Table 4.2.1.2.1-3 Asynchronous Nature For SCP AE Maximum number of outstanding asynchronous transactions 1 (Not configurable) There is no limit on the number of outstanding Storage Commitment Push Model Requests that can be received and acknowledged before the SCP AE has responded with the corresponding NEVENT-REPORT Notifications. Table 4.2.1.2.1-4 Outstanding Storage Commitment Push Model Requests for SCP AE Maximum number of outstanding Storage Commitment Requests for which no N-EVENT Notification has been sent No Maximum Limit 4.2.1.2.4. Implementation Identifying Information The implementation information for this Application Entity is: Table 4.2.1.2.1-5 DICOM Implementation Class and Version for SCP AE Implementation Class UID 1.2.840.114089.1.0.0.3.4.46 Implementation Version Name DCF 3.4.46c 4.2.1.3. Association Initiation Policy 4.2.1.3.1. Activity Send Storage Commitment Notification Over New Association 4.2.1.3.1.1 Description and Sequencing of Activity for Store-and-Forward Workflow The SCP AE will, via the SCU AE, always initiate a new Association when a Peer AE requests Storage Commitment of Composite SOP Instances. LAUREL BRIDGE SOFTWARE, INC. 500 CREEK VIEW ROAD SUITE 200 NEWARK, DE 19711 TEL: 302-453-0222 FAX: 302-453-9480 WWW.LAURELBRIDGE.COM Compass DICOM Conformance Statement - v3.3.1 Page 25 of 47 Figure 4.2.1.3.1.1-1 Sequencing Of Activity Send Storage Commitment Notification Over New Association The following sequencing constraints illustrated in Figure 4.2.1.3.1.1-1 apply to the SCP AE for handling Storage Commitment Push Model Requests using a new Association in Store-and-Forward mode. This model is also applicable in Direct Routing mode where Compass has been configured to respond to Storage Commitment Push Model Requests instead of passing them on. 1. Peer AE opens an Association with the SCP AE. 2. Peer AE requests Storage Commitment of Composite SOP Instance(s) (peer sends N-ACTION-RQ and STORAGE-SCP AE responds with N-ACTION-RSP to indicate that it received the request). 3. Peer AE closes the Association before the SCP AE can successfully send the Storage Commitment Push Model Notification (N-EVENT-REPORT-RQ). 4. SCU AE opens an Association with a peer AE. 5. SCU AE sends Storage Commitment Push Model Notification (N-EVENT-REPORT). 6. SCU AE closes the Association with the peer AE. 4.2.1.3.1.2 Proposed Presentation Contexts SCP AE will propose Presentation Contexts as shown in the following table: Abstract Syntax Name Storage Commitment Push Model Storage Commitment Push Model Table 4.2.1.3.1.2-1 Proposed Presentation Contexts By The SCP AE Abstract Syntax UID Transfer Syntax Name Transfer Syntax UID 1.2.840.10008.1.20.1 DICOM Explicit 1.2.840.10008.1.2.1 VR Little Endian 1.2.840.10008.1.20.1 DICOM Implicit VR Little Endian 1.2.840.10008.1.2 Role SCP SCP Ext. Neg None None LAUREL BRIDGE SOFTWARE, INC. 500 CREEK VIEW ROAD SUITE 200 NEWARK, DE 19711 TEL: 302-453-0222 FAX: 302-453-9480 WWW.LAURELBRIDGE.COM Compass DICOM Conformance Statement - v3.3.1 Page 26 of 47 4.2.1.4. Association Acceptance Policy 4.2.1.4.1. Activity Receive Images, Verification, and Storage Commitment Requests in Store-and-Forward Mode 4.2.1.4.1.1 Description and Sequencing of Activity The SCP AE accepts Associations only if they have valid Presentation Contexts. If none of the requested Presentation Contexts are accepted then the Association Request itself if rejected. It can be configured to only accept Associations with certain hosts (using TCP/IP address or hostname), ports, and/or Application Entity Titles. The default behavior of the SCP AE is to always attempt to send a Storage Commitment Push Model Notification (N-EVENT-REPORT) on a new Association. It is also the behavior of the SCP AE to send Storage Commitment Push Model Notification (N-EVENT-REPORT) with a status of success regardless of whether or not the Peer SCU AE has in fact sent the composite SOP Instance to Compass. The purpose of Compass' implementation of Storage Commitment is to accept all storage commitment requests on behalf of an ultimate destination that does not implement storage commitment. Figure 4.2.1.4.1.1-1 LAUREL BRIDGE SOFTWARE, INC. 500 CREEK VIEW ROAD SUITE 200 NEWARK, DE 19711 TEL: 302-453-0222 FAX: 302-453-9480 WWW.LAURELBRIDGE.COM Compass DICOM Conformance Statement - v3.3.1 Page 27 of 47 The following sequencing constraints illustrated in Figure 4.2.1.4.1.1-1 apply to the SCP AE for handling storage commitment requests in Store-and-Forward mode: 1. Peer AE opens an Association with the SCP AE. 2. Peer AE sends zero or more Composite SOP Instances. 3. Peer AE requests Storage Commitment of Composite SOP Instance(s) (peer sends N-ACTION-RQ and SCP AE responds with N-ACTION-RSP to indicate that it received the request). 4. Peer AE closes the Association. The SCP AE may reject Association attempts as shown in the Table below. The Result, Source and Reason/Diag columns represent the values returned in the corresponding fields of an ASSOCIATE-RJ PDU (see PS 3.8, Section 9.3.4). The following abbreviations are used in the Source column: a. 1 DICOM UL service-user b. 2 DICOM UL service-provider (ASCE related function) c. 3 DICOM UL service-provider (Presentation related function) Result 2 rejected-transient Source c Table 4.2.1.4.1.1-1 Reason/Diag 2 local-limit-exceeded Explanation The (configurable) maximum number of simultaneous Associations has been reached. An Association request with the same parameters may succeed at a later time. LAUREL BRIDGE SOFTWARE, INC. 500 CREEK VIEW ROAD SUITE 200 NEWARK, DE 19711 TEL: 302-453-0222 FAX: 302-453-9480 WWW.LAURELBRIDGE.COM Result 2 rejected-transient Source c 1 a rejected-permanent 1 a rejected-permanent 1 a rejected-permanent 1 b rejected-permanent Compass DICOM Conformance Statement - v3.3.1 Page 28 of 47 Reason/Diag 1 temporary congestion 2 application-contextname-not-supported 7 called-AE-title-notrecognized 3 calling-AE-title-notrecognized 1 no-reason-given Explanation No Associations can be accepted at this time due to the real-time requirements of higher priority activities (e.g. during image acquisition no Associations will be accepted) or because insufficient resources are available (e.g. memory, processes, threads). An Association request with the same parameters may succeed at a later time. The Association request contained an unsupported Application Context Name. An association request with the same parameters will not succeed at a later time. The Association request contained an unrecognized Called AE Title. An Association request with the same parameters will not succeed at a later time unless configuration changes are made. This rejection reason normally occurs when the Association initiator is incorrectly configured and attempts to address the Association acceptor using the wrong AE Title. The Association request contained an unrecognized Calling AE Title. An Association request with the same parameters will not succeed at a later time unless configuration changes are made. This rejection reason normally occurs when the Association acceptor has not been configured to recognize the AE Title of the Association initiator. The Association request could not be parsed. An Association request with the same format will not succeed at a later time. LAUREL BRIDGE SOFTWARE, INC. 500 CREEK VIEW ROAD SUITE 200 NEWARK, DE 19711 TEL: 302-453-0222 FAX: 302-453-9480 WWW.LAURELBRIDGE.COM Compass DICOM Conformance Statement - v3.3.1 Page 29 of 47 4.2.1.4.1.2 Accepted Presentation Contexts The default Behavior of the SCP AE supports all of the presentation contexts listed in Table 4.2.1.1.1-1. The SCP AE can be configured to accept a subset or a superset of these presentation contexts by adding or removing SOP Classes and/or transfer syntaxes. If multiple Transfer Syntaxes are proposed per Presentation Context then only the most preferable Transfer Syntax is accepted. The order of Transfer Syntax preference for the SCP AE is configurable. 4.2.1.4.1.3 SOP Specific Conformance for Verification SOP Class The SCP AE provides standard conformance to the Verification SOP Class as an SCP. 4.2.1.4.1.4 SOP Specific Conformance for Storage SOP Class in Store-and-Forward mode The associated Activity with the Storage service is the storage of medical image data received over the network on a designated hard disk. The SCP AE will return a failure status if it is unable to store the images on to the hard disk. The SCP AE does not have any dependencies on the number of Associations used to send images to it. Images belonging to more than one Study or Series can be sent over a single or multiple Associations. Images belonging to a single Study or Series can also be sent over different Associations. There is no limit on either the number of SOP Instances or the maximum amount of total SOP Instance data that can be transferred over a single Association. The SCP AE is configured to retain the original DICOM data in DICOM Part 10 compliant file format. The SCP AE is Level 2 (Full) conformant as a Storage SCP. In addition, all Private and SOP Class Extended Elements are maintained in the DICOM format files. In addition to saving all Elements in files, a subset of the Elements is stored in Compass' database to support the creation and organization of jobs for the SCU AE. The behavior for handling duplicate SOP Instances is not configurable. Compass will accept (assuming the presentation context is acceptable) any duplicate SOP Instances and route them as is. Service Status Success Table 4.2.1.4.1.4-1 Further Meaning Error Code Success 0000 Refused Error Out of Resources Data Set does not match SOP Class A700 A900 Reason The Composite SOP Instance was successfully received, verified, and stored in the system database. Indicates that there was not enough disk space to store the image. Indicates that the Data Set does not encode a valid instance of the SOP Class specified. This status is returned if the DICOM Object stream can be successfully parsed but does not contain values for one or more mandatory Elements of the SOP Class. The SCP AE does not perform a comprehensive check, as it only checks a subset of required Elements. In addition, if the SOP Class is for a type of image but the SOP Instance does not contain values necessary for its display then this status is returned. LAUREL BRIDGE SOFTWARE, INC. 500 CREEK VIEW ROAD SUITE 200 NEWARK, DE 19711 TEL: 302-453-0222 FAX: 302-453-9480 WWW.LAURELBRIDGE.COM Service Status Error Warning Further Meaning Cannot understand Coercion of Data Elements Compass DICOM Conformance Statement - v3.3.1 Page 30 of 47 Error Code C000 B000 Reason Indicates that the SCP AE cannot parse the Data Set into Elements. Indicates that one or more Element values were coerced. NOTE: If a failure condition does occur when handling an Association then all images previously received successfully over the Association are maintained in the Compass database. No previously successfully received images are discarded. Even if an image is successfully received but an error occurs transmitting the C-STORE Response then this final image is maintained rather than discarded. If the loss of an Association is detected then the Association is closed. The Behavior of SCP AE during communication failure is summarized in the following table: Table 4.2.1.4.1.4-2 Exception Reason Timeout expiry for an expected DICOM Message The Association is aborted by issuing a DICOM A- Request (DIMSE level timeout). i.e. The SCP AE is ABORT. If some Composite SOP Instances have waiting for the next C-STORE Request on an open already been successfully received then they are Association but the timer expires. maintained in the database. They are not automatically discarded because of a later failure. Timeout expiry for an expected DICOM PDU or TCP/IP The Association is aborted by issuing a DICOM A- packet (Low-level timeout). i.e. The SCP AE is waiting ABORT. If a C-STORE Data Set has not been fully for the next C-STORE Data Set PDU but the timer received then the data already received is discarded. If expires. some Composite SOP Instances have already been successfully received over the Association then they are maintained in the database. They are not automatically discarded because of a later failure. Association aborted by the SCU or the network layers If some Composite SOP Instances have already been indicate communication loss (i.e. low-level TCP/IP successfully received then they are maintained in the socket closure) database. They are not automatically discarded because of a later failure. 4.2.1.4.1.5 SOP Specific Conformance for Storage Commitment SOP Class in Store-and-Forward mode The SCP AE takes the list of Composite SOP Instance UIDs specified in a Storage Commitment Push Model NACTION Request and attempts to send a Notification request (N-EVENT-REPORT-RQ) on a new Association. The SCP AE will request a new Association with the configured peer AE. The SCP AE does not require that it previously received a specified Composite SOP Instance in order to respond with the Composite SOP Instance UID in the N-EVENT-REPORT-RQ. The SCP AE will support Storage Commitment Push Model requests for SOP Instances of any of the Storage SOP Classes that are also supported by the SCP AE specified in Table 4.2.1.1-1. 4.2.1.4.1.6 SOP Specific Conformance for Query/Retrieve SOP Classes The SCP AE supports both hierarchical and relational queries, with some limitations. By default, a hierarchical query will be treated as if it were a relational query (this behavior is configurable per Compass source), allowing for broken implementations which request hierarchical queries but do not provide the necessary keys above the requested Query Level. There are no attributes which are always returned by default; only the attributes requested in the query identifier are returned. Query responses are generated from the Cache portion of the Compass database only; previously received images which were added to Jobs but which were not added to the Cache will not be queryable through these SOP Classes. Received images which are added to the Cache database can alter the values in that database depending on the configurable Duplication Policy (if it is set to Keep Last). Nonetheless, the database values will never overlay the received image files if these files are retrieved through the Q/R service. LAUREL BRIDGE SOFTWARE, INC. 500 CREEK VIEW ROAD SUITE 200 NEWARK, DE 19711 TEL: 302-453-0222 FAX: 302-453-9480 WWW.LAURELBRIDGE.COM Compass DICOM Conformance Statement - v3.3.1 Page 31 of 47 Any images retrieved through the MOVE Service will be sent to the specified Move Destination AE (configurable in the Compass destinations). Any filters for the specified destination will be applied to the images outbound; however, Job Actions for the specified destination will not apply, since the MOVE Service does not create a job. Patient Root Information Model All required search keys on each of the four levels (Patient/Study/Series/Image) are supported. However, IMAGE level queries are only supported if at least one key at a higher level is specified. Study Root Information Model All required search keys on each of the three level (Study/Series/Image) are supported. However, IMAGE level queries are only supported if at least one key at a higher level is specified. At each of the four levels (Patient/Study/Series/Image), there are eight possible configurable FIND tags which can be added to the Cache database and supported via FIND service (in addition to the standard supported list). Such configurable tags are not supported for matching only for return. Additionally, these tags are stored lexicographically (rather than, perhaps, numerically) and must survive translation to and from string representation to be remembered and returned. Table 4.2.1.4.1.6-1 Patient Root C-FIND SCP Supported Elements Level Name Tag VR Types of Matching Attribute Name Patient Level Patient Name 0010,0010 PN S,* (case insensitive) Patient ID 0010,0020 LO S,* (case sensitive),U Patient Birth Date 0010.0030 DA S,R Patient Sex 0010.0040 CS S Number of Patient Related Studies 0020,1200 IS NONE Number of Patient Related Series 0020,1202 IS NONE Number of Patient Related Instances 0020,1204 IS NONE Custom Patient Columns User configured NONE Study Level Study Instance UID 0020.000D UI S,*,U Study Date 0008,0020 DA S,R Study Time 0008,0030 TM S,R Accession Number 0008.0050 SH S,* (case sensitive) Study ID 0020.0010 SH S,* (case sensitive) Number of Study Related Series 0020,1206 IS NONE Number of Study Related Instances 0020,1208 IS NONE Custom Study Columns User configured NONE Series Level Series Instance Uid 0020.000E UI S,*,U Series Number 0020,0011 IS S Modality 0008,0060 CS S,* Modalities In Study 0008,0061 CS NONE Number of Series Related Instances 0020,1209 IS NONE Custom Series Columns User configured NONE Image Level SOP Instance UID 0008,0018 UI S,*,U Instance Number 0020,0013 IS S Custom Image Columns User configured NONE N.B. The Study Root C-FIND SCP Supported Elements are the same as in the table above, with all of the Patient level attributes residing at the Study level. The table should be read as follows: Attribute Name: Attributes supported for returned C-FIND Responses. Tag: Appropriate DICOM tag for this attribute. VR: Appropriate DICOM VR for this attribute. Types of Matching: The types of Matching supported by the C-FIND SCP. An "S" indicates the identifier attribute can specify Single Value Matching, an "R" indicates Range Matching, an "*" indicates wild card matching, and a U" LAUREL BRIDGE SOFTWARE, INC. 500 CREEK VIEW ROAD SUITE 200 NEWARK, DE 19711 TEL: 302-453-0222 FAX: 302-453-9480 WWW.LAURELBRIDGE.COM Compass DICOM Conformance Statement - v3.3.1 Page 32 of 47 indicates universal matching. "NONE" indicates that no matching is supported but that values for this Element in the database can be returned. Service Status Success Refused Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Failed Warning Cancel Pending Table 4.2.1.4.1.6-2 C-FIND / C-MOVE Response Status Return Behavior Further Meaning Error Code Reason Success 0000 Out of Resources A700 Move Destination Unknown A801 Identifier does not match SOP A900 Class Feature Not Licensed C001 Compass is not licensed to reply. Feature Not Supported C002 The requested feature is not supported. C003 Patient-level query failed C004 Study-level query failed C005 Series-level query failed C006 Image-level query failed C007 Patient-level key is missing C008 Study-level key is missing C009 Series-level key is missing C00A Image-level key is missing C00B Patient-level key is not specified C00C Study-level key is not specified C00D Series-level key is not specified C00E Image-level key is not specified C00F The MOVE Destination is unavailable C010 Query Level is missing C011 No instances match the given key C012 Failure sending to destination C013 Exception while processing FIND C014 Exception while processing MOVE Max Returned Results reached B001 The operation succeeded and the results that were returned were truncated because they reached the configured Max Returned Results value for the source. User Canceled the operation FE00 Matches are continuing and current FF00 match is supplied. 4.2.1.4.2. Activity Receive DIMSE Message Requests in Direct Routing Mode Description and Sequencing of Activity The SCP AE accepts Associations only if they have valid Presentation Contexts. If none of the requested Presentation Contexts are accepted then the Association Request itself if rejected. It can be configured to only accept Associations with certain hosts (using TCP/IP address or hostname), ports, and/or Application Entity Titles. The default behavior of the SCP AE is to hand the DIMSE request off to the SCU AE and wait for a DIMSE reply from the SCU AE. This DIMSE reply is then sent back to the Remote Application Entity. LAUREL BRIDGE SOFTWARE, INC. 500 CREEK VIEW ROAD SUITE 200 NEWARK, DE 19711 TEL: 302-453-0222 FAX: 302-453-9480 WWW.LAURELBRIDGE.COM Compass DICOM Conformance Statement - v3.3.1 Page 33 of 47 4.2.2. SCU Application Entity (SCU AE) Specification 4.2.2.1. SOP Classes Compass provides Standard Conformance to the following DICOM V3.0 SOP Classes: SOP Classes Table 4.2.2.1-1 SOP Classes for AE Storage SOP Class UID SCU Transfer Computed Radiography Image 1.2.840.10008.5.1.4.1.1.1 Yes No Storage Digital X-Ray Image Storage - For 1.2.840.10008.5.1.4.1.1.1.1 Yes No Presentation Digital X-Ray Image Storage - For 1.2.840.10008.5.1.4.1.1.1.1.1 Yes No Processing Digital Mammography X-Ray Image 1.2.840.10008.5.1.4.1.1.1.2 Yes No Storage - For Presentation Digital Mammography X-Ray Image 1.2.840.10008.5.1.4.1.1.1.2.1 Yes No Storage - For Processing Digital Intra-oral X-Ray Image 1.2.840.10008.5.1.4.1.1.1.3 Yes No Storage - For Presentation Digital Intra-oral X-Ray Image 1.2.840.10008.5.1.4.1.1.1.3.1 Yes No Storage - For Processing CT Image Storage 1.2.840.10008.5.1.4.1.1.2 Yes No Enhanced CT Image Storage 1.2.840.10008.5.1.4.1.1.2.1 Yes No Ultrasound Multi-frame Image 1.2.840.10008.5.1.4.1.1.3.1 Yes No Storage MR Image Storage 1.2.840.10008.5.1.4.1.1.4 Yes No Enhanced MR Image Storage 1.2.840.10008.5.1.4.1.1.4.1 Yes No MR Spectroscopy Storage 1.2.840.10008.5.1.4.1.1.4.2 Yes No Nuclear Medicine Image Storage 1.2.840.10008.5.1.4.1.1.20 Yes No Ultrasound Image Storage 1.2.840.10008.5.1.4.1.1.6.1 Yes No Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7 Yes No Multi-frame Single Bit Secondary 1.2.840.10008.5.1.4.1.1.7.1 Yes No Capture Image Storage Multi-frame Grayscale Byte 1.2.840.10008.5.1.4.1.1.7.2 Yes No Secondary Capture Image Storage Multi-frame Grayscale Word 1.2.840.10008.5.1.4.1.1.7.3 Yes No Secondary Capture Image Storage Multi-frame True Color Secondary 1.2.840.10008.5.1.4.1.1.7.4 Yes No Capture Image Storage Standalone Overlay Storage 1.2.840.10008.5.1.4.1.1.8 Yes No (Retired) SCP LAUREL BRIDGE SOFTWARE, INC. 500 CREEK VIEW ROAD SUITE 200 NEWARK, DE 19711 TEL: 302-453-0222 FAX: 302-453-9480 WWW.LAURELBRIDGE.COM Compass DICOM Conformance Statement - v3.3.1 Page 34 of 47 SOP Classes SOP Class UID SCU SCP Standalone Curve Storage (Retired) 1.2.840.10008.5.1.4.1.1.9 Yes No Standalone Modality LUT Storage 1.2.840.10008.5.1.4.1.1.10 Yes No (Retired) Standalone VOI LUT Storage 1.2.840.10008.5.1.4.1.1.11 Yes No (Retired) Grayscale Softcopy Presentation 1.2.840.10008.5.1.4.1.1.11.1 Yes No State Storage SOP Class Color Softcopy Presentation State 1.2.840.10008.5.1.4.1.1.11.2 Yes No Storage SOP Class Pseudo-Color Softcopy Presentation 1.2.840.10008.5.1.4.1.1.11.3 Yes No State Storage SOP Class Blending Softcopy Presentation State 1.2.840.10008.5.1.4.1.1.11.4 Yes No Storage SOP Class X-Ray Angiographic Image Storage 1.2.840.10008.5.1.4.1.1.12.1 Yes No X-Ray Radiofluoroscopic Image 1.2.840.10008.5.1.4.1.1.12.2 Yes No Storage Raw Data Storage 1.2.840.10008.5.1.4.1.1.66 Yes No Spatial Registration Storage 1.2.840.10008.5.1.4.1.1.66.1 Yes No Spatial Fiducials Storage 1.2.840.10008.5.1.4.1.1.66.2 Yes No Twelve Lead ECG Waveform 1.2.840.10008.5.1.4.1.1.9.1.1 Yes No Storage General ECG Waveform Storage 1.2.840.10008.5.1.4.1.1.9.1.2 Yes No Ambulatory ECG Waveform Storage 1.2.840.10008.5.1.4.1.1.9.1.3 Yes No Hemodynamic Waveform Storage 1.2.840.10008.5.1.4.1.1.9.2.1 Yes No Cardiac Electrophysiology Waveform 1.2.840.10008.5.1.4.1.1.9.3.1 Yes No Storage Basic Voice Audio Waveform Storage 1.2.840.10008.5.1.4.1.1.9.4.1 Yes No VL Endoscopic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.1 Yes No Video Endoscopic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.1.1 Yes No VL Microscopic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.2 Yes No Video Microscopic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.2.1 Yes No VL Slide-Coordinates Microscopic 1.2.840.10008.5.1.4.1.1.77.1.3 Yes No Image Storage VL Photographic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.4 Yes No Video Photographic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.4.1 Yes No Ophthalmic Photography 8 Bit Image 1.2.840.10008.5.1.4.1.1.77.1.5.1 Yes No Storage Ophthalmic Photography 16 Bit 1.2.840.10008.5.1.4.1.1.77.1.5.2 Yes No Image Storage Stereometric Relationship Storage 1.2.840.10008.5.1.4.1.1.77.1.5.3 Yes No Basic Text SR Storage 1.2.840.10008.5.1.4.1.1.88.11 Yes No LAUREL BRIDGE SOFTWARE, INC. 500 CREEK VIEW ROAD SUITE 200 NEWARK, DE 19711 TEL: 302-453-0222 FAX: 302-453-9480 WWW.LAURELBRIDGE.COM SOP Classes Enhanced SR Storage Comprehensive SR Storage Procedure Log Storage Mammography CAD SR Storage Key Object Selection Document Storage Chest CAD SR Storage X-Ray Radiation Dose SR Storage Positron Emission Tomography Image Storage Standalone PET Curve Storage (Retired) 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 Enhanced XA Image Storage Enhanced XRF Image Storage Encapsulated PDF Storage Enhanced MR Color Image Storage Enhanced US Volume Storage General Audio Waveform Storage Arterial Pulse Waveform Storage Respiratory Waveform Storage XA/XRF Grayscale Softcopy Presentation State Storage Breast Tomosynthesis Image Storage Surface Segmentation Storage Lensometry Measurements Storage Autorefraction Measurements Storage Keratometry Measurements Storage Compass DICOM Conformance Statement - v3.3.1 Page 35 of 47 SOP Class UID SCU SCP 1.2.840.10008.5.1.4.1.1.88.22 Yes No 1.2.840.10008.5.1.4.1.1.88.33 Yes No 1.2.840.10008.5.1.4.1.1.88.40 Yes No 1.2.840.10008.5.1.4.1.1.88.50 Yes No 1.2.840.10008.5.1.4.1.1.88.59 Yes No 1.2.840.10008.5.1.4.1.1.88.65 Yes No 1.2.840.10008.5.1.4.1.1.88.67 Yes No 1.2.840.10008.5.1.4.1.1.128 Yes No 1.2.840.10008.5.1.4.1.1.129 Yes No 1.2.840.10008.5.1.4.1.1.481.1 Yes No 1.2.840.10008.5.1.4.1.1.481.2 Yes No 1.2.840.10008.5.1.4.1.1.481.3 Yes No 1.2.840.10008.5.1.4.1.1.481.4 Yes No 1.2.840.10008.5.1.4.1.1.481.5 Yes No 1.2.840.10008.5.1.4.1.1.481.6 Yes No 1.2.840.10008.5.1.4.1.1.481.7 Yes No 1.2.840.10008.5.1.4.1.1.12.1. Yes No 1.2.840.10008.5.1.4.1.1.12.2.1 Yes No 1.2.840.10008.5.1.4.1.1.104.1 Yes No 1.2.840.10008.5.1.4.1.1.4.3 Yes No 1.2.840.10008.5.1.4.1.1.6.2 Yes No 1.2.840.10008.5.1.4.1.1.9.4.2 Yes No 1.2.840.10008.5.1.4.1.1.9.5.1 Yes No 1.2.840.10008.5.1.4.1.1.9.6.1 Yes No 1.2.840.10008.5.1.4.1.1.11.5 Yes No 1.2.840.10008.5.1.4.1.1.13.1.3 Yes No 1.2.840.10008.5.1.4.1.1.66.5 Yes No 1.2.840.10008.5.1.4.1.1.78.1 Yes No 1.2.840.10008.5.1.4.1.1.78.2 Yes No 1.2.840.10008.5.1.4.1.1.78.3 Yes No LAUREL BRIDGE SOFTWARE, INC. 500 CREEK VIEW ROAD SUITE 200 NEWARK, DE 19711 TEL: 302-453-0222 FAX: 302-453-9480 WWW.LAURELBRIDGE.COM Compass DICOM Conformance Statement - v3.3.1 Page 36 of 47 SOP Classes SOP Class UID SCU SCP Subjective Refraction Measurements 1.2.840.10008.5.1.4.1.1.78.4 Yes No Storage Visual Acuity Measurements Storage 1.2.840.10008.5.1.4.1.1.78.5 Yes No Spectacle Prescription Reports 1.2.840.10008.5.1.4.1.1.78.6 Yes No Storage Macular Grid Thickness and Volume 1.2.840.10008.5.1.4.1.1.79.1 Yes No Report Storage Colon CAD SR Storage 1.2.840.10008.5.1.4.1.1.88.69 Yes No Enhanced PET Image Storage 1.2.840.10008.5.1.4.1.1.130 Yes No Basic Structured Display Storage 1.2.840.10008.5.1.4.1.1.131 Yes No Color Palette Storage 1.2.840.10008.5.1.4.39.1 Yes No Intravascular Optical Coherence 1.2.840.10008.5.1.4.1.1.14.1 Yes No Tomography Image Storage - For Presentation Intravascular Optical Coherence 1.2.840.10008.5.1.4.1.1.14.2 Yes No Tomography Image Storage - For Processing VL Whole Slide Microscopy Image 1.2.840.10008.5.1.4.1.1.77.1.6 Yes No Storage Ophthalmic Axial Measurements 1.2.840.10008.5.1.4.1.1.78.7 Yes No Storage Intraocular Lens Calculations Storage 1.2.840.10008.5.1.4.1.1.78.8 Yes No Ophthalmic Visual Field Static 1.2.840.10008.5.1.4.1.1.80.1 Yes No Perimetry Measurements Storage Implantation Plan SR Storage 1.2.840.10008.5.1.4.1.1.88.70 Yes No DICOS CT Image Storage 1.2.840.10008.5.1.4.1.1.501.1 Yes No DICOS Digital X-Ray Image Storage 1.2.840.10008.5.1.4.1.1.501.2.1 Yes No - For Presentation DICOS Digital X-Ray Image Storage 1.2.840.10008.5.1.4.1.1.501.2.2 Yes No - For Processing DICOS Threat Detection Report 1.2.840.10008.5.1.4.1.1.501.3 Yes No Storage Eddy Current Image Storage 1.2.840.10008.5.1.4.1.1.601.1 Yes No Eddy Current Multi-frame Image 1.2.840.10008.5.1.4.1.1.601.2 Yes No Storage RT Beams Delivery Instruction 1.2.840.10008.5.1.4.34.7 Yes No Storage Generic Implant Template Storage 1.2.840.10008.5.1.4.43.1 Yes No Implant Assembly Template Storage 1.2.840.10008.5.1.4.44.1 Yes No Implant Template Group Storage 1.2.840.10008.5.1.4.45.1 Yes No Query/Retrieve Patient Root Query/Retrieve 1.2.840.10008.5.1.4.1.2.1.1 Yes No Information Model - FIND LAUREL BRIDGE SOFTWARE, INC. 500 CREEK VIEW ROAD SUITE 200 NEWARK, DE 19711 TEL: 302-453-0222 FAX: 302-453-9480 WWW.LAURELBRIDGE.COM Compass DICOM Conformance Statement - v3.3.1 Page 37 of 47 SOP Classes SOP Class UID SCU SCP Patient Root Query/Retrieve 1.2.840.10008.5.1.4.1.2.1.2 Yes No Information Model - MOVE Patient Root Query/Retrieve 1.2.840.10008.5.1.4.1.2.1.3 Yes No Information Model - GET Study Root Query/Retrieve Information Model - FIND 1.2.840.10008.5.1.4.1.2.2.1 Yes No Study Root Query/Retrieve Information Model - MOVE 1.2.840.10008.5.1.4.1.2.2.2 Yes No Study Root Query/Retrieve Information Model - GET 1.2.840.10008.5.1.4.1.2.2.3 Yes No Patient/Study Only Query/Retrieve 1.2.840.10008.5.1.4.1.2.3.1 Yes No Information Model - FIND (Retired) Patient/Study Only Query/Retrieve 1.2.840.10008.5.1.4.1.2.3.2 Yes No Information Model - MOVE (Retired) Workflow Management Storage Commitment 1.2.840.10008.1.20.1 Yes No Modality Worklist Information Model - 1.2.840.10008.5.1.4.31 Yes No FIND Modality Performed Procedure Step 1.2.840.10008.3.1.2.3.3 Yes No SOP Class Verification 1.2.840.10008.1.1 Yes No Print Management Basic Grayscale Print Management Meta SOP Class 1.2.840.10008.5.1.1.9 Yes No Print Job SOP Class 1.2.840.10008.5.1.1.14 Yes No Basic Annotation Box SOP Class 1.2.840.10008.5.1.1.15 Yes No Printer SOP Class 1.2.840.10008.5.1.1.16 Yes No Basic Color Print Management Meta 1.2.840.10008.5.1.1.18 Yes No SOP Class Presentation LUT SOP Class 1.2.840.10008.5.1.1.23 Yes No Basic Print Image Overlay Box SOP 1.2.840.10008.5.1.1.24.1 Yes No Class (Retired) 4.2.2.1.1. Proposed Presentation Contexts Compass can propose a presentation context consisting of any SOP class listed in Table 4.2.2.1-1 and any transfer syntax listed in Table 4.2.2.1.1-1 below: Abstract Syntax Name * * Table 4.2.2.1.1-1 Transfer Syntax Transfer Syntax UID Name Explicit VR Little 1.2.840.10008.1.2.1 Endian Implicit VR Little 1.2.840.10008.1.2 Endian SCU Yes Yes SCP No No LAUREL BRIDGE SOFTWARE, INC. 500 CREEK VIEW ROAD SUITE 200 NEWARK, DE 19711 TEL: 302-453-0222 FAX: 302-453-9480 WWW.LAURELBRIDGE.COM Abstract Syntax Name * * * * * * * * * * * * * * * * * Compass DICOM Conformance Statement - v3.3.1 Page 38 of 47 Transfer Syntax Name Explicit VR Big Endian JPEG Baseline (Process 1) JPEG Extended (Process 2 & 4) JPEG Lossless, Non-Hierarchical (Process 14) JPEG Lossless, NonHierarchical, First-Order Prediction (Process 14 [Selection Value 1]) JPEG-LS Lossless JPEG-LS Lossy (Near-Lossless) JPEG 2000 (Lossless Only) JPEG 2000 JPEG 2000 Part 2 Multi- component (Lossless Only) JPEG 2000 Part 2 Multi- component JPIP Referenced JPIP Referenced Deflate MPEG2 Main Profile @ Main Level MPEG2 Main Profile @ High Level MPEG-4 AVC/H.264 Stereo High Profile / Level 4.1 MPEG-4 AVC/H.264 BDCompatible High Profile / Level 4.1 Transfer Syntax UID 1.2.840.10008.1.2.2 1.2.840.10008.1.2.4.50 1.2.840.10008.1.2.4.51 1.2.840.10008.1.2.4.57 1.2.840.10008.1.2.4.70 1.2.840.10008.1.2.4.80 1.2.840.10008.1.2.4.81 1.2.840.10008.1.2.4.90 1.2.840.10008.1.2.4.91 1.2.840.10008.1.2.4.92 1.2.840.10008.1.2.4.93 1.2.840.10008.1.2.4.94 1.2.840.10008.1.2.4.95 1.2.840.10008.1.2.4.100 1.2.840.10008.1.2.4.101 1.2.840.10008.1.2.4.102 1.2.840.10008.1.2.4.103 SCU Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes SCP No No No No No No No No No No No No No No No No No LAUREL BRIDGE SOFTWARE, INC. 500 CREEK VIEW ROAD SUITE 200 NEWARK, DE 19711 TEL: 302-453-0222 FAX: 302-453-9480 WWW.LAURELBRIDGE.COM Abstract Syntax Name * * * * * * * * * Compass DICOM Conformance Statement - v3.3.1 Page 39 of 47 Transfer Syntax Name MPEG-4 AVC/H.264 High Profile / Level 4.2 for 2D Video MPEG-4 AVC/H.264 High Profile / Level 4.2 for 3D Video MPEG-4 AVC/H.264 Stereo High Profile / Level 4.2 HEVC/H.265 Main Profile / Level 5.1 HEVC/H.265 Main 10 Profile / Level 5.1 RLE Lossless SMPTE ST 2110-20 Uncompressed Progressive Active Video SMPTE ST 2110-20 Uncompressed Interlaced Active Video SMPTE ST 2110-30 PCM Digital Audio Transfer Syntax UID 1.2.840.10008.1.2.4.104 1.2.840.10008.1.2.4.105 1.2.840.10008.1.2.4.106 1.2.840.10008.1.2.4.107 1.2.840.10008.1.2.4.108 1.2.840.10008.1.2.5 1.2.840.10008.1.2.7.1 1.2.840.10008.1.2.7.2 1.2.840.10008.1.2.7.3 SCU Yes Yes Yes Yes Yes Yes Yes Yes Yes SCP No No No No No No No No No * Indicates any SOP class from Table 4.2.2.1-1. NOTE: A SOP Class can be proposed in any of the following transfer syntaxes from the table below, so long as it is sent out in that same transfer syntax that it was received in; i.e., Compass cannot decompress it or recompress it into a different transfer syntax. Table 4.2.2.1.1-2 Transfer Syntax Name Transfer Syntax UID JPEG 2000 Part 2 Multi-component (Lossless Only) 1.2.840.10008.1.2.4.92 JPEG 2000 Part 2 Multi-component 1.2.840.10008.1.2.4.93 JPIP Referenced 1.2.840.10008.1.2.4.94 JPIP Referenced Deflate 1.2.840.10008.1.2.4.95 MPEG2 Main Profile @ Main Level 1.2.840.10008.1.2.4.100 MPEG2 Main Profile @ High Level 1.2.840.10008.1.2.4.101 MPEG-4 AVC/H.264 Stereo High Profile / Level 4.1 1.2.840.10008.1.2.4.102 MPEG-4 AVC/H.264 BD-Compatible High Profile / Level 1.2.840.10008.1.2.4.103 LAUREL BRIDGE SOFTWARE, INC. 500 CREEK VIEW ROAD SUITE 200 NEWARK, DE 19711 TEL: 302-453-0222 FAX: 302-453-9480 WWW.LAURELBRIDGE.COM 4.1 MPEG-4 AVC/H.264 High Profile / Level 4.2 for 2D Video MPEG-4 AVC/H.264 High Profile / Level 4.2 for 3D Video MPEG-4 AVC/H.264 Stereo High Profile / Level 4.2 HEVC/H.265 Main Profile / Level 5.1 HEVC/H.265 Main 10 Profile / Level 5.1 SMPTE ST 2110-20 Uncompressed Progressive Active Video SMPTE ST 2110-20 Uncompressed Interlaced Active Video SMPTE ST 2110-30 PCM Digital Audio Compass DICOM Conformance Statement - v3.3.1 Page 40 of 47 1.2.840.10008.1.2.4.104 1.2.840.10008.1.2.4.105 1.2.840.10008.1.2.4.106 1.2.840.10008.1.2.4.107 1.2.840.10008.1.2.4.108 1.2.840.10008.1.2.7.1 1.2.840.10008.1.2.7.2 1.2.840.10008.1.2.7.3 4.2.2.2. Association Establishment Policies 4.2.2.2.1. General The SCU AE can only request the opening of an Association. It cannot accept requests to open Associations from external Application Entities. The DICOM standard Application Context Name for DICOM is always proposed: Application Context Name Table 4.2.2.2.1-1 DICOM Application Context For SCU AE 1.2.840.10008.3.1.1.1 4.2.2.2.2. Number of Associations in Store-and-Forward mode The maximum number of simultaneous Associations is configurable. The SCU AE can initiate simultaneous Associations to a given external Destination AE up to the maximum number configured. Each Destination AE can have its own configurable maximum number of simultaneous Associations, but not more than the system-wide maximum number of simultaneous Associations will be honored. If the first attempt to open an Association fails then the SCU AE will reschedule the task to attempt it again after a configurable time delay. The total number of times to attempt Association establishment is configurable, with the default being 3. 4.2.2.2.3. Number of Associations in Direct Routing mode The maximum number of simultaneous Associations is configurable. The SCU AE can initiate simultaneous Associations to a given external Destination AE up to the maximum number configured. Each Destination AE can have its own configurable maximum number of simultaneous Associations, but not more than the system-wide maximum number of simultaneous Associations will be honored. Table 4.2.2.2.2-1 Number Of Associations For SCU AE Maximum number of simultaneous Associations 25 (Configurable) 4.2.2.2.4. Asynchronous Nature The SCU AE does not support asynchronous communication (multiple outstanding transactions over a single Association). All Association requests must be completed and acknowledged before a new operation can be initiated. LAUREL BRIDGE SOFTWARE, INC. 500 CREEK VIEW ROAD SUITE 200 NEWARK, DE 19711 TEL: 302-453-0222 FAX: 302-453-9480 WWW.LAURELBRIDGE.COM Compass DICOM Conformance Statement - v3.3.1 Page 41 of 47 Table 4.2.2.2.3-1 Asynchronous Nature For SCU AE Maximum number of outstanding asynchronous transactions 1 (Not Configurable) 4.2.2.2.5. Implementation Identifying Information Table 4.2.2.2.4-1 DICOM Implementation Class And Version For SCU AE Implementation Class UID 1.2.840.114089.1.0.0.3.4.46 Implementation Version Name DCF 3.4.46c Note that the SCU AE and SCP AE use the same Implementation Class UID and Implementation Version Name. This Version Name is updated with each new release of the product software, as the different AE versions are never released independently. 4.2.2.3. Association Initiation Policy 4.2.2.3.1. Activity Send Images to an External Peer AE in Store-and-Forward mode 4.2.2.3.1.1 Description and Sequencing of Activity The SCU AE will initiate a new Association to transmit images. An Association Request is sent to the specified CSTORE Destination AE and upon successful negotiation of the required Presentation Context the image transfer is started. In all cases an attempt will be made to transmit all the indicated images in a single Association, but this may not always be possible. The Association will be released when all the images have been sent. If an error occurs during transmission over an open Association then the image transfer is halted, unless configured to continue. Figure 4.2.2.3.1.1-1 Sequencing of Activity Send Images to an External Peer AE The following sequencing constraints illustrated in Figure 4.2.2.3.1.1-1 apply to the SCU AE: 1. SCU AE opens a new Association with the Peer Storage SCP AE. 2. SCU AE sends Composite SOP Instances. LAUREL BRIDGE SOFTWARE, INC. 500 CREEK VIEW ROAD SUITE 200 NEWARK, DE 19711 TEL: 302-453-0222 FAX: 302-453-9480 WWW.LAURELBRIDGE.COM 3. SCU AE closes the Association. Compass DICOM Conformance Statement - v3.3.1 Page 42 of 47 4.2.2.3.1.2 SOP Specific Conformance for Verification SOP Class Standard conformance is provided to the DICOM Verification Service Class as an SCU. The Verification Service as an SCU is actually only supported as a diagnostic service tool for network communication issues. SOP Specific Conformance for Image SOP Classes Composite DICOM SOP Instances are maintained as DICOM Part 10 compliant files in the Compass database. The entire set of tags received with the image will be saved in Compass; this includes all Private and SOP Extended Elements. When a SOP Instance is selected for export, its content will be exported as it was originally received except for a few possible exceptions. Any of the tags whose values can have been altered due to filtering changes administered on Compass or changes to the state of the image data due to compression can be altered when the SOP Instance is exported. The SCU AE will exhibit the following Behavior according to the Status Code value returned in a C-STORE Response from a destination C-STORE SCP: Service Status Success Refused Error Error Warning Warning Warning Warning Warning Table 4.2.2.3.1.2-1 SCU AE C-STORE Response Status Handling Behavior Further Meaning Error Code Behavior Success 0000 The SCP has successfully stored the SOP Instance. If all SOP Instances in a store job have status Success then the store job is marked as Sent. Out of Resources A700 A7FF This is treated as a failure. The store job will be requeued if it has not reached its max attempts. Data Set does not match A900 A9FF This is treated as a failure. The store SOP Class job will be requeued if it has not reached its max attempts. Cannot Understand C000-CFFF This is treated as a failure. The store job will be requeued if it has not reached its max attempts. Coercion of Data Elements B000 Compass can configurable treat this status as success or failure. If treated as failure the store job will be requeued if it has not reached its max attempts. Data Set does not match B007 Compass can configurable treat this SOP Class status as success or failure. If treated as failure the store job will be requeued if it has not reached its max attempts. Elements Discarded B006 Compass can configurable treat this status as success or failure. If treated as failure the store job will be requeued if it has not reached its max attempts. Attribute List Error 0107 Compass can configurable treat this status as success or failure. If treated as failure the store job will be requeued if it has not reached its max attempts. Attribute Value Out of 0116 Compass can configurable treat this Range status as success or failure. If treated as failure the store job will be requeued if it has not reached its max attempts. LAUREL BRIDGE SOFTWARE, INC. 500 CREEK VIEW ROAD SUITE 200 NEWARK, DE 19711 TEL: 302-453-0222 FAX: 302-453-9480 WWW.LAURELBRIDGE.COM Service Status * Further Meaning * Compass DICOM Conformance Statement - v3.3.1 Page 43 of 47 Error Code Other Behavior This is treated as a failure. The store job will be requeued if it has not reached its max attempts. Table 4.2.2.3.1.2-2 SCU AE Communication Failure Behavior Exception Behavior Timeout expiry for an expected DICOM Message The Association is aborted using a DICOM A-ABORT Response (DIMSE level timeout). and the store-job is requeued if it has not reached its max attempts. Timeout expiry for an expected DICOM PDU or TCP/IP The Association is aborted using a DICOM A-ABORT packet (Low-level timeout). and the store-job is requeued if it has not reached its max attempts. Association A-ABORTed by the SCP or the network The store-job is requeued if it has not reached its max layers indicate communication loss (i.e. low-level attempts. TCP/IP socket closure) 4.2.2.3.2. Activity Service Patient Root Q/R MOVE or Study Root Q/R MOVE Request Over New Association(s) 4.2.1.3.2.1 Description and Sequencing of Activity for Store-and-Forward Workflow The SCU AE will always initiate a new Association(s) when a Peer AE requests Patient Root Q/R MOVE or Study Root MOVE. Figure 4.2.1.3.2.1-1 Sequencing Of Activity Send Images after Move Request Over New Association(s) LAUREL BRIDGE SOFTWARE, INC. 500 CREEK VIEW ROAD SUITE 200 NEWARK, DE 19711 TEL: 302-453-0222 FAX: 302-453-9480 WWW.LAURELBRIDGE.COM Compass DICOM Conformance Statement - v3.3.1 Page 44 of 47 The following sequencing constraints illustrated in Figure 4.2.1.3.2.1-1 apply to the SCU AE for handling Patient Root MOVE or Study Root MOVE Requests using a new Association in Store-and-Forward mode. This model is also applicable in Direct Routing mode where Compass has been configured to respond to Query/Retrieve Requests instead of passing them on. 7. Peer AE opens an Association with the SCP AE. 8. Peer AE requests Patient Root Q/R MOVE or Study Root Q/R MOVE (peer sends C-MOVE-RQ and -SCP AE responds with intermediate C-MOVE-RSP messages over time to indicate that the request is being processed). 9. Peer AE keeps the Association open while the SCU AE processes the request. 10. For Study Root Q/R MOVE, or Patient Root Q/R MOVE with a Query/Retrieve Level (tag 0008,0052) value other than "PATIENT", the following steps ensue: a. SCU AE opens an Association with a peer AE. b. SCU AE sends C-STORE-RQ messages, one per image which matches the identifier provided in the C-MOVE-RQ. c. SCU AE closes the Association with the peer AE. For Patient Root Q/R MOVE with a Query/Retrieve Level (tag 0008.0052) value of "PATIENT", the above steps are repeated once for each study which matches the specified patient in the C-MOVE-RQ, resulting in the SCU AE requesting one such Association per matching Study. 4.2.1.3.2.2 Proposed Presentation Contexts The SCP AE will propose Presentation Contexts which are determined from the headers of the DICOM files to be transferred, as well as the configuration in Compass. 4.2.2.4. Association Acceptance Policy The SCU AE does not accept Associations. 4.3. Network Interfaces 4.3.1. Physical Network Interface Compass supports any network interface that implements the TCP/IP protocol. 4.3.2. Additional Protocols None. 4.3.3. IPv4 and IPv6 Support This product only supports IPv4 connections. 4.4. Configuration 4.4.1. AE Title/Presentation Address Mapping 4.4.1.1. Local AE Titles The specification of AE titles, TCP/IP addresses, and ports is configurable. Application Entity SCU AE SCP AE Role SCU SCP Table 4.4.1.1-1 Default AE Title Compass CALLED Default TCP/IP Port <None> 11112 The SCU and SCP Application Entities can be configured to have the same AE title. The SCP Application Entity has a default Application Entity of CALLED. It can be configured to accept any Called AE Title. LAUREL BRIDGE SOFTWARE, INC. 500 CREEK VIEW ROAD SUITE 200 NEWARK, DE 19711 TEL: 302-453-0222 FAX: 302-453-9480 WWW.LAURELBRIDGE.COM Compass DICOM Conformance Statement - v3.3.1 Page 45 of 47 4.4.2. Parameters Table 4.4.2-1 SCP AE Configuration Parameters Parameter Configurable Default Value Maximum Send PDU Size Yes 1048576 Maximum Receive PDU Size Yes 1048576 Maximum number of simultaneous Associations Yes 25 Time-out waiting on an open Association for the next Request message (DIMSE Request message, Association Close Request, etc.) (DIMSE timeout) Yes 1 Hour Archival time of SOP Instances that Yes 72 Hours have been successfully sent to a Peer AE in Store-and-Forward mode Always open a new Association to send a Storage Commitment Push Model Notification request (NEVENT-REPORT-RQ) in Store-andForward mode No TRUE Assume Relational Query (i.e. treat Hierarchical C-FIND Request as if it were Relational) Yes TRUE Max Query Responses Yes 1000 Parameter Maximum Send PDU Size Maximum Receive PDU Size Maximum number of simultaneous Associations SCU AE time-out waiting for a Response to a DIMSE Request message. (DIMSE timeout) Number of times a failed send job to a C-STORE Destination is automatically retried in Store-andForward mode Amount of time to wait between retries to a C-STORE Destination in Store-and-Forward mode Amount of time to wait prior to initial send attempt to a C-STORE Destination in Store-and-Forward mode Table 4.4.2-2 SCU AE Configuration Parameters Configurable Default Value Yes 1048576 Yes 1048576 Yes 25 Yes 1 Hour Yes 2 retries (for a total of 3 attempts) Yes 1 minute Yes 0 minutes LAUREL BRIDGE SOFTWARE, INC. 500 CREEK VIEW ROAD SUITE 200 NEWARK, DE 19711 TEL: 302-453-0222 FAX: 302-453-9480 WWW.LAURELBRIDGE.COM Parameter Always combine SOP Instances for the same Study Instance UID received on separate Associations within a given time window into a single outbound Association in Store-and-Forward mode Compass DICOM Conformance Statement - v3.3.1 Page 46 of 47 Configurable Yes FALSE Default Value 5. Media Interchange Compass does not support Media Interchange. 6. Support of Extended Character Sets All Compass DICOM applications support the following: ISO_IR 100 (ISO 8859-1:1987 Latin Alphabet No. 1 supplementary set) for routing decisions and filtering; other character sets can be stored and forwarded. LAUREL BRIDGE SOFTWARE, INC. 500 CREEK VIEW ROAD SUITE 200 NEWARK, DE 19711 TEL: 302-453-0222 FAX: 302-453-9480 WWW.LAURELBRIDGE.COM Compass DICOM Conformance Statement - v3.3.1 Page 47 of 47 7. Security It is assumed that Compass is used within a secured environment. It is assumed that a secured environment includes at a minimum: a. Firewall or router protections to ensure that only approved external hosts have network access to Compass. b. Firewall or router protections to ensure that Compass only has network access to approved external hosts and services. c. Any communication with external hosts and services outside the locally secured environment use appropriate secure network channels (e.g. such as a Virtual Private Network (VPN)). Alternatively, Compass can be configured to send and receive DIMSE messages via an encrypted mechanism such as TLS. Other network security procedures such as automated intrusion detection may be appropriate in some environments. Additional security features may be established by the local security policy and are beyond the scope of this conformance statement. 7.1. Security Profiles 7.1.1. TLS Security Compass supports the BCP195 TLS Secure Transport Connection Profile (See DICOM PS3.15 2015c Security and System Management Profiles, Appendix B.9) for authentication and encryption of communication between it and other DICOM clients and servers. Compass supports TLS version 1.2 as required by this profile, as well as TLS versions 1.0 and 1.1 (if configured by the user). Within the Compass application, for secure DICOM communication on the sending copy of Compass one should select any/all of the Enable TLS options under the Advanced section of the DICOM Destinations pane. On the receiving copy of Compass one should select any/all of the Enable TLS options under the DICOM Incoming section of the DICOM System pane; additionally, one must configure the TLS options in the Advanced Settings section of this pane. To properly configure incoming TLS connections, on the DICOM System pane, the Listen Port, TLS Certificate path and certificate Password must be set. The Listen Port default is port 2762, as recommended by the standard (chapter 15 section B.9: The BCP195 TLS Secure Transport Connection Profile); it is the port on which Compass will receive TLS encrypted communications (e.g., DICOM associations). The TLS Certificate path should be set to the file system location of the certificate that Compass should present for identification to clients. It is suggested that the certificate be a standard PKCS#12 certificate and it must contain an exportable private key. The Password must be set to the password for the private key in the certificate. Note: using a certificate format that does not password protect the private key allows the password setting to be ignored. 7.1.2. Anonymization See the document named CNF-LBS-DICOM-Anonymizer.pdf for conformance statement information regarding deidentification and re-identification. 7.2. Association Level Security The SCP AE can be configured to check the following values when determining whether to accept Association Open Requests: Calling AE Title Called AE Title Remote IP Address Application Context LAUREL BRIDGE SOFTWARE, INC. 500 CREEK VIEW ROAD SUITE 200 NEWARK, DE 19711 TEL: 302-453-0222 FAX: 302-453-9480 WWW.LAURELBRIDGE.COMMicrosoft Word for Microsoft 365