Appendix
AGFA PACS DICOM Conformance Statement ConfStatement
IMPAX DICOM Services
(Release 4.5)
Document No. 000702, Revision 1.3
Page 2 of 29 MED/RDH/000702
Document No. 000702, Revision 1.3
26 May, 2005 Healthcare
Document Information
Authors Ron Hitzelberger Tel: 1 (864) 943-1940
Fax: 1 (864) 943-1018
Europe: Tel: +32 3 444 8221
Fax: +32 3 444 8211
USA: Tel: 1 201 440 2500 x3598
For questions regarding the technical
content of this document, please contact:
Japan: Tel: +81 3 5704 3091
Fax: +81 3 5704 3087
Issued by:
HealthCare
Glasgow Business Community
P.O. Box 6020
640 Technology Drive
Newark, DE 19714-6020
USA
Agfa shall not be liable for errors contained herein or for incidental or
consequential damages in connection with the furnishing, performance
or use of this publication. Agfa reserves the right to revise this
publication and to make changes to its content at any time, without
obligation to notify any person or entity of such revisions and changes.
This publication may only be used in connection with the promotion,
sales, installation and use of Agfa equipment by Agfa personnel. The
information presented herein is sensitive and is classified Company
Confidential. Without written authority from the proprietor, further
distribution outside the company is not allowed.
Tel: 1 (302) 631-3494
Fax: 1 (302) 631-3145
Copyright May, 05
Healthcare
All rights reserved
MED/RDH/000702 Page 3 of 29
Document No. 000702, Revision 1.3
Healthcare 26 May, 2005
Table of Contents
Left out from this document for the sake of simplicity
…
1 INTRODUCTION
1.1 Intended Audience
The user of this document is involved with system integration and/or software design. We assume that
the reader is familiar with the terminology and concepts that are used in the DICOM 3.0 standard.
Readers not familiar with DICOM 3.0 terminology should first read the appropriate parts of the DICOM
standard itself, prior to reading this conformance statement.
Although the use of this conformance statement in conjunction with the DICOM 3.0 standard is intended
to facilitate communication with other imaging equipment, it is not sufficient to guarantee, by itself, the
inter-operation of the connection. The following issues need to be considered:
1.1.1 Integration
The integration of any device into a system of interconnected devices goes beyond the scope of the
DICOM 3.0 standard and this conformance statement when interoperability is desired. The responsibility
for analyzing the applications requirements and developing a solution that integrates the Agfa equipment
with other vendors. systems is the user.s responsibility and should not be underestimated.
1.1.2 Validation
Testing the complete range of possibilities between the Agfa equipment and non-Agfa devices, before the
connection is declared operational, is deemed to be a necessity. The user should ensure that any non-
Agfa provider accepts full responsibility for all validation required for their connection with the Agfa
equipment. The accuracy of image data once it has crossed the interface between the Agfa equipment
and the non-Agfa device as well as the stability of the image data for the intended applications is the
responsibility of the non-Agfa provider.
1.1.3 Future Evolution
As the DICOM 3.0 standard evolves to meet the user.s growing requirements and to incorporate new
features and technologies, Agfa will follow the evolution of the standard. This evolution of the standard
may require changes to devices that have implemented DICOM 3.0. The user should ensure that any
non-Agfa provider, who connects with Agfa devices, also plans future evolution of the DICOM standard. A
refusal to do so may reflect in the loss of functionality and/or connectivity between the different products.
1.2 Purpose of this Document
This document describes the conformance of IMPAX to the ACR-NEMA DICOM (Digital Imaging and
Communications in Medicine) standard, and satisfies the DICOM requirement for a vendor conformance
specification.
The IMPAX Network Gateway accepts images from modalities and performs verification and routing
services. It is the workflow manager of the IMPAX system used for storage, processing, retrieval, printing
or otherwise communicating medical image data. The Network Gateway is simply referred to as IMPAX
in this document.
1.3 Sources for this Document
ACR-NEMA Digital Imaging and Communications in Medicine (DICOM) V3.0. Current.
Page 8 of 29 MED/RDH/000702
Document No. 000702, Revision 1.3
26 May, 2005 Healthcare
2 IMPLEMENTATION MODEL
The following diagram represents the Application Entity present in IMPAX.s implementation, and
graphically depicts the relationship of the AE’s use of DICOM to Real-World Activities.
Figure 2.1 Application data flow diagram.
2.1 Functional Definition of Entities
As a storage facility, IMPAX is a single application entity that stores images sent to it by service class
users, takes responsibility for storage of the images, allows queries based on several standard query
models, and retrieves requested images.
IMPAX is able to validate images before they are stored internally by querying a service class provider for
demographic information. Images found to be registered with the HIS/RIS are stored, while images not
found to be registered are automatically corrected, where possible, or set aside for a technician to correct.
IMPAX
(Network
Gateway)
Application
Entity
DICOM
Standard Interface
Local Remote
Remote
Storage
SCU/SCP
Storage
Commitment
SCU/SCP
Query/
Retrieve
SCU/SCP
Detached
Study Mgt.
SCP
Printing
SCP
Modality
Worklist
SCP
Verification
SCU/SCP
Archive
Display
MED/RDH/000702 Page 9 of 29
Document No. 000702, Revision 1.3
Healthcare 26 May, 2005
2.1.1 Verification
The IMPAX AE supports the C-ECHO DIMSE-C service.
2.1.2 Modality Worklist Management
The IMPAX AE acts a Service Class Provider of Modality Worklist Management.
2.1.3 Remote Storage
The IMPAX AE stores a received image in its entirety, without change, in its internal data store. IMPAX
stores each image with the File Meta Information attached to it. It extracts the query information with
respect to the Patient, Study, Series and Image, and stores this information within its internal database.
The IMPAX AE also acts as a Service Class User of C-STORE to transmit images to other compatible devices.
2.1.4 Storage Commitment
The IMPAX AE acts as a Service Class Provider for Storage Commitment to explicitly take responsibility
for storing images received.
2.1.5 Query and Retrieve
The IMPAX AE responds to C-FIND queries based on the records stored in its database.
The IMPAX AE acts as a Service Class Provider of C-MOVE to retrieve images. It does so by obtaining a
reference from the database then obtaining the image object itself from the data store.
2.1.6 Detached Study Management
The IMPAX AE acts as a Service Class User of the Detached Study Management SOP Class.
2.1.7 Printing
The IMPAX AE provides for color and grayscale printing to Agfa and selected non-Agfa printers.
3 AE SPECIFICATIONS
3.1.1 Default Transfer Syntaxes
IMPAX supports the default transfer syntax displayed in Table 3.1.
Transfer Syntax UID
DICOM Implicit VR Little Endian 1.2.840.10008.1.2
Table 3.1 Default transfer syntax.
3.1.2 Extended Transfer Syntaxes
IMPAX supports the extended transfer syntaxes displayed in Table 3.2 for the purpose of storage and retrieval.
Transfer Syntax UID
DICOM Implicit VR Little Endian 1.2.840.10008.1.2
DICOM Explicit VR Big Endian 1.2.840.10008.1.2.2
RLE Lossless, PackBits 1.2.840.10008.1.2.5
JPEG Process 1, baseline, lossy (8 bit) 1.2.840.10008.1.2.4.50
JPEG Process 2,4, extended lossy (12 bit) 1.2.840.10008.1.2.4.51
JPEG Process 14, lossless 1.2.840.10008.1.2.4.57
JPEG Process 14, selection value 1, lossless 1.2.840.10008.1.2.4.70
Table 3.2 Extended transfer syntaxes.
Page 10 of 29 MED/RDH/000702
Document No. 000702, Revision 1.3
26 May, 2005 Healthcare
3.1.3 Verification as an SCU and SCP
IMPAX provides Standard Conformance to the following DICOM V3.0 SOP Class as an SCU and SCP.
SOP Class SOP Class UID
Verification 1.2.840.10008.1.1
Table 3.3 Verification SOP class.
3.1.4 Modality Worklist Management as an SCU
IMPAX provides Standard Conformance to the following DICOM V3.0 Worklist Management SOP Class
as an SCU.
SOP Class SOP Class UID
Modality Worklist Info Model .FIND 1.2.840.10008.5.1.4.31
Table 3.4 Worklist management SOP classes.
3.1.5 Storage as an SCU and SCP
Table 3.5 lists the SOP Classes that are supported by IMPAX for storage services. In general, IMPAX will
be extended to support all image SOP classes recognized by DICOM.
SOP Class SOP Class UID
Computed Radiography Image Storage 1.2.840.10008.5.1.4.1.1.1
Digital X-ray Image Storage - For Presentation 1.2.840.10008.5.1.4.1.1.1.1
Digital X-ray Image Storage - For Processing 1.2.840.10008.5.1.4.1.1.1.1.1
Digital Mammography X-ray Image Storage - For Presentation 1.2.840.10008.5.1.4.1.1.1.2
Digital Mammography X-ray Image Storage - For Processing 1.2.840.10008.5.1.4.1.1.1.2.1
CT Image Storage 1.2.840.10008.5.1.4.1.1.2
Ultrasound Multi-frame Image Storage (retired) 1.2.840.10008.5.1.4.1.1.3
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
Nuclear Medicine Image Storage (retired) 1.2.840.10008.5.1.4.1.1.5
Ultrasound Image Storage (retired) 1.2.840.10008.5.1.4.1.1.6
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
Standalone Overlay Image Storage 1.2.840.10008.5.1.4.1.1.8
Standalone Curve Storage 1.2.840.10008.5.1.4.1.1.9
Standalone Modality LUT Storage 1.2.840.10008.5.1.4.1.1.10
Standalone VOI LUT Storage 1.2.840.10008.5.1.4.1.1.11
Greyscale Softcopy Presentation State Storage 1.2.840.10008.5.1.4.1.1.11.1
X-Ray Angiographic Image Storage 1.2.840.10008.5.1.4.1.1.12.1
X-Ray RadioFluoroscopic Image Storage 1.2.840.10008.5.1.4.1.1.12.2
X-Ray Angiographic Bi-plane Image Storage (retired) 1.2.840.10008.5.1.4.1.1.12.3
Nuclear Medicine Image Storage 1.2.840.10008.5.1.4.1.1.20
Visible Light Image Storage (retired) 1.2.840.10008.5.1.4.1.1.77.1
Visible Light Slide-Coordinates Microscopic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.3
Visible Light Photographic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.4
Visible Light Multi-frame Image Storage (retired) 1.2.840.10008.5.1.4.1.1.77.2
Structured Report Text Storage 1.2.840.10008.5.1.4.1.1.88.1
Structured Report Audio Storage 1.2.840.10008.5.1.4.1.1.88.2
Structured Report Detail Storage 1.2.840.10008.5.1.4.1.1.88.3
Structured Report Comprehensive Storage 1.2.840.10008.5.1.4.1.1.88.4
Basic Text Structured Report Storage 1.2.840.10008.5.1.4.1.1.88.11
Enhanced Structured Report Storage 1.2.840.10008.5.1.4.1.1.88.22
Positron Emission Tomography Image Storage 1.2.840.10008.5.1.4.1.1.128
Table 3.5 Storage SOP Classes.
MED/RDH/000702 Page 11 of 29
Document No. 000702, Revision 1.3
Healthcare 26 May, 2005
3.1.5.1 Grayscale Softcopy Presentation State Storage as an SCP
IMPAX provides Standard Conformance to the DICOM V3.0 Grayscale Softcopy Presentation State
SOP Class as an SCP. The Image Storage SOP Classes in Table 3.6 may be referenced by instances of
Grayscale Softcopy Presentation State SOP Class.
SOP Class SOP Class UID
Computed Radiography Image Storage 1.2.840.10008.5.1.4.1.1.1
CT Image Storage 1.2.840.10008.5.1.4.1.1.2
Ultrasound Multi-frame Image Storage (retired) 1.2.840.10008.5.1.4.1.1.3
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
Nuclear Medicine Image Storage (retired) 1.2.840.10008.5.1.4.1.1.5
Positron Emission Tomography Image Storage 1.2.840.10008.5.1.4.1.1.128
Ultrasound Image Storage (retired) 1.2.840.10008.5.1.4.1.1.6
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
X-Ray RadioFluoroscopic Image Storage 1.2.840.10008.5.1.4.1.1.12.2
X-Ray Angiographic Bi-plane Image Storage (retired) 1.2.840.10008.5.1.4.1.1.12.3
Digital X-ray Image Storage - For Presentation 1.2.840.10008.5.1.4.1.1.1.1
Digital X-ray Image Storage - For Processing 1.2.840.10008.5.1.4.1.1.1.1.1
Digital Mammography X-ray Image Storage - For Presentation 1.2.840.10008.5.1.4.1.1.1.2
Digital Mammography X-ray Image Storage - For Processing 1.2.840.10008.5.1.4.1.1.1.2.1
Digital Intra-oral X-Ray Image Storage . For Presentation 1.2.840.10008.5.1.4.1.1.1.3
Digital Intra-oral X-Ray Image Storage . For Processing 1.2.840.10008.5.1.4.1.1.1.3.1
Nuclear Medicine Image Storage 1.2.840.10008.5.1.4.1.1.20
Visible Light Image Storage (retired) 1.2.840.10008.5.1.4.1.1.77.1
Visible Light Multi-frame Image Storage (retired) 1.2.840.10008.5.1.4.1.1.77.2
Visible Light Slide-Coordinates Microscopic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.3
Visible Light Photographic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.4
Table 3.6 GSPS SOP classes.
3.1.5.2 Structured Reporting Storage as an SCU and SCP
IMPAX provides Standard Conformance to the following DICOM V3.0 Structured Reporting SOP Class
as an SCU and SCP.
The following Image Storage SOP Classes may be referenced by instances of Structured Reporting SOP Class.
SOP Class SOP Class UID
Computed Radiography Image Storage 1.2.840.10008.5.1.4.1.1.1
CT Image Storage 1.2.840.10008.5.1.4.1.1.2
Ultrasound Multi-frame Image Storage (retired) 1.2.840.10008.5.1.4.1.1.3
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
Nuclear Medicine Image Storage (retired) 1.2.840.10008.5.1.4.1.1.5
Positron Emission Tomography Image Storage 1.2.840.10008.5.1.4.1.1.128
Ultrasound Image Storage (retired) 1.2.840.10008.5.1.4.1.1.6
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
X-Ray RadioFluoroscopic Image Storage 1.2.840.10008.5.1.4.1.1.12.2
X-Ray Angiographic Bi-plane Image Storage (retired) 1.2.840.10008.5.1.4.1.1.12.3
Digital X-ray Image Storage - For Presentation 1.2.840.10008.5.1.4.1.1.1.1
Digital X-ray Image Storage - For Processing 1.2.840.10008.5.1.4.1.1.1.1.1
Digital Mammography X-ray Image Storage - For Presentation 1.2.840.10008.5.1.4.1.1.1.2
Digital Mammography X-ray Image Storage - For Processing 1.2.840.10008.5.1.4.1.1.1.2.1
Digital Intra-oral X-Ray Image Storage . For Presentation 1.2.840.10008.5.1.4.1.1.1.3
Digital Intra-oral X-Ray Image Storage . For Processing 1.2.840.10008.5.1.4.1.1.1.3.1
Page 12 of 29 MED/RDH/000702
Document No. 000702, Revision 1.3
26 May, 2005 Healthcare
SOP Class SOP Class UID
Nuclear Medicine Image Storage 1.2.840.10008.5.1.4.1.1.20
Visible Light Image Storage (retired) 1.2.840.10008.5.1.4.1.1.77.1
Visible Light Multi-frame Image Storage (retired) 1.2.840.10008.5.1.4.1.1.77.2
Visible Light Slide-Coordinates Microscopic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.3
Visible Light Photographic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.4
Table 3.7 SR SOP classes.
3.1.6 Storage Commitment as an SCU and SCP
IMPAX provides Standard Conformance to the following DICOM V3.0 Storage Commitment SOP Class
as an SCU and SCP.
SOP Class SOP Class UID
Storage Commitment Push Model 1.2.840.10008.1.20.1
Table 3.8 Storage Commitment SOP Class.
3.1.7 Query/Retrieve as an SCU and SCP
IMPAX provides Standard Conformance to the following DICOM V3.0 Query/Retrieve SOP Class as an
SCU and SCP.
SOP Class SOP Class UID
Patient Root Query/Retrieve IM Find 1.2.840.10008.5.1.4.1.2.1.1
Patient Root Query/Retrieve IM Move 1.2.840.10008.5.1.4.1.2.1.2
Study Root Query/Retrieve IM Find 1.2.840.10008.5.1.4.1.2.2.1
Study Root Query/Retrieve IM Move 1.2.840.10008.5.1.4.1.2.2.2
Patient/Study Only Query/Retrieve IM Find 1.2.840.10008.5.1.4.1.2.3.1
Patient/Study Only Query/Retrieve IM Move 1.2.840.10008.5.1.4.1.2.3.2
Table 3.9 Query/Retrieve SOP classes.
3.1.8 Detached Study Management as an SCU
IMPAX provides Standard Conformance to the following DICOM V3.0 Detached Study Management
SOP Class as an SCU.
SOP Class SOP Class UID
Detached Study Management 1.2.840.10008.3.1.2.3.1
Table 3.10 Detached study management SOP classes.
3.1.9 Printing as an SCU
IMPAX provides Standard Conformance to the following DICOM V3.0 Print SOP Class as an SCU.
SOP Class SOP Class UID
Basic Film Session 1.2.840.10008.5.1.1.1
Basic Film Box 1.2.840.10008.5.1.1.2
Basic Grayscale Image Box 1.2.840.10008.5.1.1.4
Basic Color Image Box 1.2.840.10008.5.1.1.4.1
Basic Grayscale Print Management Meta 1.2.840.10008.5.1.1.9
Basic Annotation Box 1.2.840.10008.5.1.1.15
Basic Color Print Management Meta 1.2.840.10008.5.1.1.18
Presentation LUT 1.2.840.10008.5.1.1.23
Table 3.11 Print SOP classes.
MED/RDH/000702 Page 13 of 29
Document No. 000702, Revision 1.3
Healthcare 26 May, 2005
3.2 Association Establishment Policies
3.2.1 General
The following Application Context Name will be proposed and recognized by IMPAX:
DICOM 3.0 Application Context: 1.2.840.10008.3.1.1.1
IMPAX contains no limitations for maximum PDU size.
3.2.2 Number of Associations
The maximum number of simultaneous associations accepted by IMPAX is configurable at run time, based
on the system resources available. By default, the maximum number of associations is set at 32. There is
no inherent limit to the number of associations other than limits imposed by the computer operating system.
3.2.3 Asynchronous Nature
IMPAX allows a single outstanding operation on any association. Therefore, IMPAX does not support
asynchronous operations window negotiation, other than the default as specified by the DICOM specification.
3.2.4 Implementation Identifying Information
IMPAX will respond with the following implementation identifying parameters:
Implementation Class UID: 1.2.124.113532.1.1
Implementation Version Name: MITRA22JAN97
3.2.5 Called/Calling Titles
The default calling title that IMPAX will use is the host name of the computer. This parameter can be
configured via the GUI. IMPAX is configured to validate the Called Title of the requesting SCU during
association negotiation.
3.2.6 Association Initiation by Real World Activity
3.2.6.1 Real World Activity - Verification
3.2.6.1.1 Associated Real World Activity - Verification
IMPAX will issue Verification requests in response to UI mediated requests from the user to test the
validity of the DICOM connection.
3.2.6.1.2 Presentation Context Table - Verification
IMPAX requests the presentation contexts listed in Table 3.12.
SOP Class Transfer Syntax Role Extended Negotiation
All Table 3.3 All Table 3.1 SCU None
Table 3.12 Presentation contexts.
3.2.6.1.3 SOP Specific Conformance - Verification
IMPAX provides standard conformance to the DICOM Verification Service Class.
Page 14 of 29 MED/RDH/000702
Document No. 000702, Revision 1.3
26 May, 2005 Healthcare
3.2.6.2 Real World Activity - Modality Worklist Management
3.2.6.2.1 Associated Real World Activity - Modality Worklist Management
IMPAX will receive unsolicited Study-Scheduled N-EVENT-Reports. IMPAX will then request DIMSE-C
Modality Worklist - FINDs.
3.2.6.2.2 Presentation Context Table - Modality Worklist Management
IMPAX requests any of the Presentation Contexts listed in Table 3.13 for Modality Worklist Management.
SOP Class Transfer Syntax Role Extended Negotiation
Table 3.4 Table 3.1 SCU None
Table 3.13 Presentation contexts.
3.2.6.2.3 SOP Specific Conformance - Modality Worklist Management
IMPAX provides standard conformance to the DICOM Basic Worklist Management Service Class.
IMPAX supports all required matching key types:
Matching Key Types
SV Single valued match
WC Wild card match
SQ Sequence match
DR Date range match
Table 3.14 Matching Key Types.
IMPAX uses the following elements for this SOP class:
Module Attribute Name Tag Match Return
SOP Common Specific Character Set (0008,0005) 1C
Scheduled Procedure Step Sequence (0040,0100) SQ 1
>Scheduled Station AE Title (0040,0001) SV 1
>Scheduled Procedure Step Start Date (0040,0002) DR 1
>Scheduled Procedure Step Start Time (0040,0003) DR 1
Scheduled Procedure Step
>Modality (0008,0060) SV 1
Requested Procedure ID (0040,1001) 1
Requested Procedure Description (0032,1060) 1C
Study Instance UID (0020,000D) SV 1
Referenced Study Sequence (0008,1110) 2
>Referenced SOP Class UID (0008,1150) 1C
Requested Procedure
>Referenced SOP Instance UID (0008,1155) 1C
Accession Number (0008,0050) SV 2
Referring Physician.s Name (0008,0090) 2
Imaging Service Request
Reason for Imaging Service Request (0040,2001) 3
Patient Identification Patient Name (0010,0010) WC 1
Patient ID (0010,0020) SV 1
Patient Demographic Patient Birth Date (0010,0030) 2
Patient Sex (0010,0040) 2
Table 3.15 Modality worklist information model attributes.
3.2.6.3 Real World Activity - Storage
3.2.6.3.1 Associated Real World Activity - Storage
IMPAX will transmit images that have been sent to it previously, driven by user requests.
MED/RDH/000702 Page 15 of 29
Document No. 000702, Revision 1.3
Healthcare 26 May, 2005
3.2.6.3.2 Presentation Context Table - Storage
IMPAX may request any of the Presentation Contexts listed in Table 3.16 for Storage.
SOP Class Transfer Syntax Role Extended Negotiation
All Table 3. All Table 3.2 SCU None
Table 3.16 Presentation contexts for storage.
3.2.6.3.3 SOP Specific Conformance - Storage
IMPAX conforms to the DICOM Storage Service Class as an SCU.
3.2.6.4 Real World Activity - Storage Commitment
3.2.6.4.1 Associated Real World Activity - Storage Commitment
IMPAX stores images that are sent to it from an SCU. In some configurations (e.g. cache-only), IMPAX may
send images to another SCP (e.g. a PACS) for permanent storage. The request for storage commitment
may then be transmitted from IMPAX together with a list of references to one or more SOP instances. This
action is invoked through the DIMSE N-ACTION primitive. The following message is supported:
Request Storage Commitment - to request the safekeeping of a set of SOP instances.
3.2.6.4.2 Presentation Context Table . Storage Commitment
IMPAX requests the presentation contexts listed in Table 3.17.
SOP Class Transfer Syntax Role Extended Negotiation
All Table 3.8 All Table 3.1 SCU None
Table 3.17 Presentation contexts.
3.2.6.4.3 SOP Specific Conformance . Storage Commitment
IMPAX provides standard conformance to the DICOM Storage Commitment Service Class.
IMPAX supports the following elements for this SOP class as an SCU. The Transaction UID Attribute
(0008,1195) value generated by IMPAX uniquely identifies each Storage Commitment Request.
Action Type Name Action Type ID Attribute Name Tag
Transaction UID (0008,1195)
Referenced SOP Sequence (0008,1199)
>Referenced SOP Class UID (0008,1150)
>Referenced SOP Instance UID (0008,1155)
Referenced Study Component Sequence (0008,1111)
>Referenced SOP Class UID (0008,1150)
Request Storage Commitment 1
>Referenced SOP Instance UID (0008,1155)
Table 3.18 Storage commitment request . action information.
Subsequently, IMPAX expects N-EVENT-REPORT from the SCP. IMPAX returns an N-EVENT-REPORT
response primitive with one of the following status codes:
Service Status Further Meaning Protocol Codes Related Fields Description
Success Success 0000 Successful notification.
Table 3.19 Storage commitment status codes.
3.2.6.4.4 Transfer Syntax Selection Policies . Storage Commitment
IMPAX supports the Little Endian Implicit Transfer Syntax.
Page 16 of 29 MED/RDH/000702
Document No. 000702, Revision 1.3
26 May, 2005 Healthcare
3.2.6.5 Real World Activity - Find
3.2.6.5.1 Associated Real World Activity - Find
IMPAX will negotiate requests to an SCP.
3.2.6.5.2 Presentation Context Table - Find
IMPAX will initiate any of the Presentation Contexts listed in Table 3.20 for Query.
SOP Class Transfer Syntax Role Extended Negotiation
All Table 3.9 Find All Table 3.1 SCU See NOTE below
Table 3.20 Presentation contexts.
NOTE:
C-Find Extended Negotiation will be supported. IMPAX will respond with the information in Table 3.21.
Field Name Value Description of Field
Relational-queries 1 Relational queries supported
Table 3.21 Find extended negotiation.
3.2.6.5.3 SOP Specific Conformance - Find
SOP classes of the Query/Retrieve Service Class are implemented via the DIMSE C-FIND and C-MOVE
services as defined in Part 7 of the DICOM standard.
3.2.6.5.4 Presentation Context Acceptance Criterion - Find
IMPAX will initiate one Find Presentation Context per association request. Any one Abstract Syntax may
be specified more than once in an association request, if the Transfer Syntaxes differ between the
Presentation Contexts.
3.2.6.5.5 Transfer Syntax Selection Policies - Find
IMPAX supports the default transfer syntax of Implicit Little Endian.
3.2.6.5.6 SOP Specific Conformance - Find
IMPAX may request any mandatory search keys during a relational query.
The following four tables describe the search keys for the four levels of query that IMPAX requests.
Description Tag
Patient Name (0x0010,0x0010)
Patient ID (0x0010,0x0020)
Table 3.22 Patient level attributes.
Description Tag
Study Instance UID (0x0020,0x000D)
Study ID (0x0020,0x0010)
Study Date (0x0008,0x0020)
Study Time (0x0008,0x0010)
Accession Number (0x0008,0x0050)
Table 3.23 Study level attributes.
MED/RDH/000702 Page 17 of 29
Document No. 000702, Revision 1.3
Healthcare 26 May, 2005
Description Tag
Series Instance UID (0x0020,0x000E)
Series Number (0x0020,0x0011)
Modality (0x0008,0x0060)
Station Name (0x0008,0x1010)
Table 3.24 Series level attributes.
Description Tag
SOP Instance UID (0x0008,0x0018)
Image Number (0x0020,0x0013)
Table 3.25 Image level attributes.
IMPAX automatically adds a wildcard "*" to matching keys with a VR of PN. The user is not required
to add one manually.
The following matching keys are available from the User Interface within IMPAX during a relational
query: Patient_id, patient_name, accession_number, patient_location, referring physician, and modality.
A number of predefined time constraints are available in the User Interface. These include LAST
2 DAYS, LAST 7 DAYS, LAST 21 DAYS, etc. The ranges defined include the current day PLUS the
LAST 2 DAYS, etc.
No matching keys are available during a hierarchical query.
Within the application, the exact Patient ID has to be entered in the Patient_id field.
Within the application, IMPAX also has a facility to carryout extensive custom queries. These are not
DICOM queries and are to be used only when querying within the cluster.
3.2.6.6 Real World Activity - Move
3.2.6.6.1 Associated Real World Activity - Move
IMPAX will initiate retrieve requests to an SCP.
3.2.6.6.2 Presentation Context Table - Move
IMPAX will initiate any of the Presentation Contexts listed in Table 3.26 for Move.
SOP Class Transfer Syntax Role Extended Negotiation
All Table 3.9 Move Table 3.1 SCU None
Table 3.26 Presentation contexts.
3.2.6.6.3 SOP Specific Conformance - Move
IMPAX will try to establish an association with the move destination specified in the Move request. One or more
of the Presentation Contexts listed in the Store section of this document may be negotiated in this association.
3.2.6.6.4 Presentation Context Acceptance Criterion - Move
IMPAX will accept any number of Move Presentation Contexts per association request. Any one Abstract
Syntax may be specified more than once in an association request, if the Transfer Syntaxes differ
between the Presentation Contexts.
3.2.6.6.5 Transfer Syntax Selection Policies - Move
IMPAX supports the default transfer syntax of Implicit Little Endian.
Page 18 of 29 MED/RDH/000702
Document No. 000702, Revision 1.3
26 May, 2005 Healthcare
3.2.6.7 Real World Activity - Detached Study Management
3.2.6.7.1 Associated Real World Activity - Detached Study Management‘‘
IMPAX will receive DIMSE N-EVENT-REPORT. The following message is supported:
Study Scheduled - to signal that the study has been scheduled to occur.
3.2.6.7.2 Presentation Context Table - Detached Study Management
SOP Class Transfer Syntax Role Extended Negotiation
All Table 3.10 All Table 3.1 SCU None
Table 3.27 Presentation contexts.
3.2.6.7.3 SOP Specific Conformance - Detached Study Management
IMPAX provides standard conformance to the DICOM Detached Study Management Service Class.
IMPAX supports the following elements for this SOP class:
Event Type Name Attribute Name Tag
Specific Character Set (0008,0005)
Referenced Patient Sequence (0008,1120)
>Referenced SOP Class UID (0008,1150)
>Referenced SOP Instance UID (0008,1155)
Referenced Visit Sequence (0008,1125)
>Referenced SOP Class UID (0008,1150)
>Referenced SOP Instance UID (0008,1155)
Scheduled Study Start Date (0032,1000)
Scheduled Study Start Time (0032,1001)
Scheduled Study Location (0032,1020)
Requested Procedure Description (0032,1060)
Requested Procedure Code Sequence (0032,1064)
>Code Value (0008,0100)
>Coding Scheme Designator (0008,0102)
Study Scheduled
>Code Meaning (0008,0104)
Table 3.28 Detached study management object N-Event-report attributes.
IMPAX returns one of the following status codes:
Service Status Further Meaning Protocol Codes Related Fields Description
Success Success 0000 Operation performed properly.
Table 3.29 Detached study management status codes.
3.2.6.7.4 Presentation Context Initiate Criterion - Detached Study Management
IMPAX will always issue a Presentation Context for the Detached Study Management SOP Class.
3.2.6.7.5 Transfer Syntax Selection Policies - Detached Study Management
IMPAX supports only the Little Endian Implicit Transfer Syntax.
3.2.6.7.6 SOP Specific Conformance - Move
IMPAX provides standard conformance as an SCU.
3.2.6.8 Real World Activity - Printing
IMPAX provides standard conformance as an SCU.
MED/RDH/000702 Page 19 of 29
Document No. 000702, Revision 1.3
Healthcare 26 May, 2005
3.2.6.8.1 Associated Real World Activity - Printing
IMPAX issues print requests based on user interface mediated requests.
3.2.6.8.2 Presentation Context Table - Printing
IMPAX may request any of the Presentation Contexts listed in Table 3.30.
SOP Class Transfer Syntax Role Extended Negotiation
Table 3.11 Table 3.1 SCU None
Table 3.30 Presentation contexts.
3.2.6.8.3 SOP Specific Conformance - Printing
IMPAX provides standard conformance to the DICOM Print Service Classes by supporting a number of
distinct Service classes described below.
3.2.6.8.3.1 SOP Specific Conformance to Basic Film Session SOP Class
IMPAX requests the following attributes of the Basic Film Session SOP Class. Values and ranges are
configured to match the capabilities of the printer, and the preferences of the particular user.
Attribute Name Tag Possible Values
Number of copies (2000,0010) 1 . 99
Print Priority (2000,0020) MED
Medium Type (2000,0030) BLUE FILM, CLEAR FILM, PAPER (See Table 3.37and Table 3.38)
Film Destination (2000,0040) MAGAZINE, PROCESSOR, BIN_i1 (See Table 3.37and Table 3.38)
Film Session Label (2000,0050) Always blank
Table 3.31 Attributes for a Basic Film Session.
3.2.6.8.3.2 SOP Specific Conformance to Basic Film Box SOP Class
IMPAX requests the following attributes of the Basic Film Box SOP Class. Values and ranges are
configured to match the capabilities of the printer, and the preferences of the particular user. When
images are positioned on a film box with empty boxes in between the images, IMPAX will ignore these
empty film boxes and print them immediately beside one another.
Attribute name Tag Possible Values
Image Display Format (2010,0010) STANDARD\C,R,2 SLIDE, SUPERSLIDE (See Table 3.37and Table 3.38)
Referenced Film Session Sequence (2010,0500)
Referenced Basic Image Box Sequence (2010,0510)
Film Orientation (2010,0040) LANDSCAPE, PORTRAIT
Film Size ID (2010,0050) See Table 3.37and Table 3.38
Magnification Type (2010,0060) See Table 3.37and Table 3.38
Max Density (2010,0130) See Table 3.37and Table 3.38
Configuration Information (2010,0150) CS_TABLE=NN\PERCEPTION_LUT=XXX3
Annotation Display Format ID (2010,0030) ANNOTATION
Border Density (2010,0100) See Table 3.37and Table 3.38
Empty Image Display (2010,0110) See Table 3.37and Table 3.38
Min. Density (2010,0120) See Table 3.37and Table 3.38
Trim (2010,0140) YES, NO
Table 3.32 Attributes for a Basic Film Box.
1I Represents the bin number. It may have values 1 . 30 (see Table 3.38).
2 Film contains equal size rectangular image boxes with R rows of image boxes and C columns of image boxes. R and C are integers.
3 NN represents the color separation table value; XXX represents the Look Up Table value. NN and XXX are integers. Please
refer to Table 3.37 and Table 3.38 for acceptable values.
Page 20 of 29 MED/RDH/000702
Document No. 000702, Revision 1.3
26 May, 2005 Healthcare
3.2.6.8.3.3 SOP Specific Conformance to Basic Grayscale Image Box SOP Class
The following attributes are requested. Values and ranges depend on the characteristics of the images
stored in IMPAX.
Attribute name Tag Possible Values
Image Position (2020,0010) 1,2,.
Preformatted Grayscale Image Sequence (2020,0110)
>Samples Per Pixel (0028,0002)
>Photometric Interpretation (0028,0004) MONOCHROME1, MONOCHROME2
>Rows (0028,0010) >0
>Columns (0028,0011) >0
>Pixel Aspect Ratio (0028,0034) 1
>Bits Allocated (0028,0100) 8, 16
>Bits Stored (0028,0101) 8, 12
>High Bit (0028,0102) 7, 11
>Pixel Representation (0028,0103) 0
>Pixel Data (7FE0,0010)
Polarity (2020,0020) REVERSE, NORMAL
Requested Image Size (2020,0030) Length in mm of image rows
Magnification Type (2010,0060) See Table 3.37and Table 3.38
Smoothing Type (2010,0080) See Table 3.37and Table 3.38
Table 3.33 Attributes for a Basic Grayscale Image Box.
3.2.6.8.3.4 SOP Specific Conformance to Basic Color Image Box SOP Class
The following attributes are requested. Values and ranges depend on the characteristics of the images
stored in IMPAX.
Attribute name Tag Possible Values
Image Position (2020,0010) 1,2,.
Preformatted Color Image Sequence (2020,0111)
>Samples Per Pixel (0028,0002)
>Photometric Interpretation (0028,0004) PALETTE COLOR, RGB, YBR_FULL, YBR_FULL_422
>Planar Configuration (0028,0006)
>Rows (0028,0010) >0
>Columns (0028,0011) >0
>Pixel Aspect Ratio (0028,0034)
>Bits Allocated (0028,0100) 8, 16
>Bits Stored (0028,0101) 8, 12
>High Bit (0028,0102) 7, 11
>Pixel Representation (0028,0103) 0
>Pixel Data (7FE0,0010)
Polarity (2020,0020) REVERSE, NORMAL
Requested Image Size (2020,0030) Length in mm of image rows
Magnification Type (2010,0060) See Table 3.37and Table 3.38
Smoothing Type (2010,0080) See Table 3.37and Table 3.38
Table 3.34 Attributes for a Basic Color Image Box.
3.2.6.8.3.5 SOP Specific Conformance to Basic Annotation Box SOP Class
The following attributes are requested.
Attribute Name Tag Possible Values
Annotation Position (2030,0010)
Text String (2030,0020)
Table 3.35 Attributes for an Annotation Box.
MED/RDH/000702 Page 21 of 29
Document No. 000702, Revision 1.3
Healthcare 26 May, 2005
3.2.6.8.3.6 SOP Specific Conformance to Printer SOP Class
The following attributes are requested.
Attribute Name Tag Possible Values
Printer Status (2010,0010) NORMAL, WARNING, FAILURE
Printer Status Info (2110,0020) Additional info when Printer Status is WARNING or FAILURE
Printer Name (2110,0030) User defined name identifying the printer.
Manufacturer (0008,0070) Manufacturer.s model number of the printer
Manufacturer Model Name (0008,1090) Manufacturer.s model number of the printer
Table 3.36 Attributes for Printer SOP Class.
3.2.6.8.4 Agfa Printer Type Options
Left out from this document for the sake of simplicity
…
3.2.6.8.5 Other Printer Type Options
Left out from this document for the sake of simplicity
…
3.2.7 Association Acceptance Policy
3.2.7.1 Real World Activity - Verification
3.2.7.1.1 Associated Real World Activity - Verification
IMPAX will respond to Verification requests to provide an SCU with the ability to determine if IMPAX is
receiving DICOM requests.
3.2.7.1.2 Presentation Context Table - Verification
IMPAX will accept any of the Presentation Contexts listed in Table 3.39 for Verification.
SOP Class Transfer Syntax Role Extended Negotiation
All Table 3.3 All Table 3.1 SCP None
Table 3.39 Presentation contexts.
3.2.7.1.3 SOP Specific Conformance - Verification
IMPAX provides standard conformance to the DICOM Verification Service Class. IMPAX returns one of
the following status codes:
Service Status Further Meaning Protocol Codes Related Fields Description
Success Success 0000 Operation performed properly.
Table 3.40 Verification status codes.
3.2.7.1.4 Presentation Context Acceptance Criterion - Verification
IMPAX will always accept a Presentation Context for the Verification SOP Class with the default DICOM
transfer syntax listed in Table 3.1.
3.2.7.1.5 Transfer Syntax Selection Policies - Verification
Since no DICOM data object is associated with a Verification command, only the default DICOM transfer
syntax is required/supported.
3.2.7.2 Real World Activity - Storage
3.2.7.2.1 Associated Real World Activity - Storage
IMPAX will store images that are sent to it from an SCU. All images received by IMPAX can be retrieved
at a later time from IMPAX; however, the rate of return of the images will vary depending the state of the
images. The images can be in one of three states:
Online: The image is immediately available.
Nearline: The image is automatically available; however, there may be a small delay in the retrieval time.
Offline The image requires manual assistance to become online. The retrieval request will return
a failure code.
Page 24 of 29 MED/RDH/000702
Document No. 000702, Revision 1.3
26 May, 2005 Healthcare
3.2.7.2.2 Presentation Context Table - Storage
IMPAX will accept any of the Presentation Contexts listed in Table 3.41 for Storage.
SOP Class Transfer Syntax Role Extended Negotiation
All from Table 3. Table 3.2 SCP See NOTE below
Table 3.41 Presentation contexts.
NOTE:
Storage Extended Negotiation will be supported. IMPAX will respond with the information in Table 3.42.
Field Name Value Description of Field
Level of Support 2 Level 2 (FULL) SCP
Element Coercion 0 Does not coerce any element
Table 3.42 Storage extended negotiation.
3.2.7.2.3 SOP Specific Conformance - Storage
IMPAX conforms to the DICOM Storage Service Class at Level 2 (Full). No elements are discarded or
coerced by IMPAX. In the event of a successful C-STORE operation, the image has been written to
internal storage, and can be retrieved at any later time.
IMPAX returns one of the following status codes:
Service
Status Further Meaning Protocol
Codes Description
Out of resources A700 Indicates that there was not enough storage space to store the image.
Recovery from this condition is left to the administrative functions.
Refused
SOP Class not supported A800 Indicates that the SOP Class of the Image in the C-STORE operation did
not match the Abstract Syntax negotiated for the Presentation Context.
Data set does not match SOP
Class
A900 Indicates that the Data Set does not encode an instance of the SOP
Class specified.
Failed C000 The operation was not successful.
Unable to register object, study
locked; no new objects allowed
C005 Indicates that no new objects can be added to this study because it
has been locked.
Error
Cannot understand C005 Indicates that the Data Set cannot be parsed into elements.
Data set does not match SOP
Class
B007 Indicates that the Data Set does not match the SOP Class, but that the
image was stored anyway.
Warning
Duplicate SOP Instance UID D000 Indicates that the SOP Instance UID of the specified image is already
stored in the database.
Success Success 0000 Operation performed properly.
Table 3.43 C-STORE status codes.
3.2.7.2.4 Presentation Context Acceptance Criterion - Storage
IMPAX will accept any number of Storage Presentation Contexts per association request. Any one
Abstract Syntax may be specified more than once in an association request, if the Transfer Syntaxes
differ between the Presentation Contexts.
3.2.7.2.5 Transfer Syntax Selection Policies - Storage
IMPAX supports all transfer syntaxes listed in Table 3.2. By default, IMPAX sends the IOD using the
transfer syntax that was used when the image was originally stored.
If the C-STORE SCP supports a limited number of Transfer Syntaxes, IMPAX can be configured on a perdestination
basis to convert the IOD from the original transfer syntax to Implicit Little Endian.
MED/RDH/000702 Page 25 of 29
Document No. 000702, Revision 1.3
Healthcare 26 May, 2005
3.2.7.3 Real World Activity - Storage Commitment
3.2.7.3.1 Associated Real World Activity - Storage Commitment
IMPAX stores images that are sent to it from an SCU. The request for storage commitment may then be
transmitted to IMPAX together with a list of references to one or more SOP instances. IMPAX will receive
and respond to DIMSE N-ACTION. The following message is supported:
Request Storage Commitment - to request the safekeeping of a set of SOP instances.
3.2.7.3.2 Presentation Context Table . Storage Commitment
SOP Class Transfer Syntax Role Extended Negotiation
All Table 3.8 All Table 3.1 SCP None
Table 3.44 Presentation contexts.
3.2.7.3.3 SOP Specific Conformance . Storage Commitment
IMPAX supports the following elements for this SOP class as an SCP:
Action Type Name Action Type ID Attribute Name Tag
Transaction UID (0008,1195)
Referenced SOP Sequence (0008,1199)
>Referenced SOP Class UID (0008,1150)
>Referenced SOP Instance UID (0008,1155)
Referenced Study Component Sequence (0008,1111)
>Referenced SOP Class UID (0008,1150)
Request Storage Commitment 1
>Referenced SOP Instance UID (0008,1155)
Table 3.45 Storage commitment request . action information.
3.2.7.3.4 Storage Commitment Result
If IMPAX determines that it has successfully completed storage commitment, IMPAX issues an N-EVENTREPORT
to the SCU including references to the successfully stored SOP Instances contained in the N-ACTION.
In the event that IMPAX cannot commit to storing SOP Instances, IMPAX issues an N-EVENT-REPORT
to the SCU including references to the failed SOP Instances contained in the N-ACTION.
The N-EVENT-REPORT contains the Transaction UID value contained in the initiating N-ACTION. The
N-EVENT-REPORT is sent on a separate association from the N-ACTION operation.
IMPAX supports the Event Information as specified in Table 3.46.
Action Type Name Event Type ID Attribute Name Tag
Transaction UID (0008,1195)
Referenced SOP Sequence (0008,1199)
>Referenced SOP Class UID (0008,1150)
>Referenced SOP Instance UID (0008,1155)
Referenced Study Component Sequence (0008,1111)
>Referenced SOP Class UID (0008,1150)
Storage Commitment Request
Successful
1
>Referenced SOP Instance UID (0008,1155)
Transaction UID (0008,1195)
Referenced SOP Sequence (0008,1199)
>Referenced SOP Class UID (0008,1150)
>Referenced SOP Instance UID (0008,1155)
Failed SOP Sequence (0008,1198)
>Referenced SOP Class UID (0008,1150)
>Referenced SOP Instance UID (0008,1155)
Storage Commitment Request
Complete . Failure Exist
2
>Failure Reason (0008,1197)
Table 3.46 Storage commitment result . event information.
Page 26 of 29 MED/RDH/000702
Document No. 000702, Revision 1.3
26 May, 2005 Healthcare
3.2.7.3.5 Operations . Storage Commitment
If configured with off-line storage, IMPAX commits to permanently storing a SOP Instance, unless it is
manually deleted from IMPAX. Off-line storage capacity varies based on an individual IMPAX’s configuration.
In a cache-only configuration, IMPAX commits to storing a SOP Instance as long as there is available
disk space. In this configuration, IMPAX may delete SOP Instances based on a user request or based on
autopilot cache management rules.
SOP Instances can be retrieved from IMPAX via C-FIND (see Section 3.2.7.4) and C-MOVE (see Section 3.2.7.5).
3.2.7.3.6 Transfer Syntax Selection Policies . Storage Commitment
IMPAX supports only the Little Endian Implicit Transfer Syntax.
3.2.7.4 Real World Activity - Find
3.2.7.4.1 Associated Real World Activity - Find
IMPAX will respond to query requests that are sent to it from an SCU.
3.2.7.4.2 Presentation Context Table - Find
IMPAX will accept any of the Presentation Contexts listed in Table 3.47 for Query.
SOP Class Transfer Syntax Role Extended Negotiation
All Table 3.9 Find All Table 3.1 SCP See NOTE below
Table 3.47 Presentation contexts.
NOTE:
C-Find Extended Negotiation will be supported. IMPAX will respond with the information in Table 3.48.
Field Name Value Description of Field
Relational-queries 1 Relational queries supported
Table 3.48 Find extended negotiation.
3.2.7.4.3 SOP Specific Conformance - Find
SOP classes of the Query/Retrieve Service Class are implemented via the DIMSE C-FIND and C-MOVE
services as defined in Part 7 of the DICOM standard.
IMPAX supports hierarchical queries. IMPAX supports relational queries. IMPAX, by default, supports all
mandatory search keys.
Description Tag
Patient Name (0x0010, 0x0010)
Patient ID (0x0010, 0x0020)
Table 3.49 Patient level attributes.
Description Tag
Study Instance UID (0x0020, 0x000D)
Study ID (0x0020, 0x0010)
Study Date (0x0008, 0x0020)
Study Time (0x0008, 0x0010)
Accession Number (0x0008, 0x0050)
Station Name (0x0008, 0x1010)
Study Description (0x0008, 0x1030)
Table 3.50 Study level attributes.
MED/RDH/000702 Page 27 of 29
Document No. 000702, Revision 1.3
Healthcare 26 May, 2005
Description Tag
Series Instance UID (0x0020, 0x000E)
Series Number (0x0020, 0x0011)
Modality (0x0008, 0x0060)
Series Description (0x0008, 0x103e)
Table 3.51 Series level attributes.
Description Tag
SOP Instance UID (0x0008, 0x0018)
Image Number (0x0020, 0x0013)
Table 3.52 Image level attributes.
IMPAX returns one of the following status codes to a C-FIND request:
Service
Status Further Meaning Protocol
Codes
Related
Fields Description
Refused Out of Resources A700
Identifier does not match
SOP Class
A900 The specified identifier contains a request that
does not match the specified SOP Class.
Failed
Unable to process C001 For some reason (database off-line?) we cannot
process this request at this time.
Cancel Matching terminated due to
Cancel Request
FE00 The original requester canceled this operation.
Pending FF00 All Optional Keys are supported in the same
manner as Required Keys.
Pending
Pending FF01 The matching operation is continuing. Warning that
one or more Optional Keys were not supported in
the same manner as Required Keys.
Success Success 0000 Operation performed properly.
Table 3.53 C-FIND status codes.
3.2.7.4.4 Presentation Context Acceptance Criterion - Find
IMPAX will accept any number of Find Presentation Contexts per association request. Any one Abstract
Syntax may be specified more than once in an association request, if the Transfer Syntaxes differ
between the Presentation Contexts.
3.2.7.4.5 Transfer Syntax Selection Policies - Find
IMPAX currently only supports the default transfer syntax of Implicit Little Endian.
3.2.7.5 Real World Activity - Move
3.2.7.5.1 Associated Real World Activity - Move
IMPAX will respond to retrieve requests that are sent to it from an SCU.
3.2.7.5.2 Presentation Context Table - Move
IMPAX will accept any of the Presentation Contexts listed in Table 3.54 for Query.
SOP Class Transfer Syntax Role Extended Negotiation
All Table 3.9 Move Table 3.1 SCP None
Table 3.54 Presentation contexts.
Page 28 of 29 MED/RDH/000702
Document No. 000702, Revision 1.3
26 May, 2005 Healthcare
3.2.7.5.3 SOP Specific Conformance - Move
IMPAX will try to establish an association with the Move destination specified in the Move request. One or
more of the Presentation Contexts listed in the Store section of this document (refer to Section 3.2.6.3.2),
may be negotiated in this association.
IMPAX returns one of the following status codes to a C-MOVE request:
Service
Status Further Meaning Protocol
Codes Description
Out of Resources A701 Unable to Refused calculate number of matches.
Out of Resources A702 Unable to perform storage of images to move destination.
Move destination unknown A801 The destination of this move request is unknown.
Identifier does not match
SOP Class
A900 The specified identifier contains a request that does not match
the specified SOP Class.
Failed
Unable to process C002 Indicates that IMPAX cannot process this request at this time.
Cancel Storage terminated due to
Cancel Request
FE00 The original requester canceled this operation.
Warning Warning B000 Storage complete with one or more failures.
Pending Pending FF00 The storage operation is continuing.
Pending for a long time FF02 This operation is expected to require a long period of time to
complete. The SCU may break the association at any time, but
the operation will continue to completion.
Success Success 0000 Operation performed properly.
Table 3.55 C-MOVE status codes.
3.2.7.5.4 Presentation Context Acceptance Criterion - Move
IMPAX will accept any number of Move Presentation Contexts per association request. Any one Abstract
Syntax may be specified more than once in an association request, if the Transfer Syntaxes differ
between the Presentation Contexts.
3.2.7.5.5 Transfer Syntax Selection Policies - Move
By default, IMPAX sends the IOD using the transfer syntax that was used when the image was originally
stored.
If the C-MOVE destination supports a limited number of Transfer Syntaxes, IMPAX can be configured on
a per-destination basis to convert the IOD from the original transfer syntax to Implicit Little Endian.
4 COMMUNICATIONS PROFILES
IMPAX provides DICOM V3.0 TCP/IP Network Communication Support as defined in Part 8 of the
DICOM Standard.
4.1 TCP/IP Stack
IMPAX inherits its TCP/IP stack from the computer system upon which it executes.
4.1.1 Physical Media Support
IMPAX is indifferent to the physical medium over which TCP/IP executes; it inherits the medium from the
computer system upon which it executes.
5 EXTENSIONS / SPECIALIZATIONS / PRIVATIZATIONS
Not applicable.
MED/RDH/000702 Page 29 of 29
Document No. 000702, Revision 1.3
Healthcare 26 May, 2005
6 CONFIGURATION
IMPAX obtains configuration information from the following sources:
Mapping from Application Entity Title to Presentation Address is provided by the database and
configured with the Service Tools program. Along with this mapping, the database stores those AE
Titles that are allowed to communicate with IMPAX.
Hardcopy Parameters must be configured for installed printers from the IMPAX Printer Setup utility.
7 SUPPORT FOR EXTENDED CHARACTER SETS
IMPAX is known to support the following character sets:
ISO-IR 6 (default): Basic G0 Set
ISO-IR 100: Latin Alphabet No. 1
8 ACRONYMS AND ABBREVIATIONS
The following acronyms and abbreviations are used in this document:
ACR American College of Radiology
AE Application Entity
DICOM Digital Imaging and Communications in Medicine
NEMA National Electrical Manufacturers Association
PDU Protocol Data Unit
SCP Service Class Provider
SCU Service Class User
SCP Service Class Provider
SOP Service-Object Pair
TCP/IP Transmission Control Protocol/Internet Protoco
UID Unique IdentifierHEALTHCARE
eRAD PACS Dicom Conformance Statement
Version 6.0
Page ii 12/11/2009
March 27, 2008
File: CS_eRADPACS.doc
eRAD/Image Medical
9 Pilgrim Road
Greenville, SC 29607
www.eradimagemedical.com
© Copyright 1999 - 2007. All rights reserved.
eRAD, Inc. copyrights this document and the associated software. Neither this document nor the associated software may be
reproduced without the express written consent of eRAD, Inc.
This document may include technical inaccuracies and/or typographical errors. The information herein changes periodically to
address these issues and incorporates these changes into new editions of this document. eRAD, Inc. may make improvements
and/or changes to the product(s) and/or the program(s) described in this document at any time.
The following copyrights and trademarks are observed: eRAD PACS, PracticeBuilder 1-2-3, and ImageMedical.com are
registered trademarks of Image Medical Corporation.
Revision Table
Revision Date Author Comments
1.0 26-Oct-99 JKC Compiled drafts into final draft for PracticeBuilder 0.85
1.1 30-Aug-00 JKC Added report objects
1.2 6-Feb-01 JKC Added printing, additional storage SOP classes
1.3 16-Nov-01 JKC Added query/retrieve SOP classes
1.4 12-Jul-02 JKC Added MWL, study mgmt, report mgmt SOP classes and security support.
1.5 3-Apr-03 JKC Added Structured Report storage SOP classes
1.6 13-Jan-04 JKC Added JPEG transfer syntaxes to presentation context tables
1.7 12-Aug-04 JKC Updated for PracticeBuilder 5.0. Added Storage Commitment SCP
1.8 21-Sep-04 JKC Updated Storage SOP class transfer syntaxes
1.9 28-Sep-05 JKC Updated supported transfer syntaxes
1.10 6-Jan-06 JKC Change name to eRAD PACS, updated implementation UID and version
1.11 15-Aug-06 JKC Modified presentation state conformance
1.12 6-Sep-06 JKC Corrected error in private SOP class abstract syntax in table 4.1.2.1.2
1.13 12-Apr-07 JKC Added new SOP classes supported in eRAD PACS v6.0 and removed
support for retired study management SOP classes.
eRAD PACS
DICOM Conformance Statement
Page iii 12/11/2009
CONTENTS
INTRODUCTION ................................................................................................................................. 1
1 - IMPLEMENTATION MODEL .......................................................................................................... 1
1.1 APPLICATION DATA FLOW DIAGRAM ............................................................................................... 1
1.2 FUNCTIONAL DEFINITIONS OF AE ................................................................................................... 1
1.3 SEQUENCING OF REAL WORD ACTIVITIES ....................................................................................... 3
2 - AE SPECIFICATIONS .................................................................................................................... 3
2.1 STORESCP - SPECIFICATION ....................................................................................................... 3
2.1.1 Association Establishment .................................................................................................. 5
2.1.1.1 General ........................................................................................................................ 5
2.1.1.2 Number of Associations ............................................................................................... 5
2.1.1.3 Asynchronous Nature .................................................................................................. 5
2.1.1.4 Implementation Identifying Information ........................................................................ 5
2.1.2 Association Initiation ........................................................................................................... 5
2.1.3 Association Acceptance ...................................................................................................... 5
2.1.3.1 Remote System Request - Verification ........................................................................ 5
2.1.3.2 Remote System Request - Storage ............................................................................. 6
2.2 SENDSCU - SPECIFICATION ....................................................................................................... 10
2.2.1 Association Establishment ................................................................................................ 10
2.2.1.1 General ...................................................................................................................... 10
2.2.1.2 Number of Associations ............................................................................................. 10
2.2.1.3 Asynchronous Nature ................................................................................................ 10
2.2.1.4 Implementation Identifying Information ...................................................................... 10
2.2.2 Association Initiation ......................................................................................................... 10
2.2.2.2 eRAD PACS Request – Send Images ....................................................................... 10
2.2.2.3 eRAD PACS Request – Send Reports ...................................................................... 11
2.2.3 Association Acceptance .................................................................................................... 12
2.3 PRINTSCU - SPECIFICATION ...................................................................................................... 12
2.3.1 Association Establishment ................................................................................................ 12
2.3.1.1 General ...................................................................................................................... 12
2.3.1.2 Number of Associations ............................................................................................. 12
2.3.1.3 Asynchronous Nature ................................................................................................ 12
2.2.1.4 Implementation Identifying Information ...................................................................... 12
2.3.2 Association Initiation ......................................................................................................... 12
2.3.2.1 eRAD PACS Request - Print ...................................................................................... 12
2.3.3 Association Acceptance .................................................................................................... 13
2.4 QRAE - SPECIFICATION .............................................................................................................. 13
2.4.1 Association Establishment ................................................................................................ 13
2.4.1.1 General ...................................................................................................................... 13
2.4.1.2 Number of Associations ............................................................................................. 13
2.4.1.3 Asynchronous Nature ................................................................................................ 13
2.4.1.4 Implementation Identifying Information ...................................................................... 13
2.4.2 Association Initiation ......................................................................................................... 13
2.4.2.1 eRAD PACS Request - Find ...................................................................................... 14
2.4.2.2 eRAD PACS Request - Move .................................................................................... 15
2.4.3 Association Acceptance .................................................................................................... 15
2.4.3.1 Remote System Request - Find ................................................................................. 15
2.4.3.2 Remote System Request - Move ............................................................................... 16
2.5 MWLAE - SPECIFICATION ........................................................................................................... 17
2.5.1 Association Establishment ................................................................................................ 17
2.5.1.1 General ...................................................................................................................... 17
2.5.1.2 Number of Associations ............................................................................................. 17
2.5.1.3 Asynchronous Nature ................................................................................................ 17
2.5.1.4 Implementation Identifying Information ...................................................................... 17
2.5.2 Association Initiation ......................................................................................................... 17
2.5.2.1 eRAD PACS Request – Get Worklist Item ................................................................. 17
2.5.3 Association Acceptance .................................................................................................... 19
eRAD PACS
DICOM Conformance Statement
Page iv 12/11/2009
2.5.3.1 Remote System Request – Request Worklist Items ................................................... 19
2.5.3.2 Remote System Request – Update Procedure Step .................................................. 20
2.6 COMMITSCP - SPECIFICATION .................................................................................................. 21
2.6.1 Association Establishment ................................................................................................ 21
2.6.1.1 General ...................................................................................................................... 21
2.6.1.2 Number of Associations ............................................................................................. 21
2.6.1.3 Asynchronous Nature ................................................................................................ 22
2.6.1.4 Implementation Identifying Information ...................................................................... 22
2.6.2 Association Initiation ......................................................................................................... 22
2.6.2.1 eRAD PACS Request – Acknowledge Commit .......................................................... 22
2.6.3 Association Acceptance .................................................................................................... 23
2.6.3.1 Remote System Request – Commit ........................................................................... 23
3 - COMMUNICATION PROFILES .................................................................................................... 23
3.1 SUPPORTED COMMUNICATION STACKS ........................................................................................ 23
3.2 TCP/IP STACK ........................................................................................................................... 23
3.2.1 Physical Media Support .................................................................................................... 23
4 - EXTENSIONS/SPECIALIZATIONS/PRIVATIZATIONS ................................................................ 23
4.1 ERAD PACS REPORT PRIVATE SOP CLASS SPECIFICATION ......................................................... 23
4.1.1 Association Establishment ................................................................................................ 23
4.1.1.1 General ...................................................................................................................... 23
4.1.1.2 Number of Associations ............................................................................................. 23
4.1.1.3 Implementation Identifying Information ...................................................................... 24
4.1.2 Association Initiation ........................................................................................................ 24
4.1.2.1 eRAD PACS Request – Send a Report .................................................................... 24
4.1.3 Association Acceptance ................................................................................................ 24
4.1.3.1 Remote System Request – Store Report ................................................................... 25
5 - CONFIGURATION ........................................................................................................................ 25
5.1 AE TITLE/PRESENTATION ADDRESS MAPPING .............................................................................. 25
5.2 CONFIGURABLE PARAMETERS ..................................................................................................... 25
6 - SUPPORT OF EXTENDED CHARACTER SETS ......................................................................... 25
7 – CODES AND CONTROLLED TERMINOLOGY ........................................................................... 26
8 – SECURITY PROFILES ................................................................................................................ 26
eRAD PACS
DICOM Conformance Statement
Page 1 12/11/2009
INTRODUCTION
This Document provides the DICOM conformance statement for the eRAD PACS version 6.0
implementation of the DICOM standard.
1 - IMPLEMENTATION MODEL
eRAD PACS is a multi-modality storage server with viewing and processing features. It uses the
DICOM protocol to provide the following services:
• Receive images and structure reports sent by remote stations
• Send images and structured reports to remote stations
• Print images to a remote printer
• Query remote entities and initiate retrieval from those entities
• Accept queries from remote entities and initiate image transfers as directed from those entities
• Issue and accept verification messages
• Request scheduled worklist from the RIS
• Accept queries from modalities for scheduled procedure information
• Receive procedure step updates from modalities
1.1 Application Data Flow Diagram
Figure 1.1-1 graphically depicts the application data flow diagram. The eRAD PACS system provides
DICOM services using the following Application Entities:
• STORESCP – This AE is a daemon process that implements a Service Class Provider (SCP)
for the Storage service class. It also supports the Verification service class as an SCP.
• SENDSCU – This AE is a Service Class User (SCU) for the Storage service class.
• PRINTSCU – This AE is a SCU for the Print Management service class.
• QRAE – This AE is both a SCU (QRSCU) and a SCP (QRSCP) of the Query/Retrieve service
class.
• MWLAE – This AE is both a SCU (MWLSCU) and a SCP (MWLSCP) of the Modality Worklist
Management service class, and an SCP (MPPSSCP) of the Modality Performed
Procedure Step service class.
• COMMITSCP – This AE is a Service Class Provider for the Storage Commitment service
class.
1.2 Functional Definitions of AE
STORESCP waits for a remote application entity to connect to the presentation address configured for
its application entity. The TCP/IP port is defined in its control script (default 104). When the other
application connects, STORESCP verifies that it is a DICOM application entity capable of supporting
its SOP classes. It can receive images and structure reports conforming to the Storage Service Class
and verification requests conforming to the Verification Service Class. STORESCP stores received
images and reports in files, and the corresponding demographic information (patient, study, series
and image details) in the internal database.
SENDSCU is the process that sends image and report objects stored on the local disk and resident in
the database to other DICOM AEs. The objects transmitted by SENDSCU are identical to the stored
object, meaning SENDSCU does not alter it or its attributes in any way. The DICOM address
information SENDSCU uses for connecting to a remote AE is defined in the control scripts.
PRINTSCU is the process that sends objects stored on the local disk and resident in the database to
print AEs for printing. Some of the print parameters are defined in the control scripts. The user
defines the remaining information in the print session at the time the system initiates the print request.
The DICOM address information PRINTSCU uses for connecting to a remote AE is defined in the
control scripts.
eRAD PACS
DICOM Conformance Statement
Page 2 12/11/2009
QRAE consists of a service class user (QRSCU) and a service class provider (QRSCP). QRSCU is
the process that sends query and move requests to other DICOM AEs. The user defines the
parameters of the query requests at the time the system initiates the query request. The user selects
one or more objects to move before initiating a move request. The DICOM address information
QRSCU uses for connecting to a remote AE, whether it is a query provider or a move destination, is
defined in the control scripts. QRSCP waits for a remote application entity to connect to it and then
services the query and move requests. QRSCP uses the query parameters in the request and
compares them to the information in the database. It then returns the matches to the remote AE in a
Image
and report
stored on
disk
STORESCP
Remote AE
requests
verification
Remote AE
sends
image or
report
Figure 1.1-1 Application Data Flow Diagram
DICOM
Remote AE
prints
images
Remote AE
queries
database
Remote AE
receives
image or
SENDSCU report
PRINTSCU
QRSCU
User or
system
requests
operation
Remote AE
queries DB
or requests
a study
Search
the
database
QRSCP
Request
list of
scheduled
exams
MWLSCU
Remote AE
queries
database &
returns list
Return list of
scheduled
exams
MWLSCP
Remote AE
requests list of
scheduled
exams
Accept
ownership of
objects
COMMITSCP
Remote AE
requests to
transfer
ownership
Update
order and
study
information
MPPSSCP
Remote AE
completes a
procedure
step
eRAD PACS
DICOM Conformance Statement
Page 3 12/11/2009
query response. When QRSCP receives a move request, it verifies the requested destination and the
existence of the requested object(s) and then sends them to SENDSCU for transmission to the
destination AE.
MWLAE consists of a service class user (MWLSCU) and two service class providers (MWLSCP,
MPPSSCP). MWLSCU requests the list of scheduled exams and patient demographic information for
use in eRAD PACS. When enabled, MWLSCU periodically issues a query request to a remote AE.
The response messages are parsed and inserted into the worklist as scheduled exams. The patient
demographics in the response messages are used to verify the demographic information contained in
the image objects. MWLSCP accepts query requests from remote applications, particularly
modalities, which are looking for patient demographic information for scheduled exams. MWLSCP
returns to the requesting AE the list of scheduled exams that match the query parameters. MPPSSCP
creates and maintains procedure step information sent by an AE, usually an imaging modality.
COMMITSCP is a process that accepts ownership of some composite objects when requested to by a
remote AE. The affected objects were transmitted to and acknowledged by STORESCP prior to
COMMITSCP accepting the transfer of ownership. Once COMMITSCP accepts ownership of the
object(s), eRAD PACS retains a copy at all times.
1.3 Sequencing of Real Word Activities
SENDSCU only transmits, PRINTSCU only prints, QRSCP only responds to query and retrieve
requests for, and COMMITSCP only commits objects that STORESCP previously received and
successfully loaded into the eRAD PACS database. MWLSCP only responds to query requests for
objects that MWLSCU previously received and loaded into the database. MPPSSCP responds to
requests to modify existing orders received from the RIS or manually created in eRAD PACS.
COMMITSCP responds to requests issued by modalities, and requires the study referenced in the
request to be resident in eRAD PACS.
MWLSCU is configured to automatically query the remote AE at a scheduled interval. eRAD PACS
can disable these two AEs so that they do not query at any time.
2 - AE SPECIFICATIONS
2.1 STORESCP - Specification
STORESCP provides Standard Conformance to the following DICOM V3.0 SOP Class as an SCP.
Verification 1.2.840.10008.1.1
Computed Tomography (CT) Image 1.2.840.10008.5.1.4.1.1.2
Enhanced CT Image 1.2.840.10008.5.1.4.1.1.2.1
Computed Radiography Image 1.2.840.10008.5.1.4.1.1.1
Digital IntraOral Xray Image for Presentation 1.2.840.10008.5.1.4.1.1.1.3
Digital IntraOral Xray Image for Processing 1.2.840.10008.5.1.4.1.1.1.3.1
Digital Mammography Xray Image for Presentation 1.2.840.10008.5.1.4.1.1.1.2
Digital Mammography Xray Image for Processing 1.2.840.10008.5.1.4.1.1.1.2.1
Digital Xray Image for Presentation 1.2.840.10008.5.1.4.1.1.1.1
Digital Xray Image for Processing 1.2.840.10008.5.1.4.1.1.1.1.1
Hardcopy Color Image 1.2.840.10008.5.1.1.30
Hardcopy Grayscale Image 1.2.840.10008.5.1.1.29
MR Image 1.2.840.10008.5.1.4.1.1.4
Enhanced MR Image 1.2.840.10008.5.1.4.1.1.4.1
MR Spectroscopy 1.2.840.10008.5.1.4.1.1.4.2
Nuclear Medicine Image 1.2.840.10008.5.1.4.1.1.20
Nuclear Medicine Image (Retired) 1.2.840.10008.5.1.4.1.1.5
Raw Data 1.2.840.10008.5.1.4.1.1.66
Spatial Registration 1.2.840.10008.5.1.4.1.1.66.1
Spatial Fiducials 1.2.840.10008.5.1.4.1.1.66.2
Real World Value Mapping 1.2.840.10008.5.1.4.1.1.67
eRAD PACS
DICOM Conformance Statement
Page 4 12/11/2009
PET Curve 1.2.840.10008.5.1.4.1.1.129
PET Image 1.2.840.10008.5.1.4.1.1.128
RT Beams Treatment Record 1.2.840.10008.5.1.4.1.1.481.4
RT Brachy Treatment Record 1.2.840.10008.5.1.4.1.1.481.6
RT Dose 1.2.840.10008.5.1.4.1.1.481.2
RT Image 1.2.840.10008.5.1.4.1.1.481.1
RT Plan 1.2.840.10008.5.1.4.1.1.481.5
RT Structure Set 1.2.840.10008.5.1.4.1.1.481.3
RT Treatment Summary Record 1.2.840.10008.5.1.4.1.1.481.7
Secondary Capture Image 1.2.840.10008.5.1.4.1.1.7
Multi-frame Single Bit Secondary Capture 1.2.840.10008.5.1.4.1.1.7.1
Multi-frame Grayscale Byte Secondary Capture 1.2.840.10008.5.1.4.1.1.7.2
Multi-frame Grayscale Word Secondary Capture 1.2.840.10008.5.1.4.1.1.7.3
Multi-frame True Color Secondary Capture 1.2.840.10008.5.1.4.1.1.7.4
Standalone Curve 1.2.840.10008.5.1.4.1.1.9
Standalone Modality LUT 1.2.840.10008.5.1.4.1.1.10
Standalone Overlay 1.2.840.10008.5.1.4.1.1.8
Standalone VOI LUT 1.2.840.10008.5.1.4.1.1.11
Stored Print 1.2.840.10008.5.1.1.27
Ultrasound Image 1.2.840.10008.5.1.4.1.1.6.1
Ultrasound Image (Retired) 1.2.840.10008.5.1.4.1.1.6
Ultrasound Multi-frame Image 1.2.840.10008.5.1.4.1.1.3.1
Ultrasound Multi-frame Image (Retired) 1.2.840.10008.5.1.4.1.1.3
Twelve Lead ECG Waveform 1.2.840.10008.5.1.4.1.1.9.1.1
General ECG Waveform 1.2.840.10008.5.1.4.1.1.9.1.2
Ambulatory ECG Waveform 1.2.840.10008.5.1.4.1.1.9.1.3
Hemodynamic Waveform 1.2.840.10008.5.1.4.1.1.9.2.1
Cardiac Electrophysiology Waveform 1.2.840.10008.5.1.4.1.1.9.3.1
Basic Voice Audio Waveform 1.2.840.10008.5.1.4.1.1.9.4.1
X-ray Angiographic Image 1.2.840.10008.5.1.4.1.1.12.1
Enhanced XA Image 1.2.840.10008.5.1.4.1.1.12.1.1
X-ray Fluoroscopy Image 1.2.840.10008.5.1.4.1.1.12.2
Enhanced XA Image 1.2.840.10008.5.1.4.1.1.12.2.1
X-ray Angiographic BiPlane Image (Retired) 1.2.840.10008.5.1.4.1.1.12.3
Grayscale Softcopy Presentation State 1.2.840.10008.5.1.4.1.1.11.1
Color Softcopy Presentation State 1.2.840.10008.5.1.4.1.1.11.2
Pseudo-color Softcopy Presentation State 1.2.840.10008.5.1.4.1.1.11.3
Blending Softcopy Presentation State 1.2.840.10008.5.1.4.1.1.11.4
VL Endoscopic Image 1.2.840.10008.5.1.4.1.1.77.1.1
VL Microscopic Image 1.2.840.10008.5.1.4.1.1.77.1.2
VL Photographic Image 1.2.840.10008.5.1.4.1.1.77.1.4
VL Slide Coordinates Microscopic Image 1.2.840.10008.5.1.4.1.1.77.1.3
VL Image (Retired) 1.2.840.10008.5.1.4.1.1.77.1
VL Multi-frame Image (Retired) 1.2.840.10008.5.1.4.1.1.77.2
Ophthalmic Photography 8 Bit Image 1.2.840.10008.5.1.4.1.1.77.1.5.1
Ophthalmic Photography 16 Bit Image 1.2.840.10008.5.1.4.1.1.77.1.5.2
Stereometric Relationship 1.2.840.10008.5.1.4.1.1.77.1.5.3
Basic Text Structured Report 1.2.840.10008.5.1.4.1.1.88.11
Enhanced Structured Report 1.2.840.10008.5.1.4.1.1.88.22
Comprehensive Structured Report 1.2.840.10008.5.1.4.1.1.88.33
Procedure Log 1.2.840.10008.5.1.4.1.1.88.40
Mammography CAD Structured Report 1.2.840.10008.5.1.4.1.1.88.50
Key Object Selection Document 1.2.840.10008.5.1.4.1.1.88.59
Chest CAD Structured Report 1.2.840.10008.5.1.4.1.1.88.65
X-ray Radiation Dose Structured Report 1.2.840.10008.5.1.4.1.1.88.67
Encapsulated PDF 1.2.840.10008.5.1.4.1.1.104.1
eRAD PACS
DICOM Conformance Statement
Page 5 12/11/2009
2.1.1 Association Establishment
2.1.1.1 General
The maximum PDU size that the STORESCP AE uses is configurable, with a minimum of 8K bytes.
Default is 16K. Maximum is 64K.
2.1.1.2 Number of Associations
The number of simultaneous associations that STORESCP will accept is limited by the kernel
parameters of the underlying TCP/IP implementation and by a configurable parameter in one of the
configuration files.
2.1.1.3 Asynchronous Nature
STORESCP will only allow a single outstanding operation on an Association. Therefore STORESCP
does not perform asynchronous window negotiation.
2.1.1.4 Implementation Identifying Information
STORESCP will provide a single implementation Class UID, which is 1.2.826.0.1.3680043.2.93.0.99
STORESCP will provide an implementation version name of ERAD_<version>, where <version> is
the software version number. An example is ERAD_52.
2.1.2 Association Initiation
STORESCP does not initiate Associations.
2.1.3 Association Acceptance
STORESCP accepts an association when it receives a valid Association request delivered to the
configured TCP port which contains a valid application entity title, and offers at least one of the
presentation contexts listed in the tables below. STORESCP will receive any images transmitted on
that association and store images on disk. The AE also supports the Verification Service Class.
STORESCP places no limitation on who may connect to it when running in promiscuous.
2.1.3.1 Remote System Request - Verification
This section explains how STORESCP handles a remote system request verification from an SCU
using the C-ECHO command.
2.1.3.1.1 ASSOCIATED REAL-WORLD ACTIVITY - VERIFICATION
STORESCP performs the verification Service Class by responding with
C-ECHO-RSP to provide the SCU with the ability to determine if it is receiving DICOM requests.
2.1.3.1.2 PRESENTATION CONTEXT TABLE - VERIFICATION
Acceptable Verification Presentation Contexts for STORESCP
Abstract Syntax Transfer Syntax Role Ext.
Name UID Name UID Neg.
Verification 1.2.840.10008.1.1 Implicit VR Little Endian 1.2.840.10008.1.2 SCP None
2.1.3.1.2.1 SOP Specific Conformance to Verification SOP Class
STORESCP provides standard conformance to the DICOM V3.0 Verification Service Class as an
SCP.
2.1.3.1.3 PRESENTATION CONTEXT ACCEPTANCE CRITERION - VERIFICATION
STORESCP accepts any Presentation Context from the table in section 2.1.3.1.2.
2.1.3.1.4 TRANSFER SYNTAX SELECTION POLICIES - VERIFICATION
STORESCP receives requests encoded using the transfer syntax listed in section 2.1.3.1.2.
eRAD PACS
DICOM Conformance Statement
Page 6 12/11/2009
2.1.3.2 Remote System Request - Storage
This section explains how STORESCP handles a remote system request from an SCU using the CSTORE
operation.
2.1.3.2.1 ASSOCIATED REAL-WORLD ACTIVITY - STORAGE
The associated Real-World Activity associated with the storage operation is the transmission of an
object from a remote AE to the system upon which STORESCP is running. STORESCP issues a
failure status if it is unable to store the object on disk. STORESCP also invokes an attached
application for each object received. STORESCP does not respond to the C-STORE-REQ until it has
verified the data and determines it is able to insert it into the database.
2.1.3.2.2 PRESENTATION CONTEXT TABLE - STORAGE
Acceptable Storage Presentation Contexts for STORESCP
Abstract Syntax Transfer Syntax Role Ext.
Name UID Name UID Neg.
Computed
Radiography
Image
1.2.840.10008.5.1.4.1.1.1 See default transfer
syntax table
See default transfer
syntax table
SCP None
Digital X-ray Image
- Presentation
1.2.840.10008.5.1.4.1.1.1.1 See default transfer
syntax table
See default transfer
syntax table
SCP None
Digital X-ray Image
- Processing
1.2.840.10008.5.1.4.1.1.1.1.1 See default transfer
syntax table
See default transfer
syntax table
SCP None
Digital Mammo Xray
Image -
Presentation
1.2.840.10008.5.1.4.1.1.1.2 See default transfer
syntax table
See default transfer
syntax table
SCP None
Digital Mammo Xray
Image -
Processing
1.2.840.10008.5.1.4.1.1.1.2.1 See default transfer
syntax table
See default transfer
syntax table
SCP None
Digital IntraOral Xray
Image-
Presentation
1.2.840.10008.5.1.4.1.1.1.3 See default transfer
syntax table
See default transfer
syntax table
SCP None
Digital IntraOral Xray
Image –
Processing
1.2.840.10008.5.1.4.1.1.1.3.1 See default transfer
syntax table
See default transfer
syntax table
SCP None
Computed
Tomography
Image
1.2.840.10008.5.1.4.1.1.2 See default transfer
syntax table
See default transfer
syntax table
SCP None
Enhanced CT
Image
1.2.840.10008.5.1.4.1.1.2.1 See default transfer
syntax table
See default transfer
syntax table
SCP None
Ultrasound Multiframe
Image
(Retired)
1.2.840.10008.5.1.4.1.1.3 See default transfer
syntax table
See default transfer
syntax table
SCP None
Ultrasound Multiframe
Image
1.2.840.10008.5.1.4.1.1.3.1 See default transfer
syntax table
See default transfer
syntax table
SCP None
MR Image 1.2.840.10008.5.1.4.1.1.4 See default transfer
syntax table
See default transfer
syntax table
SCP None
Enhanced MR
Image
1.2.840.10008.5.1.4.1.1.4.1 See default transfer
syntax table
See default transfer
syntax table
SCP None
MR Spectroscopy
Image
1.2.840.10008.5.1.4.1.1.4.2 See default transfer
syntax table
See default transfer
syntax table
SCP None
Ultrasound Image
(Retired)
1.2.840.10008.5.1.4.1.1.6 See default transfer
syntax table
See default transfer
syntax table
SCP None
Ultrasound Image 1.2.840.10008.5.1.4.1.1.6.1 See default transfer
syntax table
See default transfer
syntax table
SCP None
Secondary
Capture Image
1.2.840.10008.5.1.4.1.1.7 See default transfer
syntax table
See default transfer
syntax table
SCP None
eRAD PACS
DICOM Conformance Statement
Page 7 12/11/2009
Acceptable Storage Presentation Contexts for STORESCP
Abstract Syntax Transfer Syntax Role Ext.
Name UID Name UID Neg.
Multi-frame Single
Bit Secondary
Capture
1.2.840.10008.5.1.4.1.1.7.1 See default transfer
syntax table
See default transfer
syntax table
SCP None
Multi-frame
Grayscale Byte
Secondary
Capture
1.2.840.10008.5.1.4.1.1.7.2 See default transfer
syntax table
See default transfer
syntax table
SCP None
Multi-frame
Grayscale Word
Secondary
Capture
1.2.840.10008.5.1.4.1.1.7.3 See default transfer
syntax table
See default transfer
syntax table
SCP None
Multi-frame True
Color Secondary
Capture
1.2.840.10008.5.1.4.1.1.7.4 See default transfer
syntax table
See default transfer
syntax table
SCP None
General ECG
Waveform
1.2.840.10008.5.1.4.1.1.9.1.2 See default transfer
syntax table
See default transfer
syntax table
SCP None
Ambulatory ECG
Waveform
1.2.840.10008.5.1.4.1.1.9.1.3 See default transfer
syntax table
See default transfer
syntax table
SCP None
Cardiac
Electrophysiology
Waveform
1.2.840.10008.5.1.4.1.1.9.3.1 See default transfer
syntax table
See default transfer
syntax table
SCP None
Basic Voice Audio
Waveform
1.2.840.10008.5.1.4.1.1.9.4.1 See default transfer
syntax table
See default transfer
syntax table
SCP None
Grayscale
Softcopy
Presentation State
1.2.840.10008.5.1.4.1.1.11.1 See default transfer
syntax table
See default transfer
syntax table
SCP None
Color Softcopy
Presentation State
1.2.840.10008.5.1.4.1.1.11.2 See default transfer
syntax table
See default transfer
syntax table
SCP None
Pseudo-color
Softcopy
Presentation State
1.2.840.10008.5.1.4.1.1.11.3 See default transfer
syntax table
See default transfer
syntax table
SCP None
Blending Softcopy
Presentation State
1.2.840.10008.5.1.4.1.1.11.4 See default transfer
syntax table
See default transfer
syntax table
SCP None
X-ray Angiographic
Image
1.2.840.10008.5.1.4.1.1.12.1 See default transfer
syntax table
See default transfer
syntax table
SCP None
Enhanced XA
Image
1.2.840.10008.5.1.4.1.1.12.1.1 See default transfer
syntax table
See default transfer
syntax table
SCP None
X-ray Fluoroscopy
Image
1.2.840.10008.5.1.4.1.1.12.2 See default transfer
syntax table
See default transfer
syntax table
SCP None
Enhanced XRF
Image
1.2.840.10008.5.1.4.1.1.12.2.1 See default transfer
syntax table
See default transfer
syntax table
SCP None
Nuclear Medicine
Image
1.2.840.10008.5.1.4.1.1.20 See default transfer
syntax table
See default transfer
syntax table
SCP None
Raw Data 1.2.840.10008.5.1.4.1.1.66 See default transfer
syntax table
See default transfer
syntax table
SCP None
Spatial Fiducials 1.2.840.10008.5.1.4.1.1.66 See default transfer
syntax table
See default transfer
syntax table
SCP None
Spatial
Registration
1.2.840.10008.5.1.4.1.1.66 See default transfer
syntax table
See default transfer
syntax table
SCP None
Real World Value
Mapping
1.2.840.10008.5.1.4.1.1.67 See default transfer
syntax table
See default transfer
syntax table
SCP None
VL Endoscopic
Image
1.2.840.10008.5.1.4.1.1.77.1.1 See default transfer
syntax table
See default transfer
syntax table
SCP None
VL Microscopic
Image
1.2.840.10008.5.1.4.1.1.77.1.2 See default transfer
syntax table
See default transfer
syntax table
SCP None
eRAD PACS
DICOM Conformance Statement
Page 8 12/11/2009
Acceptable Storage Presentation Contexts for STORESCP
Abstract Syntax Transfer Syntax Role Ext.
Name UID Name UID Neg.
VL Photographic
Image
1.2.840.10008.5.1.4.1.1.77.1.4 See default transfer
syntax table
See default transfer
syntax table
SCP None
VL Slide
Coordinates
Microscopic Image
1.2.840.10008.5.1.4.1.1.77.1.3 See default transfer
syntax table
See default transfer
syntax table
SCP None
Ophthalmic
Photography 8 Bit
Image
1.2.840.10008.5.1.4.1.1.77.1.5.1 See default transfer
syntax table
See default transfer
syntax table
SCP None
Ophthalmic
Photography 16 Bit
Image
1.2.840.10008.5.1.4.1.1.77.1.5.2 See default transfer
syntax table
See default transfer
syntax table
SCP None
Stereometric
Relationship
1.2.840.10008.5.1.4.1.1.77.1.5.3 See default transfer
syntax table
See default transfer
syntax table
SCP None
Basic Text SR 1.2.840.10008.5.1.4.1.1.88.11 See default transfer
syntax table
See default transfer
syntax table
SCP None
Enhanced SR 1.2.840.10008.5.1.4.1.1.88.22 See default transfer
syntax table
See default transfer
syntax table
SCP None
Comprehensive
SR
1.2.840.10008.5.1.4.1.1.88.33 See default transfer
syntax table
See default transfer
syntax table
SCP None
Procedure Log 1.2.840.10008.5.1.4.1.1.88.40 See default transfer
syntax table
See default transfer
syntax table
SCP None
Key Object
Selection
1.2.840.10008.5.1.4.1.1.88.59 See default transfer
syntax table
See default transfer
syntax table
SCP None
Mammography
CAD SR
1.2.840.10008.5.1.4.1.1.88.50 See default transfer
syntax table
See default transfer
syntax table
SCP None
Chest CAD SR 1.2.840.10008.5.1.4.1.1.88.65 See default transfer
syntax table
See default transfer
syntax table
SCP None
X-Ray Radiation
Dose SR
1.2.840.10008.5.1.4.1.1.88.67 See default transfer
syntax table
See default transfer
syntax table
SCP None
PET Curve 1.2.840.10008.5.1.4.1.1.129 See default transfer
syntax table
See default transfer
syntax table
SCP None
PET Image 1.2.840.10008.5.1.4.1.1.128 See default transfer
syntax table
See default transfer
syntax table
SCP None
Encapsulated PDF 1.2.840.10008.5.1.4.1.1.104.1 See default transfer
syntax table
See default transfer
syntax table
SCP None
RT Beams
Treatment Record
1.2.840.10008.5.1.4.1.1.481.4 See default transfer
syntax table
See default transfer
syntax table
SCP None
RT Brachy
Treatment Record
1.2.840.10008.5.1.4.1.1.481.6 See default transfer
syntax table
See default transfer
syntax table
SCP None
RT Dose 1.2.840.10008.5.1.4.1.1.481.2 See default transfer
syntax table
See default transfer
syntax table
SCP None
RT Image 1.2.840.10008.5.1.4.1.1.481.1 See default transfer
syntax table
See default transfer
syntax table
SCP None
RT Plan 1.2.840.10008.5.1.4.1.1.481.5 See default transfer
syntax table
See default transfer
syntax table
SCP None
RT Structure Set 1.2.840.10008.5.1.4.1.1.481.3 See default transfer
syntax table
See default transfer
syntax table
SCP None
RT Treatment
Summary Record
1.2.840.10008.5.1.4.1.1.481.7 See default transfer
syntax table
See default transfer
syntax table
SCP None
The following Storage SOP Classes are supported for archiving, but are not included in the default
configuration.
eRAD PACS
DICOM Conformance Statement
Page 9 12/11/2009
Acceptable Storage Presentation Contexts for STORESCP
Abstract Syntax Transfer Syntax Role Ext.
Name UID Name UID Neg.
Stored Print 1.2.840.10008.5.1.1.27 See default transfer
syntax table
See default transfer
syntax table
SCP None
Hardcopy
Grayscale Image
1.2.840.10008.5.1.1.29 See default transfer
syntax table
See default transfer
syntax table
SCP None
Hardcopy Color
Image
1.2.840.10008.5.1.1.30 See default transfer
syntax table
See default transfer
syntax table
SCP None
Nuclear Medicine
Image (Retired)
1.2.840.10008.5.1.4.1.1.5 See default transfer
syntax table
See default transfer
syntax table
SCP None
Standalone
Overlay
1.2.840.10008.5.1.4.1.1.8 See default transfer
syntax table
See default transfer
syntax table
SCP None
Standalone Curve 1.2.840.10008.5.1.4.1.1.9 See default transfer
syntax table
See default transfer
syntax table
SCP None
Twelve Lead ECG
Waveform
1.2.840.10008.5.1.4.1.1.9.1.1 See default transfer
syntax table
See default transfer
syntax table
SCP None
Hemodynamic
Waveform
1.2.840.10008.5.1.4.1.1.9.2.1 See default transfer
syntax table
See default transfer
syntax table
SCP None
Standalone
Modality LUT
1.2.840.10008.5.1.4.1.1.10 See default transfer
syntax table
See default transfer
syntax table
SCP None
Standalone VOI
LUT
1.2.840.10008.5.1.4.1.1.11 See default transfer
syntax table
See default transfer
syntax table
SCP None
X-ray Angio
BiPlane Image
(Ret.)
1.2.840.10008.5.1.4.1.1.12.3 See default transfer
syntax table
See default transfer
syntax table
SCP None
VL Image (Retired) 1.2.840.10008.5.1.4.1.1.77.1 See default transfer
syntax table
See default transfer
syntax table
SCP None
VL Multi-Frame
Image (Retired)
1.2.840.10008.5.1.4.1.1.77.2 See default transfer
syntax table
See default transfer
syntax table
SCP None
The default transfer syntaxes STORESCP supports are as defined in the table below. Unless noted
otherwise, all SOP classes STORESCP supports can use any of these transfer syntaxes. The
selection of which one STORESCP prefers if given the option is configurable.
Default Transfer Syntax Table
Transfer Syntax UID
Implicit VR Little Endian 1.2.840.10008.1.2
Explicit VR Little Endian 1.2.840.10008.1.2.1
Explicit VR Big Endian 1.2.840.10008.1.2.2
JPEG Baseline (Process 1) 1.2.840.10008.1.2.4.50
JPEG Lossless Non-hierarchical 1st Order Predication 1.2.840.10008.1.2.4.70
RLE Lossless 1.2.840.10008.1.2.5
JPEG 2000 Lossless Only 1.2.840.10008.1.2.4.90
JPEG 2000 1.2.840.10008.1.2.4.91
2.1.3.2.2.1 SOP Specific Conformance to Storage SOP Classes
STORESCP conforms to each Storage SOP Class at Level 2 (full) and Signature Level 3. In the case
of a successful C-STORE, the object is stored on the disk. Otherwise STORESCP returns an error
and purges the object. If STORESCP returns one of the following status codes, the C-STORE was
unsuccessful:
• A700 (Out of Resources) - Indicates that there was insufficient disk space to store the image.
• A800 (SOP Class Not Supported) - Indicates that the SOP Class of the object in the C-STORE
operation did not match the Abstract Syntax negotiated for the Presentation Context.
• A900 (Data Set does not match SOP Class) - Indicates that the Data Set does not contain an
instance of the SOP Class specified or the Affected SOP Instance UID does not match the
object’s SOP Instance UID.
• C000 (Cannot understand) - Indicates that the Data Set cannot be parsed into elements.
eRAD PACS
DICOM Conformance Statement
Page 10 12/11/2009
The stored objects may be accessed through eRAD PACS’s graphical user interface, or DICOM
Query/Retrieve SOP classes. The following stored objects can be viewed using eRAD PACS’s
graphical user interface:
Computed Tomography Image
Enhanced CT Image
Computed Radiography Image
Grayscale Softcopy Presentation State
MR Image
Enhanced MR Image
MR Spectroscopy Image
Digital Mammography Image for Presentation
Digital Mammography Image for Processing
Digital X-ray Image for Presentation
Digital X-ray Image for Processing
Nuclear Medicine Image
Nuclear Medicine Image (Retired)
PET Image
RT Image
Secondary Capture Image
Multi-frame Single Bit Secondary Capture
Multi-frame Grayscale Byte Secondary Capture
Multi-frame Grayscale Word Secondary Capture
Multi-frame True Color Secondary Capture
Ultrasound Image
Ultrasound Image (Retired)
Ultrasound Multi-frame Image
Ultrasound Multi-frame Image (Retired)
VL Endoscopic Image
VL Microscopic Image
VL Photographic Image
VL Slide Coordinates Microscopic Image
VL Image (Retired)
VL Multi-frame Image (Retired)
X-ray Angiographic Image
Enhanced XA Image
X-ray Fluoroscopy Image
Enhanced XRF Image
X-ray Angiographic Bi-Plane Image (Retired)
The following stored objects can be viewed using the eRAD PACS graphical user interface if eRAD
PACS created it:
Basic Text Structured Report
Enhanced Structured Report
Comprehensive Structured Report
STORESCP will not delete a file it has received unless directed to do so by a user or administrator.
2.1.3.2.2.2 SOP Specific Conformance to Structured Report Storage SOP Classes
In addition to the basic support for Storage SOP Classes listed in the previous section, STORESCP
will interpret and display structure reports objects that conform to the Basic Text SR, Enhanced SR
and Composite SR SOP Classes. All of the conformance conditions for general Storage SOP
Classes applied, in addition to those given in the following paragraph.
STORESCP renders the information in the structured report object in both the web and viewing
graphical user interfaces. The text and images are rendered, along with the supported report
demographics.
2.1.3.2.2.3 SOP Specific Conformance to Grayscale Softcopy Presentation State SOP Classes
When a grayscale softcopy presentation state object exists for any image object listed as viewable (in
section 2.1.3.2.2.1) and displayed on the screen, eRAD PACS informs the user it exists and allows
the user to apply it to the image. If multiple presentation state objects exist, the user can apply any
number of them selectively. If more than one presentation state object affects the same display
parameter, the last one applied takes precedence. Currently, eRAD PACS only applies the VOI LUT
and spatial transformation (zoom, pan, crop, flip/rotate). All other presentation state information is
ignored.
2.1.3.2.3 PRESENTATION CONTEXT ACCEPTANCE CRITERION - STORAGE
STORESCP will accept any and all Presentation Contexts listed in the table in section 2.1.3.2.2.
2.1.3.2.4 TRANSFER SYNTAX SELECTION POLICIES - STORAGE
The default behavior of the STORESCP application is to prefer transfer syntaxes having an explicit
value representation to those using the default implicit VR. If STORESCP is running on big-endian
hardware it will prefer DICOM Explicit Value Representation Big Endian transfer syntax (and vice
versa)
eRAD PACS
DICOM Conformance Statement
Page 10 12/11/2009
STORESCP does not support extended negotiation.
2.2 SENDSCU - Specification
SENDSCU provides Standard Conformance to the DICOM V3.0 SOP Classes listed in section 2.1, as
an SCU. SENDSCU also provides supports for the DICOM Structured Report SOP Class for Basic
Text SR objects.
2.2.1 Association Establishment
2.2.1.1 General
The maximum PDU size that SENDSCU uses is configurable, with a minimum of 8K bytes. Default is
16K. Maximum is 64K.
2.2.1.2 Number of Associations
The number of simultaneous associations that SENDSCU will initiate is limited by the kernel
parameters of the underlying TCP/IP implementation and by a configurable parameter that defaults to
5 simultaneous associations.
2.2.1.3 Asynchronous Nature
SENDSCU will only allow a single outstanding operation on an Association. Therefore SENDSCU
does not perform asynchronous window negotiation.
2.2.1.4 Implementation Identifying Information
SENDSCU provides a single implementation Class UID, 1.2.826.0.1.3680043.2.93.0.99
SENDSCU provides an implementation version name of ERAD_<version>, where <version> is the
software version number. An example is ERAD_52.
2.2.2 Association Initiation
SENDSCU initiates an association when it receives a request from a user or system process to
transmit one or more stored objects to a specified DICOM AE. The destination AE’s IP address, port
number and AE Title come from a list of preconfigured entries. SENDSCU attempts to establish a
connection and, if successful, sends the image and/or report objects as queued. Failed transmission
will be retried for a defined period of time, and then returned to the user or system for resolution.
2.2.2.2 eRAD PACS Request – Send Images
This section explains how STORESCU handles a user or system request to send one or more image
objects using the C-STORE operation.
2.2.2.2.1 ASSOCIATED REAL-WORLD ACTIVITY – SEND IMAGES
The associated Real-World Activity associated with the C-STORE operation is the user or system
request for transmitting a selected set of image objects to a remote AE.
2.2.2.2.2 PRESENTATION CONTEXT TABLE – SEND IMAGES
The Abstract Syntax of the proposed Association conforms to that which is stored in the object being
transmitted. Since SENDSCU only supports the SOPs STORESCP supports, the full list of possible
Abstract Syntaxes is listed in the table in section 2.1.3.2.2. The remainder of the presentation context
information is shown in the table below.
eRAD PACS
DICOM Conformance Statement
Page 11 12/11/2009
Proposed Presentation Contexts for SENDSCU
Abstract Syntax Transfer Syntax Role Ext.
Name UID Name UID Neg.
As Defined in Object As Defined in Object As defined in section
2.1.3.2.2
As defined in section
2.1.3.2.2
SCU None
2.2.2.2.2.1 SOP Specific Conformance to Storage SOP Classes
Upon receiving a successful status from the remote AE, SENDSCU returns to the requesting user a
good status. By default, SENDSCU does not take action upon the stored image object.
Upon a failure status or a warning from the remote AE, SENDSCU closes the Association and places
the objects on a retry queue. At scheduled intervals, SENDSCU attempts to resend the object(s).
After attempting to resend the object(s) a defined number of times, SENDSCU places them on a failed
queue, waiting for user action.
SENDSCU may add private attributes to the object. These attributes can be found in private group
0xF215, marked with a private creator value of “ImageMedical”. These attributes can be excluded
through configuration.
SENDSCU does not support extended negotiation.
2.2.2.3 eRAD PACS Request – Send Reports
This section explains how SENDSCU handles a user or the system uses the C-STORE operation to
send one or more structured report objects created by SENDSCU.
2.2.2.3.1 ASSOCIATED REAL-WORLD ACTIVITY – SEND REPORTS
Before SENDSCU attempts to send a structured report, one must be created. A user can create the
report by entering the report text and image information into the eRAD PACS Viewer. Alternatively,
an information system can send the report text information to eRAD PACS and SENDSCU will
convert the HL7 data into a structured report object. The associated Real-World Activity associated
with the C-STORE operation is the user or system request to transmit a selected set of image objects
to a remote AE. If a structured report for the study exists, SENDSCU will attempt to negotiate a
Presentation Context for the report object and transmit it.
2.2.2.3.2 PRESENTATION CONTEXT TABLE – SEND REPORTS
The Abstract Syntax of the proposed Association conforms to the Basic Text SR SOP Class.
Proposed Presentation Contexts for SENDSCU
Abstract Syntax Transfer Syntax Role Ext.
Name UID Name UID Neg.
Basic Text SR 1.2.840.10008.5.1.4.1
.1.88.11
Impl.VR Little Endian
Expl.VR Little Endian
1.2.840.10008.1.2
1.2.840.10008.1.2.1
SCU None
2.2.2.3.2.1 SOP Specific Conformance to Structured Report Storage SOP Classes
Upon receiving a successful status from the remote AE, SENDSCU returns to the requesting user a
good status. Upon a failure status or a warning from the remote AE, SENDSCU places the object on
a retry queue and periodically attempts to resend them for a defined period of time. When SENDSCU
reaches the maximum number of retries and has not successfully transmitted the object(s), it places
them on a failed queue, waiting for user action.
SENDSCU supports structure report objects for the image and other composite objects listed in the
table in section 2.1.3.2.2. SENDSCU supports the following Value Types:
Text PNAME Container
SENDSCU supports the following Relationship Types:
eRAD PACS
DICOM Conformance Statement
Page 12 12/11/2009
Source Value Type Relationship Type Target Value Type
Container CONTAINS Text, Container
Container HAS OBS CONTEXT PNAME
SENDSCU may include private attributes in the objects. Private attributes exist in private groups as
defined by DICOM’s encoding rules. These attributes can be found in private group 0xF215, marked
with a private creator value of “ImageMedical”.
SENDSCU does not support extended negotiation.
2.2.3 Association Acceptance
SENDSCU does not accept Associations.
2.3 PRINTSCU - Specification
PRINTSCU provides Standard Conformance to the DICOM V3.0 Print Management SOP Class as an
SCU.
2.3.1 Association Establishment
2.3.1.1 General
The maximum PDU size that the PRINTSCU AE uses is configurable, with a minimum of 8K bytes.
Default is 16K. Maximum is 64K.
2.3.1.2 Number of Associations
The number of simultaneous associations that PRINTSCU initiates is limited by the kernel parameters
of the underlying TCP/IP implementation and by a configurable parameter in one of the configuration
files.
2.3.1.3 Asynchronous Nature
PRINTSCU will only allow a single outstanding operation on an Association. Therefore PRINTSCU
does not perform asynchronous window negotiation.
2.2.1.4 Implementation Identifying Information
PRINTSCU will provide a single implementation Class UID of 1.2.826.0.1.3680043.2.93.0.99
PRINTSCU will provide an implementation version name of ERAD_<version>, where <version> is the
software version number. An example is ERAD_52.
2.3.2 Association Initiation
PRINTSCU initiates an association when it receives a request from a user or system process to print
one or more image objects to a specified DICOM Print AE. The destination AE’s IP address, port
number and AE Title come from a list of preconfigured entries. PRINTSCU will attempt to establish a
connection and, if successful, will send the print session information. Failed transmission will be
returned to the user or system for a resolution.
2.3.2.1 eRAD PACS Request - Print
This section explains how PRINTSCUU handles a user or the system request to print image objects
using the DICOM DIMSE services.
2.3.2.1.1 ASSOCIATED REAL-WORLD ACTIVITY - PRINT
The associated Real-World Activity associated with the print operation is the user or system request
for transmitting a selected set of image objects to a remote AE.
eRAD PACS
DICOM Conformance Statement
Page 13 12/11/2009
2.3.2.1.2 PRESENTATION CONTEXT TABLE – PRINT
The Association contains all supported Abstract Syntaxes. The list of supported presentation context
information is shown in the table below.
Proposed Presentation Contexts for PRINTSCU
Abstract Syntax Transfer Syntax Role Ext.
Name UID Name UID Neg.
Basic Grayscale
Print Meta SOP
Class
1.2.840.10008.5.1.1.9 Impl.VR Little Endian
Expl.VR Little Endian
Expl.VR Big Endian
1.2.840.10008.1.2
1.2.840.10008.1.2.1
1.2.840.10008.1.2.2
SCU None
2.3.2.1.2.1 SOP Specific Conformance to Print SOP Classes
Upon receiving a successful status from the remote AE, PRINTSCU returns to the requesting user a
good status. By default, PRINTSCU does not take action upon the printed image object.
Upon a failure status or a warning from the remote AE, PRINTSCU closes the Association and returns
to the requesting user a failed status. The user must then decide what action to take next.
PRINTSCU takes no further action until it receives instruction from the user.
2.3.3 Association Acceptance
PRINTSCU does not accept Associations.
2.4 QRAE - Specification
QRAE consists of two application entities. QRSCU provides Standard Conformance to the DICOM
V3.0 Query/Retrieve SOP Class as an SCU. QRSCP provides Standard Conformance to the DICOM
V3.0 Query/Retrieve SOP Class as an SCP.
2.4.1 Association Establishment
2.4.1.1 General
The maximum PDU size that the QRSCU and QRSCP uses is configurable, with a minimum of 8K
bytes. Default is 16K. Maximum is 64K.
2.4.1.2 Number of Associations
The number of simultaneous associations that QRSCU and QRSCP initiate is limited by the kernel
parameters of the underlying TCP/IP implementation and by a configurable parameter stored in a
configuration file.
2.4.1.3 Asynchronous Nature
QRSCU and QRSCP each allow only a single outstanding operation on an Association. Therefore
QRSCU and QRSCP do not perform asynchronous window negotiation.
2.4.1.4 Implementation Identifying Information
QRSCU and QRSCP provide a single implementation Class UID of 1.2.826.0.1.3680043.2.93.0.99.
QRSCU and QRSCP provide an implementation version name of ERAD_<version>, where <version>
is the software version number. An example is ERAD_52.
2.4.2 Association Initiation
QRSCU initiates an association when it receives a request from a user or system process to search
the database of a specified DICOM Q/R AE, or to request that a specified object be transmitted from
on AE to another. The destination AE’s IP address, port number, AE Title, and move destinations
come from a list of preconfigured entries. QRSCU will attempt to establish a connection and, if
successful, will send the query or move parameters. Failed transmission will be returned to the user
or system for a resolution.
eRAD PACS
DICOM Conformance Statement
Page 14 12/11/2009
2.4.2.1 eRAD PACS Request - Find
This section explains how QRSCU handles a user or the system request to query a remote AE using
DICOM’s DIMSE C-FIND services.
2.4.2.1.1 ASSOCIATED REAL-WORLD ACTIVITY - FIND
The associated Real-World Activity associated with the find operation is a user or system request to
list the items that match the specified criteria. The matching criteria are selected from a user interface
or from some encoded data. The activity completes when the remote AE returns the matching items.
2.4.2.1.2 PRESENTATION CONTEXT TABLE – FIND
The Association contains all supported Abstract Syntaxes. The list of supported presentation context
information is shown in the table below.
Proposed Presentation Contexts for QRSCU
Abstract Syntax Transfer Syntax Role Ext.
Name UID Name UID Neg.
Patient Root Q/R
Information Model
– FIND
1.2.840.10008.5.1.4.1.2.
1.1
Impl.VR Little Endian
Expl.VR Little Endian
Expl.VR Big Endian
1.2.840.10008.1.2
1.2.840.10008.1.2.1
1.2.840.10008.1.2.2
SCU None
Study Root Q/R
Information Model
– FIND
1.2.840.10008.5.1.4.1.2.
2.1
Impl.VR Little Endian
Expl.VR Little Endian
Expl.VR Big Endian
1.2.840.10008.1.2
1.2.840.10008.1.2.1
1.2.840.10008.1.2.2
SCU None
2.4.2.1.2.1 SOP Specific Conformance to Find SOP Classes
QRSCU conforms to the Patient Root, Study Root and Patient/Study Only SOP Class groups as an
SCU. QRSCU does not negotiate relational queries.
The complete list of keys supported by QRSCU is given in the following table.
Tag Attribute Description Type
0008, 0018 SOP Instance UID O
0008, 0020 Study Date R
0008, 0030 Study Time R
0008, 0050 Accession Number R
0008, 0060 Modality O
0008, 0090 Referring Physician O
0008, 1030 Study Description O
0008, 1060 Reading Physician O
0010, 0010 Patient Name R
0010, 0020 Patient ID R
0010, 0030 Patient Date of Birth O
0010, 0032 Patient Time of Birth O
0010, 0040 Patient Sex O
0020, 000D Study UID U
0020, 000E Series UID O
0020, 0010 Study ID R
0020, 0011 Series Number O
0020, 0013 Image Number O
Upon receiving a successful status from the remote AE, QRSCU returns to the requesting user a
good status and all the records that match the requested criteria. QRSCU then closes the
Association.
Upon a failure status or a warning from the remote AE, QRSCU closes the Association and returns to
the requesting user a failed status. The user must then decide what action to take next.
eRAD PACS
DICOM Conformance Statement
Page 15 12/11/2009
2.4.2.2 eRAD PACS Request - Move
This section explains how QRSCU handles a user or the system request to move one or more image
objects from the remote AE to another AE using DICOM’s DIMSE C-MOVE service.
2.4.2.2.1 ASSOCIATED REAL-WORLD ACTIVITY - MOVE
The associated Real-World Activity associated with the move operation is the user or system request
for transmitting a selected set of image objects from the remote AE to another AE.
2.4.2.2.2 PRESENTATION CONTEXT TABLE – MOVE
The Association contains all supported Abstract Syntaxes. The list of supported presentation context
information is shown in the table below.
Proposed Presentation Contexts for QRSCU
Abstract Syntax Transfer Syntax Role Ext.
Name UID Name UID Neg.
Patient Root Q/R
Information Model
– MOVE
1.2.840.10008.5.1.4.1.2.
1.2
Impl.VR Little Endian
Expl.VR Little Endian
Expl.VR Big Endian
1.2.840.10008.1.2
1.2.840.10008.1.2.1
1.2.840.10008.1.2.2
SCU None
Study Root Q/R
Information Model
– MOVE
1.2.840.10008.5.1.4.1.2.
2.2
Impl.VR Little Endian
Expl.VR Little Endian
Expl.VR Big Endian
1.2.840.10008.1.2
1.2.840.10008.1.2.1
1.2.840.10008.1.2.2
SCU None
2.4.2.2.2.1 SOP Specific Conformance to Move SOP Classes
QRSCU conforms to the Patient Root - Move, Study Root – Move and Patient/Study Only – Move
SOP Classes as an SCU.
Upon receiving a successful status from the remote AE, QRSCU returns to the requesting user a
good status. QRSCU then closes the Association.
Upon a failure status or a warning from the remote AE, QRSCU closes the Association and returns to
the requesting user a failed status. The user must then decide what action to take next.
2.4.3 Association Acceptance
QRSCP accepts an association when it receives a valid Association request delivered to the
configured TCP port which contains a valid application entity title, and offers at least one of the
presentation contexts listed in the tables below. QRSCP will receive query and move requests
transmitted on that association, search the database for matching records, and then either return the
matches to the requesting AE or initiate a SENDSCU operation to send the objects to the specified
AE. QRSCP places no limitation on who may connect to it when running in promiscuous mode.
2.4.3.1 Remote System Request - Find
This section explains how QRSCP handles a remote system Find request from an SCU using the CFIND
command.
2.4.3.1.1 ASSOCIATED REAL-WORLD ACTIVITY - FIND
QRSCP performs a search of the database looking for records that match the specified criteria
whenever it receives a valid C-FIND request from an AE. For each match, QRSCP will return a
response message. When all responses are sent, QRSCP will wait for another request or for the
SCU to close the association.
2.4.3.1.2 PRESENTATION CONTEXT TABLE – FIND
QRSCP will accept the Presentation Contexts listed in the following table.
eRAD PACS
DICOM Conformance Statement
Page 16 12/11/2009
Proposed Presentation Contexts for QRSCP
Abstract Syntax Transfer Syntax Role Ext.
Name UID Name UID Neg.
Patient Root Q/R
Information Model
– FIND
1.2.840.10008.5.1.4.1.2.
1.1
Impl.VR Little Endian
Expl.VR Little Endian
Expl.VR Big Endian
1.2.840.10008.1.2
1.2.840.10008.1.2.1
1.2.840.10008.1.2.2
SCP None
Study Root Q/R
Information Model
– FIND
1.2.840.10008.5.1.4.1.2.
2.1
Impl.VR Little Endian
Expl.VR Little Endian
Expl.VR Big Endian
1.2.840.10008.1.2
1.2.840.10008.1.2.1
1.2.840.10008.1.2.2
SCP None
Patient/Study Only
Q/R Information
Model – FIND
1.2.840.10008.5.1.4.1.2.
3.1
Impl.VR Little Endian
Expl.VR Little Endian
Expl.VR Big Endian
1.2.840.10008.1.2
1.2.840.10008.1.2.1
1.2.840.10008.1.2.2
SCP None
2.4.3.1.2.1 SOP Specific Conformance to Query/Retrieve SOP Classes
QRSCP provides standard conformance to the DICOM Patient Root – Find, Study Root – Find, and
Patient/Study Only - Find Service Classes as an SCP. QRSCP support all of the attributes listed in
the table in section 2.4.2.1.2.1. QRSCP does not negotiate for relational queries and therefore does
not support them. QRSCP supports both case sensitive and case insensitive queries. The option is
specified in the configuration file. QRSCP does not support extended negotiation.
2.4.3.1.3 PRESENTATION CONTEXT ACCEPTANCE CRITERION - FIND
QRSCP will accept any Presentation Context from the table in section 2.4.3.1.2. Preference will be
given to the Study Root SOP classes if multiple Presentation Contexts are requested.
2.4.3.1.4 TRANSFER SYNTAX SELECTION POLICIES - FIND
QRSCP will receive requests encoded using the transfer syntax listed in the table in section 2.4.3.1.2.
2.4.3.2 Remote System Request - Move
This section explains how QRSCP handles a remote system move request from an SCU using the CMOVE
command.
2.4.3.2.1 ASSOCIATED REAL-WORLD ACTIVITY - MOVE
QRSCP performs a search of the database looking for the requested object(s) and then sends them
to SENDSCU for transmission to the specified AE. For each match, QRSCP will return a response
message to the requesting AE. When all objects are sent, QRSCP will wait for another request or for
the SCU to close the association.
2.4.3.2.2 PRESENTATION CONTEXT TABLE – MOVE
QRSCP will accept the Presentation Contexts listed in the following table.
Proposed Presentation Contexts for QRSCP
Abstract Syntax Transfer Syntax Role Ext.
Name UID Name UID Neg.
Patient Root Q/R
Information Model
– MOVE
1.2.840.10008.5.1.4.1.2.
1.2
Impl.VR Little Endian
Expl.VR Little Endian
Expl.VR Big Endian
1.2.840.10008.1.2
1.2.840.10008.1.2.1
1.2.840.10008.1.2.2
SCP None
Study Root Q/R
Information Model
– MOVE
1.2.840.10008.5.1.4.1.2.
2.2
Impl.VR Little Endian
Expl.VR Little Endian
Expl.VR Big Endian
1.2.840.10008.1.2
1.2.840.10008.1.2.1
1.2.840.10008.1.2.2
SCP None
Patient/Study Only
Q/R Information
Model – MOVE
1.2.840.10008.5.1.4.1.2.
3.2
Impl.VR Little Endian
Expl.VR Little Endian
Expl.VR Big Endian
1.2.840.10008.1.2
1.2.840.10008.1.2.1
1.2.840.10008.1.2.2
SCP None
2.4.3.2.2.1 SOP Specific Conformance to Query/Retrieve SOP Classes
QRSCP provides standard conformance to the DICOM Patient Root – Move, Study Root – Move, and
Patient/Study Only - Move Service Classes as an SCP. QRSCP supports sub-operations for all of the
Storage SOP classes listed in section 2.1.
eRAD PACS
DICOM Conformance Statement
Page 17 12/11/2009
2.4.3.2.3 PRESENTATION CONTEXT ACCEPTANCE CRITERION - MOVE
QRSCP will accept any Presentation Context from the table in section 2.4.3.2.2. Preference will be
given to the Study Root SOP classes if multiple Presentation Contexts are requested.
2.4.3.2.4 TRANSFER SYNTAX SELECTION POLICIES - MOVE
QRSCP will receive requests encoded using the transfer syntax listed in the table in section 2.4.3.2.2.
2.5 MWLAE - Specification
MWLSCU provides Standard Conformance to the DICOM V3.0 Modality Worklist Management SOP
Class as an SCU. MWLSCP provides Standard Conformance to the DICOM V3.0 Modality Worklist
SOP Class as an SCP. MPPSSCP provides Standard Conformance to the DICOM V3.0 Modality
Performed Procedure Step SOP Class as an SCP.
2.5.1 Association Establishment
2.5.1.1 General
The maximum PDU size that MWLSCU, MWLSCP and MPPSSCP uses is configurable, with a
minimum of 8K bytes. Default is 16K. Maximum is 64K.
2.5.1.2 Number of Associations
The number of simultaneous associations that MWLSCU, MWLSCP and MPPSSCP initiates is limited
by the kernel parameters of the underlying TCP/IP implementation and by a configurable parameter
that defaults to 5 simultaneous associations.
2.5.1.3 Asynchronous Nature
MWLSCU, MWLSCP and MPPSSCP only allows a single outstanding operation on an Association
and therefore do not perform asynchronous window negotiation.
2.5.1.4 Implementation Identifying Information
MWLSCU, MWLSCP and MPPSSCP provide a single implementation Class UID,
1.2.826.0.1.3680043.2.93.0.99
MWLSCU, MWLSCP and MPPSSCP provide an implementation version name of ERAD_<version>,
where <version> is the software version number. An example is ERAD_60.
2.5.2 Association Initiation
MWLSCU initiates an association when it receives a request from the system to request a list of
scheduled procedures from the remote AE. The destination AE’s IP address, port number and AE
Title come from the configuration settings. MWLSCU issues a request for all procedures that have
been scheduled since the last successful query. Responses to the query request will be inserted into
the database and made available on the worklist.
2.5.2.1 eRAD PACS Request – Get Worklist Item
This section explains how MWLSCU handles a system request to query a remote AE using DICOM’s
DIMSE C-FIND services.
2.5.2.1.1 ASSOCIATED REAL-WORLD ACTIVITY – GET WORKLIST ITEM
When eRAD PACS wants to retrieve the most recent list of scheduled exam procedures, it calls upon
MWLSCU to query the worklist manager for a list of items. The matching criteria are hardcoded into
MWLSCU. The activity completes when the remote AE returns the matching items, if any, and the
final response message.
eRAD PACS
DICOM Conformance Statement
Page 18 12/11/2009
2.5.2.1.2 PRESENTATION CONTEXT TABLE – GET WORKLIST ITEM
The Association contains all supported Abstract Syntaxes. The list of supported presentation context
information is shown in the table below.
Proposed Presentation Contexts for MWLSCU
Abstract Syntax Transfer Syntax Role Ext.
Name UID Name UID Neg.
Modality Worklist
Information Model
– FIND
1.2.840.10008.5.1.4.31 Impl.VR Little Endian
Expl.VR Little Endian
Expl.VR Big Endian
1.2.840.10008.1.2
1.2.840.10008.1.2.1
1.2.840.10008.1.2.2
SCU None
2.5.2.1.2.1 SOP Specific Conformance to Find SOP Classes
MWLSCU may request any of the attributes in the following table. The Attributes of type R will be in
every query request. The O type attributes may be in the query.
Tag Attribute Description Type
0008, 0050 Accession Number R
0008, 0080 Institution Name O
0008, 0081 Institution Address O
0008, 0082 Institution Code Sequence O
0008, 0090 Referring Physician R
0008, 0092 Referring Physician Address R
0008, 0094 Referring Physician Telephone Number R
0008, 1080 Admitting Diagnosis Description O
0008, 1084 Admitting Diagnosis Code Sequence O
0008, 1110 Referenced Study Sequence O
0008, 1120 Referenced Patient Sequence O
0008, 1125 Referenced Visit Sequence O
0010, 0010 Patient Name R
0010, 0020 Patient ID R
0010, 0021 Issuer of Patient ID O
0010, 0030 Patient Date of Birth R
0010, 0032 Patient Time of Birth R
0010, 0040 Patient Sex R
0010, 0050 Patient Insurance Plan Code Sequence O
0010, 1000 Other Patient IDs O
0010, 1001 Other Patient Names O
0010, 1005 Patient Birth Name O
0010, 1010 Patient Age O
0010, 1020 Patient Size O
0010, 1030 Patient Weight O
0010, 1040 Patient Address R
0010, 1060 Patient’s Mother’s Birth Name O
0010, 1080 Military Rank O
0010, 1081 Branch of Service O
0010, 1090 Medical Record Locator O
0010, 2000 Medical Alerts O
0010, 2110 Contrast Allergies O
0010, 2150 Country of Residence O
0010, 2152 Region of Residence O
0010, 2154 Patient’s Telephone Number R
0010, 2160 Ethnic Group O
0010, 2180 Occupation O
0010, 21A0 Smoking Status O
0010, 21B0 Additional Patient History R
0010, 21C0 Pregnancy Status O
0010, 21D0 Last Menstrual Date O
eRAD PACS
DICOM Conformance Statement
Page 19 12/11/2009
Tag Attribute Description Type
0010, 21F0 Patient Religious Preference O
0010, 4000 Patient Comments O
0020, 000D Study UID R
0032, 1032 Requesting Physician R
0032, 1033 Requesting Service O
0032, 1060 Requested Procedure Description R
0032, 1064 Requested Procedure Code Sequence R
0038, 0004 Referenced Patient Alias Sequence O
0038, 0008 Visit Status ID O
0038, 0010 Admission ID O
0038, 0011 Issuer of Admission ID O
0038, 0016 Route of Admissions O
0038, 0020 Admitting Date O
0038, 0021 Admitting Time O
0038, 0050 Special Needs O
0038, 0300 Current Patient Location R
0038, 0400 Patient Institution Residence O
0038, 0500 Patient State O
0038, 4000 Visit Comments O
0040, 0100 Scheduled Procedure Step Sequence R
0040, 1001 Requested Procedure ID O
0040, 1002 Reason for the Requested Procedure R
0040, 1003 Requested Procedure Priority R
0040, 1004 Patient Transport Arrangements O
0040, 1005 Requested Procedure Location O
0040, 1008 Confidentiality Code O
0040, 1009 Reporting Priority O
0040, 1010 Names of Intended Results Recipients O
0040, 1400 Requested Procedure Comments O
0040, 2001 Reason for the Imaging Service Request R
0040, 2004 Issue Date of Imaging Service Request O
0040, 2005 Issue Time of Imaging Service Request O
0040, 2008 Order Entered By O
0040, 2009 Order Enterer’s Location O
0040, 2010 Order Callback Phone Number O
0040, 2016 Placer Order Number Imaging Svc Req. O
0040, 2017 Filler Order Number Imaging Svc Req. O
0040, 2400 Imaging Service Request Comments O
0040, 3001 Confidentiality Constraint on Patient Data O
Upon a failure status or a warning from the remote AE, MWLSCU closes the Association. The system
will attempt the query at the next scheduled interval.
2.5.3 Association Acceptance
MWLSCP and MPPSSCP accept associations when either one receives a valid Association request
delivered to the configured TCP port which contains a valid application entity title, and offers one of
the presentation contexts listed in section 2.5.3.1.2 or 2.5.3.2.2. MWLSCP receives query requests
transmitted on that association, search the database for matching records, and then return the
matches to the requesting AE. MPPSSCP received N-CREATE and N-SET requests transmitted on
the association and updates the database with the data conveyed in its attributes. Neither MWLSCP
nor MPPSSCP place limitations on who may connect to it when running in promiscuous mode.
2.5.3.1 Remote System Request – Request Worklist Items
This section explains how MWLSCP handles a remote system Find request from an SCU using the CFIND
command.
eRAD PACS
DICOM Conformance Statement
Page 20 12/11/2009
2.5.3.1.1 ASSOCIATED REAL-WORLD ACTIVITY – REQUEST WORKLIST ITEMS
MWLSCP performs a search of the database looking for records that match the specified criteria
whenever it receives a valid C-FIND request from an AE. For each match, MWLSCP returns a
response message. When all responses are sent, MWLSCP waits for another request or for the SCU
to close the association.
2.5.3.1.2 PRESENTATION CONTEXT TABLE – REQUEST WORKLIST ITEMS
MWLSCP will accept the Presentation Contexts listed in the following table.
Proposed Presentation Contexts for MWLSCP
Abstract Syntax Transfer Syntax Role Ext.
Name UID Name UID Neg.
Modality Worklist
Information Model
– FIND
1.2.840.10008.5.1.4.31 Impl.VR Little Endian
Expl.VR Little Endian
Expl.VR Big Endian
1.2.840.10008.1.2
1.2.840.10008.1.2.1
1.2.840.10008.1.2.2
SCP None
2.5.3.1.2.1 SOP Specific Conformance to the Modality Worklist SOP Class
MWLSCP supports all of the attributes listed in the table in section 2.5.2.1.2.1, with the noted
exceptions listed below. The attributes listed in this table as type R are searchable attributes,
although there is no guarantee that any of these attributes actually contain any value. The remaining,
type O, attributes may be requested, but MWLSCP will not perform any matching on values.
Tag Attribute Description Comment
0040, 0020 Scheduled Procedure Step Status This attribute of the Scheduled Procedure
Step Sequence only supports the following
values: STAT, MEDIUM, LOW
MWLSCP supports both case sensitive and case insensitive queries. The option is specified in the
configuration file.
2.5.3.1.3 PRESENTATION CONTEXT ACCEPTANCE CRITERION – REQUEST WORKLIST ITEMS
MWLSCP will accept any Presentation Context from the table in section 2.5.3.1.2.
2.5.3.1.4 TRANSFER SYNTAX SELECTION POLICIES – REQUEST WORKLIST ITEMS
MWLSCP will receive requests encoded using the transfer syntax listed in the table in section
2.5.3.1.2.
2.5.3.2 Remote System Request – Update Procedure Step
This section explains how MPPSSCP handles a remote system request to create and update
procedure step information using the N-CREATE and N-SET commands.
2.5.3.2.1 ASSOCIATED REAL-WORLD ACTIVITY – UPDATE PROCEDURE STEP
MPPSSCP received the attribute list in the N-CREATE or N-SET request, finds the corresponding
procedure step instance, and updates the information in the database with the information in the
request. After updating the database, MPPSSCP returns the completion status and waits for another
request or for the SCU to close the association.
2.5.3.2.2 PRESENTATION CONTEXT TABLE – REQUEST WORKLIST ITEMS
MPPSSCP accepts the Presentation Contexts listed in the following table.
Proposed Presentation Contexts for MWLSCP
Abstract Syntax Transfer Syntax Role Ext.
Name UID Name UID Neg.
Modality
Performed
Procedure Step
1.2.840.10008.3.1.2.3.3 Impl.VR Little Endian
Expl.VR Little Endian
Expl.VR Big Endian
1.2.840.10008.1.2
1.2.840.10008.1.2.1
1.2.840.10008.1.2.2
SCP None
eRAD PACS
DICOM Conformance Statement
Page 21 12/11/2009
2.5.3.2.2.1 SOP Specific Conformance to the Modality Performed Procedure Step SOP Class
MPPSSCP supports the attributes listed in the table below. Other attributes are accepted but their
values are unused.
Attribute Name Tag N-CREATE N-SET
Specific Character Set (0008,0005) 1C Not allowed
Scheduled Step Attribute Sequence (0040,0270) 1
Not allowed
>Study Instance UID (0020,000D) 1 Not allowed
>Requested Procedure ID (0040,1001) 2 Not allowed
>Scheduled Procedure Step ID (0040,0009) 2 Not allowed
Performed Procedure Step ID (0040,0253) 1 Not allowed
Performed Procedure Step Status (0040,0252) 1 1
When MPPSSCP receives an N-CREATE request for a procedure step already in the IN PROGRESS
state, it acknowledges the request with an error status (InvalidAttributeValue), and takes no action on
the data in the message.
When MPPSSCP receives a request updating the Performed Procedure Step State attribute to
COMPLETE, it updates the performed procedure state status, removes the procedure step instance
from the database, updates the exam order, sends an update message to the RIS, if one is present,
and sets the eRAD PACS study state to Completed.
When MPPSSCP receives a request updating the Performed Procedure Step State attribute to
DISCONTINUED, it updates the performed procedure step status, removes the procedure step
instance from the database, but leaves the exam order in the system, to be cancelled by the RIS or
manually.
MPPSSCP does not coerce any data attributes when it receives a request updating the Performed
Procedure Step State attribute, except for modifying the attributes listed in the table in this section as
specified in the request message.
Modality performed procedure step SOP instances persist until MPPSSCP receives a request
updating the Performed Procedure Step State attribute to DISCONTINUED or COMPLETED.
2.5.3.2.3 PRESENTATION CONTEXT ACCEPTANCE CRITERION – REQUEST WORKLIST ITEMS
MPPSSCP accepts any Presentation Context from the table in section 2.5.3.2.2.
2.5.3.2.4 TRANSFER SYNTAX SELECTION POLICIES – REQUEST WORKLIST ITEMS
MPPSSCP receives requests encoded using the transfer syntax listed in the table in section 2.5.3.2.2.
2.6 COMMITSCP - Specification
COMMITSCP provides Standard Conformance to the DICOM V3.0 Storage Commitment Push Model
SOP Class as an SCP.
2.6.1 Association Establishment
2.6.1.1 General
The maximum PDU size that the COMMITSCP AE uses is configurable, with a minimum of 8K bytes.
Default is 16K. Maximum is 64K.
2.6.1.2 Number of Associations
The number of simultaneous associations that COMMITSCP initiates is limited by the kernel
parameters of the underlying TCP/IP implementation and by a configurable parameter in one of the
configuration files.
eRAD PACS
DICOM Conformance Statement
Page 22 12/11/2009
2.6.1.3 Asynchronous Nature
COMMITSCP will only allow a single outstanding operation on an Association. COMMITSCP does
not perform asynchronous window negotiation.
2.6.1.4 Implementation Identifying Information
COMMITSCP provides a single implementation Class UID of 1.2.826.0.1.3680043.2.93.0.99.
COMMITSCP provides an implementation version name of ERAD_<version>, where <version> is the
software version number. An example is ERAD_52.
2.6.2 Association Initiation
COMMITSCP initiates associations in order to send N-EVENT-REPORT messages to a remote AE.
When COMMITSCP requests an association, it always negotiates the SCU/SCP role such that it
performs as the SCP.
2.6.2.1 eRAD PACS Request – Acknowledge Commit
This section explains how COMMITSCP acknowledges the transfer of ownership in response to a
previously issues commit request.
2.6.2.1.1 ASSOCIATED REAL-WORLD ACTIVITY – ACKNOWLEDGE COMMIT
When eRAD PACS processes the commit request, it verifies it has previously received the specified
objects, marks them to indicate it now owns the data, and verifies they are archived. Once eRAD
PACS finishes processing the request, it acknowledges the request by issuing an N-EVENT-REPORT
to the requesting AE.
2.6.2.1.2 PRESENTATION CONTEXT TABLE – ACKNOWLEDGE COMMIT
The Association request contains all supported Abstract Syntaxes. The list of supported presentation
context information is shown in the table below.
Proposed Presentation Contexts for PRINTSCU
Abstract Syntax Transfer Syntax Role Ext.
Name UID Name UID Neg.
Storage
Commitment Push
Model SOP Class
1.2.840.10008.1.20.1 Impl.VR Little Endian
Expl.VR Little Endian
Expl.VR Big Endian
1.2.840.10008.1.2
1.2.840.10008.1.2.1
1.2.840.10008.1.2.2
SCP Role
Neg.
2.6.2.1.2.1 SOP Specific Conformance to Storage Commitment Push Model SOP Classes
eRAD PACS uses the DICOM Storage SOP Classes to accept the SOP Instances the remote AE is
requesting COMMITSCP to accept. Section 2.2 lists the specific Storage SOP Classes eRAD PACS
supports.
COMMITSCP initiates an N-EVENT-REPORT to the remote AE after it verifies that the selected
objects are archived by either an eRAD PACS archive or some other archiving system. If no space is
available in the archive, COMMITSCP shall not issue an N-EVENT-REPORT message accepting the
transfer of ownership.
Once COMMITSCP processes the request and issues the N-EVENT-REPORT message, eRAD
PACS does not remove the object from its database. The data is archive internally or externally, and
can be retrieved using the user interface tools, or DICOM Query/Retrieve SOP class.
COMMITSCP does not support the optional Storage Media File-set ID and UID attributes.
COMMITSCP does not support the optional Retrieve AE Title attribute in the N-EVENT-REPORT
message.
eRAD PACS
DICOM Conformance Statement
Page 23 12/11/2009
2.6.3 Association Acceptance
COMMITSCP accepts associations when a remote AE wants to pass ownership of one or more
objects to eRAD PACS. The objects listed in the N-ACTION request must already reside within eRAD
PACS, received and acknowledged by STORESCP.
2.6.3.1 Remote System Request – Commit
This section explains how COMMITSCP handles a system request to transfer the ownership of an
object using the DICOM DIMSE services.
2.6.3.1.1 ASSOCIATED REAL-WORLD ACTIVITY –COMMIT
The associated Real-World Activity associated with the commit operation is the remote AE request to
transfer ownership of an object to a COMMITSCP. This action can only happen after the respective
object has been successfully transferred to STORESCP before initiating the commit action.
2.6.3.1.2 PRESENTATION CONTEXT TABLE –COMMIT
COMMITSCP accepts the Presentation Contexts listed in the table listed in section 2.6.2.1.2.
2.6.3.1.3 TRANSFER SYNTAX SELECTION POLICIES – COMMIT
COMMITSCP will receive requests encoded using any one of the transfer syntaxes listed in the table
in section 2.6.2.1.2.
3 - COMMUNICATION PROFILES
3.1 Supported Communication Stacks
All eRAD PACS AEs provides DICOM V3.0 TCP/IP Network Communication Support as defined in
Part 8 of the DICOM standard.
3.2 TCP/IP Stack
All eRAD PACS AEs inherit their TCP/IP stack from the operating system upon which it executes.
3.2.1 Physical Media Support
All eRAD PACS AEs are indifferent to the physical medium over which TCP/IP executes. It inherits
this from the OS.
4 - EXTENSIONS/SPECIALIZATIONS/PRIVATIZATIONS
4.1 eRAD PACS Report Private SOP Class Specification
eRAD PACS stores reports using the generic DICOM File Format as defined in Part 10, in a privatized
DICOM object. The file contains the standard meta information, identifying the encoded syntax and
the eRAD PACS Report private SOP class.
4.1.1 Association Establishment
4.1.1.1 General
The maximum PDU size that the eRAD PACS report AE uses is configurable, with a minimum of 8K
bytes. Default is 16K. Maximum is 64K.
4.1.1.2 Number of Associations
The number of simultaneous associations that the report AE initiates is limited only by the kernel
parameters of the underlying TCP/IP implementation. Therefore it can have multiple simultaneous
connections.
eRAD PACS
DICOM Conformance Statement
Page 24 12/11/2009
4.1.1.3 Implementation Identifying Information
The eRAD PACS report AE provides a single implementation Class UID of
1.2.826.0.1.3680043.2.93.0.99, and contain an implementation version name of ERAD_<version>,
where <version> is the software version number. An example is ERAD_52.
4.1.2 Association Initiation
eRAD PACS initiates an Association when a report exists for a study object that a user requested be
transmitted to a remote DICOM entity. The Association request consists of two application contexts.
One context manages the transmission of textual reports between communicating entities. The
second context manages the transmission of audio report files.
4.1.2.1 eRAD PACS Request – Send a Report
When the application successfully negotiates a presentation context for eRAD PACS reports, the SCU
shall use the DICOM C-STORE DIMSE service to pass the object to the SCP. The operation is
considered successful when the SCP returns a C-STORE response message with a status of
SUCCESS.
4.1.2.1.1 REPORT OBJECT DEFINITION
eRAD PACS’s private report object is defined as follows:
Tag VR Type Description Additional Comment
0008,0016 UI 1 SOP Class UID Equal to
1.2.826.0.1.3680043.2.93.10000300.0.1
0008,0018 UI 1 SOP Instance UID
0008,0090 PN 3 Referring Physicians Name
0008,1060 PN 3 Name Of Physicians
Reading Study
0010,0010 PN 3 Patients Name
0010,0020 LO 3 Patient ID
0020,000d UI 1 Study Instance UID
4008,010c PN 3 Interpretation Author
f215,ba01 LT 3 PB Observation Report observation text
f215,ba02 IS 3 PB Status Preliminary (=80) or Final (=100)
f215,ba03 LT 3 PB Figure Referenced image UIDs
f215,ba05 LT 3 PB Impression Report impression text
4.1.2.1.2 PRESENTATION CONTEXT TABLE – SEND A REPORT
The Association request contains all supported Abstract Syntaxes. The list of supported presentation
context information is shown in the table below.
Proposed Presentation Contexts for eRAD PACS Report AE
Abstract Syntax Transfer Syntax Role Ext.
Name UID Name UID Neg.
PracticeBuilder
Report Text
1.2.826.0.1.3680043.2.93.1.
0.1
Impl.VR Little Endian
Expl.VR Little Endian
Expl.VR Big Endian
1.2.840.10008.1.2
1.2.840.10008.1.2.1
1.2.840.10008.1.2.2
SCU None
PracticeBuilder
Report Dictation
1.2.826.0.1.3680043.2.93.1.
0.2
Impl.VR Little Endian
Expl.VR Little Endian
Expl.VR Big Endian
1.2.840.10008.1.2
1.2.840.10008.1.2.1
1.2.840.10008.1.2.2
SCU None
4.1.3 Association Acceptance
eRAD PACS will accept an Association when an Application Context exists for the PracticeBuilder
Report Text or Dictation SOP Classes.
eRAD PACS
DICOM Conformance Statement
Page 25 12/11/2009
4.1.3.1 Remote System Request – Store Report
When the remote AE sends an eRAD PACS report object using DICOM C-STORE request, the
receiving AE will store that file on disk. Provided the store process completed successfully, the AE
will return a C-STORE response packet containing a SUCCESS status to the sending AE. This AE
will then wait the next packet.
4.1.3.1.1 PRESENTATION CONTEXT TABLE – STORE REPORT
The eRAD PACS report AE will accept presentation contexts containing the Abstract Syntaxes listed
in the Presentation Context table in section 4.1.1.2. For all Abstract Syntaxes, the eRAD PACS report
AE will function in the Role of an SCP.
5 - CONFIGURATION
All eRAD PACS AEs (STORESCP, SENDSCU, PRINTSCU, etc.) attempt to load DICOM data
dictionaries specified in the DCMDICTPATH environment variable. By default, if the DCMDICTPATH
environment variable is not set, the file
/usr/local/dicom/lib/dicom.dic
is loaded. The DCMDICTPATH environment variable has the same format as the shell PATH variable
in that a colon (":") separates entries. The data dictionary code will attempt to load each file specified
in the DCMDICTPATH environment variable. It is an error if no data dictionary can be loaded.
5.1 AE Title/Presentation Address Mapping
All supported AEs use a presentation address constructed from the host-name of the server on which
it executes, and a port number specified as a command line parameter at the start of eRAD PACS’s
DCMTK daemon.
STORESCP’s, QRSCP’s, MPPSSCP’s and COMMITSCP’s application titles are the same. It is
configurable in the command scripts and from the administration web pages. The default is
PBUILDER. QRSCP can have two application titles. One is to direct query and retrieve requests to
just the worklist database. The other is to query and retrieve from the entire system archive.
SENDSCU’s, QRSCU’s, and MWLSCU’s application titles are the same and are configurable. The
default is PBUILDER.
PRINTSCU’s application title is a configurable parameter. The default is DCMPSTATE.
5.2 Configurable Parameters
• Maximum PDU size (default is 16K)
• Preferred transfer syntax (default is implicit VR little endian)
• Host name
• TCP and TLS port number (default for regular DICOM is 104; default for secure DICOM is 2762)
• Remote Application Entity IP addresses, port numbers and AE Titles
• Number of simultaneous DICOM associations (default is 5)
• AE Title to specify query/retrieve of worklist only or entire archive
• Which FIND and MOVE SOP class to use in Query/Retrieve SOP classes (default is Study Root)
• Use case sensitive or case insensitive query matching (default is case insensitive)
• Accept all DICOM Associations (promiscuous mode) or only those originating at known AEs.
• Remove private attributes when forwarding previously acquired image Storage SOP Class
objects.
6 - SUPPORT OF EXTENDED CHARACTER SETS
STORESCP, SENDSCU, PRINTSCU, MPPSSCP and COMMITSCP are indifferent to Extended
Character Sets, as the application doesn't rely on the information contained within the Data Elements.
eRAD PACS
DICOM Conformance Statement
Page 26 12/11/2009
However, since it is possible to obtain lists of data contained in the database (for administrative
functions), only the default character set is supported.
QRSCU, QRSCP and MWLSCU support the default character set only.
7 – CODES AND CONTROLLED TERMINOLOGY
This implementation makes use of the Baseline Context Groups as specified in the IODs for the SOP
Classes supported. No private mapping resource or coding schemes are employed. All available
codes are selected from values specified in the SOP instances when they arrive at eRAD PACS.
8 – SECURITY PROFILES
eRAD PACS supports the Basic TLS Secure Transport Connection Profile. All association requests
directed to and accepted at the TLS port address will use this profile. eRAD PACS uses the following
standards for its key management:
Exchange of Master Secrets RSA
Data Integrity SHA
Privacy Triple DES EDE, CBC
Entity Authentication RSA based certificatesDICOM Conformance Statement
The original document is available at http://537999.nhjqzg.asia/tiki-index.php?page=Appendix