Philips Medical Systems. Xcelera R1.1L1. Document Number XPR July PDF Free Download

DICOM Conformance Statement Issued by: Philips Medical Systems Nederland B.V. Medical IT, Interoperability Building QV-282 P.O. Box 10.000 5680 DA Best The Netherlands Email: dicom@philips.com Internet: http://www.medical.philips.com/ Document Number: XPR 080-030073

DICOM Conformance Statement Page 3 of 63 Table of Contents 1. INTRODUCTION...7 1.1. Scope and Field of Application...7 1.2. Intended Audience...7 1.3. Contents and Structure...7 1.4. Used Definitions, Terms and Abbreviations...7 1.5. References...7 1.6. Important Note to the Reader...8 1.7. General Acronyms and Abbreviations...9 2. IMPLEMENTATION MODEL...10 2.1. Application Data Flow Diagram...10 2.2. Functional Definition of Application Entities...12 2.2.1. Xcelera Imaging Import AE...12 2.2.2. Xcelera Storage Commitment AE...12 2.2.3. Xcelera Auto Export AE...12 2.2.4. Xcelera Send Images AE...12 2.2.5. Xcelera Query/Retrieve as SCU AE...12 2.2.6. Xcelera Query/Retrieve as SCP AE...12 2.2.7. Xcelera Print AE...12 2.2.8. Xcelera Media AE...13 2.3. Sequencing of Real-World Activities...13 3. AE SPECIFICATIONS...14 3.1. Xcelera Imaging Import AE...14 3.1.1. Association Establishment Policies...14 3.1.1.1. General...14 3.1.1.2. Number of Associations...14 3.1.1.3. Asynchronous Nature...15 3.1.1.4. Implementation Identifying Information...15 3.1.2. Association Initiation Policy...15 3.1.3. Association Acceptance Policy...15 3.1.3.1. Verify Application Level Communication...15 3.1.3.2. Import Images...16 3.2. Xcelera Storage Commitment AE...21 3.2.1. Association Establishment Policies...21 3.2.1.1. General...21 3.2.1.2. Number of Associations...21 3.2.1.3. Asynchronous Nature...21 3.2.1.4. Implementation Identifying Information...21 3.2.2. Association Initiation Policy...21 3.2.2.1. Invoke Storage Commitment Notification...21 3.2.3. Association Acceptance Policy...23 3.2.3.1. Verify Application Level Communication...23 3.2.3.2. Storage Commitment Acceptance...23 3.3. Xcelera Auto Export AE...25 3.3.1. Association Establishment Policies...25 3.3.1.1. General...25 3.3.1.2. Number of Associations...25 3.3.1.3. Asynchronous Nature...25 3.3.1.4. Implementation Identifying Information...25 3.3.2. Association Initiation Policy...25 3.3.2.1. Transfer DICOM Images...25 3.3.2.2. Transfer Xcelera Photo Files...28 3.3.2.3. Transfer DSR-TIFF Ultrasound Images...29 3.3.3. Association Acceptance Policy...30 3.4. Xcelera Send Images AE...31

DICOM Conformance Statement Page 4 of 63 3.4.1. Association Establishment Policies...31 3.4.1.1. General...31 3.4.1.2. Number of Associations...31 3.4.1.3. Asynchronous Nature...31 3.4.1.4. Implementation Identifying Information...31 3.4.2. Association Initiation Policy...31 3.4.2.1. Export Images...31 3.4.3. Association Acceptance Policy...34 3.5. Xcelera Query/Retrieve as SCU AE...35 3.5.1. Association Establishment Policies...35 3.5.1.1. General...35 3.5.1.2. Number of Associations...35 3.5.1.3. Asynchronous Nature...35 3.5.1.4. Implementation Identifying Information...35 3.5.2. Association Initiation Policy...35 3.5.2.1. Query a Remote System...35 3.5.2.2. Retrieve from a Remote System...37 3.5.3. Association Acceptance Policy...38 3.6. Xcelera Query/Retrieve as SCP AE...39 3.6.1. Association Establishment Policies...39 3.6.1.1. General...39 3.6.1.2. Number of Associations...40 3.6.1.3. Asynchronous Nature...40 3.6.1.4. Implementation Identifying Information...40 3.6.2. Association Initiation Policy...40 3.6.2.1. Store Retrieved Images...40 3.6.3. Association Acceptance Policy...43 3.6.3.1. Verify Application Level Communication...43 3.6.3.2. Query the Xcelera Database...43 3.6.3.3. Retrieve Images from the Xcelera Database...45 3.7. Xcelera Print AE...47 3.7.1. Association Establishment Policies...47 3.7.1.1. General...47 3.7.1.2. Number of Associations...47 3.7.1.3. Asynchronous Nature...47 3.7.1.4. Implementation Identifying Information...47 3.7.2. Association Initiation Policy...48 3.7.2.1. Print Images...48 3.7.3. Association Acceptance Policy...52 3.8. Xcelera Media AE...53 3.8.1. File Meta Information for the Xcelera Media AE...53 3.8.2. Real-World Activities...53 3.8.2.1. Real-World Activity DICOM Recording...55 3.8.2.2. Real-World Activity DICOM Reading...58 4. COMMUNICATION PROFILES...59 4.1. Supported Communication Stacks...59 4.2. TCP/IP Stack...59 4.3. API...59 4.3.1. Physical Media Support...59 5. AUGMENTED AND PRIVATE APPLICATION PROFILES...60 5.1. Augmented Application Profiles...60 5.2. Private Application Profiles...60 6. EXTENSIONS/SPECIALIZATIONS/PRIVATIZATIONS...61 6.1. Standard Extended SOPs...61 6.2. Private Transfer Syntaxes...61 7. CONFIGURATION...62 7.1. AE Title/Presentation Address Mapping...62

DICOM Conformance Statement Page 5 of 63 8. SUPPORT OF EXTENDED CHARACTER SETS...63

DICOM Conformance Statement Page 6 of 63

DICOM Conformance Statement Page 7 of 63 1. INTRODUCTION This chapter provides general information about the purpose, scope and contents of this Conformance Statement. 1.1. Scope and Field of Application The scope of this DICOM Conformance Statement is to facilitate data exchange with equipment of Philips Medical Systems. This document specifies the compliance to the DICOM standard (formally called the NEMA PS 3.X standards). It contains a short description of the applications involved and provides technical information about the data exchange capabilities of the equipment. The main elements describing these capabilities are: the supported DICOM Service Object Pair (SOP) Classes, Roles, Information Object Definitions (IOD) and Transfer Syntaxes. The field of application is the integration of the Philips Medical Systems equipment into an environment of medical devices. This Conformance Statement should be read in conjunction with the DICOM standard and its addenda [DICOM]. 1.2. Intended Audience This Conformance Statement is intended for: (potential) customers system integrators of medical equipment marketing staff interested in system functionality software designers implementing DICOM interfaces It is assumed that the reader is familiar with the DICOM standard. 1.3. Contents and Structure The DICOM Conformance Statement is contained in chapter 2 through 7 and follows the contents and structuring requirements of DICOM PS 3.2. 1.4. Used Definitions, Terms and Abbreviations DICOM definitions, terms and abbreviations are used throughout this Conformance Statement. For a description of these, see NEMA PS 3.3 and PS 3.4. The word Philips in this document refers to Philips Medical Systems. 1.5. References [DICOM] The Digital Imaging and Communications in Medicine (DICOM) standard: (NEMA PS 3.X): National Electrical Manufacturers Association (NEMA) Publication Sales 1300 N. 17 th Street, Suite 1847 Rosslyn, Va. 22209, United States of America

DICOM Conformance Statement Page 8 of 63 1.6. Important Note to the Reader This Conformance Statement by itself does not guarantee successful interoperability of Philips equipment with non-philips equipment. The user (or user s agent) should be aware of the following issues: Interoperability Interoperability refers to the ability of application functions, distributed over two or more systems, to work successfully together. The integration of medical devices into an IT environment may require application functions that are not specified within the scope of DICOM. Consequently, using only the information provided by this Conformance Statement does not guarantee interoperability of Philips equipment with non-philips equipment. It is the user s responsibility to analyze thoroughly the application requirements and to specify a solution that integrates Philips equipment with non-philips equipment. Validation Philips equipment has been carefully tested to assure that the actual implementation of the DICOM interface corresponds with this Conformance Statement. Where Philips equipment is linked to non-philips equipment, the first step is to compare the relevant Conformance Statements. If the Conformance Statements indicate that successful information exchange should be possible, additional validation tests will be necessary to ensure the functionality, performance, accuracy and stability of image and image related data. It is the responsibility of the user (or user s agent) to specify the appropriate test suite and to carry out the additional validation tests. New versions of the DICOM Standard The DICOM Standard will evolve in future to meet the user s growing requirements and to incorporate new features and technologies. Philips is actively involved in this evolution and plans to adapt its equipment to future versions of the DICOM Standard. In order to do so, Philips reserves the right to make changes to its products or to discontinue its delivery. The user should ensure that any non-philips provider linking to Philips equipment also adapts to future versions of the DICOM Standard. If not, the incorporation of DICOM enhancements into Philips equipment may lead to loss of connectivity (in case of networking) and incompatibility (in case of media).

DICOM Conformance Statement Page 9 of 63 1.7. General Acronyms and Abbreviations The following acronyms and abbreviations are used in the document. ACC American College of Cardiology ACR American College of Radiology AE Application Entity ANSI American National Standard Institute BOT Basic Offset Table CD Compact Disc CD-R CD-Recordable CD-M CD-Medical DCR Dynamic Cardio Review DICOM Digital Imaging and Communications in Medicine DIMSE DICOM Message Service Element DIMSE-C DIMSE-Composite DIMSE-N DIMSE-Normalized DICOM Explicit VR Big Endian DICOM Explicit VR Little Endian FSC File-set Creator FSR File-set Reader FSU File-set Updater GUI Graphic User Interface HIS Hospital Information System HL7 Health Level Seven ILE DICOM Implicit VR Little Endian IOD Information Object Definition ISIS Information System Imaging System MOD Magneto-Optical Disk MPPS Modality Performed Procedure Step MR Magnetic Resonance NEMA National Electrical Manufacturers Association NM Nuclear Medicine PDU Protocol Data Unit RIS Radiology Information System RWA Real-World Activity SC Secondary Capture SCM Study Component Management SCP Service Class Provider SCU Service Class User SOP Service Object Pair TCP/IP Transmission Control Protocol/Internet Protocol UID Unique Identifier US Ultrasound VR Value Representation VT Value Type WLM Worklist Management XA X-Ray Angiographic

DICOM Conformance Statement Page 10 of 63 2. IMPLEMENTATION MODEL This document is the DICOM Conformance Statement for the Philips Medical Systems Nederland B.V. Xcelera R1.1L1. All of the DICOM features presented in this document are optional and may not be available on all Xcelera related products. The Xcelera is primarily intended for archiving and viewing of MR, SC, US and XA images, Xcelera is also capable to handle Query/Retrieve requests. The Xcelera consists of a server that handles the Storage, Storage Commitment and Query/Retrieve of images and several clients that can read and write media and can view images. Figure 2-1 gives an overview of the Xcelera system in a DICOM network. Xcelera Store images Imaging Import AE Auto export images Auto Export AE Modality or Workstation Commit image storage Storage Commitment AE Query/Retrieve requests Query/Retrieve as SCU AE Xcelera Server Send images Send Images AE Retrieve (Store) images Query/Retrieve as SCP AE Modality or PACS or Workstation DICOM AE Verification All Network AE's Query/Retrieve requests Query/Retrieve as SCP AE Proprietary Protocol Print images Print AE DICOM Printer Xcelera Viewer Read / Write Images Media AE CD-R Figure 2-1: Xcelera in a DICOM network 2.1. Application Data Flow Diagram The Xcelera related implementation model is shown in Figure 2-2: Implementation Model of Xcelera R1.1L1.

DICOM Conformance Statement Page 11 of 63 Xcelera Server =========== Imaging Import AE Store Images Request Verification Send Images AE Store Images Auto Export AE Store Images Storage Commitment AE Query/Retrieve as SCU AE Request Storage Commit ment Request Verification Request Q/R of Images Query/Retrieve as SCP AE Request Verification Request Q/R of Images Store Images Xcelera Viewer =========== Media AE CD-R MOD Flop Print AE Print Images Local Remote DICOM standard Interface Figure 2-2: Implementation Model of Xcelera R1.1L1

DICOM Conformance Statement Page 12 of 63 As documented in [DICOM] PS3.4, the arrows in Figure 2-2 have the following meanings: Arrow pointing to the right indicates the local application entity initiates an association; Arrow pointing to the left indicates the local application entity accepts an association. 2.2. Functional Definition of Application Entities 2.2.1. Xcelera Imaging Import AE The Xcelera (SCP) accepts an association with a remote DICOM AE (SCU) to receive a storage request and the applicable image data. (DICOM Storage Service Class) 2.2.2. Xcelera Storage Commitment AE The Xcelera (SCP) accepts an association with a remote DICOM AE (SCU) to receive a storage commitment request. After handling the requested storage commitment, the Xcelera initiates an association with the SCU to report the status of the storage commitment. (DICOM Storage Commitment Service Class) 2.2.3. Xcelera Auto Export AE On event, the Xcelera (SCU) automatically initiates an association with a remote DICOM AE (SCP) to send a storage request and the applicable image data. (DICOM Storage Service Class) 2.2.4. Xcelera Send Images AE When the Send function in the Xcelera Server is addressed, the Xcelera (SCU) initiates an association with a remote DICOM AE (SCP) to send a storage request and the applicable image data. (DICOM Storage Service Class) 2.2.5. Xcelera Query/Retrieve as SCU AE The Xcelera (SCU) initiates an association with a remote DICOM AE (SCP) to send a Query/Retrieve request. (DICOM Query/Retrieve Service Class) 2.2.6. Xcelera Query/Retrieve as SCP AE The Xcelera Query/Retrieve as SCP AE exists of two functions. The Xcelera (SCP) accepts an association with a remote DICOM AE (SCU) to receive a Query/Retrieve request. (DICOM Query/Retrieve Service Class) When a retrieve of image data is requested, the Xcelera (SCU) initiates an association with a remote DICOM AE (SCP) to send a storage request and the applicable image data. (DICOM Storage Service Class) 2.2.7. Xcelera Print AE The Print AE in an Xcelera client (viewer) supports the functionality for basic grayscale print management, basic annotation box, and print job. On demand, the Xcelera (SCU) initiates an association with a printer (SCP) and sends a create request to the printer. (DICOM Print Management Service Class)

DICOM Conformance Statement Page 13 of 63 2.2.8. Xcelera Media AE The Media AE in an Xcelera client (viewer) supports the following functions for CD-R (typical cardiac CATHeterization), MOD (typical ECHOcardiography), and Floppy disks. Read the DICOMDIR File from the medium (representing the directory of the DICOM File(s) as recorded on the medium). This information may be displayed as an ordered list of icon images and, if present, with pertinent identifying information (patient name, etc.). Read the selected image from the medium and display it on the monitor of the View Station. This information is displayed as an ordered list of frames of the selected image or as a dynamic review of the selected image. And for CD-R and Floppy disks: Initialize the medium. Write a DICOM File-set onto the medium. Create a DICOMDIR File. Extend the DICOM File-set and update the DICOMDIR File accordingly. (DICOM Media Storage Service Class) 2.3. Sequencing of Real-World Activities All Real-World Activities as specified in the Functional Definition of Application Entities may occur independently from each other.

DICOM Conformance Statement Page 14 of 63 3. AE SPECIFICATIONS The Network capabilities of the Xcelera consist of six DICOM Application Entities: Imaging Import AE Storage Commitment AE Auto Export AE Send Image AE Query / Retrieve as SCU AE Query / Retrieve as SCP AE Next to those the Xcelera also consists of a Media AE and a Printer AE. These AE s are specified in the following sections (3.1 to 3.8). 3.1. Xcelera Imaging Import AE The Xcelera Imaging Import AE provides standard SCP conformance for the DICOM V3.0 SOP classes specified in Table 3-1. Table 3-1: Supported SOP Classes of the Xcelera Imaging Import AE SOP class Name UID Verification 1.2.840.10008.1.1 Ultrasound Multi-frame Image Storage 1.2.840.10008.5.1.4.1.1.3.1 MR Image Storage 1.2.840.10008.5.1.4.1.1.4 Ultrasound Image Storage 1.2.840.10008.5.1.4.1.1.6.1 Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7 X-Ray Angiographic Image Storage 1.2.840.10008.5.1.4.1.1.12.1 Nuclear Medicine Image Storage 1.2.840.10008.5.1.4.1.1.20 3.1.1. Association Establishment Policies 3.1.1.1. General The Xcelera Imaging Import AE always proposes the following DICOM Application Context Name (ACN): 1.2.840.10008.3.1.1.1 The maximum length PDU negotiation is included in all association establishment requests. The default maximum length PDU for an association initiated by the Xcelera Imaging Import AE is 28 kb. 3.1.1.2. Number of Associations The number of associations for the storage SCP service that may be active simultaneously is 15. For the verification service only one association can be handled at a time.

DICOM Conformance Statement Page 15 of 63 3.1.1.3. Asynchronous Nature DICOM asynchronous mode is not supported, meaning that only one transaction may be outstanding over each association at any given point in time. 3.1.1.4. Implementation Identifying Information Implementation Class UID = 1.3.46.670589.16.14.1.1.1 Implementation Version Name = Xcelera R1.1.L1 3.1.2. Association Initiation Policy The Xcelera Imaging Import AE never initiates any associations. 3.1.3. Association Acceptance Policy 3.1.3.1. Verify Application Level Communication 3.1.3.1.1. Associated Real-World Activity The Xcelera Imaging Import AE accepts associations from systems that wish to verify application level communication using the C-ECHO command. 3.1.3.1.2. Presentation Context Table The Xcelera Imaging Import AE will accept the presentation context as given in the next table. Table 3-2: Accepted Presentation Contexts of the Xcelera Imaging Import AE Presentation Context Table Abstract Syntax Transfer Syntax Name UID Name List UID List Role Extended Negotiation Verification 1.2.840.10008.1.1 ILE SCP 3.1.3.1.3. SOP Specific Conformance for C-ECHO SCP The Xcelera Imaging Import AE provides standard conformance. 3.1.3.1.4. Presentation Context Acceptance Criterion The Xcelera Imaging Import AE accepts all contexts in the intersection of the proposed and acceptable Presentation Context. This means that the Xcelera Imaging Import AE will accept multiple proposed Presentation Contexts with the same SOP Class but different Transfer Syntaxes, so there will be no checks for duplicate Presentation Contexts. 3.1.3.1.5. Transfer Syntax Selection Policies Any of the presentation contexts shown in Table 3-2 shall be accepted.

DICOM Conformance Statement Page 16 of 63 3.1.3.2. Import Images 3.1.3.2.1. Associated Real-World Activity A remote system sets up an association with the Xcelera. The Xcelera verifies that the remote system is configured as an allowed SCU, and that the maximum number of associations is not already reached. If suitable, the Xcelera will accept the association with a preferred presentation context. Then the remote system may transfer its image data to the Xcelera. When the complete image has been received, the Xcelera shall send a C-STORE response to notify the remote system that the transfer is completed successfully and the remote system may release the association. The image will be accepted only if all the relevant mandatory attributes are available (defined in the DICOM standard as type 1 - present with a value). 3.1.3.2.2. Accepted Presentation Contexts The following table illustrates the accepted presentation contexts for image storage requests.

DICOM Conformance Statement Page 17 of 63 Table 3-3: Accepted Presentation Contexts of the Xcelera Imaging Import AE Presentation Context Table Abstract Syntax Transfer Syntax Name UID Name List UID List Role Extended Negotiation Ultrasound Multi-frame Image Storage 1.2.840.10008.5.1.4.1.1.3.1 ILE JPEG Lossy Baseline JPEG Lossless First-Order Prediction (Process 14) (Selection Value 1) RLE.4.50.4.70.5 SCP MR Image Storage 1.2.840.10008.5.1.4.1.1.4 ILE SCP Ultrasound Image Storage 1.2.840.10008.5.1.4.1.1.6.1 ILE JPEG Lossy Baseline JPEG Lossless First-Order Prediction (Process 14) (Selection Value 1) RLE.4.50.4.70.5 SCP Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7 ILE JPEG Lossy Baseline JPEG Lossless First-Order Prediction (Process 14) (Selection Value 1).4.50.4.70 SCP X-Ray Angiographic Image Storage 1.2.840.10008.5.1.4.1.1.12.1 ILE JPEG Lossy Baseline JPEG Lossless First-Order Prediction (Process 14) (Selection Value 1)*.4.50.4.70 SCP Nuclear Medicine Image Storage 1.2.840.10008.5.1.4.1.1.20 ILE JPEG Lossy Baseline JPEG Lossless First-Order Prediction (Process 14) (Selection Value 1) RLE.4.50.4.70.5 SCP * Note: The JPEG Lossless (FOP - process 14) transfer syntax is preferred. 3.1.3.2.3. SOP Specific Conformance for C-STORE SCP The Xcelera conforms to the SOP s of the Storage Service Class at level 2 (full). No data elements are discarded or coerced by the Xcelera. The following table lists the actions that are performed when an exception occurs; the C-STORE Status Responses that are returned by the Xcelera Imaging Import AE are also mentioned.

DICOM Conformance Statement Page 18 of 63 Table 3-4: Exception handling Error Type Error Action Codes send in C-STORE STATUS Response Refused Remote is not licensed Log; Abort association. - Error Abort by remote system Log. - Time-out reached Log; Abort association. - Internal error Xcelera Send notification; Log; Abort association. 0110 Invalid dataset Send notification; Log. A900 Success - - 0000 For ultrasound images only the Image Information Entity level is supported. When receiving an object without image data, Xcelera rejects the object and returns an error message Invalid dataset. For ultrasound images the following section gives an overview of the image formats that are supported. Table 3-5: US HIGH BIT Supported Photometric Interpretation High Bit Value Storing Viewing MONOCHROME2 7 Yes Yes RGB 7 Yes Yes YBR_FULL 7 Yes Yes YBR_FULL_422 7 Yes Yes YBR_PARTIAL_422 7 Yes Yes PALETTE COLOR 7 (8 bit palette) Yes Yes PALETTE COLOR 15 (16 bit palette) Yes Yes

DICOM Conformance Statement Page 19 of 63 Table 3-6: US PLANAR CONFIGURATION Supported Photometric Interpretation Planar Configuration Value Storing Viewing RGB 0000H (color-by-pixel) Yes Yes RGB 0001H (color-by-plane) Yes Yes YBR_FULL 0001H (color-by-plane) Yes Yes YBR_FULL_422 0000H (color-by-pixel) Yes Yes YBR_PARTIAL_422 0000H (color-by-pixel) Yes Yes Table 3-7: US BITS ALLOCATED Supported Photometric Interpretation Bits Allocated Value Storing Viewing MONOCHROME2 0008H Yes Yes RGB 0008H Yes Yes YBR_FULL 0008H Yes Yes YBR_FULL_422 0008H Yes Yes YBR_PARTIAL_422 0008H Yes Yes PALETTE COLOR 0008H (8 bit palette) Yes Yes PALETTE COLOR 0010H (16 bit palette) Yes Yes Table 3-8: US SAMPLES PER PIXEL Supported Photometric Interpretation Samples Per Pixel Value Storing Viewing MONOCHROME2 1 Yes Yes RGB 3 Yes Yes YBR_FULL 3 Yes Yes YBR_FULL_422 3 Yes Yes YBR_PARTIAL_422 3 Yes Yes PALETTE COLOR 1 Yes Yes For the SC Image Storage, MR Image Storage and XA Image Storage all types of images can be stored and viewed. 3.1.3.2.4. Presentation Context Acceptance Criterion The Xcelera Imaging Import AE accepts all contexts in the intersection of the proposed and acceptable Presentation Context. This means that the Xcelera Imaging

DICOM Conformance Statement Page 20 of 63 Import AE will accept multiple proposed Presentation Contexts with the same SOP Class but different Transfer Syntaxes, so there will be no checks for duplicate Presentation Contexts. The images received by the Xcelera system are merged on Study UID and Series UID.

DICOM Conformance Statement Page 21 of 63 3.2. Xcelera Storage Commitment AE The Xcelera Storage Commitment AE provides standard SCP conformance for the DICOM V3.0 SOP classes specified in Table 3-9. Table 3-9: Supported SOP Classes of the Xcelera Storage Commitment AE SOP class Name UID Verification 1.2.840.10008.1.1 Storage Commitment Push Model 0.1 3.2.1. Association Establishment Policies 3.2.1.1. General The Xcelera Storage Commitment AE always proposes the following DICOM Application Context Name (ACN): 1.2.840.10008.3.1.1.1 The maximum length PDU negotiation is included in all association establishment requests. The default maximum length PDU for an association initiated by the Xcelera Storage Commitment AE is 28 kb. 3.2.1.2. Number of Associations The number of associations for the storage commitment SCP service that may be active simultaneously is 15. For the verification service only one association can be handled at a time. 3.2.1.3. Asynchronous Nature DICOM asynchronous mode is not supported, meaning that only one transaction may be outstanding over each association at any given point in time. 3.2.1.4. Implementation Identifying Information Implementation Class UID = 1.3.46.670589.16.14.1.1.1 Implementation Version Name = Xcelera R1.1.L1 3.2.2. Association Initiation Policy 3.2.2.1. Invoke Storage Commitment Notification 3.2.2.1.1. Associated Real-World Activity The Xcelera Storage Commitment AE will invoke a notification to inform the SCU whether or not it has executed the storage commitment request. The Xcelera can be configured to delay the storage commitment. In order to send a Success notification as soon as possible, the Xcelera Storage Commitment AE will check for completion of the request every hour again. If no archive is available or else if the request is not completed within the configured delay time plus 8 hours, the Xcelera Storage Commitment AE will report a Failure instantaneously.

DICOM Conformance Statement Page 22 of 63 3.2.2.1.2. Proposed Presentation Contexts The following table illustrates the proposed presentation contexts for the Storage Commitment service. Table 3-10: Proposed Presentation Contexts of the Xcelera Storage Commitment AE Presentation Context Table Abstract Syntax Transfer Syntax Name UID Name List UID List Role Extended Negotiation Storage Commitment Push Model 1.2.840.10008.1.20.1 ILE SCP 3.2.2.1.3. SOP Specific Conformance for N-EVENT-REPORT SCP The Xcelera Storage Commitment AE provides standard conformance to the Storage Commitment Push Model SOP Class. The following N-EVENT-REPORT attributes are sent. Table 3-11: N-EVENT-REPORT Attributes Event Type Name Storage Commitment Request Successful Event Type ID 1 Attribute Tag Note Transaction UID (0008,1195) - Referenced SOP Sequence (0008,1199) - >Referenced SOP Class UID >Referenced SOP Instance UID (0008,1150) - (0008,1155) - Storage Commitment Request Complete - Failures Exist 2 Transaction UID (0008,1195) - Failed SOP Sequence (0008,1198) - >Referenced SOP Class UID (0008,1150) - >Referenced SOP Instance UID (0008,1155) - >Failure Reason (0008,1197) -

DICOM Conformance Statement Page 23 of 63 3.2.3. Association Acceptance Policy 3.2.3.1. Verify Application Level Communication 3.2.3.1.1. Associated Real-World Activity The Xcelera Storage Commitment AE accepts associations from systems that wish to verify application level communication using the C-ECHO command. 3.2.3.1.2. Presentation Context Table The Xcelera Storage Commitment AE will accept the presentation context as given in the next table. Table 3-12: Accepted Presentation Contexts of the Xcelera Storage Commitment AE Presentation Context Table Abstract Syntax Transfer Syntax Name UID Name List UID List Role Extended Negotiation Verification 1.2.840.10008.1.1 ILE SCP 3.2.3.1.3. SOP Specific Conformance for C-ECHO SCP The Xcelera Storage Commitment AE provides standard conformance. 3.2.3.1.4. Presentation Context Acceptance Criterion The Xcelera Storage Commitment AE accepts all contexts in the intersection of the proposed and acceptable Presentation Context. This means that the Xcelera Storage Commitment AE will accept multiple proposed Presentation Contexts with the same SOP Class but different Transfer Syntaxes, so there will be no checks for duplicate Presentation Contexts. 3.2.3.1.5. Transfer Syntax Selection Policies Any of the presentation contexts shown in Table 3-12 are acceptable. 3.2.3.2. Storage Commitment Acceptance 3.2.3.2.1. Associated Real-World Activity In case that no archive is configured or connected, the server shall always notify the requestor that the storage commitment failed. In case the number of associations is exceeded the server shall respond to the requestor with a DICOM error. In other cases the Storage Commitment service will accept the Storage commitment request. 3.2.3.2.2. Accepted presentation Contexts Table 3-10: Proposed Presentation Contexts of the Xcelera Storage Commitment AE illustrates the accepted presentation contexts for the image storage request. 3.2.3.2.3. SOP Specific Conformance for N-ACTION SCP The Xcelera Storage Commitment AE provides standard conformance to the Storage Commitment Push Model SOP class. The following table lists the actions that are

DICOM Conformance Statement Page 24 of 63 performed when an exception occurs. The status responses that are returned by the Xcelera Storage Commitment AE are also mentioned. Table 3-13: Exception handling Error Type Error Action Codes send in N-ACTION STATUS Response Error Processing Failure Send notification; Log. 0110 Success - - 0000 In case that part of the images in a storage commitment request cannot be committed, the Xcelera Storage Commitment AE reports a failure of the complete storage commitment request. 3.2.3.2.4. Presentation Context Acceptance Criterion The Xcelera Storage Commitment AE accepts all contexts in the intersection of the proposed and acceptable Presentation Context. This means that the Xcelera Storage Commitment AE will accept multiple proposed Presentation Contexts with the same SOP Class but different Transfer Syntaxes, so there will be no checks for duplicate Presentation Contexts.

DICOM Conformance Statement Page 25 of 63 3.3. Xcelera Auto Export AE The Xcelera Auto Export AE provides standard SCU conformance for the DICOM V3.0 SOP classes specified in Table 3-14. Table 3-14: Supported SOP Classes of the Xcelera Auto Export AE SOP class Name UID Ultrasound Multi-frame Image Storage 1.2.840.10008.5.1.4.1.1.3.1 MR Image Storage 1.2.840.10008.5.1.4.1.1.4 Ultrasound Image Storage 1.2.840.10008.5.1.4.1.1.6.1 Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7 X-Ray Angiographic Image Storage 1.2.840.10008.5.1.4.1.1.12.1 Nuclear Medicine Image Storage 1.2.840.10008.5.1.4.1.1.20 3.3.1. Association Establishment Policies 3.3.1.1. General The Xcelera Auto Export AE always proposes the following DICOM Application Context Name (ACN): 1.2.840.10008.3.1.1.1 The maximum length PDU negotiation is included in all association establishment requests. The default maximum length PDU for an association initiated by the Xcelera Auto Export AE is 28 kb. 3.3.1.2. Number of Associations For the storage SCU service only one association can be active at a time. 3.3.1.3. Asynchronous Nature DICOM asynchronous mode is not supported, meaning that only one transaction may be outstanding over an association at any given point in time. 3.3.1.4. Implementation Identifying Information Implementation Class UID = 1.3.46.670589.16.14.1.1.1 Implementation Version Name = Xcelera R1.1.L1 3.3.2. Association Initiation Policy 3.3.2.1. Transfer DICOM Images 3.3.2.1.1. Associated Real-World Activity The Xcelera Auto Export AE will only export the images automatically when configured to do so. In the system configuration up to 2 destinations can be declared/configured. On association as SCP, the received DICOM images will be automatically sent to the configured destinations sequentially.

DICOM Conformance Statement Page 26 of 63 3.3.2.1.2. Proposed presentation Contexts The following table illustrates the proposed presentation contexts for the Image Storage request. Table 3-15: Proposed Presentation Contexts of the Xcelera Auto Export AE Presentation Context Table Abstract Syntax Transfer Syntax Name UID Name List UID List Role Extended Negotiation Ultrasound Multi-frame Image Storage 1.2.840.10008.5.1.4.1.1.3.1 ILE RLE JPEG Lossy Baseline JPEG Lossless First-Order Prediction (Process 14) (Selection Value 1).5.4.50.4.70 SCU MR Image Storage 1.2.840.10008.5.1.4.1.1.4 ILE SCU Ultrasound Image Storage 1.2.840.10008.5.1.4.1.1.6.1 ILE RLE JPEG Lossy Baseline JPEG Lossless First-Order Prediction (Process 14) (Selection Value 1).5.4.50.4.70 SCU Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7 ILE JPEG Lossy Baseline JPEG Lossless First-Order Prediction (Process 14) (Selection Value 1).4.50.4.70 SCU X-Ray Angiographic Image Storage 1.2.840.10008.5.1.4.1.1.12.1 ILE JPEG Lossy Baseline JPEG Lossless First-Order Prediction (Process 14) (Selection Value 1)*.4.50.4.70 SCU Nuclear Medicine Image Storage 1.2.840.10008.5.1.4.1.1.20 ILE RLE JPEG Lossy Baseline JPEG Lossless First-Order Prediction (Process 14) (Selection Value 1).5.4.50.4.70 SCU * Note: The JPEG Lossless (FOP - process 14) transfer syntax is preferred.

DICOM Conformance Statement Page 27 of 63 3.3.2.1.3. SOP Specific Conformance for C-STORE SCU The Xcelera Auto Export AE conforms to the SOP s of the Storage Service Class at level 2 (full). No data elements are discarded or coerced by the Xcelera Auto Export AE. Xcelera can be used to modify the following attributes: (0008,0020) Study Date (0008,0030) Study Time (0008,0050) Accession Number (0008,0090) Referring Physician s Name (0010,0010) Patient s Name (0010,0020) Patient ID (0010,0030) Patient s Birth Date (0010,0040) Patient s Sex (0020,000D) Study Instance UID (0020,0010) Study ID During export the values of these attributes will overrule the initially stored attribute values. When an attribute with a Value Representation Time or DateTime is exported, the time fraction is not supported. The Xcelera Auto Export AE can perform a transfer syntax conversion according to the following table. Table 3-16: Transfer syntax conversion Source Syntax Destination Syntax ILE JPEG Lossless JPEG Lossy RLE ILE + + + - - - + + + - - - + + + - - - JPEG Lossless + + + + - - JPEG Lossy - - - - + - RLE - - - - - +

DICOM Conformance Statement Page 28 of 63 The behavior on successful and unsuccessful transfer of images is given in the table below. Table 3-17: Action on received C-STORE status responses Service Status Codes Behavior on Received Status Refused A700 Log; Release association; Release application; Retry to send the images. Error 0110 Log; Release association; Release application; Retry to send the images. Warning A900 C000 B000 B006 B007 Log; Release association; Release application; Retry to send the images. Log; Release association; Release application; Retry to send the images. Log; Continue. Log; Continue. Log; Continue. Success 0000-3.3.2.2. Transfer Xcelera Photo Files 3.3.2.2.1. Associated Real-World Activity The Xcelera Auto Export AE will only export the images automatically when configured to do so. In the system configuration up to 2 destinations can be declared/configured. On creating photo files on the Xcelera, these Secondary Capture images will be automatically sent to the configured destinations sequentially. 3.3.2.2.2. Proposed presentation Contexts As the photo files shall be uncompressed, the proposed presentation context shall include uncompressed transfer syntaxes only (conform Table 3-16: Transfer syntax conversion). Accordingly the following table illustrates the proposed presentation contexts for the Secondary Capture Image Storage request.

DICOM Conformance Statement Page 29 of 63 Table 3-18: Proposed Presentation Contexts of the Xcelera Auto Export AE Presentation Context Table Abstract Syntax Transfer Syntax Name UID Name List UID List Role Extended Negotiation Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7 ILE SCU 3.3.2.2.3. SOP Specific Conformance for C-STORE SCU The Xcelera Auto Export AE conforms to the SOP s of the Storage Service Class at level 2 (full). No data elements are discarded or coerced by the Xcelera Auto Export AE. Xcelera can be used to modify the following attributes: (0008,0020) Study Date (0008,0030) Study Time (0008,0050) Accession Number (0008,0090) Referring Physician s Name (0010,0010) Patient s Name (0010,0020) Patient ID (0010,0030) Patient s Birth Date (0010,0040) Patient s Sex (0020,000D) Study Instance UID (0020,0010) Study ID During export the values of these attributes will overrule the actual attribute values. When an attribute with a Value Representation Time or DateTime is exported, the time fraction is not supported. The behavior on successful and unsuccessful transfer of images is given in Table 3-17: Action on received C-STORE status responses. 3.3.2.3. Transfer DSR-TIFF Ultrasound Images 3.3.2.3.1. Associated Real-World Activity The Xcelera Auto Export AE will only export the images automatically when configured to do so. In the system configuration up to 2 destinations can be declared/configured. On receiving DSR-TIFF ultrasound images, the images will be automatically converted to DICOM images and sent to the configured destinations sequentially. 3.3.2.3.2. Proposed presentation Contexts Table 3-15 illustrates the proposed presentation contexts for the Ultrasound / Ultrasound Multi-frame Image Storage request. 3.3.2.3.3. SOP Specific Conformance for C-STORE SCU

DICOM Conformance Statement Page 30 of 63 The Xcelera Auto Export AE conforms to the SOP s of the Storage Service Class at level 2 (full). No data elements are discarded or coerced by the Xcelera Auto Export AE. Xcelera can be used to modify the following attributes: (0008,0020) Study Date (0008,0030) Study Time (0008,0050) Accession Number (0008,0090) Referring Physician s Name (0010,0010) Patient s Name (0010,0020) Patient ID (0010,0030) Patient s Birth Date (0010,0040) Patient s Sex (0020,000D) Study Instance UID (0020,0010) Study ID During export the values of these attributes will overrule the actual attribute values. When an attribute with a Value Representation Time or DateTime is exported, the time fraction is not supported. The behavior on successful and unsuccessful transfer of images is given in Table 3-17: Action on received C-STORE status responses. 3.3.3. Association Acceptance Policy The Xcelera Auto Export AE never accepts any associations.

DICOM Conformance Statement Page 31 of 63 3.4. Xcelera Send Images AE The Xcelera Send Images AE provides standard SCU conformance for the DICOM V3.0 SOP classes specified in Table 3-19. Table 3-19: Supported SOP Classes of the Xcelera Send Images AE SOP class Name UID Ultrasound Multi-frame Image Storage 1.2.840.10008.5.1.4.1.1.3.1 MR Image Storage 1.2.840.10008.5.1.4.1.1.4 Ultrasound Image Storage 1.2.840.10008.5.1.4.1.1.6.1 Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7 X-Ray Angiographic Image Storage 1.2.840.10008.5.1.4.1.1.12.1 Nuclear Medicine Image Storage 1.2.840.10008.5.1.4.1.1.20 3.4.1. Association Establishment Policies 3.4.1.1. General The Xcelera Send Images AE always proposes the following DICOM Application Context Name (ACN): 1.2.840.10008.3.1.1.1 The maximum length PDU negotiation is included in all association establishment requests. The default maximum length PDU for an association initiated by the Xcelera Send Images AE is 28 kb. 3.4.1.2. Number of Associations For the storage SCU service 5 associations can be active at a time. 3.4.1.3. Asynchronous Nature DICOM asynchronous mode is not supported, meaning that only one transaction may be outstanding over each association at any given point in time. 3.4.1.4. Implementation Identifying Information Implementation Class UID = 1.3.46.670589.16.14.1.1.1 Implementation Version Name = Xcelera R1.1.L1 3.4.2. Association Initiation Policy 3.4.2.1. Export Images 3.4.2.1.1. Associated Real-World Activity After the activation of the Send function the Xcelera Send Images AE will only export the selected images.

DICOM Conformance Statement Page 32 of 63 3.4.2.1.2. Proposed presentation Contexts The following table illustrates the proposed presentation contexts for the image storage request. Table 3-20: Proposed Presentation Contexts of the Xcelera Send Images AE Presentation Context Table Abstract Syntax Transfer Syntax Name UID Name List UID List Role Extended Negotiation Ultrasound Multi-frame Image Storage 1.2.840.10008.5.1.4.1.1.3.1 ILE RLE JPEG Lossy Baseline JPEG Lossless First-Order Prediction (Process 14) (Selection Value 1).5.4.50.4.70 SCU MR Image Storage 1.2.840.10008.5.1.4.1.1.4 ILE SCU Ultrasound Image Storage 1.2.840.10008.5.1.4.1.1.6.1 ILE RLE JPEG Lossy Baseline JPEG Lossless First-Order Prediction (Process 14) (Selection Value 1).5.4.50.4.70 SCU Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7 ILE JPEG Lossy Baseline JPEG Lossless First-Order Prediction (Process 14) (Selection Value 1).4.50.4.70 SCU X-Ray Angiographic Image Storage 1.2.840.10008.5.1.4.1.1.12.1 ILE JPEG Lossy Baseline JPEG Lossless First-Order Prediction (Process 14) (Selection Value 1)*.4.50.4.70 SCU Nuclear Medicine Image Storage 1.2.840.10008.5.1.4.1.1.20 ILE RLE JPEG Lossy Baseline JPEG Lossless First-Order Prediction (Process 14) (Selection Value 1).5.4.50.4.70 SCU * Note: The JPEG Lossless (FOP - process 14) transfer syntax is preferred.

DICOM Conformance Statement Page 33 of 63 3.4.2.1.3. SOP Specific Conformance for C-STORE SCU The Xcelera Send Images AE conforms to the SOP s of the Storage Service Class at level 2 (full). No data elements are discarded or coerced by the Xcelera Send Images AE. Xcelera can be used to modify the following attributes: (0008,0020) Study Date (0008,0030) Study Time (0008,0050) Accession Number (0008,0090) Referring Physician s Name (0010,0010) Patient s Name (0010,0020) Patient ID (0010,0030) Patient s Birth Date (0010,0040) Patient s Sex (0020,000D) Study Instance UID (0020,0010) Study ID During export the values of these attributes will overrule the initially stored attribute values. When an attribute with a Value Representation Time or DateTime is exported, the time fraction is not supported. Xcelera Send Images AE can perform a transfer syntax conversion according to the following table. Table 3-21: Transfer syntax conversion Source Syntax Destination Syntax ILE JPEG Lossless JPEG Lossy RLE ILE + + + - - - + + + - - - + + + - - - JPEG Lossless + + + + - - JPEG Lossy - - - - + - RLE - - - - - +

DICOM Conformance Statement Page 34 of 63 The behavior on successful and unsuccessful transfer of images is given in the table below. Table 3-22: Action on received C-STORE status responses Service Status Codes Behavior on Received Status Refused A700 Log; Continue. Error 0110 Log; Continue. Warning A900 C000 B000 B006 B007 Log; Continue. Log; Continue. Log; Continue. Log; Continue. Log; Continue. Success 0000-3.4.3. Association Acceptance Policy The Xcelera Send Images AE never accepts any associations.

DICOM Conformance Statement Page 35 of 63 3.5. Xcelera Query/Retrieve as SCU AE The Xcelera Query/Retrieve as SCU AE provides standard SCU conformance for the DICOM V3.0 SOP classes specified in Table 3-23. Table 3-23: Supported SOP Classes of the Xcelera Query/Retrieve as SCU AE SOP class Name UID Study Root Query/Retrieve Information Model - FIND 1.2.840.10008.5.1.4.1.2.2.1 Study Root Query/Retrieve Information Model - MOVE 1.2.840.10008.5.1.4.1.2.2.2 3.5.1. Association Establishment Policies 3.5.1.1. General The Xcelera Query/Retrieve as SCU AE always proposes the following DICOM Application Context Name (ACN): 1.2.840.10008.3.1.1.1 The maximum length PDU negotiation is included in all association establishment requests. The default maximum length PDU for an association initiated by the Xcelera Query/Retrieve as SCU AE is 28 kb. 3.5.1.2. Number of Associations The number of associations for the Query/Retrieve SCU service that may be active simultaneously is 5. 3.5.1.3. Asynchronous Nature DICOM asynchronous mode is not supported, meaning that only one transaction may be outstanding over each association at any given point in time. 3.5.1.4. Implementation Identifying Information Implementation Class UID = 1.3.46.670589.16.14.1.1.1 Implementation Version Name = Xcelera R1.1.L1 3.5.2. Association Initiation Policy 3.5.2.1. Query a Remote System 3.5.2.1.1. Associated Real-World Activity The Xcelera Query/Retrieve as SCU AE initiates associations to other systems that support the Study Root Query/Retrieve C-FIND service. 3.5.2.1.2. Presentation Context Table The Xcelera Query/Retrieve as SCU AE will propose the presentation contexts as given in the next table.

DICOM Conformance Statement Page 36 of 63 Table 3-24: Proposed Presentation Contexts of the Xcelera Query/Retrieve as SCU AE C-FIND SCU Presentation Context Table Abstract Syntax Transfer Syntax Name UID Name List UID List Role Extended Negotiation See Note See Note ILE SCU Note: Any of the Standard Query/Retrieve FIND SOP classes listed in Table 3-23: Supported SOP Classes of the Xcelera Query/Retrieve as SCU AE. 3.5.2.1.3. SOP Specific Conformance for C-FIND SCU Only Study level queries are supported. The Xcelera Query/Retrieve as SCU AE supports queries based on the combination of the following (Study level) attributes and attribute matching types (as defined in [DICOM] PS 3.4). Table 3-25: Attribute Matching of the Xcelera Query/Retrieve as SCU AE C-FIND SCU Key Attribute Name Tag Attribute Matching Type Study Instance UID (0020,000D) Universal Matching Study Date (0008,0020) Universal Matching Range Matching Accession Number (0008,0050) Universal Matching Wild Card Matching Single Value Matching Patient s Name (0010,0010) Universal Matching Wild Card Matching (ref. Note) Patient ID (0010,0020) Universal Matching Wild Card Matching Single Value Matching Modalities in study (0008,0061) Universal Matching Patient s Birth Date (0010,0030) Universal Matching Single Value Matching Patient s Sex (0010,0040) Universal Matching Single Value Matching Note: The Patient s Name key attribute matching type is implicitly converted from Single Value matching to Wild Card matching by adding a Wild Card * character at the end of its value.

DICOM Conformance Statement Page 37 of 63 The following table lists the actions that are performed when an exception occurs. Table 3-26: Action on received C-FIND status responses Service Status Codes Behavior on Received Status Refused A700 Log; Release association. Failed A900 C001 Log; Release association. Log; Release association. Cancel FE00 Log; Release association. Success 0000 Release association. Pending FF00 FF01 Continue. Continue. 3.5.2.2. Retrieve from a Remote System 3.5.2.2.1. Associated Real-World Activity The Xcelera Query/Retrieve as SCU AE initiates associations to other systems that support the Study Root Query/Retrieve C-MOVE service. 3.5.2.2.2. Presentation Context Table The Xcelera Query/Retrieve as SCU AE will propose the presentation contexts as given in the next table: Table 3-27: Proposed Presentation Contexts of the Xcelera Query/Retrieve as SCU AE C-MOVE SCU Presentation Context Table Abstract Syntax Transfer Syntax Name UID Name List UID List Role Extended Negotiation See Note See Note ILE SCU Note: Any of the Standard Query/Retrieve C-MOVE SOP classes listed in Table 3-23: Supported SOP Classes of the Xcelera Query/Retrieve as SCU AE 3.5.2.2.3. SOP Specific Conformance for C-MOVE SCU The Xcelera Query/Retrieve as SCU AE supports the baseline behavior of SCU as specified in [DICOM] PS 3.4-2003, Annex C, section C.4.2.2.1.

DICOM Conformance Statement Page 38 of 63 The following table lists the actions that are performed when an exception occurs. Table 3-28: Action on received C-MOVE status responses Service Status Codes Behavior on Received Status Refused Failed A701 A702 A801 A900 C001 Log; Release association. Log; Release association. Log; Release association. Log; Release association. Log; Release association. Warning B000 Log; Release association. Success 0000 Release association. Pending FF00 Continue. 3.5.3. Association Acceptance Policy The Xcelera Query/Retrieve as SCU AE never accepts any associations.

DICOM Conformance Statement Page 39 of 63 3.6. Xcelera Query/Retrieve as SCP AE The Xcelera Query/Retrieve as SCP AE provides standard SCP conformance for the DICOM V3.0 SOP classes specified in Table 3-29. Table 3-29: Supported SOP Classes of the Xcelera Query/Retrieve as SCP AE SOP class Name UID Verification 1.2.840.10008.1.1 Patient Root Query/Retrieve Information Model - FIND 1.2.840.10008.5.1.4.1.2.1.1 Patient Root Query/Retrieve Information Model - MOVE 1.2.840.10008.5.1.4.1.2.1.2 Study Root Query/Retrieve Information Model - FIND 1.2.840.10008.5.1.4.1.2.2.1 Study Root Query/Retrieve Information Model - MOVE 1.2.840.10008.5.1.4.1.2.2.2 Patient/Study Only Query/Retrieve Information Model FIND 1.2.840.10008.5.1.4.1.2.3.1 Patient/Study Only Query/Retrieve Information Model - MOVE 1.2.840.10008.5.1.4.1.2.3.2 When the Query/Retrieve C-MOVE service is requested, the Xcelera Query/Retrieve as SCP AE provides standard SCU conformance for the DICOM V3.0 SOP classes specified in Table 3-30. Table 3-30: Supported Storage SOP Classes of the Xcelera Query/Retrieve as SCP AE SOP class Name UID Ultrasound Multi-frame Image Storage 1.2.840.10008.5.1.4.1.1.3.1 MR Image Storage 1.2.840.10008.5.1.4.1.1.4 Ultrasound Image Storage 1.2.840.10008.5.1.4.1.1.6.1 Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7 X-Ray Angiographic Image Storage 1.2.840.10008.5.1.4.1.1.12.1 Nuclear Medicine Image Storage 1.2.840.10008.5.1.4.1.1.20 3.6.1. Association Establishment Policies 3.6.1.1. General The Xcelera Query/Retrieve as SCP AE always proposes the following DICOM Application Context Name (ACN): 1.2.840.10008.3.1.1.1 The maximum length PDU negotiation is included in all association establishment requests. The default maximum length PDU for an association initiated by the Xcelera Query/Retrieve as SCP AE is 28 kb.

Philips Medical Systems. Xcelera R1.1L1. Document Number XPR July 2003