DICOM Conformance Statement - PDF Free Download

1. OVERVIEW Epic Burn&Print (Epic BP) is a software application for storing DICOM images on removable media as CDs and DVDs where each single support can contain images concerning only one DICOM study (complete or partial). Epic BP waits for incoming images on the predefined port using TCP/IP as network protocol. Epic BP can only receive images for storing service. 2006 Marco Grampa - All rights reserved Page 2

2. TABLE OF CONTENTS 1. OVERVIEW... 2 2. TABLE OF CONTENTS... 3 3. INTRODUCTION... 4 3.1. Revision History... 4 3.2. Audience... 4 3.3. Remarks... 4 3.4. Definitions, Terms and Abbreviations... 4 3.5. References... 5 4. NETWORKING... 6 4.1. Implementation Model... 6 4.1.1. Application Data Flow Diagram... 6 4.1.2. Functional Definition of AE s... 6 4.1.2.1. STORAGE-SCP... 6 4.1.3. Sequencing of Real World Activities... 6 4.2. AE Specifications... 6 4.2.1. STORAGE-SCP... 6 4.2.1.1. SOP Classes... 6 4.2.1.2. Association Policies... 8 4.2.1.2.1. General... 8 4.2.1.2.2. Number of Associations... 8 4.2.1.2.3. Asynchronous Nature... 8 4.2.1.2.4. Implementation Identifying Information... 8 4.2.1.3. Association Initiation Policy... 8 4.2.1.4. Association Acceptance Policy... 8 4.2.1.4.1. Activity Verification Request... 8 4.2.1.4.1.1. Description and Sequencing of Activities... 8 4.2.1.4.1.2. Accepted Presentation Contexts... 8 4.2.1.4.2. Activity Storage Request... 9 4.2.1.4.2.1. Description and Sequencing of Activities... 9 4.2.1.4.2.2. Accepted Presentation Contexts... 9 4.2.1.4.2.3. SOP Specific Conformance... 9 4.3. Network Interfaces... 9 4.3.1. Physical Network Interface... 9 4.3.2. Additional Protocols... 9 4.4. Configuration... 9 5. MEDIA INTERCHANGE... 10 5.1. Implementation Model... 10 5.1.1. Application Data Flow Diagram... 10 5.1.2. Functional definitions of AE s... 10 5.1.2.1. MEDIA-FSC... 10 5.1.3. Sequencing of Real World Activities... 10 5.1.4. File Meta Information for Implementation Class and Version... 10 5.2. AE Specifications... 11 5.2.1. MEDIA-FSC... 11 5.2.1.1. File Meta Information for the Application Entity... 11 5.2.1.2. Real World Activities... 11 5.2.1.2.1. Activity Store Job... 11 5.2.1.2.1.1. Media Storage Application Profile... 11 5.3. Augmented and Private Application Profiles... 11 5.3.1. Augmented Profiles... 11 5.3.2. Private Profiles... 11 5.4. Media Configuration... 11 2006 Marco Grampa - All rights reserved Page 3

3. INTRODUCTION This document describes the conformance of Epic BP software with the Digital Imaging and Communications in Medicine (DICOM) standard. This document is essential in order to evaluate whether or not another DICOM compliant device may communicate with this software product. This statement is conformant with the recommended format as described in PS 3.2 of the DICOM Standard. 3.1. Revision History Revision Date Comments 1 October 20, 2006 Initial version 3.2. Audience It is assumed that the readers are familiar with the terminology and concepts that are used in the DICOM standard. If the readers are unfamiliar with DICOM, it is recommended that they first read the DICOM standard itself, prior to reading this document. 3.3. Remarks This Conformance Statement is intended to facilitate communication with other medical imaging equipment but it does not guarantee the connectivity between Epic BP and any equipment or applications of thirty parts. The document itself does not include any sort of testing or validating procedure to support such connectivity. 3.4. Definitions, Terms and Abbreviations Acronym ACR ACSE AE ANSI AP API ASCII CD CD-R CD-RW CEN TC251 DICOM DIMSE DIMSE-C DIMSE-N DVD DVD+R DVD+RW FSC FSR FSU Definition American College of Radiology Association Control Service Element Application Entity American National Standards Institute Application Profile Application Programming Interface American Standard Code for Information Interchange Compact Disk Compact Disk - Recordable Compact Disk - Rewritable Comite Europeen de Normalisation-Technical Committee 251-Medical Informatics Digital Imaging and Communications in Medicine DICOM Message Service Element DICOM Message Service Element-Composite DICOM Message Service Element-Normalized Digital Video Disk Digital Video Disk - Recordable Digital Video Disk - Rewritable File-set Creator File-set Reader File-set Updater 2006 Marco Grampa - All rights reserved Page 4

GB Giga bytes HISPP Healthcare Informatics Standards Planning Panel HL7 Health Level 7 IE Information Entity IEEE Institute of Electrical and Electronics Engineers IOD Information Object Definition ISO International Standards Organization ISP International Standardized Profile JIRA Japanese Industry Radiology Apparatus MB Mega bytes MSDS Healthcare Message Standard Developers Sub-Committee NEMA National Electrical Manufacturers Association OSI Open Systems Interconnection PDU Protocol Data Unit RWA Real-World Activity SCP Service Class Provider SCU Service Class User SOP Service-Object Pair TCP/IP Transmission Control Protocol/Internet Protocol UID Unique Identifier UML Unified Modeling Language VR VR Value Representation 3.5. References This document is written with respect to the ACR-NEMA DICOM version 3.0. 2006 Marco Grampa - All rights reserved Page 5

4. NETWORKING 4.1. Implementation Model Networking implementation of Epic BP consists of one STORAGE-SCP Application Entity implemented as a DICOM SCP. 4.1.1. Application Data Flow Diagram STORAGE-SCP Application Entity Verification request by remote AE Storage request by remote AE 4.1.2. Functional Definition of AE s 4.1.2.1. STORAGE-SCP STORAGE-SCP waits for connection requests on the predefined listening TCP/IP port. When the request correspond to a C-STORE command, the STORAGE-SCP acts as a SCP for the storage service class and stores the received images as DICOM objects in the local cache (temporary area for processing images). STORAGE-SCP also responds to C-ECHO commands. 4.1.3. Sequencing of Real World Activities The SCP activity is performed in the background and does not depend on any sequencing. 4.2. AE Specifications 4.2.1. STORAGE-SCP 4.2.1.1. SOP Classes STORAGE-SCP provides Standard Conformance to the following SOP Classes: SOP Classes SCU SCP 1.2.840.10008.1.1 Verification SOP Class No Yes Storage 1.2.840.10008.5.1.1.27 Stored Print Storage SOP Class No Yes 1.2.840.10008.5.1.1.29 Hardcopy Grayscale Image Storage SOP Class No Yes 1.2.840.10008.5.1.1.30 Hardcopy Color Image Storage SOP Class No Yes 1.2.840.10008.5.1.4.1.1.1 Computed Radiography Image Storage No Yes 1.2.840.10008.5.1.4.1.1.1.1 Digital X-Ray Image Storage - For Presentation No Yes 1.2.840.10008.5.1.4.1.1.1.1.1 Digital X-Ray Image Storage - For Processing No Yes 2006 Marco Grampa - All rights reserved Page 6

1.2.840.10008.5.1.4.1.1.1.2 Digital Mammography X-Ray Image Storage - For Presentation No Yes 1.2.840.10008.5.1.4.1.1.1.2.1 Digital Mammography X-Ray Image Storage - For Processing No Yes 1.2.840.10008.5.1.4.1.1.1.3 Digital Intra-oral X-Ray Image Storage - For Presentation No Yes 1.2.840.10008.5.1.4.1.1.1.3.1 Digital Intra-oral X-Ray Image Storage - For Processing No Yes 1.2.840.10008.5.1.4.1.1.10 Standalone Modality LUT Storage No Yes 1.2.840.10008.5.1.4.1.1.11 Standalone VOI LUT Storage No Yes 1.2.840.10008.5.1.4.1.1.11.1 Grayscale Softcopy Presentation State Storage SOP Class No Yes 1.2.840.10008.5.1.4.1.1.12.1 X-Ray Angiographic Image Storage No Yes 1.2.840.10008.5.1.4.1.1.12.2 X-Ray Radiofluoroscopic Image Storage No Yes 1.2.840.10008.5.1.4.1.1.128 Positron Emission Tomography Image Storage No Yes 1.2.840.10008.5.1.4.1.1.129 Standalone PET Curve Storage No Yes 1.2.840.10008.5.1.4.1.1.2 CT Image Storage No Yes 1.2.840.10008.5.1.4.1.1.2.1 Enhanced CT Image Storage No Yes 1.2.840.10008.5.1.4.1.1.20 Nuclear Medicine Image Storage No Yes 1.2.840.10008.5.1.4.1.1.3.1 Ultrasound Multi-frame Image Storage No Yes 1.2.840.10008.5.1.4.1.1.4 MR Image Storage No Yes 1.2.840.10008.5.1.4.1.1.4.1 Enhanced MR Image Storage No Yes 1.2.840.10008.5.1.4.1.1.4.2 MR Spectroscopy Storage No Yes 1.2.840.10008.5.1.4.1.1.481.1 RT Image Storage No Yes 1.2.840.10008.5.1.4.1.1.481.2 RT Dose Storage No Yes 1.2.840.10008.5.1.4.1.1.481.3 RT Structure Set Storage No Yes 1.2.840.10008.5.1.4.1.1.481.4 RT Beams Treatment Record Storage No Yes 1.2.840.10008.5.1.4.1.1.481.5 RT Plan Storage No Yes 1.2.840.10008.5.1.4.1.1.481.6 RT Brachy Treatment Record Storage No Yes 1.2.840.10008.5.1.4.1.1.481.7 RT Treatment Summary Record Storage No Yes 1.2.840.10008.5.1.4.1.1.6.1 Ultrasound Image Storage No Yes 1.2.840.10008.5.1.4.1.1.66 Raw Data Storage No Yes 1.2.840.10008.5.1.4.1.1.66.1 Spatial Registration Storage No Yes 1.2.840.10008.5.1.4.1.1.66.2 Spatial Fiducials Storage No Yes 1.2.840.10008.5.1.4.1.1.7 Secondary Capture Image Storage No Yes 1.2.840.10008.5.1.4.1.1.7.1 Multi-frame Single Bit Secondary Capture Image Storage No Yes 1.2.840.10008.5.1.4.1.1.7.2 Multi-frame Grayscale Byte Secondary Capture Image Storage No Yes 1.2.840.10008.5.1.4.1.1.7.3 Multi-frame Grayscale Word Secondary Capture Image Storage No Yes 1.2.840.10008.5.1.4.1.1.7.4 Multi-frame True Color Secondary Capture Image Storage No Yes 1.2.840.10008.5.1.4.1.1.77.1.1 VL Endoscopic Image Storage No Yes 1.2.840.10008.5.1.4.1.1.77.1.1.1 Video Endoscopic Image Storage No Yes 1.2.840.10008.5.1.4.1.1.77.1.2 VL Microscopic Image Storage No Yes 1.2.840.10008.5.1.4.1.1.77.1.2.1 Video Microscopic Image Storage No Yes 1.2.840.10008.5.1.4.1.1.77.1.3 VL Slide-Coordinates Microscopic Image Storage No Yes 1.2.840.10008.5.1.4.1.1.77.1.4 VL Photographic Image Storage No Yes 1.2.840.10008.5.1.4.1.1.77.1.4.1 Video Photographic Image Storage No Yes 1.2.840.10008.5.1.4.1.1.77.1.5.1 Ophthalmic Photography 8 Bit Image Storage No Yes 1.2.840.10008.5.1.4.1.1.77.1.5.2 Ophthalmic Photography 16 Bit Image Storage No Yes 1.2.840.10008.5.1.4.1.1.77.1.5.3 Stereometric Relationship Storage No Yes 1.2.840.10008.5.1.4.1.1.8 Standalone Overlay Storage No Yes 1.2.840.10008.5.1.4.1.1.88.11 Basic Text SR No Yes 1.2.840.10008.5.1.4.1.1.88.22 Enhanced SR No Yes 1.2.840.10008.5.1.4.1.1.88.33 Comprehensive SR No Yes 1.2.840.10008.5.1.4.1.1.88.40 Procedure Log Storage No Yes 1.2.840.10008.5.1.4.1.1.88.50 Mammography CAD SR No Yes 1.2.840.10008.5.1.4.1.1.88.59 Key Object Selection Document No Yes 1.2.840.10008.5.1.4.1.1.88.65 Chest CAD SR No Yes 1.2.840.10008.5.1.4.1.1.9 Standalone Curve Storage No Yes 1.2.840.10008.5.1.4.1.1.9.1.1 12-lead ECG Waveform Storage No Yes 1.2.840.10008.5.1.4.1.1.9.1.2 General ECG Waveform Storage No Yes 1.2.840.10008.5.1.4.1.1.9.1.3 Ambulatory ECG Waveform Storage No Yes 1.2.840.10008.5.1.4.1.1.9.2.1 Hemodynamic Waveform Storage No Yes 1.2.840.10008.5.1.4.1.1.9.3.1 Cardiac Electrophysiology Waveform Storage No Yes 1.2.840.10008.5.1.4.1.1.9.4.1 Basic Voice Audio Waveform Storage No Yes 2006 Marco Grampa - All rights reserved Page 7

4.2.1.2. Association Policies 4.2.1.2.1. General STORAGE-SCP accepts association only in response to C-STORE requests to act as storage service class provider or in response to C-ECHO requests to act as verification service class provider. The maximum PDU size transmitted or received is configurable by the user but can not exceed 16384 bytes (default value). Epic BP supports only TCP/IP network protocol and the incoming association requests must be presented on the listening port defined in the configuration file. 4.2.1.2.2. Number of Associations The number of simultaneous associations which will be accepted by STORAGE-SCP is theoretically limited only by the kernel parameters of the underlying TCP/IP protocol implementation. In practice, the number of simultaneous associations is limited to the value defined in the configuration file (default: 25). Maximum number of simultaneous associations Configurable 4.2.1.2.3. Asynchronous Nature Asynchronous operations are not supported. 4.2.1.2.4. Implementation Identifying Information The Implementation Class UID is 1.2.826.0.1.3680043.2.1585.1 and the Implementation Version Name is EPICBP-Vx.y.z (where x, y and z are the major, minor and release version of the product). 4.2.1.3. Association Initiation Policy STORAGE-SCP does not initiate associations. 4.2.1.4. Association Acceptance Policy STORAGE-SCP accepts associations from any DICOM AE only for verification or storage requests. 4.2.1.4.1. Activity Verification Request 4.2.1.4.1.1. Description and Sequencing of Activities The verification request can be submitted from a remote AE to check if STORAGE-SCP is running. The verification request must be submitted with the C-ECHO command. 4.2.1.4.1.2. Accepted Presentation Contexts STORAGE-SCP implements the verification service class only as SCP. Presentation Context Table Abstract Syntax Ext. Role Name UID Name UID neg. Verification Service Class 1.2.840.10008.1.1 Implicit VR Little Endian 1.2.840.10008.1.2 SCP None Explicit VR Little Endian 1.2.840.10008.1.2.1 SCP None Explicit VR Big Endian 1.2.840.10008.1.2.2 SCP None 2006 Marco Grampa - All rights reserved Page 8

4.2.1.4.2. Activity Storage Request 4.2.1.4.2.1. Description and Sequencing of Activities The storage requests must be submitted through the C-STORE command. Upon receiving the C-STORE command, STORAGE-SCP writes the received image in a temporary area (cache) located on a preconfigured disk folder. All the images in the cache are processed by another Application Entity (MEDIA-FSC) and written on the media supports for definitive storing. After storing, the processed images are deleted from the cache. 4.2.1.4.2.2. Accepted Presentation Contexts STORAGE-SCP implements the storage service class only as SCP. Presentation Context Table Abstract Syntax Ext. Role Name UID Name UID neg. All Storage SOP Classes Implicit VR Little Endian 1.2.840.10008.x.y.z (see table above) 1.2.840.10008.1.2 SCP None Explicit VR Little Endian 1.2.840.10008.1.2.1 SCP None Explicit VR Big Endian 1.2.840.10008.1.2.2 SCP None 4.2.1.4.2.3. SOP Specific Conformance STORAGE-SCP implements Level 2 (Full) conformance for the Storage SOP Class. However, after stored in the local cache, the images cannot be accessed by the Application Entity itself. 4.3. Network Interfaces Epic BP provides DICOM TCP/IP Network Communication Support as defined in PS 3.8 of the DICOM standard and uses the TCP/IP stack inherited from the underlying operating system. 4.3.1. Physical Network Interface There are no restrictions on physical network. 4.3.2. Additional Protocols No additional protocols supported. 4.4. Configuration The following parameters can be modified editing the Epic BP configuration file, as reported in the user s manual. Parameter Default Value AE Title EPICBP TCP/IP Address 127.0.0.1 Listening TCP/IP Port 104 Listening TCP/IP Timer 10000 seconds ARTIM Timer 9000 seconds Maximum Received PDU Length 16384 bytes Maximum Transmitted PDU Length 16384 bytes 2006 Marco Grampa - All rights reserved Page 9

5. MEDIA INTERCHANGE 5.1. Implementation Model Media interchange implementation of Epic BP consists of one MEDIA-FSC Application Entity for write DICOM images on media supports. 5.1.1. Application Data Flow Diagram Store Job MEDIA-FSC Application Entity Storage Medium Epic BP assembles all the images received by the STORAGE-SCP AE so that each group (called Job) corresponds to a single DICOM study. Whenever a study is complete its images are stored on one or more media supports (CD or DVD). 5.1.2. Functional definitions of AE s 5.1.2.1. MEDIA-FSC MEDIA-FSC acts as an FSC using the interchange option each time a Job is submitted by the activity Store Job. The images of each Job are written together with the corresponding DICOMDIR to a single media support (CD or DVD). If the Job does not fit on a single media support it is spanned on multiple discs; however, each disc can contain images belonging to a single study. MEDIA-FSC actually writes the discs data in a preconfigured output folder, shared with the driver of the physical writing device. After a Job is definitive stored (on discs) all the related images are deleted from the local cache. 5.1.3. Sequencing of Real World Activities The Store Job activity is performed in the background and does depend on the expiration of each Job s timer. MEDIA-FSC continuously process all closed Jobs, however only a fixed number of Jobs can be simultaneously written on the storage mediums; this depend on the physical device used to write on discs. 5.1.4. File Meta Information for Implementation Class and Version The implementation information written to the File Meta Header in each file is the same of the STORAGE- SCP AE. 2006 Marco Grampa - All rights reserved Page 10

5.2. AE Specifications 5.2.1. MEDIA-FSC MEDIA-FSC provides standard conformance to DICOM Interchange Option of the Media Storage Service Class. The Application Profiles and roles are listed below: Application Profiles Supported Real World Activity Role SC Option STD-GEN-CD Store Job FSC Interchange STD-GEN-DVD-RAM Store Job FSC Interchange 5.2.1.1. File Meta Information for the Application Entity The Source Application Entity Title included in the File Meta Header is the same Application Entity Title of Epic BP installation (defined in the configuration file). No private information is used. 5.2.1.2. Real World Activities 5.2.1.2.1. Activity Store Job Epic BP scans the local cache (where STORAGE-SCP temporary stored the received files) and gathers all the images into groups, called Jobs. Each Job corresponds to a DICOM study and is associated to a timer, started when the Job is created. When the timer expires the Job is closed and Epic BP submit a Store Job command to MEDIA-FSC for definitive storing of the study images on the media support selected in the configuration file. 5.2.1.2.1.1. Media Storage Application Profile MEDIA-FSC AE supports the STD-GEN-CD and STD-GEN-DVD-RAM Application Profile. 5.3. Augmented and Private Application Profiles 5.3.1. Augmented Profiles None. 5.3.2. Private Profiles None. 5.4. Media Configuration The following parameters can be modified editing the Epic BP configuration files, as reported in the user s manual. Parameter CDMAXSIZE DVDMAXSIZE CLUSTERSIZE DICOMDIRRECSIZE USECD USEDVD Default Value 629145600 bytes 5046586572 bytes 4096 bytes 500 bytes TRUE FALSE 2006 Marco Grampa - All rights reserved Page 11