DICOM Conformance Statement Azurion R3.

0
Doc Id: HSDP-1011216
Doc status: Approved

DICOM Conformance Statement

Azurion R3.0

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 1 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved

- This page is left intentionally empty -

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 2 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved

1 DICOM Conformance Statement Overview

Azurion R3.0 system is an interventional X-ray system that is used to perform:
 Image guidance during diagnostic, interventional and minimally invasive surgery procedures for the following clinical
application areas: vascular, non-vascular, cardiovascular and neuro procedures.
 Cardiac imaging applications including diagnostics, interventional and minimally invasive surgery procedures.
It provides the following DICOM data exchange features:
 Query the MWL SCP for a Modality Worklist (MWL)
 Update the Modality Performed Procedure Step (MPPS).
 Transfer of DICOM Images and Grayscale Presentation States.
 Query/Retrieve a Workstation or PACS for a list of entries representing Series information of DICOM Images
 Send Storage Commitment to the PACS (for the safe keeping of the previously transmitted images) and handling the Storage
Commitment notifications received from the PACS.
 Print Images on DICOM Printers
 Transfer of X-Ray Radiation Dose Structured Reports to the PACS or Workstation.

The system is verified as DIN 6862-2 compliant

Figure 1 : Data Flow of Azurion R3.0 in a DICOM Network

Table 1: Network Services

SOP Class User of Provider of

Service Service
Name UID (SCU) (SCP)
Other
Verification SOP Class 1.2.840.10008.1.1 Yes Yes
Print Management
Basic Grayscale Print Management Meta SOP Class 1.2.840.10008.5.1.1.9 Yes No
>Basic Film Session SOP Class 1.2.840.10008.5.1.1.1 Yes No
>Basic Film Box SOP Class 1.2.840.10008.5.1.1.2 Yes No
>Basic Grayscale Image Box SOP Class 1.2.840.10008.5.1.1.4 Yes No
>Printer SOP Class 1.2.840.10008.5.1.1.16 Yes No
Basic Color Print Management Meta SOP Class 1.2.840.10008.5.1.1.18 Yes No
>Basic Film Session SOP Class 1.2.840.10008.5.1.1.1 Yes No
>Basic Film Box SOP Class 1.2.840.10008.5.1.1.2 Yes No
 2022 Koninklijke Philips N.V.
SNIP-IOCC-T-020001.09 (Version 2.2) Page 3 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved

SOP Class User of Provider of

Service Service
Name UID (SCU) (SCP)
>Basic Color Image Box SOP Class 1.2.840.10008.5.1.1.4.1 Yes No
>Printer SOP Class 1.2.840.10008.5.1.1.16 Yes No
Query/Retrieve
Patient Root QR Information Model - FIND SOP Class 1.2.840.10008.5.1.4.1.2.1.1 Yes No
Study Root QR Information Model - FIND SOP Class 1.2.840.10008.5.1.4.1.2.2.1 Yes No
Patient Root QR Information Model - MOVE SOP Class 1.2.840.10008.5.1.4.1.2.1.2 Yes No
Study Root QR Information Model - MOVE SOP Class 1.2.840.10008.5.1.4.1.2.2.2 Yes No
Transfer
Secondary Capture Image Storage SOP Class 1.2.840.10008.5.1.4.1.1.7 Yes Yes
Grayscale Softcopy Presentation State Storage SOP Class 1.2.840.10008.5.1.4.1.1.11.1 Yes Yes
X-Ray Angiographic Image Storage SOP Class 1.2.840.10008.5.1.4.1.1.12.1 Yes Yes
X-Ray Radiation Dose Structured Report SOP Class 1.2.840.10008.5.1.4.1.1.88.67 Yes No
Workflow Management
Storage Commitment Push Model SOP Class 1.2.840.10008.1.20.1 Yes No
Modality Performed Procedure Step SOP Class 1.2.840.10008.3.1.2.3.3 Yes No
Modality Worklist Information Model - FIND SOP Class 1.2.840.10008.5.1.4.31 Yes No

A table of Supported Media Storage Application Profiles (with roles) is provided.

Table 2: Media Services

File-set
File-set Creator File-set Reader
Media Storage Application Profile Updater
(FSC) (FSR)
(FSU)
Compact disk-Recordable
General Purpose CD-R Interchange Yes No Yes
DVD-RAM
General Purpose Interchange on DVD-RAM Media Yes No Yes
USB
General Purpose USB Media Yes Yes Yes

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 4 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved

2 Table of Contents
1 DICOM CONFORMANCE STATEMENT OVERVIEW ............................................................................... 3
2 TABLE OF CONTENTS ............................................................................................................................. 5
3 INTRODUCTION ........................................................................................................................................ 8
3.1 REVISION HISTORY ............................................................................................................................. 8
3.2 AUDIENCE ............................................................................................................................................ 8
3.3 REMARKS ............................................................................................................................................. 8
3.4 DEFINITIONS, TERMS AND ABBREVIATIONS ................................................................................... 9
3.5 REFERENCES ....................................................................................................................................... 9
4 NETWORKING ......................................................................................................................................... 10
4.1 IMPLEMENTATION MODEL ............................................................................................................... 10
4.1.1 Application Data Flow........................................................................................................................... 10
4.1.2 Functional Definition of AE’s ................................................................................................................ 11
4.1.2.1 Functional Definition of Application Entity Azurion R3.0 ............................................................. 11
4.1.3 Sequencing of Real World Activities .................................................................................................... 12
4.2 AE SPECIFICATIONS ......................................................................................................................... 13
4.2.1 AE Specification of Azurion R3.0 ......................................................................................................... 13
4.2.1.1 SOP Classes .............................................................................................................................. 13
4.2.1.2 Association Policies .................................................................................................................... 14
4.2.1.3 General ....................................................................................................................................... 14
4.2.1.4 Number of Associations .............................................................................................................. 14
4.2.1.5 Asynchronous Nature ................................................................................................................. 14
4.2.1.6 Implementation Identifying Information ....................................................................................... 15
4.2.1.7 Communication Failure Handling ................................................................................................ 15
4.2.1.8 Association Initiation Policy ........................................................................................................ 15
4.2.1.9 (Real-World) Activity – Verification as SCU ................................................................................ 16
4.2.1.9.1 Description and Sequencing of Activities .................................................................................... 16
4.2.1.9.2 Proposed Presentation Contexts ................................................................................................ 16
4.2.1.9.3 SOP Specific Conformance for Verification SOP Class .............................................................. 17
4.2.1.10 (Real-World) Activity – Modality Worklist as SCU ....................................................................... 17
4.2.1.10.1 Description and Sequencing of Activities .................................................................................... 17
4.2.1.10.2 Proposed Presentation Contexts ................................................................................................ 18
4.2.1.10.3 SOP Specific Conformance for Modality Worklist Information Model – FIND SOP Class........... 18
4.2.1.11 (Real-World) Activity – Modality Performed Procedure Step as SCU ......................................... 22
4.2.1.11.1 Description and Sequencing of Activities .................................................................................... 22
4.2.1.11.2 Proposed Presentation Contexts ................................................................................................ 24
4.2.1.11.3 SOP Specific Conformance Modality Performed Procedure Step SOP Class ............................ 24
4.2.1.12 (Real-World) Activity – Image Export .......................................................................................... 31
4.2.1.12.1 Description and Sequencing of Activities .................................................................................... 31
4.2.1.12.2 Proposed Presentation Contexts ................................................................................................ 32
4.2.1.12.3 SOP Specific Conformance for SOP Classes............................................................................. 33
4.2.1.13 (Real-World) Activity – Storage Commitment Push Model as SCU ............................................ 33
4.2.1.13.1 Description and Sequencing of Activities .................................................................................... 33
4.2.1.13.2 Proposed Presentation Contexts ................................................................................................ 34
4.2.1.13.3 SOP Specific Conformance for Storage Commitment Push Model SOP Class .......................... 34
4.2.1.14 (Real-World) Activity – FIND as SCU ......................................................................................... 36
4.2.1.14.1 Description and Sequencing of Activities .................................................................................... 36
4.2.1.14.2 Proposed Presentation Contexts ................................................................................................ 37
4.2.1.14.3 SOP Specific Conformance for SOP Classes............................................................................. 37
4.2.1.14.4 SOP Specific Conformance for Study Root QR Information Model – FIND SOP Class.............. 39
4.2.1.15 (Real-World) Activity – MOVE as SCU ....................................................................................... 41
4.2.1.15.1 Description and Sequencing of Activities .................................................................................... 41
4.2.1.15.2 Proposed Presentation Contexts ................................................................................................ 41
4.2.1.15.3 SOP Specific Conformance for Patient Root QR Information Model – MOVE SOP Class ......... 42
 2022 Koninklijke Philips N.V.
SNIP-IOCC-T-020001.09 (Version 2.2) Page 5 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved
4.2.1.15.4 SOP Specific Conformance for Study Root QR Information Model – MOVE SOP Class ........... 43
4.2.1.16 (Real-World) Activity – Print Management as SCU..................................................................... 44
4.2.1.16.1 Description and Sequencing of Activities .................................................................................... 44
4.2.1.16.2 Proposed Presentation Contexts ................................................................................................ 46
4.2.1.16.3 SOP Specific Conformance for Basic Film Session SOP Class for Basic Grayscale Print Meta 47
4.2.1.16.4 SOP Specific Conformance for Basic Film Box SOP Class for Basic Grayscale Print Meta ....... 48
4.2.1.16.5 SOP Specific Conformance for Basic Grayscale Image Box SOP Class for Basic Grayscale Print Meta 49
4.2.1.16.6 SOP Specific Conformance for Basic Grayscale Image Box SOP Class for Basic Grayscale Print Meta 50
4.2.1.16.7 Dataset Specific Conformance for Printer SOP Class for Basic Grayscale Print Meta N-EVENT-REPORT-SCP
50
4.2.1.17 Association Acceptance Policy ................................................................................................... 54
4.2.1.18 (Real-World) Activity – Verification as SCP ................................................................................ 55
4.2.1.18.1 Description and Sequencing of Activities .................................................................................... 55
4.2.1.18.2 SOP Specific Conformance for Verification SOP Class .............................................................. 55
4.2.1.19 (Real-World) Activity – Image Import .......................................................................................... 56
4.2.1.19.1 Description and Sequencing of Activities .................................................................................... 56
4.2.1.19.2 Accepted Presentation Contexts................................................................................................. 56
4.2.1.19.3 SOP Specific Conformance for Storage SOP Classes ............................................................... 57
4.3 NETWORK INTERFACES ................................................................................................................... 57
4.3.1 Physical Network Interfaces ................................................................................................................. 57
4.3.2 Additional Protocols ............................................................................................................................. 57
4.3.2.1 Basic Application-Level Confidentiality Profile ............................................................................ 57
4.3.3 IPv4 and IPv6 Support ......................................................................................................................... 57
4.4 CONFIGURATION ............................................................................................................................... 58
4.4.1 AE Title/Presentation Address Mapping ............................................................................................... 58
4.4.1.1 Local AE Titles ............................................................................................................................ 58
4.4.1.2 Remote AE Title/Presentation Address Mapping ........................................................................ 58
4.4.2 Parameters........................................................................................................................................... 58
5 MEDIA INTERCHANGE ........................................................................................................................... 59
5.1 IMPLEMENTATION MODEL ............................................................................................................... 59
5.1.1 Application Data Flow Diagram ............................................................................................................ 59
5.1.2 Functional Definitions of AE’s............................................................................................................... 59
5.1.3 Sequencing of Real World Activities .................................................................................................... 59
5.2 AE SPECIFICATIONS ......................................................................................................................... 59
5.2.1 Media Storage Media – Specification ................................................................................................... 59
5.2.1.1 File Meta Information for the Media AE ...................................................................................... 60
5.2.1.2 Real-World Activities................................................................................................................... 60
5.2.1.3 RWA – Read File-set .................................................................................................................. 60
5.2.1.3.1 Media Storage Application Profile ............................................................................................... 60
5.2.1.4 RWA – Create File-set ................................................................................................................ 60
5.2.1.4.1 Media Storage Application Profile ............................................................................................... 60
5.2.1.5 RWA – Update File-set ............................................................................................................... 61
5.2.1.5.1 Media Storage Application Profile ............................................................................................... 61
5.3 AUGMENTED AND PRIVATE APPLICATION PROFILES ................................................................. 61
5.4 MEDIA CONFIGURATION .................................................................................................................. 61
6 SUPPORT OF CHARACTER SETS ......................................................................................................... 62
7 SECURITY ................................................................................................................................................ 63
7.1 INTRODUCTION .................................................................................................................................. 63
7.2 DICOM SECURITY PROFILES SUPPORT ......................................................................................... 63
7.2.1 Secure Use and User Identity Profiles ................................................................................................. 63
7.2.1.1 DICOM Security Profile Details ................................................................................................... 63
7.2.1.1.1 Audit Trail Messages .................................................................................................................. 63
7.2.2 Security Transport Connection Profiles ................................................................................................ 64
7.2.3 Media Storage Security Profiles ........................................................................................................... 66
7.2.4 Attribute Confidentiality Profiles ........................................................................................................... 66
 2022 Koninklijke Philips N.V.
SNIP-IOCC-T-020001.09 (Version 2.2) Page 6 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved
7.2.5 Digital Signature Profiles ...................................................................................................................... 67
7.2.6 Basic Network Address Management Profiles ..................................................................................... 67
7.2.7 Application Configuration Management Profiles ................................................................................... 67
7.2.8 Time Synchronization Profiles .............................................................................................................. 67
7.3 ASSOCIATION LEVEL SECURITY ..................................................................................................... 67
7.4 APPLICATION LEVEL SECURITY ..................................................................................................... 67
8 ANNEXES................................................................................................................................................. 68
8.1 IOD CONTENTS .................................................................................................................................. 68
8.1.1 Created SOP Instances........................................................................................................................ 68
8.1.1.1 List of Created SOP Classes ...................................................................................................... 68
8.1.1.2 Secondary Capture Image Storage SOP Class .......................................................................... 68
8.1.1.3 Grayscale Softcopy Presentation State Storage SOP Class ...................................................... 73
8.1.1.4 X-Ray Angiographic Image Storage SOP Class ......................................................................... 78
8.1.1.5 X-Ray Radiation Dose SR .......................................................................................................... 86
8.1.2 Attribute Mapping ................................................................................................................................. 89
8.1.3 Coerced/Modified Fields....................................................................................................................... 90
8.2 DATA DICTIONARY OF PRIVATE ATTRIBUTES .............................................................................. 90
8.3 CODED TERMINOLOGY AND TEMPLATES ..................................................................................... 90
8.3.1 Context Group ...................................................................................................................................... 90
8.3.2 Template Specifications ....................................................................................................................... 90
8.3.2.1 TID 10001 Projection X-Ray Radiation Dose .............................................................................. 91
8.3.2.2 TID 10002 Accumulated X-Ray Dose ......................................................................................... 91
8.3.2.3 TID 10003 Irradiation Event X-Ray Data .................................................................................... 92
8.3.2.4 TID 10003B Irradiation Event X-Ray Source Data (for Fluoroscopy Irradiation Event type) ....... 94
8.3.2.5 TID 10003B Irradiation Event X-Ray Source Data (for Stationary Acquisition Irradiation Event type) 95
8.3.2.6 TID 10003C Irradiation Event X-Ray Mechanical Data ............................................................... 95
8.3.2.7 TID 10004 Accumulated Projection X-Ray Dose (for Fluoroscopy Irradiation Event type) ......... 96
8.3.2.8 TID 10004 Accumulated Projection X-Ray Dose (for Stationary Acquisition Irradiation Event type) 96
8.3.2.9 TID 10007 Accumulated Total Projection Radiography Dose ..................................................... 96
8.3.2.10 TID 1002 Observer Context ........................................................................................................ 97
8.3.2.11 TID 1004 Device Observer Identifying Attributes ........................................................................ 97
8.3.3 Private Code Definitions ....................................................................................................................... 97
8.4 GRAYSCALE IMAGE CONSISTENCY ............................................................................................... 97
8.5 STANDARD/EXTENDED/SPECIALIZED/PRIVATE SOP CLASSES ................................................. 97

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 7 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved

3 Introduction
The introduction specifies product and relevant disclaimers as well as any general information that the vendor feels is appropriate.

3.1 Revision History

The revision history provides dates and differences of the different releases.
Table 3: Revision History

Document Version Date of Issue Description of change

01 02-Nov-2022 Initial version of Azurion R3.0

3.2 Audience
This Conformance Statement is intended for:
 (Potential) customers
 System integrators of medical equipment
 Marketing staff interested in system functionality
 Software designers implementing DICOM interfaces
It is assumed that the reader is familiar with the DICOM standard.

3.3 Remarks
The DICOM Conformance Statement is contained in chapter 4 through 8 and follows the contents and structuring requirements of
DICOM PS 3.2.
This DICOM Conformance Statement by itself does not guarantee successful interoperability of Philips equipment with non-Philips
equipment. The user (or user's agent) should be aware of the following issues:

 Interoperability
Interoperability refers to the ability of application functions, distributed over two or more systems, to work successfully together.
The integration of medical devices into an IT environment may require application functions that are not specified within the scope
of DICOM. Consequently, using only the information provided by this Conformance Statement does not guarantee interoperability
of Philips equipment with non-Philips equipment.
It is the user's responsibility to analyze thoroughly the application requirements and to specify a solution that integrates Philips
equipment with non-Philips equipment.

 Validation
Philips equipment has been carefully tested to ensure that the actual implementation of the DICOM interface corresponds with
this Conformance Statement.
Where Philips equipment is linked to non-Philips equipment, the first step is to compare the relevant Conformance Statements. If
the Conformance Statements indicate that successful information exchange should be possible, additional validation tests will be
necessary to ensure the functionality, performance, accuracy and stability of image and image related data. It is the responsibility
of the user (or user's agent) to specify the appropriate test suite and to carry out the additional validation tests.

 New versions of the DICOM Standard

The DICOM Standard will evolve in future to meet the user's growing requirements and to incorporate new features and
technologies. Philips is actively involved in this evolution and plans to adapt its equipment to future versions of the DICOM
Standard. In order to do so, Philips reserves the right to make changes to its products or to discontinue its delivery. The user
should ensure that any non-Philips provider linking to Philips equipment also adapts to future versions of the DICOM Standard. If
not, the incorporation of DICOM enhancements into Philips equipment may lead to loss of connectivity (in case of networking) and
incompatibility (in case of media).

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 8 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved

3.4 Definitions, Terms and Abbreviations

Table 4: Definitions, Terms and Abbreviations

Abbreviation/Term Explanation
AE Application Entity
ANSI American National Standard Institute
CIS Clinical Information System
DICOM Digital Imaging and Communications in Medicine
DMS Document Management System
DX Digital X-Ray
ELE DICOM Explicit VR Little Endian
FSC File-set Creator
FSR File-set Reader
FSU File-set Updater
GUI Graphic User Interface
ILE DICOM Implicit VR Little Endian
IOD Information Object Definition
MPPS Modality Performed Procedure Step
NEMA National Electrical Manufacturers Association
PDU Protocol Data Unit
RIS Radiology Information Systems
RWA Real-World Activity
SC Secondary Capture
SCP Service Class Provider
SCU Service Class User
SOP Service Object Pair
SR Structured Report
TCP/IP Transmission Control Protocol/Internet Protocol
UID Unique Identifier
MWL Modality Worklist
XA X-Ray Angiographic

3.5 References
[DICOM] Digital Imaging and Communications in Medicine, Parts 1 - 22 (NEMA PS 3.1- PS 3.22),
National Electrical Manufacturers Association
1300 North 17th Street
Suite 900
Arlington, Virginia 22209
Internet: https://www.dicomstandard.org/current
Note that at any point in time the official standard consists of the most recent yearly edition of the base standard (currently
2022) plus all the supplements and correction items that have been approved as Final Text.

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 9 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved

4 Networking
This section contains the networking related services (vs. the media related ones).

4.1 Implementation model

The implementation model consists of three sections:
 The application data flow diagram, specifying the relationship between the Application Entities and the “external world” or Real-
World Activities,
 A functional description of each Application Entity, and
 The sequencing constraints among them.

4.1.1 Application Data Flow

Azurion R3.0 has a single Application Entity in its implementation, namely Azurion R3.0 Application Entity. Figure 2 shows the
relationship between the Local and Remote Real World Activities.
 After RWA Verify Application Level Communication, the Azurion R3.0 as SCU uses the remote Request Verification SCP
functionality to verify communication.
 After RWA Modality Worklist, the Azurion R3.0 as SCU uses the remote Modality Worklist Information Model SCP
functionality to query for Modality Worklist.
 After RWA Create and Set Modality Performed Procedure Step, the Azurion R3.0 as SCU uses the remote Modality
Performed Procedure Step SOP Class functionality to Report Modality Performed Procedure Step.
 After RWA Transfer Images + Presentation States + X-Ray Dose Structured Report, the Azurion R3.0 as SCU uses the
remote SCP Storage Service Class functionality to store local images-Ray Dose Structured Report and presentation states in
a remote database.
 The Azurion R3.0 as SCP Storage Service class accepts images +presentation states from the remote SCU.
 After RWA Storage Commitment, the Azurion R3.0 as SCU uses the remote SCP Storage Commitment Service Class
functionality to commit remote images and presentation states.
 After RWA Print Images, the Azurion R3.0 as SCU uses the remote SCP Print management Service Class functionality to
print the images.
 After RWA Query Retrieve, the Azurion R3.0 as SCU uses the remote SCP Query Retrieve images Service Class
functionality to Query Retrieve.

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 10 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved

Figure 2 : Functional Overview

4.1.2 Functional Definition of AE’s

This section contains a functional definition for each individual local Application Entity.

4.1.2.1 Functional Definition of Application Entity Azurion R3.0

Verification Service Class
The Azurion R3.0 can perform (only to pre-configured systems) the Verification service as SCU, the Azurion R3.0 shall request an
Association. When the association is accepted by the remote system, the Azurion R3.0 shall send the Verification request, receive
the Verification response, and request for releasing the association.
The Azurion R3.0 can also perform the verification service as SCP, it shall accept association when the association is requested by
the remote system.

Storage Service Class

The Azurion R3.0 can perform (only to pre-configured systems) the Storage service as SCU (RWA Transfer Images + Presentation
States and Structured Report), triggered by the operator or by an event in the system, e.g. closing of an examination, acquisition of
 2022 Koninklijke Philips N.V.
SNIP-IOCC-T-020001.09 (Version 2.2) Page 11 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved
images. The Azurion R3.0 shall request an association with the selected remote SCP for all applicable Storage SOP classes. When
the association is accepted, the Azurion R3.0 shall send the Storage requests (including data from local database), receive the
Storage responses and act accordingly, and finally request for releasing the association.
The Azurion R3.0 can also perform (only to pre-configured systems) the Storage service as SCP (RWA accept Images +Presentation
States). The Azurion R3.0 shall receive an association with the selected remote SCU for all applicable Storage SOP classes, accept
the association and receives the Storage requests responses and act accordingly.

Print Management Service Class

The Azurion R3.0 can perform the Print service as SCU (RWA Print Images), triggered by the operator. For each printed sheet, the
Azurion R3.0 shall request an association with the selected remote SCP (i.e., a Print Server) for all applicable SOP classes of the
applicable Print Management Meta SOP class. When the association is accepted, the Azurion R3.0 shall send the Print requests
including data from local database (the N-GET RQ message to get the printer status, the N-CREATE-RQ message to create the Film
Session and the Film Box, the N-SET-RQ message to set the Image Box on the printer, finally, the N-ACTION-RQ message to give
printer the command to print), receive the Print responses and act accordingly, and finally request for releasing the association.
The Azurion R3.0 can perform the Print service as SCU (RWA Get Printer Status), triggered by the operator in the service mode. The
Azurion R3.0 shall request an association with the selected remote SCP (Print Server) for the Printer SOP class.
When the association is accepted, the Azurion R3.0 shall send the N-GET request, receive the responses from the Print Server and
act accordingly, and finally request for releasing the association.

Basic Worklist Management Service Class

The Azurion R3.0 can perform (only to the pre-configured MWL SCP) the Basic Worklist Management service as SCU (RWA
Request Modality Worklist), triggered by the operator. The Azurion R3.0 shall request an association. When the association is
accepted, the Azurion R3.0 shall send the Worklist request, receive the Worklist responses, and request for releasing the
association.

Study Management Service Class

The Azurion R3.0 can perform (only to the pre-configured MWL SCP) the Study Management service as SCU (RWA Create and Set
Modality Performed Procedure Step), triggered by the start of an examination (triggered by the first x-ray exposure) for acquisition or
closing. The Azurion R3.0 shall request an association. When the association is accepted, the Azurion R3.0 shall send Create and Set
requests, receive the responses, and request for releasing the association.

Query Retrieve Service Class

The Azurion R3.0 can perform the Query Retrieve service as SCU. The Azurion R3.0 shall request an association. When the
association is accepted, the Azurion R3.0 shall send a Query/Retrieve request, receive the responses, and request for releasing the
association.

4.1.3 Sequencing of Real World Activities

The following sequence of Real World activities are supported by Azurion R3.0:
 The clinical user queries the MWL SCP for a (specific) Worklist representing the list of Scheduled Procedure Steps (with
demographic information). Based on that query entered at Azurion R3.0, it sends the C-FIND-RQ message with the query
criteria. The automatic broad query with configured query criteria shall be triggered whenever user selects scheduled patients
page or all patients page.
 The clinical user starts the examination. As a result, Azurion R3.0 notifies the MWL SCP of the start of a new Procedure
Step, i.e. it sends the MPPS N-CREATE-RQ message with the “IN PROGRESS” status of the examination.
 The clinical user acquires images with a certain procedure. As a result, if background image transfer is configured, Azurion
R3.0 sends automatically the acquired images (and corresponding presentation states) to the PACS and\or the Workstation,
i.e., it sends the C-STORE-RQ messages containing the image (and presentation state) information.
 The clinical user completes the examination. As a result, if auto-transfer is configured, Azurion R3.0 sends images (and
corresponding presentation states) and dose report to the PACS and/or Workstation (background image transfer), i.e., it
sends the C-STORE-RQ messages containing the image (and presentation state) and dose report information.
 When all images (and presentation states), which were to be automatically transferred to the PACS, have been transferred
and storage-commit configured, the Azurion R3.0 asks the PACS to take responsibility for the images (and presentation
states) that it has stored that originate from the examination, i.e., it sends the N-ACTION-RQ message containing the request
for storage commit.

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 12 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved
 Azurion R3.0 notifies the MWL SCP of the completion of a Procedure Step, i.e., it sends the N-SET-RQ message with the
“COMPLETED” status of the examination. Additionally to the basic flow of activities, the clinical user may also perform the
following steps:
o The clinical user manually transfers images to the PACS and/or Workstation. As a result, Azurion R3.0 sends the C-
STORE-RQ messages containing the image information.
o The clinical user manually prints selected images. As a result, Azurion R3.0 sends the N-GET-RQ message to get
the printer status, the N-CREATE-RQ message to create the Film Session and the Film Box, the N-SET-RQ
message to set the Image Box on the printer. Finally, it sends the N-ACTION-RQ message to give printer the
command to print.

Figure 3 presents normal scheduled workflow. Other workflow situations (e.g., unscheduled procedure steps) will have other
sequencing constraints. For example, printing could equally take place after the acquired images have been stored or after
the examination have been closed or could be omitted completely. Query for images could take place before images have
been acquired or could be omitted completely.

Figure 3 : Azurion R3.0 Sequence Diagram

4.2 AE Specifications
This section in the DICOM Conformance Statement is a set of Application Entity specifications. There are as many of these
subsections as there are different AEs in the implementation.

4.2.1 AE Specification of Azurion R3.0

Detail of this specific Application Entity is specified in this section.

4.2.1.1 SOP Classes

This Application Entity provides Standard Conformance to the following SOP Classes.

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 13 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved
Table 5: SOP Classes for Azurion R3.0

SOP Class Name SOP Class UID SCU SCP

Verification SOP Class 1.2.840.10008.1.1 Yes Yes
Storage Commitment Push Model SOP Class 1.2.840.10008.1.20.1 Yes No
Modality Performed Procedure Step SOP Class 1.2.840.10008.3.1.2.3.3 Yes No
Basic Grayscale Print Management Meta SOP Class 1.2.840.10008.5.1.1.9 Yes No
>Basic Film Session SOP Class 1.2.840.10008.5.1.1.1 Yes No
>Basic Film Box SOP Class 1.2.840.10008.5.1.1.2 Yes No
>Basic Grayscale Image Box SOP Class 1.2.840.10008.5.1.1.4 Yes No
>Printer SOP Class 1.2.840.10008.5.1.1.16 Yes No
Basic Color Print Management Meta SOP Class 1.2.840.10008.5.1.1.18 Yes No
>Basic Film Session SOP Class 1.2.840.10008.5.1.1.1 Yes No
>Basic Film Box SOP Class 1.2.840.10008.5.1.1.2 Yes No
>Basic Color Image Box SOP Class 1.2.840.10008.5.1.1.4.1 Yes No
>Printer SOP Class 1.2.840.10008.5.1.1.16 Yes No
Secondary Capture Image Storage SOP Class 1.2.840.10008.5.1.4.1.1.7 Yes Yes
Grayscale Softcopy Presentation State Storage SOP Class 1.2.840.10008.5.1.4.1.1.11.1 Yes Yes
X-Ray Angiographic Image Storage SOP Class 1.2.840.10008.5.1.4.1.1.12.1 Yes Yes
X-Ray Radiation Dose SR 1.2.840.10008.5.1.4.1.1.88.67 Yes No
Modality Worklist Information Model – FIND SOP Class 1.2.840.10008.5.1.4.31 Yes No
Patient Root QR Information Model – FIND SOP Class 1.2.840.10008.5.1.4.1.2.1.1 Yes No
Study Root QR Information Model – FIND SOP Class 1.2.840.10008.5.1.4.1.2.2.1 Yes No
Patient Root QR Information Model – MOVE SOP Class 1.2.840.10008.5.1.4.1.2.1.2 Yes No
Study Root QR Information Model – MOVE SOP Class 1.2.840.10008.5.1.4.1.2.2.2 Yes No

4.2.1.2 Association Policies

Each AE specification contains a description of the general association establishment and acceptance policies of the AE.

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

Table 6: DICOM Application Context

Description Value
Application Context Name 1.2.840.10008.3.1.1.1

4.2.1.4 Number of Associations

Azurion R3.0 (SCU) can initialize a maximum of one simultaneous association. The maximum number of simultaneous associations
supported by the Azurion R3.0 (SCP) is unlimited by default.

Table 7: Maximum number of associations as an Association Initiator for Azurion R3.0

Property Value
Maximum number of simultaneous associations 1

4.2.1.5 Asynchronous Nature

The Azurion R3.0 does not support asynchronous operations except for storage commitment. After the storage commitment N-
ACTION request is transmitted, storage commitment notification may be handled on another association
 2022 Koninklijke Philips N.V.
SNIP-IOCC-T-020001.09 (Version 2.2) Page 14 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved

4.2.1.6 Implementation Identifying Information

The value supplied for Implementation Class UID, and version name are documented here.

Table 8: DICOM Implementation Class and Version for Azurion R3.0

Property Value
Implementation Class UID 1.3.46.670589.7.29.3.0.1
Implementation Version Name Azurion

4.2.1.7 Communication Failure Handling

The behavior of this application entity during communication failure is summarized in the table below.

Table 9: Communication Failure Behavior

Exception Behavior
Timeout The association is released, and the command is marked failed.
The reason is logged and reported to the user.
Association aborted The ABORT is handled by failing the job and the command is marked failed.
The reason is logged and reported to the user.

4.2.1.8 Association Initiation Policy

The Application Entity will respond to a received Association rejection as shown in the next table.

Table 10: Association Rejection response

Result Source Reason/Diagnosis Behavior

1-rejected-permanent 1-DICOM UL service-user 1-no-reason-given Log entry.
2-application-context-name-not- Log entry.
supported
3-calling-AE-title-not-recognized Log entry.
7-called- AE-title-not-recognized Log entry.
2-DICOM UL service-provider 1-no-reason-given Log entry.
(ACSE related function) 2-no-reason-given Log entry.
3-DICOM UL service-provider 1-temporary-congestion Log entry.
(Presentation related function) 2-local-limit-exceeded Log entry.
2-rejected-transient 1-DICOM UL service-user 1-no-reason-given Log entry.
2-application-context-name-not- Log entry.
supported
3-calling-AE-title-not-recognized Log entry.
7-called- AE-title-not-recognized Log entry.
2-DICOM UL service-provider 1-no-reason-given Log entry.
(ACSE related function) 2-no-reason-given Log entry.
3-DICOM UL service-provider 1-temporary-congestion Log entry.
(Presentation related function) 2-local-limit-exceeded Log entry.

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 15 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved

Table 11: Association Abort Handling

Source Reason/Diagnosis Behavior

0 – DICOM UL service-user 0 – reason-not-specified Log entry.

2 – DICOM UL service-provider 0 – reason-not-specified Log entry.

1 – unrecognized-PDU Log entry.
2 – unexpected-PDU Log entry.
4 – unrecognized-PDU-parameter Log entry.
5 – unexpected-PDU-parameter Log entry.
6 – invalid-PDU-parameter-value Log entry.

4.2.1.9 (Real-World) Activity – Verification as SCU

4.2.1.9.1 Description and Sequencing of Activities
For each Verify Application Level Communication request, an association towards the remote system is established and a C-ECHO
request is transmitted. Once the response is received, the association is closed.

Figure 4: Sequencing of RWA Verify Application Level Communication

4.2.1.9.2 Proposed Presentation Contexts

Each time an association is initiated, the Azurion R3.0 proposes one presentation contexts to be used on that association. The
presentation context proposed by the Azurion R3.0 for Verify Application Level Communication is defined in Table below.

Table 12: Proposed Presentation Contexts for (Real-World) Activity – Verification as SCU

Presentation Context Table

Abstract Syntax Transfer Syntax

Role Ext. Neg.
Name UID Name UID
Verification SOP Class 1.2.840.10008.1.1 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None
Explicit VR Little Endian 1.2.840.10008.1.2.1

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 16 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved
Explicit VR Big Endian 1.2.840.10008.1.2.2

4.2.1.9.3 SOP Specific Conformance for Verification SOP Class

4.2.1.9.3.1 Dataset Specific Conformance for Verification SOP Class C-ECHO-SCU
The behavior of the Azurion R3.0 for status codes in a Verification response is summarized in Table 13.

Table 13: Verification C-ECHO Response Status Handling Behavior

Service Status Error Code Further Meaning Behavior

Success 0000 Confirmation The SCP has successfully responded to the
verification request.

The behavior of the Azurion R3.0 during communication failure is summarized in Table 14.

Table 14: Verification Communication Failure Behavior

Service Status Error Code

Timeout Association is closed. The reason is logged and reported to the user.
Association aborted The reason is logged, and failure is reported to the user.
Association rejected The reason is logged, and failure is reported to the user.

4.2.1.10 (Real-World) Activity – Modality Worklist as SCU

4.2.1.10.1 Description and Sequencing of Activities
For each Broad or Specific Worklist request, the Azurion R3.0 opens an association towards the Basic Worklist Management SCP
and sends a C-FIND request. After retrieval of all responses containing matching Worklist items, the association is closed (see Figure
5). All returned Worklist items are displayed to the operator who can select an item from the Worklist and perform an examination.

Figure 5 : Sequencing of RWA Request Modality Worklist

The clinical user may cancel the query to the MWL SCP. As a result, Azurion R3.0 sends a C-FIND Cancel Request to the MWL SCP.

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 17 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved

4.2.1.10.2 Proposed Presentation Contexts

The presentation contexts are defined in the Table 15.

Table 15: Proposed Presentation Contexts for (Real-World) Activity – Modality worklist as SCU

Presentation Context Table

Abstract Syntax Transfer Syntax

Role Ext. Neg.
Name UID Name UID
Modality Worklist Information 1.2.840.10008.5.1.4.31 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None
Model – FIND SOP Class Explicit VR Little Endian 1.2.840.10008.1.2.1
Explicit VR Big Endian 1.2.840.10008.1.2.2

4.2.1.10.3 SOP Specific Conformance for Modality Worklist Information Model – FIND SOP
Class
Two kinds of queries can be done with the Azurion R3.0 : a broad query and a specific query. A broad query for the Worklist is initiated
by the operator without filling in any search criteria (the search criteria are based on system configuration). The Matching Keys are
presented in Table 16.

A specific Worklist request is initiated by the operator after filling in search criteria in the Graphical User Interface. At least one key
should be specified. No verification of query results in relation to the original query criteria is done. The Matching Keys are presented
in Table 17.

A received Worklist entry is validated. The entry will be discarded, and an error will be reported when a type-one or type-two attribute
is missing, or when the translation of a type-one attribute fails (this includes individual attributes within a sub-sequence).

Table 16: Broad Query Presentation Contexts for (Real-World) Activity Modality Worklist as SCU

Attribute Name Tag Matching Key

Scheduled Station AE Title (0040,0001) Single value matching
Scheduled Procedure Step Start (0040,0002) Universal matching or range matching
Date
Scheduled Procedure Step Start (0040,0003) Universal matching or range matching
Time
Modality (0008,0060) Single value matching and Universal matching

Table 17: Matching Table MWL Information Model – Specific Query

Attribute Name Tag Matching Key

Scheduled Station AE Title (0040,0001) Universal matching or single value matching
Scheduled Procedure Step Start (0040,0002) Universal matching or range matching
Date
Modality (0008,0060) Universal matching or single value matching
Patient’s Name (0010,0010) Universal matching or single value matching or
wild card matching
Patient ID (0010,0020) Universal matching or single value matching
Accession Number (0008,0050) Universal matching or single value matching
Requested Procedure ID (0040,1001) Universal matching or single value matching

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 18 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved

4.2.1.10.3.1 Dataset Specific Conformance for Modality Worklist Information Model – FIND
SOP Class C-FIND-SCU
This section specifies the Modality Worklist Request Attributes.
For each attribute in the following information is supplied:
Attribute Name: Attributes supported to build a Modality Worklist Request Identifier.
Tag: DICOM tag for this attribute.
VR: DICOM VR for this attribute.
M: Matching Keys for (automatic) Worklist Update.
R: Return Keys. An “X” will indicate that this attribute as matching key can be used
Q: Interactive Query Key. An “X” will indicate that this attribute as matching key can be used.
D: Displayed Keys. An “X” indicates that this Worklist attribute is displayed to the user during a patient registration
dialog.
IOD: An “X” indicates that this Worklist attribute is included into all object Instances created during performance of
the related Procedure Step.
Type of Matching: The following types of matching exists:
 Single Value Matching
 List of UID Matching
 Wild Card Matching
 Range Matching
 Sequence Matching
 Universal Matching

Table 18: C-FIND-RQ Dataset Specification.

Modality Worklist Information Model – FIND SOP Class

Type Of
Attribute Name Tag VR M R Q D IOD Comment
Matching
Scheduled Procedure Step
Scheduled Procedure Step Sequence 0040,0100 SQ X NA
>Modality 0008,0060 CS X X X X X Single Value,
Universal,
Wild Card
>Requested Contrast Agent 0032,1070 LO X X Universal
>Scheduled Station AE Title 0040,0001 AE X X X X Single Value, Universal, Wild
Card
>Scheduled Procedure Step Start Date 0040,0002 DA X X X X Single Value, Universal, Wild
Card, range
>Scheduled Procedure Step Start Time 0040,0003 TM X X X Single Value, Range, Universal
>Scheduled Performing Physician’s 0040,0006 PN X X X X Single Value, Universal, Wild
Name Card
>Scheduled Procedure Step 0040,0007 LO X Universal
Description
>Scheduled Protocol Code Sequence 0040,0008 SQ X Universal
>>Code Value 0008,0100 SH X Universal
>>Coding Scheme Designator 0008,0102 SH X Universal
>>Coding Scheme Version 0008,0103 SH X Universal
>>Code Meaning 0008,0104 LO X Universal
>>Protocol Context Sequence 0040,0440 SQ X Universal
>>>Measurement Units Code 0040,08EA SQ X Universal
Sequence
>>>>Code Value 0008,0100 SH X Universal
>>>>Coding Scheme Designator 0008,0102 SH X Universal

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 19 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved

Modality Worklist Information Model – FIND SOP Class

Type Of
Attribute Name Tag VR M R Q D IOD Comment
Matching
Scheduled Procedure Step
>>>>Coding Scheme Version 0008,0103 SH X Universal
>>>>Code Meaning 0008,0104 LO X Universal
>>>Value Type 0040,A040 CS X Universal
>>>Concept Name Code Sequence 0040,A043 SQ X Universal
>>>>Code Value 0008,0100 SH X Universal
>>>>Coding Scheme Designator 0008,0102 SH X Universal
>>>>Coding Scheme Version 0008,0103 SH X Universal
>>>>Code Meaning 0008,0104 LO X Universal
>>>DateTime 0040,A120 DT X Universal
>>>Person Name 0040,A123 PN X Universal
>>>Text Value 0040,A160 UT X Universal
>>>Concept Code Sequence 0040,A168 SQ X Universal
>>>>Code Value 0008,0100 SH X Universal
>>>>Coding Scheme Designator 0008,0102 SH X Universal
>>>>Coding Scheme Version 0008,0103 SH X Universal
>>>>Code Meaning 0008,0104 LO X Universal
>>>Numeric Value 0040,A30A DS X Universal
>Scheduled Procedure Step ID 0040,0009 SH X Universal
>Scheduled Station Name 0040,0010 SH X Universal
>Scheduled Procedure Step Location 0040,0011 SH X Universal
>Pre-Medication 0040,0012 LO X Universal
>Scheduled Procedure Step Status 0040,0020 CS X Universal
Requested Procedure
Study Instance UID 0020,000D UI X X Universal
Requested Procedure Code Sequence 0032,1064 SQ X Universal
>Code Value 0008,0100 SH X Universal
>Coding Scheme Designator 0008,0102 SH X Universal
>Coding Scheme Version 0008,0103 SH X Universal
>Code Meaning 0008,0104 LO X Universal
Requested Procedure ID 0040,1001 SH X X X Single Value, Universal, Wild
Card
Patient Transport Arrangements 0040,1004 LO X Universal
Imaging Service Request
Accession Number 0008,0050 SH X X X X Single Value, Universal, Wild
Card
Referring Physician’s Name 0008,0090 PN X X X Universal
Requesting Physician 0032,1032 PN X Universal
Visit Relationship
Referenced Patient Sequence 0008,1120 SQ NA
>Referenced SOP Class UID 0008,1150 UI X Universal
>Referenced SOP Instance UID 0008,1155 UI X Universal
Patient Identification

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 20 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved

Modality Worklist Information Model – FIND SOP Class

Type Of
Attribute Name Tag VR M R Q D IOD Comment
Matching
Scheduled Procedure Step
Patient’s Name 0010,0010 PN X X X X X Single Value, Universal

Patient ID 0010,0020 LO X X X X X Single Value, Universal

Patient Demographic
Patients Birth Date 0010,0030 DA X X X Single, Universal, Range, Wild
Card
Patient’s Sex 0010,0040 CS X X X Single Value, Universal
Patient’s Weight 0010,1030 DS X X X Universal
Patient Medical
Medical Alerts 0010,2000 LO X Universal
Allergies 0010,2110 LO X Universal
Pregnancy Status 0010,21C0 US X X Universal
Patient State 0038,0500 LO X X Universal
SOP Common
Specific Character Set 0008,0005 CS X

The behavior of the Azurion R3.0 for status codes in C-FIND response is summarized in Table 19.
Table 19: Modality Worklist C-FIND Response Status Handling Behavior

Service Status Error Code Further Meaning Behavior

Success 0000 Matching is complete - No final The result is reported to the user and is logged.
Identifier is supplied.
Refused A700 Out of Resources Stops with processing the C-FIND Response(s) from the
SCP. Responses displayed to the user.
Failed A900 Identifier Does Not Match SOP Stops with processing the C-FIND Response(s) from the
Class SCP. The reason is logged, and the failure is reported to the
user. Responses displayed to the user.
C001 Unable to process Stops with processing the C-FIND Response(s) from the
SCP. The reason is logged, and the failure is reported to the
user. No responses displayed to the user.
Cancel FE00 Matching terminated due to Stops with processing the C-FIND Response(s) from the
Cancel Match request SCP. No responses displayed to the user.
Pending FF00 Matches are continuing – Current. Continues with processing of the C-FIND
Match is supported in the same Response(s) from the SCP
manner as supplied and any
Optional Keys were Required
Keys.
FF01 Matches are continuing – Warning Continues with processing of the C-FIND
that one or more Optional Keys Response(s) from the SCP.
were not supported for existence
for this Identifier.
* Any other * The association is aborted using A-ABORT. The reason is
status code logged, and the failure is reported to the user.
No responses displayed to the user.

The behavior of the Azurion R3.0 during communication failure is summarized in Table 20.

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 21 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved
Table 20: Modality Worklist Communication Failure Behavior

Exception Behavior
Timeout The query is marked as failed. The reason is logged and reported to the user. The Azurion R3.0 stops processing the C-
FIND Response(s) from the SCP.
Association Aborted If the association is aborted using A-ABORT, the query is marked as failed. The reason is logged, and failure is reported
to the user. Stops with processing the C-FIND Response(s) from the SCP.
Association Rejected The query is marked as failed. The reason is logged, and failure is reported to the user. No C-FIND request performed.

4.2.1.11 (Real-World) Activity – Modality Performed Procedure Step as SCU

4.2.1.11.1 Description and Sequencing of Activities
For each MPPS Job, a new association towards the Modality Performed Procedure Step is established and closed when the MPPS
Job has been transmitted. There are three kinds of MPPS Jobs:

 MPPS Create Job. Only an N-CREATE request with status “IN PROGRESS” is transmitted. Once the response is received,
the association is closed. The MPPS Create Job is submitted when:
 A Worklist examination is selected for acquisition.
 A local examination is selected for acquisition and the system is configured to be connected to an IHE compatible
MWL SCP.
 An already Completed Worklist examination or an already Completed, local examination, is re-selected for
acquisition (IHE Append Use Case).

 MPPS Set Job. Only an N-SET request is transmitted. The status field will respectively be set to “DISCONTINUED” or
“COMPLETED”. Once the response is received, the association is closed. The MPPS Set Job is submitted when:
 An examination is discontinued/deleted/restored to solve patient mixing or closed and the MPPS Create Job is already
handled (transmitted).
 MPPS Create & Set Job. Over the same association both the N-CREATE request and the N-SET request corresponding to
the same examination are transmitted. The MPPS Create & Set Job is submitted when:
An examination is discontinued/deleted/restored to solve patient mixing and the MPPS Create Job is not already handled (not
transmitted). In such a case the MPPS Create & Set Job replaces the MPPS Create Job.

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 22 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved

Figure 6: Sequencing of RWA separate MPPS Create and separate MPPS Set Job

MPPS Create and MPPS Set in same association can be established when a procedure is reopened for review and performed some
snapshots and export them and then close the study.

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 23 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved

Figure 7: Sequencing of RWA MPPS Create and Set Job

4.2.1.11.2 Proposed Presentation Contexts

Each time an association is initiated, the Azurion R3.0 proposes one presentation context to be used on that association. The
presentation context proposed by the Azurion R3.0 for Create and Set Modality Performed Procedure Step is defined in table 21.

The implementation chooses Explicit VR Little Endian transfer syntax in case multiple transfer syntaxes are accepted in the
association acceptance. All details regarding the specific conformance, including response behavior to all status codes, both from an
application level and communication errors are provided in table 23.

Table 21: Proposed Presentation Contexts for (Real-World) Activity – MPPS as SCU

Presentation Context Table

Abstract Syntax Transfer Syntax Extended

Role
Name UID Name UID Negotiation

Modality Performed 1.2.840.10008.3.1.2.3.3 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None

Procedure Step SOP Class Explicit VR Little Endian 1.2.840.10008.1.2.1
Explicit VR Big Endian 1.2.840.10008.1.2.2

4.2.1.11.3 SOP Specific Conformance Modality Performed Procedure Step SOP Class
The set of attributes within an N-CREATE and N-SET messages is fixed, and it does not depend on configuration settings. In an N-
CREATE message, all possible attributes and attribute sequences used in the N-SET are forecasted by defining the attributes and
settings their values to NULL. When an N-SET message is transmitted, it may occur that a forecasted attribute isn’t actually used.
Table 22 up till Table 24 indicate whether or not an attribute and attribute value is sent during N-CREATE.

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 24 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved
Table 24 up till Table 26 indicate whether or not an attribute and attribute value is sent during MPPS N-SET.

4.2.1.11.3.1 Dataset Specific Conformance for Modality Performed Procedure Step SOP Class
N-CREATE-SCU
Table 22: N-CREATE-RQ Dataset Specification.

Modality Performed Procedure Step SOP Class

Attribute Name Tag VR Value Comment

SOP Common Module

Specific Character Set 0008,0005 CS
Performed Procedure Step Relationship
Referenced Patient Sequence 0008,1120 SQ
>Referenced SOP Class UID 0008,1150 UI
>Referenced SOP Instance UID 0008,1155 UI
Patient’s Name 0010,0010 PN
Patient ID 0010,0020 LO
Patient’s Birth Date 0010,0030 DA
Patient’s Sex 0010,0040 CS
Scheduled Step Attributes Sequence 0040,0270 SQ
>Accession Number 0008,0050 SH Empty in case of an unscheduled exam
>Referenced Study Sequence 0008,1110 SQ Empty in case of an unscheduled exam
>>Referenced SOP Class UID 0008,1150 UI
>>Referenced SOP Instance UID 0008,1155 UI
>Study Instance UID 0020,000D UI
>Requested Procedure Description 0032,1060 LO Empty in case of an unscheduled exam
>Scheduled Procedure Step Description 0040,0007 LO Empty in case of an unscheduled exam
>Scheduled Protocol Code Sequence 0040,0008 SQ
>>Code Value 0008,0100 SH
>>Coding Scheme Designator 0008,0102 SH
>>Code Meaning 0008,0104 LO
>Scheduled Procedure Step ID 0040,0009 SH Empty in case of an unscheduled exam
>Requested Procedure ID 0040,1001 SH Empty in case of an unscheduled exam
Performed Procedure Step Information
Procedure Code Sequence 0008,1032 SQ
>Code Value 0008,0100 SH
>Coding Scheme Designator 0008,0102 SH
>Code Meaning 0008,0104 LO
>Context Group Extension Flag 0008,010B CS
>Context Identifier 0008,010F CS
>Context UID 0008,0117 UI
Performed Station AE Title 0040,0241 AE AE Title as configured by the MWL SCP/CIS unit.
Performed Station Name 0040,0242 SH
Performed Location 0040,0243 SH Always Empty
Performed Procedure Step Start Date 0040,0244 DA
Performed Procedure Step Start Time 0040,0245 TM
Performed Procedure Step End Date 0040,0250 DA
Performed Procedure Step End Time 0040,0251 TM
Performed Procedure Step Status 0040,0252 CS
Performed Procedure Step ID 0040,0253 SH

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 25 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved

Modality Performed Procedure Step SOP Class

Attribute Name Tag VR Value Comment

Performed Procedure Step Description 0040,0254 LO
Performed Procedure Type Description 0040,0255 LO

Image Acquisition Results

Modality 0008,0060 CS Applied Value(s): XA
Study ID 0020,0010 SH If no Study ID is known, the Accession Number will
be used as value.
Performed Protocol Code Sequence 0040,0260 SQ
>Code Value 0008,0100 SH
>Coding Scheme Designator 0008,0102 SH
>Coding Scheme Version 0008,0103 SH
>Code Meaning 0008,0104 LO
>Context Group Extension Flag 0008,010B CS
>Context Identifier 0008,010F CS
>Context UID 0008,0117 UI
>Protocol Context Sequence 0040,0440 SQ
>>Content Item Modifier Sequence 0040,0441 SQ
>>>Value Type 0040,A040 CS
>>>Concept Name Code Sequence 0040,A043 SQ
>>>>Code Value 0008,0100 SH
>>>>Coding Scheme Designator 0008,0102 SH
>>>>Code Meaning 0008,0104 LO
>>>>Context Group Extension Flag 0008,010B CS
>>>>Context Identifier 0008,010F CS
>>>>Context UID 0008,0117 UI
>>Value Type 0040,A040 CS
>>Concept Name Code Sequence 0040,A043 SQ
>>>Code Value 0008,0100 SH
>>>Coding Scheme Designator 0008,0102 SH
>>>Code Meaning 0008,0104 LO
>>>Context Group Extension Flag 0008,010B CS
>>>Context Identifier 0008,010F CS
>>>Context UID 0008,0117 UI
Performed Series Sequence 0040,0340 SQ Sequence will be empty when there are no images
to report
>Retrieve AE Title 0008,0054 AE
>Series Description 0008,103E LO
>Performing Physician’s Name 0008,1050 PN
>Operators’ Name 0008,1070 PN
>Operator Identification Sequence 0008,1072 SQ
>>Institution Address 0008,0081 ST
>>Person Identification Code Sequence 0040,1101 SQ
>>>Code Value 0008,0100 SH
>>>Coding Scheme Designator 0008,0102 SH
>>>Code Meaning 0008,0104 LO

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 26 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved

Modality Performed Procedure Step SOP Class

Attribute Name Tag VR Value Comment

>>>Context Group Extension Flag 0008,010B CS
>>>Context Identifier 0008,010F CS
>>>Context UID 0008,0117 UI
>>Person’s Address 0040,1102 ST
>>Person’s Telephone Numbers 0040,1103 LO
>Referenced Image Sequence 0008,1140 SQ
>>Referenced SOP Class UID 0008,1150 UI
>>Referenced SOP Instance UID 0008,1155 UI
>>Container Identifier 0040,0512 LO
>>Specimen Description Sequence 0040,0560 SQ
>>>Specimen Identifier 0040,0551 LO
>>>Specimen UID 0040,0554 UI
>Protocol Name 0018,1030 LO
>Series Instance UID 0020,000E UI
>Referenced Non-Image Composite SOP 0040,0220 SQ
Instance Sequence
>>Referenced SOP Class UID 0008,1150 UI
>>Referenced SOP Instance UID 0008,1155 UI

Radiation Dose
Image and Fluoroscopy Area Dose Product 0018,115E DS
Total Time of Fluoroscopy 0040,0300 US
Total Number of Exposures 0040,0301 US
Entrance Dose 0040,0302 US
Exposure Dose Sequence 0040,030E SQ See Table 25 for content items set through N-
SET
Entrance Dose in mGy 0040,8302 DS

Billing And Material Management Codes

Film Consumption Sequence 0040,0321 SQ Always Empty
>Medium Type 2000,0030 CS
>Film Size ID 2010,0050 CS
>Number of Films 2100,0170 IS

The behavior of the Azurion R3.0 for status codes in an MPPS N-CREATE response and NSET response is presented in Table 23
and Table 24 respectively. In case of the retransmission attempt each message stored in the persistent queue is sent over a separate
association.
Table 23: MPPS N-CREATE Response Status Handling Behavior

Service Status Error Code Further Meaning Behavior

Success 0000 Successful operation. Association will be released.
The notify status of the related examination is
Updated (set to in progress). The examination status
is not changed (e.g., still in progress).
Failure 0213 Resource Limitation The message contents are made persistent and the
message is added to the persistent queue and waits
For the next retransmission attempt. The
examination status is observed as “Failed”

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 27 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved
Failure 0118 No Such SOP Class The examination status is updated as failed. The
reason for error is logged.
Failure 0110 Processing Failure The examination status is updated as failed. The
reason for error is logged.
* Any other * Association will be released.
status If the response status is reported during initial
code transmission the message contents is made
persistent and the message is added to the
Persistent queue. If this response status is the result
of the retransmission attempt related examination is
updated to the state as if the transmission
Succeeded. This means that the notify status of the
related examination is updated (set to in progress)
The examination status is not
changed (e.g., still in progress).The response status
Is logged as a warning.

Table 24: MPPS Communication Failure Behavior (N-SET, N-CREATE) Exception Behavior

Exception Behavior
Timeout The Association is aborted using A-ABORT. The reason is logged and reported to the
user. The message content is made persistent, and the message is added to the
persistent queue and waits for the next retransmission attempt. The examination
status is set to CLOSED.
Association Aborted The command is marked as failed. The reason is logged and reported to the user. The
message content is made persistent, and the message is added to the persistent
queue and waits for the next retransmission attempt. The examination status is set to
CLOSED.
Association Rejected The command is marked as failed. The reason is logged and reported to the user. The
message content is made persistent, and the message is added to the persistent
queue and waits for the next retransmission attempt. The examination status is set to
CLOSED.

4.2.1.11.3.2 Dataset Specific Conformance for Modality Performed Procedure Step SOP Class
N-SET-SCU
Table 25: N-SET-RQ Dataset Specification.

Modality Performed Procedure Step SOP Class

Attribute Name Tag VR Value Comment

Sop Common Module

Specific Character Set 0008,0005 CS
Performed Procedure Step Information
Procedure Code Sequence 0008,1032 SQ
>Code Value 0008,0100 SH
>Coding Scheme Designator 0008,0102 SH
>Code Meaning 0008,0104 LO
>Context Group Extension Flag 0008,010B CS
>Context Identifier 0008,010F CS
>Context UID 0008,0117 UI
Performed Procedure Step End Date 0040,0250 DA
Performed Procedure Step End Time 0040,0251 TM
Performed Procedure Step Status 0040,0252 CS Applied Values: COMPLETED or DISCONTINUED
Performed Procedure Step Description 0040,0254 LO May be Empty by configuration

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 28 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved

Modality Performed Procedure Step SOP Class

Attribute Name Tag VR Value Comment

Performed Procedure Type Description 0040,0255 LO
Image Acquisition Results
Performed Protocol Code Sequence 0040,0260 SQ Sequence remains empty
>Code Value 0008,0100 SH
>Coding Scheme Designator 0008,0102 SH
>Code Meaning 0008,0104 LO
>Context Group Extension Flag 0008,010B CS
>Context Identifier 0008,010F CS
>Context UID 0008,0117 UI
>Protocol Context Sequence 0040,0440 SQ May be empty when no images to be reported
>>Content Item Modifier Sequence 0040,0441 SQ
>>>Value Type 0040,A040 CS
>>>Concept Name Code Sequence 0040,A043 SQ
>>>>Code Value 0008,0100 SH
>>>>Coding Scheme Designator 0008,0102 SH
>>>>Code Meaning 0008,0104 LO
>>>>Context Group Extension Flag 0008,010B CS
>>>>Context Identifier 0008,010F CS
>>>>Context UID 0008,0117 UI
>>Value Type 0040,A040 CS
>>Concept Name Code Sequence 0040,A043 SQ
>>>Code Value 0008,0100 SH
>>>Coding Scheme Designator 0008,0102 SH
>>>Code Meaning 0008,0104 LO
>>>Context Group Extension Flag 0008,010B CS
>>>Context Identifier 0008,010F CS
>>>Context UID 0008,0117 UI
Performed Series Sequence 0040,0340 SQ
>Retrieve AE Title 0008,0054 AE
>Series Description 0008,103E LO
>Series Description Code Sequence 0008,103F SQ
>>Code Value 0008,0100 SH
>>Coding Scheme Designator 0008,0102 SH
>>Code Meaning 0008,0104 LO
>>Context Group Extension Flag 0008,010B CS
>>Context Identifier 0008,010F CS
>>Context UID 0008,0117 UI
>Performing Physician’s Name 0008,1050 PN
>Performing Physician Identification 0008,1052 SQ
Sequence
>>Institution Address 0008,0081 ST
>>Person Identification Code Sequence 0040,1101 SQ
>>>Code Value 0008,0100 SH
>>>Coding Scheme Designator 0008,0102 SH
>>>Code Meaning 0008,0104 LO
>>>Context Group Extension Flag 0008,010B CS
>>>Context Identifier 0008,010F CS
>>>Context UID 0008,0117 UI
 2022 Koninklijke Philips N.V.
SNIP-IOCC-T-020001.09 (Version 2.2) Page 29 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved

Modality Performed Procedure Step SOP Class

Attribute Name Tag VR Value Comment

>>Person’s Address 0040,1102 ST
>>Person’s Telephone Numbers 0040,1103 LO
>Operators’ Name 0008,1070 PN
>Operator Identification Sequence 0008,1072 SQ
>>Institution Address 0008,0081 ST
>>Person Identification Code Sequence 0040,1101 SQ
>>>Code Value 0008,0100 SH
>>>Coding Scheme Designator 0008,0102 SH
>>>Code Meaning 0008,0104 LO
>>>Context Group Extension Flag 0008,010B CS
>>>Context Identifier 0008,010F CS
>>>Context UID 0008,0117 UI
>>Person’s Address 0040,1102 ST
>>Person’s Telephone Numbers 0040,1103 LO
>Referenced Image Sequence 0008,1140 SQ
>>Referenced SOP Class UID 0008,1150 UI
>>Referenced SOP Instance UID 0008,1155 UI
>>Container Identifier 0040,0512 LO
>>Specimen Description Sequence 0040,0560 SQ
>>>Specimen Identifier 0040,0551 LO
>>>Specimen UID 0040,0554 UI
>Protocol Name 0018,1030 LO
>Series Instance UID 0020,000E UI
>Referenced Non-Image Composite SOP 0040,0220 SQ Refers to Dicom Object that were transferred to the
Instance Sequence PACS.
>>Referenced SOP Class UID 0008,1150 UI
>>Referenced SOP Instance UID 0008,1155 UI
>Archive Requested 0040,A494 CS
Radiation Dose
Image and Fluoroscopy Area Dose Product 0018,115E DS
Total Time of Fluoroscopy 0040,0300 US
Total Number of Exposures 0040,0301 US
Entrance Dose 0040,0302 US
Entrance Dose in mGy 0040,8302 DS
Exposure Dose Sequence 0040,030E SQ
>KVP 0018,0060 DS
>Exposure Time 0018,1150 IS
>Radiation Mode 0018,115A CS PULSED
>Filter Type 0018,1160 SH
>Filter Material 0018,7050 CS
>X-Ray Tube Current In uA 0018,8151 DS
>Comments on Radiation Dose 0040,0310 ST
Billing And Material Management Codes
Film Consumption Sequence 0040,0321 SQ
>Medium Type 2000,0030 CS
>Film Size ID 2010,0050 CS
>Number of Films 2100,0170 IS

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 30 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved
The behavior of the Azurion R3.0 for status codes in an MPPS N-SET response is presented in Table 26. In case of the
retransmission attempt each message stored in the persistent queue is sent over a separate association.

Table 26: MPPS N-SET Response Status Handling Behavior

Service Status Error Code Further Meaning Behavior

Success 0000 Successful operation. Association will be released.
The notify status of the related examination is
Updated (set to notified). The examination status is
Set to COMPLETED and it is logged.
Failure 0213 Resource Limitation The message content is made persistent and the
Message is added to the persistent queue and waits
For the next retransmission attempt. The examination status
is set to CLOSED.
* Any other status * Association will be released.
code If this response status is reported during initial transmission
the message contents is made persistent and the message
is added to the persistent queue. If this response status is
the result of the retransmission attempt related examination
is updated to the state as if the transmission succeeded.
Then the notify status of the related examination is updated
(set to notified). The response status is logged as a warning.
The examination status is set to COMPLETED.

4.2.1.12 (Real-World) Activity – Image Export

4.2.1.12.1 Description and Sequencing of Activities
The operator can select images (and presentation states) and request them to be sent to (pre-configure) multiple destinations. Each
request is forwarded to the job queue and processed as individual request to Transfer Images (and Presentation States). If
background image and presentation state transfer is configured, the Azurion R3.0 sends the acquired images and presentation states
automatically. It can be configured which instances will be automatically marked and the destinations where the instances are
automatically sent to. The background image and presentation state transfer are triggered by the image acquisition event and/or by
the close examination event in Azurion R3.0 . For each request to Transfer Images (and Presentation States) (i.e., transfer job), one
association towards the remote system is established. Within the association, for each image or presentation state, a C-STORE
request is transmitted. Once the responses are received, the association is closed. A possible sequence of interactions between the
Azurion R3.0 and a remote AE with only one C-STORE request is presented in Figure 8.

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 31 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved

Figure 8 : Sequencing of RWA Image Export

4.2.1.12.2 Proposed Presentation Contexts

Each time an association is initiated, the Azurion R3.0 proposes two presentation contexts to be used on that association. The
presentation context proposed by the Azurion R3.0 for Transfer Images is defined in Table 27.
The implementation proposes each SOP Class only once in the abstract syntax specifying all possible transfer syntaxes for that SOP
Class. Due to the fact that the SCP has to react with a chosen transfer syntax, as per SOP Class used transfer syntax is forced by the
SCP.
Table 27: Proposed Presentation Contexts for (Real-World) Activity Image Export

Presentation Context Table

Abstract Syntax Transfer Syntax Extended

Role
Name UID Name UID Negotiation

Secondary Capture Image 1.2.840.10008.5.1.4.1.1.7 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None
Storage SOP Class Explicit VR Little Endian 1.2.840.10008.1.2.1
Explicit VR Big Endian 1.2.840.10008.1.2.2
JPEG Lossless, Non-Hierarchical, 1.2.840.10008.1.2.4.7
First-Order Prediction (Process 14) 0
Grayscale Softcopy 1.2.840.10008.5.1.4.1.1.11.1 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None
Presentation State Storage Explicit VR Little Endian 1.2.840.10008.1.2.1
SOP Class
Explicit VR Big Endian 1.2.840.10008.1.2.2
X-Ray Angiographic Image 1.2.840.10008.5.1.4.1.1.12.1 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None
Storage SOP Class Explicit VR Little Endian 1.2.840.10008.1.2.1
Explicit VR Big Endian 1.2.840.10008.1.2.2
JPEG Lossless, Non-Hierarchical, 1.2.840.10008.1.2.4.7
First-Order Prediction (Process 14) 0
X-Ray Radiation Dose SR 1.2.840.10008.5.1.4.1.1.88.6 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None
7 Explicit VR Little Endian 1.2.840.10008.1.2.1
Explicit VR Big Endian 1.2.840.10008.1.2.2

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 32 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved

4.2.1.12.3 SOP Specific Conformance for SOP Classes

Azurion R3.0 can exchange image data in the following formats:

 X-Ray Angiographic images can either be sent with raw pixel data or processed pixel data.
 Standard Secondary Capture (1.2.840.10008.5.1.4.1.1.7)
 Standard Grayscale Softcopy Presentation State SOP Class (1.2.840.10008.5.1.4.1.1.11.1)

Furthermore, the Azurion R3.0 can exchange non-image data in the following format:
 X-Ray Radiation Dose Structured Report (1.2.840.10008.5.1.4.1.1.88.67)

The behavior of Azurion R3.0 for status codes in a C-STORE response is summarized in Table 28.
Table 28: Storage C-STORE Response Status Handling Behavior

Service Status Error Code Further Meaning Behavior

Success 0000 Successful operation The SCP has successfully stored the SOP Instances. If all SOP
Instances in a send job have status success, then the job is
marked as completed. Success is logged.
Refused A700 Out of Resources The association is released, and the send job is marked as failed.
Error A900 Data Set does not match SOP An error message is logged.
Class

C000-CFFF Cannot Understand

Warning B000 Coercion of Data Elements The association is released, and the send job is marked as failed.
B006 Elements discarded An error message is logged.

B007 Data set does not match SOP

class
* Any other status * The association is released, and the send job is marked as failed.
code An error message is logged.

The behavior of Azurion R3.0 during communication failure is summarized in Table 29.
Table 29: Storage Communication Failure Behavior

Exception Behavior
Timeout The send job is marked as failed. An error message is logged.
Association aborted The send job is marked as failed. An error message is logged.
Association rejected The send job is marked as failed. An error message is logged.

4.2.1.13 (Real-World) Activity – Storage Commitment Push Model as SCU

4.2.1.13.1 Description and Sequencing of Activities
Azurion R3.0 Storage Commitment as a SCU service. It accepts a storage commitment notification (N-EVENT-REPORT) from
systems that send them.

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 33 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved

Figure 9: Data Flow Diagram – Commit Image (asynchronous)

4.2.1.13.2 Proposed Presentation Contexts

The presentation contexts are defined in the Table 30.
Table 30: Proposed Presentation Contexts for (Real-World) Activity – Storage Commitment Push Model as SCU

Presentation Context Table

Abstract Syntax Transfer Syntax Extended

Role
Name UID Name UID Negotiation

Storage Commitment Push 1.2.840.10008.1.20.1 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None
Model SOP Class Explicit VR Little Endian 1.2.840.10008.1.2.1
Explicit VR Big Endian 1.2.840.10008.1.2.2

4.2.1.13.3 SOP Specific Conformance for Storage Commitment Push Model SOP Class
This section and sub-section include the manufacturer SOP and Dataset specific information as well the status codes and their
corresponding behavior.

4.2.1.13.3.1 Dataset Specific Conformance for Storage Commitment Push Model SOP Class N-
ACTION-SCU
Details regarding the Dataset Specific response behavior will be reported in this section.

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 34 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved
Table 31: N-ACTION-RQ Dataset Specification.

Storage Commitment Push Model SOP Class

Attribute Name Tag VR Comment

Sop Common Module

SOP Class UID 0008,0016 UI
SOP Instance UID 0008,0018 UI
Storage Commitment Module
Transaction UID 0008,1195 UI
Referenced SOP Sequence 0008,1199 SQ
>Referenced SOP Class UID 0008,1150 UI
>Referenced SOP Instance UID 0008,1155 UI

The details regarding the response behavior to status codes are provided in Table 32.

Table 32: Storage Commitment N-ACTION Response Status Handling Behavior

Service Status Error Code Further Meaning Behavior

Success 0000 Successful operation The storage commitment request has been successfully
sent. The storage commitment request job is marked as
completed. Success is logged.

Table 33: Storage Commitment N-EVENT-REPORT Behavior

Event Type Event Type ID Behavior

Storage Commitment Request Successful 1 The Examination is marked as completed and it
becomes a candidate for an automatic deletion from
the local database if local resources become scarce.
Storage Commitment Request Complete – 2 The failure is reported to the operator by not marking
Failures Exist the examination as completed. The operator may re-
transfer the image data (which was previously
transferred to the PACS).

4.2.1.13.3.2 Dataset Specific Conformance for Storage Commitment Push Model SOP Class N-
EVENT-REPORT-SCP
Details regarding the Dataset Specific response behavior will be reported in this section.

Table 34: N-EVENT-REPORT-RSP Dataset Specification.

Storage Commitment Push Model SOP Class

Attribute Name Tag VR Comment

Sop Common Module

SOP Class UID 0008,0016 UI
SOP Instance UID 0008,0018 UI

The details regarding the response behavior to status codes are provided in Table 35.

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 35 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved
Table 35: Storage Commitment N-EVENT-REPORT Response Status Handling Behavior

Service Status Error Code Further Meaning Behavior

Success 0000 Successful operation The storage commitment result has been successfully
received. The SCP has successfully stored the SOP
Instances. The examination is marked as completed.

Table 36: Storage Commitment N-EVENT-REPORT Response Status

Event Type Event Type ID Behavior

Storage Commitment Request Successful 1 The Examination is marked as completed and it
becomes a candidate for an automatic deletion from
the local database if local resources become scarce.
Storage Commitment Request Complete – 2 The failure is reported to the operator by not marking
Failures Exist the examination as completed. The operator may re-
transfer the image data (which was previously
transferred to the PACS).

4.2.1.14 (Real-World) Activity – FIND as SCU

4.2.1.14.1 Description and Sequencing of Activities
The operator is able to query a (pre-configured) remote database. The ACP AE initiates an association to the selected Remote AE and
uses it to send C-FIND requests (and receive the associated find replies). For each query a number of C-FIND requests is established
in one association to the peer entity, which is released when all query results are received. An example sequencing of Activities is
presented in Figure 10 and Figure 11.

Figure 10: Sequencing of RWA (Patient Root Q/R Information Model)

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 36 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved

Figure 11: Sequencing of RWA (Study Root Q/R Information Model)

The clinical user may cancel the query to the PACS or Workstation. As a result, the Azurion R3.0 sends a C-FIND Cancel Request to
the PACS or Workstation.

4.2.1.14.2 Proposed Presentation Contexts

Each time an association is initiated, the ACP AE proposes two presentation contexts to be used on that association. The presentation
context proposed by the ACP AE for Find Remote Images is defined in Table 37.
Table 37: Proposed Presentation Contexts for (Real-World) Activity – FIND As SCU

Presentation Context Table

Abstract Syntax Transfer Syntax Extended

Role
Name UID Name UID Negotiation

Patient Root QR 1.2.840.10008.5.1.4.1.2.1.1 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None

Information Model – FIND Explicit VR Little Endian 1.2.840.10008.1.2.1
SOP Class
Explicit VR Big Endian 1.2.840.10008.1.2.2
Study Root QR Information 1.2.840.10008.5.1.4.1.2.2.1 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None
Model – FIND SOP Class Explicit VR Little Endian 1.2.840.10008.1.2.1
Explicit VR Big Endian 1.2.840.10008.1.2.2

4.2.1.14.3 SOP Specific Conformance for SOP Classes

The Azurion R3.0 provides standard conformance to this SOP class. The Azurion R3.0 AE does not generate queries containing
optional keys and it does not generate relational queries.

4.2.1.14.3.1 Dataset Specific Conformance for Patient Root QR Information Model – FIND SOP
Class C-FIND-SCU

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 37 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved
In Table 37 the supported query keys for each query level are described. Universal matching is supported by default.

Table 38: Supported Query Keys for Patient Root Information Model

Patient Root Information Model

Attribute Name Tag VR Type Of Matching Comment

Query/Retrieve Level 0008,0052 CS Single Value PATIENT, STUDY, SERIES
Specific Character Set 0008,0005 CS
Q/R Patient Level
Patient’s Name 0010,0010 PN Single value matching or
wild card matching or
universal matching
Patient ID 0010,0020 LO Single value matching or
wild card matching or
universal matching
Patient’s Birth Date 0010,0030 DA Single value matching or
universal matching
Patient’s Sex 0010,0040 CS Universal matching only
Q/R Study level
Study Date 0008,0020 DA Range matching or
universal matching
Study Time 0008,0030 TM Universal matching only
Accession Number 0008,0050 SH Value matching or wild
card matching or universal
matching
Query/Retrieve Level 0008,0052 CS Single
Modalities in Study 0008,0061 CS Single
Study Description 0008,1030) LO Universal matching
Patient’s Name 0010,0010 PN Single value matching or
wild card matching or
universal matching
Patient ID 0010,0020 LO Single value matching or
universal matching
Patient’s Birth Date 0010,0030 DA Single value matching or
universal matching
Patient’s Sex 0010,0040 CS Universal matching only
Patient Size 0010,1020 DS Universal matching
Patient Weight 0010,1030 DS Universal matching
Patient Comment 0010,4000 LT Universal matching
Study ID 0020,0010 SH Universal matching only
Study Instance UID 0020,000D UI Universal matching only
Number Of Study Related 0020,1206 IS Universal matching
Series
Q/R Series level
Modality 0008,0060 CS Universal matching only
Series Description 0008,103E LO Universal matching
Number Of Series Related 0008,1050 PN Universal matching only
Instances
Study Instance UID 0020,000D UI Single value matching only
Series Instance UID 0020,000E UI Universal matching only
Series Number 0020,0011 IS Universal matching only

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 38 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved
The behavior of the Azurion R3.0 for status codes in C-FIND response is summarized in Table 38.
Table 39: Status Response

Service
Error Code Further Meaning Behavior
Status
Success 0000 Matching is complete – No final Identifier is supplied. Stops with processing the C-Find Response(s) from the
SCP. All results are displayed to the operator.
Refused A700 Out of Resources The association is released, and the send job is marked as
Failed A900 Identifier Does Not Match SOP Class failed.
An error message is logged.
Cxxx Unable to process
Cancel FE00 Matching terminated due to Cancel Match request Stops with processing the C-Find Response(s) from the
SCP. Results already received up to that point are
displayed to the operator.
Pending FF00 Matches are continuing – Current Match is supported in Continues with processing of the C-Find Response(s) from
the same manner as supplied and any Optional Keys the SCP
were Required Keys.
FF01 Matches are continuing – Warning that one or more Continues with processing of the C-Find Response(s) from
Optional Keys were not supported for existence for this the SCP.
Identifier.
* Any other * The association is aborted using A-ABORT. The reason is
status code logged, and the failure is reported to the user.

The behavior of the Azurion R3.0 during communication failure is summarized.

Table 40: DICOM Command Communication Failure Behavior

Exception Behavior
Timeout The send job is marked as failed. An error message is logged.
Association aborted The send job is marked as failed. An error message is logged.
Association rejected The send job is marked as failed. An error message is logged.

4.2.1.14.4 SOP Specific Conformance for Study Root QR Information Model – FIND SOP Class
The Azurion R3.0 provides standard conformance to this SOP class. The Azurion R3.0 AE does not generate queries containing
optional keys and it does not generate relational queries.

4.2.1.14.4.1 Dataset Specific Conformance for Study Root QR Information Model – FIND SOP
Class C-FIND-SCU
In table 40 the supported query keys for each query level are described. Universal matching is supported as default.
Table 41: Supported Query Keys for Study Root Information Model

Study Root Information Model

Attribute Name Tag VR Type Of Matching Comment

Query/Retrieve Level 0008,0052 CS Single Value STUDY, SERIES
Specific Character Set 0008,0005 CS
Q/R Study level
Study Date 0008,0020 DA Range matching or
universal matching
Study Time 0008,0030 TM Universal matching only

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 39 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved

Study Root Information Model

Attribute Name Tag VR Type Of Matching Comment

Accession Number 0008,0050 SH Value matching or wild
card matching or universal
matching
Query/Retrieve Level 0008,0052 CS Single STUDY
Modalities in Study 0008,0061 CS Single
Study Description 0008,1030) LO Universal matching
Patient’s Name 0010,0010 PN Single value matching or
wild card matching or
universal matching
Patient ID 0010,0020 LO Single value matching or
universal matching
Patient’s Birth Date 0010,0030 DA Single value matching or
universal matching
Patient’s Sex 0010,0040 CS Universal matching only
Patient Size 0010,1020 DS Universal matching
Patient Weight 0010,1030 DS Universal matching
Patient Comment 0010,4000 LT Universal matching
Study ID 0020,0010 SH Universal matching only
Study Instance UID 0020,000D UI Universal matching only
Number Of Study Related 0020,1206 IS Universal matching
Series
Referring Physician name 0008,0090 PN Universal matching
Q/R Series level
Modality 0008,0060 CS Universal matching only
Series Description 0008,103E LO Universal matching
Number Of Series Related 0008,1050 PN Universal matching only
Instances
Study Instance UID 0020,000D UI Single value matching only
Series Instance UID 0020,000E UI Universal matching only
Series Number 0020,0011 IS Universal matching only

The behavior of the Azurion R3.0 for status codes in C-FIND response is summarized.

Table 42: Status Response

Se Error
Further Meaning Behavior
Status Code
Success 0000 Matching is complete – No final Identifier is supplied. Stops with processing the C-Find Response(s) from the SCP.
All results are displayed to the operator.
Refused A700 Out of Resources The association is released, and the send job is marked as
Failed A900 Identifier Does Not Match SOP Class failed.
An error message is logged.
Cxxx Unable to process
Cancel FE00 Matching terminated due to Cancel Match request Stops with processing the C-Find Response(s) from the SCP.
Results already received up to that point are displayed to the
operator.
Pending FF00 Matches are continuing – Current Match is supported in the Continues with processing of the C-Find Response(s) from the
same manner as supplied and any Optional Keys were SCP
Required Keys.
FF01 Matches are continuing – Warning that one or more Optional Continues with processing of the C-Find Response(s) from the
Keys were not supported for existence for this Identifier. SCP.

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 40 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved

Se Error
Further Meaning Behavior
Status Code
* Any * The association is aborted using A-ABORT. The reason is
other logged, and the failure is reported to the user.
status
code

The behavior of the Azurion R3.0 during communication failure is summarized in Table 43.
Table 43: DICOM Command Communication Failure Behavior

Exception Behavior
Timeout The send job is marked as failed. An error message is logged.
Association aborted The send job is marked as failed. An error message is logged.
Association rejected The send job is marked as failed. An error message is logged.

4.2.1.15 (Real-World) Activity – MOVE as SCU

4.2.1.15.1 Description and Sequencing of Activities
The request to move remote images is forwarded to the job queue. For each move job, one association towards the remote system is
established, and C-MOVE requests are transmitted. Once the responses are received, the association is closed. An example of
sequencing of activities is presented in Figure C-MOVE requests are done on the series level.

Figure 12: Sequencing of RWA

The clinical user may cancel the move operation. As a result, the Azurion R3.0 Sends a C-MOVE Cancel Request to the PACS or
Workstation.

4.2.1.15.2 Proposed Presentation Contexts

The presentation contexts for MOVE as SCU are defined in table 44.

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 41 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved
Table 44: Proposed Presentation Contexts for (Real-World) Activity – MOVE As SCU

Presentation Context Table

Abstract Syntax Transfer Syntax

Extended
Role
Name UID Name List UID List Negotiation
Patient Root QR Information 1.2.840.10008.5.1.4.1.2.1.2 Explicit VR Big Endian 1.2.840.10008.1.2.2 SCU None
Model – MOVE SOP Class Explicit VR Little Endian 1.2.840.10008.1.2.1
Implicit VR Little Endian 1.2.840.10008.1.2
Study Root QR Information 1.2.840.10008.5.1.4.1.2.2.2 Explicit VR Big Endian 1.2.840.10008.1.2.2 SCU None
Model – MOVE SOP Class Explicit VR Little Endian 1.2.840.10008.1.2.1
Implicit VR Little Endian 1.2.840.10008.1.2
The implementation proposes each SOP Class only ones in the abstract syntax specifying all possible transfer syntaxes for that SOP
Class. Due to the fact that the SCP has to react with a chosen transfer syntax, the per SOP Class used transfer syntax is forced by the
SCP

4.2.1.15.2.1 SOP Specific Conformance for SOP Classes

Selecting a query result can retrieve only whole examinations. It is not possible to retrieve information if Patient ID contains the sign
“greater than” or “less than” (> or <).
A C-MOVE can be done with the keys presented in Table 45 or Table 48.

4.2.1.15.3 SOP Specific Conformance for Patient Root QR Information Model – MOVE SOP
Class
The Azurion R3.0 provides standard conformance for the Patient Root QR Information Model – MOVE SOP Class.

4.2.1.15.3.1 Dataset Specific Conformance for Patient Root QR Information Model – MOVE
SOP Class C-MOVE-SCU
The behavior of the Identifiers for MOVE is summarized in this section.

Table 45: Identifiers for MOVE Patient Root Information Model as SCU

Patient Root Information Model

Attribute Name Tag VR Comment

Query/Retrieve Level 0008,0052 CS Applied value: Series
Q/R Series level
Patient ID 0010,0020 PN
Study Instance UID 0020,000D UI
Series Instance UID 0020,000E UI

The DICOM C-MOVE Patient Root Information Model Command Status Response Handling is shown in the Table 46.
Table 46: Status Response for C-MOVE Patient Root Information Model

Service Status Error Code Further Meaning Behavior

Success 0000 Sub-operations Complete No Failures The move job is marked as completed. The association is released.
Success is logged.
Refused A701 Out of Resources – Unable to The association is released, and the send job is marked as failed.
calculate number of matches An error message is logged. The reason is logged and reported to the
user.

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 42 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved

Service Status Error Code Further Meaning Behavior

A702 Out of Resources – Unable to perform
sub operations

A801 Move Destination Unknown

Failed A900 Identifier Does Not Match SOP Class The association is released, and the send job is marked as failed.
Cxxx Unable to process An error message is logged
Cancel FE00 Sub-operations terminated due to The move job is marked as cancelled. The association is released. The
Cancel Indication reason is logged and reported to the user.
Warning B000 Sub-operations Complete – One or The association is released, and the send job is marked as failed.
more Failures An error message is logged
* Any other * The association is released, and the send job is marked as failed.
status An error message is logged
code

The possible Communication Failures during a C-MOVE as SCU are shown in the Table 47.

Table 47: DICOM Command Communication Failure Behavior for C-MOVE Patient Root Information Model.

Exception Behavior
Timeout The send job is marked as failed. An error message is logged.
Association aborted The send job is marked as failed. An error message is logged.
Association rejected The send job is marked as failed. An error message is logged.

4.2.1.15.4 SOP Specific Conformance for Study Root QR Information Model – MOVE SOP
Class
The Azurion R3.0 provides standard conformance to this SOP class.

4.2.1.15.4.1 Dataset Specific Conformance for Study Root QR Information Model – MOVE SOP
Class C-MOVE-SCU
The identifiers for C-MOVE as SCU are listed in the Table 48.

Table 48: Identifiers for MOVE Study Root Information Model as SCU

Study Root Information Model

Attribute Name Tag VR Comment

Query/Retrieve Level 0008,0052 CS Applied value: SERIES
Q/R Series level
Series Instance UID 0020,000E UI
Study Instance UID 0020,000D UI

The DICOM C-MOVE Study Root Information Model Command Status Response Handling is shown in the Table 49.

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 43 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved
Table 49: Status response for Study Root Information Model C-MOVE-SCU.

Service Error
Further Meaning Behavior
Code
Status
Success 0000 Sub-operations Complete – No The SCP has successfully stored the SOP Instances. If all SOP Instances
Failures in a send job have status success, then the job is marked as completed.
Success is logged.
Refused A701 Out of Resources – Unable to The association is released, and the send job is marked as failed.
calculate number of matches An error message is logged.

A702 Out of Resources – Unable to perform

sub operations

A801 Move Destination Unknown

Failed A900 Identifier Does Not Match SOP Class The association is released, and the send job is marked as failed.
Cxxx Unable to process An error message is logged.
Cancel FE00 Sub-operations terminated due to The move job is marked as cancelled. The association is released. The
Cancel Indication reason is logged and reported to the user.
Warning B000 Sub-operations Complete – One or The association is released, and the send job is marked as failed.
more Failures An error message is logged.
* Any other * The association is released, and the send job is marked as failed.
Status An error message is logged.
code

The possible Communication Failures for C-MOVE-SCU are shown in the table 50.

Table 50: DICOM Command Communication Failure Behavior for Study Root Information Model C-MOVE-SCU

Exception Behavior
Timeout The send job is marked as failed. An error message is logged.
Association aborted The send job is marked as failed. An error message is logged.
Association rejected The send job is marked as failed. An error message is logged.

4.2.1.16 (Real-World) Activity – Print Management as SCU

4.2.1.16.1 Description and Sequencing of Activities
The operator can select images and request them to be printed on a printer (out of choice list of configured printers). Each request is
forwarded to the job queue and processed as individual request to Print Images. The print job consists of data describing the images
and graphics to be printed as well as the requested layout and other parameters. One print job on Azurion R3.0 may result in a
number of film sessions with the printer equal to the number of printed film sheets. Each film sheet within the print job is internally
processed, converted to a STANDARD/1, 1 page and then an association towards the remote Print Server is established and the page
image is sent to that Print Server. Once the transmission of the film sheet is completed, the association is closed. A sequence of
interactions between the Azurion R3.0 and a remote AE to print one film sheet is presented in Figure 13.

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 44 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved

Figure 13: Sequencing of RWA

The following implementation remarks are important to achieve successful printing:

 Each film session will be in a single association with one or more film boxes and one or more film sheets
 The number of images per Film Box is one. The images to be printed on one film are rendered by the Azurion R3.0 into one
logical image. This logical image is very large, depending on the pixel matrix size (pixels per line, lines per image). A rough
indication is 20 Mbytes. One should take this into account when selecting the DICOM printer and the printer configuration
(e.g., the amount of memory).

 The Azurion R3.0 will request for releasing the association when the print command is given (i.e., the N-ACTION Request).
The association is not kept open for receiving N-EVENT-REPORTs of the Printer SOP Class.

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 45 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved

Table 51: The Applied Order of Print Service Elements

Service Element of
Description
SOP Class
N-GET of the Printer SOP Purpose is to retrieve printer information.
Class
N-CREATE of the Basic Specifies the DICOM Printer about some general presentation parameters, applicable for all films in the Film
Film Session SOP Class Session.
Applied attributes are Number of Copies, Print Priority, Medium Type, Film Destination
N-CREATE of the Basic Specifies the DICOM Printer about some general presentation parameters, applicable for all images in the Film Box.
Film Box SOP Class Applied attributes are Film Orientation, Film Size ID, Magnification Type, Max. Density, Configuration Information,
Trim.
N-SET of the Basic Images to be printed. Applied attributes are Polarity
Grayscale Image Box SOP
Class
N-ACTION of the Basic Triggers the DICOM Printer to print. This actual print action is done at film box level. No attributes are present.
Film Box SOP Class

Table 52: Media Services

Service Element of SOP Class Description

N-EVENT-REPORT of the Printer When N-EVENT-REPORT is received, no printer status polling on a separate
SOP Class connection is executed.

4.2.1.16.2 Proposed Presentation Contexts

Each time an association is initiated, the Azurion R3.0 proposes presentation contexts to be used on that association. The
presentation contexts proposed by the Azurion R3.0 for Print Images is defined in Table 53.

The implementation proposes the SOP Class only ones in the abstract syntax specifying all possible transfer syntaxes for that SOP
Class. Due to the fact that the SCP has to react with a chosen transfer syntax, as per SOP Class used transfer syntax is forced by the
SCP.
Table 53: Proposed Presentation Contexts for (Real-World) Activity – Print Management as SCU

Presentation Context Table

Abstract Syntax Transfer Syntax Extended

Role
Name UID Name UID Negotiation

Basic Grayscale Print 1.2.840.10008.5.1.1.9 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None
Management Meta SOP Explicit VR Little Endian 1.2.840.10008.1.2.1
Class
Explicit VR Big Endian 1.2.840.10008.1.2.2
>Basic Film Session SOP 1.2.840.10008.5.1.1.1 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None
Class Explicit VR Little Endian 1.2.840.10008.1.2.1
Explicit VR Big Endian 1.2.840.10008.1.2.2
>Basic Film Box SOP Class 1.2.840.10008.5.1.1.2 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None
Explicit VR Little Endian 1.2.840.10008.1.2.1
Explicit VR Big Endian 1.2.840.10008.1.2.2
>Basic Grayscale Image Box 1.2.840.10008.5.1.1.4 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None
SOP Class Explicit VR Little Endian 1.2.840.10008.1.2.1
Explicit VR Big Endian 1.2.840.10008.1.2.2
>Printer SOP Class 1.2.840.10008.5.1.1.16 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None
Explicit VR Little Endian 1.2.840.10008.1.2.1

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 46 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved

Presentation Context Table

Abstract Syntax Transfer Syntax Extended

Role
Name UID Name UID Negotiation

Explicit VR Big Endian 1.2.840.10008.1.2.2

Basic Color Print 1.2.840.10008.5.1.1.18 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None
Management Meta SOP Explicit VR Little Endian 1.2.840.10008.1.2.1
Class
Explicit VR Big Endian 1.2.840.10008.1.2.2
>Basic Film Session SOP 1.2.840.10008.5.1.1.1 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None
Class Explicit VR Little Endian 1.2.840.10008.1.2.1
Explicit VR Big Endian 1.2.840.10008.1.2.2
>Basic Film Box SOP Class 1.2.840.10008.5.1.1.2 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None
Explicit VR Little Endian 1.2.840.10008.1.2.1
Explicit VR Big Endian 1.2.840.10008.1.2.2
>Basic Color Image Box SOP 1.2.840.10008.5.1.1.4.1 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None
Class Explicit VR Little Endian 1.2.840.10008.1.2.1
Explicit VR Big Endian 1.2.840.10008.1.2.2
>Printer SOP Class 1.2.840.10008.5.1.1.16 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None
Explicit VR Little Endian 1.2.840.10008.1.2.1
Explicit VR Big Endian 1.2.840.10008.1.2.2

4.2.1.16.3 SOP Specific Conformance for Basic Film Session SOP Class for Basic Grayscale
Print Meta
The Azurion R3.0 provides standard conformance to the Basic Grayscale Print Management Meta SOP Class.
A description and the applied optional (i.e., non-mandatory attributes as Print SCU) attributes in these Service Elements are specified
as well .Note that the Service Elements order is not specified by the DICOM standard. Azurion R3.0 sends the N-DELETE request for
the film session. Overlay, annotation (showing the values of some major identifying attributes) and shutter information is processed in
the images sent to the printer, all the processing including annotations will be part of the image.

This section and sub-section include the manufacturer SOP and Dataset specific information as well the status codes and their
Corresponding behavior.

4.2.1.16.3.1 Dataset Specific Conformance for Basic Film Session SOP Class for Basic
Grayscale Print Meta N-CREATE-SCU
Table 54: N-CREATE-RQ Dataset Specification.

Attribute Name Tag VR Value Presence of Value Source Comment

Number of Copies 2000,0010 IS Between 1 and 100 ALWAYS USER
Print Priority 2000,0020 CS MED ALWAYS AUTO
Medium Type 2000,0030 CS PAPER, BLUE FILM, ALWAYS USER
CLEAR FILM
Film Destination 2000,0040 CS MAGAZINE, PROCESSOR ALWAYS AUTO
Film Session Label 2000,0050 LO Human readable label that ANAP AUTO
identifies the film session

The details regarding the response behavior to status codes are provided in Table 55.

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 47 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved
Table 55: Status Response

Service Status Error Code Further Meaning Behavior

Success 0000 Successful operation The print job continues.
Warning 0116 Any warning The print job continues, and the warning is logged.
Error 0105 Any error The association is aborted using A-ABORT.
The print job will keep resubmitting the failed sheets until the
error is solved or the retry timeout is exceeded.
0106 Any error The association is aborted using A-ABORT. The print job will
keep resubmitting the failed sheets until the error is solved or
the retry timeout is exceeded.

4.2.1.16.4 SOP Specific Conformance for Basic Film Box SOP Class for Basic Grayscale Print
Meta
4.2.1.16.4.1 Dataset Specific Conformance for Basic Film Box SOP Class for Basic Grayscale
Print Meta N-CREATE-SCU
The behavior of the Azurion R3.0 for status codes in an N-CREATE response is summarized in Table 56.

Table 56: N-CREATE-RQ Dataset Specification.

Attribute Name Tag VR Value Presence Source Comment

of Value
Image Display Format 2010,0010 ST STANDARD\1,1
Workstation Format 2010,0010 ST STANDARD\C,R, CUSTOM\i ANAP AUTO
Film Orientation 2010,0040 CS PORTRAIT, LANDSCAPE ANAP USER
Film Size ID 2010,0050 CS DICOM specifies a number of ANAP USER
Defined Terms; more values
are possible and
is print configuration
dependent.
Border Density 2010,0100 CS BLACK
Magnification Type 2010,0060 CS Normally sent out, however ANAP AUTO
sometimes send out empty
Because
some DICOM printers are not
able to
handle (Value NONE for) this
attribute. Applied value(s):
NONE
Max Density 2010,0130 US Maximum density of the ANAP AUTO
images on
the film, expressed in
hundredths of
OD. If Max Density is higher
than
maximum printer density than
Max
Density is set to maximum
printer
density.
Trim 2010,0140 CS NO ANAP AUTO
Configuration 2010,0150 ST Contains a vendor specific ANAP AUTO
Information Lookup-
table (LUT); should be applied
by the

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 48 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved
DICOM printer if LUT data is present.
Illumination 2010,015E US ANAP
Reflected Ambient Light 2010,0160 US ANAP
Referenced Film Session 2010,0500 SQ ANAP AUTO
Sequence
>Referenced SOP Class UID 0008,1150 UI ALWAYS
>Referenced SOP Instance UID 0008,1155 UI ALWAYS
Referenced Presentation LUT 2050,0500 SQ ANAP AUTO
Sequence

The details regarding the response behavior to status codes are provided in Table 57.
Table 57: Status Response

Service Status Error Code Further Meaning Behavior

Success 0000 Successful operation The print job continues.
Warning 0116 Any warning The print job continues, and the warning is logged.
Error 0105 Any error The association is aborted using A-ABORT. The print job will
keep resubmitting the failed sheets until the error is solved or
the retry timeout is exceeded.
0106 Any error The association is aborted using A-ABORT. The print job will
keep resubmitting the failed sheets until the error is solved or
the retry timeout is exceeded.

4.2.1.16.5 SOP Specific Conformance for Basic Grayscale Image Box SOP Class for Basic
Grayscale Print Meta
4.2.1.16.5.1 Dataset Specific Conformance for Basic Grayscale Image Box SOP Class for
Basic Grayscale Print Meta N- SET-SCU
This application entity supports the attributes described in the table 58.

Table 58: N-SET-RQ Dataset Specification.

Presence of
Attribute Name Tag VR Value Source Comment
Value
SOP Class UID 0008,0016 UI ALWAYS
SOP Instance UID 0008,0018 UI ALWAYS
Image Box Position 2020,0010 US 1 ALWAYS AUTO
Polarity 2020,0020 CS NORMAL ALWAYS AUTO
Basic Grayscale 2020,0110 SQ ALWAYS AUTO
Image Sequence
>Samples Per Pixel 0028,0002 US 1 ANAP AUTO
>Photometric 0028,0004 CS MONOCHROME2 ANAP AUTO
Interpretation
>Rows 0028,0010 US Depending on the selected ANAP AUTO
printer type and film size.
>Columns 0028,0011 US Depending on the selected ANAP AUTO
printer type and film size.
>Pixel Aspect Ratio 0028,0034 IS ANAP
>Bits Allocated 0028,0100 US 8 or 16 ANAP AUTO
>Bits Stored 0028,0101 US 8 or 12 ANAP AUTO
>High Bit 0028,0102 US 7 or 11 ANAP AUTO
>Pixel 0028,0103 US 0X0000 ANAP AUTO

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 49 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved
Presence of
Attribute Name Tag VR Value Source Comment
Value
Representation
>Pixel Data 7FE0,0010 OW/OB ANAP AUTO

The details regarding the response behavior to status codes are provided in Table 59.
Table 59: Status Response

Service Status Error Code Further Meaning Behavior

Success 0000 Successful operation The print job continues.
Warning 0107 Any warning The print job continues, and the warning is logged.
Error 0105 Any error The association is aborted using A-ABORT. The print job will
keep resubmitting the failed sheets until the error is solved or
the retry timeout is exceeded.
0106 Any error The association is aborted using A-ABORT. The print job will
keep resubmitting the failed sheets until the error is solved or
the retry timeout is exceeded.

4.2.1.16.6 SOP Specific Conformance for Basic Grayscale Image Box SOP Class for Basic
Grayscale Print Meta
4.2.1.16.6.1 Dataset Specific Conformance for Printer SOP Class for Basic Grayscale Print
Meta N-GET-SCU
This application entity supports the attributes described in the Table 60.
Table 60: N-GET-RQ Dataset Specification.

Attribute Name Tag Value Presence of Value Source Comment

VR
SOP Class UID 0008,0016 UI ALWAYS AUTO
SOP Instance UID 0008,0018 UI ALWAYS AUTO
Printer Status 2110,0010 CS ANAP AUTO
Printer Status Info 2110,0020 CS ANAP AUTO
Print Priority 2000,0020 CS ALWAYS AUTO
Execution Status 2100,0020 CS ALWAYS AUTO
Execution Status 2100,0030 CS ALWAYS AUTO
Info

4.2.1.16.7 Dataset Specific Conformance for Printer SOP Class for Basic Grayscale Print Meta
N-EVENT-REPORT-SCP
This application entity supports the attributes described in the next table.
Table 61: N-EVENT-REPORT-RSP Dataset Specification.

Attribute Name Tag VR Value Presence of Value Source Comment

SOP Class UID 0008,0016 UI ALWAYS AUTO

SOP Instance UID 0008,0018 UI ALWAYS AUTO
Printer Status 2110,0010 CS ANAP AUTO
Printer Status Info 2110,0020 CS ANAP AUTO

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 50 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved

4.2.1.16.7.1 SOP Specific Conformance for Basic Color Print Management Meta SOP Class
The Azurion R3.0 provides standard conformance to the Basic Color Print Management Meta SOP Class. A description and the
applied optional (i.e., non-mandatory attributes as Print SCU) attributes in these Service Elements are specified as well .Note that the
Service Elements order is not specified by the DICOM standard. Azurion R3.0 sends the N-DELETE request for the film session.
Overlay, annotation (showing the values of some major identifying attributes) and shutter information is processed in the images sent
to the printer, all the processing including annotations will be part of the image.

4.2.1.16.7.2 SOP Specific Conformance for Basic Film Session SOP Class for Basic Color
Print Meta
4.2.1.16.7.2.1 Dataset Specific Conformance for Basic Film Session SOP Class for Basic Color Print
Meta N-CREATE-SCU
This application entity supports the attributes described in the Table 62.

Table 62: N-CREATE-RQ Dataset Specification.

Attribute Name Tag VR Value Presence of Value Source Comment

Number of Copies 2000,0010 IS Between 1 and 100 ALWAYS USER
Print Priority 2000,0020 CS MED ALWAYS AUTO
Medium Type 2000,0030 CS PAPER, BLUE FILM, ALWAYS USER
CLEAR FILM
Film Destination 2000,0040 CS MAGAZINE, PROCESSOR ALWAYS AUTO
Film Session Label 2000,0050 LO Human readable label that ANAP AUTO
identifies the film session

The details regarding the response behavior to status codes are provided in Table 63.

Table 63: Status Response

Service Status Error Code Further Meaning Behavior

Success 0000 Successful operation The print job continues.
Warning 0107 Any warning The print job continues, and the warning is logged.
Error 0105 Any error The association is aborted using A-ABORT. The print job will
keep resubmitting the failed sheets until the error is solved or
the retry timeout is exceeded.
0106 Any error The association is aborted using A-ABORT. The print job will
keep resubmitting the failed sheets until the error is solved or
the retry timeout is exceeded.

4.2.1.16.7.3 SOP Specific Conformance for Basic Film Box SOP Class for Basic Color Print
Meta
4.2.1.16.7.3.1 Dataset Specific Conformance for Basic Film Box SOP Class for Basic Color Print Meta
N-CREATE-SCU
The behavior of the Azurion R3.0 for status codes in an N-CREATE response is summarized in Table 64.

Table 64: N-CREATE-RQ Dataset Specification.

Attribute Name Tag VR Value Presence of Value Source Comment

SOP Class UID 0008,0016 UI ALWAYS AUTO

SOP Instance UID 0008,0018 UI ALWAYS AUTO

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 51 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved

Attribute Name Tag VR Value Presence of Value Source Comment

Workstation 2010,0010 ST STANDARD\C, R, ALWAYS AUTO

Format CUSTOM\i
Film Orientation 2010,0040 CS PORTRAIT, LANDSCAPE ALWAYS USER
Film Size ID 2010,0050 CS DICOM specifies a number of ALWAYS USER
Defined Terms; more values
are possible and is print
configuration dependent.
Magnification Type 2010,0060 CS Normally sent out, however ALWAYS AUTO
sometimes send out empty
Because some DICOM
printers are not able to
handle (Value NONE for) this
attribute. Applied value(s):
NONE
Max Density 2010,0130 US Maximum density of the ALWAYS AUTO
images on the film,
expressed in hundredths of
OD. If Max Density is higher
than maximum printer density
than Max Density is set to
maximum printer density.
Trim 2010,0140 CS NO ALWAYS AUTO
Configuration 2010,0150 ST Contains a vendor specific ALWAYS AUTO
Information Lookup-table (LUT); should
be applied by the DICOM
printer if LUT data is present.
Reflected Ambient 2010,0160 US VNAP
Light
Referenced Film 2010,0500 SQ Parent Film Session ALWAYS AUTO
Session Sequence
>Referenced SOP 0008,1150 UI 1.2.840.10008.5.1.1.1 ALWAYS AUTO
Class UID
>Referenced SOP 0008,1155 UI UID of Parent Film Session ALWAYS AUTO
Instance UID
Referenced Image 2010,0510 SQ ALWAYS
Box Sequence
Referenced Basic 2010,0520 SQ VNAP
Annotation Box
Sequence
Referenced 2050,0500 SQ VNAP
Presentation LUT
Sequence

The details regarding the response behavior to status codes are provided in Table 65.

Table 65: Status Response

Service Status Error Code Further Meaning Behavior

Success 0000 Successful operation The print job continues.
Warning 0107 Any warning The print job continues, and the warning is logged.
Error 0105 Any error The association is aborted using A-ABORT. The print job will
keep resubmitting the failed sheets until the error is solved or
the retry timeout is exceeded.

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 52 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved
0106 Any error The association is aborted using A-ABORT. The print job will
keep resubmitting the failed sheets until the error is solved or
the retry timeout is exceeded.

4.2.1.16.7.3.2 Dataset Specific Conformance for Basic Film Box SOP Class for Basic Color Print Meta
N-ACTION-SCU
The behavior of the Azurion R3.0 for status codes in an N-ACTION response is summarized in Table 66.
Table 66: N-ACTION-RQ Dataset Specification.

Attribute Name Tag VR Value Presence of Value Source Comment

SOP Class UID 0008,0016 UI ALWAYS AUTO

SOP Instance UID 0008,0018 UI ALWAYS AUTO

4.2.1.16.7.4 SOP Specific Conformance for Basic Color Image Box SOP Class for Basic Color
Print Meta
4.2.1.16.7.4.1 Dataset Specific Conformance for Basic Color Image Box SOP Class for Basic Color
Print Meta N-SET-SCU
This application entity supports the attributes described in the Table 67.

Table 67: N-SET-RQ Dataset Specification.

Attribute Name Tag VR Value Presence of Value Source Comment

SOP Class UID 0008,0016 UI ALWAYS AUTO

SOP Instance UID 0008,0018 UI ALWAYS AUTO
Image Box 2020,0010 US ANAP AUTO
Position
Polarity 2020,0020 CS ANAP AUTO
Samples Per Pixel 0028,0002 US ANAP AUTO
Photometric 0028,0004 CS ANAP AUTO
Interpretation
Rows 0028,0010 US ANAP AUTO
Columns 0028,0011 US ANAP AUTO
Pixel Aspect Ratio 0028,0034 IS ANAP AUTO
Bits Allocated 0028,0100 US ANAP AUTO
Bits Stored 0028,0101 US ANAP AUTO
High Bit 0028,0102 US ANAP AUTO
Pixel 0028,0103 US ANAP AUTO
Representation
Pixel Data 7FE0,0010 OW/OB ANAP AUTO

The details regarding the response behavior to status codes are provided in Table 68.

Table 68: Status Response

Service Status Error Code Further Meaning Behavior

Success 0000 Successful operation The print job continues.
Warning 0107 Any warning The print job continues, and the warning is logged.
Error 0105 Any error The association is aborted using A-ABORT. The print job will
keep resubmitting the failed sheets until the error is solved or
the retry timeout is exceeded.
 2022 Koninklijke Philips N.V.
SNIP-IOCC-T-020001.09 (Version 2.2) Page 53 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved

Service Status Error Code Further Meaning Behavior

0106 Any error The association is aborted using A-ABORT. The print job will
keep resubmitting the failed sheets until the error is solved or
the retry timeout is exceeded.

4.2.1.16.7.5 SOP Specific Conformance for Basic Color Image Box SOP Class for Basic Color
Print Meta
4.2.1.16.7.5.1 Dataset Specific Conformance for Printer SOP Class for Basic Color Print Meta N-
EVENT-REPORT-SCP
This application entity supports the attributes described in the Table 69.

Table 69: N-EVENT-REPORT-RSP Dataset Specification.

Presence of
Attribute Name Tag VR Value Source Comment
Value
SOP Class UID 0008,0016 UI ALWAYS AUTO
SOP Instance UID 0008,0018 UI ALWAYS AUTO

4.2.1.17 Association Acceptance Policy

The Application Entity will respond to a received Association rejection as shown in the Table 70.

Table 70: Association Rejection response

Result Source Reason/Diagnosis Behavior

1-rejected-permanent 1-DICOM UL service-user 1-no-reason-given Log entry
2-application-context-name-not- Log entry
supported
3-calling-AE-title-not-recognized Log entry
7-called- AE-title-not-recognized Log entry
2-DICOM UL service-provider 1-no-reason-given Log entry
(ACSE related function) 2-no-reason-given Log entry
3-DICOM UL service-provider 1-temporary-congestion Log entry
(Presentation related function) 2-local-limit-exceeded Log entry
2-rejected-transient 1-DICOM UL service-user 1-no-reason-given Log entry
2-application-context-name-not- Log entry
supported
3-calling-AE-title-not-recognized Log entry
7-called- AE-title-not-recognized Log entry
2-DICOM UL service-provider 1-no-reason-given Log entry
(ACSE related function) 2-no-reason-given Log entry
3-DICOM UL service-provider 1-temporary-congestion Log entry
(Presentation related function) 2-local-limit-exceeded Log entry

The behavior of the Azurion R3.0 during Abort Handling is summarized in Table 71.
Table 71: Association Abort Handling

Source Reason/Diagnosis Behavior

0 – DICOM UL service-user 0 – reason-not-specified Log entry
2 – DICOM UL service-provider 0 – reason-not-specified Log entry

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 54 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved
1 – unrecognized-PDU Log entry
2 – unexpected-PDU Log entry
4 – unrecognized-PDU-parameter Log entry
5 – unexpected-PDU-parameter Log entry
6 – invalid-PDU-parameter-value Log entry

4.2.1.18 (Real-World) Activity – Verification as SCP

4.2.1.18.1 Description and Sequencing of Activities
A remote system requests verification from Azurion R3.0 using the C-ECHO command.

Figure 14: (Real World) Activity – Verification as SCP Accepted Presentation Contexts

The presentation contexts are defined in next table.

Table 72: Acceptable Presentation Contexts for (Real-World) Activity – Verification as SCP

Presentation Context Table

Abstract Syntax Transfer Syntax

Extended
Role
Negotiation
Name UID Name List UID List
Verification SOP Class 1.2.840.10008.1.1 Explicit VR Little Endian 1.2.840.10008.1.2.1 SCP None
Implicit VR Little Endian 1.2.840.10008.1.2

4.2.1.18.2 SOP Specific Conformance for Verification SOP Class

Azurion R3.0 (C-ECHO SCP) provides standard conformance to the DICOM V3.0 verification SOP Class.

4.2.1.18.2.1 Dataset Specific Conformance for Verification C-ECHO SCP

This part of the section includes the dataset specific behavior, i.e., error codes, error and exception handling, time-outs, etc.

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 55 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved
Table 73: Status Response

Service Status Error Code Further Meaning Behavior

Success 0000 Success C-ECHO command was successful received.

4.2.1.19 (Real-World) Activity – Image Import

4.2.1.19.1 Description and Sequencing of Activities
The real world activity associated with the C-STORE operation is the storage of the image in the memory of the system upon which
Azurion R3.0 is running in order to make it available for immediate processing by applications. Azurion R3.0 will issue a failure status if
it is unable to store the image in the memory.

Figure 15: (Real World) Activity – Image Import.

4.2.1.19.2 Accepted Presentation Contexts

The presentation contexts are defined in the Table 74.

Table 74: Acceptable Presentation Contexts for (Real-World) Activity – Image Import

Presentation Context Table

Abstract Syntax Transfer Syntax

Extended
Role
Negotiation
Name UID Name List UID List
Secondary Capture Image 1.2.840.10008.5.1.4.1.1.7 Implicit VR Little Endian 1.2.840.10008.1.2 SCP None
Storage SOP Class Explicit VR Little Endian 1.2.840.10008.1.2.1
Explicit VR Big Endian 1.2.840.10008.1.2.2
JPEG Lossless, Non- 1.2.840.10008.1.2.4.70
Hierarchical, First-Order
Prediction (Process 14)
Grayscale Softcopy 1.2.840.10008.5.1.4.1.1.11.1 Implicit VR Little Endian 1.2.840.10008.1.2 SCP None
Presentation State Storage SOP Explicit VR Little Endian 1.2.840.10008.1.2.1
Class
Explicit VR Big Endian 1.2.840.10008.1.2.2
X-Ray Angiographic Image 1.2.840.10008.5.1.4.1.1.12.1 Implicit VR Little Endian 1.2.840.10008.1.2 SCP None
Storage SOP Class Explicit VR Little Endian 1.2.840.10008.1.2.1
Explicit VR Big Endian 1.2.840.10008.1.2.2

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 56 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved

Presentation Context Table

Abstract Syntax Transfer Syntax

Extended
Role
Negotiation
Name UID Name List UID List
JPEG Lossless, Non- 1.2.840.10008.1.2.4.70
Hierarchical, First-Order
Prediction (Process 14)

4.2.1.19.3 SOP Specific Conformance for Storage SOP Classes

This section and sub-section include the manufacturer SOP and Dataset specific information as well the status codes and their
corresponding behavior.

Azurion R3.0 provides standard conformance to the DICOM V3.0 Storage Service Class as a SCP. Azurion R3.0 conforms to the
SOPs of the Storage Service Class at Level 2 (Full). In case of a successful C-STORE, the stored image may be accessed by the
processing applications.

4.2.1.19.3.1 Dataset Specific Conformance for C-STORE-RSP

This includes the dataset specific behavior, i.e., error codes, error and exception handling, time-outs, etc.

Table 75: Status Response

Service Status Error Code Further Meaning Behavior

Success 0000 Successful stored Whenever the store operation succeeded.
Failure Cxxx Failed Whenever the store operation failed.
Failure A901 Data set does not match SOP class When the import operation has failed.
* Any other status Unsuccessful operation Operation not completed, and reason is logged.

4.3 Network Interfaces

4.3.1 Physical Network Interfaces
The System provides only DICOM V3.0 TCP/IP Network Communication Support as defined in PS 3.8 of the standard.
TCP/IP is the only protocol stack supported.
Supported physical medium include:
 IEEE 802.3-1995, 10BASE-T
 IEEE 802.3-1995, 100BASE-TX (Fast Ethernet)
 IEEE 802.3, 1000BASE-X (Fiber Optic Gigabit Ethernet).
The TCP/IP Stack as supported by the underlying Operating System. The API is the WinSock 2 interface as supported by the
underlying Operating System.

4.3.2 Additional Protocols

4.3.2.1 Basic Application-Level Confidentiality Profile
See Section 7.1.5.

4.3.3 IPv4 and IPv6 Support

Azurion R3.0 supports DICOM communication, as per DICOM standards/specifications, for both IPv4 and IPv6. However, not both IP
versions at the same time. For BCP 195 secure connection see section 7.2.2.

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 57 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved

4.4 Configuration
Any implementation’s DICOM conformance may be dependent upon configuration, which takes place at the time of installation. Issues
concerning configuration are addressed in this section.

4.4.1 AE Title/Presentation Address Mapping

An important installation issue is the translation from AE title to presentation address. How this is to be performed is described here.

4.4.1.1 Local AE Titles

The local AE title mapping and configuration are specified as:

Table 76: AE Title Configuration

Application Entity Default AE Title Default TCP/IP Port

IENGINE_SCU IENGINE_SCU 29536

4.4.1.2 Remote AE Title/Presentation Address Mapping

All relevant remote applications that should be able to setup a DICOM association towards Azurion R3.0 and that should be able to
accept a DICOM association from Azurion R3.0 must be configured during Azurion R3.0 configuration time.

4.4.2 Parameters
The specification of important operational parameters, their default value and range (if configurable) are specified here.
Table 77: Configuration Parameters

Parameter Configurable Default Value

AE Title Yes IENGINE_SCU
Port number Yes 29536
IP host name/address Yes -

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 58 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved

5 Media Interchange
5.1 Implementation model
The implementation model identifies the DICOM Application Entities for Media in specific implementation and relates the Application
Entities to Real-World Activities.

5.1.1 Application Data Flow Diagram

As part of the implementation model, an application data flow diagram is included. The next Figure shows the media interchange
application data flow as a functional overview of the Media AE for DICOM CD and DVD.

Figure 16: Application Data Flow Diagram

The Media AE acts as a FSC for CD-R and DVD, when writing the selected images in a patient folder onto the medium.

5.1.2 Functional Definitions of AE’s

The Azurion R3.0 implements the following functions for DICOM media.
 Write a DICOM file-set onto the medium.
 Create a DICOMDIR file.

5.1.3 Sequencing of Real World Activities

Not applicable.

5.2 AE Specifications
This section in the DICOM Conformance Statement specifies a set of Media Application Entities.

5.2.1 Media Storage Media – Specification

This section contains general policies that apply to all of the Application Entities described in subsequent section. The Azurion R3.0
provides standard conformance to the DICOM interchange option of the media storage service class, and follows the specifications as
defined in the DICOM standard – Media Storage and File Format for Data Interchange (PS 3.10) and Media Storage Application
Profiles (PS 3.11).

The Azurion R3.0 supports multi-patient and multi-session for CD-R media (both reading and writing). For one or more Application
Profiles, the following table shows the Real-World Activities and the roles of each of these Real-World Activities.

Table 78: AE Media Storage related Application Profiles, Real-World Activities and Roles

Supported Application Profile Identifier Real-World Activities Roles

General Purpose CD-R Interchange STD-GEN-CD Create File-set FSC/FSR

General Purpose Interchange on DVD-RAM Media STD-GEN-DVD-RAM Create File-set FSC/FSR
General Purpose USB Media Interchange STD-GEN-USB Create File-set FSC/FSR/FSU

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 59 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved

5.2.1.1 File Meta Information for the Media AE

Table 79: Implementation Identifying Information

Property Value
Implementation Class UID: 1.3.46.670589.7.29.3.0.1
Implementation Version Name: Azurion

5.2.1.2 Real-World Activities

The AE specification contains a description of the Real-World Activities, which invoke the particular AE.

5.2.1.3 RWA – Read File-set

Azurion R3.0 can read SC, XA and GSPS objects.

5.2.1.3.1 Media Storage Application Profile

Refer to the table in section 5.2.1, Table 78: AE Media Storage related Application Profiles, Real-World Activities and Roles.

5.2.1.3.1.1 Options
Not applicable.

5.2.1.4 RWA – Create File-set

This Media Application Entity has a File-set Creator functionality which is described here.

Write Images
The Azurion R3.0 acts as an FSC when writing DICOM objects onto DICOM media. The Azurion R3.0 can also store private attributes.
When the Azurion R3.0 has to write objects to DICOM media, it can encounter the following situation.

The objects were previously received via C-STORE operations. Some attributes in the received images have a zero-length value
(Type 2 attributes). However, the Application Profile specifies some of these attributes as type 1: they must have a value. In such
cases the Azurion R3.0 supplies a value for the following attributes (if necessary):
 Patient ID;
 Study ID;
 Series Number;
 Instance number;
 Study Date;
 Study Time.
The mechanism of generating a value for Patient ID is to create a new value (i.e., Study Instance UID) for each new study written to
the medium, even if this study belongs to a patient recorded earlier. Study ID is assigned the value of the first Requested Procedure ID
(0040, 1001) encountered in the Request Attributes Sequence (0040, 0275).

5.2.1.4.1 Media Storage Application Profile

Refer to the table in section 5.2.1, Table 78: AE Media Storage related Application Profiles, Real-World Activities and Roles.

5.2.1.4.1.1 Options
Not applicable.

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 60 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved

5.2.1.5 RWA – Update File-set

Not applicable.

5.2.1.5.1 Media Storage Application Profile

Refer to the table in section 5.2.1, Table 78: AE Media Storage related Application Profiles, Real-World Activities and Roles.

5.2.1.5.1.1 Options
Not applicable.

5.3 Augmented and Private Application Profiles

Not applicable

5.4 Media Configuration

Not applicable.

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 61 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved

6 Support of Character Sets

Any support for character sets in Network and Media services is described here.

Table 80: Supported DICOM Character Sets

ISO
Character Code
Defined Term ESC Sequence Registration Character Set
Set Description Element
Number
Latin alphabet No. 1 ISO_IR 100 - ISO-IR 100 G1 Supplementary set of ISO 8859
- ISO-IR 6 G0 ISO 646
Japanese ISO 2022 IR 159 ESC 02/04 ISO-IR 159 G0 JIS X 0212: Supplementary Kanji
02/0804/04 set
Japanese ISO 2022 IR 87 ESC 02/04 04/02 ISO-IR 87 G0 JIS X 0208: Kanji and Hiragana
Japanese ISO 2022 IR 13 ESC 02/09 04/09 ISO-IR 13 G1 JIS X 0201: Katakana
ESC 02/08 04/10 ISO-IR 14 G0 JIS X 0201: Romaji (only for the
patient’s name)
Chinese GB18030 - GB18030 - -

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 62 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved

7 Security
7.1 Introduction
The security section describes security features implemented by this product. It includes description of non-DICOM network protocols,
list of supported DICOM security profiles as well other applicable security related profiles.

7.2 DICOM Security Profiles Support

7.2.1 Secure Use and User Identity Profiles
Table 81: Secure Use and User Identity Profiles

Profile Creator/Sender Consumer/Receiver Reference

Audit Trail Message Format Yes N/A 7.2.1.1.1

Audit Trail Message Transmission Profile - Yes N/A 7.2.1.1.1
SYSLOG-TLS

7.2.1.1 DICOM Security Profile Details

7.2.1.1.1 Audit Trail Messages
The Audit Trail Component is a component of Azurion R3.0 and can create messages according to the ATNA, IHE defined standard.
Actors are information systems or components of information systems that produce, manage, or act on categories of information
required by operational activities in the enterprise. The Audit Trail Component allows security officers in an institution to audit activities,
to detect non-compliant behavior in the enterprise, and to facilitate detection of improper creation, access, modification and deletion of
Protected Health Information (PHI), where PHI data is considered as information records (Registration, Order, Study/Procedure,
Reports and to a lesser degree Images/Presentation States), and not the flow of information between the systems. This includes
information exported to and imported from every secured node in the “secured domain”.
The messages will be created and sent to a syslog server according to the syslog protocol. The time that is used will be the local time
of the system which is synchronized with the NTP Time Server. The timeserver and syslog server are elements of the Hospital
infrastructure

The following table specifies the DICOM Audit Messages that Azurion R3.0 can detect and report. It defines the list of triggers that will
cause audit message to be generated if these triggers can be configured or not. It also specifies if the content of the Audit message
can be configured or not.

Table 82: DICOM Specific Audit Messages

Audit Message Used

Data Export Y
Data Import Y
User Created Y
User Deleted Y
User Updated Y
User Group Mapping Changed Y
Begin Transferring DICOM Instances Y
DICOM Instances Accessed Y
DICOM Instances Transferred Y
Study Created Y
Emergency Study Created Y
Study Updated Y
DICOM Study Deleted Y
Series Updated Y

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 63 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved
Procedure Open With Y
Procedure Started Y
Procedure Complete Y
Procedure Suspend Y
Security Alert Y
User Authentication - User Login Y
User Authentication - User Logged Off Y
Node Added Y
Node Removed Y
Patient Deleted Y
Application Activity Y

7.2.2 Security Transport Connection Profiles

Azurion R3.0 supports BCP 195 TLS Secure Transport Connection Profile.

Table 83: Secure Transport Connections Profiles

Profile Secured AE Sender Receiver

BCP195 TLS Secure Transport Connection ALL Y Y

The Azurion R3.0 supports X.509 certificates. The following TLS Certification checks will be done (TLS Handshake). The machine
(either server or client) that will send its certificate will:

 Choose the certificate according to Common Name (CN) value in the Subject-field.
 This name is case-sensitive. All present certificates should have unique CN names.
The server verifies:

 That the client certificate is a X.509 certificate which is not tampered with
 That the client certificate is in the list of trusted certificates
 That the client certificate is not expired (present time is between “Valid From” and “Valid To” fields of the X.509 certificate)
 That the client certificate has the correct purpose (at least the Client Authentication purpose)
The client verifies:

 That the server certificate is a X.509 certificate which is not tampered with
 That the server certificate is in the list of trusted certificates
 That the server certificate is not expired (present time is between “Valid From” and “Valid To” fields of the X.509 certificate)
 That the server certificate has the correct purpose (at least Server Authentication purpose)
No verification is done on:

 Revocation of certificates
 Limiting the connection to a limited set of IP-addresses
Node authentication with or without encryption is only possible when both nodes have:

 An access to their own private keys

 An access to a copy of the certificate of the other node containing its public key
The Azurion R3.0 can only read certificates from the certificate stores of the HKEY_LOCAL_MACHINE registry key. It is the
responsibility of the Hospital to setup and maintain the certificate stores. This includes the removal of revoked certificates and
certificate updates prior to their expiration. Since neither X.500 directories, Lightweight Directory Access Protocol (LDAP) nor
Certificate Revocation Lists (CRLs) are supported, the whole certificate chain needs to be replaced after a security breach.

The following figure presents the message flow of TLS handshake supported.

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 64 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved

Figure 17: Message flow of TLS handshake

Azurion R3.0 supports Secure communication as a “mode of operation”. This functionality will be used by the DICOM nodes, which
can authenticate each other before they exchange DICOM information. For secure communication, the TLS protocol v1.0,1.1 &1.2 are
used which provides message authentication, integrity, confidentiality, and replay protection. Confidentiality is optional and can be
controlled by the encryption settings. The system supports a secure negotiation using the following Cipher Suites:

Table 84: Secure Transport Connections and Cipher Suites

Profile Cipher Suite

BCP 195 TLS Secure Transport Connection TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384

TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
TLS_DHE_RSA_WITH_AES_256_GCM_SHA384
TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 65 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved

TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
TLS_RSA_WITH_AES_256_GCM_SHA384
TLS_RSA_WITH_AES_128_GCM_SHA256
TLS_RSA_WITH_AES_256_CBC_SHA256
TLS_RSA_WITH_AES_128_CBC_SHA256
TLS_RSA_WITH_AES_256_CBC_SHA
TLS_RSA_WITH_AES_128_CBC_SHA
TLS_DHE_RSA_WITH_AES_256_CBC_SHA
TLS_DHE_RSA_WITH_AES_128_CBC_SHA
TLS_DHE_DSS_WITH_AES_256_CBC_SHA256
TLS_DHE_DSS_WITH_AES_128_CBC_SHA256
TLS_DHE_DSS_WITH_AES_256_CBC_SHA
TLS_DHE_DSS_WITH_AES_128_CBC_SHA

Note: Cipher suites that include cryptographic MD5,RC4,DES or 3DES are not supported by the system.

7.2.3 Media Storage Security Profiles

Not applicable

7.2.4 Attribute Confidentiality Profiles

Azurion R3.0 conforms to the Basic Application-Level Confidentiality Profile as a de-identifier. This functionality is targeted towards
creating a special purpose, de-identified version of an already existing Data set.
Table 85: Attribute Confidentiality Profiles

Profile Option AE De-identifier Re-identifier Configurable

Basic Application-Level Basic Profile ALL Y N Y

Confidentiality

Table presents all attributes that can be de-identified by the Azurion R3.0. Each Attribute to be protected has its value replaced by a
different “replacement value” which does not allow identification of the patient.

Table 86: De-identified Attributes

Attribute Name Tag VR Replacement Value

Patient Name 0010,0010 PN Assign user-specified value
Patient ID 0010,0020 LO Generate and provide a new ID
Patient’s Birth Date 0010,0030 DA Make Empty
Patient’s Sex 0010,0040 CS Make Empty
Other Patient Ids 0010,1000 LO Make Empty
Patient’s Size 0010,1020 DS Make Empty
Patient Weight 0010,1030 DS Make Empty
Ethnic Group 0010,2160 SH Make Empty
Additional Patient’s History 0010,21B0 LT Make Empty
Patient Comments 0010,4000 LT Make Empty
SOP Instance UID 0008,0018 UI Generate and provide new ID
Accession Number 0008,0050 SH Make Empty
Institution Name 0008,0080 LO Make Empty
Referring Physician’s Name 0008,0090 PN Make Empty
Device Serial Number 0008,1000 LO Make Empty
Station Name 0008,1010 SH Make Empty

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 66 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved

Attribute Name Tag VR Replacement Value

Institutional Department Name 0008,1040 LO Make Empty
Performing Physician’s Name 0008,1050 PN Make Empty
Operators’ Name 0008,1070 PN Make Empty
Referenced SOP Instance UID 0008,1155 UI Generate and provide a new ID
Protocol Name 0018,1030 LO Make Empty
Study ID 0020,0010 SH Make Empty
Study Instance UID 0020,000D UI Generate and provide a new ID
Series Instance UID 0020,000E UI Generate and provide a new ID
Performed Procedure Step Description 0040,0254 LO Make Empty
Request Attributes Sequence 0040,0275 SQ Generate and provide dummy value
Series Description 0008,103E LO Make Empty

7.2.5 Digital Signature Profiles

Not applicable

7.2.6 Basic Network Address Management Profiles

Not applicable.

7.2.7 Application Configuration Management Profiles

Not applicable.

7.2.8 Time Synchronization Profiles

Azurion R3.0 conforms to the IHE Consistent Time Profile as time client. It is possible to synchronize time with the NTP Timeserver
using serviceability. The NTP Timeserver is an element of Hospital Infrastructure.

7.3 Association Level Security

The Azurion R3.0 accepts associations from any AE-Title but only for Storage commit N-Event-Report, and C-Store as SCP services.
If Azurion R3.0 is configured to use secure mode, then the incoming associations (for Azurion R3.0 as SCP) should follow secure
mode.

7.4 Application Level Security

The Azurion R3.0 allows the use of either a conventional (non-secure) DICOM communication or a secure DICOM communication
based on the Transport Layer Security (TLS) protocol [TLS]. If configured, the Azurion R3.0 supports security
Measures for:
 Secure authentication of a node
 Integrity and confidentiality of transmitted data
 Replay protection
 Generation of audit trail records
 Access control and user authentication.

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 67 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved

8 Annexes
8.1 IOD Contents
8.1.1 Created SOP Instances
This section specifies each IOD created by this application and specifies the content for each IOD created (including private IODs).
For each attribute in the IOD the following information is supplied:
 Attribute name
 Tag
 VR – Value representation
 Value – specifies possible values
 Presence of value – specifies if attribute is always present or only under specific conditions
 Source of value – specifies the source of the value
 Comment – gives additional information on the attribute

Abbreviations used in the IOD tables for the column “Presence of Module” are:
ALWAYS The module is always present.
CONDITIONAL The module is used under specified condition.

Abbreviations used in the Module table for the column “Presence of Value” are:
ALWAYS The attribute is always present with a value.
EMPTY The attribute is always present without any value. (attribute sent zero length)
VNAP The attribute is always present and its Value is Not Always Present.
(attribute sent zero length if no value is present)
ANAP The attribute is present under specified condition – if present then it will always have a value.

The abbreviations used in the Module table for the column “Source” are:
AUTO The attribute value is generated automatically.
CONFIG The attribute value source is a configurable parameter.
COPY The attribute value source is another SOP instance.
FIXED The attribute value is hard coded in the application.
IMPLICIT The attribute value source is a user-implicit setting.
MPPS The attribute value is the same as that use for Modality Performed Procedure Step.
MWL The attribute value source is a Modality Worklist.
USER The attribute value source is explicit user input.

8.1.1.1 List of Created SOP Classes

Table 87: List of Created SOP Classes

SOP Class Name SOP Class UID

Secondary Capture Image Storage SOP Class 1.2.840.10008.5.1.4.1.1.7
Grayscale Softcopy Presentation State Storage SOP Class 1.2.840.10008.5.1.4.1.1.11.1
X-Ray Angiographic Image Storage SOP Class 1.2.840.10008.5.1.4.1.1.12.1
X-Ray Radiation Dose Structured Report SOP Class 1.2.840.10008.5.1.4.1.1.88.67

8.1.1.2 Secondary Capture Image Storage SOP Class

Table 88: SOP Class Modules

Information Entity Module Presence

Patient Patient Module ALWAYS
Study General Study Module ALWAYS

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 68 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved
Patient Study Module ALWAYS
Series General Series Module ALWAYS
Equipment General Equipment Module ALWAYS
SC Equipment Module ALWAYS
Image General Image Module ALWAYS
Image Pixel Module ALWAYS
General Reference Module User Defined
SC Image Module ALWAYS
VOI LUT Module ALWAYS
SOP Common Module ALWAYS

Table 89: Patient Module

Presence of
Attribute Name Tag VR Value Source Comment
Value
Referenced Patient 0008,1120 SQ ANAP MWL
Sequence
>Referenced SOP Class 0008,1150 UI ALWAYS MWL
UID
>Referenced SOP Instance 0008,1155 UI ALWAYS MWL
UID
Patient’s Name 0010,0010 PN VNAP MWL,USER
Patient ID 0010,0020 LO VNAP MWL,USER
Patient’s Birth Date 0010,0030 DA VNAP MWL,USER
Patient’s Sex 0010,0040 CS VNAP MWL,USER
Other Patient IDs 0010,1000 LO ANAP MWL,USER
Ethnic Group 0010,2160 SH ANAP MWL
Patient Comments 0010,4000 LT ANAP MWL

Table 90: General Study Module

Presence of
Attribute Name Tag VR Value Source Comment
Value
Study Date 0008,0020 DA VNAP AUTO
Study Time 0008,0030 TM VNAP AUTO
Accession Number 0008,0050 SH VNAP MWL
Referring Physician’s Name 0008,0090 PN VNAP MWL
Study Description 0008,1030 LO VNAP USER,MWL Copied from Requested
procedure step
description
Procedure Code Sequence 0008,1032 SQ ANAP AUTO,MWL
>Code Value 0008,0100 SH ALWAYS AUTO,MWL
>Coding Scheme 0008,0102 SH ALWAYS AUTO,MWL
Designator
>Coding Scheme Version 0008,0103 SH ALWAYS AUTO,MWL
>Code Meaning 0008,0104 LO ALWAYS AUTO,MWL
Referenced Study 0008,1110 SQ ALWAYS AUTO,MWL
Sequence
>Referenced SOP Class 0008,1150 UI ALWAYS AUTO,MWL
UID
>Referenced SOP Instance 0008,1155 UI ALWAYS AUTO,MWL
UID
Study Instance UID 0020,000D UI ALWAYS AUTO,MWL

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 69 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved
Presence of
Attribute Name Tag VR Value Source Comment
Value
Study ID 0020,0010 SH VNAP AUTO,MWL, In case Study ID is
USER empty, accession
number is used. If that
is also empty then the
system generates a
value for it

Table 91: Patient Study Module

Attribute Name Tag VR Value Presence of Source Comment

Value
Patient’s Size 0010,1020 DS ALWAYS MWL,USER When received from the
MWL SCP, the value
can still be modified
Patient’s Weight 0010,1030 DS ALWAYS MWL,USER When received from the
MWL SCP, the value
can still be modified
Medical Alerts 0010,2000 LO VNAP MWL,USER
Allergies 0010,2110 LO VNAP MWL,USER
Additional Patient History 0010,21B0 LT VNAP MWL

Table 92: General Series Module

Presence of
Attribute Name Tag VR Value Source Comment
Value
Series Date 0008,0021 DA ANAP AUTO
Series Time 0008,0031 TM ANAP AUTO
Modality 0008,0060 CS OT ALWAYS AUTO
Series Description 0008,103E LO ANAP AUTO
Performing Physicians’ Name 0008,1050 PN ANAP MWL,USER
Operators’ Name 0008,1070 PN ANAP MWL, USER
Referenced Performed 0008,1111 SQ Identifies the MPPS SOP ANAP AUTO,
Procedure Step Sequence Instance to which this image MPPS
is related
>Referenced SOP Class UID 0008,1150 UI MPPS SOP Class UID ALWAYS MPPS
>Referenced SOP Instance 0008,1155 UI MPPS SOP Instance UID ALWAYS MPPS
UID
Protocol Name 0018,1030 LO ANAP AUTO
Series Instance UID 0020,000E UI ALWAYS AUTO
Series Number 0020,0011 IS VNAP AUTO
Laterality 0020,0060 CS ANAP AUTO
Performed Procedure Step 0040,0244 DA ANAP AUTO
Start Date
Performed Procedure Step 0040,0245 TM ANAP AUTO
Start Time
Performed Procedure Step 0040,0253 SH ANAP AUTO,
ID MWL
Performed Procedure Step 0040,0254 LO ANAP MWL
Description
Request Attributes Sequence 0040,0275 SQ ANAP MWL
>Accession Number 0008,0050 SH ANAP MWL
>Requested Procedure 0032,1060 LO ANAP MWL
Description

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 70 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved
Presence of
Attribute Name Tag VR Value Source Comment
Value
>Requested Procedure Code 0032,1064 SQ ANAP MWL
Sequence
>>Code Value 0008,0100 SH ALWAYS MWL
>>Coding Scheme 0008,0102 SH ALWAYS MWL
Designator
>>Coding Scheme Version 0008,0103 SH ALWAYS MWL
>>Code Meaning 0008,0104 LO ALWAYS MWL
>Scheduled Procedure Step 0040,0007 LO ALWAYS MWL
Description
> Scheduled Protocol Code 0040,0008 SQ ALWAYS MWL
Sequence
>>Code Value 0008,0100 SH ALWAYS MWL
>>Coding Scheme 0008,0102 SH ALWAYS MWL
Designator
>>Coding Scheme Version 0008,0103 SH ALWAYS MWL
>>Code Meaning 0008,0104 LO ALWAYS MWL
>Scheduled Procedure Step 0040,0009 SH ANAP MWL
ID
>Requested Procedure ID 0040,1001 SH ANAP MWL

Table 93: General Equipment Module

Presence of
Attribute Name Tag VR Value Source Comment
Value
Manufacturer 0008,0070 LO Philips ALWAYS AUTO
Institution Name 0008,0080 LO VNAP CONFIG
Station Name 0008,1010 SH VNAP CONFIG
Institutional Department 0008,1040 LO VNAP AUTO
Name
Manufacturer’s Model Name 0008,1090 LO Azurion ANAP AUTO
Device Serial Number 0018,1000 LO VNAP AUTO
Software Versions 0018,1020 LO 3.0.0 VNAP AUTO

Table 94: SC Equipment Module

Presence of
Attribute Name Tag VR Value Source Comment
Value
Modality 0008,0060 CS OT ANAP AUTO
Conversion Type 0008,0064 CS WSD ALWAYS AUTO

Table 95: General Image Module

Presence
Attribute Name Tag VR Value Source Comment
of Value
Image Type 0008,0008 CS DERIVED\PRIMARY ALWAYS AUTO
Content Date 0008,0023 DA ALWAYS AUTO
Content Time 0008,0033 TM ALWAYS AUTO
Instance Number 0020,0013 IS ALWAYS AUTO
Patient Orientation 0020,0020 CS VNAP AUTO
Lossy Image Compression 0028,2110 CS 00 ALWAYS AUTO

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 71 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved
Table 96: General Reference Module

Presence of
Attribute Name Tag VR Value Source Comment
Value
Derivation Description 0008,2111 ST ANAP AUTO

Table 97: Image Pixel Module

Presence
Attribute Name Tag VR Value Source Comment
of Value
Samples per Pixel 0028,0002 US ALWAYS AUTO
Photometric Interpretation 0028,0004 CS RGB ALWAYS AUTO
Planar Configuration 0028,0006 US ANAP AUTO
Rows 0028,0010 US ALWAYS AUTO
Columns 0028,0011 US ALWAYS AUTO
Bits Allocated 0028,0100 US 8 or 16 ALWAYS AUTO
Note: For Snapshot function,
this number is 8
Bits Stored 0028,0101 US 8 or 12 ALWAYS AUTO
Note: For Snapshot function,
this number is 8
High Bit 0028,0102 US ALWAYS AUTO
Pixel Representation 0028,0103 US 0000H ALWAYS AUTO
Smallest Image Pixel 0028,0106 US/SS ANAP AUTO
Value
Largest Image Pixel Value 0028,0107 US/SS ANAP AUTO
Pixel Data 7FE0,0010 OW/OB ALWAYS AUTO

Table 98: SC Image Module

Presence
Attribute Name Tag VR Value Source Comment
of Value
Date of Secondary Capture 0018,1012 DA ANAP AUTO
Time of Secondary Capture 0018,1014 TM ANAP AUTO
Nominal Scanned Pixel 0018,2010 DS ANAP AUTO
Spacing
Pixel Spacing Calibration 0028,0A02 CS ANAP AUTO
Type

Table 99: VOI LUT Module

Presence of
Attribute Name Tag VR Value Source Comment
Value
Window Center 0028,1050 DS ALWAYS AUTO
Window Width 0028,1051 DS ALWAYS AUTO

Table 100: SOP Common Module

Presence of
Attribute Name Tag VR Value Source Comment
Value
Specific Character Set 0008,0005 CS ANAP AUTO
Instance Creation Date 0008,0012 DA ANAP AUTO
Instance Creation Time 0008,0013 TM ANAP AUTO
SOP Class UID 0008,0016 UI 1.2.840.10008.5.1.4.1.1.7 ALWAYS AUTO
SOP Instance UID 0008,0018 UI ALWAYS AUTO
Instance Number 0020,0013 IS ANAP AUTO

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 72 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved

8.1.1.3 Grayscale Softcopy Presentation State Storage SOP Class

Table 101: SOP Class Modules

Information Entity Module Presence

Patient Patient Module Always
Study General Study Module Always
Patient Study Module Always
Series General Series Module Always
Presentation Series Module Always
Equipment General Equipment Module Always
Presentation State Presentation State Identification Module Always
Presentation State Relationship Module Always
Presentation State Shutter Module Always
Display Shutter Module Always
Bitmap Display Shutter Module Always
Displayed Area Module Always
Graphic Layer Module Always
Softcopy Presentation LUT Module Always
Softcopy VOI LUT module Always
SOP Common Module Always

Table 102: Patient Module

Presence of
Attribute Name Tag VR Value Source Comment
Value
Referenced Patient Sequence 0008,1120 SQ ANAP MWL
>Referenced SOP Class UID 0008,1150 UI ALWAYS MWL
>Referenced SOP Instance UID 0008,1155 UI ALWAYS MWL
Patient’s Name 0010,0010 PN VNAP MWL,USER
Patient ID 0010,0020 LO VNAP MWL,USER
Patient’s Birth Date 0010,0030 DA VNAP MWL,USER
Patient’s Sex 0010,0040 CS VNAP MWL,USER
Other Patient IDs 0010,1000 LO ANAP MWL,USER
Ethnic Group 0010,2160 SH ANAP MWL,USER
Patient Comments 0010,4000 LT ANAP MWL,USER

Table 103: General Study Module

Presence
Attribute Name Tag VR Value Source Comment
of Value
Study Date 0008,0020 DA VNAP AUTO
Study Time 0008,0030 TM VNAP AUTO
Accession Number 0008,0050 SH VNAP MWL
Referring Physician’s Name 0008,0090 PN VNAP MWL
Study Description 0008,1030 LO VNAP USER,MWL Copied from
Requested procedure
step description.
Procedure Code Sequence 0008,1032 SQ ANAP MWL,AUTO
>Code Value 0008,0100 SH ALWAYS MWL,AUTO
>Coding Scheme Designator 0008,0102 SH ALWAYS MWL,AUTO
>Coding Scheme Version 0008,0103 SH ALWAYS MWL,AUTO

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 73 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved
>Code Meaning 0008,0104 LO ALWAYS MWL,AUTO
Referenced Study Sequence 0008,1110 SQ ANAP MWL
>Referenced SOP Class UID 0008,1150 UI ALWAYS MWL
>Referenced SOP Instance UID 0008,1155 UI ALWAYS MWL
Study Instance UID 0020,000D UI ALWAYS AUTO
Study ID 0020,0010 SH VNAP AUTO, MWL, In case Study ID is
USER empty, accession
number is used. If
that is also empty
then the system
generates a value for
it

Table 104: Patient Study Module

Presence
Attribute Name Tag VR Value Source Comment
of Value
Patient’s Size 0010,1020 DS ALWAYS MWL, In meters. When
USER received from the
MWL SCP, the value
can still be modified
Patient’s Weight 0010,1030 DS ALWAYS MWL, In kilograms. When
USER received from the
MWL SCP, the value
can still be modified

Medical Alerts 0010,2000 LO VNAP MWL,USER

Allergies 0010,2110 LO VNAP MWL,USER
Additional Patient History 0010,21B0 LT VNAP MWL

Table 105: General Series Module

Presence
Attribute Name Tag VR Value of Source Comment
Value
Series Date 0008,0021 DA ANAP AUTO
Series Time 0008,0031 TM ANAP AUTO
Modality 0008,0060 CS PR ALWAYS AUTO
Series Description 0008,103E LO ALWAYS AUTO
Performing Physicians’ Name 0008,1050 PN ANAP MWL, USER

Operators’ Name 0008,1070 PN ANAP MWL, USER

Referenced Performed Procedure 0008,1111 SQ Identifies the MPPS SOP ANAP AUTO,
Step Sequence Instance to which this image is MPPS
related

>Referenced SOP Class UID 0008,1150 UI MPPS SOP Class UID ALWAYS MWL

>Referenced SOP Instance UID 0008,1155 UI MPPS SOP Instance UID ALWAYS MWL

Protocol Name 0018,1030 LO ANAP AUTO

Series Instance UID 0020,000E UI ALWAYS AUTO
Series Number 0020,0011 IS VNAP AUTO
Laterality 0020,0060 CS EMPTY AUTO
Performed Procedure Step Start 0040,0244 DA ALWAYS AUTO
Date

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 74 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved
Presence
Attribute Name Tag VR Value of Source Comment
Value
Performed Procedure Step Start 0040,0245 TM ALWAYS AUTO
Time
Performed Procedure Step ID 0040,0253 SH Same as MPPS ALWAYS AUTO,USER

Performed Procedure Step 0040,0254 LO ANAP MWL

Description
Request Attributes Sequence 0040,0275 SQ ANAP MWL
>Accession Number 0008,0050 SH ANAP MWL
>Issuer of Accession Number 0008,0051 SQ ANAP MWL
Sequence
>Referenced Study Sequence 0008,1110 SQ ANAP MWL
>>Referenced SOP Class UID 0008,1150 UI ALWAYS MWL
>>Referenced SOP Instance UID 0008,1155 UI ALWAYS MWL
>Study Instance UID 0020,000D UI ANAP MWL
>Requested Procedure Description 0032,1060 LO ANAP MWL
>Requested Procedure Code 0032,1064 SQ ANAP MWL
Sequence
>>Code Value 0008,0100 SH ALWAYS MWL
>>Coding Scheme Designator 0008,0102 SH ALWAYS MWL
>>Coding Scheme Version 0008,0103 SH ALWAYS MWL
>>Code Meaning 0008,0104 LO ALWAYS MWL
>Scheduled Protocol Code 0040,0008 SQ ANAP MWL
Sequence
>>Code Value 0008,0100 SH ALWAYS MWL
>>Coding Scheme Designator 0008,0102 SH ALWAYS MWL
>>Coding Scheme Version 0008,0103 SH ALWAYS MWL
>>Code Meaning 0008,0104 LO ALWAYS MWL
>>Protocol Context Sequence 0040,0440 SQ ANAP MWL
>>>Value Type 0040,A040 CS ALWAYS MWL
>>>Concept Name Code Sequence 0040,A043 SQ ALWAYS MWL
>>>>Code Value 0008,0100 SH ALWAYS MWL
>>>>Coding Scheme Designator 0008,0102 SH ALWAYS MWL
>>>>Code Meaning 0008,0104 LO ALWAYS MWL
>Reason for the Requested 0040,1002 LO ANAP MWL
Procedure
>Reason for Requested Procedure 0040,100A SQ ANAP MWL
Code Sequence
>>Code Value 0008,0100 SH ALWAYS MWL
>>Coding Scheme Designator 0008,0102 SH ALWAYS MWL
>>Context Identifier 0008,010F CS ANAP MWL
>>Context UID 0008,0117 UI ANAP MWL
>Scheduled Procedure Step ID 0040,0009 SH ALWAYS MWL

>Requested Procedure ID 0040,1001 SH ALWAYS MWL

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 75 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved
Table 106: Presentation Series Module

Presence
Attribute Name Tag VR Value Source Comment
of Value
Modality 0008,0060 CS PR ALWAYS AUTO

Table 107: General Equipment Module

Presence
Attribute Name Tag VR Value Source Comment
of Value
Manufacturer 0008,0070 LO Philips VNAP AUTO
Institution Name 0008,0080 LO VNAP AUTO
Station Name 0008,1010 SH VNAP AUTO
Institutional Department Name 0008,1040 LO VNAP AUTO
Manufacturer’s Model Name 0008,1090 LO Azurion ANAP AUTO
Device Serial Number 0018,1000 LO VNAP AUTO
Software Versions 0018,1020 LO 3.0.0 VNAP AUTO

Table 108: Presentation State Identification Module

Presence
Attribute Name Tag VR Value Source Comment
of Value
Instance Number 0020,0013 IS ALWAYS AUTO
Content Label 0070,0080 CS AS LAST SEEN ALWAYS AUTO
Content Description 0070,0081 LO VNAP AUTO
Presentation Creation Date 0070,0082 DA ALWAYS AUTO
Presentation Creation Time 0070,0083 TM ALWAYS AUTO
Content Creator’s Name 0070,0084 PN VNAP AUTO

Table 109: Presentation State Relationship Module

Presence
Attribute Name Tag VR Value Source Comment
of Value
Referenced Series Sequence 0008,1115 SQ ALWAYS AUTO
>Referenced Image Sequence 0008,1140 SQ ALWAYS AUTO
>>Referenced SOP Class UID 0008,1150 UI ALWAYS AUTO
>>Referenced SOP Instance UID 0008,1155 UI ALWAYS AUTO
>Series Instance UID 0020,000E UI ALWAYS AUTO

Table 110: Presentation State Shutter Module

Presence
Attribute Name Tag VR Value Source Comment
of Value
Shutter Presentation Value 0018,1622 US ALWAYS AUTO

Table 111: Display Shutter Module

Presence of
Attribute Name Tag VR Value Source Comment
Value
Shutter Shape 0018,1600 CS RECTANGULAR ALWAYS AUTO
Shutter Left Vertical Edge 0018,1602 IS ANAP AUTO
Shutter Right Vertical Edge 0018,1604 IS ANAP AUTO
Shutter Upper Horizontal Edge 0018,1606 IS ANAP AUTO
Shutter Lower Horizontal Edge 0018,1608 IS ANAP AUTO
Shutter Presentation Value 0018,1622 US ANAP AUTO

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 76 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved

Table 112: Bitmap Display Shutter Module

Presence of
Attribute Name Tag VR Value Source Comment
Value
Shutter Shape 0018,1600 CS RECTANGULAR ALWAYS AUTO
Shutter Presentation Value 0018,1622 US ANAP AUTO

Table 113: Displayed Area Module

Presence
Attribute Name Tag VR Value Source Comment
of Value
Displayed Area Selection 0070,005A SQ ALWAYS AUTO
Sequence
>Referenced Image Sequence 0008,1140 SQ ANAP AUTO
>>Referenced SOP Class UID 0008,1150 UI ALWAYS AUTO
>>Referenced SOP Instance UID 0008,1155 UI ALWAYS AUTO
>Displayed Area Top Left Hand 0070,0052 SL ALWAYS AUTO calculated by the
Corner system but initiated
by user i.e. without
user zoom and pan
displayed area does
not have any
meaning
>Displayed Area Bottom Right 0070,0053 SL ALWAYS AUTO
Hand Corner
>Presentation Size Mode 0070,0100 CS SCALE TO FIT ALWAYS AUTO
>Presentation Pixel Aspect Ratio 0070,0102 IS ANAP AUTO

Table 114: Graphic Layer Module

Presence
Attribute Name Tag VR Value Source Comment
of Value
Graphic Layer Sequence 0070,0060 SQ ALWAYS AUTO
>Graphic Layer 0070,0002 CS GRAPHICS ALWAYS AUTO
>Graphic Layer Order 0070,0062 IS 1 ALWAYS AUTO

Table 115: Softcopy Presentation LUT Module

Presence
Attribute Name Tag VR Value Source Comment
of Value
Presentation LUT Shape 2050,0020 CS IDENTITY ALWAYS AUTO

Table 116 : Softcopy VOI LUT Module

Presence
Attribute Name Tag VR Value Source Comment
of Value
Softcopy VOI LUT Sequence 0028,3110 SQ ALWAYS AUTO
>Window Center 0028,1050 DS ALWAYS AUTO
>Window Width 0028,1051 DS ALWAYS AUTO

Table 117: SOP Common Module

Presence
Attribute Name Tag VR Value Source Comment
of Value
Specific Character Set 0008,0005 CS ANAP AUTO
Instance Creation Date 0008,0012 DA ANAP AUTO

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 77 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved
Instance Creation Time 0008,0013 TM ANAP AUTO
SOP Class UID 0008,0016 UI 1.2.840.10008.5.1.4.1.1.11.1 ALWAYS AUTO
SOP Instance UID 0008,0018 UI ALWAYS AUTO
Instance Number 0020,0013 IS ANAP AUTO

8.1.1.4 X-Ray Angiographic Image Storage SOP Class

Table 118: SOP Class Modules

Information Entity Module Presence

Patient Patient Module Always
Study General Study Module Always
Patient Study Module Always
Series General Series Module Always
Equipment General Equipment Module Always
Image General Image Module Always
General Reference Module User Defined
Image Pixel Module Always
Contrast/Bolus Module Always
Cine Module Always
Multi-Frame Module Always
Display Shutter Module Always
X-Ray Image Module Always
X-Ray Acquisition Module Always
X-Ray Table Module Always
XA Positioner Module Always
DX Detector Module Always
Modality LUT Module Always
VOI LUT Module Always
Curve Module User Defined
This is present only when ECG signals are present in
the data
SOP Common Module Always

Table 119: Patient Module

Presence of
Attribute Name Tag VR Value Source Comment
Value
Referenced Patient Sequence 0008,1120 SQ ANAP MWL
>Referenced SOP Class UID 0008,1150 UI ALWAYS MWL
>Referenced SOP Instance UID 0008,1155 UI ALWAYS MWL
Patient’s Name 0010,0010 PN VNAP MWL,USER
Patient ID 0010,0020 LO VNAP MWL,USER
Patient’s Birth Date 0010,0030 DA VNAP MWL,USER
Patient’s Sex 0010,0040 CS VNAP MWL,USER
Other Patient IDs 0010,1000 LO ANAP MWL,USER
Ethnic Group 0010,2160 SH ANAP MWL,USER
Patient Comments 0010,4000 LT ANAP MWL,USER

Table 120: General Study Module

Presence of
Attribute Name Tag VR Value Source Comment
Value
 2022 Koninklijke Philips N.V.
SNIP-IOCC-T-020001.09 (Version 2.2) Page 78 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved
Study Date 0008,0020 DA VNAP AUTO
Study Time 0008,0030 TM VNAP AUTO
Accession Number 0008,0050 SH VNAP MWL
Referring Physician’s Name 0008,0090 PN Patient’s referring VNAP MWL
physician.
Study Description 0008,1030 LO VNAP USER,MWL Copied from Requested
procedure step
description
Procedure Code Sequence 0008,1032 SQ ANAP MWL,AUTO
>Code Value 0008,0100 SH ALWAYS MWL,AUTO
>Coding Scheme Designator 0008,0102 SH ALWAYS MWL,AUTO
> Coding Scheme Version 0008,0103 SH ALWAYS MWL,AUTO
>Code Meaning 0008,0104 LO ALWAYS MWL,
AUTO
Referenced Study Sequence 0008,1110 SQ ANAP MWL
>Referenced SOP Class UID 0008,1150 UI ALWAYS MWL
>Referenced SOP Instance UID 0008,1155 UI ALWAYS MWL
Study Instance UID 0020,000D UI ALWAYS MWL
Study ID 0020,0010 SH VNAP MWL In case Study ID is
empty, accession number
is used. If that is also
empty then the system
generates a value for it

Table 121: Patient Study Module

Presence of
Attribute Name Tag VR Value Source Comment
Value
Patient’s Size 0010,1020 DS ALWAYS MWL,USER In meters. When received
from the MWL SCP, the
value can still be
modified.
Patient’s Weight 0010,1030 DS ALWAYS MWL,USER In kilograms. When
received from the MWL
SCP, the value can still
be modified.
Medical Alerts 0010,2000 LO VNAP MWL,USER
Allergies 0010,2110 LO VNAP MWL,USER
Additional Patient History 0010,21B0 LT VNAP MWL

Table 122: General Series Module

Presence of
Attribute Name Tag VR Value Source Comment
Value
Series Date 0008,0021 DA ANAP AUTO
Series Time 0008,0031 TM ANAP AUTO
Modality 0008,0060 CS XA ALWAYS AUTO
Series Description 0008,103E LO ANAP AUTO
Performing Physicians’ Name 0008,1050 PN ANAP MWL, USER
Operators’ Name 0008,1070 PN ANAP MWL, USER
Referenced Performed 0008,1111 SQ Identifies the MPPS SOP ANAP AUTO, MPPS
Procedure Step Sequence Instance to which this
image is related
>Referenced SOP Class UID 0008,1150 UI MPPS SOP Class UID ALWAYS MWL
>Referenced SOP Instance UID 0008,1155 UI MPPS SOP Instance UID ALWAYS MWL

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 79 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved
Presence of
Attribute Name Tag VR Value Source Comment
Value
Protocol Name 0018,1030 LO ANAP AUTO
Series Instance UID 0020,000E UI ALWAYS AUTO
Series Number 0020,0011 IS VNAP AUTO
Laterality 0020,0060 CS EMPTY AUTO
Performed Procedure Step Start 0040,0244 DA ANAP AUTO,
Date
Performed Procedure Step Start 0040,0245 TM ANAP AUTO
Time
Performed Procedure Step ID 0040,0253 SH Same as MPPS ANAP AUTO, USER
Performed Procedure Step 0040,0254 LO Same as MPPS ANAP AUTO, USER
Description
Request Attributes Sequence 0040,0275 SQ ANAP MWL
>Accession Number 0008,0050 SH ANAP MWL
>Issuer of Accession Number 0008,0051 SQ ANAP MWL
Sequence
>Referenced Study Sequence 0008,1110 SQ ANAP MWL
>>Referenced SOP Class UID 0008,1150 UI ALWAYS MWL
>>Referenced SOP Instance UID 0008,1155 UI ALWAYS MWL
>Study Instance UID 0020,000D UI ANAP MWL
>Requested Procedure 0032,1060 LO ANAP MWL
Description
>Requested Procedure Code 0032,1064 SQ ANAP MWL
Sequence
>>Code Value 0008,0100 SH ALWAYS MWL
>>Coding Scheme Designator 0008,0102 SH ALWAYS MWL
>>Code Meaning 0008,0104 LO ALWAYS MWL
>>Context Identifier 0008,010F CS ANAP MWL
>>Context UID 0008,0117 UI ANAP MWL
>Scheduled Procedure Step 0040,0007 LO ANAP MWL
Description
>Scheduled Protocol Code 0040,0008 SQ ANAP MWL
Sequence
>>Code Value 0008,0100 SH ALWAYS MWL
>>Coding Scheme Designator 0008,0102 SH ALWAYS MWL
>>Code Meaning 0008,0104 LO ALWAYS MWL
>>Context Identifier 0008,010F CS ANAP MWL
>>Context UID 0008,0117 UI ANAP MWL
>>Protocol Context Sequence 0040,0440 SQ ANAP MWL
>>>Content Item Modifier 0040,0441 SQ ANAP MWL
Sequence
>>>>Value Type 0040,A040 CS ALWAYS MWL
>>>>Concept Name Code 0040,A043 SQ ALWAYS MWL
Sequence
>>>>>Code Value 0008,0100 SH ALWAYS MWL
>>>>>Coding Scheme 0008,0102 SH ALWAYS MWL
Designator
>>>>>Code Meaning 0008,0104 LO ALWAYS MWL
>>>Value Type 0040,A040 CS ALWAYS MWL
>>>Concept Name Code 0040,A043 SQ ALWAYS MWL
Sequence
>>>>Code Value 0008,0100 SH ALWAYS MWL

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 80 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved
Presence of
Attribute Name Tag VR Value Source Comment
Value
>>>>Coding Scheme Designator 0008,0102 SH ALWAYS MWL
>>>>Code Meaning 0008,0104 LO ALWAYS MWL
>>>>Context Identifier 0008,010F CS ANAP MWL
>>>>Context UID 0008,0117 UI ANAP MWL
>Scheduled Procedure Step ID 0040,0009 SH ANAP MWL
>Reason for Requested 0040,100A SQ ANAP MWL
Procedure Code Sequence
>>Code Value 0008,0100 SH ALWAYS MWL
>>Coding Scheme Designator 0008,0102 SH ALWAYS MWL
>>Code Meaning 0008,0104 LO ALWAYS MWL
>>Context Identifier 0008,010F CS ANAP MWL
>>Context UID 0008,0117 UI ANAP MWL
>Requested Procedure ID 0040,1001 SH ALWAYS MWL

Table 123: General Equipment Module

Presence of
Attribute Name Tag VR Value Source Comment
Value
Manufacturer 0008,0070 LO Philips VNAP AUTO
Institution Name 0008,0080 LO VNAP AUTO
Station Name 0008,1010 SH VNAP AUTO
Institutional Department Name 0008,1040 LO VNAP AUTO
Manufacturer’s Model Name 0008,1090 LO Azurion ANAP AUTO
Device Serial Number 0018,1000 LO VNAP AUTO
Software Versions 0018,1020 LO 3.0.0 VNAP AUTO

Table 124: General Image Module

Presence of
Attribute Name Tag VR Value Source Comment
Value
Image Type 0008,0008 CS Applied value(s): ANAP AUTO
ORIGINAL or
DERIVED (if subtraction
has been processed into
the image)

Value 2: PRIMARY

Value 3:
SINGLE PLANE (if
the image is a single plane
acquisition)

BIPLANE A (if the image

is the first plane of a Bi-
plane acquisition)

BIPLANE B (if the image is

the second plane of a Bi-
plane acquisition)

Value 4:
SINGLE A (if the image
is derived from plane A of a

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 81 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved
biplane image and sent as
a SINGLE PLANE image)

SINGLE B (if the

image is derived from plane
B of a biplane image and
sent as a SINGLE PLANE
image)
Acquisition Date 0008,0022 DA ANAP AUTO
Content Date 0008,0023 DA ANAP AUTO
Acquisition Time 0008,0032 TM ANAP AUTO
Content Time 0008,0033 TM ANAP AUTO
Irradiation Event UID 0008,3010 UI ANAP AUTO
Referenced Image Sequence 0008,1140 SQ ANAP AUTO
>Referenced SOP Class UID 0008,1150 UI ALWAYS AUTO
>Referenced SOP Instance UID 0008,1155 UI ALWAYS AUTO
Derivation Description 0008,2111 ST ANAP AUTO
Instance Number 0020,0013 IS VNAP AUTO
Patient Orientation 0020,0020 CS ANAP AUTO
Lossy Image Compression 0028,2110 CS 00 ANAP AUTO
Presentation LUT Shape 2050,0020 CS IDENTITY ALWAYS AUTO

Table 125: General reference module

Presence of
Attribute Name Tag VR Value Source Comment
Value
Derivation Description 0008,2111 ST VNAP AUTO
Source Image Sequence 0008,2112 SQ ANAP AUTO
> Referenced SOP Class 0008,1150 UI ALWAYS AUTO Documentation
UID of source images for
derived images. This
will be present only for
Derived images.
>Referenced SOP Instance 0008,1155 UI ALWAYS AUTO
UID
>Referenced Frame 0008,1160 IS ALWAYS AUTO
Number

Table 126: Image Pixel Module

Presence of
Attribute Name Tag VR Value Source Comment
Value
Samples per Pixel 0028,0002 US 1 ALWAYS AUTO
Photometric Interpretation 0028,0004 CS MONOCHROME2: Upon ALWAYS AUTO
import, only images with
a photometric
interpretation
MONOCHROME1 or
MONOCHROME2 are
accepted.
Rows 0028,0010 US ALWAYS AUTO
Columns 0028,0011 US ALWAYS AUTO
Bits Allocated 0028,0100 US 8 or 16 ALWAYS AUTO
Note: For Snapshot
function, this number is 8

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 82 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved
Bits Stored 0028,0101 US 8 or 12 ALWAYS AUTO
Note: For Snapshot
function, this number is 8
High Bit 0028,0102 US 7 ALWAYS AUTO
Pixel Representation 0028,0103 US 0000H ALWAYS AUTO
Pixel Data 7FE0,0010 OW/OB ANAP AUTO

Table 127: Contrast/Bolus Module

Presence of
Attribute Name Tag VR Value Source Comment
Value
Contrast/Bolus Agent 0018,0010 LO VNAP AUTO

Table 128: Cine Module

Presence of
Attribute Name Tag VR Value Source Comment
Value
Recommended Display Frame 0008,2144 IS ANAP AUTO
Rate
Cine Rate 0018,0040 IS ANAP AUTO
Frame Time Vector 0018,1065 DS ANAP AUTO
Frame Time 0018,1063 DS ANAP AUTO Either frame time
vector or Frame time
will be present
Frame Delay 0018,1066 DS ANAP AUTO

Table 129: Multi-Frame Module

Presence of
Attribute Name Tag VR Value Source Comment
Value
Number of Frames 0028,0008 IS ALWAYS AUTO
Frame Increment Pointer 0028,0009 AT ALWAYS AUTO

Table 130: Display Shutter Module

Presence of
Attribute Name Tag VR Value Source Comment
Value
Shutter Shape 0018,1600 CS RECTANGULAR ALWAYS AUTO
Shutter Left Vertical Edge 0018,1602 IS ALWAYS AUTO
Shutter Right Vertical Edge 0018,1604 IS ALWAYS AUTO
Shutter Upper Horizontal Edge 0018,1606 IS ALWAYS AUTO
Shutter Lower Horizontal Edge 0018,1608 IS ALWAYS AUTO

Table 131: X-Ray Image Module

Presence of
Attribute Name Tag VR Value Source Comment
Value
Image Type 0008,0008 CS ALWAYS AUTO
Derivation Description 0008,2111 ST ALWAYS AUTO
Scan Options 0018,0022 CS ANAP AUTO ROTA
Referenced Image Sequence 0008,1140 SQ ALWAYS AUTO
>Referenced SOP Class UID 0008,1150 UI ALWAYS AUTO
>Referenced SOP Instance UID 0008,1155 UI ALWAYS AUTO
Samples per Pixel 0028,0002 US 1 ALWAYS AUTO

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 83 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved
Presence of
Attribute Name Tag VR Value Source Comment
Value
Photometric Interpretation 0028,0004 CS MONOCHROME2 Upon ALWAYS AUTO
import, only images with a
photometric interpretation
MONOCHROME1 or
MONOCHROME2 are
accepted.
Frame Increment Pointer 0028,0009 AT ALWAYS AUTO
Bits Allocated 0028,0100 US 8 or 16 ALWAYS AUTO
Note: For Snapshot
function, this number is 8
Bits Stored 0028,0101 US 8 or 12 ALWAYS AUTO
Note: For Snapshot
function, this number is 8
High Bit 0028,0102 US 11 ALWAYS AUTO
Pixel Representation 0028,0103 US 0000H ALWAYS AUTO
Pixel Intensity Relationship 0028,1040 CS ALWAYS AUTO
Lossy Image Compression 0028,2110 CS 00 ALWAYS AUTO

Table 132: X-Ray Acquisition Module

Presence of
Attribute Name Tag VR Value Source Comment
Value
KVP 0018,0060 DS ALWAYS AUTO
Exposure Time 0018,1150 IS Only sent if Exposure ANAP AUTO
(0018, 1152) is not sent.
X-Ray Tube Current 0018,1151 IS Only sent if Exposure ANAP AUTO
(0018, 1152) is not sent.
Average Pulse Width 0018,1154 DS ANAP AUTO
Exposure 0018,1152 IS Only sent if Exposure ANAP AUTO
Time (0018, 1150) and X-
Ray Tube Current (0018,
1151) are not sent.
Radiation Setting 0018,1155 CS ALWAYS AUTO
Imager Pixel Spacing 0018,1164 DS ANAP AUTO
X-Ray Tube Current in µA 0018,8151 DS ANAP AUTO

Table 133: X-Ray Table Module

Presence of
Attribute Name Tag VR Value Source Comment
Value
Table Motion 0018,1134 CS STATIC, DYNAMIC VNAP AUTO
Table Vertical Increment 0018,1135 DS Incremental change (per ANAP AUTO
frame) in vertical position
relatively to the first frame
of Multi-Frame image in
mm
Table Lateral Increment 0018,1136 DS Incremental change (per ANAP AUTO
frame) in lateral position
relatively to the first frame
of Multi-Frame image in
mm
Table Longitudinal Increment 0018,1137 DS Incremental change (per ANAP AUTO
frame) in longitudinal
position relatively to the

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 84 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved
first frame of Multi-Frame
image in mm
Table Angle 0018,1138 DS Angle of table plane in ANAP AUTO
degrees relative to
horizontal plane (gravity
plane). Positive values
indicate that the head of
the table is upwards.

Table 134: XA Positioner Module

Presence of
Attribute Name Tag VR Value Source Comment
Value
Distance Source to Detector 0018,1110 DS ALWAYS AUTO
Distance Source to Patient 0018,1111 DS ALWAYS AUTO
Positioner Motion 0018,1500 CS STATIC, DYNAMIC ALWAYS AUTO
Positioner Primary Angle 0018,1510 DS ALWAYS AUTO
Positioner Secondary Angle 0018,1511 DS ALWAYS AUTO
Positioner Primary Angle 0018,1520 DS An array that contains the ANAP AUTO
Increment Positioner Primary Angle
Increments between the
n-th frame and the
previous frame for a
Multi-frame image.
Positioner Secondary Angle 0018,1521 DS An array that contains the ANAP AUTO
Increment Positioner Secondary
Angle Increments
between the n-th frame
and the previous frame
for a Multi-frame image.

Table 135: DX Detector Module

Presence of
Attribute Name Tag VR Value Source Comment
Value
Imager Pixel Spacing 0018,1164 DS ALWAYS AUTO
Detector Type 0018,7004 CS ANAP AUTO

Table 136: Modality LUT Module

Presence
Attribute Name Tag VR Value Source Comment
of Value
Modality LUT Sequence 0028,3000 SQ ANAP AUTO
>LUT Descriptor 0028,3002 US/SS ANAP AUTO
>Modality LUT Type 0028,3004 LO US ANAP AUTO
>LUT Data 0028,3006 UN ANAP AUTO

Note: Modality LUT and pixel intensity “LOG” only when X-Ray Angiographic images are sent with unprocessed pixel data
-No Modality LUT and pixel intensity “LIN” when X-Ray Angiographic images are sent with processed pixel data.
Table 137: VOI LUT Module

Presence of
Attribute Name Tag VR Value Source Comment
Value
Window Center 0028,1050 DS 2085 ALWAYS AUTO
Window Width 0028,1051 DS 2409 ALWAYS AUTO

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 85 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved

Table 138: Curve Module

Presence of
Attribute Name Tag VR Value Source Comment
Value
Curve Dimensions 5000,0005 US ALWAYS AUTO
Number Of Points 5000,0010 US ALWAYS AUTO
Type Of Data 5000,0020 CS ALWAYS AUTO
Axis Units 5000,0030 SH DPPS\NONE ALWAYS AUTO
Data Value Representation 5000,0103 US ALWAYS AUTO
Minimum Coordinate Value 5000,0104 US ALWAYS AUTO
Maximum Coordinate Value 5000,0105 US ALWAYS AUTO
Curve Data Descriptor 5000,0110 US ALWAYS AUTO
Coordinate Start Value 5000,0112 US ALWAYS AUTO
Coordinate Step Value 5000,0114 US VNAP AUTO
Curve Data 5000,3000 OW ALWAYS AUTO

Table 139: SOP Common Module

Presence
Attribute Name Tag VR Value Source Comment
of Value
Specific Character Set 0008,0005 CS - ANAP AUTO
Instance Creation Date 0008,0012 DA ALWAYS AUTO
Instance Creation Time 0008,0013 TM ALWAYS AUTO
SOP Class UID 0008,0016 UI 1.2.840.10008.5.1.4.1.1.12.1 ALWAYS AUTO
SOP Instance UID 0008,0018 UI Generated by device ALWAYS AUTO
Instance Number 0020,0013 IS ALWAYS AUTO

8.1.1.5 X-Ray Radiation Dose SR

Table 140: SOP Class Modules

Information Entity Module Presence

Patient Patient Module Always

Study General Study Module Always
Patient Study Module Always
Series SR Document Series Module Always
Equipment General Equipment Module Always
Enhanced General Equipment Module Always
Image SR Document General Module Always
SR Document Content Module Always
SOP Common Module Always

Table 141: Patient Module

Presence
Attribute Name Tag VR Value Source Comment
of Value
Referenced Patient Sequence 0008,1120 SQ ANAP MWL
>Referenced SOP Class UID 0008,1150 UI ALWAYS MWL
>Referenced SOP Instance UID 0008,1155 UI ALWAYS MWL
Patient’s Name 0010,0010 PN ALWAYS MWL, USER
Patient ID 0010,0020 LO VNAP MWL, USER
Patient’s Birth Date 0010,0030 DA VNAP MWL, USER
 2022 Koninklijke Philips N.V.
SNIP-IOCC-T-020001.09 (Version 2.2) Page 86 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved
Patient’s Sex 0010,0040 CS VNAP MWL, USER
Other Patient IDs 0010,1000 LO ANAP MWL, USER
Ethnic Group 0010,2160 SH ANAP MWL, USER
Patient Comments 0010,4000 LT ANAP MWL, USER

Table 142: General Study Module

Presence
Attribute Name Tag VR Value Source Comment
of Value
Study Date 0008,0020 DA ALWAYS MWL, AUTO
Study Time 0008,0030 TM ALWAYS MWL, AUTO
Accession Number 0008,0050 SH ALWAYS MWL
Referring Physician’s Name 0008,0090 PN VNAP MWL
Study Description 0008,1030 LO VNAP MWL, USER Copied from
Requested
procedure step
description
Procedure Code Sequence 0008,1032 SQ ANAP MWL, AUTO
Referenced Study Sequence 0008,1110 SQ ANAP MWL
>Referenced SOP Class UID 0008,1150 UI ALWAYS MWL
>Referenced SOP Instance 0008,1155 UI ALWAYS MWL
UID
Study Instance UID 0020,000D UI ALWAYS AUTO
Study ID 0020,0010 SH VNAP MWL, AUTO, In case Study ID is
USER empty, accession
number is used. If that
is also empty then the
system generates a
value for it

Table 143: Patient Study Module

Presence
Attribute Name Tag VR Value Source Comment
of Value
Patient’s Weight 0010,1030 DS ANAP MWL, USER When received from
the MWL SCP, the
value can still be
modified.
Patient’s Size 0010,1020 DS ANAP MWL, USER
Medical Alerts 0010,2000 LO ANAP MWL, USER
Allergies 0010,2110 LO ANAP MWL, USER
Additional Patient History 0010,21B0 LT ANAP MWL

Table 144 : SR Document Series Module

Presence
Attribute Name Tag VR Value Source Comment
of Value
Series Date 0008,0021 DA ANAP AUTO
Series Time 0008,0031 TM ANAP AUTO
Modality 0008,0060 CS SR ALWAYS AUTO
Series Description 0008,103E LO “Radiation Dose Information” ANAP AUTO
Referenced Performed 0008,1111 SQ VNAP AUTO
Procedure Step Sequence
>Referenced SOP Class UID 0008,1150 UI ALWAYS AUTO
>Referenced SOP Instance 0008,1155 UI ALWAYS AUTO
 2022 Koninklijke Philips N.V.
SNIP-IOCC-T-020001.09 (Version 2.2) Page 87 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved
UID
Protocol Name 0018,1030 LO ALWAYS AUTO
Series Instance UID 0020,000E UI ALWAYS AUTO
Series Number 0020,0011 IS ALWAYS AUTO

Table 145: General Equipment Module

Presence
Attribute Name Tag VR Value Source Comment
of Value
Manufacturer 0008,0070 LO Philips VNAP AUTO
Institution Name 0008,0080 LO ANAP CONFIG
Station Name 0008,1010 SH ANAP CONFIG
Institutional Department Name 0008,1040 LO ANAP CONFIG
Manufacturer’s Model Name 0008,1090 LO Azurion ANAP AUTO
Device Serial Number 0018,1000 LO ANAP AUTO
Software Versions 0018,1020 LO R3.0 ANAP AUTO

Table 146: Enhanced General Equipment Module

Presence
Attribute Name Tag VR Value Source Comment
of Value
Manufacturer 0008,0070 LO Philips ALWAYS AUTO
Manufacturer’s Model Name 0008,1090 LO Azurion ALWAYS AUTO
Device Serial Number 0018,1000 LO ALWAYS AUTO
Software Versions 0018,1020 LO R3.0 ALWAYS AUTO

Table 147: SR Document General Module

Presence
Attribute Name Tag VR Value Source Comment
of Value
Content Date 0008,0023 DA ALWAYS AUTO
Content Time 0008,0033 TM ALWAYS AUTO
Instance Number 0020,0013 IS ALWAYS AUTO
Referenced Request Sequence 0040,A370 SQ ANAP AUTO
>Study Instance UID 0020,000D UI ALWAYS MWL
>Requested Procedure 0032,1060 LO VNAP AUTO
Description
>Requested Procedure ID 0040,1001 SH VNAP AUTO
>Reason for the Requested 0040,1002 LO ANAP AUTO
Procedure
>Placer Order Number/Imaging 0040,2016 LO VNAP AUTO
Service Request
>Filler Order Number/Imaging 0040,2017 LO VNAP AUTO
Service Request
Performed Procedure Code 0040,A372 SQ VNAP AUTO
Sequence
Current Requested Procedure 0040,A375 SQ ANAP AUTO
Evidence Sequence
>Referenced Series Sequence 0008,1115 SQ ALWAYS AUTO
>>Referenced SOP Sequence 0008,1199 SQ ALWAYS AUTO
>>>Referenced SOP Class UID 0008,1150 UI ALWAYS AUTO
>>>Referenced SOP Instance 0008,1155 UI ALWAYS AUTO
UID
>>Series Instance UID 0020,000E UI ALWAYS AUTO

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 88 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved
Presence
Attribute Name Tag VR Value Source Comment
of Value
>Study Instance UID 0020,000D UI ALWAYS AUTO
Completion Flag 0040,A491 CS COMPLETE ALWAYS AUTO
Completion Flag Description 0040,A492 LO “Complete X-Ray Radiation ANAP AUTO
Dose Structured Report”
Verification Flag 0040,A493 CS UNVERIFIED ALWAYS AUTO

Table 148 : SR Document Content Module

Presence of
Attribute Name Tag VR Value Source Comment
Value
Value Type 0040,A040 CS CONTAINER ALWAYS AUTO
Concept Name Code Sequence 0040,A043 SQ ANAP AUTO
Content Template Sequence 0040,A504 SQ ANAP AUTO
>Template Identifier 0040,DB0 CS ALWAYS AUTO
0
>Mapping Resource 0008,0105 CS ALWAYS AUTO
Continuity of Content 0040,A050 CS ALWAYS AUTO
Content Sequence 0040,A730 SQ ANAP AUTO
>Measured Value Sequence 0040,A300 SQ VNAP AUTO
>>Measurement Units Code 0040,08E SQ ALWAYS AUTO
Sequence A
>>Numeric Value 0040,A30 DS ALWAYS
A
>Relationship Type 0040,A010 CS ALWAYS AUTO
>Text Value 0040,A160 UT MANDATORY AUTO
CONDITIONAL
>Value Type 0040,A040 CS ALWAYS AUTO
>Concept Name Code 0040,A043 SQ ANAP AUTO
Sequence
>>Code Value 0008,0100 SH ALWAYS AUTO
>>Coding Scheme Designator 0008,0102 SH ALWAYS AUTO
>>Code Meaning 0008,0104 LO ALWAYS AUTO
>Concept Code Sequence 0040,A168 SQ ALWAYS AUTO
>>Code Value 0008,0100 SH ALWAYS AUTO
>>Coding Scheme Designator 0008,0102 SH ALWAYS AUTO
>>Code Meaning 0008,0104 LO ALWAYS AUTO

Table 149: SOP Common Module

Presence
Attribute Name Tag VR Value Source Comment
of Value
Specific Character Set 0008,0005 CS - ANAP AUTO
Instance Creation Date 0008,0012 DA ANAP AUTO
Instance Creation Time 0008,0013 TM ANAP AUTO
SOP Class UID 0008,0016 UI 1.2.840.10008.5.1.4.1.1.88.67 ALWAYS AUTO
SOP Instance UID 0008,0018 UI ALWAYS AUTO
Instance Number 0020,0013 IS ANAP AUTO

8.1.2 Attribute Mapping

Not applicable

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 89 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved

8.1.3 Coerced/Modified Fields

Not applicable

8.2 Data Dictionary of Private Attributes

Not applicable

8.3 Coded Terminology and Templates

Not applicable

8.3.1 Context Group

Not applicable.

8.3.2 Template Specifications

X-RAY RADIATION DOSE STRUCTURED REPORT IOD TEMPLATES
The templates comply SCP the X-Ray Radiation Dose please refer the figure below:

Figure 18: X-Ray Radiation Dose Structured Report IOD Template Structure

This section describes the content of all the templates used in the X-Ray Radiation Dose Reporting SR.
Table 150: Used Templates for X-Ray Radiation Dose Reporting

Template Name Template ID

Projection X-Ray Radiation Dose TID 10001

Accumulated X-Ray Dose TID 10002
Irradiation Event X-Ray Data TID 10003
Irradiation Event X-Ray Source Data (for Fluoroscopy Irradiation Event type) TID 10003B
Irradiation Event X-Ray Source Data (for Stationary Acquisition Event type) TID 10003B
Irradiation Event X-Ray Mechanical Data TID 10003C
Accumulated Acquisition Projection X-Ray Dose (for Fluoroscopy Irradiation Event type) TID 10004
Accumulated Acquisition Projection X-Ray Dose (for Stationary Acquisition Event type) TID 10004
Accumulated Total Projection Radiography Dose TID 10007
 2022 Koninklijke Philips N.V.
SNIP-IOCC-T-020001.09 (Version 2.2) Page 90 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved

Template Name Template ID

Observer Context TID 1002

Device Observer Identifying Attributes TID 1004

8.3.2.1 TID 10001 Projection X-Ray Radiation Dose

Table 151: Projection X-Ray Radiation Dose

Relation with Presence of

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

>> HAS CONCEPT EV (363703001, SCT, “Has Intent”) CODE 1 ALWAYS R-002E9, SRT, “Combined
MOD Diagnostic and Therapeutic
Procedure”
> CONTAINS EV (122142, DCM, « Acquisition Device CODE 1 ALWAYS 113958, DCM, “Integrated
Type ») Projection Radiography
System”
> DTID 1002 “Observer Context” INCLUDE 1-n ALWAYS

> HAS OBS EV (113705, DCM, “Scope of CODE 1 ALWAYS (113016, DCM, “Performed
CONTEXT Accumulation”) Procedure Step”)

>> HAS 121126, DCM, “Performed Procedure UIDREF 1 ALWAYS

PROPERTIES Step SOP Instance UID”

> CONTAINS 113945, DCM, "X-Ray Detector Data CODE 1 USER OPTIONAL
Available"

> CONTAINS DTID 10002 “Accumulated X-Ray Dose” INCLUDE 1 ALWAYS (113622, DCM, “Single
Plane”) OR (113620, DCM,
"Plane A") OR (113621,
DCM, "Plane B")
> CONTAINS DTID 10003 “Irradiation Event X-Ray INCLUDE 1-n ALWAYS
Data”

> CONTAINS EV (121106, DCM, “Comment”) TEXT 1 ALWAYS X-Ray Radiation Dose
Structured Report related to
the Performed . . .
> CONTAINS EV (113854, DCM, “Source of Dose CODE 1-n ALWAYS (113856, DCM, Automated
Information”) Data Collection)

8.3.2.2 TID 10002 Accumulated X-Ray Dose

Table 152: Accumulated X-Ray Dose

Relation with Presence of

NL Concept Name VT VM Value
Parent Value
EV (113702, DCM, “Accumulated X- CONTAINER 1 ALWAYS
Ray Dose Data”)
> HAS CONCEPT EV (113764, DCM, “Acquisition Plane”) CODE 1 ALWAYS (113622, DCM, “Single
MOD Plane”)

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 91 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved
> CONTAINS EV (122505, DCM, “Calibration”) CONTAINER 1 USER OPTIONAL

>> HAS CONCEPT EV (113794, DCM, “Dose CODE 1 USER OPTIONAL (A-2C090, SRT,
MOD Measurement Device”) “Dosimeter”)
>> CONTAINS EV (113723, DCM, “Calibration DATETIME 1 USER OPTIONAL
DateTime”)
>> CONTAINS EV (122322, DCM, “Calibration NUM 1 USER OPTIONAL Units1, UCUM, “no units”)
Factor”)
>> CONTAINS EV (113763, DCM, “Calibration NUM 1 USER OPTIONAL Units: (%, UCUM,
Uncertainty”) “Percent”)
>> CONTAINS EV (113724, DCM, “Calibration TEXT 1 USER OPTIONAL
Responsible Party”)
>> CONTAINS EV (113720, DCM, “Calibration TEXT 1 USER OPTIONAL
Protocol”)
> CONTAINS (001, 99PHI-IXR-XPER, “Height of NUM 1 ALWAYS Units: (mm, UCUM, “mm”)
System”)
> CONTAINS (002, 99PHI-IXR-XPER, “Focal Spot to NUM 1 ALWAYS Units: (mm, UCUM, “mm”)
ISO Center”)
> CONTAINS DTID (10004) “Accumulated Projection INCLUDE 1 ALWAYS
X-Ray Dose”
> CONTAINS DTID (10007) “Accumulated Total INCLUDE 1 CONDITIONAL IFF TID (10001) Row 2 =
Projection Radiography Dose” (113704, DCM, “Projection
X-Ray”) and TID (10001)
Row 4 is absent)

8.3.2.3 TID 10003 Irradiation Event X-Ray Data

Table 153: Irradiation Event X-Ray Data

Relation with Presence of

NL Concept Name VT VM Value
Parent Value
CONTAINS EV (113706, DCM, “Irradiation Event 1 ALWAYS
X-Ray Data”) CONTAINER

> HAS CONCEPT EV (113764, DCM, “Acquisition Plane”) CODE 1 ALWAYS (113622, DCM, “Single
MOD Plane”)
> CONTAINS EV (113769, DCM, “Irradiation Event 1 ALWAYS -
UID”) UIDREF

> CONTAINS DT (111526, DCM, “DateTime DATETIME 1 ALWAYS

Started”)
> CONTAINS EV (113721, DCM, “Irradiation Event CODE 1 ALWAYS (113611, DCM, “Stationary
Type”) Acquisition”)
(P5-06000, SRT,
“Fluoroscopy”)
> CONTAINS EV (125203, DCM, “Acquisition TEXT 1 ALWAYS -
Protocol”)
> CONTAINS EV (113745, DCM, “Patient Table CODE 1 ALWAYS -
Relationship”)
> CONTAINS EV (113743, DCM, “Patient CODE 1 ALWAYS -
Orientation”)
>> HAS CONCEPT EV (113744, DCM, « Patient CODE 1 ALWAYS -
MOD Orientation Modifier »)
> CONTAINS EV (123014, DCM, “Target Region”) CODE 1 ALWAYS -

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 92 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved
>> HAS CONCEPT EV (272741003, SCT, "Laterality") CODE 1 USER
MOD CONDITIONAL
> CONTAINS EV (122130, DCM, “Dose Area NUM 1 ALWAYS Units: (Gy.m2, UCUM,
Product”) “Gy.m2”)
> CONTAINS EV (111638, DCM, “Patient Equivalent NUM 1 USER OPTIONAL
Thickness”)
> CONTAINS EV (121106, DCM, “Comment”) TEXT 1 USER OPTIONAL

> CONTAINS DTID 10003A “Irradiation Event X-Ray INCLUDE 1 CONDITIONAL IFF TID (10001) Row 8 is
Detector Data” absent or has a value of (R-
0038D, SRT, “Yes”)
> CONTAINS DTID 10003B “Irradiation Event X-Ray INCLUDE 1 CONDITIONAL IFF TID (10001) Row 9 is
Source Data” absent or has a value of (R-
0038D, SRT, “Yes”)
> CONTAINS DTID 10003C “Irradiation Event X-Ray INCLUDE 1 CONDITIONAL IFF TID (10001) Row 10 is
Mechanical Data” absent or has a value of (R-
0038D, SRT, “Yes”)
> CONTAINS (003, 99PHI-IXR-XPER, “Number of NUM 1 ALWAYS Units: (1, UCUM, “no units”)
Frames”)
> CONTAINS (004, 99PHI-IXR-XPER, “Sub Images NUM 1 ALWAYS Units: (1, UCUM, “no units”)
per Frame”)
>> CONTAINS (005, 99PHI-IXR-XPER, “Wedges and CONTAINER
Shutters”)
>>> CONTAINS (006, 99PHI-IXR-XPER, “Bottom NUM 1 ALWAYS Units: (mm, UCUM, “mm”)
Shutter”)
>>> CONTAINS (007, 99PHI-IXR-XPER, “Left Shutter”) NUM 1 ALWAYS Units: (mm, UCUM, “mm”)

>>> CONTAINS (008, 99PHI-IXR-XPER, “Right NUM 1 ALWAYS Units: (mm, UCUM, “mm”)
Shutter”)
>>> CONTAINS (009, 99PHI-IXR-XPER, “Top Shutter”) NUM 1 ALWAYS Units: (mm, UCUM, “mm”)

>>> CONTAINS (010, 99PHI-IXR-XPER, “Distance NUM 1 ALWAYS Units: (mm, UCUM, “mm”)
Wedge 1”)
>>> CONTAINS (011, 99PHI-IXR-XPER, “Distance NUM 1 ALWAYS Units: (mm, UCUM, “mm”)
Wedge 2”)
>>> CONTAINS (012, 99PHI-IXR-XPER, “Angle Wedge NUM 1 ALWAYS Units: (deg, UCUM, “deg”)
1”)
>>> CONTAINS (013, 99PHI-IXR-XPER, “Angle Wedge NUM 1 ALWAYS Units: (deg, UCUM, “deg”)
2”)
>> CONTAINS (014, 99PHI-IXR-XPER, “Beam CONTAINER
Position”)
>>> CONTAINS (015, 99PHI-IXR-XPER, “Longitudinal NUM 1 ALWAYS Units: (mm, UCUM, “mm”)
Beam Position”)
>>> CONTAINS (016, 99PHI-IXR-XPER, “Lateral Beam NUM 1 ALWAYS Units: (mm, UCUM, “mm”)
Position”)
>>> CONTAINS (017, 99PHI-IXR-XPER, “Beam Angle”) NUM 1 ALWAYS Units: (deg, UCUM, “deg”)

> CONTAINS (018, 99PHI-IXR-XPER, “Final NUM 1 ALWAYS Units: (mm, UCUM, “mm”)
Distance Source to Detector)
> CONTAINS (019, 99PHI-IXR-XPER, “Final Table NUM 1 ALWAYS Units: (deg, UCUM, “deg”)
Cradle Angle”)
> CONTAINS (021, 99PHI-IXR-XPER, “Table Height NUM 1 ALWAYS Units: (mm, UCUM, “mm”)
Position”)
> CONTAINS (022, 99PHI-IXR-XPER, “Final Table NUM 1 ALWAYS Units: (deg, UCUM, “deg”)
Tilt Angle”)
>> CONTAINS (023, 99PHI-IXR-XPER, “Detector CONTAINER
Field Size”)

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 93 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved
>>> CONTAINS (024, 99PHI-IXR-XPER, “X Side”) NUM 1 ALWAYS Units: (mm, UCUM, “mm”)

>>> CONTAINS (025, 99PHI-IXR-XPER, “Y Side”) NUM 1 ALWAYS Units: (mm, UCUM, “mm”)

> CONTAINS (026, 99PHI-IXR-XPER, “Object NUM 1 ALWAYS Units: (mm, UCUM, “mm”)
Thickness”)
> CONTAINS (121114, DCM, “Performing TEXT 1 ALWAYS
Physician”)
> CONTAINS (029, 99PHI-IXR-XPER, “Application TEXT 1 ALWAYS Left Coronary 15 fps
Name”) Medium
> CONTAINS (030, 99PHI-IXR-XPER, “Fluoro TEXT 1 ALWAYS Medium
Flavour”)

8.3.2.4 TID 10003B Irradiation Event X-Ray Source Data (for Fluoroscopy Irradiation Event
type)
Table 154: Irradiation Event X-Ray Source Data

Relation with Presence of

NL Concept Name VT VM Value
Parent Value
> CONTAINS EV (113738, DCM, “Dose (RP)”) NUM 1 ALWAYS Units: (Gy, UCUM, “Gy”)
> CONTAINS EV(113780, DCM, ”Reference Point TEXT 1 ALWAYS 15cm below BeamIsocenter
Definition”)
> CONTAINS EV (113732, DCM, “Fluoro Mode”) CODE 1 USER (113631, DCM, “Pulsed”)
CONDITIONAL
> CONTAINS EV (113768, DCM, “Number of Pulses”) NUM 1 ALWAYS Units: (1, UCUM, “no units”)
> CONTAINS EV (113793, DCM, “Pulse Width”) NUM 1 ALWAYS Units: (ms, UCUM, “ms”)
> CONTAINS EV (113742, DCM, “Irradiation Duration”) NUM 1 ALWAYS Units: (s, UCUM, “s”)
> CONTAINS EV (113733, DCM, “KVP”) NUM 1 ALWAYS Units: (kV, UCUM, kV)

> CONTAINS EV (113734, DCM, “X-Ray Tube NUM 1 ALWAYS Units: (mA, UCUM, mA)
Current”)
> CONTAINS EV (113767, DCM, “Average X-Ray Tube NUM 1 ALWAYS Units: (mA, UCUM, mA)
Current”)
> CONTAINS EV (113736, DCM, “Exposure”) NUM 1 MANDATORY Units: (uA.s, UCUM, uA.s)
CONDITIONAL
> CONTAINS EV (113766, DCM, “Focal Spot Size”) NUM 1 OPTIONAL Units: (mm, UCUM, mm)
CONTAINS (113771, DCM, "X-Ray Filters) CONTAINER 1-n OPTIONAL
> CONTAINS EV (113772, DCM, “X-Ray Filter Type”) CODE 1 ALWAYS -
> CONTAINS EV (113757, DCM, “X-Ray Filter CODE 1 ALWAYS (C-120F9, SRT, “Aluminum
Material”) or Aluminum compound”)
> CONTAINS EV (113758, DCM, “X-Ray Filter NUM 1 ALWAYS Units: (mm, UCUM, mm)
Thickness Minimum”))
> CONTAINS EV (113773, DCM, “X-Ray Filter NUM 1 ALWAYS Units: (mm, UCUM, mm)
Thickness Maximum”)
> CONTAINS EV (113790, DCM, “Collimated Field NUM 1 ALWAYS Units: (m2, UCUM, m2)
Area”)
> CONTAINS EV (113788, DCM, “Collimated Field NUM 1 OPTIONAL Units: (mm, UCUM, mm)
Height”)
> CONTAINS EV (113789, DCM, “Collimated Field NUM 1 OPTIONAL Units: (mm, UCUM, mm)
Width”)

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 94 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved

8.3.2.5 TID 10003B Irradiation Event X-Ray Source Data (for Stationary Acquisition
Irradiation Event type)
Table 155: Irradiation Event X-Ray Source Data

Relation with Presence of

NL Concept Name VT VM Value
Parent Value
> CONTAINS EV (113738, DCM, “Dose (RP)”) NUM 1 ALWAYS Units: (Gy, UCUM, “Gy”)
> CONTAINS EV(113780, DCM, ”Reference Point TEXT 1 ALWAYS 15cm below BeamIsocenter
Definition”)
> CONTAINS EV (113768, DCM, “Number of Pulses”) NUM 1 ALWAYS Units: (1, UCUM, “no units”)
> CONTAINS EV (113793, DCM, “Pulse Width”) NUM 1 ALWAYS Units: (ms, UCUM, “ms”)
> CONTAINS EV (113742, DCM, “Irradiation Duration”) NUM 1 ALWAYS Units: (s, UCUM, “s”)
> CONTAINS EV (113733, DCM, “KVP”) NUM 1 ALWAYS Units: (kV, UCUM, kV)

> CONTAINS EV (113734, DCM, “X-Ray Tube NUM 1 ALWAYS Units: (mA, UCUM, mA)
Current”)
> CONTAINS EV (113767, DCM, “Average X-Ray Tube NUM 1 ALWAYS Units: (mA, UCUM, mA)
Current”)
> CONTAINS EV (113736, DCM, “Exposure”) NUM 1 MANDATORY Units: (uA.s, UCUM, uA.s)
CONDITIONAL
> CONTAINS EV (113766, DCM, “Focal Spot Size”) NUM 1 OPTIONAL Units: (mm, UCUM, mm)
> CONTAINS EV (113772, DCM, “X-Ray Filter Type”) CODE 1 ALWAYS -
> CONTAINS EV (113757, DCM, “X-Ray Filter CODE 1 ALWAYS (C-120F9, SRT, “Aluminum
Material”) or Aluminum compound”)
> CONTAINS EV (113758, DCM, “X-Ray Filter NUM 1 ALWAYS Units: (mm, UCUM, mm)
Thickness Minimum”))
> CONTAINS EV (113773, DCM, “X-Ray Filter NUM 1 ALWAYS Units: (mm, UCUM, mm)
Thickness Maximum”)
> CONTAINS EV (113790, DCM, “Collimated Field NUM 1 ALWAYS Units: (m2, UCUM, m2)
Area”)
> CONTAINS EV (113788, DCM, “Collimated Field NUM 1 OPTIONAL Units: (mm, UCUM, mm)
Height”)
> CONTAINS EV (113789, DCM, “Collimated Field NUM 1 OPTIONAL Units: (mm, UCUM, mm)
Width”)

8.3.2.6 TID 10003C Irradiation Event X-Ray Mechanical Data

Table 156: Irradiation Event X-Ray Mechanical Data

Relation with Presence of

NL Concept Name VT VM Value
Parent Value
EV (112011, DCM, “Positioner Primary NUM 1 USER OPTION Units: (deg, UCUM, deg)
Angle”) CONDITIONAL
EV (112012, DCM, “Positioner NUM 1 USER OPTION Units: (deg, UCUM, deg)
Secondary Angle”) CONDITIONAL
EV (113754, DCM, “Table Head Tilt NUM 1 USER OPTION Units: (deg, UCUM, deg)
Angle”)
EV (113755, DCM, “Table Horizontal NUM 1 USER OPTION Units: (deg, UCUM, deg)
Rotation Angle”)
EV (113756, DCM, “Table Cradle Tilt NUM 1 USER OPTION Units: (deg, UCUM, deg)
Angle”)
(113748, DCM, “Distance Source to NUM 1 USER OPTION Units: (mm, UCUM, “mm”)
Isocenter”)
(113737, DCM, “Distance Source to NUM 1 USER OPTION Units: (mm, UCUM, “mm”)
Reference Point

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 95 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved
(113750, DCM, “Distance Source to NUM 1 USER OPTION Units: (mm, UCUM, “mm”)
Detector”)
(113751, DCM, “Table Longitudinal NUM 1 USER OPTION Units: (mm, UCUM, “mm”)
Position”)
(113752, DCM, “Table Lateral Position”) NUM 1 USER OPTION Units: (mm, UCUM, “mm”)
(113753, DCM, “Table Height Position”) NUM 1 USER OPTION Units: (mm, UCUM, “mm”)

8.3.2.7 TID 10004 Accumulated Projection X-Ray Dose (for Fluoroscopy Irradiation Event
type)
Table 157: Accumulated Projection X-Ray Dose

Relation with Presence of Value

NL Concept Name VT VM Value
Parent
>> CONTAINS EV (113726, DCM, “Fluoro Dose Area 1 ALWAYS Units: (Gy.m2, UCUM,
Product Total”) NUM “Gy.m2”)
>> CONTAINS EV (113728, DCM, “Fluoro Dose (RP) 1 ALWAYS Units: (Gy, UCUM, “Gy”)
NUM
Total”)
>> CONTAINS EV (113730, DCM, “Total Fluoro Time”) NUM 1 ALWAYS Units: (s, UCUM, “s”)

8.3.2.8 TID 10004 Accumulated Projection X-Ray Dose (for Stationary Acquisition
Irradiation Event type)
Table 158: Accumulated Projection X-Ray Dose

NL Relation with Parent Concept Name VT VM Presence of Value Value

>> CONTAINS EV (113727, DCM, “Acquisition NUM 1 ALWAYS Units: (Gy.m2, UCUM,
Dose Area Product Total) “Gy.m2”)

>> CONTAINS EV (113729, DCM, NUM 1 CONDITIONAL Units: (Gy, UCUM, “Gy”)
« Acquisition Dose (RP)
Total »)
>> CONTAINS EV (113855, DCM, “Total NUM 1 ALWAYS Units: (s, UCUM, “s”)
Acquisition Time”)

8.3.2.9 TID 10007 Accumulated Total Projection Radiography Dose

Table 159: Accumulated Total Projection Radiography Dose

Presence of
NL Relation with Parent Concept Name VT VM Value
Value
> CONTAINS EV (113722, DCM, “Dose Area NUM 1 ALWAYS Units: (Gy.m2, UCUM,
Product Total”) Gy.m2)
> CONTAINS EV (113725, DCM, “Dose (RP) NUM 1 ALWAYS Units: (Gy, UCUM, Gy)
Total”)
> CONTAINS EV (113737, DCM, “Distance NUM 1 USER OPTION Units: (mm, UCUM, “mm”)
Source to Reference Point)
> CONTAINS EV (113731, DCM, “Total NUM 1 USER OPTION Units: (1, UCUM, no units)
Number of Radiographic
Frame
> CONTAINS EV (113780, DCM, “Reference TEXT 1 ALWAYS 15cm below BeamIsocenter
Point Definition”)

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 96 of 97
 DICOM Conformance Statement Azurion R3.0
Doc Id: HSDP-1011216
Doc status: Approved

8.3.2.10 TID 1002 Observer Context

Table 160: Observer Context

Presence of
NL Relation with Parent Concept Name VT VM Value
Value
> HAS OBS CONTEXT EV (121005, DCM, “Observer CODE 1 ALWAYS (121007, DCM, “Device”)
Type”)
HAS OBS CONTEXT DTID 1003 "Person Observer CODE 1 MANDATORY
Identifying Attributes CONDITIONAL
HAS OBS CONTEXT DTID 1004 “Device Observer INCLUDE 1 ALWAYS
Identifying Attributes”
HAS OBS CONTEXT DTID 1015 "Person Observer INCLUDE 1 OPTIONAL
Description

8.3.2.11 TID 1004 Device Observer Identifying Attributes

Table 161: Device Observer Identifying Attributes

Presence of
NL Relation with Parent Concept Name VT VM Value
Value
> HAS OBS CONTEXT EV (121012, DCM, “Device UIDREF 1 ALWAYS
Observer UID”)
> HAS OBS CONTEXT EV (121013, DCM, “Device TEXT 1 CONDITIONAL
Observer Name”)
> HAS OBS CONTEXT EV (121014, DCM, “Device TEXT 1 ALWAYS Philips
Observer Manufacturer”)
> HAS OBS CONTEXT EV (121015, DCM, “Device TEXT 1 ALWAYS Azurion
Observer Model Name”)
> HAS OBS CONTEXT EV (121016, DCM, “Device TEXT 1 ALWAYS
Observer Serial Number”)

8.3.3 Private Code Definitions

Not applicable.

8.4 Grayscale Image Consistency

The monitors and printers attached to the product can be calibrated by using the Service Application.

8.5 Standard/Extended/Specialized/Private SOP Classes

Not applicable.

 2022 Koninklijke Philips N.V.

SNIP-IOCC-T-020001.09 (Version 2.2) Page 97 of 97