NX 2.0 DICOM Conformance Statement

HE/001132 Document No.001132, Revision 2.
0 NodeID Livelink : 14140190 Agfa HealthCare
Page 1 of 92 14 June, 2007
L,
AGFA HEALTHCARE
DICOM Conformance Statement
"Workstation NX 2.0"
Status : Released Revision 2.0 NodeID Livelink : 14140190
HE/001132 Agfa HealthCare Document No. 001132, Revision 2.0 NodeID Livelink : 14140190
Page 2 of 92 14 June, 2007
Document Information
Service-related contact information worldwide
All service-related contact information is available on this URL
http://www.agfa.com/en/he/support/support_service/index.jsp
Issued by: Agfa HealthCare SIV Connectivity Septestraat 27 B-2640 Mortsel Belgium
Agfa shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance or use of this publication. Agfa reserves the right to revise this publication and to make changes to its content at any time, without obligation to notify any person or entity of such revisions and changes. This publication may only be used in connection with the promotion, sales, installation and use of Agfa equipment. Copyright June, 07 Agfa HealthCare All rights reserved
tel: 32.3.444.7338 email: [email protected]
HE/001132 Document No.001132, Revision 2.0 NodeID Livelink : 14140190 Agfa HealthCare
Page 3 of 92 14 June, 2007
Conformance Statement Overview

"Workstation", 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. "Workstation" 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 "Workstation" Table 1.1-1: Network Services Supported
SOP Classes Transfer Computed Radiography Image Storage Digital X-Ray Image Storage For Presentation Digital X-Ray Image Storage For Processing Grayscale Softcopy Presentation State Storage SOP Class Digital Mammography Image Storage For Presentation Digital Mammography Image Storage For Processing Workflow Management Storage Commitment Push Model SOP Class Modality Performed Procedure Step SOP Class Modality Worklist Information Model FIND Print Management Basic Grayscale Print Management Meta SOP Class Basic Film Session SOP Class Basic Film Box SOP Class Basic Grayscale Image Box SOP Class Printer SOP Class Print Job SOP Class Presentation LUT SOP Class User of Service (SCU) Option Option Option Option Option Option Option Option Option Option Option Option Option Option Option Option Provider of Service (SCP) No No No No No No No No No No No No No No No No
"Workstation" does support Media Services. Table 1.1-2: Media Services Supported
Media Storage Application Profile Compact Disk - Recordable General Purpose CD-R Yes No Write Files (FSC or FSU) Read Files (FSR)
Page 4 of 92 14 June, 2007
Table of Contents
1
1.1 1.2 1.3 1.3.1 1.3.2 1.4 1.5
Introduction ............................................................................................7
Revision Record ................................................................................................... 7 Purpose and Intended Audience of this Document ................................................ 7 General Remarks ................................................................................................. 7 Integration and Validation Activities.................................................................. 7 Future Evolution .............................................................................................. 7 Acronyms and Abbreviations ................................................................................ 8 Related Documents .............................................................................................. 8
Networking .............................................................................................9
2.1 Implementation Model .......................................................................................... 9 2.1.1 Application Data Flow Diagram........................................................................ 9 2.1.2 Functional Definitions of AEs .......................................................................... 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
Page 5 of 92 14 June, 2007
2.2.2.3.1 2.2.2.3.1.1 2.2.2.3.1.2 2.2.2.3.1.3
Activity Print Images ..........................................................................34 Description and Sequencing of Activity 34 Proposed Presentation Contexts 36 SOP Specific Conformance - Basic Grayscale Print Management Meta SOP Class 36 2.2.2.3.1.4 SOP Specific Conformance Print Job SOP Class (1.2.840.10008.5.1.1.14) 41 2.2.2.3.1.5 SOP Specific Conformance Presentation LUT SOP Class (1.2.840.10008.5.1.1.23) 43 2.2.2.3.1.6 SOP Specific Conformance Verification SOP Class (1.2.840.10008.1.1) 44 2.2.3 RIS Application Entity Specification.................................................................45 2.2.3.1 SOP Classes Supported ............................................................................45 2.2.3.2 Association Establishment Policies ............................................................45 2.2.3.2.1 General ................................................................................................45 2.2.3.2.2 Number of Associations ........................................................................45 2.2.3.2.3 Asynchronous Nature ...........................................................................45 2.2.3.2.4 Implementation Identifying Information..................................................45 2.2.3.3 Association Initiation Policies .....................................................................46 2.2.3.3.1 Activity Query RIS..............................................................................46 2.2.3.3.1.1 Description and Sequencing of Activity 46 2.2.3.3.1.2 Proposed Presentation Contexts 46 2.2.3.3.1.3 SOP Specific Conformance Modality Worklist SOP Class (1.2.840.10008.5.1.4.31) 46 2.2.3.4 User defined fields.....................................................................................50 2.2.4 MPPS Application Entity Specification ............................................................51 2.2.4.1 SOP Classes Supported ............................................................................51 2.2.4.2 Association Establishment Policies ............................................................51 2.2.4.2.1 General ................................................................................................51 2.2.4.2.2 Number of Associations ........................................................................51 2.2.4.2.3 Asynchronous Nature ...........................................................................51 2.2.4.2.4 Implementation Identifying Information..................................................51 2.2.4.3 Association Initiation Policies .....................................................................52 2.2.4.3.1 Activity Acquire Images, Print Images, ...............................................52 2.2.4.3.1.1 Description and Sequencing of Activity 52 2.2.4.3.1.2 Proposed Presentation Contexts 53 2.2.4.3.1.3 SOP Specific Conformance MPPS (1.2.840.10008.3.1.2.3.3) 53 2.3 Network Interfaces...............................................................................................58 2.3.1 Physical Medium Support ...............................................................................58 2.3.2 Additional Protocols........................................................................................58 2.4 Configuration.......................................................................................................59 2.4.1 AE Title/ Presentation Address Mapping .........................................................59 2.4.1.1 Local AE Titles ..........................................................................................59 2.4.1.2 Remote AE Title/ Presentation Address Mapping .......................................59 2.4.1.2.1 Storage.................................................................................................59 2.4.1.2.1.1 Archive options 59 2.4.1.2.2 RIS.......................................................................................................61 2.4.1.2.2.1 Configuration of a RIS 61 2.4.1.2.2.2 Configuration of RIS Mapping 62 2.4.1.2.3 MPPS...................................................................................................63 2.4.1.2.4 Printing.................................................................................................63 2.4.1.3 Queue Management & Job description ......................................................63 2.4.1.4 DICOM Store AE .......................................................................................63 2.4.1.4.1 Queue description.................................................................................63
Page 6 of 92 14 June, 2007
2.4.1.4.2 2.4.1.5 2.4.2
Job description .....................................................................................64 DICOM Print AE ........................................................................................64 Parameters.....................................................................................................64
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
4 5
5.1 5.2 5.3
Support for Extended Character Sets...................................................71 Security ................................................................................................72

Security Profiles ..................................................................................................72 Association Level Security ...................................................................................72 Application Level Security....................................................................................72
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
Page 7 of 92 14 June, 2007
1
1.1
Revision Number 1.0 2.0
INTRODUCTION Revision Record

Date 20/12/2006 21/03/2007 Reason for Change Initial version NX2.0 Updated for NX2.0.xxx
1.2
Purpose and Intended Audience of this Document
This document is a DICOM Conformance Statement for the DICOM Services of the "Workstation" 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, 2004. 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
1.3.1
General Remarks
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 users 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 users 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 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.
Page 8 of 92 14 June, 2007
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 AET ACSE CD-R DICOM FSC FSU FSR GSDF GSPS IE IOD ISO LUT MPPS MSPS PDU SCU SCP SOP UID VR DICOM Application Entity Application Entity Title Association Control Service Element Compact Disk Recordable Digital Imaging and Communications in Medicine File-Set Creator File-Set Updater File-Set Reader Grayscale Standard Display Function Grayscale Softcopy Presentation State Information Entity (DICOM) Information Object Definition International Standard Organization Lookup Table Modality Performed Procedure Step Modality Scheduled Procedure Step DICOM Protocol Data Unit DICOM Service Class User (DICOM client) DICOM Service Class Provider (DICOM server) DICOM Service-Object Pair Unique Identifier Value Representation
1.5
Related Documents
ACR-NEMA Digital Imaging and Communications in Medicine (DICOM) V3.0. 2004. IHE Radiology Technical Framework Revision 6 Final Text, May 2005
Page 9 of 92 14 June, 2007
2
2.1
2.1.1
NETWORKING Implementation Model

Application Data Flow Diagram local remote
Request to send images & GSPS
DICOM Store Application Entity
Remote Application Entity Receives Images & GSPS
Request to Print film sheets
DICOM Print Application Entity
Remote Application Entity Prints Film Sheets
Query RIS RIS Application Entity Query RIS by AccessionNumber
Remote Application Entity Provides Worklist Items
Archive Images MPPS Application Entity Print Images
Remote Application Entity Receives MPPS Create / Update
Acquire Images
DICOM Standard Interface

Figure 2.1-1: Functional Overview Application Data Flow
2.1.2 2.1.2.1
Functional Definitions of AEs 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
Page 10 of 92 14 June, 2007
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 a MPPS, by adding a Dose to a MPPS or by adding a Print Sheet to a MPPS. The local real-world activity Close Session or the modification of the sessions Accession Number will complete the MPPS. This happens completely automatically and no user intervention is possible.
Page 11 of 92 14 June, 2007
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. 2. 3. 4. 5. 6. 7. 8. 9. Query RIS Receive Worklist Select Workitem Create MPPS Acquire Images Print Acquired Images Store Acquired Images (+ GSPS) Commit Acquired Images Finalize MPPS
Page 12 of 92 14 June, 2007
2.2
2.2.1 2.2.1.1
AE Specifications
DICOM Store Application Entity Specification 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 Computed Radiography Image Storage Digital X-ray Image Storage for presentation Digital X-ray Image Storage for processing Digital Mammography Image Storage For Presentation Digital Mammography Image Storage For Processing Grayscale Softcopy Presentation State Storage SOP Class Storage Commitment Push Model SOP Class SOP Class UID 1.2.840.10008.5.1.4.1.1.1 1.2.840.10008.5.1.4.1.1.1.1 1.2.840.10008.5.1.4.1.1.1.1.1 1.2.840.10008.5.1.4.1.1.1.2 1.2.840.10008.5.1.4.1.1.1.2.1 1.2.840.10008.5.1.4.1.1.11.1 1.2.840.10008.1.20.1 SCU Yes Yes Yes Yes Yes Yes Yes SCP No No No No No No No
2.2.1.2 2.2.1.2.1
Association Establishment Policies 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
"Workstation" 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 Maximum number of simultaneous associations initiated 1 per destination (32 max)
Table 2.2-4: Number of Associations as an Association Acceptor for DICOM Store AE Maximum number of simultaneous associations accepted 1 for storage commit response
Page 13 of 92 14 June, 2007
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 Implementation Version Name 1.3.51.0.1.3 AGFA DTF1.0.XX
1
2.2.1.3 2.2.1.3.1 2.2.1.3.1.1
Association Initiation Policies Activity Send Images 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 hasnt 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-EVENTREPORT 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.
Page 14 of 92 14 June, 2007
"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
Figure 2.2-1: Example of a Storage AE Sequencing Diagram (with Storage Commit)
The DICOM Store AE may reject the association attempts as shown in the table below:
Page 15 of 92 14 June, 2007
Table 2.2-7: Association Reject Reasons

Result The Dicom library refuses the association The Dicom library refuses the association The Dicom library refuses the association A799 Response Reason/Diag SCU Device not known
Maximum number of association processing threads exceeded Dicom Library is not allowed to accept C-STORE commands from this device and therefore refuses the association. SOP Class is not found back in the configuration The Dicom library is unable to create the Dicom media file due to the fact that the disk is full The Dicom library is unable to create the Dicom media file due to resource problems other than disk is full. The Dicom library is unable to acquire the complete C-STORE request due to network problems. The Dicom library is unable to acquire the complete C-STORE request due to network problems (time-out while reading data from socket) 2.
The Dicom library refuses the association The Dicom library refuses the association
A0102 A702
The Dicom library refuses the association
A703
A703
A701
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:
The time-out value is hard-coded in the Dicom library as being 60 seconds.
Page 16 of 92 14 June, 2007
Table 2.2-8: Presentation Contexts Proposed by DICOM Store AE

Presentation Context Table Abstract Syntax Name CR Image Storage UID 1.2.840.1000 8.5.1.4.1.1.1 Transfer Syntax Name List JPEG LLNH1 Encoded (i.e. lossless) JPEG LLNHF Encoded (i.e. lossless) JPEG Lossy 8 bit JPEG Lossy 12 bit Implicit VR Little Endian Explicit VR Little Endian JPEG LLNH1 Encoded (i.e. lossless) JPEG LLNHF Encoded (i.e. lossless) JPEG Lossy 8 bit JPEG Lossy 12 bit Implicit VR Little Endian Explicit VR Little Endian JPEG LLNH1 Encoded (i.e. lossless) JPEG LLNHF Encoded (i.e. lossless) JPEG Lossy 8 bit JPEG Lossy 12 bit Implicit VR Little Endian Explicit VR Little Endian JPEG LLNH1 Encoded (i.e. lossless) JPEG LLNHF Encoded (i.e. lossless) JPEG Lossy 8 bit JPEG Lossy 12 bit Implicit VR Little Endian Explicit VR Little Endian JPEG LLNH1 Encoded (i.e. lossless) JPEG LLNHF Encoded (i.e. lossless) JPEG Lossy 8 bit JPEG Lossy 12 bit Implicit VR Little Endian Explicit VR Little Endian Implicit VR Little Endian Explicit VR Little Endian UID List 1.2.840.10008.1.2.4.57 1.2.840.10008.1.2.4.70 1.2.840.10008.1.2.4. 50 1.2.840.10008.1.2.4.51 1.2.840.10008.1.2 1.2.840.10008.1.2.1 1.2.840.10008.1.2.4.57 1.2.840.10008.1.2.4.70 1.2.840.10008.1.2.4.50 1.2.840.10008.1.2.4.51 1.2.840.10008.1.2.1 1.2.840.10008.1.2.4.57 1.2.840.10008.1.2.4.70 1.2.840.10008.1.2.4.50 1.2.840.10008.1.2.4.51 1.2.840.10008.1.2 1.2.840.10008.1.2.1 1.2.840.10008.1.2.4.57 1.2.840.10008.1.2.4.70 1.2.840.10008.1.2.4.50 1.2.840.10008.1.2.4.51 1.2.840.10008.1.2 1.2.840.10008.1.2.1 1.2.840.10008.1.2.4.57 1.2.840.10008.1.2.4.70 1.2.840.10008.1.2.4. 50 1.2.840.10008.1.2.4.511.2. 840.10008.1.2 1.2.840.10008.1.2.1 1.2.840.10008.1.2 1.2.840.10008.1.2.1 SCU None SCU None SCU Role Extended Negotiation None
Digital X-ray Image Storage for presentation
1.2.840.1000 8.5.1.4.1.1.1. 1
SCU
None
Digital X-ray Image Storage for processing
1.2.840.1000 8.5.1.4.1.1.1. 1.1
Digital Mammography Image Storage For Presentation
1.2.840.1000 8.5.1.4.1.1.1. 2
SCU
None
Digital Mammography Image Storage For Processing
1.2.840.1000 8.5.1.4.1.1.1. 2.1
SCU
None
Grayscale Softcopy Presentation State Storage SOP Class
1.2.840.1000 8.5.1.4.1.1.11 .1
Page 17 of 92 14 June, 2007
Presentation Context Table Abstract Syntax Name Storage Commitment Push Model SOP Class UID 1.2.840.1000 8.1.20.1 Transfer Syntax Name List Implicit VR Little Endian UID List 1.2.840.10008.1.2 SCU Role Extended Negotiation None
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
2.2.1.3.1.3 2.2.1.3.1.3.1
SOP Specific Conformance 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).
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).
Page 18 of 92 14 June, 2007
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 "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: Table 2.2-9: Use of GSPS vs. Burning in the image
CR DX for presentation MG for presentation Image (processing,W/L,collimation) Annotations Shutters DX for processing
Processed pixels + LUTs GSPS or Burned in 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 shutter is described in the shutter module of the image header. GSPS or discarded Always burned in
RAW pixels
Ignored
Zoom Markers
The following paragraphs describe into detail how each annotation is embedded in the GSPS:
2.2.1.3.1.3.1.6.1
Text
Page 19 of 92 14 June, 2007
Graphic Layer Module (0070,0060) (0070,0002) (0070,0068)
Graphic Layer Sequence >Graphic Layer >Graphic Layer Description
ID123 Text
Graphic Annotation Module (0070,0001) Graphic Annotation Sequence (0070,0002) > Graphic Layer (0070,0008) (0070,0003) (0070,0004) (0070,0006) (0070,0010) (0070,0011) (0070,0012) (0070,0014) (0070,0015) > Text Object Sequence >> Bounding box annotation units >> Anchor Point Annotation Units >> Unformatted Text Value >> Bounding Box Top Left Hand Corner >> Bounding Box Top Right Hand Corner >> Bounding Box Text Horizontal Justification >> Anchor Point >> Anchor Point Visibility
ID123 PIXEL [value] [value] [value] LEFT -
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.
ID Arrow
Graphic Annotation Module (0070,0001) Graphic Annotation Sequence (0070,0002) > Graphic Layer (0070,0008) > Text Object Sequence (0070,0003) >> Bounding box annotation units (0070,0004) (0070,0006) (0070,0010) (0070,0011) (0070,0012) (0070,0014) (0070,0015) (0070,0009) Arrow line (0070,0005) (0070,0020) (0070,0021) (0070,0022) (0070,0023) (0070,0024) Arrow point >> Anchor Point Annotation Units >> Unformatted Text Value >> Bounding Box Top Left Hand Corner >> Bounding Box Top Right Hand Corner >> Bounding Box Text Horizontal Justification >> Anchor Point >> Anchor Point Visibility > Graphic Object Sequence >> Graphic Annotation Units >> Graphic Dimensions >> Number of Graphic Points >> Graphic Data >> Graphic Type >> Graphic Filled
[ID of the corresponding layer] PIXEL PIXEL [value] [value] [value] LEFT [value of arrow point] N
PIXEL 2 2 [values] POLYLINE -
Page 20 of 92 14 June, 2007
(0070,0001) (0070,0005) (0070,0020) (0070,0021) (0070,0022) (0070,0023) (0070,0024)
Graphic Annotation Sequence >> Graphic Annotation Units >> Graphic Dimensions >> Number of Graphic Points >> Graphic Data >> Graphic Type >> Graphic Filled
PIXEL 2 3 [values] POLYLINE -
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.
ID Rectangle or Rectangle_SAL
Graphic Annotation Module (0070,0001) Graphic Annotation Sequence (0070,0002) > Graphic Layer (0070,0008) > Text Object Sequence (0070,0003) >> Bounding box annotation units (0070,0004) >> Anchor Point Annotation Units (0070,0006) (0070,0010) (0070,0011) (0070,0012) (0070,0014) (0070,0015) (0070,0009) (0070,0005) (0070,0020) (0070,0021) (0070,0022) (0070,0023) (0070,0024) >> Unformatted Text Value >> Bounding Box Top Left Hand Corner >> Bounding Box Top Right Hand Corner >> Bounding Box Text Horizontal Justification >> Anchor Point >> Anchor Point Visibility > Graphic Object Sequence >> Graphic Annotation Units >> Graphic Dimensions >> Number of Graphic Points >> Graphic Data >> Graphic Type >> Graphic Filled
[ID of the corresponding layer] PIXEL [value] [value] [value] LEFT PIXEL 2 5 [values] POLYLINE 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.
Graphic Layer Module (0070,0060) (0070,0002)
Graphic Layer Sequence >Graphic Layer
ID
Page 21 of 92 14 June, 2007
(0070,0060) (0070,0068)
Graphic Layer Sequence >Graphic Layer Description
Circle
Graphic Annotation Module (0070,0001) Graphic Annotation Sequence (0070,0002) > Graphic Layer (0070,0008) (0070,0003) (0070,0004) (0070,0006) (0070,0010) (0070,0011) (0070,0012) (0070,0014) (0070,0015) (0070,0009) (0070,0005) (0070,0020) (0070,0021) (0070,0022) (0070,0023) (0070,0024) > Text Object Sequence >> Bounding box annotation units >> Anchor Point Annotation Units >> Unformatted Text Value >> Bounding Box Top Left Hand Corner >> Bounding Box Top Right Hand Corner >> Bounding Box Text Horizontal Justification >> Anchor Point >> Anchor Point Visibility > Graphic Object Sequence >> Graphic Annotation Units >> Graphic Dimensions >> Number of Graphic Points >> Graphic Data >> Graphic Type >> Graphic Filled
[ID of the corresponding layer] PIXEL [value] [value] [value] LEFT PIXEL 2 2 [values] CIRCLE N
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.
ID Polygon
Graphic Annotation Module (0070,0001) Graphic Annotation Sequence (0070,0002) > Graphic Layer (0070,0008) (0070,0003) (0070,0004) (0070,0006) (0070,0010) (0070,0011) (0070,0012) (0070,0014) (0070,0015) (0070,0009) (0070,0005) (0070,0020) (0070,0021) > Text Object Sequence >> Bounding box annotation units >> Anchor Point Annotation Units >> Unformatted Text Value >> Bounding Box Top Left Hand Corner >> Bounding Box Top Right Hand Corner >> Bounding Box Text Horizontal Justification >> Anchor Point >> Anchor Point Visibility > Graphic Object Sequence >> Graphic Annotation Units >> Graphic Dimensions >> Number of Graphic Points
[ID of the corresponding layer] PIXEL [value] [value] [value] LEFT PIXEL 2 [value]
Page 22 of 92 14 June, 2007
(0070,0001) (0070,0022) (0070,0023) (0070,0024)
Graphic Annotation Sequence >> Graphic Data >> Graphic Type >> Graphic Filled
[values] POLYLINE N
2.2.1.3.1.3.1.6.6
Freehand
ID Freehand
Graphic Annotation Module (0070,0001) Graphic Annotation Sequence (0070,0002) > Graphic Layer (0070,0008) (0070,0003) (0070,0004) (0070,0006) (0070,0010) (0070,0011) (0070,0012) (0070,0014) (0070,0015) (0070,0009) (0070,0005) (0070,0020) (0070,0021) (0070,0022) (0070,0023) (0070,0024) > Text Object Sequence >> Bounding box annotation units >> Anchor Point Annotation Units >> Unformatted Text Value >> Bounding Box Top Left Hand Corner >> Bounding Box Top Right Hand Corner >> Bounding Box Text Horizontal Justification >> Anchor Point >> Anchor Point Visibility > Graphic Object Sequence >> Graphic Annotation Units >> Graphic Dimensions >> Number of Graphic Points >> Graphic Data >> Graphic Type >> Graphic Filled
[ID of the corresponding layer] PIXEL [value] [value] [value] LEFT PIXEL 2 [value] [values] INTERPOLATED N
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:
ID Line
Graphic Annotation Module (0070,0001) Graphic Annotation Sequence (0070,0002) > Graphic Layer
[ID of the corresponding layer]
Page 23 of 92 14 June, 2007
(0070,0001) (0070,0009)
Graphic Annotation Sequence > Graphic Object Sequence PIXEL 2 2 [values] POLYLINE PIXEL 2 2 [values] POLYLINE -
Item for the actual line (0070,0005) >> Graphic Annotation Units (0070,0020) (0070,0021) (0070,0022) (0070,0023) (0070,0024) >> Graphic Dimensions >> Number of Graphic Points >> Graphic Data >> Graphic Type >> Graphic Filled
Item for the indication of the middle (0070,0005) >> Graphic Annotation Units (0070,0020) (0070,0021) (0070,0022) (0070,0023) (0070,0024) >> Graphic Dimensions >> Number of Graphic Points >> Graphic Data >> Graphic Type >> Graphic Filled
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:
A B
Graphic Layer Module (0070,0060) Graphic Layer Sequence (0070,0002) >Graphic Layer (0070,0068) >Graphic Layer Description Graphic Annotation Module (0070,0001) Graphic Annotation Sequence (0070,0002) > Graphic Layer (0070,0009) > Graphic Object Sequence Item for the first line (A) (0070,0005) >> Graphic Annotation Units (0070,0020) >> Graphic Dimensions (0070,0021) (0070,0022) (0070,0023) (0070,0024) >> Number of Graphic Points >> Graphic Data >> Graphic Type >> Graphic Filled
ID Perpendicular
[ID of the corresponding layer]
PIXEL 2 2 [values] POLYLINE PIXEL 2 2
Item for the second line (B) (0070,0005) >> Graphic Annotation Units (0070,0020) >> Graphic Dimensions (0070,0021) >> Number of Graphic Points
Page 24 of 92 14 June, 2007
(0070,0001) (0070,0022) (0070,0023) (0070,0024)
Graphic Annotation Sequence >> Graphic Data >> Graphic Type >> Graphic Filled
[values] POLYLINE -
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.
ID Calibration Ruler
Graphic Annotation Module (0070,0001) Graphic Annotation Sequence (0070,0002) > Graphic Layer (0070,0008) (0070,0003) (0070,0004) (0070,0006) (0070,0010) (0070,0011) (0070,0012) (0070,0014) (0070,0015) (0070,0009) First ruler line (0070,0005) (0070,0020) (0070,0021) (0070,0022) (0070,0023) (0070,0024) > Text Object Sequence >> Bounding box annotation units >> Anchor Point Annotation Units >> Unformatted Text Value >> Bounding Box Top Left Hand Corner >> Bounding Box Top Right Hand Corner >> Bounding Box Text Horizontal Justification >> Anchor Point >> Anchor Point Visibility > Graphic Object Sequence >> Graphic Annotation Units >> Graphic Dimensions >> Number of Graphic Points >> Graphic Data >> Graphic Type >> Graphic Filled
[ID of the corresponding layer] PIXEL [value] [value] [value] LEFT -
PIXEL 2 2 [values] CIRCLE N
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
Page 25 of 92 14 June, 2007
ID Angle
Graphic Annotation Module (0070,0001) Graphic Annotation Sequence (0070,0002) > Graphic Layer (0070,0008) (0070,0009) > Text Object Sequence > Graphic Object Sequence
[ID of the corresponding layer] -> 2 texts for the degrees 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.
ID Distance
Graphic Annotation Module (0070,0001) Graphic Annotation Sequence (0070,0002) > Graphic Layer (0070,0008) > Text Object Sequence (0070,0009) > Graphic Object Sequence Item for the actual line (0070,0005) >> Graphic Annotation Units (0070,0020) >> Graphic Dimensions
[ID of the corresponding layer] -> used for the distance text
PIXEL 2
Page 26 of 92 14 June, 2007
(0070,0001) (0070,0021) (0070,0022) (0070,0023) (0070,0024)
Graphic Annotation Sequence >> Number of Graphic Points >> Graphic Data >> Graphic Type >> Graphic Filled
2 [values] POLYLINE PIXEL 2 2 [values] POLYLINE -
Items for the ruler (cfr. Calibration ruler) (0070,0005) >> Graphic Annotation Units (0070,0020) (0070,0021) (0070,0022) (0070,0023) (0070,0024) >> Graphic Dimensions >> Number of Graphic Points >> Graphic Data >> Graphic Type >> Graphic Filled
2.2.1.3.1.3.1.6.12
Leg Length Difference
ID Leg Length Difference
[ID of the corresponding layer] Measurement text First horizontal line Second horizontal line Vertical line Arrow point 1 Arrow point 2 Arrow line
Page 27 of 92 14 June, 2007
2.2.1.3.1.3.1.6.13
Scoliosis
Upp
er L
ine
23
Lo we r li ne
ID Scoliosis Measurement
[ID of the corresponding layer] Measurement text 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) (0018,1602) (0018,1604) (0018,1606) (0018,1608) Shutter Shape Shutter Left Vertical Edge Shutter Right Vertical Edge Shutter Upper Horizontal Edge Shutter Lower Horizontal Edge RECTANGULAR [value] [value] [value] [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)
Page 28 of 92 14 June, 2007
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 clockwise If image is not flipped : increased with 90 (modulo 360) Otherwise : decreased with 90 (modulo 360) Rotate 90 counter clockwise If image is not flipped : decreased with 90 (modulo 360) Otherwise : increased with 90 (modulo 360) Flip horizontal
Image Rotation
(0070,0042)
Image flip
horizontal
(0070,0041)
inverted (true 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 "Workstation". 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:
Page 29 of 92 14 June, 2007
Table 2.2-11: Storage Commitment N-ACTION Information Action Type Name Request Storage Commitment Action ID 1 Type Attribute Transaction UID Storage Media FileSet ID Storage Media FileSet UID Referenced SOP Sequence >Referenced SOP Class UID >Referenced SOP Instance UID >Storage File-Set ID Media Tag (0008,1195) (0088, 0130) (0088,0140) (0008,1199) (0008,1150) (0008,1155) (0088, 0130) 3 (0088, 0140) 3 Requirement SCU 1 3 3 1 1 1 Type
>Storage Media File-Set UID
Table 2.2-12: Storage Commitment N-ACTION Response Status Handling Behavior

Service Status Success Warning Error Further Meaning Error Code 0000 Behavior successful Notification
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 Timeout Association aborted Behavior e.g. The Association is aborted using A-ABORT and command marked as failed. The reason is logged and reported to the user. 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
Page 30 of 92 14 June, 2007
2.2.1.4 2.2.1.4.1 2.2.1.4.1.1
Association Acceptance Policies Receive Storage Commitment Response Description and Sequencing of Activity
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) 3. Close Association
Figure 2.2-2: 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
Presentation Context Table Abstract Syntax Name Storage Commitment Push Model Verification UID 1.2.840.10008.1.20.1 Transfer Syntax Name List Implicit VR Little Endian Explicit VR Little Endian Implicit VR Little Endian Explicit VR Little Endian UID List 1.2.840.10008.1.2 1.2.840.10008.1.2.1 1.2.840.10008.1.2 1.2.840.10008.1.2.1 SCP None Role SCU Extended Negotiation None
1.2.840.10008.1.1
Page 31 of 92 14 June, 2007
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 Name Storage Commitment Request Successful Action ID 1 Type Attribute Transaction UID Storage Media File-Set ID Storage Media File-Set UID Referenced SOP Sequence >Referenced SOP Class UID >Referenced Instance UID SOP Tag (0008,1195) (0088,0130) (0088,0140) (0008,1199) (0008,1150) (0008,1155) (0088,0130) 3 (0088,0140) (0008,1195) (0008,1199) (0008,1150) (0008,1155) (0008,1198) (0008,1150) (0008,1155) (0008,1197) Requirement SCU 1 3 3 1 1 1 Type
>Storage Media FileSet ID >Storage Media FileSet UID Storage Commitment Request CompleteFailures Exist 2 Transaction UID Referenced SOP Sequence >Referenced SOP Class UID >Referenced SOP Instance UID Failed SOP sequence >Referenced SOP Class UID >Referenced SOP Instance UID >Failure Reason
3 1 1 1 1 1 1 1 1
The behavior of Storage AE when receiving Event Types within the N-EVENT-REPORT is summarized in the Table below:
Page 32 of 92 14 June, 2007
Table 2.2-16: Storage Commitment N-EVENT-REPORT Behavior

Event Type Name Storage Commitment Successful Storage Commitment Complete Failure exists Event ID Request 1 Request 2 Type Behavior The job will be marked as SUCCESSFUL The job will be marked as FAILED.
The reasons for returning specific status codes in a N-EVENT-REPORT response are summarized in the table below:
Table 2.2-17: Storage Commitment N-EVENT-REPORT Response Status Reasons

Service Status Success Further Meaning status Code 0000 Reasons 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
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. 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.
Page 33 of 92 14 June, 2007
2.2.2 2.2.2.1
DICOM Print Application Entity Specification SOP Classes Supported
This Application Entity provides Standard Conformance to the following SOP Class(es): Table 2.2-18: SOP Class(es) for the DICOM Print Application Entity
SOP Class Verification Basic Grayscale Print Management Meta SOP Class Basic Film Session SOP Class Basic Film Box SOP Class Basic Grayscale Image Box SOP Class Printer SOP Class Print Job SOP Class Presentation LUT SOP Class SOP Class UID 1.2.840.10008.1.1 1.2.840.10008.5.1.1.9 1.2.840.10008.5.1.1.1 1.2.840.10008.5.1.1.2 1.2.840.10008.5.1.1.4 1.2.840.10008.5.1.1.16 1.2.840.10008.5.1.1.14 1.2.840.10008.5.1.1.23 SCU Yes Yes Yes Yes Yes Yes Yes Yes SCP No No No No No No No No
2.2.2.2 2.2.2.2.1
2.2.2.2.2
"Workstation" 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 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-20: Number of Associations as an Association Initiator for DICOM Print AE Maximum number of simultaneous associations initiated 1 per (32 max) destination
2.2.2.2.3
Asynchronous Nature
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.
Page 34 of 92 14 June, 2007
2.2.2.2.4
Table 2.2-22: DICOM implementation Class and Version for DICOM Print AE Implementation Class UID Implementation Version Name 1.3.51.0.1.3 DPM1.XX 3
2.2.2.3 2.2.2.3.1 2.2.2.3.1.1
Association Initiation Policies Activity Print Images Description and Sequencing of Activity
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 "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. The default PDU size negotiated by the "Workstation" is 65542 bytes. It is possible to print up to 16 bit (see 2.4.1.2.4).
XX is the build version number
Page 35 of 92 14 June, 2007
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
16. Close Association
Figure 2.2-3: Sequencing of Receive Storage Commitment response
Page 36 of 92 14 June, 2007
2.2.2.3.1.2
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
SOP Class SOP Class Verification Basic Grayscale Print Management Meta SOP Class Print Job SOP Class Presentation LUT SOP Class SOP Class UID 1.2.840.10008.1.1 1.2.840.10008.5.1 .1.9 1.2.840.10008.5.1 .1.14 1.2.840.10008.5.1 .1.23 Transfer Syntax Name DICOM Implicit VR Little Endian DICOM Implicit VR Little Endian DICOM Implicit VR Little Endian DICOM Implicit VR Little Endian UID 1.2.840.10008.1.2 1.2.840.10008.1.2 1.2.840.10008.1.2 1.2.840.10008.1.2 SCU SCU SCU SCU None None None None Extended Negotiation
Role
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
"Workstation" 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). "Workstation"(SCU) can send the following DIMSE services:
Page 37 of 92 14 June, 2007
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: Table 2.2-24: Supported N-CREATE Attributes for a Basic Film Session
Attribute Name Number of Copies Print priority Medium Type Film destination Tag (2000,0010) (2000,0020) (2000,0030) (2000,0040) Value Always set to 1 Configurable BLUE FILM ,CLEAR FILM, PAPER (configurable) MAGAZINE, BIN-i , PROCESSOR (configurable)
"Workstation" (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 0000 0116H Status Success Warning (or Failure, depends on the selected Printer Profile) Error Meaning Film Session successfully created The SCP AE returns the attribute Value Out of Range. This may result in Image Quality Degradation. "Workstation" will continue when its destination is an AGFA printer, but stops (ABORT) when its destination is a non-AGFA printer (might lead to unacceptable image quality). The SCP AE returns the attribute Invalid Attribute Value . This indicates that the requested memory allocation cannot be provided.
0106H 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 "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 :
Page 38 of 92 14 June, 2007
Table 2.2-26: N-ACTION Status Codes

Code 0000 B601 B602 B604 C600 C601 C603 * Status Success Warning Meaning Normally returned by the SCP AE. Film(s) belonging to the film session are accepted for printing. Film session printing (collation) is not supported. Film Session SOP Instance hierarchy does not contain Image Box SOP Instances (empty page). Image size is larger then Image Box size, the image has been magnified. Film Session SOP Instance hierarchy does not contain Film Box SOP instances. Unable to create Film SOP Instance; The print queue is full (device failure). 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.
Error
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.
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. "Workstation" (SCU) can send the following DIMSE services: N-CREATE 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: Table 2.2-27: Supported N-CREATE Attributes for a Basic Film Box
Attribute Name Image Display Format Film Orientation Film Size ID Magnification type Border Density Empty Image Density Min Density Max Density Trim Tag (2010,0010) (2010,0040) (2010,0050) (2010, 0060) (2010,0100) (2010,0110) (2010,0120) (2010,0130) (2010,0140) Value STANDARD\1,1 PORTRAIT,LANDSCAPE 8INX10IN, 10INX12IN, 10INX14IN, 11INX14IN, 14INX14IN, 14INX17IN, A4, A, 14INx36IN, 14Inx51IN (configurable) NONE, REPLICATE WHITE, BLACK or ODx100 (configurable) WHITE, BLACK or ODx100 (configurable) Configurable Configurable NO
Page 39 of 92 14 June, 2007
Attribute Name Configuration Information Illumination Reflective Ambient Light Referenced Film Session Sequence >Referenced SOP Class UID >Referenced SOP Instance UID Referenced Presentation LUT Sequence >Referenced SOP Class UID >Referenced SOP Instance UID
Tag (2010,0150) (2010,015E) (2010,0160) (2010,0500) (0008,1150) (0008,1155) (2050, 0500) (0008, 1150) (0008, 1155)
Value Configurable Configurable Configurable A sequence which provides references to a Film Session SOP Class/Instance pairs. Only a single Item is permitted in this Sequence. Uniquely identifies the referenced SOP Class Uniquely identifies the referenced SOP Instance. A sequence which provides references to a Presentation LUT related SOP Class/Instance pairs. Only a single Item shall be included in this sequence. Uniquely identifies the referenced SOP Class Uniquely identifies the referenced SOP Instance.
"Workstation" (SCU) will process the N-CREATE confirmation and response Status codes. The status codes below are recognized: Table 2.2-28: N-CREATE Status Codes
Code 0000 B605 * Status Success Warning Other Status codes Meaning Normally returned by the SCP AE. Film Box successfully created. Requested Min Density or Max Density outside of printers operating range. The printer will use its respective minimum or maximum density value instead. Other Dicom error codes result in the failure of the job. Other warnings are not communicated to the user.
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. "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:
Page 40 of 92 14 June, 2007
Table 2.2-29: Supported N-SET Attributes for a Basic Grayscale Image Box
Attribute Name Image Position Polarity Tag (2020,0010) (2020,0020) Value 1 NORMAL, REVERSE 1 MONOCHROME2 larger than 0 larger than 0 8 16 8 16 7 to 15 0 A data stream of the pixel samples that comprise the Image.
Basic Grayscale Image Sequence (2020,0110) >Samples Per Pixel (0028,0002) >Photometric Interpretation (0028,0004) >Rows >Columns >Bits Allocated >Bits Stored >High Bit >Pixel Representation >Pixel Data (0028,0010) (0028,0011) (0028,0100) (0028,0101) (0028,0102) (0028,0103) (7FE0,0010)
"Workstation" (SCU) will process the N-SET confirmation and response Status codes. The status codes listed below in Table 2.2-30are recognized: Table 2.2-30: N-SET Status Codes
Code 0000 B604 B605 C603 C605 * Status Success Warning Meaning Normally returned by the SCP AE. Image successfully stored in Image Box Image size is larger then Image Box size, the image has been magnified. Requested Min Density or Max Density outside of printers operating range. The printer will use its respective minimum or maximum density value instead. Image size is larger then Image box size Insufficient memory in printer to store the image.
Error
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 wellknown SOP Instance UID. The Printer SOP Class is used to monitor the status of the printer. "Workstation" (SCU) will accept the following DIMSE services: N-EVENT-REPORT
"Workstation" (SCU) can send the following DIMSE services: 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.
Page 41 of 92 14 June, 2007
Table 2.2-31: Notification Event Information Event Name Normal Type Event Type ID 1 Attribute Printer Status Info Film Destination Printer Name Printer Status Info Film Destination Printer Name Printer Status Info Film Destination Printer Name Tag (2110, 0020) (2000, 0040) (2110, 0030) (2110, 0020) (2000, 0040) (2110, 0030) (2110, 0020) (2000, 0040) (2110, 0030)
Warning
Failure
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: Table 2.2-32: Supported Attributes for N-GET on a Printer Attribute Name
Printer Status Printer Status Info Printer Name Manufacturer Manufacturer Model Name Device Serial Number Software Versions Date Last Calibration Time Last Calibration
Tag
(2110,0010) (2110,0020) (2110,0030) (0008,0070) (0008,1090) (0018,1000) (0018,1020) (0018,1200) (0018,1201)
Value
NORMAL, WARNING, FAILURE
Printer dependent
User defined name identifying the printer. Manufacturer of the printer Manufacturers model number of the printer Manufacturers serial number of the printer Manufacturer's designation of software version of the printer. Date when the printer was last calibrated. 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. "Workstation" (SCU) will accept the following DIMSE services:
Page 42 of 92 14 June, 2007
N-EVENT-REPORT
"Workstation" (SCU) can send the following DIMSE services: N-GET
N-EVENT-REPORT is used by the SCP to report execution status changes to "Workstation" (SCU) in an asynchronous way. N-EVENT-REPORT has the following arguments : Table 2.2-33: Notification Event Information Event Type Name Pending Event Type ID 1 Attribute Execution Status Info Print Job ID Film Session Label Printer Name Execution Status Info Print Job ID Film Session Label Printer Name Execution Status Info Print Job ID Film Session Label Printer Name Execution Status Info Print Job ID Film Session Label Printer Name Tag (2100, 0030) (2100, 0010) (2000, 0050) (2110, 0030) (2100, 0030) (2100, 0010) (2000, 0050) (2110, 0030) (2100, 0030) (2100, 0010) (2000, 0050) (2110, 0030) (2100, 0030) (2100, 0010) (2000, 0050) (2110, 0030)
Printing
Done
Failure
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. "Workstation" (SCU) returns the confirmation from the N-EVENT-REPORT operation.
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. Table 2.2-34: Supported N-GET Attributes for a Print Job
Attribute Name Execution Status Tag (2100, 0020) Value PENDING, PRINTING, DONE, FAILURE
Page 43 of 92 14 June, 2007
Attribute Name Execution State Info Print Priority Creation Date Creation Time Printer Name Originator
Tag (2100, 0030) (2000, 0020) (2100, 0040) (2100, 0050) (2110, 0030) (2100, 0070)
Value Printer dependent. HIGH, MED, LOW Date of print job creation. Time of print job creation User defined name identifying the printer DICOM AE title that issued the print operation
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). A N-CREATE is issued by "Workstation" (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 (2050,0020) Name Presentation LUT Shape Supported IDENTITY (Note) Default IDENTITY
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: Table 2.2-36: N-CREATE confirmation and response Status codes
Code 0000 B605 Status Success Warning Meaning Presentation LUT successfully created Requested Min or Max Density outside of printers operating range. The printer will use its respective minimum or maximum value instead.
Page 44 of 92 14 June, 2007
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.
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.
Page 45 of 92 14 June, 2007
2.2.3 2.2.3.1
RIS Application Entity Specification SOP Classes Supported
SOP Class Name Modality Worklist Information Model FIND SOP Class UID 1.2.840.10008.5.1.4.31 SCU Yes SCP No
2.2.3.2 2.2.3.2.1
2.2.3.2.2
"Workstation" 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
2.2.3.2.3
Asynchronous Nature
Table 2.2-40: Asynchronous Nature as an Association Initiator for RIS AE Maximum number of outstanding asynchronous transactions 1
"Workstation" does not support asynchronous communication (multiple outstanding transactions over a single connection)
2.2.3.2.4
Table 2.2-41: DICOM implementation Class and Version for DICOM RIS AE Implementation Class UID Implementation Version Name
4
1.3.51.0.1.3 AGFA DTF1.0.XX 4
Page 46 of 92 14 June, 2007
2.2.3.3 2.2.3.3.1 2.2.3.3.1.1
Association Initiation Policies Activity Query RIS Description and Sequencing of Activity
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 6. Close Association
Figure 2.2-4: Sample Sequencing Diagram for Refresh Worklist
2.2.3.3.1.2
The RIS Application Entity is capable of proposing the Presentation Contexts shown in the following table: Table 2.2-42: Presentation Contexts Proposed by DICOM Store AE
Presentation Context Table Abstract Syntax Name Modality Worklist Information Model FIND UID 1.2.840.10008.5.1.4.31 Transfer Syntax Name List Implicit VR Little Endian UID List 1.2.840.10008.1.2 Role SCU Extended Negotiation None
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.
Page 47 of 92 14 June, 2007
The behavior of a RIS AE when encountering status codes in a C-FIND response is summarized in the Table below: Table 2.2-43: C-Find Response Status Handling Behavior
Service Status Success Refused Failed Cancel Pending Status Code 0000 A700 A900 C000-CFFF FE00 FF00 FF01 * Other Status codes Status Code Matching is complete Out of resources Identifier does not match SOP Class Unable to Process Matching terminated due to Cancel request Matches are continuing Current Match is supplied and any Optional Keys were supported in the same manner as Required Keys. Matches are continuing Warning that one or more Optional Keys were not supported Other Dicom error codes result in the failure of the job. Other warnings are not communicated to the user.
Exception Timeout Association aborted Behavior
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 Station AE Title Scheduled Procedure Step Start Date
Scheduled Procedure Step (0040, 0001) Single Value Matching (0040, 0002) Range Matching (0040, 0003) (0040, 0011) (0008, 0060) Single Value Matching (0040, 0007) (0040, 0006) (0040, 000B) (0040, 0010) (0040, 0008) (0040, 0012) (0040, 0009) (0032, 1070) (0040, 0020) (0040, 0400) Requested Procedure
Scheduled Procedure Step Start Time Scheduled Procedure Step Location Modality Scheduled Procedure Step Description Scheduled Performing Physician's Name Scheduled Performing Physician's ID Sequence Scheduled Station Name Scheduled Protocol Code Sequence Pre-Medication Scheduled Procedure Step ID Request Contrast Agent Scheduled Procedure Step Status Scheduled Procedure Step Comment
Page 48 of 92 14 June, 2007
Attribute name
Tag
Broad Query
Accession number query
Requested Procedure Description (0032, 1060) 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) 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 Enterers 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) Patients 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)
Wildcard matching
Page 49 of 92 14 June, 2007
Attribute name Admitting Time Scheduled Admission Date Scheduled Admission Time Admitting Diagnosis Description Admitting Diagnosis Code Sequence
Tag
Broad Query
Accession number query
(0038, 0021) (0038, 001A) (0038, 001B) (0008, 1080) (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) Patients Birth Name (0010, 1005) Patients Mothers Birth Name (0010, 1060) Medical Record Locator (0010, 1090) Referenced Patient Alias Sequence (0032,0004) Patient Demographic Patients Birth Date (0010, 0030) Patient's Sex (0010, 0040) Patients Birth Time (0010, 0032) Patients Primary Language Code Sequence (0010, 0101) >Patients Primary Language Code Modifier (0010, 0102) Sequence Patients Weight (0010, 1030) Patients Size (0010, 1020) Patients 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) Patients Insurance Plan Code Sequence (0010, 0050) Patients Address (0010, 1040) Country of Residence (0010, 2150) Region of Residence (0010, 2152) Patients Telephone Numbers (0010, 2154) Patients 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)
Page 50 of 92 14 June, 2007
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 (0019, 0010) (0019, 10F0) (0019, 10F1) (0019, 10F2) (0019, 10F3) (0019, 10F4) Description Agfa ADC NX User Defined field 1 User Defined field 2 User Defined field 3 User Defined field 4 User Defined field 5 VR LO LO LO LO LO LO
Page 51 of 92 14 June, 2007
2.2.4 2.2.4.1
MPPS Application Entity Specification SOP Classes Supported
SOP Class Name Modality Performed Procedure Step SOP Class UID 1.2.840.10008.3.1.2.3.3 SCU Yes SCP No
2.2.4.2 2.2.4.2.1
2.2.4.2.2
"Workstation" 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
2.2.4.2.3
Asynchronous Nature
Table 2.2-50: Asynchronous Nature as an Association Initiator for MPPS AE Maximum number of outstanding asynchronous transactions 1
"Workstation" does not support asynchronous communication (multiple outstanding transactions over a single connection)
2.2.4.2.4
Table 2.2-51: DICOM implementation Class and Version for DICOM MPPS AE Implementation Class UID Implementation Version Name 1.3.51.0.1.3 AGFA DTF1.0.XX 5
Page 52 of 92 14 June, 2007
2.2.4.3 2.2.4.3.1 2.2.4.3.1.1
Association Initiation Policies Activity Acquire Images, Print Images, Description and Sequencing of Activity
When the first image of a session arrives, an association will be opened to create an MPPS instance (via NCREATE) on the MPPS manager. "Workstation" 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 "Workstation", an association will be opened to complete the MPPS instance (via N-SET). Again "Workstation" 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-5: Sample Sequencing Diagram for MPPS
Page 53 of 92 14 June, 2007
2.2.4.3.1.2
The MPPS Application Entity is capable of proposing the Presentation Contexts shown in the following table: Table 2.2-52: Presentation Contexts Proposed by DICOM Store AE
Presentation Context Table Abstract Syntax Name Modality Performed Procedure Step UID 1.2.840.10008.3.1.2.3.3 Transfer Syntax Name List Implicit VR Little Endian Explicit VR Little Endian UID List 1.2.840.10008.1.2 1.2.840.10008.1.2.1 Role SCU Extended Negotiation None
2.2.4.3.1.3
N-CREATE N-SET
SOP Specific Conformance MPPS (1.2.840.10008.3.1.2.3.3)
"Workstation" (SCU) can send the following DIMSE services:
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: Table 2.2-53: N-CREATE/N-SET Response Status Handling Behavior
Service Status Success Failure Further Meaning Matching is complete Status Code 0000 Behavior The SCP has completed the operation successfully
Processing Failure 0110H Performed Procedure Step Object may no longer be updated
Page 54 of 92 14 June, 2007
Service Status *
Further Meaning Other Status codes
Status Code *
Behavior Other Dicom error codes result in the failure of the job. Other warnings are not communicated to the user.
Exception Timeout Association aborted Behavior If the sending fails, the system will retry automatically until the session is cleaned up. 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
Specific Character Set
Tag
N-CREATE
N-SET
X
(0008, 0005) X Performed Procedure Step Relationship Scheduled Step Attribute Sequence (0040, 0270) >Study Instance UID (0020, 000D) X From MWL >Referenced Study Sequence (0008, 1110) user input From MWL >>Referenced SOP Class UID (0008, 1150) user input From MWL >>Referenced SOP Instance UID (0008, 1155) user input From MWL >Accession Number (0008, 0050) user input From MWL >Placer Order Number/Imaging Service Request (0040, 2016) user input From MWL >Filler Order Number/Imaging Service Request (0040, 2017) user input From MWL >Requested Procedure ID (0040, 1001) user input From MWL >Requested Procedure Description (0032, 1060) user input From MWL >Scheduled Procedure Step ID (0040, 0009) user input From MWL >Scheduled Procedure Step Description (0040, 0007) user input From MWL >Scheduled Protocol Code Sequence (0040, 0008) user input From MWL >>Code Value (0008, 0100) user input From MWL >>Coding Scheme designator (0008, 0102) user input From MWL >>Coding Scheme Version (0008, 0103) user input
or or or or N/A or or or or or or or or or or
Page 55 of 92 14 June, 2007
Attribute
>>Code Meaning >>All other Attributes from Scheduled Protocol Code Sequence Patients Name
Tag
(0008, 0104)
N-CREATE
From MWL user input or
N-SET
From MWL or user input From MWL or Patient ID (0010, 0020) user input From MWL or Patients Birth Date (0010, 0030) user input From MWL or Patients Sex (0010, 0040) user input From MWL or Referenced Patient Sequence (0008, 1120) user input From MWL or >Referenced SOP Class UID (0008, 1150) user input From MWL or >Referenced Instance UID (0008, 1155) 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" Exam group names of the exposures in the Performed Procedure Step Description (0040, 0254) study set to the Requested Procedure Description from Performed Procedure Type Description (0040, 0255) the SPS Procedure Code Sequence (0008, 1032) Zero length Performed Procedure Step End Date (0040, 0250) Empty Performed Procedure Step End Time (0040, 0251) Empty (0010, 0010) Comments on the Performed Procedure Step (0040, 0280) Empty Performed Procedure Step Discontinuation (0040, 0281) Empty Reason Code Sequence >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 for Study ID (0020, 0010) unscheduled
"COMPLETED"
X Zero length close session date close session time only if user provided this information Available if discontinued
Page 56 of 92 14 June, 2007
Attribute
Performed Protocol Code Sequence >Code Value >Coding Scheme Designator >Coding Scheme Version >Code Meaning >All other Attributes from Performed Protocol Code Sequence Performed Series Sequence
Tag
(0040, (0008, (0008, (0008, (0008, 0260) 0100) 0102) 0103) 0104)
N-CREATE
case Empty Empty Empty Empty Empty
N-SET
Empty Empty Empty Empty Empty
(0040, 0340)
Empty If user provided this information. Otherwise empty. concatenation of CR or DX plus all exam groups of the exposures, taken in this MPPS Operator who was logged in at the Create of this MPPS X BODY PART [space] VIEW POSITION Blank X X X X X X X X X X X X X X X X X X X X X
>Performing Physicians Name
(0008, 1050)
Empty
>Protocol Name
(0018, 1030)
Empty
>Operators Name >Series Instance UID
(0008, 1070) (0020, 000E)
Empty Empty
>Series Description (0008, 103E) Empty >Retrieve AE Title (0008, 0054) Empty >Referenced Image Sequence (0008, 1140) Empty >>Referenced SOP Class UID (0008, 1150) Empty >>Referenced SOP Instance UID (0008, 1155) Empty >Referenced Non-Image Composite SOP (0040, 0220) Empty Instance Sequence >>Referenced SOP Class UID (0008, 1150) Empty >>Referenced SOP Instance UID (0008, 1155) Empty Billing And Material Management Code Module Film Consumption Sequence (0040, 0321) Empty >Number of Films (2100, 0170) Empty >Medium Type (2000, 0030) Empty >Film Size ID (2010, 0050) Empty Radiation Dose Module Total Number of Exposures (0040,0301) Empty Exposure Dose Sequence (0040,030E) Empty >Distance Source to Detector (0018,1110) Empty >Entrance Dose (0040,0302) Empty >Entrance Dose in mGy (0040,8302) Empty >KVp (0018,0060) Empty >X-ray Tube Current in A (0018,8151) Empty >Image Area Dose Product (0018,115E) Empty >Exposure Time (0018,1150) Empty >Filter Type (0018,1160) Empty >Filter Material (0018,7050) Empty
Page 57 of 92 14 June, 2007
Note:
1. 2. 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. 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. Only attributes that are specified in a SOP Instance at N-CREATE may later be updated through the NSET. If "Workstation" wishes to use the PPS Discontinuation Reason Code Sequence (0040, 0281), it creates that attribute (zero-length) during MPPS N-CREATE.
3.
Page 58 of 92 14 June, 2007
2.3
Network Interfaces
"Workstation" provides DICOM V3.0 TCP/IP Network Communication Support as defined in PS 3.8 of the DICOM Standard (2004). "Workstation" inherits its TCP/IP stack from the computer system upon which it executes.
2.3.1
Physical Medium Support
"Workstation" 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
"Workstation" can use DNS to resolve hostnames. It will use the TCP/IP stack from the Windows System it runs on. 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.
Page 59 of 92 14 June, 2007
2.4
2.4.1 2.4.1.1
Configuration
AE Title/ Presentation Address Mapping Local AE Titles
"Workstation" 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
Storage Hardcopy RIS MPPS
Default AE Title
No Default No Default No Default No Default
Default TCP/IP Port

104 Not Applicable Not Applicable 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, hostnames 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. 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
Page 60 of 92 14 June, 2007
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 - 15-bit M1 Image + VOI Lut 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 15-bit M1 Image + VOI Lut 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
Table 2.4-2: Overview of the PACS DICOM CR-Image Types supported by "Workstation".
PI (1) Description 8-bit OD 8-bit ODGAMMA 8-bit P-Value Intercept M-Lut Rescale Slope 28.1053 10.9804 -10.9804 10.9804 -10.9804 1.0 1.0 0.684 -0.684 0.684 Type 28.1054 OD OD OD OD P-VALUES P-VALUES OD OD OD Explanation 28.3003 VOI-Lut WinCenter WinWidth 28,1050 1600 1600 1600 1600 128 128 1600 1600 1600 28.1051 2800 2800 2800 2800 256 256 2800 2800 2800 P-LUT LUTShape 2050,0020 INVERSE IDENTITY X X X X X X X X X X X X X X X X X X MU1 MU2 (2) (3)
28,0004 28.1052 M1 M2 M1 M2 M1 M2 200 3000 200 3000 0.0 0.0 200 3000 200
12-bit OD 12-bit ODGAMMA
M1 M2 M1
Page 61 of 92 14 June, 2007
PI (1) M2 12-bit P-Value M1 M2 12-bit OD REL M1 M2 12-bit Image --> VOI Lut OD REL (12) 12-bit image --> VOI Lut ODGamma (12) 15-bit Image --> VOI Lut P-Value (15) M1 M2 M1 M2 M1 M2 12-bit Image --> VOI Lut OD REL (12) 12-bit Image --> VOI Lut ODGamma (12) 15-bit Image --> VOI Lut P-Value (15) M1 M2 M1 M2 M1 Intercept 3000 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
M-Lut Rescale Slope -0.684 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 Type OD P-VALUES P-VALUES OD REL OD REL LOG_E REL LOG_E REL LOG_E REL LOG_E REL P-VALUES P-VALUES LOG_E REL LOG_E REL LOG_E REL LOG_E REL P-VALUES Explanation -
VOI-Lut WinCenter WinWidth 1600 2048 2048 2048 2048 2800 4096 4096 4096 4096 - (7) - (7) - (7) - (7) - (7) - (7) - (7) - (7) - (7) - (7) WW (9)
P-LUT LUTShape INVERSE IDENTITY INVERSE IDENTITY INVERSE
MU1 MU2 (2) X X X X X X X X X X X X X X X X X (3) X X X X X
E25, NK5. - (7) E25, NK5. - (7) E25, NK5. - (7) E25, NK5. - (7) E25, NK5. - (7) E25, NK5. - (7) - (7) - (7) - (7) - (7) WC (9)
M2 0.0 1.0 P-VALUES WC (9) WW (9) IDENTITY (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
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 "Workstation" are marked with an X.
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 2.4.1.2.2.1.1
Configuration of a RIS 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.
Page 62 of 92 14 June, 2007
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 Procedure content Target region Imaging direction Coding Scheme Designator JJ1017T JJ1017P JJ1017D No. of items 1 1 0-N Code Value/Code Meaning Specified in Section 5.3 7 Specified in Section 5.4 13 Specified in Section 5.5 13
(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 "Workstation" exposure tree. Example of a Japanese SPS Example of a Scheduled Protocol Code Sequence in a Japanese SPS: Coding Scheme Designator JJ1017T JJ1017P JJ1017D JJ1017D Coding Scheme Version 1.0 1.0 1.0 1.0 Code Value GX.01.00 25.6.201 G-5200 G-A101 Code Meaning
Radiography General Radiography NOS Chest Respiratory System Lung Anterior to posterior Left lateral
This SPS schedules 2 exposures: Chest AP and Chest LL "Workstation" can be configured for the use of the Japanese system of Protocol Codes (JJ1017) by means of the "Workstation Service & Configuration Tool".
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.
See guidelines of the JIRA and JAHIS [JAPAN].
Page 63 of 92 14 June, 2007
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, hostnames 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 Table 2.4-4: Configurable Printer parameters. Parameter Name Description Use N-Events IP Address Port Number AE Title SSL Enabled Configurable (yes/no) Yes Yes Yes Yes Yes Yes Yes
2.4.1.3 2.4.1.4 2.4.1.4.1
Queue Management & Job description DICOM Store AE 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
Page 64 of 92 14 June, 2007
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 GSPSs 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,
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 "Workstation". Parameter General Parameters Max PDU Receive Size 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 duration of the Association. Max PDU Receive Size information is exchanged during DICOM Association Negotiation in the Maximum Length Sub-Item of the AASSOCIATION-RQ and A-ASSOCIATE-AC) No 65542 Configurable (yes/no) Default value
No
65542
Page 65 of 92 14 June, 2007
Parameter Time-out waiting for an acceptance or rejection response to an Association Request (Application Level Timeout) Time-out waiting for a response to an Association release request (Application Level Timeout) Time-out waiting for completion of a TCP/IP connect request (Low-level timeout) Time-out awaiting a Response to a DIMSE Request (Low-Level Timeout) Time-out for waiting for data between TCP/IPpackets (Low Level Timeout) Storage parameters Storage SCU time-out waiting for a response to a CSTORE-RQ
Configurable (yes/no) No
Default value
15 minutes
No No No No
15 minutes 100 seconds 100 seconds 100 seconds
No
15 minutes Manually: Theres no restriction of the number of retires of failed jobs as long as they arent deleted. N/A
Number of times a failed send job may be retried
No
Delay between retrying failed send jobs
No
Supported Transfer Syntaxes configurable for each remote AE)
(separately
Yes
Secure DICOM (SSL) Is Archive?8 Storage Commit Parameters Enable Storage Commit
Yes Yes
Yes
Enable secure DICOM Connection
Yes
If yes, images sent to this destination will be referenced in the MPPS.
Page 66 of 92 14 June, 2007
Parameter Timeout waiting for a Storage Commitment Notification (maximum duration of applicability for a Storage Commitment Transaction UID). Modality Worklist Parameters Modality Worklist SCU time-out waiting for the final response to a C-FIND-RQ Maximum number of Worklist Items Supported Transfer Syntaxes for Modality Worklist Delay between automatic Worklist Updates MPPS Parameters Enable MPPS Reporting MPPS SCU time-out waiting for a response to a NCREATE-RQ MPPS SCU time-out waiting for a response to a NSET-RQ Supported Transfer Syntaxes for MPPS Print Parameters Print SCU time-out waiting for a response to a NCREATE-RQ Print SCU time-out waiting for a response to a NSET-RQ Print SCU time-out waiting for a response to a NACTION-RQ Supported Transfer Syntaxes configurable for each remote printer) (separately
Configurable (yes/no) Yes
Default value
No No No Yes
15 minutes 400 Implicit VR Little Endian Explicit VR Little Endian
Yes No No No 15 minutes 15 minutes Implicit VR Little Endian Explicit VR Little Endian
No No No No No
10 minutes 10 minutes 10 minutes Taken from printer device model provided by Agfa. Automatically : 8 times 2 times immediately, then the job gets parked for 3 minutes and retried 3 times again. In case the job still fails, it is parked for 5 minutes and retried 3 times. 10 minutes
Number of times a failed print-job may be retried
Delay between retrying failed print-jobs
No
Print SCU time-out waiting for a response to a NCREATE-RQ
No
Page 67 of 92 14 June, 2007
3
3.1
MEDIA INTERCHANGE
"Workstation" is able to create or read DICOM Interchange media. The related capabilities are described in the following sections.
Implementation Model
Export To CD-R
Offline-Media Application Entity
Export
CD-R 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 3.1.3
Functional Definition of AEs 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 "Workstation".
3.1.4
File Meta Information for Implementation Class and Version
The implementation information written to the File Meta Header in each file is:
Page 68 of 92 14 June, 2007
Table 3.1-1: AE Related Application Profiles, Real World Activities and Roles
Implementation Class UID Implementation Version Name 1.3.51.0.1.3 AGFA DTF1.0.XX
9
3.2
3.2.1
AE Specifications
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 Portable data for imaging Real-World Activity Export to CD-R Roles FSC (creation of a File-Set) SC Option Interchange
3.2.1.1 3.2.1.1.1
Real World Activities 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 IDs, patient related information and all related physicians 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
XX is the build version number.
Page 69 of 92 14 June, 2007
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 Patients Name Study Instance UID Modality Series Instance UID Laterality Series description Protocol name Body Part Examined Smallest Pixel Value in Series Largest Pixel Value in Series Presentation Intent Type SOP Instance UID SOP Class UID Specific character set Patient Orientation Image type Image comments Presentation LUT shape Tag (0010,0010) (0020,000D) (0008,0060) (0020,000E) (0020,0060) (0008,103E) (0018,1030) (0018,0015) (0028,0108) (0028,0109) (0008,0068) (0008,0018) (0008,0016) (0008,0005) (0020,0020) (0008,0008) (0020,4000) (2050,0020) Set to Anonymous Keep value Keep value Keep value Keep value Keep value Keep value Keep value Keep value Keep value Keep value Keep value Keep value Keep value Keep value Keep value Keep value 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: IODS, SOP Classes and Transfer syntaxes for offline media IOD
CR Image Storage Digital X-Ray Image Storage For Presentation
SOP Class UID

1.2.840.10008.5.1.4.1.1.1
Transfer Syntax
Explicit VR Little Endian
Transfer Syntax UID

1.2.840.10008.1.2.1
1.2.840.10008.5.1.4.1.1.1.1
1.2.840.10008.1.2.1
Page 70 of 92 14 June, 2007
IOD
Digital X-Ray Image Storage For Processing Grayscale Softcopy Presentation State Storage Digital Mammography Image Storage For Presentation Digital Mammography Image Storage For Processing
SOP Class UID

1.2.840.10008.5.1.4.1.1.1.1.1
Transfer Syntax
Transfer Syntax UID

1.2.840.10008.1.2.1
1.2.840.10008.5.1.4.1.1.11.1 1.2.840.10008.5.1.4.1.1.1.2 1.2.840.10008.5.1.4.1.1.1.2.1
Explicit VR Little Endian Implicit VR Little Endian Implicit VR Little Endian
1.2.840.10008.1.2.1
1.2.840.10008.1.2 1.2.840.10008.1.2
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".
Page 71 of 92 14 June, 2007
SUPPORT FOR EXTENDED CHARACTER SETS
"Workstation" supports the following character sets:
ISO-IR 6 (default) ISO-IR 100 ISO-IR 101 ISO-IR 109 ISO-IR 110 ISO-IR 148 ISO-IR 126 ISO-IR 144 ISO-IR 127 ISO-IR 13
Basic G0 Set Latin Alphabet No. 1 Latin Alphabet No. 2 Latin Alphabet No. 3 Latin Alphabet No. 4 Latin Alphabet No. 5 Greek Cyrillic Arabic Japanese Hebrew GB18030-2000 Big 5 GB 2313-80 ASCII and Kanji 13 Katakana, Romaj and Kanji Japanese suppl. Kanji Greek Cyrillic Hebrew Korean Arabic Latin alphabet No 1 Latin alphabet No 2 Latin alphabet No 3 Latin alphabet No 4 Latin alphabet No 5 Unicode
ISO-IR 138 Chinese Character Sets GB18030 ISO 2022 B5
ISO 2022 GBK Japanese Character Sets ISO 2022 IR 87 ISO 2022 IR ISO 2022 IR 87
ISO 2022 IR 159 Other Character Sets ISO 2022 IR 126 ISO 2022 IR 144 ISO 2022 IR 138 ISO 2022 IR 149 ISO 2022 IR 127 ISO 2022 IR 100 ISO 2022 IR 101 ISO 2022 IR 109 ISO 2022 IR 110 ISO 2022 IR 148 UTF-8
Page 72 of 92 14 June, 2007
5
5.1
SECURITY Security Profiles

Basic TLS Secure Transport Connection Profile Basic Network Address Management Profile Basic Time synchronization Profile
The workstation supports the following profiles:
5.2
Association Level Security
"Workstation" 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
"Workstation" 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 "Workstation" can be configured to get its time from an NTP-server.
Page 73 of 92 14 June, 2007
6
6.1
6.1.1
ANNEXES IOD Contents

Created SOP Instances
The following tables use a number of abbreviations. The abbreviations used in the Presence of...- column, are: VNAP ANAP ALWAYS EMPTY Value Not Always Present (attribute sent zero length if no value is present) Attribute Not Always Present Always Present with a value Attribute is sent without a value
The abbreviations used in the Source-column: USER AUTO MWL. CONFIG the attribute value source is from User input the attribute value is generated automatically the attribute value is the value received from the Modality Worklist the attribute value source is a configurable parameter
6.1.1.1
Common Modules
Table 6.1-1: Common Modules

Attribute Name Tag VR Value Presence of Value Source
Patient's Name Patient ID Issuer of Patient ID Other Patient IDs Other Patient Names Patients Birth Name Patients Mothers Birth Name Medical Record Locator Patients Age Occupation Confidentiality Constraint Patient Data Description Patient's Birth Date Patients Birth Time Patient's Sex
Patient Patient Identification (0010, 0010) PN (0010, 0020) LO (0010, 0021) LO (0010,1000) LO (0010,1001) PN (0010, 1005) PN (0010, 1060) PN (0010, 1090) LO Patient Demographic (0010, 1010) AS (0010, 2180) SH on (0040, 3001) (0010, 0030) (0010, 0032) (0010, 0040) (0010, 0050) LO DA TM CS SQ
VNAP VNAP ANAP ANAP ANAP ANAP ANAP ANAP ANAP ANAP ANAP VNAP VNAP VNAP ANAP
User / MWL User / MWL MWL MWL MWL MWL MWL MWL User / MWL MWL MWL User / MWL User / MWL User / MWL MWL
Patient's Insurance Plan Code Sequence
Page 74 of 92 14 June, 2007
Attribute Name
Tag
VR
Value
Presence of Value
Source
> Code Sequence > Patients Primary Language Code Modifier Sequence >> Code Sequence Patient's Size Patient's Weight Patients Address Military Rank Branch of Service Country of Residence Region of Residence Patients Telephone Numbers
Ethnic Group
(0010, 0102) (0010, 1020) (0010, 1030) (0010, 1040) (0010, 1080) (0010, 1081) (0010, 2150) (0010, 2152) (0010, 2154) (0010,2160) (0010, 21F0) (0010,4000) (0008, 1120) (0008, 1150) (0008, 1155) (0038, 0008) (0038, 0300) (0038, 0400) (0038, 4000) (0010, 2000) (0010, 2110) (0010, 21A0) (0010, 21C0) (0010, 21D0) (0038, 0050) (0038, 0500) (0010, 21B0)
SQ DS DS LO LO LO LO LO SH SH LO LT
ANAP ANAP ANAP ANAP ANAP ANAP ANAP ANAP ANAP ANAP ANAP ANAP ANAP ANAP ANAP ANAP ANAP ANAP ANAP ANAP ANAP ANAP ANAP ANAP ANAP ANAP ANAP
MWL User / MWL User / MWL MWL User / MWL User / MWL MWL MWL MWL User / MWL MWL User / MWL MWL MWL MWL MWL MWL MWL Auto MWL MWL User / MWL User / MWL User / MWL MWL MWL MWL
Patient's Religious Preference Patient Comments Referenced Patient Sequence >Referenced SOP Class UID >Referenced SOP Instance UID Visit Status ID Current Patient Location Patients Institution Residence Visit Comments Medical Alerts Contrast Allergies Smoking Status Pregnancy Status Last Menstrual Date Special Needs Patient State Additional Patients History
Visit Status
SQ UI UI CS LO LO LT
Patient Medical
LO LO CS US DA LO LO LT Study General Study 000D) UI 0020) DA 0030) TM 0090) PN SQ Requested Procedure ID or generated for unscheduled (app A IHE note 5) Performed Procedure Description
Study Instance UID Study Date Study Time Referring Physician's Name Referring Physician Identification Sequence
(0020, (0008, (0008, (0008,
ALWAYS ALWAYS ALWAYS VNAP ANAP
MWL / Auto Auto Auto User / MWL MWL
(0008, 0096)
Study ID Accession Number Study Description
(0020, 0010) (0008, 0050) (0008, 1030)
SH SH LO
ALWAYS VNAP ANAP
Auto / MWL User / MWL Auto
step
Page 75 of 92 14 June, 2007
Attribute Name Physician(s) of Record
Tag (0008, 1048) (0008, 1049) (0008, 1060) (0008, 1062) (0008, 1120) (0008, 1150) (0008, 1155) (0008, 1032)
VR PN SQ PN
Value
Presence of Value ANAP ANAP ANAP ANAP ANAP ANAP ANAP ANAP ANAP ANAP ANAP ANAP ANAP ANAP ANAP
Source MWL MWL MWL User MWL MWL MWL MWL MWL MWL User / MWL User / MWL User / MWL MWL MWL
Physician(s) of Record Identification Sequence Name of Physician(s) Reading Study Physician(s) Reading Study Identification Sequence Referenced Patient Sequence >Referenced SOP Class UID >Referenced SOP Instance UID
Procedure Code Sequence Admitting Diagnoses Description Admitting Diagnoses Code Sequence Patients Age Patient's Size Patient's Weight Occupation Additional Patients History
SQ UI
UI SQ Patient Study (0008, 1080) LO (0008, 1084) (0010, 1010) (0010, 1020) (0010, 1030) (0010, 2480) (0010, 21B0) SQ AS DS DS SH LT Series General Series
Modality Series Instance UID Series Number Laterality Performing Physicians Name Performing Physicians Identification Sequence Protocol Name Series Description
(0008,0060) (0020,000E) (0020, 0011) (0020,0060) (0008, 1050) (0008, 1050) (0018, 1030) (0008, 103E)
CS UI IS CS PN SQ LO LO Exposure Type Name Depending on security setting either auto filled in with login Different image for each
ALWAYS ALWAYS ALWAYS ALWAYS ANAP ANAP ANAP ALWAYS
Config, >Archive settings SOP Class Auto Auto User / Auto User MWL Auto Auto
Based on protocol code
Operators' Name Referenced Performed Procedure Step Sequence >Referenced SOP Class UID >Referenced SOP Instance UID Related Series Sequence > Study Instance UID > Series instance UID >Purpose of Reference Code Sequence Patient Position Smallest Pixel Value in Series
(0008, 1070) (0008, 1111) (0008, 1150) (0008, 1155) (0008, 1250) (0020, 000D) (0020, 000E) (0040, A170) (0018, 5100) (0028, 0108)
PN SQ UI UI SQ UI UI SQ CS US
ALWAYS ANAP ANAP ANAP ANAP
User / Auto Auto Auto Auto MWL
Empty
ANAP NEVER
Page 76 of 92 14 June, 2007
Attribute Name Largest Pixel Value in Series Request Attributes Sequence >Requested Procedure ID >Reason for the Requested Procedure >Reason for Requested Procedure Code Sequence >Scheduled Procedure Step ID >Scheduled Procedure Step Description >Scheduled Protocol Code Sequence >> Protocol Context Sequence >>>Content Item Modifier Sequence Performed Procedure Step ID Performed Procedure Step Description Performed Procedure Step Start Date Performed Procedure Step Start Time Performed Protocol Code Sequence > Code Value > Code Scheme Designator > Code Meaning > Protocol Context Sequence >>Content Item Modifier Sequence Comments on the Performed Procedure Step
Tag (0028, 0109) (0040, 0275) (0040, 1001) (0040, 1002) (0040, 100A) (0040, 0009) (0040, 0007) (0040, 0008) (0040, 0440) (0040, 0441) (0040, 0253)
VR US SQ SH LO SQ SH LO SQ SQ SQ SH
Value
Presence of Value NEVER ANAP ANAP
Source
MWL MWL
ANAP ANAP
10
MWL MWL MWL
ANAP
(0040, 0254) (0040, 0244) (0040, 0245) (0040, 0260) (0008, 0100) (0008, 0102) (0008, 0104) (0040, 0440) (0040, 0441) (0040, 0280)
LO DA TM SQ SH SH SH SQ SQ
ANAP Exam group names of exposures in the study
Auto
Auto Auto Auto
ANAP ANAP ANAP ANAP ANAP ANAP ANAP
MWL / User MWL / User MWL / User MWL / User MWL / User MWL / User Auto
Station Name Institution Name Institution Address Institutional Department Name Manufacturer Manufacturers Model Name Device Serial Number Software Versions
LO Equipment General Equipment (0008, 1010) SH (0008, 0080) LO (0008, 0081) ST (0008, 1040) LO (0008, 0070) (0008, 1090) (0018, 1000) (0018, 1020) LO
ANAP ANAP ANAP ALWAYS ALWAYS ALWAYS ANAP
LO LO LO Image General Image
Auto MWL/ Config MWL /Config MWL/ Config Auto (from digitizer) Auto (from digitizer) Auto Auto
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".
Page 77 of 92 14 June, 2007
Attribute Name Instance Number Patient Orientation Content Date Content Time Image Type Acquisition Number Acquisition Date Acquisition Time Acquisition Datetime Referenced Image Sequence > Referenced SOP Class UID > Referenced SOP Instance UID > Referenced Frame Number > Purpose of Reference Code Sequence Derivation description Source Image Sequence > Referenced SOP Class UID > Referenced SOP Instance UID > Referenced Frame Number > Purpose of Reference Code Sequence Referenced Waveform Sequence > Purpose of Reference Code Sequence Images in Acquisition Image Comments Quality Control Image Burned in Annotation Lossy Image Compression Lossy Image Compression Ratio Lossy Image Compression Method Presentation LUT Shape Samples per Pixel 11 Photometric Interpretation Rows Columns Pixel Aspect Ratio Bits Allocated Bits Stored High Bit 12 Pixel Representation
11 12
Tag (0020, 0013) (0020, 0020) (0008, 0023) (0008, 0033) (0008, 0008) (0020, 0012) (0008, 0022) (0008, 0032) (0008, 002A) (0008, 1140) (0008, 1150) (0008, 1155) (0008, 1160) (0040, A170) (0008, 2111) (0008, 2112) (0008, 1150) (0008, 1155) (0008, 1160) (0040, A170) (0008, 113A) (0040, A170) (0020, 1002) (0020, 4000) (0028, 0300) (0028, 0301) (0028, 2110) (0028, 2112) (0028, 2114) (2050, 0020) (0028, 0002) (0028, 0004) (0028, 0010) (0028, 0011) (0028, 0034) (0028, 0100) (0028, 0101) (0028, 0102) (0028, 0103)
VR CS IS DT TM CS IS DA TM DT SQ UI UI IS SQ ST SQ UI UI IS SQ SQ SQ IS LT CS CS CS DS
Value
Presence of Value ALWAYS ALWAYS VNAP VNAP ALWAYS ANAP ALWAYS ALWAYS ALWAYS ANAP ANAP ANAP ANAP ANAP ANAP ANAP
Source Auto Auto Auto Auto Auto Auto Auto / User Auto / User Auto
Auto Auto
NEVER ANAP NEVER ANAP When exposure is defined as QC in study tree No ANAP ALWAYS EMPTY ANAP ANAP ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ANAP ALWAYS ALWAYS ALWAYS ALWAYS Auto User Auto Fixed Empty Auto Auto Config Fixed Auto Auto Auto Auto Auto Auto Auto Auto
CS CS Image Pixel US 1 CS M1 or M2 US US IS US US US US
Fixed M1 when using DX for Processing
Depends on digitizer type. In case of DX for Processing, the pixel representation is fixed 0
Page 78 of 92 14 June, 2007
Attribute Name Pixel Data Planar Configuration Smallest Image Pixel Value Largest Image Pixel Value Red Palette Color Lookup Table descriptor Green Palette Color Lookup Table descriptor Blue Palette Color Lookup Table descriptor Red Palette Color Lookup Table data Green Palette Color Lookup Table data Blue Palette Color Lookup Table data SOP Class UID SOP Instance UID Specific Character Set Instance Creation Date Instance Creation Time Related General SOP Class UID Original Specialized SOP Class UID Coding Scheme Identification Sequence > Code Scheme Designator > Coding Scheme Registry > Coding Scheme UID > Coding Scheme External ID > Coding Scheme Name > Responsible Organization Timezone Offset From UTC Contributing Equipment Sequence > Manufacturer > Institution Name > Institution Address
Tag (7FE0, 0010) (0028, 0006) (0028, 0106) (0028, 0107) (0028, 1101) (0028, 1102) (0028, 1103) (0028, 1201) (0028, 1202)
VR OB US US US US US US OW OW
Value
Presence of Value ALWAYS NEVER NEVER NEVER NEVER NEVER NEVER NEVER NEVER NEVER ALWAYS ALWAYS ANAP ALWAYS ALWAYS NEVER NEVER NEVER NEVER NEVER NEVER NEVER NEVER NEVER NEVER ALWAYS ANAP ANAP
Source Auto
(0028, 1203) OW SOP Common (0008, 0016) UI (0008, 0018) UI (0008, 0005) CS (0008, 0012) DA (0008, 0013) TM (0008, 001A) UI (0008, 001B) (0008, 0110) (0008, 0102) (0008, 0112) (0008, 010C) (0008, 0114) (0008, 0115) (0008, 0116) (0008, 0201) (0018, A001) (0008,0070) (0008,0080) (0008,0081) UI SQ SH LO UI ST ST ST SH SQ LO LO ST
Fixed Auto Config Auto Auto
Config Config MWL / Config Config:Station name of the digitizer known on NX MWL / Config Auto Auto Auto
> Station Name > Institutional Department Name > Manufacturers Model Name > Device Serial Number > Software Versions > Spatial Resolution > Date of Last Calibration > Time of Last Calibration > Contribution DateTime
(0008,1010) (0008,1040) (0008,1090) (0018,1000) (0018,1020) (0018,1050) (0018,1200) (0018,1201) (0018,A002)
SH LO LO LO LO DS DA TM DT
ALWAYS ANAP ALWAYS ALWAYS ALWAYS NEVER NEVER NEVER NEVER
Page 79 of 92 14 June, 2007
Attribute Name > Contribution Description Instance Number SOP Instance Status SOP Authorization Date and Time SOP Authorization Comment Authorization Equipment Certification Number Encrypted Attributes Sequence >Encrypted Content Transfer Syntax UID >Encrypted Content
Tag (0018,A003) (0020,0013) (0100,0410) (0100,0420) (0100,0424) (0100,0426) (0400,0500)
VR ST IS CS DT LT LO SQ
Value
Presence of Value NEVER ALWAYS NEVER NEVER NEVER NEVER NEVER NEVER NEVER
Source
Auto
Plate sensitivity
Plate erasability Requested Procedure Description
(0400,0510) UI (0400,0520) OB Private attributes Only available in case that the image was scanned using a non-Compact family (0019,10F6) DS digitizer. Only available in case that the image was scanned using a non-Compact family (0019,10F7) DS digitizer. (0032,1060) LO
ANAP
Auto
ANAP ANAP
Auto Manual/MWL
6.1.1.2 6.1.1.2.1
CR CR Image IOD
Table 6.1-2: IOD of Created CR Image SOP Instances

IE Patient Study Series Equipment Image Module Patient Identification Extended Patient General Study Patient Study General Series CR Series General Equipment General Image Image Pixel CR Image Modality LUT VOI LUT SOP Common Reference Table 6.1-1 Table 6.1-1 Table 6.1-1 Table 6.1-1 Table 6.1-1 Table 6.1-3 Table 6.1-1 Table 6.1-1 Table 6.1-1 Table 6.1-3 Table 6.1-3 Table 6.1-3 Table 6.1-1 Presence of Module ALWAYS If received from MWL ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS
Page 80 of 92 14 June, 2007
6.1.1.2.2
CR Modules
Table 6.1-3: CR Modules of Created SOP Instances

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

IE Patient Study Series Equipment Image Module Patient Identification Extended Patient General Study Patient Study General Series DX Series General Equipment General Image Image Pixel Display Shutter DX Anatomy DX Image DX Detector X-Ray acquisition dose X-Ray Collimator DX Positioning VOI LUT Acquisition Context SOP Common Reference Table 6.1-1 Table 6.1-1 Table 6.1-1 Table 6.1-1 Table 6.1-1 Table 6.1-5 Table 6.1-1 Table 6.1-1 Table 6.1-1 Table 6.1-5 Table 6.1-5 Table 6.1-5 Table 6.1-5 Table 6.1-5 Table 6.1-5 Table 6.1-5 Table 6.1-5 Table 6.1-5 Table 6.1-1 Presence of Module ALWAYS If received from MWL ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS When shutter is applied ALWAYS ALWAYS ALWAYS When the XRDI Module is installed When the XRDI Module is installed ALWAYS ALWAYS ALWAYS
6.1.1.3.2
DX Modules
Table 6.1-5: DX Module of Created SOP Instances

Modality Referenced Performed Procedure
(0008, 0060) (0008, 1111)
Series DX Series CS DX SQ
ALWAYS ANAP
Config Auto
Page 82 of 92 14 June, 2007
Attribute Name Step Sequence > Referenced SOP Class UID > Referenced SOP Instance UID Presentation Intent Type
Tag
VR
Value
Presence of Value ANAP ANAP ALWAYS
Source
(0008, 1150) (0008, 1155) (0008, 0068)
UI UI For Processing/For Presentation Image Display Shutter CS IS IS IS IS IS US DX Anatomy SQ CS SQ CS 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 (used by Auto-QC2)
Auto Auto Config
Shutter Shape Shutter Left Vertical Edge Shutter Right Vertical Edge Shutter Upper Horizontal Edge Shutter Lower Horizontal Edge Vertices of the Polygonal Shutter Shutter Presentation Value Anatomic Region Sequence > Anatomic Region Modifier Sequence Image Laterality
(0018, 1600) (0018, 1602) (0018, 1604) (0018, 1606) (0018, 1608) (0018, 1620) (0018, 1622) (0008,2218) (0008, 2220) (0020, 0062)
ANAP ANAP ANAP ANAP ANAP ANAP ANAP ANAP ANAP ALWAYS
User User User User User User User Config / User Config Config / User
Image Type Samples per Pixel Photometric Interpretation Bits Allocated Bits Stored High Bit Pixel Representation Pixel Intensity Relationship Pixel Intensity Relationship Sign Rescale Intercept 13 28 Rescale Slope Rescale Type Presentation LUT Shape Lossy Image Compression Lossy Image Compression Ratio Derivation Description Acquisition Device Processing Description Acquisition Device Processing Code
13
(0008, 0008) (0028, 0002) (0028, 0004) (0028, 0100) (0028, 0101) (0028, 0102) (0028, 0103) (0028, 1040) (0028, 1041) (0028, 1052) (0028, 1053) (0028, 1054) (2050, 0020) (0028, 2110) (0028, 2112) (0008, 2111) (0018, 1400) (0018, 1401)
CS US CS US US US US CS SS DS DS LO CS CS DS ST LO LO
0 and 1 0 and 1 IDENTITY 00
ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ANAP ANAP ANAP ANAP
Auto Auto Config Auto Auto Auto Auto Auto Auto Config Config Config Fixed Fixed Auto Auto Auto Auto
Fixed when using DX for Processing
Page 83 of 92 14 June, 2007
Attribute Name Patient Orientation Calibration Image Burned in Annotation VOI LUT Sequence >LUT Descriptor >LUT Explanation >LUT Data Window Center Window Width Window Center & Explanation Detector Type Detector Configuration
Tag (0020, 0020) (0050, 0004) (0028, 0301) (0028, 3010) (0028, 3002) (0028, 3003) (0028, 3006) (0028, 1050) (0028, 1051) Width (0028, 1055) (0018, 7004) (0018, 7005)
VR CS CS CS SQ SS LO SS DS DS
Value
Presence of Value ALWAYS ANAP ALWAYS ANAP ANAP ANAP ANAP ANAP ANAP ANAP ANAP (1) ANAP
Source Auto Config Fixed Auto Auto Auto Auto Auto Auto Auto Auto Auto
YES
LO DX Detector CS CS 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 (e.g. MD10) For the DX/S family of digitizers, this is the Image plate ID. For the ADC Compact family of digitizers, this is the cassette ID.
Detector Description Detector Mode
(0018, 7006) (0018, 7008)
LT LT
ALWAYS ANAP(1)
Auto Auto
Detector ID Date of Last Detector Calibration Exposures on Detector Since Last Calibration Exposures on Detector Since Manufactured Detector Time Since Last Exposure Detector Active Time Detector Activation Offset From Exposure Detector Binning Detector Manufacturer Name Detector Manufacturers Model Name Detector Conditions Nominal Flag Detector temperature Sensitivity Field of View Shape Field of view Dimension(s) Field of View Origin Field of View Rotation
(0018, 700A) (0018, 700C) (0018, 7010) (0018, 1404) (0018, 7012) (0018, 7014) (0018, 7016) (0018, 701A) (0018, 702A) (0018, 702B) (0018, 7000) (0018, 7001) (0018, 6000) (0018, 1147) (0018, 1149) (0018, 7030) (0018, 7032)
SH DA IS IS DS DS DS DS LO LO CS DS DS CS IS DS DS
ALWAYS ANAP ANAP ANAP ANAP(1) ANAP(1) ANAP ANAP (1) ANAP (1) ANAP ANAP (1) ANAP (1) ALWAYS ANAP (1) (1) ANAP ANAP (1) ANAP
(1) (1)
Auto Auto Auto Auto Auto Auto Auto Auto Auto Auto Auto Auto Config / User Auto Auto Auto User
Page 84 of 92 14 June, 2007
Attribute Name Field of View Horizontal Flip Imager Pixel Spacing Pixel Spacing Detector Element Physical Size Detector Element Spacing Detector Active Shape Detector Active Dimension(s) Detector Active Origin Collimator Shape Collimator Left Vertical Edge Collimator Right Vertical Edge Collimator Upper Horizontal Edge Collimator Lower Horizontal Edge Center of Circular Collimator Radius of Circular Collimator Vertices of the Polygonal Collimator Projection Eponymous Name Code Sequence Patient Position View Position View Code Sequence Patient Orientation Code Sequence Patient Orientation Modifier Code Sequence Patient Gantry Relationship Code Sequence Distance Source to Patient Distance Source to Detector Estimated Radiographic Magnification Factor Positioner Type Positioner Primary Angle Positioner Secondary Angle Detector Primary Angle Detector Secondary Angle Body Part Thickness Compression Force KVP X-Ray Tube Current X-Ray Tube Current in A Exposure Time Exposure Time in s Exposure Exposure in As
Tag (0018, 7034) (0018, 1164) (0028, 0030) (0018, 7020) (0018, 7022) (0018, 7024) (0018, 7026) (0018, 7028) (0018, 1700) (0018, 1702) (0018, 1704) (0018, 1706) (0018, 1708) (0018, 1710) (0018, 1712) (0018, 1720)
VR CS DS DS DS DS CS
Value
Presence of Value ANAP ALWAYS ALWAYS ANAP ANAP ALWAYS ALWAYS ANAP ANAP ANAP ANAP ANAP ANAP ANAP ANAP ANAP
Source User Auto Auto Auto Auto Fixed Auto Auto Auto / User Auto / User Auto / User Auto / User Auto / User Auto / User Auto / User Auto / User
DS DS X-Ray Collimator CS IS IS IS IS IS IS IS DX Positioning SQ CS CS SQ SQ SQ SQ DS DS
RECTANGLE Cassette size translated into MM
(0018, 5104) (0018, 5100) (0018, 5101) (0054, 0220) (0054, 0410) (0054, 0412) (0054, 0414) (0018, 1111) (0018, 1110)
Based on protocol code
ANAP ANAP ALWAYS ANAP ANAP (1) ANAP (1) ANAP ANAP (1) ANAP (1) ANAP (1) ANAP ANAP (1) ANAP (1) (1) ANAP (1) ANAP ANAP ANAP ANAP (1) ANAP ANAP (1) ANAP (1) (1) ANAP ANAP (1) (1) ANAP
(1) (1) (1)
Auto User Auto / User Auto Auto Auto Auto Auto Auto User/XRDI Auto Auto Auto Auto Auto (1) User/XRDI (1) User/XRDI
(1) (1)
(0018, 1114) DS (0018, 1508) CS (0018, 1510) DS (0018, 1511) DS (0018, 1510) DS (0018, 1511) DS (0018, 11A0) DS (0018, 11A2) DS X-Ray Acquisition dose (0018, 0060) DS (0018, 1151) IS (0018, 8151) IS (0018, 1150) IS (0018, 8150) IS (0018, 1152) IS (0018, 1153) IS
User/XRDI (1) User/XRDI (1) User/XRDI (1) User/XRDI (1) User/XRDI (1) User/XRDI Auto
Page 85 of 92 14 June, 2007
Attribute Name Distance Source to Detector Distance Source to Patient Image Area Dose Product Body Part Thickness Relative X-Ray Exposure Entrance Dose Entrance Dose in mGy Exposed Area Distance Source to Entrance Comments on Radiation Dose X-Ray Output Half Value Layer Organ Dose Organ Exposed Anode target Material Filter Material Filter Thickness Minimum Filter Thickness Maximum Grid Grid Absorbing Material Grid Pitch Grid Thickness Exposure Control Mode Exposure Control Mode Description Phototimer Setting Image and Fluoroscopy Area Dose Product Grid Focal Distance Rectification Type VOI LUT Sequence >LUT Descriptor >LUT Explanation >LUT Data Window Center Window Width Window Center Explanation
Tag (0018, 1110) (0018, 1111) (0018, 115E) (0018, 11A0) (0018, 1405) (0040, 0302) (0040, 8302) (0040, 0303) (0040, 0306) (0040, 0310) (0040, 0312) (0040, 0314) (0040, 0316) (0040, 0318) (0018, 1191) (0018, 7050) (0018, 7052) (0018, 7054) (0018, 1166) (0018, 7040) (0018, 7044) (0018, 7042) (0018, 7060) (0018, 7062) (0018, 7065) (0018, 115E) (0018, 704C) (0018, 1156) (0028, (0028, (0028, (0028, (0028, (0028, & Width (0028, 1055) 3010) 3002) 3003) 3006) 1050) 1051)
VR DS DS DS DS IS US US US DS ST DS DS DS CS CS CS DS DS CS LT DS DS CS LT DS
Value
Presence of Value ANAP (1) ANAP (1) ANAP (1) (1) ANAP
Source User/XRDI Auto Auto (1) User/XRDI Auto (1) User/XRDI (1) User/XRDI Auto Auto Auto Auto Auto (1) User/XRDI Auto (1) User/XRDI (1) User/XRDI Auto Auto (1) User/XRDI (1) User/XRDI (1) User/XRDI (1) User/XRDI User/XRDI
(1) (1) (1)
Lgm value multiplied by 100
ANAP (1) ANAP (1) ANAP ANAP (1) ANAP (1) ANAP (1) ANAP (1) ANAP (1) (1) ANAP ANAP (1) ANAP (1) ANAP (1) ANAP (1) ANAP (1) ANAP (1) ANAP (1) ANAP (1) ANAP (1) ANAP (1) ANAP (1) ANAP (1) ANAP (1) (1) ANAP (1) ANAP ANAP ANAP ANAP ANAP ANAP ANAP ANAP EMPTY EMPTY EMPTY EMPTY EMPTY EMPTY EMPTY
- Manual - Automatic
User/XRDI (1) User/XRDI User/XRDI (1) User/XRDI Auto Auto Auto Auto Auto Auto Auto Auto Fixed Fixed Fixed Fixed Fixed Fixed Fixed
(1)
DS DS CS VOI LUT SQ SS LO SS DS DS
Acquisition Context Sequence > Value Type > Concept Name Code Sequence > Referenced Frame numbers > Numeric Value > Measurement Units Code Sequence > Date
LO Acquisition Context (0040, 0555) SQ (0040, A040) CS (0040, A043) SQ (0040, A136) US (0040, A30A) DS (0040, 08EA) (0040, A121) SQ DT
Page 86 of 92 14 June, 2007
Attribute Name > Time > Person Name > Text Value > Concept Code Sequence Acquisition Context Description
Tag (0040, A122) (0040, A123) (0040, A160) (0040, A168) (0040, 0556)
VR
Value
Presence of Value EMPTY EMPTY EMPTY EMPTY (2) ANAP or ALWAYS
Source Fixed Fixed Fixed Fixed Auto
Cassette orientation
(1)
TM PN UT SQ ST Private attributes LANDSCAPE (0019,10F5) CS PORTRAIT
Auto
: 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 6.1.1.4.1
MG MG Image IOD
Table 6.1-6: IOD of Created MG Image SOP Instances
IE Patient Study Series
Module Patient Identification Extended Patient General Study Patient Study General Series DX Series Mammography Series General Equipment General Image Image Pixel Display Shutter DX Anatomy DX Image DX Detector X-Ray acquisition dose X-Ray Collimator DX Positioning Mammography Image VOI LUT Acquisition Context SOP Common
Reference Table 6.1-1 Table 6.1-1 Table 6.1-1 Table 6.1-1 Table 6.1-1 Table 6.1-5 Table 6.1-7 Table 6.1-1 Table 6.1-1 Table 6.1-1 Table 6.1-5 Table 6.1-5 Table 6.1-5 Table 6.1-5 Table 6.1-5 Table 6.1-5 Table 6.1-5 Table 6.1-7 Table 6.1-5 Table 6.1-5 Table 6.1-1
Presence of Module ALWAYS If received from MWL ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS When shutter is applied ALWAYS ALWAYS ALWAYS When the XRDI Module is installed When the XRDI Module is installed ALWAYS ALWAYS ALWAYS ALWAYS
Equipment Image
Page 87 of 92 14 June, 2007
6.1.1.4.2
MG Modules
Table 6.1-7: MG Module of Created SOP Instances

Modality Request Attributes Sequence
Positioner Type Distance Source to detector Distance Source to patient Positioner Primary Angle Positioner Secondary Angle Image Laterality Organ Exposed Implant Present View Code Sequence View Modifier Code Sequence
Series Mammography Series (0008, 0060) CS MG Sequence that contains attributes from the (0040, 0275) DS Imaging Service Request Image Mammography Image Mammographic (0018, 1508) CS None (0018, 1110) DS (0018, 1111) DS (0018, 1510) DS (0018, 1511) DS R = right L = left (0020, 0062) CS B = both (e.g. cleavage) (0040, 0318) CS BREAST YES (0028, 1300) DS NO (0054, 0220) CS (0054, 0222) SQ
ALWAYS ANAP
Config MWL
Always ANAP ANAP ANAP ANAP ALWAYS ALWAYS ANAP Always ANAP
Auto Auto Auto User/XRDI14 User/XRDI26 Auto Auto Config Config / User Config / User
6.1.1.5 6.1.1.5.1
GSPS GSPS IOD
Table 6.1-8: IOD of Created DX Image SOP Instances

IE Patient Study Series Equipment Image Module Patient Identification Extended Patient General Study Patient Study General Series Presentation Series General Equipment Presentation State Display Shutter Displayed Area Graphic Annotation Graphic Layer
14
Reference Table 6.1-1 Table 6.1-1 Table 6.1-1 Table 6.1-1 Table 6.1-1 Table 6.1-9 Table 6.1-1 Table 6.1-9 Table 6.1-9 Table 6.1-9 Table 6.1-9 Table 6.1-9
Presence of Module ALWAYS If received from MWL ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS When shutter is applied ALWAYS When graphic annotations are present When graphic annotations are present
Value is supplied by user of XRDI component in case of XRDI configuration
Page 88 of 92 14 June, 2007
IE
Module Modality LUT Softcopy VOI LUT Softcopy Presentation LUT Spatial Transformation SOP Common
Reference Table 6.1-9 Table 6.1-9 Table 6.1-9 Table 6.1-9 Table 6.1-1
Presence of Module ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS
6.1.1.5.2
GSPS Modules
Table 6.1-9: GSPS Modules of Created SOP Instances

Modality
Instance Number Content Label Content Description Presentation Creation Date Presentation Creation Time Content Creators Name Referenced Series Sequence >Series Instance UID >Referenced Image Sequence >>Referenced SOP Class UID >>Referenced SOP Instance UID >> Referenced Frame Number Shutter Presentation Value Mask Subtraction Sequence >Mask Operation > Contrast Frame Averaging Recommended Viewing Mode Shutter Shape Shutter Left Vertical Edge Shutter Right Vertical Edge Shutter Upper Horizontal Edge Shutter Lower Horizontal Edge Vertices of the Polygonal Shutter Shutter Presentation Value Displayed Area Selection Sequence >Referenced Image Sequence
Series Presentation Series (0008, 0060) CS PR Image Presentation State (0020, 0013) IS (0070, 0080) CS GSPS (0070, 0081) LO (0070, 0082) DA (0070, 0083) TM (0070, 0084) PN (0008, 1115) SQ (0020, 000E) UI (0008,1140) SQ (0008,1150) UI (0008,1155) UI (0008, 1160) IS (0018, 1622) US (0028, 6100) SQ (0028, 6101) CS (0028, 6112) US (0028, 1090) CS Display Shutter (0018, 1600) CS (0018, 1602) IS (0018, 1604) IS (0018, 1606) IS (0018, 1608) (0018, 1620) IS IS
ALWAYS
Fixed
ALWAYS ALWAYS Empty ALWAYS ALWAYS VNAP ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ANAP ANAP ANAP ANAP ANAP ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ANAP ANAP
Auto Auto Empty Auto Auto Auto Auto Auto Auto Auto Auto Auto Auto Auto Auto Auto Auto User User User User User User User
(0018, 1622) US Displayed Area (0070, 005A) (0008, 1140) SQ SQ
ALWAYS ANAP
Auto Auto
Page 89 of 92 14 June, 2007
Attribute Name >>Referenced SOP Class UID >>Referenced SOP Instance UID >Displayed Area Top Left Hand Corner >Displayed Area Bottom Right Hand Corner >Presentation Size Mode >Presentation Pixel Spacing > Presentation Pixel Aspect Ratio > Presentation Pixel Magnification Ratio Image Rotation Image Horizontal Flip Graphic Annotation Sequence >Referenced Image Sequence >>Referenced SOP Class UID >>Referenced SOP Instance UID >>Referenced Frame number >Graphic Layer >Text Object Sequence >>Bounding Box Annotation Units >>Anchor Point Annotation Units >>Unformatted Text Value >>Bounding Box Top Left Hand Corner >>Bounding Box Bottom Right Hand Corner >>Bounding Box Text Horizontal Justification >>Anchor Point >>Anchor Point Visibility >Graphic Object Sequence >>Graphic Annotation Units >>Graphic Dimensions >>Number of Graphic Points >>Graphic Data >>Graphic Type >>Graphic Filled Presentation LUT Shape Graphic Layer Sequence >Graphic Layer >Graphic Layer Order >Graphic Layer Recommended Display Grayscale Value >Graphic Layer Recommended Display RGB Value
Tag (0008, 1150) (0008, 1155) (0070, 0052) (0070, 0053) (0070, 0100) (0070, 0101) (0070, 0102)
VR UI UI SL SL CS DS IS
Value
Presence of Value ANAP ANAP ALWAYS ALWAYS
Source Auto Auto Auto Auto Auto Auto Auto Auto User User User Auto Auto Auto Auto Auto Auto Auto Auto Auto Auto Auto Auto Auto Auto Auto Auto Auto Auto Auto Auto Auto Auto Auto Auto Auto Auto
SCALE TO FIT
ALWAYS ALWAYS ANAP ANAP ANAP ANAP ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ANAP ANAP ANAP ANAP ANAP ANAP ANAP ANAP ANAP ANAP ANAP ANAP ANAP ANAP ANAP ANAP ALWAYS ALWAYS ALWAYS ALWAYS ANAP ANAP
(0070, 0103) FL Spatial Transformation (0070, 0042) US (0070, 0041) CS Graphic Annotation (0070, 0001) SQ (0008, 1140) SQ (0008, 1150) UI (0008, 1155) UI (0008, 1155) IS (0070, 0002) CS (0070, 0008) SQ (0070, 0003) CS PIXEL (0070, 0004) CS PIXEL (0070, 0006) ST (0070, 0010) (0070, 0011) FL FL
(0070, 0012) CS (0070, 0014) FL (0070, 0015) CS (0070, 0009) SQ (0070, 0005) CS (0070, 0020) US (0070, 0021) US (0070, 0022) FL (0070, 0023) CS (0070, 0024) CS Softcopy Presentation LUT (2050, 0020) CS IDENTITY Graphic Layer (0070, 0060) SQ (0070, 0002) CS (0070, 0062) IS (0070, 0066) (0070, 0067) US US
Page 90 of 92 14 June, 2007
Attribute Name >Graphic Layer Description Rescale Intercept Rescale Slope Rescale Type VOI LUT Sequence >LUT Descriptor >LUT Explanation >LUT Data Window Center Window Width
Tag
VR
Value
Presence of Value ANAP ANAP ANAP ANAP ANAP ANAP ANAP ANAP ANAP ANAP
Source Auto Auto Auto Auto Auto Auto Auto Auto Auto Auto
(0070, 0068) LO Modality LUT (0028,1052) DS (0028,1053) DS (0028,1054) LO VOI LUT (0028,3010) SQ (0028,3002) SS (0028,3003) LO (0028,3006) SS (0028,1050) DS (0028,1051) DS
Window Center Explanation
&
Width (0028,1055) LO ANAP Auto
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 Patient Name Patient ID Patients Birth Date Patients Sex Patients Weight Referring Physicians Name ---Study Instance UID Referenced Study Sequence Accession Number ---Requested Procedure ID Requested Procedure Description Image IOD Patient Name Patient ID Patients Birth Date Patients Sex Patients Weight Referring Physicians Name ---Study Instance UID Referenced Study Sequence Accession Number Request Attributes Sequence > Requested Procedure ID Scheduled Sequence Step Attributes MPPS IOD Patient Name Patient ID Patients Birth Date Patients Sex
> Study Instance UID > Referenced Study Sequence > Accession Number ---> Requested Procedure ID > Requested Description Procedure
Page 91 of 92 14 June, 2007
Modality Worklist Scheduled Procedure Step ID Scheduled Description Scheduled Sequence ------------------------Scheduled Performing Physicians Name Requested Sequence ------------Procedure Code Procedure Protocol Step Code
Image IOD > Scheduled Procedure Step ID > Scheduled Description > Scheduled Sequence Performed Sequence Study ID Performed Procedure Step ID Performed Procedure Step Start Date Performed Procedure Step Start Time Performed Description Procedure the Step Procedure Protocol Protocol Step Code Code
MPPS IOD > Scheduled Procedure Step ID > Scheduled Description ---Performed Sequence Study ID Performed Procedure Step ID Performed Procedure Step Start Date Performed Procedure Step Start Time Performed Description Procedure the Step Protocol Code Procedure Step
Comments on Procedure Step ----
Performed
Comments on Procedure Step
Performed
Performed Series Sequence > Performing Physicians Name Procedure Code Sequence Study Component ---SOP Class UID SOP Instance UID Protocol Name
Performing Physicians Name ---Referenced Sequence
> Referenced SOP Class UID > Referenced SOP Instance UID Protocol Name
Page 92 of 92 14 June, 2007
6.3
Grayscale Image Consistency
The display monitor attached to "Workstation" can be calibrated according to the Grayscale Standard Display Function (GSDF).
This document was approved by:

Signatures:
1. Bruno Laffin on 2007/06/14 12:06:45 PM GMT+1 Approval Completion Date: 2007/06/14 1:41:36 PM GMT+1 Document ID/Node ID: 14140190 Source Version: 8 PDF Version: 9
Applied Categories and Attributes:

NX 2.0 DICOM Conformance Statement

Uploaded by

Copyright:

Available Formats

NX 2.0 DICOM Conformance Statement

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 2.0 DICOM Conformance Statement

Uploaded by

Copyright:

Available Formats

HE/001132 Document No.001132, Revision 2.

0 NodeID Livelink : 14140190 Agfa HealthCare

Page 1 of 92 14 June, 2007

Page 2 of 92 14 June, 2007

Service-related contact information worldwide

All service-related contact information is available on this URL

tel: 32.3.444.7338 email: [email protected]

Page 3 of 92 14 June, 2007

Conformance Statement Overview

Page 4 of 92 14 June, 2007

Page 5 of 92 14 June, 2007

2.2.2.3.1 2.2.2.3.1.1 2.2.2.3.1.2 2.2.2.3.1.3

Page 6 of 92 14 June, 2007

2.4.1.4.2 2.4.1.5 2.4.2

Support for Extended Character Sets...................................................71 Security ................................................................................................72

Page 7 of 92 14 June, 2007

INTRODUCTION Revision Record

Purpose and Intended Audience of this Document

Page 8 of 92 14 June, 2007

Acronyms and Abbreviations

Page 9 of 92 14 June, 2007

NETWORKING Implementation Model

Request to send images & GSPS

DICOM Store Application Entity

Remote Application Entity Receives Images & GSPS

Request to Print film sheets

DICOM Print Application Entity

Remote Application Entity Prints Film Sheets

Query RIS RIS Application Entity Query RIS by AccessionNumber

Remote Application Entity Provides Worklist Items

Archive Images MPPS Application Entity Print Images

Remote Application Entity Receives MPPS Create / Update

DICOM Standard Interface

Functional Definitions of AEs Functional Definition of DICOM Store Application Entity

Page 10 of 92 14 June, 2007

Functional Definition of DICOM Print Application Entity

Functional Definition of RIS Application Entity

DICOM Modality Worklist

DICOM Modality Worklist query on Accession Number

Functional Definition of MPPS Application Entity

Page 11 of 92 14 June, 2007

Sequencing of Real World Activities

5. Acquire Images 6. Print Acquired Images

7. Store Acquired Images 8. Commit Acquired Images

Page 12 of 92 14 June, 2007

Association Establishment Policies General

Page 13 of 92 14 June, 2007

Implementation Identifying Information

2.2.1.3 2.2.1.3.1 2.2.1.3.1.1

XX is the build version number.

Page 14 of 92 14 June, 2007

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

Page 15 of 92 14 June, 2007

Table 2.2-7: Association Reject Reasons

The Dicom library refuses the association

The Dicom library refuses the association

The Dicom library refuses the association

Proposed Presentation Contexts

The time-out value is hard-coded in the Dicom library as being 60 seconds.