ClearCanvas Workstation

DICOM Conformance Statement

Document Version: 3.7

Product Name(s): ClearCanvas RIS/PACS

Component Name(s): ClearCanvas Workstation

Edition(s): Personal

Version: 13.1

Date: February 12, 2015

Synaptive Medical
MaRS Discovery District
101 College Street, Suite 200
Toronto, ON M5G 1L7
Canada
 1 CONFORMANCE STATEMENT OVERVIEW

1.1 OVERVIEW
The application supports querying a remote system for a list of DICOM objects that may then be retrieved
to the local system and displayed, in the case of images. It also supports sending locally loaded objects
across the network to another system. Only hierarchical study root query and retrieval is supported for
both SCP and SCU query operations.

For the purposes of display, the application supports:

- Most image storage SOP Classes defined as of DICOM 2011.

- Images of any photometric interpretation.
- Images compressed with the following Transfer Syntaxes:
- RLE Lossless
- JPEG Baseline (Process 1)
- JPEG Extended (Process 2 & 4)
- JPEG Lossless, Non-Hierarchical (Process 14)
- JPEG Lossless, Non-Hierarchical, First-Order Prediction (Process 14 [Selection Value 1])
- JPEG 2000 Image Compression
- JPEG 2000 Image Compression (Lossless Only)
- Key object selection documents containing image entries.
- Grayscale softcopy presentation states and color softcopy presentation states for images in a key
object selection document.
- Encapsulated PDF documents when a suitable external PDF viewer application is available.

Notes:

- The hanging protocols support in the application is a proprietary implementation, and is not
DICOM compatible.
- Certain functions of the application are “Premium Features” and may not be available under all
licenses. This document describes the conformance of these features when the application is
installed with an appropriate license.

All other storage SOP Classes can be retrieved and stored locally, and sent to other DICOM devices, but
are otherwise completely ignored by the application. Table 1.1-1 provides a detailed summary.

Table 1.1-1
NETWORK SERVICES

SOP Classes User of Service Provider of

(SCU) Service
(SCP)
Image Transfer
Breast Tomosynthesis Image Storage Stored and Viewed Yes
Computed Radiography Image Storage Stored and Viewed Yes
CT Image Storage Stored and Viewed Yes
Digital Intra-oral X-Ray Image Storage – For Stored and Viewed Yes
Presentation
Digital Intra-oral X-Ray Image Storage – For Stored and Viewed Yes
Processing

Page 2
Digital Mammography X-Ray Image Storage – For Stored and Viewed Yes
Presentation
Digital Mammography X-Ray Image Storage – For Stored and Viewed Yes
Processing
Digital X-Ray Image Storage – For Presentation Stored and Viewed Yes
Digital X-Ray Image Storage – For Processing Stored and Viewed Yes
Enhanced CT Image Storage Stored and Viewed Yes
Enhanced MR Image Storage Stored and Viewed Yes
Enhanced PET Image Storage Stored and Viewed Yes
Enhanced US Image Storage Stored and Viewed Yes
Enhanced XA Image Storage Stored and Viewed Yes
Enhanced XRF Image Storage Stored and Viewed Yes
MR Image Storage Stored and Viewed Yes
Multi-frame Grayscale Byte Secondary Capture Stored and Viewed Yes
Image Storage
Multi-frame Grayscale Word Secondary Capture Stored and Viewed Yes
Image Storage
Multi-frame Single Bit Secondary Capture Image Stored and Viewed Yes
Storage
Multi-frame True Color Secondary Capture Image Stored and Viewed Yes
Storage
Nuclear Medicine Image Storage (Retired) Stored and Viewed Yes
Nuclear Medicine Image Storage Stored and Viewed Yes
Ophthalmic Photography 16 Bit Image Storage Stored and Viewed Yes
Ophthalmic Photography 8 Bit Image Storage Stored and Viewed Yes
Ophthalmic Tomography Image Storage Stored and Viewed Yes
Positron Emission Tomography Image Storage Stored and Viewed Yes
RT Image Storage Stored and Viewed Yes
Secondary Capture Image Storage Stored and Viewed Yes
Ultrasound Image Storage Stored and Viewed Yes
Ultrasound Image Storage (Retired) Stored and Viewed Yes
Ultrasound Multi-frame Image Storage Stored and Limited Viewing Yes
Ultrasound Multi-frame Image Storage (Retired) Stored and Limited Viewing Yes
Video Endoscopic Image Storage Stored and Limited Viewing Yes
Video Microscopic Image Storage Stored and Limited Viewing Yes
Video Photographic Image Storage Stored and Limited Viewing Yes
VL Endoscopic Image Storage Stored and Viewed Yes
VL Microscopic Image Storage Stored and Viewed Yes
VL Photographic Image Storage Stored and Viewed Yes
VL Slide-Coordinates Microscopic Image Storage Stored and Viewed Yes

Page 3
X-Ray 3D Angiographic Image Storage Stored and Viewed Yes
X-Ray 3D Craniofacial Image Storage Stored and Viewed Yes
X-Ray Angiographic Bi-Plane Image Storage Stored and Viewed Yes
(Retired)
X-Ray Angiographic Image Storage Stored and Viewed Yes
X-Ray Radiofluoroscopic Image Storage Stored and Viewed Yes
Waveforms, Notes, Reports, Measurements Transfer
12-lead ECG Waveform Storage Stored only Yes
Ambulatory ECG Waveform Storage Stored only Yes
Basic Text SR Storage Stored only Yes
Basic Voice Audio Waveform Storage Stored only Yes
Blending Softcopy Presentation State Storage Stored only Yes
Cardiac Electrophysiology Waveform Storage Stored only Yes
Chest CAD SR Storage Stored only Yes
Colon CAD SR Storage Stored only Yes
Color Softcopy Presentation State Storage Yes – Key Object Selections only Yes
Comprehensive SR Storage Stored only Yes
Deformable Spatial Registration Storage Stored only Yes
Encapsulated CDA Storage Stored only Yes
Encapsulated PDF Storage Yes – Requires external viewer Yes
Enhanced SR Storage Stored only Yes
General ECG Waveform Storage Stored only Yes
Grayscale Softcopy Presentation State Storage Yes – Key Object Selections only Yes
Hemodynamic Waveform Storage Stored only Yes
Key Object Selection Document Storage Yes – Images only Yes
Macular Grid Thickness and Volume Report Storage Stored only Yes
Mammography CAD SR Storage Stored only Yes
MR Spectroscopy Storage Stored only Yes
Procedure Log Storage Stored only Yes
Pseudo-Color Softcopy Presentation State Storage Stored only Yes
Raw Data Storage Stored only Yes
Real World Value Mapping Storage Stored only Yes
RT Beams Treatment Record Storage Stored only Yes
RT Brachy Treatment Record Storage Stored only Yes
RT Dose Storage Stored only Yes
RT Ion Beams Treatment Record Storage Stored only Yes
RT Ion Plan Storage Stored only Yes
RT Plan Storage Stored only Yes
RT Structure Set Storage Stored only Yes

Page 4
RT Treatment Summary Record Storage Stored only Yes
Segmentation Storage Stored only Yes
Spatial Fiducials Storage Stored only Yes
Spatial Registration Storage Stored only Yes
Spectacle Prescription Reports Storage Stored only Yes
Standalone Curve Storage (Retired) Stored only Yes
Standalone Modality LUT Storage (Retired) Stored only Yes
Standalone Overlay Storage (Retired) Stored only Yes
Standalone PET Curve Storage (Retired) Stored only Yes
Standalone VOI LUT Storage (Retired) Stored only Yes
Stereometric Relationship Storage Stored only Yes
Stored Print Storage (Retired) Stored only Yes
X-Ray Radiation Dose SR Storage Stored only Yes
Query/Retrieve

Study Root Information Model FIND Yes – Hierarchical only Yes

Study Root Information Model MOVE Yes – Hierarchical only Yes

Table 1.1-2
MEDIA SERVICES

Media Storage Application Profile Write Files Read Files

(FSC or FSU) (FSR)
Compact Disk - Recordable
General Purpose CD-R Yes Yes – Not DICOMDIR
DVD
General Purpose DVD-RAM Yes Yes – Not DICOMDIR
General Purpose DVD Yes Yes – Not DICOMDIR
BD
General Purpose BD Yes Yes – Not DICOMDIR

Note: Support for General Purpose BD is based on the final text of DICOM Supplement 153.

Page 5
 2 TABLE OF CONTENTS

1 ... CONFORMANCE STATEMENT OVERVIEW ........................................................................................ 2

1.1 ....... OVERVIEW ............................................................................................................................... 2
2 ... TABLE OF CONTENTS ......................................................................................................................... 6
3 ... INTRODUCTION .................................................................................................................................... 8
3.1 ....... REVISION HISTORY ................................................................................................................ 8
3.2 ....... AUDIENCE ................................................................................................................................ 8
3.3 ....... REMARKS ................................................................................................................................. 9
4 ... NETWORKING ..................................................................................................................................... 10
4.1 ....... IMPLEMENTATION MODEL ................................................................................................... 10
4.1.1 .... Application Data Flow ....................................................................................................... 10
4.1.2 .... Functional Definitions of AEs ............................................................................................ 11
4.1.3 .... Sequencing of Real-World Activities ................................................................................. 12
4.2 ....... AE SPECIFICATIONS ............................................................................................................. 12
4.2.1 .... ECHO-SCP ....................................................................................................................... 12
4.2.2 .... ECHO-SCU ....................................................................................................................... 14
4.2.3 .... STORAGE-SCP ................................................................................................................ 15
4.2.4 .... STORAGE-SCU ................................................................................................................ 20
4.2.5 .... FIND-SCP ......................................................................................................................... 26
4.2.6 .... FIND-SCU ......................................................................................................................... 30
4.2.7 .... MOVE-SCP ....................................................................................................................... 35
4.2.8 .... MOVE-SCU ....................................................................................................................... 39
4.2.9 .... PRINT-SCU ....................................................................................................................... 42
4.3 ....... NETWORK INTERFACES ...................................................................................................... 48
4.3.1 .... Physical Network Interface ............................................................................................... 48
4.3.2 .... Additional Protocols .......................................................................................................... 49
4.3.3 .... IPv4 and IPv6 Support ...................................................................................................... 51
4.4 ....... NETWORK CONFIGURATION ............................................................................................... 51
4.4.1 .... AE Title/Presentation Address Mapping ........................................................................... 51
4.4.2 .... Parameters ........................................................................................................................ 51
5 ... MEDIA INTERCHANGE ....................................................................................................................... 53
5.1 ....... IMPLEMENTATION MODEL ................................................................................................... 53
5.1.1 .... Application Data Flow ....................................................................................................... 53
5.1.2 .... Functional Definitions of AE’s ........................................................................................... 54
5.1.3 .... Sequencing of Real-World Activities ................................................................................. 54
5.1.4 .... File Meta Information Options ........................................................................................... 54
5.2 ....... AE SPECIFICATIONS ............................................................................................................. 55
5.2.1 .... MEDIA-FSR ...................................................................................................................... 55
5.2.2 .... MEDIA-FSU ...................................................................................................................... 55
5.2.3 .... MEDIA-FSC ...................................................................................................................... 56
5.3 ....... AUGMENTED AND PRIVATE PROFILES .............................................................................. 62
5.3.1 .... Augmented Profiles ........................................................................................................... 62
5.3.2 .... Private Profiles .................................................................................................................. 62
5.4 ....... MEDIA CONFIGURATION ...................................................................................................... 62
6 ... SUPPORT OF CHARACTER SETS .................................................................................................... 63
6.1 ....... OVERVIEW ............................................................................................................................. 63
6.2 ....... CHARACTER SETS ................................................................................................................ 63
6.3 ....... CHARACTER SET CONFIGURATION ................................................................................... 64

Page 6
7 ... SECURITY............................................................................................................................................ 65
7.1 ....... SECURITY PROFILES ............................................................................................................ 65
7.1.1 .... Basic Application Level Confidentiality Profile .................................................................. 65
7.1.2 .... Audit Trail Message Format Profile ................................................................................... 74
7.2 ....... ASSOCIATION LEVEL SECURITY ........................................................................................ 76
7.3 ....... APPLICATION LEVEL SECURITY ......................................................................................... 76
8 ... ANNEXES ............................................................................................................................................. 77
8.1 ....... IOD CONTENTS ..................................................................................................................... 77
8.1.1 .... Created SOP Instances .................................................................................................... 77
8.1.2 .... Usage of Attributes from Received IODs .......................................................................... 97
8.1.3 .... Attribute Mapping ............................................................................................................ 106
8.1.4 .... Coerced/Modified Fields ................................................................................................. 106
8.2 ....... DATA DICTIONARY OF PRIVATE ATTRIBUTES ................................................................ 106
8.3 ....... CODED TERMINOLOGY AND TEMPLATES ....................................................................... 106
8.4 ....... GRAYSCALE IMAGE CONSISTENCY ................................................................................. 106
8.5 ....... STANDARD EXTENDED/SPECIALIZED/PRIVATE SOP CLASSES ................................... 106
8.6 ....... PRIVATE TRANSFER SYNTAXES....................................................................................... 106

Page 7
 3 INTRODUCTION

3.1 REVISION HISTORY

Document Date of Issue Author Description

Version
1.0 July 25, 2008 Henry Hernaez Version for Final Review
1.1 December 11, 2008 Stewart Bright Version for Final Review
1.2 July 22, 2009 Jasper Yeh, Stewart Bright Version for Final Review
1.3 September 18, 2009 Jasper Yeh Version for Final Review
1.4 December 17, 2009 Jasper Yeh, Stewart Bright Version for Final Review
1.5 February 22, 2010 Stewart Bright Version for Final Review
1.6 September 16, 2010 Jasper Yeh, Stewart Bright Version for Final Review
1.7 September 21, 2010 Jasper Yeh, Stewart Bright Version for Final Review
1.8 February 16, 2011 Jasper Yeh, Stewart Bright Version for Final Review
1.9 March 31, 2011 Jasper Yeh, Stewart Bright Version for Final Review
2.0 June 14, 2011 Jasper Yeh Version for Final Review
2.1 July 27, 2011 Jasper Yeh Version for Final Review
2.2 August 30, 2011 Jasper Yeh Version for Final Review
2.3 August 30, 2011 Jasper Yeh Version for Final Review
2.4 September 16, 2011 Jasper Yeh Version for Final Review
2.5 November 17, 2011 Jasper Yeh Version for Final Review
2.6 February 6, 2012 Jasper Yeh Version for Final Review
2.7 March, 27, 2012 Jasper Yeh Version for Final Review
2.8 May 24, 2012 Thanh Huynh, Jasper Yeh Version for Final Review
2.9 July 18, 2012 Stewart Bright Version for Final Review
3.0 September 27, 2012 Jasper Yeh Version for Final Review
3.1 January 23, 2013 Jasper Yeh Version for Final Review
3.2 January 23, 2013 Jasper Yeh Version for Final Review
3.3 February 27, 2013 Jasper Yeh Version for Final Review
3.4 July 29, 2013 Jasper Yeh Version for Final Review
3.5 December 1, 2013 Jasper Yeh Version for Final Review
3.6 August 1, 2014 Jasper Yeh Version for Final Review
3.7 February 12, 2015 Jasper Yeh Version for Final Review

3.2 AUDIENCE
This document is written for the people who need to understand how ClearCanvas Workstation will
integrate into their healthcare facility. This includes both those responsible for overall imaging network
policy and architecture, as well as integrators and developers who need to have a detailed understanding
of the DICOM features of the product. This document contains some basic DICOM definitions so that any
reader may understand how this product implements DICOM features. However, integrators and

Page 8
developers are expected to fully understand all the DICOM terminology, how the tables in this document
relate to the product’s functionality, and how that functionality integrates with other devices that support
compatible DICOM features.

3.3 REMARKS
This application has been approved for sale as a medical device in the United States.

The hanging protocols support in the application is a proprietary implementation, and is not DICOM
compatible.

Certain functions of the application are “Premium Features” and may not be available under all licenses.
This document describes the conformance of these features when the application is installed with an
appropriate license.

Page 9
 4 NETWORKING

4.1 IMPLEMENTATION MODEL

4.1.1 Application Data Flow

Local User
Creates Ancillary
Content
Requested Images
STORAGE-SCU
Received by
Application Entity
Remote AE
Local User
Requests Send

Local User Remote AE

ECHO-SCU
Requests Receives Verify
Application Entity
Verification Command

Local User
Requests Query
Remote AE
FIND-SCU Receives Query or
Application Entity Retrieve
Local User Views Command
Images of Patient
with Prior Studies

Remote AE
Local User MOVE-SCU Receives Query or
Requests Retrieval Application Entity Retrieve
Command

Unsolicited or
STORAGE-SCP Requested
Application Entity Instances Sent by
Remote AE

Remote AE
FIND-SCP
Requests Query or
Application Entity
Retrieval

Unsolicited or Remote AE
Requested Instances MOVE-SCP
Sent to Remote AE via
Requested Image
Application Entity
STORAGE-SCU Retrieval

Verification
ECHO-SCP
Requested by
Application Entity
Remote AE

Local User Selects PRINT-SCU Remote AE

Images for Printing Application Entity Receives Print Job

DICOM Standard
Interface

Figure 4.1-1
IMPLEMENTATION MODEL

Page 10
The application is a .NET application that provides a user interface, internal database and network
listener that spawns additional threads as necessary to handle incoming connections, as well as limited
media support.

Conceptually, the network services may be modeled as the following separate AEs, though in fact all the
AEs share a single (configurable) AE Title:

- ECHO-SCP, which responds to verification requests

- ECHO-SCU, which sends a verification request
- STORAGE-SCP, which receives incoming composite instances
- STORAGE-SCU, which sends outbound composite instances
- FIND-SCP, which receives incoming queries for lists of studies
- FIND-SCU, which queries remote AEs for lists of studies
- MOVE-SCP, which responds to requests for studies
- MOVE-SCU, which retrieves selected studies
- PRINT-SCU, which sends print jobs

4.1.2 Functional Definitions of AEs

4.1.2.1 ECHO-SCP
ECHO-SCP waits in the background for connections, will accept associations with Presentation Contexts
for the SOP Class of the Verification Service Class, and will respond successfully to echo requests.

4.1.2.2 ECHO-SCU
ECHO-SCU is activated through the user interface when a user selects a remote AE to verify (from a pre-
configured list), then initiates a verification.

4.1.2.3 STORAGE-SCP
STORAGE-SCP waits in the background for connections, will accept associations with Presentation
Contexts for SOP Classes of the Storage Service Class, and will store the received instances to the
internal database where they may subsequently be listed and viewed through the user interface.

4.1.2.4 STORAGE-SCU
STORAGE-SCU is typically activated through the user interface when a user selects studies from the
local store and requests that they be sent to a remote AE (selected from a pre-configured list).
STORAGE-SCU can also be activated internally when a user creates ancillary content such as key object
selections, secondary capture images, softcopy presentation states, and encapsulated PDF documents.

4.1.2.5 FIND-SCP
FIND-SCP waits in the background for connections, will accept associations with Presentation Contexts
for the SOP Class of the Study Root Query/Retrieve Information Model – FIND Service Class, and will
respond successfully to query requests.

4.1.2.6 FIND-SCU
FIND-SCU is typically activated through the user interface when a user selects a remote AE to query
(from a pre-configured list), then initiates a query for studies. For a single study at a time, the user can
also elect to view details of the series in it, which also utilizes FIND-SCU.

FIND-SCU can also be activated internally when a user opens one or more studies for viewing and there
is at least one remote AE marked as a “Default Server” in the configuration. A query is initiated to list
prior studies related to the current patient(s) being viewed.

Page 11
4.1.2.7 MOVE-SCP
MOVE-SCP waits in the background for connections, will accept associations with Presentation Contexts
for the SOP Class of the Study Root Query/Retrieve Information Model – MOVE Service Class, and will
respond successfully to move requests by initiating storage of instances to the remote AE.

4.1.2.8 MOVE-SCU
MOVE-SCU is activated through the user interface when a user selects a study for retrieval. A connection
to the remote AE is established to initiate the retrieval and the STORAGE-SCP AE receives the retrieved
instances.

4.1.2.9 PRINT-SCU
PRINT-SCU is activated through the user interface when a user selects one or more previously-identified
images for printing. A connection to the remote AE is established to transfer the selected images for
printing.

4.1.3 Sequencing of Real-World Activities

All SCP activities are performed asynchronously in the background and are not dependent on any
sequencing. All SCU activities are initiated through the user interface with the following exceptions:

- STORAGE-SCU is also initiated internally by both MOVE-SCP and a Send Key Object
Selections operation.
- FIND-SCU is also initiated internally by a Query for Prior Studies operation.

ECHO-SCU and FIND-SCU activities are typically synchronous and blocking except when FIND-SCU is
invoked as a Query for Prior Studies operation, in which case it is asynchronous and non-blocking.
STORAGE-SCU and MOVE-SCU activities are asynchronous and non-blocking.

4.2 AE SPECIFICATIONS

4.2.1 ECHO-SCP

4.2.1.1 SOP Classes

ECHO-SCP provides Standard Conformance to the following SOP classes:

Table 4.2-1
SOP CLASSES SUPPORTED BY ECHO SCP

SOP Class Name SOP Class UID

Verification SOP Class 1.2.840.10008.1.1

4.2.1.2 Association Policies

4.2.1.2.1 General
ECHO-SCP accepts but never initiates associations.

Table 4.2-2
MAXIMUM PDU SIZE RECEIVED FOR ECHO-SCP

Maximum PDU size received 114kB (approximate)

Page 12
4.2.1.2.2 Number of Associations
Table 4.2-3
NUMBER OF ASSOCIATIONS FOR ECHO-SCP

Maximum number of simultaneous associations Unlimited

4.2.1.2.3 Asynchronous Nature

ECHO-SCP will only allow a single outstanding operation on an Association. Therefore, ECHO-SCP will
not perform asynchronous operations window negotiation.

4.2.1.2.4 Implementation Identifying Information

Table 4.2-4
DICOM IMPLEMENTATION CLASS AND VERSION FOR ECHO SCP

Implementation Class UID 1.3.6.1.4.1.25403.1.1.1

Implementation Version Name Dicom 0.1

4.2.1.3 Association Initiation Policy

ECHO-SCP does not initiate associations.

4.2.1.4 Association Acceptance Policy

When ECHO-SCP accepts an association, it will respond to echo requests. The association will be
rejected if:

- The Called AE Title does not match the AE Title shared by all the SCPs of the application.

4.2.1.4.1 Activity – Receive Echo Request

4.2.1.4.1.1 Description and Sequencing of Activities

As requests are received, they are responded to immediately.

4.2.1.4.1.2 Accepted Presentation Contexts

Table 4.2-5
ACCEPTABLE PRESENTATION CONTEXTS FOR ECHO-SCP AND RECEIVE ECHO REQUEST

Presentation Context Table

Abstract Syntax Transfer Syntax Role Extended
Name UID Name UID Negotiation
Verification 1.2.840.10008.1.1 Explicit VR Little 1.2.840.10008.1.2.1 SCP None
Endian
Implicit VR Little 1.2.840.10008.1.2 SCP None
Endian

4.2.1.4.1.2.1 Extended Negotiation

No extended negotiation is performed.

4.2.1.4.1.3 SOP Specific Conformance

4.2.1.4.1.3.1 SOP Specific Conformance to Verification SOP Class

ECHO-SCP provides standard conformance to the Verification Service Class.

Page 13
4.2.1.4.1.3.2 Presentation Context Acceptance Criterion
ECHO-SCP will only accept a Presentation Context compatible with the one listed in Table 4.2-5.

4.2.1.4.1.3.3 Transfer Syntax Selection Policies

ECHO-SCP will select the first Transfer Syntax proposed by the client that is supported by the SCP, per
Presentation Context.

ECHO-SCP will accept duplicate Presentation Contexts; that is, if it is offered multiple Presentation
Contexts, each of which offers acceptable Transfer Syntaxes, it will accept all Presentation Contexts,
applying the same method for selecting a Transfer Syntax for each.

4.2.2 ECHO-SCU

4.2.2.1 SOP Classes

ECHO-SCU provides Standard Conformance to the following SOP classes:

Table 4.2-6
SOP CLASSES SUPPORTED BY ECHO-SCU

SOP Class Name SOP Class UID

Verification SOP Class 1.2.840.10008.1.1

4.2.2.2 Association Policies

4.2.2.2.1 General
ECHO-SCU initiates but never accepts associations.

Table 4.2-7
MAXIMUM PDU SIZE RECEIVED FOR ECHO-SCU

Maximum PDU size received 114kB (approx.)

4.2.2.2.2 Number of Associations

Table 4.2-8
NUMBER OF ASSOCIATIONS FOR ECHO-SCU

Maximum number of simultaneous associations 1

4.2.2.2.3 Asynchronous Nature

ECHO-SCU will only allow a single outstanding operation on an Association. Therefore, ECHO-SCU will
not perform asynchronous operations window negotiation.

4.2.2.2.4 Implementation Identifying Information

Table 4.2-9
DICOM IMPLEMENTATION CLASS AND VERSION FOR ECHO-SCU

Implementation Class UID 1.3.6.1.4.1.25403.1.1.1

Implementation Version Name Dicom 0.1

4.2.2.3 Association Initiation Policy

ECHO-SCU attempts to initiate a new association when the user performs the verify action from the user
interface to either a single remote AE or a group of remote AEs.

Page 14
4.2.2.3.1 Activity – Send Echo Request

4.2.2.3.1.1 Description and Sequencing of Activities

A single attempt will be made to verify the remote AE. If the verification fails, for whatever reason, no retry
will be performed.

4.2.2.3.1.2 Proposed Presentation Contexts

Table 4.2-10
PROPOSED PRESENTATION CONTEXTS FOR ECHO-SCU AND SEND ECHO REQUEST

Presentation Context Table

Abstract Syntax Transfer Syntax Role Extended
Name UID Name UID Negotiation
Verification 1.2.840.10008.1.1 Explicit VR Little 1.2.840.10008.1.2.1 SCU None
Endian
Implicit VR Little 1.2.840.10008.1.2 SCU None
Endian

4.2.2.3.1.2.1 Extended Negotiation

No extended negotiation is performed.

4.2.2.3.1.3 SOP Specific Conformance

4.2.2.3.1.3.1 SOP Specific Conformance to Verification SOP Class

ECHO-SCU provides standard conformance to the Verification Service Class.

4.2.2.3.1.3.2 Presentation Context Acceptance Criterion

ECHO-SCU does not accept associations.

4.2.2.3.1.3.3 Transfer Syntax Selection Policies

ECHO-SCU prefers Explicit VR Little Endian Transfer Syntax, which is always first in the proposed
Presentation Context.

4.2.2.4 Association Acceptance Policy

ECHO-SCU does not accept associations.

4.2.3 STORAGE-SCP

4.2.3.1 SOP Classes

STORAGE-SCP provides Standard Conformance to the following SOP classes:

Table 4.2-11
SOP CLASSES SUPPORTED BY STORAGE-SCP

SOP Class Name SOP Class UID

12-lead ECG Waveform Storage 1.2.840.10008.5.1.4.1.1.9.1.1
Ambulatory ECG Waveform Storage 1.2.840.10008.5.1.4.1.1.9.1.3
Basic Text SR Storage 1.2.840.10008.5.1.4.1.1.88.11
Basic Voice Audio Waveform Storage 1.2.840.10008.5.1.4.1.1.9.4.1
Blending Softcopy Presentation State Storage 1.2.840.10008.5.1.4.1.1.11.4

Page 15
Breast Tomosynthesis Image Storage 1.2.840.10008.5.1.4.1.1.13.1.3
Cardiac Electrophysiology Waveform Storage 1.2.840.10008.5.1.4.1.1.9.3.1
Chest CAD SR Storage 1.2.840.10008.5.1.4.1.1.88.65
Colon CAD SR Storage 1.2.840.10008.5.1.4.1.1.88.69
Color Softcopy Presentation State Storage 1.2.840.10008.5.1.4.1.1.11.2
Comprehensive SR Storage 1.2.840.10008.5.1.4.1.1.88.33
Computed Radiography Image Storage 1.2.840.10008.5.1.4.1.1.1
CT Image Storage 1.2.840.10008.5.1.4.1.1.2
Deformable Spatial Registration Storage 1.2.840.10008.5.1.4.1.1.66.3
Digital Intra-oral X-Ray Image Storage – For Presentation 1.2.840.10008.5.1.4.1.1.1.3
Digital Intra-oral X-Ray Image Storage – For Processing 1.2.840.10008.5.1.4.1.1.1.3.1
Digital Mammography X-Ray Image Storage – For Presentation 1.2.840.10008.5.1.4.1.1.1.2
Digital Mammography X-Ray Image Storage – For Processing 1.2.840.10008.5.1.4.1.1.1.2.1
Digital X-Ray Image Storage – For Presentation 1.2.840.10008.5.1.4.1.1.1.1
Digital X-Ray Image Storage – For Processing 1.2.840.10008.5.1.4.1.1.1.1.1
Encapsulated CDA Storage 1.2.840.10008.5.1.4.1.1.104.2
Encapsulated PDF Storage 1.2.840.10008.5.1.4.1.1.104.1
Enhanced CT Image Storage 1.2.840.10008.5.1.4.1.1.2.1
Enhanced MR Image Storage 1.2.840.10008.5.1.4.1.1.4.1
Enhanced PET Image Storage 1.2.840.10008.5.1.4.1.1.130
Enhanced SR Storage 1.2.840.10008.5.1.4.1.1.88.22
Enhanced US Image Storage 1.2.840.10008.5.1.4.1.1.6.2
Enhanced XA Image Storage 1.2.840.10008.5.1.4.1.1.12.1.1
Enhanced XRF Image Storage 1.2.840.10008.5.1.4.1.1.12.2.1
General ECG Waveform Storage 1.2.840.10008.5.1.4.1.1.9.1.2
Grayscale Softcopy Presentation State Storage 1.2.840.10008.5.1.4.1.1.11.1
Hemodynamic Waveform Storage 1.2.840.10008.5.1.4.1.1.9.2.1
Key Object Selection Document Storage 1.2.840.10008.5.1.4.1.1.88.59
Macular Grid Thickness and Volume Report Storage 1.2.840.10008.5.1.4.1.1.79.1
Mammography CAD SR Storage 1.2.840.10008.5.1.4.1.1.88.50
MR Image Storage 1.2.840.10008.5.1.4.1.1.4
MR Spectroscopy Storage 1.2.840.10008.5.1.4.1.1.4.2
Multi-frame Grayscale Byte Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7.2
Multi-frame Grayscale Word Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7.3
Multi-frame Single Bit Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7.1
Multi-frame True Color Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7.4
Nuclear Medicine Image Storage (Retired) 1.2.840.10008.5.1.4.1.1.5
Nuclear Medicine Image Storage 1.2.840.10008.5.1.4.1.1.20
Ophthalmic Photography 16 Bit Image Storage 1.2.840.10008.5.1.4.1.1.77.1.5.2

Page 16
Ophthalmic Photography 8 Bit Image Storage 1.2.840.10008.5.1.4.1.1.77.1.5.1
Ophthalmic Tomography Image Storage 1.2.840.10008.5.1.4.1.1.77.1.5.4
Positron Emission Tomography Image Storage 1.2.840.10008.5.1.4.1.1.128
Procedure Log Storage 1.2.840.10008.5.1.4.1.1.88.40
Pseudo-Color Softcopy Presentation State Storage 1.2.840.10008.5.1.4.1.1.11.3
Raw Data Storage 1.2.840.10008.5.1.4.1.1.66
Real World Value Mapping Storage 1.2.840.10008.5.1.4.1.1.67
RT Beams Treatment Record Storage 1.2.840.10008.5.1.4.1.1.481.4
RT Brachy Treatment Record Storage 1.2.840.10008.5.1.4.1.1.481.6
RT Dose Storage 1.2.840.10008.5.1.4.1.1.481.2
RT Image Storage 1.2.840.10008.5.1.4.1.1.481.1
RT Ion Beams Treatment Record Storage 1.2.840.10008.5.1.4.1.1.481.9
RT Ion Plan Storage 1.2.840.10008.5.1.4.1.1.481.8
RT Plan Storage 1.2.840.10008.5.1.4.1.1.481.5
RT Structure Set Storage 1.2.840.10008.5.1.4.1.1.481.3
RT Treatment Summary Record Storage 1.2.840.10008.5.1.4.1.1.481.7
Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7
Segmentation Storage 1.2.840.10008.5.1.4.1.1.66.4
Spatial Fiducials Storage 1.2.840.10008.5.1.4.1.1.66.2
Spatial Registration Storage 1.2.840.10008.5.1.4.1.1.66.1
Spectacle Prescription Reports Storage 1.2.840.10008.5.1.4.1.1.78.6
Standalone Curve Storage (Retired) 1.2.840.10008.5.1.4.1.1.9
Standalone Modality LUT Storage (Retired) 1.2.840.10008.5.1.4.1.1.10
Standalone Overlay Storage (Retired) 1.2.840.10008.5.1.4.1.1.8
Standalone PET Curve Storage (Retired) 1.2.840.10008.5.1.4.1.1.129
Standalone VOI LUT Storage (Retired) 1.2.840.10008.5.1.4.1.1.11
Stereometric Relationship Storage 1.2.840.10008.5.1.4.1.1.77.1.5.3
Stored Print Storage (Retired) 1.2.840.10008.5.1.1.27
Ultrasound Image Storage 1.2.840.10008.5.1.4.1.1.6.1
Ultrasound Image Storage (Retired) 1.2.840.10008.5.1.4.1.1.6
Ultrasound Multi-frame Image Storage 1.2.840.10008.5.1.4.1.1.3.1
Ultrasound Multi-frame Image Storage (Retired) 1.2.840.10008.5.1.4.1.1.3
Video Endoscopic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.1.1
Video Microscopic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.2.1
Video Photographic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.4.1
VL Endoscopic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.1
VL Microscopic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.2
VL Photographic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.4
VL Slide-Coordinates Microscopic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.3

Page 17
X-Ray 3D Angiographic Image Storage 1.2.840.10008.5.1.4.1.1.13.1.1
X-Ray 3D Craniofacial Image Storage 1.2.840.10008.5.1.4.1.1.13.1.2
X-Ray Angiographic Bi-Plane Image Storage (Retired) 1.2.840.10008.5.1.4.1.1.12.3
X-Ray Angiographic Image Storage 1.2.840.10008.5.1.4.1.1.12.1
X-Ray Radiation Dose SR Storage 1.2.840.10008.5.1.4.1.1.88.67
X-Ray Radiofluoroscopic Image Storage 1.2.840.10008.5.1.4.1.1.12.2

4.2.3.2 Association Policies

4.2.3.2.1 General
STORAGE-SCP accepts but never initiates associations.

Table 4.2-12
MAXIMUM PDU SIZE RECEIVED FOR STORAGE-SCP

Maximum PDU size received 114kB (approx.)

4.2.3.2.2 Number of Associations

Table 4.2-13
NUMBER OF ASSOCIATIONS FOR STORAGE-SCP

Maximum number of simultaneous associations Unlimited

4.2.3.2.3 Asynchronous Nature

STORAGE-SCP will only allow a single outstanding operation on an Association. Therefore, STORAGE-
SCP will not perform asynchronous operations window negotiation.

4.2.3.2.4 Implementation Identifying Information

Table 4.2-14
DICOM IMPLEMENTATION CLASS AND VERSION FOR STORAGE-SCP

Implementation Class UID 1.3.6.1.4.1.25403.1.1.1

Implementation Version Name Dicom 0.1

4.2.3.3 Association Initiation Policy

STORAGE-SCP does not initiate associations.

4.2.3.4 Association Acceptance Policy

When STORAGE-SCP accepts an association, it will respond to storage requests. The association will be
rejected if:

- The Called AE Title does not match the AE Title shared by all the SCPs of the application.

4.2.3.4.1 Activity – Receive Storage Request

4.2.3.4.1.1 Description and Sequencing of Activities

As instances are received, they are copied to the local file system and a record inserted into the internal
database. If the received instance is a duplicate of a previously received instance, the old file and
database record will be overwritten with the new one.

Page 18
4.2.3.4.1.2 Accepted Presentation Contexts
Table 4.2-15
ACCEPTABLE PRESENTATION CONTEXTS FOR
STORAGE-SCP AND RECEIVE STORAGE REQUEST

Presentation Context Table

Abstract Syntax Transfer Syntax Role Extended
Name UID Name UID Negotiation
See Table 4.2-11 See Table 4.2-11 Explicit VR Little 1.2.840.10008.1.2.1 SCP None
Endian
Implicit VR Little 1.2.840.10008.1.2 SCP None
Endian
RLE Lossless 1.2.840.10008.1.2.5 SCP None
JPEG Baseline 1.2.840.10008.1.2.4.50 SCP None
(Process 1):
JPEG Extended 1.2.840.10008.1.2.4.51 SCP None
(Process 2 & 4)
JPEG Lossless, 1.2.840.10008.1.2.4.57 SCP None
Non-Hierarchical
(Process 14)
JPEG Lossless, 1.2.840.10008.1.2.4.70 SCP None
Non-Hierarchical,
First-Order
Prediction
(Process 14
[Selection Value
1])
JPEG 2000 Image 1.2.840.10008.1.2.4.90 SCP None
Compression
(Lossless Only)
JPEG 2000 Image 1.2.840.10008.1.2.4.91 SCP None
Compression

4.2.3.4.1.2.1 Extended Negotiation

No extended negotiation is performed, though STORAGE-SCP:

- is a Level 2 Storage SCP (Full – does not discard any data elements)
- does not support digital signatures
- does not coerce any received data elements

4.2.3.4.1.3 SOP Specific Conformance

4.2.3.4.1.3.1 SOP Specific Conformance to Storage SOP Classes

STORAGE-SCP provides standard conformance to the Storage Service Class.

4.2.3.4.1.3.2 Presentation Context Acceptance Criterion

STORAGE-SCP will always accept any Presentation Context for the supported SOP Classes with the
supported Transfer Syntaxes. More than one proposed Presentation Context will be accepted for the
same Abstract Syntax if the Transfer Syntax is supported, whether or not it is the same as another
Presentation Context.

Page 19
4.2.3.4.1.3.3 Transfer Syntax Selection Policies
STORAGE-SCP will always select the first Transfer Syntax proposed by the client that is supported by the
SCP, per Presentation Context.

STORAGE-SCP will accept duplicate Presentation Contexts; that is, if it is offered multiple Presentation
Contexts, each of which offers acceptable Transfer Syntaxes, it will accept all Presentation Contexts,
applying the same method for selecting a Transfer Syntax for each.

4.2.3.4.1.3.4 Response Status

STORAGE-SCP will behave as described in the Table below when generating the C-STORE response
command message.

Table 4.2-16
RESPONSE STATUS FOR STORAGE-SCP AND RECEIVE STORAGE REQUEST

Service Further Meaning Status Reason

Status Codes
Failure Processing Failure 0110 Sent when an error occurs
trying to save the stored
SOP instance to disk
Success 0000 Sent as each SOP is stored

4.2.4 STORAGE-SCU

4.2.4.1 SOP Classes

STORAGE-SCU provides Standard Conformance to the following SOP classes:

Table 4.2-17
SOP CLASSES SUPPORTED BY STORAGE-SCU

SOP Class Name SOP Class UID

12-lead ECG Waveform Storage 1.2.840.10008.5.1.4.1.1.9.1.1
Ambulatory ECG Waveform Storage 1.2.840.10008.5.1.4.1.1.9.1.3
Basic Text SR Storage 1.2.840.10008.5.1.4.1.1.88.11
Basic Voice Audio Waveform Storage 1.2.840.10008.5.1.4.1.1.9.4.1
Blending Softcopy Presentation State Storage 1.2.840.10008.5.1.4.1.1.11.4
Breast Tomosynthesis Image Storage 1.2.840.10008.5.1.4.1.1.13.1.3
Cardiac Electrophysiology Waveform Storage 1.2.840.10008.5.1.4.1.1.9.3.1
Chest CAD SR Storage 1.2.840.10008.5.1.4.1.1.88.65
Colon CAD SR Storage 1.2.840.10008.5.1.4.1.1.88.69
Color Softcopy Presentation State Storage 1.2.840.10008.5.1.4.1.1.11.2
Comprehensive SR Storage 1.2.840.10008.5.1.4.1.1.88.33
Computed Radiography Image Storage 1.2.840.10008.5.1.4.1.1.1
CT Image Storage 1.2.840.10008.5.1.4.1.1.2
Deformable Spatial Registration Storage 1.2.840.10008.5.1.4.1.1.66.3
Digital Intra-oral X-Ray Image Storage – For Presentation 1.2.840.10008.5.1.4.1.1.1.3
Digital Intra-oral X-Ray Image Storage – For Processing 1.2.840.10008.5.1.4.1.1.1.3.1

Page 20
Digital Mammography X-Ray Image Storage – For Presentation 1.2.840.10008.5.1.4.1.1.1.2
Digital Mammography X-Ray Image Storage – For Processing 1.2.840.10008.5.1.4.1.1.1.2.1
Digital X-Ray Image Storage – For Presentation 1.2.840.10008.5.1.4.1.1.1.1
Digital X-Ray Image Storage – For Processing 1.2.840.10008.5.1.4.1.1.1.1.1
Encapsulated CDA Storage 1.2.840.10008.5.1.4.1.1.104.2
Encapsulated PDF Storage 1.2.840.10008.5.1.4.1.1.104.1
Enhanced CT Image Storage 1.2.840.10008.5.1.4.1.1.2.1
Enhanced MR Image Storage 1.2.840.10008.5.1.4.1.1.4.1
Enhanced PET Image Storage 1.2.840.10008.5.1.4.1.1.130
Enhanced SR Storage 1.2.840.10008.5.1.4.1.1.88.22
Enhanced US Image Storage 1.2.840.10008.5.1.4.1.1.6.2
Enhanced XA Image Storage 1.2.840.10008.5.1.4.1.1.12.1.1
Enhanced XRF Image Storage 1.2.840.10008.5.1.4.1.1.12.2.1
General ECG Waveform Storage 1.2.840.10008.5.1.4.1.1.9.1.2
Grayscale Softcopy Presentation State Storage 1.2.840.10008.5.1.4.1.1.11.1
Hemodynamic Waveform Storage 1.2.840.10008.5.1.4.1.1.9.2.1
Key Object Selection Document Storage 1.2.840.10008.5.1.4.1.1.88.59
Macular Grid Thickness and Volume Report Storage 1.2.840.10008.5.1.4.1.1.79.1
Mammography CAD SR Storage 1.2.840.10008.5.1.4.1.1.88.50
MR Image Storage 1.2.840.10008.5.1.4.1.1.4
MR Spectroscopy Storage 1.2.840.10008.5.1.4.1.1.4.2
Multi-frame Grayscale Byte Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7.2
Multi-frame Grayscale Word Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7.3
Multi-frame Single Bit Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7.1
Multi-frame True Color Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7.4
Nuclear Medicine Image Storage (Retired) 1.2.840.10008.5.1.4.1.1.5
Nuclear Medicine Image Storage 1.2.840.10008.5.1.4.1.1.20
Ophthalmic Photography 16 Bit Image Storage 1.2.840.10008.5.1.4.1.1.77.1.5.2
Ophthalmic Photography 8 Bit Image Storage 1.2.840.10008.5.1.4.1.1.77.1.5.1
Ophthalmic Tomography Image Storage 1.2.840.10008.5.1.4.1.1.77.1.5.4
Positron Emission Tomography Image Storage 1.2.840.10008.5.1.4.1.1.128
Procedure Log Storage 1.2.840.10008.5.1.4.1.1.88.40
Pseudo-Color Softcopy Presentation State Storage 1.2.840.10008.5.1.4.1.1.11.3
Raw Data Storage 1.2.840.10008.5.1.4.1.1.66
Real World Value Mapping Storage 1.2.840.10008.5.1.4.1.1.67
RT Beams Treatment Record Storage 1.2.840.10008.5.1.4.1.1.481.4
RT Brachy Treatment Record Storage 1.2.840.10008.5.1.4.1.1.481.6
RT Dose Storage 1.2.840.10008.5.1.4.1.1.481.2
RT Image Storage 1.2.840.10008.5.1.4.1.1.481.1

Page 21
RT Ion Beams Treatment Record Storage 1.2.840.10008.5.1.4.1.1.481.9
RT Ion Plan Storage 1.2.840.10008.5.1.4.1.1.481.8
RT Plan Storage 1.2.840.10008.5.1.4.1.1.481.5
RT Structure Set Storage 1.2.840.10008.5.1.4.1.1.481.3
RT Treatment Summary Record Storage 1.2.840.10008.5.1.4.1.1.481.7
Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7
Segmentation Storage 1.2.840.10008.5.1.4.1.1.66.4
Spatial Fiducials Storage 1.2.840.10008.5.1.4.1.1.66.2
Spatial Registration Storage 1.2.840.10008.5.1.4.1.1.66.1
Spectacle Prescription Reports Storage 1.2.840.10008.5.1.4.1.1.78.6
Standalone Curve Storage (Retired) 1.2.840.10008.5.1.4.1.1.9
Standalone Modality LUT Storage (Retired) 1.2.840.10008.5.1.4.1.1.10
Standalone Overlay Storage (Retired) 1.2.840.10008.5.1.4.1.1.8
Standalone PET Curve Storage (Retired) 1.2.840.10008.5.1.4.1.1.129
Standalone VOI LUT Storage (Retired) 1.2.840.10008.5.1.4.1.1.11
Stereometric Relationship Storage 1.2.840.10008.5.1.4.1.1.77.1.5.3
Stored Print Storage (Retired) 1.2.840.10008.5.1.1.27
Ultrasound Image Storage 1.2.840.10008.5.1.4.1.1.6.1
Ultrasound Image Storage (Retired) 1.2.840.10008.5.1.4.1.1.6
Ultrasound Multi-frame Image Storage 1.2.840.10008.5.1.4.1.1.3.1
Ultrasound Multi-frame Image Storage (Retired) 1.2.840.10008.5.1.4.1.1.3
Video Endoscopic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.1.1
Video Microscopic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.2.1
Video Photographic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.4.1
VL Endoscopic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.1
VL Microscopic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.2
VL Photographic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.4
VL Slide-Coordinates Microscopic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.3
X-Ray 3D Angiographic Image Storage 1.2.840.10008.5.1.4.1.1.13.1.1
X-Ray 3D Craniofacial Image Storage 1.2.840.10008.5.1.4.1.1.13.1.2
X-Ray Angiographic Bi-Plane Image Storage (Retired) 1.2.840.10008.5.1.4.1.1.12.3
X-Ray Angiographic Image Storage 1.2.840.10008.5.1.4.1.1.12.1
X-Ray Radiation Dose SR Storage 1.2.840.10008.5.1.4.1.1.88.67
X-Ray Radiofluoroscopic Image Storage 1.2.840.10008.5.1.4.1.1.12.2

4.2.4.2 Association Policies

4.2.4.2.1 General
STORAGE-SCU initiates but never accepts associations.

Page 22
 Table 4.2-18
MAXIMUM PDU SIZE RECEIVED FOR STORAGE-SCU

Maximum PDU size received 114kB (approx.)

4.2.4.2.2 Number of Associations

Table 4.2-19
NUMBER OF ASSOCIATIONS FOR STORAGE-SCU

Maximum number of simultaneous associations Unlimited

4.2.4.2.3 Asynchronous Nature

STORAGE-SCU will only allow a single outstanding operation on an Association. Therefore, STORAGE-
SCU will not perform asynchronous operations window negotiation.

4.2.4.2.4 Implementation Identifying Information

Table 4.2-20
DICOM IMPLEMENTATION CLASS AND VERSION FOR STORAGE-SCU

Implementation Class UID 1.3.6.1.4.1.25403.1.1.1

Implementation Version Name Dicom 0.1

4.2.4.3 Association Initiation Policy

When initiated by the user, STORAGE-SCU attempts to initiate a new association for the study, or group
of studies, selected (e.g. one association per user-initiated send operation). When initiated by MOVE-
SCP, one association is initiated per move request. When initiated internally in response to the user
creating ancillary content, one association is initiated for all the instances per remote AE. In the case of
key object selections, the association is initiated by the act of closing the viewer window where key object
selection documents and softcopy presentation states have been created.

4.2.4.3.1 Activity – Send Storage Request

4.2.4.3.1.1 Description and Sequencing of Activities

For each instance selected from the user interface to be transferred, a single attempt will be made to
transmit it to the selected remote AE. If the send fails, for whatever reason, no retry will be performed,
and an attempt will be made to send the next instance.

4.2.4.3.1.2 Proposed Presentation Contexts

Table 4.2-21
PROPOSED PRESENTATION CONTEXTS FOR STORAGE-SCU AND SEND STORAGE REQUEST

Presentation Context Table

Abstract Syntax Transfer Syntax Role Extended
Name UID Name UID Negotiation
See Table 4.2-17 See Table 4.2-17 Explicit VR Little 1.2.840.10008.1.2.1 SCU None
Endian
Implicit VR Little 1.2.840.10008.1.2 SCU None
Endian
RLE Lossless 1.2.840.10008.1.2.5 SCU None
JPEG Baseline 1.2.840.10008.1.2.4.50 SCU None
(Process 1):

Page 23
 JPEG Extended 1.2.840.10008.1.2.4.51 SCU None
(Process 2 & 4)
JPEG Lossless, 1.2.840.10008.1.2.4.57 SCU None
Non-Hierarchical
(Process 14)
JPEG Lossless, 1.2.840.10008.1.2.4.70 SCU None
Non-Hierarchical,
First-Order
Prediction
(Process 14
[Selection Value
1])
JPEG 2000 Image 1.2.840.10008.1.2.4.90 SCU None
Compression
(Lossless Only)
JPEG 2000 Image 1.2.840.10008.1.2.4.91 SCU None
Compression

STORAGE-SCU examines all the Abstract Syntax/Transfer Syntax pairs in the instances to be stored,
and applies the following algorithm when determining the Presentation Contexts to propose:

- For each Abstract Syntax/Transfer Syntax pair where the Transfer Syntax is uncompressed, a
Presentation Context will be defined for the Abstract Syntax with both Explicit and Implicit Little
Endian Transfer Syntaxes only.
- For those Abstract Syntax/Transfer Syntax pairs where the Transfer Syntax is encapsulated (e.g.
compressed), a Presentation Context is defined for the Abstract Syntax with only the
encapsulated Transfer Syntax.
- For those Abstract Syntax/Transfer Syntax pairs where the Transfer Syntax is encapsulated and
STORAGE-SCU is able to convert to an uncompressed Transfer Syntax (e.g. Explicit or Implicit
Little Endian), an additional Presentation Context is defined for each such Abstract Syntax, with
only Explicit and Implicit Little Endian Transfer Syntaxes.

The implications of this algorithm are:

- STORAGE-SCU will never compress an instance in order to store it.

- Compressed instances will be stored as-is whenever possible, or failing that, in either Explicit or
Implicit Little Endian format. When STORAGE-SCU is incapable of decompressing an instance,
it simply will not be stored and STORAGE-SCU will continue sending the remaining instances.

4.2.4.3.1.2.1 Extended Negotiation

No extended negotiation is performed.

4.2.4.3.1.3 SOP Specific Conformance

4.2.4.3.1.3.1 SOP Specific Conformance to Storage SOP Classes

STORAGE-SCU provides standard conformance to the Storage Service Class.

4.2.4.3.1.3.2 Presentation Context Acceptance Criterion

STORAGE-SCU does not accept associations.

4.2.4.3.1.3.3 Transfer Syntax Selection Policies

For encapsulated Transfer Syntaxes, STORAGE-SCU prefers to send each instance using its current
Transfer Syntax, and will find the first Presentation Context where the Transfer Syntax was accepted. In
the case where the Transfer Syntax was not accepted by the remote STORAGE-SCP, STORAGE-SCU

Page 24
will check for the acceptance of Explicit VR Little Endian and Implicit VR Little Endian, in that order. If
STORAGE-SCU cannot change the Transfer Syntax, the sub-operation will fail and it will not store the
instance.

In the case of uncompressed Transfer Syntaxes, STORAGE-SCU has no real preference. It will store the
instances in either Explicit VR Little Endian or Implicit VR Little Endian, depending on what was accepted
by the SCP.

4.2.4.3.1.3.4 Response Status

STORAGE-SCU will behave as described in the Table below in response to the status returned in the C-
STORE response command message.

Table 4.2-22
RESPONSE STATUS FOR STORAGE-SCU AND SEND STORAGE REQUEST

Service Further Meaning Status Behavior

Status Codes
Failure N/A Any Message shown in Send
Queue UI, continues storing
remaining instances
Warning N/A Any Message shown in Send
Queue UI, continues storing
remaining instances

4.2.4.3.2 Activity – Send User-Created Ancillary Content

4.2.4.3.2.1 Description and Sequencing of Activities

For each content creation session, a single attempt will be made to transmit the user-created ancillary
content (e.g. key object selections, softcopy presentation states, and encapsulated PDF documents) to
remote AE(s) according to the following rules:

 If configured to do so, the created instances will be sent to the user’s “Default Servers”, if any
have been defined. This will be done only when the source images exist on the respective
“Default Server.”
 If configured to do so, the created instances will be sent to the AE from which the source images
were received, based on the value in each source image’s meta header for “Source Application
Entity Title (0002,0016)”. The AE must be in the application’s pre-configured list in order for this
to succeed.
 If the source images were loaded directly (streamed) from a ClearCanvas ImageServer, the
created instances will be sent to it. This is not configurable.

Additionally, if the source images were loaded from the local store, the created instances will be imported
into it. This is not configurable.

For each remote AE, a single association will be established to send all the created instances. If an
instance cannot be sent, for whatever reason, no retry will be performed, and an attempt will be made to
send the next instance. An error message will be shown in the workstation’s UI.

4.2.4.3.2.2 Proposed Presentation Contexts

Table 4.2-23
PROPOSED PRESENTATION CONTEXTS FOR STORAGE-SCU
AND SEND USER-CREATED ANCILLARY CONTENT

Page 25
 Presentation Context Table
Abstract Syntax Transfer Syntax Role Extended
Name UID Name UID Negotiation
See Table 4.2-17 See Table 4.2-17 Explicit VR Little 1.2.840.10008.1.2.1 SCU None
Endian
Implicit VR Little 1.2.840.10008.1.2 SCU None
Endian

All user-created ancillary content types are never compressed for storage. In all instances, a single
Presentation Context will be defined for the Abstract Syntax with both Explicit and Implicit Little Endian
Transfer Syntaxes only.

4.2.4.3.2.2.1 Extended Negotiation

No extended negotiation is performed.

4.2.4.3.2.3 SOP Specific Conformance

4.2.4.3.2.3.1 SOP Specific Conformance to Storage SOP Classes

STORAGE-SCU provides standard conformance to the Storage Service Class.

4.2.4.3.2.3.2 Presentation Context Acceptance Criterion

STORAGE-SCU does not accept associations.

4.2.4.3.2.3.3 Transfer Syntax Selection Policies

STORAGE-SCU always stores key object selection documents and softcopy presentation states in either
Explicit VR Little Endian or Implicit VR Little Endian, depending on what was accepted by the SCP.

4.2.4.3.2.3.4 Response Status

See Table 4.2-22.

4.2.4.4 Association Acceptance Policy

STORAGE-SCU does not accept associations.

4.2.5 FIND-SCP

4.2.5.1 SOP Classes

FIND-SCP provides Standard Conformance to the following SOP classes:

Table 4.2-24
SOP CLASSES SUPPORTED BY FIND-SCP

SOP Class Name SOP Class UID

Study Root Query/Retrieve Information Model – FIND 1.2.840.10008.5.1.4.1.2.2.1

4.2.5.2 Association Policies

4.2.5.2.1 General
FIND-SCP accepts but never initiates associations.

Page 26
 Table 4.2-25
MAXIMUM PDU SIZE RECEIVED FOR FIND-SCP

Maximum PDU size received 114kB (approx.)

4.2.5.2.2 Number of Associations

Table 4.2-26
NUMBER OF ASSOCIATIONS FOR FIND-SCP

Maximum number of simultaneous associations Unlimited

4.2.5.2.3 Asynchronous Nature

FIND-SCP will only allow a single outstanding operation on an Association. Therefore, FIND-SCP will not
perform asynchronous operations window negotiation.

4.2.5.2.4 Implementation Identifying Information

Table 4.2-27
DICOM IMPLEMENTATION CLASS AND VERSION FOR FIND-SCP

Implementation Class UID 1.3.6.1.4.1.25403.1.1.1

Implementation Version Name Dicom 0.1

4.2.5.3 Association Initiation Policy

FIND-SCP does not initiate associations.

4.2.5.4 Association Acceptance Policy

When FIND-SCP accepts an association, it will respond to query requests. The association will be
rejected if:

- The Called AE Title does not match the AE Title shared by all the SCPs of the application.

4.2.5.4.1 Activity – Receive Query Request

4.2.5.4.1.1 Description and Sequencing of Activities

When a query is received, the internal database is queried for the result set.

4.2.5.4.1.2 Accepted Presentation Contexts

Table 4.2-28
ACCEPTABLE PRESENTATION CONTEXTS FOR FIND-SCP AND RECEIVE QUERY REQUEST

Presentation Context Table

Abstract Syntax Transfer Syntax Role Extended
Name UID Name UID Negotiation
See Table 4.2-24 See Table 4.2-24 Explicit VR Little 1.2.840.10008.1.2.1 SCP None
Endian
Implicit VR Little 1.2.840.10008.1.2 SCP None
Endian

4.2.5.4.1.2.1 Extended Negotiation

No extended negotiation is performed.

Page 27
In particular, relational queries are not supported.

4.2.5.4.1.3 SOP Specific Conformance

4.2.5.4.1.3.1 SOP Specific Conformance to C-FIND SOP Classes

FIND-SCP provides standard conformance to the supported C-FIND SOP Classes with one exception: all
matching is case-insensitive, which is not in strict compliance with DICOM 2009 PS 3.4. This was a
conscious decision, as case-sensitive matching is not intuitive and most users would be completely
unaware of the fact that it even matters, causing many expected query matches to not be returned.

Only a single information model, Study Root, is supported.

Only those attributes that are requested are returned in a C-FIND response. Some optional requested
attributes will be returned as per Table 4.2-29.

Table 4.2-29
STUDY ROOT RESPONSE IDENTIFIER FOR FIND-SCP

Types of
Name Tag
Matching
STUDY Level
Study Instance UID (0020,000D) UNIQUE
Patient’s ID (0010,0020) S,*,U
Patient’s Name (0010,0010) S,*,U
Patient's Birth Date (0010,0030) U
Patient's Sex (0010,0040) S,*,U
Patient Species Description (0010,2201) S,*,U
Patient Species Code Sequence (0010,2202) SQ
> Code Value (0008,0100) S,*,U
> Coding Scheme Designator (0008,0102) S,*,U
> Code Meaning (0008,0104) S,*,U
Patient Breed Description (0010,2292) S,*,U
Patient Breed Code Sequence (0010,2293) SQ
> Code Value (0008,0100) S,*,U
> Coding Scheme Designator (0008,0102) S,*,U
> Code Meaning (0008,0104) S,*,U
Responsible Person (0010,2297) S,*,U
Responsible Person Role (0010,2298) S,*,U
Responsible Organization (0010,2299) S,*,U
Study ID (0020,0010) S,*,U
Study Description (0008,1030) S,*,U
Modalities In Study (0008,0061) S,*,U
Study Date (0008,0020) S,U,R
Study Time (0008,0030) U
Accession Number (0008,0050) S,*,U

Page 28
 Referring Physician’s Name (0008,0090) S,*,U
Procedure Code Sequence (0008,1032) SQ
> Code Value (0008,0100) S,*,U
> Coding Scheme Designator (0008,0102) S,*,U
Number Of Study Related Series (0020,1206) S,*,U
Number Of Study Related Instances (0020,1208) S,*,U
SERIES Level
Series Instance UID (0020,000E) UNIQUE
Modality (0008,0060) S,*,U
Series Description (0008,103E) S,*,U
Series Number (0020,0011) S,*,U
Number Of Series Related Instances (0020,1209) S,*,U
IMAGE Level
SOP Instance UID (0008,0018) UNIQUE
Instance Number (0020,0013) S,*,U
SOP Class UID (0008,0016) L,U

Common to all query levels

Specific Character Set (0008,0005) N/A

Types of Matching:

An "S" indicates the identifier attribute uses Single Value Matching, an “R” indicates Range Matching, a
“*” indicates wildcard matching, a ‘U’ indicates Universal Matching, an ‘SQ’ indicates Sequence Matching,
and an ‘L’ indicates that a UID list is sent. “UNIQUE” indicates that this is the Unique Key for that query
level, in which case Universal Matching or Single Value Matching is used depending on the query level.

Note that, in the case of wildcard matching, the question mark (?) operator is currently not supported.

4.2.5.4.1.3.2 Presentation Context Acceptance Criterion

FIND-SCP will always accept any Presentation Context for the supported SOP Classes with the
supported Transfer Syntaxes. More than one proposed Presentation Context will be accepted for the
same Abstract Syntax if the Transfer Syntax is supported, whether or not it is the same as another
Presentation Context.

4.2.5.4.1.3.3 Transfer Syntax Selection Policies

FIND-SCP will always select the first Transfer Syntax proposed by the client that is supported by the
SCP, per Presentation Context.

FIND-SCP will accept duplicate Presentation Contexts; that is, if it is offered multiple Presentation
Contexts, each of which offers acceptable Transfer Syntaxes, it will accept all Presentation Contexts,
applying the same method for selecting a Transfer Syntax for each.

4.2.5.4.1.3.4 Response Status

FIND-SCP will behave as described in Table 4.2-30 when constructing the C-FIND response command
message(s).

Page 29
 Table 4.2-30
RESPONSE STATUS FOR FIND-SCP AND RECEIVE QUERY REQUEST

Service Further Meaning Status Behavior

Status Codes
Failure Identifier does not A900 Sent when the Query/Retrieve Level
match SOP Class in the C-FIND request is not present
or valid

Unable to process Cxxx Sent if internal database query is

unsuccessful

Pending Matches are FF00 Sent

continuing -
Current Match is
supplied and any
Optional Keys
were supported in
the same manner
as Required Keys
Success Matching is 0000 Sent
complete

4.2.6 FIND-SCU

4.2.6.1 SOP Classes

FIND-SCU provides Standard Conformance to the following SOP classes:

Table 4.2-31
SOP CLASSES SUPPORTED BY FIND-SCU

SOP Class Name SOP Class UID

Study Root Query/Retrieve Information Model – FIND 1.2.840.10008.5.1.4.1.2.2.1

4.2.6.2 Association Policies

4.2.6.2.1 General
FIND-SCU initiates but never accepts associations.

Table 4.2-32
MAXIMUM PDU SIZE RECEIVED FOR FIND-SCU

Maximum PDU size received 114kB (approx.)

4.2.6.2.2 Number of Associations

Table 4.2-33
NUMBER OF ASSOCIATIONS FOR FIND-SCU

Maximum number of simultaneous associations 1

4.2.6.2.3 Asynchronous Nature

FIND-SCU will only allow a single outstanding operation on an Association. Therefore, FIND-SCU will not
perform asynchronous operations window negotiation.

Page 30
4.2.6.2.4 Implementation Identifying Information
Table 4.2-34
DICOM IMPLEMENTATION CLASS AND VERSION FOR FIND-SCU

Implementation Class UID 1.3.6.1.4.1.25403.1.1.1

Implementation Version Name Dicom 0.1

4.2.6.3 Association Initiation Policy

FIND-SCU attempts to initiate a new association when the user performs the query action from the user
interface. Furthermore, FIND-SCU attempts to initiate new associations for the purpose of locating prior
studies when the user opens one or more studies for viewing.

4.2.6.3.1 Activity – Query Remote AE

4.2.6.3.1.1 Description and Sequencing of Activities

A single attempt will be made to query the remote AE. If the query fails for whatever reason, no retry will
be performed.

4.2.6.3.1.2 Proposed Presentation Contexts

Table 4.2-35
PROPOSED PRESENTATION CONTEXTS FOR FIND-SCU AND QUERY REMOTE AE

Presentation Context Table

Abstract Syntax Transfer Syntax Role Extended
Name UID Name UID Negotiation
See Table 4.2-31 See Table 4.2-31 Explicit VR Little 1.2.840.10008.1.2.1 SCU None
Endian
Implicit VR Little 1.2.840.10008.1.2 SCU None
Endian

4.2.6.3.1.2.1 Extended Negotiation

No extended negotiation is performed.

In particular, relational queries are not supported.

4.2.6.3.1.3 SOP Specific Conformance

4.2.6.3.1.3.1 SOP Specific Conformance to C-FIND SOP Classes

FIND-SCU provides standard conformance to the supported C-FIND SOP Classes.

Only a single information model, Study Root, is supported and is only used at the STUDY and SERIES
levels. IMAGE level queries are never performed.

No CANCEL requests are ever issued.

Unexpected attributes returned in a C-FIND response (those not requested) are discarded. Requested
return attributes not returned by the SCP are ignored. In general, non-matching responses returned by
the SCP due to unsupported (hopefully optional) matching keys are not filtered locally by the FIND-SCU
and thus will still be presented in the browser, with the exception of Modalities in Study, which is filtered
by the SCU.

Page 31
Specific Character Set is not included in the C-FIND request at any level. If present in the response,
Specific Character Set will be used to identify character sets other than the default character set for
display of strings in the browser.

Instance Availability is not included in the C-FIND request at any level. For STUDY level queries initiated
by the user, the value is shown in the results table if it was returned in the response.

Retrieve AE Title is not included in the C-FIND request at any level. If present in the response, it is
ignored. The application currently assumes that the AE queried is also the AE from which to retrieve;
normally, this is a reasonable assumption.

Table 4.2-36
STUDY ROOT REQUEST IDENTIFIER FOR FIND-SCU

Types of
Name Tag
Matching
STUDY Level
Study Instance UID (0020,000D) UNIQUE
Patient’s ID (0010,0020) S,*,U
Patient’s Name (0010,0010) S,*,U
Patient's Birth Date (0010,0030) U
Patient Species Description (0010,2201) S,*,U
Patient Species Code Sequence (0010,2202) SQ
> Code Value (0008,0100) S,*,U
> Coding Scheme Designator (0008,0102) U
> Code Meaning (0008,0104) S,*,U
Patient Breed Description (0010,2292) S,*,U
Patient Breed Code Sequence (0010,2293) SQ
> Code Value (0008,0100) S,*,U
> Coding Scheme Designator (0008,0102) U
> Code Meaning (0008,0104) S,*,U
Responsible Person (0010,2297) S,*,U
Responsible Person Role (0010,2298) U
Responsible Organization (0010,2299) S,*,U
Referring Physician’s Name (0008,0090) S,*,U
Study Description (0008,1030) S,*,U
Modalities In Study (0008,0061) S,U
Study Date (0008,0020) S,U,R
Study Time (0008,0030) U
Accession Number (0008,0050) S,*,U
Number Of Study Related Instances (0020, 1208) U
SERIES Level
Study Instance UID (0020,000D) UNIQUE
Series Instance UID (0020, 000E) UNIQUE

Page 32
 Modality (0008, 0060) U
Series Description (0008, 103E) U
Series Number (0020, 0011) U
Number of Series Related Instances (0020, 1209) U
IMAGE Level
N/A
Common to all query levels
Specific Character Set (0008,0005) N/A

Types of Matching:

An "S" indicates the identifier attribute uses Single Value Matching, an “R” indicates Range Matching, a
“*”indicates wildcard matching, a ‘U’ indicates Universal Matching, an ‘SQ’ indicates Sequence Matching,
an ‘L’ indicates that a UID list is sent, and “UNIQUE” indicates that this is the Unique Key for that query
level.

4.2.6.3.1.3.2 Presentation Context Acceptance Criterion

FIND-SCU does not accept associations.

4.2.6.3.1.3.3 Transfer Syntax Selection Policies

FIND-SCU prefers Explicit VR Little Endian Transfer Syntax, which is always first in the proposed
Presentation Context.

4.2.6.3.1.3.4 Response Status

FIND-SCU will behave as described in Table 4.2-37 in response to the status returned in the C-FIND
response command message(s).

Table 4.2-37
RESPONSE STATUS FOR FIND-SCU AND QUERY REMOTE AE REQUEST

Service Further Meaning Status Behavior

Status Codes
Failure N/A Any Association closed, message shown
to user
Cancel Matching FE00 Association closed, message shown
terminated due to to user
Cancel request
Success Matching is 0000 Association closed
complete - No final
Identifier is
supplied

4.2.6.3.2 Activity – Query for Prior Studies

4.2.6.3.2.1 Description and Sequencing of Activities

When one or more studies are opened for viewing by the user, an attempt is made to query the local
store and each remote AE defined as a “Default Server” in the configuration for each unique patient ID in
the opened studies. If a query fails for whatever reason, the remaining queries will not be performed, and
the user will be notified of the failure.

Page 33
Studies discovered this way which were not specifically selected by the user are considered “prior
studies” and are listed by the application to inform the user of their presence. In some configurations
(namely, when the source AE of the prior study is a ClearCanvas ImageServer), the application also
supports viewing the prior study as if it had been selected by the user initially via the Streaming
mechanism (see Section 4.3.2.1).

The only parameter used in each query is the patient ID, with a wildcard character (asterisk) appended by
default. A configurable algorithm exists that allows the patient ID query parameter to be modified before
the query is executed, in order to maximize the number of studies returned in the results.

Similarly, because not all the results returned will belong to the patient, there is another configurable
algorithm used to reconcile the patient ID in the returned study identifiers against those of the loaded
studies. By default, the algorithm specifies that each patient ID in the results must match one of the
patient IDs in the loaded studies exactly in order to be considered a true match. Studies returned in the
results that cannot be reconciled are filtered out.

These algorithms are very flexible, but would typically only be used to trim whitespace and suffixes rather
than making sweeping modifications. For obvious reasons, configuration of the algorithms should be
done with great care, as it could result in false matches or in true matches being missed, which could
adversely impact patient care.

4.2.6.3.2.2 Proposed Presentation Contexts

See Table 4.2-35.

4.2.6.3.2.2.1 Extended Negotiation

No extended negotiation is performed.

In particular, relational queries are not supported.

4.2.6.3.2.3 SOP Specific Conformance

4.2.6.3.2.3.1 SOP Specific Conformance to C-FIND SOP Classes

FIND-SCU provides standard conformance to the supported C-FIND SOP Classes.

Only a single information model, Study Root, is supported and is only used at the highest level (STUDY).

No CANCEL requests are ever issued.

Unexpected attributes returned in a C-FIND response (those not requested) are discarded. Requested
return attributes not returned by the SCP are ignored.

Specific Character Set is not included in the C-FIND request. If present in the response, Specific
Character Set will be used to identify character sets other than the default character set for display of
strings in the viewer.

For each “prior study” found, Retrieve AE Title is used to determine if the study can be streamed, and if
so, the study will be loaded into the viewer in the same way as one(s) selected by the user.

Table 4.2-38
STUDY ROOT REQUEST IDENTIFIER FOR FIND-SCU FOR QUERY FOR PRIOR STUDIES

Types of
Name Tag
Matching
STUDY Level
Study Instance UID (0020,000D) UNIQUE

Page 34
 Patient’s ID (0010,0020) *
Patient’s Name (0010,0010) U
Patient's Birth Date (0010,0030) U
Patient’s Birth Time (0010,0032) U
Patient’s Sex (0010,0040) U
Study Description (0008,1030) U
Modalities In Study (0008,0061) U
Study ID (0020,0010) U
Study Description (0008,1030) U
Study Date (0008,0020) U
Study Time (0008,0030) U
Accession Number (0008,0050) U
Referring Physician’s Name (0008,0090) U
Number of Study Related Instances (0020,1208) U
Number of Study Related Series (0020,1206) U
SERIES Level
N/A
IMAGE Level
N/A
Common to all query levels
Specific Character Set (0008,0005) N/A

Types of Matching:

An "S" indicates the identifier attribute uses Single Value Matching, an “R” indicates Range Matching, a
“*”indicates wildcard matching, a ‘U’ indicates Universal Matching, an ‘L’ indicates that a UID list is sent,
and “UNIQUE” indicates that this is the Unique Key for that query level.

4.2.6.3.2.3.2 Presentation Context Acceptance Criterion

FIND-SCU does not accept associations.

4.2.6.3.2.3.3 Transfer Syntax Selection Policies

FIND-SCU prefers Explicit VR Little Endian Transfer Syntax, which is always first in the proposed
Presentation Context.

4.2.6.3.2.3.4 Response Status

See Table 4.2-37.

4.2.6.4 Association Acceptance Policy

FIND-SCU does not accept associations.

4.2.7 MOVE-SCP

4.2.7.1 SOP Classes

MOVE-SCP provides Standard Conformance to the following SOP classes:

Page 35
 Table 4.2-39
SOP CLASSES SUPPORTED BY MOVE-SCP

SOP Class Name SOP Class UID

Study Root Query/Retrieve Information Model – MOVE 1.2.840.10008.5.1.4.1.2.2.2

4.2.7.2 Association Policies

4.2.7.2.1 General
MOVE-SCP accepts but never initiates associations.

Table 4.2-40
MAXIMUM PDU SIZE RECEIVED FOR MOVE-SCP

Maximum PDU size received 114kB (approx.)

4.2.7.2.2 Number of Associations

Table 4.2-41
NUMBER OF ASSOCIATIONS FOR MOVE-SCP

Maximum number of simultaneous associations Unlimited

4.2.7.2.3 Asynchronous Nature

MOVE-SCP will only allow a single outstanding operation on an Association. Therefore, MOVE-SCP will
not perform asynchronous operations window negotiation.

4.2.7.2.4 Implementation Identifying Information

Table 4.2-42
DICOM IMPLEMENTATION CLASS AND VERSION FOR MOVE-SCP

Implementation Class UID 1.3.6.1.4.1.25403.1.1.1

Implementation Version Name Dicom 0.1

4.2.7.3 Association Initiation Policy

MOVE-SCP initiates an association with the AE specified as the Move Destination in the MOVE request,
in order to store the requested instances. The remote AE must be in the application’s pre-configured AE
list.

4.2.7.4 Association Acceptance Policy

When MOVE-SCP accepts an association, it will respond to move requests. The association will be
rejected if:

- The Called AE Title does not match the AE Title shared by all the SCPs of the application.

4.2.7.4.1 Activity – Receive Move Request

4.2.7.4.1.1 Description and Sequencing of Activities

As requests are received, a STORAGE-SCU operation is initiated to send the requested instances to the
specified remote AE.

Page 36
4.2.7.4.1.2 Proposed Presentation Contexts
Table 4.2-43
ACCEPTABLE PRESENTATION CONTEXTS FOR MOVE-SCP AND RECEIVE MOVE REQUEST

Presentation Context Table

Abstract Syntax Transfer Syntax Role Extended
Name UID Name UID Negotiation
See Table 4.2-39 See Table 4.2-39 Explicit VR Little 1.2.840.10008.1.2.1 SCP None
Endian
Implicit VR Little 1.2.840.10008.1.2 SCP None
Endian

4.2.7.4.1.2.1 Extended Negotiation

No extended negotiation is performed through MOVE-SCP.

In particular, relational retrievals are not supported.

4.2.7.4.1.3 SOP Specific Conformance

4.2.7.4.1.3.1 SOP Specific Conformance to C-MOVE SOP Classes

MOVE-SCP provides standard conformance to the supported C-MOVE SOP Classes.

Only a single information model, Study Root, is supported.

The move is performed to the destination AE Title specified in the original request. . If the destination AE
does not exist in the application’s pre-configured list, the store operations are not performed.

Table 4.2-44
STUDY ROOT REQUEST IDENTIFIER FOR MOVE-SCP

Unique,
Name Tag Matching or
Return Key
STUDY level
Study Instance UID (0020,000D) U
SERIES level
Study Instance UID (0020,000D) U
Series Instance UID (0020,000E) U
IMAGE level
Study Instance UID (0020,000D) U
Series Instance UID (0020,000E) U
SOP Instance UID (0008,0018) U

4.2.7.4.1.3.2 Presentation Context Acceptance Criterion

MOVE-SCP will only accept a Presentation Context compatible with the one listed in Table 4.2-43.

4.2.7.4.1.3.3 Transfer Syntax Selection Policies

MOVE-SCP will always select the first Transfer Syntax proposed by the client that is supported by the
SCP, per Presentation Context.

Page 37
MOVE-SCP will accept duplicate Presentation Contexts; that is, if it is offered multiple Presentation
Contexts, each of which offers acceptable Transfer Syntaxes, it will accept all Presentation Contexts,
applying the same method for selecting a Transfer Syntax for each.

4.2.7.4.1.3.4 Response Status

MOVE-SCP will behave as described in the Table below when generating the C-MOVE response
command message.

Table 4.2-45
RESPONSE STATUS FOR MOVE-SCP AND SEND TO REMOTE AE REQUEST

Service Further Meaning Status Behavior

Status Codes
Failure Refused: Move A801 Sent if the destination AE
Destination Title has not been
unknown preconfigured

Identifier does not A900 Sent when the

match SOP Class Query/Retrieve Level is not
present or is invalid

Unable to process Cxxx Sent if the internal database

query fails

Warning Sub-operations B000 Sent when at least one

Complete - One or storage sub-operation has
more Failures failed

Success Sub-operations 0000 Sent when storage sub-

Complete - No operations have completed
Failures with no failures

Pending Sub-operations are FF00 Sent as sub-operations

continuing progress

4.2.7.4.1.3.5 Sub-operation Dependent Behavior

Since the C-MOVE operation is dependent on completion of C-STORE sub-operations that are occurring
on a separate association, the question of failure of operations on the other association(s) must be
considered.

MOVE-SCP initiates a C-STORE sub-operation for each SOP instance that matches the information
supplied in the C-MOVE request (for example, all SOP instances in a study). The responses from the
MOVE-SCP are purely dependent on the success or failure of the C-STORE sub-operations, not on any
explicit action by MOVE-SCP.

Whether or not the remote AE accepts the C-STORE sub-operations is beyond the control of MOVE-
SCP.

If the association on which the C-MOVE request was issued is aborted for any reason, the C-STORE sub-
operations will continue.

If the C-MOVE operation is canceled by the remote AE, MOVE-SCP will also attempt to cancel the
remaining C-STORE sub-operation(s) and close the association.

Page 38
Because MOVE-SCP uses STORAGE-SCU to store the requested instances, the progress and status of
the C-STORE sub-operations will appear in the application’s “Send Queue” UI.

4.2.8 MOVE-SCU

4.2.8.1 SOP Classes

MOVE-SCU provides Standard Conformance to the following SOP classes:

Table 4.2-46
SOP CLASSES SUPPORTED BY MOVE-SCU

SOP Class Name SOP Class UID

Study Root Query/Retrieve Information Model – MOVE 1.2.840.10008.5.1.4.1.2.2.2

4.2.8.2 Association Policies

4.2.8.2.1 General
MOVE-SCU initiates but never accepts associations.

Table 4.2-47
MAXIMUM PDU SIZE RECEIVED FOR MOVE-SCU

Maximum PDU size received 114kB (approx.)

4.2.8.2.2 Number of Associations

Table 4.2-48
NUMBER OF ASSOCIATIONS FOR MOVE-SCU

Maximum number of simultaneous associations Unlimited

4.2.8.2.3 Asynchronous Nature

MOVE-SCU will only allow a single outstanding operation on an Association. Therefore, MOVE-SCU will
not perform asynchronous operations window negotiation.

4.2.8.2.4 Implementation Identifying Information

Table 4.2-49
DICOM IMPLEMENTATION CLASS AND VERSION FOR MOVE-SCU

Implementation Class UID 1.3.6.1.4.1.25403.1.1.1

Implementation Version Name Dicom 0.1

4.2.8.3 Association Initiation Policy

MOVE-SCU attempts to initiate a new association when the user performs the retrieve action from the
user interface.

4.2.8.3.1 Activity – Retrieve from Remote AE

4.2.8.3.1.1 Description and Sequencing of Activities

For the studies or series selected from the user interface to be retrieved, a single attempt will be made to
retrieve them from the selected remote AE. If the retrieve fails, for whatever reason, no retry will be
performed.

Page 39
4.2.8.3.1.2 Proposed Presentation Contexts
Table 4.2-50
PROPOSED PRESENTATION CONTEXTS FOR MOVE-SCU AND RETRIEVE FROM REMOTE AE
REQUEST

Presentation Context Table

Abstract Syntax Transfer Syntax Role Extended
Name UID Name UID Negotiation
See Table 4.2-46 See Table 4.2-46 Explicit VR Little 1.2.840.10008.1.2.1 SCU None
Endian
Implicit VR Little 1.2.840.10008.1.2 SCU None
Endian

4.2.8.3.1.2.1 Extended Negotiation

No extended negotiation is performed.

In particular, relational retrievals are not supported.

4.2.8.3.1.3 SOP Specific Conformance

4.2.8.3.1.3.1 SOP Specific Conformance to C-MOVE SOP Classes

MOVE-SCU provides standard conformance to the supported C-MOVE SOP Classes, with one exception:
the retrieval is performed from the AE that was queried by FIND-SCU, rather than the AE specified in the
Retrieve AE Title attribute of the C-FIND response.

Only a single information model, Study Root, is supported.

Retrievals can be performed at the STUDY and SERIES levels only.

No CANCEL requests are ever issued.

The instances are retrieved to the current application’s local store by specifying the Move Destination as
the shared AE Title of the local application. This implies that the remote C-MOVE SCP must be
preconfigured to determine the presentation address corresponding to the local application’s AE.

Table 4.2-51
STUDY ROOT REQUEST IDENTIFIER FOR MOVE-SCU

Unique,
Name Tag Matching or
Return Key
STUDY level
Study Instance UID (0020,000D) UNIQUE
SERIES level
Study Instance UID (0020,000D) UNIQUE
Series Instance UID (0020,000E) UNIQUE

4.2.8.3.1.3.2 Presentation Context Acceptance Criterion

MOVE-SCU does not accept associations.

Page 40
4.2.8.3.1.3.3 Transfer Syntax Selection Policies
MOVE-SCU prefers Explicit VR Little Endian Transfer Syntax, which is always first in the proposed
Presentation Context.

4.2.8.3.1.3.4 Response Status

MOVE-SCU will behave as described in the Table below in response to the status returned in the C-
MOVE response command message(s).

Table 4.2-52
RESPONSE STATUS FOR MOVE-SCU AND RETRIEVE FROM REMOTE AE REQUEST

Service Further Meaning Status Behavior

Status Codes
Failure N/A Any Association closed,
message shown in Receive
Queue UI

Cancel Sub-operations FE00 Association closed,

terminated due to message shown in Receive
Cancel Indication Queue UI

Warning N/A Any message shown in Receive

Queue UI

Success Sub-operations 0000 Association closed

Complete - No
Failures

4.2.8.3.1.3.5 Sub-operation Dependent Behavior

Since the C-MOVE operation is dependent on completion of C-STORE sub-operations that are occurring
on another association, the question of failure of operations on the other association(s) must be
considered.

With the exception of showing error messages in the Receive Queue UI, MOVE-SCU completely ignores
whatever activities are taking place in relation to the STORAGE-SCP AE that is receiving the retrieved
instances. Once the C-MOVE has been initiated it runs to completion (or failure) as described in the C-
MOVE response command message(s). There is no attempt by MOVE-SCU to confirm that instances
have actually been successfully received or locally stored.

Whether or not completely or partially successful retrievals are made available in the internal database to
the user is purely dependent on the success or failure of the C-STORE sub-operations, not on any explicit
action by MOVE-SCU.

Whether or not the remote AE attempts to retry any failed C-STORE sub-operations is beyond the control
of MOVE-SCU.

If the association on which the C-MOVE was issued is aborted for any reason, whether or not the C-
STORE sub-operations continue is dependent on the remote AE; the local STORAGE-SCP will continue
to accept associations and storage operations regardless. In this case, an error indicating why the
MOVE-SCU association terminated before the C-MOVE operation completed should be shown in the
application’s “Receive Queue” UI.

4.2.8.4 Association Acceptance Policy

MOVE-SCU does not accept associations.

Page 41
4.2.9 PRINT-SCU

4.2.9.1 SOP Classes

PRINT-SCU provides Standard Conformance to the following SOP classes:

Table 4.2-53
SOP CLASSES SUPPORTED BY PRINT-SCU

SOP Class Name SOP Class UID

Basic Grayscale Print Management Meta SOP Class 1.2.840.10008.5.1.1.9
Basic Film Session SOP Class 1.2.840.10008.5.1.1.1
Basic Film Box SOP Class 1.2.840.10008.5.1.1.2
Basic Grayscale Image Box SOP Class 1.2.840.10008.5.1.1.4
Printer SOP Class 1.2.840.10008.5.1.1.16
Basic Color Print Management Meta SOP Class 1.2.840.10008.5.1.1.18
Basic Film Session SOP Class 1.2.840.10008.5.1.1.1
Basic Film Box SOP Class 1.2.840.10008.5.1.1.2
Basic Color Image Box SOP Class 1.2.840.10008.5.1.1.4.1
Printer SOP Class 1.2.840.10008.5.1.1.16

4.2.9.2 Association Policies

4.2.9.2.1 General
PRINT-SCU initiates but never accepts associations.

Table 4.2-54
MAXIMUM PDU SIZE RECEIVED FOR PRINT-SCU

Maximum PDU size received 114kB (approx.)

4.2.9.2.2 Number of Associations

Table 4.2-55
NUMBER OF ASSOCIATIONS FOR PRINT-SCU

Maximum number of simultaneous associations 1

4.2.9.2.3 Asynchronous Nature

PRINT-SCU will only allow a single outstanding operation on an Association. Therefore, PRINT-SCU will
not perform asynchronous operations window negotiation.

4.2.9.2.4 Implementation Identifying Information

Table 4.2-56
DICOM IMPLEMENTATION CLASS AND VERSION FOR PRINT-SCU

Implementation Class UID 1.3.6.1.4.1.25403.1.1.1

Implementation Version Name Dicom 0.1

Page 42
4.2.9.3 Association Initiation Policy
PRINT-SCU attempts to initiate a new association when the user performs the print images action from
the user interface to a single remote AE.

4.2.9.3.1 Activity – Print Images

4.2.9.3.1.1 Description and Sequencing of Activities

A single attempt will be made to send images for printing to the remote AE. If the request fails for
whatever reason, no retry will be performed. The application allows the user to cancel a print job that is in
progress, in which case PRINT-SCU will immediately abort the association.

4.2.9.3.1.2 Proposed Presentation Contexts

Table 4.2-57
PROPOSED PRESENTATION CONTEXTS FOR PRINT-SCU AND PRINT IMAGES

Presentation Context Table

Abstract Syntax Transfer Syntax Role Extended
Name UID Name UID Negotiation
See Table 4.2-53 See Table 4.2-53 Explicit VR Little 1.2.840.10008.1.2.1 SCU None
Endian
Implicit VR Little 1.2.840.10008.1.2 SCU None
Endian

4.2.9.3.1.2.1 Extended Negotiation

No extended negotiation is performed.

4.2.9.3.1.3 SOP Specific Conformance

The tables in this section use a number of abbreviations. The abbreviations used in the “Presence of
Value” column are:

- ALWAYS: Attribute is always present with a non-zero-length value

- ANAP: Attribute is not always present; this is usually because the user selected “Default” for the
attribute in the configuration, which means that the printer should apply its own default value.

The abbreviations used in the “Source” column are:

- AUTO: The attribute value is generated automatically, or indirectly from previous user input
- USER: The attribute value is taken directly from user input

4.2.9.3.1.3.1 SOP Specific Conformance to Basic Film Session SOP Class

PRINT-SCU provides standard conformance to the Basic Film Session SOP Class.

A single film session is created by issuing an N-CREATE request to the SCP containing the attributes
listed in Table 4.2-58. Specific Character Set is not included in the N-CREATE request.

The selected images are then processed in sequence by creating the necessary film boxes that reference
the film session (see 4.2.9.3.1.3.2).

After all the selected images have been processed, the film session is deleted by issuing an N-DELETE
request to the SCP.

Page 43
 Table 4.2-58
BASIC FILM SESSION SOP CLASS N-CREATE ATTRIBUTE SUPPORT FOR PRINT-SCU

Attribute Name Tag VR Value Presence Source

of Value
Number of Copies (2000,0010) IS A number between 1 and 100 ALWAYS USER
Print Priority (2000,0020) CS One of HIGH, MED or LOW ANAP USER
Medium Type (2000,0030) CS One of PAPER, CLEAR FILM, ANAP USER
BLUE FILM, MAMMO CLEAR
FILM, MAMMO BLUE FILM
Film Destination (2000,0040) CS One of MAGAZINE, ANAP USER
PROCESSOR or BIN_i, where
“i” represents a bin number
between 0 and 9

PRINT-SCU will behave as described in Table 4.2-59 in response to the status returned in a Basic Film
Session N-DELETE response after all the selected images have been processed. Otherwise, PRINT-
SCU behaves as described in Table 4.2-66.

Table 4.2-59
BASIC FILM SESSION N-DELETE RESPONSE STATUS FOR PRINT-SCU AND PRINT IMAGES

Service Further Meaning Status Behavior

Status Codes
Failure N/A Any Association closed, message shown
to user
Warning N/A Any Message logged
Success Print operation 0000 Association closed
completed
successfully

4.2.9.3.1.3.2 SOP Specific Conformance to Basic Film Box SOP Class

PRINT-SCU provides standard conformance to the Basic Film Box SOP Class.

During any given film session, a single film box is created initially by issuing an N-CREATE request to the
SCP containing the attributes listed in Table 4.2-60.

The available image boxes that reference the film box are then set by processing the selected images in
sequence. Individual image boxes are updated by issuing N-SET requests as a Basic Grayscale Image
Box (see 4.2.9.3.1.3.3) or as a Basic Color Image Box (see 4.2.9.3.1.3.4) depending on a user-specified
option.

When all the image boxes available on the film box have been set, the film box is printed by issuing an N-
ACTION “Print” request to the SCP. If the response status is Success, PRINT-SCU proceeds by issuing
an N-DELETE request to the SCP for the film box.

If there are still selected images that have not yet been processed, PRINT-SCU repeats the actions
starting with creating a new film box.

Page 44
 Table 4.2-60
BASIC FILM BOX SOP CLASS N-CREATE ATTRIBUTE SUPPORT FOR PRINT-SCU

Attribute Name Tag VR Value Presence Source

of Value
Image Display Format (2010,0010) ST See Table 4.2-61 ALWAYS USER
Referenced Film (2010,1500) SQ A single item that references ALWAYS AUTO
Session Sequence the parent film session
> Referenced SOP (0008,1150) UI Basic Film Session SOP Class ALWAYS AUTO
Class UID 1.2.840.10008.5.1.1.1
> Referenced SOP (0008,1155) UI The UID of the parent film ALWAYS AUTO
Instance UID session
Film Orientation (2010,0040) CS One of PORTRAIT or ALWAYS USER
LANDSCAPE
Film Size ID (2010,0050) CS See Table 4.2-62 ALWAYS USER
Magnification Type (2010,0060) CS One of REPLICATE, ANAP USER
BILINEAR or CUBIC
Configuration (2010,0150) ST When present, a printer ANAP USER
Information configuration string specified
by the user
Border Density (2010,0100) CS One of BLACK or WHITE ANAP USER
Empty Image Density (2010,0110) CS One of BLACK or WHITE ANAP USER
Requested Resolution (2020,0050) CS One of STANDARD or HIGH ALWAYS USER
ID

Table 4.2-61
SUPPORTED IMAGE DISPLAY FORMATS FOR PRINT-SCU

Image Display Format Description

STANDARD\1,1 1 single image box
STANDARD\1,2 2 rows of 1 image box
STANDARD\2,1 1 row of 2 equal sized image boxes
STANDARD\2,2 2 rows of 2 equal sized image boxes
STANDARD\2,4 4 rows of 2 equal sized image boxes
STANDARD\4,1 1 row of 4 equal sized image boxes
STANDARD\4,2 2 rows of 4 equal sized image boxes
STANDARD\4,4 4 rows of 4 equal sized image boxes
ROW\1,2 First row with 1 image box, second row with
2 equal sized image boxes
COL\1,2 First column with 1 image box, second
column with 2 equal sized image boxes

Table 4.2-62
SUPPORTED FILM SIZE IDS FOR PRINT-SCU

Film Size ID Description

8INX10IN 8 in x 10 in

Page 45
 8_5INX11IN 8.5 in x 11 in
10INX12IN 10 in x 12 in
10INX14IN 10 in x 14 in (25.7 cm x 36.4 cm)
11INX14IN 11 in x 14 in
11INX17IN 11 in x 17 in
14INX14IN 14 in x 14 in
14INX17IN 14 in x 17 in
24CMX24CM 24 cm x 24 cm
24CMX30CM 24 cm x 30 cm
A4 A4 (210 mm x 297 mm)
A3 A3 (294 mm x 420 mm)

4.2.9.3.1.3.3 SOP Specific Conformance to Basic Grayscale Image Box SOP Class
PRINT-SCU provides standard conformance to the Basic Grayscale Image Box SOP Class.

For each image box SOP instance contained in the film box N-CREATE response, PRINT-SCU will
update the image box by issuing an N-SET request with the attributes listed in Table 4.2-63.

Table 4.2-63
BASIC GRAYSCALE IMAGE BOX SOP CLASS N-SET ATTRIBUTE SUPPORT FOR PRINT-SCU

Attribute Name Tag VR Value Presence Source

of Value
Image Box Position (2020,0010) US An integer indicating the ALWAYS AUTO
sequencing of the image
boxes, with the first image box
having the value 1
Basic Grayscale Image (2020,0110) SQ A single item containing the ALWAYS AUTO
Sequence grayscale image box pixel data
> Samples Per Pixel (0028,0002) US 1 ALWAYS AUTO
> Photometric (0028,0004) CS MONOCHROME2 ALWAYS AUTO
Interpretation
> Rows (0028,0010) US Number of rows in pixel data ALWAYS AUTO
> Columns (0028,0011) US Number of columns in pixel ALWAYS AUTO
data
> Pixel Aspect Ratio (0028,0034) IS 1\1 ALWAYS AUTO
> Bits Allocated (0028,0100) US 8 ALWAYS AUTO
> Bits Stored (0028,0101) US 8 ALWAYS AUTO
> High Bit (0028,0102) US 7 ALWAYS AUTO
> Pixel Representation (0028,0103) US 0 ALWAYS AUTO
> Pixel Data (7FE0,0010) OW The pixel data of the image to ALWAYS AUTO
be printed, complete with any
visible user annotations and
pre-rendered to an appropriate
resolution for printing

Page 46
Requested Image Size (2020,0030) DS The physical width of the ANAP AUTO
image if True Size printing was
requested; not present
otherwise
Requested (2020,0040) CS CROP if True Size printing ALWAYS AUTO
Decimate/Crop was requested; otherwise
Behavior DECIMATE.

4.2.9.3.1.3.4 SOP Specific Conformance to Basic Color Image Box SOP Class
PRINT-SCU provides standard conformance to the Basic Color Image Box SOP Class.

For each image box SOP instance contained in the film box N-CREATE response, PRINT-SCU will
update the image box by issuing an N-SET request with the attributes listed in Table 4.2-64.

Table 4.2-64
BASIC COLOR IMAGE BOX SOP CLASS N-SET ATTRIBUTE SUPPORT FOR PRINT-SCU

Attribute Name Tag VR Value Presence Source

of Value
Image Box Position (2020,0010) US An integer indicating the ALWAYS AUTO
sequencing of the image
boxes, with the first image box
having the value 1
Basic Color Image (2020,0111) SQ A single item containing the ALWAYS AUTO
Sequence color image box pixel data
> Samples Per Pixel (0028,0002) US 3 ALWAYS AUTO
> Photometric (0028,0004) CS RGB ALWAYS AUTO
Interpretation
> Planar Configuration (0028,0006) US 0
> Rows (0028,0010) US Number of rows in pixel data ALWAYS AUTO
> Columns (0028,0011) US Number of columns in pixel ALWAYS AUTO
data
> Pixel Aspect Ratio (0028,0034) IS 1\1 ALWAYS AUTO
> Bits Allocated (0028,0100) US 8 ALWAYS AUTO
> Bits Stored (0028,0101) US 8 ALWAYS AUTO
> High Bit (0028,0102) US 7 ALWAYS AUTO
> Pixel Representation (0028,0103) US 0 ALWAYS AUTO
> Pixel Data (7FE0,0010) OW The pixel data of the image to ALWAYS AUTO
be printed, complete with any
visible user annotations and
pre-rendered to an appropriate
resolution for printing
Requested Image Size (2020,0030) DS The physical width of the ANAP AUTO
image if True Size printing was
requested; not present
otherwise
Requested (2020,0040) CS CROP if True Size printing ALWAYS AUTO
Decimate/Crop was requested; otherwise
Behavior DECIMATE.

Page 47
4.2.9.3.1.3.5 SOP Specific Conformance to Printer SOP Class
PRINT-SCU provides standard conformance to the Printer SOP Class.

N-EVENT-REPORT requests received by PRINT-SCU from the SCP are accepted and confirmation of
receipt is always supplied via an N-EVENT-REPORT response with a success status. Additionally,
PRINT-SCU behaves as described in Table 4.2-65 upon receipt of the request.

Table 4.2-65
PRINTER N-EVENT-REPORT REQUEST BEHAVIOUR FOR PRINT-SCU AND PRINT IMAGES

Event Type Name Event Type ID Attribute Tag Behavior

Normal 1 Any Any Receipt logged (at debug level).
Warning 2 Any Any Receipt logged.
Failure 3 Any Any Receipt logged, association closed,
message shown to user.

4.2.9.3.1.3.6 Presentation Context Acceptance Criterion

PRINT-SCU does not accept associations.

4.2.9.3.1.3.7 Transfer Syntax Selection Policies

PRINT-SCU prefers Explicit VR Little Endian Transfer Syntax, which is always first in the proposed
Presentation Context.

4.2.9.3.1.3.8 Response Status

PRINT-SCU will behave as described in Table 4.2-66 in response to the status returned in any response
message other than Basic Film Session N-DELETE. See Table 4.2-59 for the response behavior to Basic
Film Session N-DELETE.

Table 4.2-66
RESPONSE STATUS FOR PRINT-SCU AND PRINT IMAGES

Service Further Meaning Status Behavior

Status Codes
Failure N/A Any Association closed, message shown
to user
Warning N/A Any Message logged
Success N/A 0000 Operation proceeds as described in
the appropriate SOP Specific
Conformance section(s).

4.2.9.4 Association Acceptance Policy

PRINT-SCU does not accept associations.

4.3 NETWORK INTERFACES

4.3.1 Physical Network Interface

The application is indifferent to the physical medium over which TCP/IP executes; which is dependent on
the underlying operating system and hardware.

Page 48
4.3.2 Additional Protocols
When host names rather than IP addresses are used in the configuration properties to specify
presentation addresses for remote AEs, the application is dependent on the name resolution mechanism
of the underlying operating system.

4.3.2.1 Web Access to DICOM Persistent Objects (WADO)

The application claims partial conformance to DICOM 2009 PS 3.18 “Web Access to DICOM Persistent
Objects (WADO)” in that the HTTP GET request sent to the remote server is compliant. The application
is non-conformant in that, although it does include the required MIME types in the Accept field of the
HTTP GET request, if the MIME type of the returned object is anything other than
”application/clearcanvas” (when retrieving pixel data), the behavior is undefined and the application will
be unable to render the image to the screen.

The following parameters are used in the HTTP GET Request sent to the remote server.

Table 4.3-1
PARAMETERS OF HTTP GET REQUEST

Parameter Value
requestType WADO
studyUID The Study Instance UID of the composite object
seriesUID The Series Instance UID of the composite object
objectUID The SOP Instance UID of the composite object
frameNumber Valid only when contentType is
application/clearcanvas; the frame within the
composite object instance to be returned
contentType application/clearcanvas (for pixel data)
– or –
application/clearcanvas-header (for PS 3.10 headers)
stopTag Valid only when contentType is
application/clearcanvas-header; indicates the
hexadecimal tag at which the remote AE should stop
parsing the PS 3.10 DICOM file before returning it.
Pixel Data (0x7FE0, 0010) is never returned
regardless of this value.

When a study is loaded from a ClearCanvas ImageServer, the viewer application uses a proprietary web
service to retrieve a gzip compressed XML stream containing the majority of the content of the DICOM
headers for the entire study, always excluding pixel data. This is referred to as the instance XML or study
XML.

The application/clearcanvas MIME type is a custom MIME type intended to speed the retrieval of DICOM
image data; it allows for per-frame pixel data to be retrieved, without any header information. The
application/clearcanvas-header MIME type is a custom MIME type used to retrieve the entire DICOM PS
3.10 header when the application has detected that some attributes have been excluded from the
instance XML.

The following describes the motivation for the proprietary web service and custom
application/clearcanvas MIME type(s) used by the application:

Page 49
 - DICOM queries (e.g. Hierarchical Study Root Query) at the IMAGE level are often poorly
supported, providing little information. Also, the time required to perform the queries for each
series down to the IMAGE level can be quite long, especially on slower networks.
- The Image Sets and Display Sets can be constructed from the XML headers without having to
retrieve any DICOM PS 3.10 files. The application has all required information about the images
before any have been displayed.
- Once a study is open in the viewer, the pixel data can be retrieved on demand for each image, or
for each frame in a multi-frame image, without having to request the entire DICOM PS 3.10 file at
once. This provides a significant time savings in the case of multi-frame images. Although PS
3.18 does allow for retrieval of individual frames, for obvious reasons, it must explicitly disallow
the application/dicom MIME type, leaving only low bit-depth image types, such as JPEG.
- This approach optimizes both the ‘time to first image’ (after initial study load) and the time taken
to load each image (or frame) the user selects.

The content of the HTTP GET response is always a byte array containing the image pixel data, normally
taken directly from the DICOM PS 3.10 file on the remote server. When the returned image data is
compressed, the response headers will contain enough information about the pixel data to allow it to be
decompressed. When the pixel data is not compressed, it is assumed the client has enough information
from the instance XML to handle the data appropriately.

When the pixel data in the response is compressed, the following information is contained in the response
headers.

Table 4.3-2
CONTENTS OF HTTP GET RESPONSE HEADERS
FOR COMPRESSED PIXEL DATA

Header Key Equivalent Tag

Compressed N/A (value = true)
TransferSyntaxUid (0002,0010)
BitsAllocated (0028,0100)
BitsStored (0028,0101)
DerivationDescription (0008,2111)
HighBit (0028,0102)
ImageHeight (0028,0010)
ImageWidth (0028,0011)
LossyImageCompression (0028,2110)
LossyImageCompressionMethod (0028,2114)
LossyImageCompressionRatio (0028,2112)
NumberOfFrames (0028,0008)
PhotometricInterpretation (0028,0004)
PixelRepresentation (0028,0103)
PlanarConfiguration (0028,0006)
SamplesPerPixel (0028,0002)

As stated previously, the instance XML will normally contain all the DICOM header information for each
SOP instance in the study. However, in the interest of saving space on the server, excessively long
values are excluded, but the fact that they have been excluded is stored in the XML. When an attribute

Page 50
has been excluded, the application will operate normally without that information until one of the excluded
attributes is required by the application. The attempt to access an excluded attribute is detected by the
application and the full header for the SOP instance will be silently retrieved. The parameters of the
HTTP GET request will be as described in Table 4.3-1 where contentType is “clearcanvas-header”. The
remote AE will then return the entire DICOM PS 3.10 compliant file, parsed up to the value of stopTag, if
it was provided. If stopTag is not specified, the file will be parsed up to, but not including, Pixel Data
(0x7FE, 00010). Regardless of the value of stopTag, the pixel data will never be returned.

4.3.3 IPv4 and IPv6 Support

By default, this product supports IPv4. When configured, it will also support IPv6. It does not utilize any
of the optional configuration identification or security features of IPv6.

4.4 NETWORK CONFIGURATION

All configuration of the application is performed through the use of configuration files stored in pre-defined
locations that are specific to the underlying operating system.

4.4.1 AE Title/Presentation Address Mapping

The Calling AE Title of the local application is configurable in the configuration file. The mapping of the
logical name by which remote AEs are described in the user interface to Called AE Titles as well as
presentation address (hostname or IP address and port number) is configurable in the configuration file.

4.4.2 Parameters
Table 4.4-1
CONFIGURATION PARAMETERS TABLE

Parameter Configurable Default Value

General Parameters
PDU size No N/A
Time-out waiting for acceptance or rejection Response Yes 1 hour
to an Association Open Request. (Application Level
timeout)
General DIMSE level time-out values No 30 seconds
Time-out waiting for response to TCP/IP connect() Yes 10 seconds
request. (Low-level timeout)
Time-out waiting for acceptance of a TCP/IP message Yes 30 seconds
over the network. (Low-level timeout)
Time-out for waiting for data between TCP/IP packets. Yes 30 seconds
(Low-level timeout)
Send Buffer Size (TCP/IP socket) Yes 118341 bytes
Receive Buffer Size (TCP/IP socket) Yes 118341 bytes
Any changes to default TCP/IP settings, such as No None
configurable stack parameters.
AE Specific Parameters (all AEs)
Size constraint in maximum object size No None
Maximum PDU size the AE can receive Yes 116794 bytes
Maximum PDU size the AE can send Yes 116794 bytes
AE specific DIMSE level time-out values No 30 seconds

Page 51
Number of simultaneous Associations by Service and/or N/A N/A
SOP Class
SOP Class support Yes All supported SOP
Classes
Transfer Syntax support Yes All supported
Transfer Syntaxes
Other parameters that are configurable No None

Page 52
 5 MEDIA INTERCHANGE

5.1 IMPLEMENTATION MODEL

5.1.1 Application Data Flow

Local User
Requests File
Load
MEDIA-FSR
Application Storage Medium
Entity
Local User Views
Images of Patient
with Prior Studies

Local User MEDIA-FSU

Creates Ancillary Application Storage Medium
Content Entity

MEDIA-FSC
Export to
Application Removable Storage
Removable Media
Entity Medium

Figure 5.1-1
IMPLEMENTATION MODEL
The application is a.NET application that provides a user interface, network support and media support as
a File Set Reader (FSR), a File Set Updater (FSU), and a File Set Creator (FSC).

Conceptually, the media services may be modeled as the following separate AEs, though in fact all the
AEs share the same single (configurable) AE Title as the network services:

- MEDIA-FSR, which loads a user-selected PS 3.10 compliant file (which may be an image, key
object selection, or softcopy presentation state) either from the local file system or from PS 3.12
compliant media according to one of the (non-secure) General Purpose Media Storage
Application Profiles of PS 3.11 (including CD-R and DVD). The application is effectively media-
neutral, as the user is required to browse and locate the files and directories manually.

Any DICOM image encoded in one of the following Transfer Syntaxes may be loaded:
- Explicit VR Little Endian
- Implicit VR Little Endian
- Explicit VR Big Endian
- RLE Lossless
- JPEG Baseline (Process 1)

Page 53
 - JPEG Extended (Process 2 & 4)
- JPEG Lossless, Non-Hierarchical (Process 14)
- JPEG Lossless, Non-Hierarchical, First-Order Prediction (Process 14 [Selection Value 1])
- JPEG 2000 Image Compression
- JPEG 2000 Image Compression (Lossless Only)

- MEDIA-FSU, which writes PS 3.10 compliant files containing user-created ancillary content such
as key object selections, secondary capture images, softcopy presentation states and
encapsulated PDF documents. The key object selection document may contain only image
entries, and the softcopy presentation states may be any of the following SOP classes:
- Grayscale Softcopy Presentation State Storage
- Color Softcopy Presentation State Storage

- MEDIA-FSC, which writes PS 3.10 compliant file sets containing user-selected images,
presentation states, and other instances to a removable storage medium. The following media
storage application profiles are supported:
- General Purpose CD-R Interchange (STD-GEN-CD)
- General Purpose Interchange on DVD-RAM Media (STD-GEN-DVD-RAM)
- General Purpose DVD Interchange with JPEG (STD-GEN-DVD-JPEG)
- General Purpose BD Interchange (STD-GEN-BD)

5.1.2 Functional Definitions of AE’s

5.1.2.1 MEDIA-FSR
MEDIA-FSR is typically activated through the user interface to select directories and images for display or
import into the internal database or to be opened for viewing. It can also be activated internally in
response to the user viewing images if the patient has prior studies that are available in the internal
database.

5.1.2.2 MEDIA-FSU
MEDIA-FSU is activated internally when a user creates ancillary content such as key object selections,
secondary capture images, softcopy presentation states, and encapsulated PDF documents. The exact
mechanism differs between functions (such as closing the viewer while there are pending items
designated as key images). Upon creation, all ancillary content SOP instances are added to the file-set.

5.1.2.3 MEDIA-FSC
MEDIA-FSC is activated through the user interface when the user selects one or more studies for export
to a removable storage medium. The application uses support built in to the operating system to create
the selected file set on the destination medium.

5.1.3 Sequencing of Real-World Activities

FSR activities are sequentially initiated when activated through the user interface, and another activity
may not be initiated until the prior activity has completed. When activated internally by a Load Prior
Studies operation, the activity is asynchronous and non-blocking.

All current FSU activities are activated internally by a Write User-Created Ancillary Content operation,
which is asynchronous and non-blocking.

The activities of MEDIA-FSC are activated through the user interface and are asynchronous and non-
blocking with respect to other application entities; only one export operation may be performed at a time.

5.1.4 File Meta Information Options

Table 5.1-1
DICOM IMPLEMENTATION CLASS AND VERSION FOR MEDIA STORAGE

Page 54
 Implementation Class UID 1.3.6.1.4.1.25403.1.1.1
Implementation Version Name Dicom 0.1

5.2 AE SPECIFICATIONS

5.2.1 MEDIA-FSR
MEDIA-FSR provides standard conformance to the Media Storage Service Class.

Table 5.2-1
APPLICATION PROFILES, ACTIVITIES, AND ROLES FOR MEDIA-FSR

Application Profiles Supported Real World Activity Role

STD-GEN-CD Load Directory or File FSR
STD-GEN-DVD-RAM Load Directory or File FSR
STD-GEN-DVD-JPEG Load Directory or File FSR
STD-GEN-BD Load Directory or File FSR

Note: The application is media neutral and dependent on the underlying hardware. Any (non-secure)
General Purpose Profile can be supported.
There is no explicit support for reading DICOMDIR files. A file set is simply treated as a collection of files
and the hierarchical relationships of the instances automatically inferred from the data sets.

5.2.1.1 File Meta Information for the Application Entity

Not applicable, since MEDIA-FSR is not an FSC or FSU.

5.2.1.2 Real World Activities

5.2.1.2.1 Activity – Load Directory or File

MEDIA-FSR can be activated through the user interface when a user selects the file import or open
operation. Images will be imported into the internal database or loaded and displayed, respectively.

5.2.1.2.1.1 Application Profile Specific Conformance

There are no extensions or specializations.

5.2.1.2.2 Activity – Load Prior Studies

MEDIA-FSR can be activated internally in response to the user viewing images in order to identify and list
studies related to the current patient. The user can navigate to these prior studies in the same viewer
context as the originally selected images.

5.2.1.2.2.1 Application Profile Specific Conformance

There are no extensions or specializations.

5.2.2 MEDIA-FSU

5.2.2.1 File Meta Information for the Application Entity

The Source Application Entity Title included in the File Meta Header is configurable (see Section 5.4).

5.2.2.2 Real World Activities

5.2.2.2.1 Activity – Write User-Created Ancillary Content

MEDIA-FSU is currently only activated internally in response to the user creating ancillary content. The
exact mechanism differs between functions (such as closing the viewer while there are pending items

Page 55
designated as key images). When this occurs, the necessary SOP instances are created and added to
the file-set.

5.2.2.2.1.1 Application Profile Specific Conformance

There are no extensions or specializations.

5.2.3 MEDIA-FSC
MEDIA-FSC provides standard conformance to the Media Storage Service Class.

Table 5.2-2
APPLICATION PROFILES, ACTIVITIES, AND ROLES FOR MEDIA-FSC

Application Profiles Supported Real World Activity Role

STD-GEN-CD Export to removable media FSC
STD-GEN-DVD-RAM Export to removable media FSC
STD-GEN-DVD-JPEG Export to removable media FSC
STD-GEN-BD Export to removable media FSC

Note: Support for STD-GEN-BD is based on the final text of DICOM Supplement 153.

5.2.3.1 File Meta Information for the Application Entity

The Source Application Entity Title included in the File Meta Header is configurable (see Section 5.4).

5.2.3.2 Real World Activities

5.2.3.2.1 Activity – Export to Removable Media

MEDIA-FSC acts as an FSC when requested to export SOP Instances from the internal database to a
removable storage medium such as a CD-R or DVD. The application is dependent on the system
hardware as well as support from the operating system. Consequently, the system must possess
hardware capable of writing to one or more of the supported media types in Table 5.2-3 in order to use
the MEDIA-FSC application entity.

Table 5.2-3
SUPPORTED MEDIA TYPES FOR MEDIA-FSC

Media Supported Reference

CD-R DICOM 2009 PS 3.12 Annex F
DVD-RAM DICOM 2009 PS 3.12 Annex J
DVD-R (authoring and general), DICOM 2009 PS 3.12 Annex P
DVD-RW, DVD+R, DVD+RW
BD-R, BD-RE DICOM Supplement 153

An interface will be presented allowing the user to modify media creation options such as including a
portable viewer application and modifying the media volume label. The interface also provides details on
the available media capacity, allowing the user to adjust the contents as may be deemed necessary.

The user will be prompted to insert suitable media into the selected media creation device. The entire
contents of the export job, including the corresponding DICOMDIR and any additional options such as an
included portable viewer application, will be written together in one single operation. The user can cancel
an export job during the procedure. Only one export job may be performed at a time.

Page 56
Where applicable (optical media such as CD-R, DVD-RAM, DVD and BD):

 Only single session discs will be created.

 Writing in multi-session mode is not supported. In general, inserted media must be completely
blank in order to be used, and there is no option to erase it before export; it must first be erased
using an external application.
 Cancelling an export job to one of these media types may result in unusable media.

5.2.3.2.1.1 Application Profile Specific Conformance

MEDIA-FSC supports the SOP Classes and Transfer Syntaxes listed in the Table below:

Table 5.2-4
IODS, SOP CLASSES AND TRANSFER SYNTAXES FOR MEDIA-FSC

Information Object Transfer Syntax

SOP Class UID Transfer Syntax
Definition UID
12-lead ECG Waveform Explicit VR Little
1.2.840.10008.5.1.4.1.1.9.1.1 1.2.840.10008.1.2.1
Storage Endian
Ambulatory ECG Explicit VR Little
1.2.840.10008.5.1.4.1.1.9.1.3 1.2.840.10008.1.2.1
Waveform Storage Endian
Explicit VR Little
Basic Text SR Storage 1.2.840.10008.5.1.4.1.1.88.11 1.2.840.10008.1.2.1
Endian
Basic Voice Audio Explicit VR Little
1.2.840.10008.5.1.4.1.1.9.4.1 1.2.840.10008.1.2.1
Waveform Storage Endian
Blending Softcopy
Explicit VR Little
Presentation State 1.2.840.10008.5.1.4.1.1.11.4 1.2.840.10008.1.2.1
Endian
Storage
Breast Tomosynthesis Explicit VR Little
1.2.840.10008.5.1.4.1.1.13.1.3 1.2.840.10008.1.2.1
Image Storage Endian
Cardiac Electrophysiology Explicit VR Little
1.2.840.10008.5.1.4.1.1.9.3.1 1.2.840.10008.1.2.1
Waveform Storage Endian
Explicit VR Little
Chest CAD SR Storage 1.2.840.10008.5.1.4.1.1.88.65 1.2.840.10008.1.2.1
Endian
Explicit VR Little
Colon CAD SR Storage 1.2.840.10008.5.1.4.1.1.88.69 1.2.840.10008.1.2.1
Endian
Color Softcopy
Explicit VR Little
Presentation State 1.2.840.10008.5.1.4.1.1.11.2 1.2.840.10008.1.2.1
Endian
Storage
Comprehensive SR Explicit VR Little
1.2.840.10008.5.1.4.1.1.88.33 1.2.840.10008.1.2.1
Storage Endian
Computed Radiography Explicit VR Little
1.2.840.10008.5.1.4.1.1.1 1.2.840.10008.1.2.1
Image Storage Endian
Explicit VR Little
CT Image Storage 1.2.840.10008.5.1.4.1.1.2 1.2.840.10008.1.2.1
Endian
Deformable Spatial Explicit VR Little
1.2.840.10008.5.1.4.1.1.66.3 1.2.840.10008.1.2.1
Registration Storage Endian
Digital Intra-oral X-Ray
Explicit VR Little
Image Storage – For 1.2.840.10008.5.1.4.1.1.1.3 1.2.840.10008.1.2.1
Endian
Presentation

Page 57
Digital Intra-oral X-Ray
Explicit VR Little
Image Storage – For 1.2.840.10008.5.1.4.1.1.1.3.1 1.2.840.10008.1.2.1
Endian
Processing
Digital Mammography X-
Explicit VR Little
Ray Image Storage – For 1.2.840.10008.5.1.4.1.1.1.2 1.2.840.10008.1.2.1
Endian
Presentation
Digital Mammography X-
Explicit VR Little
Ray Image Storage – For 1.2.840.10008.5.1.4.1.1.1.2.1 1.2.840.10008.1.2.1
Endian
Processing
Digital X-Ray Image
Explicit VR Little
Storage – For 1.2.840.10008.5.1.4.1.1.1.1 1.2.840.10008.1.2.1
Endian
Presentation
Digital X-Ray Image Explicit VR Little
1.2.840.10008.5.1.4.1.1.1.1.1 1.2.840.10008.1.2.1
Storage – For Processing Endian
Encapsulated CDA Explicit VR Little
1.2.840.10008.5.1.4.1.1.104.2 1.2.840.10008.1.2.1
Storage Endian
Encapsulated PDF Explicit VR Little
1.2.840.10008.5.1.4.1.1.104.1 1.2.840.10008.1.2.1
Storage Endian
Enhanced CT Image Explicit VR Little
1.2.840.10008.5.1.4.1.1.2.1 1.2.840.10008.1.2.1
Storage Endian
Enhanced MR Image Explicit VR Little
1.2.840.10008.5.1.4.1.1.4.1 1.2.840.10008.1.2.1
Storage Endian
Enhanced PET Image Explicit VR Little
1.2.840.10008.5.1.4.1.1.130 1.2.840.10008.1.2.1
Storage Endian
Explicit VR Little
Enhanced SR Storage 1.2.840.10008.5.1.4.1.1.88.22 1.2.840.10008.1.2.1
Endian
Enhanced US Image Explicit VR Little
1.2.840.10008.5.1.4.1.1.6.2 1.2.840.10008.1.2.1
Storage Endian
Enhanced XA Image Explicit VR Little
1.2.840.10008.5.1.4.1.1.12.1.1 1.2.840.10008.1.2.1
Storage Endian
Enhanced XRF Image Explicit VR Little
1.2.840.10008.5.1.4.1.1.12.2.1 1.2.840.10008.1.2.1
Storage Endian
General ECG Waveform Explicit VR Little
1.2.840.10008.5.1.4.1.1.9.1.2 1.2.840.10008.1.2.1
Storage Endian
Grayscale Softcopy
Explicit VR Little
Presentation State 1.2.840.10008.5.1.4.1.1.11.1 1.2.840.10008.1.2.1
Endian
Storage
Hemodynamic Waveform Explicit VR Little
1.2.840.10008.5.1.4.1.1.9.2.1 1.2.840.10008.1.2.1
Storage Endian
Key Object Selection Explicit VR Little
1.2.840.10008.5.1.4.1.1.88.59 1.2.840.10008.1.2.1
Document Storage Endian
Macular Grid Thickness
Explicit VR Little
and Volume Report 1.2.840.10008.5.1.4.1.1.79.1 1.2.840.10008.1.2.1
Endian
Storage
Mammography CAD SR Explicit VR Little
1.2.840.10008.5.1.4.1.1.88.50 1.2.840.10008.1.2.1
Storage Endian

Page 58
Media Storage Directory Explicit VR Little
1.2.840.10008.1.3.10 1.2.840.10008.1.2.1
Storage Endian
Explicit VR Little
MR Image Storage 1.2.840.10008.5.1.4.1.1.4 1.2.840.10008.1.2.1
Endian
Explicit VR Little
MR Spectroscopy Storage 1.2.840.10008.5.1.4.1.1.4.2 1.2.840.10008.1.2.1
Endian
Multi-frame Grayscale
Explicit VR Little
Byte Secondary Capture 1.2.840.10008.5.1.4.1.1.7.2 1.2.840.10008.1.2.1
Endian
Image Storage
Multi-frame Grayscale
Explicit VR Little
Word Secondary Capture 1.2.840.10008.5.1.4.1.1.7.3 1.2.840.10008.1.2.1
Endian
Image Storage
Multi-frame Single Bit
Explicit VR Little
Secondary Capture Image 1.2.840.10008.5.1.4.1.1.7.1 1.2.840.10008.1.2.1
Endian
Storage
Multi-frame True Color
Explicit VR Little
Secondary Capture Image 1.2.840.10008.5.1.4.1.1.7.4 1.2.840.10008.1.2.1
Endian
Storage
Nuclear Medicine Image Explicit VR Little
1.2.840.10008.5.1.4.1.1.5 1.2.840.10008.1.2.1
Storage (Retired) Endian
Nuclear Medicine Image Explicit VR Little
1.2.840.10008.5.1.4.1.1.20 1.2.840.10008.1.2.1
Storage Endian
Ophthalmic Photography Explicit VR Little
1.2.840.10008.5.1.4.1.1.77.1.5.2 1.2.840.10008.1.2.1
16 Bit Image Storage Endian
Ophthalmic Photography 8 Explicit VR Little
1.2.840.10008.5.1.4.1.1.77.1.5.1 1.2.840.10008.1.2.1
Bit Image Storage Endian
Ophthalmic Tomography Explicit VR Little
1.2.840.10008.5.1.4.1.1.77.1.5.4 1.2.840.10008.1.2.1
Image Storage Endian
Positron Emission
Explicit VR Little
Tomography Image 1.2.840.10008.5.1.4.1.1.128 1.2.840.10008.1.2.1
Endian
Storage
Explicit VR Little
Procedure Log Storage 1.2.840.10008.5.1.4.1.1.88.40 1.2.840.10008.1.2.1
Endian
Pseudo-Color Softcopy
Explicit VR Little
Presentation State 1.2.840.10008.5.1.4.1.1.11.3 1.2.840.10008.1.2.1
Endian
Storage
Explicit VR Little
Raw Data Storage 1.2.840.10008.5.1.4.1.1.66 1.2.840.10008.1.2.1
Endian
Real World Value Mapping Explicit VR Little
1.2.840.10008.5.1.4.1.1.67 1.2.840.10008.1.2.1
Storage Endian
RT Beams Treatment Explicit VR Little
1.2.840.10008.5.1.4.1.1.481.4 1.2.840.10008.1.2.1
Record Storage Endian
RT Brachy Treatment Explicit VR Little
1.2.840.10008.5.1.4.1.1.481.6 1.2.840.10008.1.2.1
Record Storage Endian
Explicit VR Little
RT Dose Storage 1.2.840.10008.5.1.4.1.1.481.2 1.2.840.10008.1.2.1
Endian

Page 59
 Explicit VR Little
RT Image Storage 1.2.840.10008.5.1.4.1.1.481.1 1.2.840.10008.1.2.1
Endian
RT Ion Beams Treatment Explicit VR Little
1.2.840.10008.5.1.4.1.1.481.9 1.2.840.10008.1.2.1
Record Storage Endian
Explicit VR Little
RT Ion Plan Storage 1.2.840.10008.5.1.4.1.1.481.8 1.2.840.10008.1.2.1
Endian
Explicit VR Little
RT Plan Storage 1.2.840.10008.5.1.4.1.1.481.5 1.2.840.10008.1.2.1
Endian
Explicit VR Little
RT Structure Set Storage 1.2.840.10008.5.1.4.1.1.481.3 1.2.840.10008.1.2.1
Endian
RT Treatment Summary Explicit VR Little
1.2.840.10008.5.1.4.1.1.481.7 1.2.840.10008.1.2.1
Record Storage Endian
Secondary Capture Image Explicit VR Little
1.2.840.10008.5.1.4.1.1.7 1.2.840.10008.1.2.1
Storage Endian
Explicit VR Little
Segmentation Storage 1.2.840.10008.5.1.4.1.1.66.4 1.2.840.10008.1.2.1
Endian
Explicit VR Little
Spatial Fiducials Storage 1.2.840.10008.5.1.4.1.1.66.2 1.2.840.10008.1.2.1
Endian
Spatial Registration Explicit VR Little
1.2.840.10008.5.1.4.1.1.66.1 1.2.840.10008.1.2.1
Storage Endian
Spectacle Prescription Explicit VR Little
1.2.840.10008.5.1.4.1.1.78.6 1.2.840.10008.1.2.1
Reports Storage Endian
Standalone Curve Storage Explicit VR Little
1.2.840.10008.5.1.4.1.1.9 1.2.840.10008.1.2.1
(Retired) Endian
Standalone Modality LUT Explicit VR Little
1.2.840.10008.5.1.4.1.1.10 1.2.840.10008.1.2.1
Storage (Retired) Endian
Standalone Overlay Explicit VR Little
1.2.840.10008.5.1.4.1.1.8 1.2.840.10008.1.2.1
Storage (Retired) Endian
Standalone PET Curve Explicit VR Little
1.2.840.10008.5.1.4.1.1.129 1.2.840.10008.1.2.1
Storage (Retired) Endian
Standalone VOI LUT Explicit VR Little
1.2.840.10008.5.1.4.1.1.11 1.2.840.10008.1.2.1
Storage (Retired) Endian
Stereometric Relationship Explicit VR Little
1.2.840.10008.5.1.4.1.1.77.1.5.3 1.2.840.10008.1.2.1
Storage Endian
Stored Print Storage Explicit VR Little
1.2.840.10008.5.1.1.27 1.2.840.10008.1.2.1
(Retired) Endian
Explicit VR Little
Ultrasound Image Storage 1.2.840.10008.5.1.4.1.1.6.1 1.2.840.10008.1.2.1
Endian
Ultrasound Image Storage Explicit VR Little
1.2.840.10008.5.1.4.1.1.6 1.2.840.10008.1.2.1
(Retired) Endian
Ultrasound Multi-frame Explicit VR Little
1.2.840.10008.5.1.4.1.1.3.1 1.2.840.10008.1.2.1
Image Storage Endian
Ultrasound Multi-frame Explicit VR Little
1.2.840.10008.5.1.4.1.1.3 1.2.840.10008.1.2.1
Image Storage (Retired) Endian
Video Endoscopic Image Explicit VR Little
1.2.840.10008.5.1.4.1.1.77.1.1.1 1.2.840.10008.1.2.1
Storage Endian

Page 60
Video Microscopic Image Explicit VR Little
1.2.840.10008.5.1.4.1.1.77.1.2.1 1.2.840.10008.1.2.1
Storage Endian
Video Photographic Image Explicit VR Little
1.2.840.10008.5.1.4.1.1.77.1.4.1 1.2.840.10008.1.2.1
Storage Endian
VL Endoscopic Image Explicit VR Little
1.2.840.10008.5.1.4.1.1.77.1.1 1.2.840.10008.1.2.1
Storage Endian
VL Microscopic Image Explicit VR Little
1.2.840.10008.5.1.4.1.1.77.1.2 1.2.840.10008.1.2.1
Storage Endian
VL Photographic Image Explicit VR Little
1.2.840.10008.5.1.4.1.1.77.1.4 1.2.840.10008.1.2.1
Storage Endian
VL Slide-Coordinates
Explicit VR Little
Microscopic Image 1.2.840.10008.5.1.4.1.1.77.1.3 1.2.840.10008.1.2.1
Endian
Storage
X-Ray 3D Angiographic Explicit VR Little
1.2.840.10008.5.1.4.1.1.13.1.1 1.2.840.10008.1.2.1
Image Storage Endian
X-Ray 3D Craniofacial Explicit VR Little
1.2.840.10008.5.1.4.1.1.13.1.2 1.2.840.10008.1.2.1
Image Storage Endian
X-Ray Angiographic Bi-
Explicit VR Little
Plane Image Storage 1.2.840.10008.5.1.4.1.1.12.3 1.2.840.10008.1.2.1
Endian
(Retired)
X-Ray Angiographic Image Explicit VR Little
1.2.840.10008.5.1.4.1.1.12.1 1.2.840.10008.1.2.1
Storage Endian
X-Ray Radiation Dose SR Explicit VR Little
1.2.840.10008.5.1.4.1.1.88.67 1.2.840.10008.1.2.1
Storage Endian
X-Ray Radiofluoroscopic Explicit VR Little
1.2.840.10008.5.1.4.1.1.12.2 1.2.840.10008.1.2.1
Image Storage Endian

5.2.3.2.1.1.1 Application Profile Specific Conformance to General Purpose CD-R Interchange

MEDIA-FSC provides standard conformance to the General Purpose CD-R Interchange Media Storage
Application Profile.

The supported SOP Classes and Transfer Syntaxes are listed in Table 5.2-4.

5.2.3.2.1.1.2 Application Profile Specific Conformance to General Purpose Interchange on DVD-

RAM Media
MEDIA-FSC provides standard conformance to the General Purpose Interchange on DVD-RAM Media
Storage Application Profile.

The supported SOP Classes and Transfer Syntaxes are listed in Table 5.2-4.

5.2.3.2.1.1.3 Application Profile Specific Conformance to General Purpose DVD Interchange

with JPEG
MEDIA-FSC provides standard conformance to the General Purpose DVD Interchange with JPEG Media
Storage Application Profile.

Due to a technical limitation, all images are stored uncompressed for the purposes of this Media Storage
Application Profile.

The supported SOP Classes and Transfer Syntaxes are listed in Table 5.2-4.

Page 61
5.2.3.2.1.1.4 Application Profile Specific Conformance to General Purpose BD Interchange
MEDIA-FSC provides standard conformance to the General Purpose BD Interchange Media Storage
Application Profile.

Due to a technical limitation of the operating system support for removable media creation, MEDIA-FSC
uses a UDF 2.5 file system on BD-R media instead of the UDF 2.6 prescribed in DICOM Supplement 153.

The supported SOP Classes and Transfer Syntaxes are listed in Table 5.2-4.

5.3 AUGMENTED AND PRIVATE PROFILES

5.3.1 Augmented Profiles

No augmented profiles are used.

5.3.2 Private Profiles

No private profiles are used.

5.4 MEDIA CONFIGURATION

The media services share the same single configurable AE Title as that of the network services (see
Section 4.4.1).

Page 62
 6 SUPPORT OF CHARACTER SETS

6.1 OVERVIEW
The application supports all extended character sets defined in the DICOM 2009 standard, including
single-byte and multi-byte character sets as well as code extension techniques using ISO 2022 escapes.

Support extends to correctly decoding and displaying the correct symbol for all names and strings found
in storage instances from media and received over the network, and in the internal database.

No specific support for sorting of strings other than in the default character set is provided in the
browsers.

6.2 CHARACTER SETS

In addition to the default character repertoire, the Defined Terms for Specific Character Set in Table 6.2-1
are supported:

Table 6.2-1
SUPPORTED SPECIFIC CHARACTER SET DEFINED TERMS

Character Set Description Defined Term

Latin alphabet No. 1 ISO_IR 100
Latin alphabet No. 2 ISO_IR 101
Latin alphabet No. 3 ISO_IR 109
Latin alphabet No. 4 ISO_IR 110
Cyrillic ISO_IR 144
Arabic ISO_IR 127
Greek ISO_IR 126
Hebrew ISO_IR 138
Latin alphabet No. 5 ISO_IR 148
Japanese ISO_IR 13
Thai ISO_IR 166
Unicode in UTF-8 ISO_IR 192
Default repertoire ISO 2022 IR 6
Latin alphabet No. 1 ISO 2022 IR 100
Latin alphabet No. 2 ISO 2022 IR 101
Latin alphabet No. 3 ISO 2022 IR 109
Latin alphabet No. 4 ISO 2022 IR 110
Cyrillic ISO 2022 IR 144
Arabic ISO 2022 IR 127
Greek ISO 2022 IR 126
Hebrew ISO 2022 IR 138
Latin alphabet No. 5 ISO 2022 IR 148
Thai ISO 2022 IR 166

Page 63
 Japanese ISO 2022 IR 13
Japanese ISO 2022 IR 87
Japanese ISO 2022 IR 159
Korean ISO 2022 IR 149
Chinese (Simplified) Extended GB18030

6.3 CHARACTER SET CONFIGURATION

Whether or not characters are displayed correctly depends on the presence of font support in the
underlying operating system. Typically, it may be necessary for the user to add one of the “all Unicode”
fonts to their system configuration in order to correctly display characters that would not typically be used
in the default locale.

Page 64
 7 SECURITY

7.1 SECURITY PROFILES

7.1.1 Basic Application Level Confidentiality Profile

The application provides partial conformance to the Basic Application Level Confidentiality Profile for de-
identification only. The following describes the application’s de-identification conformance:

- Removes, re-maps, nulls (makes empty), or adjusts required attributes as specified in DICOM
2011 PS 3.15 Table E.1-1 (Basic Application Level Confidentiality Profile Attributes) with the
following notable exceptions:
- Content Sequence (0040,A730) is retained
- Graphic Annotation Sequence (0070,0001) is retained
- Overlay Data (60xx,3000) is retained
- Referenced Image Sequence (0008,1140) is retained (nested UIDs are re-mapped)
- Referenced Study Sequence (0008,1110) is retained (nested UIDs are re-mapped)
- Source Image Sequence (0008,2112) is retained (nested UIDs are re-mapped)
- Adjusts some additional tags of the DA (Date) and DT (Date/Time) VRs, particularly those that
relate to the study date, content date, treatment date, and hardware calibration date. The
adjustment is based on the change in the value of the Study Date (0008,0020) attribute.
- Optionally allows retaining ALL private tags, not only the ones which are considered to be ‘safe’.
- Does NOT put original or modified attributes into the Encrypted Attributes Sequence.
- Does NOT obscure information burned into the pixel data that may identify the patient, or modify
the pixel data in any way. This is of particular importance for ultrasound, as many images have
the patient’s information burned into the pixel data and, therefore, the application will not be able
to completely de-identify the image(s).
- Does NOT obscure information in formatted documents embedded in the data set. This is of
particular importance for ancillary content such as Encapsulated PDFs, whose PDF content may
contain non-structured references to patient information and, therefore, the application will not be
able to completely de-identify the documents.
- Does NOT add or modify the Patient Identity Removed (0012,0062) attribute. Since the
application does not currently support obscuring potential patient information burned directly into
the pixel data, it is impossible to determine whether or not the image has been de-identified.
- The actions are applied recursively to nested data sets (items in sequence attributes).

The following table describes the attributes modified during de-identification:

Table 7.1-1
ATTRIBUTES MODIFIED DURING DE-IDENTIFICATION

Attribute Tag Action

Accession Number (0008,0050) Z,S
Acquisition Comments (0018,4000) X
Acquisition Context Sequence (0040,0555) X
Acquisition Date (0008,0022) D
Acquisition DateTime (0008,002A) D
Acquisition Device Processing Description (0018,1400) Z
Acquisition Protocol Description (0018,9424) X
Acquisition Time (0008,0032) D
Actual Human Performers Sequence (0040,4035) X

Page 65
Additional Patient History (0010,21B0) X
Admission ID (0038,0010) X
Admitting Date (0038,0020) X
Admitting Diagnoses Code Sequence (0008,1084) X
Admitting Diagnoses Description (0008,1080) X
Admitting Time (0038,0021) X
Affected SOP Instance UID (0000,1000) X
Allergies (0010,2110) X
Approval Status DateTime (0044,0004) D
Arbitrary (4000,0010) X
Attribute Modification DateTime (0400,0562) D
Author Observer Sequence (0040,A078) X
Branch of Service (0010,1081) X
Calibration Date (0014,407E) D
Calibration Time (0014,407C) D
Cassette ID (0018,1007) X
Comments on the Performed Procedure Step (0040,0280) X
Concatenation UID (0020,9161) U
Confidentiality Constraint on Patient Data Description (0040,3001) X
Content Creator's Identification Code Sequence (0070,0086) X
Content Creator's Name (0070,0084) Z
Content Date (0008,0023) D
Content Time (0008,0033) D
Context Group Extension Creator UID (0008,010D) U
Contrast/Bolus Agent (0018,0010) Z
Contribution Date Time (0018,A002) D
Contribution Description (0018,A003) X
Country of Residence (0010,2150) X
Creation Date (2100,0040) D
Creation Time (2100,0050) D
Creator-Version UID (0008,9123) U
Current Patient Location (0038,0300) X
Curve Data (5000,3000) X
Curve Date (0008,0025) X
Curve Time (0008,0035) X
Custodial Organization Sequence (0040,A07C) X
Data Set Trailing Padding (FFFC,FFFC) X
Date (0040,A121) D
Date of Document or Verbal Transaction (Trial) (0040,A110) D
Date of Gain Calibration (0014,3076) D

Page 66
Date of Last Calibration (0018,1200) D
Date of Last Detector Calibration (0018,700C) D
Date of Secondary Capture (0018,1012) D
DateTime (0040,A120) D
Decay Correction DateTime (0018,9701) D
Derivation Description (0008,2111) X
Detector ID (0018,700A) X
Device Serial Number (0018,1000) Z
Device UID (0018,1002) U
Digital Signature DateTime (0400,0105) D
Digital Signature UID (0400,0100) X
Digital Signatures Sequence (FFFA,FFFA) X
Dimension Organization UID (0020,9164) U
Discharge Date (0038,0030) D
Discharge Diagnosis Description (0038,0040) X
Discharge Time (0038,0032) D
Distribution Address (4008,011A) X
Distribution Name (4008,0119) X
Dose Reference UID (300A,0013) U
Effective DateTime (0068,6226) D
End Acquisition DateTime (0018,9517) D
Ethnic Group (0010,2160) X
Exclusion Start Datetime (0018,9804) D
Expected Completion Date Time (0040,4011) D
Expiry Date (0014,1020) D
Failed SOP Instance UID List (0008,0058) U
Fiducial UID (0070,031A) U
Filler Order Number / Imaging Service Request (0040,2017) Z
Findings Group Recording Date (Trial) (0040,A023) D
Findings Group Recording Time (Trial) (0040,A024) D
First Treatment Date (3008,0054) D
Frame Acquisition DateTime (0018,9074) D
Frame Comments (0020,9158) X
Frame of Reference UID (0020,0052) U
Frame Reference DateTime (0018,9151) D
Gantry ID (0018,1008) X
Generator ID (0018,1005) X
Hanging Protocol Creation DateTime (0072,000A) D
Human Performer's Name (0040,4037) X
Human Performer's Organization (0040,4036) X

Page 67
Icon Image Sequence (0088,0200) X
Identifying Comments (0008,4000) X
Image Comments (0020,4000) X
Image Presentation Comments (0028,4000) X
Imaging Service Request Comments (0040,2400) X
Impressions (4008,0300) X
Information Issue DateTime (0068,6270) D
Instance Creation Date (0008,0012) D
Instance Creation Time (0008,0013) D
Instance Creator UID (0008,0014) U
Institution Address (0008,0081) X
Institution Code Sequence (0008,0082) Z
Institution Name (0008,0080) Z
Institutional Department Name (0008,1040) X
Insurance Plan Identification (0010,1050) X
Intended Recipients of Results Identification Sequence (0040,1011) X
Interpretation Approval Date (4008,0112) D
Interpretation Approval Time (4008,0113) D
Interpretation Approver Sequence (4008,0111) X
Interpretation Author (4008,010C) X
Interpretation Diagnosis Description (4008,0115) X
Interpretation ID Issuer (4008,0202) X
Interpretation Recorded Date (4008,0100) D
Interpretation Recorded Time (4008,0101) D
Interpretation Recorder (4008,0102) X
Interpretation Text (4008,010B) X
Interpretation Transcriber (4008,010A) X
Interpretation Transcription Date (4008,0108) D
Interpretation Transcription Time (4008,0109) D
Irradiation Event UID (0008,3010) U
Issue Date of Imaging Service Request (0040,2004) D
Issue Time of Imaging Service Request (0040,2005) D
Issuer of Admission ID (0038,0011) X
Issuer of Patient ID (0010,0021) X
Issuer of Service Episode ID (0038,0061) X
Large Palette Color Lookup Table UID (0028,1214) U
Last Menstrual Date (0010,21D0) X
MAC (0400,0404) X
Media Storage SOP Instance UID (0002,0003) U
Medical Alerts (0010,2000) X

Page 68
Medical Record Locator (0010,1090) X
Military Rank (0010,1080) X
Modified Attributes Sequence (0400,0550) X
Modified Image Date (0020,3403) D
Modified Image Description (0020,3406) X
Modified Image Time (0020,3405) D
Modifying Device ID (0020,3401) X
Modifying Device Manufacturer (0020,3404) X
Most Recent Treatment Date (3008,0056) D
Name of Physician(s) Reading Study (0008,1060) X
Names of Intended Recipients of Results (0040,1010) X
Observation Date (Trial) (0040,A192) D
Observation Date Time (0040,A032) D
Observation Time (Trial) (0040,A193) D
Occupation (0010,2180) X
Operator Identification Sequence (0008,1072) Z
Operators' Name (0008,1070) Z
Order Callback Phone Number (0040,2010) X
Order Entered By (0040,2008) X
Order Enterer's Location (0040,2009) X
Original Attributes Sequence (0400,0561) X
Other Patient IDs (0010,1000) X
Other Patient IDs Sequence (0010,1002) X
Other Patient Names (0010,1001) X
Overlay Comments (6000,4000) X
Overlay Date (0008,0024) X
Overlay Time (0008,0034) X
Palette Color Lookup Table UID (0028,1199) U
Participant Sequence (0040,A07A) X
Participation DateTime (0040,A082) D
Patient Comments (0010,4000) X
Patient ID (0010,0020) Z,S
Patient State (0038,0500) X
Patient Transport Arrangements (0040,1004) X
Patient's Address (0010,1040) X
Patient's Age (0010,1010) X
Patient's Birth Date (0010,0030) Z,S
Patient's Birth Name (0010,1005) X
Patient's Birth Time (0010,0032) X
Patient's Institution Residence (0038,0400) X

Page 69
Patient's Insurance Plan Code Sequence (0010,0050) X
Patient's Mother's Birth Name (0010,1060) X
Patient's Name (0010,0010) Z,S
Patient's Primary Language Code Sequence (0010,0101) X
Patient's Primary Language Modifier Code Sequence (0010,0102) X
Patient's Religious Preference (0010,21F0) X
Patient's Sex (0010,0040) Z
Patient's Sex Neutered (0010,2203) Z
Patient's Size (0010,1020) X
Patient's Telephone Numbers (0010,2154) X
Patient's Weight (0010,1030) X
Performed Location (0040,0243) X
Performed Procedure Step Description (0040,0254) X
Performed Procedure Step ID (0040,0253) X
Performed Procedure Step Start Date (0040,0244) X
Performed Procedure Step Start Time (0040,0245) X
Performed Station AE Title (0040,0241) X
Performed Station Geographic Location Code Sequence (0040,4030) X
Performed Station Name (0040,0242) X
Performed Station Name Code Sequence (0040,4028) X
Performing Physician Identification Sequence (0008,1052) X
Performing Physician's Name (0008,1050) X
Person Identification Code Sequence (0040,1101) Z
Person Name (0040,A123) Z
Person's Address (0040,1102) X
Person's Telephone Numbers (0040,1103) X
Physician Approving Interpretation (4008,0114) X
Physician(s) of Record (0008,1048) X
Physician(s) of Record Identification Sequence (0008,1049) X
Physician(s) Reading Study Identification Sequence (0008,1062) X
Placer Order Number / Imaging Service Request (0040,2016) Z
Plate ID (0018,1004) X
Pregnancy Status (0010,21C0) X
Pre-Medication (0040,0012) X
Presentation Creation Date (0070,0082) D
Presentation Creation Time (0070,0083) D
Procedure Expiration Date (0014,4078) D
Procedure Last Modified Date (0014,407A) D
Procedure Step Cancellation DateTime (0040,4052) D
Product Expiration DateTime (0044,000B) D

Page 70
Protocol Name (0018,1030) Z
Radiopharmaceutical Start DateTime (0018,1078) D
Radiopharmaceutical Stop DateTime (0018,1079) D
Reason for Study (0032,1030) X
Reason for the Imaging Service Request (0040,2001) X
Referenced DateTime (0040,A13A) D
Referenced Digital Signature Sequence (0400,0402) X
Referenced Frame of Reference UID (3006,0024) U
Referenced General Purpose Scheduled Procedure Step (0040,4023) U
Transaction UID
Referenced Patient Alias Sequence (0038,0004) X
Referenced Patient Sequence (0008,1120) X
Referenced Performed Procedure Step Sequence (0008,1111) Z
Referenced SOP Instance MAC Sequence (0400,0403) X
Referenced SOP Instance UID (0008,1155) U
Referenced SOP Instance UID in File (0004,1511) U
Referring Physician Identification Sequence (0008,0096) X
Referring Physician's Address (0008,0092) X
Referring Physician's Name (0008,0090) Z
Referring Physician's Telephone Numbers (0008,0094) X
Region of Residence (0010,2152) X
Related Frame of Reference UID (3006,00C2) U
Request Attributes Sequence (0040,0275) X
Requested Contrast Agent (0032,1070) X
Requested Procedure Comments (0040,1400) X
Requested Procedure Description (0032,1060) Z
Requested Procedure ID (0040,1001) X
Requested Procedure Location (0040,1005) X
Requested SOP Instance UID (0000,1001) U
Requesting Physician (0032,1032) X
Requesting Service (0032,1033) X
Responsible Organization (0010,2299) X
Responsible Person (0010,2297) X
Results Comments (4008,4000) X
Results Distribution List Sequence (4008,0118) X
Results ID Issuer (4008,0042) X
Review Date (300E,0004) D
Review Time (300E,0005) D
Reviewer Name (300E,0008) Z
RT Plan Date (300A,0006) D

Page 71
RT Plan Time (300A,0007) D
Safe Position Exit Date (3008,0162) D
Safe Position Exit Time (3008,0164) D
Safe Position Return Date (3008,0166) D
Safe Position Return Time (3008,0168) D
Scheduled Admission Date (0038,001A) D
Scheduled Admission Time (0038,001B) D
Scheduled Discharge Date (0038,001C) D
Scheduled Discharge Time (0038,001D) D
Scheduled Human Performers Sequence (0040,4034) X
Scheduled Patient Institution Residence (0038,001E) X
Scheduled Performing Physician Identification Sequence (0040,000B) X
Scheduled Performing Physician's Name (0040,0006) X
Scheduled Procedure Step Description (0040,0007) X
Scheduled Procedure Step End Date (0040,0004) X
Scheduled Procedure Step End Time (0040,0005) X
Scheduled Procedure Step Location (0040,0011) X
Scheduled Procedure Step Modification Date Time (0040,4010) D
Scheduled Procedure Step Start Date (0040,0002) X
Scheduled Procedure Step Start Time (0040,0003) X
Scheduled Station AE Title (0040,0001) X
Scheduled Station Geographic Location Code Sequence (0040,4027) X
Scheduled Station Name (0040,0010) X
Scheduled Station Name Code Sequence (0040,4025) X
Scheduled Study Location (0032,1020) X
Scheduled Study Location AE Title (0032,1021) X
Scheduled Study Start Date (0032,1000) D
Scheduled Study Start Time (0032,1001) D
Series Date (0008,0021) D
Series Description (0008,103E) X,S
Series Instance UID (0020,000E) U
Series Time (0008,0031) D
Service Episode Description (0038,0062) X
Service Episode ID (0038,0060) X
Smoking Status (0010,21A0) X
SOP Authorization DateTime (0100,0420) D
SOP Instance UID (0008,0018) U
Source Strength Reference Date (300A,022C) D
Source Strength Reference Time (300A,022E) D
Special Needs (0038,0050) X

Page 72
Start Acquisition DateTime (0018,9516) D
Station Name (0008,1010) Z
Storage Media File-set UID (0088,0140) U
Structure Set Date (3006,0008) D
Structure Set Time (3006,0009) D
Study Arrival Date (0032,1040) D
Study Arrival Time (0032,1041) D
Study Comments (0032,4000) X
Study Completion Date (0032,1050) D
Study Completion Time (0032,1051) D
Study Date (0008,0020) D
Study Description (0008,1030) X,S
Study ID (0020,0010) Z,S
Study ID Issuer (0032,0012) X
Study Instance UID (0020,000D) U
Study Read Date (0032,0034) D
Study Read Time (0032,0035) D
Study Time (0008,0030) D
Study Verified Date (0032,0032) D
Study Verified Time (0032,0033) D
Substance Administration DateTime (0044,0010) D
Synchronization Frame of Reference UID (0020,0200) U
Template Extension Creator UID (0040,DB0D) U
Template Extension Organization UID (0040,DB0C) U
Text Comments (4000,4000) X
Text String (2030,0020) X
Time (0040,A122) D
Time of Document Creation or Verbal Transaction (Trial) (0040,A112) D
Time of Gain Calibration (0014,3077) D
Time of Last Calibration (0018,1201) D
Time of Last Detector Calibration (0018,700E) D
Time of Secondary Capture (0018,1014) D
Timezone Offset From UTC (0008,0201) X
Topic Author (0088,0910) X
Topic Keywords (0088,0912) X
Topic Subject (0088,0906) X
Topic Title (0088,0904) X
Transaction UID (0008,1195) U
Treatment Control Point Date (3008,0024) D
Treatment Control Point Time (3008,0025) D

Page 73
 Treatment Date (3008,0250) D
Treatment Time (3008,0251) D
UID (0040,A124) U
Verification Date Time (0040,A030) D
Verifying Observer Identification Code Sequence (0040,A088) Z
Verifying Observer Name (0040,A075) Z
Verifying Observer Sequence (0040,A073) Z
Verifying Organization (0040,A027) X
Visit Comments (0038,4000) X

In the modification method column, the following legend applies:

- Z: the attribute is nulled, or set to an empty value
- X: the attribute is removed entirely
- U: the value is a DICOM UID that is re-mapped
- S: the value is specified by the user
- D: date or date/time offset by the difference between the original and modified Study Date

During de-identification, no attributes are added, with the exception of those specified by the user.

With the exception of UIDs, Study Date and the Date or Date/Time attributes offset by the difference in
Study Date (those marked with a ‘D’ in Table 7.1-1), no attribute values are generated.

The integrity of UIDs for all files de-identified in the same session will be maintained, meaning that all
relationships, such as Study and Series relationships, will be maintained in the de-identified SOP
Instances.

Please note that there is currently no provision for “well known UIDs” such as “well-known frames of
reference” or “well-known SOP instances” during de-identification. All UID values in applicable attributes
(those marked M in Table 7.1-1) are remapped.

7.1.2 Audit Trail Message Format Profile

The application provides conformance to the Audit Trail Message Format Profile defined in the final text of
DICOM Supplement 95. The following describes the application’s audit message format conformance:

- Audit trail messages are generated and transmitted when the application is used in conjunction
with a central enterprise application server.
- Audit trail messages are generated and stored to the local file system when the application is part
of a standalone commercial installation.
- Audit trail messages are not generated otherwise.
- Audit trail messages are not received nor processed by the application.
- Audit event reporting cannot be configured through the application interface. However, in an
enterprise scenario, the server to which the application transmits audit messages can be
configured.

The following table describes the auditable events that are detected and reported:

Table 7.1-2
DETECTED AND REPORTED AUDIT EVENTS

Event Behavior
Application Activity Not detected or reported
Audit Log Used Not detected or reported

Page 74
Begin Transferring DICOM Instances Detected and reported when a C-STORE operation is
initiated:
 manually by the user
 automatically, when a “Send Key Object
Selections” operation is triggered
 by the local MOVE-SCP in response to a C-
MOVE request
Data Export Detected and reported when instances in the internal
database are exported, in any form, to a location
outside the internal database. This includes:
 a local file system
 an external file system, or removable media
 a DICOM Printer
To be clear, operations that trigger “DICOM Instances
Transferred” do not trigger this event. Also, this event
can only be triggered directly by a user-initiated
operation.
Data Import Detected and reported when instances are imported
into the internal database:
 manually by the user from any file system,
local or remote
 automatically, when the user creates Key
Object Selection Documents, and associated
Softcopy Presentation States
 when a re-index of the internal database is
performed
DICOM Instances Accessed Detected and reported when instances in the internal
database are read, created, or updated. More
specifically:
 When the user opens a study for viewing; this
includes viewing the header information.
 When the user creates Key Object Selection
Documents and accompanying Softcopy
Presentation States; these are also
automatically imported into the internal
database.
 When the user edits a SOP Instance via the
application’s DICOM Editor.
 When the user creates an anonymous copy of
a study in the internal database; these are
also automatically imported into the internal
database.
DICOM Instances Transferred Detected and reported when the transfer is complete
regardless of origin of C-STORE operation
DICOM Study Deleted Detected and reported when instances in the internal
database are deleted
Network Entry Not detected or reported
Order Record Not detected or reported
Patient Record Not detected or reported

Page 75
 Procedure Record Not detected or reported
Query Detected and reported when a C-FIND request is sent
or received
Security Alert Detected and reported when user authentication fails
and when audit trail logging is suspended or resumed
User Authentication Detected and reported when user authentication
succeeds or the user signs out; user authentication
capabilities only exist in commercial offerings of the
software.

7.2 ASSOCIATION LEVEL SECURITY

None supported.

7.3 APPLICATION LEVEL SECURITY

None supported.

Page 76
 8 ANNEXES

8.1 IOD CONTENTS

8.1.1 Created SOP Instances

See Section 4.2.9.3.1.3 for a description of SOP Instances created during image print operations.

See Section 7.1.1 for a description of SOP Instances created during de-identification.

Table 8.1-1 specifies the attributes of a Grayscale Softcopy Presentation State created by the application.

Table 8.1-2 specifies the attributes of a Color Softcopy Presentation State created by the application.

Table 8.1-3 specifies the attributes of a Key Object Selection Document created by the application.

Table 8.1-4 specifies the attributes of an Encapsulated PDF created by the application.

Table 8.1-5 specifies the attributes of a Secondary Capture Image created by the application.

The following tables use a number of abbreviations. The abbreviations used in the “Presence of Module”
column are:

- ALWAYS: Module is always present

The abbreviations used in the “Presence of Value” column are:

- ALWAYS: Attribute is always present with a non-zero-length value

- ANAP: Attribute is not always present
- EMPTY: Attribute is included without a value
- NEVER: Attribute is never included
- VNAP: Value not always present (attribute sent zero-length if no value)

The abbreviations used in the “Source” column are:

- AUTO: The attribute value is generated automatically, or indirectly from previous user input
- COPY: The attribute value is copied verbatim from the referenced SOP instances
- USER: The attribute value is taken directly from user input

8.1.1.1 Grayscale Softcopy Presentation State IOD

Masks in the softcopy presentation state are not supported by the application.

Table 8.1-1
IOD OF CREATED GRAYSCALE SOFTCOPY PRESENTATION STATE SOP INSTANCES

IE Module Reference Presence of Module

Patient Patient Table 8.1-6 ALWAYS
Clinical Trial Subject Table 8.1-7 Only if module exists in referenced
SOP instance(s)
Study General Study Table 8.1-8 ALWAYS
Patient Study Table 8.1-9 Only if module exists in referenced
SOP instance(s)

Page 77
 Clinical Trial Study Table 8.1-10 Only if module exists in referenced
SOP instance(s)
Series General Series Table 8.1-12 ALWAYS
Presentation Series Table 8.1-13 ALWAYS
Equipment General Equipment Table 8.1-11 ALWAYS
Presentation Presentation State Identification Table 8.1-14 ALWAYS
State
Presentation State Relationship Table 8.1-15 ALWAYS
Presentation State Shutter Table 8.1-16 ALWAYS
Presentation State Mask Table 8.1-25 ALWAYS
Display Shutter Table 8.1-17 Only if a Display Shutter is to be
applied to referenced image(s) and the
Bitmap Display Shutter Module is not
present
Bitmap Display Shutter Table 8.1-18 Only if a Bitmap Display Shutter is to
be applied to referenced image(s) and
the Display Shutter Module is not
present
Overlay Plane Table 8.1-19 Only if overlays are to be applied to
referenced image(s) or the Bitmap
Display Shutter Module is present
Overlay Activation Table 8.1-20 Only if overlays are to be applied to
referenced image(s)
Displayed Area Table 8.1-21 ALWAYS
Graphic Annotation Table 8.1-22 Only if graphic annotations are to be
applied to referenced image(s)
Spatial Transformation Table 8.1-23 ALWAYS
Graphic Layer Table 8.1-24 Only if graphic annotations or overlays
are to be applied to referenced
image(s)
Softcopy VOI LUT Table 8.1-26 ALWAYS
Softcopy Presentation LUT Table 8.1-27 ALWAYS
SOP Common Table 8.1-28 ALWAYS

8.1.1.2 Color Softcopy Presentation State IOD

ICC Profiles and CIELab values are not supported by the application, and thus any application-generated
color softcopy presentation state SOP instances may contain the following mandatory IOD modules which
do not fully conform to the DICOM Standard:

- Presentation State Shutter, PS 3.3 C.11.12 (See Table 8.1-16)

- ICC Profile, PS 3.3 C.11.15 (See Table 8.1-29)

Table 8.1-2
IOD OF CREATED COLOR SOFTCOPY PRESENTATION STATE SOP INSTANCES

IE Module Reference Presence of Module

Patient Patient Table 8.1-6 ALWAYS

Page 78
 Clinical Trial Subject Table 8.1-7 Only if module exists in referenced
SOP instance(s)
Study General Study Table 8.1-8 ALWAYS
Patient Study Table 8.1-9 Only if module exists in referenced
SOP instance(s)
Clinical Trial Study Table 8.1-10 Only if module exists in referenced
SOP instance(s)
Series General Series Table 8.1-12 ALWAYS
Presentation Series Table 8.1-13 ALWAYS
Equipment General Equipment Table 8.1-11 ALWAYS
Presentation Presentation State Identification Table 8.1-14 ALWAYS
State
Presentation State Relationship Table 8.1-15 ALWAYS
Presentation State Shutter Table 8.1-16 ALWAYS
Display Shutter Table 8.1-17 Only if a Display Shutter is to be
applied to referenced image(s) and the
Bitmap Display Shutter Module is not
present
Bitmap Display Shutter Table 8.1-18 Only if a Bitmap Display Shutter is to
be applied to referenced image(s) and
the Display Shutter Module is not
present
Overlay Plane Table 8.1-19 Only if overlays are to be applied to
referenced image(s) or the Bitmap
Display Shutter Module is present
Overlay Activation Table 8.1-20 Only if overlays are to be applied to
referenced image(s)
Displayed Area Table 8.1-21 ALWAYS
Graphic Annotation Table 8.1-22 Only if graphic annotations are to be
applied to referenced image(s)
Spatial Transformation Table 8.1-23 ALWAYS
Graphic Layer Table 8.1-24 Only if graphic annotations or overlays
are to be applied to referenced
image(s)
ICC Profile Table 8.1-29 NOT INCLUDED
SOP Common Table 8.1-30 ALWAYS

8.1.1.3 Key Object Selection Document IOD

Table 8.1-3
IOD OF CREATED KEY OBJECT SELECTION DOCUMENT SOP INSTANCES

IE Module Reference Presence of Module

Patient Patient Table 8.1-6 ALWAYS
Clinical Trial Subject Table 8.1-7 Only if module exists in
referenced SOP instance(s)

Page 79
Study General Study Table 8.1-8 ALWAYS
Patient Study Table 8.1-9 Only if module exists in
referenced SOP instance(s)
Clinical Trial Study Table 8.1-10 Only if module exists in
referenced SOP instance(s)
Series Key Object Document Table 8.1-31 ALWAYS
Series
Equipment General Equipment Table 8.1-11 ALWAYS
Document Key Object Document Table 8.1-32 ALWAYS
SR Document Content Table 8.1-33 ALWAYS
SOP Common Table 8.1-34 ALWAYS

8.1.1.4 Encapsulated PDF IOD

Table 8.1-4
IOD OF CREATED ENCAPSULATED PDF SOP INSTANCES

IE Module Reference Presence of Module

Patient Patient Table 8.1-6 ALWAYS
Clinical Trial Subject Table 8.1-7 Only if module exists in referenced
SOP instance(s)
Study General Study Table 8.1-8 ALWAYS
Patient Study Table 8.1-9 Only if module exists in referenced
SOP instance(s)
Clinical Trial Study Table 8.1-10 Only if module exists in referenced
SOP instance(s)
Series Encapsulated Document Series Table 8.1-38 ALWAYS
Equipment General Equipment Table 8.1-11 ALWAYS
SC Equipment Table 8.1-39 ALWAYS
Encapsulated Encapsulated Document Table 8.1-40 ALWAYS
Document
SOP Common Table 8.1-41 ALWAYS

8.1.1.5 Secondary Capture Image IOD

The Secondary Capture Image IOD utilized by the application is a Standard Extended SOP Class based
on the Secondary Capture Image Storage SOP Class (1.2.840.10008.5.1.4.1.1.88.59). The following
modules are included in created instances to provide additional important details regarding the derived
content where applicable:

- Frame of Reference Module (Table 8.1-44)

- Image Plane Module (Table 8.1-46)
- Other additional auxiliary image-level attributes (Table 8.1-52)

Table 8.1-5
IOD OF CREATED SECONDARY CAPTURE IMAGE SOP INSTANCES

IE Module Reference Presence of Module

Page 80
Patient Patient Table 8.1-6 ALWAYS
Clinical Trial Subject Table 8.1-7 Only if module exists in source
image(s)
Study General Study Table 8.1-8 ALWAYS
Patient Study Table 8.1-9 Only if module exists in source
image(s)
Clinical Trial Study Table 8.1-10 Only if module exists in source
image(s)
Series General Series Table 8.1-42 ALWAYS
Equipment General Equipment Table 8.1-11 ALWAYS
SC Equipment Table 8.1-43 ALWAYS
Frame of Frame of Reference Table 8.1-44 Only if module exists in source
Reference image(s)
Image General Image Table 8.1-45 ALWAYS
Image Plane Table 8.1-46 Only if module exists in source
image(s)
Image Pixel Table 8.1-47 ALWAYS
Device N/A NOT INCLUDED
Specimen N/A NOT INCLUDED
SC Image Table 8.1-48 ALWAYS
Overlay Plane N/A NOT INCLUDED
Modality LUT Table 8.1-49 Only if Photometric Interpretation
(0028,0004) is either
MONOCHROME1 or
MONOCHROME2
VOI LUT Table 8.1-50 Only if Photometric Interpretation
(0028,0004) is either
MONOCHROME1 or
MONOCHROME2
ICC Profile N/A NOT INCLUDED
SOP Common Table 8.1-51 ALWAYS
Auxiliary Attributes Table 8.1-52 ALWAYS – includes additional
common modality-specific attributes
for compatibility support

8.1.1.6 Common Modules

Table 8.1-6
PATIENT MODULE OF CREATED SOP INSTANCES

Attribute Name Tag VR Value Presence Source

of Value
Patient’s Name (0010,0010) PN From Referenced Image(s) ANAP COPY
Patient ID (0010,0020) LO From Referenced Image(s) ANAP COPY
Issuer of Patient ID (0010,0021) LO From Referenced Image(s) ANAP COPY

Page 81
Patient’s Birth Date (0010,0030) DA From Referenced Image(s) ANAP COPY
Patient’s Sex (0010,0040) CS From Referenced Image(s) ANAP COPY
Referenced Patient (0008,1120) SQ From Referenced Image(s) ANAP COPY
Sequence
> Referenced SOP (0008,1150) UI From Referenced Image(s) ALWAYS COPY
Class UID
> Referenced SOP (0008,1155) UI From Referenced Image(s) ALWAYS COPY
Instance UID
Patient’s Birth Time (0010,0032) TM From Referenced Image(s) ANAP COPY
Other Patient IDs (0010,1000) LO From Referenced Image(s) ANAP COPY
Other Patient IDs (0010,1002) SQ From Referenced Image(s) ANAP COPY
Sequence
> Patient ID (0010,0020) LO From Referenced Image(s) ANAP COPY
> Issuer of Patient ID (0010,0021) LO From Referenced Image(s) ANAP COPY
> Type of Patient ID (0010,0022) CS From Referenced Image(s) ANAP COPY
Other Patient Names (0010,1001) PN From Referenced Image(s) ANAP COPY
Ethnic Group (0010,2160) SH From Referenced Image(s) ANAP COPY
Patient Comments (0010,4000) LT From Referenced Image(s) ANAP COPY
Patient Species (0010,2201) LO From Referenced Image(s) ANAP COPY
Description
Patient Species Code (0010,2202) SQ From Referenced Image(s) ANAP COPY
Sequence
> Include ‘Code Sequence Macro’ Defined Context ID is 7454.

Patient Breed (0010,2292) LO From Referenced Image(s) ANAP COPY

Description
Patient Breed Code (0010,2293) SQ From Referenced Image(s) ANAP COPY
Sequence
> Include ‘Code Sequence Macro’ Defined Context ID is 7480.

Breed Registration (0010,2294) SQ From Referenced Image(s) ANAP COPY

Sequence
> Breed Registration (0010,2295) LO From Referenced Image(s) ANAP COPY
Number
> Breed Registry Code (0010,2296) SQ From Referenced Image(s) ANAP COPY
Sequence
>> Include ‘Code Sequence Macro’ Defined Context ID is 7481.

Responsible Person (0010,2297) PN From Referenced Image(s) ANAP COPY

Responsible Person (0010,2298) CS From Referenced Image(s) ANAP COPY
Role
Responsible (0010,2299) LO From Referenced Image(s) ANAP COPY
Organization
Patient Identity (0012,0062) CS From Referenced Image(s) ANAP COPY
Removed

Page 82
De-identification Method (0012,0063) LO From Referenced Image(s) ANAP COPY
De-identification Method (0012,0064) SQ From Referenced Image(s) ANAP COPY
Code Sequence
> Include ‘Code Sequence Macro’ No Baseline Context ID is defined.

Table 8.1-7
CLINICAL TRIAL SUBJECT MODULE OF CREATED SOP INSTANCES

Attribute Name Tag VR Value Presence Source

of Value
Clinical Trial Sponsor (0012,0010) LO From Referenced Image(s) ANAP COPY
Name
Clinical Trial Protocol ID (0012,0020) LO From Referenced Image(s) ANAP COPY
Clinical Trial Protocol (0012,0021) LO From Referenced Image(s) ANAP COPY
Name
Clinical Trial Site ID (0012,0030) LO From Referenced Image(s) ANAP COPY
Clinical Trial Site Name (0012,0031) LO From Referenced Image(s) ANAP COPY
Clinical Trial Subject ID (0012,0040) LO From Referenced Image(s) ANAP COPY
Clinical Trial Subject (0012,0042) LO From Referenced Image(s) ANAP COPY
Reading ID

Table 8.1-8
GENERAL STUDY MODULE OF CREATED SOP INSTANCES

Attribute Name Tag VR Value Presence Source

of Value
Study Instance UID (0020,000D) UI From Referenced Image(s) ANAP COPY
Study Date (0008,0020) DA From Referenced Image(s) ANAP COPY
Study Time (0008,0030) TM From Referenced Image(s) ANAP COPY
Referring Physician’s (0008,0090) PN From Referenced Image(s) ANAP COPY
Name
Referring Physician (0008,0096) SQ From Referenced Image(s) ANAP COPY
Identification Sequence
> Include ‘Person Identification Macro’
Study ID (0020,0010) SH From Referenced Image(s) ANAP COPY
Accession Number (0008,0050) SH From Referenced Image(s) ANAP COPY
Study Description (0008,1030) LO From Referenced Image(s) ANAP COPY
Physician(s) of Record (0008,1048) PN From Referenced Image(s) ANAP COPY
Physician(s) of Record (0008,1049) SQ From Referenced Image(s) ANAP COPY
Identification Sequence
> Include ‘Person Identification Macro’
Name of Physician(s) (0008,1060) PN From Referenced Image(s) ANAP COPY
Reading Study

Page 83
Physician(s) Reading (0008,1062) SQ From Referenced Image(s) ANAP COPY
Study Identification
Sequence
> Include ‘Person Identification Macro’
Referenced Study (0008,1110) SQ From Referenced Image(s) ANAP COPY
Sequence
> Include ‘SOP Instance Reference Macro’
Procedure Code (0008,1032) SQ From Referenced Image(s) ANAP COPY
Sequence
> Include ‘Code Sequence Macro’ No Baseline Context ID is defined.

Table 8.1-9
PATIENT STUDY MODULE OF CREATED SOP INSTANCES

Attribute Name Tag VR Value Presence Source

of Value
Admitting Diagnoses (0008,1080) LO From Referenced Image(s) ANAP COPY
Description
Admitting Diagnoses (0008,1084) SQ From Referenced Image(s) ANAP COPY
Code Sequence
> Include ‘Code Sequence Macro’ No Baseline Context ID is defined.
Patient’s Age (0010,1010) AS From Referenced Image(s) ANAP COPY
Patient’s Size (0010,1020) DS From Referenced Image(s) ANAP COPY
Patient’s Weight (0010,1030) DS From Referenced Image(s) ANAP COPY
Occupation (0010,2180) SH From Referenced Image(s) ANAP COPY
Additional Patient’s (0010,21B0) LT From Referenced Image(s) ANAP COPY
History
Admission ID (0038,0010) LO From Referenced Image(s) ANAP COPY
Issuer of Admission ID (0038,0011) LO From Referenced Image(s) ANAP COPY
Service Episode ID (0038,0060) LO From Referenced Image(s) ANAP COPY
Issuer of Service (0038,0061) LO From Referenced Image(s) ANAP COPY
Episode ID
Service Episode (0038,0062) LO From Referenced Image(s) ANAP COPY
Description
Patient’s Sex Neutered (0010,2203) CS From Referenced Image(s) ANAP COPY

Table 8.1-10
CLINICAL TRIAL STUDY MODULE OF CREATED SOP INSTANCES

Attribute Name Tag VR Value Presence Source

of Value
Clinical Trial Time Point (0012,0050) LO From Referenced Image(s) ANAP COPY
ID
Clinical Trial Time Point (0012,0051) ST From Referenced Image(s) ANAP COPY
Description

Page 84
 Table 8.1-11
GENERAL EQUIPMENT MODULE OF CREATED SOP INSTANCES

Attribute Name Tag VR Value Presence Source

of Value
Manufacturer (0008,0070) LO ClearCanvas Inc. ALWAYS AUTO
Manufacturer’s Model (0008,1090) LO ClearCanvas Workstation ALWAYS AUTO
Name
Device Serial Number (0018,1000) LO Not Included NEVER AUTO
Software Versions (0018,1020) LO Version of ClearCanvas ALWAYS AUTO
Workstation software
Institution Name (0008,0080) LO Not Included NEVER AUTO
Institution Address (0008,0081) ST Not Included NEVER AUTO
Institutional Department (0008,1040) LO Not Included NEVER AUTO
Name
Station Name (0008,1010) SH Not Included NEVER AUTO

8.1.1.7 Common Softcopy Presentation State Modules

Table 8.1-12
GENERAL SERIES MODULE OF CREATED PRESENTATION STATE SOP INSTANCES

Attribute Name Tag VR Value Presence Source

of Value
Modality (0008,0060) CS PR ALWAYS AUTO
Series Instance UID (0020,000E) UI Automatically Generated ALWAYS AUTO
Series Number (0020,0011) IS Zero-length EMPTY AUTO

Table 8.1-13
PRESENTATION SERIES MODULE OF CREATED PRESENTATION STATE SOP INSTANCES

Attribute Name Tag VR Value Presence Source

of Value
Modality (0080,0060) CS PR ALWAYS AUTO

Table 8.1-14
PRESENTATION STATE IDENTIFICATION MODULE OF
CREATED PRESENTATION STATE SOP INSTANCES

Attribute Name Tag VR Value Presence Source

of Value
Presentation Creation (0070,0082) DA Date when presentation state ALWAYS AUTO
Date was captured
Presentation Creation (0070,0083) TM Time when presentation state ALWAYS AUTO
Time was captured
Instance Number (0020,0013) IS 1 ALWAYS AUTO

Page 85
Content Label (0070,0080) CS FOR_PRESENTATION ALWAYS AUTO
Content Description (0070,0081) LO Zero-length EMPTY AUTO
Content Creator’s Name (0070,0084) PN Zero-length EMPTY AUTO

Table 8.1-15
PRESENTATION STATE RELATIONSHIP MODULE OF CREATED PRESENTATION STATE SOP
INSTANCES

Attribute Name Tag VR Value Presence Source

of Value
Referenced Series (0008,1115) SQ One or more items identifying ALWAYS AUTO
Sequence the referenced image(s)
> Include ‘Image SOP Instance Reference Macro’

Table 8.1-16
PRESENTATION STATE SHUTTER MODULE OF
CREATED PRESENTATION STATE SOP INSTANCES

Attribute Name Tag VR Value Presence Source

of Value
Shutter Presentation (0018,1622) US See Table 8.1-17 or Table 8.1-18, whichever is
Value applicable.
Shutter Presentation (0018,1624) US See Table 8.1-17 or Table 8.1-18, whichever is
Color CIELab Value applicable.

Table 8.1-17
DISPLAY SHUTTER MODULE OF CREATED PRESENTATION STATE SOP INSTANCES

Attribute Name Tag VR Value Presence Source

of Value
Shutter Shape (0018,1600) CS One or more of ALWAYS AUTO
RECTANGULAR, CIRCULAR
and POLYGONAL
Shutter Left Vertical (0018,1602) IS From Presentation State ANAP AUTO
Edge
Shutter Right Vertical (0018,1604) IS From Presentation State ANAP AUTO
Edge
Shutter Upper (0018,1606) IS From Presentation State ANAP AUTO
Horizontal Edge
Shutter Lower (0018,1608) IS From Presentation State ANAP AUTO
Horizontal Edge
Center of Circular (0018,1610) IS From Presentation State ANAP AUTO
Shutter
Radius of Circular (0018,1612) IS From Presentation State ANAP AUTO
Shutter
Vertices of the (0018,1620) IS From Presentation State ANAP AUTO
Polygonal Shutter

Page 86
Shutter Presentation (0018,1622) US 0 ALWAYS AUTO
Value
Shutter Presentation (0018,1624) US Not Included NEVER AUTO
Color CIELab Value

Table 8.1-18
BITMAP DISPLAY SHUTTER MODULE OF CREATED PRESENTATION STATE SOP INSTANCES

Attribute Name Tag VR Value Presence Source

of Value
Shutter Shape (0018,1600) CS BITMAP ALWAYS AUTO
Shutter Overlay Group (0018,1623) US From Presentation State ALWAYS AUTO
Shutter Presentation (0018,1622) US From Presentation State ALWAYS AUTO
Value
Shutter Presentation (0018,1624) US Not Included NEVER AUTO
Color CIELab Value

Table 8.1-19
OVERLAY PLANE MODULE OF CREATED PRESENTATION STATE SOP INSTANCES

Attribute Name Tag VR Value Presence Source

of Value
Overlay Rows (60xx,0010)) US From Presentation State ALWAYS AUTO
Overlay Columns (60xx,0011) US From Presentation State ALWAYS AUTO
Overlay Type (60xx,0040) CS From Presentation State ALWAYS AUTO
Overlay Origin (60xx,0050) SS From Presentation State ALWAYS AUTO
Overlay Bits Allocated (60xx,0100) US 1 ALWAYS AUTO
Overlay Bit Position (60xx,0102) US 0 ALWAYS AUTO
Overlay Data (60xx,3000) OB From Presentation State ALWAYS AUTO
Overlay Description (60xx,0022) LO From Presentation State ANAP AUTO
Overlay Subtype (60xx,0045) LO From Presentation State ANAP AUTO
Overlay Label (60xx,1500) LO From Presentation State ANAP AUTO

Table 8.1-20
OVERLAY ACTIVATION MODULE OF CREATED PRESENTATION STATE SOP INSTANCES

Attribute Name Tag VR Value Presence Source

of Value
Overlay Activation (60xx,1001) CS From Presentation State VNAP AUTO
Layer

Page 87
 Table 8.1-21
DISPLAYED AREA MODULE OF CREATED PRESENTATION STATE SOP INSTANCES

Attribute Name Tag VR Value Presence Source

of Value
Displayed Area (0070,005A) SQ One item for each image frame ALWAYS AUTO
Selection Sequence describing its displayed area
> Referenced Image (0008,1140) SQ References exactly one image ALWAYS AUTO
Sequence frame
>> Include ‘Image SOP Instance Reference Macro’
> Displayed Area Top (0070,0052) SL From Presentation State ALWAYS AUTO
Left Hand Corner
> Displayed Area (0070,0053) SL From Presentation State ALWAYS AUTO
Bottom Right Hand
Corner
> Presentation Size (0070,0100) CS One of SCALE TO FIT, TRUE ALWAYS AUTO
Mode SIZE or MAGNIFY
> Presentation Pixel (0070,0101) DS Included only when ANAP AUTO
Spacing Presentation Size Mode is
TRUE SIZE
> Presentation Pixel (0070,0102) IS Taken from referenced frame ALWAYS AUTO
Aspect Ratio or image if available, otherwise
1\1
> Presentation Pixel (0070,0103) FL Included only when ANAP AUTO
Magnification Ratio Presentation Size Mode is
MAGNIFY

Table 8.1-22
GRAPHIC ANNOTATION MODULE OF CREATED PRESENTATION STATE SOP INSTANCES

Attribute Name Tag VR Value Presence Source

of Value
Graphic Annotation (0070,0001) SQ One or more items describing ALWAYS AUTO
Sequence user-drawn measurements
and annotations. – user-drawn
ROI measurements with an
associated text element are
described in a single item
> Referenced Image (0008,1140) SQ References exactly one image
Sequence frame
>> Include ‘Image SOP Instance Reference Macro’
> Graphic Layer (0070,0002) CS From Presentation State ALWAYS AUTO
> Text Object Sequence (0070,0008) SQ One or more items if included ANAP AUTO
>> Bounding Box (0070,0003) CS PIXEL ALWAYS AUTO
Annotation Units
>> Anchor Point (0070,0004) CS PIXEL when text is part of a ANAP AUTO
Annotation Units callout graphic; not included
otherwise
>> Unformatted Text (0070,0006) ST From Presentation State ALWAYS AUTO
Value

Page 88
>> Bounding Box Top (0070,0010) FL From Presentation State ALWAYS AUTO
Left Hand Corner
>> Bounding Box (0070,0011) FL From Presentation State ALWAYS AUTO
Bottom Right Hand
Corner
>> Bounding Box Text (0070,0012) CS LEFT ALWAYS AUTO
Horizontal Justification
>> Anchor Point (0070,0014) FL Included only when text is part ANAP AUTO
of a callout graphic
>> Anchor Point (0070,0015) CS Included only when text is part ANAP AUTO
Visibility of a callout graphic
> Graphic Object (0070,0009) SQ One or more items if included ANAP AUTO
Sequence
>> Graphic Annotation (0070,0005) CS PIXEL ALWAYS AUTO
Units
>> Graphic Dimensions (0070,0020) US From Presentation State ALWAYS AUTO
>> Number of Graphic (0070,0021) US From Presentation State ALWAYS AUTO
Points
>> Graphic Data (0070,0022) FL From Presentation State ALWAYS AUTO
>> Graphic Type (0070,0023) CS One of POINT, POLYLINE, ALWAYS AUTO
INTERPOLATED, CIRCLE or
ELLIPSE
>> Graphic Filled (0070,0024) CS N when sequence item ANAP AUTO
describes a closed graphic; not
included otherwise

Table 8.1-23
SPATIAL TRANSFORMATION MODULE OF CREATED PRESENTATION STATE SOP INSTANCES

Attribute Name Tag VR Value Presence Source

of Value
Image Rotation (0070,0042) US One of 0, 90, 180 or 270 ALWAYS AUTO
Image Horizontal Flip (0070,0041) CS One of Y or N ALWAYS AUTO

Table 8.1-24
GRAPHIC LAYER MODULE OF CREATED PRESENTATION STATE SOP INSTANCES

Attribute Name Tag VR Value Presence Source

of Value
Graphic Layer (0070,0060) SQ One or more items ALWAYS AUTO
Sequence
> Graphic Layer (0070,0002) CS From Presentation State ALWAYS AUTO
> Graphic Layer Order (0070,0062) IS From Presentation State ALWAYS AUTO
> Graphic Layer (0070,0066) US Not Included NEVER AUTO
Recommended Display
Grayscale Value

Page 89
> Graphic Layer (0070,0401) US Not Included NEVER AUTO
Recommended Display
CIELab Value
> Graphic Layer (0070,0068) LO From Presentation State ALWAYS AUTO
Description

8.1.1.8 Grayscale Softcopy Presentation State Modules

Table 8.1-25
PRESENTATION STATE MASK MODULE OF
CREATED GRAYSCALE SOFTCOPY PRESENTATION STATE SOP INSTANCES

Attribute Name Tag VR Value Presence Source

of Value
No conditions met to require inclusion of any attributes in this module

Table 8.1-26
SOFTCOPY VOI LUT MODULE OF
GRAYSCALE SOFTCOPY PRESENTATION STATE SOP INSTANCES

Attribute Name Tag VR Value Presence Source

of Value
Softcopy VOI LUT (0028,3110) SQ
One item for each frame ALWAYS AUTO
Sequence describing the applied VOI
LUT
> Referenced Image (0008,1140) SQ References exactly one image ALWAYS AUTO
Sequence frame
> Include ‘Image SOP Instance Reference Macro’
> VOI LUT Sequence (0028,3010) SQ Included if Window Center and ANAP AUTO
Window Width are not
specified
>> LUT Descriptor (0028,3002) US From Presentation State ALWAYS AUTO
>> LUT Explanation (0028,3003) LO Not Included NEVER AUTO
>> LUT Data (0028,3006) US From Presentation State ALWAYS AUTO
> Window Center (0028,1050) DS From Presentation State ANAP AUTO
> Window Width (0028,1051) DS From Presentation State ANAP AUTO
> Window Center & (0028,1055) LO From Presentation State ANAP AUTO
Width Explanation
> VOI LUT Function (0028,1056) CS LINEAR when included ANAP AUTO

Table 8.1-27
SOFTCOPY PRESENTATION LUT MODULE OF
GRAYSCALE SOFTCOPY PRESENTATION STATE SOP INSTANCES

Attribute Name Tag VR Value Presence Source

of Value
Presentation LUT (2050,0010) SQ Not Included NEVER AUTO
Sequence

Page 90
Presentation LUT (2050,0020) CS From Presentation State ALWAYS AUTO
Shape

Table 8.1-28
SOP COMMON MODULE OF
CREATED GRAYSCALE SOFTCOPY PRESENTATION STATE SOP INSTANCES

Attribute Name Tag VR Value Presence Source

of Value
Specific Character Set (0008,0005) CS ISO_IR 192 ALWAYS AUTO
(Unicode in UTF-8)
SOP Class UID (0008,0016) UI 1.2.840.10008.5.1.4.1.1.11.1 ALWAYS AUTO
(Grayscale Softcopy
Presentation State Storage)
SOP Instance UID (0008,0018) UI Automatically generated ALWAYS AUTO

8.1.1.9 Color Softcopy Presentation State Modules

Table 8.1-29
ICC PROFILE MODULE OF CREATED COLOR SOFTCOPY PRESENTATION STATE SOP
INSTANCES

Attribute Name Tag VR Value Presence Source

of Value
ICC Profile (0028,2000) OB Not Included NEVER AUTO

Table 8.1-30
SOP COMMON MODULE OF CREATED COLOR SOFTCOPY PRESENTATION STATE SOP
INSTANCES

Attribute Name Tag VR Value Presence Source

of Value
Specific Character Set (0008,0005) CS ISO_IR 192 ALWAYS AUTO
(Unicode in UTF-8)
SOP Class UID (0008,0016) UI 1.2.840.10008.5.1.4.1.1.11.2 ALWAYS AUTO
(Color Softcopy Presentation
State Storage)
SOP Instance UID (0008,0018) UI Automatically generated ALWAYS AUTO

8.1.1.10 Key Object Selection Document Modules

Table 8.1-31
KEY OBJECT DOCUMENT SERIES MODULE OF
CREATED KEY OBJECT SELECTION DOCUMENT SOP INSTANCES

Attribute Name Tag VR Value Presence Source

of Value
Modality (0008,0060) CS KO ALWAYS AUTO

Page 91
Series Instance UID (0020,000E) UI Automatically generated ALWAYS AUTO
Series Number (0020,0011) IS Automatically generated (one ALWAYS AUTO
greater than highest series
number in study)
Series Date (0008,0021) DA Date when key object selection ALWAYS AUTO
was created
Series Time (0008,0031) TM Time when key object ALWAYS AUTO
selection was created
Series Description (0008,103E) LO From User Input ALWAYS USER
Referenced Performed (0008,1111) SQ Zero-length EMPTY AUTO
Procedure Step
Sequence

Table 8.1-32
KEY OBJECT DOCUMENT MODULE OF
CREATED KEY OBJECT SELECTION DOCUMENT SOP INSTANCES

Attribute Name Tag VR Value Presence Source

of Value
Instance Number (0020,0013) IS 1 ALWAYS AUTO
Content Date (0008,0023) DA Date when key object selection ALWAYS AUTO
was created
Content Time (0008,0033) TM Time when key object ALWAYS AUTO
selection was created
Referenced Request (0040,A370) SQ Not Included NEVER AUTO
Sequence
Current Requested (0040,A375) SQ One or more items describing ALWAYS AUTO
Procedure Evidence the referenced image(s) and
Sequence associated softcopy
presentation state SOP
instances.
> Include ‘Hierarchical SOP Instance Reference Macro’
Identical Documents (0040,A525) SQ One or more items describing ALWAYS AUTO
Sequence all key object selection
document SOP instances
being created during the
session due to referenced
image(s) from one or more
studies, including the SOP
instance in which this attribute
exists.
> Include ‘Hierarchical SOP Instance Reference Macro’

Table 8.1-33
SR DOCUMENT CONTENT MODULE OF
CREATED KEY OBJECT SELECTION DOCUMENT SOP INSTANCES

Attribute Name Tag VR Value Presence Source

of Value

Page 92
Value Type (0040,A040) CS CONTAINER ALWAYS AUTO
Concept Name Code (0040,A043) SQ Key Object Selection ALWAYS USER
Sequence Document Title
> Include ‘Code Sequence Macro’ 9 Defined Context ID is 7010.
Continuity of Content (0040,A050) CS SEPARATE ALWAYS AUTO
Content Template (0040,A504) SQ Not Included NEVER AUTO
Sequence
Content Sequence (0040,A730) SQ One or more content items as ALWAYS
described in Section 9.1.1.1.1
(such as Table 8.1-35 and
Table 8.1-37)

Table 8.1-34
SOP COMMON MODULE OF CREATED KEY OBJECT SELECTION DOCUMENT SOP INSTANCES

Attribute Name Tag VR Value Presence Source

of Value
Specific Character Set (0008,0005) CS ISO_IR 192 ALWAYS AUTO
(Unicode in UTF-8)
SOP Class UID (0008,0016) UI 1.2.840.10008.5.1.4.1.1.88.59 ALWAYS AUTO
(Key Object Selection
Document Storage)
SOP Instance UID (0008,0018) UI Automatically generated ALWAYS AUTO

9.1.1.1.1 Content Items Used in Key Object Selection Documents

Table 8.1-35
TEXT CONTENT ITEM USED IN
CREATED KEY OBJECT SELECTION DOCUMENT SOP INSTANCES

Attribute Name Tag VR Value Presence Source

of Value
Relationship Type (0040,A010) CS CONTAINS ALWAYS AUTO
Value Type (0040,A040) CS TEXT ALWAYS AUTO
Concept Name Code (0040,A043) SQ DCM 113012 Key Object ALWAYS AUTO
Sequence Description
> Include ‘Code Sequence Macro’ No Baseline Context ID is defined.
Text Value (0040,A160) UT Free form text describing key ALWAYS USER
object selection
Content Sequence (0040,A730) SQ Not Included NEVER AUTO
Referenced Content (0040,DB73) UL Not Included NEVER AUTO
Item Identifier

Page 93
 Table 8.1-36
PERSON NAME CONTENT ITEM USED IN
CREATED KEY OBJECT SELECTION DOCUMENT SOP INSTANCES

Attribute Name Tag VR Value Presence Source

of Value
Relationship Type (0040,A010) CS HAS OBS CONTEXT ALWAYS AUTO
Value Type (0040,A040) CS PNAME ALWAYS AUTO
Concept Name Code (0040,A043) SQ DCM 121008 Person Observer ALWAYS AUTO
Sequence Name
> Include ‘Code Sequence Macro’ No Baseline Context ID is defined.
Person Name (0040,A123) PN Name or Username of user ALWAYS USER
creating the key object
selection
Content Sequence (0040,A730) SQ Not Included NEVER AUTO
Referenced Content (0040,DB73) UL Not Included NEVER AUTO
Item Identifier

Table 8.1-37
IMAGE REFERENCE CONTENT ITEM USED IN
CREATED KEY OBJECT SELECTION DOCUMENT SOP INSTANCES

Attribute Name Tag VR Value Presence Source

of Value
Relationship Type (0040,A010) CS CONTAINS ALWAYS AUTO
Value Type (0040,A040) CS IMAGE ALWAYS AUTO
Concept Name Code (0040,A043) SQ DCM 113012 Key Object ALWAYS AUTO
Sequence Description
> Include ‘Code Sequence Macro’ No Baseline Context ID is defined.
Content Sequence (0040,A730) SQ Not Included NEVER AUTO
Referenced SOP (0008,1199) SQ Exactly one item referencing ALWAYS AUTO
Sequence an image
> Referenced SOP (0008,1150) UI SOP Class UID of referenced ALWAYS AUTO
Class UID image
> Referenced SOP (0008,1155) UI SOP Instance UID of ALWAYS AUTO
Instance UID referenced image
> Referenced Frame (0008,1160) IS List of frame numbers to which ANAP AUTO
Number this item refers, or zero-length
if image is not multi-frame or
item applies to all frames
> Referenced Segment (0062,000B) US Not Included NEVER AUTO
Number
> Referenced SOP (0008,1199) SQ Exactly one item referencing ANAP AUTO
Sequence an associated softcopy
presentation state when
included

Page 94
>> Referenced SOP (0008,1150) UI SOP Class UID of associated ALWAYS AUTO
Class UID softcopy presentation state
>> Referenced SOP (0008,1155) UI SOP Instance UID of ALWAYS AUTO
Instance UID associated softcopy
presentation state
> Referenced Real (0008,114B) SQ Not Included NEVER AUTO
World Value Mapping
Instance Sequence
> Icon Image Sequence (0088,0200) SQ Not Included NEVER AUTO
Referenced Content (0040,DB73) UL Not Included NEVER AUTO
Item Identifier

9.1.1.2 Encapsulated PDF Modules

Table 8.1-38
ENCAPSULATED DOCUMENT SERIES MODULE OF CREATED ENCAPSULATED PDF SOP
INSTANCES

Attribute Name Tag VR Value Presence Source

of Value
Modality (0008,0060) CS DOC ALWAYS AUTO
Series Instance UID (0020,000E) UI Automatically generated ALWAYS AUTO
Series Number (0020,0011) IS Automatically generated (one ALWAYS AUTO
greater than highest series
number in study)
Series Date (0008,0021) DA Date when user created ALWAYS AUTO
encapsulated PDF instance
Series Time (0008,0031) TM Time when user created ALWAYS AUTO
encapsulated PDF instance
Referenced Performed (0008,1111) SQ Not Included NEVER AUTO
Procedure Step
Sequence
Series Description (0008,103E) LO From User Input ALWAYS USER
Series Description Code (0008,103F) SQ Not Included NEVER AUTO
Sequence
Request Attributes (0040,0275) SQ Not Included NEVER AUTO
Sequence
Performed Procedure (0040,0253) SH Not Included NEVER AUTO
Step ID
Performed Procedure (0040,0244) DA Not Included NEVER AUTO
Step Start Date
Performed Procedure (0040,0245) TM Not Included NEVER AUTO
Step Start Time
Performed Procedure (0040,0254) LO Not Included NEVER AUTO
Step Description
Performed Protocol (0040,0260) SQ Not Included NEVER AUTO
Code Sequence

Page 95
Comments on the (0040,0280) ST Not Included NEVER AUTO
Performed Procedure
Step

Table 8.1-39
SC EQUIPMENT MODULE OF CREATED ENCAPSULATED PDF SOP INSTANCES

Attribute Name Tag VR Value Presence Source

of Value
Conversion Type (0008,0064) CS SD (Scanned Document) ALWAYS AUTO
Modality (0008,0060) CS DOC ALWAYS AUTO
Secondary Capture (0018,1010) LO Not Included NEVER AUTO
Device ID
Secondary Capture (0018,1016) LO Not Included NEVER AUTO
Device Manufacturer
Secondary Capture (0018,1018) LO Not Included NEVER AUTO
Device Manufacturer’s
Model Name
Secondary Capture (0018,1019) LO Not Included NEVER AUTO
Device Software
Versions
Video Image Format (0018,1022) SH Not Included NEVER AUTO
Acquired
Digital Image Format (0018,1023) LO Not Included NEVER AUTO
Acquired

Table 8.1-40
ENCAPSULATED DOCUMENT MODULE OF CREATED ENCAPSULATED PDF SOP INSTANCES

Attribute Name Tag VR Value Presence Source

of Value
Instance Number (0020,0013) IS 1 ALWAYS AUTO
Content Date (0008,0023) DA Date when PDF document file ALWAYS AUTO
was created on file system
Content Time (0008,0033) TM Time when PDF document file ALWAYS AUTO
was created on file system
Acquisition DateTime (0008,002A) DT Timestamp when PDF ALWAYS AUTO
document file was created on
file system
Burned In Annotation (0028,0301) CS YES ALWAYS AUTO
Source Instance (0042,0013) SQ Not Included NEVER AUTO
Sequence
Document Title (0042,0010) DT From User Input ALWAYS AUTO
Concept Name Code (0040,A043) SQ Zero-length EMPTY AUTO
Sequence
Verification Flag (0040,A493) CS Not Included NEVER AUTO
HL7 Instance Identifier (0040,E001) ST Not Included NEVER AUTO

Page 96
MIME Type of (0042,0012) LO application/pdf ALWAYS AUTO
Encapsulated
Document
List of MIME Types (0042,0014) LO Not Included NEVER AUTO
Encapsulated (0042,0011) OB PDF document binary content ALWAYS USER
Document

Table 8.1-41
SOP COMMON MODULE OF CREATED ENCAPSULATED PDF SOP INSTANCES

Attribute Name Tag VR Value Presence Source

of Value
Specific Character Set (0008,0005) CS ISO_IR 192 ALWAYS AUTO
(Unicode in UTF-8)
SOP Class UID (0008,0016) UI 1.2.840.10008.5.1.4.1.1.104.1 ALWAYS AUTO
(Encapsulated PDF Storage)
SOP Instance UID (0008,0018) UI Automatically generated ALWAYS AUTO

9.1.1.3 Secondary Capture Image Modules

Table 8.1-42
GENERAL SERIES MODULE OF CREATED SECONDARY CAPTURE IMAGE SOP INSTANCES

Attribute Name Tag VR Value Presence Source

of Value
Modality (0008,0060) CS From source image(s) of ALWAYS COPY
derived content
Series Instance UID (0020,000E) UI Automatically generated ALWAYS AUTO
Series Number (0020,0011) IS Automatically generated (one ALWAYS AUTO
greater than highest series
number in study)
Laterality (0020,0060) CS Not Included NEVER AUTO
Note: Since the series
contains individual
secondary capture
images which may not
necessarily be of the
same anatomy, this
attribute is not included.
However, the Image
Laterality (0020,0062)
attribute is included as
part of the Standard
Extended SOP Class.
Series Date (0008,0021) DA Date when secondary capture ALWAYS AUTO
series was created
Series Time (0008,0031) TM Time when secondary capture ALWAYS AUTO
series was created
Performing Physicians’ (0008,1050) PN Not Included NEVER AUTO
Name

Page 97
Performing Physician (0008,1052) SQ Not Included NEVER AUTO
Identification Sequence
Protocol Name (0018,1030) LO Not Included NEVER AUTO
Series Description (0008,103E) LO FOR KEY IMAGES ALWAYS AUTO
Series Description Code (0008,103F) SQ Not Included NEVER AUTO
Sequence
Operators’ Name (0008,1070) PN Not Included NEVER AUTO
Operator Identification (0008,1072) SQ Not Included NEVER AUTO
Sequence
Referenced Performed (0008,1111) SQ Not Included NEVER AUTO
Procedure Step
Sequence
Related Series (0008,1250) SQ Not Included NEVER AUTO
Sequence
Body Part Examined (0018,0015) CS Not Included NEVER AUTO
Note: Since the series
contains individual
secondary capture
images which may not
necessarily be of the
same anatomy, this
attribute is not included.
Patient Position (0018,5100) CS Not Included NEVER AUTO
Smallest Pixel Value in (0028,0108) US Not Included NEVER AUTO
Series
Largest Pixel Value in (0028,0109) US Not Included NEVER AUTO
Series
Request Attributes (0040,0275) SQ Not Included NEVER AUTO
Sequence
Anatomical Orientation (0010,2210) CS From source image(s) of ALWAYS COPY
Type derived content

Table 8.1-43
SC EQUIPMENT MODULE OF CREATED SECONDARY CAPTURE IMAGE SOP INSTANCES

Attribute Name Tag VR Value Presence Source

of Value
Conversion Type (0008,0064) CS WSD (Workstation) ALWAYS AUTO
Modality (0008,0060) CS From source image(s) of ALWAYS COPY
derived content
Secondary Capture (0018,1010) LO Not Included NEVER AUTO
Device ID
Secondary Capture (0018,1016) LO ClearCanvas Inc. ALWAYS AUTO
Device Manufacturer
Secondary Capture (0018,1018) LO ClearCanvas Workstation ALWAYS AUTO
Device Manufacturer’s
Model Name

Page 98
Secondary Capture (0018,1019) LO Version of ClearCanvas ALWAYS AUTO
Device Software Workstation software
Versions
Video Image Format (0018,1022) SH Not Included NEVER AUTO
Acquired
Digital Image Format (0018,1023) LO Not Included NEVER AUTO
Acquired

Table 8.1-44
FRAME OF REFERENCE MODULE OF CREATED SECONDARY CAPTURE IMAGE SOP
INSTANCES

Attribute Name Tag VR Value Presence Source

of Value
Frame of Reference (0020,0052) UI From source image(s) of ANAP COPY
UID derived content, if present
Position Reference (0020,1040) LO From source image(s) of ANAP COPY
Indicator derived content, if present

Table 8.1-45
GENERAL IMAGE MODULE OF CREATED SECONDARY CAPTURE IMAGE SOP INSTANCES

Attribute Name Tag VR Value Presence Source

of Value
Instance Number (0020,0013) IS Automatically generated ALWAYS AUTO
Patient Orientation (0020,0020) CS Not included
Content Date (0008,0023) DA Date when secondary capture ALWAYS AUTO
pixel data was created
Content Time (0008,0033) TM Time when secondary capture ALWAYS AUTO
pixel data was created
Image Type (0008,0008) CS DERIVED\SECONDARY ALWAYS AUTO
Acquisition Number (0020,0012) IS Not Included NEVER AUTO
Acquisition Date (0008,0022) DA Not Included NEVER AUTO
Acquisition Time (0008,0032) TM Not Included NEVER AUTO
Acquisition DateTime (0008,002A) DT Not Included NEVER AUTO
Referenced Image (0008,1140) SQ Not Included NEVER AUTO
Sequence
Derivation Description (0008,2111) ST Text description of the ALWAYS AUTO
derivation of the images
Derivation Code (0008,9215) SQ Code sequence ALWAYS AUTO
Sequence
> Include ‘Code Sequence Macro’ Defined CID 7203

Source Image (0008,2112) SQ One or more items referencing ANAP AUTO

Sequence images that contributed to the
derived content

Page 99
> Referenced SOP (0008,1150) UI From source image of derived ALWAYS AUTO
Class UID content
> Referenced SOP (0008,1155) UI From source image of derived ALWAYS AUTO
Instance UID content
> Purpose of Reference (0040,A170) SQ One item describing how the ALWAYS AUTO
Code Sequence source image contributed to
the derived content
>> Include ‘Code Sequence Macro’ Defined CID 7202

> Spatial Locations (0028,135A) CS YES if source images ALWAYS AUTO

Preserved contained spatial location
information which was
preserved in derived content
> Patient Orientation (0020,0020) CS Not Included NEVER AUTO
Referenced Instance (0008,114A) SQ Not Included NEVER AUTO
Sequence
Images in Acquisition (0020,1002) IS Not Included NEVER AUTO
Image Comments (0020,4000) LT Text description of the ANAP AUTO
derivation of the images
Quality Control Image (0028,0300) CS From source image(s) of ANAP COPY
derived content
Burned in Annotation (0028,0301) CS YES if at least one of the ANAP AUTO
source image(s) has YES in
this attribute, NO if all of the
source image(s) has NO in this
attribute. Not included
otherwise.
Recognizable Visual (0028,0302) CS YES if at least one of the ANAP AUTO
Features source image(s) has YES in
this attribute, NO if all of the
source image(s) has NO in this
attribute. Not included
otherwise.
Lossy Image (0028,2110) CS 01 if at least one of the source ANAP AUTO
Compression image(s) has 01 in this
attribute, 00 if all of the source
image(s) has 00 in this
attribute. Not included
otherwise.
Lossy Image (0028,2112) DS Maximum lossy compression ANAP AUTO
Compression Ratio ratio if at least one of the
source image(s) was lossy
compressed.
Lossy Image (0028,2114) CS From source image(s) if ANAP COPY
Compression Method present and consistent
Icon Image Sequence (0088,0200) SQ Not Included NEVER AUTO
Presentation LUT (2050,0020) CS Not Included NEVER AUTO
Shape
Irradiation Event UID (0008,3010) UI Not Included NEVER AUTO

Page 100
 Table 8.1-46
IMAGE PLANE MODULE OF CREATED SECONDARY CAPTURE IMAGE SOP INSTANCES

Attribute Name Tag VR Value Presence Source

of Value
Pixel Spacing (0028,0030) DS Pixel spacing in effect when ANAP AUTO
secondary capture pixel data
was created (i.e. may be
manually calibrated by user)
Image Orientation (0020,0037) DS Orientation of image (in patient ANAP AUTO
(Patient) coordinates) in effect when
secondary capture pixel data
was created
Image Position (Patient) (0020,0032) DS Position of top-left corner of ANAP AUTO
image (in patient coordinates)
in effect when secondary
capture pixel data was created
Slice Thickness (0018,0050) DS Effective thickness of the ANAP AUTO
image in mm, if applicable
Slice Location (0020,1041) DS Not Included NEVER AUTO

Table 8.1-47
IMAGE PIXEL MODULE OF CREATED SECONDARY CAPTURE IMAGE SOP INSTANCES

Attribute Name Tag VR Value Presence Source

of Value
Samples per Pixel (0028,0002) US 1 or 3 ALWAYS AUTO
Photometric (0028,0004) CS MONOCHROME1, ALWAYS AUTO
Interpretation MONOCHROME2, or RGB
Rows (0028,0010) US Number of rows in image ALWAYS AUTO
Columns (0028,0011) US Number of columns in image ALWAYS AUTO
Bits Allocated (0028,0100) US 8 or 16 ALWAYS AUTO
Bits Stored (0028,0101) US Number of bits stored in image ALWAYS AUTO
High Bit (0028,0102) US Always exactly one less than ALWAYS AUTO
Bits Stored
Pixel Representation (0028,0103) US 0 or 1 ALWAYS AUTO
Pixel Data (7FE0,0010) OW Pixel data of image ALWAYS AUTO
Planar Configuration (0028,0006) US 0 ALWAYS AUTO

Page 101
Pixel Aspect Ratio (0028,0034) IS 1\1 if image was manually VNAP AUTO
calibrated by user, otherwise
aspect ratio in effect when
secondary capture pixel data
was created
Note: If the source image(s)
do not provide pixel
spacing, and the user
has not manually
calibrated the image, this
attribute will contain the
value of the attribute from
the source image(s) if
consistent.
Smallest Image Pixel (0028,0106) US Not Included NEVER AUTO
Value
Largest Image Pixel (0028,0107) US Not Included NEVER AUTO
Value
Red Palette Color (0028,1101) US Not Included NEVER AUTO
Lookup Table
Descriptor
Green Palette Color (0028,1102) US Not Included NEVER AUTO
Lookup Table
Descriptor
Blue Palette Color (0028,1103) US Not Included NEVER AUTO
Lookup Table
Descriptor
Red Palette Color (0028,1201) OW Not Included NEVER AUTO
Lookup Table Data
Green Palette Color (0028,1202) OW Not Included NEVER AUTO
Lookup Table Data
Blue Palette Color (0028,1203) OW Not Included NEVER AUTO
Lookup Table Data
ICC Profile (0028,2000) OB Not Included NEVER AUTO
Pixel Data Provider (0028,7FE0) UT Not Included NEVER AUTO
URL
Pixel Padding Range (0028,0121) US Not Included NEVER AUTO
Limit

Table 8.1-48
SC IMAGE MODULE OF CREATED SECONDARY CAPTURE IMAGE SOP INSTANCES

Attribute Name Tag VR Value Presence Source

of Value
Date of Secondary (0018,1012) DA Date when secondary capture ALWAYS AUTO
Capture pixel data was created
Time of Secondary (0018,1014) TM Time when secondary capture ALWAYS AUTO
Capture pixel data was created
Nominal Scanned Pixel (0018,2010) DS Not Included NEVER AUTO
Spacing

Page 102
Document Class Code (0040,E008) SQ Not Included NEVER AUTO
Sequence
Pixel Spacing (0028,0030) DS Pixel spacing in effect when ANAP AUTO
secondary capture pixel data
was created (i.e. may be
manually calibrated by user)
Pixel Spacing (0028,0A02) CS FIDUCIAL or GEOMETRY if ANAP AUTO
Calibration Type specified by source image(s)
of derived content
Note: If the image was
manually calibrated by
user, this attribute will be
empty
Pixel Spacing (0028,0A04) LO Text description of calibration ANAP AUTO
Calibration Description method if specified by source
image(s) of derived content
Note: If source image(s) do
not specify calibration
method, this attribute
may use the following
values:
Actual – pixel spacing
assumed to be actual
physical spacing for
cross-sectional source
image(s).
Detector – pixel spacing
assumed to be at
detector plane for
projectional source
image(s).
Geometry – pixel spacing
corrected for geometric
magnification for
projectional source
image(s).
Fiducial – pixel spacing
calibrated by fiducials in
projectional source
image(s).
Magnified – pixel spacing
adjusted for estimated
magnification factor in
projection source
image(s).
Manual – pixel spacing
was manually calibrated
by user.
Unknown – interpretation
of pixel spacing is
unknown.

Page 103
 Table 8.1-49
MODALITY LUT MODULE OF CREATED SECONDARY CAPTURE IMAGE SOP INSTANCES
If the pixel data range of the secondary capture pixel data is unchanged from that of the source image(s),
the modality LUTs included with the secondary capture image may be copied verbatim from the source
image(s). Otherwise, the included modality LUTs are recalculated in order to produce the same modality
values from the secondary capture as from the source image(s).

For example, the pixel data from the source images of MPR are transformed according to their per-frame
modality LUTs, thus changing their pixel data range. The modality LUT function is thus recalculated so
that, for any given patient location, the modality value would be the same whether from the secondary
capture or from the source images.

Attribute Name Tag VR Value Presence Source

of Value
Modality LUT Sequence (0028,3000) SQ Not Included NEVER AUTO
Rescale Intercept (0028,1052) DS Intercept of modality LUT ALWAYS AUTO
rescale function in effect when
secondary capture pixel data
was created
Rescale Slope (0028,1053) DS Slope of modality LUT rescale ALWAYS AUTO
function in effect when
secondary capture pixel data
was created
Rescale Type (0028,1054) LO Output units of modality LUT ALWAYS AUTO
rescale function in effect when
secondary capture pixel data
was created
Note: In addition to the
standard terms HU and
OD, this attribute may
also specify terms
defined for the Units
(0054,1001) attribute
(e.g. BQML, CNTS)

Table 8.1-50
VOI LUT MODULE OF CREATED SECONDARY CAPTURE IMAGE SOP INSTANCES
If the pixel data range of the secondary capture pixel data is unchanged from that of the source image(s),
the VOI LUTs included with the secondary capture image may be copied verbatim from the source
image(s). Otherwise, the included VOI LUTs are recalculated in order to approximate the same viewing
effect on the secondary capture as viewing the source image(s).

For example, the pixel data from the source images of MPR are transformed according to their per-frame
modality LUTs, thus changing their pixel data range. Any VOI LUTs of the source images are thus
recalculated so as to select the same range of modality values.

Attribute Name Tag VR Value Presence Source

of Value
VOI LUT Sequence (0028,3010) SQ One or more items describing ANAP AUTO
VOI LUTs for the derived
content

Page 104
> LUT Descriptor (0028,3002) US Descriptor of VOI LUT ALWAYS AUTO
or
SS
> LUT Explanation (0028,3003) LO Text label of VOI LUT ANAP AUTO
> LUT Data (0028,3006) US Data of VOI LUT ALWAYS AUTO
or
OW
Window Center (0028,1050) DS Window center values for VOI ANAP AUTO
LUT of the derived content
Window Width (0028,1051) DS Window width values for VOI ANAP AUTO
LUT of the derived content
Window Center & Width (0028,1055) LO Text label for VOI LUT of the ANAP AUTO
Explanation derived content
VOI LUT Function (0028,1056) CS Type of VOI LUT function of ANAP AUTO
the derived content

Table 8.1-51
SOP COMMON MODULE OF CREATED SECONDARY CAPTURE IMAGE SOP INSTANCES

Attribute Name Tag VR Value Presence Source

of Value
Specific Character Set (0008,0005) CS ISO_IR 192 ALWAYS AUTO
(Unicode in UTF-8)
SOP Class UID (0008,0016) UI 1.2.840.10008.5.1.4.1.1.7 ALWAYS AUTO
(Secondary Capture Image
Storage)
SOP Instance UID (0008,0018) UI Automatically generated ALWAYS AUTO

Table 8.1-52
AUXILIARY ATTRIBUTES OF CREATED SECONDARY CAPTURE IMAGE SOP INSTANCES

Attribute Name Tag VR Value Presence Source

of Value
Image Laterality (0020,0062) CS From source image(s) of ANAP AUTO
derived content
Note: The value of this
attribute may come from
frame, image or series
level laterality attributes,
whichever is more
specific.
Units (0054,1001) CS Output units of modality LUT ANAP AUTO
rescale function, if modality of
source image(s) is PT

9.1.2 Usage of Attributes from Received IODs

No SOP Class specific fields are required.

Page 105
The internal database, remote query and directory browsers make use of the conventional identification
attributes to distinguish patients, studies, series and instances. In particular, if two patients have the same
value for Patient ID, they will be treated as the same in the browser and the internal database.

9.1.3 Attribute Mapping

Not applicable.

9.1.4 Coerced/Modified Fields

No coercion is performed.

9.2 DATA DICTIONARY OF PRIVATE ATTRIBUTES

No private attributes are defined.

9.3 CODED TERMINOLOGY AND TEMPLATES

Not applicable.

9.4 GRAYSCALE IMAGE CONSISTENCY

No specific support to ensure grayscale image consistency.

9.5 STANDARD EXTENDED/SPECIALIZED/PRIVATE SOP CLASSES

Secondary capture image SOP instances created by the application for the purposes of supporting key
images conform to a Standard Extended SOP Class based on the Secondary Capture Image Storage
SOP Class (1.2.840.10008.5.1.4.1.1.88.59). The contents of this Standard Extended SOP Class are
described in Section 8.1.1.5.

No specialized or private SOP classes are used.

9.6 PRIVATE TRANSFER SYNTAXES

No private transfer syntaxes are used.

Page 106