DICOM Conformance
Statement
Clinical Content Management
System Release 5.30.5
Emageon Inc.
85000-0816A
http://www.emageon.com
NOTICE - Confidentiality Statement
© 2000-2006 Emageon Inc. 1200 Corporate Drive, Suite 200, Birmingham, AL 35242 | Support: 888-EMAGEON. The information contained herein
is confidential and is the sole property of Emageon Inc. None of the information may be reproduced, copied, and/or re-distributed electronically,
manually, or otherwise to any person without advance written permission from Emageon, except as may be expressly authorized by contracts or
other agreements between Emageon and its customer. Emageon is a registered trademark and Enterprise Visual Medical System (EVMS) is a
trademark of Emageon Inc. Other trademarks or service marks referred to herein are the property of their respective owners.
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
Contents
1
Introduction............................................................................................................................. 4
1.1
Purpose ........................................................................................................................... 4
1.2
Related Documents ......................................................................................................... 4
2
Implementation Model........................................................................................................... 5
2.1
Enterprise Archive Manager ............................................................................................ 5
2.1.1
Application Data Flow Diagram ....................................................................................... 5
2.1.2
Functional Definition of AE’s............................................................................................ 6
2.2
Worklist Manager............................................................................................................. 8
2.2.1
Application data Flow Diagram........................................................................................ 8
2.2.2
Functional Definition of AE’s............................................................................................ 8
2.2.3
Sequencing of Real-World Activities ............................................................................... 9
2.3
Prefetcher ...................................................................................................................... 10
2.3.1
Application Data Flow Diagram ..................................................................................... 10
2.3.2
Functional Definition of AE’s.......................................................................................... 10
2.3.3
Sequencing of Real World Activities ............................................................................. 11
2.4
Technologist Workflow................................................................................................... 12
2.4.1
Application Data Flow Diagram ..................................................................................... 12
2.4.2
Functional Definition of AE’s.......................................................................................... 12
2.4.3
Sequence of Real World Activities ................................................................................ 13
3
AE Specifications................................................................................................................. 14
3.1
Enterprise Archive DICOM Component Specification ................................................... 14
3.1.1
Association Establishment Policies ............................................................................... 16
3.1.2
Association Initiation by Real-World Activity ................................................................. 17
3.1.3
Association Acceptance Policy...................................................................................... 24
3.2
Enterprise Archive Proxy Component Specification...................................................... 42
3.2.1
Association Establishment Policies ............................................................................... 44
3.2.2
Association Initiation by Real-World Activity ................................................................. 45
3.2.3
Association Acceptance Policy...................................................................................... 52
3.2.4
Worklist Manager Specification ..................................................................................... 71
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 2 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
3.2.5
Association Establishment Policies ............................................................................... 71
3.2.6
Association Initiation by Real-World Activity ................................................................. 71
3.2.7
Association Acceptance Policy...................................................................................... 71
3.3
Prefetcher Specification................................................................................................. 80
3.3.1
Association Establishment Policies ............................................................................... 80
3.3.2
Association Initiation by Real-World Activity ................................................................. 81
3.3.3
Association Acceptance Policy...................................................................................... 83
3.4
Technologist Workflow (TWF) Specification.................................................................. 85
3.4.1
Association Establishment Policies ............................................................................... 86
3.4.2
Association Initiation by Real-World Activity ................................................................. 87
3.4.3
Association Acceptance Policy...................................................................................... 88
4
Communication Profiles ..................................................................................................... 93
4.1
Supported Communication Stacks (Parts 8,9) .............................................................. 93
4.2
TCP/IP Stack ................................................................................................................. 93
4.2.1
API ................................................................................................................................. 93
4.2.2
Physical Media Support................................................................................................. 93
5
Extensions/Specializations/Privatizations ....................................................................... 94
5.1
Standard Extended/Specialized/Private SOPs.............................................................. 94
5.2
Private Transfer Syntaxes ............................................................................................. 94
6
Configuration........................................................................................................................ 95
6.1
AE Title/Presentation Address Mapping........................................................................ 95
6.2
Configurable Parameters............................................................................................... 95
7
Support of Extended Character Sets ................................................................................ 96
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 3 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
1
1.1
Introduction
Purpose
This document specifies the conformance of Emageon’s Clinical Content Management
System Release 5.30 to the DICOM 3.0 standard. This document covers
conformance for the following:
1.2
•
Enterprise DICOM Archive Manager – an enterprise class archive providing
long-term storage and retrieval of all DICOM V3.0 objects. It has been designed
for performance, scalability, and reliability.
•
Worklist Manager – a worklist management and persistence engine. It is
designed to support multiple worklist types. It responds to various inputs to
create, schedule, and update information pertaining to work items.
•
Prefetcher – an application that moves DICOM objects on the network in a
predictive manner to facilitate access by real world entities.
•
Technologist Workflow (TWF) – An application that allows for patient
demographic reconciliation with images received from a modality that does not
have worklist support.
Related Documents
NEMA 1999, 2000, 2003, 2004, 2005, 2005 The DICOM Standard: Parts 1 – 14.
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 4 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
2
Implementation Model
2.1
Enterprise Archive Manager
The Enterprise Archive Manager allows for the storage and retrieval of DICOM
objects. Additionally, it allows for the querying of information about the DICOM objects
that have been stored to it.
Administration is accomplished using a remote administrative application.
2.1.1 Application Data Flow Diagram
2.1.1.1
Enterprise Archive DICOM Component AE
C -E cho
O b je ct
s to re d o n
m e d ia
C -S tore
C -F in d
C -M ove
C -G et
M e ta -D B
E n te rp rise
A rch ive
D IC O M A E
C -S tore
N -A ction
N -E ventR epo rt
D IC O M In te rfa c e
N -C re ate
N -S et
(M P P S )
Figure 1-1 Enterprise Archive DICOM AE Implementation Model
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 5 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
2.1.1.2
Enterprise Archive Proxy Component AE
C-Echo
Object
stored on
media
C-Store
C-Find
C-Move
Enterprise
Archive
Proxy AE
C-Store
C-Find
C-Move
Meta-DB
N-Action
N-EventReport
DICOM Interface
Figure 1-2
Enterprise Archive Proxy AE Implementation Model
2.1.2 Functional Definition of AE’s
2.1.2.1
DICOM AE
The Enterprise Archive Manager waits for another application to connect at the
presentation address configured for its Application Entity Title. When another
application connects, the archive expects it to be a DICOM application. The archive
will accept associations with Presentation Contexts for the following SOP Classes:
•
Storage Service Class
•
Storage Commitment Service Class
•
Query/Retrieve Service Class
•
Verification Service Class
•
Study Management Service Class
The archive will receive objects/requests. When it receives an object, it stores that
object in gzip loss-less compressed Part 10 format as a file on a file system and
registers that object in the database.
When a request is received it is processed accordingly. If the request is a retrieve
request, the archive will locate the object in the database, retrieve the object from the
file system in which it is stored, establish an association with the application to receive
the object, and send the object across that association. If the request is a query, the
archive will simply perform the query on the database and return the results.
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 6 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
2.1.2.2
Proxy AE
If the Enterprise Archive Manager is configured with the Proxy component, it waits for
a remote application to connect at the presentation address configured for its “Proxy”
Application Entity Title. When another application connects, the Enterprise Archive
Manager expects it to be a DICOM application. The Enterprise Archive Manager will
accept associations with Presentation Contexts for SOP Classes of the Storage
Service Class, Storage Commitment Service Class, the Query/Retrieve Service Class,
and/or the Verification Service Class. It will receive requests. When a request is
received it is processed. When it receives an object, it stores that object in Part 10
format on some media and registers that object in the database.
If the request is a storage commitment request, it responds with a status of success.
After that, the Proxy will locate the specified objects in the Archive Manager and
Advanced Visualization and then send a storage commitment response.
If the request is a retrieve request the Proxy will locate the object in the database or in
another configured DICOM archive on the network, retrieve the object from the media
that it stored it on or from the external archive where it was found, establish an
association with the application to receive the object, and send the object across that
association. If the request is a query, the Proxy will simply perform the query on the
database and on the other configured archives on the network and return the results.
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 7 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
2.2
Worklist Manager
The Worklist Manager accepts hospital and radiological information system (HIS and
RIS) messages that are in HL7 format. The system converts those messages into the
DICOM data model and uses the information to populate and update a DICOM
modality worklist that is maintained in a relational database. The system then allows
DICOM modality worklist queries against the worklist data.
This document is only concerned with the DICOM aspects of the Worklist Manager.
Administration of the system is accomplished using a remote administrative
application.
2.2.1 Application data Flow Diagram
HL7 Messages
Procedure Scheduled
Procedure Update
Patient Update/Merge
Patient Visit Update
Worklist
Manager AE
C-Find
Meta-DB
DICOM Interface
Figure 2-1 Worklist Manager AE Implementation Model
2.2.2 Functional Definition of AE’s
The Worklist Manager provides a DICOM Modality Worklist SCP that accepts requests
for workitems from properly configured DICOM Modality Worklist SCUs. Typically, a
SCU is either a modality, or if the modality does not support DICOM’s modality
worklist, a DICOM Interface (a.k.a “Black”) Box associated with the modality and
acting on the modality’s behalf.
The modality then presents the query’s resulting workitems to the modality operator
who then chooses and performs an item of work. The resulting images are then
typically stored in an image archive.
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 8 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
2.2.3 Sequencing of Real-World Activities
The Worklist Manager must have a feed of HL7 messages from the HIS/RIS in order
to function properly. This information is used to populate and update the worklist
information residing in the database. The types of HL7 messages used by the system
include:
•
•
•
•
Procedure Scheduled
Procedure Update
Patient Update/Merge
Patient Visit Update
The Emageon HL7 Interface is used to capture HL7 messages and forward them to
the Worklist Manager for processing.
In order to maintain a modality worklist, the Worklist Manager must receive at least
Procedure Scheduled messages.
Procedure Update messages will allow the system to update/cancel workitems.
Patient Update/Merge and Patient Visit Update messages will allow the system to
update workitem demographics – while critical for workflow and data
consistency/accuracy, these are not required for the system to be functional.
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 9 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
2.3
Prefetcher
The Emageon Prefetcher moves images on the network in a predictive manner to
facilitate access by real world entities.
Administration is accomplished using a remote administrative application.
2.3.1 Application Data Flow Diagram
BSCN
HL7 Message
Exam Scheduled
Exam Performed
C-Find
Prefetcher
AE
C-Move
DICOM Interfaces
Figure 3-1 Prefetcher AE Implementation Model
2.3.2 Functional Definition of AE’s
The Emageon Prefetcher provides no services to clients in the typical client server
sense. It is purely a ‘listener’ to the environment, and performs moves as a result of
what it hears.
In general the Prefetcher will accept the following associations with Presentation
Contexts for the following SOP classes:
•
BSCN SCP – receive BSCN as prefetching trigger
•
C-FIND SCU – query archive for priors
•
C-MOVE SCU – make move requests to the archive
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 10 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
2.3.3 Sequencing of Real World Activities
The Prefetcher ‘listens’ for events in the environment that trigger prefetching rules.
These Rules can query DICOM network devices, as well as initiate move requests for
DICOM objects to and from remote DICOM devices.
The Emageon Prefetcher receives events, such as HL7 or BSCN, and executes
custom rules for those events. Those rules can perform C-FIND operations against an
archive in an effort to find prior studies that the rule deems important. Those prior
studies are scheduled to be moved at some point in the future.
When it is time for a set of priors to be moved the Prefetcher will make a C-MOVE
request to the archive hosting the objects in question. All moves will begin as study
level operations. If a failure occurs and a listing of failed SOP instance UIDs is
provided in the result of the study level move, then the Prefetcher will perform a CFIND to obtain a complete listing of objects in the study in question. The failed objects
may be moved again, at the object level, at a future point in time.
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 11 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
2.4
Technologist Workflow
The Emageon Technologist Workflow(TWF) provides a user-interface to the
technologist for reconciling patient demographic data for images received from
modalities that do not support worklist functionality. The TWF functions as plugin to
the Emageon Archive and supports both automatic and manual reconciliation of
studies.
2.4.1 Application Data Flow Diagram
2.4.2 Functional Definition of AE’s
The TWF receives studies from modalites and stores the reconciled studies back to
the Emageon Archive. The TWF also supports MWL queries to retrieve patient
demographic data from the Emageon Worklist.
The TWF will accept associations for the following SOP classes:
•
C-STORE SCP – Receives studies from modalites lacking worklist
functionality.
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 12 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
•
MWL C-FIND SCU – Queries the Modality Worklist for patient demographic
data
2.4.3 Sequence of Real World Activities
A study is acquired at a modality that does not have worklist functionality. The
technologist enters whatever patient demographic data that is on-hand and sends the
study to the TWF using its unique AE-title. The TWF will attempt to auto-reconcile the
study by performing a MWL C-FIND query against the Emageon Worklist for some
pre-defined attributes. If a match is found in the Worklist, the demographic data will be
merged into the study. The technologist will have the opportunity to review this
information before the updated study is moved to the Emageon Archive for storage.
This move is handled internally and does not require an association for a C-Store to
be created.
In the event that a match in the worklist is not found, the technologist will have the
option to manually enter the patient information.
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 13 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
3
3.1
AE Specifications
Enterprise Archive DICOM Component Specification
This Application Entity provides Standard Conformance to the following DICOM V3.0
SOP Classes as an SCU and/or SCP (as indicated in the table) :
(NOTE: New SOP classes may be supported through simple configuration changes of
the product.)
SOP Class Name
SOP Class UID
SCU/SCP
Verification
Verification
1.2.840.10008.1.1
N/Y
Storage
12-lead ECG Waveform Storage
1.2.840.10008.5.1.4.1.1.9.1.1
Y/Y
Ambulatory ECG Waveform Storage
1.2.840.10008.5.1.4.1.1.9.1.3
Y/Y
Basic Text SR Storage
1.2.840.10008.5.1.4.1.1.88.11
Y/Y
Basic Voice Audio Waveform Storage
1.2.840.10008.5.1.4.1.1.9.4.1
Y/Y
Cardiac Electrophysiology Waveform
Storage
1.2.840.10008.5.1.4.1.1.9.3.1
Y/Y
Comprehensive SR Storage
1.2.840.10008.5.1.4.1.1.88.33
Y/Y
Computed Radiography Image Storage
1.2.840.10008.5.1.4.1.1.1
Y/Y
CT Image Storage
1.2.840.10008.5.1.4.1.1.2
Y/Y
Digital X-Ray Image Storage
(Presentation)
1.2.840.10008.5.1.4.1.1.1.1
Y/Y
Digital X-Ray Image Storage (Processing)
1.2.840.10008.5.1.4.1.1.1.1.1
Y/Y
Digital Mammography Image Storage
(Presentation)
1.2.840.10008.5.1.4.1.1.1.2
Y/Y
Digital Mammography Image Storage
(Processing)
1.2.840.10008.5.1.4.1.1.1.2.1
Y/Y
Digital Intra-oral X-Ray Image Storage
(Presentation)
1.2.840.10008.5.1.4.1.1.1.3
Y/Y
Digital Intra-oral X-Ray Image Storage
(Processing)
1.2.840.10008.5.1.4.1.1.1.3.1
Y/Y
Enhanced SR Storage
1.2.840.10008.5.1.4.1.1.88.22
Y/Y
General ECG Waveform Storage
1.2.840.10008.5.1.4.1.1.9.1.2
Y/Y
Grayscale Softcopy Presentation State
Storage
1.2.840.10008.5.1.4.1.1.11.1
Y/Y
Hardcopy Color Image Storage
1.2.840.10008.5.1.1.30
Y/Y
Hardcopy Grayscale Image Storage
1.2.840.10008.5.1.1.29
Y/Y
Hemodynamic Waveform Storage
1.2.840.10008.5.1.4.1.1.9.2.1
Y/Y
Key Object Selection Document
1.2.840.10008.5.1.4.1.1.88.59
Y/Y
Mammography CAD SR
1.2.840.10008.5.1.4.1.1.88.50
Y/Y
Multi-frame Single Bit Secondary Capture
Image Storage
1.2.840.10008.5.1.4.1.1.7.1
Y/Y
Multi-frame Grayscale Byte Secondary
Capture Image Storage
1.2.840.10008.5.1.4.1.1.7.2
Y/Y
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 14 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
SOP Class Name
SOP Class UID
SCU/SCP
Multi-frame Grayscale Word Secondary
Capture Image Storage
1.2.840.10008.5.1.4.1.1.7.3
Y/Y
Multi-frame True Color Secondary Capture
Image Storage
1.2.840.10008.5.1.4.1.1.7.4
Y/Y
MR Image Storage
1.2.840.10008.5.1.4.1.1.4
Y/Y
Nuclear Medicine Image Storage
1.2.840.10008.5.1.4.1.1.20
Y/Y
Nuclear Medicine Image Storage (Retired)
1.2.840.10008.5.1.4.1.1.5
Y/Y
Positron Emission Tomography Image
Storage
1.2.840.10008.5.1.4.1.1.128
Y/Y
RT Beams Treatment Record Storage
1.2.840.10008.5.1.4.1.1.481.4
Y/Y
RT Brachy Treatment Record Storage
1.2.840.10008.5.1.4.1.1.481.6
Y/Y
RT Dose Storage
1.2.840.10008.5.1.4.1.1.481.2
Y/Y
RT Image Storage
1.2.840.10008.5.1.4.1.1.481.1
Y/Y
RT Plan Storage
1.2.840.10008.5.1.4.1.1.481.5
Y/Y
RT Structure Set Storage
1.2.840.10008.5.1.4.1.1.481.3
Y/Y
RT Treatment Summary Record Storage
1.2.840.10008.5.1.4.1.1.481.7
Y/Y
Secondary Capture Image Storage
1.2.840.10008.5.1.4.1.1.7
Y/Y
Stand-alone Curve Storage
1.2.840.10008.5.1.4.1.1.9
Y/Y
Stand-alone Modality LUT Storage
1.2.840.10008.5.1.4.1.1.10
Y/Y
Stand-alone Overlay Storage
1.2.840.10008.5.1.4.1.1.8
Y/Y
Stand-alone VOI LUT Storage
1.2.840.10008.5.1.4.1.1.11
Y/Y
Standalone PET Curve Storage
1.2.840.10008.5.1.4.1.1.129
Y/Y
Stored Print Storage
1.2.840.10008.5.1.1.27
Y/Y
Ultrasound Image Storage
1.2.840.10008.5.1.4.1.1.6.1
Y/Y
Ultrasound Image Storage (Retired)
1.2.840.10008.5.1.4.1.1.6
Y/Y
Ultrasound Multi-frame Image Storage
1.2.840.10008.5.1.4.1.1.3.1
Y/Y
Ultrasound Multi-frame Image Storage
(Retired)
1.2.840.10008.5.1.4.1.1.3
Y/Y
VL Endoscopic Image Storage
1.2.840.10008.5.1.4.1.1.77.1.1
Y/Y
VL Microscopic Image Storage
1.2.840.10008.5.1.4.1.1.77.1.2
Y/Y
VL Slide-Coordinates Microscopic Image
Storage
1.2.840.10008.5.1.4.1.1.77.1.3
Y/Y
VL Photographic Image Storage
1.2.840.10008.5.1.4.1.1.77.1.4
Y/Y
X-Ray Angiographic Bi-Plane Image
Storage (retired)
1.2.840.10008.5.1.4.1.1.12.3
Y/Y
X-Ray Angiographic Image Storage
1.2.840.10008.5.1.4.1.1.12.1
Y/Y
X-Ray Radiofluoroscopic Image Storage
1.2.840.10008.5.1.4.1.1.12.2
Y/Y
Patient Root Query/Retrieve Information
Model – FIND
1.2.840.10008.5.1.4.1.2.1.1
N/Y
Patient Root Query/Retrieve Information
Model – MOVE
1.2.840.10008.5.1.4.1.2.1.2
N/Y
Patient Root Query/Retrieve Information
Model – GET
1.2.840.10008.5.1.4.1.2.1.3
N/Y
Query/Retrieve
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 15 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
SOP Class Name
SOP Class UID
SCU/SCP
Study Root Query/Retrieve Information
Model – FIND
1.2.840.10008.5.1.4.1.2.2.1
N/Y
Study Root Query/Retrieve Information
Model – MOVE
1.2.840.10008.5.1.4.1.2.2.2
N/Y
Study Root Query/Retrieve Information
Model – GET
1.2.840.10008.5.1.4.1.2.2.3
N/Y
Patient/Study Only Query/Retrieve
Information Model – FIND
1.2.840.10008.5.1.4.1.2.3.1
N/Y
Patient/Study Only Query/Retrieve
Information Model – MOVE
1.2.840.10008.5.1.4.1.2.3.2
N/Y
Patient/Study Only Query/Retrieve
Information Model – GET
1.2.840.10008.5.1.4.1.2.3.3
N/Y
1.2.840.10008.1.20.1
N/Y
1.2.840.10008.3.1.2.3.3
Y/Y
1.2.840.10008.1.9
Y/N
1.2.840.10008.5.1.4.31
Y/N
Storage Commitment
Storage Commitment Push Model
Study Management
Modality Performed Procedure Step
BSCN
Basic Study Content Notification
Modality Worklist
Modality Worklist Information Model –
FIND
3.1.1 Association Establishment Policies
3.1.1.1
General
The DICOM Component of the Enterprise Archive Manager will attempt to establish an
association anytime a C-MOVE request is received from a remote application entity in
order to store the requested data in the move. The archive will only attempt to
establish associations in response to valid C-MOVE requests for images that are
known to its database, or for response to valid Storage Commitment requests.
The archive will attempt to establish an association even if the destination is unknown
by pairing the requested destination with the IP address of the C-MOVE requestor
using the DICOM well-known port (104).
The DICOM Component supports SCU/SCP Role Negotiation.
The DICOM Component supports configurable Maximum PDU sizes, both sent and
received (the default is 50KB, both sent and received).
3.1.1.2
Number of Associations
The Enterprise Archive Manager will attempt only one storage association
establishment to service C-MOVE requests or Storage Commitment requests.
The Enterprise Archive Manager will accept any number of simultaneous associations,
the number of which can be configured. The maximum limit on the number of
simultaneous associations is dependent on the number of open file descriptors
allowed by the underlying operating system.
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 16 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
3.1.1.3
Asynchronous Nature
The Enterprise Archive Manager will allow any number of asynchronous operations,
whether invoked and performed. This number of asynchronous operations is
configurable. When establishing storage associations to service C-MOVE requests
the archive will attempt to negotiate the configured asynchronous operations window
in order to optimize object moves.
3.1.1.4
Implementation Identifying Information
The Enterprise Archive Manager DICOM Component will provide a single
Implementation Class UID and Implementation Version Name as follows:
DICOM Component Implementation Class UID
1.2.826.0.1.3680043.2.133.1.1
Implementation Version Name
5.30
3.1.2 Association Initiation by Real-World Activity
The Enterprise Archive Manager will attempt to initiate one storage association for
each C-MOVE request or Storage Commitment request that is received.
If the Router component is enabled, it is possible to configure it to utilize one or
multiple associations. For ease of implementation, most destinations are configured
to utilize one association.
3.1.2.1
Storage Association:
Completing a Move Request to a Remote System and
Unsolicited Storage of DICOM Objects to a Remote System
3.1.2.1.1
Associated Real-World Activity
The associated real-world activity is the receipt of a C-MOVE request from a remote
application entity.
Other components that may be installed in the Archive can cause associations to be
established for various reasons.
Router Plug-In
The Router Plug-In, if installed, establishes a pooled association to the configured CStore SCP(s) when an object is stored to the Archive. If an established association
exists in the association pool, the association is reused instead of establishing a new
association. The Router Plug-In then performs a C-Store on the pooled association(s)
to the configured SCP(s) for each object stored to the Archive.
3.1.2.1.2
Proposed Presentation Contexts
The Enterprise Archive Manager will propose a collection of presentation contexts,
which will be obtained by applying the algorithm presented in the next section to the
following Presentation Context Table:
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 17 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
Presentation Context Table
Abstract Syntax
Name
UID
Transfer Syntax
Role
Extended
Negotiation
12-lead ECG Waveform Storage
1.2.840.10008.5.1.4.1.1.9.1.1
See Table 3.1.2.1.2-1
SCU
None
Ambulatory ECG Waveform Storage
1.2.840.10008.5.1.4.1.1.9.1.3
See Table 3.1.2.1.2-1
SCU
None
Basic Study Content Notification
1.2.840.10008.1.9
See Table 3.1.2.1.2-1
SCU
None
Basic Text SR Storage
1.2.840.10008.5.1.4.1.1.88.11
See Table 3.1.2.1.2-1
SCU
None
Basic Voice Audio Waveform Storage
1.2.840.10008.5.1.4.1.1.9.4.1
See Table 3.1.2.1.2-1
SCU
None
Cardiac Electrophysiology Waveform
Storage
1.2.840.10008.5.1.4.1.1.9.3.1
See Table 3.1.2.1.2-1
SCU
None
Comprehensive SR Storage
1.2.840.10008.5.1.4.1.1.88.33
See Table 3.1.2.1.2-1
SCU
None
Computed Radiography Image
Storage
1.2.840.10008.5.1.4.1.1.1
See Table 3.1.2.1.2-1
SCU
None
CT Image Storage
1.2.840.10008.5.1.4.1.1.2
See Table 3.1.2.1.2-1
SCU
None
Digital X-Ray Image Storage
(Presentation)
1.2.840.10008.5.1.4.1.1.1.1
See Table 3.1.2.1.2-1
SCU
None
Digital X-Ray Image Storage
(Processing)
1.2.840.10008.5.1.4.1.1.1.1.1
See Table 3.1.2.1.2-1
SCU
None
Digital Mammography Image Storage
(Presentation)
1.2.840.10008.5.1.4.1.1.1.2
See Table 3.1.2.1.2-1
SCU
None
Digital Mammography Image Storage
(Processing)
1.2.840.10008.5.1.4.1.1.1.2.1
See Table 3.1.2.1.2-1
SCU
None
Digital Intra-oral X-Ray Image Storage
(Presentation)
1.2.840.10008.5.1.4.1.1.1.3
See Table 3.1.2.1.2-1
SCU
None
Digital Intra-oral X-Ray Image Storage
(Processing)
1.2.840.10008.5.1.4.1.1.1.3.1
See Table 3.1.2.1.2-1
SCU
None
Enhanced SR Storage
1.2.840.10008.5.1.4.1.1.88.22
See Table 3.1.2.1.2-1
SCU
None
General ECG Waveform Storage
1.2.840.10008.5.1.4.1.1.9.1.2
See Table 3.1.2.1.2-1
SCU
None
Grayscale Softcopy Presentation State
Storage
1.2.840.10008.5.1.4.1.1.11.1
See Table 3.1.2.1.2-1
SCU
None
Hardcopy Color Image Storage
1.2.840.10008.5.1.1.30
See Table 3.1.2.1.2-1
SCU
None
Hardcopy Grayscale Image Storage
1.2.840.10008.5.1.1.29
See Table 3.1.2.1.2-1
SCU
None
Hemodynamic Waveform Storage
1.2.840.10008.5.1.4.1.1.9.2.1
See Table 3.1.2.1.2-1
SCU
None
Key Object Selection Document
1.2.840.10008.5.1.4.1.1.88.59
See Table 3.1.2.1.2-1
SCU
None
Mammography CAD SR
1.2.840.10008.5.1.4.1.1.88.50
See Table 3.1.2.1.2-1
SCU
None
Multi-frame Single Bit Secondary
Capture Image Storage
1.2.840.10008.5.1.4.1.1.7.1
See Table 3.1.2.1.2-1
SCU
None
Multi-frame Grayscale Byte Secondary
Capture Image Storage
1.2.840.10008.5.1.4.1.1.7.2
See Table 3.1.2.1.2-1
SCU
None
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 18 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
Presentation Context Table
Abstract Syntax
Name
UID
Transfer Syntax
Role
Extended
Negotiation
Multi-frame Grayscale Word
Secondary Capture Image Storage
1.2.840.10008.5.1.4.1.1.7.3
See Table 3.1.2.1.2-1
SCU
None
Multi-frame True Color Secondary
Capture Image Storage
1.2.840.10008.5.1.4.1.1.7.4
See Table 3.1.2.1.2-1
SCU
None
MR Image Storage
1.2.840.100008.5.1.4.1.1.4
See Table 3.1.2.1.2-1
SCU
None
Nuclear Medicine Image Storage
1.2.840.10008.5.1.4.1.1.20
See Table 3.1.2.1.2-1
SCU
None
Nuclear Medicine Image Storage
(Retired)
1.2.840.10008.5.1.4.1.1.5
See Table 3.1.2.1.2-1
SCU
None
Positron Emission Tomography Image
Storage
1.2.840.10008.5.1.4.1.1.128
See Table 3.1.2.1.2-1
SCU
None
RT Beams Treatment Record Storage
1.2.840.10008.5.1.4.1.1.481.4
See Table 3.1.2.1.2-1
SCU
None
RT Brachy Treatment Record Storage
1.2.840.10008.5.1.4.1.1.481.6
See Table 3.1.2.1.2-1
SCU
None
RT Dose Storage
1.2.840.10008.5.1.4.1.1.481.2
See Table 3.1.2.1.2-1
SCU
None
RT Image Storage
1.2.840.10008.5.1.4.1.1.481.1
See Table 3.1.2.1.2-1
SCU
None
RT Plan Storage
1.2.840.10008.5.1.4.1.1.481.5
See Table 3.1.2.1.2-1
SCU
None
RT Structure Set Storage
1.2.840.10008.5.1.4.1.1.481.3
See Table 3.1.2.1.2-1
SCU
None
RT Treatment Summary Record
Storage
1.2.840.10008.5.1.4.1.1.481.7
See Table 3.1.2.1.2-1
SCU
None
Secondary Capture Image Storage
1.2.840.10008.5.1.4.1.1.7
See Table 3.1.2.1.2-1
SCU
None
Stand-alone Curve Storage
1.2.840.10008.5.1.4.1.1.9
See Table 3.1.2.1.2-1
SCU
None
Stand-alone Modality LUT Storage
1.2.840.10008.5.1.4.1.1.10
See Table 3.1.2.1.2-1
SCU
None
Stand-alone Overlay Storage
1.2.840.10008.5.1.4.1.1.8
See Table 3.1.2.1.2-1
SCU
None
Stand-alone VOI LUT Storage
1.2.840.10008.5.1.4.1.1.11
See Table 3.1.2.1.2-1
SCU
None
Standalone PET Curve Storage
1.2.840.10008.5.1.4.1.1.129
See Table 3.1.2.1.2-1
SCU
None
Stored Print Storage
1.2.840.10008.5.1.1.27
See Table 3.1.2.1.2-1
SCU
None
Ultrasound Image Storage
1.2.840.10008.5.1.4.1.1.6.1
See Table 3.1.2.1.2-1
SCU
None
Ultrasound Image Storage (Retired)
1.2.840.10008.5.1.4.1.1.6
See Table 3.1.2.1.2-1
SCU
None
Ultrasound Multi-frame Image Storage
1.2.840.10008.5.1.4.1.1.3.1
See Table 3.1.2.1.2-1
SCU
None
Ultrasound Multi-frame Image Storage
(Retired)
1.2.840.10008.5.1.4.1.1.3
See Table 3.1.2.1.2-1
SCU
None
VL Endoscopic Image Storage
1.2.840.10008.5.1.4.1.1.77.1.1
See Table 3.1.2.1.2-1
SCU
None
VL Microscopic Image Storage
1.2.840.10008.5.1.4.1.1.77.1.2
See Table 3.1.2.1.2-1
SCU
None
VL Slide-Coordinates Microscopic
Image Storage
1.2.840.10008.5.1.4.1.1.77.1.3
See Table 3.1.2.1.2-1
SCU
None
VL Photographic Image Storage
1.2.840.10008.5.1.4.1.1.77.1.4
See Table 3.1.2.1.2-1
SCU
None
X-Ray Angiographic Bi-Plane Image
Storage (retired)
1.2.840.10008.5.1.4.1.1.12.3
See Table 3.1.2.1.2-1
SCU
None
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 19 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
Presentation Context Table
Abstract Syntax
Name
UID
Transfer Syntax
Role
Extended
Negotiation
X-Ray Angiographic Image Storage
1.2.840.10008.5.1.4.1.1.12.1
See Table 3.1.2.1.2-1
SCU
None
X-Ray Radiofluoroscopic Image
Storage
1.2.840.10008.5.1.4.1.1.12.2
See Table 3.1.2.1.2-1
SCU
None
Table 3.1.2.1.2-1
Transfer Syntax for Send to a Remote System
Name
UID
Little Endian Explicit VR
1.2.840.10008.1.2.1
Little Endian Implicit VR
1.2.840.10008.1.2
Big Endian Explicit VR
1.2.840.10008.1.2.2
Deflated Little Endian Explicit VR
1.2.840.10008.1.2.1.99
Lossless JPEG Image Compression (baseline)
1.2.840.10008.1.2.4.70
Lossy JPEG Image Compression (8-bit, coding
Process 1)
1.2.840.10008.1.2.4.50
Lossy JPEG Image Compression (12-bit, coding
Process 4)
1.2.840.10008.1.2.4.51
JPEG 2000 Image Compression (Lossless Only)
1.2.840.10008.1.2.4.90
JPEG 2000 Image Compression
1.2.840.10008.1.2.4.91
Algorithm for Computing the Proposed Presentation Contexts for Outgoing Storage Associations
At the time of the association establishment, the set of DICOM objects to be sent out
has been determined. Since both the transfer syntax in which each DICOM object has
been stored and the SOP Class UID of each DICOM object are stored in the archives
database, both of these tags are already known. The intention of the algorithm is to
send out each object in the transfer syntax it has been initially stored in or a similar
one. So, we understand that if the object has been initially received in a supported
encapsulated transfer syntax, the algorithm would make sure that for the specific
abstract syntax, a presentation context with that particular transfer syntax has been
proposed. The encapsulated transfer syntax is preserved for efficiency, in order to
save the processing time of the compression conversion. In the case of objects stored
in a native transfer syntax, preserving the transfer syntax is not important, and any
native transfer syntax should be acceptable.
The archive will perform an analysis of the different encapsulated transfer syntaxes for
each abstract syntax, and it will propose one presentation context for each
encapsulated transfer syntax class recorded, plus a context with the list of all the other
supported transfer syntaxes. This at least creates the possibility for each desired
presentation context to be accepted. As an example, let us assume that the retrieve
set of a C-Move request contains Ultrasound Multi-Frame objects stored in both the
Lossless JPEG transfer syntax and the Lossy JPEG transfer syntax coding Process 1.
Three presentation contexts will be proposed for the Ultrasound Multi-Frame abstract
syntax: one with the Lossless JPEG transfer syntax, one with the Lossy JPEG transfer
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 20 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
syntax coding Process 1, and one containing a list of all the other supported native
transfer syntaxes.
Once the association negotiation is complete, some presentation contexts will be
accepted and some will not. For datasets that had DICOM objects stored in different
transfer syntaxes for the same abstract class, a heuristic will need to be applied in
order to select the appropriate presentation context. The configurable
TransferSyntaxPriorityList property controls the choosing of the appropriate
presentation context. For each transfer syntax UID, a list of transfer syntax lists will be
provided. The User Service will be created on the first available (accepted)
presentation context obtained from parsing the priority list (i.e. the list of transfer
syntaxes is parsed and the first presentation context that matches in the accepted
transfer syntax is used). The first entry in the list should be the same as the transfer
syntax used as key, at least in the case of encapsulated transfer syntaxes.
Algorithm for Computing the Proposed Presentation Contexts for Outgoing Router PlugIn
Storage Associations
At the time of pooled association establishment, the Router has no knowledge of all
the objects to be stored on the association. Therefore, the Router must propose
presentation contexts for all storage SOP classes supported by the Archive with a list
of native transfer syntaxes in the order specified by the Archive DICOM Component.
The Router will always propose the default storage transfer syntax configured for the
Archive even if it is encapsulated transfer syntax.
When the Router encounters an object stored in encapsulated transfer syntax, the
Router will designate the object’s SOP class as special. The Router will then, in
addition to the above, propose presentation contexts for each special designated SOP
class, and each encapsulated transfer syntax supported by the Archive.
3.1.2.2
Completing Storage Commitment Request from a Remote System
3.1.2.2.1
Associated Real-World Activity
The associated real-world activity is the response to a Storage Commitment request
from a remote application entity.
3.1.2.2.2
Proposed Presentation Contexts
The following presentation contexts will be proposed for each association:
Presentation Context Table
Abstract Syntax
Name
Storage
Commitment
Push Model
UID
1.2.840.10008.1.20.1
Transfer Syntax
Name
UID
Little Endian Explicit VR
1.2.840.10008.1.2.1
Little Endian Implicit VR
1.2.840.10008.1.2
Big Endian Explicit VR
1.2.840.10008.1.2.2
Deflated Little Endian
Explicit VR
1.2.840.10008.1.2.1.99
Role
SCP
Extended
Negotiation
None
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 21 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
3.1.2.3
Forwarding MPPS Messages
3.1.2.3.1
Associated Real-World Activity
The Router PlugIn schedules and forwards messages to the DSS/Order Filler or any
other MPPS SCP The Router PlugIn provides reliable delivery of PPS messages in
the event the DSS/Order Filler or any MPPS SCP is unable to accept a message.
3.1.2.3.2
Proposed Presentation Contexts
The Router PlugIn will propose the following Transfer Syntaxes for each presentation
context in an association it initiates:
Presentation Context Table
Abstract Syntax
Name
Modality
Performed
Procedure Step
Transfer Syntax
UID
1.2.840.10008.3.1.2.3.3
Name
UID
Little Endian Explicit VR
1.2.840.10008.1.2.1
Little Endian Implicit VR
1.2.840.10008.1.2
Big Endian Explicit VR
1.2.840.10008.1.2.2
Deflated Little Endian
Explicit VR
1.2.840.10008.1.2.1.99
3.1.2.4
Retrieve a Modality Worklist from a Remote System
3.1.2.4.1
Associated Real-World Activity
Role
SCU
Extended
Negotiation
None
The Modality Worklist Reconciliation component of the Enterprise Archive, if installed
and configured, will cause an association to be established to a Modality Worklist SCP
each time a new study is stored to the Archive. The Modality Worklist Reconciliation
component will query the Modality Worklist SCP for demographic and other data
relating to that study.
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 22 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
3.1.2.4.2
Proposed Presentation Contexts
The following presentation contexts will be proposed for each association:
Presentation Context Table
Abstract Syntax
Name
Transfer Syntax
UID
Modality
Worklist
Information
Model – FIND
1.2.840.10008.5.1.4.31
Name
UID
Little Endian Explicit VR
1.2.840.10008.1.2.1
3.1.2.5
Send Basic Study Content Notification to a Remote System
3.1.2.5.1
Associated Real-World Activity
Role
SCU
Extended
Negotiation
None
The BSCN component of the Enterprise Archive, if installed and configured, will cause
a BSCN dataset to be stored to a configurable number of destination Application
Entities. When the Archive receives an object a timing interval, set to a configurable
value, is associated with the study to which that object belongs. If that study is already
associated with a timing interval, that timing interval is reset. When a timing interval
expires, a BSCN object is generated for the associated study and stored to each of
the configured destination Application Entities.
In addition to its default behavior, the BSCN component is also configurable to
immediately generate and send a BSCN object whenever the first image of a new
study arrives at the Archive.
3.1.2.5.2
Proposed Presentation Contexts
The following presentation contexts will be proposed for each association:
Presentation Context Table
Abstract Syntax
Name
Basic Study
Content
Notification
UID
1.2.840.10008.1.9
Transfer Syntax
Name
Little Endian Explicit VR
UID
1.2.840.10008.1.2.1
Role
SCU
Extended
Negotiation
None
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 23 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
3.1.3 Association Acceptance Policy
When the Enterprise Archive Manager accepts an association, it will allow the storage
of objects, the retrieval of objects previously stored, the query for information about
stored objects, the verification of the archive, and the storage commitment of stored
object.
The Enterprise Archive Manager is configurable to allow security restrictions ranging
from no restrictions (promiscuous) to limiting a particular remote application entity to
specified SOP classes and specified SCU/SCP roles. If security is turned on,
association attempts by unknown entities will be rejected outright and proposed
presentation contexts from known remote application entities may be rejected based
on their allowed security permissions.
3.1.3.1
Respond to a Verification Request from a Remote System
3.1.3.1.1
Associated Real-World Activity
When the Enterprise Archive Manager receives a verification request (C-ECHO) it will
respond with a status of success if possible.
3.1.3.1.2
Presentation Context Table
The Enterprise Archive Manager will accept the following Transfer Syntaxes for each
presentation context in an association it receives:
Presentation Context Table
Abstract Syntax
Name
Verification
3.1.3.1.3
UID
1.2.840.10008.1.1
Transfer Syntax
Name
UID
Little Endian Explicit VR
1.2.840.10008.1.2.1
Little Endian Implicit VR
1.2.840.10008.1.2
Big Endian Explicit VR
1.2.840.10008.1.2.2
Deflated Little Endian
Explicit VR
1.2.840.10008.1.2.1.99
Extended
Negotiation
Role
SCP
None
SOP Specific Conformance for Verification SOP Class
The Enterprise Archive Manager conforms to the SOP of the Verification Service
Class fully.
Extended negotiation is not supported for the Verification Service Class.
If the Enterprise Archive Manager returns anything other than success then the CECHO operation failed.
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 24 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
3.1.3.1.4
Presentation Context Acceptance Criterion
There is no prioritization used for the acceptance of presentation contexts. Any
combination of supported transfer syntax and abstract syntax is accepted, in case the
product is configured for them.
3.1.3.1.5
Transfer Syntax Selection Policies
The Enterprise DICOM Archive Manager selects transfer syntaxes in Acceptor first
mode: the first transfer syntax in the archive’s list of allowable transfer syntaxes that
also exists in the proposed transfer syntax list will be selected.
3.1.3.2
Receive Objects from a Remote System
3.1.3.2.1
Associated Real-World Activity
When the Enterprise DICOM Archive Manager receives a storage request (C-STORE)
for an object, that object is stored to media on the underlying platform in DICOM Part
10 format and registers the object in the underlying database. If it is unable to store
the object a failure response will be returned and the object will be stored in an
exceptions area on the underlying platform if possible.
The data set of the C-STORE command is stored with no loss of information.
3.1.3.2.2
Presentation Context Table
The Enterprise Archive Manager will accept the following Transfer Syntaxes for each
presentation context in an association it receives:
Presentation Context Table
Abstract Syntax
Name
UID
Transfer Syntax
Role
Extended
Negotiation
12-lead ECG Waveform Storage
1.2.840.10008.5.1.4.1.1.9.1.1
See Table 3.1.3.2.2-1
SCP
None
Ambulatory ECG Waveform
Storage
1.2.840.10008.5.1.4.1.1.9.1.3
See Table 3.1.3.2.2-1
SCP
None
Basic Study Content Notification
1.2.840.10008.1.9
See Table 3.1.3.2.2-1
SCP
None
Basic Text SR Storage
1.2.840.10008.5.1.4.1.1.88.11
See Table 3.1.3.2.2-1
SCP
None
Basic Voice Audio Waveform
Storage
1.2.840.10008.5.1.4.1.1.9.4.1
See Table 3.1.3.2.2-1
SCP
None
Cardiac Electrophysiology
Waveform Storage
1.2.840.10008.5.1.4.1.1.9.3.1
See Table 3.1.3.2.2-1
SCP
None
Comprehensive SR Storage
1.2.840.10008.5.1.4.1.1.88.33
See Table 3.1.3.2.2-1
SCP
None
Computed Radiography Image
Storage
1.2.840.10008.5.1.4.1.1.1
See Table 3.1.3.2.2-1
SCP
None
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 25 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
Presentation Context Table
Abstract Syntax
Name
UID
Transfer Syntax
Role
Extended
Negotiation
CT Image Storage
1.2.840.10008.5.1.4.1.1.2
See Table 3.1.3.2.2-1
SCP
None
Digital X-Ray Image Storage
(Presentation)
1.2.840.10008.5.1.4.1.1.1.1
See Table 3.1.3.2.2-1
SCP
None
Digital X-Ray Image Storage
(Processing)
1.2.840.10008.5.1.4.1.1.1.1.1
See Table 3.1.3.2.2-1
SCP
None
Digital Mammography Image
Storage (Presentation)
1.2.840.10008.5.1.4.1.1.1.2
See Table 3.1.3.2.2-1
SCP
None
Digital Mammography Image
Storage (Processing)
1.2.840.10008.5.1.4.1.1.1.2.1
See Table 3.1.3.2.2-1
SCP
None
Digital Intra-oral X-Ray Image
Storage (Presentation)
1.2.840.10008.5.1.4.1.1.1.3
See Table 3.1.3.2.2-1
SCP
None
Digital Intra-oral X-Ray Image
Storage (Processing)
1.2.840.10008.5.1.4.1.1.1.3.1
See Table 3.1.3.2.2-1
SCP
None
Enhanced SR Storage
1.2.840.10008.5.1.4.1.1.88.22
See Table 3.1.3.2.2-1
SCP
None
General ECG Waveform Storage
1.2.840.10008.5.1.4.1.1.9.1.2
See Table 3.1.3.2.2-1
SCP
None
Grayscale Softcopy Presentation
State Storage
1.2.840.10008.5.1.4.1.1.11.1
See Table 3.1.3.2.2-1
SCP
None
Hardcopy Color Image Storage
1.2.840.10008.5.1.1.30
See Table 3.1.3.2.2-1
SCP
None
Hardcopy Grayscale Image
Storage
1.2.840.10008.5.1.1.29
See Table 3.1.3.2.2-1
SCP
None
Hemodynamic Waveform Storage
1.2.840.10008.5.1.4.1.1.9.2.1
See Table 3.1.3.2.2-1
SCP
None
Key Object Selection Document
1.2.840.10008.5.1.4.1.1.88.59
See Table 3.1.3.2.2-1
SCP
None
Mammography CAD SR
1.2.840.10008.5.1.4.1.1.88.50
See Table 3.1.3.2.2-1
SCP
None
Multi-frame Single Bit Secondary
Capture Image Storage
1.2.840.10008.5.1.4.1.1.7.1
See Table 3.1.3.2.2-1
SCP
None
Multi-frame Grayscale Byte
Secondary Capture Image Storage
1.2.840.10008.5.1.4.1.1.7.2
See Table 3.1.3.2.2-1
SCP
None
Multi-frame Grayscale Word
Secondary Capture Image Storage
1.2.840.10008.5.1.4.1.1.7.3
See Table 3.1.3.2.2-1
SCP
None
Multi-frame True Color Secondary
Capture Image Storage
1.2.840.10008.5.1.4.1.1.7.4
See Table 3.1.3.2.2-1
SCP
None
MR Image Storage
1.2.840.100008.5.1.4.1.1.4
See Table 3.1.2.1.2-1
SCP
None
Nuclear Medicine Image Storage
1.2.840.10008.5.1.4.1.1.20
See Table 3.1.2.1.2-1
SCP
None
Nuclear Medicine Image Storage
(Retired)
1.2.840.10008.5.1.4.1.1.5
See Table 3.1.2.1.2-1
SCP
None
Positron Emission Tomography
Image Storage
1.2.840.10008.5.1.4.1.1.128
See Table 3.1.2.1.2-1
SCP
None
See Table 3.1.3.2.2-1
SCP
None
RT Beams Treatment Record
Storage
1.2.840.10008.5.1.4.1.1.481.4
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 26 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
Presentation Context Table
Abstract Syntax
Name
UID
Transfer Syntax
Role
Extended
Negotiation
RT Brachy Treatment Record
Storage
1.2.840.10008.5.1.4.1.1.481.6
See Table 3.1.3.2.2-1
SCP
None
RT Dose Storage
1.2.840.10008.5.1.4.1.1.481.2
See Table 3.1.3.2.2-1
SCP
None
RT Image Storage
1.2.840.10008.5.1.4.1.1.481.1
See Table 3.1.3.2.2-1
SCP
None
RT Plan Storage
1.2.840.10008.5.1.4.1.1.481.5
See Table 3.1.3.2.2-1
SCP
None
RT Structure Set Storage
1.2.840.10008.5.1.4.1.1.481.3
See Table 3.1.3.2.2-1
SCP
None
RT Treatment Summary Record
Storage
1.2.840.10008.5.1.4.1.1.481.7
See Table 3.1.3.2.2-1
SCP
None
Secondary Capture Image Storage
1.2.840.10008.5.1.4.1.1.7
See Table 3.1.3.2.2-1
SCP
None
Stand-alone Curve Storage
1.2.840.10008.5.1.4.1.1.9
See Table 3.1.3.2.2-1
SCP
None
Stand-alone Modality LUT Storage
1.2.840.10008.5.1.4.1.1.10
See Table 3.1.3.2.2-1
SCP
None
Stand-alone Overlay Storage
1.2.840.10008.5.1.4.1.1.8
See Table 3.1.3.2.2-1
SCP
None
Stand-alone VOI LUT Storage
1.2.840.10008.5.1.4.1.1.11
See Table 3.1.3.2.2-1
SCP
None
Standalone PET Curve Storage
1.2.840.10008.5.1.4.1.1.129
See Table 3.1.3.2.2-1
SCP
None
Stored Print Storage
1.2.840.10008.5.1.1.27
See Table 3.1.3.2.2-1
SCP
None
Ultrasound Image Storage
1.2.840.10008.5.1.4.1.1.6.1
See Table 3.1.3.2.2-1
SCP
None
Ultrasound Image Storage
(Retired)
1.2.840.10008.5.1.4.1.1.6
See Table 3.1.3.2.2-1
SCP
None
Ultrasound Multi-frame Image
Storage
1.2.840.10008.5.1.4.1.1.3.1
See Table 3.1.3.2.2-1
SCP
None
Ultrasound Multi-frame Image
Storage (Retired)
1.2.840.10008.5.1.4.1.1.3
See Table 3.1.3.2.2-1
SCP
None
VL Endoscopic Image Storage
1.2.840.10008.5.1.4.1.1.77.1.1
See Table 3.1.3.2.2-1
SCP
None
VL Microscopic Image Storage
1.2.840.10008.5.1.4.1.1.77.1.2
See Table 3.1.3.2.2-1
SCP
None
VL Slide-Coordinates Microscopic
Image Storage
1.2.840.10008.5.1.4.1.1.77.1.3
See Table 3.1.3.2.2-1
SCP
None
VL Photographic Image Storage
1.2.840.10008.5.1.4.1.1.77.1.4
See Table 3.1.3.2.2-1
SCP
None
X-Ray Angiographic Bi-Plane
Image Storage (retired)
1.2.840.10008.5.1.4.1.1.12.3
See Table 3.1.3.2.2-1
SCP
None
X-Ray Angiographic Image Storage
1.2.840.10008.5.1.4.1.1.12.1
See Table 3.1.3.2.2-1
SCP
None
X-Ray Radiofluoroscopic Image
Storage
1.2.840.10008.5.1.4.1.1.12.2
See Table 3.1.3.2.2-1
SCP
None
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 27 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
Table 3.1.3.2.2-1
Transfer Syntax for Send to a Remote System
Name
3.1.3.2.3
UID
Little Endian Explicit VR
1.2.840.10008.1.2.1
Little Endian Implicit VR
1.2.840.10008.1.2
Big Endian Explicit VR
1.2.840.10008.1.2.2
Deflated Little Endian Explicit VR
1.2.840.10008.1.2.1.99
Lossless JPEG Image Compression (baseline)
1.2.840.10008.1.2.4.70
Lossy JPEG Image Compression (8-bit, coding
Process 1)
1.2.840.10008.1.2.4.50
Lossy JPEG Image Compression (12-bit, coding
Process 4)
1.2.840.10008.1.2.4.51
JPEG 2000 Image Compression (Lossless Only)
1.2.840.10008.1.2.4.90
JPEG 2000 Image Compression
1.2.840.10008.1.2.4.91
SOP Specific Conformance for all Storage SOP Classes
The Enterprise Archive Manager DICOM component conforms to the SOP’s of the
Storage Service Class at Level 2 (full). No elements are discarded or coerced, unless
explicitly configured to do so. Discarding offending DICOM elements (invalid tags) or
coercing some data elements to address customer needs is possible; however, it can
be done only with Emageon’s direct involvement, and it implies custom
implementations of coercion strategies.
In the event of a successful C-STORE operation, the object is fully stored to the
underlying platform’s media in Part 10 format and is accessible either as a file or
through the archive. If the DICOM object has been received in the archive using a
supported native transfer syntax, the transfer syntax used for the Part 10 format will
always be JPEG 2000 Image Compression(Lossless Only). However, If the DICOM
object has been received using an encapsulated transfer syntax, Lossless JPEG or
Lossy JPEG Image Compression coding Process 1 or coding Process 4, then the Part
10 object will be stored using the same transfer syntax.
The archive performs minimal object validation to ensure database integrity.
Additional validation may be configured to prevent the object from being stored in the
archive.
Extended negotiation is not supported for Storage Service Classes.
If the Enterprise Archive Manager returns one of the following status codes, then the
C-STORE operation was unsuccessful. If possible the offending object will be stored
in the exceptions area on the underlying platform. All status codes are in hexadecimal.
0110 (Processing Failure) – Indicates that an unknown error occurred during the
storage of the received object.
A900 (SOP Class UID Mismatch) – Indicates that the SOP Class UID of the object
received did not match the presentation context over which the object arrived. The
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 28 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
Error Comment field of the status will be populated with a description of the error
encountered.
C000 (Data Set Read Error) – Indicates that the archive encountered an error while
reading the object’s data set. This may be returned if the data set is corrupted. The
Error Comment field of the status will be populated with a description of the error
encountered.
C001 (SOP Instance UID Mismatch) – Indicates that the SOP Instance UID of the
object received did not match the SOP Instance UID sent in the C-STORE command.
The Error Comment field of the status will be populated with a description of the error
encountered.
C002 (Cannot Understand) – Indicates that an unknown error was thrown from within
the archive. The Error Comment field of the status will be populated with a description
of the error encountered.
If the Enterprise Archive Manager returns the following status code it indicates that the
C-STORE operation was a success but there were warnings. All status codes are in
hexadecimal.
B007 (Data Set Does Not Match SOP Class) – Indicates that the object received did
not fully match the SOP Class of the object, but the mismatch was not significant
enough to warrant an exception.
Implementation specifics for Person Names
The values of data elements with a VR of PN (Person Name) will be stored in a
canonical format. Only the StandardName will be stored, and all Name Components
will be stored regardless of their value, separated by the caret character (‘^’). This
normalizes the names, always appending the trailing caret characters. As an example,
the following names are equivalent: LN^FN, LN^FN^, LN^FN^^, LN^FN^^^ and will all
be stored in the database layer as LN^FN^^^. The stored person name will also be
uppercased.
3.1.3.2.4
Presentation Context Acceptance Criterion
There is no prioritization used for the acceptance of presentation contexts. Any
combination of supported transfer syntax and abstract syntax is accepted, in case the
product is configured for them.
3.1.3.2.5
Transfer Syntax Selection Policies
The Enterprise Archive Manager DICOM component selects transfer syntaxes in
Acceptor first mode: the first transfer syntax in the archive’s list of allowable transfer
syntaxes that also exists in the proposed transfer syntax list will be selected.
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 29 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
3.1.3.3
Response to a Query Request from a Remote System
3.1.3.3.1
Associated Real-World Activity
When the Enterprise Archive Manager receives a query request (C-FIND) it will
resolve the request against the underlying database and return all found information to
the query initiator. The archive supports query transactions for all stored DICOM
composite objects.
3.1.3.3.2
Presentation Context Table
The Enterprise DICOM Archive Manager will accept the following Transfer Syntaxes
for each presentation context in an association it receives:
Presentation Context Table
Abstract Syntax
Name
Patient Root
Query/Retrieve
Information
Model – FIND
Study Root
Query/Retrieve
Information
Model – FIND
Patient/Study
Only
Query/Retrieve
Information
Model – FIND
UID
1.2.840.10008.5.1.4.1.2.1.1
1.2.840.10008.5.1.4.1.2.2.1
1.2.840.10008.5.1.4.1.2.3.1
Transfer Syntax
Name
UID
Little Endian Explicit VR
1.2.840.10008.1.2.1
Little Endian Implicit VR
1.2.840.10008.1.2
Big Endian Explicit VR
1.2.840.10008.1.2.2
Deflated Little Endian
Explicit VR
1.2.840.10008.1.2.1.99
Little Endian Explicit VR
1.2.840.10008.1.2.1
Little Endian Implicit VR
1.2.840.10008.1.2
Big Endian Explicit VR
1.2.840.10008.1.2.2
Deflated Little Endian
Explicit VR
1.2.840.10008.1.2.1.99
Little Endian Explicit VR
1.2.840.10008.1.2.1
Little Endian Implicit VR
1.2.840.10008.1.2
Big Endian Explicit VR
1.2.840.10008.1.2.2
Deflated Little Endian
Explicit VR
1.2.840.10008.1.2.1.99
Role
Extended
Negotiation
SCP
Relational
SCP
Relational
SCP
Relational
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 30 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
3.1.3.3.3
SOP Specific Conformance for all Find SOP Classes
The Enterprise Archive Manager conforms to the SOP’s of the Query/Retrieve Service
Class at both the hierarchical and relational level.
SOP Extended Negotiation
Item bytes
Field Name
Description of Field
1
Relationalqueries/retrieval
This byte field defines relational-query/retrieval support for
the
Association-acceptor. It shall be encoded as an
unsigned binary integer and shall use one of the
following values
0 - relational-queries/retrieval not supported
1 - relational-queries/retrieval supported
Query Modes
The Enterprise Archive Manager supports both the Hierarchical and Relational search
modes.
Information Models
The Enterprise Archive Manager supports the Patient Root, Study Root, and PatientStudy Only information models.
Table 3.1.3.3.3-1
Patient Root Image C-FIND Supported Attributes
Attribute Name
Patient Level
Patient Name
Patient ID
Referenced Patient Sequence
Referenced SOP Class UID
Referenced SOP Instance UID
Patient’s Birth Date
Patient’s Birth Time
Patient’s Sex
Other Patient IDs
Other Patient Names
Ethnic Group
Patient Comments
Number of Patient Related Studies
Number of Patient Related Series
Number of Patient Related Instances
Study Level
Study Date
Study Time
Accession Number
Study ID
Study Instance UID
Tag
Query Keys
Matching
SCP
Query Keys
Return
SCP
(0010, 0010)
(0010, 0020)
(0008, 1120)
(0008, 1150)
(0008, 1155)
(0010, 0030)
(0010, 0032)
(0010, 0040)
(0010, 1000)
(0010, 1001)
(0010, 2160)
(0010, 4000)
(0020, 1200)
(0020, 1202)
(0020, 1204)
Supported
Supported (U)
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
(0008, 0020)
(0008, 0030)
(0008, 0050)
(0020, 0010)
(0020, 000D)
Supported
Supported
Supported
Supported
Supported (U)
Supported
Supported
Supported
Supported
Supported
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 31 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
Attribute Name
Modalities in Study
Referring Physician’s Name
Study Description
Procedure Code Sequence
Code Value
Coding Scheme Designator
Coding Scheme Version
Code Meaning
Name of Physician(s) Reading Study
Admitting Diagnoses Description
Referred Study Sequence
Referenced SOP Class UID
Referenced SOP Instance UID
Patient’s Age
Patient’s Size
Patient’s Weight
Occupation
Additional Patient History
Other Study Numbers
Number of Study Related Series
Number of Study Related Instances
Interpretation Author
Series Level
Modality
Series Number
Series Instance UID
Number of Series Related Instances
Performed Procedure Step ID
Reference Study Component Sequence
Referenced SOP Class UID
Referenced SOP Instance UID
Request Attribute Sequence
Requested Procedure ID
Scheduled Procedure Step ID
Performed Procedure Step Start Date
Performed Procedure Step Start Time
Body Part Examined
Station Name
Institution Name
Performing Physician’s Name
Manufacturer
Manufacturer’s Model Name
Series Description
Series Date
Series Time
Protocol Name
Composite Object Instance Level
Instance Number
Overlay Number
Curve Number
(0008, 0061)
(0008, 0090)
(0008, 1030)
(0008, 1032)
(0008, 0100)
(0008, 0102)
(0008, 0103)
(0008, 0104)
(0008, 1060)
(0008, 1080)
(0008, 1110)
(0008, 1150)
(0008, 1155)
(0010, 1010)
(0010, 1020)
(0010, 1030)
(0010, 2180)
(0010, 21B0)
(0020, 1070)
(0020, 1206)
(0020, 1208)
(4008, 010C)
Query Keys
Matching
SCP
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Query Keys
Return
SCP
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
(0008, 0060)
(0020, 0011)
(0020, 000E)
(0020, 1209)
(0040, 0253)
(0008, 1111)
(0008, 1150)
(0008, 1155)
(0040, 0275)
(0040, 1001)
(0040, 0009)
(0040, 0244)
(0040, 0245)
(0018, 0015)
(0008, 1010)
(0008, 0080)
(0008, 1050)
(0008, 0070)
(0008, 1090)
(0008, 103E)
(0008, 0021)
(0008, 0031)
(0018, 1030)
Supported
Supported
Supported (U)
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
(0020, 0013)
(0020, 0022)
(0020, 0024)
Supported
Supported
Supported
Supported
Supported
Supported
Tag
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 32 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
Attribute Name
LUT Number
SOP Instance UID
SOP Class UID
Image Specific Level
Rows
Columns
Bits Allocated
Number of Frames
(0020, 0026)
(0008, 0018)
(0008, 0016)
Query Keys
Matching
SCP
Supported
Supported (U)
Supported
Query Keys
Return
SCP
Supported
Supported
Supported
(0020, 0010)
(0020, 0011)
(0028, 0100)
(0028, 0008)
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Tag
(U) = Unique
Table 3.1.3.3.3-2
Study Root Image C-FIND Supported Attributes
Attribute Name
Study Level
Study Date
Study Time
Accession Number
Patient Name
Patient ID
Study ID
Study Instance UID
Modalities in Study
Referring Physician’s Name
Study Description
Procedure Code Sequence
Code Value
Coding Scheme Designator
Coding Scheme Version
Code Meaning
Name of Physician(s) Reading Study
Admitting Diagnoses Description
Referred Study Sequence
Referenced SOP Class UID
Referenced SOP Instance UID
Referenced Patient Sequence
Referenced SOP Class UID
Referenced SOP Instance UID
Referenced SOP Instance UID
Patient’s Birth Date
Patient’s Birth Time
Patient’s Sex
Other Patient IDs
Other Patient Names
Patient’s Age
Patient’s Size
Patient’s Weight
Ethnic Group
Tag
(0008, 0020)
(0008, 0030)
(0008, 0050)
(0010, 0010)
(0010, 0020)
(0020, 0010)
(0020, 000D)
(0008, 0061)
(0008, 0090)
(0008, 1030)
(0008, 1032)
(0008, 0100)
(0008, 0102)
(0008, 0103)
(0008, 0104)
(0008, 1060)
(0008, 1080)
(0008, 1110)
(0008, 1150)
(0008, 1155)
(0008, 1120)
(0008, 1150)
(0008, 1155)
(0008, 1155)
(0010, 0030)
(0010, 0032)
(0010, 0040)
(0010, 1000)
(0010, 1001)
(0010, 1010)
(0010, 1020)
(0010, 1030)
(0010, 2160)
Query Keys
Matching
SCP
Supported
Supported
Supported
Supported
Supported (U)
Supported
Supported (U)
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Query Keys
Return
SCP
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 33 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
Attribute Name
Occupation
Additional Patient History
Patient Comments
Other Study Numbers
Number of Patient Related Studies
Number of Patient Related Series
Number of Patient Related Instances
Number of Study Related Series
Number of Study Related Instances
Interpretation Author
Series Level
Modality
Series Number
Series Instance UID
Number of Series Related Instances
Performed Procedure Step ID
Reference Study Component Sequence
Referenced SOP Class UID
Referenced SOP Instance UID
Request Attribute Sequence
Requested Procedure ID
Scheduled Procedure Step ID
Performed Procedure Step Start Date
Performed Procedure Step Start Time
Body Part Examined
Station Name
Institution Name
Performing Physician’s Name
Manufacturer
Manufacturer’s Model Name
Series Description
Series Date
Series Time
Protocol Name
Composite Object Instance Level
Instance Number
Overlay Number
Curve Number
LUT Number
SOP Instance UID
SOP Class UID
Image Specific Level
Rows
Columns
Bits Allocated
Number of Frames
Tag
Query Keys
Matching
SCP
Query Keys
Return
SCP
(0010, 2180)
(0010, 21B0)
(0010, 4000)
(0020, 1070)
(0020, 1200)
(0020, 1202)
(0020, 1204)
(0020, 1206)
(0020, 1208)
(4008, 010C)
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
(0008, 0060)
(0020, 0011)
(0020, 000E)
(0020, 1209)
(0040, 0253)
(0008, 1111)
(0008, 1150)
(0008, 1155)
(0040, 0275)
(0040, 1001)
(0040, 0009)
(0040, 0244)
(0040, 0245)
(0018, 0015)
(0008, 1010)
(0008, 0080)
(0008, 1050)
(0008, 0070)
(0008, 1090)
(0008, 103E)
(0008, 0021)
(0008, 0031)
(0018, 1030)
Supported
Supported
Supported (U)
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
(0020, 0013)
(0020, 0022)
(0020, 0024)
(0020, 0026)
(0008, 0018)
(0008, 0016)
Supported
Supported
Supported
Supported
Supported (U)
Supported
Supported
Supported
Supported
Supported
Supported
Supported
(0020, 0010)
(0020, 0011)
(0028, 0100)
(0028, 0008)
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
(U) = Unique
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 34 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
Patient/Study Only Image C-FIND Supported Attributes
Attributes for the Patient and Study Levels of the Patient/Study Only Query/Retrieve
Information Model are the same as the corresponding attributes for the Patient and
Study Levels of the Patient Root Query/Retrieve Information Model. For information
about these attributes, see the Patient Root Image C-FIND Supported Attributes
table (Table 3.1.3.3.3-1).
.
Table 3.1.3.3.3-3
Grayscale Soft Copy Presentation State C-FIND Supported Attributes
Attribute Name
GSPS Instance Specific Level
Presentation Label
Presentation Description
Presentation Creation Date
Presentation Creation Time
Presentation Creator’s Name
Referenced Series Sequence
>Series Instance UID
>Referenced Image Sequence
>>Referenced SOP Class UID
>>Referenced SOP Instance UID
Table 3.1.3.3.3-4
Tag
(0070, 0080)
(0070, 0081)
(0070, 0082)
(0070, 0083)
(0070, 0084)
(0008, 1115)
(0020, 000E)
(0008, 1140)
(0008, 1150)
(0008, 1155)
Query Keys
Matching
SCP
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Query Keys
Return
SCP
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Basic Text SR and Enhanced SR C-FIND Supported Attributes
Attribute Name
SR Instance Specific Level
Completion Flag
Verification Flag
Content Date
Content Time
Observation Date Time
Verifying Observer Sequence
>Verifying Organization
>Verification DateTime
>Verifying Observer Name
>Verifying Observer Identification Code
Sequence
Referenced Request Sequence
>Study Instance UID
>Accession Number
>Requested Procedure ID
>Requested Procedure Code Sequence
>>Code Value
>>Code Scheme Designator
>>Code Scheme Version
>>Code Meaning
Tag
Query Keys
Matching
SCP
Query Keys
Return
SCP
(0040, A491)
(0040, A493)
(0008, 0023)
(0008, 0033)
(0040, A032)
(0040, A073)
(0040, A027)
(0040, A030)
(0040, A075)
(0040, A088)
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
(0040, A370)
(0020, 000D)
(0008, 0050)
(0040, 1000)
(0032, 1064)
(0008, 0100)
(0008, 0102)
(0008, 0103)
(0008, 0104)
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 35 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
Attribute Name
Concept Name Code Sequence
>Code Value
>Coding Scheme Designator
>Coding Scheme Version
>Code Meaning
Tag
(0040, A043)
(0008, 0100)
(0008, 0102)
(0008, 0103)
(0008, 0104)
Query Keys
Matching
SCP
Supported
Supported
Supported
Supported
Supported
Query Keys
Return
SCP
Supported
Supported
Supported
Supported
Supported
C-FIND Status Codes
If the Enterprise DICOM Archive Manager returns one of the following status codes for
C-FIND then the operation was unsuccessful. All status codes are in hexadecimal.
0110(Processing Failure) – Indicates that an unknown error occurred during the query.
C000 (Data Set Read Error) – Indicates that there was an error reading the query
parameters data set. This may be returned if the data set is corrupted. The Error
Comment field of the status will be populated with a description of the error
encountered.
C001 (Unable To Process) – Indicates that the archive was unable to fully process the
query. The Error Comment field of the status will be populated with a description of the
error encountered.
A900 (Identifier Does Not Match SOP Class) – Indicates that the query parameter
data set did not conform to the requirements of the presentation context it was
received across.
FE00 (Matching Terminated Due To Cancel Request) – Indicates that the query
operation was terminated by the remote application entity prior to completion.
A700 (Out Of Resources) – Indicates that the archive ran out of resources to process
the query request.
Query implementation specifics
The SCUs are recommended to append wildcard “*” at the end of each component of
any structured name to facilitate matching.
3.1.3.3.4
Presentation Context Acceptance Criterion
There is no prioritization used for the acceptance of presentation contexts. Any
combination of supported transfer syntax and abstract syntax is accepted, in case the
product is configured for them.
3.1.3.3.5
Transfer Syntax Selection Policies
The Enterprise Archive Manager selects transfer syntaxes in Acceptor first modes:
the first transfer syntax in the archive’s list of allowable transfer syntaxes that also
exists in the proposed transfer syntax list will be selected.
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 36 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
3.1.3.4
Respond to a Retrieve Request from a Remote System
3.1.3.4.1
Associated Real-World Activity
When the Enterprise Archive Manager receives a request for retrieval (C-MOVE or CGET), the request will be resolved against the underlying database. If any objects are
found, it will attempt to establish an association over which to store the found objects
(C-MOVE only). If the association is established, it will retrieve the found objects from
the underlying platform and store them over the association, returning pending
responses to the retrieval request initiator.
3.1.3.4.2
Presentation Context Table
The Enterprise Archive Manager will accept the following Transfer Syntaxes for each
presentation context in an association it receives:
Presentation Context Table
Abstract Syntax
Name
Patient Root
Query/Retrieve
Information
Model – MOVE
Patient Root
Query/Retrieve
Information
Model – GET
Study Root
Query/Retrieve
Information
Model – MOVE
Study Root
Query/Retrieve
Information
Model – GET
Patient/Study
Only
Query/Retrieve
Information
UID
1.2.840.10008.5.1.4.1.2.1.2
1.2.840.10008.5.1.4.1.2.1.3
1.2.840.10008.5.1.4.1.2.2.2
1.2.840.10008.5.1.4.1.2.2.3
1.2.840.10008.5.1.4.1.2.3.2
Transfer Syntax
Name
Role
Extended
Negotiation
SCP
Relational
SCP
Relational
SCP
Relational
SCP
Relational
SCP
Relational
UID
Little Endian Explicit VR
1.2.840.10008.1.2.1
Little Endian Implicit VR
1.2.840.10008.1.2
Big Endian Explicit VR
1.2.840.10008.1.2.2
Deflated Little Endian
Explicit VR
1.2.840.10008.1.2.1.99
Little Endian Explicit VR
1.2.840.10008.1.2.1
Little Endian Implicit VR
1.2.840.10008.1.2
Big Endian Explicit VR
1.2.840.10008.1.2.2
Deflated Little Endian
Explicit VR
1.2.840.10008.1.2.1.99
Little Endian Explicit VR
1.2.840.10008.1.2.1
Little Endian Implicit VR
1.2.840.10008.1.2
Big Endian Explicit VR
1.2.840.10008.1.2.2
Deflated Little Endian
Explicit VR
1.2.840.10008.1.2.1.99
Little Endian Explicit VR
1.2.840.10008.1.2.1
Little Endian Implicit VR
1.2.840.10008.1.2
Big Endian Explicit VR
1.2.840.10008.1.2.2
Deflated Little Endian
Explicit VR
1.2.840.10008.1.2.1.99
Little Endian Explicit VR
1.2.840.10008.1.2.1
Little Endian Implicit VR
1.2.840.10008.1.2
Big Endian Explicit VR
1.2.840.10008.1.2.2
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 37 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
Presentation Context Table
Abstract Syntax
Name
Model – MOVE
Patient/Study
Only
Query/Retrieve
Information
Model – GET
3.1.3.4.3
UID
Transfer Syntax
Name
Deflated Little Endian
Explicit VR
1.2.840.10008.5.1.4.1.2.3.3
Role
Extended
Negotiation
SCP
Relational
UID
1.2.840.10008.1.2.1.99
Little Endian Explicit VR
1.2.840.10008.1.2.1
Little Endian Implicit VR
1.2.840.10008.1.2
Big Endian Explicit VR
1.2.840.10008.1.2.2
Deflated Little Endian
Explicit VR
1.2.840.10008.1.2.1.99
SOP Specific Conformance for All Query/Retrieve SOP Classes
C-MOVE or C-GET Status Codes
If the Enterprise Archive Manager returns one of the following status codes for CMOVE or C-GET then the operation was unsuccessful. All status codes are in
hexadecimal.
0110 (Processing Failure) – Indicates that an unknown error occurred during the
query.
C000 (Data Set Read Error) – Indicates that there was an error reading the move/get
parameters data set. This may be returned if the data set is corrupted. The Error
Comment field of the status will be populated with a description of the error
encountered.
C001 (Unable To Process) – Indicates that the archive was unable to fully process the
move/get. The Error Comment field of the status will be populated with a description of
the error encountered.
A900 (Identifier Does Not Match SOP Class) – Indicates that the move/get parameter
data set did not conform to the requirements of the presentation context it was
received across.
FE00 (Sub-Operations Terminated Due To Cancel Request) – Indicates that the
move/get request was terminated by the remote application entity prior to completion.
A701 (Unable To Calculate Number Of Matches) – Indicates that the archive was
unable to calculate the number of matching objects for this move/get request. May be
due to lack of resources.
A702 (Unable To Perform Sub-Operations) – Indicates that the archive was unable to
perform the storage sub-operations. May be due to lack of resources.
A801 (Move Destination Unknown) – Indicates that the archive was unable to connect
to the move destination (C-MOVE only).
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 38 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
3.1.3.4.4
Presentation Context Acceptance Criterion
There is no prioritization used for the acceptance of presentation contexts. Any
combination of supported transfer syntax and abstract syntax is accepted, in case the
product is configured for them.
3.1.3.4.5
Transfer Syntax Selection Policies
The Enterprise Archive Manager selects transfer syntaxes in Acceptor first mode: the
first transfer syntax in the archive’s list of allowable transfer syntaxes that also exists
in the proposed transfer syntax list will be selected.
3.1.3.5
Accepting a Storage Commitment Request from a Remote System
3.1.3.5.1
Associated Real-World Activity
When the Enterprise Archive Manager receives a storage commitment request (NACTION) it will immediately respond with a status of success. It will then attempt to
locate all objects in the Archive Manager and Advanced Visualization for which
storage commitment was requested. Once it has located the objects, it will establish
an association back to the requesting entity and will send a storage commitment
response (N-EVENT-REPORT), detailing all objects that were/were not found. Upon
completion of the N-EVENT-REPORT, it will close the association.
3.1.3.5.2
Proposed Presentation Contexts
The Enterprise DICOM Archive Manager will accept the following Transfer Syntaxes
for each presentation context in an association it receives:
Presentation Context Table
Abstract Syntax
Name
Storage
Commitment
Push Model
UID
1.2.840.10008.1.20.1
Transfer Syntax
Name
UID
Little Endian Explicit VR
1.2.840.10008.1.2.1
Little Endian Implicit VR
1.2.840.10008.1.2
Big Endian Explicit VR
1.2.840.10008.1.2.2
Deflated Little Endian
Explicit VR
1.2.840.10008.1.2.1.99
Role
SCP
Extended
Negotiation
None
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 39 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
3.1.3.5.3
SOP Specific Conformance for Storage Commitment Push SOP Class
The Enterprise Archive Manager conforms to the SOP of the Storage Commitment
Push Service Class fully.
Extended negotiation is not supported for the Storage Commitment Push Service
Class.
If the Enterprise Archive Manager returns one of the following status codes for NACTION, then the request for storage commitment was unsuccessful.
0119 (Class-instance conflict) – Indicates that the SOP Instance UID sent in the NACTION-RQ was not the Storage Commitment Push Model SOP Instance UID
(1.2.840.10008.1.20.1.1).
0110 (Processing Failure) – Indicates that an unknown error occurred during the
storage commitment.
3.1.3.5.4
Presentation Context Acceptance Criterion
There is no prioritization used for the acceptance of presentation contexts. Any
combination of supported transfer syntax and abstract syntax is accepted, in case the
product is configured for them.
3.1.3.5.5
Transfer Syntax Selection Policies
The Enterprise Archive Manager selects transfer syntaxes in Acceptor first mode: the
first transfer syntax in the archive’s list of allowable transfer syntaxes that also exists
in the proposed transfer syntax list will be selected.
3.1.3.6
Receiving MPPS Messages
3.1.3.6.1
Associated Real-World Activity
When the Archive Manager receives an N-Create or N-Set operation, it will process it
accordingly and respond with a status of Success (0000h) to the MPPS SCU. The
received message will then be forwarded reliably to the remote configured MPPS
SCP. For this operation the Archive Manager is serving the role of the MPPS SCU.
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 40 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
3.1.3.6.2
Presentation Context Table
The Archive Manager will accept the following Transfer Syntaxes for each
presentation context in an association it receives:
Presentation Context Table
Abstract Syntax
Name
Modality
Performed
Procedure Step
3.1.3.6.3
UID
1.2.840.10008.3.1.2.3.3
Transfer Syntax
Name
UID
Little Endian Explicit VR
1.2.840.10008.1.2.1
Little Endian Implicit VR
1.2.840.10008.1.2
Big Endian Explicit VR
1.2.840.10008.1.2.2
Deflated Little Endian
Explicit VR
1.2.840.10008.1.2.1.99
Role
SCP
Extended
Negotiation
None
SOP Specific Conformance Statement for MPPS
The Archive Manager provides standard conformance to the DICOM Modality
Performed Procedure Step SOP Class as an SCP.
3.1.3.6.4
Presentation Context Acceptance Criterion
There is no prioritization used for the acceptance of presentation contexts. Any
combination of supported transfer syntax and abstract syntax is accepted, in case the
product is configured for them.
3.1.3.6.5
Transfer Syntax Selection Policies
The Archive Manager selects transfer syntaxes in Acceptor first mode: the first
transfer syntax in the archive’s list of allowable transfer syntaxes that also exists in the
proposed transfer syntax list will be selected.
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 41 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
3.2
Enterprise Archive Proxy Component Specification
This Application Entity provides Standard Conformance to the following DICOM V3.0
SOP Classes as an SCU and/or SCP. The Application Entity can support all Storage
SOP Classes as SCU and SCP after dynamic reconfiguration of the archive.properties
file.
SOP Class Name
SOP Class UID
SCU/SCP
Verification
1.2.840.10008.1.1
N/Y
Computed Radiography Image
Storage
1.2.840.10008.5.1.4.1.1.1
Y/Y
CT Image Storage
1.2.840.10008.5.1.4.1.1.2
Y/Y
Hardcopy Color Image Storage
1.2.840.10008.5.1.1.30
Y/Y
Hardcopy Grayscale Image Storage
1.2.840.10008.5.1.1.29
Y/Y
MR Image Storage
1.2.840.10008.5.1.4.1.1.4
Y/Y
Nuclear Medicine Image Storage
1.2.840.10008.5.1.4.1.1.20
Y/Y
Nuclear Medicine Image Storage
(Retired)
1.2.840.10008.5.1.4.1.1.5
Y/Y
Positron Emission Tomography
Image Storage
1.2.840.10008.5.1.4.1.1.128
Y/Y
RT Dose Storage
1.2.840.10008.5.1.4.1.1.481.2
Y/Y
RT Image Storage
1.2.840.10008.5.1.4.1.1.481.1
Y/Y
RT Plan Storage
1.2.840.10008.5.1.4.1.1.481.5
Y/Y
RT Structure Set Storage
1.2.840.10008.5.1.4.1.1.481.3
Y/Y
* RT Beams Treatment Record
Storage
1.2.840.10008.5.1.4.1.1.481.4
Y/Y
* RT Brachy Treatment Record
Storage
1.2.840.10008.5.1.4.1.1.481.6
Y/Y
* RT Treatment Summary Record
Storage
1.2.840.10008.5.1.4.1.1.481.7
Y/Y
Secondary Capture Image Storage
1.2.840.10008.5.1.4.1.1.7
Y/Y
Stand-alone Curve Storage
1.2.840.10008.5.1.4.1.1.9
Y/Y
* 12-lead ECG Waveform Storage
1.2.840.10008.5.1.4.1.1.9.1.1
Y/Y
* General ECG Waveform Storage
1.2.840.10008.5.1.4.1.1.9.1.2
Y/Y
* Ambulatory ECG Waveform
Storage
1.2.840.10008.5.1.4.1.1.9.1.3
Y/Y
* Hemodynamic Waveform Storage
1.2.840.10008.5.1.4.1.1.9.2.1
Y/Y
* Cardiac Electrophysiology
Waveform Storage
1.2.840.10008.5.1.4.1.1.9.3.1
Y/Y
* Basic Voice Audio Waveform
Storage
1.2.840.10008.5.1.4.1.1.9.4.1
Y/Y
Verification
Storage
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 42 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
SOP Class Name
SOP Class UID
SCU/SCP
Stand-alone Modality LUT Storage
1.2.840.10008.5.1.4.1.1.10
Y/Y
Stand-alone Overlay Storage
1.2.840.10008.5.1.4.1.1.8
Y/Y
Stand-alone VOI LUT Storage
1.2.840.10008.5.1.4.1.1.11
Y/Y
* Grayscale Softcopy Presentation
State Storage
1.2.840.10008.5.1.4.1.1.11.1
Y/Y
Standalone PET Curve Storage
1.2.840.10008.5.1.4.1.1.129
Y/Y
Stored Print Storage
1.2.840.10008.5.1.1.27
Y/Y
Ultrasound Image Storage
1.2.840.10008.5.1.4.1.1.6.1
Y/Y
Ultrasound Image Storage (Retired)
1.2.840.10008.5.1.4.1.1.6
Y/Y
Ultrasound Multi-frame Image
Storage
1.2.840.10008.5.1.4.1.1.3.1
Y/Y
Ultrasound Multi-frame Image
Storage (Retired)
1.2.840.10008.5.1.4.1.1.3
Y/Y
X-Ray Angiographic Bi-Plane Image
Storage
1.2.840.10008.5.1.4.1.1.12.3
Y/Y
X-Ray Angiographic Image Storage
1.2.840.10008.5.1.4.1.1.12.1
Y/Y
X-Ray Radiofluoroscopic Image
Storage
1.2.840.10008.5.1.4.1.1.12.2
Y/Y
Digital X-Ray Image Storage – for
Presentation
1.2.840.10008.5.1.4.1.1.1.1
Y/Y
Digital X-Ray Image Storage – for
Processing
1.2.840.10008.5.1.4.1.1.1.1.1
Y/Y
Digital Mammography Image
Storage – for Presentation
1.2.840.10008.5.1.4.1.1.1.2
Y/Y
Digital Mammography Image
Storage – for Processing
1.2.840.10008.5.1.4.1.1.1.2.1
Y/Y
Digital Intra-oral X-Ray Image
Storage – for Presentation
1.2.840.10008.5.1.4.1.1.1.3
Y/Y
Digital Intra-oral X-Ray Image
Storage – for Processing
1.2.840.10008.5.1.4.1.1.1.3.1
Y/Y
VL Endoscopic Image Storage
1.2.840.10008.5.1.4.1.1.77.1.1
Y/Y
VL Microscopic Image Storage
1.2.840.10008.5.1.4.1.1.77.1.2
Y/Y
VL Slide-Coordinates Microscopic
Image Storage
1.2.840.10008.5.1.4.1.1.77.1.3
Y/Y
VL Photographic Image Storage
1.2.840.10008.5.1.4.1.1.77.1.4
Y/Y
* Basic text SR
1.2.840.10008.5.1.4.1.1.88.11
Y/Y
* Enhanced SR
1.2.840.10008.5.1.4.1.1.88.22
Y/Y
* Comprehensive SR
1.2.840.10008.5.1.4.1.1.88.33
Y/Y
1.2.840.10008.5.1.4.1.2.1.1
Y/Y
Query/Retrieve
Patient Root Query/Retrieve
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 43 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
SOP Class Name
SOP Class UID
SCU/SCP
Information Model – FIND
Patient Root Query/Retrieve
Information Model – MOVE
1.2.840.10008.5.1.4.1.2.1.2
Y/Y
Study Root Query/Retrieve
Information Model – FIND
1.2.840.10008.5.1.4.1.2.2.1
Y/Y
Study Root Query/Retrieve
Information Model – MOVE
1.2.840.10008.5.1.4.1.2.2.2
Y/Y
Patient/Study Only Query/Retrieve
Information Model – FIND
1.2.840.10008.5.1.4.1.2.3.1
Y/Y
Patient/Study Only Query/Retrieve
Information Model – MOVE
1.2.840.10008.5.1.4.1.2.3.2
Y/Y
1.2.840.10008.1.20.1
N/Y
Storage Commitment
Storage Commitment Push Model
* These SOP Classes have been implemented in the Proxy; however, they are not supported as
standard features. If the user wishes to use these features, the appropriate properties must be
added.
3.2.1 Association Establishment Policies
3.2.1.1
General
The Proxy will attempt to establish an association anytime a C-FIND request is
received from a remote application entity. The Proxy will attempt to establish
associations with other archives on the network in order to find objects until all
configured archives have been queried. The Proxy will attempt to establish
associations in response to valid Storage Commitment requests.
Anytime a C-MOVE request is received from a remote application entity, the Proxy will
attempt to establish one or more associations. If the object is known in the local
database, the Proxy will attempt to establish an association in order to store the object
requested in the move. If the object is not known in the local database and a movethru has been configured, the Proxy will attempt to establish an association with the
remote DICOM archive where the object is known in order to move the requested
object to the Archive’s local database, then the Proxy will attempt to establish an
association in order to store the object requested in the move. If the object is not
known in the local database and a third-party-move has been configured, the Proxy
will attempt to establish an association with the remote DICOM archive where the
object is known in order to request a move of the object directly to the original
application entity requesting the object.
The Proxy will attempt to establish an association to store objects even if the
destination is unknown by pairing the requested destination with the IP address of the
C-MOVE requestor and the DICOM well-known port (104).
The Emageon Proxy supports SCU/SCP Role Negotiation.
The Emageon Proxy has configurable Maximum PDU sizes; both sent and received
(the default is 50KB, both sent and received).
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 44 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
3.2.1.2
Number of Associations
The Proxy will attempt only one storage association establishment to service C-MOVE
requests where move-thru is configured or Storage Commitment requests.
The Proxy will accept any number of simultaneous associations, the number of which
can be configured. The maximum limit on the number of simultaneous associations is
dependent on the number of open file descriptors allowed by the underlying operating
system.
3.2.1.3
Asynchronous Nature
The Proxy will allow any number of asynchronous operations, whether invoked and
performed. This number of asynchronous operations is configurable. When
establishing storage associations to service C-MOVE requests the Proxy will attempt
to negotiate the configured asynchronous operations window in order to optimize
object moves.
3.2.1.4
Implementation Identifying Information
The Enterprise Archive Manager Proxy Component will provide a single
Implementation Class UID and Implementation Version Name as follows:
Proxy Component Implementation Class UID
1.2.826.0.1.3680043.2.133.1.1
Implementation Version Name
5.30
3.2.2 Association Initiation by Real-World Activity
The Proxy will attempt to initiate one storage association for each C-MOVE request
where move-thru is configured or Storage Commitment request that is received.
3.2.2.1
Storage Association:
Completing a Move Request to a Remote System
3.2.2.1.1
Associated Real-World Activity
The associated real-world activity is the receipt of a C-MOVE request from a remote
application entity where move-thru is configured.
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 45 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
3.2.2.1.2
Proposed Presentation Contexts
The Proxy will propose a collection of presentation contexts, which will be obtained by
applying the algorithm presented in the next section to the following Presentation
Context Table:
Presentation Context Table
Abstract Syntax
Name
UID
Transfer Syntax
Role
Extended
Negotiation
12-lead ECG Waveform Storage
1.2.840.10008.5.1.4.1.1.9.1.1
See Table 3.2.2.1.2-1
SCU
None
Ambulatory ECG Waveform
Storage
1.2.840.10008.5.1.4.1.1.9.1.3
See Table 3.2.2.1.2-1
SCU
None
Basic Study Content Notification
1.2.840.10008.1.9
See Table 3.2.2.1.2-1
SCU
None
Basic Text SR Storage
1.2.840.10008.5.1.4.1.1.88.11
See Table 3.2.2.1.2-1
SCU
None
Basic Voice Audio Waveform
Storage
1.2.840.10008.5.1.4.1.1.9.4.1
See Table 3.2.2.1.2-1
SCU
None
Cardiac Electrophysiology
Waveform Storage
1.2.840.10008.5.1.4.1.1.9.3.1
See Table 3.2.2.1.2-1
SCU
None
Comprehensive SR Storage
1.2.840.10008.5.1.4.1.1.88.33
See Table 3.2.2.1.2-1
SCU
None
Computed Radiography Image
Storage
1.2.840.10008.5.1.4.1.1.1
See Table 3.2.2.1.2-1
SCU
None
CT Image Storage
1.2.840.10008.5.1.4.1.1.2
See Table 3.2.2.1.2-1
SCU
None
Digital X-Ray Image Storage
(Presentation)
1.2.840.10008.5.1.4.1.1.1.1
See Table 3.2.2.1.2-1
SCU
None
Digital X-Ray Image Storage
(Processing)
1.2.840.10008.5.1.4.1.1.1.1.1
See Table 3.2.2.1.2-1
SCU
None
Digital Mammography Image
Storage (Presentation)
1.2.840.10008.5.1.4.1.1.1.2
See Table 3.2.2.1.2-1
SCU
None
Digital Mammography Image
Storage (Processing)
1.2.840.10008.5.1.4.1.1.1.2.1
See Table 3.2.2.1.2-1
SCU
None
Digital Intra-oral X-Ray Image
Storage (Presentation)
1.2.840.10008.5.1.4.1.1.1.3
See Table 3.2.2.1.2-1
SCU
None
Digital Intra-oral X-Ray Image
Storage (Processing)
1.2.840.10008.5.1.4.1.1.1.3.1
See Table 3.2.2.1.2-1
SCU
None
Enhanced SR Storage
1.2.840.10008.5.1.4.1.1.88.22
See Table 3.2.2.1.2-1
SCU
None
General ECG Waveform Storage
1.2.840.10008.5.1.4.1.1.9.1.2
See Table 3.2.2.1.2-1
SCU
None
Grayscale Softcopy Presentation
State Storage
1.2.840.10008.5.1.4.1.1.11.1
See Table 3.2.2.1.2-1
SCU
None
Hardcopy Color Image Storage
1.2.840.10008.5.1.1.30
See Table 3.2.2.1.2-1
SCU
None
Hardcopy Grayscale Image
Storage
1.2.840.10008.5.1.1.29
See Table 3.2.2.1.2-1
SCU
None
Hemodynamic Waveform Storage
1.2.840.10008.5.1.4.1.1.9.2.1
See Table 3.2.2.1.2-1
SCU
None
Key Object Selection Document
1.2.840.10008.5.1.4.1.1.88.59
See Table 3.2.2.1.2-1
SCU
None
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 46 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
Presentation Context Table
Abstract Syntax
Name
UID
Transfer Syntax
Role
Extended
Negotiation
Mammography CAD SR
1.2.840.10008.5.1.4.1.1.88.50
See Table 3.2.2.1.2-1
SCU
None
Multi-frame Single Bit Secondary
Capture Image Storage
1.2.840.10008.5.1.4.1.1.7.1
See Table 3.2.2.1.2-1
SCU
None
Multi-frame Grayscale Byte
Secondary Capture Image Storage
1.2.840.10008.5.1.4.1.1.7.2
See Table 3.2.2.1.2-1
SCU
None
Multi-frame Grayscale Word
Secondary Capture Image Storage
1.2.840.10008.5.1.4.1.1.7.3
See Table 3.2.2.1.2-1
SCU
None
Multi-frame True Color Secondary
Capture Image Storage
1.2.840.10008.5.1.4.1.1.7.4
See Table 3.2.2.1.2-1
SCU
None
MR Image Storage
1.2.840.100008.5.1.4.1.1.4
See Table 3.1.2.1.2-1
SCU
None
Nuclear Medicine Image Storage
1.2.840.10008.5.1.4.1.1.20
See Table 3.1.2.1.2-1
SCU
None
Nuclear Medicine Image Storage
(Retired)
1.2.840.10008.5.1.4.1.1.5
See Table 3.1.2.1.2-1
SCU
None
Positron Emission Tomography
Image Storage
1.2.840.10008.5.1.4.1.1.128
See Table 3.1.2.1.2-1
SCU
None
RT Beams Treatment Record
Storage
1.2.840.10008.5.1.4.1.1.481.4
See Table 3.2.2.1.2-1
SCU
None
RT Brachy Treatment Record
Storage
1.2.840.10008.5.1.4.1.1.481.6
See Table 3.2.2.1.2-1
SCU
None
RT Dose Storage
1.2.840.10008.5.1.4.1.1.481.2
See Table 3.2.2.1.2-1
SCU
None
RT Image Storage
1.2.840.10008.5.1.4.1.1.481.1
See Table 3.2.2.1.2-1
SCU
None
RT Plan Storage
1.2.840.10008.5.1.4.1.1.481.5
See Table 3.2.2.1.2-1
SCU
None
RT Structure Set Storage
1.2.840.10008.5.1.4.1.1.481.3
See Table 3.2.2.1.2-1
SCU
None
RT Treatment Summary Record
Storage
1.2.840.10008.5.1.4.1.1.481.7
See Table 3.2.2.1.2-1
SCU
None
Secondary Capture Image Storage
1.2.840.10008.5.1.4.1.1.7
See Table 3.2.2.1.2-1
SCU
None
Stand-alone Curve Storage
1.2.840.10008.5.1.4.1.1.9
See Table 3.2.2.1.2-1
SCU
None
Stand-alone Modality LUT Storage
1.2.840.10008.5.1.4.1.1.10
See Table 3.2.2.1.2-1
SCU
None
Stand-alone Overlay Storage
1.2.840.10008.5.1.4.1.1.8
See Table 3.2.2.1.2-1
SCU
None
Stand-alone VOI LUT Storage
1.2.840.10008.5.1.4.1.1.11
See Table 3.2.2.1.2-1
SCU
None
Standalone PET Curve Storage
1.2.840.10008.5.1.4.1.1.129
See Table 3.2.2.1.2-1
SCU
None
Stored Print Storage
1.2.840.10008.5.1.1.27
See Table 3.2.2.1.2-1
SCU
None
Ultrasound Image Storage
1.2.840.10008.5.1.4.1.1.6.1
See Table 3.2.2.1.2-1
SCU
None
Ultrasound Image Storage
(Retired)
1.2.840.10008.5.1.4.1.1.6
See Table 3.2.2.1.2-1
SCU
None
Ultrasound Multi-frame Image
Storage
1.2.840.10008.5.1.4.1.1.3.1
See Table 3.2.2.1.2-1
SCU
None
Ultrasound Multi-frame Image
Storage (Retired)
1.2.840.10008.5.1.4.1.1.3
See Table 3.2.2.1.2-1
SCU
None
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 47 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
Presentation Context Table
Abstract Syntax
Name
UID
Transfer Syntax
Role
Extended
Negotiation
VL Endoscopic Image Storage
1.2.840.10008.5.1.4.1.1.77.1.1
See Table 3.2.2.1.2-1
SCU
None
VL Microscopic Image Storage
1.2.840.10008.5.1.4.1.1.77.1.2
See Table 3.2.2.1.2-1
SCU
None
VL Slide-Coordinates Microscopic
Image Storage
1.2.840.10008.5.1.4.1.1.77.1.3
See Table 3.2.2.1.2-1
SCU
None
VL Photographic Image Storage
1.2.840.10008.5.1.4.1.1.77.1.4
See Table 3.2.2.1.2-1
SCU
None
X-Ray Angiographic Bi-Plane
Image Storage (retired)
1.2.840.10008.5.1.4.1.1.12.3
See Table 3.2.2.1.2-1
SCU
None
X-Ray Angiographic Image Storage
1.2.840.10008.5.1.4.1.1.12.1
See Table 3.2.2.1.2-1
SCU
None
X-Ray Radiofluoroscopic Image
Storage
1.2.840.10008.5.1.4.1.1.12.2
See Table 3.2.2.1.2-1
SCU
None
Table 3.2.2.1.2-1
Transfer Syntax for Send to a Remote System
Name
UID
Little Endian Explicit VR
1.2.840.10008.1.2.1
Little Endian Implicit VR
1.2.840.10008.1.2
Big Endian Explicit VR
1.2.840.10008.1.2.2
Deflated Little Endian Explicit VR
1.2.840.10008.1.2.1.99
Lossless JPEG Image Compression (baseline)
1.2.840.10008.1.2.4.70
Lossy JPEG Image Compression (8-bit, coding
Process 1)
1.2.840.10008.1.2.4.50
Lossy JPEG Image Compression (12-bit, coding
Process 4)
1.2.840.10008.1.2.4.51
JPEG 2000 Image Compression (Lossless Only)
1.2.840.10008.1.2.4.90
JPEG 2000 Image Compression
1.2.840.10008.1.2.4.91
Algorithm for Computing the Proposed Presentation Contexts for Outgoing Storage Associations
At the time of the association establishment, the set of DICOM objects to be sent out
has been determined. Since both the transfer syntax in which each DICOM object has
been stored and the SOP Class UID of each DICOM object are stored in the archives
database, both of these tags are already known. The intention of the algorithm is to
send out each object in the transfer syntax it has been initially stored in or a similar
one. So, we understand that if the object has been initially received in a supported
encapsulated transfer syntax, the algorithm would make sure that for the specific
abstract syntax, a presentation context with that particular transfer syntax has been
proposed. The encapsulated transfer syntax is preserved for efficiency, in order to
save the processing time of the compression conversion. In the case of objects stored
in a native transfer syntax, preserving the transfer syntax is not important, and any
native transfer syntax should be acceptable.
The archive will perform an analysis of the different encapsulated transfer syntaxes for
each abstract syntax, and it will propose one presentation context for each
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 48 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
encapsulated transfer syntax class recorded, plus a context with the list of all the other
supported transfer syntaxes. This at least creates the possibility for each desired
presentation context to be accepted. As an example, let us assume that the retrieve
set of a C-Move request contains Ultrasound Multi-Frame objects stored in both the
Lossless JPEG transfer syntax and the Lossy JPEG transfer syntax coding Process 1.
Three presentation contexts will be proposed for the Ultrasound Multi-Frame abstract
syntax: one with the Lossless JPEG transfer syntax, one with the Lossy JPEG transfer
syntax coding Process 1, and one containing a list of all the other supported native
transfer syntaxes.
Once the association negotiation is complete, some presentation contexts will be
accepted and some will not. For datasets that had DICOM objects stored in different
transfer syntaxes for the same abstract class, a heuristic will need to be applied in
order to select the appropriate presentation context. The configurable
TransferSyntaxPriorityList property controls the choosing of the appropriate
presentation context. For each transfer syntax UID, a list of transfer syntax lists will be
provided. The User Service will be created on the first available (accepted)
presentation context obtained from parsing the priority list (i.e. the list of transfer
syntaxes is parsed and the first presentation context that matches in the accepted
transfer syntax is used). The first entry in the list should be the same as the transfer
syntax used as key, at least in the case of encapsulated transfer syntaxes.
3.2.2.2
Query a Remote DICOM Device
3.2.2.2.1
Associated Real-World Activity
The associated real-world activity is the receipt of a C-FIND request from a remote
application entity and there are configured external archives.
3.2.2.2.2
Proposed Presentation Contexts
The Proxy will propose the following Transfer Syntaxes for each presentation context
in an association it initiates to an external archive:
Presentation Context Table
Abstract Syntax
Transfer Syntax
Role
Name
Patient Root
Query/Retrieve
Information
Model – FIND
Study Root
Query/Retrieve
UID
Name
UID
Little Endian Explicit VR
1.2.840.10008.1.2.1
Little Endian Implicit VR
1.2.840.10008.1.2
Big Endian Explicit VR
1.2.840.10008.1.2.2
Deflated Little Endian
Explicit VR
1.2.840.10008.1.2.1.99
1.2.840.10008.5.1.4.1.2.1.1
1.2.840.10008.5.1.4.1.2.2.1
Little Endian Explicit VR
1.2.840.10008.1.2.1
Little Endian Implicit VR
1.2.840.10008.1.2
Extended
Negotiation
SCU
Relational*
SCU
Relational*
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 49 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
Presentation Context Table
Abstract Syntax
Transfer Syntax
Extended
Negotiation
Role
Name
UID
Information
Model – FIND
Patient/Study
Only
Query/Retrieve
Information
Model – FIND
1.2.840.10008.5.1.4.1.2.3.1
Name
UID
Big Endian Explicit VR
1.2.840.10008.1.2.2
Deflated Little Endian
Explicit VR
1.2.840.10008.1.2.1.99
Little Endian Explicit VR
1.2.840.10008.1.2.1
Little Endian Implicit VR
1.2.840.10008.1.2
Big Endian Explicit VR
1.2.840.10008.1.2.2
Deflated Little Endian
Explicit VR
1.2.840.10008.1.2.1.99
SCU
Relational*
*If all external archives support relational, then the Proxy will support relational.
3.2.2.2.3
SOP Specific Conformance Statement for All SOP Classes
The Proxy provides standard conformance to the DICOM Query/Retrieve – FIND SOP
Classes as an SCU.
3.2.2.3
Request a Move Association to Remote DICOM Device
3.2.2.3.1
Associated Real-World Activity
The associated real-world activity is the receipt of a C-MOVE request from a remote
application entity and there are configured external archives.
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 50 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
3.2.2.3.2
Proposed Presentation Contexts
The Proxy will propose the following Transfer Syntaxes for each presentation context
in an association it initiates:
Presentation Context Table
Abstract Syntax
Name
Patient Root
Query/Retrieve
Information
Model – MOVE
Study Root
Query/Retrieve
Information
Model – MOVE
Patient/Study
Only
Query/Retrieve
Information
Model – MOVE
Transfer Syntax
UID
1.2.840.10008.5.1.4.1.2.1.2
1.2.840.10008.5.1.4.1.2.2.2
1.2.840.10008.5.1.4.1.2.3.2
Name
Role
UID
Little Endian Explicit VR
1.2.840.10008.1.2.1
Little Endian Implicit VR
1.2.840.10008.1.2
Big Endian Explicit VR
1.2.840.10008.1.2.2
Deflated Little Endian
Explicit VR
1.2.840.10008.1.2.1.99
Little Endian Explicit VR
1.2.840.10008.1.2.1
Little Endian Implicit VR
1.2.840.10008.1.2
Big Endian Explicit VR
1.2.840.10008.1.2.2
Deflated Little Endian
Explicit VR
1.2.840.10008.1.2.1.99
Little Endian Explicit VR
1.2.840.10008.1.2.1
Little Endian Implicit VR
1.2.840.10008.1.2
Big Endian Explicit VR
1.2.840.10008.1.2.2
Deflated Little Endian
Explicit VR
1.2.840.10008.1.2.1.99
Extended
Negotiation
SCU
Relational*
SCU
Relational*
SCU
Relational*
*If all external archives support relational, then the Proxy will support relational.
3.2.2.3.3
SOP Specific Conformance Statement for all SOP Classes
The Proxy provides standard conformance to the DICOM Query/Retrieve – MOVE
SOP Classes as an SCU.
3.2.2.4
Completing Storage Commitment Request from a Remote System
3.2.2.4.1
Associated Real-World Activity
The associated real-world activity is the response to a Storage Commitment request
from a remote application entity.
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 51 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
3.2.2.4.2
Proposed Presentation Contexts
The following presentation contexts will be proposed for each association:
Presentation Context Table
Abstract Syntax
Name
Storage
Commitment
Push Model
Transfer Syntax
UID
1.2.840.10008.1.20.1
Name
UID
Little Endian Explicit VR
1.2.840.10008.1.2.1
Little Endian Implicit VR
1.2.840.10008.1.2
Big Endian Explicit VR
1.2.840.10008.1.2.2
Deflated Little Endian
Explicit VR
1.2.840.10008.1.2.1.99
Role
SCP
Extended
Negotiation
None
3.2.3 Association Acceptance Policy
When the Proxy accepts an association, it will allow the retrieval of objects previously
stored, the query for information about stored objects, the verification of the Proxy,
and the storage commitment of stored object.
The Proxy is configurable to allow security restrictions ranging from no restrictions
(promiscuous) to limiting a particular remote application entity to specified SOP
classes and specified SCU/SCP roles. If security is turned on, association attempts
by unknown entities will be rejected outright and proposed presentation contexts from
known remote application entities may be rejected based on their allowed security
permissions.
3.2.3.1
Respond to a Verification Request from a Remote System
3.2.3.1.1
Associated Real-World Activity
When the Proxy receives a verification request (C-ECHO) it will respond with a status
of success if possible.
3.2.3.1.2
Presentation Context Table
The Proxy will accept the following Transfer Syntaxes for each presentation context in
an association it receives:
Presentation Context Table
Abstract Syntax
Name
Verification
UID
1.2.840.10008.1.1
Transfer Syntax
Name
UID
Little Endian Explicit VR
1.2.840.10008.1.2.1
Little Endian Implicit VR
1.2.840.10008.1.2
Big Endian Explicit VR
1.2.840.10008.1.2.2
Deflated Little Endian
Explicit VR
1.2.840.10008.1.2.1.99
Role
SCP
Extended
Negotiation
None
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 52 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
3.2.3.1.3
SOP Specific Conformance for Verification SOP Class
The Proxy conforms to the SOP of the Verification Service Class fully.
Extended negotiation is not supported for the Verification Service Class.
If the Proxy returns anything other than success then the C-ECHO operation failed.
3.2.3.1.4
Presentation Context Acceptance Criterion
There is no prioritization used for the acceptance of presentation contexts. Any
combination of supported transfer syntax and abstract syntax is accepted, in case the
product is configured for them.
3.2.3.1.5
Transfer Syntax Selection Policies
The Proxy selects transfer syntaxes in Acceptor first mode: the first transfer syntax in
the Proxy’s list of allowable transfer syntaxes that also exists in the proposed transfer
syntax list will be selected.
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 53 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
3.2.3.2
Receive Objects from a Remote System
3.2.3.2.1
Associated Real-World Activity
When the Proxy receives a storage request (C-STORE) for an object, that object is
stored to media on the underlying platform in Part 10 format and the object is
registered in the underlying database. If it is unable to store the object a failure
response will be returned and the object will be stored in an exceptions area on the
underlying platform if possible.
The data set of the C-STORE command is stored with no loss of information.
3.2.3.2.2
Presentation Context Table
The Proxy will accept the following Transfer Syntaxes for each presentation context in
an association it receives:
Presentation Context Table
Abstract Syntax
Name
UID
Transfer Syntax
Role
Extended
Negotiation
12-lead ECG Waveform Storage
1.2.840.10008.5.1.4.1.1.9.1.1
See Table 3.2.3.2.2-1
SCP
None
Ambulatory ECG Waveform Storage
1.2.840.10008.5.1.4.1.1.9.1.3
See Table 3.2.3.2.2-1
SCP
None
Basic Study Content Notification
1.2.840.10008.1.9
See Table 3.2.3.2.2-1
SCP
None
Basic Text SR Storage
1.2.840.10008.5.1.4.1.1.88.11
See Table 3.2.3.2.2-1
SCP
None
Basic Voice Audio Waveform Storage
1.2.840.10008.5.1.4.1.1.9.4.1
See Table 3.2.3.2.2-1
SCP
None
Cardiac Electrophysiology Waveform
Storage
1.2.840.10008.5.1.4.1.1.9.3.1
See Table 3.2.3.2.2-1
SCP
None
Comprehensive SR Storage
1.2.840.10008.5.1.4.1.1.88.33
See Table 3.2.3.2.2-1
SCP
None
Computed Radiography Image Storage
1.2.840.10008.5.1.4.1.1.1
See Table 3.2.3.2.2-1
SCP
None
CT Image Storage
1.2.840.10008.5.1.4.1.1.2
See Table 3.2.3.2.2-1
SCP
None
Digital X-Ray Image Storage
(Presentation)
1.2.840.10008.5.1.4.1.1.1.1
See Table 3.2.3.2.2-1
SCP
None
Digital X-Ray Image Storage
(Processing)
1.2.840.10008.5.1.4.1.1.1.1.1
See Table 3.2.3.2.2-1
SCP
None
Digital Mammography Image Storage
(Presentation)
1.2.840.10008.5.1.4.1.1.1.2
See Table 3.2.3.2.2-1
SCP
None
Digital Mammography Image Storage
(Processing)
1.2.840.10008.5.1.4.1.1.1.2.1
See Table 3.2.3.2.2-1
SCP
None
Digital Intra-oral X-Ray Image Storage
(Presentation)
1.2.840.10008.5.1.4.1.1.1.3
See Table 3.2.3.2.2-1
SCP
None
Digital Intra-oral X-Ray Image Storage
(Processing)
1.2.840.10008.5.1.4.1.1.1.3.1
See Table 3.2.3.2.2-1
SCP
None
Enhanced SR Storage
1.2.840.10008.5.1.4.1.1.88.22
See Table 3.2.3.2.2-1
SCP
None
General ECG Waveform Storage
1.2.840.10008.5.1.4.1.1.9.1.2
See Table 3.2.3.2.2-1
SCP
None
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 54 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
Presentation Context Table
Abstract Syntax
Name
UID
Transfer Syntax
Role
Extended
Negotiation
Grayscale Softcopy Presentation State
Storage
1.2.840.10008.5.1.4.1.1.11.1
See Table 3.2.3.2.2-1
SCP
None
Hardcopy Color Image Storage
1.2.840.10008.5.1.1.30
See Table 3.2.3.2.2-1
SCP
None
Hardcopy Grayscale Image Storage
1.2.840.10008.5.1.1.29
See Table 3.2.3.2.2-1
SCP
None
Hemodynamic Waveform Storage
1.2.840.10008.5.1.4.1.1.9.2.1
See Table 3.2.3.2.2-1
SCP
None
Key Object Selection Document
1.2.840.10008.5.1.4.1.1.88.59
See Table 3.2.3.2.2-1
SCP
None
Mammography CAD SR
1.2.840.10008.5.1.4.1.1.88.50
See Table 3.2.3.2.2-1
SCP
None
Multi-frame Single Bit Secondary
Capture Image Storage
1.2.840.10008.5.1.4.1.1.7.1
See Table 3.2.3.2.2-1
SCP
None
Multi-frame Grayscale Byte Secondary
Capture Image Storage
1.2.840.10008.5.1.4.1.1.7.2
See Table 3.2.3.2.2-1
SCP
None
Multi-frame Grayscale Word
Secondary Capture Image Storage
1.2.840.10008.5.1.4.1.1.7.3
See Table 3.2.3.2.2-1
SCP
None
Multi-frame True Color Secondary
Capture Image Storage
1.2.840.10008.5.1.4.1.1.7.4
See Table 3.2.3.2.2-1
SCP
None
MR Image Storage
1.2.840.100008.5.1.4.1.1.4
See Table 3.1.2.1.2-1
SCP
None
Nuclear Medicine Image Storage
1.2.840.10008.5.1.4.1.1.20
See Table 3.1.2.1.2-1
SCP
None
Nuclear Medicine Image Storage
(Retired)
1.2.840.10008.5.1.4.1.1.5
See Table 3.1.2.1.2-1
SCP
None
Positron Emission Tomography Image
Storage
1.2.840.10008.5.1.4.1.1.128
See Table 3.1.2.1.2-1
SCP
None
RT Beams Treatment Record Storage
1.2.840.10008.5.1.4.1.1.481.4
See Table 3.2.3.2.2-1
SCP
None
RT Brachy Treatment Record Storage
1.2.840.10008.5.1.4.1.1.481.6
See Table 3.2.3.2.2-1
SCP
None
RT Dose Storage
1.2.840.10008.5.1.4.1.1.481.2
See Table 3.2.3.2.2-1
SCP
None
RT Image Storage
1.2.840.10008.5.1.4.1.1.481.1
See Table 3.2.3.2.2-1
SCP
None
RT Plan Storage
1.2.840.10008.5.1.4.1.1.481.5
See Table 3.2.3.2.2-1
SCP
None
RT Structure Set Storage
1.2.840.10008.5.1.4.1.1.481.3
See Table 3.2.3.2.2-1
SCP
None
RT Treatment Summary Record
Storage
1.2.840.10008.5.1.4.1.1.481.7
See Table 3.2.3.2.2-1
SCP
None
Secondary Capture Image Storage
1.2.840.10008.5.1.4.1.1.7
See Table 3.2.3.2.2-1
SCP
None
Stand-alone Curve Storage
1.2.840.10008.5.1.4.1.1.9
See Table 3.2.3.2.2-1
SCP
None
Stand-alone Modality LUT Storage
1.2.840.10008.5.1.4.1.1.10
See Table 3.2.3.2.2-1
SCP
None
Stand-alone Overlay Storage
1.2.840.10008.5.1.4.1.1.8
See Table 3.2.3.2.2-1
SCP
None
Stand-alone VOI LUT Storage
1.2.840.10008.5.1.4.1.1.11
See Table 3.2.3.2.2-1
SCP
None
Standalone PET Curve Storage
1.2.840.10008.5.1.4.1.1.129
See Table 3.2.3.2.2-1
SCP
None
Stored Print Storage
1.2.840.10008.5.1.1.27
See Table 3.2.3.2.2-1
SCP
None
Ultrasound Image Storage
1.2.840.10008.5.1.4.1.1.6.1
See Table 3.2.3.2.2-1
SCP
None
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 55 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
Presentation Context Table
Abstract Syntax
Name
UID
Transfer Syntax
Role
Extended
Negotiation
Ultrasound Image Storage (Retired)
1.2.840.10008.5.1.4.1.1.6
See Table 3.2.3.2.2-1
SCP
None
Ultrasound Multi-frame Image Storage
1.2.840.10008.5.1.4.1.1.3.1
See Table 3.2.3.2.2-1
SCP
None
Ultrasound Multi-frame Image Storage
(Retired)
1.2.840.10008.5.1.4.1.1.3
See Table 3.2.3.2.2-1
SCP
None
VL Endoscopic Image Storage
1.2.840.10008.5.1.4.1.1.77.1.1
See Table 3.2.3.2.2-1
SCP
None
VL Microscopic Image Storage
1.2.840.10008.5.1.4.1.1.77.1.2
See Table 3.2.3.2.2-1
SCP
None
VL Slide-Coordinates Microscopic
Image Storage
1.2.840.10008.5.1.4.1.1.77.1.3
See Table 3.2.3.2.2-1
SCP
None
VL Photographic Image Storage
1.2.840.10008.5.1.4.1.1.77.1.4
See Table 3.2.3.2.2-1
SCP
None
X-Ray Angiographic Bi-Plane Image
Storage (retired)
1.2.840.10008.5.1.4.1.1.12.3
See Table 3.2.3.2.2-1
SCP
None
X-Ray Angiographic Image Storage
1.2.840.10008.5.1.4.1.1.12.1
See Table 3.2.3.2.2-1
SCP
None
X-Ray Radiofluoroscopic Image
Storage
1.2.840.10008.5.1.4.1.1.12.2
See Table 3.2.3.2.2-1
SCP
None
Table 3.2.3.2.2-1
Transfer Syntax for Send to a Remote System
Name
3.2.3.2.3
UID
Little Endian Explicit VR
1.2.840.10008.1.2.1
Little Endian Implicit VR
1.2.840.10008.1.2
Big Endian Explicit VR
1.2.840.10008.1.2.2
Deflated Little Endian Explicit VR
1.2.840.10008.1.2.1.99
Lossless JPEG Image Compression (baseline)
1.2.840.10008.1.2.4.70
Lossy JPEG Image Compression (8-bit, coding
Process 1)
1.2.840.10008.1.2.4.50
Lossy JPEG Image Compression (12-bit, coding
Process 4)
1.2.840.10008.1.2.4.51
JPEG 2000 Image Compression (Lossless Only)
1.2.840.10008.1.2.4.90
JPEG 2000 Image Compression
1.2.840.10008.1.2.4.91
SOP Specific Conformance for all Storage SOP Classes
The Proxy conforms to the SOP’s of the Storage Service Class at Level 2 (full). No
elements are discarded or coerced. In the event of a successful C-STORE operation
the object is fully stored to the underlying platform’s media in Part 10 format and is
accessible either as a file or through the Proxy.
Minimal object validation is performed by the Proxy to ensure database integrity.
Additional validation may be configured to prevent the object from being stored in the
Proxy. This capability should only be configured by Emageon based on customer
request or Emageon recommendation.
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 56 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
Extended negotiation is not supported for Storage Service Classes.
If the Proxy returns one of the following status codes then the C-STORE operation
was unsuccessful. If possible the offending object will be stored in the exceptions
area on the underlying platform. All status codes are in hexadecimal.
0110 (Processing Failure) – Indicates that an unknown error occurred during the
storage of the received object.
A900 (SOP Class UID Mismatch) – Indicates that the SOP Class UID of the object
received did not match the presentation context over which the object arrived. The
Error Comment field of the status will be populated with a description of the error
encountered.
C000 (Data Set Read Error) – Indicates that the Proxy encountered an error while
reading the object’s data set. This may be returned if the data set is corrupted. The
Error Comment field of the status will be populated with a description of the error
encountered.
C001 (SOP Instance UID Mismatch) – Indicates that the SOP Instance UID of the
object received did not match the SOP Instance UID sent in the C-STORE command.
The Error Comment field of the status will be populated with a description of the error
encountered.
C002 (Cannot Understand) – Indicates that an unknown error was thrown from within
the Proxy. The Error Comment field of the status will be populated with a description
of the error encountered.
If the Proxy returns the following status code it indicates that the C-STORE operation
was a success but there were warnings. All status codes are in hexadecimal.
B007 (Data Set Does Not Match SOP Class) – Indicates that the object received did
not fully match the SOP Class of the object, but the mismatch was not significant
enough to warrant an exception.
Implementation specifics for Person Names
The values of data elements with a VR of PN (Person Name) will be stored in a
canonical format. Only the StandardName will be stored, and all Name Components
will be stored regardless of their value, separated by the caret character (‘^’). This
normalizes the names, always appending the trailing caret characters. As an example,
the following names are equivalent: LN^FN, LN^FN^, LN^FN^^, LN^FN^^^ and will all
be stored in the database layer as LN^FN^^^. The stored person name will also be
uppercased.
3.2.3.2.4
Presentation Context Acceptance Criterion
There is no prioritization used for the acceptance of presentation contexts. Any
combination of supported transfer syntax and abstract syntax is accepted, in case the
product is configured for them.
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 57 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
3.2.3.2.5
Transfer Syntax Selection Policies
The Proxy selects transfer syntaxes in Acceptor first mode: the first transfer syntax in
the Proxy’s list of allowable transfer syntaxes that also exists in the proposed transfer
syntax list will be selected.
3.2.3.3
Response to a Query Request from a Remote System
3.2.3.3.1
Associated Real-World Activity
When the Proxy receives a query request (C-FIND) it will resolve the request against
the underlying database and, if configured, other archives on the network and return
all found information to the query initiator. The Proxy supports query transactions for
all stored DICOM composite objects.
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 58 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
3.2.3.3.2
Presentation Context Table
The Proxy will accept the following Transfer Syntaxes for any presentation context
proposed to it during an association establishment:
Presentation Context Table
Abstract Syntax
Name
Patient Root
Query/Retrieve
Information
Model – FIND
Study Root
Query/Retrieve
Information
Model – FIND
Patient/Study
Only
Query/Retrieve
Information
Model – FIND
UID
1.2.840.10008.5.1.4.1.2.1.1
1.2.840.10008.5.1.4.1.2.2.1
1.2.840.10008.5.1.4.1.2.3.1
Transfer Syntax
Name
UID
Little Endian Explicit VR
1.2.840.10008.1.2.1
Little Endian Implicit VR
1.2.840.10008.1.2
Big Endian Explicit VR
1.2.840.10008.1.2.2
Deflated Little Endian
Explicit VR
1.2.840.10008.1.2.1.99
Little Endian Explicit VR
1.2.840.10008.1.2.1
Little Endian Implicit VR
1.2.840.10008.1.2
Big Endian Explicit VR
1.2.840.10008.1.2.2
Deflated Little Endian
Explicit VR
1.2.840.10008.1.2.1.99
Little Endian Explicit VR
1.2.840.10008.1.2.1
Little Endian Implicit VR
1.2.840.10008.1.2
Big Endian Explicit VR
1.2.840.10008.1.2.2
Deflated Little Endian
Explicit VR
1.2.840.10008.1.2.1.99
Role
Extended
Negotiation
SCP
Relational
SCP
Relational
SCP
Relational
*If all external archive support relational, then the Proxy will support relational.
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 59 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
3.2.3.3.3
SOP Specific Conformance for all Query/Retrieve SOP Classes
The Proxy conforms to the SOP’s of the Query/Retrieve Service Class at both the
hierarchical and relational level.
SOP Extended Negotiation
Item bytes
1
Field Name
Relationalqueries/retrieval
Description of Field
This byte field defines relational-query/retrieval support
for the Association-acceptor. It shall be encoded as an
unsigned binary integer and shall use one of the
following values
0 - relational-queries/retrieval not supported
1 - relational-queries/retrieval supported
Query Modes
The Enterprise Archive Manager supports both the Hierarchical and Relational search
modes.
Information Models
The Enterprise Archive Manager supports the Patient Root, Study Root, and PatientStudy Only information models.
Table 3.2.3.3.3-1
Patient Root Image C-FIND Supported Attributes
Attribute Name
Patient Level
Patient Name
Patient ID
Referenced Patient Sequence
Referenced SOP Class UID
Referenced SOP Instance UID
Patient’s Birth Date
Patient’s Birth Time
Patient’s Sex
Other Patient IDs
Other Patient Names
Ethnic Group
Patient Comments
Number of Patient Related Studies
Number of Patient Related Series
Number of Patient Related Instances
Study Level
Study Date
Study Time
Accession Number
Study ID
Study Instance UID
Modalities in Study
Referring Physician’s Name
Tag
Query Keys
Matching
SCP
Query Keys
Return
SCP
(0010, 0010)
(0010, 0020)
(0008, 1120)
(0008, 1150)
(0008, 1155)
(0010, 0030)
(0010, 0032)
(0010, 0040)
(0010, 1000)
(0010, 1001)
(0010, 2160)
(0010, 4000)
(0020, 1200)
(0020, 1202)
(0020, 1204)
Supported
Supported (U)
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
(0008, 0020)
(0008, 0030)
(0008, 0050)
(0020, 0010)
(0020, 000D)
(0008, 0061)
(0008, 0090)
Supported
Supported
Supported
Supported
Supported (U)
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 60 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
Attribute Name
Study Description
Procedure Code Sequence
Code Value
Coding Scheme Designator
Coding Scheme Version
Code Meaning
Name of Physician(s) Reading Study
Admitting Diagnoses Description
Referred Study Sequence
Referenced SOP Class UID
Referenced SOP Instance UID
Patient’s Age
Patient’s Size
Patient’s Weight
Occupation
Additional Patient History
Other Study Numbers
Number of Study Related Series
Number of Study Related Instances
Interpretation Author
Series Level
Modality
Series Number
Series Instance UID
Number of Series Related Instances
Performed Procedure Step ID
Reference Study Component Sequence
Referenced SOP Class UID
Referenced SOP Instance UID
Request Attribute Sequence
Requested Procedure ID
Scheduled Procedure Step ID
Performed Procedure Step Start Date
Performed Procedure Step Start Time
Body Part Examined
Station Name
Institution Name
Performing Physician’s Name
Manufacturer
Manufacturer’s Model Name
Series Description
Series Date
Series Time
Protocol Name
Composite Object Instance Level
Instance Number
Overlay Number
Curve Number
LUT Number
SOP Instance UID
SOP Class UID
(0008, 1030)
(0008, 1032)
(0008, 0100)
(0008, 0102)
(0008, 0103)
(0008, 0104)
(0008, 1060)
(0008, 1080)
(0008, 1110)
(0008, 1150)
(0008, 1155)
(0010, 1010)
(0010, 1020)
(0010, 1030)
(0010, 2180)
(0010, 21B0)
(0020, 1070)
(0020, 1206)
(0020, 1208)
(4008, 010C)
Query Keys
Matching
SCP
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Query Keys
Return
SCP
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
(0008, 0060)
(0020, 0011)
(0020, 000E)
(0020, 1209)
(0040, 0253)
(0008, 1111)
(0008, 1150)
(0008, 1155)
(0040, 0275)
(0040, 1001)
(0040, 0009)
(0040, 0244)
(0040, 0245)
(0018, 0015)
(0008, 1010)
(0008, 0080)
(0008, 1050)
(0008, 0070)
(0008, 1090)
(0008, 103E)
(0008, 0021)
(0008, 0031)
(0018, 1030)
Supported
Supported
Supported (U)
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
(0020, 0013)
(0020, 0022)
(0020, 0024)
(0020, 0026)
(0008, 0018)
(0008, 0016)
Supported
Supported
Supported
Supported
Supported (U)
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Tag
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 61 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
Attribute Name
Image Specific Level
Rows
Columns
Bits Allocated
Number of Frames
Tag
(0020, 0010)
(0020, 0011)
(0028, 0100)
(0028, 0008)
Query Keys
Matching
SCP
Supported
Supported
Supported
Supported
Query Keys
Return
SCP
Supported
Supported
Supported
Supported
(U) = Unique
Table 3.2.3.3.3-2
Study Root Image C-FIND Supported Attributes
Attribute Name
Study Level
Study Date
Study Time
Accession Number
Patient Name
Patient ID
Study ID
Study Instance UID
Modalities in Study
Referring Physician’s Name
Study Description
Procedure Code Sequence
Code Value
Coding Scheme Designator
Coding Scheme Version
Code Meaning
Name of Physician(s) Reading Study
Admitting Diagnoses Description
Referred Study Sequence
Referenced SOP Class UID
Referenced SOP Instance UID
Referenced Patient Sequence
Referenced SOP Class UID
Referenced SOP Instance UID
Referenced SOP Instance UID
Patient’s Birth Date
Patient’s Birth Time
Patient’s Sex
Other Patient IDs
Other Patient Names
Patient’s Age
Patient’s Size
Patient’s Weight
Ethnic Group
Occupation
Additional Patient History
Patient Comments
Tag
(0008, 0020)
(0008, 0030)
(0008, 0050)
(0010, 0010)
(0010, 0020)
(0020, 0010)
(0020, 000D)
(0008, 0061)
(0008, 0090)
(0008, 1030)
(0008, 1032)
(0008, 0100)
(0008, 0102)
(0008, 0103)
(0008, 0104)
(0008, 1060)
(0008, 1080)
(0008, 1110)
(0008, 1150)
(0008, 1155)
(0008, 1120)
(0008, 1150)
(0008, 1155)
(0008, 1155)
(0010, 0030)
(0010, 0032)
(0010, 0040)
(0010, 1000)
(0010, 1001)
(0010, 1010)
(0010, 1020)
(0010, 1030)
(0010, 2160)
(0010, 2180)
(0010, 21B0)
(0010, 4000)
Query Keys
Matching
SCP
Supported
Supported
Supported
Supported
Supported (U)
Supported
Supported (U)
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Query Keys
Return
SCP
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 62 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
Attribute Name
Other Study Numbers
Number of Patient Related Studies
Number of Patient Related Series
Number of Patient Related Instances
Number of Study Related Series
Number of Study Related Instances
Interpretation Author
Series Level
Modality
Series Number
Series Instance UID
Number of Series Related Instances
Performed Procedure Step ID
Reference Study Component Sequence
Referenced SOP Class UID
Referenced SOP Instance UID
Request Attribute Sequence
Requested Procedure ID
Scheduled Procedure Step ID
Performed Procedure Step Start Date
Performed Procedure Step Start Time
Body Part Examined
Station Name
Institution Name
Performing Physician’s Name
Manufacturer
Manufacturer’s Model Name
Series Description
Series Date
Series Time
Protocol Name
Composite Object Instance Level
Instance Number
Overlay Number
Curve Number
LUT Number
SOP Instance UID
SOP Class UID
Image Specific Level
Rows
Columns
Bits Allocated
Number of Frames
Tag
Query Keys
Matching
SCP
Query Keys
Return
SCP
(0020, 1070)
(0020, 1200)
(0020, 1202)
(0020, 1204)
(0020, 1206)
(0020, 1208)
(4008, 010C)
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
(0008, 0060)
(0020, 0011)
(0020, 000E)
(0020, 1209)
(0040, 0253)
(0008, 1111)
(0008, 1150)
(0008, 1155)
(0040, 0275)
(0040, 1001)
(0040, 0009)
(0040, 0244)
(0040, 0245)
(0018, 0015)
(0008, 1010)
(0008, 0080)
(0008, 1050)
(0008, 0070)
(0008, 1090)
(0008, 103E)
(0008, 0021)
(0008, 0031)
(0018, 1030)
Supported
Supported
Supported (U)
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
(0020, 0013)
(0020, 0022)
(0020, 0024)
(0020, 0026)
(0008, 0018)
(0008, 0016)
Supported
Supported
Supported
Supported
Supported (U)
Supported
Supported
Supported
Supported
Supported
Supported
Supported
(0020, 0010)
(0020, 0011)
(0028, 0100)
(0028, 0008)
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
(U) = Unique
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 63 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
Patient/Study Only Image C-FIND Supported Attributes
Attributes for the Patient and Study Levels of the Patient/Study Only Query/Retrieve
Information Model are the same as the corresponding attributes for the Patient and
Study Levels of the Patient Root Query/Retrieve Information Model. For information
about these attributes, see the Patient Root Image C-FIND Supported Attributes
table (Table 3.2.3.3.3-1).
Table 3.2.3.3.3-3
Grayscale Soft Copy Presentation State C-FIND Supported Attributes
Attribute Name
GSPS Instance Specific Level
Presentation Label
Presentation Description
Presentation Creation Date
Presentation Creation Time
Presentation Creator’s Name
Referenced Series Sequence
>Series Instance UID
>Referenced Image Sequence
>>Referenced SOP Class UID
>>Referenced SOP Instance UID
Table 3.2.3.3.3-4
Tag
(0070, 0080)
(0070, 0081)
(0070, 0082)
(0070, 0083)
(0070, 0084)
(0008, 1115)
(0020, 000E)
(0008, 1140)
(0008, 1150)
(0008, 1155)
Query Keys
Matching
SCP
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Query Keys
Return
SCP
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Basic Text SR and Enhanced SR C-FIND Supported Attributes
Attribute Name
SR Instance Specific Level
Completion Flag
Verification Flag
Content Date
Content Time
Observation Date Time
Verifying Observer Sequence
>Verifying Organization
>Verification DateTime
>Verifying Observer Name
>Verifying Observer Identification Code
Sequence
Referenced Request Sequence
>Study Instance UID
>Accession Number
>Requested Procedure ID
>Requested Procedure Code Sequence
>>Code Value
>>Code Scheme Designator
>>Code Scheme Version
Tag
Query Keys
Matching
SCP
Query Keys
Return
SCP
(0040, A491)
(0040, A493)
(0008, 0023)
(0008, 0033)
(0040, A032)
(0040, A073)
(0040, A027)
(0040, A030)
(0040, A075)
(0040, A088)
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
(0040, A370)
(0020, 000D)
(0008, 0050)
(0040, 1000)
(0032, 1064)
(0008, 0100)
(0008, 0102)
(0008, 0103)
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 64 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
Attribute Name
>>Code Meaning
Concept Name Code Sequence
>Code Value
>Coding Scheme Designator
>Coding Scheme Version
>Code Meaning
Tag
(0008, 0104)
(0040, A043)
(0008, 0100)
(0008, 0102)
(0008, 0103)
(0008, 0104)
Query Keys
Matching
SCP
Supported
Supported
Supported
Supported
Supported
Supported
Query Keys
Return
SCP
Supported
Supported
Supported
Supported
Supported
Supported
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 65 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
C-FIND Status Codes
If the Proxy returns one of the following status codes for C-FIND then the operation
was unsuccessful. All status codes are in hexadecimal.
0110 (Processing Failure) – Indicates that an unknown error occurred during the
query.
C000 (Data Set Read Error) – Indicates that there was an error reading the query
parameters data set. This may be returned if the data set is corrupted. The Error
Comment field of the status will be populated with a description of the error
encountered.
C001 (Unable To Process) – Indicates that the Proxy was unable to fully process the
query. The Error Comment field of the status will be populated with a description of the
error encountered.
A900 (Identifier Does Not Match SOP Class) – Indicates that the query parameter
data set did not conform to the requirements of the presentation context it was
received across.
FE00 (Matching Terminated Due To Cancel Request) – Indicates that the query
operation was terminated by the remote application entity prior to completion.
A700 (Out Of Resources) – Indicates that the Proxy ran out of resources to process
the query request.
If the Proxy returns one of the following status codes for C-MOVE then the operation
was unsuccessful. All status codes are in hexadecimal.
0110 (Processing Failure) – Indicates that an unknown error occurred during the
query.
C000 (Data Set Read Error) – Indicates that there was an error reading the move
parameters data set. This may be returned if the data set is corrupted. The Error
Comment field of the status will be populated with a description of the error
encountered.
C001 (Unable To Process) – Indicates that the Proxy was unable to fully process the
move. The Error Comment field of the status will be populated with a description of the
error encountered.
A900 (Identifier Does Not Match SOP Class) – Indicates that the move parameter data
set did not conform to the requirements of the presentation context it was received
across.
FE00 (Sub-Operations Terminated Due To Cancel Request) – Indicates that the move
request was terminated by the remote application entity prior to completion.
A701 (Unable To Calculate Number Of Matches) – Indicates that the Proxy was
unable to calculate the number of matching objects for this move request. May be due
to lack of resources.
A702 (Unable To Perform Sub-Operations) – Indicates that the Proxy was unable to
perform the storage sub-operations. May be due to lack of resources.
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 66 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
A801 (Move Destination Unknown) – Indicates that the Proxy was unable to connect
to the move destination (C-MOVE only).
Query implementation specifics
The SCUs are recommended to append wildcard “*” at the end of each component of
any structured name to facilitate matching.
3.2.3.3.4
Presentation Context Acceptance Criterion
There is no prioritization used for the acceptance of presentation contexts. Any
combination of supported transfer syntax and abstract syntax is accepted, in case the
product is configured for them.
3.2.3.3.5
Transfer Syntax Selection Policies
The Proxy selects transfer syntaxes in Acceptor first mode: the first transfer syntax in
the Proxy’s list of allowable transfer syntaxes that also exists in the proposed transfer
syntax list will be selected.
3.2.3.4
Respond to a Retrieve Request from a Remote System
3.2.3.4.1
Associated Real-World Activity
When the Proxy receives a request for retrieval (C-MOVE), it will first resolve the
request against the underlying database and then the other archives on the network.
If any objects are found, it will attempt to establish an association over which to store
the found objects (C-MOVE and move-thru only). If the association is established, it
will retrieve the found objects from the underlying platform or archive and store them
over the association, returning pending responses to the retrieval request initiator.
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 67 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
3.2.3.4.2
Presentation Context Table
The Enterprise Archive Manager will accept the following Transfer Syntaxes for each
presentation context in an association it receives:
Presentation Context Table
Abstract Syntax
Name
Patient Root
Query/Retrieve
Information
Model – MOVE
Study Root
Query/Retrieve
Information
Model – MOVE
Patient/Study
Only
Query/Retrieve
Information
Model – MOVE
3.2.3.4.3
UID
1.2.840.10008.5.1.4.1.2.1.2
1.2.840.10008.5.1.4.1.2.2.2
1.2.840.10008.5.1.4.1.2.3.2
Transfer Syntax
Name
UID
Little Endian Explicit VR
1.2.840.10008.1.2.1
Little Endian Implicit VR
1.2.840.10008.1.2
Big Endian Explicit VR
1.2.840.10008.1.2.2
Deflated Little Endian
Explicit VR
1.2.840.10008.1.2.1.99
Little Endian Explicit VR
1.2.840.10008.1.2.1
Little Endian Implicit VR
1.2.840.10008.1.2
Big Endian Explicit VR
1.2.840.10008.1.2.2
Deflated Little Endian
Explicit VR
1.2.840.10008.1.2.1.99
Little Endian Implicit VR
1.2.840.10008.1.2
Big Endian Explicit VR
1.2.840.10008.1.2.2
Deflated Little Endian
Explicit VR
1.2.840.10008.1.2.1.99
Role
Extended
Negotiation
SCP
Relational
SCP
Relational
SCP
Relational
SOP Specific Conformance for All Query/Retrieve SOP Classes
C-MOVE Status Codes
If the Enterprise Archive Manager returns one of the following status codes for CMOVE then the operation was unsuccessful. All status codes are in hexadecimal.
0110 (Processing Failure) – Indicates that an unknown error occurred during the
query.
C000 (Data Set Read Error) – Indicates that there was an error reading the move/get
parameters data set. This may be returned if the data set is corrupted. The Error
Comment field of the status will be populated with a description of the error
encountered.
C001 (Unable To Process) – Indicates that the archive was unable to fully process the
move/get. The Error Comment field of the status will be populated with a description of
the error encountered.
A900 (Identifier Does Not Match SOP Class) – Indicates that the move/get parameter
data set did not conform to the requirements of the presentation context it was
received across.
FE00 (Sub-Operations Terminated Due To Cancel Request) – Indicates that the
move/get request was terminated by the remote application entity prior to completion.
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 68 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
A701 (Unable To Calculate Number Of Matches) – Indicates that the archive was
unable to calculate the number of matching objects for this move/get request. May be
due to lack of resources.
A702 (Unable To Perform Sub-Operations) – Indicates that the archive was unable to
perform the storage sub-operations. May be due to lack of resources.
A801 (Move Destination Unknown) – Indicates that the archive was unable to connect
to the move destination.
3.2.3.4.4
Presentation Context Acceptance Criterion
There is no prioritization used for the acceptance of presentation contexts. Any
combination of supported transfer syntax and abstract syntax is accepted, in case the
product is configured for them.
3.2.3.4.5
Transfer Syntax Selection Policies
The Proxy selects transfer syntaxes in Acceptor first mode: the first transfer syntax in
the Proxy’s list of allowable transfer syntaxes that also exists in the proposed transfer
syntax list will be selected.
3.2.3.5
Accepting a Storage Commitment Request from a Remote System
3.2.3.5.1
Associated Real-World Activity
When the Proxy receives a storage commitment request (N-ACTION) it will
immediately respond with a status of success. It will then attempt to locate all objects
in the Archive Manager and Advanced Visualization for which storage commitment
was requested. Once it has located the objects, it will establish an association back to
the requesting entity and will send a storage commitment response (N-EVENTREPORT), detailing all objects that were/were not found. Upon completion of the NEVENT-REPORT, it will close the association.
3.2.3.5.2
Proposed Presentation Contexts
The Proxy will accept the following Transfer Syntaxes for each presentation context in
an association it receives:
Presentation Context Table
Abstract Syntax
Name
Storage
Commitment
Push Model
UID
1.2.840.10008.1.20.1
Transfer Syntax
Name
UID
Little Endian Explicit VR
1.2.840.10008.1.2.1
Little Endian Implicit VR
1.2.840.10008.1.2
Big Endian Explicit VR
1.2.840.10008.1.2.2
Deflated Little Endian
Explicit VR
1.2.840.10008.1.2.1.99
Role
SCP
Extended
Negotiation
None
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 69 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
3.2.3.5.3
SOP Specific Conformance for Storage Commitment Push SOP Class
The Proxy conforms to the SOP of the Storage Commitment Push Service Class fully.
Extended negotiation is not supported for the Storage Commitment Push Service
Class.
If the Proxy returns one of the following status codes for N-ACTION, then the request
for storage commitment was unsuccessful.
0119 (Class-instance conflict) – Indicates that the SOP Instance UID sent in the NACTION-RQ was not the Storage Commitment Push Model SOP Instance UID
(1.2.840.10008.1.20.1.1).
0110 (Processing Failure) – Indicates that an unknown error occurred during the
storage commitment.
3.2.3.5.4
Presentation Context Acceptance Criterion
There is no prioritization used for the acceptance of presentation contexts. Any
combination of supported transfer syntax and abstract syntax is accepted, in case the
product is configured for them.
3.2.3.5.5
Transfer Syntax Selection Policies
The Proxy selects transfer syntaxes in Acceptor first mode: the first transfer syntax in
the archive’s list of allowable transfer syntaxes that also exists in the proposed
transfer syntax list will be selected.
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 70 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
3.2.4 Worklist Manager Specification
This Application Entity provides Standard Conformance to the following DICOM V3.0
SOP Classes as an SCU and/or SCP (as indicated in the table) :
SOP Class Name
SOP Class UID
SCU/SCP
Verification
Verification
1.2.840.10008.1.1
N/Y
1.2.840.10008.5.1.4.31
N/Y
Modality Worklist
Modality Worklist Information Model - FIND
3.2.5 Association Establishment Policies
3.2.5.1
General
The Worklist Manager never initiates DICOM associations. The Worklist Manager has
configurable Maximum PDU sizes - both sent and received (the default is 50kb, both
sent and received).
3.2.5.2
Number of Associations
The Worklist Manager will accept any number of simultaneous associations up to a
configurable limit. The default limit (which may be increased or decreased) is 200
simultaneous connections. The maximum limit on the number of simultaneous
associations is dependent on the number of open file descriptors by the underlying
operating system.
3.2.5.3
Asynchronous Nature
The Worklist Manager will allow any number of asynchronous operations, whether
invoked or performed. The number of asynchronous operations is configurable.
3.2.5.4
Implementation Identifying Information
The Worklist Manager will provide a single Implementation Class UID and
Implementation Version Name as follows:
Worklist Manager Implementation Class UID
1.2.826.0.1.3680043.2.133.1.3
Implementation Version Name
5.30.5
3.2.6 Association Initiation by Real-World Activity
The Worklist Manager does not initiate associations.
3.2.7 Association Acceptance Policy
The Worklist Manager is configurable to allow security restrictions ranging from no
restrictions (promiscuous mode) to limiting successful association negotiation to a
known set of remote AEs for a configurable set of SOP classes.
If security is turned on, association attempts by unknown application entities will be
rejected outright and proposed presentation contexts from known remote application
entities may be rejected based on their allowed security permissions (allowable
service classes for the AE).
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 71 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
3.2.7.1
Respond to a Verification Request from a Remote System
3.2.7.1.1
Associated Real-World Activity
When the Worklist Manager receives a verification request (C-ECHO), it will respond
with a status of success if possible.
3.2.7.1.2
Presentation Context Table
The Worklist Manager will accept the following Transfer Syntaxes for each
presentation context in an association it receives:
Presentation Context Table
Abstract Syntax
Name
Verification
3.2.7.1.3
UID
1.2.840.10008.1.1
Transfer Syntax
Name
UID
Little Endian Explicit VR
1.2.840.10008.1.2.1
Little Endian Implicit VR
1.2.840.10008.1.2
Big Endian Explicit VR
1.2.840.10008.1.2.2
Role
SCP
Extended
Negotiation
None
SOP Specific Conformance – Verification
The Worklist Manager fully conforms to the SOP of the Verification Service class.
Extended negotiation is not supported for the Verification Service Class.
If the Worklist Manager returns anything other than success, then the C-ECHO
request failed.
3.2.7.1.4
Presentation Context Acceptance Criterion
There is no prioritization used for the acceptance of presentation contexts. Any
combination of supported transfer syntax and abstract syntax is accepted, in case the
product is configured for them.
3.2.7.1.5
Transfer Syntax Selection Policies
The Worklist Manager selects transfer syntaxes in Acceptor first mode: the first
transfer syntax in the Worklist Manager’s list of allowable transfer syntaxes that also
exists in the proposed transfer syntax list will be selected.
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 72 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
3.2.7.2
Respond to a Modality Worklist (MWL) Query Request from a Remote System
3.2.7.2.1
Associated Real-World Activity
This activity is initiated by an SCU, typically an imaging modality, which wishes to
query the Worklist Manager for information related to Scheduled Procedure Steps and
entities related to the Scheduled Procedure Steps. Part of this information is use by
the imaging modality itself, but much of the information is intended to be presented to
the modality operator.
3.2.7.2.2
Presentation Context Table
The Worklist Manager will accept the following Transfer Syntaxes for each
presentation context in an association it receives:
Presentation Context Table
Abstract Syntax
Name
Transfer Syntax
UID
Modality
Worklist
Information
Model - FIND
1.2.840.10008.5.1.4.31
3.2.7.2.3
Name
UID
Little Endian Explicit VR
1.2.840.10008.1.2.1
Little Endian Implicit VR
1.2.840.10008.1.2
Big Endian Explicit VR
1.2.840.10008.1.2.2
Extended
Negotiation
Role
SCP
None
SOP Specific Conformance
Worklist Manager provides standard conformance to the DICOM Modality Worklist
SOP Class as an SCP.
The Worklist Manager supports all required matching key types and all allowable
optional matching key attributes.
Subject to availability from the HIS/RIS, the Worklist Manager supports virtually all
required and optional return key attributes.
Worklist Manager supports the following elements for this SOP class:
Attribute Name
Tag
Query Keys
Matching
SCP
Query Keys
Return
SCP
SOP Common Module
SOP Class UID
(0008,0016)
Supported
Supported
SOP Instance UID
(0008,0018)
Supported (U)
Supported
Specific Character Set
(0008,0005)
Supported
Supported
Instance Creation Date
(0008,0012)
Supported
Supported
Instance Creation Time
(0008,0013)
Supported
Supported
Instance Creator UID
(0008,0014)
Supported
Supported
Instance Number
(0020,0013)
Supported
Supported
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 73 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
Attribute Name
Tag
Query Keys
Matching
SCP
Query Keys
Return
SCP
Patient Relationship Module
Referenced Visit Sequence
(0008,1125)
Supported
Supported
> Referenced SOP Class UID
(0008,1150)
Supported
Supported
> Referenced SOP Instance UID
(0008,1155)
Supported
Supported
Referenced Patient Alias Sequence
(0038,0004)
Supported
Supported
> Referenced SOP Class UID
(0008,1150)
Supported
Supported
> Referenced SOP Instance UID
(0008,1155)
Supported
Supported
Patient Name
(0010,0010)
Supported
Supported
Patient ID
(0010,0020)
Supported
Supported
Issuer of Patient ID
(0010,0021)
Supported
Supported
Other Patient Ids
(0010,1000)
Supported
Supported
Other Patient Names
(0010,1001)
Supported
Supported
Patient’s Birth Name
(0010,1005)
Supported
Supported
Patient’s Mother’s Birth Name
(0010,1060)
Supported
Supported
Medical Record Locator
(0010,1090)
Supported
Supported
Patient’s Age
(0010,1010)
Supported
Supported
Occupation
(0010,2180)
Supported
Supported
Patient Data Confidentiality Constraint Description
(0040,3001)
Supported
Supported
Patient’s Birth Date
(0010,0030)
Supported
Supported
Patient’s Birth Time
(0010,0032)
Supported
Supported
Patient’s Sex
(0010,0040)
Supported
Supported
Patient’s Insurance Plan Code Sequence
(0010,0050)
Supported
Supported
> Code Value
(0008,0100)
Supported
Supported
> Coding Scheme Designator
(0008,0102)
Supported
Supported
> Coding Scheme Version
(0008,0103)
Supported
Supported
> Code Meaning
(0008,0104)
Supported
Supported
Patient’s Size
(0010,1020)
Supported
Supported
Patient’s Weight
(0010,1030)
Supported
Supported
Patient’s Address
(0010,1040)
Supported
Supported
Military Rank
(0010,1080)
Supported
Supported
Branch of Service
(0010,1081)
Supported
Supported
County of Residence
(0010,2150)
Supported
Supported
Region of Residence
(0010,2152)
Supported
Supported
Patient Identification Module
Patient Demographic Module
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 74 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
Attribute Name
Tag
Query Keys
Matching
SCP
Query Keys
Return
SCP
Patient’s Telephone Numbers
(0010,2154)
Supported
Supported
Ethnic Group
(0010,2160)
Supported
Supported
Patient’s Religious Preference
(0010,21F0)
Supported
Supported
Patient Comments
(0010,4000)
Supported
Supported
Medical Alerts
(0010,2000)
Supported
Supported
Contrast Allergies
(0010,2110)
Supported
Supported
Smoking Status
(0010,21A0)
Supported
Supported
Additional Patient History
(0010,21B0)
Supported
Supported
Pregnancy Status
(0010,21C0)
Supported
Supported
Last Menstrual Date
(0010,21D0)
Supported
Supported
Special Needs
(0038,0050)
Supported
Supported
Patient State
(0038,0500)
Supported
Supported
Referenced Patient Sequence
(0008,1120)
Supported
Supported
> Referenced SOP Class UID
(0008,1150)
Supported
Supported
> Referenced SOP Instance UID
(0008,1155)
Supported
Supported
Institution Name
(0008,0080)
Supported
Supported
Institution Address
(0008,0081)
Supported
Supported
Institution Code Sequence
(0008,0082)
Supported
Supported
> Code Value
(0008,0100)
Supported
Supported
> Coding Scheme Designator
(0008,0102)
Supported
Supported
> Coding Scheme Version
(0008,0103)
Supported
Supported
> Code Meaning
(0008,0104)
Supported
Supported
Admission ID
(0038,0010)
Supported
Supported
Issuer of Admission ID
(0038,0011)
Supported
Supported
Visit Status ID
(0038,0008)
Supported
Supported
Current Patient Location
(0038,0300)
Supported
Supported
Patient’s Institutional Residence
(0038,0400)
Supported
Supported
Visit Comments
(0038,4000)
Supported
Supported
(0008,0090)
Supported
Supported
Patient Medical Module
Visit Relationship Module
Visit Identification Module
Visit Status Module
Visit Admission Module
Referring Physician’s Name
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 75 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
Attribute Name
Tag
Query Keys
Matching
SCP
Query Keys
Return
SCP
Referring Physician’s Address
(0008,0092)
Supported
Supported
Referring Physician’s Phone Numbers
(0008,0094)
Supported
Supported
Admitting Diagnosis Description
(0008,1080)
Supported
Supported
Admitting Diagnosis Code Sequence
(0008,1084)
Supported
Supported
> Code Value
(0008,0100)
Supported
Supported
> Coding Scheme Designator
(0008,0102)
Supported
Supported
> Coding Scheme Version
(0008,0103)
Supported
Supported
> Code Meaning
(0008,0104)
Supported
Supported
Route of Admissions
(0038,0016)
Supported
Supported
Admitting Date
(0038,0020)
Supported
Supported
Admitting Time
(0038,0021)
Supported
Supported
Scheduled Procedure Step Sequence
(0040,0100)
Supported
Supported
> Scheduled Station AE Title
(0040,0001)
Supported
Supported
> Scheduled Station Name
(0040,0010)
Supported
Supported
> Scheduled Procedure Step Location
(0040,0011)
Supported
Supported
> Scheduled Procedure Step Start Date
(0040,0002)
Supported
Supported
> Scheduled Procedure Step Start Time
(0040,0003)
Supported
Supported
> Scheduled Procedure Step End Date
(0040,0004)
Supported
Supported
> Scheduled Procedure Step End Time
(0040,0005)
Supported
Supported
> Scheduled Performing Physician’s Name
(0040,0006)
Supported
Supported
> Scheduled Procedure Step Description
(0040,0007)
Supported
Supported
> Scheduled Protocol Sequence
(0040,0008)
Supported
Supported
>> Code Value
(0008,0100)
Supported
Supported
>> Coding Scheme Designator
(0008,0102)
Supported
Supported
>> Coding Scheme Version
(0008,0103)
Supported
Supported
>> Code Meaning
(0008,0104)
Supported
Supported
>> Protocol Context Sequence
(0040, 0440)
Not Supported
Not Supported
> Scheduled Procedure Step ID
(0040,0009)
Supported
Supported
> Scheduled Procedure Step Status
(0040,0020)
Supported
Supported
> Comments on the Scheduled Procedure Step
(0040,0400)
Supported
Supported
> Modality
(0008,0060)
Supported
Supported
> Requested Contrast Agent
(0032,1070)
Supported
Supported
> Pre-medication
(0040,0012)
Supported
Supported
Scheduled Procedure Step Module
Requested Procedure Step Module
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 76 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
Attribute Name
Tag
Query Keys
Matching
SCP
Query Keys
Return
SCP
Requested Procedure ID
(0040,1001)
Supported
Supported
Reason for the Requested Procedure
(0040,1002)
Supported
Supported
Requested Procedure Comments
(0040,1400)
Supported
Supported
Requested Procedure Code Sequence
(0032,1064)
Supported
Supported
> Code Value
(0008,0100)
Supported
Supported
> Coding Scheme Designator
(0008,0102)
Supported
Supported
> Coding Scheme Version
(0008,0103)
Supported
Supported
> Code Meaning
(0008,0104)
Supported
Supported
Study Instance UID
(0020,000D)
Supported
Supported
Referenced Study Sequence
(0008,1110)
Supported
Supported
> Referenced SOP Class UID
(0008,1150)
Supported
Supported
> Referenced SOP Instance UID
(0008,1155)
Supported
Supported
Requested Procedure Description
(0032,1060)
Supported
Supported
Requested Procedure Priority
(0040,1003)
Supported
Supported
Patient Transport Arrangements
(0040,1004)
Supported
Supported
Requested Procedure Location
(0040,1005)
Supported
Supported
Confidentiality Code
(0040,1008)
Supported
Supported
Reporting Priority
(0040,1009)
Supported
Supported
Names of Intended Recipients of Results
(0040,1010)
Supported
Supported
Reason for the Imaging Service Request
(0040,2001)
Supported
Supported
Imaging Service Request Comments
(0040,2400)
Supported
Supported
Requesting Physician
(0032,1032)
Supported
Supported
Referring Physician’s Name
(0008,0090)
Supported
Supported
Requesting Service
(0032,1033)
Supported
Supported
Accession Number
(0008,0050)
Supported
Supported
Issuing Date of Imaging Service Request
(0040,2004)
Supported
Supported
Issuing Time of Imaging Service Request
(0040,2005)
Supported
Supported
Placer Order Number / Imaging Service Request
(0040,2016)
Supported
Supported
Filler Order Number / Imaging Service Request
(0040,2017)
Supported
Supported
Order Entered By…
(0040,2008)
Supported
Supported
Order Enterer’s Location
(0040,2009)
Supported
Supported
Order Callback Number
(0040,2010)
Supported
Supported
Imaging Service Request Module
(U) = Unique
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 77 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
C-FIND Status Codes – Modality Worklist Query
The Worklist Manager shall return, via the C-FIND response primitive, the C-FIND
Response Status Code applicable to the associated request.
If the Worklist Manager returns one of the following status codes for C-FIND then the
operation was unsuccessful. All status codes are in hexadecimal.
0110(Processing Failure) – Indicates that an unknown error occurred during the query.
C000 (Data Set Read Error) – Indicates that there was an error reading the query
parameters data set. This may be returned if the data set is corrupted. The Error
Comment field of the status will be populated with a description of the error encountered.
C001 (Unable To Process) – Indicates that the archive was unable to fully process the
query. The Error Comment field of the status will be populated with a description of the
error encountered.
A900 (Identifier Does Not Match SOP Class) – Indicates that the query parameter data
set did not conform to the requirements of the presentation context it was received
across.
FE00 (Matching Terminated Due To Cancel Request) – Indicates that the query
operation was terminated by the remote application entity prior to completion.
A700 (Out Of Resources) – Indicates that the archive ran out of resources to process the
query request.
DICOM PS 3.4-2003 Table K.4-1 defines the status values specific to this SOP Class and
DIMSE Service.
Query implementation specifics – Modality Worklist Query
When the Worklist Manager receives a Modality Worklist Query request it will resolve the
request against the underlying database and return all matching items (general purpose
scheduled procedure steps) and requested return keys to the query initiator.
Person Names are stored in the database in uppercase. All VR PN attributes found in
query datasets will be converted to uppercase before a database query is made.
Because of this, the system in effect supports case-insensitive matching for PN VR
attributes.
Per the recommendation by IHE, SCUs are recommended to append wildcard “*” at the
end of each component of any structured name to facilitate matching.
3.2.7.2.4
Presentation Context Acceptance Criterion
There is no prioritization used for the acceptance of presentation contexts. Any
combination of supported transfer syntax and abstract syntax is accepted, in case the
product is configured for them.
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 78 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
3.2.7.2.5
Transfer Syntax Selection Policies
The Worklist Manager selects transfer syntaxes in Acceptor first mode: the first
transfer syntax in the Worklist Manager’s list of allowable transfer syntaxes that also
exists in the proposed transfer syntax list will be selected.
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 79 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
3.3
Prefetcher Specification
This Application Entity provides Standard Conformance to the following DICOM V3.0
SOP Classes as an SCU and/or SCP (as indicated in the table):
SOP Class Name
SOP Class UID
SCU/SCP
BSCN
Basic Study Content Notification
1.2.840.10008.1.9
N/Y
Study Root Query/Retrieve Information
Model – FIND
1.2.840.10008.5.1.4.1.2.2.1
Y/N
Study Root Query/Retrieve Information
Model – MOVE
1.2.840.10008.5.1.4.1.2.2.2
Y/N
Query/Retrieve
3.3.1 Association Establishment Policies
3.3.1.1
General
The Prefetcher is capable of querying and making move requests to other DICOM archives
according to user configurable rules. This feature is known as “prefetching.” When
performing prefetching functions, the Prefetcher will attempt to establish associations with
remote application entities in order to query for and request the move of objects.
The Prefetcher has configurable Maximum PDU sizes, both sent and received (the default
is 50KB, both sent and received).
3.3.1.2
Number of Associations
The Prefetcher will establish any number of simultaneous associations performing
DICOM Queries, depending only on the environmental triggering events and the rule
implementations.
The Prefetcher will establish any number of associations performing DICOM Moves, up to a
configurable limit. This limit is configurable from the Prefetcher administration utilities and
is specific to the AE of the Move SCP. Distinct Move SCPs can have distinct limits.
3.3.1.3
Asynchronous Nature
The Prefetcher will accept only 1 operation per association as a BSCN SCU.
In all SOP Classes where the Prefetcher acts as an SCP, the Prefetcher will invoke
only 1 operation per association.
3.3.1.4
Implementation identifying Information
The Pre-fetcher will provide a single Implementation Class UID and Implementation
Version Name as follows:
Pre-fetcher Implementation Class UID (BSCN
SCP, Query SCU)
Pre-fetcher Implementation Class UID (Move
SCU)
Implementation Version Name
1.2.826.0.1.3680043.2.133.1.4.2
1.2.826.0.1.3680043.2.133.1.4.1
none provided
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 80 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
3.3.2 Association Initiation by Real-World Activity
The Prefetcher will initiate an association to a remote entity when triggered by receipt
of an event, which causes a configured prefetching rule to look for priors. Additionally,
the Prefetcher will initiate an association to a remote device at the scheduled delivery
time of priors.
3.3.2.1
Query a Remote DICOM Device
3.3.2.1.1
Associated Real-World Activity
An triggering event (receipt of an HL7 or BSCN message) invokes a prefetch rule.
The pre-fetcher will initiate an association to the configured destination to search for
data which that may be relevant older procedures performed. The search queries for
data based on the following:
•
•
•
3.3.2.1.2
A matching patient.
Prior images of a patient.
Objects within a study.
Proposed Presentation Contexts
The Prefetcher will propose the following Transfer Syntaxes for each presentation
context in an association it initiates:
Presentation Context Table
Abstract Syntax
Name
Study Root
Query/Retrieve
Information
Model – FIND
3.3.2.1.3
Transfer Syntax
UID
Name
1.2.840.10008.5.1.4.1.2.2.1
UID
Little Endian Explicit VR
1.2.840.10008.1.2.1
Little Endian Implicit VR
1.2.840.10008.1.2
Big Endian Explicit VR
1.2.840.10008.1.2.2
Deflated Little Endian
Explicit VR
1.2.840.10008.1.2.1.99
Role
SCU
Extended
Negotiation
none
SOP Specific Conformance Statement for Query SOP Class
Query Attributes
The query attributes can vary depending on the configured rules, which can add
arbitrary tags to the query using an internal API. However, the following attributes are
included in the queries by default:
Patient Level Query
Attribute Tag
(0010, 0010)
(0010, 0020)
(0010, 0021)
(0010, 0030)
(0010, 0040)
Element Name
Patient Name
Patient ID
Issuer of Patient ID
Patient Birth Date
Patient Sex
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 81 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
Study Level Query
Attribute Tag
(0008, 0020)
(0008, 0030)
(0008, 0050)
(0008, 0061)
(0020, 000D)
(0020, 0010)
Element Name
Study Date
Study Time
Accession Number
Modalities In Study
Study Instance UID
Study ID
3.3.2.2
Request a Move Association to a Remote System
3.3.2.2.1
Associated Real-World Activity
A prefetch order previously scheduled is due for delivery. The Prefetcher will make CMOVE requests to the source entity of the prior exam determined to be needed by the
rule.
3.3.2.2.2
Proposed Presentation Contexts
The Prefetcher will propose the following Transfer Syntaxes for each presentation
context in an association it initiates:
Presentation Context Table
Abstract Syntax
Name
Study Root
Query/Retrieve
Information
Model – MOVE
3.3.2.2.3
Transfer Syntax
UID
Name
1.2.840.10008.5.1.4.1.2.2.2
UID
Little Endian Explicit VR
1.2.840.10008.1.2.1
Little Endian Implicit VR
1.2.840.10008.1.2
Big Endian Explicit VR
1.2.840.10008.1.2.2
Deflated Little Endian
Explicit VR
1.2.840.10008.1.2.1.99
Role
Extended
Negotiation
SCU
none
SOP Specific Conformance Statement for Move SOP Class
Query Attributes
The move request attributes can vary depending on the configured patient resolution
strategy. Not all patient level attributes may be present as a result of said strategy.
The following is a super set of possible attributes:
Study Level Move
Attribute Tag
(0010, 0010)
(0010, 0020)
(0010, 0021)
(0010, 0030)
(0010, 0032)
(0010, 0040)
(0020, 000D)
Element Name
Patient Name
Patient ID
Issuer of Patient ID
Patient Birth Date
Patient Birth Time
Patient Sex
Study Instance UID
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 82 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
Image Level Move
Attribute Tag
(0008, 0018)
(0010, 0010)
(0010, 0020)
(0010, 0021)
(0010, 0030)
(0010, 0032)
(0010, 0040)
(0020, 000D)
(0020, 000E)
Element Name
SOP Instance UID
Patient Name
Patient ID
Issuer of Patient ID
Patient Birth Date
Patient Birth Time
Patient Sex
Study Instance UID
Series Instance UID
3.3.3 Association Acceptance Policy
The Prefetcher accepts only BSCN messages. All remaining DICOM activity
performed by the Prefetcher is in a SCU role. Acceptance of BSCN messages is used
to support triggering of Prefetch rules.
3.3.3.1
Receive a BSCN message from a Remote System
3.3.3.1.1
Associated Real-World Activity
The Prefetcher supports only BSCN storage. Any other association types will be
rejected. The associated data set of a BSCN will be used internally for triggering
prefetching. The data set is not persisted, or retransmitted.
3.3.3.1.2
Presentation Context Tables
The following presentation contexts are supported by the Prefetcher during
association establishment:
Presentation Context Table
Abstract Syntax
Name
Basic Study
Content
Notification
3.3.3.1.3
UID
1.2.840.10008.1.9
Transfer Syntax
Name
UID
Little Endian Explicit VR
1.2.840.10008.1.2.1
Little Endian Implicit VR
1.2.840.10008.1.2
Big Endian Explicit VR
1.2.840.10008.1.2.2
Deflated Little Endian
Explicit VR
1.2.840.10008.1.2.1.99
Role
SCP
Extended
Negotiation
None
SOP Specific Conformance for all Storage SOP Classes
The Prefetcher does not store images, and therefore does not verify their storage. As
a result, the response BSCN Status Code is always: 0x003 Success.
The Prefetcher will as a result of a BSCN trigger internal prefetching rules that have
expressed interest in these types of events. The result of rule execution is determined
by the rule implementation. Typically, a rule will query a storage AE for related
images and schedule the transfer (C-MOVE) of those images to another AE.
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 83 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
3.3.3.1.4
Presentation Context Acceptance Criterion
There is no prioritization used for the acceptance of presentation contexts. Any
combination of supported transfer syntax and abstract syntax is accepted, in case the
product is configured for them.
3.3.3.1.5
Transfer Syntax Selection Policies
The Prefetcher always selects a transfer syntax using an acceptor first policy.
Acceptor first – the first transfer syntax in the Prefetcher’s list of allowable transfer
syntaxes that also exists in the proposed transfer syntax list will be selected.
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 84 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
3.4
Technologist Workflow (TWF) Specification
This Application Entity provides Standard Conformance to the following DICOM V3.0
SOP Classes as an SCP:
SOP Class Name
SOP Class UID
SCU/SCP
Verification
Verification
1.2.840.10008.1.1
N/Y
12-lead ECG Waveform Storage
1.2.840.10008.5.1.4.1.1.9.1.1
N/Y
Ambulatory ECG Waveform Storage
1.2.840.10008.5.1.4.1.1.9.1.3
N/Y
Basic Text SR Storage
1.2.840.10008.5.1.4.1.1.88.11
N/Y
Basic Voice Audio Waveform Storage
1.2.840.10008.5.1.4.1.1.9.4.1
N/Y
Storage
Cardiac Electrophysiology Waveform Storage
1.2.840.10008.5.1.4.1.1.9.3.1
N/Y
Comprehensive SR Storage
1.2.840.10008.5.1.4.1.1.88.33
N/Y
Computed Radiography Image Storage
1.2.840.10008.5.1.4.1.1.1
N/Y
CT Image Storage
1.2.840.10008.5.1.4.1.1.2
N/Y
Digital X-Ray Image Storage (Presentation)
1.2.840.10008.5.1.4.1.1.1.1
N/Y
Digital X-Ray Image Storage (Processing)
1.2.840.10008.5.1.4.1.1.1.1.1
N/Y
Digital Mammography Image Storage
(Presentation)
1.2.840.10008.5.1.4.1.1.1.2
N/Y
Digital Mammography Image Storage
(Processing)
1.2.840.10008.5.1.4.1.1.1.2.1
N/Y
Digital Intra-oral X-Ray Image Storage
(Presentation)
1.2.840.10008.5.1.4.1.1.1.3
N/Y
Digital Intra-oral X-Ray Image Storage
(Processing)
1.2.840.10008.5.1.4.1.1.1.3.1
N/Y
Enhanced SR Storage
1.2.840.10008.5.1.4.1.1.88.22
N/Y
General ECG Waveform Storage
1.2.840.10008.5.1.4.1.1.9.1.2
N/Y
Grayscale Softcopy Presentation State Storage
1.2.840.10008.5.1.4.1.1.11.1
N/Y
Hardcopy Color Image Storage
1.2.840.10008.5.1.1.30
N/Y
Hardcopy Grayscale Image Storage
1.2.840.10008.5.1.1.29
N/Y
Hemodynamic Waveform Storage
1.2.840.10008.5.1.4.1.1.9.2.1
N/Y
Key Object Selection Document
1.2.840.10008.5.1.4.1.1.88.59
N/Y
Mammography CAD SR
1.2.840.10008.5.1.4.1.1.88.50
N/Y
Multi-frame Single Bit Secondary Capture
Image Storage
1.2.840.10008.5.1.4.1.1.7.1
N/Y
Multi-frame Grayscale Byte Secondary Capture
Image Storage
1.2.840.10008.5.1.4.1.1.7.2
N/Y
Multi-frame Grayscale Word Secondary
Capture Image Storage
1.2.840.10008.5.1.4.1.1.7.3
N/Y
Multi-frame True Color Secondary Capture
Image Storage
1.2.840.10008.5.1.4.1.1.7.4
N/Y
MR Image Storage
1.2.840.10008.5.1.4.1.1.4
N/Y
Nuclear Medicine Image Storage
1.2.840.10008.5.1.4.1.1.20
N/Y
Nuclear Medicine Image Storage (Retired)
1.2.840.10008.5.1.4.1.1.5
N/Y
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 85 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
SOP Class Name
SOP Class UID
SCU/SCP
Positron Emission Tomography Image Storage
1.2.840.10008.5.1.4.1.1.128
N/Y
RT Beams Treatment Record Storage
1.2.840.10008.5.1.4.1.1.481.4
N/Y
RT Brachy Treatment Record Storage
1.2.840.10008.5.1.4.1.1.481.6
N/Y
RT Dose Storage
1.2.840.10008.5.1.4.1.1.481.2
N/Y
RT Image Storage
1.2.840.10008.5.1.4.1.1.481.1
N/Y
RT Plan Storage
1.2.840.10008.5.1.4.1.1.481.5
N/Y
RT Structure Set Storage
1.2.840.10008.5.1.4.1.1.481.3
N/Y
RT Treatment Summary Record Storage
1.2.840.10008.5.1.4.1.1.481.7
N/Y
Secondary Capture Image Storage
1.2.840.10008.5.1.4.1.1.7
N/Y
Stand-alone Curve Storage
1.2.840.10008.5.1.4.1.1.9
N/Y
Stand-alone Modality LUT Storage
1.2.840.10008.5.1.4.1.1.10
N/Y
Stand-alone Overlay Storage
1.2.840.10008.5.1.4.1.1.8
N/Y
Stand-alone VOI LUT Storage
1.2.840.10008.5.1.4.1.1.11
N/Y
Standalone PET Curve Storage
1.2.840.10008.5.1.4.1.1.129
N/Y
Stored Print Storage
1.2.840.10008.5.1.1.27
N/Y
Ultrasound Image Storage
1.2.840.10008.5.1.4.1.1.6.1
N/Y
Ultrasound Image Storage (Retired)
1.2.840.10008.5.1.4.1.1.6
N/Y
Ultrasound Multi-frame Image Storage
1.2.840.10008.5.1.4.1.1.3.1
N/Y
Ultrasound Multi-frame Image Storage
(Retired)
1.2.840.10008.5.1.4.1.1.3
N/Y
VL Endoscopic Image Storage
1.2.840.10008.5.1.4.1.1.77.1.1
N/Y
VL Microscopic Image Storage
1.2.840.10008.5.1.4.1.1.77.1.2
N/Y
VL Slide-Coordinates Microscopic Image
Storage
1.2.840.10008.5.1.4.1.1.77.1.3
N/Y
VL Photographic Image Storage
1.2.840.10008.5.1.4.1.1.77.1.4
N/Y
X-Ray Angiographic Bi-Plane Image Storage
(retired)
1.2.840.10008.5.1.4.1.1.12.3
N/Y
X-Ray Angiographic Image Storage
1.2.840.10008.5.1.4.1.1.12.1
N/Y
X-Ray Radiofluoroscopic Image Storage
1.2.840.10008.5.1.4.1.1.12.2
N/Y
1.2.840.10008.5.1.4.31
Y/N
Modality Worklist
Modality Worklist Information Model – FIND
3.4.1 Association Establishment Policies
3.4.1.1
General
The TWF will create an association with the MWL C-FIND SCP when prompted by the
user. The TWF has configurable Maximum PDU sizes - both sent and received (the
default is 1024kb, both sent and received).
3.4.1.2
Number of Associations
Outgoing associations for the C-FIND requests are pooled with the size of the pool
being configurable. The default pool size is for 5 simultaneous associations.
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 86 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
3.4.1.3
Asynchronous Nature
The TWF will allow any number of asynchronous operations, whether invoked and
performed. This number of asynchronous operations is configurable. Implementation
Identifying Information
The TWF will provide a single Implementation Class UID and Implementation Version
Name as follows:
DICOM Component Implementation Class UID
1.2.826.0.1.3680043.2.133.1.1
Implementation Version Name
3.1.9
3.4.2 Association Initiation by Real-World Activity
The TWF will attempt to initiate one association for each C-FIND request from the
user. The association will be initiated once a user chooses to query the MWL for the
patient demographic information to be used in the reconciliation. The query can be
done for a configurable set of attributes.
3.4.2.1
Query Modality Worklist
3.4.2.1.1
Associated Real-World Activity
The user selects a study within TWF to be reconciled. The MWL is queried by TWF for
a set of defined attributes. The results are returned and the user has the option to
choose the best match to reconcile the patient demographic data.
3.4.2.1.2
Proposed Presentation Contexts
Presentation Context Table
Abstract Syntax
Name
Modality
Worklist
Information
Model – FIND
3.4.2.1.3
Transfer Syntax
UID
1.2.840.10008.5.1.4.31
Name
UID
Little Endian Explicit VR 1.2.840.10008.1.2.1
Role
Extended
Negotiation
SCU
None
Information Model
TWF will attempt to query the MWL for the following default attributes. The attributes
used for identification by the TWF are configurable:
Attribute Name
Tag
Query Keys Matching SCU
Patient ID
(0010, 0020)
Supported
Scheduled Procedure Step Sequence
(0040, 0100)
Supported
Modality
(0008, 0060)
Supported
Accession Number
(0008, 0050)
Supported
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 87 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
3.4.3 Association Acceptance Policy
When the TWF accepts an association, it will allow the storage of objects and
verification of the TWF interface.
The TWF will accept any number of simultaneous associations, the number of which
can be configured. The maximum limit on the number of simultaneous associations is
dependent on the number of open file descriptors allowed by the underlying operating
system.
The TWF is configurable to allow security restrictions ranging from no restrictions
(promiscuous) to limiting a particular remote application entity to specified SOP
classes and specified SCU/SCP roles. If security is turned on, association attempts
by unknown entities will be rejected outright and proposed presentation contexts from
known remote application entities may be rejected based on their allowed security
permissions.
3.4.3.1
Store DICOM Objects
3.4.3.1.1
Associated Real-World Activity
This activity is initiated by a modality lacking worklist functionality to populate the
patient demographic information in the acquired images. The technologist pushes the
images to the unique AE-title of the TWF interface for reconciliation.
3.4.3.1.2
Presentation Contexts
Presentation Context Table
Abstract Syntax
Name
UID
Transfer Syntax
Role
Extended
Negotiation
12-lead ECG Waveform Storage
1.2.840.10008.5.1.4.1.1.9.1.1
See Table 3.6.2.1.2-1
SCP
None
Ambulatory ECG Waveform Storage
1.2.840.10008.5.1.4.1.1.9.1.3
See Table 3.6.2.1.2-1
SCP
None
Basic Study Content Notification
1.2.840.10008.1.9
See Table 3.6.2.1.2-1
SCP
None
Basic Text SR Storage
1.2.840.10008.5.1.4.1.1.88.11
See Table 3.6.2.1.2-1
SCP
None
Basic Voice Audio Waveform
Storage
1.2.840.10008.5.1.4.1.1.9.4.1
See Table 3.6.2.1.2-1
SCP
None
Cardiac Electrophysiology
Waveform Storage
1.2.840.10008.5.1.4.1.1.9.3.1
See Table 3.6.2.1.2-1
SCP
None
Comprehensive SR Storage
1.2.840.10008.5.1.4.1.1.88.33
See Table 3.6.2.1.2-1
SCP
None
Computed Radiography Image
Storage
1.2.840.10008.5.1.4.1.1.1
See Table 3.6.2.1.2-1
SCP
None
CT Image Storage
1.2.840.10008.5.1.4.1.1.2
See Table 3.6.2.1.2-1
SCP
None
Digital X-Ray Image Storage
(Presentation)
1.2.840.10008.5.1.4.1.1.1.1
See Table 3.6.2.1.2-1
SCP
None
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 88 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
Presentation Context Table
Abstract Syntax
Name
UID
Transfer Syntax
Role
Extended
Negotiation
Digital X-Ray Image Storage
(Processing)
1.2.840.10008.5.1.4.1.1.1.1.1
See Table 3.6.2.1.2-1
SCP
None
Digital Mammography Image
Storage (Presentation)
1.2.840.10008.5.1.4.1.1.1.2
See Table 3.6.2.1.2-1
SCP
None
Digital Mammography Image
Storage (Processing)
1.2.840.10008.5.1.4.1.1.1.2.1
See Table 3.6.2.1.2-1
SCP
None
Digital Intra-oral X-Ray Image
Storage (Presentation)
1.2.840.10008.5.1.4.1.1.1.3
See Table 3.6.2.1.2-1
SCP
None
Digital Intra-oral X-Ray Image
Storage (Processing)
1.2.840.10008.5.1.4.1.1.1.3.1
See Table 3.6.2.1.2-1
SCP
None
Enhanced SR Storage
1.2.840.10008.5.1.4.1.1.88.22
See Table 3.6.2.1.2-1
SCP
None
General ECG Waveform Storage
1.2.840.10008.5.1.4.1.1.9.1.2
See Table 3.6.2.1.2-1
SCP
None
Grayscale Softcopy Presentation
State Storage
1.2.840.10008.5.1.4.1.1.11.1
See Table 3.6.2.1.2-1
SCP
None
Hardcopy Color Image Storage
1.2.840.10008.5.1.1.30
See Table 3.6.2.1.2-1
SCP
None
Hardcopy Grayscale Image Storage
1.2.840.10008.5.1.1.29
See Table 3.6.2.1.2-1
SCP
None
Hemodynamic Waveform Storage
1.2.840.10008.5.1.4.1.1.9.2.1
See Table 3.6.2.1.2-1
SCP
None
Key Object Selection Document
1.2.840.10008.5.1.4.1.1.88.59
See Table 3.6.2.1.2-1
SCP
None
Mammography CAD SR
1.2.840.10008.5.1.4.1.1.88.50
See Table 3.6.2.1.2-1
SCP
None
Multi-frame Single Bit Secondary
Capture Image Storage
1.2.840.10008.5.1.4.1.1.7.1
See Table 3.6.2.1.2-1
SCP
None
Multi-frame Grayscale Byte
Secondary Capture Image Storage
1.2.840.10008.5.1.4.1.1.7.2
See Table 3.6.2.1.2-1
SCP
None
Multi-frame Grayscale Word
Secondary Capture Image Storage
1.2.840.10008.5.1.4.1.1.7.3
See Table 3.6.2.1.2-1
SCP
None
Multi-frame True Color Secondary
Capture Image Storage
1.2.840.10008.5.1.4.1.1.7.4
See Table 3.6.2.1.2-1
SCP
None
MR Image Storage
1.2.840.100008.5.1.4.1.1.4
See Table 3.1.2.1.2-1
SCP
None
Nuclear Medicine Image Storage
1.2.840.10008.5.1.4.1.1.20
See Table 3.1.2.1.2-1
SCP
None
Nuclear Medicine Image Storage
(Retired)
1.2.840.10008.5.1.4.1.1.5
See Table 3.1.2.1.2-1
SCP
None
Positron Emission Tomography
Image Storage
1.2.840.10008.5.1.4.1.1.128
See Table 3.1.2.1.2-1
SCP
None
RT Beams Treatment Record
Storage
1.2.840.10008.5.1.4.1.1.481.4
See Table 3.6.2.1.2-1
SCP
None
RT Brachy Treatment Record
Storage
1.2.840.10008.5.1.4.1.1.481.6
See Table 3.6.2.1.2-1
SCP
None
RT Dose Storage
1.2.840.10008.5.1.4.1.1.481.2
See Table 3.6.2.1.2-1
SCP
None
RT Image Storage
1.2.840.10008.5.1.4.1.1.481.1
See Table 3.6.2.1.2-1
SCP
None
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 89 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
Presentation Context Table
Abstract Syntax
Name
UID
Transfer Syntax
Role
Extended
Negotiation
RT Plan Storage
1.2.840.10008.5.1.4.1.1.481.5
See Table 3.6.2.1.2-1
SCP
None
RT Structure Set Storage
1.2.840.10008.5.1.4.1.1.481.3
See Table 3.6.2.1.2-1
SCP
None
RT Treatment Summary Record
Storage
1.2.840.10008.5.1.4.1.1.481.7
See Table 3.6.2.1.2-1
SCP
None
Secondary Capture Image Storage
1.2.840.10008.5.1.4.1.1.7
See Table 3.6.2.1.2-1
SCP
None
Stand-alone Curve Storage
1.2.840.10008.5.1.4.1.1.9
See Table 3.6.2.1.2-1
SCP
None
Stand-alone Modality LUT Storage
1.2.840.10008.5.1.4.1.1.10
See Table 3.6.2.1.2-1
SCP
None
Stand-alone Overlay Storage
1.2.840.10008.5.1.4.1.1.8
See Table 3.6.2.1.2-1
SCP
None
Stand-alone VOI LUT Storage
1.2.840.10008.5.1.4.1.1.11
See Table 3.6.2.1.2-1
SCP
None
Standalone PET Curve Storage
1.2.840.10008.5.1.4.1.1.129
See Table 3.6.2.1.2-1
SCP
None
Stored Print Storage
1.2.840.10008.5.1.1.27
See Table 3.6.2.1.2-1
SCP
None
Ultrasound Image Storage
1.2.840.10008.5.1.4.1.1.6.1
See Table 3.6.2.1.2-1
SCP
None
Ultrasound Image Storage (Retired)
1.2.840.10008.5.1.4.1.1.6
See Table 3.6.2.1.2-1
SCP
None
Ultrasound Multi-frame Image
Storage
1.2.840.10008.5.1.4.1.1.3.1
See Table 3.6.2.1.2-1
SCP
None
Ultrasound Multi-frame Image
Storage (Retired)
1.2.840.10008.5.1.4.1.1.3
See Table 3.6.2.1.2-1
SCP
None
VL Endoscopic Image Storage
1.2.840.10008.5.1.4.1.1.77.1.1
See Table 3.6.2.1.2-1
SCP
None
VL Microscopic Image Storage
1.2.840.10008.5.1.4.1.1.77.1.2
See Table 3.6.2.1.2-1
SCP
None
VL Slide-Coordinates Microscopic
Image Storage
1.2.840.10008.5.1.4.1.1.77.1.3
See Table 3.6.2.1.2-1
SCP
None
VL Photographic Image Storage
1.2.840.10008.5.1.4.1.1.77.1.4
See Table 3.6.2.1.2-1
SCP
None
X-Ray Angiographic Bi-Plane Image
Storage (retired)
1.2.840.10008.5.1.4.1.1.12.3
See Table 3.6.2.1.2-1
SCP
None
X-Ray Angiographic Image Storage
1.2.840.10008.5.1.4.1.1.12.1
See Table 3.6.2.1.2-1
SCP
None
X-Ray Radiofluoroscopic Image
Storage
1.2.840.10008.5.1.4.1.1.12.2
See Table 3.6.2.1.2-1
SCP
None
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 90 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
Table 3.6.2.1.2-1
Transfer Syntax for Receive from a Remote System
Name
UID
Little Endian Explicit VR
1.2.840.10008.1.2.1
Little Endian Implicit VR
1.2.840.10008.1.2
Big Endian Explicit VR
1.2.840.10008.1.2.2
Deflated Little Endian Explicit VR
1.2.840.10008.1.2.1.99
Lossy JPEG Image Compression (8-bit, coding
Process 1)
1.2.840.10008.1.2.4.50
Lossy JPEG Image Compression (12-bit, coding
Process 4)
1.2.840.10008.1.2.4.51
Lossless JPEG Image Compression (baseline)
1.2.840.10008.1.2.4.70
3.4.3.2
Respond to a Verification Request from a Remote System
3.4.3.2.1
Associated Real-World Activity
When the TWF receives a verification request (C-ECHO) it will respond with a status
of success if possible.
3.4.3.2.2
Presentation Context Table
The TWF will accept the following Transfer Syntaxes for each presentation context in
an association it receives:
Presentation Context Table
Abstract Syntax
Name
Verification
3.4.3.2.3
UID
1.2.840.10008.1.1
Transfer Syntax
Name
UID
Little Endian Explicit VR
1.2.840.10008.1.2.1
Little Endian Implicit VR
1.2.840.10008.1.2
Big Endian Explicit VR
1.2.840.10008.1.2.2
Deflated Little Endian
Explicit VR
1.2.840.10008.1.2.1.99
Role
SCP
Extended
Negotiation
None
SOP Specific Conformance for Verification SOP Class
The TWF conforms to the SOP of the Verification Service Class fully.
Extended negotiation is not supported for the Verification Service Class.
If the TWF returns anything other than success then the C-ECHO operation failed.
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 91 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
3.4.3.2.4
Presentation Context Acceptance Criterion
There is no prioritization used for the acceptance of presentation contexts. Any
combination of supported transfer syntax and abstract syntax is accepted, in case the
product is configured for them.
3.4.3.2.5
Transfer Syntax Selection Policies
The TWF selects transfer syntaxes in Acceptor first mode: the first transfer syntax in
the TWF’s list of allowable transfer syntaxes that also exists in the proposed transfer
syntax list will be selected.
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 92 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
4
4.1
Communication Profiles
Supported Communication Stacks (Parts 8,9)
System 5.30 provides DICOM V3.0 TCP/IP Network Support as defined in PS3.8.
4.2
TCP/IP Stack
System 5.30 inherits its TCP/IP stack from the Java virtual machine, and, by default,
the underlying platform on which the virtual machine is executing.
4.2.1 API
The API used to enable the TCP/IP stack for System 5.30 is the Java Socket API
found in the java.net package of the Java Development Kit.
4.2.2 Physical Media Support
System 5.30 is indifferent to the physical medium over which TCP/IP executes. This
is inherited from the particular platform that the Java virtual machine is executing on.
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 93 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
5
5.1
Extensions/Specializations/Privatizations
Standard Extended/Specialized/Private SOPs
System 5.30 supports Standard Extended, Specialized, and Private Storage SOPs as
long as they conform to the Storage Service Class specification (PS3.4, Annex B).
System 5.30 supports Standard Extended, Specialized, and Private Query/Retrieve
SOPs as long as they conform to the Query/Retrieve Service Class specification
(PS3.4, Annex C).
No other Standard Extended, Specialized, and Private SOPs are supported.
5.2
Private Transfer Syntaxes
Private transfer syntaxes are not supported by System 5.30 at installation. However,
private transfer syntaxes can be developed and “plugged-in” to the archive using the
administrative interface.
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 94 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
6
Configuration
The Admin Console (a graphical user interface (GUI)) tool for System 5.30 is used for
configuration and administration. This tool is remotely enabled through the use of
Java Remote Method Invocation (RMI), allowing the system to be configured and
administrated from any location on the network. Configurable parameters include, but
are not limited to, system level debugging, known remote application entities, various
security concerns, and service classes supported. For a complete list of configuration
possibilities please see the Administration User Guide.
6.1
AE Title/Presentation Address Mapping
All AE Title/Presentation Address mapping may need to be present in multiple
locations, depending on the Application Entity. In all cases, an Administration Console
allows for the configuration of the AE Title.
6.2
Configurable Parameters
The amount of configuration the system allows is extensive.
In general, the following parameters are configurable for each component:
•
Listening IP port number
•
Application entity title
•
Number of simultaneous associations
•
Minimum and Maximum PDU
•
DICOM Part 10 file storage location
•
Accepted DIMSE Commands
•
Accepted SOP Classes
•
Remote AE list (AE Title, Hostname, Port)
•
Network Timeout
A member of Emageon’s support staff must perform configuration.
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 95 of 96
Clinical Content Management DICOM Conformance Statement
System Release 5.30.5
7
Support of Extended Character Sets
The System 5.30 release supports all 8-bit character sets supported by DICOM V3.0.
Multi-byte character sets are not supported.
PROPRIETARY AND CONFIDENTIAL. VERIFY CORRECT DOCUMENT REVISION PRIOR TO USE.
85000-0816A
Page 96 of 96