NX Agfa

HE/001261 Page 1 of 87
Document No.001261, Revision 1.2

Livelink NodeID 27014072
Agfa HealthCare 10 November, 2009
AGFA HEALTHCARE
DICOM Conformance Statement
NX 2.0.8000 / 3.0.8000 Workstation
Status: Released
Document No. 001261
Revision 1.2
When printed, this is NOT a controlled copy

HE/001261 Page 2 of 87
Document Information
Service-related contact All service-related contact information http://www.agfa.com/en/he/support/support_service/index.jsp

information worldwide is available on this URL
Issued by: Agfa shall not be liable for errors contained herein or for incidental or
Agfa HealthCare consequential damages in connection with the furnishing, performance
SIV Connectivity or use of this publication. Agfa reserves the right to revise this
publication and to make changes to its content at any time, without
Septestraat 27
obligation to notify any person or entity of such revisions and changes.
B-2640 Mortsel This publication may only be used in connection with the promotion,
Belgium sales, installation and use of Agfa equipment.
Copyright  November, 09
tel: 32 3 444 7588 Agfa HealthCare
email: [email protected] All rights reserved
HE/001261 Page 3 of 87
Conformance Statement Overview
NX 2.0.8000/3.0.8000 implements the necessary DICOM services to facilitate receiving of unprocessed

CR images from an AGFA Digitizer, performing image processing and sending the processed images to
a remote storage or print device over a Medical Imaging Systems network. NX 2.0.8000/3.0.8000 may
also acquire patient information from a Radiology Information System (RIS) for use in identifying
processed images.
The table below provides an overview of the network services supported by NX 2.0.8000/3.0.8000.
Table 1.1-1: Network Services Supported
SOP Classes User of Service (SCU) Provider of Service (SCP)

Transfer
Computed Radiography Image Storage Yes No
Digital X-Ray Image Storage – For Presentation Option No
Digital X-Ray Image Storage – For Processing Option No
Grayscale Softcopy Presentation State Storage SOP Class Yes No
Digital Mammography Image Storage – For Presentation Option No
Digital Mammography Image Storage – For Processing Option No
Workflow Management
Storage Commitment Push Model SOP Class Yes No
Modality Performed Procedure Step SOP Class Option No
Modality Worklist Information Model – FIND Option No
Print Management
Basic Grayscale Print Management Meta SOP Class Yes No
Basic Film Session SOP Class Yes No
Basic Film Box SOP Class Yes No
Basic Grayscale Image Box SOP Class Yes No
Printer SOP Class Yes No
Print Job SOP Class Yes No
Presentation LUT SOP Class Yes No
NX 2.0.8000/3.0.8000 does support Media Services.
Table 1.1-2: Media Services Supported
Media Storage Application Profile Write Files (FSC or FSU) Read Files (FSR)
Compact Disk - Recordable
General Purpose CD-R/DVD Yes No
HE/001261 Page 4 of 87
Table of Contents
1 Introduction ............................................................................................7
1.1 Revision Record ................................................................................................... 7
1.2 Purpose and Intended Audience of this Document ................................................ 7
1.3 General Remarks ................................................................................................. 7
1.3.1 Integration and Validation Activities.................................................................. 7
1.3.2 Future Evolution .............................................................................................. 7
1.4 Acronyms and Abbreviations ................................................................................ 8
1.5 Related Documents .............................................................................................. 8
2 Networking .............................................................................................9
2.1 Implementation Model .......................................................................................... 9
2.1.1 Application Data Flow Diagram........................................................................ 9
2.1.2 Functional Definitions of AE’s .........................................................................10
2.1.2.1 Functional Definition of DICOM Store Application Entity.............................10
2.1.2.2 Functional Definition of DICOM Print Application Entity ..............................10
2.1.2.3 Functional Definition of RIS Application Entity............................................10
2.1.2.3.1 DICOM Modality Worklist ......................................................................10
2.1.2.3.2 DICOM Modality Worklist query on Accession Number .........................10
2.1.2.4 Functional Definition of MPPS Application Entity........................................10
2.1.3 Sequencing of Real World Activities................................................................11
2.2 AE Specifications.................................................................................................12
2.2.1 DICOM Store Application Entity Specification .................................................12
2.2.1.1 SOP Classes Supported ............................................................................12
2.2.1.2 Association Establishment Policies ............................................................12
2.2.1.2.1 General ................................................................................................12
2.2.1.2.2 Number of Associations ........................................................................12
2.2.1.2.3 Asynchronous Nature ...........................................................................13
2.2.1.2.4 Implementation Identifying Information..................................................13
2.2.1.3 Association Initiation Policies .....................................................................13
2.2.1.3.1 Activity – Send Images .........................................................................13
2.2.1.3.1.1 Description and Sequencing of Activity.............................................13
2.2.1.3.1.2 Proposed Presentation Contexts......................................................16
2.2.1.3.1.3 SOP Specific Conformance..............................................................17
2.2.1.4 Association Acceptance Policies................................................................28
2.2.1.4.1 Receive Storage Commitment Response..............................................28
2.2.1.4.1.2 Accepted Presentation Contexts ......................................................28
2.2.1.4.1.3 SOP Specific Conformance – Storage Commitment SOP Class
(1.2.840.10008.1.20.1) .......................................................................................................29
2.2.1.4.1.4 SOP Specific Conformance – Verification SOP Class
(1.2.840.10008.1.1) 30
2.2.2 DICOM Print Application Entity Specification...................................................31
2.2.2.2.1 General ................................................................................................31
2.2.2.3.1 Activity – Print Images ..........................................................................32
HE/001261 Page 5 of 87

2.2.2.3.1.3 SOP Specific Conformance - Basic Grayscale Print Management
Meta SOP Class 34
2.2.2.3.1.4 SOP Specific Conformance Print Job SOP Class
(1.2.840.10008.5.1.1.14) ....................................................................................................39
2.2.2.3.1.5 SOP Specific Conformance Presentation LUT SOP Class
(1.2.840.10008.5.1.1.23) ....................................................................................................41
2.2.2.3.1.6 SOP Specific Conformance Verification SOP Class
(1.2.840.10008.1.1) 41
2.2.3 RIS Application Entity Specification.................................................................42
2.2.3.2.1 General ................................................................................................42
2.2.3.3.1 Activity – Query RIS..............................................................................43
2.2.3.3.1.3 SOP Specific Conformance – Modality Worklist SOP Class
(1.2.840.10008.5.1.4.31) ....................................................................................................43
2.2.3.4 User defined fields.....................................................................................47
2.2.4 MPPS Application Entity Specification ............................................................48
2.2.4.2.1 General ................................................................................................48
2.2.4.3.1 Activity – Acquire Images......................................................................49
2.2.4.3.1.3 SOP Specific Conformance – MPPS (1.2.840.10008.3.1.2.3.3)........50
2.3 Network Interfaces...............................................................................................54
2.3.1 Physical Medium Support ...............................................................................54
2.3.2 Additional Protocols........................................................................................54
2.4 Configuration.......................................................................................................55
2.4.1 AE Title/ Presentation Address Mapping .........................................................55
2.4.1.1 Local AE Titles ..........................................................................................55
2.4.1.2 Remote AE Title/ Presentation Address Mapping .......................................55
2.4.1.2.1 Storage.................................................................................................55
2.4.1.2.1.1 Archive options ................................................................................55
2.4.1.2.2 RIS.......................................................................................................58
2.4.1.2.2.1 Configuration of a RIS......................................................................58
2.4.1.2.2.2 Configuration of RIS Mapping ..........................................................59
2.4.1.2.3 MPPS...................................................................................................59
2.4.1.2.4 Printing.................................................................................................59
2.4.1.3 Queue Management & Job description ......................................................60
2.4.1.4 DICOM Store AE .......................................................................................60
2.4.1.4.1 Queue description.................................................................................60
2.4.1.4.2 Job description .....................................................................................60
2.4.1.5 DICOM Print AE ........................................................................................60
2.4.2 Parameters.....................................................................................................61
HE/001261 Page 6 of 87
3 Media Interchange................................................................................63
3.1 Implementation Model .........................................................................................63
3.1.2 Functional Definition of AEs............................................................................63
3.1.3 Sequencing of Real World Activities................................................................63
3.1.4 File Meta Information for Implementation Class and Version ...........................63
3.2 AE Specifications.................................................................................................64
3.2.1 Offline-Media Application Entity Specification..................................................64
3.2.1.1 Real World Activities..................................................................................64
3.2.1.1.1 Real World Activity - Export to CD-R.....................................................64
3.2.1.1.1.1 Media Storage Application Profile ....................................................65
3.3 Media Configuration ............................................................................................66
4 Support for Extended Character Sets...................................................67
5 Security ................................................................................................68
5.1 Security Profiles ..................................................................................................68
5.2 Association Level Security ...................................................................................68
5.3 Application Level Security....................................................................................68
6 Annexes ...............................................................................................69
6.1 IOD Contents.......................................................................................................69
6.1.1 Created SOP Instances ..................................................................................69
6.1.1.1 Common Modules .....................................................................................69
6.1.1.2 CR.............................................................................................................74
6.1.1.2.1 CR Image IOD......................................................................................74
6.1.1.2.2 CR Modules..........................................................................................74
6.1.1.3 DX.............................................................................................................75
6.1.1.3.1 DX Image IOD ......................................................................................75
6.1.1.3.2 DX Modules..........................................................................................76
6.1.1.4 MG ............................................................................................................80
6.1.1.4.1 MG Image IOD .....................................................................................80
6.1.1.4.2 MG Modules .........................................................................................81
6.1.1.5 GSPS........................................................................................................82
6.1.1.5.1 GSPS IOD............................................................................................82
6.1.1.5.2 GSPS Modules.....................................................................................82
6.2 Attribute Mapping ................................................................................................85
6.3 Grayscale Image Consistency .............................................................................86
6.4 Veterinary Extensions..........................................................................................87
HE/001261 Page 7 of 87
1 INTRODUCTION
1.1 Revision Record
Dicom Conformance Statement NX 2.0.8000 / 3.0.8000

Revision
Date Reason for Change
Number
1.0 2008-05-22 Initial version NX x.0.8000
1.1 2009-06-29 Table 6.1-7 ; 6.1-8 ; 6.1-9 : update attributes and modules
1.2 2009-10-22 Correct Veterinary Breed Registration Sequence tag and Detector
Primary (and Secondary) Angle tag
1.2 Purpose and Intended Audience of this Document
This document is a DICOM Conformance Statement for the DICOM Services of the NX
2.0.8000/3.0.8000 product. It is written according to part PS 3.2 of Digital Imaging and
Communications in Medicine (DICOM) 3.0, NEMA PS 3.1-3.16, 2008.
The user of this document is involved with system integration and/or software design. We
assume that the reader is familiar with the terminology and concepts that are used in the
DICOM 3.0 standard and the IHE Technical Framework.
Readers not familiar with DICOM 3.0 terminology should first read the appropriate parts of
the DICOM standard itself, prior to reading this conformance statement.
Although the use of this conformance statement in conjunction with the DICOM 3.0 standard
is intended to facilitate communication with Agfa ADC imaging equipment, it is not sufficient
to guarantee, by itself, the inter-operation of the connection.
1.3 General Remarks
1.3.1 Integration and Validation Activities
The integration of any device into a system of interconnected devices goes beyond the
scope of the DICOM 3.0 standard and this conformance statement when interoperability is
desired. The responsibility for analyzing the applications requirements and developing a
solution that integrates the Agfa equipment with other vendors’ systems is the user’s
responsibility and should not be underestimated.
In some circumstances it might be necessary to perform a validation to make sure that
functional interoperability between the Agfa equipment and non-Agfa devices works as
expected. The user should ensure that any non-Agfa provider accepts responsibility for any
validation required for their connection with the Agfa equipment.
1.3.2 Future Evolution
As the DICOM 3.0 standard evolves to meet the user’s growing requirements and to
incorporate new features and technologies, Agfa will follow the evolution of the standard.
This evolution of the standard may require changes to devices that have implemented
DICOM 3.0. The user should ensure that any non-Agfa provider, who connects with Agfa
HE/001261 Page 8 of 87
devices, also plans for future evolution of the DICOM standard. A refusal to do so may result
in the loss of functionality and/or connectivity between the different products.
1.4 Acronyms and Abbreviations
Definitions, terms and abbreviations used in this document are defined within the different
parts of the DICOM standard. Abbreviations and terms are as follows:
AE DICOM Application Entity
AET Application Entity Title
ACSE Association Control Service Element
CD-R Compact Disk Recordable
DICOM Digital Imaging and Communications in Medicine
FSC File-Set Creator
FSU File-Set Updater
FSR File-Set Reader
GSDF Grayscale Standard Display Function
GSPS Grayscale Softcopy Presentation State
IE Information Entity
IOD (DICOM) Information Object Definition
ISO International Standard Organization
LUT Lookup Table
MPPS Modality Performed Procedure Step
MSPS Modality Scheduled Procedure Step
PDU DICOM Protocol Data Unit
SCU DICOM Service Class User (DICOM client)
SCP DICOM Service Class Provider (DICOM server)
SOP DICOM Service-Object Pair
UID Unique Identifier
VR Value Representation
1.5 Related Documents

 ACR-NEMA Digital Imaging and Communications in Medicine (DICOM) V3.0.2008.
 IHE Radiology Technical Framework Revision 6 – Final Text, May 2005
HE/001261 Page 9 of 87
2 NETWORKING
2.1 Implementation Model
2.1.1 Application Data Flow Diagram
local remote
Remote
Request to send DICOM Store Application Entity
images & GSPS Application Entity Receives Images
& GSPS
Remote
Request to Print DICOM Print Application Entity
film sheets Application Entity Prints Film
Sheets
Query RIS Remote

RIS Application Entity
Application Entity Provides Worklist
Items
Query RIS by
AccessionNumber
Archive Images
Remote
MPPS Application Entity
Application Entity Receives MPPS
Print Images Create / Update
Acquire Images
DICOM Standard
Interface
Figure 2.1-1: Functional Overview – Application Data Flow

HE/001261 Page 10 of 87
2.1.2 Functional Definitions of AE’s
2.1.2.1 Functional Definition of DICOM Store Application Entity

The DICOM Store Application Entity sends images and Presentation States to a remote AE
(this can be a configured Archiving station, a diagnostic workstation …). It is associated with
the local real-world activity “Send Images & GSPS”. If Storage Commitment is configured for
the archive destination, the DICOM Store AE will request Storage Commitment and a job will
only be marked as successful when the commitment is successfully obtained. An image that
has been successfully sent to an archive cannot be sent to that archive again.
2.1.2.2 Functional Definition of DICOM Print Application Entity

The DICOM Print Application Entity prints images on a remote AE (a configured Printer). It is
associated with the local real-world activity “Request to print film sheets”. A job will only be
marked as “successful” when the sheet is successfully printed.
2.1.2.3 Functional Definition of RIS Application Entity

The RIS Application Entity receives Worklist information from a remote AE. It is associated
with the local real-world activity “Query RIS”. This can be triggered manually by clicking the
“Query RIS” button or triggered automatically at a specified interval. When properly
configured, the RIS can also be queried by Accession Number.
The RIS query can be configured in different ways (for the possible configurations, see §
2.4.1.2.2.1). The two that are relevant for DICOM are described in the following paragraphs:
2.1.2.3.1 DICOM Modality Worklist

The use of DICOM Modality Worklist (DMWL) queries the RIS by means of query keys. The
query keys can be changed by the user in the configuration tool (see § 2.4.1.2.2.1). Based
on these keys, the worklist will be populated during the next RIS query.
2.1.2.3.2 DICOM Modality Worklist query on Accession Number

By querying by Accession Number, only the worklist items that contain the specified
Accession Number are returned. These results are parsed, mapped and shown as a
Worklist.
2.1.2.4 Functional Definition of MPPS Application Entity

The MPPS Application Entity sends MPPS information to a remote AE when MPPS
reporting is configured. The local real-world activities “Acquire Images”, “Archive Images”
and “Print Images” can trigger the creation of an MPPS instance. This can also be done by
adding a new SOP Instance UID to an MPPS, by adding a Dose to an MPPS or by adding a
Print Sheet to an MPPS. The local real-world activity “Close Session” or the modification of
the session’s Accession Number will complete the MPPS. This happens completely
automatically and no user intervention is possible.
HE/001261 Page 11 of 87
2.1.3 Sequencing of Real World Activities
Store Print MPPS RIS RIS MPPS Printer PACS
1. Query RIS (by

AccessionNumber)
2. Receive Worklist
3. Select Workitem (SPS)
4. Create MPPS
(when first image acquired)
5. Acquire Images
6. Print Acquired Images
7. Store Acquired Images

8. Commit Acquired Images
9. Complete MPPS
Figure 2.1-2: sequencing constraints
Under normal scheduled workflow conditions the sequencing constraints illustrated in Figure
2.1-2 apply:
1. Query RIS
2. Receive Worklist
3. Select Workitem
4. Create MPPS
5. Acquire Images
6. Print Acquired Images
7. Store Acquired Images (+ GSPS)
8. Commit Acquired Images
9. Finalize MPPS
HE/001261 Page 12 of 87
2.2 AE Specifications
2.2.1 DICOM Store Application Entity Specification
2.2.1.1 SOP Classes Supported

This Application Entity provides Standard Conformance to the following SOP Class(es):
Table 2.2-1: SOP Class(es) for the DICOM Store Application Entity
SOP Class Name SOP Class UID SCU SCP

Computed Radiography Image Storage 1.2.840.10008.5.1.4.1.1.1 Yes No
Digital X-ray Image Storage – for presentation 1.2.840.10008.5.1.4.1.1.1.1 Yes No
Digital X-ray Image Storage – for processing 1.2.840.10008.5.1.4.1.1.1.1.1 Yes No
Digital Mammography Image Storage – For Presentation 1.2.840.10008.5.1.4.1.1.1.2 Yes No
Digital Mammography Image Storage – For Processing 1.2.840.10008.5.1.4.1.1.1.2.1 Yes No
Grayscale Softcopy Presentation State Storage SOP Class 1.2.840.10008.5.1.4.1.1.11.1 Yes No
Storage Commitment Push Model SOP Class 1.2.840.10008.1.20.1 Yes No
Verification SOP Class 1.2.840.10008.1.1 Yes Yes
2.2.1.2 Association Establishment Policies
2.2.1.2.1 General
The DICOM standard Application context is always proposed:
Table 2.2-2: DICOM Application Context
Application Context Name 1.2.840.10008.3.1.1.1
2.2.1.2.2 Number of Associations

NX 2.0.8000/3.0.8000 initiates one association at a time for each destination to which a
transfer request is being processed in the active job queue list. Only one job per destination
will be active at a time, the other remains pending until the active job for that destination is
completed or failed. There can however be several simultaneous associations to different
destinations.
Table 2.2-3: Number of Associations as an Association Initiator for DICOM Store AE
1 per destination
Maximum number of simultaneous associations initiated
(32 max)
Table 2.2-4: Number of Associations as an Association Acceptor for DICOM Store AE
1 for storage
Maximum number of simultaneous associations accepted
commit response
HE/001261 Page 13 of 87
2.2.1.2.3 Asynchronous Nature

Table 2.2-5: Asynchronous Nature as an Association Initiator for DICOM Store AE
Maximum number of outstanding asynchronous transactions 1

The DICOM Store AE allows a single outstanding operation on any association. Therefore,
it does not support asynchronous operations window negotiation, other than the default as
specified by the DICOM specification.
2.2.1.2.4 Implementation Identifying Information

Table 2.2-6: DICOM implementation Class and Version for DICOM Store AE
Implementation Class UID 1.3.51.0.1.3
Implementation Version Name AGFA DTF1.0.XX 1
2.2.1.3 Association Initiation Policies
2.2.1.3.1 Activity – Send Images
2.2.1.3.1.1 Description and Sequencing of Activity

A user can select an image and request it to be sent to a destination. The request is
forwarded to the job queue and then processed. An image can also be sent automatically
when closing an exam.
Note:
An image can only be sent to an archiving destination if it hasn’t been archived there yet.
The DICOM Store AE is then invoked by the queue that is responsible for processing
network archival tasks for a specific destination. The DICOM Store AE will attempt to initiate
a new Association in order to issue a C-STORE request. If the job contains multiple images,
then multiple C-STORE requests will be issued over the same Association. The association
will be closed when the last image (or GSPS) is sent.
If the association cannot be opened, the job is set to a retry state. If after a configurable
number of retries the job still fails, it is set to an error state (“Failed”). It can then be restarted
by the user through the job control interface. If three successive jobs to a same destination
fail, the queue for that destination will be stalled. It will retry to process the job three (3) more
times. If this fails, the queue for that destination will be stalled for a longer time, meaning that
it will only retry jobs to that destination every five (5) minutes.
When the association was rejected by the device due to a configuration issue, the queue for
that device will be stalled when three (3) successive jobs experience a device failure.
If the Remote AE is configured to support Storage Commit, the DICOM Store AE will send a
Storage Commit request (N-ACTION) over a new association and will then wait for an N-
EVENT-REPORT. If the N-EVENT-REPORT does not arrive within the waiting period, the
AE closes the association and assumes that a separate association will be set up for the N-
1
XX is the build version number.
HE/001261 Page 14 of 87
EVENT-REPORT. If this report does not arrive within a (configurable) amount of time, the
job will be marked as FAILED.
NX 2.0.8000/3.0.8000 does not foresee additional logic when the system is shut down,
regarding storage commitment time outs. In other words: when a storage commit reply does
not reach NX 2.0.8000/3.0.8000 successfully, because NX 2.0.8000/3.0.8000 was/is down
at that point in time, the job will time out and go to FAILED.
A possible sequence of iterations between the DICOM Store AE and an Image Manager is
illustrated in Figure 2.2-1.
Store PACS
1. Open Association
2. C-STORE (CR Image)
3. C-STORE (GSPS)
4. C-STORE (CR Image)
5. C-STORE (GSPS)
6. Close Association
7. Open Association
6. N-ACTION (Storage Commit Rq)
7. N-EVENT-REPORT (Storage Commit Resp)
Figure 2.2-1: Example of a Storage AE Sequencing Diagram (with Storage Commit)

HE/001261 Page 15 of 87
The DICOM Store AE may reject the association attempts as shown in the table below:
Table 2.2-7: Association Reject Reasons
Result Response Reason/Diag

The Dicom library refuses the association SCU Device not known
The Dicom library refuses the association Maximum number of association processing
threads exceeded
The Dicom library refuses the association A799 Dicom Library is not allowed to accept C-
STORE commands from this device and
therefore refuses the association.
The Dicom library refuses the association A0102 SOP Class is not found back in the
configuration
The Dicom library refuses the association A702 The Dicom library is unable to create the
Dicom media file due to the fact that the disk
is full
The Dicom library refuses the association A703 The Dicom library is unable to create the
Dicom media file due to resource problems
other than ‘disk is full’.
The Dicom library refuses the association A703 The Dicom library is unable to acquire the
complete C-STORE request due to network
problems.
The Dicom library refuses the association A701 The Dicom library is unable to acquire the
complete C-STORE request due to network
problems (time-out while reading data from
2
socket) .
2
The time-out value is hard-coded in the Dicom library as being 60 seconds.
HE/001261 Page 16 of 87
2.2.1.3.1.2 Proposed Presentation Contexts
The DICOM Store AE is capable of proposing the Presentation Contexts shown in the
following table:
Table 2.2-8: Presentation Contexts Proposed by DICOM Store AE

Presentation Context Table
Abstract Syntax Transfer Syntax Role Extended
Name UID Name List UID List Negotiation
CR Image 1.2.840.10008. JPEG LLNH1 Encoded 1.2.840.10008.1.2.4.57 SCU None

Storage 5.1.4.1.1.1 (i.e. lossless)
JPEG LLNHF Encoded 1.2.840.10008.1.2.4.70
(i.e. lossless)
JPEG Lossy 8 bit 1.2.840.10008.1.2.4. 50
JPEG Lossy 12 bit 1.2.840.10008.1.2.4.51
Implicit VR Little Endian 1.2.840.10008.1.2
Explicit VR Little Endian 1.2.840.10008.1.2.1
Digital X-ray 1.2.840.10008. JPEG LLNH1 Encoded 1.2.840.10008.1.2.4.57 SCU None
Image Storage – 5.1.4.1.1.1.1 (i.e. lossless)
For Presentation JPEG LLNHF Encoded 1.2.840.10008.1.2.4.70
(i.e. lossless)
JPEG Lossy 8 bit 1.2.840.10008.1.2.4.50
JPEG Lossy 12 bit 1.2.840.10008.1.2.4.51
Implicit VR Little Endian 1.2.840.10008.1.2.1
Explicit VR Little Endian
Digital X-ray 1.2.840.10008. JPEG LLNH1 Encoded 1.2.840.10008.1.2.4.57 SCU None
Image Storage – 5.1.4.1.1.1.1.1 (i.e. lossless)
For Processing JPEG LLNHF Encoded 1.2.840.10008.1.2.4.70
(i.e. lossless)
JPEG Lossy 8 bit 1.2.840.10008.1.2.4.50
JPEG Lossy 12 bit 1.2.840.10008.1.2.4.51
Digital 1.2.840.10008. JPEG LLNH1 Encoded 1.2.840.10008.1.2.4.57 SCU None
Mammography 5.1.4.1.1.1.2 (i.e. lossless)
Image Storage – JPEG LLNHF Encoded 1.2.840.10008.1.2.4.70
For Presentation (i.e. lossless)
JPEG Lossy 8 bit 1.2.840.10008.1.2.4.50
JPEG Lossy 12 bit 1.2.840.10008.1.2.4.51
Digital 1.2.840.10008. JPEG LLNH1 Encoded 1.2.840.10008.1.2.4.57 SCU None
Mammography 5.1.4.1.1.1.2.1 (i.e. lossless)
Image Storage – JPEG LLNHF Encoded 1.2.840.10008.1.2.4.70
For Processing (i.e. lossless)
JPEG Lossy 8 bit 1.2.840.10008.1.2.4. 50
JPEG Lossy 12 bit 1.2.840.10008.1.2.4.51
HE/001261 Page 17 of 87

Abstract Syntax Transfer Syntax Role Extended
Grayscale 1.2.840.10008. Implicit VR Little Endian 1.2.840.10008.1.2 SCU None

Softcopy 5.1.4.1.1.11.1 Explicit VR Little Endian 1.2.840.10008.1.2.1
Presentation
State Storage
SOP Class
Storage 1.2.840.10008. Implicit VR Little Endian 1.2.840.10008.1.2 SCU None
Commitment 1.20.1
Push Model SOP
Class
Verification SOP 1.2.840.10008. Implicit VR Little Endian 1.2.840.10008.1.2 SCU None
Class 1.1
Depending on the configuration of NX 2.0.8000/3.0.8000, either the CR Image Storage, the

Digital X-ray Image Storage – For Processing or the Digital X-ray Image Storage – For
Presentation, the Digital Mammography Image Storage – For Presentation or the Digital
Mammography Image Storage – For Processing will be proposed.
The Grayscale Softcopy Presentation State Storage SOP Class and the Storage
Commitment Push Model SOP Class will only be proposed if configured.
2.2.1.3.1.3 SOP Specific Conformance
2.2.1.3.1.3.1 Image & Presentation State Storage
2.2.1.3.1.3.1.1 Computed Radiography Image Storage SOP Class

(1.2.840.10008.5.1.4.1.1.1)
The Computed Radiography Image Storage SOP class is a Storage Standard SOP Class
that uses the CR IOD (§ 6.1.1.2.1).
2.2.1.3.1.3.1.2 Digital X-ray Image Storage – For Presentation SOP Class

(1.2.840.10008.5.1.4.1.1.1.1)
The Digital X-Ray Image Storage - For Presentation SOP Class uses the DX IOD
(§6.1.1.3.1) with an Enumerated Value of FOR PRESENTATION for Presentation Intent
Type (0008, 0068).
2.2.1.3.1.3.1.3 Digital X-ray Image Storage – For Processing SOP Class

(1.2.840.10008.5.1.4.1.1.1.1)
The Digital X-Ray Image Storage - For Processing SOP Class uses the DX IOD (§6.1.1.3.1)
with an Enumerated Value of FOR PROCESSING for Presentation Intent Type (0008,
0068).
As a SCU of the Digital X-Ray Image Storage - For Processing SOP Class, it also supports
the Digital X-Ray Image Storage - For Presentation SOP Class.
2.2.1.3.1.3.1.4 Digital Mammography Image Storage – For Presentation SOP Class

(1.2.840.10008.5.1.4.1.1.1.2)
The Digital Mammography Image Storage - For Presentation SOP Class uses the MG IOD
(§6.1.1.4.1) with an Enumerated Value of FOR PRESENTATION for Presentation Intent
Type (0008, 0068).
HE/001261 Page 18 of 87
2.2.1.3.1.3.1.5 Digital Mammography Image Storage – For Processing SOP Class

(1.2.840.10008.5.1.4.1.1.1.2.1)
The Digital Mammography Image Storage - For Processing SOP Class uses the MG IOD
(§6.1.1.4.1) with an Enumerated Value of FOR PROCESSING for Presentation Intent Type
(0008, 0068).
2.2.1.3.1.3.1.6 Grayscale Softcopy Presentation State Storage SOP Class

(1.2.840.10008.5.1.4.1.1.11.1)
The Grayscale Softcopy Presentation State Storage SOP Class extends the functionality of
the Storage Service class to add the ability to convey an intended presentation state or
record an existing presentation state.
It includes capabilities for specifying:

 the output grayscale space in P-Values
 grayscale contrast transformations including modality and VOI LUT
 selection of the area of the image to display
 image and display relative annotations, including graphics, text and overlays
Note:
A GSPS always refers to exactly one (1) image. Since re-sending an image is prohibited
in NX 2.0.8000/3.0.8000, an archived image can also have maximally one (1) GSPS that
refers to it.
Depending on the configured SOP class to be used (CR (§ 2.2.1.3.1.3.1.1), DX for

presentation (§2.2.1.3.1.3.1.2) or MG for presentation (§ 2.2.1.3.1.3.1.4) annotations and
shutters are stored in the GSPS or burned in the image as described in the following table:
Table 2.2-9: Use of GSPS vs. Burning in the image
CR
DX for presentation DX for processing
MG for presentation
Image Processed pixels
(processing,W/L,collimation) + RAW pixels
LUTs
Annotations GSPS or Burned in
Shutters GSPS or
when GSPS is not used:
In case of CR the shutter is
burned into the Pixel data.
In case of DX and MG the Ignored
shutter is described in the
shutter module of the image
header.
Zoom GSPS or discarded
Markers Always burned in
The following paragraphs describe into detail how each annotation is embedded in the GSPS:
HE/001261 Page 19 of 87
2.2.1.3.1.3.1.6.1 Text
Graphic Layer Module

(0070,0060) Graphic Layer Sequence
(0070,0002) >Graphic Layer ID123
(0070,0068) >Graphic Layer Description Text
Graphic Annotation Module

(0070,0001) Graphic Annotation Sequence
(0070,0002) > Graphic Layer ID123
(0070,0008) > Text Object Sequence
(0070,0003) >> Bounding box annotation units PIXEL
(0070,0004) >> Anchor Point Annotation Units -
(0070,0006) >> Unformatted Text Value [value]
(0070,0010) >> Bounding Box Top Left Hand Corner [value]
(0070,0011) >> Bounding Box Top Right Hand Corner [value]
(0070,0012) >> Bounding Box Text Horizontal Justification LEFT
(0070,0014) >> Anchor Point -
(0070,0015) >> Anchor Point Visibility -
2.2.1.3.1.3.1.6.2 Arrow
A text is foreseen for each arrow, but it may be an empty string. The arrow consists of two polylines.

(0070,0002) >Graphic Layer ID
(0070,0068) >Graphic Layer Description Arrow

(0070,0002) > Graphic Layer [ID of the corresponding layer]
(0070,0004) >> Anchor Point Annotation Units PIXEL
(0070,0014) >> Anchor Point [value of arrow point]
(0070,0015) >> Anchor Point Visibility N
(0070,0009) > Graphic Object Sequence
Arrow line
(0070,0005) >> Graphic Annotation Units PIXEL
(0070,0020) >> Graphic Dimensions 2
(0070,0021) >> Number of Graphic Points 2
(0070,0022) >> Graphic Data [values]
(0070,0023) >> Graphic Type POLYLINE
(0070,0024) >> Graphic Filled -
Arrow point
HE/001261 Page 20 of 87
2.2.1.3.1.3.1.6.3 Rectangle
A rectangle is always provided with a corresponding text (for measurements). If the text is moved by
the operator, an extra text object is added to the GSPS.

(0070,0068) >Graphic Layer Description Rectangle or Rectangle_SAL

(0070,0014) >> Anchor Point -
(0070,0024) >> Graphic Filled N
2.2.1.3.1.3.1.6.4 Circle
A circle is always provided with a corresponding text (for measurements). If the text is moved by the
operator, an extra text object is added to the GSPS.

(0070,0068) >Graphic Layer Description Circle

(0070,0014) >> Anchor Point -
(0070,0023) >> Graphic Type CIRCLE
HE/001261 Page 21 of 87
2.2.1.3.1.3.1.6.5 Polygon
A polygon is always provided with a corresponding text (for measurements). If the text is moved by
the operator, an extra text object is added to the GSPS.

(0070,0068) >Graphic Layer Description Polygon

(0070,0014) >> Anchor Point -
(0070,0021) >> Number of Graphic Points [value]
2.2.1.3.1.3.1.6.6 Freehand

(0070,0068) >Graphic Layer Description Freehand

(0070,0014) >> Anchor Point -
(0070,0021) >> Number of Graphic Points [value]
(0070,0023) >> Graphic Type INTERPOLATED
HE/001261 Page 22 of 87
2.2.1.3.1.3.1.6.7 Line
A line consists of two parts: the actual line, and a small line indicating the middle point of the line:

(0070,0068) >Graphic Layer Description Line

Item for the actual line
Item for the indication of the middle
2.2.1.3.1.3.1.6.8 Perpendicular
A perpendicular also consists of two lines A and B, as illustrated in the example below:

(0070,0068) >Graphic Layer Description Perpendicular

Item for the first line (A)
HE/001261 Page 23 of 87

Item for the second line (B)
2.2.1.3.1.3.1.6.9 Calibration ruler

The calibration ruler is displayed at the side of the image and is the result of a calibration action of
the operator.
It consists out of a ruler (constructed using several lines) and some text.

(0070,0068) >Graphic Layer Description Calibration Ruler

(0070,0014) >> Anchor Point -
First ruler line
(0070,0023) >> Graphic Type CIRCLE
…
2.2.1.3.1.3.1.6.10 Angle
An angle measurement is a combination of 2 lines and 2 short lines, with 2 angle texts.
HE/001261 Page 24 of 87

(0070,0068) >Graphic Layer Description Angle

(0070,0008) > Text Object Sequence -> 2 texts for the degrees
(0070,0009) > Graphic Object Sequence Long line 1
Long line 2
Small middle line 1
Small middle line 2
2.2.1.3.1.3.1.6.11 Distance
A distance is composed of a line with a text value.
(0070,0068) >Graphic Layer Description Distance

(0070,0008) > Text Object Sequence -> used for the distance text
Item for the actual line
Items for the ruler (cfr. Calibration ruler)
HE/001261 Page 25 of 87
2.2.1.3.1.3.1.6.12 Leg Length Difference

(0070,0068) >Graphic Layer Description Leg Length Difference

(0070,0008) > Text Object Sequence Measurement text
(0070,0009) > Graphic Object Sequence First horizontal line
Second horizontal line
Vertical line
Arrow point 1
Arrow point 2
Arrow line
2.2.1.3.1.3.1.6.13 Scoliosis
er Line
Upp
23
Lo
we
r li
ne

(0070,0068) >Graphic Layer Description Scoliosis Measurement
HE/001261 Page 26 of 87

(0070,0008) > Text Object Sequence Measurement text
(0070,0009) > Graphic Object Sequence Upper line
Upper line perpendicular
Lower line
Lower line perpendicular
2.2.1.3.1.3.1.6.14 Display Shutter

Display Shutter Module
(0018,1600) Shutter Shape RECTANGULAR

(0018,1602) Shutter Left Vertical Edge [value]
(0018,1604) Shutter Right Vertical Edge [value]
(0018,1606) Shutter Upper Horizontal Edge [value]
(0018,1608) Shutter Lower Horizontal Edge [value]
The manner in which the display area occluded by the shutter is neutralized (black-out, gray,
or other means) is defined by the Attribute Shutter Presentation Value (0018,1622). This
attribute present in the Presentation LUT module is mandatory when a display shutter is
present in the GSPS. The value can go from 0000xH (black) to FFFFxH (white).
2.2.1.3.1.3.1.6.15 Flipping/ rotating/ zooming

Flipping and rotating is always done on pixel level. The relevant DICOM tags can be found in
the following table:
Table 2.2-10: DICOM spatial transformation module attributes.
attribute tag Actions

Rotate 90 Rotate 90 counter Flip horizontal
clockwise clockwise
Image Rotation (0070,0042) If image is not If image is not flipped :
flipped : increased decreased with 90
with 90 (modulo (modulo 360)
360) Otherwise : increased
Otherwise : with 90 (modulo 360)
decreased with 90
(modulo 360)
Image horizontal (0070,0041) inverted (true 
flip false)
Zoom/Pan is integrated in the Displayed Area module of the GSPS.
2.2.1.3.1.3.2 Storage Commitment Push Model SOP Class (1.2.840.10008.1.20.1)

When the Storage Commitment Push Model has been configured, the DICOM Store AE will
request storage commitment for instances of the Image Storage SOP Class and Grayscale
Softcopy Presentation State Storage SOP Class with each successfully completed “sent”
job. The DICOM Store AE transmits the SOP Instances to the Remote AE. The request for
storage commitment is transmitted to the Remote AE together with a list of references to one
or more SOP Instances. If the Provider accepts the Storage Commitment with Success
Status, the generated Transaction UID, together with study identification data and a time-
stamp, is kept. Success or failure of storage commitment is subsequently indicated by a
notification from the Remote AE to NX 2.0.8000/3.0.8000.
HE/001261 Page 27 of 87
The DIMSE-N Services applicable to the Storage Commitment Push Model SOP Class are:
 N-EVENT_REPORT
 N-ACTION
The Storage Commitment Request operation allows a DICOM Store AE to request an SCP
to commit to the safekeeping of a set of SOP Instances as described above. This operation
is invoked through the N-ACTION primitive.
The N-ACTION is invoked by NX 2.0.8000/3.0.8000 and is sent by creating a new

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

summarized in the Table below:
Table 2.2-11: Storage Commitment N-ACTION Information
Action Requirement
Action Type Name Attribute Tag
Type ID Type SCU
Request Storage 1 Transaction UID (0008,1195) 1
Commitment Storage Media File-Set ID (0088,0130) 3
Storage Media File-Set UID (0088,0140) 3
Referenced SOP Sequence (0008,1199) 1
>Referenced SOP Class UID (0008,1150) 1
>Referenced SOP Instance UID (0008,1155) 1
>Storage Media File-Set ID (0088,0130) 3
>Storage Media File-Set UID (0088,0140) 3
Table 2.2-12: Storage Commitment N-ACTION Response Status Handling Behavior
Service Further Meaning Error Code Behavior

Status
Success 0000 successful Notification
Warning
Error
The behavior of the AE during communication failure is summarized in a table as follows:
Table 2.2-13: DICOM Command Communication Failure Behavior
Exception Behavior
Timeout e.g. The Association is aborted using A-ABORT and command marked as failed. The
reason is logged and reported to the user.
Association aborted e.g. The command is marked as failed. The reason is logged and reported to the user.
The DICOM Store AE does not wait for an N-EVENT-REPORT. It closes the association as
soon as it receives the N-ACTION-RP from the Remote AE. So, NX does not support N-
EVENT-REPORT within the same association as the N-ACTION.
2.2.1.3.1.3.3 Verification SOP Class (1.2.840.10008.1.1)

The Storage AE provides standard conformance to the Verification SOP Class as an SCU.
This verification is accomplished on an established Association using the C-ECHO DIMSE-C
service.
HE/001261 Page 28 of 87
These tests can be executed in the "Workstation Service & Configuration Tool".
The Configuration Tool opens an association when testing of a remote application is

requested during a configuration session. This can be done when entering new data for
remote application configuration or to verify existing configuration data using the C-ECHO
DIMSE-C service.
2.2.1.4 Association Acceptance Policies
2.2.1.4.1 Receive Storage Commitment Response

Each Storage Commitment Request that NX sends, is uniquely identified by the Transaction
UID Attribute (0008,1195) value that is generated by NX. After sending a Storage
Commitment Request, NX expects an N-EVENT-REPORT from the SCP. NX will then
respond with an N-EVENT-REPORT response primitive with a status code.
The NX DICOM Store AE will accept associations in order to receive responses to a Storage
Commitment Request.
DICOM Store AE PACS
1. Open Association
2. N-EVENT-REPORT (Storage Commit Resp)
Figure 2.2-1: Sequencing of Receive Storage Commitment response
2.2.1.4.1.2 Accepted Presentation Contexts

Table 2.2-14: Acceptable Presentation Contexts for Receive Storage Commitment Response

Abstract Syntax Transfer Syntax Extended
Role
Storage 1.2.840.10008.1.20.1 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None

Commitment Explicit VR Little Endian 1.2.840.10008.1.2.1
Push Model
Verification 1.2.840.10008.1.1 Implicit VR Little Endian 1.2.840.10008.1.2 SCP None
HE/001261 Page 29 of 87
2.2.1.4.1.3 SOP Specific Conformance – Storage Commitment SOP Class

(1.2.840.10008.1.20.1)
The AE will consider Storage Commitment FAILED if no N-EVENT-REPORT is received for
a Transaction UID within a configurable time period.
Table 2.2-15: Storage Commitment N-EVENT-REPORT expected Information
Action Type Action Type Requirement

Attribute Tag
Name ID Type SCU
Storage Commitment 1 Transaction UID (0008,1195) 1
Request Successful Storage Media File-Set ID (0088,0130) 3
Storage Media File-Set UID (0088,0140) 3
Referenced SOP Sequence (0008,1199) 1
>Storage Media File-Set ID (0088,0130) 3
>Storage Media File-Set UID (0088,0140) 3
Storage Commitment 2 Transaction UID (0008,1195) 1
Request Complete- Referenced SOP Sequence (0008,1199) 1
Failures Exist
Failed SOP sequence (0008,1198) 1
>Failure Reason (0008,1197) 1
The behavior of Storage AE when receiving Event Types within the N-EVENT-REPORT is
Table 2.2-16: Storage Commitment N-EVENT-REPORT Behavior
Event Type Name Event Type ID Behavior

Storage Commitment Request Successful 1 The job will be marked as SUCCESSFUL
Storage Commitment Request Complete – 2 The job will be marked as FAILED.

Failure exists
The reasons for returning specific status codes in an N-EVENT-REPORT response are
summarized in the table below:
Table 2.2-17: Storage Commitment N-EVENT-REPORT Response Status Reasons
Service Further Meaning status Code Reasons

Status
Success 0000 The SCP has successfully returned all matching information.
The behavior of the DICOM Store AE when receiving Event types over this association is the
same as when receiving them over the same association as documented in section
2.2.1.3.1.3.2 .
HE/001261 Page 30 of 87
2.2.1.4.1.4 SOP Specific Conformance – Verification SOP Class (1.2.840.10008.1.1)

The Storage AE provides standard conformance to the Verification SOP Class as an SCP.
This verification is accomplished on an established Association using the C-ECHO DIMSE-C
service.
HE/001261 Page 31 of 87
2.2.2 DICOM Print Application Entity Specification

Table 2.2-18: SOP Class(es) for the DICOM Print Application Entity
SOP Class SOP Class UID SCU SCP

Verification 1.2.840.10008.1.1 Yes No
Basic Grayscale Print Management Meta SOP Class 1.2.840.10008.5.1.1.9 Yes No
Basic Film Session SOP Class 1.2.840.10008.5.1.1.1 Yes No
Basic Film Box SOP Class 1.2.840.10008.5.1.1.2 Yes No
Basic Grayscale Image Box SOP Class 1.2.840.10008.5.1.1.4 Yes No
Printer SOP Class 1.2.840.10008.5.1.1.16 Yes No
Print Job SOP Class 1.2.840.10008.5.1.1.14 Yes No
Presentation LUT SOP Class 1.2.840.10008.5.1.1.23 Yes No
2.2.2.2.1 General

NX 2.0.8000/3.0.8000 initiates one association at a time for each destination to which a print
request is being processed in the active job queue list. Only one job per destination will be
active at a time, the others remain pending until the active job for that destination is
completed or failed. There can however be several simultaneous associations to different
destinations.
Table 2.2-20: Number of Associations as an Association Initiator for DICOM Print AE
1 per destination
Maximum number of simultaneous associations initiated
(32 max)

Table 2.2-21: Asynchronous Nature as an Association Initiator for DICOM Print AE
Maximum number of outstanding asynchronous transactions None

DICOM Print AE allows a single outstanding operation on any association. Therefore it does
not support asynchronous operations window negotiation, other than the default as specified
by the DICOM specification.
HE/001261 Page 32 of 87

Table 2.2-22: DICOM implementation Class and Version for DICOM Print AE
Implementation Version Name DPM1.XX 3
2.2.2.3.1 Activity – Print Images

The user composes images into film sheets and requests them to be sent to a specific
hardcopy device. A priori, the desired film format can be selected. Each sheet is internally
processed, converted to a STANDARD/1,1 page and then one print job is forwarded to the
job queue of the destination and processed individually.
The DICOM Print AE or NX 2.0.8000/3.0.8000 will initiate a separate Association for each
Print Session.
If the Printer rejects the Association, then NX 2.0.8000/3.0.8000 issues a warning message.
In case of a time-out (e.g. no answer from the Printer) or a warning message, the request
will be retried after at least 20 seconds. In the mean time requests to other destinations will
be handled.
After an association is established, the NX 2.0.8000/3.0.8000 will send one film session to
the Printer. Each film session will contain one film box, which in turn contains one image
box.
The N-ACTION DIMSE service on Film Session SOP class instructs the printer to print the
film session.
The print job has finished printing when the job is transferred to the printer or when the
printer has sent the N-EVENT-REPORT “Done” (in case print job sop class is supported by
the printer).
The NX 2.0.8000/3.0.8000 releases the association. In case of N-EVENT-REPORT it will

not wait for print job status “Done”.
The default PDU size negotiated by the NX 2.0.8000/3.0.8000 is 65542 bytes.
It is possible to print up to 16 bit (see §2.4.1.2.4).
3
XX is the build version number
HE/001261 Page 33 of 87
DICOM Print AE Printer
1. Open Association
2. N-CREATE-RQ (Basic Film Session)
3. N-CREATE -RSP
4. N-CREATE-RQ (Presentation LUT)

5. N-CREATE-RSP
6. N-CREATE-RQ (Basic Film Box)

7. N-CREATE-RSP
8. N-SET-RQ (Basic Grayscale Image Box)

9. N-SET-RSP
10. N-GET-RQ (Printer)

11. N-GET-RSP
12. N-ACTION-RQ
13. N-ACTION-RSP
14. N-DELETE-RQ
15. N-DELETE-RSP
Figure 2.2-2: Sequencing of Print Images

HE/001261 Page 34 of 87

The DICOM Print AE is capable of proposing the Presentation Contexts shown in the
following table:
Table 2.2-23: Presentation Contexts Proposed by DICOM Print AE
Extended
SOP Class Transfer Syntax
Role Negotiation
SOP Class SOP Class UID Name UID
Verification 1.2.840.10008.1.1 DICOM Implicit 1.2.840.10008.1.2 SCU None
VR Little Endian
Basic Grayscale Print 1.2.840.10008.5.1.1.9 DICOM Implicit 1.2.840.10008.1.2 SCU None
Management Meta SOP Class VR Little Endian
Print Job SOP Class 1.2.840.10008.5.1.1.14 DICOM Implicit 1.2.840.10008.1.2 SCU None
VR Little Endian
Basic Annotation Box SOP 1.2.840.10008.5.1.1.15 DICOM Implicit 1.2.840.10008.1.2 SCU None
Class VR Little Endian
Presentation LUT SOP Class 1.2.840.10008.5.1.1.23 DICOM Implicit 1.2.840.10008.1.2 SCU None
VR Little Endian
Print Queue Management SOP 1.2.840.10008.5.1.1.26 DICOM Implicit 1.2.840.10008.1.2 SCU None
Class VR Little Endian
Note:
The Presentation Context shall use Abstract Syntax IDs which correspond to the SOP
Classes UID of the Meta SOP Class specified in the first column of the Transfer Syntax
Table or included SOP Classes. None of the included SOP Classes supports extended
negotiation.
2.2.2.3.1.3 SOP Specific Conformance - Basic Grayscale Print Management Meta SOP
Class
NX 2.0.8000/3.0.8000 provides Standard conformance to the DICOM Basic Grayscale Print
Management Class (1.2.840.10008.1.1.9) as SCU.
Support for Basic Grayscale Print Management as SCU also implies support for the
following SOP Classes as SCU:
1. Basic Film Session SOP Class
2. Basic Film Box SOP Class
3. Basic Grayscale Image Box SOP Class
4. Printer SOP Class
2.2.2.3.1.3.1 Basic Film Session SOP Class (1.2.840.10008.5.1.1.1)

The Basic Film Session IOD describes the presentation parameters which are common for
all the films of a film session (e.g. number of films, film destination, …)
The Basic Film Session SOP Instance refers to one or more Basic Film Box SOP Instance
(§2.2.2.3.1.3.2).
HE/001261 Page 35 of 87
NX 2.0.8000/3.0.8000(SCU) can send the following DIMSE services:
 N-CREATE
 N-ACTION
N-CREATE is issued by NX 2.0.8000/3.0.8000 (SCU) to create a Basic Film Session SOP

instance, when an Association has been established. The N-CREATE causes the Basic Film
Session (root element) to be created by the SCP AE and its attributes initialized. The
following attributes are supported:
Table 2.2-24: Supported N-CREATE Attributes for a Basic Film Session
Attribute Name Tag Value

Number of Copies (2000,0010) Always set to 1
Print priority (2000,0020) Configurable
Medium Type (2000,0030) BLUE FILM ,CLEAR FILM, PAPER (configurable)
Film destination (2000,0040) MAGAZINE, BIN-i , PROCESSOR (configurable)
NX 2.0.8000/3.0.8000 (SCU) will process the N-CREATE confirmation and response Status
codes. The following status codes are recognized:
Table 2.2-25: N-CREATE Status Codes
Code Status Meaning

0000 Success Film Session successfully created
0116H Warning (or The SCP AE returns the attribute ”Value Out of Range”. This may result in Image Quality
Failure, Degradation.
depends on NX 2.0.8000/3.0.8000 will continue when its destination is an AGFA printer, but stops
the selected (ABORT) when its destination is a non-AGFA printer (might lead to unacceptable image
Printer Profile) quality).
0106H Error The SCP AE returns the attribute ”Invalid Attribute Value” . This indicates that the requested
memory allocation cannot be provided.
0213H Resource Limitation is returned by the SCP AE for the Basic Film Session SOP Class to
indicate that the requested allocation can temporarily not be provided.
* Other Status Other Dicom error codes result in the failure of the job. Other warnings are not
codes communicated to the user.
N-ACTION is issued by NX 2.0.8000/3.0.8000 (SCU) to print a Film Session. This means

that all subordinate Basic Film Boxes will be assembled into a print job for printing (the job
can therefore contain more than one film).
NX 2.0.8000/3.0.8000 (SCU) will process the N-ACTION confirmation and response Status
codes. The following status codes in Table 2.2-26 are recognized :
HE/001261 Page 36 of 87
Table 2.2-26: N-ACTION Status Codes
Code Status Meaning

0000 Success Normally returned by the SCP AE. Film(s) belonging to the film session are accepted for
printing.
B601 Warning Film session printing (collation) is not supported.
B602 Film Session SOP Instance hierarchy does not contain Image Box SOP Instances (empty
page).
B604 Image size is larger then Image Box size, the image has been magnified.
C600 Error Film Session SOP Instance hierarchy does not contain Film Box SOP instances.
C601 Unable to create Film SOP Instance; The print queue is full (device failure).
C603 Image size is larger then Image box size
* Other Status Other Dicom error codes result in the failure of the job. Other warnings are not communicated
codes to the user.
N-DELETE is issued by NX 2.0.8000/3.0.8000 (SCU) to delete a Film Session. This means

that the complete Film Session SOP Instance hierarchy will be deleted.
2.2.2.3.1.3.2 Basic Film Box SOP Class (1.2.840.10008.5.1.1.2)

The Basic Film Box IOD is an abstraction of the presentation of one film of the film session.
The Basic Film Box IOD describes the presentation parameters which are common for all
images on a given sheet of film.
The Basic Film Box SOP Instance refers to one or more Image Box SOP Instances, zero or
more film related Annotation Box SOP Instances, and zero or one Presentation LUT SOP
Instance.
NX 2.0.8000/3.0.8000 (SCU) can send the following DIMSE services:
 N-CREATE
N-CREATE is issued by NX 2.0.8000/3.0.8000 (SCU) to create a Basic Film Box under the
created Film Session and initialize its attributes (the creation of a Basic Film Box also
causes the subordinate Basic Image Boxes to be created for each location in the film
format).
The supported Film Box N-CREATE attributes are listed in the table below:
Table 2.2-27: Supported N-CREATE Attributes for a Basic Film Box

Image Display Format (2010,0010) STANDARD\1,1
Film Orientation (2010,0040) PORTRAIT,LANDSCAPE
Film Size ID (2010,0050) 8INX10IN, 10INX12IN, 10INX14IN, 11INX14IN, 14INX14IN,
14INX17IN, A4, A, 14INx36IN, 14INx51IN (configurable)
Magnification type (2010,0060) NONE, REPLICATE
Border Density (2010,0100) WHITE, BLACK or ODx100 (configurable)
Empty Image Density (2010,0110) WHITE, BLACK or ODx100 (configurable)
Min Density (2010,0120) Configurable
Max Density (2010,0130) Configurable
Trim (2010,0140) NO
HE/001261 Page 37 of 87

Configuration Information (2010,0150) Configurable
Illumination (2010,015E) Configurable, only applicable for printing with P-Values
Reflective Ambient Light (2010,0160) Configurable, only applicable for printing with P-Values
Referenced Film Session (2010,0500) A sequence which provides references to a Film Session SOP
Sequence Class/Instance pairs. Only a single item is permitted in this
Sequence.
>Referenced SOP Class UID (0008,1150) Uniquely identifies the referenced SOP Class
>Referenced SOP Instance UID (0008,1155) Uniquely identifies the referenced SOP Instance.
Referenced Presentation LUT (2050,0500) A sequence which provides references to a Presentation LUT
Sequence related SOP Class/Instance pairs. Only a single item shall be
included in this sequence.
>Referenced SOP Class UID (0008,1150) Uniquely identifies the referenced SOP Class
>Referenced SOP Instance UID (0008,1155) Uniquely identifies the referenced SOP Instance.
codes. The status codes below are recognized:
Table 2.2-28: N-CREATE Status Codes
Code Status Meaning

0000 Success Normally returned by the SCP AE. Film Box successfully created.
B605 Warning Requested Min Density or Max Density outside of printer’s operating range. The printer will use its
respective minimum or maximum density value instead.
* Other Other Dicom error codes result in the failure of the job. Other warnings are not communicated to
Status the user.
codes
2.2.2.3.1.3.3 Basic Grayscale Image Box SOP Class (1.2.840.10008.5.1.1.4)

The Basic Image Box IOD is an abstraction of the presentation of an image and image
related data in the image area of a film. The Basic Image Box IOD describes the
presentation parameters and image pixel data which apply to a single image of a sheet of
film.
The Basic Grayscale Image Box SOP Instance is created by the SCP at the time as the
Basic Film Box SOP Instance (§ 2.2.2.3.1.3.2) is created, based on the value of the Basic
Film Box Attribute Image Display Format (2010, 0010).
The Basic Grayscale Image Box SOP Instance refers to zero or one Image Overlay Box
SOP Instance and zero or one Presentation LUT SOP Instance.
 N-SET
N-SET is issued by NX 2.0.8000/3.0.8000 (SCU) to update an instance of the Grayscale

Image Box SOP Class.
When all needed Basic Grayscale Image Boxes have been set, NX 2.0.8000/3.0.8000
(SCU) issues a print command. There can be empty image positions. By using N-SET, NX
2.0.8000/3.0.8000 (SCU) can instruct the SCP to erase the image in the image position by
setting a zero length and no value in the attribute Basic Grayscale Image Sequence. The N-
Set attributes for the Basic Grayscale Image Box are listed below:
HE/001261 Page 38 of 87
Table 2.2-29: Supported N-SET Attributes for a Basic Grayscale Image Box

Image Position (2020,0010) 1
Polarity (2020,0020) NORMAL
Basic Grayscale Image Sequence (2020,0110)
>Samples Per Pixel (0028,0002) 1
>Photometric Interpretation (0028,0004) MONOCHROME2
>Rows (0028,0010) larger than 0
>Columns (0028,0011) larger than 0
>Bits Allocated (0028,0100) 8 – 16
>Bits Stored (0028,0101) 8 – 16
>High Bit (0028,0102) 7 to 15
>Pixel Representation (0028,0103) 0
>Pixel Data (7FE0,0010) A data stream of the pixel samples that comprise the Image.
NX 2.0.8000/3.0.8000 (SCU) will process the N-SET confirmation and response Status
codes. The status codes listed below in Table 2.2-30 are recognized:
Table 2.2-30: N-SET Status Codes
Code Status Meaning

0000 Success Normally returned by the SCP AE. Image successfully stored in Image Box
B604 Warning Image size is larger then Image Box size, the image has been magnified.
B605 Requested Min Density or Max Density outside of printer’s operating range. The printer will
use its respective minimum or maximum density value instead.
C603 Error Image size is larger then Image box size
C605 Insufficient memory in printer to store the image.
* Other Status Other Dicom error codes result in the failure of the job. Other warnings are not communicated
codes to the user.
2.2.2.3.1.3.4 Printer SOP Class (1.2.840.10008.5.1.1.16)

The Printer IOD is an abstraction of the hard copy printer and is the basic Information Entity
to monitor the status of the printer. The Printer SOP Instance is created by the SCP during
start-up of the hard copy printer and has a well-known SOP Instance UID.
The Printer SOP Class is used to monitor the status of the printer.
NX 2.0.8000/3.0.8000 (SCU) will accept the following DIMSE services:
 N-EVENT-REPORT
 N-GET
N-EVENT-REPORT is used to report the changes of the printer status in an asynchronous

way. The SCP uses the N-EVENT-REPORT to inform NX 2.0.8000/3.0.8000 about each
execution change. NX 2.0.8000/3.0.8000 will return the confirmation of the N-EVENT-
REPORT operation.
HE/001261 Page 39 of 87
Table 2.2-31: Notification Event Information
Event Type Name Event Type ID Attribute Tag

Printer Status Info (2110, 0020)
Normal 1 Film Destination (2000, 0040)
Printer Name (2110, 0030)
Warning 2 Film Destination (2000, 0040)
Failure 3 Film Destination (2000, 0040)
Note:
If the Event Type Name = Warning or Failure then the warning/failure condition can be
stored by the SCP Printer Status Info argument.
N-GET is issued by NX 2.0.8000/3.0.8000 (SCU) to retrieve an instance of the Printer SOP

class. NX 2.0.8000/3.0.8000 specifies the UID of the SOP Instance to be retrieved. The
supported N-GET attributes are listed in the table below:
Table 2.2-32: Supported Attributes for N-GET on a Printer

Printer Status (2110,0010) NORMAL, WARNING, FAILURE
Printer Status Info (2110,0020) Printer dependent
Printer Name (2110,0030) User defined name identifying the printer.
Manufacturer (0008,0070) Manufacturer of the printer
Manufacturer Model Name (0008,1090) Manufacturer’s model number of the printer
Device Serial Number (0018,1000) Manufacturer’s serial number of the printer
Software Versions (0018,1020) Manufacturer's designation of software version of the printer.
Date Last Calibration (0018,1200) Date when the printer was last calibrated.
Time Last Calibration (0018,1201) Time when the printer was last calibrated.
2.2.2.3.1.4 SOP Specific Conformance Print Job SOP Class (1.2.840.10008.5.1.1.14)

The Print Job IOD is an abstraction of the Print Job transaction and is the basic information
entity to monitor the execution of the Print Process. A Print Job contains one film or multiple
films, all belonging to the same film session.
The Print Job SOP Class is created by N-ACTION operation of the Film Session SOP Class
(§2.2.2.3.1.3.1), Film Box SOP Class (§2.2.2.3.1.3.2), or Pull Print Request SOP Class. The
Print Job SOP Instance is deleted after the films are printed or after a failure condition.
NX 2.0.8000/3.0.8000 (SCU) will accept the following DIMSE services:
 N-EVENT-REPORT
 N-GET
HE/001261 Page 40 of 87
N-EVENT-REPORT is used by the SCP to report execution status changes to NX

2.0.8000/3.0.8000 (SCU) in an asynchronous way.
N-EVENT-REPORT has the following arguments
Table 2.2-33: Notification Event Information
Event Type Name Event Type ID Attribute Tag

Pending 1 Execution Status Info (2100,0030)
Print Job ID (2100,0010)
Film Session Label (2000,0050)
Printer Name (2110,0030)
Printing 2 Execution Status Info (2100,0030)
Done 3 Execution Status Info (2100,0030)
Failure 4 Execution Status Info (2100,0030)
Note:
The SCU only releases the Association after the receipt of the event type Done or
Failure, if the print job sop class is supported.
NX 2.0.8000/3.0.8000 (SCU) returns the confirmation from the N-EVENT-REPORT
operation.
N-GET is used to retrieve an instance of the Print Job SOP Class. NX 2.0.8000/3.0.8000
(SCU) uses the N-GET to request the SCP to get a Print Job SOP Instance. NX
2.0.8000/3.0.8000 specifies the UID of the SOP Instance to be retrieved.
Table 2.2-34: Supported N-GET Attributes for a Print Job

Execution Status (2100,0020) PENDING, PRINTING, DONE, FAILURE
Execution State Info (2100,0030) Printer dependent.
Print Priority (2000,0020) HIGH, MED, LOW
Creation Date (2100,0040) Date of print job creation.
Creation Time (2100,0050) Time of print job creation
Printer Name (2110,0030) User defined name identifying the printer
Originator (2100,0070) DICOM AE title that issued the print operation
HE/001261 Page 41 of 87
2.2.2.3.1.5 SOP Specific Conformance Presentation LUT SOP Class

(1.2.840.10008.5.1.1.23)
The Presentation LUT Information Object is an abstraction of a Presentation LUT. The
objective of the Presentation LUT is to realize image display tailored for specific modalities,
applications, and user preferences. It is used to prepare image pixel data for display on
devices that conform to the Grayscale Standard Display Function.
The output of the Presentation LUT is Presentation Values (P-Values).
An N-CREATE is issued by NX 2.0.8000/3.0.8000 (SCU) to create a Presentation LUT SOP

Instance. The supported Presentation LUT attributes are listed below:
Table 2.2-35: Supported Attributes for Presentation LUT
Tag Name Supported Default

(2050,0020) Presentation LUT Shape IDENTITY (Note) IDENTITY
Note:
‘Presentation LUT Sequence’ is not supported.
codes. The status codes listed below are recognized:
Table 2.2-36: N-CREATE confirmation and response Status codes
Code Status Meaning

0000 Success Presentation LUT successfully created
B605 Warning Requested Min or Max Density outside of printer’s operating range. The printer will use its
respective minimum or maximum value instead.
Note:
NX 2.0.8000/3.0.8000 (SCU) uses the N-CREATE Service Element to request the
SCP to create a Presentation LUT SOP Instance. NX 2.0.8000/3.0.8000 shall initialize
the Attributes of the SOP Class.
The Presentation LUT persists in the SCP as long as the Association in which it was
created is open or an explicit N-DELETE is issued by the SCU.
2.2.2.3.1.6 SOP Specific Conformance Verification SOP Class (1.2.840.10008.1.1)

See § 2.2.1.4.1.4.
HE/001261 Page 42 of 87
2.2.3 RIS Application Entity Specification


Modality Worklist Information Model – FIND 1.2.840.10008.5.1.4.31 Yes No
2.2.3.2.1 General

NX 2.0.8000/3.0.8000 initiates one association at a time to query the worklist.
Table 2.2-39: Number of Associations as an Association Initiator for RIS AE
Maximum number of simultaneous associations initiated 1

Table 2.2-40: Asynchronous Nature as an Association Initiator for RIS AE

NX 2.0.8000/3.0.8000 does not support asynchronous communication (multiple outstanding
transactions over a single connection).

Table 2.2-41: DICOM implementation Class and Version for DICOM RIS AE
4
HE/001261 Page 43 of 87
2.2.3.3.1 Activity – Query RIS

The request for Query RIS is initiated by user interaction (pressing the “Query RIS” button)
or automatically at specific time intervals (configurable by the user). Depending on the
configuration this can either be a query based on a user provided accession number or be a
complete worklist update based on date, modality and Scheduled Station AE title.
RIS AE Department Scheduler
1. Open Association
2. C-FIND Request (Worklist query)
3. C-FIND Response(Worklist item)-status = pending
4. C-FIND Response(Worklist item)-status = pending
5. C-FIND Response - status = success
Figure 2.2-3: Sample Sequencing Diagram for Refresh Worklist

The RIS Application Entity is capable of proposing the Presentation Contexts shown in the
following table:

Role
Modality 1.2.840.10008.5.1.4.31 Implicit VR Little 1.2.840.10008.1.2 SCU None

Worklist Endian
Information
Model – FIND
2.2.3.3.1.3 SOP Specific Conformance – Modality Worklist SOP Class

(1.2.840.10008.5.1.4.31)
The Modality Worklist SOP class, defined within the Basic Worklist Management Service
Class, defines an application-level class of service which facilitates the communication of
information to the imaging modality about Scheduled Procedure Steps, and entities related
to the Scheduled Procedure Steps.
This worklist is structured according to Scheduled Procedure Steps. A procedure step is a

unit of service in the context of a requested imaging procedure.
HE/001261 Page 44 of 87
The behavior of a RIS AE when encountering status codes in a C-FIND response is

Table 2.2-43: C-Find Response Status Handling Behavior
Service Status Status Code Status Code

Success 0000 Matching is complete
Refused A700 Out of resources
Failed A900 Identifier does not match SOP Class
C000-CFFF Unable to Process
Cancel FE00 Matching terminated due to Cancel request
Pending FF00 Matches are continuing – Current Match is supplied and any Optional
Keys were supported in the same manner as Required Keys.
FF01 Matches are continuing – Warning that one or more Optional Keys were
not supported
* Other Status codes Other Dicom error codes result in the failure of the job. Other warnings
are not communicated to the user.
Exception Behavior
Timeout
Association aborted
The table below provides a description of the Worklist Request Identifier. Unexpected
attributes returned in a C-FIND response are ignored.
Table 2.2-45: Worklist request identifiers
Attribute name Tag Broad Query Accession number

query
Scheduled Procedure Step
Scheduled Station AE Title (0040,0001) Single Value Matching
Scheduled Procedure Step Start Date (0040,0002) Range Matching
Scheduled Procedure Step Start Time (0040,0003)
Scheduled Procedure Step Location (0040,0011)
Modality (0008,0060) Single Value Matching
Scheduled Procedure Step Description (0040,0007)
Scheduled Performing Physician's Name (0040,0006)
Scheduled Performing Physician's ID Sequence (0040,000B)
Scheduled Station Name (0040,0010)
Scheduled Protocol Code Sequence (0040,0008)
Pre-Medication (0040,0012)
Scheduled Procedure Step ID (0040,0009)
Request Contrast Agent (0032,1070)
Scheduled Procedure Step Status (0040,0020)
Scheduled Procedure Step Comment (0040,0400)
Requested Procedure
Requested Procedure Description (0032,1060)
HE/001261 Page 45 of 87

query
Requested Procedure Code Sequence (0032,1064)
Requested Procedure ID (0040,1001)
Study Instance UID (0020,000D)
Referenced Study Sequence (0008,1110)
Reason for the Requested Procedure (0040,1002)
Requested Procedure Priority (0040,1003)
Patient Transport Arrangement (0040,1004)
Requested Procedure Location (0040,1005)
Requested Procedure Comments (0040,1400)
Confidentiality Code (0040,1008)
Reporting Priority (0040,1009)
Names of Intended Recipients of Results (0040,1010)
Intended Recipients of Results Identification (0040,1011)
Sequence
Imaging Service Request
Accession Number (0008,0050) Wildcard matching
Requesting Physician (0032,1032)
Requesting Physician Identification Sequence (0032,1031)
Referring Physician's Name (0008,0090)
Referring Physician Identification Sequence (0008,0096)
Requesting Service (0032,1033)
Placer Order Number (0040,2016)
Filler Order Number (0040,2017)
Imaging Service Request Comments (0040,2400)
Issue Date of Imaging Service Request (0040,2004)
Issue Time of Imaging Service Request (0040,2005)
Order Entered by… (0040,2008)
Order Enterer’s Location (0040,2009)
Order Callback Phone Number (0040,2010)
Reason for imaging service (0040,2001)
Visit Identification
Admission ID (0038,0010)
Institution Name (0008,0080)
Institution Address (0008,0081)
Institution Code Sequence (0008,0082)
Issuer of Admission ID (0038,0011)
Visit Status
Current Patient Location (0038,0300)
Visit Status ID (0038,0008)
Patient’s Institution Residence (0038,0400)
Visit Comments (0038,4000)
Visit Relationship
Referenced Patient Sequence (0008,1120)
Visit Admission
Route of Admissions (0038,0016)
Admitting Date (0038,0020)
Admitting Time (0038,0021)
Scheduled Admission Date (0038,001A)
Scheduled Admission Time (0038,001B)
HE/001261 Page 46 of 87

query
Admitting Diagnosis Description (0008,1080)
Admitting Diagnosis Code Sequence (0008,1084)
Patient Identification
Patient's Name (0010,0010)
Patient ID (0010,0020)
Other Patient IDs (0010,1000)
Issuer of Patient ID (0010,0021)
Other Patient Names (0010,1001)
Patient’s Birth Name (0010,1005)
Patient’s Mother’s Birth Name (0010,1060)
Medical Record Locator (0010,1090)
Referenced Patient Alias Sequence (0038,0004)
Patient Demographic
Patients Birth Date (0010,0030)
Patient's Sex (0010,0040)
Patient’s Birth Time (0010,0032)
Patient’s Primary Language Code Sequence (0010,0101)
>Patient’s Primary Language Code Modifier (0010,0102)
Sequence
Patient’s Weight (0010,1030)
Patient’s Size (0010,1020)
Patient’s Age (0010,1010)
Military Rank (0010,1080)
Branch of Service (0010,1081)
Ethnic Group (0010,2160)
Occupation (0010,2180)
Patient Comment (0010,4000)
Confidentiality constraint on patient data (0040,3001)
Patient’s Insurance Plan Code Sequence (0010,0050)
Patient’s Address (0010,1040)
Country of Residence (0010,2150)
Region of Residence (0010,2152)
Patient’s Telephone Numbers (0010,2154)
Patient’s Religious Preference (0010,21F0)
Patient Medical
Patient State (0038,0500)
Pregnancy Status (0010,21C0)
Medical Alerts (0010,2000)
Contrast Allergies (0010,2110)
Special Needs (0038,0050)
Additional Patient History (0010,21B0)
Last Menstrual Date (0010,21D0)
Smoking Status (0010,21A0)
HE/001261 Page 47 of 87
2.2.3.4 User defined fields

There are five (5) optional (type 3) user defined fields that can be mapped from the RIS and
which can be sent out during archiving and exporting.
These fields can be found in the following Table:
Table 2.2-46: List of User defined DICOM fields
Tag Description VR
(0019,0010) “Agfa ADC NX” LO
(0019,10F0) User Defined field 1 LO
HE/001261 Page 48 of 87
2.2.4 MPPS Application Entity Specification


Modality Performed Procedure Step 1.2.840.10008.3.1.2.3.3 Yes No
2.2.4.2.1 General

NX 2.0.8000/3.0.8000 initiates one association at a time to query the worklist.
Table 2.2-49: Number of Associations as an Association Initiator for MPPS AE
Maximum number of simultaneous associations initiated 1

Table 2.2-50: Asynchronous Nature as an Association Initiator for MPPS AE

NX 2.0.8000/3.0.8000 does not support asynchronous communication (multiple outstanding
transactions over a single connection).

Table 2.2-51: DICOM implementation Class and Version for DICOM MPPS AE
5
HE/001261 Page 49 of 87
2.2.4.3.1 Activity – Acquire Images

When the first image of a session arrives, an association will be opened to create an MPPS
instance (via N-CREATE) on the MPPS manager. NX 2.0.8000/3.0.8000 will wait for an N-
CREATE response from the Department Scheduler (status success). When the N-CREATE
response is received, the association with the Department Scheduler will be closed. When
the session is closed on NX 2.0.8000/3.0.8000, an association will be opened to complete
the MPPS instance (via N-SET). Again NX 2.0.8000/3.0.8000 will wait for an N-SET
response from the Department Scheduler (status success). Once the response is received,
the association will be closed.
When all images of a study are transferred to another study and no new images are
acquired before the session is closed, an N-SET MPPS discontinued will be sent in stead of
the normal N-SET response.
MPPS AE Department Scheduler
1. Open Association
2. N-CREATE (MPPS) - IN PROGRESS
4. Aquire Images()
5. Open Association
6. N-SET (MPPS) - COMPLETED
Figure 2.2-4: Sample Sequencing Diagram for MPPS

HE/001261 Page 50 of 87

The MPPS Application Entity is capable of proposing the Presentation Contexts shown in
the following table:

Role
Modality 1.2.840.10008.3.1.2.3.3 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None

Performed Explicit VR Little Endian 1.2.840.10008.1.2.1
Procedure Step
2.2.4.3.1.3 SOP Specific Conformance – MPPS (1.2.840.10008.3.1.2.3.3)

 N-CREATE
 N-SET
A N-CREATE allows NX 2.0.8000/3.0.8000 to create an instance of the Modality Performed

Procedure Step SOP Class and provide information about a specific real-world Performed
Procedure Step that is under control of NX 2.0.8000/3.0.8000.
A N-SET allows NX 2.0.8000/3.0.8000 to set Attribute Values of an instance of the Modality

Performed Procedure Step SOP Class and provide information about a specific real-world
Modality Performed Procedure Step that is under control of NX 2.0.8000/3.0.8000.
Note:
NX 2.0.8000/3.0.8000 informs the Information System as soon as possible that the
performance of the Procedure Step has been started by sending the N-CREATE
Service Request. This allows an SCP of the Modality Worklist SOP Class (if
supported) to update the Modality Worklist. Some of the attribute values are already
known at the beginning of the Procedure Step, they are sent in the N-CREATE
command. Other mandatory attributes are known only at the end of the Performed
Procedure Step, they are assigned a value in the N-SET command.
The behavior of MPPS AE when encountering status codes in an MPPS N-CREATE or N-

SET response is summarized in the Table below:
Table 2.2-53: N-CREATE/N-SET Response Status Handling Behavior
Service Further Meaning Status Code Behavior

Status
Success Matching is complete 0000 The SCP has completed the operation successfully
Failure Processing Failure – 0110H

Performed Procedure
Step Object may no
longer be updated
* Other Status codes * Other Dicom error codes result in the failure of the job.
Other warnings are not communicated to the user.
HE/001261 Page 51 of 87
Exception Behavior
Timeout If the sending fails, the system will retry automatically until the session is cleaned up.
Association aborted If the sending fails, the system will retry automatically until the session is cleaned up.
The following table provides a description of the MPPS N-CREATE and N-SET request
identifiers sent by the MPPS AE. Empty cells in the N-CREATE and N-SET columns indicate
that the attribute is not sent. An “X” indicates that an appropriate value will be sent.
Table 2.2-55: MPPS N-CREATE/N-SET Request Identifier
Attribute Tag N-CREATE N-SET

Specific Character Set (0008,0005) X X
Performed Procedure Step Relationship
Scheduled Step Attribute Sequence (0040,0270)
>Study Instance UID (0020,000D) X
>Referenced Study Sequence (0008,1110) From MWL or user input
>>Referenced SOP Class UID (0008,1150) From MWL or user input
>>Referenced SOP Instance UID (0008,1155) From MWL or user input
>Accession Number (0008,0050) From MWL or user input N/A
>Placer Order Number/Imaging Service Request (0040,2016) From MWL or user input
>Filler Order Number/Imaging Service Request (0040,2017) From MWL or user input
>Requested Procedure ID (0040,1001) From MWL or user input
>Requested Procedure Description (0032,1060) From MWL or user input
>Scheduled Procedure Step ID (0040,0009) From MWL or user input
>Scheduled Procedure Step Description (0040,0007) From MWL or user input
>Scheduled Protocol Code Sequence (0040,0008) From MWL or user input
>>Code Value (0008,0100) From MWL or user input
>>Coding Scheme designator (0008,0102) From MWL or user input
>>Coding Scheme Version (0008,0103) From MWL or user input
>>Code Meaning (0008,0104) From MWL or user input
>>All other Attributes from Scheduled Protocol
Code Sequence
Patient’s Name (0010,0010) From MWL or user input
Patient ID (0010,0020) From MWL or user input
Patient’s Birth Date (0010,0030) From MWL or user input
Patient’s Sex (0010,0040) From MWL or user input
Referenced Patient Sequence (0008,1120) From MWL or user input
>Referenced SOP Class UID (0008,1150) From MWL or user input
>Referenced Instance UID (0008,1155) From MWL or user input
Performed Procedure Step Information
Performed Procedure Step ID (0040,0253) X
Performed Station AE Title (0040,0241) X
Performed Station Name (0040,0242) X
Performed Location (0040,0243) X
Performed Procedure Step Start Date (0040,0244) X
Performed Procedure Step Start Time (0040,0245) X
Performed Procedure Step Status (0040,0252) "IN PROGRESS" "COMPLETED"
HE/001261 Page 52 of 87

Exam group names of
the exposures in the
Performed Procedure Step Description (0040,0254) study X
set to the Requested
Procedure Description
Performed Procedure Type Description (0040,0255) from the SPS X
Procedure Code Sequence (0008,1032) Zero length Zero length
Performed Procedure Step End Date (0040,0250) Empty close session date
Performed Procedure Step End Time (0040,0251) Empty close session time
only if user provided
Comments on the Performed Procedure Step (0040,0280) Empty this information
Performed Procedure Step Discontinuation Available if
Reason Code Sequence (0040,0281) Empty discontinued
>Code Value (0008,0100) Empty “”
>Coding Scheme Designator (0008,0102) Empty “”
>Coding Scheme Version (0008,0103) Empty “”
>Code Meaning (0008,0104) Empty “”
Image Acquisition Results
Modality (0008,0060) CR or DX
set to Requested
Procedure ID or
automatically generated
Study ID (0020,0010) for unscheduled case
Performed Protocol Code Sequence (0040,0260) Empty Empty
>Code Value (0008,0100) Empty Empty
>Coding Scheme Designator (0008,0102) Empty Empty
>Coding Scheme Version (0008,0103) Empty Empty
>Code Meaning (0008,0104) Empty Empty
>All other Attributes from Performed Protocol
Code Sequence
Performed Series Sequence (0040,0340) Empty

If user provided this
information. Otherwise
>Performing Physician’s Name (0008,1050) Empty empty.
concatenation of “CR ”
or “DX ” plus all exam
groups of the
exposures, taken in
>Protocol Name (0018,1030) Empty this MPPS
Operator who was
logged in at the Create
>Operator’s Name (0008,1070) Empty of this MPPS
>Series Instance UID (0020,000E) Empty X
BODY PART [space]
>Series Description (0008,103E) Empty VIEW POSITION
>Retrieve AE Title (0008,0054) Empty Blank
>Referenced Image Sequence (0008,1140) Empty X
>>Referenced SOP Class UID (0008,1150) Empty X
>>Referenced SOP Instance UID (0008,1155) Empty X
>Referenced Non-Image Composite SOP X
Instance Sequence (0040,0220) Empty
>>Referenced SOP Class UID (0008,1150) Empty X
>>Referenced SOP Instance UID (0008,1155) Empty X
HE/001261 Page 53 of 87

Billing And Material Management Code Module
Film Consumption Sequence (0040,0321) Empty X
>Number of Films (2100,0170) Empty X
>Medium Type (2000,0030) Empty X
>Film Size ID (2010,0050) Empty X
Radiation Dose Module
Total Number of Exposures (0040,0301) Empty X
Exposure Dose Sequence (0040,030E) Empty X
>Distance Source to Detector (0018,1110) Empty X
>Entrance Dose (0040,0302) Empty X
>Entrance Dose in mGy (0040,8302) Empty X
>KVp (0018,0060) Empty X
>X-ray Tube Current in μA (0018,8151) Empty X
>Image Area Dose Product (0018,115E) Empty X
>Exposure Time (0018,1150) Empty X
>Filter Type (0018,1160) Empty X
>Filter Material (0018,7050) Empty X
Note:
1. The requirement for the final state is that which applies at the time that the Performed
Procedure Step Status (0040,0252) is N-SET to a value of COMPLETED or
DISCONTINUED. It is only described if it is different from the SCP requirement for the
N-CREATE.
2. The Performed Series Sequence (0040,0340) may not be empty (zero length) at the
time that the Performed Procedure Step Status (0040,0252) is N-SET to a value of
COMPLETED or DISCONTINUED. In other words a Series must exist for every
Performed Procedure Step, though it may contain no Images or Non-Image Composite
objects, if none were created.
3. Only attributes that are specified in a SOP Instance at N-CREATE may later be updated
through the N-SET. If NX 2.0.8000/3.0.8000 wishes to use the PPS Discontinuation
Reason Code Sequence (0040, 0281), it creates that attribute (zero-length) during
MPPS N-CREATE.
HE/001261 Page 54 of 87
2.3 Network Interfaces

NX 2.0.8000/3.0.8000 provides DICOM V3.0 TCP/IP Network Communication Support as
defined in PS 3.8 of the DICOM Standard (2008). NX 2.0.8000/3.0.8000 inherits its TCP/IP
stack from the computer system upon which it executes.
2.3.1 Physical Medium Support

NX 2.0.8000/3.0.8000 is indifferent to the physical medium over which TCP/IP executes; it
inherits the medium from the computer system upon which it is being executed.
2.3.2 Additional Protocols

NX 2.0.8000/3.0.8000 can use DNS to resolve hostnames. It will use the TCP/IP stack from
the Windows System it runs on.
For audit trailing the NX 2.0.8000/3.0.8000 will query an NTP server as time reference. This
NTP Server can be configured in the "Workstation Service & Configuration Tool". For all
other cases the local system clock will be used as a time reference.
HE/001261 Page 55 of 87
2.4 Configuration
2.4.1 AE Title/ Presentation Address Mapping
2.4.1.1 Local AE Titles

NX 2.0.8000/3.0.8000 uses the AE Titles and TCP/IP Ports configured by means of the
"Workstation Service & Configuration Tool". The Field Service Engineer can configure the
TCP Port via the "Workstation Service & Configuration Tool". No Default AE Titles are
provided. The AE Titles must be configured during installation. The local AE Title used by
each individual application can be configured independently of the AE Title used by other
local applications.
Table 2.4-1: AE Title Configuration Table
Application Entity Default AE Title Default TCP/IP Port

Storage No Default 104
Hardcopy No Default Not Applicable
RIS No Default Not Applicable
MPPS No Default Not Applicable
2.4.1.2 Remote AE Title/ Presentation Address Mapping

The AE title, host names and port numbers of remote applications are configured using the
"Workstation Service & Configuration Tool".
2.4.1.2.1 Storage
The "Workstation Service & Configuration Tool" must be used to set the AE Titles, port-
numbers, host-names and capabilities for the remote Storage SCPs. Associations will only
be accepted from known AE Titles while associations from unknown AE Titles will be
rejected (an AE Title is known if it can be selected within the "Workstation Service &
Configuration Tool"). Multiple remote Storage SCPs can be defined. Any Storage SCP can
be configured to be an “Archive” device causing storage commitment to be requested for
images or presentation states transmitted to the device.
Storage Commit can be enabled or disabled.
The Archive Connection can be tested by means of a DICOM Ping (C-echo) test to the
archive.
2.4.1.2.1.1 Archive options

When sending images to an archive, this can be done by means of the following SOP
classes: CR, DX and MG for presentation or DX and MG for processing. The latter is a RAW
image, without any annotations or measurements burned in.
Image pixels can be sent in the requested output type (configurable) depending on the used
SOP class and whether GSPS is supported or not6.
6
anonymous archiving (i.e. without patient demographics) is not supported
HE/001261 Page 56 of 87
CR image, WITHOUT GSPS:

- 8 bit OD
- 8 bit OD Gamma correction
- 8 bit P-Value
- 12-bit OD
- 12-bit OD Gamma correction
- 12 bit P-Value
- 12-bit OD REL
- 12-bit M1 Image + VOI Lut OD REL
- 12-bit M1 Image + VOI Lut Gamma
- 15-bit M1 Image + VOI Lut P-Value
Note: it is possible to send P-values even in CR images, using the (2050, 0020)
Presentation Lut Shape = "Identity" in the General Image Module.
CR image, GSPS ENABLED:

 only P-value output formats are allowed, since the output of GSPS has to be P-values
anyway:
- 8 bit P-Value
- 12 bit P-Value
Note: when GSPS is enabled, the LUT tables in the GSPS are a copy of the LUTs in the
image object.
DX image "for presentation" and/or MG image “for presentation”, both with or without
GSPS:
- 8 bit P-Value
- 12 bit P-Value
DX image "for processing" or MG image “for processing”

 this is always without GSPS, as it is the raw image.
 the output type cannot be chosen either.
HE/001261 Page 57 of 87
Table 2.4-2: Overview of the PACS DICOM CR-Image Types supported by NX 2.0.8000/3.0.8000.
PI M-Lut Rescale VOI-Lut P-LUT MU1 MU2

LUT-
(1) Intercept Slope Type Explanation WinCenter WinWidth Shape (2) (3)
Description 28,0004 28.1052 28.1053 28.1054 28.3003 28,1050 28.1051 2050,0020
8-bit OD M1 200 10.9804 OD - 1600 2800 - X X

M2 3000 -10.9804 OD - 1600 2800 - X X
8-bit ODGAMMA M1 200 10.9804 OD - 1600 2800 - X X
M2 3000 -10.9804 OD - 1600 2800 - X X
8-bit P-Value M1 0.0 1.0 P-VALUES - 128 256 INVERSE X X
M2 0.0 1.0 P-VALUES - 128 256 IDENTITY X X
12-bit OD M1 200 0.684 OD - 1600 2800 - X X

M2 3000 -0.684 OD - 1600 2800 - X X
12-bit ODGAMMA M1 200 0.684 OD - 1600 2800 - X X
M2 3000 -0.684 OD - 1600 2800 - X X
12-bit P-Value M1 0.0 1.0 P-VALUES - 2048 4096 INVERSE X X
M2 0.0 1.0 P-VALUES - 2048 4096 IDENTITY X X
12-bit OD REL M1 0.0 1.0 OD REL - 2048 4096 - X X

M2 0.0 1.0 OD REL - 2048 4096 - X X
12-bit Image --> VOI Lut OD REL M1 0.0 1.0 LOG_E REL E25, NK5. … - (7) - (7) - X
(12)
M2 0.0 1.0 LOG_E REL E25, NK5. … - (7) - (7) - X
12-bit image --> VOI Lut M1 0.0 1.0 LOG_E REL E25, NK5. … - (7) - (7) - X
ODGamma (12)
M2 0.0 1.0 LOG_E REL E25, NK5. … - (7) - (7) - X
15-bit Image --> VOI Lut P-Value
M1 0.0 1.0 P-VALUES E25, NK5. … - (7) - (7) INVERSE X
(15)
M2 0.0 1.0 P-VALUES E25, NK5. … - (7) - (7) IDENTITY X
12-bit Image --> VOI Lut OD REL M1 0.0 1.0 LOG_E REL - - (7) - (7) - X
(12)
M2 0.0 1.0 LOG_E REL - - (7) - (7) - X
12-bit Image --> VOI Lut M1 0.0 1.0 LOG_E REL - - (7) - (7) - X
ODGamma (12)
M2 0.0 1.0 LOG_E REL - - (7) - (7) - X
15-bit Image --> VOI Lut P-Value M1 0.0 1.0 P-VALUES - WC (9) WW (9) INVERSE X
(15)
M2 0.0 1.0 P-VALUES - WC (9) WW (9) IDENTITY X
(1) Photometric Interpretation : MONOCHROME1 (M1) or MONOCHROME2 (M2)
(2) Formats supported by Musica1 processing
(3) Formats supported by Musica2 processing
(7) WinCenter/WinWidth are not present. Instead LUT Data is present.
(9) Values are in pixel values (e.g. 16384, 16384)
(12) After application of the VOI Lut, the bit depth will be equal to the bit depth before application of the VOI Lut, i.e. 12 bit
(15) After application of the VOI Lut, the bit depth will be equal to the bit depth before application of the VOI Lut, i.e. 15 bit
The above table should be read as follows:

- This table contains the properties for each DICOM CR-Image Type. The relevant
DICOM tags are shown in the column headers and the values that define a specific
DICOM CR-Image Type can be found below the corresponding tag.
- The PACS DICOM CR-Image Types supported by NX 2.0.8000/3.0.8000 are marked
with an “X”.
HE/001261 Page 58 of 87
2.4.1.2.2 RIS
The "Workstation Service & Configuration Tool" must be used to set the AE Title, port-
number, host-name and capabilities of the remote Modality Worklist SCP.
Only one single remote Modality Worklist SCP can be defined at the same time.
2.4.1.2.2.1 Configuration of a RIS
2.4.1.2.2.1.1 Query keys

Query keys are used when the RIS connection is configured for DICOM Modality Worklist. In
the configuration Tool, the user is allowed to enter and/or modify certain query keys. Based
on these keys, the worklist will be populated at the next RIS query.
See Table 2.2-45.
2.4.1.2.2.1.2 Protocol Codes
Note on Japanese Protocol Codes

In Japan, the use of protocol codes is slightly different. See the guidelines of the JIRA and
JAHIS [JAPAN].
Each Scheduled Protocol Code Sequence consists of the following information:
Table 2.4-3: Information in a Japanese Scheduled Protocol Code Sequence.
Item Coding Scheme No. of items Code Value/Code Meaning

Designator
7
Procedure content JJ1017T 1 Specified in Section 5.3
7
Target region JJ1017P 1 Specified in Section 5.4
7
Imaging direction JJ1017D 0-N Specified in Section 5.5
(Table copied from [JAPAN], p.9)
Each item mentioned in the table is wrapped in a scheduled protocol code sequence item.
As shown in the table, for each item a different coding scheme designator is used.
In practice, a triplet (with the imaging direction possibly omitted) refers to a single Exposure
Type in the NX 2.0.8000/3.0.8000 exposure tree.
Example of a Japanese SPS

Example of a Scheduled Protocol Code Sequence in a Japanese SPS:
Coding Coding Code Value Code Meaning

Scheme Scheme
Designator Version
JJ1017T 1.0 GX.01.00 Radiography – General Radiography – NOS
JJ1017P 1.0 25.6.201 Chest – Respiratory System – Lung
JJ1017D 1.0 G-5200 Anterior to posterior
JJ1017D 1.0 G-A101 Left lateral
This SPS schedules 2 exposures: Chest AP and Chest LL
NX 2.0.8000/3.0.8000 can be configured for the use of the Japanese system of Protocol
Codes (JJ1017) by means of the "Workstation Service & Configuration Tool".
7
See guidelines of the JIRA and JAHIS [JAPAN].
HE/001261 Page 59 of 87
2.4.1.2.2.2 Configuration of RIS Mapping

RIS mapping defines how incoming worklist attributes from the RIS are mapped to the SPS
elements.
With RIS mapping, the incoming SPS attributes of the RIS are mapped to the internal data
structure of NX 2.0.8000/3.0.8000. Standard the system will provide a default (1:1) mapping.
However in cases where the RIS sends out the RIS data in a non DICOM conformant way,
the customization of the mapping needs to be done by the operator. This can be done in the
"Workstation Service & Configuration Tool".
2.4.1.2.3 MPPS
MPPS reporting can be enabled/ disabled by the operator.
The "Workstation Service & Configuration Tool" must be used to set the AE Title, port-
number, host-name and capabilities of the remote MPPS SCP. Only one single remote
MPPS SCP can be defined at a time.
2.4.1.2.4 Printing
The "Workstation Service & Configuration Tool" must be used to set the AE Titles, port-
numbers, host-names and capabilities for the printers. Only the supported printers can be
configured. Multiple printers can be defined.
The DICOM attributes per printer that are configurable are defined in Table 2.2-24, Table
2.2-27 and Table 2.2-29
Additionally, the following parameters can be configured:
Table 2.4-4: Configurable Printer parameters.
Parameter Configurable (yes/no)

Name Yes
Description Yes
Use N-Events Yes
IP Address Yes
Port Number Yes
AE Title Yes
SSL Enabled Yes
HE/001261 Page 60 of 87
2.4.1.3 Queue Management & Job description
2.4.1.4 DICOM Store AE
2.4.1.4.1 Queue description

Each Remote Store AE destination has its own configuration (as described in § 2.4.1.2.1)
and queue. For each destination, a different retry policy can be configured.
It is possible to configure the rerouting of a DICOM Store queue. A typical example for when
this is needed is a PACS that is temporarily down. The queue can be rerouted to a web
server. This web server will then later on forward the images to the PACS. A DICOM Store
queue can only be rerouted to another DICOM Store queue with:
- The same output type configured (this includes the SOP class to be used)
- The same GSPS support
If the new destination is configured for Storage Commitment, the storage commit request will
be sent to the new destination when processing the job.
By means of a SENT-flag, an image that has already been successfully sent to a specific
archive cannot be sent to that archive twice. The SENT-flag can be applied to all DICOM
store destinations, including both the archive and the other softcopy destinations (e.g.
viewing stations).
2.4.1.4.2 Job description

One archive job can contain multiple images. All these images and their GSPS’s will be sent
to the archive through a single association.
The user can perform the following actions on existing jobs: “Delete job” and “Expedite job”
When an image in the archive job does not reach its destination, or when the storage
commit replies “time out”, the job is FAILED.
2.4.1.5 DICOM Print AE

There is only one entry per print job (with possible multiple sheets) in the queue.
All queue actions are done on one print job: retry, reprint, expedite, …
HE/001261 Page 61 of 87
2.4.2 Parameters
The specification of important operational parameters, and if configurable, their default value
and range, are specified in the table below.
The parameters that apply to all Application Entities are specified in the “General
Parameters” section. Those specific to particular Applications are specified in separate
sections specific to each AE.
Table 2.4-5: Configurable Parameters for NX 2.0.8000/3.0.8000.
Parameter Configurable Default value

(yes/no)
General Parameters
Max PDU Receive Size No 65542
Max PDU Send Size (larger PDUs will never be sent, even if the
receiver supports a larger Max PDU Receive Size. If the
receiver supports a smaller Max PDU Receive Size then the
Max PDU Send Size will be reduced accordingly for the
No 65542
duration of the Association. Max PDU Receive Size information
is exchanged during DICOM Association Negotiation in the
Maximum Length Sub-Item of the A-ASSOCIATION-RQ and A-
ASSOCIATE-AC)
Time-out waiting for an acceptance or rejection response to an
No 15 minutes
Association Request (Application Level Timeout)
Time-out waiting for a response to an Association release
No 15 minutes
request (Application Level Timeout)
Time-out waiting for completion of a TCP/IP connect request
No 100 seconds
(Low-level timeout)
Time-out awaiting a Response to a DIMSE Request (Low-Level
No 100 seconds
Timeout)
Time-out for waiting for data between TCP/IP-packets (Low
No 100 seconds
Level Timeout)
Storage parameters
Storage SCU time-out waiting for a response to a C-STORE-RQ No 15 minutes

Manually: There’s no
restriction of the number of
Number of times a failed send job may be retried No
retires of failed jobs as long
as they aren’t deleted.
Delay between retrying failed send jobs No N/A
Supported Transfer Syntaxes (separately configurable for each
Yes
remote AE)
Secure DICOM (SSL) Yes
Is Archive?8 Yes
Storage Commit Parameters
Enable Storage Commit Yes
Enable secure DICOM Connection Yes
Timeout waiting for a Storage Commitment Notification

(maximum duration of applicability for a Storage Commitment Yes
Transaction UID).
8
If yes, images sent to this destination will be referenced in the MPPS.
HE/001261 Page 62 of 87
Parameter Configurable Default value

(yes/no)
Modality Worklist Parameters
Modality Worklist SCU time-out waiting for the final response to
a C-FIND-RQ No 15 minutes
Maximum number of Worklist Items No 400

Implicit VR Little Endian
Supported Transfer Syntaxes for Modality Worklist No
Delay between automatic Worklist Updates Yes
MPPS Parameters
Enable MPPS Reporting Yes
MPPS SCU time-out waiting for a response to a N-CREATE-RQ No 15 minutes
MPPS SCU time-out waiting for a response to a N-SET-RQ No 15 minutes

Implicit VR Little Endian
Supported Transfer Syntaxes for MPPS No
Print Parameters
Print SCU time-out waiting for a response to a N-CREATE-RQ No 10 minutes
Print SCU time-out waiting for a response to a N-SET-RQ No 10 minutes
Print SCU time-out waiting for a response to a N-ACTION-RQ No 10 minutes

Supported Transfer Syntaxes (separately configurable for each Taken from printer device
No
remote printer) model provided by Agfa.
Number of times a failed print-job may be retried No Automatically : 8 times
2 times immediately, then the
job gets parked for 3 minutes
and retried 3 times again. In
Delay between retrying failed print-jobs No case the job still fails, it is
parked for 5 minutes and
retried 3 times.
Print SCU time-out waiting for a response to a N-CREATE-RQ No 10 minutes
HE/001261 Page 63 of 87
3 MEDIA INTERCHANGE
NX 2.0.8000/3.0.8000 is able to create or read DICOM Interchange media. The related
capabilities are described in the following sections.
3.1 Implementation Model
Offline-Media Application CD-R

Export To CD-R Export
Entity Storage Medium
Figure 3.1-1: Application Data Flow Diagram for Media Storage
The Offline-Media Application Entity exports DICOM images and Presentation States to a
CD-R Storage medium. It is associated with the local real-world activity “Export Images”.
“Export Images” is performed upon user request.
3.1.2 Functional Definition of AEs
3.1.3 Sequencing of Real World Activities
At least one image or presentation state must exist and be selected before the Offline-Media
Application Entity can be invoked. The Offline-Media Application Entity is invoked through
the local real-world activity “Export Images”.
The operator must insert a new (blank) CD-R media before invocation of the Offline-Media
Application Entity. If no CD-R is inserted, the Offline-Media Application Entity will prompt for
a media to be inserted before starting to write to the CD-R device. The export job can be
canceled from the job queue by clicking “Cancel” on this prompt.
Processed Images are exported in standard DICOM format. A Dicom Viewer is burned with
the images on the CD, to view these images later on. The images can be read by any Dicom
Compatible application.
Export to a hard disk is NOT supported by NX 2.0.8000/3.0.8000.
3.1.4 File Meta Information for Implementation Class and Version

The implementation information written to the File Meta Header in each file is:
Table 3.1-1: File Meta Implementation Class and Version Name

Implementation Version Name AGFA DTF1.0.XX9
9
XX is the build version number.
HE/001261 Page 64 of 87
3.2 AE Specifications
3.2.1 Offline-Media Application Entity Specification
The Offline-Media Application Entity provides standard conformance to the DICOM

Interchange Option of the Media Storage Service Class. The Application Profiles and roles
are listed below:
Table 3.2-1: AE Related Application Profiles, Real World Activities and Roles
Application Profile Supported Real-World Activity Roles SC Option
Portable data for imaging Export to CD-R FSC (creation of a File-Set) Interchange
3.2.1.1 Real World Activities
3.2.1.1.1 Real World Activity - Export to CD-R
The Offline-Media Application Entity acts as an FSC using the interchange option when
requested to export SOP Instances from the local database to a CD-R medium. If the current
contents selection does not fit on a single media, an error message is displayed and the
export will fail. The user will be prompted to insert an empty CD-R for each export job. The
contents of the export job will be written together with a corresponding DICOMDIR, which is
placed in the root directory, to a single-session CD-R. Writing in multi-session mode is
supported. The user can cancel an export job in the job queue.
The file names and directory names may reflect the patient name or ID if necessary, but in
case the operator selects “anonymous export” these names and IDs should not refer to the
actual patient. The aim of anonymous export is that any data, which could be used to derive
the identity of the patient, is removed from the image. This includes all dates, UID and other
ID’s, patient related information and all related physician’s names. All attributes from the
following modules are therefore blanked:
- Patient
- Patient Study
- Patient Medical
- General Study
- General Series
- DX Series
- SOP Common
- General Image
Exceptions exist for attributes which are necessary to correctly import or interpret the image.
Therefore the following values are kept or replaced by generated values:
Table 3.2-2: Necessary Values when performing an Anonymous Export.
Attribute Tag Set to …

Patient’s Name (0010,0010) “Anonymous”
Study Instance UID (0020,000D) Keep value
Modality (0008,0060) Keep value
Series Instance UID (0020,000E) Keep value
HE/001261 Page 65 of 87
Attribute Tag Set to …

Laterality (0020,0060) Keep value
Series description (0008,103E) Keep value
Protocol name (0018,1030) Keep value
Body Part Examined (0018,0015) Keep value
Smallest Pixel Value in Series (0028,0108) Keep value
Largest Pixel Value in Series (0028,0109) Keep value
Presentation Intent Type (0008,0068) Keep value
SOP Instance UID (0008,0018) Keep value
SOP Class UID (0008,0016) Keep value
Specific character set (0008,0005) Keep value
Patient Orientation (0020,0020) Keep value
Image type (0008,0008) Keep value
Image comments (0020,4000) Keep value
Presentation LUT shape (2050,0020) Keep value
3.2.1.1.1.1 Media Storage Application Profile
The Offline-Media Application Entity supports the STD-GEN-CD Application Profile.
3.2.1.1.1.1.1 Options
The Offline-Media Application Entity supports the SOP Classes and Transfer Syntaxes listed
in the Table below:
Table 3.2-3: IOD’S, SOP Classes and Transfer syntaxes for offline media
IOD SOP Class UID Transfer Syntax Transfer Syntax UID
CR Image Storage 1.2.840.10008.5.1.4.1.1.1 Explicit VR Little Endian 1.2.840.10008.1.2.1
Digital X-Ray Image

1.2.840.10008.5.1.4.1.1.1.1 Explicit VR Little Endian 1.2.840.10008.1.2.1
Storage – For Presentation
Digital X-Ray Image

1.2.840.10008.5.1.4.1.1.1.1.1 Explicit VR Little Endian 1.2.840.10008.1.2.1
Storage – For Processing
Grayscale Softcopy
1.2.840.10008.5.1.4.1.1.11.1 Explicit VR Little Endian 1.2.840.10008.1.2.1
Presentation State Storage
Digital Mammography
Image Storage – For 1.2.840.10008.5.1.4.1.1.1.2 Implicit VR Little Endian 1.2.840.10008.1.2
Presentation
Digital Mammography
Image Storage – For 1.2.840.10008.5.1.4.1.1.1.2.1 Implicit VR Little Endian 1.2.840.10008.1.2
Processing
HE/001261 Page 66 of 87
3.3 Media Configuration
The Source AE Title in the File Meta Information is the AE Title that can be configured in the
General Settings in the "Workstation Service & Configuration Tool".
HE/001261 Page 67 of 87
4 SUPPORT FOR EXTENDED CHARACTER SETS
NX 2.0.8000/3.0.8000 supports the following character sets:
 ISO-IR 6 (default) Basic G0 Set

 ISO-IR 100 Latin Alphabet No. 1
 ISO-IR 126 Greek
 ISO-IR 144 Cyrillic
 ISO-IR 127 Arabic
 ISO-IR 13 Japanese
 ISO-IR 138 Hebrew
Chinese Character Sets
 GB18030 GB18030-2000
 ISO 2022 B5 Big 5
 ISO 2022 GBK GB 2313-80
Japanese Character Sets
 ISO 2022 IR 87 ASCII and Kanji
 ISO 2022 IR 13 Katakana, Roman and Kanji
ISO 2022 IR 87
 ISO 2022 IR 159 Japanese suppl. Kanji
Other Character Sets
 ISO 2022 IR 126 Greek
 ISO 2022 IR 144 Cyrillic
 ISO 2022 IR 138 Hebrew
 ISO 2022 IR 149 Korean
 ISO 2022 IR 127 Arabic
 ISO 2022 IR 100 Latin alphabet No 1
 UTF-8 Unicode
HE/001261 Page 68 of 87
5 SECURITY
5.1 Security Profiles

The workstation supports the following profiles:
 Basic TLS Secure Transport Connection Profile

 Basic Network Address Management Profile
 Basic Time synchronization Profile
5.2 Association Level Security

NX 2.0.8000/3.0.8000 supports secure associations using TLS. Associations are only
allowed to be opened when they are received from an AE title that is known to the
Workstation (i.e. the specific AE title has been configured in the "Workstation Service &
Configuration Tool".).
5.3 Application Level Security

NX 2.0.8000/3.0.8000 supports application level security by means of role based access
control. These user roles are associated to the Windows XP users. In the "Workstation
Service & Configuration Tool", user roles can be assigned to certain accounts. Some of the
user roles can be modified or new ones can be created by a user with the appropriate rights.
By default the workstation will be configured to automatically log the current user out after a
certain period of non-activity.
Audit logging to an external repository is supported.
NX 2.0.8000/3.0.8000 can be configured to get its time from an NTP-server.

HE/001261 Page 69 of 87
6 ANNEXES
6.1 IOD Contents
6.1.1 Created SOP Instances

The following tables use a number of abbreviations. The abbreviations used in the
“Presence of Value”- column, are:
 VNAP Value Not Always Present (attribute sent zero length if no value is present)
 ANAP Attribute Not Always Present
 ALWAYS Always Present with a value
 EMPTY Attribute is sent without a value
The abbreviations used in the “Source”-column:
 USER the attribute value source is from User input

 AUTO the attribute value is generated automatically
 MWL the attribute value is the value received from the Modality Worklist
 CONFIG the attribute value source is a configurable parameter
6.1.1.1 Common Modules

Table 6.1-1: Common Modules
Presence of
Attribute Name Tag VR Value Source
Value
Patient
Patient Identification
Patient's Name (0010,0010) PN VNAP User / MWL
Patient ID (0010,0020) LO VNAP User / MWL
Issuer of Patient ID (0010,0021) LO ANAP MWL
Other Patient IDs (0010,1000) LO ANAP MWL
Other Patient Names (0010,1001) PN ANAP MWL
Patient’s Birth Name (0010,1005) PN ANAP MWL
Patient’s Mother’s Birth Name (0010,1060) PN ANAP MWL
Medical Record Locator (0010,1090) LO ANAP MWL
Patient Demographic
Patient’s Age (0010,1010) AS ANAP User / MWL
Occupation (0010,2180) SH ANAP MWL
Confidentiality Constraint on Patient
Data Description (0040,3001) LO ANAP MWL
Patient's Birth Date (0010,0030) DA VNAP User / MWL
Patient’s Birth Time (0010,0032) TM VNAP User / MWL
Patient's Sex (0010,0040) CS VNAP User / MWL
Patient's Insurance Plan Code
Sequence (0010,0050) SQ ANAP MWL
> Code Sequence
> Patient’s Primary Language Code (0010,0102) SQ ANAP MWL
HE/001261 Page 70 of 87
Presence of
Value
Modifier Sequence
>> Code Sequence
Patient's Size (0010,1020) DS ANAP User / MWL
Patient's Weight (0010,1030) DS ANAP User / MWL
Patient’s Address (0010,1040) LO ANAP MWL
Military Rank (0010,1080) LO ANAP User / MWL
Branch of Service (0010,1081) LO ANAP User / MWL
Country of Residence (0010,2150) LO ANAP MWL
Region of Residence (0010,2152) LO ANAP MWL
Patient’s Telephone Numbers (0010,2154) SH ANAP MWL
Ethnic Group (0010,2160) SH ANAP User / MWL
Patient's Religious Preference (0010,21F0) LO ANAP MWL
Patient Comments (0010,4000) LT ANAP User / MWL
Visit Status
Referenced Patient Sequence (0008,1120) SQ ANAP MWL
>Referenced SOP Class UID (0008,1150) UI ANAP MWL
>Referenced SOP Instance UID (0008,1155) UI ANAP MWL
Visit Status ID (0038,0008) CS ANAP MWL
Current Patient Location (0038,0300) LO ANAP MWL
Patient’s Institution Residence (0038,0400) LO ANAP MWL
Visit Comments (0038,4000) LT ANAP Auto
Patient Medical
Medical Alerts (0010,2000) LO ANAP MWL
Contrast Allergies (0010,2110) LO ANAP MWL
Smoking Status (0010,21A0) CS ANAP User / MWL
Pregnancy Status (0010,21C0) US ANAP User / MWL
Last Menstrual Date (0010,21D0) DA ANAP User / MWL
Special Needs (0038,0050) LO ANAP MWL
Patient State (0038,0500) LO ANAP MWL
Additional Patient’s History (0010,21B0) LT ANAP MWL
Study
General Study
Study Instance UID (0020,000D) UI ALWAYS MWL / Auto
Study Date (0008,0020) DA ALWAYS Auto
Study Time (0008,0030) TM ALWAYS Auto
Referring Physician's Name (0008,0090) PN VNAP User / MWL
Referring Physician Identification
Requested Procedure ID
or generated for
unscheduled (app A IHE
Study ID (0020,0010) SH note 5) ALWAYS Auto / MWL
Accession Number (0008,0050) SH VNAP User / MWL
Performed Procedure
Study Description (0008,1030) LO step Description ANAP Auto
Physician(s) of Record (0008,1048) PN ANAP MWL
Physician(s) of Record Identification
Name of Physician(s) Reading
Study (0008,1060) PN ANAP MWL
HE/001261 Page 71 of 87
Presence of
Value
Physician(s) Reading Study
Identification Sequence (0008,1062) ANAP User
Referenced Patient Sequence (0008,1120) SQ ANAP MWL
>Referenced SOP Class UID (0008,1150) UI ANAP MWL
>Referenced SOP Instance UID (0008,1155) UI ANAP MWL
Procedure Code Sequence (0008,1032) SQ ANAP MWL
Patient Study
Admitting Diagnoses Description (0008,1080) LO ANAP MWL
Admitting Diagnoses Code
Patient’s Age (0010,1010) AS ANAP User / MWL
Patient's Size (0010,1020) DS ANAP User / MWL
Patient's Weight (0010,1030) DS ANAP User / MWL
Occupation (0010,2480) SH ANAP MWL
Additional Patient’s History (0010,21B0) LT ANAP MWL
Series
General Series
Config,
>Archive settings
Modality (0008,0060) CS ALWAYS SOP Class
Series Instance UID (0020,000E) UI Different for each image ALWAYS Auto
Series Number (0020,0011) IS ALWAYS Auto
Laterality (0020,0060) CS Based on protocol code ALWAYS User / Auto
Performing Physicians’ Name (0008,1050) PN ANAP User
Performing Physician’s Identification
Protocol Name (0018,1030) LO ANAP Auto
Series Description (0008,103E) LO Exposure Type Name ALWAYS Auto
Depending on security
setting either auto filled
Operators' Name (0008,1070) PN in with login ALWAYS User / Auto
Referenced Performed Procedure
Step Sequence (0008,1111) SQ ANAP Auto
>Referenced SOP Class UID (0008,1150) UI ANAP Auto
>Referenced SOP Instance UID (0008,1155) UI ANAP Auto
Patient Position (0018,5100) CS Empty ANAP
Smallest Pixel Value in Series (0028,0108) US NEVER
Largest Pixel Value in Series (0028,0109) US NEVER
Request Attributes Sequence (0040,0275) SQ ANAP MWL
>Requested Procedure ID (0040,1001) SH ANAP MWL
>Reason for the Requested
Procedure (0040,1002) LO
>Reason for Requested Procedure
Code Sequence (0040,100A) SQ Screening/Diagnostic
>Scheduled Procedure Step ID (0040,0009) SH ANAP MWL
>Scheduled Procedure Step
Description (0040,0007) LO ANAP MWL
HE/001261 Page 72 of 87
Presence of
Value
>Scheduled Protocol Code
10
>> Protocol Context Sequence (0040,0440) SQ
>>>Content Item Modifier Sequence (0040,0441) SQ

Performed Procedure Step ID (0040,0253) SH ANAP Auto
Exam group
names of
Performed Procedure Step exposures in
Description (0040,0254) LO the study Auto
Performed Procedure Step Start
Date (0040,0244) DA Auto
Performed Procedure Step Start
Time (0040,0245) TM Auto
Comments on the Performed
Procedure Step (0040,0280) LO ANAP Auto
Equipment
General Equipment
Station Name (0008,1010) SH Auto
Institution Name (0008,0080) LO ANAP MWL/ Config
Institution Address (0008,0081) ST ANAP MWL /Config
Institutional Department Name (0008,1040) LO ANAP MWL/ Config
Auto (from
Manufacturer (0008,0070) LO ALWAYS digitizer)
Auto (from
Manufacturer’s Model Name (0008,1090) LO ALWAYS digitizer)
Device Serial Number (0018,1000) LO ALWAYS Auto
Gantry ID (0018,1008) LO ALWAYS Auto
Software Versions (0018,1020) LO ANAP Auto
Image
General Image
Instance Number (0020,0013) CS ALWAYS Auto
Patient Orientation (0020,0020) IS ALWAYS Auto
Content Date (0008,0023) DT VNAP Auto
Content Time (0008,0033) TM VNAP Auto
Image Type (0008,0008) CS ALWAYS Auto
Acquisition Number (0020,0012) IS ANAP Auto
Acquisition Date (0008,0022) DA ALWAYS Auto / User
Acquisition Time (0008,0032) TM ALWAYS Auto / User
Acquisition Datetime (0008,002A) DT ALWAYS Auto
Referenced Image Sequence (0008,1140) SQ ANAP
> Referenced SOP Class UID (0008,1150) UI ANAP
> Referenced SOP Instance UID (0008,1155) UI ANAP
> Referenced Frame Number (0008,1160) IS ANAP
> Purpose of Reference Code
Sequence (0040,A170) SQ ANAP
Derivation description (0008,2111) ST ANAP Auto
10
The following rules are applicable for DICOM:
- When 0008,0102 was not supplied by the RIS, its value will be "UNKNOWN".
HE/001261 Page 73 of 87
Presence of
Value
Source Image Sequence (0008,2112) SQ ANAP Auto
> Referenced SOP Class UID (0008,1150) UI
> Referenced SOP Instance UID (0008,1155) UI
> Referenced Frame Number (0008,1160) IS
Sequence (0040,A170) SQ
Sequence (0040,A170) SQ ANAP Auto
Image Comments (0020,4000) LT ANAP User
When exposure is
defined as QC in study
Quality Control Image (0028,0300) CS tree ANAP Auto
Burned in Annotation (0028,0301) CS No ALWAYS Fixed
Lossy Image Compression (0028,2110) CS EMPTY Empty
Lossy Image Compression Ratio (0028,2112) DS ANAP Auto
Lossy Image Compression Method (0028,2114) CS ANAP Auto
Presentation LUT Shape (2050,0020) CS ALWAYS Config
EI (0019,10FA) IS ANAP Config
DI (0019,10FB) FL ANAP Config
TEI (0019,10FC) IS ANAP Config
Image Pixel
Samples per Pixel (0028,0002) US 1 ALWAYS Fixed
11
Photometric Interpretation (0028,0004) CS M1 or M2 ALWAYS Auto
Rows (0028,0010) US ALWAYS Auto
Columns (0028,0011) US ALWAYS Auto
Pixel Aspect Ratio (0028,0034) IS ANAP Auto
Bits Allocated (0028,0100) US ALWAYS Auto
Bits Stored (0028,0101) US ALWAYS Auto
High Bit (0028,0102) US ALWAYS Auto
12
Pixel Representation (0028,0103) US ALWAYS Auto
Pixel Data (7FE0,0010) OB ALWAYS Auto
SOP Common
SOP Class UID (0008,0016) UI ALWAYS Fixed
SOP Instance UID (0008,0018) UI ALWAYS Auto
Specific Character Set (0008,0005) CS ANAP Config
Instance Creation Date (0008,0012) DA ALWAYS Auto
Instance Creation Time (0008,0013) TM ALWAYS Auto
Instance Number (0020,0013) IS ALWAYS Auto
Private attributes
Only available in case
that the image was
scanned using a non-
Plate sensitivity (0019,10F6) DS Compact family digitizer. ANAP Auto
Only available in case
that the image was
scanned using a non-
Plate erasability (0019,10F7) DS Compact family digitizer. ANAP Auto
Requested Procedure Description (0032,1060) LO ANAP Manual/MWL
11
Fixed M1 when using DX for Processing
12
Depends on digitizer type. In case of DX for Processing, the pixel representation is fixed 0
HE/001261 Page 74 of 87
6.1.1.2 CR
6.1.1.2.1 CR Image IOD

Table 6.1-2: IOD of Created CR Image SOP Instances
IE Module Reference Presence of Module

Patient Patient Identification Table 6.1-1 ALWAYS
Extended Patient Table 6.1-1 If received from MWL
Study General Study Table 6.1-1 ALWAYS
Patient Study Table 6.1-1 ALWAYS
Series General Series Table 6.1-1 ALWAYS
CR Series Table 6.1-3 ALWAYS
Equipment General Equipment Table 6.1-1 ALWAYS
Image General Image Table 6.1-1 ALWAYS
Image Pixel Table 6.1-1 ALWAYS
CR Image Table 6.1-3 ALWAYS
Modality LUT Table 6.1-3 ALWAYS
VOI LUT Table 6.1-3 ALWAYS
SOP Common Table 6.1-1 ALWAYS
6.1.1.2.2 CR Modules
Table 6.1-3: CR Modules of Created SOP Instances
Presence
of Value
Series
CR Series
View Position (0018,5101) CS Based on protocol code ALWAYS Auto / User
0 to 1 (mm), 0 = small
(1)
Focal Spot (0018,1190) DS focus, 1 = large focus Auto/XRDI
Filter Type (0018,1160) SH Auto
Body Part Examined (0018,0015) CS Based on protocol code ALWAYS Auto / User
Collimator/ Grid Name (0018,1180) SH
Plate Type (0018,1260) SH ALWAYS Auto
Phosphor Type (0018,1261) LO ANAP Auto
Image
CR Image
Fixed per
Photometric Interpretation (0028,0004) CS ALWAYS archive model
KVP (0018,0060) DS ANAP (1) Auto
Plate ID (0018,1004) LO ALWAYS Auto
Distance Source to Detector (0018,1110) DS ANAP (1) Auto
(1)
Distance Source to Patient (0018,1111) DS ANAP Auto
Exposure Time (0018,1150) IS ANAP (1) Auto
X-Ray Tube Current (0018,1151) IS ANAP (1) Auto
(1)
Exposure (0018,1152) IS ANAP Auto
Exposure in µAs (0018,1153) IS ANAP (1) Auto
Imager Pixel Spacing (0018,1164) DS ALWAYS Auto
Pixel Spacing (0028,0030) DS ALWAYS Auto
(1)
Generator Power (0018,1170) IS ANAP Auto
HE/001261 Page 75 of 87
Presence
of Value
Acquisition Device Processing
Description (0018,1400) LO ANAP Auto
Code (0018,1401) LO ANAP Auto
Cassette Orientation (0018,1402) CS ALWAYS Auto / User
Cassette Size (0018,1403) CS ALWAYS Auto
Lgm value multiplied by
Relative X-Ray Exposure (0018,1405) IS 100 ANAP Auto
Sensitivity (0018,6000) DS ALWAYS Config / User
Modality LUT
Modality LUT Sequence (0028,3000) SQ ANAP Auto
> LUT Descriptor (0028,3002) SS ANAP Auto
> LUT Explanation (0028,3003) LO ANAP Auto
> Modality LUT Type (0028,3004) LO
> LUT Data (0028,3006) SS ANAP Auto
Rescale Intercept (0028,1052) DS ANAP Auto
Rescale Slope (0028,1053) DS ANAP Auto
Rescale Type (0028,1054) LO ANAP Auto
VOI LUT
VOI LUT Sequence (0028,3010) SQ ANAP Config
> LUT Descriptor (0028,3002) SS ANAP Auto
> LUT Explanation (0028,3003) LO ANAP Auto
> LUT Data (0028,3006) SS ANAP Auto
Window Center (0028,1050) DS ANAP Auto
Window Width (0028,1051) DS ANAP Auto
Window Center & Width
Explanation (0028,1055) LO ANAP Auto
6.1.1.3 DX
6.1.1.3.1 DX Image IOD

Table 6.1-4: IOD of Created DX Image SOP Instances

DX Series Table 6.1-5 ALWAYS
Display Shutter Table 6.1-5 When shutter is applied
DX Anatomy Table 6.1-5 ALWAYS
DX Image Table 6.1-5 ALWAYS
DX Detector Table 6.1-5 ALWAYS
X-Ray acquisition dose Table 6.1-5 When the XRDI Module is installed
X-Ray Collimator Table 6.1-5 When the XRDI Module is installed
HE/001261 Page 76 of 87

DX Positioning Table 6.1-5
Acquisition Context Table 6.1-5 ALWAYS
6.1.1.3.2 DX Modules
Table 6.1-5: DX Module of Created SOP Instances
Presence
of Value
Series
DX Series
Modality (0008,0060) CS DX ALWAYS Config
Referenced Performed Procedure
Step Sequence (0008,1111) SQ ANAP Auto
> Referenced SOP Class UID (0008,1150) UI ANAP Auto
> Referenced SOP Instance UID (0008,1155) UI ANAP Auto
For Processing/For
Presentation Intent Type (0008,0068) CS Presentation ALWAYS Config
Image
Display Shutter
Shutter Shape (0018,1600) CS ANAP User
Shutter Left Vertical Edge (0018,1602) IS ANAP User
Shutter Right Vertical Edge (0018,1604) IS ANAP User
Shutter Upper Horizontal Edge (0018,1606) IS ANAP User
Shutter Lower Horizontal Edge (0018,1608) IS ANAP User
Shutter Presentation Value (0018, 1622) US ANAP User
DX Anatomy
Anatomic Region Sequence (0008,2218) SQ ANAP Config / User
> Anatomic Region Modifier
Sequence (0008,2220) SQ ANAP Config
Image Laterality (0020,0062) CS ALWAYS Config / User
DX Image
ORIGINAL when coming
from a digitizer, DERIVED
when the image comes
from a Save as new.
The sub-attribute IOD

Specific Characteristics is
filled in with the exposure
type name for QA images
Image Type (0008,0008) CS (used by Auto-QC2). ALWAYS Auto
Samples per Pixel (0028,0002) US ALWAYS Auto
Photometric Interpretation (0028,0004) CS ALWAYS Config
Bits Allocated (0028,0100) US ALWAYS Auto
Bits Stored (0028,0101) US ALWAYS Auto
High Bit (0028,0102) US ALWAYS Auto
Pixel Representation (0028,0103) US ALWAYS Auto
Pixel Intensity Relationship (0028,1040) CS ALWAYS Auto
Pixel Intensity Relationship Sign (0028,1041) SS ALWAYS Auto
HE/001261 Page 77 of 87
Presence
of Value
Rescale Intercept 13 (0028,1052) DS 0 and 1 ALWAYS Config
Rescale Slope 13 (0028,1053) DS 0 and 1 ALWAYS Config
Rescale Type (0028,1054) LO ALWAYS Config
Presentation LUT Shape (2050,0020) CS IDENTITY ALWAYS Fixed
Lossy Image Compression (0028,2110) CS 00 ALWAYS Fixed
Lossy Image Compression Ratio (0028,2112) DS ANAP Auto
Derivation Description (0008,2111) ST ANAP Auto
Description (0018,1400) LO ANAP Auto
Code (0018,1401) LO ANAP Auto
Patient Orientation (0020,0020) CS ALWAYS Auto
Calibration Image (0050,0004) CS ANAP Config
Burned in Annotation (0028,0301) CS YES ALWAYS Fixed
VOI LUT Sequence (0028,3010) SQ ANAP Auto
>LUT Descriptor (0028,3002) SS ANAP Auto
>LUT Explanation (0028,3003) LO ANAP Auto
>LUT Data (0028,3006) SS ANAP Auto
DX Detector
Detector Type (0018,7004) CS ANAP Auto
(1)
Detector Configuration (0018,7005) CS ANAP Auto
For the DX/S family of
digitizers:
0 = Phosphor IP
1 = Needle IP
For the ADC Compact

family of digitizers:
- Label of the type of
storage phosphor plates
Detector Description (0018,7006) LT (e.g. MD10) ALWAYS Auto
(1)
Detector Mode (0018,7008) LT ANAP Auto
For the DX/S family of
digitizers, this is the
Image plate ID.
For the ADC Compact

family of digitizers, this is
Detector ID (0018,700A) SH the cassette ID. ALWAYS Auto
Date of Last Detector Calibration (0018,700C) DA ANAP Auto
Exposures on Detector Since Last
Calibration (0018,7010) IS ANAP Auto
Exposures on Detector Since
Manufactured (0018,1404) IS ANAP Auto
Detector Time Since Last
(1)
Exposure (0018,7012) DS ANAP Auto
Detector Active Time (0018,7014) DS ANAP (1) Auto
13
Fixed when using DX for Processing
HE/001261 Page 78 of 87
Presence
of Value
Detector Activation Offset From
Exposure (0018,7016) DS ANAP (1) Auto
(1)
Detector Binning (0018,701A) DS ANAP Auto
Detector Manufacturer Name (0018,702A) LO ANAP (1) Auto
Detector Manufacturer’s Model
Name (0018,702B) LO ANAP (1) Auto
(1)
Detector Conditions Nominal Flag (0018,7000) CS ANAP Auto
(1)
Detector temperature (0018,7001) DS ANAP Auto
Sensitivity (0018,6000) DS ALWAYS Config / User
Field of View Shape (0018,1147) CS ANAP (1) Auto
Field of view Dimension(s) (0018,1149) IS ANAP (1) Auto
(1)
Field of View Origin (0018,7030) DS ANAP Auto
Field of View Rotation (0018,7032) DS ANAP User
Field of View Horizontal Flip (0018,7034) CS ANAP User
Imager Pixel Spacing (0018,1164) DS ALWAYS Auto
Pixel Spacing (0028,0030) DS ALWAYS Auto
Detector Element Physical Size (0018,7020) DS ANAP Auto
Detector Element Spacing (0018,7022) DS ANAP Auto
Detector Active Shape (0018,7024) CS RECTANGLE ALWAYS Fixed
Cassette size translated
Detector Active Dimension(s) (0018,7026) DS into MM ALWAYS Auto
Detector Active Origin (0018,7028) DS ANAP Auto
X-Ray Collimator
Collimator Shape (0018,1700) CS ANAP Auto / User
Collimator Left Vertical Edge (0018,1702) IS ANAP Auto / User
Collimator Right Vertical Edge (0018,1704) IS ANAP Auto / User
Collimator Upper Horizontal Edge (0018,1706) IS ANAP Auto / User
Collimator Lower Horizontal Edge (0018,1708) IS ANAP Auto / User
Center of Circular Collimator (0018,1710) IS ANAP Auto / User
Radius of Circular Collimator (0018,1712) IS ANAP Auto / User
Vertices of the Polygonal
Collimator (0018,1720) IS ANAP Auto / User
DX Positioning
Projection Eponymous Name
Code Sequence (0018,5104) SQ ANAP Auto
Patient Position (0018,5100) CS ANAP User
View Position (0018,5101) CS Based on protocol code ALWAYS Auto / User
View Code Sequence (0054,0220) SQ ANAP Auto
Patient Orientation Code
(1)
Sequence (0054,0410) SQ ANAP Auto
Patient Orientation Modifier Code
(1)
Patient Gantry Relationship Code
(1)
Distance Source to Patient (0018,1111) DS ANAP (1) Auto
Distance Source to Detector (0018,1110) DS ANAP (1) Auto
Estimated Radiographic
(1)
Magnification Factor (0018,1114) DS 0.00 to 9.99 ANAP (1) User/XRDI
(1)
Positioner Type (0018,1508) CS ANAP Auto
(1)
Positioner Primary Angle (0018,1510) DS -180 to +180 (Degree) ANAP (1) User/XRDI
(1)
Positioner Secondary Angle (0018,1511) DS ANAP Auto
HE/001261 Page 79 of 87
Presence
of Value
Detector Primary Angle (0018,1530) DS ANAP (1) Auto
Detector Secondary Angle (0018,1531) DS ANAP (1) Auto
(1)
Body Part Thickness (0018,11A0) DS 0 to 999 (mm) ANAP User/XRDI
(1)
Compression Force (0018,11A2) DS 0 to 99 (kg) ANAP User/XRDI
X-Ray Acquisition dose
(1)
KVP (0018,0060) DS 0 to 99 ANAP (1) User/XRDI
(1)
X-Ray Tube Current (0018,1151) IS ANAP (1) User/XRDI
(1) (1)
X-Ray Tube Current in µA (0018,8151) IS ANAP User/XRDI
(1) (1)
Exposure Time (0018,1150) IS 0 to 99999 (ms) ANAP User/XRDI
(1)
Exposure Time in µs (0018,8150) IS ANAP (1) User/XRDI
(1)
Exposure (0018,1152) IS 0 to 999 ANAP (1) User/XRDI
(1)
Exposure in µAs (0018,1153) IS 0 to 999 ANAP Auto/XRDI
(1)
Distance Source to Detector (0018,1110) DS ANAP (1) User/XRDI
Distance Source to Patient (0018,1111) DS ANAP (1) Auto
(1)
Image Area Dose Product (0018,115E) DS ANAP Auto
(1)
Body Part Thickness (0018,11A0) DS 0 to 999 ANAP (1) User/XRDI
Lgm value multiplied by
Relative X-Ray Exposure (0018,1405) IS 100 ANAP Auto
(1)
Entrance Dose (0040,0302) US ANAP (1) User/XRDI
(1)
Entrance Dose in mGy (0040,8302) US ANAP (1) User/XRDI
Exposed Area (0040,0303) US ANAP (1) Auto
(1)
Distance Source to Entrance (0040,0306) DS ANAP Auto
(1)
Comments on Radiation Dose (0040,0310) ST ANAP Auto
X-Ray Output (0040,0312) DS ANAP (1) Auto
Half Value Layer (0040,0314) DS ANAP (1) Auto
0.0 to 99.9, 100 to 999,
Calculation error = “----“ (4
blanks), >999mGy = “----“
(1)
Organ Dose (0040,0316) DS (4 blanks) ANAP (1) User/XRDI
(1)
Organ Exposed (0040,0318) CS ANAP Auto
(1)
Anode target Material (0018,1191) CS 0 to 1, 0 = W, 1= Mo ANAP (1) User/XRDI
(1) (1)
Filter Material (0018,7050) CS 0 to 1, 0 = Rh, 1= Mo ANAP User/XRDI
Filter Thickness Minimum (0018,7052) DS ANAP (1) Auto
(1)
Filter Thickness Maximum (0018,7054) DS ANAP Auto
0 to 1, 0 = Grid, 1 = No
(1)
Grid (0018,1166) CS Grid ANAP (1) User/XRDI
(1)
Grid Absorbing Material (0018,7040) LT ANAP (1) User/XRDI
(1) (1)
Grid Pitch (0018,7044) DS ANAP User/XRDI
(1)
Grid Thickness (0018,7042) DS ANAP (1) User/XRDI
- Manual
(1) (1)
Exposure Control Mode (0018,7060) CS - Automatic ANAP User/XRDI
Exposure Control Mode
(1) (1)
Description (0018,7062) LT ANAP User/XRDI
(1)
Phototimer Setting (0018,7065) DS ANAP (1) User/XRDI
Image and Fluoroscopy Area
(1) (1)
Dose Product (0018,115E) DS ANAP User/XRDI
(1)
Grid Focal Distance (0018,704C) DS ANAP (1) User/XRDI
(1)
Rectification Type (0018,1156) CS ANAP Auto
VOI LUT
HE/001261 Page 80 of 87
Presence
of Value
Acquisition Context
Acquisition Context Sequence (0040,0555) SQ EMPTY Fixed
> Value Type (0040,A040) CS EMPTY Fixed
> Concept Name Code Sequence (0040,A043) SQ EMPTY Fixed
> Referenced Frame numbers (0040,A136) US EMPTY Fixed
> Numeric Value (0040,A30A) DS EMPTY Fixed
> Measurement Units Code
Sequence (0040,08EA) SQ EMPTY Fixed
> Date (0040,A121) DT EMPTY Fixed
> Time (0040,A122) TM EMPTY Fixed
> Person Name (0040,A123) PN EMPTY Fixed
> Text Value (0040,A160) UT EMPTY Fixed
> Concept Code Sequence (0040,A168) SQ EMPTY Fixed
(2)
Acquisition Context Description (0040,0556) ST ANAP Auto
Private attributes
LANDSCAPE or
Cassette orientation (0019,10F5) CS PORTRAIT ALWAYS Auto
(1)
: Can only be available in case of XRDI. For details on the actual content, please refer to the XRDI Dicom
Conformance statement.
(2)
: Never present
6.1.1.4 MG
6.1.1.4.1 MG Image IOD

Table 6.1-6: IOD of Created MG Image SOP Instances

DX Series Table 6.1-5 ALWAYS
Mammography Series Table 6.1-7 ALWAYS
DX Anatomy Table 6.1-5 ALWAYS
DX Image Table 6.1-5 ALWAYS
DX Detector Table 6.1-5 ALWAYS
HE/001261 Page 81 of 87

X-Ray acquisition dose Table 6.1-5 When the XRDI Module is installed
X-Ray Collimator Table 6.1-5 When the XRDI Module is installed
DX Positioning Table 6.1-5
Mammography Image Table 6.1-7 ALWAYS
Acquisition Context Table 6.1-5 ALWAYS
6.1.1.4.2 MG Modules
Table 6.1-7: MG Module of Created SOP Instances
Presence of
Value
Series
Mammography Series
Modality (0008,0060) CS MG ALWAYS Config
Sequence that contains
attributes from the
Request Attributes Sequence (0040,0275) DS Imaging Service Request ANAP MWL
Equipment
General Equipment
US
or
Pixel Padding Value (0028,0120) SS ANAP Auto
Image
Mammography Image
Mammographic
Positioner Type (0018,1508) CS None Always Auto
Distance Source to detector (0018,1110) DS ANAP Auto
Distance Source to patient (0018,1111) DS ANAP Auto
Positioner Primary Angle (0018,1510) DS ANAP User/XRDI14
Positioner Secondary Angle (0018,1511) DS ANAP User/XRDI14
R = right
L = left
Image Laterality (0020,0062) CS B = both (e.g. cleavage) ALWAYS Auto
Organ Exposed (0040,0318) CS BREAST ALWAYS Auto
YES
Implant Present (0028,1300) DS NO ANAP Config
Config /
View Code Sequence (0054,0220) CS Always User
Config /
View Modifier Code Sequence (0054,0222) SQ ANAP User
Image Pixel
US
or
Pixel Padding Range Limit (0028,0121) SS ANAP Auto
14
Value is supplied by user of XRDI component in case of XRDI configuration
HE/001261 Page 82 of 87
6.1.1.5 GSPS
6.1.1.5.1 GSPS IOD

Table 6.1-8: IOD of Created GSPS SOP Instances

Presentation Series Table 6.1-9 ALWAYS
Image Presentation State Table 6.1-9 ALWAYS
Bitmap Display Shutter Table 6.1-9 When shutter is applied
Overlay Plane Table 6.1-9 When shutter is applied
Displayed Area Table 6.1-9 ALWAYS
Graphic Annotation Table 6.1-9 When graphic annotations are present
Graphic Layer Table 6.1-9 When graphic annotations are present
Modality LUT Table 6.1-9 ALWAYS
Softcopy VOI LUT Table 6.1-9 ALWAYS
Softcopy Presentation
Table 6.1-9 ALWAYS
LUT
Spatial Transformation Table 6.1-9 ALWAYS
6.1.1.5.2 GSPS Modules

Table 6.1-9: GSPS Modules of Created SOP Instances
Presence
of Value
Series
Presentation Series
Modality (0008,0060) CS PR ALWAYS Fixed
Presentation State
Presentation State Identification Module
Instance Number (0020,0013) IS ALWAYS Auto
Content Label (0070,0080) CS GSPS ALWAYS Auto
Content Description (0070,0081) LO Empty Empty
Presentation Creation Date (0070,0082) DA ALWAYS Auto
Presentation Creation Time (0070,0083) TM ALWAYS Auto
Content Creator’s Name (0070,0084) PN VNAP Auto
Presentation State Relationship Module
Referenced Series Sequence (0008,1115) SQ ALWAYS Auto
>Series Instance UID (0020,000E) UI ALWAYS Auto
>Referenced Image Sequence (0008,1140) SQ ALWAYS Auto
>>Referenced SOP Class UID (0008,1150) UI ALWAYS Auto
>>Referenced SOP Instance UID (0008,1155) UI ALWAYS Auto
HE/001261 Page 83 of 87
Presence
of Value
>> Referenced Frame Number (0008,1160) IS ALWAYS Auto
Presentation State Mask
Mask Subtraction Sequence (0028,6100) SQ ANAP Auto
>Mask Operation (0028,6101) CS ANAP Auto
> Contrast Frame Averaging (0028,6112) US ANAP Auto
Recommended Viewing Mode (0028,1090) CS ANAP Auto
Display Shutter
Shutter Shape (0018,1600) CS ANAP User
Shutter Left Vertical Edge (0018,1602) IS ANAP User
Shutter Right Vertical Edge (0018,1604) IS ANAP User
Shutter Upper Horizontal Edge (0018,1606) IS ANAP User
Shutter Lower Horizontal Edge (0018,1608) IS ANAP User
Vertices of the Polygonal Shutter (0018,1620) IS ANAP User
Bitmap Display Shutter
Shutter Shape (0018,1600) CS BITMAP ANAP User
Shutter Presentation Value (0018,1622) US 0 ANAP User
Shutter Overlay Group (0018,1623) US 6000 ANAP Auto
Overlay Plane
Overlay Rows (60xx,0010) US ANAP Auto
Overlay Columns (60xx,0011) US ANAP Auto
Background
Overlay Description (60xx,0022) LO darkening ANAP Auto
Overlay Type (60xx,0040) CS G ANAP Auto
Overlay Subtype (60xx,0045) LO AUTOMATED ANAP Auto
Overlay Origin (60xx,0050) SS 1 ANAP Auto
Overlay Bits Allocated (60xx,0100) US 1 ANAP Auto
Overlay Bit Position (60xx,0102) US 0 ANAP Auto
Overlay Activation Layer (60xx,1001) CS ANAP Auto
Overlay Label (60xx,1500) LO Mask image ANAP Auto
Overlay Data (60xx,3000) OB or OW ANAP Auto
Displayed Area
Displayed Area Selection
Sequence (0070,005A) SQ ALWAYS Auto
>Referenced Image Sequence (0008,1140) SQ ANAP Auto
>>Referenced SOP Class UID (0008,1150) UI ANAP Auto
>>Referenced SOP Instance UID (0008,1155) UI ANAP Auto
>Displayed Area Top Left Hand
Corner (0070,0052) SL ALWAYS Auto
>Displayed Area Bottom Right
Hand Corner (0070,0053) SL ALWAYS Auto
SCALE TO
>Presentation Size Mode (0070,0100) CS FIT ALWAYS Auto
>Presentation Pixel Spacing (0070,0101) DS ALWAYS Auto
> Presentation Pixel Aspect Ratio (0070,0102) IS ANAP Auto
> Presentation Pixel Magnification
Ratio (0070,0103) FL ANAP Auto
Spatial Transformation
Image Rotation (0070,0042) US ANAP User
Image Horizontal Flip (0070,0041) CS ANAP User
HE/001261 Page 84 of 87
Presence
of Value
Graphic Annotation
Graphic Annotation Sequence (0070,0001) SQ ALWAYS User
>Referenced Image Sequence (0008,1140) SQ ALWAYS Auto
>>Referenced SOP Class UID (0008,1150) UI ALWAYS Auto
>>Referenced SOP Instance UID (0008,1155) UI ALWAYS Auto
>>Referenced Frame number (0008,1155) IS
>Graphic Layer (0070,0002) CS ALWAYS Auto
>Text Object Sequence (0070,0008) SQ ANAP Auto
>>Bounding Box Annotation Units (0070,0003) CS PIXEL ANAP Auto
>>Anchor Point Annotation Units (0070,0004) CS PIXEL ANAP Auto
>>Unformatted Text Value (0070,0006) ST ANAP Auto
>>Bounding Box Top Left Hand
Corner (0070,0010) FL ANAP Auto
>>Bounding Box Bottom Right
Hand Corner (0070,0011) FL ANAP Auto
>>Bounding Box Text Horizontal
Justification (0070,0012) CS ANAP Auto
>>Anchor Point (0070,0014) FL ANAP Auto
>>Anchor Point Visibility (0070,0015) CS ANAP Auto
>Graphic Object Sequence (0070,0009) SQ ANAP Auto
>>Graphic Annotation Units (0070,0005) CS ANAP Auto
>>Graphic Dimensions (0070,0020) US ANAP Auto
>>Number of Graphic Points (0070,0021) US ANAP Auto
>>Graphic Data (0070,0022) FL ANAP Auto
>>Graphic Type (0070,0023) CS ANAP Auto
>>Graphic Filled (0070,0024) CS ANAP Auto
Softcopy Presentation LUT
Presentation LUT Shape (2050,0020) CS IDENTITY ALWAYS Auto
Graphic Layer
Graphic Layer Sequence (0070,0060) SQ ALWAYS Auto
>Graphic Layer (0070,0002) CS ALWAYS Auto
>Graphic Layer Order (0070,0062) IS ALWAYS Auto
>Graphic Layer Recommended
Display Grayscale Value (0070,0066) US ANAP Auto
>Graphic Layer Recommended
Display RGB Value (0070,0067) US ANAP Auto
>Graphic Layer Description (0070,0068) LO ANAP Auto
Modality LUT
Rescale Intercept (0028,1052) DS ANAP Auto
Rescale Slope (0028,1053) DS ANAP Auto
Rescale Type (0028,1054) LO ANAP Auto
VOI LUT
HE/001261 Page 85 of 87
6.2 Attribute Mapping

The relationships between attributes received via Modality Worklist, stored in acquired
images and communicated via MPPS are summarized in Table 6.2-1.
Table 6.2-1: Attribute Mapping between Modality Worklist, Image and MPPS
Modality Worklist Image IOD MPPS IOD

Patient Name Patient Name Patient Name
Patient ID Patient ID Patient ID
Patient’s Birth Date Patient’s Birth Date Patient’s Birth Date
Patient’s Sex Patient’s Sex Patient’s Sex
Patient’s Weight Patient’s Weight
Referring Physician’s Name Referring Physician’s Name
---- ---- Scheduled Step Attributes Sequence
Study Instance UID Study Instance UID > Study Instance UID
Referenced Study Sequence Referenced Study Sequence > Referenced Study Sequence
Accession Number Accession Number > Accession Number
---- Request Attributes Sequence ----
Requested Procedure ID > Requested Procedure ID > Requested Procedure ID
Requested Procedure Description > Requested Procedure Description
Scheduled Procedure Step ID > Scheduled Procedure Step ID > Scheduled Procedure Step ID
Scheduled Procedure Step > Scheduled Procedure Step > Scheduled Procedure Step
Description Description Description
Scheduled Protocol Code Sequence > Scheduled Protocol Code Sequence ----
---- Performed Protocol Code Sequence Performed Protocol Code Sequence
---- Study ID Study ID
---- Performed Procedure Step ID Performed Procedure Step ID
---- Performed Procedure Step Start Date Performed Procedure Step Start Date
---- Performed Procedure Step Start Time Performed Procedure Step Start Time
---- Performed Procedure Step Performed Procedure Step
Description Description
---- Comments on the Performed Comments on the Performed
Procedure Step Procedure Step
---- ---- Performed Series Sequence
Scheduled Performing Physician’s Performing Physician’s Name > Performing Physician’s Name
Name
Requested Procedure Code ---- Procedure Code Sequence
Sequence
---- Referenced Study Component ----
Sequence
---- > Referenced SOP Class UID SOP Class UID
---- > Referenced SOP Instance UID SOP Instance UID
---- Protocol Name Protocol Name
HE/001261 Page 86 of 87
6.3 Grayscale Image Consistency
The display monitor attached to NX 2.0.8000/3.0.8000 can be calibrated according to the

Grayscale Standard Display Function (GSDF).
HE/001261 Page 87 of 87
6.4 Veterinary Extensions
This section lists the DICOM attributes that are supported by the NX workstation for the
veterinary market. The attributes have been incorporated based on DICOM correction item
CP-643.
Presence of
Value
Patient
Patient species description (0010,2201) LO User/MWL
Patient breed description (0010,2292) LO ANAP User/MWL
Breed registration sequence (0010,2294) SQ ANAP User/MWL
> Breed registration number (0010,2295) LO User/MWL
> Breed registration code
sequence (0010,2296) SQ User/MWL
Responsible person (0010,2297) PN ANAP MWL
Responsible person Role (0010,2298) PN ANAP MWL
Responsible organization (0010,2299) LO ANAP MWL
Patient’s Sex Neutered (0010,2203) CS ANAP User/MWL
Details as of PDF Creation Date
Document Metadata
001261_NX 2.0.8000/3.0.8000 DICOM Conformance
Title:
Statement
Livelink ID: 27014072
Version#: 4
Version Date: 2009/10/26 01:01 PM CET
Status: Approved on 2009/11/10 08:27 AM CET
Owner: Peter Buytaert (awabr)
Created By: Peter Buytaert (awabr)
Created Date: 2009/02/05 09:01 AM CET
PDF Creation Date: 2009/11/10 08:30 AM CET
This document was approved by:
Signatures:
1. John Gibbs (ambcj) on 2009/11/04 01:27 PM CET

2. Bruno Laffin (nawyv) on 2009/11/09 06:09 PM CET
3. Koen Fabri (amlse) on 2009/10/26 05:58 PM CET
Detailed Approver History:
 Approval task originally assigned to and completed by Koen Fabri (amlse)

 Approval task originally assigned to and completed by John Gibbs (ambcj)
 Approval task originally assigned to and completed by Bruno Laffin (nawyv)
Version & Status History

Version# Date Created Status
4 2009/10/26 01:01 PM CET Approved - 2009/11/10
3 2009/07/01 10:00 AM CET Approved - 2009/07/22
2 2009/02/05 09:04 AM CET Approved - 2009/02/06
1 2009/02/05 09:01 AM CET

NX Agfa

Uploaded by

Copyright:

Available Formats

NX Agfa

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

NX Agfa

Uploaded by

Copyright:

Available Formats

HE/001261 Page 1 of 87

Document No.001261, Revision 1.2

NX 2.0.8000 / 3.0.8000 Workstation

When printed, this is NOT a controlled copy

Service-related contact All service-related contact information http://www.agfa.com/en/he/support/support_service/index.jsp

Conformance Statement Overview

NX 2.0.8000/3.0.8000 implements the necessary DICOM services to facilitate receiving of unprocessed

Table 1.1-1: Network Services Supported

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

NX 2.0.8000/3.0.8000 does support Media Services.

Table 1.1-2: Media Services Supported

2.2.2.3.1.2 Proposed Presentation Contexts......................................................34

4 Support for Extended Character Sets...................................................67

1.1 Revision Record

Dicom Conformance Statement NX 2.0.8000 / 3.0.8000

1.2 Purpose and Intended Audience of this Document

1.3 General Remarks

1.3.1 Integration and Validation Activities

1.3.2 Future Evolution

1.4 Acronyms and Abbreviations

1.5 Related Documents

2.1 Implementation Model

2.1.1 Application Data Flow Diagram

Query RIS Remote

Figure 2.1-1: Functional Overview – Application Data Flow

2.1.2 Functional Definitions of AE’s

2.1.2.1 Functional Definition of DICOM Store Application Entity

2.1.2.2 Functional Definition of DICOM Print Application Entity

2.1.2.3 Functional Definition of RIS Application Entity

2.1.2.3.1 DICOM Modality Worklist

2.1.2.3.2 DICOM Modality Worklist query on Accession Number

2.1.2.4 Functional Definition of MPPS Application Entity

2.1.3 Sequencing of Real World Activities

Store Print MPPS RIS RIS MPPS Printer PACS

1. Query RIS (by

3. Select Workitem (SPS)

6. Print Acquired Images

7. Store Acquired Images

Figure 2.1-2: sequencing constraints

2.2.1 DICOM Store Application Entity Specification

2.2.1.1 SOP Classes Supported

SOP Class Name SOP Class UID SCU SCP

2.2.1.2 Association Establishment Policies

Table 2.2-2: DICOM Application Context

Application Context Name 1.2.840.10008.3.1.1.1

2.2.1.2.2 Number of Associations

Table 2.2-3: Number of Associations as an Association Initiator for DICOM Store AE

Table 2.2-4: Number of Associations as an Association Acceptor for DICOM Store AE

2.2.1.2.3 Asynchronous Nature

Maximum number of outstanding asynchronous transactions 1

2.2.1.2.4 Implementation Identifying Information

Implementation Class UID 1.3.51.0.1.3

Implementation Version Name AGFA DTF1.0.XX 1

2.2.1.3 Association Initiation Policies

2.2.1.3.1 Activity – Send Images

2.2.1.3.1.1 Description and Sequencing of Activity

Figure 2.2-1: Example of a Storage AE Sequencing Diagram (with Storage Commit)

Table 2.2-7: Association Reject Reasons

Result Response Reason/Diag