GFA Ealth ARE DICOM Conformance Statement: "Workstation NX 2.0"
GFA Ealth ARE DICOM Conformance Statement: "Workstation NX 2.0"
GFA Ealth ARE DICOM Conformance Statement: "Workstation NX 2.0"
L,
AGFA HEALTHCARE
DICOM Conformance Statement
"Workstation NX 2.0"
Status : Released
Revision 2.0
Document Information
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 ã June, 07
tel: 32.3.444.7338 Agfa HealthCare
email: [email protected] All rights reserved
The table below provides an overview of the network services supported by "Workstation"
Media Storage Application Profile Write Files (FSC or FSU) Read Files (FSR)
Compact Disk - Recordable
General Purpose CD-R Yes No
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 .......................................................................... 9
2.1.2.1 Functional Definition of DICOM Store Application Entity.............................. 9
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 15
2.2.1.3.1.3 SOP Specific Conformance 17
2.2.1.4 Association Acceptance Policies................................................................30
2.2.1.4.1 Receive Storage Commitment Response..............................................30
2.2.1.4.1.1 Description and Sequencing of Activity 30
2.2.1.4.1.2 Accepted Presentation Contexts 30
2.2.1.4.1.3 SOP Specific Conformance – Storage Commitment SOP Class
(1.2.840.10008.1.20.1) 31
2.2.1.4.1.4 SOP Specific Conformance – Verification SOP Class
(1.2.840.10008.1.1) 32
2.2.2 DICOM Print Application Entity Specification...................................................33
2.2.2.1 SOP Classes Supported ............................................................................33
2.2.2.2 Association Establishment Policies ............................................................33
2.2.2.2.1 General ................................................................................................33
2.2.2.2.2 Number of Associations ........................................................................33
2.2.2.2.3 Asynchronous Nature ...........................................................................33
2.2.2.2.4 Implementation Identifying Information..................................................34
2.2.2.3 Association Initiation Policies .....................................................................34
3 Media Interchange................................................................................67
3.1 Implementation Model .........................................................................................67
3.1.2 Functional Definition of AEs............................................................................67
3.1.3 Sequencing of Real World Activities................................................................67
3.1.4 File Meta Information for Implementation Class and Version ...........................67
3.2 AE Specifications.................................................................................................68
3.2.1 Offline-Media Application Entity Specification..................................................68
3.2.1.1 Real World Activities..................................................................................68
3.2.1.1.1 Real World Activity - Export to CD-R.....................................................68
3.2.1.1.1.1 Media Storage Application Profile 69
3.3 Media Configuration ............................................................................................70
5 Security ................................................................................................72
5.1 Security Profiles ..................................................................................................72
5.2 Association Level Security ...................................................................................72
5.3 Application Level Security....................................................................................72
6 Annexes ...............................................................................................73
6.1 IOD Contents.......................................................................................................73
6.1.1 Created SOP Instances ..................................................................................73
6.1.1.1 Common Modules .....................................................................................73
6.1.1.2 CR.............................................................................................................79
6.1.1.2.1 CR Image IOD......................................................................................79
6.1.1.2.2 CR Modules..........................................................................................80
6.1.1.3 DX.............................................................................................................81
6.1.1.3.1 DX Image IOD ......................................................................................81
6.1.1.3.2 DX Modules..........................................................................................81
6.1.1.4 MG ............................................................................................................86
6.1.1.4.1 MG Image IOD .....................................................................................86
6.1.1.4.2 MG Modules .........................................................................................87
6.1.1.5 GSPS........................................................................................................87
6.1.1.5.1 GSPS IOD............................................................................................87
6.1.1.5.2 GSPS Modules.....................................................................................88
6.2 Attribute Mapping ................................................................................................90
6.3 Grayscale Image Consistency .............................................................................92
1 INTRODUCTION
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.
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.
2 NETWORKING
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
Archive Images
Remote
MPPS Application Entity
Application Entity Receives MPPS
Print Images Create / Update
Acquire Images
DICOM Standard
Interface
successfully obtained. An image that has been successfully sent to an archive cannot be sent to that archive
again.
4. Create MPPS
(when first image acquired)
5. Acquire Images
9. Complete MPPS
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
2.2 AE Specifications
Table 2.2-1: SOP Class(es) for the DICOM Store Application Entity
2.2.1.2.1 General
The DICOM standard Application context is always proposed:
1 per destination
Maximum number of simultaneous associations initiated
(32 max)
1 for storage
Maximum number of simultaneous associations accepted
commit response
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.
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-EVENT-REPORT. If this report does not arrive within a
(configurable) amount of time, the job will be marked as FAILED.
1
XX is the build version number.
"Workstation" 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 "Workstation"
successfully, because "Workstation" 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)
8. Close Association
The DICOM Store AE may reject the association attempts as shown in the table below:
2
The time-out value is hard-coded in the Dicom library as being 60 seconds.
Depending on the configuration of "Workstation", 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
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.
Note:
A GSPS always refers to exactly one (1) image. Since re-sending an image is prohibited in
"Workstation", 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), DX for presentation (§2.2.1..3.2) or
MG for presentation (§ 2.2.1.3.1.3.4) annotations and shutters are stored in the GSPS or burned in the
image as described in the following table:
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:
2.2.1.3.1.3.1.6.1 Text
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.
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.
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.
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.
2.2.1.3.1.3.1.6.6 Freehand
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:
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:
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
2.2.1.3.1.3.1.6.11 Distance
A distance is composed of a line with a text value.
2.2.1.3.1.3.1.6.13 Scoliosis
ine
er L
Upp
23
Lo
we
r li
ne
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)
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 "Workstation" 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:
>Storage Media
(0088, 0140)
File-Set UID 3
Warning
Error
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 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
The NX DICOM Store AE will accept associations in order to receive responses to a Storage Commitment
Request.
1. Open Association
2. N-EVENT-REPORT (Storage Commit Resp)
3. Close Association
>Referenced SOP
(0008,1155) 1
Instance UID
(0088,0130)
>Storage Media File-
3
Set ID
The behavior of Storage AE when receiving Event Types within the N-EVENT-REPORT is summarized in
the Table below:
The reasons for returning specific status codes in a N-EVENT-REPORT response are summarized in the
table below:
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
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.
Table 2.2-18: SOP Class(es) for the DICOM Print Application Entity
2.2.2.2.1 General
The DICOM standard Application context is always proposed:
1 per destination
Maximum number of simultaneous associations initiated
(32 max)
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.
The DICOM Print AE or "Workstation" will initiate a separate Association for each Print Session.
If the Printer rejects the Association, then "Workstation" 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 "Workstation" 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 "Workstation" releases the association. In case of N-EVENT-REPORT it will not wait for print job status
“Done”.
3
XX is the build version number
1. Open Association
3. N-CREATE -RSP
12. N-ACTION-RQ
13. N-ACTION-RSP
14. N-DELETE-RQ
15. N-DELETE-RSP
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 Management 1.2.840.10008.5.1 DICOM Implicit 1.2.840.10008.1.2 SCU None
Meta SOP Class .1.9 VR Little Endian
Print Job SOP Class 1.2.840.10008.5.1 DICOM Implicit 1.2.840.10008.1.2 SCU None
.1.14 VR Little Endian
Presentation LUT SOP Class 1.2.840.10008.5.1 DICOM Implicit 1.2.840.10008.1.2 SCU None
.1.23 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.
Support for Basic Grayscale Print Management as SCU also implies support for the following SOP Classes
as SCU:
The Basic Film Session SOP Instance refers to one or more Basic Film Box SOP Instance (§2.2.2.3.1.3.2).
Ø N-CREATE
Ø N-ACTION
N-CREATE is issued by "Workstation" (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:
"Workstation" (SCU) will process the N-CREATE confirmation and response Status codes. The following
status codes are recognized:
N-ACTION is issued by "Workstation" (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.)
"Workstation" (SCU) will process the N-ACTION confirmation and response Status codes. The following
status codes in Table 2.2-25 are recognized :
N-DELETE is issued by "Workstation" (SCU) to delete a Film Session. This means that the complete Film
Session SOP Instance hierarchy will be deleted.
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.
N-CREATE is issued by "Workstation" (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:
"Workstation" (SCU) will process the N-CREATE confirmation and response Status codes. The status codes
below are recognized:
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.
"Workstation" (SCU) can send the following DIMSE services:
· N-SET
N-SET is issued by "Workstation" (SCU) to update an instance of the Grayscale Image Box SOP Class.
When all needed Basic Grayscale Image Boxes have been set, "Workstation" (SCU) issues a print
command. There can be empty image positions. By using N-SET, "Workstation" (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:
Table 2.2-29: Supported N-SET Attributes for a Basic Grayscale Image Box
"Workstation" (SCU) will process the N-SET confirmation and response Status codes. The status codes
listed below in Table 2.2-30are recognized:
· 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 "Workstation" about each execution change. "Workstation"
will return the confirmation of the N-EVENT-REPORT operation.
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 "Workstation" (SCU) to retrieve an instance of the Printer SOP class. "Workstation"
specifies the UID of the SOP Instance to be retrieved. The supported N-GET attributes are listed in the table
below:
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.
"Workstation" (SCU) will accept the following DIMSE services:
· N-EVENT-REPORT
· N-GET
N-EVENT-REPORT is used by the SCP to report execution status changes to "Workstation" (SCU) in an
asynchronous way.
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.
N-GET is used to retrieve an instance of the Print Job SOP Class. "Workstation" (SCU) uses the N-GET to
request the SCP to get a Print Job SOP Instance. "Workstation" specifies the UID of the SOP Instance to be
retrieved.
A N-CREATE is issued by "Workstation" (SCU) to create a Presentation LUT SOP Instance. The supported
Presentation LUT attributes are listed below:
Note:
‘Presentation LUT Sequence’ is not supported.
"Workstation" (SCU) will process the N-CREATE confirmation and response Status codes. The status codes
listed below are recognized:
Note:
"Workstation" (SCU) uses the N-CREATE Service Element to request the SCP to create a
Presentation LUT SOP Instance. "Workstation" 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.
Table 2.2-37: SOP Class(es) for the DICOM Store Application Entity
2.2.3.2.1 General
The DICOM standard Application context is always proposed:
"Workstation" does not support asynchronous communication (multiple outstanding transactions over a
single connection)
4
XX is the build version number
1. Open Association
2. C-FIND Request (Worklist query)
3. C-FIND Response(Worklist item)-status = pending
4. C-FIND Response(Worklist item)-status = pending
5. C-FIND Response - status = success
6. Close Association
The behavior of a RIS AE when encountering status codes in a C-FIND response is summarized in the Table
below:
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.
Tag Description VR
(0019, 0010) “Agfa ADC NX” LO
(0019, 10F0) User Defined field 1 LO
(0019, 10F1) User Defined field 2 LO
(0019, 10F2) User Defined field 3 LO
(0019, 10F3) User Defined field 4 LO
(0019, 10F4) User Defined field 5 LO
Table 2.2-47: SOP Class(es) for the DICOM Store Application Entity
2.2.4.2.1 General
The DICOM standard Application context is always proposed:
"Workstation" does not support asynchronous communication (multiple outstanding transactions over a
single connection)
5
XX is the build version number
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.
1. Open Association
3. Close Association
4. Aquire Images()
5. Open Association
7. Close Association
· N-CREATE
· N-SET
A N-CREATE allows "Workstation" 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
"Workstation".
A N-SET allows "Workstation" 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 "Workstation".
Note:
"Workstation" 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 NSET 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:
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.
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 "Workstation" wishes to use the PPS Discontinuation Reason Code Sequence (0040, 0281), it
creates that attribute (zero-length) during MPPS N-CREATE.
For audit trailing the "Workstation" 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.
2.4 Configuration
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.
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.
CR image, WITHOUT GSPS:
- 8 bit OD
- 8 bit OD Gamma correction
- 8 bit P-Value
6
anonymous archiving (i.e. without patient demographics) is not supported
- 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
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
- 15-bit M1 Image + VOI Lut P-Value
Table 2.4-2: Overview of the PACS DICOM CR-Image Types supported by "Workstation".
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 (eg. 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.c 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.c 15 bit
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.
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
"Workstation" exposure tree.
"Workstation" 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].
With RIS mapping, the incoming SPS attributes of the RIS are mapped to the internal data structure of
"Workstation". 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, Table
2.2-29
Additionally, the following parameters can be configured
Parameter Configurable
(yes/no)
Name Yes
Description Yes
AE Title Yes
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).
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.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.
General Parameters
Max PDU Receive Size No 65542
Storage parameters
Storage SCU time-out waiting for a response to a C- No 15 minutes
STORE-RQ
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.
Is Archive?8 Yes
8
If yes, images sent to this destination will be referenced in the MPPS.
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
Print Parameters
Print SCU time-out waiting for a response to a N-
No 10 minutes
CREATE-RQ
3 MEDIA INTERCHANGE
"Workstation" is able to create or read DICOM Interchange media. The related capabilities are described in
the following sections.
- 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.
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 "Workstation".
Table 3.1-1: AE Related Application Profiles, Real World Activities and Roles
3.2 AE Specifications
Table 3.2-1: AE Related Application Profiles, Real World Activities and Roles
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
9
XX is the build version number.
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:
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
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
5 SECURITY
By default the workstation will be configured to automatically log the current user out after a certain period of
non-activity.
6 ANNEXES
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
Presence of
Attribute Name Tag VR Value Source
Value
> Code Sequence
> Patient’s Primary Language
Code Modifier Sequence (0010, 0102) SQ ANAP MWL
>> 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
Sequence (0008, 0096) SQ ANAP MWL
Requested
Procedure ID or
generated for
unscheduled (app A
Study ID (0020, 0010) SH IHE note 5) ALWAYS Auto / MWL
Accession Number (0008, 0050) SH VNAP User / MWL
Performed
Procedure step
Study Description (0008, 1030) LO Description ANAP Auto
Presence of
Attribute Name Tag VR Value Source
Value
Physician(s) of Record (0008, 1048) PN ANAP MWL
Physician(s) of Record
Identification Sequence (0008, 1049) SQ ANAP MWL
Name of Physician(s) Reading
Study (0008, 1060) PN ANAP MWL
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
Sequence (0008, 1084) SQ ANAP MWL
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 SOP
Modality (0008,0060) CS ALWAYS Class
Different for each
Series Instance UID (0020,000E) UI image ALWAYS Auto
Series Number (0020, 0011) IS ALWAYS Auto
Based on protocol
Laterality (0020,0060) CS code ALWAYS User / Auto
Performing Physicians’ Name (0008, 1050) PN ANAP User
Performing Physician’s
Identification Sequence (0008, 1050) SQ ANAP MWL
Protocol Name (0018, 1030) LO ANAP Auto
Exposure Type
Series Description (0008, 103E) LO Name ALWAYS Auto
Depending on
security setting either
auto filled in with
Operators' Name (0008, 1070) PN 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
Related Series Sequence (0008, 1250) SQ ANAP MWL
> Study Instance UID (0020, 000D) UI
> Series instance UID (0020, 000E) UI
>Purpose of Reference Code
Sequence (0040, A170) SQ
Patient Position (0018, 5100) CS Empty ANAP
Smallest Pixel Value in Series (0028, 0108) US NEVER
Presence of
Attribute Name Tag VR Value Source
Value
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
>Scheduled Procedure Step ID (0040, 0009) SH ANAP MWL
>Scheduled Procedure Step
Description (0040, 0007) LO ANAP MWL
>Scheduled Protocol Code
10
Sequence (0040, 0008) SQ ANAP MWL
>> 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
Performed Protocol Code
Sequence (0040, 0260) SQ ANAP MWL / User
> Code Value (0008, 0100) SH ANAP MWL / User
> Code Scheme Designator (0008, 0102) SH ANAP MWL / User
> Code Meaning (0008, 0104) SH ANAP MWL / User
> Protocol Context Sequence (0040, 0440) SQ ANAP MWL / User
>>Content Item Modifier
Sequence (0040, 0441) SQ ANAP MWL / User
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
Software Versions (0018, 1020) LO ANAP Auto
Image
General Image
10
The following rules are applicable for DICOM:
- When 0008,102 was not supplied by the RIS, its value will be "UNKNOWN".
- When 0008,103 was not supplied by the RIS, its value will be "UNKNOWN".
- When 0008,104 was not supplied by the RIS, its value will be "UNKNOWN".
Presence of
Attribute Name Tag VR Value Source
Value
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
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
> Purpose of Reference Code
Sequence (0040, A170) SQ
Referenced Waveform Sequence (0008, 113A) SQ NEVER
> Purpose of Reference Code
Sequence (0040, A170) SQ ANAP Auto
Images in Acquisition (0020, 1002) IS NEVER
Image Comments (0020, 4000) LT ANAP User
When exposure is
defined as QC in
Quality Control Image (0028, 0300) CS study 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
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
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
Presence of
Attribute Name Tag VR Value Source
Value
Pixel Data (7FE0, 0010) OB ALWAYS Auto
Planar Configuration (0028, 0006) US NEVER
Smallest Image Pixel Value (0028, 0106) US NEVER
Largest Image Pixel Value (0028, 0107) US NEVER
Red Palette Color Lookup Table
descriptor (0028, 1101) US NEVER
Green Palette Color Lookup Table
descriptor (0028, 1102) US NEVER
Blue Palette Color Lookup Table
descriptor (0028, 1103) US NEVER
Red Palette Color Lookup Table
data (0028, 1201) OW NEVER
Green Palette Color Lookup Table
data (0028, 1202) OW NEVER
Blue Palette Color Lookup Table
data (0028, 1203) OW NEVER
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
Related General SOP Class UID (0008, 001A) UI NEVER
Original Specialized SOP Class
UID (0008, 001B) UI NEVER
Coding Scheme Identification
Sequence (0008, 0110) SQ NEVER
> Code Scheme Designator (0008, 0102) SH NEVER
> Coding Scheme Registry (0008, 0112) LO NEVER
> Coding Scheme UID (0008, 010C) UI NEVER
> Coding Scheme External ID (0008, 0114) ST NEVER
> Coding Scheme Name (0008, 0115) ST NEVER
> Responsible Organization (0008, 0116) ST NEVER
Timezone Offset From UTC (0008, 0201) SH NEVER
Contributing Equipment Sequence (0018, A001) SQ
> Manufacturer (0008,0070) LO ALWAYS Config
> Institution Name (0008,0080) LO ANAP Config
Config:Station
name of the
> Station Name (0008,1010) SH ALWAYS
digitizer
known on NX
> Institutional Department Name (0008,1040) LO ANAP MWL / Config
> Manufacturer’s Model Name (0008,1090) LO ALWAYS Auto
> Device Serial Number (0018,1000) LO ALWAYS Auto
> Software Versions (0018,1020) LO ALWAYS Auto
> Spatial Resolution (0018,1050) DS NEVER
> Date of Last Calibration (0018,1200) DA NEVER
> Time of Last Calibration (0018,1201) TM NEVER
> Contribution DateTime (0018,A002) DT NEVER
Presence of
Attribute Name Tag VR Value Source
Value
> Contribution Description (0018,A003) ST NEVER
Instance Number (0020,0013) IS ALWAYS Auto
SOP Instance Status (0100,0410) CS NEVER
SOP Authorization Date and Time (0100,0420) DT NEVER
SOP Authorization Comment (0100,0424) LT NEVER
Authorization Equipment
Certification Number (0100,0426) LO NEVER
Encrypted Attributes Sequence (0400,0500) SQ NEVER
>Encrypted Content Transfer
Syntax UID (0400,0510) UI NEVER
>Encrypted Content (0400,0520) OB NEVER
Private attributes
Only available in
case that the image
was scanned using a
non-Compact family
Plate sensitivity (0019,10F6) DS digitizer. ANAP Auto
Only available in
case that the image
was scanned using a
non-Compact family
Plate erasability (0019,10F7) DS digitizer. ANAP Auto
Requested Procedure Description (0032,1060) LO ANAP Manual/MWL
6.1.1.2 CR
6.1.1.2.2 CR Modules
Table 6.1-3: CR Modules of Created SOP Instances
Presence
Attribute Name Tag VR Value Source
of Value
Series
CR Series
View Position (0018,5101) CS Based on protocol code ALWAYS Auto / User
Focal Spot (0018, 1190) DS Auto
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
Distance Source to Patient (0018, 1111) DS ANAP (1) Auto
Exposure Time (0018, 1150) IS ANAP (1) Auto
X-Ray Tube Current (0018, 1151) IS ANAP (1) Auto
Exposure (0018, 1152) IS ANAP (1) 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
Generator Power (0018, 1170) IS ANAP (1) Auto
Acquisition Device Processing
Description (0018, 1400) LO ANAP Auto
Acquisition Device Processing
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
Presence
Attribute Name Tag VR Value Source
of Value
> 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.2 DX Modules
Table 6.1-5: DX Module of Created SOP Instances
Presence
Attribute Name Tag VR Value Source
of Value
Series
DX Series
Modality (0008, 0060) CS DX ALWAYS Config
Referenced Performed Procedure (0008, 1111) SQ ANAP Auto
Presence
Attribute Name Tag VR Value Source
of Value
Step Sequence
> 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
Vertices of the Polygonal Shutter (0018, 1620) 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
13
Fixed when using DX for Processing
Presence
Attribute Name Tag VR Value Source
of Value
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
Window Center (0028, 1050) DS ANAP Auto
Window Width (0028, 1051) DS ANAP Auto
Window Center & Width
Explanation (0028, 1055) LO 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
Presence
Attribute Name Tag VR Value Source
of Value
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
Sequence (0054, 0410) SQ ANAP (1) Auto
Patient Orientation Modifier Code
Sequence (0054, 0412) SQ ANAP (1) Auto
Patient Gantry Relationship Code
(1)
Sequence (0054, 0414) SQ ANAP Auto
Distance Source to Patient (0018, 1111) DS ANAP (1) Auto
Distance Source to Detector (0018, 1110) DS ANAP (1) Auto
Estimated Radiographic
(1) (1)
Magnification Factor (0018, 1114) DS ANAP User/XRDI
(1)
Positioner Type (0018, 1508) CS ANAP Auto
Positioner Primary Angle (0018, 1510) DS ANAP (1) Auto
Positioner Secondary Angle (0018, 1511) DS ANAP (1) Auto
(1)
Detector Primary Angle (0018, 1510) DS ANAP Auto
(1)
Detector Secondary Angle (0018, 1511) DS ANAP Auto
(1)
Body Part Thickness (0018, 11A0) DS ANAP User/XRDI
(1)
Compression Force (0018, 11A2) DS ANAP User/XRDI
X-Ray Acquisition dose
(1) (1)
KVP (0018, 0060) DS ANAP User/XRDI
(1) (1)
X-Ray Tube Current (0018, 1151) IS ANAP User/XRDI
(1)
X-Ray Tube Current in µA (0018, 8151) IS ANAP (1) User/XRDI
(1)
Exposure Time (0018, 1150) IS ANAP (1) User/XRDI
(1) (1)
Exposure Time in µs (0018, 8150) IS ANAP User/XRDI
(1)
Exposure (0018, 1152) IS ANAP (1) User/XRDI
(1)
Exposure in µAs (0018, 1153) IS ANAP Auto
Presence
Attribute Name Tag VR Value Source
of Value
(1)
Distance Source to Detector (0018, 1110) DS ANAP (1) User/XRDI
Distance Source to Patient (0018, 1111) DS ANAP (1) Auto
Image Area Dose Product (0018, 115E) DS ANAP (1) Auto
(1) (1)
Body Part Thickness (0018, 11A0) DS ANAP User/XRDI
Lgm value multiplied by
Relative X-Ray Exposure (0018, 1405) IS 100 ANAP Auto
(1) (1)
Entrance Dose (0040, 0302) US ANAP User/XRDI
(1) (1)
Entrance Dose in mGy (0040, 8302) US ANAP User/XRDI
Exposed Area (0040, 0303) US ANAP (1) Auto
Distance Source to Entrance (0040, 0306) DS ANAP (1) Auto
Comments on Radiation Dose (0040, 0310) ST ANAP (1) Auto
X-Ray Output (0040, 0312) DS ANAP (1) Auto
Half Value Layer (0040, 0314) DS ANAP (1) Auto
(1) (1)
Organ Dose (0040, 0316) DS ANAP User/XRDI
Organ Exposed (0040, 0318) CS ANAP (1) Auto
(1)
Anode target Material (0018, 1191) CS ANAP (1) User/XRDI
(1)
Filter Material (0018, 7050) CS ANAP (1) User/XRDI
Filter Thickness Minimum (0018, 7052) DS ANAP (1) Auto
Filter Thickness Maximum (0018, 7054) DS ANAP (1) Auto
(1)
Grid (0018, 1166) CS ANAP (1) User/XRDI
(1)
Grid Absorbing Material (0018, 7040) LT ANAP (1) User/XRDI
(1)
Grid Pitch (0018, 7044) DS ANAP (1) User/XRDI
(1)
Grid Thickness (0018, 7042) DS ANAP (1) User/XRDI
- Manual
(1)
Exposure Control Mode (0018, 7060) CS - Automatic ANAP (1) User/XRDI
Exposure Control Mode
(1)
Description (0018, 7062) LT ANAP (1) User/XRDI
(1)
Phototimer Setting (0018, 7065) DS ANAP (1) User/XRDI
Image and Fluoroscopy Area
(1)
Dose Product (0018, 115E) DS ANAP (1) User/XRDI
(1) (1)
Grid Focal Distance (0018, 704C) DS ANAP User/XRDI
(1)
Rectification Type (0018, 1156) CS ANAP Auto
VOI LUT
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
Window Center (0028, 1050) DS ANAP Auto
Window Width (0028, 1051) DS ANAP Auto
Window Center & Width
Explanation (0028, 1055) LO ANAP Auto
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
Presence
Attribute Name Tag VR Value Source
of Value
> 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.2 MG Modules
Table 6.1-7: MG Module of Created SOP Instances
Presence
Attribute Name Tag VR Value Source
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
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/XRDI26
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
View Code Sequence (0054, 0220) CS Always Config / User
View Modifier Code Sequence (0054, 0222) SQ ANAP Config / User
6.1.1.5 GSPS
14
Value is supplied by user of XRDI component in case of XRDI configuration
Presence
Attribute Name Tag VR Value Source
of Value
Series
Presentation Series
Modality (0008, 0060) CS PR ALWAYS Fixed
Image
Presentation State
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
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
>> Referenced Frame Number (0008, 1160) IS ALWAYS Auto
Shutter Presentation Value (0018, 1622) US ANAP Auto
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 ALWAYS User
Shutter Left Vertical Edge (0018, 1602) IS ALWAYS User
Shutter Right Vertical Edge (0018, 1604) IS ALWAYS User
Shutter Upper Horizontal Edge (0018, 1606) IS ALWAYS User
Shutter Lower Horizontal Edge (0018, 1608) IS ALWAYS User
Vertices of the Polygonal Shutter (0018, 1620) IS ANAP User
Shutter Presentation Value (0018, 1622) US ANAP User
Displayed Area
Displayed Area Selection
Sequence (0070, 005A) SQ ALWAYS Auto
>Referenced Image Sequence (0008, 1140) SQ ANAP Auto
Presence
Attribute Name Tag VR Value Source
of Value
>>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
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
Presence
Attribute Name Tag VR Value Source
of Value
>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
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
Window Center (0028,1050) DS ANAP Auto
Window Width (0028,1051) DS ANAP Auto
Window Center & Width
Explanation (0028,1055) LO ANAP Auto
Table 6.2-1: Attribute Mapping between Modality Worklist, Image and MPPS
Study Instance UID Study Instance UID > Study Instance UID
Referenced Study Sequence Referenced Study Sequence > Referenced Study Sequence
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 Performing Physician’s Performing Physician’s Name > Performing Physician’s Name
Name