DICOM Conformance Statement

CXDI Control Software NE

Ver. 2.19

July 12, 2019

Rev 2.9
Notes and Disclaimers
• Reprinting, transmitting, or storing in a retrieval system any part of this document without the permission
of Canon is prohibited.
• Canon reserves the right to change the specifications of the product without prior notice.

Trademarks
• Ethernet is a trademark of Xerox Corporation.
• Windows is registered trademark of Microsoft Corporation in the United States and/or other countries.
• System and product names in this manual are the trademarks of each manufacturer that developed them.

2
Conformance Statement Overview

This product CXDI Control Software NE (hereinafter referred to as “CXDI NE”) implements the
necessary DICOM services to download work lists from an information system, save acquired
DX images, CR Images, and associated Presentation States to a network storage device or
Storage Medium, print to a networked hardcopy device and inform the information system
about the work actually done.

The table below provides an overview of the network services supported by CXDI NE.

Table 1
Network Services

SOP Classes User of Service (SCU) Provider of Service (SCP)

Transfer

Digital X-Ray Image Storage – For Presentation Yes No

Computed Radiography Image Storage Yes No

Grayscale Softcopy Presentation State Yes No

X-Ray Radiation Dose SR Yes No

Workflow Management

Modality Worklist Yes No

Storage Commitment Push Model Yes No

Modality Performed Procedure Step Yes No

Print Management

Basic Grayscale Print Management Yes No

Presentation LUT Yes No

Table 2 provides overview of the Media Storage Application Profiles supported by CXDI NE.

Table 2
Media Services

Write Files Read Files

Media Storage Application Profiles
(FSC or FSU) (FSR)

Compact Disk - Recordable

General Purpose CD-R Yes No

3
 Table of Contents

Conformance Statement Overview .................................................................................................................... 3

1. Introduction ................................................................................................................................................... 6
1.1 Revision History .................................................................................................................................... 6
1.2 Audience ............................................................................................................................................... 9
1.3 Remarks ................................................................................................................................................ 9
1.4 Terms and Definitions ............................................................................................................................ 9
1.5 Basics of DICOM Communication ...................................................................................................... 11
1.6 Abbreviations....................................................................................................................................... 11
1.7 References .......................................................................................................................................... 12
2. Networking .................................................................................................................................................. 13
2.1 Implementation Model ........................................................................................................................ 13
2.1.1 Application Data Flow ....................................................................................................................... 13
2.1.2 Functional Definition of AEs ..................................................................................................... 14
2.1.3 Sequencing of Real-World Activities ....................................................................................... 15
2.2 AE Specifications ................................................................................................................................ 17
2.2.1 Storage Application Entity Specification ................................................................................. 17
2.2.2 Workflow Application Entity Specification ............................................................................... 30
2.2.3 Hardcopy Application Entity Specification .............................................................................. 43
2.3 Network Interfaces .............................................................................................................................. 54
2.3.1 Physical Network Interface ...................................................................................................... 54
2.3.2 Additional Protocols ................................................................................................................. 54
2.3.3 IPv4 and IPv6 Support ............................................................................................................. 54
2.4 Configuration ....................................................................................................................................... 55
2.4.1 AE Title/Presentation Address Mapping .................................................................................. 55
2.4.2 Parameters ............................................................................................................................... 56
3. Media Interchange ....................................................................................................................................... 58
3.1 Implementation Model ........................................................................................................................ 58
3.1.1 Application Data Flow .............................................................................................................. 58
3.1.2 Functional Definition of AEs ..................................................................................................... 58
3.1.3 Sequencing of Real-World Activities ....................................................................................... 58
3.1.4 File Meta Information Options ................................................................................................. 58
3.2 AE Specifications ................................................................................................................................ 59
3.2.1 Media Application Entity Specification .................................................................................... 59
3.3 Augmented and Private Application Profiles ...................................................................................... 60
3.4 Media Configuration ............................................................................................................................ 60
4. Support of Character Sets .......................................................................................................................... 61
5. Security ........................................................................................................................................................ 62
6. Annexes ....................................................................................................................................................... 63
6.1 IOD Contents ....................................................................................................................................... 63
6.1.1 Created SOP Instances ........................................................................................................... 63
6.1.2 Used Fields in Received IOD by Application ........................................................................... 81
6.1.3 Attribute mapping .................................................................................................................... 81
6.1.4 Coerced/Modified Fields.......................................................................................................... 82
6.2 Data Dictionary of Private Attributes ................................................................................................... 82
6.3 Coded Terminology and Templates .................................................................................................... 82
6.4 Grayscale Image Consistency ............................................................................................................ 83
6.5 Standard Extended/Specialized/Private SOP Classes ....................................................................... 83

4
6.6 Private Transfer Syntaxes.................................................................................................................... 83
6.7 Structured Reports .............................................................................................................................. 83
6.7.1 Templates ................................................................................................................................. 83

5
1. Introduction

1.1 Revision History

Document Software
Date of Issue Description
Version Version
1.0 December 10, 2009 1.00 First issue
Error correction
Supported character sets added
Description of “Specific Character Set” changed
(Table 2.2-31, Table 6.1-27)
1.1 March 1, 2010 1.05
“Patient’s Birth Date” restriction added
(Table 2.2-31, Table 6.1-4)
“SOP Instance UID” changed (Table 6.1-31)
“Ethernet 1000BASE-T” added (Table 2.3-1)
Error correction
Descriptions added/changed
(Table 2.2-27, Table 2.2-31, Table 2.2-41,
Table 2.2-46, Table 6.1-1, Table 6.1-3, Table 6.1-7,
1.2 April 1, 2010 1.10
Table 6.1-10, Table 6.1-11, Table 6.1-16, Table 6.1-22,
Table 6.1-25, Table 6.1-27, Table 6.1-31)
New tables added
(Table 6.1-28)
Network Services added, Abbreviations added,
Supported character sets added
Description of “Specific Character Set” changed
(Table 2.2-31, Table 6.1-27)
Descriptions added/changed
(Table 2.2-1, Table 2.2-9, Table 2.2-27, Table 6.1-1,
1.3 September 1, 2010 1.20
Table 6.1-6, Table 6.1-7, Table 6.1-16, Table 6.1-17,
Table 6.1-18, Table 6.1-20, Table 6.1-22, Table 6.1-27,
Table 6.1-28)
New tables added
(Table 6.1-2, Table 6.1-15, Table 6.1-21, Table 6.1-23,
Table 6.1-24, Table 6.1-26, Table 6.1-29, Table 6.1-30)
3. Media Interchange added
Tag information added
(Table 2.2-10, Table 2.2-39, Table 2.2-40, Table 2.2-42,
Table 2.2-45, Table 2.2-47, Table 2.2-48, Table 2.2-50)
Descriptions added/changed/deleted
1.4 February 1, 2011 1.30 (Table 2.2-31, Table 2.2-39, Table 2.2-41, Table 2.2-46,
Table 2.2-49, Table 6.1-1, Table 6.1-2, Table 6.1-3,
Table 6.1-4, Table 6.1-5, Table 6.1-6, Table 6.1-7,
Table 6.1-9, Table 6.1-14, Table 6.1-15, Table 6.1-16,
Table 6.1-18, Table 6.1-19, Table 6.1-22, Table 6.1-24,
Table 6.1-27)
Error correction
Descriptions changed
(2.2.3.3.2.1 Description and Sequencing of Activities,
1.5 August 1, 2011 1.40 Correction substitution (Figure 2.2-7)
Descriptions added/changed
(Table 2.2-46, Table 2.2-49, Table 6.1-11, Table 6.1-21,
Table 6.1-24)
Descriptions of 2.2.2.3.2.3 added.
1.6 February 1, 2012 2.00 Descriptions added/changed/deleted
(Table 2.2-27, Table 2.2-31, Table 6.1-21, Table 6.1-28

6
 1. Introduction

Document Software
Date of Issue Description
Version Version
Descriptions added/changed/deleted
1.7 June 1, 2012 2.01
(Table 2.2-43)
Descriptions added/changed
(Conformance Statement Overview, 3.1.3, 3.2.1)
3.3 Augmented Private Application Profile added
1.8 September 21, 2012 2.02 3.4 Media Configuration added
Descriptions added/changed/deleted
(Table 1, Table 2, Table 6.1-18, Table 6.1-20,
Table 6.1-26)
Table number correction of error (Table 3.2-1, Table
3.2-2)
New tables added (Table 6.1-12)
Table changed number (Table 6.1-13, Table 6.1-14,
Table 6.1-15, Table 6.1-16, Table 6.1-17, Table 6.1-18,
Table 6.1-19, Table 6.1-20, Table 6.1-21, Table 6.1-22,
1.9 January 22, 2013 2.10 Table 6.1-23, Table 6.1-24, Table 6.1-25, Table 6.1-26,
Table 6.1-27, Table 6.1-28, Table 6.1-29, Table 6.1-30,
Table 6.1-31)
Descriptions added/changed
(Table 2.2-31, Table 6.1-1, Table 6.1-2, Table 6.1-3,
Table 6.1-7, Table 6.1-15, Table 6.1-18, Table 6.1-20,
Table 6.1-21, Table 6.1-26, Table 6.1-28, Table 6.1-30)
Error correction (Page-8 1.4 Terms and Definitions Tag,
Table 6.1-7, Table 6.1-17, Table 6.1-18, Table 6.1-30)
2.0 August 22, 2013 2.11
Descriptions added/changed
(Table 2.2-27)

Descriptions added/changed/deleted: Table 1, 1.6,

Figure 2.1-1, 2.1.3, Figure 2.1-2, Table 2.2-1, 2.2.1.3.2,
Figure 2.2-2, Table 2.2-9, Table 2.2-31, Table 6.1-1, Table
6.1-2, Table 6.1-3, Table 6.1-8, Table 6.1-15, Table 6.1-17,
Table 6.1-28, 6.1.3, 6.3, and 6.7
Table number correction: Table 6.1-5, Table 6.1-6, Table
6.1-7, Table 6.1-8, Table 6.1-9, Table 6.1-10, Table 6.1-11,
Table 6.1-12, Table 6.1-13, Table 6.1-14, Table 6.1-15,
2.1 March 7, 2014 2.12
Table 6.1-16, Table 6.1-17, Table 6.1-18, Table 6.1-19,
Table 6.1-20, Table 6.1-21, Table 6.1-22, Table 6.1-23,
Table 6.1-24, Table 6.1-25, Table 6.1-26, Table 6.1-27,
Table 6.1-28, Table 6.1-29, Table 6.1-30, and Table 6.1-35
New tables added: Table 6.1-4, Table 6.1-31, Table
6.1-32, Table 6.1-33, Table 6.1-34, Table 6.7-1, Table
6.7-2, Table 6.7-3, Table 6.7-4, Table 6.7-5, and Table
6.7-6

Error correction: Table 6.1-33 and Table 6.1-34

2.2 August 19, 2014 2.12
Descriptions added: Table 6.1-34

2.3 October 22, 2014 2.13 Descriptions added: Table 6.1-18

2.4 June 19, 2015 2.14 Software version number updated

2.5 October 21, 2015 2.15 Software version number updated

7
1. Introduction

Document Software
Date of Issue Description
Version Version
2.6 November 18, 2016 2.16 Software version number updated
Software version number updated
2.7 October 23, 2017 2.17
Description changed: 2.3.3
2.8 November 19, 2018 2.18 Software version number updated
Description changed.(Table 2.2-31, Table 2.4-1, Table
2.9 July 12, 2019 2.19
3.4-1, Table 6.1-8)

8
 1. Introduction

1.2 Audience
This document is written for the people that need to understand how CXDI NE will integrate into
their healthcare facility. This includes both those responsible for overall imaging network policy
and architecture, as well as integrators 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
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.

1.3 Remarks
The scope of this DICOM Conformance Statement is to facilitate integration between CXDI NE
and other DICOM products. The Conformance Statement should be read and understood in
conjunction with the DICOM Standard. DICOM by itself does not guarantee interoperability. The
Conformance Statement does, however, facilitate a first-level comparison for interoperability
between different applications supporting compatible DICOM functionality.

This Conformance Statement is not supposed to replace validation with other DICOM
equipment to ensure proper exchange of intended information. In fact, the user should be aware
of the following important issues:

— The comparison of different Conformance Statements is just the first step towards
assessing interconnectivity and interoperability between the product and other DICOM
conformant equipment.

— Test procedures should be defined and executed to validate the required level of
interoperability with specific compatible DICOM equipment, as established by the
healthcare facility.

CXDI NE has participated in an industry-wide testing program sponsored by Integrating the

Healthcare Enterprise (IHE). The IHE Integration Statement for CXDI NE, together with the IHE
Technical Framework, may facilitate the process of validation testing.

1.4 Terms and Definitions

Informal definitions are provided for the following terms used in this Conformance Statement.
The DICOM Standard is the authoritative source for formal definitions of these terms.

Abstract Syntax – the information agreed to be exchanged between applications, generally

equivalent to a Service/Object Pair (SOP) Class.
Examples: Verification SOP Class, Modality Worklist Information Model Find SOP Class,
Computed Radiography Image Storage SOP Class.

Application Entity (AE) – an end point of a DICOM information exchange, including the DICOM
network or media interface software; i.e., the software that sends or receives DICOM
information objects or messages. A single device may have multiple Application Entities.

Application Entity Title – the externally known name of an Application Entity, used to identify a
DICOM application to other DICOM applications on the network.

Application Context – the specification of the type of communication used between

Application Entities.
Example: DICOM network protocol.

9
1. Introduction

Association – a network communication channel set up between Application Entities.

Attribute – a unit of information in an object definition; a data element identified by a tag. The
information may be a complex data structure (Sequence), itself composed of lower level data
elements.
Examples: Patient ID (0010,0020), Accession Number (0008,0050), Photometric Interpretation
(0028,0004), Procedure Code Sequence (0008,1032).

Information Object Definition (IOD) – the specified set of Attributes that comprise a type of
data object; does not represent a specific instance of the data object, but rather a class of
similar data objects that have the same properties. The Attributes may be specified as
Mandatory (Type 1), Required but possibly unknown (Type 2), or Optional (Type 3), and there
may be conditions associated with the use of an Attribute (Types 1C and 2C).
Examples: MR Image IOD, CT Image IOD, Print Job IOD.

Module – a set of Attributes within an Information Object Definition that are logically related to
each other.
Example: Patient Module includes Patient Name, Patient ID, Patient Birth Date, and Patient Sex.

Negotiation – first phase of Association establishment that allows Application Entities to agree
on the types of data to be exchanged and how that data will be encoded.

Presentation Context – the set of DICOM network services used over an Association, as
negotiated between Application Entities; includes Abstract Syntaxes and Transfer Syntaxes.

Protocol Data Unit (PDU) – a packet (piece) of a DICOM message sent across the network.
Devices must specify the maximum size packet they can receive for DICOM messages.

Service Class Provider (SCP) – role of an Application Entity that provides a DICOM network
service; typically, a server that performs operations requested by another Application Entity
(Service Class User).
Examples: Picture Archiving and Communication System (image storage SCP, and image
query/retrieve SCP), Radiology Information System (modality worklist SCP).

Service Class User (SCU) – role of an Application Entity that uses a DICOM network service;
typically, a client.
Examples: imaging modality (image storage SCU, and modality worklist SCU), imaging
workstation (image query/retrieve SCU)

Service/Object Pair (SOP) Class – the specification of the network or media transfer (service)
of a particular type of data (object); the fundamental unit of DICOM interoperability specification.
Examples: Ultrasound Image Storage Service, Basic Grayscale Print Management.

Service/Object Pair (SOP) Instance – an information object; a specific occurrence of

information exchanged in a SOP Class.
Examples: a specific x-ray image.

Tag – a 32-bit identifier for a data element, represented as a pair of four digit hexadecimal
numbers, the “group” and the “element”. If the “group” number is odd, the tag is for a private
(manufacturer-specific) data element.
Examples: (0010,0020) [Patient ID], (7FE0,0010) [Pixel Data], (0019,0210) [private data element]

Transfer Syntax – the encoding used for exchange of DICOM information objects and
messages.
Examples: JPEG compressed (images), little endian explicit value representation.

Unique Identifier (UID) – a globally unique “dotted decimal” string that identifies a specific
object or a class of objects; an ISO-8824 Object Identifier.
Examples: Study Instance UID, SOP Class UID, SOP Instance UID.

10
 1. Introduction

Value Representation (VR) – the format type of an individual DICOM data element, such as text,
an integer, a person’s name, or a code. DICOM information objects can be transmitted with
either explicit identification of the type of each data element (Explicit VR), or without explicit
identification (Implicit VR); with Implicit VR, the receiving application must use a DICOM data
dictionary to look up the format of each data element.

1.5 Basics of DICOM Communication

This section describes terminology used in this Conformance Statement for the non-specialist.
The key terms used in the Conformance Statement are highlighted in italics below. This section
is not a substitute for training about DICOM, and it makes many simplifications about the
meanings of DICOM terms.

Two Application Entities (devices) that want to communicate with each other over a network
using DICOM protocol must first agree on several things during an initial network “handshake”.
One of the two devices must initiate an Association (a connection to the other device), and ask
if specific services, information, and encoding can be supported by the other device
(Negotiation).

DICOM specifies a number of network services and types of information objects, each of which
is called an Abstract Syntax for the Negotiation. DICOM also specifies a variety of methods for
encoding data, denoted Transfer Syntaxes. The Negotiation allows the initiating Application
Entity to propose combinations of Abstract Syntax and Transfer Syntax to be used on the
Association; these combinations are called Presentation Contexts. The receiving Application
Entity accepts the Presentation Contexts it supports.

For each Presentation Context, the Association Negotiation also allows the devices to agree on
Roles – which one is the Service Class User (SCU - client) and which is the Service Class
Provider (SCP - server). Normally the device initiating the connection is the SCU, i.e., the client
system calls the server, but not always.

The Association Negotiation finally enables exchange of maximum network packet (PDU) size,
security information, and network service options (called Extended Negotiation information).

The Application Entities, having negotiated the Association parameters, may now commence
exchanging data. Common data exchanges include queries for worklists and lists of stored
images, transfer of image objects and analyses (structured reports), and sending images to film
printers. Each exchangeable unit of data is formatted by the sender in accordance with the
appropriate Information Object Definition, and sent using the negotiated Transfer Syntax.
There is a Default Transfer Syntax that all systems must accept, but it may not be the most
efficient for some use cases. Each transfer is explicitly acknowledged by the receiver with a
Response Status indicating success, failure, or that query or retrieve operations are still in
process.

1.6 Abbreviations
AE Application Entity
AET Application Entity Title
CR Computed Radiography
CT Computed Tomography
DHCP Dynamic Host Configuration Protocol
DICOM Digital Imaging and Communications in Medicine

11
1. Introduction

DNS Domain Name System

DX Digital X-ray
GSDF Grayscale Standard Display Function
GSPS Grayscale Softcopy Presentation State
HIS Hospital Information System
IHE Integrating the Healthcare Enterprise
IOD Information Object Definition
IPv4 Internet Protocol version 4
ISO International Organization for Standardization
LDAP Lightweight Directory Access Protocol
LUT Look-up Table
MPPS Modality Performed Procedure Step
MSPS Modality Scheduled Procedure Step
MWL Modality Worklist
NTP Network Time Protocol
PACS Picture Archiving and Communication System
PDU Protocol Data Unit
RDSR X-ray Radiation Dose SR
RIS Radiology Information System
SCP Service Class Provider
SCU Service Class User
SOP Service-Object Pair
SPS Scheduled Procedure Step
SR Structured Reporting
TCP/IP Transmission Control Protocol/Internet Protocol
UL Upper Layer
VM Value Multiplicity
VR Value Representation

1.7 References
NEMA PS3 Digital Imaging and Communications in Medicine (DICOM) Standard, available free
at http://medical.nema.org/

12
2. Networking

2.1 Implementation Model

2.1.1 Application Data Flow
Remote
Application Entity Receives
Send Images & GSPS
Images & GSPS

Remote
Send Reports Application Entity Receives
Reports
Storage
Application
Entity
Remote
Send Commitment Application Entity Receives
Commitment

Verification
Verify
SCU or SCP

Remote
Application Entity
Update
Provides Worklist
Worklist
Items

Remote
Workflow
Acquire Application Entity
Application
Images Receives MPPS
Entity
Create / Update

Verify Verification
SCP

Remote
Send Film
Application Entity
Images &
Prints Film
PresentationLUT
Sheets
Hardcopy
Application
Entity

Verify
Verification
SCP

Figure 2.1-1
Application Data Flow Diagram

13
2. Networking

— The Storage Application Entity sends images and Presentation States and Structured
Reports to a remote AE. It is associated with the local real-world activity “Send Images &
GSPS” and “Send Reports”. “Send Images & GSPS” and “Send Reports” are performed
upon user request for each study completed or for specific images selected. When
activated by user’s settings (auto-send), each marked set of images and associated
Presentation States can be immediately stored to a preferred destination whenever a
Study is closed by the user. If the remote AE is configured as an archive device the
Storage AE will request Storage Commitment and if a commitment is successfully
obtained will record this information in the local database.

— The Workflow Application Entity receives Worklist information from and sends MPPS
information to a remote AE. It is associated with the local real-world activities “Update
Worklist” and “Acquire Images”. When the “Update Worklist” local real-world activity is
performed the Workflow Application Entity queries a remote AE for worklist items and
provides the set of worklist items matching the query request. “Update Worklist” is
performed as a result of an operator request. When the “Acquire Images” local real-world
activity is performed the Workflow Application Entity creates and updates Modality
Performed Procedure Step instances managed by a remote AE. Acquisition of images will
result in automated creation of an MPPS Instance. Completion of the MPPS is performed
as the result of an operator action.

— The Hardcopy Application Entity prints images on a remote AE (Printer). It is associated

with the local real-world activity “Film Images”. “Film Images” creates a print-job within
the print queue containing one virtual film sheets composed from images.

2.1.2 Functional Definition of AEs

2.1.2.1 Functional Definition of Storage Application Entity

The existence of a send-job queue entry with associated network destination will activate the
Storage AE. An association request is sent to the destination AE and upon successful
negotiation of a Presentation Context the image transfer is started. If the association cannot be
opened, the related send-job is set to an error state and can be restarted by the user via job
control interface. By default, the Storage AE will not try to initiate another association for this
send-job automatically.

2.1.2.2 Functional Definition of Workflow Application Entity

Worklist Update attempts to download a Worklist from a remote node. If the Workflow AE
establishes an Association to a remote AE, it will transfer all worklist items via the open
Association. During receiving the worklist response items are counted and the query processing
is canceled if the configurable limit of items is reached. The results will be displayed in a list,
which will be cleared with the next Worklist Update.

The Workflow AE performs the creation of an MPPS Instance automatically whenever

acquisition is started. Further updates on the MPPS data can be performed interactively from
the related MPPS user interface. The MPPS “Completed” or “Discontinued” states can only be
set from the user interface.

14
 2. Networking

2.1.2.3 Functional Definition of Hardcopy Application Entity

The existence of a print-job in the print queue will activate the Hardcopy AE. An association is
established with the printer and the printer’s status determined. If the printer is operating
normally, the film sheets described within the print-job will be printed. If the printer is not
operating normally, the print-job will set to an error state and can be restarted by the user via
the job control interface.

2.1.3 Sequencing of Real-World Activities

Department Image Report
Storage Hardcopy Workflow Printer
Scheduler Manager Server

1. Query Worklist

2. Receive Worklist

3. Select Workitem (MSPS)

4. Start Acquisition
(Create MPPS)

5. Acquire Images

6. Complete Acquisition
(Finalize MPPS)

7. Print Acquired Images

8. Store Acquired Images & GSPS

9. Commit Acquired Images & GSPS

10. Store RDSR

11. Commit RDSR

Figure 2.1-2
Sequencing Constraints

Under normal scheduled workflow conditions the sequencing constraints illustrated in Figure
2.1-2 apply:

1. Query Worklist

2. Receive Worklist of Modality Scheduled Procedure Steps (MSPS)

3. Select Workitem (MSPS) from Worklist

4. Start acquisition and create MPPS

15
2. Networking

5. Acquire Images

6. Complete acquisition and finalize MPPS

7. Print acquired images

8. Store acquired images and any associated Grayscale Softcopy Presentation State (GSPS)
instances.

9. If the Image Manager is configured as an archive device the Storage AE will request Storage
Commitment for the images and associated GSPS instances.

10. Store Structured Report (SR) instances.

11. If the Report Server is configured as an archive device the Storage AE will request Storage
Commitment for the SR instances.

Other workflow situations (e.g. unscheduled procedure steps) will have other sequencing
constraints. Printing could equally take place after the acquired images have been stored.
Printing could be omitted completely if no printer is connected or hardcopies are not required.

16
 2. Networking

2.2 AE Specifications

2.2.1 Storage Application Entity Specification

2.2.1.1 SOP Classes

CXDI NE provides Standard Conformance to the following SOP Classes:

Table 2.2-1
SOP Classes for AE Storage

SOP Class Name SOP Class UID SCU SCP

Digital X-Ray Image Storage-For 1.2.840.10008.5.1.4.1.1.1.1

Yes No
Presentation

Computed Radiography Image 1.2.840.10008.5.1.4.1.1.1

Yes No
Storage

Grayscale Softcopy Presentation 1.2.840.10008.5.1.4.1.1.11.1

Yes No
State Storage

Storage Commitment Push 1.2.840.10008.1.20.1

Yes No
Model

Verification 1.2.840.10008.1.1 Yes Yes

X-Ray Radiation Dose SR 1.2.840.10008.5.1.4.1.1.88.67 Yes No

2.2.1.2 Association Policies

2.2.1.2.1 General
The DICOM standard application context name for DICOM 3.0 is always proposed:

Table 2.2-2
DICOM Application Context for AE Storage

Application Context Name 1.2.840.10008.3.1.1.1

2.2.1.2.2 Number of Associations

CXDI NE initiates one Association at a time for each destination to which a transfer request is
being processed in the active job queue list. Only one job will be active at a time, the other
remains pending until the active job is completed or failed.

Table 2.2-3
Number of Associations Initiated for AE Storage

Maximum number of simultaneous Associations 1

CXDI NE accepts Associations to receive N-EVENT-REPORT notifications for the Storage

Commitment Push Model SOP Class.

Table 2.2-4
Number of Associations Accepted for AE Storage

Maximum number of simultaneous Associations 2

17
2. Networking

2.2.1.2.3 Asynchronous Nature

CXDI NE supports asynchronous communication (multiple outstanding transactions over a
single Association).

Table 2.2-5
Asynchronous Nature as a SCU for AE Storage

Maximum number of outstanding asynchronous

2
transactions

2.2.1.2.4 Implementation Identifying Information

The implementation information for this Application Entity is:

Table 2.2-6
DICOM Implementation Class and Version for AE Storage

Implementation Class UID 1.2.392.200046.100.14.xxxxx*

Implementation Version Name CXDI NE xxxxx*
*
xxxxx: Actually replaced by the version number

2.2.1.3 Association Initiation Policy

2.2.1.3.1 Activity – Verify

2.2.1.3.1.1 Description and Sequencing of Activities

The request for a verification is initiated by user interaction and the result is displayed on user
interface.

Verification Remote
SCU Verification SCP

1. Open Association

2. C-ECHO

3. Close Association

Figure 2.2-1
Sequencing of Activity – verify

1. The Verification SCU opens an association with the Remote Verification SCP.

2. Verification is transmitted to the Remote Verification SCP using a C-ECHO request and the
Remote Verification SCP replies with a C-ECHO response (status success).

3. The Verification SCU closes the association with the Remote Verification SCP.

18
 2. Networking

2.2.1.3.1.2 Proposed Presentation Contexts

The CXDI NE is capable of proposing the Presentation Contexts as shown in the following table:

Table 2.2-7
Proposed Presentation Context for Connectivity Verification

Presentation Context Table

Abstract Syntax Transfer Syntax Ext.
Role
Name UID Name List UID List Neg.

Verification 1.2.840.10008.1.1 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None

2.2.1.3.1.3 SOP Specific Conformance Verification SOP Class

The CXDI NE provides standard conformance to the DICOM Verification Service Class as an
SCU. The status code for the C-ECHO is as follows:

Table 2.2-8
C-ECHO Response Status Handling Behavior

Code Status Meaning

0000 Success The C-ECHO request is accepted.

Any other * The Association is released using A-RELEASE and the failure is
status code. reported to the user.

2.2.1.3.2 Activity – Send Images, Pres States, & Structured Reports

2.2.1.3.2.1 Description and Sequencing of Activities

A user can select images and presentation states and request them to be sent to multiple
destinations (up to 2). Each request is forwarded to the job queue and processed individually.
When the “Output Setting” option is active, each instance stored in database will be forwarded
to the network job queue for a pre-configured auto-send target destination. It can be configured
which instances will be automatically marked and the destination where the instances are
automatically sent to. The “Output Setting” is triggered by the End Exam. The transfer of
presentation states is optional.

The Storage AE is invoked by the job control interface that is responsible for processing
network archival tasks. The job consists of data describing the instances marked for storage
and the destination. An internal daemon process triggered by a job for a specific network
destination initiates a C-STORE request to store images. The output of the Image is only
P-Value. If the process successfully establishes an Association to a remote Application Entity, it
will transfer each instance via the open Association. Status of the transfer is reported through
the job control interface. Only one job will be active at a time. If the C-STORE Response from
the remote Application contains a status other than Success or Warning, the Association is
aborted and the related Job is switched to a failed state. It can be restarted any time by user
interaction.

The Storage AE attempts to initiate a new Association in order to issue a C-STORE request.

If the Remote AE is configured as an archive device the Storage AE will, after all images and
presentation states have been sent, transmit Storage Commitment request (N-ACTION) over a
separate association. Upon receiving the N-ACTION response the Storage AE will delay
releasing the Association for a configurable amount of time. If no N-EVENT-REPORT is received
within this time period the Association will be immediately released (i.e. notification of Storage
Commitment success or failure will be received over a separate association).

19
2. Networking

However, the Storage AE is capable of receiving an N-EVENT-REPORT request at any time

during an association provided a Presentation Context for the Storage Commitment Push
Model has been successfully negotiated (i.e. the N-ACTION is sent at the end of one
association and the N-EVENT-REPORT is received during an association initiated for a
subsequent send job or during an association initiated by the Remote AE for the specific
purpose of sending the N-EVENT-REPORT). Structured Reports are sent to remote AE in
separate association.

Storage Image Report

AE Manager Server

1. Open Association

2. C-STORE (Image)

3. Close Association

4. Open Association

5. N-ACTION (Storage Commitment Request for Image)

6. N-EVENT-REPORT (Storage Commitment Response)

7. Close Association

8. Open Association

9. C-STORE (GSPS)

10. Close Association

11. Open Association

12. N-ACTION (Storage Commitment Request for GSPS)

13. N-EVENT-REPORT (Storage Commitment Response)

14. Close Association

15. Open Association

16. C-STORE (RDSR)

17. Close Association

18. Open Association

19. N-ACTION (Storage Commitment Request for RDSR)

20. N-EVENT-REPORT (Storage Commitment Response)

21. Close Association

Figure 2.2-2
Sequencing of Activity – Send Images & Pres States

20
 2. Networking

A possible sequence of interactions between the Storage AE and an Image Manager (e.g. a
storage or archive device supporting the Storage and Storage Commitment SOP Classes as an
SCP) and Report Server (e.g. a storage or archive device supporting the Storage and Storage
Commitment SOP Classes as an SCP) is illustrated in Figure 2.2-2:

1. The Storage AE opens an association with the Image Manager.

2. An acquired image is transmitted to the Image Manager using a C-STORE request and the
Image Manager replies with a C-STORE response (status success).

3. The Storage AE closes the association with the Image Manager.

4. The Storage AE opens an association with the Image Manager.

5. An N-ACTION request is transmitted to the Image Manager to obtain storage commitment

of previously transmitted image. The Image Manager replies with an N-ACTION response
indicating the request has been received and is being processed.

6. The Image Manager immediately transmits an N-EVENT-REPORT request notifying the

Storage AE of the status of the Storage Commitment Request (sent in step 5 using the
N-ACTION message). The Storage AE replies with an N-EVENT-REPORT response
confirming receipt. The Image Manager could send this message at any time or omit it
entirely in favor of transmitting the N-EVENT-REPORT over a separate dedicated
association (see note).

7. The Storage AE closes the association with the Image Manager.

8. The Storage AE opens an association with the Image Manager.

9. An acquired GSPS is transmitted to the Image Manager using a C-STORE request and the
Image Manager replies with a C-STORE response (status success).

10. The Storage AE closes the association with the Image Manager.

11. The Storage AE opens an association with the Image Manager.

12. An N-ACTION request is transmitted to the Image Manager to obtain storage commitment
of previously transmitted GSPS. The Image Manager replies with an N-ACTION response
indicating the request has been received and is being processed.

13. The Image Manager immediately transmits an N-EVENT-REPORT request notifying the
Storage AE of the status of the Storage Commitment Request (sent in step 12 using the
N-ACTION message). The Storage AE replies with an N-EVENT-REPORT response
confirming receipt. The Image Manager could send this message at any time or omit it
entirely in favor of transmitting the N-EVENT-REPORT over a separate dedicated
association (see note).

14. The Storage AE closes the association with the Image Manager.

15. The Storage AE opens an association with the Report Server.

16. SR is transmitted to the Report Server using C-STORE request and the Report Server
replies with a C-STORE response (status success).

17. The Storage AE closes the association with the Report Server.

18. The Storage AE opens an association with the Report Server.

19. An N-ACTION request is transmitted to the Report Server to obtain storage commitment of
previously transmitted the SR. The replies with an N-ACTION response indicating the
request has been received and is being processed.

21
2. Networking

20. The Report Server immediately transmits an N-EVENT-REPORT request notifying the
Storage AE of the status of the Storage Commitment Request (sent in step 19 using the
N-ACTION message). The Storage AE replies with an N-EVENT-REPORT response
confirming receipt. The Report Server could send this message at any time or omit it entirely
in favor of transmitting the N-EVENT-REPORT over a separate dedicated association (see
note).

21. The Storage AE closes the association with the Report Server.

NOTE: Many other message sequences are possible depending on the number of images and
GSPS instances to be stored, support for Storage Commitment and when the SCP
sends the N-EVENT-REPORT. The N-EVENT-REPORT can also be sent over a separate
association initiated by the Image Manager (see Section 2.2.1.4.2 on Activity – Receive
Storage Commitment Response).

2.2.1.3.2.2 Proposed Presentation Contexts

CXDI NE is capable of proposing the Presentation Contexts shown in the following table:

Table 2.2-9
Proposed Presentation Contexts for Activity Send Images

Presentation Context Table

Abstract Syntax Transfer Syntax Ext.
Role
Name UID Name List UID List Neg.

Digital X-Ray Implicit VR Little Endian 1.2.840.10008.1.2

1.2.840.10008.5.
Image Storage-For Explicit VR Little Endian 1.2.840.10008.1.2.1 SCU None
1.4.1.1.1.1
Presentation Explicit VR Big Endian 1.2.840.10008.1.2.2
Computed Implicit VR Little Endian 1.2.840.10008.1.2
1.2.840.10008.5.
Radiography Explicit VR Little Endian 1.2.840.10008.1.2.1 SCU None
1.4.1.1.1
Image Storage Explicit VR Big Endian 1.2.840.10008.1.2.2
Grayscale
Implicit VR Little Endian 1.2.840.10008.1.2
Softcopy 1.2.840.10008.5.
Explicit VR Little Endian 1.2.840.10008.1.2.1 SCU None
Presentation State 1.4.1.1.11.1
Explicit VR Big Endian 1.2.840.10008.1.2.2
Storage
Storage Implicit VR Little Endian 1.2.840.10008.1.2
1.2.840.10008.1.
Commitment Push Explicit VR Little Endian 1.2.840.10008.1.2.1 SCU None
20.1
Model Explicit VR Big Endian 1.2.840.10008.1.2.2
Implicit VR Little Endian 1.2.840.10008.1.2
X-Ray Radiation 1.2.840.10008.5.
Explicit VR Little Endian 1.2.840.10008.1.2.1 SCU None
Dose SR 1.4.1.1.88.67
Explicit VR Big Endian 1.2.840.10008.1.2.2

A Presentation Context for the Storage Commitment Push Model will only be proposed if the
Remote AE is configured as an archive device.

22
 2. Networking

2.2.1.3.2.3 SOP Specific Conformance Image & Pres State Storage SOP Classes

All Image & Presentation State Storage SOP Classes supported by the Storage AE exhibit the
same behavior, except where stated, and are described together in this section.

The status meaning is logged and the job warning is reported to the user via the job control
application when receiving Event Type Image/GSPS failure. If images relating to GSPS in a send
job have status failure then the GPSP is not send.

The behavior of Storage AE when encountering status codes in a C-STORE response is

summarized in the Table below:

Table 2.2-10
Storage C-STORE Response Status Handling Behavior

Service
Further Meaning Error Code Behavior
Status
The SCP has successfully stored the SOP Instance.
Success Success 0000 If all SOP Instances in a send job have status
success then the job is marked as complete.
The Association is released using A-RELEASE and
the send job is marked as failed. The status meaning
Refused Out of Resources A700-A7FF is logged and the job failure is reported to the user
via the job control application. This is a transient
failure.
The Association is released using A-RELEASE and
Data Set does not the send job is marked as failed. The status meaning
Error A900-A9FF
match SOP Class is logged and the job failure is reported to the user
via the job control application.
The Association is released using A-RELEASE and
the send job is marked as failed. The status meaning
Error Cannot Understand C000-CFFF
is logged and the job failure is reported to the user
via the job control application.
Image transmission is considered successful. The
Coercion of Data
Warning B000 status meaning is logged and the job warning is
Elements
reported to the user via the job control application.
Image transmission is considered successful. The
Elements
Warning B006 status meaning is logged and the job warning is
Discarded
reported to the user via the job control application.
Image transmission is considered successful. The
Data Set does not
Warning B007 status meaning is logged and the job warning is
match SOP Class
reported to the user via the job control application.
The Association is released using A-RELEASE and
Any other the send job is marked as failed. The status meaning
* *
status code. is logged and the job failure is reported to the user
via the job control application.

Error Comment (0000,0902) and Error ID (0000,0903) are reported to the user via additional
information on error dialog.

23
2. Networking

The behavior of Storage AE during communication failure is summarized in the Table below:

Table 2.2-11
Storage Communication Failure Behavior

Exception
Behavior

The send job is marked as failed. The reason is

Timeout logged and the job failure is reported to the user via
the job control application.
The send job is marked as failed. The reason is
Association aborted by the SCP or network layers logged and the job failure is reported to the user via
the job control application.

A failed send job can be restarted by user interaction.

The contents of X-Ray Image Storage SOP Instances created by CXDI NE conform to the
DICOM X-Ray Image IOD definition and are described in section 6.1.

The contents of Grayscale Softcopy Presentation State Storage SOP Instances created by
CXDI NE conform to the DICOM Grayscale Softcopy Presentation State IOD and are described
in section 6.1.

Grayscale Softcopy Presentation State Storage SOP Instances are created upon user request
(e.g. explicitly via “End Exam”) in order to save the most recent visual appearance of an image.
Even If images from multiple studies are being displayed a separate Presentation State will be
created for each image.

When displaying an existing image the most recently saved Grayscale Softcopy Presentation
State containing references to the image will be automatically applied.

Grayscale Softcopy Presentation State Storage SOP Instances created by CXDI NE will only
reference instances of X-Ray Image Storage SOP Instances.

2.2.1.3.2.4 SOP Specific Conformance for Storage Commitment SOP Class

2.2.1.3.2.4.1 Storage Commitment Operations (N-ACTION)

The Storage AE will request storage commitment for instances of the X-Ray Image Storage SOP
Class and Grayscale Softcopy Presentation State Storage SOP Class if the Remote AE is
configured as an archive device and a presentation context for the Storage Commitment Push
Model has been accepted.

The Storage AE will consider Storage Commitment failed if no N-EVENT-REPORT is received for
a Transaction UID within a configurable time period after receiving a successful N-ACTION
response (duration of applicability for a Transaction UID)

24
 2. Networking

The behavior of Storage AE when encountering status codes in an N-ACTION response is

summarized in the Table below:

Table 2.2-12
Storage Commitment N-ACTION Response Status Handling Behavior

Service Further
Error Code Behavior
Status Meaning
The request for storage commitment is considered
successfully sent. A timer is started which will expire
Success Success 0000
if no N-EVENT-REPORT for the Transaction UID is
received within a configurable timeout period.
The Association is released using A-RELEASE and
Any other status the send job is marked as failed. The status meaning
* *
code. is logged and the job failure is reported to the user
via the job control application.

The behavior of Storage AE during communication failure is summarized in the Table below:

Table 2.2-13
Storage Commitment Communication Failure Behavior

Exception Behavior
The send job is marked as failed. The reason is
Timeout
logged and the job failure is reported to the user.
The send job is marked as failed. The reason is
Association aborted by the SCP or network layers
logged and the job failure is reported to the user.

25
2. Networking

2.2.1.3.2.4.2 Storage Commitment Notifications (N-EVENT-REPORT)

The Storage AE is capable of receiving an N-EVENT-REPORT notification if it has successfully

negotiated a Presentation Context for the Storage Commitment Push Model (i.e. only
associations established with archive devices).
Upon receipt of an N-EVENT-REPORT the timer associated with the Transaction UID will be
canceled.
The behavior of Storage AE when receiving Event Types within the N-EVENT-REPORT is
summarized in the Table below.

Table 2.2-14
Storage Commitment N-EVENT-REPORT Behavior

Event Type Event Type

Behavior
Name ID
The Referenced SOP Instance under Referenced SOP Sequence
(0008,1199) is marked within the database as “Stored & Committed
Storage
(SC)”. Successfully committed SOP Instances are candidates for
Commitment
1 automatic deletion from the local database if local resources become
Request
scarce. The conditions under which automatic deletion is initiated and
Successful
the amount of space freed are site configurable. The oldest SOP
Instances are deleted first.
The Referenced SOP Instances under Referenced SOP Sequence
(0008,1199) are treated in the same way as in the success case (Event
Storage
Type 1). The Referenced SOP Instances under Failed SOP Sequence
Commitment
(0008,1198) are marked within the database as “Store & Commit Failed
Request 2
(SF)”. The Failure Reasons are logged and the job failure is reported to
Complete –
the user via the job control application. A send job that failed storage
Failures Exist
commitment will not be automatically restarted but can be restarted by
user interaction.

The reasons for returning specific status codes in an N-EVENT-REPORT response are
summarized in the Table below.

Table 2.2-15
Storage Commitment N-EVENT-REPORT Response Status Reasons

Service Further
Error Code Reasons
Status Meaning
The storage commitment result has been
Success Success 0000
successfully received.
Invalid object The Transaction UID in the N-EVENT-REPORT
Failure 0117
instance request is not recognized.

26
 2. Networking

2.2.1.4 Association Acceptance Policy

2.2.1.4.1 Activity – Verify

2.2.1.4.1.1 Description and Sequencing of Activities

The Verification SCP will accept associations in order to receive C-ECHO request.

Verification Remote Verification

SCP SCU

1. Open Association

2. C-ECHO

3. Close Association

Figure 2.2-3
Sequencing of Activity – Verify

1. The Image Manager opens an association with the Storage AE.

2. Verification is transmitted to the Storage AE using a C-ECHO request and the Storage AE
replies with a C-ECHO response (status success).

3. The Image Manager closes the association with the Storage AE.

The result of C-ECHO is reported to the user via the message field.

2.2.1.4.1.2 Accepted Presentation Contexts

The CXDI NE will accept Presentation Contexts as shown in the Table below.

Table 2.2-16
Acceptable Presentation Contexts for
Connectivity Verification

Presentation Context Table

Abstract Syntax Transfer Syntax Ext.
Role
Name UID Name List UID List Neg.

Verification 1.2.840.10008.1.1 Implicit VR Little Endian 1.2.840.10008.1.2 SCP None

2.2.1.4.1.3 SOP Specific Conformance for Verification SOP Class

The Storage AE provides standard conformance to the Verification SOP Class as an SCP. If the
C-ECHO request was successfully received, a 0000 (Success) status code will be returned in
the C-ECHO response. Otherwise, Association will be aborted.

27
2. Networking

2.2.1.4.2 Activity – Receive Storage Commitment Response

2.2.1.4.2.1 Description and Sequencing of Activities

The Storage AE will accept associations in order to receive responses to a Storage

Commitment Request.

Storage AE Image Manager

1. Open Association

2. N-EVENT-REPORT (Storage Commitment Response)

3. Close Association

Figure 2.2-4
Sequencing of Activity – Receive Storage Commitment Response

A possible sequence of interactions between the Storage AE and an Image Manager (e.g. a
storage or archive device supporting Storage Commitment SOP Classes as an SCP) is
illustrated in the Figure above:

1. The Image Manager opens a new association with the Storage AE.

2. The Image Manager sends an N-EVENT-REPORT request notifying the Storage AE of the
status of a previous Storage Commitment Request. The Storage AE replies with an
N-EVENT-REPORT response confirming receipt.

3. The Image Manager closes the association with the Storage AE.

The Storage AE may reject association attempts as shown in the Table below. The Result,
Source and Reason/Diag columns represent the values returned in the appropriate fields of an
ASSOCIATE-RJ PDU (see PS 3.8, Section 9.3.4). The contents of the Source column is
abbreviated to save space and the meaning of the abbreviations are:

a) 1 – DICOM UL service-user

b) 2 – DICOM UL service-provider (ASCE related function)

c) 3 – DICOM UL service-provider (Presentation related function)

28
 2. Networking

Table 2.2-17
Association Rejection Reasons

Result Source Reason/Diag Explanation

The association request contained an
1 – rejected- 2 – protocol-version- unsupported protocol version. An association
b
permanent not-supported request with the same parameters will not
succeed at a later time.
The association request contained an
1 – rejected- 2 – application-context- unsupported Application Context Name. An
a
permanent name-not-supported association request with the same parameters
will not succeed at a later time.
The association request contained an
unrecognized Called AE Title. An association
request with the same parameters will not
succeed at a later time unless configuration
1 – rejected- 7 – called-AE-title-not-
a changes are made. This rejection reason
permanent recognized
normally occurs when the association initiator is
incorrectly configured and attempts to address
the association acceptor using the wrong AE
Title.
The association request contained an
unrecognized Calling AE Title. An association
request with the same parameters will not
1 – rejected- 3 – calling-AE-title-not- succeed at a later time unless configuration
a
permanent recognized changes are made. This rejection reason
normally occurs when the association acceptor
has not been configured to recognize the AE Title
of the association initiator.
The association request contained an
unrecognized SCP/SCU Role Selection
1 – rejected-
b 1 – no-reason-given Sub-Item. An association request with the same
permanent
parameters will not succeed at a later time unless
configuration changes are made.

2.2.1.4.2.2 Accepted Presentation Contexts

The Storage AE will accept Presentation Contexts as shown in the Table below.

Table 2.2-18
Acceptable Presentation Contexts for
Activity Receive Storage Commitment Response

Presentation Context Table

Abstract Syntax Transfer Syntax Ext.
Role
Name UID Name List UID List Neg.

Storage
Commitment 1.2.840.10008.1.20.1 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None
Push Model

Verification 1.2.840.10008.1.1 Implicit VR Little Endian 1.2.840.10008.1.2 SCP None

29
2. Networking

2.2.1.4.2.3 SOP Specific Conformance for Storage Commitment SOP Class

2.2.1.4.2.3.1 Storage Commitment Notifications (N-EVENT-REPORT)

Upon receipt of an N-EVENT-REPORT the timer associated with the Transaction UID will be
canceled.
The behavior of Storage AE when receiving Event Types within the N-EVENT-REPORT is
summarized in Table 2.2-14.
The reasons for returning specific status codes in an N-EVENT-REPORT response are
summarized in Table 2.2-15.

2.2.2 Workflow Application Entity Specification

2.2.2.1 SOP Classes

CXDI NE provides Standard Conformance to the following SOP Classes:

Table 2.2-19
SOP Classes for AE Workflow

SOP Class Name SOP Class UID SCU SCP

Modality Worklist Information Model – FIND 1.2.840.10008.5.1.4.31 Yes No

Modality Performed Procedure Step 1.2.840.10008.3.1.2.3.3 Yes No

2.2.2.2 Association Policies

2.2.2.2.1 General
The DICOM standard application context name for DICOM 3.0 is always proposed:

Table 2.2-20
DICOM Application Context for AE Workflow

Application Context Name 1.2.840.10008.3.1.1.1

2.2.2.2.2 Number of Associations

CXDI NE initiates one Association at a time for a Worklist request.

Table 2.2-21
Number of Associations Initiated for AE Workflow

Maximum number of simultaneous Associations 1

30
 2. Networking

2.2.2.2.3 Asynchronous Nature

CXDI NE does not support asynchronous communication (multiple outstanding transactions
over a single Association).

Table 2.2-22
Asynchronous Nature as a SCU for AE Workflow

Maximum number of outstanding asynchronous

N/A
transactions

2.2.2.2.4 Implementation Identifying Information

The implementation information for this Application Entity is:

Table 2.2-23
DICOM Implementation Class and Version for AE Workflow

Implementation Class UID 1.2.392.200046.100.14.xxxxx*

Implementation Version Name CXDI NE xxxxx*
*
xxxxx: Actually replaced by the version number

2.2.2.3 Association Initiation Policy

2.2.2.3.1 Activity – Verify

See 2.2.1.3.1.

2.2.2.3.2 Activity – Worklist Update

2.2.2.3.2.1 Description and Sequencing of Activities

The request for a Worklist Update is initiated by user interaction, i.e. pressing the buttons
“Refresh”/”Refresh Option”. With “Refresh Option” a dialog to enter search criteria is opened
and an interactive query can be performed.

The interactive Patient Worklist Query will display a dialog for entering data as search criteria.
When the Query is started on user request, only the data from the dialog will be inserted as
matching keys into the query.

Upon initiation of the request, the CXDI NE will build an Identifier for the C-FIND request, will
initiate an Association to send the request and will wait for Worklist responses. After retrieval of
all responses, CXDI NE will access the local database to add or update patient demographic
data. To protect the system from overflow, the CXDI NE will limit the number of processed
worklist responses to a configurable maximum. During receiving the worklist response items are
counted and the query processing is canceled by issuing a C-FIND-CANCEL if the configurable
limit of items is reached. The results will be displayed in a list, which will be cleared with the next
worklist update.

CXDI NE will initiate an Association in order to issue a C-FIND request according to the Modality
Worklist Information Model.

31
2. Networking

Department
Workflow AE Scheduler

1. Open Association

2. C-FIND Request (Worklist Query)

3. C-FIND Response (Worklist Item) – Status = Pending

4. C-FIND Response (Worklist Item) – Status = Pending

5. C-FIND Response – Status = Success

6. Close Association

7. Select Worklist Item

Figure 2.2-5
Sequencing of Activity – Worklist Update

A possible sequence of interactions between the Workflow AE and a Departmental Scheduler

(e.g. a device such as a RIS or HIS which supports the Modality Worklist SOP Class as an SCP)
is illustrated in the Figure above:

1. The Worklist AE opens an association with the Departmental Scheduler.

2. The Worklist AE sends a C-FIND request to the Departmental Scheduler containing the
Worklist Query attributes.

3. The Departmental Scheduler returns a C-FIND response containing the requested attributes
of the first matching Worklist Item.

4. The Departmental Scheduler returns another C-FIND response containing the requested
attributes of the second matching Worklist Item.

5. The Departmental Scheduler returns another C-FIND response with status “Success”
indicating that no further matching Worklist Items exist. This example assumes that only 2
Worklist items match the Worklist Query.

6. The Worklist AE closes the association with the Departmental Scheduler.

7. The user selects a Worklist Item from the Worklist and prepares to acquire new images.

32
 2. Networking

2.2.2.3.2.2 Proposed Presentation Contexts

CXDI NE will propose Presentation Contexts as shown in the following table:

Table 2.2-24
Proposed Presentation Contexts for Activity Worklist Update

Presentation Context Table

Abstract Syntax Transfer Syntax Ext.
Role
Name UID Name List UID List Neg.

Modality Worklist Implicit VR Little Endian 1.2.840.10008.1.2

1.2.840.10008.5.1
Information Model Explicit VR Little Endian 1.2.840.10008.1.2.1 SCU None
.4.31
– FIND Explicit VR Big Endian 1.2.840.10008.1.2.2

2.2.2.3.2.3 SOP Specific Conformance for Modality Worklist

The behavior of CXDI NE when encountering status codes in a Modality Worklist C-FIND
response is summarized in the Table below. If CXDI NE receives any other SCP response status
than “Success” or “Pending”, an error message will appear on the user interface.

Table 2.2-25
Modality Worklist C-FIND Response Status Handling Behavior

Service
Further Meaning Error Code Behavior
Status
Matching is The SCP has completed the matches. Worklist items
Success 0000
complete are available for display or further processing.
The Association is released using A-RELEASE. The
Refused Out of Resources A700
status meaning is logged and reported to the user.
Identifier does not The Association is released using A-RELEASE. The
Failed A900
match SOP Class status meaning is logged and reported to the user.
The Association is released using A-RELEASE. The
Failed Unable to Process C000 – CFFF
status meaning is logged and reported to the user.
If the query was cancelled due to too many worklist
items then the SCP has completed the matches.
Matching
Worklist items are available for display or further
Cancel terminated due to FE00
processing. Otherwise, the Association is released
Cancel request
using A-RELEASE. The status meaning is logged and
reported to the user.
Matches are FF00 The worklist item contained in the Identifier is collected
Pending
continuing for later display or further processing.
Matches are The worklist item contained in the Identifier is collected
continuing – for later display or further processing.
Warning that one
Pending FF01
or more Optional
Keys were not
supported
Any other The Association is released using A-RELEASE. The
* *
status code. status meaning is logged and reported to the user.

33
2. Networking

The behavior of CXDI NE during communication failure is summarized in the Table below.

Table 2.2-26
Modality Worklist Communication Failure Behavior

Exception Behavior
The worklist query is marked as failed. The reason is logged and
Timeout
reported to the user if an interactive query.
Association aborted by the SCP The worklist query is marked as failed. The reason is logged and
or network layers reported to the user if an interactive query.

Acquired images will always use the Study Instance UID specified for the Scheduled Procedure
Step (if available). If an acquisition is unscheduled, a Study Instance UID will be generated
locally.

The Table below provides a description of the CXDI NE Worklist Request Identifier and specifies
the attributes that are copied into the images. Unexpected attributes returned in a C-FIND
response are ignored.

Requested return attributes not supported by the SCP are set to have no value. Non-matching
responses returned by the SCP due to unsupported optional matching keys are ignored.

CXDI NE will automatically select the protocol according to the protocol item, which CXDI NE
received from the SCP. The protocol item’s TAG is configurable.

Table 2.2-27
Worklist Request Identifier

Module Name
Tag VR M R Q D IOD
Attribute Name
SOP Common
Specific Character Set (0008,0005) CS x
Scheduled Procedure Step
Scheduled Procedure Step Sequence (0040,0100) SQ x
> Modality (0008,0060) CS S x x x
> Requested Contrast Agent (0032,1070) LO x
> Scheduled Station AE Title (0040,0001) AE S x x
> Scheduled Procedure Step Start Date (0040,0002) DA R x x x
> Scheduled Procedure Step Start Time (0040,0003) TM R x x x
> Scheduled Performing Physician’s Name (0040,0006) PN S* x x
> Scheduled Procedure Step Description (0040,0007) LO x x x
> Scheduled Protocol Code Sequence (0040,0008) SQ x x
>> Code Value (0008,0100) CS x x
>> Coding Scheme Designator (0008,0102) SH x x
>> Coding Scheme Version (0008,0103) SH x x
>> Code Meaning (0008,0104) LO x x x
> Scheduled Procedure Step ID (0040,0009) SH x x x
> Scheduled Station Name (0040,0010) SH S x x
> Scheduled Procedure Step Location (0040,0011) SH S x x
> Pre-Medication (0040,0012) LO x

34
 2. Networking

Module Name
Tag VR M R Q D IOD
Attribute Name
Requested Procedure
Referenced Study Sequence (0008,1110) SQ x x
> Referenced SOP Class UID (0008,1150) UI x x
> Referenced SOP Instance UID (0008,1155) UI x x
Study Instance UID (0020,000D) UI x x x
Requested Procedure Description (0032,1060) LO x x x
Requested Procedure Code Sequence (0032,1064) SQ x x
> Code Value (0008,0100) CS x x
> Coding Scheme Designator (0008,0102) SH x x
> Coding Scheme Version (0008,0103) SH x x
> Code Meaning (0008,0104) LO x x
Requested Procedure ID (0040,1001) SH S x x x x
Reason for the Requested Procedure (0040,1002) LO
Requested Procedure Priority (0040,1003) SH
Patient Transport Arrangements (0040,1004) LO
Requested Procedure Location (0040,1005) LO
Requested Procedure Comments (0040,1400) LT
Imaging Service Request
Accession Number (0008,0050) SH S x x x x
Referring Physician’s Name (0008,0090) PN x x x
Requesting Physician (0032,1032) PN x x
Requesting Service (0032,1033) LO
Order Entered By (0040,2008) PN
Order Enterer’s Location (0040,2009) SH
Order Callback Phone Number (0040,2010) SH
Placer Order Number/Imaging Service Request (0040,2016) LO
Filler Order Number/Imaging Service Request (0040,2017) LO
Imaging Service Request Comments (0040,2400) LT
Visit Identification
Institution Name (0008,0080) LO
Institution Address (0008,0081) LO
Admission ID (0038,0010) LO
Issuer of Admission ID (0038,0011) LO
Visit Status
Visit Status ID (0038,0008) CS
Current Patient Location (0038,0300) LO
Patient’s Institution Residence (0038,0400) LO
Visit Comments (0038,4000) LT

35
2. Networking

Module Name
Tag VR M R Q D IOD
Attribute Name
Visit Admission
Referring Physician’s Address (0008,0092) ST
Referring Physician’s Telephone Numbers (0008,0094) SH
Admitting Diagnosis Description (0008,1080) LO
Route of Admissions (0038,0016) LO
Patient Identification
Patient Name (0010,0010) PN S* x x x x
Patient ID (0010,0020) LO S x x x x
Issuer of Patient ID (0010,0021) LO
Other Patient IDs (0010,1000) LO
Other Patient Names (0010,1001) PN
Patient’s Birth Name (0010,1005) PN
Patient’s Mother’s Birth Name (0010,1060) PN
Medical Record Locator (0010,1090) LO
Patient Demographic
Patient’s Birth Date (0010,0030) DA x x x
Patient’s Sex (0010,0040) CS x x x
Patient’s Age (0010,1010) AS
Patient’s Size (0010,1020) DS x x x
Patient’s Weight (0010,1030) DS x x x
Patient’s Address (0010,1040) LO
Military Rank (0010,1080) LO
Branch of Service (0010,1081) LO
Country of Residence (0010,2150) LO
Region of Residence (0010,2152) LO
Patient’s Telephone Numbers (0010,2154) SH
Ethnic Group (0010,2160) SH
Patient's Religious Preference (0010,21F0) LO
Patient Comments (0010,4000) LT
Confidentiality constraint on patient data (0040,3001) LO
Patient Medical
Medical Alerts (0010,2000) LO
Allergies (0010,2110) LO
Smoking Status (0010,21A0) CS
Additional Patient History (0010,21B0) LT
Pregnancy Status (0010,21C0) US x x
Special Needs (0038,0050) LO
Patient State (0038,0500) LO

36
 2. Networking

The above table should be read as follows:

Module Name:
The name of the associated module for supported worklist attributes.

Attribute Name:
Attributes supported to build a CXDI NE Worklist Request Identifier.

Tag: DICOM tag for this attribute.

VR: DICOM VR for this attribute.

M: Matching keys for Worklist Update. An “S” will indicate that CXDI NE will supply an
attribute value for Single Value Matching, an “R” will indicate Range Matching and a “*”
will denote wildcard matching.

R: Return keys. An “x” will indicate that CXDI NE will supply this attribute as Return Key with
zero length for Universal Matching.

Q: Interactive Query Key. An “x” will indicate that CXDI NE will supply this attribute as
matching key, if entered in the Query Patient Worklist dialog. For example, the Patient
Name can be entered thereby restricting Worklist responses to Procedure Steps
scheduled for the patient.

D: Displayed keys. An “x” indicates that this worklist attribute is displayed to the user during
a patient registration dialog. For example, Patient Name will be displayed when registering
the patient prior to an examination.

IOD: An “x” indicates that this Worklist attribute is included into all Object Instances created
during performance of the related Procedure Step.

37
2. Networking

2.2.2.3.3 Activity – Acquire Images

2.2.2.3.3.1 Description and Sequencing of Activities

After Patient registration, the CXDI NE is awaiting the 1st application of X-Ray Dose to the
patient. The trigger to create an MPPS SOP Instance is derived from this event. An Association
to the configured MPPS SCP system is established immediately and the related MPPS SOP
Instance will be created.

An MPPS Instance that has been sent with a state of “COMPLETED” or “DISCONTINUED” can
no longer be updated.

The CXDI NE will support creation of “unscheduled cases” by allowing MPPS Instances to be
communicated for locally registered Patients.

CXDI NE will initiate an Association to issue an:

— N-CREATE request according to the CREATE Modality Performed Procedure Step SOP
Instance.

— N-SET request to update the contents and state of the MPPS according to the SET
Modality Performed Procedure Step Information operation.

Department
Workflow AE
Scheduler

1. Open Association

2. N-CREATE (MPPS) – IN PROGRESS

3. Close Association

4. Acquire Images

5. Open Association

6. N-SET (MPPS) – COMPLETED

7. Close Association

Figure 2.2-6
Sequencing of Activity – Acquire Images

A possible sequence of interactions between the Workflow AE and a Departmental Scheduler

(e.g. a device such as a RIS or HIS which supports the MPPS SOP Class as an SCP) is
illustrated in Figure 2.2-6:

1. The Worklist AE opens an association with the Departmental Scheduler.

2. The Worklist AE sends an N-CREATE request to the Departmental Scheduler to create an

MPPS instance with status of “IN PROGRESS” and create all necessary attributes. The
Departmental Scheduler acknowledges the MPPS creation with an N-CREATE response
(status success).

38
 2. Networking

3. The Worklist AE closes the association with the Departmental Scheduler.

4. All images are acquired and stored in the local database.

5. The Worklist AE opens an association with the Departmental Scheduler.

6. The Worklist AE sends an N-SET request to the Departmental Scheduler to update the
MPPS instance with status of “COMPLETED” and set all necessary attributes.
The Departmental Scheduler acknowledges the MPPS update with an N-SET response
(status success).

7. The Worklist AE closes the association with the Departmental Scheduler.

2.2.2.3.3.2 Proposed Presentation Contexts

CXDI NE will propose Presentation Contexts as shown in the following table:

Table 2.2-28
Proposed Presentation Contexts for Real-World Activity Acquire Images

Presentation Context Table

Abstract Syntax Transfer Syntax Ext.
Role
Name UID Name List UID List Neg.

Modality Implicit VR Little Endian 1.2.840.10008.1.2

1.2.840.10008.
Performed Explicit VR Little Endian 1.2.840.10008.1.2.1 SCU None
3.1.2.3.3
Procedure Step Explicit VR Big Endian 1.2.840.10008.1.2.2

2.2.2.3.3.3 SOP Specific Conformance for MPPS

The behavior of CXDI NE when encountering status codes in an MPPS N-CREATE or N–SET
response is summarized in Table 2.2-29. If any other SCP response status than “Success” or
“Warning” is received by CXDI NE, an error message will appear on the user interface.

Table 2.2-29
MPPS N-CREATE / N-SET Response Status Handling Behavior

Service
Further Meaning Error Code Behavior
Status

Success Success 0000 The SCP has completed the operation successfully.

Processing Failure –
Performed The Association is released using A-RELEASE and the
Failure Procedure Step 0110 MPPS is marked as failed. The status meaning is
Object may no logged and reported to the user.
longer be updated
The MPPS operation is considered successful. The
Attribute Value Out
Warning 0116 status meaning is logged and the job warning is
of Range
reported to the user via the job control application.
The Association is released using A-RELEASE and the
Any other
* * MPPS is marked as failed. The status meaning is
status code.
logged and reported to the user.

39
2. Networking

The behavior of CXDI NE during communication failure is summarized in the Table below:

Table 2.2-30
MPPS Communication Failure Behavior

Exception Behavior
The send job is marked as failed. The reason is logged and the job
Timeout
failure is reported to the user via the job control application.
Association aborted by the SCP The MPPS is marked as failed. The reason is logged and reported to
or network layers the user.

Table 2.2-31 provides a description of the MPPS N-CREATE and N-SET request identifiers sent
by CXDI NE. Empty cells in the N-CREATE and N-SET columns indicate that the attribute is not
sent. A “Zero length” attribute will be sent with zero length.

Table 2.2-31
MPPS N-CREATE / N-SET Request Identifier

Attribute Name Tag VR N-CREATE N-SET

“ISO_IR 100”, “ISO_IR 101”, “ISO_IR 100”, “ISO_IR 101”,

“ISO_IR 110”, “ISO_IR 126”, “ISO_IR 110”, “ISO_IR 126”,
Specific Character “ISO_IR 144”, “ISO_IR 148”, “ISO_IR 144”, “ISO_IR 148”,
(0008,0005) CS
Set “ISO 2022 IR 13”, ”ISO 2022 IR 13”,
“ISO 2022 IR 87”, ”ISO 2022 IR 87”,
“GB18030”, “ISO_IR 192” ”GB18030”, ”ISO_IR 192”
Modality (0008,0060) CS “DX”, “CR”
Procedure Code
(0008,1032) SQ From Modality Worklist From Modality Worklist
Sequence
> Code Value (0008,0100) SH From Modality Worklist From Modality Worklist
> Coding Scheme
(0008,0102) SH From Modality Worklist From Modality Worklist
Designator
> Coding Scheme
(0008,0103) SH From Modality Worklist From Modality Worklist
Version
> Code Meaning (0008,0104) LO From Modality Worklist From Modality Worklist
Referenced Patient
(0008,1120) SQ Zero length
Sequence
From Modality Worklist or
Patient’s Name (0010,0010) PN user input (3 component
groups with 5 components)
From Modality Worklist or
Patient ID (0010,0020) LO
user input
From Modality Worklist or
user input.
Patient’s Birth Date (0010,0030) DA
Dates before the year 1753
cannot be input.
From Modality Worklist or
Patient’s Sex (0010,0040) CS
user input
Image and
Fluoroscopy Area (0018,115E) DS Total DAP
Dose Product

40
 2. Networking

Attribute Name Tag VR N-CREATE N-SET

Study ID (0020,0010) SH From Modality Worklist

Performed Station AE
(0040,0241) AE From configuration
Title
Performed Station
(0040,0242) SH Zero length
Name
Performed Location (0040,0243) SH Zero length
Performed Procedure
(0040,0244) DA Actual start date
Step Start Date
Performed Procedure
(0040,0245) TM Actual start time
Step Start Time
Performed Procedure
(0040,0250) DA Zero length Actual end date
Step End Date
Performed Procedure
(0040,0251) TM Zero length Actual end time
Step End Time
Performed Procedure “DISCONTINUED”,
(0040,0252) CS “IN PROGRESS”
Step Status “COMPLETED”
Performed Procedure
(0040,0253) SH Automatically created
Step ID
Performed Procedure
(0040,0254) LO User input User input
Step Description
Performed Procedure
(0040,0255) LO Zero length Zero length
Type Description
Performed Protocol
(0040,0260) SQ Zero length Zero or more items
Code Sequence
From Modality Worklist or user
> Code Value (0008,0100) SH
input
> Coding Scheme From Modality Worklist or “C
(0008,0102) SH
Designator Unique”
> Coding Scheme From Modality Worklist or not
(0008,0103) SH
Version send
From Modality Worklist or user
> Code Meaning (0008,0104) LO
input
Scheduled Step If 1st dose applied results in
(0040,0270) SQ
Attributes Sequence an Instance
From Modality Worklist or
> Accession Number (0008,0050) SH
user input
> Referenced Study
(0008,1110) SQ From Modality Worklist
Sequence
>> Referenced SOP
(0008,1150) UI From Modality Worklist
Class UID
>> Referenced SOP
(0008,1155) UI From Modality Worklist
Instance UID
> Study Instance UID (0020,000D) UI From Modality Worklist

41
2. Networking

Attribute Name Tag VR N-CREATE N-SET

> Requested
Procedure (0032,1060) LO From Modality Worklist
Description
> Scheduled
Procedure Step (0040,0007) LO From Modality Worklist
Description
> Scheduled Protocol
(0040,0008) SQ From Modality Worklist
Code Sequence
>> Code Value (0008,0100) SH From Modality Worklist
>> Coding Scheme
(0008,0102) SH From Modality Worklist
Designator
>> Coding Scheme
(0008,0103) SH From Modality Worklist
Version
>> Code Meaning (0008,0104) LO From Modality Worklist
> Scheduled
(0040,0009) SH From Modality Worklist
Procedure Step ID
> Requested
(0040,1001) SH From Modality Worklist
Procedure ID
Performed Procedure
Step Discontinuation
(0040,0281) SQ Zero or more items
Reason Code
Sequence
> Code Value (0008,0100) SH “110500”, ”110514”
> Coding Scheme
(0008,0102) SH “DCM”
Designator
“Doctor cancelled
> Code Meaning (0008,0104) LO procedure”, ”Incorrect worklist
entry selected”
Total Number of
(0040,0301) US Number of exposures
Exposures
Exposure Dose
(0040,030E) SQ Zero or more items
Sequence
> KVP (0018,0060) DS Generated by device
> Exposure Time (0018,1150) IS Generated by device
> X-Ray Tube Current (0018,1151) IS Generated by device
> Exposure (0018,1152) IS Generated by device
> Exposure in μAs (0018,1153) IS Generated by device
> Radiation Mode (0018,115A) CS “PULSED”
> X-Ray Tube Current
(0018,8151) DS Generated by device
in μA
Performed Series
(0040,0340) SQ Zero length One or more items
Sequence
> Retrieve AE Title (0008,0054) AE Zero length
> Series Description (0008,103E) LO User input
> Performing
(0008,1050) PN User input
Physician’s Name

42
 2. Networking

Attribute Name Tag VR N-CREATE N-SET

> Operator’s Name (0008,1070) PN User input

> Referenced Image
(0008,1140) SQ Zero or more items
Sequence
>> Referenced SOP “1.2.840.10008.5.1.4.1.1.1.1”
(0008,1150) UI
Class UID “1.2.840.10008.5.1.4.1.1.1”
>> Referenced SOP
(0008,1155) UI Automatically created
Instance UID
> Protocol Name (0018,1030) LO User input
> Series Instance UID (0020,000E) UI Automatically created
> Referenced
Non-Image
(0040,0220) SQ Zero or more items
Composite SOP
Instance Sequence
>> Referenced SOP “1.2.840.10008.5.1.4.1.1.11.1”
(0008,1150) UI
Class UID “1.2.840.10008.5.1.4.1.1.88.67”
>> Referenced SOP
(0008,1155) UI Automatically created
Instance UID
Entrance Dose in
(0040,8302) DS Generated by device
mGy

2.2.2.4 Association Acceptance Policy

The Workflow Application Entity does not accept Associations.

2.2.3 Hardcopy Application Entity Specification

2.2.3.1 SOP Classes

CXDI NE provides Standard Conformance to the following SOP Classes:

Table 2.2-32
SOP Classes for AE Hardcopy

SOP Class Name SOP Class UID SCU SCP

Basic Grayscale Print Management Meta 1.2.840.10008.5.1.1.9 Yes No

Presentation LUT 1.2.840.10008.5.1.1.23 Yes No

2.2.3.2 Association Policies

2.2.3.2.1 General
The DICOM standard application context name for DICOM 3.0 is always proposed:

Table 2.2-33
DICOM Application Context for AE Hardcopy

Application Context Name 1.2.840.10008.3.1.1.1

43
2. Networking

2.2.3.2.2 Number of Associations

CXDI NE initiates one Association at a time for each configured hardcopy device. Multiple
hardcopy devices can be configured.

Table 2.2-34
Number of Associations Initiated for AE Hardcopy

Maximum number of simultaneous Associations 1

2.2.3.2.3 Asynchronous Nature

CXDI NE does not support asynchronous communication (multiple outstanding transactions
over a single Association).

Table 2.2-35
Asynchronous Nature as a SCU for AE Hardcopy

Maximum number of outstanding asynchronous

N/A
transactions

2.2.3.2.4 Implementation Identifying Information

The implementation information for this Application Entity is:

Table 2.2-36
DICOM Implementation Class and Version for AE Hardcopy

Implementation Class UID 1.2.392.200046.100.14.xxxxx*

Implementation Version Name CXDI NE xxxxx*

*
xxxxx: Actually replaced by the version number

2.2.3.3 Association Initiation Policy

2.2.3.3.1 Activity – Verify

See 2.2.1.4.1.

2.2.3.3.2 Activity – Film Images

2.2.3.3.2.1 Description and Sequencing of Activities

A user composes images onto film sheets and requests them to be sent to a specific hardcopy
device. The user can select the desired film format. Each print-job is forwarded to the job queue
and processed individually.
The Hardcopy AE is invoked by the job control interface that is responsible for processing
network tasks. The job consists of data describing the images and graphics to be printed as
well as the requested layout and other parameters. The film sheet is internally processed,
converted to a STANDARD/1,1 page and then the page image is sent. If no association to the
printer can be established, the print-job is switched to a failed state and the user informed.

44
 2. Networking

Hardcopy AE Printer

1. Open Association

2. N-GET (Printer)

3. N-CREATE (Film Session)

Only P-Value
4. N-CREATE (Presentation LUT)

5. N-CREATE (Film Box)

6. N-SET (Image Box)

7. N-ACTION (Film Box)

8. Print film sheets

9. N-DELETE (Film Session)

10. Close Association

Figure 2.2-7
Sequencing of Activity – Film Images

A typical sequence of DIMSE messages sent over an association between Hardcopy AE and a
Printer is illustrated in Figure 2.2-7:

1. Hardcopy AE opens an association with the Printer.

2. N-GET on the Printer SOP Class is used to obtain current printer status information. If the
Printer reports a status of FAILURE, the print-job is switched to a failed state and the user
informed.

3. N-CREATE on the Film Session SOP Class creates a Film Session.

4. N-CREATE on the Presentation LUT SOP Class creates a Presentation LUT (if supported by
the printer).

5. N-CREATE on the Film Box SOP Class creates a Film Box linked to the Film Session. A
single Image Box will be created as the result of this operation. (Hardcopy AE only uses the
format STANDARD\1,1)

6. N-SET on the Image Box SOP Class transfers the contents of the film sheet to the printer.

7. N-ACTION on the Film Box SOP Class instructs the printer to print the Film Box.

8. The printer prints the requested number of film sheets.

9. N-DELETE on the Film Session SOP Class deletes the complete Film Session SOP Instance
hierarchy.

10. Hardcopy AE closes the association with the Printer.

45
2. Networking

Status of the print-job is reported through the job control interface. Only one job will be active at
a time. If any Response from the remote Application contains a status other than Success or
Warning, the Association is released and the related Job is switched to a failed state. It can be
restarted any time by user interaction.

2.2.3.3.2.2 Proposed Presentation Contexts

CXDI NE is capable of proposing the Presentation Contexts shown in the Table below:

Table 2.2-37
Proposed Presentation Contexts for Activity Film Images

Presentation Context Table

Abstract Syntax Transfer Syntax Ext.
Role
Name UID Name List UID List Neg.

Basic Grayscale Implicit VR Little Endian 1.2.840.10008.1.2

1.2.840.10008.5.
Print Management Explicit VR Little Endian 1.2.840.10008.1.2.1 SCU None
1.1.9
Meta Explicit VR Big Endian 1.2.840.10008.1.2.2
Implicit VR Little Endian 1.2.840.10008.1.2
1.2.840.10008.5.
Presentation LUT Explicit VR Little Endian 1.2.840.10008.1.2.1 SCU None
1.1.23
Explicit VR Big Endian 1.2.840.10008.1.2.2

2.2.3.3.2.3 Common SOP Specific Conformance for all Print SOP Classes
The general behavior of Hardcopy AE during communication failure is summarized in the Table
below. This behavior is common for all SOP Classes supported by Hardcopy AE.

Table 2.2-38
Hardcopy Communication Failure Behavior

Exception Behavior
The print-job is marked as failed. The reason is
Timeout logged and the job failure is reported to the user via
the job control application.
The print-job is marked as failed. The reason is
Association aborted by the SCP or network layers logged and the job failure is reported to the user via
the job control application.

2.2.3.3.2.4 SOP Specific Conformance for the Printer SOP Class

Hardcopy AE supports the following DIMSE operations and notifications for the Printer SOP
Class:

— N-GET

Details of the supported attributes and status handling behavior are described in the following
subsections.

46
 2. Networking

2.2.3.3.2.4.1 Printer SOP Class Operations (N-GET)

Hardcopy AE uses the Printer SOP Class N-GET operation to obtain information about the
current printer status. The attributes obtained via N-GET are listed in the Table below:

Table 2.2-39
Printer SOP Class N-GET Response Attributes

Presence
Attribute Name Tag VR Value Source
of Value

Printer Status (2110,0010) CS Provided by Printer ALWAYS Printer

Printer Status info (2110,0020) CS Provided by Printer ALWAYS Printer

The Printer Status information is evaluated as follows:

1. If Printer status (2110,0010) is NORMAL, the print-job continues to be printed.

2. If Printer status (2110,0010) is FAILURE, the print-job is marked as failed.

3. If Printer status (2110,0010) is WARNING, the print-job continues to be printed.

Printer Status (2110,0010) and Printer Status Info (2110,0020) are reported to the user via
additional information on error dialog if Print Status is FAILURE or WARNING.

The behavior of Hardcopy AE when encountering status codes in an N-GET response is

summarized in the Table below:

Table 2.2-40
Printer SOP Class N-GET Response Status Handling Behavior

Service Further
Error Code Behavior
Status Meaning

Success Success 0000 The request to get printer status information was success.

The Association is released using A-RELEASE and the send

Any other job is marked as failed. The status meaning is logged and
* * status code. the job failure is reported to the user via the job control
application.

Error Comment (0000,0902) and Error ID (0000,0903) are reported to the user via additional
information on error dialog.

2.2.3.3.2.5 SOP Specific Conformance for the Film Session SOP Class
Hardcopy AE supports the following DIMSE operations for the Film Session SOP Class:

— N-CREATE

— N-DELETE

Details of the supported attributes and status handling behavior are described in the following
subsections.

47
2. Networking

2.2.3.3.2.5.1 Film Session SOP Class Operations (N-CREATE)

The attributes supplied in an N-CREATE Request are listed in the Table below:

Table 2.2-41
Film Session SOP Class N-CREATE Request Attributes

Presence of
Attribute Name Tag VR Value Source
Value
Number of
(2000,0010) IS ANAP CONFIG
Copies
Print Priority (2000,0020) CS “HIGH”, “MED”, “LOW” ANAP CONFIG
“PAPER”, “CLEAR FILM”, “BLUE
Medium Type (2000,0030) CS ANAP CONFIG
FILM”
Film Destination (2000,0040) CS “MAGAZINE” or “PROCESSOR” ANAP CONFIG

The behavior of Hardcopy AE when encountering status codes in an N-CREATE response is

summarized in the Table below:

Table 2.2-42
Film Session SOP Class N-CREATE Response Status Handling Behavior

Service
Further Meaning Error Code Behavior
Status
Success Success 0000 The SCP has completed the operation successfully.
The Association is released using A-RELEASE. The
Failure Invalid Attribute Value 0106
status meaning is logged and reported to the user.
The Association is released using A-RELEASE. The
Failure Resource limitation 0213
status meaning is logged and reported to the user.
Memory allocation The N-CREATE operation is considered successful
Warning B600
not supported but the status meaning is logged.
The Association is released using A-RELEASE and
Any other the send job is marked as failed. The status
* * status code. meaning is logged and the job failure is reported to
the user via the job control application.

Error Comment (0000,0902) and Error ID (0000,0903) are reported to the user via additional
information on error dialog.

2.2.3.3.2.5.2 Film Session SOP Class Operations (N-DELETE)

The behavior of Hardcopy AE when encountering status codes in an N-DELETE response is

summarized in the Table below:

Table 2.2-43
Printer SOP Class N-DELETE Response Status Handling Behavior

Service
Further Meaning Error Code Behavior
Status
Success Success 0000 The SCP has completed the operation successfully.
The Association is released using A-RELEASE and
Any other
* * status code.
the send job is marked as failed. The status meaning
is only logged.

48
 2. Networking

2.2.3.3.2.6 SOP Specific Conformance for the Presentation LUT SOP Class
Hardcopy AE supports the following DIMSE operations for the Presentation LUT SOP Class:

— N-CREATE

Details of the supported attributes and status handling behavior are described in the following
subsections.

2.2.3.3.2.6.1 Presentation LUT SOP Class Operations (N-CREATE)

The attributes supplied in an N-CREATE Request are listed in the Table below:

Table 2.2-44
Presentation LUT SOP Class N-CREATE Request Attributes

Presence of
Attribute Name Tag VR Value Source
Value
Presentation
(2050,0020) CS “IDENTITY” ALWAYS AUTO
LUT Shape

The behavior of Hardcopy AE when encountering status codes in an N-CREATE response is

summarized in the Table below:

Table 2.2-45
Presentation LUT SOP Class N-CREATE Response Status Handling Behavior

Service Error
Further Meaning Behavior
Status Code

Success Success 0000 The SCP has completed the operation successfully.

Requested Min Density or

The N-CREATE operation is considered successful
Warning Max Density outside of B605
but the status meaning is logged.
printer’s operating range.
The Association is released using A-RELEASE and
Any other
the send job is marked as failed. The status
* * status
meaning is logged and the job failure is reported to
code.
the user via the job control application.

Error Comment (0000,0902) and Error ID (0000,0903) are reported to the user via additional
information on error dialog.

2.2.3.3.2.7 SOP Specific Conformance for the Film Box SOP Class
Hardcopy AE supports the following DIMSE operations for the Film Box SOP Class:

— N-CREATE

— N-ACTION

Details of the supported attributes and status handling behavior are described in the following
subsections.

49
2. Networking

2.2.3.3.2.7.1 Film Box SOP Class Operations (N-CREATE)

The attributes supplied in an N-CREATE Request are listed in the Table below:

Table 2.2-46
Film Box SOP Class N-CREATE Request Attributes

Presence
Attribute Name Tag VR Value Source
of Value

Image Display Format (2010,0010) CS “STANDARD\1,1” ALWAYS AUTO

Film Orientation (2010,0040) CS “PORTRAIT”, “LANDSCAPE” ALWAYS CONFIG
Film Size ID (2010,0050) CS ALWAYS CONFIG
“REPLICATE”, “BILINEAR”,
Magnification Type (2010,0060) CS ANAP CONFIG
“CUBIC”, “NONE”
Smoothing Type (2010,0080) CS ANAP CONFIG
Border Density (2010,0100) CS “BLACK”, “WHITE” ALWAYS CONFIG
Min Density (2010,0120) US ANAP CONFIG
Max Density (2010,0130) US ANAP CONFIG
Trim (2010,0140) CS “YES”, “NO” ANAP CONFIG
Configuration Information (2010,0150) ST ANAP CONFIG
Illumination (2010,015E) US ANAP CONFIG
Reflective Ambient Light (2010,0160) US ANAP CONFIG
Referenced Film Session
(2010,0500) SQ ALWAYS AUTO
Sequence
> Referenced SOP Class
(0008,1150) UI “1.2.840.10008.5.1.1.1” ALWAYS AUTO
UID
> Referenced SOP From created Film Session SOP
(0008,1155) UI ALWAYS AUTO
Instance UID Instance
Referenced Presentation
(2050,0500) SQ ALWAYS AUTO
LUT Sequence
> Referenced SOP Class
(0008,1150) UI “1.2.840.10008.5.1.1.23” ALWAYS AUTO
UID
> Referenced SOP From Created Presentation LUT
(0008,1155) UI ALWAYS AUTO
Instance UID SOP Instance

The behavior of Hardcopy AE when encountering status codes in an N-CREATE response is

summarized in the Table below:

Table 2.2-47
Film Box SOP Class N-CREATE Response Status Handling Behavior

Service Error
Further Meaning Behavior
Status Code
The SCP has completed the operation
Success Success 0000
successfully.
The N-CREATE operation is considered
Requested Min Density or Max Density
Warning B605 successful but the status meaning is
outside of printer’s operating range.
logged.
There is an existing Film Box that has The Association is released using
Failure not been printed and N-ACTION at the C616 A-RELEASE. The status meaning is
Film Session level is not supported. logged and reported to the user.

50
 2. Networking

Service Error
Further Meaning Behavior
Status Code
The Association is released using
Any other A-RELEASE and the send job is marked
* * status as failed. The status meaning is logged
code. and the job failure is reported to the
user via the job control application.

Error Comment (0000,0902) and Error ID (0000,0903) are reported to the user via additional
information on error dialog.

2.2.3.3.2.7.2 Film Box SOP Class Operations (N-ACTION)

An N-ACTION Request is issued to instruct the Print SCP to print the contents of the Film Box.
The Action Reply argument in an N-ACTION response is not evaluated.
The behavior of Hardcopy AE when encountering status codes in an N-ACTION response is
summarized in the Table below:

Table 2.2-48
Film Box SOP Class N-ACTION Response Status Handling Behavior

Service Error
Further Meaning Behavior
Status Code
The SCP has completed the operation
Success Success 0000 successfully. The film has been
accepted for printing.
Film Box SOP Instance hierarchy does The N-ACTION operation is considered
Warning not contain Image Box SOP Instances B603 successful but the status meaning is
(empty page) logged.
The N-ACTION operation is considered
Image size is larger than Image Box
Warning B604 successful but the status meaning is
size. The Image has been demagnified.
logged.
Image size is larger than the Image The N-ACTION operation is considered
Warning Box size. The Image has been cropped B609 successful but the status meaning is
to fit. logged.
Image size or Combined Print Image
The N-ACTION operation is considered
Size is larger than the Image Box size.
Warning B60A successful but the status meaning is
The Image or Combined Print Image
logged.
has been decimated to fit.
The Association is released using
Unable to create Print Job SOP A-RELEASE and the print-job is marked
Failure C602
Instance; print queue is full. as failed. The status meaning is logged
and reported to the user.
The Association is released using
Image size is larger than Image Box A-RELEASE and the print-job is marked
Failure C603
size. as failed. The status meaning is logged
and reported to the user.
The Association is released using
Combined Print Image Size is larger A-RELEASE and the print-job is marked
Failure C613
than the Image Box size. as failed. The status meaning is logged
and reported to the user.

51
2. Networking

Service Error
Further Meaning Behavior
Status Code
The Association is released using
Any other A-RELEASE and the send job is marked
* * status as failed. The status meaning is logged
code. and the job failure is reported to the
user via the job control application.

Error Comment (0000,0902) and Error ID (0000,0903) are reported to the user via additional
information on error dialog.

2.2.3.3.2.8 SOP Specific Conformance for the Image Box SOP Class
Hardcopy AE supports the following DIMSE operations for the Image Box SOP Class:

— N-SET

Details of the supported attributes and status handling behavior are described in the following
subsections.

2.2.3.3.2.8.1 Image Box SOP Class Operations (N-SET)

The attributes supplied in an N-SET Request are listed in the Table below:

Table 2.2-49
Image Box SOP Class N-SET Request Attributes

Presence of
Attribute Name Tag VR Value Source
Value

Image Box Position (2020,0010) US “1” ALWAYS AUTO

Requested Image Size (2020,0030) DS ALWAYS AUTO

Requested
(2020,0040) CS “DECIMATE”, “CROP”, “FAIL” ALWAYS CONFIG
Decimate/Crop Behavior

Basic Grayscale Image

(2020,0110) SQ ALWAYS AUTO
Sequence

> Samples Per Pixel (0028,0002) US “1” ALWAYS AUTO

> Photometric “MONOCHROME1”,

(0028,0004) CS ALWAYS CONFIG
Interpretation “MONOCHROME2”

> Rows (0028,0010) US ALWAYS AUTO

> Columns (0028,0011) US ALWAYS AUTO

> Bits Allocated (0028,0100) US “16” ALWAYS AUTO

> Bits Stored (0028,0101) US “12” ALWAYS AUTO

> High Bit (0028,0102) US “11” ALWAYS AUTO

> Pixel Representation (0028,0103) US “0” ALWAYS AUTO

> Pixel Data (7FE0,0010) OW Pixels of rendered film sheet ALWAYS AUTO

52
 2. Networking

The behavior of Hardcopy AE when encountering status codes in an N-SET response is

summarized in the Table below:

Table 2.2-50
Image Box SOP Class N-SET Response Status Handling Behavior

Service Error
Further Meaning Behavior
Status Code
The SCP has completed the operation
Success Success 0000 successfully. Image successfully stored
in Image Box.
The N-SET operation is considered
Image size is larger than Image Box
Warning B604 successful but the status meaning is
size. The image has been demagnified.
logged.
The N-SET operation is considered
Requested Min Density or Max Density
Warning B605 successful but the status meaning is
outside of printer’s operating range.
logged.
The N-SET operation is considered
Image size is larger than Image Box
Warning B609 successful but the status meaning is
size. The image has been cropped to fit.
logged.
Image size or Combined Print Image
The N-SET operation is considered
Size is larger than Image Box size. The
Warning B60A successful but the status meaning is
image or combined Print Image has
logged.
been decimated to fit.
The Association is released using
Image size is larger than Image Box A-RELEASE and the print-job is marked
Failure C603
size. as failed. The status meaning is logged
and reported to the user.
The Association is released using
Insufficient memory in printer to store A-RELEASE and the print-job is marked
Failure C605
the image. as failed. The status meaning is logged
and reported to the user.
The Association is released using
Combined Print Image Size is larger A-RELEASE and the print-job is marked
Failure C613
than Image Box size. as failed. The status meaning is logged
and reported to the user.
The Association is released using
Any other
A-RELEASE and the print-job is marked
* * status
as failed. The status meaning is logged
code.
and reported to the user.

Error Comment (0000,0902) and Error ID (0000,0903) are reported to the user via additional
information on error dialog.

2.2.3.4 Association Acceptance Policy

The Hardcopy Application Entity does not accept Associations.

53
2. Networking

2.3 Network Interfaces

2.3.1 Physical Network Interface

CXDI NE supports a single network interface. One of the following physical network interfaces
will be available depending on installed hardware options:

Table 2.3-1
Supported Physical Network Interfaces

Ethernet 1000baseT

Ethernet 100base-TX

Ethernet 10baseT

2.3.2 Additional Protocols

CXDI NE conforms to the System Management Profiles listed in the Table below. All requested
transactions for the listed profiles and actors are supported. Supports for optional transactions
are listed in the Table below:

Table 2.3-2
Supported System Management Profiles

Profile Name Actor Protocols Used Optional Transactions Security Support

Network Address DHCP Client DHCP N/A

Management DNS Client DNS N/A

Time NTP Client NTP

Synchronization DHCP Client DHCP N/A

2.3.3 IPv4 and IPv6 Support

This product supports both IPv4 and IPv6 connections.

54
 2. Networking

2.4 Configuration

2.4.1 AE Title/Presentation Address Mapping

2.4.1.1 Local AE Titles

All local applications use the AE Titles and TCP/IP Ports configured via the Service Tool.
The Field Service Engineer can configure the TCP Port via the Service Tool. The default AE Title
is “AETITLE” for all local AEs. The local AE Title used by each individual application can be
configured independently of the AE Title used by other local applications. If so configured, all
local AEs are capable of using the same AE Title.

Table 2.4-1
AE Title Configuration Table

Application Entity Default AE Title Default TCP/IP Port

Storage AETITLE Not Applicable

Workflow AETITLE Not Applicable

Hardcopy AETITLE Not Applicable

2.4.1.2 Remote AE Title/Presentation Address Mapping

The AE Title, host names and port numbers of remote applications are configured using the
CXDI user interface.

2.4.1.2.1 Storage
The CXDI NE Settings user interface must be used to set the AE Titles, port-numbers,
host-names and capabilities for the remote Storage SCPs. Associations will only be accepted
from known AE Titles and associations from unknown AE Titles will be rejected (an AE Title is
known if it can be selected within the Settings user interface). Multiple remote Storage SCPs
can be defined. Any Storage SCP can be configured to be an “Archive” device causing storage
commitment to be requested for images or presentation states transmitted to the device.

2.4.1.2.2 Workflow
The CXDI NE Settings user interface must be used to set the AE Title, port-number, host-name
and capabilities of the remote Modality Worklist SCP. Only a single remote Modality Worklist
SCP can be defined.

2.4.1.2.3 Hardcopy
The CXDI NE Settings user interface must be used to set the AE Titles, port-numbers,
host-names, IP-addresses and capabilities for the remote Print SCPs.
Multiple remote Print SCPs can be defined.

55
2. Networking

2.4.2 Parameters
A large number of parameters related to acquisition and general operation can be configured
using the Service Tool. The Table below only shows those configuration parameters relevant to
DICOM communication. See the CXDI NE Service Manual for details on general configuration
capabilities.

Table 2.4-2
Configuration Parameters Table

Configurable
Parameter Default Value
(Yes/No)

Storage Parameters
Supported Transfer Syntaxes (separately configurable for
Yes Implicit VR Little Endian
each remote AE)
Max PDU Length Yes 16384 Bytes
ARTIM time-out Yes 30 s
Send time-out Yes 60 s
Receive time-out Yes 60 s
Storage Commitment Parameters
Supported Transfer Syntaxes (separately configurable for
Yes Implicit VR Little Endian
each remote AE)
Max PDU Length Yes 16384 Bytes
Timeout waiting for a Storage Commitment Notification
(maximum duration of applicability for a Storage No ∞
Commitment Transaction UID).
ARTIM time-out Yes 30 s
Send time-out Yes 60 s
Receive time-out Yes 60 s
Modality Worklist Parameters
Supported Transfer Syntaxes (separately configurable for
Yes Implicit VR Little Endian
each remote AE)
Max PDU Length Yes 16384 Bytes
ARTIM time-out Yes 30 s
Send time-out Yes 60 s
Receive time-out Yes 60 s
MPPS Parameters
Supported Transfer Syntaxes (separately configurable for
Yes Implicit VR Little Endian
each remote AE)
Max PDU Length Yes 16384 Bytes
ARTIM time-out Yes 30 s
Send time-out Yes 60 s
Receive time-out Yes 60 s

56
 2. Networking

Configurable
Parameter Default Value
(Yes/No)
Print Parameters
Supported Transfer Syntaxes (separately configurable for
Yes Implicit VR Little Endian
each remote AE)
Max PDU Length Yes 16384 Bytes
ARTIM time-out Yes 30 s
Send time-out Yes 60 s
Receive time-out Yes 60 s

57
3. Media Interchange

3.1 Implementation Model

3.1.1 Application Data Flow

Media Application
Export to disc Storage Medium
Entity

Figure 3.1-1
Application Data Flow Diagram for Media Storage

— The Media Application Entity exports images and Presentation States to a Storage Medium.

3.1.2 Functional Definition of AEs

3.1.2.1 Functional Definition of Media Application Entity

Activation of the “Output setting” button entry will pass the currently patient, studies, series or
instances to the Media Application Entity. The SOP Instances associated with the selection will
be collected into one or more export jobs. The contents of each export job will be written to a
Storage Medium.

3.1.3 Sequencing of Real-World Activities

Store path is configured via the Service tool or System Setup Screen. Selected images will be
forwarded to the Storage Medium queue due to be triggered by send action if the Storage
Medium function is active.

3.1.4 File Meta Information Options

The implementation information written to the File Meta Header in each file is:

Table 3.1-1
DICOM Implementation Class and Version for Media Storage

Implementation Class UID 1.2.392.200046.100.14.xxxxx*

Implementation Version Name CXDI NE xxxxx*

*
xxxxx: Actually replaced by the version number

58
 3. Media Interchange

3.2 AE Specifications

3.2.1 Media Application Entity Specification

The Media Application Entity provides standard conformance to the Media Storage Service
Class.
The Application Profiles and roles are listed below:

Table 3.2-1
Application Profiles, Activities and Roles for Media

Application Profiles Supported Real World Activity Role

STD-GEN-CD Export to CD-R FSC

3.2.1.1 File Meta Information for Application Entity

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

3.2.1.2 Real-World Activities

3.2.1.2.1 Activity-Export to CD-R

The Media Application Entity acts as an FSC when requested to export SOP Instances from the
local database to a CD-R medium.

3.2.1.2.1.1 Media Storage Application Profiles

The Media Application Entity supports the STD-GEN-CD Application Profile.

3.2.1.2.1.1.1 Options

The Media Application Entity supports the SOP Classes and Transfer Syntax listed in the Table
below:

Table 3.2-2
IODs, SOP Classes and Transfer Syntaxes for Media

Information Object
SOP Class UID Transfer Syntax Transfer Syntax UID
Definition
Media Storage Directory
1.2.840.10008.1.3.10 Explicit VR Little Endian 1.2.840.10008.1.2.1
Storage
Digital X-Ray Image
Storage-For 1.2.840.10008.5.1.4.1.1.1.1 Explicit VR Little Endian 1.2.840.10008.1.2.1
Presentation
Computed Radiography
1.2.840.10008.5.1.4.1.1.1 Explicit VR Little Endian 1.2.840.10008.1.2.1
Image Storage
Grayscale Softcopy
Presentation State 1.2.840.10008.5.1.4.1.1.11.1 Explicit VR Little Endian 1.2.840.10008.1.2.1
Storage

59
3. Media Interchange

3.3 Augmented and Private Application Profiles

No Augmented and private Application Profiles are supported.

3.4 Media Configuration

The Table below only shows those configuration parameters relevant to the Media Application.

Table 3.4-1
Configuration Parameters Table

Configurable
Parameter Default Value
(Yes / No)

File-Set ID No C_C_DIR

60
4. Support of Character Sets

All CXDI NE DICOM applications support the following character sets in addition to the default:

ISO 2022 IR 6 (ISO 646)

ISO_IR 100 (ISO 8859-1: Latin Alphabet No.1 supplementary set)

ISO_IR 101 (ISO 8859-2: Latin Alphabet No.2 supplementary set)

ISO_IR 110 (ISO 8859-4: Latin Alphabet No.4 supplementary set)

ISO_IR 126 (ISO 8859-7: Greek)

ISO_IR 144 (ISO 8859-5: Cyrillic)

ISO_IR 148 (ISO 8859-9: Latin Alphabet No.5 supplementary set)

ISO 2022 IR 13 (JIS X 0201: Romaji, Katakana)

ISO 2022 IR 87 (JIS X 0208: Kanji)

GB18030

ISO_IR 192 (Unicode in UTF-8)

61
5. Security

CXDI NE does not support any specific security measures.

It is assumed that CXDI NE is used within a secured environment. It is assumed that a secured
environment includes at a minimum:

a) Firewall or router protections to ensure that only approved external hosts have network
access to CXDI NE.

b) Firewall or router protections to ensure that CXDI NE only has network access to approved
external hosts and services.

c) Any communication with external hosts and services outside the locally secured
environment use appropriate secure network channels (e.g. such as a Virtual Private
Network (VPN))

Other network security procedures such as automated intrusion detection may be appropriate
in some environments. Additional security features may be established by the local security
policy and are beyond the scope of this conformance statement.

62
6. Annexes

6.1 IOD Contents

6.1.1 Created SOP Instances

Table 6.1-1 and Table 6.1-2 specify the attributes of an X-Ray Image transmitted by the CXDI
NE storage application.

Table 6.1-3 specifies the attributes of a Grayscale Softcopy Presentation State transmitted by
the CXDI NE storage application.

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

VNAP Value Not Always Present (attribute sent zero length if no value is present)

ANAP Attribute Not Always Present

ALWAYS Always Present

EMPTY Attribute is sent without a value

The abbreviations used in the “Source” column:

MWL the attribute value source Modality Worklist

USER the attribute value source is from User input

AUTO the attribute value is generated automatically

MPPS the attribute value is the same as that use for Modality Performed Procedure
Step

CONFIG the attribute value source is a configurable parameter

NOTE: All dates and times are encoded in the local configured calendar and time. Date, Time
and Time zone are configured using the Windows Date and Time.

63
6. Annexes

6.1.1.1 X-Ray Image IOD

Table 6.1-1
IOD of Created DX SOP Instances

IE Module Reference Presence of Module

Patient Patient Table 6.1-5 ALWAYS

General Study Table 6.1-6 ALWAYS
Study
Patient Study Table 6.1-7 ALWAYS
General Series Table 6.1-8 ALWAYS
Series
DX Series Table 6.1-15 ALWAYS
Equipment General Equipment Table 6.1-17 ALWAYS
General Image Table 6.1-18 ALWAYS
Image Pixel Table 6.1-19 ALWAYS
DX Anatomy Imaged Table 6.1-20 ALWAYS
DX Image Table 6.1-21 ALWAYS
DX Detector Table 6.1-23 ALWAYS
Image
DX Positioning Table 6.1-25 ALWAYS
Acquisition Context Table 6.1-26 ALWAYS
SOP Common Table 6.1-28 ALWAYS
X-Ray Acquisition Dose Table 6.1-29 ALWAYS
X-Ray Grid Table 6.1-30 ALWAYS

Table 6.1-2
IOD of Created CR SOP Instances

IE Module Reference Presence of Module

Patient Patient Table 6.1-5 ALWAYS

General Study Table 6.1-6 ALWAYS
Study
Patient Study Table 6.1-7 ALWAYS
General Series Table 6.1-8 ALWAYS
Series
CR Series Table 6.1-16 ALWAYS
Equipment General Equipment Table 6.1-17 ALWAYS
General Image Table 6.1-18 ALWAYS
Image Pixel Table 6.1-19 ALWAYS
CR Image Table 6.1-22 ALWAYS
Image Modality LUT Table 6.1-24 ALWAYS
VOI LUT Table 6.1-27 ALWAYS
SOP Common Table 6.1-28 ALWAYS
Other Table 6.1-35 ALWAYS

64
 6. Annexes

6.1.1.2 Grayscale Softcopy Presentation State IOD

Table 6.1-3
IOD of Created Grayscale Softcopy Presentation State SOP Instances

IE Module Reference Presence of Module

Patient Patient Table 6.1-5 ALWAYS

General Study Table 6.1-6 ALWAYS
Study
Patient Study Table 6.1-7 ALWAYS
General Series Table 6.1-8 ALWAYS
Series
Presentation Series Table 6.1-9 ALWAYS
Equipment General Equipment Table 6.1-17 ALWAYS
Presentation State
Table 6.1-10 ALWAYS
Identification
Presentation State
Table 6.1-11 ALWAYS
Relationship

Presentation Displayed Area Table 6.1-12 ALWAYS

State Softcopy VOI LUT Table 6.1-13 ALWAYS
Softcopy Presentation LUT Table 6.1-14 ALWAYS
Modality LUT Table 6.1-24 ALWAYS
SOP Common Table 6.1-28 ALWAYS

6.1.1.3 X-Ray Radiation Dose SR IOD

Table 6.1-4
IOD of Created X-Ray Radiation Dose SR SOP Instances

IE
Module Reference Presence of Module

Patient Patient Table 6.1-5 ALWAYS

General Study Table 6.1-6 ALWAYS
Study
Patient Study Table 6.1-7 ALWAYS
Series SR Document Series Table 6.1-31 ALWAYS
General Equipment Table 6.1-17 ALWAYS
Equipment
Enhanced General Equipment Table 6.1-32 ALWAYS
SOP Common Table 6.1-28 ALWAYS
Document SR Document General Table 6.1-33 ALWAYS
SR Document Content Table 6.1-34 ALWAYS

65
6. Annexes

6.1.1.4 Modules
Table 6.1-5
Patient

Presence
Attribute Name Tag VR Value Source
of Value
From Modality Worklist or user
input. Values supplied via Modality
Worklist will be entered as received. MWL/
Patient’s Name (0010,0010) PN VNAP
Values supplied via user input will USER
contain 3 component groups with 5
components (some possibly empty).
MWL/
From Modality Worklist or user input
Patient ID (0010,0020) LO ALWAYS USER/
or generated by device
AUTO
From Modality Worklist or user
input. MWL/
Patient’s Birth Date (0010,0030) DA VNAP
Dates before the year 1753 cannot USER
be input.
MWL/
Patient’s Sex (0010,0040) CS From Modality Worklist or user input VNAP
USER
From user input or generated by USER/
Other Patient IDs (0010,1000) LO ANAP
device. AUTO
From user input or generated by USER/
Patient Comments (0010,4000) LT ANAP
device. AUTO

Table 6.1-6
General Study

Presence
Attribute Name Tag VR Value Source
of Value

Study Date (0008,0020) DA <yyyymmdd> ALWAYS AUTO

Study Time (0008,0030) TM <hhmmss.fff> ALWAYS AUTO
MWL/
Accession Number (0008,0050) SH From Modality Worklist or user input VNAP
USER
Referring Physician’s MWL/
(0008,0090) PN From Modality Worklist or user input VNAP
Name USER
Study Description (0008,1030) LO Comment text box in study list. ANAP USER
Procedure Code
(0008,1032) SQ From Modality Worklist ANAP MWL
Sequence
> Code Value (0008,0100) SH From Modality Worklist ANAP MWL
> Coding Scheme
(0008,0102) SH From Modality Worklist ANAP MWL
Designator
> Coding Scheme
(0008,0103) SH From Modality Worklist ANAP MWL
Version
> Code Meaning (0008,0104) LO From Modality Worklist ANAP MWL
Name of Physician (s) MWL/
(0008,1060) PN From Modality Worklist or user input ANAP
Reading Study USER

66
 6. Annexes

Presence
Attribute Name Tag VR Value Source
of Value
Referenced Study
(0008,1110) SQ From Modality Worklist ANAP MWL
Sequence
> Referenced SOP
(0008,1150) UI From Modality Worklist ANAP MWL
Class UID
> Referenced SOP
(0008,1155) UI From Modality Worklist ANAP MWL
Instance UID
From Modality Worklist or MWL/
Study Instance UID (0020,000D) UI ALWAYS
generated by device AUTO
From Modality Worklist or MWL/
Study ID (0020,0010) SH ALWAYS
generated by device AUTO

Table 6.1-7
Patient Study

Presence
Attribute Name Tag VR Value Source
of Value
From Modality Worklist or user input MWL/
Patient’s Age (0010,1010) AS or calculated from DoB input on ANAP USER/
base of actual Date AUTO
Patient's Size (0010,1020) DS From Modality Worklist ANAP MWL
Patient's Weight (0010,1030) DS From Modality Worklist ANAP MWL

Table 6.1-8
General Series

Presence
Attribute Name Tag VR Value Source
of Value

Series Date (0008,0021) DA <yyyymmdd> ALWAYS AUTO

Series Time (0008,0031) TM <hhmmss.fff> ALWAYS AUTO
“CR” (If this module is created by
DX image/GSPS, this attribute is
Modality (0008,0060) CS ALWAYS AUTO
included in DX series/Presentation
Series module.)
Organ from Study list. Maximum
Series Description (0008,103E) LO ANAP USER
512 characters.
Operator field in Study list.
Operator’s Name (0008,1070) PN ANAP USER
Maximum 64 characters.
Uniquely identifies the Performed
Procedure Step SOP Instance to
Referenced
which the Series is related.
Performed Procedure (0008,1111) SQ ANAP AUTO
(If this module is created by DX
Step Sequence
image, this attribute is included in
DX series module.)
> Referenced SOP
(0008,1150) UI “1.2.840.10008.3.1.2.3.3” ANAP AUTO
Class UID
> Referenced SOP
(0008,1155) UI MPPS SOP Instance UID ANAP AUTO
Instance UID

67
6. Annexes

Presence
Attribute Name Tag VR Value Source
of Value
Defined Terms are in PS3.16 Annex
Body Part Examined (0018,0015) CS ANAP AUTO
L.
Protocol Name (0018,1030) LO Organ program, “Unknown” ALWAYS AUTO
Series Instance UID (0020,000E) UI Generated by device ALWAYS AUTO
Series Number (0020,0011) IS Generated by device ALWAYS AUTO
“L”, “R”, empty (If this module is
created by DX image, this attribute
Laterality (0020,0060) CS ANAP AUTO
is included in DX Anatomy Imaged
module.)
Performed Procedure
(0040,0244) DA <yyyymmdd> ALWAYS AUTO
Step Start Date
Performed Procedure
(0040,0245) TM <hhmmss.fff> ALWAYS AUTO
Step Start Time
Performed Procedure
(0040,0253) SH Generated by device ALWAYS AUTO
Step ID
Performed Procedure
(0040,0254) LO User input ANAP AUTO
Step Description
Performed Protocol
(0040,0260) SQ From Modality Worklist ANAP MWL
Code Sequence
> Code Value (0008,0100) SH From Modality Worklist or user input ANAP MWL
> Coding Scheme From Modality Worklist or “C
(0008,0102) SH ANAP MWL
Designator Unique”
> Coding Scheme
(0008,0103) SH From Modality Worklist or not send ANAP MWL
Version
> Code Meaning (0008,0104) LO From Modality Worklist or user input ANAP MWL
Request Attributes
(0040,0275) SQ From Modality Worklist ANAP MWL
Sequence
> Requested
Procedure (0032,1060) LO From Modality Worklist ANAP MWL
Description
> Scheduled
Procedure Step (0040,0007) LO From Modality Worklist ANAP MWL
Description
> Scheduled Protocol
(0040,0008) SQ From Modality Worklist ANAP MWL
Code Sequence
>> Code Value (0008,0100) SH From Modality Worklist ANAP MWL
>> Coding Scheme
(0008,0102) SH From Modality Worklist ANAP MWL
Designator
>> Coding Scheme
(0008,0103) SH From Modality Worklist ANAP MWL
Version
>> Code Meaning (0008,0104) LO From Modality Worklist ANAP MWL
> Scheduled
(0040,0009) SH From Modality Worklist ANAP MWL
Procedure Step ID
> Requested
(0040,1001) SH From Modality Worklist ANAP MWL
Procedure ID

68
 6. Annexes

Table 6.1-9
Presentation Series

Presence
Attribute Name Tag VR Value Source
of Value

Modality (0008,0060) CS “PR” ALWAYS AUTO

Table 6.1-10
Presentation State Identification

Presence
Attribute Name Tag VR Value Source
of Value
Instance Number (0020,0013) IS Generated by device ALWAYS AUTO
Content Label (0070,0080) CS “CONTENTLABEL” ALWAYS AUTO
Content Description (0070,0081) LO “Content description” ALWAYS AUTO
Presentation Creation
(0070,0082) DA Generated by device ALWAYS AUTO
Date
Presentation Creation
(0070,0083) TM Generated by device ALWAYS AUTO
Time
Content Creator’s
(0070,0084) PN Generated by device VNAP AUTO
Name

Table 6.1-11
Presentation State Relationship

Presence
Attribute Name Tag VR Value Source
of Value
Referenced Series
(0008,1115) SQ One or more items. ALWAYS AUTO
Sequence
> Referenced Image
(0008,1140) SQ From referenced image ALWAYS AUTO
Sequence
>> Referenced SOP
(0008,1150) UI From referenced image ALWAYS AUTO
Class UID
>> Referenced SOP
(0008,1155) UI From referenced image ALWAYS AUTO
Instance UID
>> Referenced Frame If referenced image is a multi-frame
(0008,1160) IS ANAP AUTO
Number image
> Series Instance UID (0020,000E) UI From referenced image ALWAYS AUTO

Table 6.1-12
Displayed Area

Presence
Attribute Name Tag VR Value Source
of Value
Displayed Area
(0070,005A) SQ One or more items ALWAYS AUTO
Selection Sequence
> Referenced Image
(0008,1140) SQ One or more items ALWAYS AUTO
Sequence

69
6. Annexes

Presence
Attribute Name Tag VR Value Source
of Value
>> Referenced SOP
(0008,1150) UI From referenced image ALWAYS AUTO
Class UID
>> Referenced SOP
(0008,1155) UI From referenced image ALWAYS AUTO
Instance UID
>> Referenced Frame If referenced image is a multi-frame
(0008,1160) IS ANAP AUTO
Number image
> Displayed Area Top
(0070,0052) SL “1\1” ALWAYS AUTO
Left Hand Corner
> Displayed Area
Bottom Right Hand (0070,0053) SL From current display setting ALWAYS AUTO
Corner
> Presentation Size
(0070,0100) CS “SCALE TO FIT” ALWAYS AUTO
Mode
> Presentation Pixel “0.16\0.16”, “0.32\0.32”,
(0070,0101) DS ANAP AUTO
Spacing “0.125\0.125”

Table 6.1-13
Softcopy VOI LUT

Presence
Attribute Name Tag VR Value Source
of Value
Softcopy VOI LUT
(0028,3110) SQ One or more items ALWAYS AUTO
Sequence
AUTO/
> Window Center (0028,1050) DS 0～65536 ALWAYS
USER
AUTO/
> Window Width (0028,1051) DS 1～131072 ALWAYS
USER

Table 6.1-14
Softcopy Presentation LUT

Presence
Attribute Name Tag VR Value Source
of Value
Presentation LUT
(2050,0020) CS “IDENTITY” ALWAYS AUTO
Shape

70
 6. Annexes

Table 6.1-15
DX Series

Presence
Attribute Name Tag VR Value Source
of Value

Modality (0008,0060) CS “DX” ALWAYS AUTO

Identifies the intent of the images
Presentation Intent
(0008,0068) CS that are contained within this Series. ALWAYS AUTO
Type
FOR PRESENTATION
Referenced Uniquely identifies the Performed
Performed Procedure (0008,1111) SQ Procedure Step SOP Instance to ANAP AUTO
Step Sequence which the Series is related.
> Referenced SOP
(0008,1150) UI “1.2.840.10008.3.1.2.3.3” ANAP AUTO
Class UID
> Referenced SOP
(0008,1155) UI MPPS SOP Instance UID ANAP AUTO
Instance UID

Table 6.1-16
CR Series

Presence
Attribute Name Tag VR Value Source
of Value
Defined Terms are in PS3.16 Annex
Body Part Examined (0018,0015) CS VNAP AUTO
L.
“AP”, ”PA”, ”LL”, ”RL”, ”RLD”, ”LLD
View Position (0018,5101) CS VNAP AUTO
”, ”RLO”, ”LLO” ,empty

Collimator/Grid Name (0018,1180) SH Generated by device ANAP AUTO

Focal Spot (0018,1190) DS Generated by device ANAP AUTO

Table 6.1-17
General Equipment

Presence
Attribute Name Tag VR Value Source
of Value
“Canon Inc.”
(If this module is created by RDSR,
Manufacturer (0008,0070) LO this attribute is included in ALWAYS AUTO
Enhanced General Equipment
Module)
Institution Name (0008,0080) LO From Configuration ANAP CONFIG
Station Name (0008,1010) SH From Configuration ALWAYS CONFIG
“CXDI Control Software NE”
(If this module is created by RDSR,
Manufacturer’s Model
(0008,1090) LO this attribute is included in ALWAYS AUTO
Name
Enhanced General Equipment
Module)

71
6. Annexes

Presence
Attribute Name Tag VR Value Source
of Value
From Configuration
(If this module is created by RDSR,
Device Serial Number (0018,1000) LO this attribute is included in ALWAYS CONFIG
Enhanced General Equipment
Module)
From Configuration
(If this module is created by RDSR,
Software Version (0018,1020) LO this attribute is included in ALWAYS CONFIG
Enhanced General Equipment
Module)
The inherent limiting resolution in
mm of the acquisition equipment for
high contrast objects for the data
gathering and reconstruction
Spatial Resolution (0018,1050) DS technique chosen. If variable across ALWAYS AUTO
the images of the series, the value
at the image center.
(If this module is created by RDSR,
this attribute doesn’t appear.)
Last calibration date (If this module
Date of Last
(0018,1200) DA is created by GSPS and RDSR, this ANAP AUTO
Calibration
attribute doesn’t appear.)
Last calibration Time (If this module
Time of Last
(0018,1201) TM is created by GSPS and RDSR, this ANAP AUTO
Calibration
attribute doesn’t appear.)

Table 6.1-18
General Image

Presence
Attribute Name Tag VR Value Source
of Value

Acquisition Date (0008,0022) DA Generated by device ALWAYS AUTO

Acquisition Time (0008,0032) TM Generated by device ALWAYS AUTO
Instance Number (0020,0013) IS Generated by device ALWAYS AUTO

Generated by device (If this module

is created by DX image, this
Patient Orientation (0020,0020) CS ANAP AUTO
attribute is included in DX Image
module.)

Image Comments (0020,4000) LT From user input ANAP USER

“IDENTITY” (If this module is

Presentation LUT
(2050,0020) CS created by DX image, this attribute ANAP AUTO
Shape
is included in DX Image module.)

72
 6. Annexes

Table 6.1-19
Image Pixel

Presence
Attribute Name Tag VR Value Source
of Value
“1” (If this module is created by DX
Samples per Pixel (0028,0002) US image, this attribute is included in ANAP AUTO
DX Image module.)
Rows (0028,0010) US Vertical pixel number ALWAYS AUTO
Columns (0028,0011) US Horizontal pixel number ALWAYS AUTO
“16” (If this module is created by DX
Bits Allocated (0028,0100) US image, this attribute is included in ANAP AUTO
DX Image module.)
“12”, ”16” (If this module is created
Bits Stored (0028,0101) US by DX image, this attribute is ANAP AUTO
included in DX Image module.)
“11”, ”15” (If this module is created
High Bit (0028,0102) US by DX image, this attribute is ANAP AUTO
included in DX Image module.)
“0” (If this module is created by DX
Pixel Representation (0028,0103) US image, this attribute is included in ANAP AUTO
DX Image module.)
Pixel Data (7FE0,0010) OW Pixel Data ALWAYS AUTO

Table 6.1-20
DX Anatomy Imaged

Presence
Attribute Name Tag VR Value Source
of Value
Anatomic Region
(0008,2218) SQ Zero Length ALWAYS AUTO
Sequence
Laterality of (possibly paired) body part
(as described in Anatomic Region
Sequence (0008,2218)) examined.
Image Laterality (0020,0062) CS ALWAYS AUTO
Enumerated Values:
“R” = right, “L” = left, “U” = unpaired,
“B” = both left and right

Table 6.1-21
DX Image

Presence
Attribute Name Tag VR Value Source
of Value
“DERIVED\PRIMARY\”
Image Type (0008,0008) CS ALWAYS AUTO
“DERIVED\SECONDARY\”
Acquisition Device
(0018,1401) LO Generated by device ALWAYS AUTO
Processing Code
“A”(Anterior), “P”(Posterior),
Patient Orientation (0020,0020) CS “R”(Right), “L”(Left), “H”(Head), ALWAYS AUTO
“F”(Foot)
Samples per Pixel (0028,0002) US “1” ALWAYS AUTO

73
6. Annexes

Presence
Attribute Name Tag VR Value Source
of Value
Photometric
(0028,0004) CS “MONOCHROME2” ALWAYS AUTO
Interpretation

Bits Allocated (0028,0100) US “16” ALWAYS AUTO

Bits Stored (0028,0101) US “12”, ”16” ALWAYS AUTO

High Bit (0028,0102) US “11”, ”15” ALWAYS AUTO

Pixel Representation (0028,0103) US “0” ALWAYS AUTO

Burned In Annotation (0028,0301) CS “NO” ALWAYS AUTO

Pixel Intensity
(0028,1040) CS “LOG” ALWAYS AUTO
Relationship
Pixel Intensity
(0028,1041) SS “1” ALWAYS AUTO
Relationship Sign
AUTO/
Window Center (0028,1050) DS 0～65536 ALWAYS
USER
AUTO/
Window Width (0028,1051) DS 1～131072 ALWAYS
USER
Rescale Intercept (0028,1052) DS “0” ALWAYS AUTO
Rescale Slope (0028,1053) DS “1” ALWAYS AUTO
Rescale Type (0028,1054) LO “US” ALWAYS AUTO
Lossy Image
(0028,2110) CS “00” = NOT lossy compression ALWAYS AUTO
Compression
Presentation LUT
(2050,0020) CS “IDENTITY” ALWAYS AUTO
Shape

Table 6.1-22
CR Image

Presence
Attribute Name Tag VR Value Source
of Value
Photometric
(0028,0004) CS “MONOCHROME2” ALWAYS AUTO
Interpretation
KVP (0018,0060) DS Generated by device ANAP AUTO
Distance Source to AUTO/
(0018,1110) DS Generated by device or user input ANAP
Detector USER
Distance Source to AUTO/
(0018,1111) DS Generated by device or user input ANAP
Patient USER
Exposure Time (0018,1150) IS Generated by device ANAP AUTO
X-Ray Tube Current (0018,1151) IS Generated by device ANAP AUTO
Exposure (0018,1152) IS Generated by device ANAP AUTO
Exposure in μAs (0018,1153) IS Generated by device ANAP AUTO
Imager Pixel Spacing (0018,1164) DS Generated by device ALWAYS AUTO

74
 6. Annexes

Presence
Attribute Name Tag VR Value Source
of Value
Acquisition Device
(0018,1401) LO Generated by device ALWAYS AUTO
Processing Code
Relative X-Ray
(0018,1405) IS Generated by device ANAP AUTO
Exposure
Exposure Index (0018,1411) DS Generated by device ANAP AUTO
Target Exposure
(0018,1412) DS Generated by device ANAP AUTO
Index
Deviation Index (0018,1413) DS Generated by device ANAP AUTO
Pixel Spacing (0028,0030) DS Generated by device ANAP AUTO

Table 6.1-23
DX Detector

Presence
Attribute Name Tag VR Value Source
of Value

Imager Pixel Spacing (0018,1164) DS Generated by device ALWAYS AUTO

Detector Type (0018,7004) CS “SCINTILLATOR” ALWAYS AUTO

Detector
(0018,7005) CS “AREA” ALWAYS AUTO
Configuration
Detector ID (0018,700A) SH Generated by device ALWAYS AUTO
Date of Last Detector
(0018,700C) DA Last calibration date ALWAYS AUTO
Calibration
Time of Last Detector
(0018,700E) TM Last calibration Time ALWAYS AUTO
Calibration
Detector Binning (0018,701A) DS “1\1” ALWAYS AUTO
Pixel Spacing (0028,0030) DS Generated by device ANAP AUTO

Table 6.1-24
Modality LUT

Presence
Attribute Name Tag VR Value Source
of Value

Rescale Intercept (0028,1052) DS “0” ALWAYS AUTO

Rescale Slope (0028,1053) DS “1” ALWAYS AUTO
Rescale Type (0028,1054) LO “US” ALWAYS AUTO

75
6. Annexes

Table 6.1-25
DX Positioning

Presence
Attribute Name Tag VR Value Source
of Value
Distance Source to AUTO/
(0018,1110) DS Generated by device or user input ANAP
Detector USER
Distance Source to AUTO/
(0018,1111) DS Generated by device or user input ANAP
Patient USER
Positioner Type (0018,1508) CS ““ EMPTY AUTO
“AP”, ”PA”, ”LL”, ”RL”, ”RLD”, ”LLD”,
View Position (0018,5101) CS ANAP AUTO
“RLO”, ”LLO”

Table 6.1-26
Acquisition Context

Presence
Attribute Name Tag VR Value Source
of Value
Acquisition Context
(0040,0555) SQ Zero length ALWAYS AUTO
Sequence

Table 6.1-27
VOI LUT

Presence
Attribute Name Tag VR Value Source
of Value
AUTO/
Window Center (0028,1050) DS 0～65536 ALWAYS
USER
AUTO/
Window Width (0028,1051) DS 1～131072 ALWAYS
USER

Table 6.1-28
SOP Common

Presence
Attribute Name Tag VR Value Source
of Value
“ISO_IR 100”, “ISO_IR 101”,
“ISO_IR 110”, “ISO_IR 126”,
Specific Character
(0008,0005) CS “ISO_IR 144”, “ISO_IR 148”, “ISO ANAP CONFIG
Set
2022 IR 13”, “ISO 2022 IR 87”,
“GB18030”, “ISO_IR 192”
“1.2.840.10008.5.1.4.1.1.1.1” (DX),
“1.2.840.10008.5.1.4.1.1.1” (CR),
“1.2.840.10008.5.1.4.1.1.11.1”
SOP Class UID (0008,0016) UI ALWAYS AUTO
(GSPS),
“1.2.840.10008.5.1.4.1.1.88.67”
(RDSR)

SOP Instance UID (0008,0018) UI Generated by device ALWAYS AUTO

76
 6. Annexes

Table 6.1-29
X-ray Acquisition Dose

Presence
Attribute Name Tag VR Value Source
of Value

KVP (0018,0060) DS Generated by device ANAP AUTO

Exposure Time (0018,1150) IS Generated by device ANAP AUTO
X-Ray Tube Current (0018,1151) IS Generated by device ANAP AUTO
Exposure (0018,1152) IS Generated by device ANAP AUTO
Exposure in μAs (0018,1153) IS Generated by device ANAP AUTO
Image and
Fluoroscopy Area (0018,115E) DS Generated by device ANAP AUTO
Dose Product
Relative X-ray
(0018,1405) IS Generated by device ANAP AUTO
Exposure
Exposure Index (0018,1411) DS Generated by device ANAP AUTO
Target Exposure
(0018,1412) DS Generated by device ANAP AUTO
Index
Deviation Index (0018,1413) DS Generated by device ANAP AUTO
X-Ray Tube Current in
(0018,8151) DS Generated by device ANAP AUTO
μA
Entrance Dose in
(0040,8302) DS Generated by device ANAP AUTO
mGy

Table 6.1-30
X-ray Grid

Presence
Attribute Name Tag VR Value Source
of Value

Grid ID (0018,1006) LO Generated by device ANAP AUTO

Table 6.1-31
SR Document Series

Presence
Attribute Name Tag VR Value Source
of Value

Modality (0008,0060) CS “SR” ALWAYS AUTO

Series Instance UID (0020,000E) UI Generated by device ALWAYS AUTO

Series Number (0020,0011) IS “1” ALWAYS AUTO

Referenced Uniquely identifies the Performed

Performed Procedure (0008,1111) SQ Procedure Step SOP Instance to ANAP AUTO
Step Sequence which the Series is related.
> Referenced SOP
(0008,1150) UI “1.2.840.10008.3.1.2.3.3” ANAP AUTO
Class UID
> Referenced SOP
(0008,1155) UI MPPS SOP Instance UID ANAP AUTO
Instance UID

77
6. Annexes

Table 6.1-32
Enhanced General Equipment

Presence
Attribute Name Tag VR Value Source
of Value

Manufacturer (0008,0070) LO “Canon Inc.” ALWAYS AUTO

Manufacturer's Model
(0008,1090) LO “CXDI Control Software NE” ALWAYS AUTO
Name
Device Serial Number (0018,1000) LO From Configuration ALWAYS CONFIG
Software Versions (0018,1020) LO From Configuration ALWAYS CONFIG

Table 6.1-33
SR Document General

Presence
Attribute Name Tag VR Value Source
of Value

Instance Number (0020,0013) IS “1” ALWAYS AUTO

Completion Flag (0040,A491) CS “COMPLETE” ALWAYS AUTO
Verification Flag (0040,A493) CS “UNVERIFIED” ALWAYS AUTO
Content Date (0008,0023) DA <yyyymmdd> ALWAYS AUTO
Content Time (0008,0033) TM <hhmmss.fff> ALWAYS AUTO
The list of Requested Procedures
Referenced Request
(0040,A370) SQ the Procedure Step shall contribute ALWAYS AUTO
Sequence
to.
From Modality Worklist or generated MWL/
> Study Instance UID (0020,000D) UI ALWAYS
by device AUTO

Uniquely identifies the Study SOP

> Referenced Study
(0008,1110) SQ Instance that represents the VNAP MWL
Sequence
Requested Procedure.

>> Referenced SOP

(0008,1150) UI From Modality Worklist ANAP MWL
Class UID
>> Referenced SOP
(0008,1155) UI From Modality Worklist ANAP MWL
Instance UID
From Modality Worklist or generated MWL/
> Accession Number (0008,0050) SH VNAP
by device USER
> Requested
(0040,1001) SH From Modality Worklist VNAP MWL
Procedure ID
> Requested
Procedure (0032,1060) LO From Modality Worklist VNAP MWL
Description
> Requested A sequence that conveys the
Procedure (0032,1064) SQ Procedure Type of the Requested ALWAYS AUTO
Code Sequence Procedure.
> Placer Order
Number/Imaging (0040,2016) LO Zero length ALWAYS AUTO
Service Request
> Filler Order
Number/Imaging (0040,2017) LO Zero length ALWAYS AUTO
Service Request

78
 6. Annexes

Presence
Attribute Name Tag VR Value Source
of Value

A Sequence that conveys the codes

Performed Procedure
(0040,A372) SQ of the performed procedures VNAP MWL
Code Sequence
pertaining to this SOP Instance.

> Code Value (0008,0100) SH From Modality Worklist ANAP MWL

> Coding Scheme

(0008,0102) SH From Modality Worklist ANAP MWL
Designator

> Coding Scheme

(0008,0103) SH From Modality Worklist ANAP MWL
Version

> Code Meaning (0008,0104) LO From Modality Worklist ANAP MWL

Full set of Composite SOP

Instances, of which the creator is
Current Requested aware, which were created to satisfy
Procedure Evidence (0040,A375) SQ the current Requested Procedure(s) ANAP AUTO
Sequence for which this SR Document is
generated or that are referenced in
the content tree.

From Modality Worklist or generated

> Study Instance UID (0020,000D) UI ANAP AUTO
by device

Sequence of Items where each Item

> Referenced Series includes the Attributes of a Series
(0008,1115) SQ ANAP AUTO
Sequence containing referenced Composite
Object(s).

>> Series Instance

(0020,000E) UI Generated by device ANAP AUTO
UID

References to Composite Object

SOP Class/SOP Instance pairs that
>> Referenced SOP are part of the Study defined by
(0008,1199) SQ ANAP AUTO
Sequence Study Instance UID and the Series
defined by Series Instance UID
(0020,000E).

>>> Referenced SOP

(0008,1150) UI From referenced image ANAP AUTO
Class UID

>>> Referenced SOP

(0008,1155) UI Generated by device ANAP AUTO
Instance UID

Table 6.1-34
SR Document Content

Presence
Attribute Name Tag VR Value Source
of Value
Value Type (0040,A040) CS CONTAINER ALWAYS AUTO

79
6. Annexes

Presence
Attribute Name Tag VR Value Source
of Value
Code describing the concept
represented by this Content Item.
Concept Name Code
(0040,A043) SQ Also conveys the value of Document ALWAYS AUTO
Sequence
Title and section headings in
documents.
> Code Value (0008,0100) SH 113701 ALWAYS AUTO
> Coding Scheme
(0008,0102) SH DCM ALWAYS AUTO
Designator
> Code Meaning (0008,0104) LO X-Ray Radiation Dose Report ALWAYS AUTO
Continuity of Content (0040,A050) CS SEPARATE ALWAYS AUTO
Template that describes the content
Content Template
(0040,A504) SQ of this Content item and its ALWAYS AUTO
Sequence
subsidiary Content items.
> Mapping Resource (0008,0105) CS DCMR ALWAYS AUTO
> Template Identifier (0040,DB00) CS 10001 ALWAYS AUTO
Observation Date The date and item on which this
(0040,A032) DT ALWAYS AUTO
Time Content item was completed.
A potentially recursively nested
Sequence of Items that conveys
Content Sequence (0040,A730) SQ content that is the Target of ALWAYS AUTO
Relationships with the enclosing
Source Content Item.

Table 6.1-35
Other

Presence
Attribute Name Tag VR Value Source
of Value
Generated by device (If this module
Image and
is created by DX image, this
Fluoroscopy Area (0018,115E) DS ANAP AUTO
attribute is included in X-Ray
Dose Product
Acquisition Dose module.)
Generated by device (If this module
X-Ray Tube Current in is created by DX image, this
(0018,8151) DS ANAP AUTO
μA attribute is included in X-Ray
Acquisition Dose module.)
Generated by device (If this module
is created by DX image, this
Entrance Dose in mGy (0040,8302) DS ANAP AUTO
attribute is included in X-Ray
Acquisition Dose module.)

80
 6. Annexes

6.1.2 Used Fields in Received IOD by Application

The CXDI NE storage application does not receive SOP Instances. The usage of attributes
received via Modality Worklist is described in section 2.2.2.3.2.3.

6.1.3 Attribute mapping

The relationships between attributes received via Modality Worklist, stored in acquired images
and communicated via MPPS are summarized in Table 6.1-36.

Table 6.1-36
Attribute Mapping between Modality Worklist, Image and MPPS

Modality Worklist Image IOD MPPS IOD

Patient Name Patient Name Patient Name

Patient ID Patient ID Patient ID
Patient’s Birth Date Patient’s Birth Date Patient’s Birth Date
Patient’s Sex Patient’s Sex Patient’s Sex
Patient’s Size Patient’s Size
Patient’s Weight Patient’s Weight
Referring Physician’s Name Referring Physician’s Name
Scheduled Step Attributes
---- ----
Sequence
Study Instance UID Study Instance UID > Study Instance UID
Referenced Study Sequence Referenced Study Sequence > Referenced Study Sequence
Accession Number Accession Number > Accession Number
---- Request Attributes Sequence ----
Requested Procedure ID > Requested Procedure ID > Requested Procedure ID
> Requested Procedure > Requested Procedure
Requested Procedure Description
Description Description
Scheduled Procedure Step ID > Scheduled Procedure Step ID > Scheduled Procedure Step ID
Scheduled Procedure Step > Scheduled Procedure Step > Scheduled Procedure Step
Description Description Description
Scheduled Protocol Code > Scheduled Protocol Code > Scheduled Protocol Code
Sequence Sequence Sequence
Performed Protocol Code Performed Protocol Code
----
Sequence Sequence
Requested Procedure ID Study ID Study ID
Performed Procedure Step Start
---- Study Date
Date
Performed Procedure Step Start
---- Study Time
Time
Performed Procedure Step
---- Study Description
Description
---- Performed Procedure Step ID Performed Procedure Step ID
Performed Procedure Step Start Performed Procedure Step Start
----
Date Date

81
6. Annexes

Modality Worklist Image IOD MPPS IOD

Performed Procedure Step Start Performed Procedure Step Start
----
Time Time
Performed Procedure Step Performed Procedure Step
----
Description Description
Requested Procedure Code
Procedure Code Sequence Procedure Code Sequence
Sequence
Referenced Performed Procedure
---- ----
Step Sequence
---- > Referenced SOP Class UID SOP Class UID
---- > Referenced SOP Instance UID SOP Instance UID
---- ---- Performed Series Sequence
---- Protocol Name > Protocol Name
---- Series Description > Series Description
---- Series Instance UID > Series Instance UID
---- Operators' Name > Operators' Name
---- ---- > Referenced Image Sequence
---- SOP Class UID (Image) >> Referenced SOP Class UID
>> Referenced SOP Instance
---- SOP Instance UID (Image)
UID
> Referenced Non-Image
---- ---- Composite SOP Instance
Sequence
---- SOP Class UID (GSPS) >> Referenced SOP Class UID
>> Referenced SOP Instance
---- SOP Instance UID (GSPS)
UID

6.1.4 Coerced/Modified Fields

The Modality Worklist AE will reject attribute values received in the response to a Modality
Worklist Query if the value length is longer than the maximum length permitted by the attribute’s
VR.

6.2 Data Dictionary of Private Attributes

CXDI NE does not support private attribute.

6.3 Coded Terminology and Templates

The Workflow AE is capable of supporting arbitrary coding schemes for Protocol Codes. The
contents of Scheduled Protocol Code Sequence (0040,0008) supplied in Worklist Items will be
mapped to Image IOD and MPPS attributes as described in Table 6.1-36. A user will establish a
mapping between the site-specific codes and the Protocol Names used internally to identify
acquisition protocols.

82
 6. Annexes

6.4 Grayscale Image Consistency

The high resolution display monitor attached to the CXDI NE can be calibrated according to the
Grayscale Standard Display Function (GSDF). And the Image Consistency is achieved through
the support of the Presentation LUT.

6.5 Standard Extended/Specialized/Private SOP Classes

CXDI NE does not claim conformance to any Extended, Specialized or Private SOP Classes.

6.6 Private Transfer Syntaxes

CXDI NE does not support private transfer syntaxes.

6.7 Structured Reports

6.7.1 Templates

6.7.1.1 Projection X-Ray Radiation Dose

6.7.1.1.1 Template Structure

TID 10001 TID 1004

TID 1002
Projection X-Ray Radiation Device Observer
Observer Context
Dose Identifying Attributes

TID 10002 TID 10004

Accumulated X-Ray Dose ACCUMULATED
Data PROJECTION X-RAY DOSE

TID 10003
Irradiation Event X-Ray
Data

83
6. Annexes

6.7.1.1.1.1 TID 1002 Observer Context

Table 6.7-1
TID 1002 Observer Context

Presence
NL Rel with Parent VT Concept Name Value
of Value
EV (121005,DCM, EV (121007, DCM,
HAS OBS CONTEXT CODE ALWAYS
“Observer Type”) “Device”)
DTID (1004) Device
HAS OBS CONTEXT INCLUDE observer identifying ALWAYS
attributes

6.7.1.1.1.2 TID 1004 Device Observer Identifying Attributes

Table 6.7-2
TID 1004 Device Observer Identifying Attributes

Presence
NL Rel with Parent VT Concept Name Value
of Value
EV (121012,DCM, “Device Generated by
UIDREF ALWAYS
Observer UID”) Device
EV (121013,DCM, “Device
TEXT ALWAYS From Configuration
Observer Name”)
EV (121014,DCM, “Device
TEXT ALWAYS “Canon Inc.”
Observer Manufacturer”)
EV (121015,DCM, “Device “CXDI Control
TEXT ALWAYS
Observer Model Name”) Software NE”
EV (121016,DCM, “Device
TEXT ALWAYS From Configuration
Observer Serial Number”)

6.7.1.1.1.3 TID 10001 Projection X-Ray Radiation Dose

Table 6.7-3
TID 10001 Projection X-Ray Radiation Dose

Presence
NL Rel with Parent VT Concept Name Value
of Value
EV (113701, DCM, “X-Ray
CONTAINER ALWAYS
Radiation Dose Report”)
HAS CONCEPT EV (121058, DCM, DT (113704, DCM,
> CODE ALWAYS
MOD “Procedure reported”) “Projection X-Ray”)

HAS CONCEPT EV (G-C0E8, SRT, EV (R-408C3, SRT,

>> CODE ALWAYS
MOD “Has Intent”) “Diagnostic Intent”)

DTID (1002)
> INCLUDE ALWAYS
Observer Context
EV (113016, DCM,
EV (113705, DCM, “Scope
> HAS OBS CONTEXT CODE ALWAYS “Performed
of Accumulation”)
Procedure Step”)

84
 6. Annexes

Presence
NL Rel with Parent VT Concept Name Value
of Value
EV (121126, DCN,
Generated by
>> HAS PROPERTIES UIDREF Performed Procedure Step ALWAYS
Device
SOP Instance UID)
DTID (10002)
> CONTAINS INCLUDE ALWAYS
Accumulated X-Ray Dose
DTID (10003)
> CONTAINS INCLUDE ALWAYS
Irradiation Event X-Ray Data
EV (113856, DCM,
EV (113854, DCM, “Source
> CONTAINS CODE ALWAYS Automated Data
of Dose Information”)
Collection)

6.7.1.1.1.4 TID 10002 Accumulated X-Ray Dose Data

Table 6.7-4
Accumulated X-Ray Dose Data

Presence
NL Rel with Parent VT Concept Name Value
of Value
EV (113702, DCM,
CONTAINER “Accumulated X-Ray Dose ALWAYS
Data”)
HAS CONCEPT EV (113764, DCM, EV (113622, DCM,
> CODE ALWAYS
MOD “Acquisition Plane”) “Single Plane”)
DTID (10004) Accumulated
> CONTAINS INCLUDE ALWAYS
Projection X-Ray Dose

6.7.1.1.1.5 TID 10003 Irradiation Event X-Ray Data

Table 6.7-5
TID 10003 Irradiation Event X-Ray Data

Presence
NL Rel with Parent VT Concept Name Value
of Value
EV (113706, DCM,
CONTAINER “Irradiation Event X-Ray ALWAYS
Data”)
HAS CONCEPT EV (113764, DCM, EV (113622, DCM,
> CODE ALWAYS
MOD “Acquisition Plane” “Single Plane”)
DT (111526, DCM “Date Generated by
> CONTAINS DATETIME ALWAYS
Time Started”) device
EV (113611, DCM,
EV (113721, DCM,
> CONTAINS CODE ALWAYS “ Stationary
“Irradiation Event Type”)
Acquisition”)
EV (125203, DCM, Generated by
> CONTAINS TEXT ALWAYS
“Acquisition Protocol”) device
EV (113780, DCM,
> CONTAINS TEXT “Reference Point ALWAYS “Unknown”
Definition”)

85
6. Annexes

Presence
NL Rel with Parent VT Concept Name Value
of Value
EV (113769, DCM, Generated by
> CONTAINS UIDREF ALWAYS
“Irradiation Event UID”) device
EV (122130, DCM, Generated by
> CONTAINS NUM VNAP
“Dose Area Product”) device
EV (113738, DCM, Generated by
> CONTAINS NUM VNAP
“Dose (RP)”) device
EV (113768, DCM, Generated by
> CONTAINS NUM ANAP
“Number of Pulses”) device
Generated by
> CONTAINS NUM EV (113733, DCM, “KVP”) ANAP
device
EV (113734, DCM, Generated by
> CONTAINS NUM ANAP
“X-Ray Tube Current”) device
EV (113824, DCM, Generated by
> CONTAINS NUM ANAP
“Exposure Time”) device
EV (113736, DCM, Generated by
> CONTAINS NUM ANAP
“Exposure”) device
EV (113766, DCM, Generated by
> CONTAINS NUM ANAP
“Focal Spot Size”) device
DCID (4031)
EV (123014, DCM,
> CONTAINS CODE ALWAYS Common Anatomic
“Target Region”)
Regions
EV (113795, DCM, Generated by
> CONTAINS IMAGE ANAP
“Acquired Image”) device
EV (113845, DCM, Generated by
> CONTAINS NUM ANAP
“Exposure Index”) device
EV (113846, DCM, “Target Generated by
> CONTAINS NUM ANAP
Exposure Index”) device
EV (113847, DCM, Generated by
> CONTAINS NUM ANAP
“Deviation Index”) device

6.7.1.1.1.6 TID 10004 Accumulated Projection X-Ray Dose

Table 6.7-6
TID 10004 Accumulated Projection X-Ray Dose

Presence
NL Rel with Parent VT Concept Name Value
of Value
EV (113722, DCM, “Dose Generated by
NUM VNAP
Area Product Total”) device
EV (113725, DCM, “Dose Generated by
NUM VNAP
(RP) Total”) device
EV (113727, DCM,
Generated by
NUM “Acquisition Dose Area VNAP
device
Product Total”)
EV (113729, DCM,
Generated by
NUM “Acquisition Dose (RP) VNAP
device
Total”)

86
 6. Annexes

Presence
NL Rel with Parent VT Concept Name Value
of Value

EV (113855, DCM, “Total Generated by

NUM VNAP
Acquisition Time”) device

EV (113780, DCM,
TEXT “Reference Point ALWAYS “Unknown”
Definition”)

87
88
89
90
 *BT8-1617-E01*

CANON INC.
BT8-1617-E01 0719P0.001 © CANON INC. 2012–2019