Commvault CCA V4.1. Commvault Clinical Archive v4.1 DICOM Conformance Statement

Transcription

1 Commvault Commvault Clinical Archive, (CCA) DICOM Conformance Statement CCA V4.1 Commvault Clinical Archive v4.1 DICOM Conformance Statement Last modified 3/24/2017 7:23:00 AM

2 1. CONFORMANCE STATEMENT OVERVIEW The Commvault Clinical Archive, DICOM Archive, (CCA), is a self-contained networked computer system for archiving diagnostic medical images. External systems cam send images to the archive for permanent storage, and retrieve the images or query for information about the images. The CCA can also be configured by Commvault to provide read-only query and retrieval services for images stored in the archive file systems of certain legacy PACS archives. The CCA stores DICOM instances internally as Part 10 DICOM format to maximize data migration to other archive products. The system conforms to the DICOM standard to allow the sharing of medical information with other digital imaging systems using the services listed in the table below. SOP Classes Verification Table 1-1 NETWORK SERVICES ser of Service (SC) Provider of Service (SCP) Verification Transfer All storage SOP Classes, as included in Table or as configured Query/Retrieve Patient Root Q/R - FIND Patient Root Q/R - MOVE Study Root Q/R - FIND Study Root Q/R - MOVE Modality Worklist Information Model FIND No Page 2 of 52

3 2. TABLE OF CONTENTS CONFORMANCE STATEMENT OVERVIEW TABLE OF CONTENTS INTRODCTION ADIENCE REMARKS DEFINITIONS, TERMS AND ABBREVIATIONS REFERENCES NETWORKING IMPLEMENTATION MODEL Application Data Flow Diagram Functional Definition of AEs Sequencing of Real-World Activities AE SPECIFICATIONS STORAGE-SC Application Entity Specification QERY-RETRIEVE-SCP Application Entity Specification STORAGE-SCP Application Entity Specification QERY-RETRIEVE-SC Application Entity Specification WORKLIST-QERY-SC Application Entity Specification NETWORK INTERFACES Physical Network Interface Additional Protocols CONFIGRATION AE Title/Presentation Address Mapping Parameters MEDIA INTERCHANGE IMPLEMENTATION MODEL Application Data Flow Diagram Functional definitions of AE s Sequencing of Real World Activities File Meta Information for Implementation Class and Version AE SPECIFICATIONS Online Media Application Entity Specification Offline Media Application Entity Specification AGMENTED AND PRIVATE APPLICATION PROFILES Augmented Application Profiles Private Application Profiles MEDIA CONFIGRATION The CCA uses the open Commvault Data Platform to store the DICOM Part 10 files as archived tomes as files. SPPORT OF CHARACTER SETS SECRITY SECRITY PROFILES NONE SPPORTED. ASSOCIATION LEVEL SECRITY APPLICATION LEVEL SECRITY ANNEXES PRIVATE NAS/DAS MEDIA FORMAT SPECIFICATION PRIVATE SOP CLASSES PRIVATE TRANSFER SYNTAXES PRIVATE ATTRIBTES Revision History Page 3 of 52

4 Page 4 of 52

5 3. INTRODCTION 3.1. ADIENCE This document is intended for hospital staff, health system integrators, software designers or implementers. It is assumed that the reader has a working understanding of DICOM REMARKS DICOM compliance alone, does not guarantee interoperability. However, the Conformance Statement facilitates a first-level validation for interoperability between different applications supporting the same DICOM functionality. This Conformance Statement is not intended to replace validation with other DICOM equipment to ensure proper exchange of information intended. The scope of this Conformance Statement is to facilitate communication between the Commvault Clinical Archive, (CCA) and other DICOM systems. The Conformance Statement should be read and understood in conjunction with the DICOM Standard [DICOM]. However, by itself it is not guaranteed to ensure the desired interoperability and a successful interconnectivity. The user should be aware of the following important issues: The comparison of different Conformance Statements is the first step towards assessing interconnectivity between the CCA and other DICOM conformant equipment. Define and perform test procedures to validate the desired level of connectivity DEFINITIONS, TERMS AND ABBREVIATIONS Abstract Syntax Application Entity (AE) Application Entity Title (AET) DICOM Protocol Data nit (PD) Service Object Pair (SOP) Service Class Provider (SCP) Service Class ser (SC) SOP Class Transfer Syntax nique Identifier (ID) Equivalent to SOP Class An end-point in a DICOM information exchange The name of an Application Entity to identify other DICOM application entities on the network. Digital Imaging and Communications in Medicine A packet of DICOM networked message A DICOM unit of interoperability The AE role of being the provider of the DICOM service The AE role of being the user of the DICOM service The SOP Class identifies the type message or service The type data encoding used message exchange A DIOCOM globally unique identifier defined by DICOM 3.4. REFERENCES Digital Imaging and Communications in Medicine (DICOM) Standard at Page 5 of 52

6 4. NETWORKING 4.1. IMPLEMENTATION MODEL Application Data Flow Diagram The division of the CCA into the separate DICOM Application Entities represents a somewhat arbitrary partitioning of functionality. For the purpose of this document they are organized in this manner so as to detail their independent logical functionality. By default all of the defined Application Entities have different AE Titles. However, the CCA can be configured so that the QERY-RETRIEVE-SCP AE and STORAGE-SC AE share the same Application Entity Title. However, the QERY-RETRIEVE-SCP AE and STORAGE-SCP AE must have separate Application Entity Titles. DICOM Standard Interface QERY-RETRIEVE-SCP AE Requests Image Export by Storage-SC AE QERY-RETRIEVE-SCP Application Entity STORAGE-SC Application Entity Remote Application Entity issues Verification, Query or Retrieve Command Remote Application Entity receives instances to store STORAGE-SC AE Requests Image Read from MEDIA- STORAGE-SC QERY-RETRIEVE-SC Application Entity Remote Application Entity responds to verify storage transfers STORAGE-SC AE Requests Image Storage to MEDIA- STORAGE-SC MEDIA-STORAGE-SC Application Entity STORAGE-SCP Application Entity WORKLIST QERY-SC Application Entity Semperdata Archive DICOM Standard Media Storage Interface Remote Application Entity sends instances Remote Worklist Application Entity scheduled procedures Composite Objects Stored in DICOM Standard Media Filesets Figure CCA DICOM DATA FLOW DIAGRAM Page 6 of 52

7 The Application Entities detailed in the Application Data Flow Diagram are all components of a software system running on Microsoft Windows Server platforms. The STORAGE-SC AE sends Composite SOP Instances. It handles requests from the QERY- RETRIEVE-SCP AE to transmit Images to a specific DICOM destination. The STORAGE-SC AE functions as a C-STORE SC. The STORAGE-SC AE may also be invoked with a web user interface. The QERY-RETRIEVE-SCP AE handles incoming query and retrieve requests. It handles external queries for Patient, Study, Series, and Image data, and also Image retrieval requests. The QERY-RETRIEVE-SCP AE handles retrieval requests by issuing a command to the STORAGE- SC AE to send the requested Images to the destination specified by the Remote AE. The QERY-RETRIEVE-SCP AE functions as an SCP for C-FIND and C-MOVE Requests. The STORAGE-SCP AE receives incoming DICOM images and adds them to the CCA database. It responds to external Storage and Verification Requests as a Service Class Provider (SCP) for C- STORE and C-ECHO requests. The STORAGE-SC AE queries the remote storage SCP for the purpose of: a. Performing inventory assessment of the DICOM patients, studies, series and images on a remote AE using C-FIND b. Verifying prior storage operations to the target storage SCP using C-FIND c. Performs study transfers from a source PACS to the local CCA archive using C-MOVE d. Read back verification of prior storage operations by retrieving instances from the target storage SCP using C-MOVE. The WORKLIST-QERY-SC AE queries the remote worklist SCP to obtain a list of scheduled patients and migrated unsent studies to the destination storage SCP. The MEDIA-STORAGE-SCP AE Transfers composite Objects to and from Storage media written in DICOM media storage formats Functional Definition of AEs Functional Definition of STORAGE-SC Application Entity The QERY-RETRIEVE-SCP AE can invoke the STORAGE-SC AE to trigger the transfer of specific images to a remote destination AE. The STORAGE-SC AE must be correctly configured with the host and port number of any external DICOM AE s that are to be C-MOVE retrieval destinations. The Presentation Context is determined from the headers of the DICOM files to be transferred, together with configured presentation context constraints. This AE converts the transfer syntax the DICOM image object if the original Presentation Context is not supported by the remote destination AE or when compression is preferred. The STORAGE-SC AE chooses by referring to a configurable transfer syntax map that constrains the transfer syntax to the Storage SCP. The map specifies the transfer syntax map for each connected Storage SCP and for each SOP Class (abstract syntax) Functional Definition of QERY-RETRIEVE-SCP Application Entity The QERY-RETRIEVE-SCP AE waits for another application to connect at the presentation address configured for its Application Entity Title. When another application connects, QERY-RETRIEVE-SCP AE expects it to be a DICOM application. QERY-RETRIEVE-SCP AE will accept Associations with Presentation Contexts for SOP Classes of the DICOM Query-Retrieve Service Class, and Verification Service Class. It will handle query and retrieve requests on these Presentation Contexts and respond with data objects with values corresponding to the contents of the CCA database. For C-MOVE requests Page 7 of 52

8 the destination for the image objects is determined from the Destination AE Title contained in the C- MOVE request. When a retrieval request is received, the QERY-RETRIEVE-SCP AE issues a command to the STORAGE-SC AE to send the specified images to the C-MOVE Destination AE Functional Definition of STORAGE-SCP Application Entity The STORAGE-SCP AE waits for another application to connect at the presentation address configured for its Application Entity Title. When another application connects, the STORAGE-SCP AE expects it to be a DICOM application. The STORAGE-SCP AE will accept Associations with Presentation Contexts for SOP Classes of the Verification and Storage Classes. Any composite SOP Instances received on such Presentation Contexts will be added to the CCA database Functional Definition of QERY-RETRIEVE-SC Application Entity The QERY-RETRIEVE-SC is activated from: An inventory assessment application for cataloging the DICOM information on a PACS using C- FIND Automated inbound and outbound streaming processes that move DICOM studies into and out of the CCA local archive using C-MOVE Verification operations that verify that each instance transfer can be queried (C-FIND) and that selected instances can be ready back correctly by comparing retrieved (C-MOVE) and archived instances Functional Definition of the WORKLIST-QERY-SC Application Entity The WORKLIST-QERY-SC periodically queries the worklist to find the patients scheduled for procedures. CCA then migrates any un-migrated studies into destination storage AE so that the studies are available as priors for reading new studies Functional Definition of MEDIA-STORAGE-SC Application Entity The MEDIA-STORAGE-SC AE stores images received by the STORAGE-SCP AE, and retrieves images for the STORAGE-SC AE to send in response to C-MOVE Requests Sequencing of Real-World Activities The only sequencing constraint that exists across all the CCA Application Entities is the fact that a Composite SOP Instance must be completely received by the STORAGE-SCP AE before Query-Retrieve Requests related to this SOP Instance can be successfully handled. Page 8 of 52

9 Peer Storage SCP AE Peer Query- Retrieve SC AE Peer Storage- SC AE STORAGE- SCP AE QERY- RETRIEVE- SCP AE STORAGE- SC AE C-STORE - Peer AE Sends Composite SOP Instance C-FIND - Peer AE Queries for Information related to SOP Instance Return Information related to SOP Instance Notification of Images to be sent to C-MOVE Destination AE in R C-MOVE - Peer AE Requests Retrieval of SOP Instance Images Sent to Peer AE in Response Figure SEQENCING CONSTRAINTS 4.2. AE SPECIFICATIONS STORAGE-SC Application Entity Specification SOP Classes The STORAGE-SC AE provides Standard Conformance to the following DICOM V3.0 SOP Classes: 1 Table STANDARD STORAGE SOP CLASSES SOP Class Name SOP Class ID SC SCP Computed Radiography Image Storage Digital X-Ray Image Storage For Presentation Digital X-Ray Image Storage For Processing Digital Mammography X-Ray Image Storage 1 The archive supports all DICOM Storage SOP Classes as they are added to the DICOM Standard: Page 9 of 52

10 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 Legacy Converted Enhanced CT Image Storage ltrasound Multi-frame Image Storage (Retired) ltrasound Multi-frame Image Storage MR Image Storage Enhanced MR Image Storage MR Spectroscopy Storage Enhanced MR Color Image Storage Legacy Converted Enhanced CT Image Storage Nuclear Medicine Image Storage (Retired) ltrasound Image Storage (Retired) ltrasound Image Storage Enhanced S Volume 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) Standalone Curve Storage (Retired) lead ECG Waveform Storage General ECG Waveform Storage Ambulatory ECG Waveform Storage Hemodynamic Waveform Storage Cardiac Electrophysiology Waveform Storage Basic Voice Audio Waveform Storage Standalone Modality LT Storage (Retired) Standalone VOI LT Storage (Retired) Grayscale Softcopy Presentation State Storage SOP Class Page 10 of 52

11 Color Softcopy Presentation State Storage SOP Class Pseudo-Color Softcopy Presentation State Storage SOP Class Blending Softcopy Presentation State Storage SOP Class X-Ray Angiographic Image Storage Enhanced XA Image Storage X-Ray Radiofluoroscopic Image Storage Enhanced XRF Image Storage X-Ray Angiographic Bi-Plane Image Storage (Retired) X-Ray 3D Angiographic Image Storage X-Ray 3D Craniofacial Image Storage Breast Tomosynthesis Image Storage Breast Projection X-Ray Image Storage For Presentation Breast Projection X-Ray Image Storage For Processing Intravascular Optical Coherence Tomography Image Storage - For Presentation Intravascular Optical Coherence Tomography Image Storage - For Processing Nuclear Medicine Image Storage Parametric Map Storage Raw Data Storage Spatial Registration Storage Spatial Fiducials Storage Deformable Spatial Registration Storage Segmentation Storage Tractography Results Storage Real World Value Mapping Storage Surface Scan Mesh Storage Surface Scan Point Cloud Storage VL Image Storage (Retired) VL Multi-frame Image Storage (Retired) VL Endoscopic Image Storage Video Endoscopic Image Storage VL Microscopic Image Storage Video Microscopic Image Storage VL Slide-Coordinates Microscopic Image Storage VL Photographic Image Storage Page 11 of 52

12 Video Photographic Image Storage Ophthalmic Photography 8 Bit Image Storage Ophthalmic Photography 16 Bit Image Storage Stereometric Relationship Storage Ophthalmic Tomography Image Storage Wide Field Ophthalmic Photography Stereographic Projection Image Storage Wide Field Ophthalmic Photography 3D Coordinates Image Storage VL Whole Slide Microscopy Image Storage Lensometry Measurements Storage Autorefraction Measurements Storage Keratometry Measurements Storage Subjective Refraction Measurements Storage Visual Acuity Measurements Storage Spectacle Prescription Report Storage Ophthalmic Axial Measurements Storage Intraocular Lens Calculations Storage Macular Grid Thickness and Volume Report Ophthalmic Visual Field Static Perimetry Measurements Storage Ophthalmic Thickness Map Storage Corneal Topography Map Storage Basic Text SR Storage Enhanced SR Storage Comprehensive SR Storage Comprehensive 3D SR Storage Extensible SR Storage Procedure Log Storage Mammography CAD SR Storage Key Object Selection Document Chest CAD SR Storage X-Ray Radiation Dose SR Storage Radiopharmaceutical Radiation Dose SR Storage Colon CAD SR Storage Implantation Plan SR Storage Acquisition Context SR Storage Encapsulated PDF Storage Encapsulated CDA Storage Positron Emission Tomography Image Storage Page 12 of 52

13 Legacy Converted Enhanced PET Image Storage Standalone PET Curve Storage (Retired) Enhanced PET Image Storage Basic Structured Display Storage RT Image Storage RT Dose Storage RT Structure Set Storage RT Beams Treatment Record Storage RT Plan Storage RT Brachy Treatment Record Storage RT Treatment Summary Record Storage RT Ion Plan Storage RT Ion Beams Treatment Record Storage RT Beams Delivery Instruction Storage RT Brachy Application Setup Delivery Instruction Storage Generic Implant Template Storage Implant Assembly Template Storage Implant Template Group Storage The set of SOP Classes is configurable to exclude or support additional or SOP Classes. CCA also implements the private Change Object Storage SOP Class. Table PRIVATE STORAGE SOP CLASSES SOP Class ID SC SCP Change Object Storage Association Policies General The STORAGE-SC AE can only form Associations when requested to do so by the QERY- RETRIEVE-SCP AE or by commands entered into the Administrative user interface. The STORAGE- SC 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: Table DICOM Application Context for STORAGE-SC AE Application Context Name Page 13 of 52

14 CCA rejects association requests from applications when the AE Title is not listed within the configuration unless configured to accept any AE Title Number of Associations The AE sets no limit to the maximum number of simultaneous Associations. Table Number of Associations as a SC for STORAGE-SC AE Maximum number of simultaneous Associations No set limit Asynchronous Nature The STORAGE-SC 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. Table ASYNCHRONOS NATRE AS A SC FOR STORAGE-SC AE Maximum number of outstanding asynchronous transactions Implementation Identifying Information Table DICOM IMPLEMENTATION CLASS AND VERSION FOR STORAGE-SC AE Implementation Class ID Implementation Version Name Semperdata_1.0 Note that this AE use the same Implementation Class ID as the other network AEs. All CCA AE s use the same Implementation Version Name. The Version Name is updated with each new release of the product software that changes DICOM behavior Association Initiation Policy Activity Send Images The primary activity triggering a send is a move request from an external Application Entity. Additional activities include: The archive user selects studies to send from the user interface An archive plug-in requests studies for sending (see the manuals associated with those plugins) Outbound migration Pre-fetch Transfer and updates to a remote CCA for replication TABLE TRANSFER SYNTAXES FOR SEND INSTANCES Name ID Implicit VR Little Endian Explicit VR Little Endian Deflated Explicit VR Little Endian Page 14 of 52

15 JPEG Baseline, Lossy JPEG 8-Bit Image Compression JPEG Extended, Lossy JPEG 12-Bit Image Compression JPEG Lossless, Non-Hierarchical, First-Order Prediction (Process 14 [Selection Value 1]): Default Transfer Syntax for Lossless JPEG Image Compression JPEG-LS Lossless Image Compression JPEG-LS Lossy (Near-Lossless) Image Compression JPEG 2000 Image Compression (Lossless Only) JPEG 2000 Image Compression MPEG2 Main Main Level RLE Lossless CCA provides full (level 2) conformance. This means that upon sending an instance received via DICOM it will send out all attributes that it received including private attributes from other manufacturers (though private attributes can be excluded in the configuration). The CCA association policy is to transfer with no information loss. CCA will negotiate to accept and send images in a lossless transfer syntax. In general, CCA will have images in a variety of transfer syntaxes, even lossy ones when the source sends lossy compressed images. When the inserted into the archive is lossy, the attempt will be to first negotiate the transfer using the lossy transfer syntax, to avoid further degradation of image quality later in the image lifecycle. Therefore, in the default configuration, CCA proposes the transfer syntax of the stored instance as well as the default transfer syntaxes (default settings are ILE plus ELE though this is configurable) and may propose lossless compressed syntaxes when configured to do so. When sending an image to the remote Storage SCP AE, the Storage SC converts the image to a transfer syntax chosen from a configurable map. Each AE may have its own configurable map that specifies the transfer syntax to present for the abstract syntax to store Description and Sequencing of Activity The STORAGE-SC AE will initiate a new Association when the QERY-RETRIEVE-SCP AE invokes the STORAGE-SC AE to transmit images. The QERY-RETRIEVE-SCP AE will issue such a command whenever it receives a valid C-MOVE Request. An Association Request is sent to the specified C-MOVE 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. The STORAGE-SC AE will not attempt to independently retry the image export. Page 15 of 52

16 Peer Storage SCP AE Peer Query- Retrieve SC AE QERY- RETRIEVE-SCP AE STORAGE- SC AE Peer AE Queries for Patient, Study, Series, or Image Information Return Patient, Study, Series, or Image Information Peer AE Requests Retrieval of Studies, Series, or Images Notification of Images to be sent to C-MOVE Destination AE in Response Open Association Images Sent to Peer AE in Response Close Association Figure SEQENCING OF ACTIVITY - SEND IMAGES REQESTED BY AN EXTERNAL PEER AE The following sequencing constraints illustrated in Figure apply to the STORAGE-SC AE: 1. Peer AE requests retrieval of Study, Series, or Images from QERY-RETRIEVE-SCP AE (C-MOVE- RQ). 2. QERY-RETRIEVE-SCP AE signals STORAGE-SC AE to send the image Composite SOP Instances indicated in the C-MOVE-RQ to the C-MOVE Destination AE. 3. STORAGE-SC AE opens a new Association with the indicated C-MOVE Destination AE. 4. STORAGE-SC AE sends the indicated Composite SOP Instances. 5. STORAGE-SC AE closes the Association. 6. The Verification Service is only supported as a utility function for Service staff. It is used only as a diagnostic tool Proposed Presentation Contexts STORAGE-SC AE will propose Presentation Contexts as shown in the following table: Page 16 of 52

17 Table PROPOSED PRESENTATION CONTEXTS BY THE STORAGE-SC AE Presentation Context Table Abstract Syntax Transfer Syntax Role Ext. Neg. Name ID Name ID Verification DICOM Implicit VR Little Endian Any Composite Instance Storage SOP Class, as included in Table Any Composite Instance Storage SOP Class, as included in Table Any Composite Instance Storage SOP Class, as included in Table Any Composite Instance Storage SOP Class, as included in Table Any Composite Instance Storage SOP Class, as included in Table Any Composite Instance Storage SOP Class, as included in Table Any Composite Instance Storage SOP Class, as included in Table Any Composite Instance Storage SOP Class, as included in Table SC None Explicit VR Little Endian SC None Implicit VR Little Endian SC None Deflated Explicit VR Little Endian JPEG Lossless, Non- Hierarchical, First-Order Prediction (Process 14 [Selection Value 1]): Default Transfer Syntax for Lossless JPEG Image Compression JPEG Baseline (Process 1): Default Transfer Syntax for Lossy JPEG 8 Bit Image Compression JPEG Extended (Process 2 & 4): Default Transfer Syntax for Lossy JPEG 12 Bit Image Compression (Process 4 only) JPEG 2000 Image Compression (Lossless Only) JPEG 2000 Image Compression SC None SC None SC None SC None SC None SC None At the time of establishing the association, the set of DICOM objects to send is known. The policy goal is to send each object in the transfer syntax as originally accepted and stored, or alternatively, a transfer syntax that can be reversibly converted from the stored transfer syntax, so as to prevent any information loss. As an example, a study may contain ultrasound multi-frame images of JPEG lossy, JPEG lossless and RLE. Five Presentation Contexts will be proposed: the three compressed just cited, ELE and ILE. 2 If all are accepted, the stored images will export with transfer syntax as stored. If the JEPG lossless transfer syntax is not accepted, CCA will convert and send as ELE. 2 Explicit Big Endian is absent by default but can be added if configured Page 17 of 52

18 If the JPEG lossy transfer syntax or RLE is not accepted, CCA will transfer as ELE or JPEG lossless depending on the configuration. This situation results in unavoidable information loss since is it is not reversible. pon receiving a CMOVE request, CCA will identify the location of all the objects in the request. The objects can be resident (as part of CCA archive storage) or remote when CCA is configured with connectors other systems. Regardless of the location of the objects, these will be retrieved one by one. If the data is resident, object ordering logic ensures that the IODs are produced in an orderly sequence, one series at the time 3. If data is stored remotely in other PACS systems, the order of the objects sent is not guaranteed. Transfer Syntax and SOP Class information is therefore known before sending each image. The internal algorithm first identifies whether the specific presentation context, once the defined transformation rules were applied (e.g. enforced conversion to Jpeg 2000 for All Mammography Data), is found in the accepted presentation context list. If not, the new presentation context is added and the association is renegotiated. By default, the ILE and ELE transfer syntaxes are proposed for each SOP Class in a certain transfer. This setting is overridden by the usage of Transfer Syntax Maps. If a transfer syntax map has been defined for a certain SOP Class, only the defined transfer syntax will be proposed in the presentation context list 4. CCA will never flood the target system with the entire set SOP classes in its presentation context list. CCA will propose at most 127 presentation contexts, oddly numbered. If the target accepts more than one presentation contexts, the ones with the smallest presentation context ID will be picked SOP Specific Conformance for Verification SOP Class Standard conformance is provided to the DICOM Verification Service Class as an SC. The Verification Service as an SC is intended only a diagnostic service tool for network communication SOP Specific Conformance for Image SOP Classes Composite DICOM SOP Instances are maintained as DICOM Part 10 compliant files in the CCA database. The entire set of tags received with the image will be saved in CCA; this includes all Private and SOP Extended Elements. When a SOP Instance is selected for export from CCA, its content will be exported as it was originally received except for a few possible exceptions. Some of the Patient demographic and Study information Elements whose values can have been altered due to changes administered on CCA or changes to the state of the image data due to compression can be altered when the SOP Instance is exported. The Patient demographic and Study information can be entered or altered manually, or from HL7 messaging. The replacement behavior depends on which specific DICOM and HL7 services are supported. Also, this behavior is configurable. Values can be altered without changing the SOP Instance ID unless otherwise noted. Refer to the Annex for the specific details of which Elements can have their values altered at time of export. 3 There is no implied ordering of the series however, nor of the instances within a series (no Series number/instance number ordering). 4 The reason for this logic is that if a transfer syntax map is defined, there is specific intent is to use that map. If this was not the case, a disaster scenario can be: 100MB Cine ltrasound is stored Lossy Compressed. The target does not accepted and the SC would fall back to ELE or ILE, sending a 2.4GB IOD. Multiply this by 10,000 ultrasounds and you can endanger an enterprise storage this way. Page 18 of 52

19 The original value of any DICOM tag that is changed by CCA is stored in the Original Attributes Sequence as follows: DICOM Tag Name DICOM Tag Value Original Attributes Sequence (0400,0561) >Source of Previous Values >Attribute Modification DateTime >Modifying System >Reason for the Attribute Modification >Modified Attributes Sequence (0400,0564) SORCE PACS (0400,0562) Date/time when the modification has been performed (0400,0563) LAITEK INC. CCA (0400,0565) CORRECT (0400,0550) The original value If a DICOM attribute is modified multiple times, it will be stored multiple times in the Original Attributes Sequence, with different timestamps. The CCA CCA creates files called Service Logs that can be used to monitor their status and diagnose any problems that may arise. If any error occurs during DICOM communication then appropriate messages are always output to these Service Logs. In addition, error messages may be output as alerts to the ser Interface in certain cases. The STORAGE-SC 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 Table STORAGE-SC AE C-STORE RESPONSE STATS HANDLING BEHAVIOR Further Meaning Error Code Behavior Success Success 0000 The SCP has successfully stored the exported SOP Instance. A message is sent to the QERY-RETRIEVE- SCP AE indicating successful export. The QERY- RETRIEVE-SCP AE will send the appropriate PENDING or SCCESS Status in the C-MOVE Response. Success indication message is output to the Service Logs. No message is posted to the ser Interface. Error Cannot Process C000 - CFFF This is treated as a permanent Failure. A message is sent to the QERY-RETRIEVE-SCP AE indicating an export failure and the Association is released. The QERY- RETRIEVE-SCP AE will send an appropriate Status in the C-MOVE Response. Error indication message is output to the Service Logs. No message is posted to the ser Interface. All Status Codes indicating an error or refusal are treated as a permanent failure. The STORAGE-SC AE never automatically resends images when an error Status Code is returned in a C-STORE Response. For specific behavior regarding Status Code values returned in C-MOVE Responses, refer to the Services Supported as an SCP by the QERY-RETRIEVE-SCP AE. Page 19 of 52

20 Table STORAGE-SC AE COMMNICATION FAILRE BEHAVIOR Exception Timeout expiry for an expected DICOM PD or TCP/IP packet (Low-level timeout). Behavior The Association is aborted using a DICOM A-ABORT and a message is sent to the QERY-RETRIEVE-SCP AE indicating an export failure. The QERY-RETRIEVE-SCP AE will send an appropriate Status in the C-MOVE Response. Error indication message is output to the Service Logs. Association A-ABORTed by the SCP or the network layers indicate communication loss (i.e. low-level TCP/IP socket closure) A retry attempts to establish another association and resume transfer. An error indication message is output to the Service Logs Association Acceptance Policy The STORAGE-SC AE does not accept Associations QERY-RETRIEVE-SCP Application Entity Specification SOP Classes The QERY-RETRIEVE-SCP AE provides Standard Conformance to the following DICOM V3.0 SOP Classes: Table SOP CLASSES FOR QERY-RETRIEVE-SCP AE SOP Class Name SOP Class ID SC SCP Verification No No Patient Root Q/R Information Model - FIND No Patient Root Q/R Information Model - MOVE No Study Root Q/R Information Model - FIND No Study Root Q/R Information Model - MOVE No Association Policies General The QERY-RETRIEVE-SCP AE will never initiate Associations; it only accepts Association Requests from external DICOM AEs. The QERY-RETRIEVE-SCP AE will accept Associations for Verification, C- FIND, and C-MOVE requests. In the case of a C-MOVE request, the QERY-RETRIEVE-SCP AE will issue a command to the STORAGE-SC AE to initiate an Association with the Destination DICOM AE to send images as specified by the originator of the C-MOVE Request. The DICOM standard Application Context Name for DICOM 3.0 is always accepted: Table DICOM APPLICATION CONTEXT FOR QERY-RETRIEVE-SCP AE Application Context Name Page 20 of 52

21 Number of Associations The QERY-RETRIEVE-SCP AE can support multiple simultaneous Associations. Each time the QERY-RETRIEVE-SCP AE receives an Association, a child process spawns to process the Verification, Query, or Retrieval request. Table NMBER OF SIMLTANEOS ASSOCIATIONS AS A SCP FOR QERY-RETRIEVE-SCP AE Maximum number of simultaneous Associations No set limit Asynchronous Nature The QERY-RETRIEVE-SCP 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. Table ASYNCHRONOS NATRE AS A SCP FOR QERY-RETRIEVE-SCP AE Maximum number of outstanding asynchronous transactions Implementation Identifying Information The implementation information for the Application Entity is: Table DICOM IMPLEMENTATION CLASS AND VERSION FOR QERY-RETRIEVE-SCP AE Implementation Class ID Implementation Version Name Semperdata_1.0 Note that this AE use the same Implementation Class ID as the other network AEs. All CCA CCA AE s use the same Implementation Version Name. The Version Name is updated with each new release of the product software that changes DICOM behavior Association Initiation Policy The QERY-RETRIEVE-SCP AE does not initiate Associations Association Acceptance Policy Activity Query Retrieval Request Description and Sequencing of Activity The QERY-RETRIEVE-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 is rejected. It can be configured to only accept Associations with certain hosts (using TCP/IP address) and/or Application Entity Titles. If the QERY-RETRIEVE-SCP AE receives a query (C-FIND) request then the response(s) will be sent over the same Association used to send the C-FIND-Request. If the QERY-RETRIEVE-SCP AE receives a retrieve request (C-MOVE) then the responses will be sent over the same Association used to send the C-MOVE-Request. The QERY-RETRIEVE-SCP AE will Page 21 of 52

22 notify the STORAGE-SC to send the requested SOP Instances to the C-MOVE Destination. The STORAGE-SC AE notifies the QERY-RETRIEVE-SCP AE of the success or failure of each attempt to send a Composite SOP Instance to the peer C-MOVE Destination AE. The QERY-RETRIEVE-SCP AE then sends a C-MOVE Response indicating this status after each attempt. Once the STORAGE-SC AE has finished attempting to transfer all the requested SOP Instances, the QERY-RETRIEVE-SCP AE sends a final C-MOVE Response indicating the overall status of the attempted retrieval. Peer C-MOVE Destination AE Peer Query- Retrieve SC AE QERY- RETRIEVE-SCP AE STORAGE- SC AE Open Association Peer AE Queries for Patient, Study, Series, or Image Information Return Patient, Study, Series, or Image Information Close Association Open Association Peer AE Requests Retrieval of Studies, Series, or Images Notification of Images to be sent to C-MOVE Destination AE in Response Open Association Repeat Image Sent to C-MOVE Destination C-MOVE-RSP sent for each Image Sent Notification of success or failure for each attempt Close Association Final C-MOVE-RSP sent Close Association Figure SEQENCING OF ACTIVITY HANDLING QERY AND RETRIEVAL REQESTS The following sequencing constraints illustrated in Figure apply to the QERY-RETRIEVE-SCP AE for handling queries (C-FIND-Requests): 1. Peer AE opens an Association with the QERY-RETRIEVE-SCP AE. 2. Peer AE sends a C-FIND-RQ Message 3. QERY-RETRIEVE-SCP AE returns a C-FIND-RSP Message to the peer AE with matching information. A C-FIND-RSP is sent for each entity matching the identifier specified in the C-FIND- RQ. A final C-FIND-RSP is sent indicating that the matching is complete. 4. Peer AE closes the Association. Note that the peer AE does not have to close the Association immediately. Further C-FIND or C-MOVE Requests can be sent over the Association before it is Page 22 of 52

23 closed. The following sequencing constraints illustrated in apply to the QERY-RETRIEVE-SCP AE for handling retrievals (C-MOVE-Requests): 1. Peer AE opens an Association with the QERY-RETRIEVE-SCP AE. 2. Peer AE sends a C-MOVE-RQ Message 3. QERY-RETRIEVE-SCP AE notifies the STORAGE-SC AE to send the Composite SOP Instances to the peer C-MOVE Destination AE as indicated in the C-MOVE-RQ. 4. After attempting to send a SOP Instance, the STORAGE-SC AE indicates to the QERY- RETRIEVE-SCP AE whether the transfer succeeded or failed. The QERY-RETRIEVE-SCP AE then returns a C-MOVE-RSP indicating this success or failure. 5. Once the STORAGE-SC AE has completed all attempts to transfer the SOP Instances to the C- MOVE Destination AE, or the first failure occurred, the QERY-RETRIEVE-SCP AE sends a final C-MOVE-RSP indicating the overall success or failure of the retrieval. 6. Peer AE closes the Association. Note that the peer AE does not have to close the Association immediately. Further C-FIND or C-MOVE Requests can be sent over the Association before it is closed. The QERY-RETRIEVE-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 PD (see PS 3.8, Section 9.3.4). The following abbreviations are used in the Source column: a. 1 DICOM L service-user b. 2 DICOM L service-provider (ASCE related function) c. 3 DICOM L service-provider (Presentation related function) Table ASSOCIATION REJECTION REASONS Result Source Reason/Diag Explanation 1 rejectedpermanent 1 rejectedpermanent a b 3 calling-aetitle-notrecognized 1 no-reasongiven 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 Accepted Presentation Contexts QERY-RETRIEVE-SCP AE will accept Presentation Contexts as shown in the following table: Table ACCEPTED PRESENTATION CONTEXTS BY THE QERY-RETRIEVE-SCP AE Page 23 of 52

24 Presentation Context Table Abstract Syntax Transfer Syntax Role Ext. Neg. Name ID Name ID Verification DICOM Implicit VR Little Endian Patient Root Q/R Information Model - FIND Patient Root Q/R Information Model - MOVE Study Root Q/R Information Model - FIND Study Root Q/R Information Model - MOVE DICOM Explicit VR Little Endian DICOM Implicit VR Little Endian DICOM Explicit VR Little Endian DICOM Implicit VR Little Endian DICOM Explicit VR Little Endian DICOM Implicit VR Little Endian DICOM Explicit VR Little Endian DICOM Implicit VR Little Endian SCP None SCP None SCP None SCP None SCP None SOP Specific Conformance for Query SOP Classes The QERY-RETRIEVE-SCP AE supports hierarchical queries and not relational queries. There are no attributes always returned by default. Only those attributes requested in the query identifier are returned. Query responses always return values from the CCA CCA database. Exported SOP Instances are always updated with the latest values in the database prior to export. Thus, a change in Patient demographic information will be contained in both the C-FIND Responses and any Composite SOP Instances exported to a C-MOVE Destination AE. Patient Root Information Model All required search keys on each of the four levels (Patient, Study, Series, and Image) are supported. However, the Patient ID (0010,0020) key must have at least a partial value if the Patient s Name (0010,0010) is not present in a Patient Level query. Study Root Information Model All the required search keys on each of the three levels (Study, Series, and Image) are supported. If no partial values are specified for Study attributes then either the Patient ID (0010,0020) key or the Patient s Name (0010,0010) must have at least a partial value specified. The tables 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, a R will indicate Range Matching, a * will denote wildcard matching, an will indicate universal matching, and L will indicate that ID lists are supported Page 24 of 52

25 for matching. NONE indicates that no matching is supported, but that values for this Element in the database can be returned. All queries are case insensitive matching. The supported query elements below are extensible with configuration. Table PATIENT ROOT C-FIND SCP SPPORTED ELEMENTS Level Name Attribute Name Patient Level Patient's Name Patient ID Patient's Birth Date Patient s Birth Time Patient's Sex Other Patient IDs Other Patient Names Study Level Study ID Study Instance ID Study Date Study Time Accession Number Modalities in Study Institution Name Referring Physician's Name Study Description Number of Study related Images Series Level Tag VR Types of Matching (0010,0010) (0010,0020) (0010,0030) (0010,0032) (0010,0040) (0010,1000) (0010,1001) (0020,0010) (0020,000D) (0008,0020) (0008,0030) (0008,0050) 0008,0061) (0008,0080) (0008,0090) (0008,1030) (0020,1208) PN LO DA TM CS LO PN SH I DA TM SH CS LO PN LO IS,* NONE NONE NONE S,R, S,R, Modality (0008,0060) CS Series Description (0008,103E) LO Series Number 0020,0011) IS Series Instance ID (0020,000E) I Request Attribute Sequence (0040,0275 SQ >Requested Procedure ID (0040,1001) SH >Scheduled Procedure Step ID (0040,0009) SH Performed Procedure Step Start Date (0040,0244) DA Performed Procedure Step Start Time (0040,0245) TM Body Part Examined (0018,0015) CS Number of Series Related Instances (0020,1209) I NONE Composite Instance Level Instance Number (0020,0013) IS SOP Instance ID (0020,0018) I SOP Class ID (0020,0016) I Page 25 of 52

26 Content Date 0008,0023) DA Image SOP Classes Samples per Pixel (0028,0002) S Photometric Interpretation (0028,0004) CS Number of Frames (0028,0008) IS Rows (0028,0010) S Columns (0028,0011) S Bits Allocated (0028,0100) S High Bit (0028,0102) S Pixel Representation (0028,0103) S SR SOP Classes Referenced Request Sequence (0040,A370) SQ >Study Instance ID (0020,000D) I >Accession Number (0008,0050) SH >Requested Procedure ID (0040,1001) SH >Requested Procedure Code Sequence (0032,1064 SQ >>Code Value (0008,0100) SH >>Coding Scheme Designator (0008,0102) SH >>Coding Scheme Version (0008,0103) SH >>Code Meaning (0008,0100) LO Content Template Sequence (0040,A504) SQ >Template Identifier (0040,DB00) CS Key Object SOP Class Content Date Content Time Observation DateTime Referenced Request Sequence >Study Instance ID >Accession Number >Requested Procedure ID >Requested Procedure Code Sequence >>Code Value >>Coding Scheme Designator >>Coding Scheme Version >>Code Meaning Concept Name Code Sequence >Code Value >Coding Scheme Designator >Coding Scheme Version >Code Meaning (0008,0023) (0008,0033) (0040,A032) (0040,A370) (0020,000D) (0008,0050) (0040,1001) (0032,1064) (0008,0100) (0008,0102) (0008,0103) (0008,0104) (0040,A043) (0008,0100) (0008,0102) (0008,0103) (0008,0104) DA TM DT SQ I SH SH SQ SH SH SH LO SQ SH SH SH LO Table STDY ROOT C-FIND SCP SPPORTED ELEMENTS Page 26 of 52