DICOM

Conformance Statement

Allura Xper FD20 Release 1.0

Issued by:
Philips Medical Systems Nederland B.V.
Digital Imaging Systems-CardioVascular

Building HOF-127
P.O. Box 10.000
5680 DA Best
The Netherlands

email: [email protected]
Internet: http://www.medical.philips.com/

Document Number: XDB040-041131

 DICOM Conformance Statement Page 1 of 71

1. DICOM C ONFORMANCE S TATEMENT O VERVIEW

Allura Xper FD20 is an image acquisition modality. It provides the following DICOM
data exchange features: (see Figure 1):
• Query the Department System Scheduler for a Modality Worklist (MWL)
• Update the Performed Procedure Step Manager with information about
Performed Procedure Steps (MPPS)
• Transfer of DICOM Images to the Image Archive or Image Displays
• Transfer of requests for storage commitment to the Image Archive (for the
safekeeping of the previously transmitted images) and handling the storage
commitment notifications received from the Image Archive
• Query/Retrieve the Image Archive or Image Displays for a list of entries
representing Series of DICOM Images
• Store DICOM Images sent from the Image Archive or Image Displays
• Print Images on DICOM Printers

Department System MWL

Scheduler

Performed Procedure MPPS

Step Manager

Allura Xper FD
Allura Xper RIS AE

Storage (Commit)
Image Archive Query/Retrieval
/Image Display Allura Xper ACP AE

Import

Image Print
Print Server

Figure 1 Data Flow of Allura Xper FD20 in a DICOM network

Table 1 presents an overview of all supported by Allura Xper FD20 networking DICOM
Service (SOP) Classes with roles (User/Provider), organized in four categories:
• Transfer
• Query/Retrieve
• Workflow Management
• Print Management
Table 1: Network Services

SOP Class User of Provider

Service of Service
Name UID (SCU) (SCP)

Transfer
Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7 Yes Yes
X-Ray Angiographic Image Storage 1.2.840.10008.5.1.4.1.1.12.1 Yes Yes

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 2 of 71

SOP Class User of Provider

Service of Service
Name UID (SCU) (SCP)

Query/Retrieve
Patient Root Query/Retrieve Information 1.2.840.10008.5.1.4.1.2.1.1 Yes No
Model – FIND
Patient Root Query/Retrieve Information 1.2.840.10008.5.1.4.1.2.1.2 Yes No
Model – MOVE
Study Root Query/Retrieve Information 1.2.840.10008.5.1.4.1.2.2.1 Yes No
Model – FIND
Study Root Query/Retrieve Information 1.2.840.10008.5.1.4.1.2.2.2 Yes No
Model – MOVE
Workflow Management
Storage Commitment Push Model 1.2.840.10008.1.20.1 Yes No
Modality Performed Procedure Step 1.2.840.10008.3.1.2.3.3 Yes No
Modality Worklist Information Model – FIND 1.2.840.10008.5.1.4.31 Yes No
Print Management
Basic Grayscale Print Management (Meta) 1.2.840.10008.5.1.1.9 Yes No
>Basic Film Session 1.2.840.10008.5.1.1.1 Yes No
>Basic Film Box 1.2.840.10008.5.1.1.2 Yes No
>Basic Grayscale Image Box 1.2.840.10008.5.1.1.4 Yes No
> Printer SOP Class 1.2.840.10008.5.1.1.16 Yes No

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 3 of 71

2. TABLE OF C ONTENTS
1. DICOM CONFORMANCE STATEMENT OVERVIEW ............................................................... 1
2. TABLE OF CONTENTS .............................................................................................................. 3
3. INTRODUCTION ......................................................................................................................... 5
3.1. Revision History....................................................................................................................... 5
3.2. Audience.................................................................................................................................. 5
3.3. Remarks .................................................................................................................................. 5
3.4. Definitions, Terms and Abbreviations ..................................................................................... 6
3.5. References .............................................................................................................................. 8
4. NETWORKING ............................................................................................................................ 9
4.1. Implementation model ............................................................................................................. 9
4.1.1. Application Data Flow ......................................................................................................... 9
4.1.2. Functional Definition of AE’s ............................................................................................. 11
4.1.2.1. Functional Definition of RIS AE......................................................................................... 12
4.1.2.2. Functional Definition of ACP AE ....................................................................................... 12
4.1.3. Sequencing of Real World Activities ................................................................................. 13
4.2. AE Specifications................................................................................................................... 15
4.2.1. RIS AE............................................................................................................................... 15
4.2.1.1. SOP Classes..................................................................................................................... 15
4.2.1.2. Association Policies .......................................................................................................... 16
4.2.1.3. Association Initiation Policy............................................................................................... 17
4.2.1.4. Association Acceptance Policy ......................................................................................... 29
4.2.2. ACP AE ............................................................................................................................. 29
4.2.2.1. SOP Classes..................................................................................................................... 29
4.2.2.2. Association Policies .......................................................................................................... 29
4.2.2.3. Association Initiation Policy............................................................................................... 30
4.2.2.4. Association Acceptance Policy ......................................................................................... 51
4.3. Network Interfaces................................................................................................................. 54
4.3.1. Physical Network Interface ............................................................................................... 54
4.3.2. Additional Protocols .......................................................................................................... 54
4.4. Configuration ......................................................................................................................... 54
4.4.1. AE Title/Presentation Address Mapping ........................................................................... 55
4.4.1.1. Local AE Titles .................................................................................................................. 55
4.4.1.2. Remote AE Title/Presentation Address Mapping ............................................................. 55
4.4.2. Parameters........................................................................................................................ 55
5. MEDIA INTERCHANGE............................................................................................................ 58
6. SUPPORT OF CHARACTER SETS ......................................................................................... 59
7. SECURITY................................................................................................................................. 60
7.1. Association Level Security .................................................................................................... 60
7.2. Application Level Security ..................................................................................................... 60
7.2.1. DICOM Basic TLS Secure Transport Connection Profile ................................................. 60
7.2.2. Generation of Audit Records............................................................................................. 62
8. ANNEXES.................................................................................................................................. 63
8.1. IOD Contents......................................................................................................................... 63
8.1.1. Secondary Capture Image Storage SOP Class - C-STORE-RQ ..................................... 63
8.1.2. X-Ray Angiographic Image Storage SOP Class – C-STORE RQ.................................... 65
8.1.3. Usage of Attributes from Received IOD’s ......................................................................... 70
8.1.4. Attribute Mapping .............................................................................................................. 70
8.1.5. Coerced/Modified fields..................................................................................................... 71
8.2. Data Dictionary of Private Attributes ..................................................................................... 71
8.3. Coded Terminology and Templates ...................................................................................... 71
8.4. Grayscale Image consistency ............................................................................................... 71
8.5. Standard Extended/Specialized/Private SOPs ..................................................................... 71
8.6. Private Transfer Syntaxes ..................................................................................................... 71

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
DICOM Conformance Statement Page 4 of 71

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 5 of 71

3. I NTRODUCTION

3.1. Revision History

The revision history provides dates and differences of the different releases.

Table 2: Revision History

Document
Date of Issue Author Description
Version
00 20 February 2004 PMS DIS-C/V New version of conformance according to the new
template (Ref. DICOM 2003 supplement 64 Version 18)
01 20 April 2004 PMS DIS-C/V Document prepared for a review
02 29 April 2004 PMS DIS-C/V Document updated after the review XDB040-041333,
PMSim73197, PMSim73200, PMSim73373
03 29 April 2004 PMS DIS-C/V PMSim62311
04 16 June 2004 PMS DIS-C/V PMSim79003
05 6 August 2004 PMS DIS-C/V PMSim82933

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-2004.
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 assure that the actual

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 6 of 71

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).

3.4. Definitions, Terms and Abbreviations

DICOM definitions, terms and abbreviations are used throughout this Conformance
Statement. For a description of these, see NEMA PS 3.3-2004 and PS 3.4-2004.
The word Philips in this document refers to Philips Medical Systems.
The following acronyms are used in this document.
ACC American College of Cardiology
ACN Application Context Name
ACP Archiving/Connectivity and Print
ACR American College of Radiology
AE Application Entity
ANSI American National Standard Institute
AP Application Profile
BWLM Basic Worklist Management
CRL Certificate Revocation List
DICOM Digital Imaging and Communications in Medicine
DIMSE DICOM Message Service Element
DIMSE-C DIMSE-Composite
DIMSE-N DIMSE-Normalized
CN Common Name
EBE DICOM Explicit VR Big Endian
ELE DICOM Explicit VR Little Endian
GUI Graphic User Interface
HIS Hospital Information System
JPEG Joint Photographic Experts Group
ILE DICOM Implicit VR Little Endian

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 7 of 71

IOD Information Object Definition

LDAP Lightweight Directory Access Protocol
MWL Modality Worklist Management
MPPS Modality Performed Procedure Step
NEMA National Electrical Manufacturers Association
NTP Network Time Protocol
N.A. Not Applicable
PDU Protocol Data Unit
PHI Protected Health Information
RIS Radiology Information System
RWA Real-World Activity
SC Secondary Capture
SCP Service Class Provider
SCU Service Class User
SOP Service Object Pair
TCP/IP Transmission Control Protocol/Internet Protocol
TLS Transport Layer Security
UID Unique Identifier
XA X-Ray Angiographic
xxx Any status code
* Any

The following terms are used in this document.

Audit Record Repository
A system unit that receives and collects audit records from multiple systems [IHE].
Image Archive
A system that provides long term storage of images, presentation states, Key Image
Notes and Evidence Documents [IHE].
Image Display
A system that offers browsing of patients’ studies. In addition, it may support the
retrieval and display of selected sets of images, presentation states, Key Image
Notes, and Evidence Documents [IHE].
Department System Scheduler
A department-based information system that provides functions related to the
management of orders received from external systems or through the department
system’s user interface. Upon a defined workflow action, makes procedures available
for charge posting. The actor defines the action/event that actually causes charges to
post [IHE].
Performed Procedure Step Manager
A system that re-distribute the Modality Performed Procedure Step Information from
the Acquisition Modality or image Creator to the Department System Scheduler/Order
Filler and Image Manager [IHE].
Print Server
A system that accepts and processes DICOM print requests as a DICOM Print SCP
and performs image rendering on hardcopy media. The system must support pixel
rendering according to the DICOM Grayscale Standard Display Function [IHE].

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 8 of 71

Protected Health Information

Protected Health Information is considered as information records, and not the flow of
information between the systems [IHE].
Time Server
A system unit that knows, maintains and distributes the correct time in the enterprise
[IHE].

3.5. References
[DICOM] Digital Imaging and Communications in Medicine (DICOM), Part 1 – 16
(NEMA PS 3.1-2004 – PS 3.16-2003),
National Electrical Manufacturers Association (NEMA)
Publication Sales 1300 N. 17th Street, Suite 1847
Rosslyn, Virginia. 22209, United States of America

[IHE] Integrating the Healthcare Enterprise

(IHE) Technical Framework Revision 5.4:
Radiological Society of North America (RSNA), Inc.
820 Jorie Boulevard, Oak Brook, IL, United States of America
[NTP] RFC 1305: Network Time Protocol Version 3.
[SYSLOG] RFC 3164:The BSD Syslog Protocol.
[TLS] RFC 2246:Transport Layer Security protocol (TLS) v1.0.

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 9 of 71

4. N ETWORKING
This section contains the networking related services.

4.1. Implementation model

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

4.1.1. Application Data Flow

Allura Xper FD20 has two Application Entities in its implementation, namely RIS
Application Entity (RIS AE) and ACP AE Application Entity (ACP AE). Figure 2 shows
the Networking application data flow as a functional overview of these application
entities. On the left-hand side, the local Real-World Activities are presented, whereas
on the right-hand side, the remote Real-World Activities are presented.
As depicted in Figure 2, the RIS AE and ACP AE incorporate the following
functionality:
• After RWA Request Modality Worklist, the RIS AE 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 RIS AE
as SCU uses the remote Modality Performed Procedure Step SOP Class
functionality to Report Modality Performed Procedure Step.
• After RWA Verify Application Level Communication (in the service mode), the
RIS AE as SCU uses the remote Request Verification SCP functionality to
verify communication.
• After RWA Transfer Images, the ACP AE as SCU uses the remote SCP
Storage Service Class functionality to store local images in a remote
database.
• After RWA Import Images, the ACP AE as SCP provides standard Storage
Service Class functionality to the requesting SCU.
• After RWA Find Remote Images, the ACP AE as SCU uses the remote SCP
Query/Retrieve Service Class functionality to query for remote Series of
Images.
• After RWA Move Remote Images, the ACP AE as SCU uses the remote SCP
Query/Retrieve Service Class functionality to import remote Series of Images.
• After RWA Request Storage Commitment, the ACP AE as SCU uses the
remote SCP Storage Commitment Service Class functionality to commit
remote images.
• After RWA Print Images, the ACP AE as SCU uses the remote Print
Management Service Class to request the remote printer status and to print
local images on that printer.

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 10 of 71

• After RWA Get Printer Status (in the service mode), the ACP AE as SCU uses
the remote Print Management Service Class to request the remote printer
status.
• After RWA Verify Application Level Communication, the ACP AE as SCU uses
the remote Request Verification SCP functionality to verify communication.
• After RWA Request Verification (in the service mode), the ACP AE as SCP
provides standard Verification Service Class functionality to the requesting
SCU.

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 11 of 71

Local Real-World Activities Remote Real-World Activities

Integris Allura FD

Request
Modality Query Modality Worklist
Worklist C-FIND

RIS AE
Report
Create and Modality Performed
Set Modality Performed Procedure Step
Procedure Step N-CREATE N-SET

Verify
Application Level Request Verification
Communication C-ECHO

Store Images
Transfer Images
C-STORE

Import Images Import Images

C-STORE

Find Remote Images Query Remote Images

C-FIND

ACP AE Retrieve Remote Images

Move Remote Images C-MOVE

Request Storage Storage Commitment

Commitment N-ACTION
N-EVENT-REPORT

Print
N-CREATE N-GET
Print images N-SET N-ACTION

Get Get Status

printer status N-GET

Verify
Application Level Request Verification
Communication C-ECHO

DICOM Standard Interface

As documented in the PS 3.4, the arrows in the diagram have the following meanings:
- An arrow pointing to the right indicates the local application entity initiates an association.
- An arrow pointing to the left indicates the local application entity accepts an association.

Figure 2 Allura Xper FD20 application data flow diagram

4.1.2. Functional Definition of AE’s

This section describes in general terms the functions performed by RIS AE and ACP
AE.

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 12 of 71

4.1.2.1. Functional Definition of RIS AE

4.1.2.1.1. Basic Worklist Management Service Class

The RIS AE can perform (only to the pre-configured Department System Scheduler)
the Basic Worklist Management service as SCU (RWA Request Modality Worklist),
triggered by the operator. The RIS AE shall request an association. When the
association is accepted, the RIS AE shall send the Worklist request, receive the
Worklist responses, and request for releasing the association.

4.1.2.1.2. Study Management Service Class

The RIS AE can perform (only to the pre-configured Performed Procedure Step
Manager) the Study Management service as SCU (RWA Create and Set Modality
Performed Procedure Step), triggered by the selection of an examination for
acquisition or closing or deletion of an examination. The RIS AE shall request an
association. When the association is accepted, the RIS AE shall send the create and
set requests, receive the responses, and request for releasing the association.

4.1.2.1.3. Verification Service Class

The RIS AE can perform (only to pre-configured systems) the Verification service as
SCU (triggered by the operator in the service mode). The RIS AE shall request an
association. When the association is accepted, the RIS AE shall send the Verification
request, receive the Verification response, and request for releasing the association.

4.1.2.2. Functional Definition of ACP AE

4.1.2.2.1. Storage Service Class

The ACP AE accepts (only from pre-configured systems) associations from systems
that wish to store images using the C-STORE command (RWA Import Images). A
remote SCU shall request an association with the ACP AE for Storage SOP class.
After accepting the association, the ACP AE shall receive and respond to the Storage
requests, and release the association when requested.
The ACP AE can perform (only to pre-configured systems) the Storage service as
SCU (RWA Transfer Images), triggered by the operator or by an event in the system,
e.g. closing of an examination, acquisition of images). The ACP AE shall request an
association with the selected remote SCP for all applicable Storage SOP classes.
When the association is accepted, the ACP AE shall send the Storage requests
(including data from local database), receive the Storage responses and act
accordingly, and finally request for releasing the association.

4.1.2.2.2. Query/Retrieve Service Class

The ACP AE can perform (only to pre-configured systems) the Query/Retrieve service
as SCU (RWA Find Remote Images and Move Remote Images), triggered by the
operator. The ACP AE shall request an association with the selected remote SCP for
the applicable Query/Retrieve SOP class. When the association is accepted, the ACP
AE shall send the Query/Retrieve requests, receive the Query/Retrieve responses and
act accordingly, and finally request for releasing the association.
The ACP AE fully supports the Cancel functionality.
Limitations: Import jobs initiated on the ACP AE to the Image Archive or the Image
Display supporting Grayscale Softcopy Presentation States may fail (if one of a C-
MOVE-RQ is done not only for Series with Images but also for a Series with
Grayscale Softcopy Presentation States objects). However, such images can always
be imported by initiating a Push on the remote node towards the ACP AE.

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 13 of 71

4.1.2.2.3. Storage Commitment Service Class

The ACP AE can perform (only to the Image Archive) the Storage Commitment
service as SCU (RWA Request Storage Commitment), triggered by the closing of an
examination event in the Allura Xper FD20. The ACP AE shall request an association
with the Image Archive SCP for the Storage Commitment Push Model SOP class.
When the association is accepted, the ACP AE shall send the Storage Commitment
request, receive the Storage Commitment request responses and act accordingly. The
ACP AE shall wait for a synchronous report for a specified amount of time and after
that, it shall request for releasing the association. As a result, the Storage Commit
SCP must then request a new association to confirm the storage commit
asynchronously. After accepting that association, the ACP AE shall receive the
Storage Commitment reports, and release the association when requested.

4.1.2.2.4. Print Management Service Class

The ACP AE can perform the Print service as SCU (RWA Print Images), triggered by
the operator. For each printed sheet, the ACP AE 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
ACP AE 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
FilmSession and the FilmBox, 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 ACP AE can perform the Print service as SCU (RWA Get Printer Status),
triggered by the operator in the service mode. The ACP AE shall request an
association with the selected remote SCP (Print Server) for the Printer SOP class.
When the association is accepted, the ACP AE shall send the N-Get request, receive
the responses from the Print Server and act accordingly, and finally request for
releasing the association.

4.1.2.2.5. Verification Service Class

The ACP AE accepts (only from pre-configured systems) associations from systems
that wish to verify application level communication using the C-ECHO command
(RWA Request Verification). A remote SCU shall request an association with the ACP
AE for Verification SOP class. After accepting the association, the ACP AE shall
receive and respond to the Verification request, and release the association when
requested.
The ACP AE can perform (only to pre-configured systems) the Verification service as
SCU (triggered by the operator in the service mode). The ACP AE shall request an
association. When the association is accepted, the ACP AE shall send the Verification
request, receive the Verification response, and request for releasing the association.

4.1.3. Sequencing of Real World Activities

The following sequence of Real World activities are supported by the Allura Xper
FD20:
• The clinical user queries the Department System Scheduler for a (specific)
Worklist representing the list of Scheduled Procedure Steps (with
demographic information). Based on that query entered at the Allura Xper
FD20, it sends the BWLM C-FIND-RQ message with the query criteria.
• The clinical user starts the examination. As a result, the Allura Xper FD20
notifies the Performed Procedure Step Manager of the start of a new

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 14 of 71

Procedure Step, i.e. it sends the MPPS N-CREATE-RQ message with the "IN
PROCESS" status of the examination.
• The clinical user acquires images with a certain procedure. As a result, if
background image transfer is configured, the Allura Xper FD20 sends
automatically the acquired images to the Image Archive and\or the Image
Display, i.e., it sends the C-STORE-RQ messages containing the image
information.
• The clinical user completes the examination. As a result, if auto-transfer is
configured, the Allura Xper FD20 sends images to the Image Archive and/or
Image Display (background image transfer), i.e., it sends the C-STORE-RQ
messages containing the image information.
• When all images, which were to be automatically transferred to the Image
Archive, have been transferred and if Image Archive supports storage-commit,
the Allura Xper FD20 asks the Image Archive to take responsibility for the
images that it has stored that originate from the examination, i.e., it sends the
N-ACTION-RQ message containing the request for storage commit.
• The Allura Xper FD20 notifies the Performed Procedure Step Manager 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:
• The clinical user manually transfers images to the Image Archive and/or
Image Display. As a result, the Allura Xper FD20 sends the C-STORE-RQ
messages containing the image information.
• The clinical user manually prints selected images. As a result, the Allura Xper
FD20 sends the N-GET-RQ message to get the printer status, the N-
CREATE-RQ message to create the FilmSession and the FilmBox, 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.
• The clinical user queries the Image Archive or Image Display for Series
entities. As a result, the Allura Xper FD20 sends a number of C-FIND-RQ
messages containing the query criteria. The results received from the Image
Archive or Image Display (i.e., Series entities) are presented to the clinical
user as a list of entries, where each entry represents a set of Series entities
with the same Study Instance UID (0020,000D), Protocol Name (0018,1030),
and Performing Physician’s Name (0008,1050).
• The clinical user asks for the retrieval of one entry from the Image Archive or
Image Display. As a result, the Allura Xper FD20 sends the C-MOVE-RQ
messages containing the identification of the Series of images to be imported.
• The clinical user may delete an examination. As a result, if it is a Worklist
examination, an association is established for transmitting an N-SET request
with the “DISCONTINUED” status.

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

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 15 of 71

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.

Select Examination for Acquisition

Department Performed
Image Archive/
ACP AE RIS AE System Procedure Step Print Server
Image Display
Scheduler Manager

Query for Worklist

Query Worklist

Receive Worklist

Select Examination for Acquisition

Create MPPS
MPPS

Image Acquired
Store Images

Print Images

Examination Closed
Store Images

Commit Images

Commitment confirmation

Set MPPS

Query Images

Receive Images

Figure 3 Allura Xper FD20 Sequencing constraints

4.2. AE Specifications
The next section contains entity specifications for each application entity.

4.2.1. RIS AE
Every detail of the RIS AE shall be completely specified under this section.

4.2.1.1. SOP Classes

The RIS AE provides Standard Conformance to the SOP Classes presented in Table
3.

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 16 of 71

Table 3: SOP Classes for RIS AE

SOP Class Name SOP Class UID SCU SCP

Modality Worklist Information Model – FIND 1.2.840.10008.5.1.4.31 Yes No
Modality Performed Procedure Step 1.2.840.10008.3.1.2.3.3 Yes No
Verification 1.2.840.10008.1.1 Yes No
Note: Any SOP specific behavior is documented later in the conformance statement in the applicable SOP
specific conformance section.

4.2.1.2. Association Policies

This section contains a description of the general association establishment and
acceptance policies of the RIS AE.

4.2.1.2.1. General
The RIS AE always proposes the DICOM Application Context Name (ACN) presented
in Table 4. The maximum PDU length for receiving data can be configured. The
minimum PDU size is 4 Kbytes (4kB) and the maximum PDU length is 215 Bytes. The
PDU length for sending data is unrestricted.

Table 4: DICOM Application Context

Application Context Name 1.2.840.10008.3.1.1.1

4.2.1.2.2. Number of Associations

The RIS AE supports a maximum of two simultaneous associations as SCU. The
associations can be either for the execution of Modality Worklist query, or for the
execution of Modality Performed Procedure Step (MPPS), or for the execution of
Verification of Application Level Communication.
The RIS AE does not handle incoming associations.

Table 5: Number of Associations as an Association Initiator for RIS AE

Maximum number of simultaneous associations 2

Table 6: Number of Associations as an Association Acceptor for RIS AE

Maximum number of simultaneous associations N.A.

4.2.1.2.3. Asynchronous Nature

The RIS AE does not support asynchronous operations and will not perform
asynchronous window negotiation.

Table 7: Asynchronous Nature as an Association Initiator for RIS AE

Maximum number of outstanding asynchronous transactions N.A.

4.2.1.2.4. Implementation Identifying Information

The value supplied for Implementation Class UID is presented in Table 8.

Table 8: DICOM Implementation Class and Version for RIS AE

Implementation Class UID 1.3.46.670589.7.28.2.0.0

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 17 of 71

Implementation Version Name AlluraXper20RIS

4.2.1.3. Association Initiation Policy

The RIS AE initiates associations as a result of the following events:
• The operator queries for the Worklist (see Section 4.2.1.3.1)
• The operator selects a Worklist-based examination for acquisition (see
Section 4.2.1.3.2)
• The operator cancels, removes or closes an examination (see Section
4.2.1.3.2)
• In the service mode, the operator verifies application level communication
(see Section 4.2.1.3.3).

4.2.1.3.1. Request Modality Worklist

4.2.1.3.1.1. Description and Sequencing of Activities

For each Broad or Specific Worklist request, the RIS AE 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 4). All returned Worklist items are displayed to the operator who
can select an item from the Worklist and perform an examination.

Request Modality
Remote AE
Worklist

A-ASSOCIATE

C-FIND

A-RELEASE

Figure 4 Sequencing of RWA Request Modality Worklist

The clinical user may cancel the query to the Department System Scheduler. As a
result, the Allura Xper FD20 sends a C-FIND Cancel Request to the Department
System Scheduler.

4.2.1.3.1.2. Proposed Presentation Contexts

Each time an association is initiated, the RIS AE proposes one presentation contexts
to be used on that association. The presentation context proposed by the RIS AE for
Request Modality Worklist is defined in Table 9.

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 18 of 71

Table 9: Proposed Presentation Contexts for RIS AE Request Modality Worklist

Presentation Context Table

Abstract Syntax Transfer Syntax Extended

Role
Negotiation
Name UID Name List UID List
MWL – FIND 1.2.840.10008.5.1.4.31 ILE 1.2.840.10008.1.2 SCU None
ELE 1.2.840.10008.1.2.1
EBE 1.2.840.10008.1.2.2

The implementation chooses ELE transfer syntax in case multiple transfer syntaxes
are accepted in the association acceptance.

4.2.1.3.1.3. SOP Specific Conformance for SOP Classes

Two kinds of queries can be done with the RIS AE: 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 10.
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 11.
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).
Attributes shown in the C-FIND response are configurable.

Table 10 Matching Table MWL Information Model – Broad Query

Attribute Name Tag Matching Key

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

Table 11 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 Date (0040,0002) Universal matching or range matching
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

Worklist request identifier of the RIS AE queries is presented in Table 12 up till Table
20.

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 19 of 71

Table 12: Worklist request identifier: Patient Identification Module

Attribute Name Tag Note
Patient's Name 0010,0010
Patient ID 0010,0020
Other Patient IDs 0010,1000

Table 13: Worklist request identifier: Patient Demographic Module

Attribute Name Tag Note
Patient's Birth Date 0010,0030
Patient's Birth Time 0010,0032
Patient's Sex 0010,0040 Applied Value(s): F, M, O
Patient's Size 0010,1020
Patient's Weight 0010,1030
Ethnic Group 0010,2160
Patient Comments 0010,4000
Patient Data Confidentiality Constraint
0040,3001
Description

Table 14: Worklist request identifier: Patient Medical Module

Attribute Name Tag Note
Medical Alerts 0010,2000
Contrast Allergies 0010,2110
Additional Patient History 0010,21B0
Pregnancy Status 0010,21C0 Applied Value(s): 0001, 0002, 0003, 0004
Patient State 0038,0500

Table 15: Worklist request identifier: Visit Relationship Module

Attribute Name Tag Note
Referenced Patient Sequence 0008,1120
>Referenced SOP Class UID 0008,1150
>Referenced SOP Instance UID 0008,1155

Table 16: Worklist request identifier: Visit Status Module

Attribute Name Tag Note
Current Patient Location 0038,0300

Table 17: Worklist request identifier: Scheduled Procedure Step Module

Attribute Name Tag Note
Scheduled Procedure Step Sequence 0040,0100
>Modality 0008,0060
>Requested Contrast Agent 0032,1070
>Scheduled Station AE Title 0040,0001
>Scheduled Procedure Step Start Date 0040,0002
>Scheduled Procedure Step Start Time 0040,0003
>Scheduled Performing Physician's Name 0040,0006
>Scheduled Procedure Step Description 0040,0007
>Scheduled Action Item Code Sequence 0040,0008
>>Code Value 0008,0100
>>Coding Scheme Designator 0008,0102

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 20 of 71

Attribute Name Tag Note

>>Code Meaning 0008,0104
>Scheduled Procedure Step ID 0040,0009
>Scheduled Procedure Step Location 0040,0011
>Pre-Medication 0040,0012

Table 18: Worklist request identifier: Requested Procedure Module

Attribute Name Tag Note
Referenced Study Sequence 0008,1110
>Referenced SOP Class UID 0008,1150
>Referenced SOP Instance UID 0008,1155
Study Instance UID 0020,000D
Requested Procedure Description 0032,1060
Requested Procedure Code Sequence 0032,1064
>Code Value 0008,0100
>Coding Scheme Designator 0008,0102
>Code Meaning 0008,0104
Requested Procedure ID 0040,1001
Reason for the Requested Procedure 0040,1002
Requested Procedure Priority 0040,1003
Patient Transport Arrangements 0040,1004
Requested Procedure Location 0040,1005
Names of Intended Recipients of Results 0040,1010
Requested Procedure Comments 0040,1400

Table 19: Worklist request identifier: Imaging Service Request Module

Attribute Name Tag Note
Accession Number 0008,0050
Referring Physician's Name 0008,0090
Requesting Physician 0032,1032
Requesting Service 0032,1033
Reason for the Imaging Service Request 0040,2001
Issue Date of Imaging Service Request 0040,2004
Issue Time of Imaging Service Request 0040,2005
Imaging Service Request Comments 0040,2400

Table 20: Worklist request identifier: SOP Common Module

Attribute Name Tag Note
Specific Character Set 0008,0005 See chapter 7 for more information

The behavior of the RIS AE for status codes in a Modality Worklist C-FIND response
is presented in Table 21.

Table 21: Modality Worklist C-FIND Response Status Handling Behavior

Service Status Further Meaning Error Code Behavior

Success Matching is complete - No final 0000 The result is reported to the user
Identifier is supplied. and is logged.
Refused Out of Resources A700 Stops with processing the C-Find
Response(s) from the SCP. The
reason is logged and the failure is
reported to the user.

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 21 of 71

Service Status Further Meaning Error Code Behavior

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

The behavior of the RIS AE during communication failure is presented in Table 22.

Table 22: Modality Worklist Communication Failure Behavior

Exception Behavior
Timeout The query is marked as failed. The association is aborted using
A-ABORT. The reason is logged and reported to the user. The
RIS AE 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.3.2. Create and Set Modality Performed Procedure Step

4.2.1.3.2.1. Description and Sequencing of Activities

For a Worklist examination, when such an examination is selected for acquisition, one
association towards the Modality Performed Procedure Step SCP is established, and
an N-CREATE request with status “IN PROGRESS” is transmitted. Once the
response is received, the association is closed. When, later on, the examination is
cancelled/removed or closed, an association is established for transmitting an N-SET
request. The status field will respectively be set to “DISCONTINUED” or
“COMPLETED”. Once the response is received, the association is closed. Sequencing
of Activities in case of a Worklist examination is presented in Figure 5.
For a local examination, when such an examination is selected for acquisition, no
association towards the Modality Performed Procedure Step SCP is established.
When, later on, the examination is closed, an association is established for the N-

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 22 of 71

CREATE request and the N-SET request. Once the responses are received, the
association is closed. Sequencing of Activities in case of a local examination is
presented in Figure 6.

Create and Set

Modality
Remote AE
Performed
Procedure Step

A-ASSOCIATE

N-CREATE (IN PROGRESS)

A-RELEASE

A-ASSOCIATE

N-SET(COMPLETED/DISCONTINUED)

A-RELEASE

Figure 5 Sequencing of RWA Create and Set Modality Performed Procedure

Step (for a Worklist examination)

Create and Set

Modality
Remote AE
Performed
Procedure Step

A-ASSOCIATE

N-CREATE (IN PROGRESS)

N-SET(COMPLETED/DISCONTINUED)

A-RELEASE

Figure 6 Sequencing of RWA Create and Set Modality Performed Procedure

Step (for a local examination)

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 23 of 71

4.2.1.3.2.2. Proposed Presentation Contexts

Each time an association is initiated, the RIS AE proposes one presentation context to
be used on that association. The presentation context proposed by the RIS AE for
Create and Set Modality Performed Procedure Step is defined in Table 23.

Table 23 Proposed Presentation Contexts for RIS AE Create and Set Modality
Performed Procedure Step

Presentation Context Table

Abstract Syntax Transfer Syntax Extended

Role
Negotiation
Name UID Name List UID List
MPPS 1.2.840.10008.3.1.2.3.3 ILE 1.2.840.10008.1.2 SCU None
ELE 1.2.840.10008.1.2.1
EBE 1.2.840.10008.1.2.2

The implementation chooses ELE 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 35 Table 36, and Table 37.

4.2.1.3.2.3. SOP Specific Conformance for SOP Classes

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 24 up till Table 29
indicate whether or not an attribute and attribute value is sent during N-CREATE.
Table 30 up till Table 34 indicate whether or not an attribute and attribute value is sent
during MPPS N-SET.

Table 24: N-CREATE MPPS Request Identifier: SOP Common Module

Attribute Name Tag Note
Specific Character Set 0008,0005 See chapter 7 for more information

Table 25: N-CREATE MPPS Request Identifier: Image Acquisition Results

Module
Attribute Name Tag Note
Modality 0008,0060 Applied Value(s): XA
Note 0020,0010
Study ID
Performed Action Item Code Sequence 0040,0260 Sequence remains empty
Performed Series Sequence 0040,0340 Sequence will be empty when there are no
images to report
Note:: If no Study ID is known, the Accession Number will be used as value.

Table 26: N-CREATE MPPS Request Identifier: Performed Procedure Step

Information Module
Attribute Name Tag Note
Procedure Code Sequence 0008,1032
>Code Value 0008,0100

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 24 of 71

Attribute Name Tag Note

>Coding Scheme Designator 0008,0102
>Code Meaning 0008,0104
Performed Station AE Title 0040,0241 AE Title as configured by the RIS/CIS unit.
Performed Station Name 0040,0242
Performed Location 0040,0243 Always Empty
Performed Procedure Step Start Date 0040,0244
Performed Procedure Step Start Time 0040,0245
Performed Procedure Step End Date 0040,0250
Performed Procedure Step End Time 0040,0251
Performed Procedure Step Status 0040,0252
Performed Procedure Step ID 0040,0253
Performed Procedure Step Description 0040,0254
Performed Procedure Type Description 0040,0255

Table 27: N-CREATE MPPS Request Identifier: Performed Procedure Step

Relationship Module
Attribute Name Tag Note
Referenced Patient Sequence 0008,1120
>Referenced SOP Class UID 0008,1150
>Referenced SOP Instance UID 0008,1155
Patient's Name 0010,0010
Patient ID 0010,0020
Patient's Birth Date 0010,0030
Patient's Sex 0010,0040
Scheduled Step Attribute Sequence 0040,0270
>Accession Number 0008,0050
>Referenced Study Sequence 0008,1110
>>Referenced SOP Class UID 0008,1150
>>Referenced SOP Instance UID 0008,1155
>Study Instance UID 0020,000D
>Requested Procedure Description 0032,1060
>Scheduled Procedure Step Description 0040,0007
>Scheduled Action Item Code Sequence 0040,0008
>>Code Value 0008,0100
>>Coding Scheme Designator 0008,0102
>>Code Meaning 0008,0104
>Scheduled Procedure Step ID 0040,0009
>Requested Procedure ID 0040,1001

Table 28: N-CREATE MPPS Request Identifier: Billing and Material Management
Codes Module
Attribute Name Tag Note
Film Consumption Sequence 0040,0321 Always empty

Table 29: N-CREATE MPPS Request Identifier: Radiation Dose Module

Attribute Name Tag Note
Image Area Dose Product 0018,115E
Total Time of Fluoroscopy 0040,0300
Total Number of Exposures 0040,0301
Entrance Dose 0040,0302
Entrance Dose in mGy 0040,8302

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 25 of 71

Table 30: N-SET MPPS Request Identifier: Image Acquisition Results Module
Attribute Name Tag Note
Performed Action Item Code Sequence 0040,0260 Sequence remains empty
>Code Value 0008,0100
>Coding Scheme Designator 0008,0102
>Code Meaning 0008,0104
Performed Series Sequence 0040,0340 May empty when no images to be reported
>Performing Physician’s Name 0008,1050
>Operators Name 0008,1070
>Protocol Name 0018,1030
>Series Instance UID 0020,000E
>Series Description 0008,103E
>Retrieve AE Title 0008,0054
>Referenced Image Sequence 0008,1140 Refers to Dicom Object that were automatically
transferred to the Image Archive.
>>Referenced SOP Class UID 0008,1150
>>Referenced SOP Instance UID 0008,1155
>Referenced Standalone SOP Instance 0040,0220 Refers to Dicom Object that were automatically
Sequence transferred to the Image Archive.
>>Referenced SOP Class UID 0008,1150
>>Referenced SOP Instance UID 0008,1155

Table 31: N-SET MPPS Request Identifier: Performed Procedure Step

Information Module
Attribute Name Tag Note
Procedure Code Sequence 0008,1032
>Code Value 0008,0100
>Coding Scheme Designator 0008,0102
>Code Meaning 0008,0104
Performed Procedure Step End Date 0040,0250
Performed Procedure Step End Time 0040,0251
Performed Procedure Step Status 0040,0252 Applied Values: “COMPLETED” or
“DISCONTINUED”
Performed Procedure Step Description 0040,0254
Performed Procedure Type Description 0040,0255

Table 32: N-SET MPPS Request Identifier: Radiation Dose Module

Attribute Name Tag Note
Image Area Dose Product 0018,115E
Total Time of Fluoroscopy 0040,0300
Total Number of Exposures 0040,0301
Entrance Dose 0040,0302 In dGy
Entrance Dose in mGy 0040,8302 In mGy

Table 33: N-SET MPPS Request Identifier: Billing and Material Management
Codes Module
Attribute Name Tag Note
Film Consumption Sequence 0040,0321
>Medium Type 2000,0030
>Film Size ID 2010,0050 DICOM defined terms are extended with the
“ANY FILM” term

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 26 of 71

Attribute Name Tag Note

>Number of Films 2100,0170

Table 34: N-SET MPPS Request Identifier: SOP Common Module

Attribute Name Tag Note
Specific Character Set 0008,0005
Note: The SOP Common Module is also send during the N-SET Request

Referenced Image Sequence (0008,1140) and to Referenced Standalone SOP

Instance Sequence (0040,0220) report all Image Series which have been
automatically transferred to the Image Archive. The manually transferred series are
not reported in MPPS.
The behavior of the RIS AE for status codes in an MPPS N-CREATE response and N-
SET response is presented in Table 35 and Table 36 respectively. In case of the
retransmission attempt each message stored in the persistent queue is sent over a
separate association.

Table 35: MPPS N-CREATE Response Status Handling Behavior

Service Status Further Meaning Error Code Behavior

Success Successful operation. 0000 The related examination is updated
and if this response status is the
result of the retransmission attempt
message is removed from the
persistent queue.
Failure Resource limitation 0213 The message contents 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 If the response status is reported
status code 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
(i.e., the examination enters the
COMPLETED/DISCONTINUED
status) and the message is
removed from the persistent queue.
The response status is logged as a
warning.

Table 36: MPPS N-SET Response Status Handling Behavior

Service Status Further Meaning Error Code Behavior

Success Successful operation. 0000 The related examination is
updated and if this response status
is the result of the retransmission
attempt message is removed from
the persistent queue. The
examination status is set to
COMPLETED and it is logged.

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 27 of 71

Service Status Further Meaning Error Code Behavior

Failure Resource limitation 0213 The message contents 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 If this response status is reported
status code 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
and the message is removed from
the persistent queue. The
response status is logged as a
warning. The examination status is
set to COMPLETED.

The behavior of the RIS AE during communication failure is summarized in Table 37.

Table 37: MPPS Communication Failure Behavior (N-SET, N_CREATE)

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.3.3. Verify Application Level Communication

4.2.1.3.3.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.

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 28 of 71

Verify Application
Level Remote AE
Communication

A-ASSOCIATE

C-ECHO

A-RELEASE

Figure 7 Sequencing of RWA Verify Application Level Communication

4.2.1.3.3.2. Proposed Presentation Contexts

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

Table 38: Proposed Presentation Contexts for RIS AE Verify Application Level
Communication

Presentation Context Table

Abstract Syntax Transfer Syntax Extended

Role
Negotiation
Name UID Name List UID List
Verification 1.2.840.10008.1.1 ILE 1.2.840.10008.1.2 SCU None
ELE 1.2.840.10008.1.2.1
EBE 1.2.840.10008.1.2.2

The implementation chooses ELE transfer syntax in case multiple transfer syntaxes
are accepted in the association acceptance.

4.2.1.3.3.3. SOP Specific Conformance for SOP Classes

The behavior of the RIS AE for status codes in an Verification response is
summarized in Table 39.

Table 39: Verification C-ECHO Response Status Handling Behavior

Service Status Further Meaning Error Code Behavior

Success Successful operation. 0000 The success is reported to the
operator.
* * Any other The failure is reported to the
status code operator.

The behavior of the RIS AE during communication failure is summarized in Table 40.

Table 40: Verification Communication Failure Behavior

Exception Behavior
Timeout The association is aborted using A-ABORT. The reason is
logged and reported to the user.

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 29 of 71

Exception Behavior
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.4. Association Acceptance Policy

The RIS AE does not accept associations.

4.2.2. ACP AE
Every detail of the ACP AE shall be completely specified under this section.

4.2.2.1. SOP Classes

The ACP AE provides Standard Conformance to the SOP Classes presented in Table
41.

Table 41: SOP Classes for ACP AE

SOP Class Name SOP Class UID SCU SCP

Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7 Yes Yes
X-Ray Angiographic Image Storage 1.2.840.10008.5.1.4.1.1.12.1 Yes Yes
Patient Root Query/Retrieve Information Model – 1.2.840.10008.5.1.4.1.2.1.1 Yes No
FIND
Patient Root Query/Retrieve Information Model – 1.2.840.10008.5.1.4.1.2.1.2 Yes No
MOVE
Study Root Query/Retrieve Information Model – 1.2.840.10008.5.1.4.1.2.2.1 Yes No
FIND
Study Root Query/Retrieve Information Model – 1.2.840.10008.5.1.4.1.2.2.2 Yes No
MOVE
Storage Commitment Push Model 1.2.840.10008.1.20.1 Yes No
Basic Grayscale Print Management (Meta) 1.2.840.10008.5.1.1.9 Yes No
>Basic Film Session 1.2.840.10008.5.1.1.1 Yes No
>Basic Film Box 1.2.840.10008.5.1.1.2 Yes No
>Basic Grayscale Image Box 1.2.840.10008.5.1.1.4 Yes No
>Printer 1.2.840.10008.5.1.1.16 Yes No
Verification 1.2.840.10008.1.1 Yes Yes
Note: Any SOP specific behavior is documented later in the conformance statement in the applicable SOP
specific conformance section.

4.2.2.2. Association Policies

This section contains a description of the general association establishment and
acceptance policies of the ACP AE.

4.2.2.2.1. General
The ACP AE always proposes the DICOM Application Context Name (ACN)
presented in Table 42. The maximum PDU length for receiving data is unrestricted
and can be configured (0< max. PDU < 232 -1 Bytes). The PDU length for sending
data is unrestricted.

Table 42: DICOM Application Context

Application Context Name 1.2.840.10008.3.1.1.1

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 30 of 71

4.2.2.2.2. Number of Associations

As a result of local activities, the ACP AE (SCU) can initialize a maximum of six
simultaneous associations. One association may be used to issue storage
commitment or transfer images requests, another association may be used to find
remote Series of Images, another association may be used to move remote Series of
Images, another association may be used to print images, another association may be
used to handle storage commitment notifications, and finally another association may
be used to verify application level communication.
The maximum number of simultaneous associations supported by the ACP AE (SCP)
is unlimited by default and can be configured.

Table 43: Number of Associations as an Association Initiator for ACP AE

Maximum number of simultaneous associations 6

Table 44: Number of Associations as an Association Acceptor for ACP AE

Maximum number of simultaneous associations Unlimited

4.2.2.2.3. Asynchronous Nature

The ACP AE 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.

Table 45: Asynchronous Nature as an Association Initiator for ACP AE

Maximum number of outstanding asynchronous transactions 1

4.2.2.2.4. Implementation Identifying Information

The value supplied for Implementation Class UID is presented in Table 46.

Table 46: DICOM Implementation Class UID and Version Name for ACP AE

Implementation Class UID 1.3.46.670589.7.28.2.0.1

Implementation Version Name AlluraXper20ACP

4.2.2.3. Association Initiation Policy

The ACP AE initiate associations as a result of the following events:
• Images are transferred from the Allura Xper FD20 to a remote system (see
Section 4.2.2.3.1).
• The operator queries for remote Series of Images (see Section 4.2.2.3.2).
• The operator requests import of remote Series of Images (see Section
4.2.2.3.3).
• A storage commitment for archived images is requested (see Section
4.2.2.3.4).
• The operator prints local images (see Section 4.2.2.3.5).
• In the service mode, the operator verifies printer status (see Section
4.2.2.3.6).
• In the service mode, the operator verifies application level communication
(see Section 4.2.2.3.7).

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 31 of 71

4.2.2.3.1. Transfer Images

4.2.2.3.1.1. Description and Sequencing of Activities

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

Transfer Images Remote AE

A-ASSOCIATE

C-STORE

A-RELEASE

Figure 8 Sequencing of RWA Transfer Images

4.2.2.3.1.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
Transfer Images is defined in Table 47.

Table 47: Proposed Presentation Contexts for Transfer Images

Presentation Context Table

Abstract Syntax Transfer Syntax

Extended
Role
Name Negotiation
Name UID UID List
List
Secondary 1.2.840.10008.5.1.4.1.1.7 ILE 1.2.840.10008.1.2 SCU None
Capture Image ELE 1.2.840.10008.1.2.1
Storage SOP EBE 1.2.840.10008.1.2.2
Note 1
Class FOP 1.2.840.10008.1.2.4.70
X-Ray Angio- 1.2.840.10008.5.1.4.1.1.12.1 ILE 1.2.840.10008.1.2 SCU None
graphic Image ELE 1.2.840.10008.1.2.1
Storage SOP EBE 1.2.840.10008.1.2.2
Note 1
Class FOP 1.2.840.10008.1.2.4.70
Note 1: Lossless, Non-Hierarchical, first-order prediction JPEG compression.

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

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 32 of 71

SCP has to react with a chosen transfer syntax, the per SOP Class used transfer
syntax is forced by the SCP.

4.2.2.3.1.3. SOP Specific Conformance for SOP Classes

The ACP AE can exchange image data in the following formats:
• Standard Extended X-Ray Angiographic (1.2.840.10008.5.1.4.1.1.12.1)
• Standard Secondary Capture (1.2.840.10008.5.1.4.1.1.7)

X-Ray Angiographic images can either be sent with raw pixel data or processed pixel
data.
The contents of Standard Extended X-Ray Angiographic Image Storage SOP
Instances and Standard Secondary Capture Image Storage SOP Instances created by
ACP AE conform to the DICOM X-Ray Angiographic Image IOD and Standard
Secondary Capture Image IOD respectively (see Section 8.1.2 and Section 8.1.1).
The behavior of the ACP AE for status codes in an C-STORE response is
summarized in Table 48.

Table 48: Storage C-STORE Response Status Handling Behavior

Service Status Further Meaning Error Code Behavior

Success Successful operation 0000 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 Out of Resources A700-A7FF The association is aborted using A-
ABORT and the send job is marked
as failed.
The failure reason is logged.
Error Data Set does not match SOP A900-A9FF The association is aborted using A-
Class ABORT and the send job is marked
as failed. The failure reason is
logged.
Cannot Understand C000-CFFF The association is aborted using A-
ABORT and the send job is marked
as failed. The failure reason is
logged.
Warning Coercion of Data Elements B000 The association is aborted using A-
ABORT and the send job is marked
as failed. The failure reason is
logged.
Elements discarded B006 The association is aborted using A-
ABORT and the send job is marked
as failed. The failure reason is
logged.
Data set does not match SOP class B007 The association is aborted using A-
ABORT and the send job is marked
as failed. The failure reason is
logged.
* * Any other The association is aborted using A-
status code ABORT and the send job is marked
as failed. The failure reason is
logged.

The behavior of the ACP AE during communication failure is summarized in Table 49.

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 33 of 71

Table 49: Storage Communication Failure Behavior

Exception Behavior
Timeout The association is aborted using A-ABORT and the
send job is marked as failed. The failure reason is logged.
Association aborted The association is aborted using A-ABORT and the
send job is marked as failed. The failure reason is logged.
Association rejected The association is aborted using A-ABORT and the
send job is marked as failed. The failure reason is logged.

4.2.2.3.2. Find Remote Images

4.2.2.3.2.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 9 and Figure 10.

Find Remote
Remote AE
Images

A-ASSOCIATE

C-FIND(Patient level)

C-FIND(Study level)

C-FIND(Series level)

A-RELEASE

Figure 9 Sequencing of RWA Find Remote Images (Patient Root Q/R Information
Model)

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 34 of 71

Find Remote
Remote AE
Images

A-ASSOCIATE

C-FIND(Study level)

C-FIND(Series level)

A-RELEASE

Figure 10 Sequencing of RWA Find Remote Images (Study Root Q/R Information
Model)
The clinical user may cancel the query to the Image Archive or Image Display. As a
result, the Allura Xper FD20 sends a C-FIND Cancel Request to the Image Archive or
Image Display.

4.2.2.3.2.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 50.

Table 50: Proposed Presentation Contexts for Find Remote Images

Presentation Context Table

Abstract Syntax Transfer Syntax

Extended
Role
Name Negotiation
Name UID UID List
List
Pat. Root Q/R 1.2.840.10008.5.1.4.1.2.1.1 ILE 1.2.840.10008.1.2 SCU None
Inf. Model– ELE 1.2.840.10008.1.2.1
FIND SOP EBE 1.2.840.10008.1.2.2
Class
Study Root 1.2.840.10008.5.1.4.1.2.2.1 ILE 1.2.840.10008.1.2 SCU None
Q/R Inf. ELE 1.2.840.10008.1.2.1
Model–FIND EBE 1.2.840.10008.1.2.2
SOP Class

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.2.3.2.3. SOP Specific Conformance for SOP Classes

With the Allura Xper FD20 one can query for Series of Images. Series of Images
which have the same Study Instance UID (0020,000D), Protocol Name (0018,1030),
and Performing Physician’s Name (0008,1050), will be presented as one query result.
The Allura Xper FD20 interprets this as one query result belonging to the same
examination.

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 35 of 71

A query can be done with one of the DICOM attributes presented in Table 51 up till
Table 55.

Table 51: Patient Root Query/Retrieve Information Model – FIND SOP Class:
Patient level keys
Attribute Name Tag Matching type
Patient's Name 0010,0010 Single value matching or wild card matching or
universal matching
Patient ID 0010,0020 Single value matching or universal matching
Patient's Birth Date 0010,0030 Single value matching or universal matching
Patient's Sex 0010,0040 Universal matching only

Table 52: Patient Root Query/Retrieve Information Model – FIND SOP Class
:Study level keys
Attribute Name Tag Matching type
Study Date 0008,0020 Range matching or universal matching
Study Time 0008,0030 Universal matching only
Accession Number 0008,0050 Single value matching or wild card matching or
universal matching
Study ID 0020,0010 Universal matching only
Study Instance UID 0020,000D Universal matching only
Patient ID 0010,0020 Single value matching or universal matching

Table 53: Patient Root Query/Retrieve Information Model – FIND SOP Class:
Series level keys
Attribute Name Tag Matching type
Modality 0008,0060 Universal matching only
Series Number 0020,0011 Universal matching only
Series Instance UID 0020,000E Universal matching only
Performing Physician's Name 0008,1050 Universal matching only
Protocol Name 0018,1030 Single value matching or universal matching
Patient ID 0010,0020 Single value matching or universal matching
Study Instance UID 0020,000D Single value matching only

Table 54: Study Root Query/Retrieve Information Model – FIND SOP Class:
Study level keys
Attribute Name Tag Matching type
Study Date 0008,0020 Range matching or universal matching
Study Time 0008,0030 Universal matching only
Accession Number 0008,0050 Value matching or wild card matching or
universal matching
Patient's Name 0010,0010 Single value matching or wild card matching or
universal matching
Patient ID 0010,0020 Single value matching or universal matching
Patient's Birth Date 0010,0030 Single value matching or universal matching
Patient's Sex 0010,0040 Universal matching only
Study ID 0020,0010 Universal matching only
Study Instance UID 0020,000D Universal matching only

Table 55: Study Root Query/Retrieve Information Model – FIND SOP Class:
Series level keys
Attribute Name Tag Matching type
Modality 0008,0060 Universal matching only
Performing Physician's Name 0008,1050 Universal matching only

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 36 of 71

Attribute Name Tag Matching type

Protocol Name 0018,1030 Single value matching or universal matching
Study Instance UID 0020,000D Single value matching only
Series Instance UID 0020,000E Universal matching only
Series Number 0020,0011 Universal matching only

The behavior of the ACP AE for status codes in an C-FIND response is summarized in
Table 56.

Table 56: Query C-FIND Response Status Handling Behavior

Service Status Further Meaning Error Code Behavior

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

The behavior of the ACP AE during communication failure is presented in Table 57.

Table 57: Query Communication Failure Behavior

Exception Behavior
Timeout The query is marked as failed. The association is aborted using
A-ABORT. The reason is logged and reported to the user. The
ACP AE 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.

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 37 of 71

4.2.2.3.3. Move Remote Images

4.2.2.3.3.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 11.
C-MOVE requests are done on the series level.

Move Remote
Remote AE
Images

A-ASSOCIATE

C-MOVE

A-RELEASE

Figure 11 Sequencing of RWA Move Remote Images

The clinical user may cancel the move operation. As a result, the Allura Xper FD20
sends a C-MOVE Cancel Request to the Image Archive or Image Display.

4.2.2.3.3.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
Move Remote Images is defined in Table 58.

Table 58: Proposed Presentation Contexts for Move Remote Images

Presentation Context Table

Abstract Syntax Transfer Syntax

Extended
Role
Name Negotiation
Name UID UID List
List
Pat.Root Q/R 1.2.840.10008.5.1.4.1.2.1.2 ILE 1.2.840.10008.1.2 SCU None
Inf. Model – ELE 1.2.840.10008.1.2.1
MOVE SOP EBE 1.2.840.10008.1.2.2
Class
Study Root 1.2.840.10008.5.1.4.1.2.2.2 ILE 1.2.840.10008.1.2 SCU None
Q/R Inf. ELE 1.2.840.10008.1.2.1
Model–MOVE EBE 1.2.840.10008.1.2.2
SOP Class

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.

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 38 of 71

4.2.2.3.3.3. 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 59 or Table 60.

Table 59: Patient Root Query/Retrieve Information Model – MOVE SOP Class:
Series level attributes
Attribute Name Tag Matching type
Patient ID 0010,0020 Single value matching or universal matching
Study Instance UID 0020,000D Single value
Series Instance UID 0020,000E Single value

Table 60: Study Root Query/Retrieve Information Model – MOVE SOP Class:
Series level attributes
Attribute Name Tag Matching type
Series Instance UID 0020,000E Single value
Study Instance UID 0020,000D Single value

The behavior of the ACP AE for status codes in an C-MOVE response is summarized
in Table 61.

Table 61: Query C-MOVE Response Status Handling Behavior

Service Status Further Meaning Error Code Behavior

Refused Out of Resources – Unable to A701 The move job is marked as failed.
calculate number of matches The association is released. The
reason is logged and reported to
the user.
Out of Resources – Unable to A702 The move job is marked as failed.
perform suboperations The association is released. The
reason is logged and reported to
the user.
Move Destination Unknown A801 The move job is marked as failed.
The association is released. The
reason is logged and reported to
the user.

Failed Identifier Does Not Match SOP A900 The move job is marked as failed.
Class The association is released. The
reason is logged and reported to
the user.
Unable to process Cxxx The move job is marked as failed.
The association is released. The
reason is logged and reported to
the user.
Cancel Sub-operations terminated due to FE00 The move job is marked as
Cancel Indication cancelled. The association is
released. The reason is logged and
reported to the user.
Success Sub-operations Complete – No 0000 The move job is marked as
Failures completed. The association is
released. Success is logged.
Warning Sub-operations Complete – One or B000 The move job is marked as failed.
more Failures The association is released. The
reason is logged and reported to
the user.

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 39 of 71

Service Status Further Meaning Error Code Behavior

Pending Sub-operations are continuing FF00 The move job continues.

* * Any other The association is aborted using A-

status code ABORT. The reason is logged and
the failure is reported to the user.

The behavior of the ACP AE during MOVE Communication failure is presented in

Table 62.

Table 62: Move Communication Failure Behavior

Exception Behavior
Timeout The query is marked as failed. The association is aborted using
A-ABORT. The reason is logged and reported to the user. The
ACP AE 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.2.3.4. Request Storage Commitment

4.2.2.3.4.1. Description and Sequencing of Activities

If the Remote AE is configured as an Image Archive and images have been sent to
that Image Archive, the ACP AE will request storage commitment for instances of
these images before it closes the examination. The request is forwarded to the job
queue and processed as individual request to Request Storage Commitment. Only if a
corresponding storage commitment notification is successfully received, the
examination is completed.
For each request to Request Storage Commitment, one association towards the
remote system is established, and the N-ACTION request is transmitted. The storage
commitment request (N-ACTION) and confirmation (N-EVENT-REPORT) can be
handled either in a synchronous (see Figure 12) or asynchronous (see Figure 13) way
(a configurable item). The ACP AE can wait for synchronous report for a specified
amount of time (configurable) and after that, it will request for releasing the
association. As a result, the Storage Commit SCP must then request a new
association to confirm the storage commit asynchronously.
The successful completion of the storage commitment request job only indicates that
the N-ACTION request has been successfully transmitted to the Remote AE. In case
of a synchronous storage commitment, the examination is marked as completed right
after the successful completion of the storage commitment request job. In case of a
asynchronous storage commitment, the examination is marked as completed only if a
corresponding storage commitment notification from the Remote AE has been
successfully received.

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 40 of 71

Request Storage
Remote AE
Commitment

A-ASSOCIATE

N-ACTION

N-EVENT-REPORT

A-RELEASE

Figure 12 Sequencing of RWA Request Storage Commitment (synchronous)

Request Storage
Remote AE
Commitment

A-ASSOCIATE

N-ACTION

A-RELEASE

A-ASSOCIATE

N-EVENT-REPORT

A-RELEASE

Figure 13 Sequencing of RWA Request Storage Commitment (asynchronous)

4.2.2.3.4.2. Proposed Presentation Contexts

Each time an association is initiated, the ACP AE proposes one presentation context
to be used on that association. The presentation context proposed by the ACP AE for
Request Storage Commitment is defined in Table 63.

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 41 of 71

Table 63: Proposed Presentation Contexts for Request Storage Commitment

Presentation Context Table

Abstract Syntax Transfer Syntax

Extended
Role
Name Negotiation
Name UID UID List
List
Storage ILE 1.2.840.10008.1.2
Commit Push 1.2.840.10008.1.20.1.1 ELE 1.2.840.10008.1.2.1 SCU None
Model EBE 1.2.840.10008.1.2.2

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, the per SOP Class used transfer
syntax is forced by the SCP.

4.2.2.3.4.3. SOP Specific Conformance for SOP Classes

4.2.2.3.4.3.1. Storage Commitment Operations (N-ACTION)

The behavior of the ACP AE for status codes in the N-ACTION response is
summarized in Table 64.

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

Service Status Further Meaning Error Code Behavior

Success Successful operation 0000 The storage commitment request
has been successfully sent. The
storage commitment request job is
marked as completed. Success is
logged.
* * Any other The association is aborted using A-
status code ABORT. The storage commitment
request job is marked as failed. The
failure is also logged.

The behavior of the ACP AE during communication failure is summarized in Table 65.

Table 65: Storage Commitment Communication Failure Behavior

Exception Behavior
Timeout The association is aborted using A-ABORT and the storage
commitment request job is marked as failed. The examination
remains not completed. The failure reason is logged.
Association aborted The association is aborted using A-ABORT and the storage
commitment request job is marked as failed. The examination
remains not completed. The failure reason is logged.
Association rejected The association is aborted using A-ABORT and the storage
commitment request job is marked as failed. The examination
remains not completed. The failure reason is logged.

4.2.2.3.4.3.2. Storage Commitment Operations (N- EVENT-REPORT)

The behavior of the ACP AE for event types within N-ACTION is presented in Table
66.

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 42 of 71

Table 66: Storage Commitment N-EVENT-REPORT Behavior

Event Type Event Type ID Behavior

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

The behavior of the ACP AE for status codes in the N-EVENT-REPORT response is
summarized in Table 67.

Table 67: Storage Commitment N-EVENT-REPORT Response Status Handling

Behavior

Service Status Further Meaning Error Code Behavior

Success Successful operation 0000 The storage commitment result has
been successfully received. The
SCP has successfully stored the
SOP Instances. The examination is
marked as completed.
* * Any other The association is aborted using A-
status code ABORT. The examination remains
not completed. The failure is also
logged.

4.2.2.3.5. Print Images

4.2.2.3.5.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 the Allura Xper FD20
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 ACP AE and a remote AE to print one film sheet is presented in Figure
14.

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 43 of 71

Print Images Printer

A-ASSOCIATE

N-GET(Printer)

N-CREATE (Basic Film Session)

N-CREATE (Basic Film Box)

N-SET(Basic Grayscale Image Box)

N-ACTION(Basic Film Box)

A-RELEASE

Figure 14 Sequencing of RWA Print Images

The following implementation remarks are important to achieve successful printing:
• Each film sheet is printed in a separate association
• The number of Film Boxes per Film Session is one.
• The number of images per Film Box is one. The images to be printed on one
film are rendered by the ACP AE 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 ACP AE 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.

4.2.2.3.5.2. Proposed Presentation Contexts

Each time an association is initiated, the ACP AE proposes presentation contexts to
be used on that association. The presentation contexts proposed by the ACP AE for
Print Images is defined in Table 68.

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 44 of 71

Table 68: Proposed Presentation Contexts for Print Images

Presentation Context Table

Abstract Syntax Transfer Syntax

Extended
Role
Name Negotiation
Name UID UID List
List
Basic
ILE 1.2.840.10008.1.2
Grayscale Print
1.2.840.10008.5.1.1.9 ELE 1.2.840.10008.1.2.1 SCU None
Mgmt.Meta
EBE 1.2.840.10008.1.2.2
SOP Class
> Basic Film ILE 1.2.840.10008.1.2
Session SOP 1.2.840.10008.5.1.1.1 ELE 1.2.840.10008.1.2.1 SCU None
Class EBE 1.2.840.10008.1.2.2
> Basic Film ILE 1.2.840.10008.1.2
Box SOP 1.2.840.10008.5.1.1.2 ELE 1.2.840.10008.1.2.1 SCU None
Class EBE 1.2.840.10008.1.2.2
> Basic
ILE 1.2.840.10008.1.2
Grayscale
1.2.840.10008.5.1.1.4 ELE 1.2.840.10008.1.2.1 SCU None
Image Box
EBE 1.2.840.10008.1.2.2
SOP Class
ILE 1.2.840.10008.1.2
> Printer SOP
1.2.840.10008.5.1.1.16 ELE 1.2.840.10008.1.2.1 SCU None
Class
EBE 1.2.840.10008.1.2.2

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, the per SOP Class used transfer
syntax is forced by the SCP.

4.2.2.3.5.3. SOP Specific Conformance for SOP Classes

The ACP AE provides standard conformance to the Basic Grayscale Print
Management Meta SOP Class. The applied order of Print Service Elements
(DIMSE’s) is specified in Table 69. 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.
The ACP AE does not do an explicit N-DELETE request on the created instances;
these are deleted implicitly when releasing the association. Overlay, annotation
(showing the values of some major identifying attributes) and shutter information is
processed in the images sent to the printer.

Table 69: The Applied Order of Print Service Elements

Service Element of SOP Class Description

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

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 45 of 71

Table 70 specifies the supported Service Elements, which may be generated by the
Printer at any time during the association.

Table 70: The Applied Seq. of Print Service Elements and its Optional Attributes

Service Element of SOP Class Note

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

An overview of the applied attributes in the applied Service Elements of the supported
SOP Classes is presented in Table 71 up till Table 78.

Table 71: N-GET-RQ Printer Module

Attribute Name Tag Note

Printer Status 2110,0010 Polling is not supported. Applied Value(s):

FAILURE, NORMAL, WARNING
Printer Status Info 2110,0020 Applied Value(s): FILM JAM, RECEIVER FULL,
SUPPLY EMPTY, SUPPLY LOW

Table 72: Modules of the Film Session SOP Class

Information Entity Module Name Usage

Image SOP Common Module Not used

Printer Basic Film Session Presentation Module Used
Basic Film Session Relationship Module Not used

Table 73: N-CREATE-RQ Basic Film Session Presentation Module

Attribute Name Tag Note

Number of Copies 2000,0010 Between 1 and 99.

Print Priority 2000,0020 Applied value(s): HIGH
Medium Type 2000,0030 Applied value(s): BLUE FILM, CLEAR FILM,
PAPER
Film Session Label 2000,0050 Human readable label that identifies the film
session
Film Destination 2000,0040 Applied value(s): MAGAZINE, PROCESSOR

Table 74: N-CREATE Basic Film Box Presentation Module

Attribute Name Tag Note

Image Display Format 2010,0010 The applied value below indicates that one
(large) image is contained in a Film Box.
Applied value(s): CUSTOM\1,STANDARD\1,1
(I is a vendor specific index, i.e. an integer) is
applied if the Standard Image Display Format
does not result in acceptable films. Purpose of
this value is to use the film surface as much as
possible for image printing (and avoid large
margins). This should be agreed per printer
vendor.
Film Orientation 2010,0040 Applied value(s): LANDSCAPE, PORTRAIT

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 46 of 71

Attribute Name Tag Note

Film Size ID 2010,0050 DICOM specifies a number of Defined Terms;

more values are possible and is print
configuration dependent.
Magnification Type 2010,0060 Normally sent out, however sometimes send
out empty
Because some DICOM printers are not able to
handle
(Value NONE for) this attribute. Applied
value(s): NONE
Trim 2010,0140 No
Configuration Information 2010,0150 Contains a vendor specific Lookup-table (LUT);
should be applied by the DICOM printer if LUT
data is present.
Max Density 2010,0130 Maximum density of the 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.

Table 75: N-CREATE-RQ Basic Film Box Relationship Module

Attribute Name Tag Matching key

Referenced Film Session Sequence 2010,0500 Parent Film Session.

> Referenced SOP Class UID 0008,1150 Applied Value(s): 1.2.840.10008.5.1.1.1
> Referenced SOP Instance UID 0008,1155

Table 76: N-ACTION Basic Film Box SOP Class

Attribute Name Tag Note

No attributes present

Table 77: Modules of the Basic Grayscale Image Box SOP Class

Information Entity Module Name Usage

Image SOP Common Module Not used

Printer Image Box Pixel Presentation Module Used

Table 78: N-SET-RQ Image Box Pixel Presentation Module

Attribute Name Tag Note

Image Position 2020,0010 Applied value(s): 1

Polarity 2020,0020 Applied value(s): NORMAL
Preformatted Grayscale Image 2020,0110
Sequence
> Samples per Pixel 0028,0002 Applied value(s): 1
> Photometric Interpretation 0028,0004 Applied value(s): MONOCHROME2
> Rows 0028,0010 Depending on the selected printer type and film
size.
> Columns 0028,0011 Depending on the selected printer type and film
size.
> Bits Allocated 0028,0100 Applied value(s): 16, 8

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 47 of 71

Attribute Name Tag Note

> Bits Stored 0028,0101 Applied value(s): 12, 8

> High Bit 0028,0102 Applied value(s): 11, 7
> Pixel Representation 0028,0103 Applied value(s): 0x0000
> Pixel Data 7FE0, 0010

The behavior of the ACP AE for status codes in an N-GET response is summarized in
Table 79.

Table 79: N-GET Response Status Handling Behavior

Service Status Further Meaning Error Code Behavior

Success Successful operation 0000 The print job continues.
Warning Any warning xxx The print job continues and the
warning is logged.
Error Any error xxx The association is aborted using A-
ABORT and the print job is marked
as failed. The failure reason is
logged.

The behavior of the ACP AE for status codes in an N-CREATE response is

summarized in Table 80.

Table 80: Basic Film Session N-CREATE Response Status Handling Behavior

Service Status Further Meaning Error Code Behavior

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

The behavior of the ACP AE for status codes in an N-CREATE response is

summarized in Table 81.

Table 81: Basic Film Box N-CREATE Response Status Handling Behavior

Service Status Further Meaning Error Code Behavior

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

The behavior of the ACP AE for status codes in an N-SET response is summarized in
Table 82.

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 48 of 71

Table 82: Basic Grayscale Image Box N-SET Response Status Handling
Behavior

Service Status Further Meaning Error Code Behavior

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

The behavior of the ACP AE for status codes in an N-ACTION response is

summarized in Table 83.

Table 83: Basic Film Box N-ACTION Response Status Handling Behavior

Service Status Further Meaning Error Code Behavior

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

The behavior of the ACP AE for status codes in an N-EVENT-REPORT response is

summarized in Table 84.

Table 84: Printer SOP Class - N-EVENT-REPORT Behavior

Attribute Name Tag Note

Printer Status Info 2110,0020 Conditionally sent by the Printer. This status
information will be ignored. However, polling
this status via the
N-GET Service Element is done.

The behavior of the ACP AE during communication failure is presented in Table 85.

Table 85: Printer Communication Failure Behavior

Exception Behavior
Retry time-out The print job fails. The reason is logged and reported to the user.
Any other exception A retry to resubmit the failed sheets is repeated until the error is
solved, the print job is cancelled or the retry time-out is
exceeded.

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 49 of 71

4.2.2.3.6. Get Printer Status

4.2.2.3.6.1. Description and Sequencing of Activities

The operator (in the service mode) can select a DICOM printer (out of choice list of
configured printers) and test its status. A sequence of interactions between the ACP
AE and a remote AE to check the DICOM printer status is presented in Figure 15.

Get Printer Status Printer

A-ASSOCIATE

N-GET

A-RELEASE

Figure 15 Sequencing of RWA Transfer Images

4.2.2.3.6.2. Proposed Presentation Contexts

Each time an association is initiated, the ACP AE proposes presentation contexts to
be used on that association. The presentation contexts proposed by the ACP AE for
Get Printer Status is defined in Table 86.

Table 86: Proposed Presentation Contexts for Transfer Images

Presentation Context Table

Abstract Syntax Transfer Syntax

Extended
Role
Name Negotiation
Name UID UID List
List
Basic
ILE 1.2.840.10008.1.2
Grayscale Print
1.2.840.10008.5.1.1.9 ELE 1.2.840.10008.1.2.1 SCU None
Mgmt.Meta
EBE 1.2.840.10008.1.2.2
SOP Class
ILE 1.2.840.10008.1.2
> Printer SOP
1.2.840.10008.5.1.1.16 ELE 1.2.840.10008.1.2.1 SCU None
Class
EBE 1.2.840.10008.1.2.2

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, the per SOP Class used transfer
syntax is forced by the SCP.

4.2.2.3.6.3. SOP Specific Conformance for SOP Classes

The ACP AE provides standard conformance to the Basic Grayscale Print
Management Meta SOP Class. The behavior of the ACP AE for status codes in an N-
GET response is summarized in Table 87.

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 50 of 71

Table 87: N-GET Response Status Handling Behavior

Service Status Further Meaning Error Code Behavior

Success Successful operation 0000 Success is reported to the user and
is logged.
Warning Any warning xxx Success is reported to the user and
the warning is logged.
Error Any error xxx Failure is reported to the user. The
association is aborted using A-
ABORT and the failure is logged.

The behavior of the ACP AE during communication failure is presented in Table 88.

Table 88: Printer Communication Failure Behavior

Exception Behavior
Retry time-out The print status job fails. The reason is logged and reported to
the user.
Any other exception A retry to resubmit the request for the printer status is repeated
until the error is solved, the request is cancelled or the retry time-
out is exceeded.

4.2.2.3.7. Verify Application Level Communication

4.2.2.3.7.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.

Verify Application
Level Remote AE
Communication

A-ASSOCIATE

C-ECHO

A-RELEASE

Figure 16 Sequencing of RWA Verify Application Level Communication

4.2.2.3.7.2. Proposed Presentation Contexts

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

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 51 of 71

Table 89: Proposed Presentation Contexts for ACP AE Verify Application Level
Communication

Presentation Context Table

Abstract Syntax Transfer Syntax Extended

Role
Negotiation
Name UID Name List UID List
Verification 1.2.840.10008.1.1 ILE 1.2.840.10008.1.2 SCU None
ELE 1.2.840.10008.1.2.1
EBE 1.2.840.10008.1.2.2

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, the per SOP Class used transfer
syntax is forced by the SCP.

4.2.2.3.7.3. SOP Specific Conformance for SOP Classes

The behavior of the ACP AE for status codes in an Verification response is
summarized in Table 90.

Table 90: Verification C-ECHO Response Status Handling Behavior

Service Status Further Meaning Error Code Behavior

Success Successful operation. 0000 The success is reported to the
operator.
* * Any other The failure is reported to the
status code operator.

The behavior of the ACP AE for status codes in an Verification response is

summarized in Table 91.

Table 91: Verification Communication Failure Behavior

Exception Behavior
Timeout The association is aborted using A-ABORT. 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.2.4. Association Acceptance Policy

The ACP AE accepts associations for the following purposes:
• To allow remote applications to store images on the Allura Xper FD20 (see
Section 4.2.2.4.1)
• To allow remote applications to verify application level communication with the
ACP AE
• To receive the Storage Commitment Notification
The ACP AE provides standard conformance to the rejection of an association. The
ACP AE shall reject association requests from unknown applications, i.e. applications
that offer an unknown “calling AE title”. An application is known if – and only if – it is
defined during configuration of the ACP AE. The ACP AE shall reject association
requests from applications that do not address the ACP AE, i.e. applications that offer

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 52 of 71

a wrong “called AE title”. The ACP AE title is defined during configuration of the Allura
Xper FD20.

4.2.2.4.1. Import Images

4.2.2.4.1.1. Description and Sequencing of Activities

The ACP AE shall accept associations from systems that wish to store images in the
Allura Xper FD20 database using the C-STORE command (see Figure 17 ).

Remote AE Import Images

A-ASSOCIATE

C-STORE

A-RELEASE

Figure 17 Sequencing of RWA Import Images

4.2.2.4.1.2. Accepted Presentation Contexts

Table 92: Acceptable Presentation Contexts for Import Images

Presentation Context Table

Abstract Syntax Transfer Syntax Extended

Role
Negotiation
Name UID Name List UID List
Secondary ILE 1.2.840.10008.1.2
Capture ELE 1.2.840.10008.1.2.1
Image 1.2.840.10008.5.1.4.1.1.7 EBE 1.2.840.10008.1.2.2 SCP None
Note
Storage FOP 1.2.840.10008.1.2.4.70
SOP Class
X-Ray ILE 1.2.840.10008.1.2
Angiographi ELE 1.2.840.10008.1.2.1
c Image 1.2.840.10008.5.1.4.1.1.12.1 EBE 1.2.840.10008.1.2.2 SCP None
Note
Storage FOP 1.2.840.10008.1.2.4.70
SOP Class
Note: Lossless, Non-Hierarchical, First-Order Prediction JPEG compression.

The ACP AE accepts all contexts in the intersection of the proposed and acceptable
Presentation Contexts. This means that the ACP AE accepts multiple Proposed
Presentation Contexts with the same SOP Class but different Transfer Syntaxes.
There is no check for duplicate contexts and are therefore accepted.

4.2.2.4.1.3. SOP Specific Conformance for SOP Classes

The ACP AE provides standard conformance to the error handling of image import. All
error messages occur in a C-STORE response. It provides level 2 (full) conformance.

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 53 of 71

The behavior of the ACP AE for status codes in an C-STORE response is

summarized in Table 93.

Table 93: Storage C-STORE Response Status Handling Behavior

Service Status Further Meaning Error Code Behavior

Success Successful operation 0000 The images shall be stored in the
Allura Xper FD20 local database.
Success shall be logged.
Refused Out of Resources A700-A7FF The Allura Xper FD20 local
database is full – recovery from this
condition is left to the SCU. The
ACP AE shall send a notification,
and abort the association. The
failure reason is logged.
Error Data Set does not match SOP A900 SOP class of the image(s) does not
Class match the negotiated abstract
syntax. The ACP AE shall send a
notification and abort the
association. The failure reason is
logged.
Cannot Understand C000 The image(s) cannot be parsed.
The ACP AE shall send a
notification and abort the
association. The failure reason is
logged.
Warning Coercion of Data Elements B000 The association is aborted using A-
ABORT and the send job is marked
as failed. The failure reason is
logged.
Elements discarded B006 The association is aborted using A-
ABORT and the send job is marked
as failed. The failure reason is
logged.
Data set does not match SOP class B007 The association is aborted using A-
ABORT and the send job is marked
as failed. The failure reason is
logged.

4.2.2.4.2. Request Verification

4.2.2.4.2.1. Description and Sequencing of Activities

The ACP AE shall accept associations from systems that wish to verify application
level communication to the Allura Xper FD20 (see Figure 18).

Request
Remote AE
Verification

A-ASSOCIATE

C-ECHO

A-RELEASE

Figure 18 Sequencing of RWA Request Verification

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 54 of 71

4.2.2.4.2.2. Accepted Presentation Contexts

Table 94: Acceptable Presentation Contexts for Request Verification

Presentation Context Table

Abstract Syntax Transfer Syntax Extended

Role
Negotiation
Name UID Name List UID List
Verification 1.2.840.10008.1.1 ILE 1.2.840.10008.1.2
ELE 1.2.840.10008.1.2.1 SCP None
EBE 1.2.840.10008.1.2.2

4.2.2.4.2.3. SOP Specific Conformance for SOP Classes

The ACP AE provides standard conformance to the DICOM Verification Service
Class.
The behavior of the ACP AE for status codes in an Verification response is
summarized in Table 95.

Table 95: Verification C-ECHO Response Status Handling Behavior

Service Status Further Meaning Error Code Behavior

N.A. N.A. N.A. N.A.

The behavior of the ACP AE for status codes in an Verification response is

summarized in Table 96.

Table 96: Verification Communication Failure Behavior

Exception Behavior
Timeout The association is aborted using A-ABORT. 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.3. Network Interfaces

4.3.1. Physical Network Interface

The Allura Xper FD20 provides DICOM V3.0 TCP/IP Network Communication. The
TCP/IP stack is inherited from the .Net Framework/Windows XP operating system.
The Allura Xper FD20 supports a single network interface: Ethernet ISO.8802-3.
Standard AUI, optional twisted pair 10/100-BaseT.

4.3.2. Additional Protocols

None.

4.4. Configuration
The Allura Xper FD20 RIS AE and ACP AE are configured by means of a Service
Application. This Service Application is password protected and intended to be used

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 55 of 71

by Philips Customer Support Service Engineers only. Configuration is stored in a

configuration repository.

4.4.1. AE Title/Presentation Address Mapping

4.4.1.1. Local AE Titles

All local applications use the AE Titles and TCP/IP Ports configured via the Service
Application. Default AE Titles are provided. The local AE title mapping and
configuration are presented in Table 97.

Table 97: AE Title Configuration Table

Application Entity Default AE Title Default TCP/IP Port

RIS AE IBIS_RIS N.A.
ACP AE AE_localnode 5101

4.4.1.2. Remote AE Title/Presentation Address Mapping

All relevant remote applications that should be able to setup a DICOM association
towards Allura Xper FD20 and that should be able to accept a DICOM association
from Allura Xper FD20 must be configured during the Allura Xper FD20 configuration
time.

4.4.2. Parameters
The parameters that apply to each Application Entity are specified in separate
sections specific to each AE (see Table 98).

Table 98: Configuration Parameters table

Parameter Configurable Default Value

RIS AE (Local System)

AE title Yes IBIS_RIS
Port number Yes -
IP host name/address Yes -
Association time out (Time-out waiting for acceptance or Yes 15 seconds
rejection Response to an Association Open Request)
ARTIM time out Yes 30 seconds
Message time out (Time-out waiting for acceptance of a Yes 15 seconds
TCP/IP message over the network)
Maximum PDU size (receiving) Yes 16384
Maximum PDU size (sending) No 16384
RIS AE (Basic Worklist Management)
AE title Yes BWLM_SCP_AE
Port number Yes 104
IP host name/address Yes BWLM-SCP-HN
Time span backwards/forwards (the time span before/after Yes 2880 minutes (48h)
the current time and date for which scheduling information is
needed)
Is a Secure Node Yes No
Encryption On/Off Yes Off
Name of Private key-Certificate pair Yes BWLM-SCP-CN
RIS AE (Modality Performed Procedure Step)
AE title Yes MPPS_SCP_AE
Port number Yes 104

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 56 of 71

Parameter Configurable Default Value

IP host name/address Yes MPPS-SCP-HN
Expiration time (the time after which the message will expire) Yes 10080 minutes (1 week)
Retry time Yes 60 minutes (1h)
Is a Secure Node Yes No
Encryption On/Off Yes Off
Name of Private key-Certificate pair Yes MPPS-SCP-CN
ACP AE (Local System)
AE title Yes AE_localnode
Port number Yes 5101
IP host name/address Yes Localnode
ARTIM time out Yes 60 seconds
Message time out (Time-out waiting for acceptance of a No 60 seconds
TCP/IP message over the network)
Maximum PDU size (receiving) Yes 16384
Maximum PDU size (sending) No 16384
Maximum number of incoming associations Yes 0
Is a Secure Node Yes No
Encryption On/Off Yes Off
Name of Private key-Certificate pair Yes -
ACP AE (Remote Network Node)
AE title Yes Depends on the type of
a configured network
node
Port number Yes 9999
IP host name/address Yes Depends on the type of
a configured network
Human Readable Name Yes Depends on the type of
a configured network
ARTIM time out Yes 60 seconds
Message time out (Time-out waiting for acceptance of a No 3600 seconds for export
TCP/IP message over the network) or import network nodes
300 seconds for storage
commitment or
query/retrieve nodes
Supported transfer syntaxes and preferred order as SCU and Yes Depends on the type of
SCP a configured network
Supported SOP classes as SCU and SCP Yes Depends on the type of
a configured network
Archive/Storage commitment settings Yes No
Automatic conversion settings (e.g., pure, extended DICOM) Yes FULL
Is a Secure Node Yes No
Encryption On/Off Yes Off
Name of Private key-Certificate pair Yes -
ACP AE (Remote DICOM Printer)
AE title Yes Depends on the
configured printer
Port number Yes 9999
IP host name/address Yes Depends on the
configured printer
Human Readable Name Yes Depends on the
configured printer
ARTIM time out Yes 60
Message time out (Time-out waiting for acceptance of a No 3600 seconds
TCP/IP message over the network)
Print medium type Depends on the
configured printer
Gray level transformation Yes STANDARD

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 57 of 71

Parameter Configurable Default Value

Automatic conversion settings (e.g., pure, extended DICOM) Yes FULL

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 58 of 71

5. M EDIA I NTERCHANGE

The Allura Xper FD20 does not support Media Storage.

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 59 of 71

6. S UPPORT OF C HARACTER S ETS

Besides the DICOM default character repertoire, ISO 646 Latin Alphabet (ISO-IR 6),
the following character sets are supported:
• ISO 8859 Western Europe Supplementary Set 1 (ISO-IR 100)
• JIS X 0201 Japanese Katakana and Romaji (ISO-IR 13 and ISO-IR 14) (only
for the patient name)
• JIS X 0208 Japanese Kanji and Hiragana (ISO-IR 87) (only for the patient
name)
• JIS X 0212 Japanese Kanji supplementary set (ISO-IR 159) (only for the
patient name)
The strings in Allura Xper FD20 are represented in UNICODE.
When an unsupported character set is received, the image data shall be rejected.

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 60 of 71

7. S ECURITY

7.1. Association Level Security

The Allura Xper FD20 shall reject association requests from unknown applications, i.e.
applications that offer an unknown “calling AE title”. An application is known if – and
only if – it is defined during configuration of the Allura Xper FD20. The Allura Xper
FD20 shall reject association requests from applications that do not address its ACP
AE, i.e. applications that offer a wrong “called AE title”. The ACP AE title is defined
during configuration of the Allura Xper FD20.

7.2. Application Level Security

The Allura Xper FD20 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 Allura Xper FD20 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.

7.2.1. DICOM Basic TLS Secure Transport Connection Profile

Secure communication is a “mode of operation” of the Allura Xper FD20 supported by
the implementation of the DICOM Basic TLS Secure Transport Connection Profile.
This functionality will be used by the nodes that can authenticate each other before
they exchange DICOM information. For secure communication the TLS protocol v1.0
is used which provides message authentication, integrity, confidentiality, and replay
protection. Confidentiality is optional and can be controlled by the encryption settings.
The Allura Xper FD20 may communicate using the following Cipher Suites:
• TLS_RSA_WITH_NULL_SHA (Node authentication without encryption)
• TLS_RSA_WITH_3DES_SHA (Node authentication with encryption)
The Allura Xper FD20 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)

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 61 of 71

• 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 Allura Xper FD20 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.
Figure 19 presents the message flow of TLS handshake supported by the Allura Xper
FD20.

SCU SCP

client_hello

server_hello

certificate

certificate_request

server_hello_done

certificate

client_key_exchange

certificate_verify

change_cipher_spec

finished

change_cipher_spec

finished

Figure 19 Message flow of TLS handshake

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 62 of 71

7.2.2. Generation of Audit Records

The Allura Xper FD20 can create audit messages according to the IHE Basic Security
Integration Profile [IHE] 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). These messages may contain
information that identifies the patient. The following messages will be created and sent
to a central Audit Record Repository according to the Syslog protocol [SYSLOG]:
• ActorConfig (when security or networking configuration of the Allura Xper
FD20 is modified via the field service functionality)
• ActorStartStop (when the Allura Xper FD20 starts or shuts down)
• Export (when an examination is saved to a file for field service purposes or
printed on a film/paper)
• BeginStoringInstances (when an examination is transferred from the Allura
Xper FD20 to a remote network node)
• DICOMInstancesDeleted (when an examination is deleted and it is not
scheduled, prepared, or imported)
• DICOMInstancesUsed (when an examination is selected for acquisition)
• UserAuthenticated (when the user logs in or logs out)
• SecurityAlert (when an authentication of a secure node during TLS negotiation
[TLS] fails, e.g. Due to an invalid certificate)
If the central Audit Record Repository is not available, the audit trail record will be
stored by the Allura Xper FD20 in a local buffer. Once the central Audit Record
Repository is available again, the content of that buffer will be transferred to the
central Audit Record Repository. The time that is part of the audit message will be the
local time of the Allura Xper FD20. This time will be synchronized with a Time Server.
The Time Server and central Audit Record Repository are elements of the Hospital
infrastructure.

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 63 of 71

8. A NNEXES

8.1. IOD Contents

The details of the applied modules are given in the tables below. The situation that an
attribute is present conditionally/optionally or that an attribute may contain a zero
length value is indicated too. Conditions and Defined/Enumerated Values of DICOM
3.0 are applicable but are not shown in the tables. The specified attributes are present
and filled except for what is specified in the notes.
Several attribute values in the MPPS or Images are either received via Basic Worklist
Management (BWLM) or entered by the user locally. The user locally cannot change
attributes values, which are received via BWLM, as long as a RIS/CIS connection is
established.

8.1.1. Secondary Capture Image Storage SOP Class - C-STORE-RQ

Table 99: Modules of the Secondary Capture Image Storage SOP Class

Information Entity Module Name Usage

Patient Patient Used

Study General Study Used
Patient Study Used
Series General Series Used
Equipment General Equipment Used
SC Equipment Used
Image General Image Used
Image Pixel Used
SC Image Not used
Overlay Plane Not used
Modality LUT Not used
VOI LUT Used
SOP common Used

Table 100: Patient Module

Attribute Name Tag Note
Referenced Patient Sequence 0008,1120
>Referenced SOP Class UID 0008,1150
>Referenced SOP Instance UID 0008,1155
Patient's Name 0010,0010 Patient's full name.
Patient ID 0010,0020
Patient's Birth Date 0010,0030 Birth data of the patient.
Patient's Sex 0010,0040 Sex of the named patient.
Other Patient IDs 0010,1000
Ethnic Group 0010,2160
Patient Comments 0010,4000

Table 101: General Study Module

Attribute Name Tag Note
Study Date 0008,0020
Study Time 0008,0030
Accession Number 0008,0050
Referring Physician's Name 0008,0090 Patient's referring physician.

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 64 of 71

Attribute Name Tag Note

Referenced Study Sequence 0008,1110
>Referenced SOP Class UID 0008,1150
>Referenced SOP Instance UID 0008,1155
Study Instance UID 0020,000D
Study ID 0020,0010

Table 102: Patient Study Module

Attribute Name Tag Note
Patient's Size 0010,1020 Length or size of the Patient, in meters.
Patient's Weight 0010,1030 Weight of the Patient, in kilograms.
Additional Patient History 0010,21B0

Table 103: General Series Module

Attribute Name Tag Note
Series Date 0008,0021
Series Time 0008,0031
Modality 0008,0060
Series Description 0008,103E
Performing Physician's Name 0008,1050 Name of the Physicians administering the
Series.
Operator's Name 0008,1070 Technologist(s) supporting the series.
Referenced Study Component Sequence 0008,1111
>Referenced SOP Class UID 0008,1150
>Referenced SOP Instance UID 0008,1155
Protocol Name 0018,1030
Series Instance UID 0020,000E
Series Number 0020,0011
Laterality 0020,0060
Performed Procedure Step Start Date 0040,0244
Performed Procedure Step Start Time 0040,0245
Performed Procedure Step ID 0040,0253
Performed Procedure Step Description 0040,0254
Request Attributes Sequence 0040,0275
>Scheduled Procedure Step ID 0040,0009
>Requested Procedure ID 0040,1001

Table 104: General Equipment Module

Attribute Name Tag Note
Manufacturer 0008,0070
Institution Name 0008,0080
Station Name 0008,1010
Manufacturer's Model Name 0008,1090 Manufacturers model number of the equipment
that produced the digital images.
Device Serial Number 0018,1000
Software Version(s) 0018,1020

Table 105: SC Image Equipment Module

Attribute Name Tag Note
Conversion Type 0008,0064 Applied Value: WSD

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 65 of 71

Table 106: General Image Module

Attribute Name Tag Note
Content Date 0008,0023
Content Time 0008,0033
Instance Number 0020,0013
Patient Orientation 0020,0020
Lossy Image Compression 0028,2110
Image Type 0008,0008 Applied value(s):
Value 1: DERIVED
Value 2: PRIMARY
Derivation Description 0008,2111

Table 107: Image Pixel Module

Attribute Name Tag Note
Rows 0028,0010
Columns 0028,0011
Pixel Data 7FE0,0010
Samples per Pixel 0028,0002
Photometric Interpretation 0028,0004
Bits Allocated 0028,0100
Bits Stored 0028,0101
High Bit 0028,0102
Pixel Representation 0028,0103

Table 108: Voi Lut Module

Attribute Name Tag Note
Window Center 0028,1050
Window Width 0028,1051

Table 109: SOP Common Module

Attribute Name Tag Note
Specific Character Set 0008,0005
SOP Class UID 0008,0016
SOP Instance UID 0008,0018

8.1.2. X-Ray Angiographic Image Storage SOP Class – C-STORE RQ

Table 110: Modules of the X-Ray Angiographic Image Storage SOP Class

Information Entity Module Name Usage

Patient Patient Used

Study General Study Used
Patient Study Used
Series General Series Used
Equipment General Equipment Used
Image General Image Used
Image Pixel Used
Contrast/bolus Used
Cine Used
Multi-Frame Used
Frame Pointers Not used
Mask Not used

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 66 of 71

Information Entity Module Name Usage

Display Shutter Used

Device Not used
Therapy Not used
X-Ray Image Used
X-Ray Acquisition Used
X-Ray Collimator Not used
X-Ray Table Not used
XA Positioner Used
Overlay Plane Not used
Multi-frame Overlay Not used
Curve Used
Modality LUT Not used
VOI LUT Used
SOP common Used

Table 111: Patient Module

Attribute Name Tag Note
Referenced Patient Sequence 0008,1120
>Referenced SOP Class UID 0008,1150
>Referenced SOP Instance UID 0008,1155
Patient's Name 0010,0010 Patient's full name.
Patient ID 0010,0020
Patient's Birth Date 0010,0030 Birth data of the patient.
Patient's Sex 0010,0040 Sex of the named patient.
Other Patient Ids 0010,1000
Ethnic Group 0010,2160
Patient Comments 0010,4000
The “>” character indicates that the SOP Class is part of the above mentioned Meta SOP Class

Table 112: General Study Module

Attribute Name Tag Note
Study Date 0008,0020
Study Time 0008,0030
Accession Number 0008,0050
Referring Physician's Name 0008,0090 Patient's referring physician.
Referenced Study Sequence 0008,1110
>Referenced SOP Class UID 0008,1150
>Referenced SOP Instance UID 0008,1155
Study Instance UID 0020,000D
Study ID (Note 1) 0020,0010
The “>” character indicates that the SOP Class is part of the above mentioned Meta SOP Class

Note 1: In case the Study ID is empty the accession number will be assigned. In case Study ID and
Accession Number are the same, the Study ID will be left empty.

Table 113: Patient Study Module

Attribute Name Tag Note
Patient's Size 0010,1020 Length or size of the Patient, in meters.
Patient's Weight 0010,1030 Weight of the Patient, in kilograms.
Additional Patient History 0010,21B0

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 67 of 71

Table 114: General Series Module

Attribute Name Tag Note
Series Date 0008,0021
Series Time 0008,0031
Modality 0008,0060
Series Description 0008,103E
Performing Physician's Name 0008,1050 Name of the Physicians administering the
Series.
Operator's Name 0008,1070 Technologist(s) supporting the series.
Referenced Study Component Sequence 0008,1111
>Referenced SOP Class UID 0008,1150
>Referenced SOP Instance UID 0008,1155
Protocol Name 0018,1030
Series Instance UID 0020,000E
Series Number 0020,0011
Laterality 0020,0060
Performed Procedure Step Start Date 0040,0244
Performed Procedure Step Start Time 0040,0245
Performed Procedure Step ID 0040,0253
Performed Procedure Step Description 0040,0254
Request Attributes Sequence 0040,0275
>Scheduled Procedure Step ID 0040,0009
>Requested Procedure ID 0040,1001

Table 115: General Equipment Module

Attribute Name Tag Note
Manufacturer 0008,0070
Institution Name 0008,0080
Station Name 0008,1010
Manufacturer's Model Name 0008,1090 Manufacturers model number of the equipment
that produced the digital images.
Device Serial Number 0018,1000
Software Version(s) 0018,1020

Table 116: General Image Module

Attribute Name Tag Note
Content Date 0008,0023
Content Time 0008,0033
Instance Number 0020,0013
Patient Orientation 0020,0020
Lossy Image Compression 0028,2110
Image Type 0008,0008 Applied value(s):
Value 1: ORIGINAL
Value 2: PRIMARY
Value 3: SINGLE PLANE
Derivation Description 0008,2111

Table 117: Image Pixel Module

Attribute Name Tag Note
Rows 0028,0010
Columns 0028,0011
Samples per Pixel 0028,0002
Photometric Interpretation 0028,0004

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 68 of 71

Attribute Name Tag Note

Bits Allocated 0028,0100
Bits Stored 0028,0101
High Bit 0028,0102
Pixel Representation 0028,0103
Pixel Data 7FE0,0010

Table 118: Contrast/bolus Module

Attribute Name Tag Note
Contrast/Bolus Agent 0018,0010

Table 119: Cine Module

Attribute Name Tag Note
Recommended Display Frame Rate 0008,2144
Cine Rate 0018,0040
Frame Time 0018,1063
Frame Time Vector 0018,1065
Frame Delay 0018,1066

Table 120: Multi-Frame Module

Attribute Name Tag Note
Number of Frames 0028,0008
Frame Increment Pointer 0028,0009 Applied Value(s): 0x00181065 or 0x00181063

Table 121: Display Shutter Module

Attribute Name Tag Note
Shutter Shape 0018,1600 Applied Value(s): RECTANGULAR
Shutter Left Vertical Edge 0018,1602
Shutter Right Vertical Edge 0018,1604
Shutter Upper Horizontal Edge 0018,1606
Shutter Lower Horizontal Edge 0018,1608
Center of Circular Shutter 0018,1610
Radius of Circular Shutter 0018,1612

Table 122: X-ray Image Module

Attribute Name Tag Note
Image Type 0008,0008 Applied Value(s):
ORIGINAL
PRIMARY
SINGLE PLANE
Samples per Pixel 0028,0002 Applied Value(s): 1
Photometric Interpretation 0028,0004 Applied Value(s): MONOCHROME2
Bits Allocated 0028,0100 Applied Value(s): 16, 8
Bits Stored 0028,0101 Applied Value(s): 10, 8
High Bit 0028,0102
Pixel Representation 0028,0103 Applied Value(s): 0x0000
Pixel Intensity Relationship 0028,1040 Applied Value(s): LIN

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 69 of 71

Table 123: X-ray Acquisition Module

Attribute Name Tag Note
KVP 0018,0060
Exposure Time 0018,1150 Only sent if Exposure (0018,1152) is not sent.
X-Ray Tube Current 0018,1151 Only sent if Exposure (0018,1152) is not sent.
Exposure 0018,1152 Only sent if Exposure Time (0018,1150) and X-
Ray Tube Current (0018,1151) are not sent.
Radiation Setting 0018,1155
Distance Source to Entrance 0040,0306
Imager Pixel Spacing 0018,1164

Table 124: XA Positioner Module

Attribute Name Tag Note
Distance Source to Detector 0018,1110
Distance Source to Patient 0018,1111
Positioner Motion 0018,1500 Applied Value(s): DYNAMIC
Positioner Primary Angle 0018,1510
Positioner Secondary Angle 0018,1511
Positioner Primary Angle Increment 0018,1520 An array that contains the Positioner Primary
Angle Increments between the nth frame and
the previous frame for a Multi-frame image.
Positioner Secondary Angle Increment 0018,1521 An array that contains the Positioner
Secondary Angle Increments between the nth
frame and the previous frame for a Multi-frame
image.

Table 125: Curve Module

Attribute Name Tag Note
Curve Dimensions 5000,0005 Applied Value(s): 2
Number of Points 5000,0010
Type of Data 5000,0020
Axis Units 5000,0030
Data Value Representation 50xx,0103 Applied Value(s): “0000H”
Minimum Coordinate Value 5000,0104
Maximum Coordinate Value 5000,0105
Curve Data Descriptor 50xx,0110 Applied Value(s):
For X: “0000H”
For Y: “0001H”
Coordinate Start Value 5000,0112
Coordinate Step Value 5000,0114
Curve Data 5000,3000

Table 126: Voi Lut Module

Attribute Name Tag Note
Window Center 0028,1050
Window Width 0028,1051

Table 127: SOP Common Module

Attribute Name Tag Note
Specific Character Set 0008,0005
SOP Class UID 0008,0016
SOP Instance UID 0008,0018

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 70 of 71

8.1.3. Usage of Attributes from Received IOD’s

No SOP class specific fields are required.

8.1.4. Attribute Mapping

Table 128: Attribute mapping between Modality Worklist, Image IOD and MPPS
IOD
Modality Worklist Image IOD MPPS IOD
Patient Name Patient Name Patient Name
Patient ID Patient ID Patient ID
Other Patient Ids ----
Patient’s Birth Date Patient’s Birth Date Patient’s Birth Date
Patient's Birth Time ----
Patient’s Sex Patient’s Sex Patient’s Sex
Patient's Size ----
Patient’s Weight Patient’s Weight ----
Ethnic Group Ethnic Group ----
Patient Comments Patient Comments ----
Referring Physician’s Name Referring Physician’s Name ----
---- ---- Scheduled Step Attributes
Sequence
Study Instance UID Study Instance UID >Study Instance UID
Referenced Study Sequence Referenced Study Sequence >Referenced Study Sequence
Accession Number Accession Number >Accession Number
---- ---- ----
---- Request Attributes Sequence ----
Requested Procedure ID >Requested Procedure ID >Requested Procedure ID
Requested Procedure Description >Requested Procedure Description
Scheduled Procedure Step ---- ----
Sequence
>Scheduled Procedure Step ID >Scheduled Procedure Step ID >Scheduled Procedure Step ID
>Scheduled Action Item Code >Scheduled Action Item Code
Sequence Sequence
>Scheduled Procedure Step >Scheduled Procedure Step >Scheduled Procedure Step
Description Description Description
Scheduled Protocol Code >Scheduled Protocol Code ----
Sequence Sequence
---- Performed Protocol Code Performed Protocol Code
Sequence Sequence
---- Study ID Study ID
---- Performed Procedure Step ID Performed Procedure Step ID
---- Performed Procedure Step Start Performed Procedure Step Start
Date Date
---- Performed Procedure Step Start Performed Procedure Step Start
Time Time
---- Performed Procedure Step Performed Procedure Step
Description Description
---- ---- Performed Series Sequence
>Scheduled Performing Physician’s Performing Physician’s Name >Performing Physician’s Name
Name
Series Instance UID >Series Instance UID
Requested Procedure Code ---- Procedure Code Sequence
Sequence
---- Protocol Name Protocol Name

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131
 DICOM Conformance Statement Page 71 of 71

8.1.5. Coerced/Modified fields

Allura Xper FD20 re-exports earlier imported images with a new Series Instance UID
and Image SOP Instance UID.

8.2. Data Dictionary of Private Attributes

N.A.

8.3. Coded Terminology and Templates

N.A.

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 SOPs

N.A.

8.6. Private Transfer Syntaxes

None.

 Koninklijke Philips Electronics N.V. 2004

Allura Xper FD20 XDB040-041131