ClearCanvas Workstation DICOM Conformance Statement. Document Version: 1.5

Transcription

1 ClearCanvas Workstation DICOM Conformance Statement Document Version: 1.5 Product Name(s): Release: ClearCanvas Workstation 2.0 SP1 Date: February 22, 2010

2 1 CONFORMANCE STATEMENT OVERVIEW 1.1 OVERVIEW The application supports querying a remote system for a list of DICOM objects that may then be retrieved to the local system and displayed, in the case of images. It also supports sending locally loaded objects across the network to another system. Only hierarchical study root query and retrieval is supported for both SCP and SCU query operations. The application is capable of storing, retrieving and displaying: - All image storage SOP Classes defined as of DICOM 2008, including multi-frame images. - Images of any photometric interpretation. - Images compressed with the following Transfer Syntaxes: - RLE Lossless - JPEG Baseline (Process 1) - JPEG Extended (Process 2 & 4) - JPEG Lossless, Non-Hierarchical (Process 14) - JPEG Lossless, Non-Hierarchical, First-Order Prediction (Process 14 [Selection Value 1]) - Key object selection documents containing image entries - Grayscale softcopy presentation states and color softcopy presentation states for images in a key object selection document Transfer SOP Classe s Table NETWORK SERVICES User of Service (SCU) Color Softcopy Presentation State Storage Yes Key Object Selections only Yes Computed Radiography Image Storage Stored and Viewed Yes CT Image Storage Stored and Viewed Yes Digital Intra-oral X-Ray Image Storage For Presentation Digital Intra-oral X-Ray Image Storage For Processing Digital Mammography X-Ray Image Storage For Presentation Digital Mammography X-Ray Image Storage For Processing Stored and Viewed Stored and Viewed Stored and Viewed Stored and Viewed Digital X-Ray Image Storage For Presentation Stored and Viewed Yes Digital X-Ray Image Storage For Processing Stored and Viewed Yes Enhanced CT Image Storage Stored and Limited Viewing Yes Enhanced MR Image Storage Stored and Limited Viewing Yes Enhanced XA Image Storage Stored and Limited Viewing Yes Enhanced XRF Image Storage Stored and Limited Viewing Yes Provider of Service (SCP) Yes Yes Yes Yes Page 2

3 Grayscale Softcopy Presentation State Storage Yes Key Object Selections only Yes Key Object Selection Document Storage Yes Images only Yes MR Image Storage Stored and Viewed Yes Multi-frame Grayscale Byte Secondary Capture Image Storage Multi-frame Grayscale Word Secondary Capture Image Storage Multi-frame Single Bit Secondary Capture Image Storage Multi-frame True Color Secondary Capture Image Storage Stored only Stored only Stored only Stored only Nuclear Medicine Image Storage (Retired) Stored and Viewed Yes Nuclear Medicine Image Storage Stored and Viewed Yes Ophthalmic Photography 16 Bit Image Storage Stored and Viewed Yes Ophthalmic Photography 8 Bit Image Storage Stored and Viewed Yes Ophthalmic Tomography Image Storage Stored only Yes Positron Emission Tomography Image Storage Stored and Viewed Yes RT Image Storage Stored and Viewed Yes Secondary Capture Image Storage Stored and Viewed Yes Ultrasound Image Storage Stored and Viewed Yes Ultrasound Image Storage (Retired) Stored and Viewed Yes Ultrasound Multi-frame Image Storage Stored and Viewed Yes Ultrasound Multi-frame Image Storage (Retired) Stored and Viewed Yes Video Endoscopic Image Storage Stored only Yes Video Microscopic Image Storage Stored only Yes Video Photographic Image Storage Stored only Yes VL Endoscopic Image Storage Stored only Yes VL Microscopic Image Storage Stored only Yes VL Photographic Image Storage Stored only Yes VL Slide-Coordinates Microscopic Image Storage Stored only Yes X-Ray 3D Angiographic Image Storage Stored only Yes X-Ray 3D Craniofacial Image Storage Stored only Yes X-Ray Angiographic Bi-Plane Image Storage (Retired) Stored and Viewed X-Ray Angiographic Image Storage Stored and Viewed Yes X-Ray Radiofluoroscopic Image Storage Stored and Viewed Yes Query/Retrieve Study Root Information Model FIND Yes Hierarchical only Yes Study Root Information Model MOVE Yes Hierarchical only Yes Yes Yes Yes Yes Yes Page 3

4 Media Storage Application Profile Compact Disk - Recordable Table MEDIA SERVICES Write Files (FSC or FSU) Read Files (FSR) General Purpose CD-R No Yes Not DICOMDIR DVD General Purpose DVD-RAM No Yes Not DICOMDIR Page 4

5 2 TABLE OF CONTENTS 1...CONFORMANCE STATEMENT OVERVIEW OVERVIEW TABLE OF CONTENTS INTRODUCTION REVISION HISTORY AUDIENCE REMARKS NETWORKING IMPLEMENTATION MODEL Application Data Flow Functional Definitions of AEs Sequencing of Real-World Activities AE SPECIFICATIONS ECHO-SCP ECHO-SCU STORAGE-SCP STORAGE-SCU FIND-SCP FIND-SCU MOVE-SCP MOVE-SCU NETWORK INTERFACES Physical Network Interface Additional Protocols IPv4 and IPv6 Support NETWORK CONFIGURATION AE Title/Presentation Address Mapping Parameters MEDIA INTERCHANGE IMPLEMENTATION MODEL Application Data Flow Functional Definitions of AE s Sequencing of Real-World Activities AE SPECIFICATIONS MEDIA-FSR MEDIA-FSU AUGMENTED AND PRIVATE PROFILES Augmented Profiles Private Profiles MEDIA CONFIGURATION SUPPORT OF CHARACTER SETS OVERVIEW CHARACTER SETS CHARACTER SET CONFIGURATION SECURITY SECURITY PROFILES Page 5

6 Basic Application Level Confidentiality Profile Audit Trail Message Format Profile ASSOCIATION LEVEL SE CURITY APPLICATION LEVEL SE CURITY ANNEXES IOD CONTENTS Created SOP Instances Usage of Attributes from Received IODs Attribute Mapping Coerced/Modified Fields DATA DICTIONARY OF PRIVATE ATTRIBUTES CODED TERMINOLOGY AND TEMPLATES GRAYSCALE IMAGE CONSISTENCY STANDARD EXTENDED/SPECIALIZED/PRIVATE SOP CLASSES PRIVATE TRANSFER SYNTAXES Page 6

7 3 INTRODUCTION 3.1 REVISION HISTORY Document Version Date of Issue Author Description 1.0 July 25, 2008 Henry Hernaez Version for Final Review 1.1 December 11, 2008 Stewart Bright Version for Final Review 1.2 July 22, 2009 Jasper Yeh, Stewart Bright Version for Final Review 1.3 September 18, 2009 Jasper Yeh Version for Final Review 1.4 December 17, 2009 Jasper Yeh, Stewart Bright Version for Final Review 1.5 February 22, 2010 Stewart Bright Version for Final Review 3.2 AUDIENCE This document is written for the people that need to understand how ClearCanvas Workstation will integrate into their healthcare facility. This includes both those responsible for overall imaging network policy and architecture, as well as integrators and developers 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 and developers 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 This application has been approved for clinical use in Canada only. Page 7

8 4 NETWORKING 4.1 IMPLEMENTATION MODEL Application Data Flow Local User Creates Key Object Selection Local User Requests Send STORAGE-SCU Application Entity Requested Images Received by Remote AE Local User Requests Verification ECHO-SCU Application Entity Remote AE Receives Verify Command Local User Requests Query Local User Views Images of Patient with Prior Studies FIND-SCU Application Entity Remote AE Receives Query or Retrieve Command Local User Requests Retrieval MOVE-SCU Application Entity Remote AE Receives Query or Retrieve Command STORAGE-SCP Application Entity Unsolicited or Requested Instances Sent by Remote AE FIND-SCP Application Entity Remote AE Requests Query or Retrieval Unsolicited or Requested Instances Sent to Remote AE via STORAGE-SCU MOVE-SCP Application Entity Remote AE Requested Image Retrieval ECHO-SCP Application Entity Verification Requested by Remote AE DICOM Standard Interface Figure IMPLEMENTATION MODEL The application is a.net application that provides a user interface, internal database and network listener that spawns additional threads as necessary to handle incoming connections, as well as limited media support. Conceptually, the network services may be modeled as the following separate AEs, though in fact all the AEs share a single (configurable) AE Title: Page 8

9 - ECHO-SCP, which responds to verification requests - ECHO-SCU, which sends a verification request - STORAGE-SCP, which receives incoming composite instances - STORAGE-SCU, which sends outbound composite instances - FIND-SCP, which receives incoming queries for lists of studies - FIND-SCU, which queries remote AEs for lists of studies - MOVE-SCP, which responds to requests for studies - MOVE-SCU, which retrieves selected studies Functional Definitions of AEs ECHO-SCP ECHO-SCP waits in the background for connections, will accept associations with Presentatio n Contexts for the SOP Class of the Verification Service Class, and will respond successfully to echo requests ECHO-SCU ECHO-SCU is activated through the user interface when a user selects a remote AE to verify (from a pre - configured list), then initiates a verification STORAGE-SCP STORAGE-SCP waits in the background for connections, will accept associations with Presentation Contexts for SOP Classes of the Storage Service Class, and will store the received instances to the local database where they may subsequently be listed and viewed through the user interface STORAGE-SCU STORAGE-SCU is typically activated through the user interface when a user selects studies from the local database and requests that they be sent to a remote AE (selected from a pre -configured list). STORAGE-SCU can also be activated internally when a user closes a viewed study and there are pending images marked as key objects. Softcopy presentation states created at the time the images were marked as key objects are referenced alongside the source images to create a key object selection document. The key object selection document and any softcopy presentation states are sent to remote AE(s) marked as Default Servers in the configuration. In the case where the study has been opened directly from the remote AE (ie. a ClearCanvas ImageServer), the instances are always sent back to the same remote AE regardless of whether or not it is a Default Server FIND-SCP FIND-SCP waits in the background for connections, will accept associations with Presentation Contexts for the SOP Class of the Study Root Query/Retrieve Information Model FIND Service Class, and will respond successfully to query requests FIND-SCU FIND-SCU is typically activated through the user interface when a user selects a remote AE to query (from a pre-configured list), then initiates a query. FIND-SCU can also be activated internally when a user opens a study for viewing and there is at least one remote AE marked as a Default Server in the configuration. A query is initiated to list prior studies related to the current patient(s) being viewed MOVE-SCP MOVE-SCP waits in the background for connections, will accept associations with Presentation Contexts for the SOP Class of the Study Root Query/Retrieve Information M odel MOVE Service Class, and will respond successfully to move requests by initiating storage of instances to the remote AE. Page 9

10 MOVE-SCU MOVE-SCU is activated through the user interface when a user selects a study for retrieval. A connection to the remote AE is established to initiate the retrieval and the STORAGE -SCP AE receives the retrieved instances Sequencing of Real-World Activities All SCP activities are performed asynchronously in the background and are not dependent on any sequencing. All SCU activities are initiated through the user interface with the following exceptions: - STORAGE-SCU is also initiated internally by both MOVE-SCP and a Send Key Object.Selections operation. - FIND-SCU is also initiated internally by a Query for Prior Studies operation. ECHO-SCU and FIND-SCU activities are typically synchronous and blocking except when FIND-SCU is invoked as a Query for Prior Studies operation, in which case it is asynchronous and non-blocking. STORAGE-SCU and MOVE-SCU activities are asynchronous and non-blocking. 4.2 AE SPECIFICATIONS ECHO-SCP SOP Classe s ECHO-SCP provides Standard Conformance to the following SOP classes: Table SOP CLASSES SUPPORTED BY ECHO SCP SOP Class Name SOP Class UID Verification SOP Class Association Policies General ECHO-SCP accepts but never initiates associations. Table MAXIMUM PDU SIZE RECEIVED AS A SCP FOR ECHO -SCP Maximum PDU size received 114kB (approximate) Number of Associations Table NUMBER OF ASSOCIATIONS AS A SCP FOR ECHO-SCP Maximum number of simultaneous associations Unlimited Asynchronous Nature ECHO-SCP will only allow a single outstanding operation on an Association. Therefore, ECHO-SCP will not perform asynchronous operations window negotiation. Page 10

11 Implementation Identifying Information Table DICOM IMPLEMENTATION CLASS AND VERSION FOR ECHO SCP Implementation Class UID Implementation Version Name Dicom Association Initiation Policy ECHO-SCP does not initiate associations Association Acceptance Policy When ECHO-SCP accepts an association, it will respond to echo requests. The association will be rejected if: - The Called AE Title does not match the AE Title shared by all the SCPs of the application. - The Calling AE Title is not in the application s pre-configured list Activity Receive Echo Reque st Description and Sequencing of Activities As requests are received, they are responded to immediately Accepted Pre sentation Contexts Table ACCEPTABLE PRESENTATION CONTEXTS FOR ECHO-SCP AND RECEIVE ECHO REQUEST Presentation Context Table Abstract Syntax Transfer Syntax Role Extended Negotiation Name UID Name UID Verification Explicit VR Little Endian Extended Negotiation No extended negotiation is performed SOP Specific Conformance Implicit VR Little Endian SOP Specific Conformance to Verification SOP Class ECHO-SCP provides standard conformance to the Verification Service Class Presentation Context Acceptance Criterion SCP None SCP None ECHO-SCP will only accept a Presentation Context compatible with the one listed in Table Transfer Syntax Selection Policies ECHO-SCP will select the first Transfer Syntax proposed by the client that is supported by the SCP, per Presentation Context. ECHO-SCP will accept duplicate Presentation Contexts; that is, if it is offered multiple Presentation Contexts, each of which offers acceptable Transfer Syntaxes, it will accept all Presentation Contexts, applying the same method for selecting a Transfer Syntax for each. Page 11

12 4.2.2 ECHO-SCU SOP Classe s ECHO-SCU provides Standard Conformance to the following SOP classes: Table SOP CLASSES SUPPORTED BY ECHO-SCU SOP Class Name SOP Class UID Verification SOP Class Association Policies General ECHO-SCU initiates but never accepts associations. Table MAXIMUM PDU SIZE RECEIVED AS A SCP FOR ECHO -SCU Maximum PDU size received 114kB (approx.) Number of Associations Table NUMBER OF ASSOCIATIONS AS A SCP FOR ECHO-SCU Maximum number of simultaneous associations Asynchronous Nature ECHO-SCU will only allow a single outstanding operation on an Association. Therefore, ECHO -SCU will not perform asynchronous operations window negotiation Implementation Identifying Information Table DICOM IMPLEMENTATION CLASS AND VERSION FOR ECHO-SCU Implementation Class UID Implementation Version Name Dicom Association Initiation Policy ECHO-SCU attempts to initiate a new association when the user performs the verify action from the user interface to either a single remote AE or a group of remote AEs Activity Send Echo Reque st Description and Sequencing of Activities A single attempt will be made to verify the remote AE. If the verification fails, for whatever reason, no retry will be performed. Page 12

13 Proposed Presentation Contexts Table PROPOSED PRESENTATION CONTEXTS FOR ECHO -SCU AND SEND ECHO REQUEST Presentation Context Table Abstract Syntax Transfer Syntax Role Extended Negotiation Name UID Name UID Verification Explicit VR Little Endian Extended Negotiation No extended negotiation is performed SOP Specific Conformance Implicit VR Little Endian SOP Specific Conformance to Verification SOP Class ECHO-SCU provides standard conformance to the Verification Service Class Presentation Context Acceptance Criterion ECHO-SCU does not accept associations Transfer Syntax Selection Policies SCU None SCU None ECHO-SCU prefers Explicit VR Little Endian Transfer Syntax, which is alway s first in the proposed Presentation Context Association Acceptance Policy ECHO-SCU does not accept associations STORAGE-SCP SOP Classe s STORAGE-SCP provides Standard Conformance to the following SOP classes: Table SOP CLASSES SUPPORTED BY STORAGE-SCP SOP Class Name SOP Class UID Color Softcopy Presentation State Storage Computed Radiography Image Storage CT Image Storage Digital Intra-oral X-Ray Image Storage For Presentation Digital Intra-oral X-Ray Image Storage For Processing Digital Mammography X-Ray Image Storage For Presentation Digital Mammography X-Ray Image Storage For Processing Digital X-Ray Image Storage For Presentation Digital X-Ray Image Storage For Processing Page 13

14 Enhanced CT Image Storage Enhanced MR Image Storage Enhanced XA Image Storage Enhanced XRF Image Storage Grayscale Softcopy Presentation State Storage Key Object Selection Document Storage MR Image Storage Multi-frame Grayscale Byte Secondary Capture Image Storage Multi-frame Grayscale Word Secondary Capture Image Storage Multi-frame Single Bit Secondary Capture Image Storage Multi-frame True Color Secondary Capture Image Storage Nuclear Medicine Image Storage (Retired) Nuclear Medicine Image Storage Ophthalmic Photography 16 Bit Image Storage Ophthalmic Photography 8 Bit Image Storage Ophthalmic Tomography Image Storage Positron Emission Tomography Image Storage RT Image Storage Secondary Capture Image Storage Ultrasound Image Storage Ultrasound Image Storage (Retired) Ultrasound Multi-frame Image Storage Ultrasound Multi-frame Image Storage (Retired) Video Endoscopic Image Storage Video Microscopic Image Storage Video Photographic Image Storage VL Endoscopic Image Storage VL Microscopic Image Storage VL Photographic Image Storage VL Slide-Coordinates Microscopic Image Storage X-Ray 3D Angiographic Image Storage X-Ray 3D Craniofacial Image Storage X-Ray Angiographic Bi-Plane Image Storage (Retired) X-Ray Angiographic Image Storage X-Ray Radiofluoroscopic Image Storage Association Policies General STORAGE-SCP accepts but never initiates associations. Page 14

15 Table MAXIMUM PDU SIZE RECEIVED AS A SCP FOR STORAGE-SCP Maximum PDU size received 114kB (approx.) Number of Associations Table NUMBER OF ASSOCIATIONS AS A SCP FOR STORAGE-SCP Maximum number of simultaneous associations Unlimited Asynchronous Nature STORAGE-SCP will only allow a single outstanding operation on an Association. Therefore, STORAGE - SCP will not perform asynchronous operations window negotiation Implementation Identifying Information Table DICOM IMPLEMENTATION CLASS AND VERSION FOR STORAGE-SCP Implementation Class UID Implementation Version Name Dicom Association Initiation Policy STORAGE-SCP does not initiate associations Association Acceptance Policy When STORAGE-SCP accepts an association, it will respond to storage requests. The association will be rejected if: - The Called AE Title does not match the AE Title shared by all the SCPs of the application. - The Calling AE Title is not in the application s pre-configured list Activity Receive Storage Request Description and Sequencing of Activities As instances are received, they are copied to the local file system and a record inserted into the local database. If the received instance is a duplicate of a previously received instance, the old file and database record will be overwritten with the new one Accepted Pre sentation Contexts Table ACCEPTABLE PRESENTATION CONTEXTS FOR STORAGE-SCP AND RECEIVE STORAGE REQUEST Presentation Context Table Abstract Syntax Transfer Syntax Role Extended Negotiation Name UID Name UID See Table See Table Explicit VR Little Endian Implicit VR Little Endian SCP None SCP None Page 15

16 Extended Negotiation RLE Lossless SCP None JPEG Baseline (Process 1): JPEG Extended (Process 2 & 4) JPEG Lossless, Non-Hierarchical (Process 14) JPEG Lossless, Non-Hierarchical, First-Order Prediction (Process 14 [Selection Value 1]) No extended negotiation is performed, though STORAGE-SCP: - is a Level 2 Storage SCP (Full does not discard any data elements) - does not support digital signatures - does not coerce any received data elements SOP Specific Conformance SOP Specific Conformance to Storage SOP Classe s STORAGE-SCP provides standard conformance to the Storage Service Class Presentation Context Acceptance Criterion SCP None SCP None SCP None SCP None STORAGE-SCP will always accept any Presentation Context for the supported SOP Classes with the supported Transfer Syntaxes. More than one proposed Presentation Context will be accepted for the same Abstract Syntax if the Transfer Syntax is supported, whether or not it is the same as another Presentation Context Transfer Syntax Selection Policies STORAGE-SCP will always select the first Transfer Syntax proposed by the client that is supported by the SCP, per Presentation Context. STORAGE-SCP will accept duplicate Presentation Contexts; that is, if it is offered multiple Presentation Contexts, each of which offers acceptable Transfer Syntaxes, it will accept all Presentation Contexts, applying the same method for selecting a Transfer Syntax for each Response Status STORAGE-SCP will behave as described in the Table below when generating the C-STORE response command message. Table RESPONSE STATUS FOR STORAGE-SCP AND RECEIVE STORAGE REQUEST Service Status Further Meaning Status Code s Reason Failure Processing Failure 0110 Sent when an error occurs trying to save the stored Page 16

17 SOP instance to disk Success 0000 Sent as each SOP is stored STORAGE-SCU SOP Classe s STORAGE-SCU provides Standard Conformance to the following SOP classes: Table SOP CLASSES SUPPORTED BY STORAGE-SCU SOP Class Name SOP Class UID Color Softcopy Presentation State Storage Computed Radiography Image Storage CT Image Storage Digital Intra-oral X-Ray Image Storage For Presentation Digital Intra-oral X-Ray Image Storage For Processing Digital Mammography X-Ray Image Storage For Presentation Digital Mammography X-Ray Image Storage For Processing Digital X-Ray Image Storage For Presentation Digital X-Ray Image Storage For Processing Enhanced CT Image Storage Enhanced MR Image Storage Enhanced XA Image Storage Enhanced XRF Image Storage Grayscale Softcopy Presentation State Storage Key Object Selection Document Storage MR Image Storage Multi-frame Grayscale Byte Secondary Capture Image Storage Multi-frame Grayscale Word Secondary Capture Image Storage Multi-frame Single Bit Secondary Capture Image Storage Multi-frame True Color Secondary Capture Image Storage Nuclear Medicine Image Storage (Retired) Nuclear Medicine Image Storage Ophthalmic Photography 16 Bit Image Storage Ophthalmic Photography 8 Bit Image Storage Ophthalmic Tomography Image Storage Positron Emission Tomography Image Storage RT Image Storage Secondary Capture Image Storage Ultrasound Image Storage Ultrasound Image Storage (Retired) Page 17

18 Ultrasound Multi-frame Image Storage Ultrasound Multi-frame Image Storage (Retired) Video Endoscopic Image Storage Video Microscopic Image Storage Video Photographic Image Storage VL Endoscopic Image Storage VL Microscopic Image Storage VL Photographic Image Storage VL Slide-Coordinates Microscopic Image Storage X-Ray 3D Angiographic Image Storage X-Ray 3D Craniofacial Image Storage X-Ray Angiographic Bi-Plane Image Storage (Retired) X-Ray Angiographic Image Storage X-Ray Radiofluoroscopic Image Storage Association Policies General STORAGE-SCU initiates but never accepts associations. Table MAXIMUM PDU SIZE RECEIVED AS A SCP FOR STORAGE-SCU Maximum PDU size received 114kB (approx.) Number of Associations Table NUMBER OF ASSOCIATIONS AS A SCP FOR STORAGE-SCU Maximum number of simultaneous associations Unlimited Asynchronous Nature STORAGE-SCU will only allow a single outstanding operation on an Association. Therefore, STORAGE - SCU will not perform asynchronous operations window negotiation Implementation Identifying Information Table DICOM IMPLEMENTATION CLASS AND VERSION FOR STORAGE-SCU Implementation Class UID Implementation Version Name Dicom Association Initiation Policy When initiated by the user, STORAGE-SCU attempts to initiate a new association for the study, or group of studies, selected (e.g. one association per user-initiated send operation). When initiated by MOVE- SCP, one association is initiated per move request. When initiated internally in response to the user closing one or more studies that contain newly-created key object selections and associated softcopy Page 18

19 presentation states, one association is initiated per study (e.g. one association per key object selection and any softcopy presentation states) Activity Send Storage Request Description and Sequencing of Activities For each instance selected from the user interface to be transferred, a single attempt will be made to transmit it to the selected remote AE. If the send fails, for whatever reason, no retry will be performed, and an attempt will be made to send the next instance Proposed Presentation Contexts Table PROPOSED PRESENTATION CONTEXTS FOR STORAGE-SCU AND SEND STORAGE REQUEST Presentation Context Table Abstract Syntax Transfer Syntax Role Extended Negotiation Name UID Name UID See Table See Table Explicit VR Little Endian Implicit VR Little Endian SCU None SCU None RLE Lossless SCU None JPEG Baseline (Process 1): JPEG Extended (Process 2 & 4) JPEG Lossless, Non-Hierarchical (Process 14) JPEG Lossless, Non-Hierarchical, First-Order Prediction (Process 14 [Selection Value 1]) SCU None SCU None SCU None SCU None STORAGE-SCU examines all the Abstract Syntax/Transfer Syntax pairs in the instances to be stored, and applies the following algorithm when determining the Presentation Contexts to propose: - For each Abstract Syntax/Transfer Syntax pair where the Transfer Syntax is uncompressed, a Presentation Context will be defined for the Abstract Syntax with both Explicit and Implicit Little Endian Transfer Syntaxes only. - For those Abstract Syntax/Transfer Syntax pairs where the Transfer Syntax is encapsulated (e.g. compressed), a Presentation Context is defined for the Abstract Syntax with only the encapsulated Transfer Syntax. - For those Abstract Syntax/Transfer Syntax pairs where the Transfer Syntax is encapsulated and STORAGE-SCU is able to convert to an uncompressed Transfer Syntax (e.g. Explicit or Implicit Little Endian), an additional Presentation Context is defined for each such Abstract Syntax, with only Explicit and Implicit Little Endian Transfer Syntaxes. The implications of this algorithm are: Page 19

20 - STORAGE-SCU will never compress an instance in order to store it. - Compressed instances will be stored as-is whenever possible, or failing that, in either Explicit or Implicit Little Endian format. When STORAGE-SCU is incapable of decompressing an instance, it simply will not be stored and STORAGE-SCU will continue sending the remaining instances Extended Negotiation No extended negotiation is performed SOP Specific Conformance SOP Specific Conformance to Storage SOP Classe s STORAGE-SCU provides standard conformance to the Storage Service Class Presentation Context Acceptance Criterion STORAGE-SCU does not accept associations Transfer Syntax Selection Policies For encapsulated Transfer Syntaxes, STORAGE-SCU prefers to send each instance using its current Transfer Syntax, and will find the first Presentation Context where the Transfer Syntax was accepted. In the case where the Transfer Syntax was not accepted by the remote STORAGE-SCP, STORAGE-SCU will check for the acceptance of Explicit VR Little Endian and Implicit VR Little Endian, in that order. If STORAGE-SCU cannot change the Transfer Syntax, the sub-operation will fail and it will not store the instance. In the case of uncompressed Transfer Syntaxes, STORAGE-SCU has no real preference. It will store the instances in either Explicit VR Little Endian or Implicit VR Little Endian, depending on what was accepted by the SCP Response Status STORAGE-SCU will behave as described in the Table below in response to the status returned in the C- STORE response command message. Table RESPONSE STATUS FOR STORAGE-SCU AND SEND STORAGE REQUEST Service Status Further Meaning Status Code s Behavior Failure N/A Any Message shown in Send Queue UI, continues storing remaining instances Warning N/A Any Message shown in Send Queue UI, continues storing remaining instances Activity Send Key Object Selections Description and Sequencing of Activities For each key object selection document, a single attempt will be made to transmit it and the softcopy presentation states of each image in the selection to the source AE in the case of a streaming server (i.e. ClearCanvas ImageServer), as well as all remote AEs defined as Default Servers in the configuration. If the send fails, for whatever reason, no retry will be performed, and an attempt will be made to send the next instance. Page 20

21 Proposed Presentation Contexts Table PROPOSED PRESENTATION CONTEXTS FOR STORAGE-SCU AND SEND KEY OBJECT SELECTIONS Presentation Context Table Abstract Syntax Transfer Syntax Role Extended Negotiation Name UID Name UID See Table See Table Explicit VR Little Endian Implicit VR Little Endian SCU None SCU None Key object selection documents and softcopy presentation states cannot be compressed. In all instances, a single Presentation Context will be defined for the Abstract Syntax with both Explicit and Implicit Little Endian Transfer Syntaxes only Extended Negotiation No extended negotiation is performed SOP Specific Conformance SOP Specific Conformance to Storage SOP Classe s STORAGE-SCU provides standard conformance to the Storage Service Class Presentation Context Acceptance Criterion STORAGE-SCU does not accept associations Transfer Syntax Selection Policies STORAGE-SCU always stores key object selection documents and softcopy presentation states in either Explicit VR Little Endian or Implicit VR Little Endian, depending on what was accepted by the SCP Response Status See Table Association Acceptance Policy STORAGE-SCU does not accept associations FIND-SCP SOP Classe s FIND-SCP provides Standard Conformance to the following SOP classes: Table SOP CLASSES SUPPORTED BY FIND-SCP SOP Class Name SOP Class UID Study Root Query/Retrieve Information Model FIND Page 21

22 Association Policies General FIND-SCP accepts but never initiates associations. Table MAXIMUM PDU SIZE RECEIVED AS A SCP FOR FIND-SCP Maximum PDU size received 114kB (approx.) Number of Associations Table NUMBER OF ASSOCIATIONS AS A SCP FOR FIND-SCP Maximum number of simultaneous associations Unlimited Asynchronous Nature FIND-SCP will only allow a single outstanding operation on an Association. Therefore, FIND-SCP will not perform asynchronous operations window negotiation Implementation Identifying Information Table DICOM IMPLEMENTATION CLASS AND VERSION FOR FIND-SCP Implementation Class UID Implementation Version Name Dicom Association Initiation Policy FIND-SCP does not initiate associations Association Acceptance Policy When FIND-SCP accepts an association, it will respond to query requests. The association will be rejected if: - The Called AE Title does not match the AE Title shared by all the SCPs of the application. - The Calling AE Title is not in the application s pre-configured list Activity Receive Query Request Description and Sequencing of Activities When a query is received, the local database is queried for the result set Accepted Pre sentation Contexts Table ACCEPTABLE PRESENTATION CONTEXTS FOR FIND-SCP AND RECEIVE QUERY REQUEST Presentation Context Table Abstract Syntax Transfer Syntax Role Extended Negotiation Name UID Name UID See Table See Table Explicit VR Little Endian SCP None Page 22

23 Implicit VR Little Endian SCP None Extended Negotiation No extended negotiation is performed. In particular, relational queries are not supported SOP Specific Conformance SOP Specific Conformance to C-FIND SOP Cla sse s FIND-SCP provides standard conformance to the supported C-FIND SOP Classes with one exception: all matching is case-insensitive, which is not in strict compliance with DICOM PS 3.4. This was a conscious decision, as case-sensitive matching is not intuitive and most users would be completely unaware of the fact that it even matters, causing many expected query matches to not be returned. Only a single information model, Study Root, is supported. Only those attributes that are requested are returned in a C-FIND response. Some optional requested attributes will be returned as per Table Table STUDY ROOT RESPONSE IDENTIFIER FOR FIND-SCP Name STUDY Level Tag Type s of Matching Study Instance UID (0020,000D) UNIQUE Patient s ID (0010,0020) S,*,U Patient s Name (0010,0010) S,*,U Patient's Birth Date (0010,0030) NONE Patient's Sex (0010,0040) S,*,U Study ID (0020,0010) S,*,U Study Description (0008,1030) S,*,U Modalities In Study (0008,0061) S,*,U Study Date (0008,0020) S,U,R Study Time (0008,0030) NONE Accession Number (0008,0050) S,*,U Referring Physician s Name (0008,0090) S,*,U Procedure Code Sequence (0008,1032) NONE >Code Value (0008,0100) S,*,U >Coding Scheme Designator (0008,0102) S,*,U Number Of Study Related Series (0020,1206) S,*,U Number Of Study Related Instances (0020,1208) S,*,U SERIES Level Series Instance UID (0020,000E) UNIQUE Modality (0008,0060) S,*,U Page 23

24 Series Description (0008,103E) S,*,U Series Number (0020,0011) S,*,U Number Of Series Related Instances (0020,1209) S,*,U IMAGE Level SOP Instance UID (0008,0018) UNIQUE Instance Number (0020,0013) S,*,U SOP Class UID (0008,0016) L,U Common to all query levels Specific Character Set (0008,0005) N/A Types of Matching: An "S" indicates the identifier attribute uses Single Value Matching, an R indicates Range Matching, a * indicates wildcard matching, a U indicates Universal Matching, and an L indicates that a UID list is sent. NONE indicates that no matching is supported, but that values for this Element are returned when requested (i.e. universal matching), and UNIQUE indicates that this is the Unique Key for that query level, in which case Universal Matching or Single Value Matching is used depending on the query level. Note that, in the case of wildcard matching, the question mark (?) operator is currently not supported Presentation Context Acceptance Criterion FIND-SCP will always accept any Presentation Context for the supported SOP Classes with the supported Transfer Syntaxes. More than one proposed Presentation Context will be accepted for the same Abstract Syntax if the Transfer Syntax is supported, whether or not it is the same as another Presentation Context Transfer Syntax Selection Policies FIND-SCP will always select the first Transfer Syntax proposed by the client that is supported by the SCP, per Presentation Context. FIND-SCP will accept duplicate Presentation Contexts; that is, if it is offered multiple Presentation Contexts, each of which offers acceptable Transfer Syntaxes, it will accept all Presentation Contexts, applying the same method for selecting a Transfer Syntax for each Response Status FIND-SCP will behave as described in Table when constructing the C-FIND response command message(s). Table RESPONSE STATUS FOR FIND-SCP AND RECEIVE QUERY REQUEST Service Status Failure Further Meaning Identifier does not match SOP Class Status Code s A900 Behavior Sent when the Query/Retrieve Level in the C-FIND request is not present or valid Unable to process Cxxx Sent if internal database query is Page 24

25 Pending Success Matches are continuing - Current Match is supplied and any Optional Keys were supported in the same manner as Required Keys Matching is complete unsuccessful FF00 Sent 0000 Sent FIND-SCU SOP Classe s FIND-SCU provides Standard Conformance to the following SOP classes: Table SOP CLASSES SUPPORTED BY FIND-SCU SOP Class Name SOP Class UID Study Root Query/Retrieve Information Model FIND Association Policies General FIND-SCU initiates but never accepts associations. Table MAXIMUM PDU SIZE RECEIVED AS A SCP FOR FIND-SCU Maximum PDU size received 114kB (approx.) Number of Associations Table NUMBER OF ASSOCIATIONS AS A SCP FOR FIND-SCU Maximum number of simultaneous associations Asynchronous Nature FIND-SCU will only allow a single outstanding operation on an Association. Therefore, FIND -SCU will not perform asynchronous operations window negotiation Implementation Identifying Information Table DICOM IMPLEMENTATION CLASS AND VERSION FOR FIND-SCU Implementation Class UID Implementation Version Name Dicom 0.1 Page 25

26 Association Initiation Policy FIND-SCU attempts to initiate a new association when the user performs the query action from the user interface. Furthermore, FIND-SCU attempts to initiate new associations for the purpose of locating prior studies when the user opens a study for viewing Activity Query Remote AE Description and Sequencing of Activities A single attempt will be made to query the remote AE. If the query fails for whatever reason, no retry will be performed Proposed Presentation Contexts Table PROPOSED PRESENTATION CONTEXTS FOR FIND-SCU AND SEND QUERY REQUEST Presentation Context Table Abstract Syntax Transfer Syntax Role Extended Negotiation Name UID Name UID See Table See Table Explicit VR Little Endian Extended Negotiation No extended negotiation is performed. In particular, relational queries are not supported SOP Specific Conformance Implicit VR Little Endian SOP Specific Conformance to C-FIND SOP Cla sse s SCU None SCU None FIND-SCU provides standard conformance to the supported C-FIND SOP Classes. Only a single information model, Study Root, is supported and is only used at the STUDY and SERIES levels. IMAGE level queries are never performed. No CANCEL requests are ever issued. Unexpected attributes returned in a C-FIND response (those not requested) are discarded. Requested return attributes not returned by the SCP are ignored. In general, non-matching responses returned by the SCP due to unsupported (hopefully optional) matching keys are not filtered locally by the FIND-SCU and thus will still be presented in the browser, with the exception of Modalities in Study, which is filtered by the SCU. Specific Character Set is not included in the C-FIND request at any level. If present in the response, Specific Character Set will be used to identify character sets other than the default character set for display of strings in the browser. Instance Availability is incorrectly included (but empty) in the C-FIND request at the STUDY level only; it is not included in SERIES level requests. For STUDY level queries initiated by the user, the value is shown in the results table if it was returned in the response. Retrieve AE Title is not included in the C-FIND request at any level. If present in the response, it is ignored. Page 26

27 Table STUDY ROOT REQUEST IDENTIFIER FOR FIND-SCU Name STUDY Level Tag Type s of Matching Study Instance UID (0020,000D) UNIQUE Patient s ID (0010,0020) S,*,U Patient s Name (0010,0010) S,*,U Patient's Birth Date (0010,0030) U Referring Physician s Name (0008,0090) S,*,U Study Description (0008,1030) S,*,U Modalities In Study (0008,0061) S,U Study Date (0008,0020) S,U,R Study Time (0008,0030) U Accession Number (0008,0050) S,*,U Number Of Study Related Instances (0020, 1208) U SERIES Level Study Instance UID (0020,000D) UNIQUE Series Instance UID (0020, 000E) UNIQUE Modality (0008, 0060) U Series Description (0008, 103E) U Series Number (0020, 0011) U Number of Series Related Instances (0020, 1209) U N/A IMAGE Level Common to all query levels Specific Character Set (0008,0005) N/A Instance Availability (0008,0056) N/A Retrieve AE Title (0008,0054) N/A Types of Matching: An "S" indicates the identifier attribute uses Single Value Matching, an R indicates Range Matching, a * indicates wildcard matching, a U indicates Universal Matching, an L indicates that a UID list is sent, and UNIQUE indicates that this is the Unique Key for that query level Presentation Context Acceptance Criterion FIND-SCU does not accept associations Transfer Syntax Selection Policies FIND-SCU prefers Explicit VR Little Endian Transfer Syntax, which is always first in the proposed Presentation Context. Page 27

28 Response Status FIND-SCU will behave as described in Table in response to the status returned in the C-FIND response command message(s). Table RESPONSE STATUS FOR FIND-SCU AND QUERY REMOTE AE REQUEST Service Status Further Meaning Status Code s Behavior Failure N/A Any Association closed, message shown to user Cancel Success Matching terminated due to Cancel request Matching is complete - No final Identifier is supplied FE Activity Query for Prior Studie s Description and Sequencing of Activities Association closed, message shown to user 0000 Association closed Attempts are made to query each remote AE defined as a Default Server in the configuration for each patient ID considered a match to that of the current patient. If the query fails for whatever reason, no retry will be performed, however the user will be notified. Studies discovered this way which were not specifically selected by the user are considered prior studies and are lis ted by the application to inform the user of their presence. In some configurations (namely, when the source AE of the prior study is a ClearCanvas ImageServer), the application also supports viewing the prior study as if it had been selected by the user initially via the Streaming mechanism (see Section ) Proposed Presentation Contexts See Table Extended Negotiation No extended negotiation is performed. In particular, relational queries are not supported SOP Specific Conformance SOP Specific Conformance to C-FIND SOP Cla sse s FIND-SCU provides standard conformance to the supported C-FIND SOP Classes. Only a single information model, Study Root, is supported and is only used at the highest level (STUDY). No CANCEL requests are ever issued. A configurable algorithm computes a list of Patient IDs that, when used in a wildcard query, will identify all studies related to the current patient. Available operations include trimming prefixes/suffixes and removing extra whitespace in order to reconcile Patient IDs with different formatting. Unexpected attributes returned in a C-FIND response (those not requested) are discarded. Requested return attributes not returned by the SCP are ignored. Page 28

29 Specific Character Set is not included in the C-FIND request. If present in the response, Specific Character Set will be used to identify character sets other than the default character set for display of strings in the viewer. For each prior study found, Retrieve AE Title is used to determine if the study can be streamed, and if so, the study will be loaded into the viewer in the same way as one selected by the user. Table STUDY ROOT REQUEST IDENTIFIER FOR FIND-SCU FOR QUERY FOR PRIOR STUDIES Name STUDY Level Tag Type s of Matching Study Instance UID (0020,000D) UNIQUE Patient s ID (0010,0020) * Patient s Name (0010,0010) U Patient's Birth Date (0010,0030) U Patient s Birth Time (0010,0032) U Patient s Sex (0010,0040) U Study Description (0008,1030) U Modalities In Study (0008,0061) U Study ID (0020,0010) U Study Description (0008,1030) U Study Date (0008,0020) U Study Time (0008,0030) U Accession Number (0008,0050) U Referring Physician s Name (0008,0090) U Number of Study Related Instances (0020,1208) U Number of Study Related Series (0020,1206) U N/A N/A SERIES Level IMAGE Level Common to all query levels Specific Character Set (0008,0005) N/A Retrieve AE Title (0008,0054) N/A Types of Matching: An "S" indicates the identifier attribute uses Single Value Matching, an R indicates Range Matching, a * indicates wildcard matching, a U indicates Universal Matching, an L indicates that a UID list is sent, and UNIQUE indicates that this is the Unique Key for that query level Presentation Context Acceptance Criterion FIND-SCU does not accept associations. Page 29