DICOMConformance Statement Mammo Diagnost DR

DICOM Conformance Statement
MammoDiagnost DR 2.0
Koninklijke Philips Electronics N.V. 2011 All rights are reserved.
Document Number:6969431.00
Issued by:
Philips Medical Systems Nederland BV, a Philips Healthcare company, P.O. Box 10.000 5680 DA Best The Netherlands Email: dicom@philips.com Internet: http://www.healthcare.philips.com/connectivity Document Number: 6969431.00 Date: 17-Jun-2011
DICOM Conformance Statement: MammoDiagnost DR 2.0
Page 3 of 79
1. DICOM Conformance Statement Overview

This document is the DICOM Conformance Statement for the Philips Medical Systems MammoDiagnost DR 2.0. This DICOM Conformance Statement for the Philips Medical Systems MammoDiagnost DR 2.0 is based on the PII 9.1 platform. The figure below shows the position of the MammoDiagnost DR 2.0 in a radiology environment.
Figure 1: Eleva Workspot in a DICOM network MammoDiagnost DR 2.0 is an embedded modality system for DICOM images. It provides, among other things, the following features: Verification of application level communication. Basic Worklist Management (BWLM). Storage of images on a remote DICOM System. Commitment of stored images on a remote DICOM system (Push Model) Study management per Modality Performed Procedure Step (MPPS) Printing of hardcopies on a remote DICOM Printer. Storage of images per DICOM Media only on Compact Disc (CD) A table of supported network DICOM Service (SOP) classes is provided with roles (User (SCU)/ Provider (SCP)).
Koninklijke Philips Electronics N.V.
17-Jun-2011
Page 4 of 79
Table 1: Network Services

SOP Class Name Other 1.2.840.10008.1.1 Print Management 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.23 Transfer 1.2.840.10008.5.1.4.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 Workflow Management 1.2.840.10008.1.20.1 1.2.840.10008.3.1.2.3.3 1.2.840.10008.5.1.4.31 UID User of Service (SCU) Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Provider of Service (SCP) Yes No No No No No No No No No No No No
Verification SOP Class 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 >Presentation LUT SOP Class Computed Radiography Image Storage SOP Class Digital Mammography X-Ray Image Storage - Pres. SOP Digital Mammography X-Ray Image Storage - Proc. SOP Storage Commitment Push Model SOP Class Modality Performed Procedure Step SOP Class Modality Worklist Information Model - FIND SOP Class
The services can be specified as a SCU, SCP or as an Option, which means that it is either configurable or that it can be purchased separately. A table of Supported Media Storage Application Profiles (with roles) is provided. Table 2: Media Services
File-set Creator (FSC) Yes File-set Updater (FSU) Yes File-set Reader (FSR) No
Media Storage Application Profile Compact Disk-Recordable General Purpose CD-R Interchange
17-Jun-2011
Page 5 of 79
2. Table of Contents
1. DICOM CONFORMANCE STATEMENT OVERVIEW ............................................................................... 3 2. TABLE OF CONTENTS ............................................................................................................................. 5 3. INTRODUCTION ........................................................................................................................................ 7 3.1. REVISION HISTORY ............................................................................................................................. 7 3.2. AUDIENCE ............................................................................................................................................ 7 3.3. REMARKS ............................................................................................................................................. 7 3.4. DEFINITIONS, TERMS AND ABBREVIATIONS ................................................................................... 8 3.5. REFERENCES ....................................................................................................................................... 8 4. NETWORKING ........................................................................................................................................... 9 4.1. IMPLEMENTATION MODEL ................................................................................................................. 9 4.1.1. Application Data Flow ............................................................................................................................ 9 4.1.2. Functional Definition of AEs ................................................................................................................ 11 4.1.2.1. Functional Definition of Eleva ..................................................................................................... 11 4.1.3. Sequencing of Real World Activities .................................................................................................... 12 4.2. AE SPECIFICATIONS ......................................................................................................................... 13 4.2.1. Eleva .................................................................................................................................................... 13 4.2.1.1. SOP Classes .............................................................................................................................. 13 4.2.1.2. Association Policies .................................................................................................................... 13 4.2.1.2.1. General ....................................................................................................................................... 13 4.2.1.2.2. Number of Associations.............................................................................................................. 13 4.2.1.2.3. Asynchronous Nature ................................................................................................................. 14 4.2.1.2.4. Implementation Identifying Information....................................................................................... 14 4.2.1.2.5. Communication Failure Handling ............................................................................................... 14 4.2.1.3. Association Initiation Policy ........................................................................................................ 14 4.2.1.3.1. (Real-World) Activity Verification as SCU................................................................................ 16 4.2.1.3.2. (Real-World) Activity Modality worklist as SCU ....................................................................... 17 4.2.1.3.3. (Real-World) Activity Modality Performed Procedure Step as SCU ........................................ 25 4.2.1.3.4. (Real-World) Activity Image Export ......................................................................................... 32 4.2.1.3.5. (Real-World) Activity Storage Commitment Push Model as SCU ........................................... 34 4.2.1.3.6. (Real-World) Activity Print Management as SCU .................................................................... 37 4.2.1.4. Association Acceptance Policy ................................................................................................... 43 4.2.1.4.1. (Real-World) Activity Verification as SCP ................................................................................ 44 4.3. NETWORK INTERFACES ................................................................................................................... 46 4.3.1. Physical Network Interfaces ................................................................................................................. 46 4.3.2. Additional Protocols ............................................................................................................................. 46 4.4. CONFIGURATION ............................................................................................................................... 46 4.4.1. AE Title/Presentation Address Mapping .............................................................................................. 46 4.4.1.1. Local AE Titles ............................................................................................................................ 46 4.4.1.2. Remote AE Title/Presentation Address Mapping ....................................................................... 46 4.4.2. Parameters .......................................................................................................................................... 46 5. MEDIA INTERCHANGE ........................................................................................................................... 48 5.1. IMPLEMENTATION MODEL ............................................................................................................... 48 5.1.1. Application Data Flow Diagram ............................................................................................................ 48 5.1.2. Functional Definitions of AE's .............................................................................................................. 48 5.1.3. Sequencing of Real World Activities .................................................................................................... 48 5.2. AE SPECIFICATIONS ......................................................................................................................... 48 5.2.1. Eleva Media - Specification .................................................................................................................. 49 5.2.1.1. File Meta Information for the Eleva ............................................................................................. 49 5.2.1.2. Real-World Activities .................................................................................................................. 49 5.2.1.2.1. RWA - Create File-set ................................................................................................................ 49 5.2.1.2.2. RWA - Update File-set ............................................................................................................... 49 5.2.1.2.3. RWA - Display Directory ............................................................................................................. 50
17-Jun-2011
Page 6 of 79
5.3. AUGMENTED AND PRIVATE APPLICATION PROFILES ................................................................. 50 5.4. MEDIA CONFIGURATION................................................................................................................... 50 6. SUPPORT OF CHARACTER SETS ......................................................................................................... 52 7. SECURITY ................................................................................................................................................ 53 7.1. SECURITY PROFILES ........................................................................................................................ 53 7.1.1. Security use Profiles ............................................................................................................................ 53 7.1.2. Security Transport Connection Profiles ................................................................................................ 53 7.1.3. Digital Signature Profiles ...................................................................................................................... 53 7.1.4. Media Storage Security Profiles ........................................................................................................... 53 7.1.5. Attribute Confidentiality Profiles ........................................................................................................... 53 7.1.6. Network Address Management Profiles ............................................................................................... 53 7.1.7. Time Synchronization Profiles .............................................................................................................. 53 7.1.8. Application Configuration Management Profiles .................................................................................. 53 7.1.9. Audit Trail Profiles ................................................................................................................................ 54 7.2. ASSOCIATION LEVEL SECURITY ..................................................................................................... 54 7.3. APPLICATION LEVEL SECURITY ..................................................................................................... 54 8. ANNEXES OF APPLICATION "ELEVA" ................................................................................................. 55 8.1. IOD CONTENTS .................................................................................................................................. 55 8.1.1. Created SOP Instance ......................................................................................................................... 55 8.1.1.1. List of created SOP Classes for Export ...................................................................................... 55 8.1.1.2. Computed Radiography Image Storage SOP Class................................................................... 55 8.1.1.3. Digital Mammography X-Ray Image Storage - Pres. SOP ......................................................... 60 8.1.1.4. Digital Mammography X-Ray Image Storage - Proc. SOP ......................................................... 67 8.1.2. Usage of Attributes from Received IOD ............................................................................................... 74 8.1.3. Attribute Mapping ................................................................................................................................. 74 8.1.4. Coerced/Modified fields........................................................................................................................ 75 8.2. DATA DICTIONARY OF PRIVATE ATTRIBUTES .............................................................................. 76 8.3. CODED TERMINOLOGY AND TEMPLATES ..................................................................................... 76 8.3.1. Context Groups .................................................................................................................................... 76 8.3.2. Template Specifications ....................................................................................................................... 76 8.3.3. Private code definitions ........................................................................................................................ 76 8.4. GRAYSCALE IMAGE CONSISTENCY ............................................................................................... 76 8.5. STANDARD EXTENDED/SPECIALIZED/PRIVATE SOPS ................................................................. 76 8.5.1. Standard Extended/Specialized/Private SOP Instance ........................................................................ 76 8.5.1.1. Computed Radiography Image Storage SOP Class................................................................... 76 8.5.1.2. Digital Mammography X-Ray Image Storage - Pres. SOP ......................................................... 77 8.5.1.3. Digital Mammography X-Ray Image Storage - Proc. SOP ......................................................... 78 8.6. PRIVATE TRANSFER SYNTAXES ..................................................................................................... 79
17-Jun-2011
Page 7 of 79
3. Introduction
The introduction specifies product and relevant disclaimers as well as any general information that the vendor feels is appropriate.
3.1. Revision History

The revision history provides dates and differences of the different releases. Table 3: Revision History
Document Version 00 Date of Issue 17-Jun-2011 Status Final Updated after review. Description
3.2. Audience
This Conformance Statement is intended for: (Potential) customers System integrators of medical equipment Marketing staff interested in system functionality Software designers implementing DICOM interfaces It is assumed that the reader is familiar with the DICOM standard.
3.3. Remarks
The DICOM Conformance Statement is contained in chapter 4 through 8 and follows the contents and structuring requirements of DICOM PS 3.2. This DICOM Conformance Statement by itself does not guarantee successful interoperability of Philips equipment with non-Philips equipment. The user (or user's agent) should be aware of the following issues: Interoperability Interoperability refers to the ability of application functions, distributed over two or more systems, to work successfully together. The integration of medical devices into an IT environment may require application functions that are not specified within the scope of DICOM. Consequently, using only the information provided by this Conformance Statement does not guarantee interoperability of Philips equipment with non-Philips equipment. It is the user's responsibility to analyze thoroughly the application requirements and to specify a solution that integrates Philips equipment with non-Philips equipment. Validation Philips equipment has been carefully tested to assure that the actual implementation of the DICOM interface corresponds with this Conformance Statement. Where Philips equipment is linked to non-Philips equipment, the first step is to compare the relevant Conformance Statements. If the Conformance Statements indicate that successful information exchange should be possible, additional validation tests will be necessary to ensure the functionality, performance, accuracy and stability of image and image related data. It is the respons ibility of the user (or user's agent) to specify the appropriate test suite and to carry out the additional validation tests. New versions of the DICOM Standard The DICOM Standard will evolve in future to meet the user's growing requirements and to incorporate new features and technologies. Philips is actively involved in this evolution and plans to adapt its equipment to future versions of the DICOM Standard. In order to do so, Philips reserves the right to make changes to its products or to discontinue its delivery. The user should ensure that any non-Philips provider linking to Philips equipment also adapts to future versions of the DICOM Standard. If not, the incorporation of DICOM enhancements into Philips equipment may lead to loss of connectivity (in case of networking) and incompatibility (in case of media).
17-Jun-2011
Page 8 of 79
3.4. Definitions, Terms and Abbreviations

Table 4: Definitions, Terms and Abbreviations
Abbreviation/Term AE AP CD CD-R CR DICOM DX EBE ELE FSC FSR FSU GUI ILE IOD MG MPPS NEMA NM OT PDU PX RF RIS RWA SC SCM SCP SCU SOP TCP/IP UID US WLM XA Application Entity Application Profile Compact Disc CD-Recordable Computed Radiography Digital Imaging and Communications in Medicine Digital X-Ray DICOM Explicit VR Big Endian DICOM Explicit VR Little Endian File-set Creator File-set Reader File-set Updater Graphic User Interface DICOM Implicit VR Little Endian Information Object Definition Digital Mammography X-Ray Modality Performed Procedure Step National Electrical Manufacturers Association Nuclear Medicine Other Protocol Data Unit Panoramic X-Ray X-Ray Radiofluoroscopic Radiology Information System Real-World Activity Secondary Capture Study Component Management Service Class Provider Service Class User Service Object Pair Transmission Control Protocol/Internet Protocol Unique Identifier Ultrasound Worklist Management X-Ray Angiographic Explanation
3.5. References
[DICOM] Digital Imaging and Communications in Medicine, Parts 1 - 18 (NEMA PS 3.1- PS 3.18), National Electrical Manufacturers Association (NEMA) Publication Sales 1300 N. 17th Street, Suite 1752 Rosslyn, Virginia. 22209, United States of America Internet: http://medical.nema.org/ Note that at any point in time the official standard consists of the most recent yearly edition of the base standard (currently 2009) plus all the supplements and correction items that have been approved as Final Text.
17-Jun-2011
Page 9 of 79
4. Networking
This section contains the networking related services (vs. the media related ones).
4.1. Implementation model

The implementation model consists of three sections: The application data flow diagram, specifying the relationship between the Application Entities and the "external world" or RealWorld Activities, A functional description of each Application Entity, and The sequencing constraints among them.
4.1.1.
Application Data Flow
The Mammo Diagnost DR 2.0 system consists of one single application entity only the Mammo Diagnost DR 2.0 Entity (Eleva AE). The figure below shows the networking application data flow as a functional overview of the Eleva AE. It incorporates the following functionality: The Eleva AE can verify application level communication by using the Verification service as SCP. The Eleva AE can request a worklist by using the Basic Worklist Management service as SCU. The Eleva AE can store images by using the Storage service as SCU and use the Storage-Commitment SOP Class perform storagecommit as SCU. The Eleva AE can compose the Modality Performed Procedure Step by using the Study Management service as SCU. The Eleva AE can print images by using the Print Management service as SCU Eleva AE.
17-Jun-2011
Page 10 of 79
Figure 2: Application Data Flow Diagram
17-Jun-2011
Page 11 of 79
4.1.2.
Functional Definition of AEs
This section contains a functional definition for each individual local Application Entity. 4.1.2.1. Functional Definition of Eleva
The Eleva AE is the one and only entity within the Mammo Diagnost DR 2.0. It includes the following service classes. Verification Service Class: The Eleva AE provides the Verification service as SCP and SCU. A remote SCU shall request an association with the Eleva AE for Verification SOP class. After accepting the association the Eleva AE shall receive and respond to the Verification request and release the association when requested. After initiating the Verify, the Eleva AE shall request an association with the selected remote SCP for the Verification SOP class. After accepting the association the Eleva AE shall send the verify request, wait for response, and then release the association. The user interface shall inform on the status of the verification. Basic Worklist Management Service Class: The Eleva AE may use the Basic Worklist Management service as SCU. After initiating the worklist query the Eleva AE shall request an association with the configured remote Basic Worklist Management SCP. After accepting the association the Eleva AE shall send the find request, wait for response, and the release the association. The user interface shall be updated with the query results. Storage Service Class: The Eleva AE may use the Storage service as SCU. During or after a performed procedure step the Eleva AE shall store the related images at the configured Storage SCP. It shall request an association with the remote Storage SCP for the applicable Storage SOP classes. After accepting the association the Eleva AE shall send the store request, wait for response, and then release the association. After successful storage the user interface shall be updated accordingly and in case of failure, the error is notified and logged with the option to redo the job. Storage Commitment Service Class: The Eleva AE may use the Storage Commitment service as SCU. If storage commitment is configured, then, after Store images, the Eleva AE shall automatically request commitment of images at the configured Storage Commitment SCP. It shall request an association with the remote Storage Commitment SCP for the Storage Commitment SOP class. After accepting the association the Eleva AE shall send the action request, wait for response, and then release the association. Depending on the configuration the storage commitment report may be received either synchronous or asynchronous. In case of a storage commitment failure, the error is notified and logged. Basic Grayscale Print Management Meta Class: The Eleva AE may use the Basic Grayscale Print Management service as SCU. During or after a performed procedure step, the Eleva AE shall request printing of the images by the configured Print SCP. It shall request an association with the remote Print SCP for the Basic Grayscale Print Management SOP class. After accepting the association the Eleva AE shall send the requests, wait for responses, and then release the association. Depending on the status and the configuration the Eleva AE may retry to print. Modality Performed Procedure Step Service Class: The Eleva AE may use the Modality Performed Procedure Step service as SCU. After performing a procedure step the Eleva AE shall request an association with the configured remote Study Management SCP. After accepting the association the Eleva AE shall send a create request, wait for response, and then release the association. Next the Eleva AE shall request a new association to send a set request, and after response, release the association.
17-Jun-2011
Page 12 of 79
Depending on the status of creates and set and the configuration the Eleva AE may perform a retry. The user interface shall be updated with the performed procedure step status.
4.1.3.
Sequencing of Real World Activities
The figure blow shows a typical sequence of an examination using a worklist. The user updates the worklist (query Worklist) and then selects and opens an examination. When the user starts the examination (acquiring the first image), the RIS is notified (Create Performed Procedure Step). After the user performs an acquisition (image 1-N) per default the image is sent to archive (Store Image) and printer (Print Image) simultaneously. Finally, when closing the examination, the RIS is notified to update the data of the examination (Set Performed Procedure Step). Note that Print Image will send images to the printer only when enough images were received to fulfill the configured printer format or when the print job is flushed manually. When the last image of an examination is received the print job will be flushed automatically.
Figure 3: Sequence of an examination
17-Jun-2011
Page 13 of 79
4.2. AE Specifications
This section in the DICOM Conformance Statement is a set of Application Entity specifications. There are as many of these subsections as there are different AE's in the implementation.
4.2.1.
Eleva
Detail of this specific Application Entity is specified in this section. 4.2.1.1. SOP Classes
This Application Entity provides Standard Conformance to the following SOP Classes. Table 5: SOP Classes for Eleva
SOP Class Name Verification SOP Class Storage Commitment Push Model SOP Class Modality Performed Procedure Step SOP Class Computed Radiography Image Storage SOP Class Digital Mammography X-Ray Image Storage - Pres. SOP Digital Mammography X-Ray Image Storage - Proc. SOP Modality Worklist Information Model - FIND SOP Class 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 >Presentation LUT SOP Class SOP Class UID 1.2.840.10008.1.1 1.2.840.10008.1.20.1 1.2.840.10008.3.1.2.3.3 1.2.840.10008.5.1.4.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.31 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.23 SCU Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes SCP Yes No No No No No No No No No No No No
Note: Any SOP specific behavior is documented later in the conformance statement in the applicable SOP specific conformance section. 4.2.1.2. Association Policies
Each AE specification contains a description of the general association establishment and acceptance policies of the AE. 4.2.1.2.1. General
The DICOM standard application context is specified below. Table 6: DICOM Application Context
Description Application Context Name 1.2.840.10008.3.1.1.1 Value
4.2.1.2.2.
Number of Associations
The number of simultaneous associations that an Application Entity may support as a Initiator or Acceptor is specified here. Table 7: Number of associations as an Association Initiator for this AE
Description Maximum number of simultaneous associations 2 Value
17-Jun-2011
Page 14 of 79
Table 8: Number of associations as an Association Acceptor for this AE

Description Maximum number of simultaneous associations 1 Value
4.2.1.2.3.
Asynchronous Nature
The implementation supports negotiation of multiple outstanding transactions, along with the maximum number of outstanding transactions supported. Table 9: Asynchronous nature as an Association Initiator for this AE
Description Maximum number of outstanding asynchronous transactions 0 Value
4.2.1.2.4.
Implementation Identifying Information
The value supplied for Implementation Class UID and version name are documented here. Table 10: DICOM Implementation Class and Version for Eleva
Implementation Class UID Implementation Version Name 1.3.46.670589.30.32.0 PMS_ELEVA_32.0
4.2.1.2.5.
Communication Failure Handling
The behavior of the AE during communication failure is summarized in the next table. Table 11: Communication Failure Behavior
Exception Timeout Association aborted Behavior The Association is aborted using A-ABORT and the command is marked as failed. The reason is logged and reported to the user. The command is marked as failed. The reason is logged an reported to the user.
4.2.1.3.
Association Initiation Policy
The Application Entity will respond to a received Association rejection as shown in the next table. Table 12: Association Rejection response
Result 1 - rejectedpermanent Source 1 - DICOM UL service-user Reason/Diagnosis 1 - no-reason-given Behavior Association is not established. The following error is logged. Association rejected by peer ( 1: REJECT_RESULT_permanent, 1: REJECT_SOURCE_dul_user, 1: REJECT-REASON_no_reason_given) Association is not established. The following error is logged. Association rejected by peer ( 1: REJECT_RESULT_permanent, 1: REJECT_SOURCE_dul_user, 2: REJECTREASON_application_context_not_support) Association is not established. The following error is logged. Association rejected by peer ( 1: REJECT_RESULT_permanent, 1: REJECT_SOURCE_dul_user, 3: REJECTREASON_calling_aetitle_not_recognized)
2 - application-contextname-not supported
3 - calling-AE-title-notrecognized
17-Jun-2011
Page 15 of 79
Result
Source
Reason/Diagnosis 7 - called-AE-title-notrecognized
Behavior Association is not established. The following error is logged. Association rejected by peer ( 1: REJECT_RESULT_permanent, 1: REJECT_SOURCE_dul_user, 7: REJECTREASON_called_aetitle_not_recognized) Association is not established. The following error is logged. Error: UserRecoverable: impl.dicom.access.PEER: Association rejected by peer ( 1: REJECT_RESULT_permanent, 2: REJECT_SOURCE_dul_provider (acse), 1: REJECT-REASON_no_reason_given) Association is not established. The following error is logged. Association rejected by peer ( 1: REJECT_RESULT_permanent, 2: REJECT_SOURCE_dul_provider (acse), 2: REJECTREASON_application_context_not support) Association is not established. The following error is logged. Association rejected by peer ( 1: REJECT_RESULT_permanent, 3: REJECT_SOURCE_dul_provider (presentation), 1: REJECTREASON_no_reason_given) Association is not established. The following error is logged. Association rejected by peer ( 1: REJECT_RESULT_permanent, 3: REJECT_SOURCE_dul_provider (presentation), 2: REJECTREASON_application_context_not_support) Association is not established. The following error is logged. Association rejected by peer ( 2: REJECT_RESULT_transient, 1: REJECT_SOURCE_dul_user, 1: REJECT-REASON_no_reason_given) Association is not established. The following error is logged. Association rejected by peer ( 2: REJECT_RESULT_transient, 1: REJECT_SOURCE_dul_user, 2: REJECTREASON_application_context_not-support) Association is not established. The following error is logged. Association rejected by peer ( 2: REJECT_RESULT_transient, 1: REJECT_SOURCE_dul_user, 3: REJECTREASON_calling_aetitle_not_recognized) Association is not established. The following error is logged. Association rejected by peer ( 2: REJECT_RESULT_transient, 1: REJECT_SOURCE_dul_user, 7: REJECTREASON_called_aetitle_not_recognized) Association is not established. The following error is logged. Association rejected by peer ( 2: REJECT_RESULT_transient, 2: REJECT_SOURCE_dul_provider (acse), 1: REJECTREASON_no_reason_given) Association is not established. The following error is logged. Association rejected by peer ( 2: REJECT_RESULT_transient, 2: REJECT_SOURCE_dul_provider (acse), 2: REJECTREASON_application_context_not_support) Association is not established. The following error is logged. Association rejected by peer ( 2: REJECT_RESULT_transient, 3: REJECT_SOURCE_dul_provider (presentation), 1: REJECTREASON_no_reason_given) Association is not established. The following error is logged. Association rejected by peer ( 2: REJECT_RESULT_transient, 3: REJECT_SOURCE_dul_provider (presentation), 2: REJECTREASON_application context not support)
2 - DICOM UL serviceprovider (ACSE related function)
1 - no-reason-given
2 - protocol-versionnot-supported
3 - DICOM UL serviceprovider(Presentation related function)
1 - temporarycongestion
2 - local-limitexceeded
2 - rejectedtransient
1 - DICOM UL service-user
1 - no-reason-given
2 - application-contextname-not-supported
3 - calling-AE-title-notrecognized
7 - called-AE-title-notrecognized
2 - DICOM UL serviceprovider (ACSE related function)
1 - no-reason-given
2 - protocol-versionnot-supported
3 - DICOM UL serviceprovider (Presentation related function)
1 - temporarycongestion
2 - local-limitexceeded
The behavior of the AE on receiving an Association abort is summarized in the next table.
17-Jun-2011
Page 16 of 79
Table 13: Association Abort Handling

Source 0 - DICOM UL service-user (initiated abort) 2 - DICOM UL service-provider (initiated abort) Reason/Diagnosis 0 - reason-notspecified 0 - reason-notspecified 1 - unrecognized-PDU Behavior When received, the Eleva Workspot terminates the connection with the following log: Association ABORTED by peer ( 0: ABORTED_SOURCE_dul_user, 0: ABORT_REASON_not_specified). When received, the Eleva Workspot terminates the connection with the following log: Association ABORTED by peer ( 2: ABORTED_SOURCE_dul_provider, 0: ABORT_REASON_not_specified). When received, the Eleva Workspot terminates the connection with the following log: Association ABORTED by peer ( 2: ABORTED_SOURCE_dul_provider, 1: ABORT_REASON_unrecognized_pdu). When received, the Eleva Workspot terminates the connection with the following log: Association ABORTED by peer ( 2: ABORTED_SOURCE_dul_provider, 2: ABORT_REASON_unexpected_pdu). When received, the Eleva Workspot terminates the connection with the following log: Association ABORTED by peer ( 2: ABORTED_SOURCE_dul_provider, 4: ABORT_REASON_unrecognized_pdu_parameter). When received, the Eleva Workspot terminates the connection with the following log: Association ABORTED by peer ( 2: ABORTED_SOURCE_dul_provider, 5: ABORT_REASON_unexpected_pdu_parameter). When received, the Eleva Workspot terminates the connection with the following log: Association ABORTED by peer ( 2: ABORTED_SOURCE_dul_provider, 6: ABORT_REASON_invalid_pdu_parameter).
2 - unexpected-PDU
4 - unrecognized-PDUparameter 5 - unexpected-PDUparameter 6 - invalid-PDUparameter-value
The behavior of the AE on receiving an association abort is summarized in next table. Table 14: DICOM Command Communication Failure Behavior
Exception Timeout Association aborted Behavior The Association is aborted using A-ABORT and command marked as failed. The reason is logged and reported to the user. The command is marked as failed. The reason is logged and reported to the user.
4.2.1.3.1. 4.2.1.3.1.1.
(Real-World) Activity Verification as SCU Description and Sequencing of Activities
On the system, the dialogue is placed in System->Settings->Quality assurance->DICOM verification. The verification can be performed for each configured AET and is part 3 in an incremental 3-step-test: ping (IP level) DICOM Association establishment DICOM Verification The result on each level is displayed (OK / Failed). 4.2.1.3.1.2. Proposed Presentation Contexts
The presentation contexts are defined in the next table.
17-Jun-2011
Page 17 of 79
Table 15: Proposed Presentation Contexts for (Real-World) Activity Verification as SCU
Presentation Context Table Abstract Syntax Name Verification SOP Class UID 1.2.840.10008.1.1 Transfer Syntax Role Name List Explicit VR Big Endian Explicit VR Little Endian Implicit VR Little Endian UID List 1.2.840.10008.1.2.2 1.2.840.10008.1.2.1 1.2.840.10008.1.2 SCU Extended Negotiation None
4.2.1.3.1.3.
SOP Specific Conformance for Verification SOP Class
This section and sub-section include the manufacturer SOP and Dataset specific information as well the status codes and their corresponding behavior. 4.2.1.3.1.3.1. Dataset Specific Conformance for Verification C-ECHO SCU
Detail regarding the Dataset Specific response behavior will be reported in this section.
4.2.1.3.2. 4.2.1.3.2.1.
(Real-World) Activity Modality worklist as SCU Description and Sequencing of Activities
Figure 4: (Real World) Activity - Modality Worklist as SCU For each Broad or specific Worklist request, an association towards the Basic Worklist Management SCP is established and a CFIND request is transmitted. The Broad query can be configured with a combination of the Matching Keys: Scheduled Station AE Title Scheduled Procedure Step Start Date Modality Each of the matching keys is optional. The association will be closed on reception of the last C-FIND response. The Worklist Query result is displayed in the Patient List. The query is interruptible if it was triggered by the user.
17-Jun-2011
Page 18 of 79
After clicking the Query Worklist button the Eleva AE shall request an association with the configured remote Basic Worklist Management SCP. When the association is accepted the Eleva AE shall send the Broad Query find request, wait for response and then release the association. This RWA may be initiated in two ways. After clicking the Query Worklist button the Eleva AE shall request and association with the configured remote Basic W orklist Management SCP. When the association is accepted the Eleva AE shall send the Broad Query find request, wait for response and the release the association. After clicking the Patient Query button - entering and confirming the matching key values - the Eleva AE shall request an association with the configured remote Basic Worklist Management SCP. When the association is accepted the Eleva AE shall send the patient query find request, wait for response, and then release the association. Optionally the Broad Query may also be performed automatically in the system background. The time interval between subsequent background queries is configurable. Manual and automatic background queries are serialized and do not interfere with another. 4.2.1.3.2.2. Proposed Presentation Contexts
The presentation contexts are defined in the next table. Table 16: Proposed Presentation Contexts for (Real-World) Activity Modality worklist As SCU
Presentation Context Table Abstract Syntax Name Modality Worklist Information Model - FIND SOP Class UID 1.2.840.10008.5.1.4.31 Transfer Syntax Role Name List Explicit VR Big Endian Explicit VR Little Endian Implicit VR Little Endian UID List 1.2.840.10008.1.2.2 1.2.840.10008.1.2.1 1.2.840.10008.1.2 SCU Extended Negotiation None
4.2.1.3.2.3.
SOP Specific Conformance for Modality Worklist Information Model - FIND SOP Class
This section includes the SOP specific behavior, i.e. error codes, error and exception handling, time-outs, etc. Behavior of an Application Entity SOP class is summarized as shown in next Table. The standard as well as the manufacturer specific status codes and their corresponding behavior are specified. 4.2.1.3.2.3.1. Dataset Specific Conformance for Patient Query
Detail regarding the Dataset Specific response behavior will be reported in this section. The table below should be read as follows: Attribute Name: Attributes supported to build a Modality Worklist Request Identifier. Tag: DICOM tag for this attribute. VR: DICOM VR for this attribute. M: Matching Keys for (automatic) Worklist Update. R: Return Keys. An X will indicate that this attribute as Return Key with zero length for Universal Matching. Q: Interactive Query Key. An X will indicate that this attribute as matching key can be used. D: Displayed Keys. An X indicates that this Worklist attribute is displayed to the user during a patient registration dialog.
17-Jun-2011
Page 19 of 79
An X indicates that this Worklist attribute is included into all object Instances created during performance of the related Procedure Step. Type of matching: The following types of matching exists: Single Value Matching List of UID Matching Wild Card Matching Range Matching Sequence Matching Universal Matching IOD: Table 17: Worklist Request Identifier
Attribute Name Tag VR M R Q D IOD Type of Matching Comment
Other Patient IDs Patient ID Patient's Name
0010,1000 0010,0020 0010,0010
LO LO PN X X
Patient Identification Module X X X X X X X Single Value,Universal Single Value,Universal, WildCard
Issuer of Patient ID Confidentiality Constraint on Patient Data Description Ethnic Group Occupation Patient Comments Patient's Age Patient's Birth Date Patient's Sex Patient's Size Patient's Weight Additional Patient History Allergies Medical Alerts Pregnancy Status Special Needs Current Patient Location Specific Character Set Scheduled Procedure Step Sequence >Comments on the Scheduled Procedure Step >Modality >Pre-Medication >Requested Contrast Agent
0010,0021 0040,3001 0010,2160 0010,2180 0010,4000 0010,1010 0010,0030 0010,0040 0010,1020 0010,1030 0010,21B0 0010,2110 0010,2000 0010,21C0 0038,0050 0038,0300 0008,0005 0040,0100 0040,0400 0008,0060 0040,0012 0032,1070
LO LO SH SH LT AS DA CS DS DS LT LO LO US LO LO CS SQ LT CS LO LO X
X Patient Demographic Module X X X X X X X X X X X X X X Visit Status Module X X SOP Common Module X If configured X X X X X X X Patient Medical Module X X X X
Scheduled Procedure Step Module X X X X X Single Value,Universal X Single Value,Universal SOP Classes: CR, DX, OT, US, MG, RF, XA, NM
17-Jun-2011
Page 20 of 79
Attribute Name >Scheduled Performing Physician's Name >Scheduled Procedure Step Description >Scheduled Procedure Step End Date >Scheduled Procedure Step End Time >Scheduled Procedure Step ID >Scheduled Procedure Step Location >Scheduled Procedure Step Start Date >Scheduled Procedure Step Start Time >Scheduled Procedure Step Status >Scheduled Station AE Title >Scheduled Station Name >Scheduled Protocol Code Sequence >>Code Meaning >>Code Value >>Coding Scheme Designator >>Coding Scheme Version Names of Intended Recipients of Results Patient Transport Arrangements Reason for the Requested Procedure Requested Procedure Comments Requested Procedure Description Requested Procedure ID Requested Procedure Priority Study Instance UID Referenced Study Sequence >Referenced SOP Class UID >Referenced SOP Instance UID Requested Procedure Code Sequence >Code Meaning >Code Value >Coding Scheme Designator >Coding Scheme Version Accession Number
Tag 0040,0006 0040,0007 0040,0004 0040,0005 0040,0009 0040,0011 0040,0002 0040,0003 0040,0020 0040,0001 0040,0010 0040,0008 0008,0104 0008,0100 0008,0102 0008,0103 0040,1010 0040,1004 0040,1002 0040,1400 0032,1060 0040,1001 0040,1003 0020,000D 0008,1110 0008,1150 0008,1155 0032,1064 0008,0104 0008,0100 0008,0102 0008,0103 0008,0050
VR PN LO DA TM SH SH DA TM CS AE SH SQ LO SH SH SH PN LO LO LT LO SH SH UI SQ UI UI SQ LO SH SH SH SH
R X X X X X X
IOD
Type of Matching
Comment
X X X
X X
X X X X X X X
Single Value,Universal
Value: All, Today, Today+Tomorrow, Today+Yesterday, Today+Yesterday+Tomorrow
Requested Procedure Module X X X X X X X X X X X X X X X X X Imaging Service Request Module X X X X Single X Single Value,Universal
17-Jun-2011
Page 21 of 79
Attribute Name
Tag
VR
IOD
Type of Matching Value,Universal
Comment
Imaging Service Request Comments Issue Date of Imaging Service Request Reason for the Imaging Service Request (retired) Referring Physician's Name Requesting Physician Requesting Service
0040,2400 0040,2004 0040,2001 0008,0090 0032,1032 0032,1033
LT DA LO PN PN LO
X X X X X X
This part of the section includes the dataset specific behavior, i.e. error codes, error and exception handling, time-outs, etc. Table 18: Status Response
Service Status Success Failure Error Code 0000 A700 A900 Cxxx Cancel Pending FE00 FF00 FF01 Further Meaning Matching is complete Refused - Out of resources Failed - Identifier does not match SOP Class Failed - 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 for existence and/or matching for this identifier Behavior The worklist is updated. The association is released. The reason is logged. The association is released. The reason is logged. The association is released. The reason is logged. The association is released. The reason is logged. The query Worklist job continues. The Query Worklist job continues.
Table 19: DICOM Command Communication Failure Behavior

Exception RIS query timeout (default 240 seconds) Association aborted Behavior The association is aborted using A_ABORT and command marked as failed.The reason is logged and reported to the user. The command is marked as failed. The reason is logged and reported to the user.
Patient and Study Merge: The ELEVA AE looks in its internal database for a Study with the same Study Instance UID (0020,000D) as given in the Scheduled Procedure Step. If a Study Instance UID match was not found, it looks for a Patient with the same Patient ID (0010,0020) as given in the Scheduled Procedure Step. If no Patient match is found, a new Patient is created, using attributes from Scheduled Procedure step. If Patient with a matching Patient ID was found, attributes are updated for the internal Patient, based on the attributes as given in the Scheduled Procedure Step. A new Study with a Study Instance UID as given in the Scheduled Procedure Step is created. If a Study Instance UID match was found, all Patient attributes as given in the Scheduled Procedure Step are updated in the internal database for the parent patient of this study. Study attributes are updated for the internal study based on the attributes as given in the Scheduled Procedure Step. Scheduled Procedure Step (= Examination) Merge: If the ELEVA AE's internal database contains no SPS with Scheduled Procedure Step ID (0040,0009) identifying an incoming
17-Jun-2011
Page 22 of 79
Scheduled Procedure Step, it creates a new one and creates an corresponding Examination referencing this Scheduled Procedure Step ID. If the ELEVA AE's internal database contains already an SPS with the Scheduled Procedure Step ID (0040,0009) identifying an incoming Scheduled Procedure Step, the behavior depends on the corresponding Examination state. If the Examination is still "scheduled", the SPS attributes are compared to the attributes sent with the most recent WLM query. If at least one attribute differs, the scheduled Examination is deleted and re-scheduled. Manual changes the user might have performed on this Examination are lost. If the Examination has already started, no changes are performed, and the potential changes of the incoming Scheduled Procedu re Step are disregarded. 4.2.1.3.2.3.2. Dataset Specific Conformance for Broadcast Query
Detail regarding the Dataset Specific response behavior will be reported in this section. The table below should be read as follows: Attribute Name: Attributes supported to build a Modality Worklist Request Identifier. Tag: DICOM tag for this attribute. VR: DICOM VR for this attribute. M: Matching Keys for (automatic) Worklist Update. R: Return Keys. An "X" will indicate that this attribute as matching key can be used. Q: Interactive Query Key. An "X" will indicate that this attribute as matching key can be used. D: Displayed Keys. An "X" indicates that this Worklist attribute is displayed o the user during a patient registration dialog. IOD: An "X" indicates that this Worklist attribute is included into all object Instances created during performance of the related Procedure Step. Type of matching: The following types of matching exists: Single Value Matching List of UID Matching Wild Card Matching Range Matching Sequence Matching Universal Matching Table 20: Worklist Request Identifier
Attribute Name Tag VR M R Q D IOD Type of Matching Comment
Patient Identification Module Other Patient IDs Patient ID Patient's Name Issuer of Patient ID Confidentiality Constraint on Patient Data Description Ethnic Group Occupation Patient Comments Patient's Age Patient's Birth Date Patient's Sex Patient's Size Patient's Weight 0010,1000 0010,0020 0010,0010 0010,0021 0040,3001 0010,2160 0010,2180 0010,4000 0010,1010 0010,0030 0010,0040 0010,1020 0010,1030 LO LO PN LO Patient Demographic Module LO SH SH LT AS DA CS DS DS X X X X X Last name, First name, Prefix, Middle name, Suffix
17-Jun-2011
Page 23 of 79
Attribute Name
Tag
VR
IOD
Type of Matching
Comment
Patient Medical Module Additional Patient History Allergies Medical Alerts Pregnancy Status Special Needs Current Patient Location Specific Character Set Scheduled Procedure Step Sequence >Comments on the Scheduled Procedure Step >Modality >Pre-Medication >Requested Contrast Agent >Scheduled Performing Physician's Name >Scheduled Procedure Step Description >Scheduled Procedure Step End Date >Scheduled Procedure Step End Time >Scheduled Procedure Step ID >Scheduled Procedure Step Location >Scheduled Procedure Step Start Date >Scheduled Procedure Step Start Time >Scheduled Procedure Step Status >Scheduled Station AE Title >Scheduled Station Name >Scheduled Protocol Code Sequence >>Code Meaning >>Code Value >>Coding Scheme Designator >>Coding Scheme Version Names of Intended Recipients of Results Patient Transport Arrangements Reason for the Requested Procedure 0010,21B0 0010,2110 0010,2000 0010,21C0 0038,0050 0038,0300 0008,0005 0040,0100 0040,0400 0008,0060 0040,0012 0032,1070 0040,0006 0040,0007 0040,0004 0040,0005 0040,0009 0040,0011 0040,0002 0040,0003 0040,0020 0040,0001 0040,0010 0040,0008 0008,0104 0008,0100 0008,0102 0008,0103 0040,1010 0040,1004 0040,1002 LT LO LO US LO Visit Status Module LO CS SQ LT CS LO LO PN LO DA TM SH SH DA TM CS AE SH SQ LO SH SH SH Requested Procedure Module PN LO LO Values: All, Today, Today+Tomorrow, Today+Yesterday, Today+Yesterday+Tomorrow X SOP Classes: CR, DX, OT, US, MG, RF, XA, NM X SOP Common Module X If Configured X X
Scheduled Procedure Step Module
17-Jun-2011
Page 24 of 79
Attribute Name Requested Procedure Comments Requested Procedure Description Requested Procedure ID Requested Procedure Priority Study Instance UID Referenced Study Sequence >Referenced SOP Class UID >Referenced SOP Instance UID Requested Procedure Code Sequence >Code Meaning >Code Value >Coding Scheme Designator >Coding Scheme Version Accession Number Imaging Service Request Comments Issue Date of Imaging Service Request Reason for the Imaging Service Request (retired) Referring Physician's Name Requesting Physician
Tag 0040,1400 0032,1060 0040,1001 0040,1003 0020,000D 0008,1110 0008,1150 0008,1155 0032,1064 0008,0104 0008,0100 0008,0102 0008,0103 0008,0050 0040,2400 0040,2004 0040,2001 0008,0090 0032,1032
VR LT LO SH SH UI SQ UI UI SQ LO SH SH SH SH LT DA LO PN PN
IOD
Type of Matching
Comment
Imaging Service Request Module X
X X
Service Status Success Failure Error Code 0000 A700 A900 Cxxx Cancel Pending FE00 FF00 FF01 Further Meaning Matching is complete Refused - Out of resources Failed - Identifier does not match SOP Class Failed - 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 for existence and/or matching for this identifier Behavior The worklist is updated. The association is released. The reason is logged. The association is released. The reason is logged. The association is released. The reason is logged. The association is released. The reason is logged. The Query Worklist job continues. The Query Worklist job continues.
17-Jun-2011
Page 25 of 79

Exception RIS Query timeout (default 240 seconds) Association aborted Behavior The association is aborted using A-ABORT and command marked as failed. The reason is logged and reported to the user. The command is marked as failed. The reason is logged and reported to the user.
4.2.1.3.2.3.3.
Dataset Specific Conformance for Modality Worklist Information Model - FIND C-CANCEL-SCU
Detail regarding the Dataset Specific response behavior will be reported in this section. This part of the section includes the dataset specific behavior, i.e. error codes, error and exception handling, time-outs, etc. Table 23: DICOM Command Communication Failure Behavior
Exception Timeout Association aborted Behavior The association is aborted using AP-ABORT and command marked as failed. The reason is logged and reported to the user. The command is marked as failed. The reason is logged and reported to the user.
4.2.1.3.3. 4.2.1.3.3.1.
(Real-World) Activity Modality Performed Procedure Step as SCU Description and Sequencing of Activities
Figure 5: (Real World) Activity - Modlaity Performed Procedure Step as SCU
17-Jun-2011
Page 26 of 79
Description of Activities: A MammoDiagnost DR 2.0 "Examination" is regarded equivalent to a DICOM Procedure Step. It is scheduled or manually entered before and acquisition is taken, and performed by taking acquisitions. If scheduled by the RIS, one Examination is the result of one Scheduled Procedure Step. Since an examination may not be re-opened after having been closed, and each examination workflow context is enclosed in one MPPS, one examination may result in 0:1 MPPS instances. However, image archiving after the examination's closure leads to 1:n MPPS instances per examination (append case). After the image for a Scheduled Procedure Step has been acquired, the system sets the MPPS status of the related examination to "IN PROGRESS" and generates an initial MPPS in progress message. The system does not generate intermediate MPPS in progress message for subsequent acquisitions of this Scheduled Procedure Step instance. After finishing the appropriate acquisition(s), the system will change the MPPS status of the related examination to "COMPLETED: and generate and MPPS N-SET-FINAL message. MammoDiagnost DR 2.0 also generates MPPS messages for unscheduled examinations. The MPPS completed message will list the UID's of all related DICOM archived images and the format of (optionally) generated direct prints. After abandoning or discontinuing a procedure step, the operator may set the MPPS Status of the related examination to "DISCONTINUED" and the system generates a MPPS DISCONTINUED message. The reason for abandoning or discontinuing a procedure step is unspecified. The operator may interchange the performed sequence order of scheduled procedure steps. MPPS messages may interleave. Depending on the application workflow optimization by the user, an MPPS sequence like this may come up: MPPS / SOP Instance UID 1: N-CREATE (IN PROGRESS) MPPS / SOP Instance UID 2: N-CREATE (IN PROGRESS) MPPS / SOP Instance UID 3: N-CREATE (IN PROGRESS) ... MPPS / SOP Instance UID 2: N-SET (COMPLETED) MPPS / SOP Instance UID 1: N-SET (COMPLETED) MPPS / SOP Instance UID 3: N-SET (COMPLETED) (i.e.: running multiple procedure steps 'in parallel') Sequencing of Activities: After storing a performed procedure step the Eleva AE shall request an association with the configured remote Study Management SCP. After accepting the association the Eleva AE shall send a N-CREATE request, wait for response, and then release the association. 4.2.1.3.3.2. Proposed Presentation Contexts
The presentation contexts are defined in the next table. Table 24: Proposed Presentation Contexts for (Real-World) Activity Modality Performed Procedure Step As SCU
Presentation Context Table Abstract Syntax Name Modality Performed Procedure Step SOP Class UID 1.2.840.10008.3.1.2.3.3 Transfer Syntax Role Name List Explicit VR Big Endian Explicit VR Little Endian Implicit VR Little Endian UID List 1.2.840.10008.1.2.2 1.2.840.10008.1.2.1 1.2.840.10008.1.2 SCU Extended Negotiation None
17-Jun-2011
Page 27 of 79
4.2.1.3.3.3.
SOP Specific Conformance for Modality Performed Procedure Step SOP Class
When acquiring the first image of a Scheduled or Unscheduled Procedure Step, MammoDiagnost DR 2.0 generates a MPPS IN PROGRESS message. MammoDiagnost DR 2.0 does not generate intermediate IN PROGRESS (N-SET) messages and does not support the Performed Procedure Step Exception Management Option. MammoDiagnost DR 2.0 has no Billing Code Tables and does not support the Performed Procedure Step Billing and Material Management Option, except default values for Medium Type (2000,0030) and Film Size ID (2010,0050), if optional Local Print is configured. Assisted Acquisition Protocol Setting Option: Eleva AE by default derives the specific acquisition protocol form the Scheduled Protocol Code Sequence Items. Any single item results in an examination. Eleva AE supports 3 more (configurable) mapping relations, as shown below: Examination is selected from Scheduled Protocol Code Items -> Code Value (0040,0008) (default). Examination is selected from Scheduled Procedure Step Description (0040,0007). Examination is selected form Request Procedure Code Items -> Code Value (0032,1064). Examination is selected from Requested Procedure Description (0032,1060). Eleva AE does not evaluate the attributes: Code Scheme Designator (0008,0102), Coding Scheme Version (0008,0103), Code Meaning (0008,0104).
Eleva AE only evaluate the attributes Code Value (0008,0100), for mapping the examination settings. I.e. Eleva AE expects that any used Code Value is unique (unambiguous) within a given RIS domain. Restriction Depending on Number of Scheduled Protocol Code Items: It is highly recommended that the Scheduled Procedure Step contains only 1 Item in the Scheduled Protocol Code Sequence. If the Scheduled Procedure Step contains <n> items in the Scheduled Protocol Code Sequence, the Scheduled Procedure Step is split into <n> examinations, where any single examination shows only 1 of the Scheduled Protocol Code Items, but all the other attributes are the same. When such an examination is returned back via MPPS, also the Performed Protocol Code Sequence will show only 1 item. If all <n> Scheduled Procedure Step Code Items are performed, <n> MPPS instances will be sent back to the RIS, and the sum of all Performed Protocol Code Items will be <n>. 4.2.1.3.3.3.1. Dataset Specific Conformance for Modality Performed Procedure Step SOP Class N-CREATE-SCU
This section includes the dataset specific behavior, i.e. error codes, error and exception handling, time-outs, etc. Table 25: MPPS Request Identifiers for N-CREATE-RQ
Attribute Name Tag VR Value SOP Common Module Optional/Config Comment
Specific Character Set Patient ID Patient's Birth Date Patient's Name Patient's Sex Referenced Patient Sequence Scheduled Step Attributes Sequence
0008,0005 0010,0020 0010,0030 0010,0010 0010,0040 0008,1120 0040,0270
CS
Performed Procedure Step Relationship Module LO DA PN CS SQ SQ
17-Jun-2011
Page 28 of 79
Attribute Name >Accession Number >Requested Procedure Description >Requested Procedure ID >Scheduled Procedure Step Description >Scheduled Procedure Step ID >Study Instance UID >Referenced Study Sequence >>Referenced SOP Class UID >>Referenced SOP Instance UID >Scheduled Protocol Code Sequence >>Code Meaning >>Code Value >>Coding Scheme Designator Issuer of Patient ID Performed Location Performed Procedure Step Description Performed Procedure Step End Date Performed Procedure Step End Time Performed Procedure Step ID Performed Procedure Step Start Date Performed Procedure Step Start Time Performed Procedure Step Status Performed Procedure Type Description Performed Station AE Title Performed Station Name Procedure Code Sequence >Code Meaning >Code Value >Coding Scheme Designator >Coding Scheme Version Modality Study ID Performed Protocol Code Sequence >Code Meaning >Code Value >Coding Scheme Designator
Tag 0008,0050 0032,1060 0040,1001 0040,0007 0040,0009 0020,000D 0008,1110 0008,1150 0008,1155 0040,0008 0008,0104 0008,0100 0008,0102 0010,0021 0040,0243 0040,0254 0040,0250 0040,0251 0040,0253 0040,0244 0040,0245 0040,0252
VR SH LO SH LO SH UI SQ UI UI SQ LO SH SH LO
Value
Comment
Performed Procedure Step Information Module SH EMPTY LO DA TM SH DA TM CS COMPLETED, DISCONTINUED, IN PROGRESS Start of the examination Start of the examination Finish of the examination: EMPTY Finish of the examination: EMPTY
0040,0255 0040,0241 0040,0242 0008,1032 0008,0104 0008,0100 0008,0102 0008,0103 0008,0060 0020,0010 0040,0260 0008,0104 0008,0100 0008,0102
LO AE SH SQ LO SH SH SH Image Acquisition Results Module CS SH SQ LO SH SH Eleva EMPTY
17-Jun-2011
Page 29 of 79
Attribute Name >Coding Scheme Version Performed Series Sequence Entrance Dose Image and Fluoroscopy Area Dose Product Total Number of Exposures Total Time of Fluoroscopy Entrance Dose in mGy Exposure Dose Sequence >Overlay Data
Tag 0008,0103 0040,0340 0040,0302 0018,115E 0040,0301 0040,0300 0040,8302 0040,030E 6000,3000
VR SH SQ US DS US US DS SQ O W/ OB LO US US SS CS LO US US LO UI LT CS DS DS CS 0 G 0 1
Value
Comment
length of: 0 Radiation Dose Module Not sent in case of appended MPPS Instances
>Overlay Label >Overlay Bit Position >Overlay Bits Allocated >Overlay Origin >Overlay Type >Overlay Description >Overlay Columns >Overlay Rows >Position Reference Indicator >Frame of Reference UID >Detector Mode >View Position >Detector Secondary Angle >Detector Primary Angle Image Type
6000,1500 6000,0102 6000,0100 6000,0050 6000,0040 6000,0022 6000,0011 6000,0010 0020,1040 0020,0052 0018,7008 0018,5101 0018,1531 0018,1530 0008,0008
G=Graphics
CONTACT, MAG, STEREO
-15, 0, 15 POSTBIOPSY, STEREO_MINUS/STER EO_PLUS, STEREO_SCOUT, ORIGINAL, PRIMARY For Scout Views the value STEREO_SCOUT shall be used. For all paired Stereo and Control Views the values STEREO_MINUS / STEREO_PLUS shall be used. For Control 0 Views the value POSTBIOPSY shall be used.
>Organ Dose >Organ Exposed >View Code Sequence >>View Modifier Code Sequence Film Consumption Sequence
0040,0316 0040,0318 0054,0220 0054,0222
DS CS SQ SQ Billing And Material Management Code Module SQ length of: 0
0040,0321
Service Status Success Error Code 0000 Further Meaning Successful operation Behavior The SCP has successfully received the modality performed procedure step create request. Log entry.
17-Jun-2011
Page 30 of 79
Service Status Failure
Error Code 0213 xxxx
Further Meaning Resource limitation (Any failure accept)
Behavior The command is reported to the user as failed. The reason is logged. After a configured period of time the storage will be retried up to a configured number of times. The command is reported to the user as failed. The reason is logged. No retry.
Table 27: DICOM COmmand Communcation Failure Behavior

4.2.1.3.3.3.2.
Dataset Specific Conformance for Modality Performed Procedure Step SOP Class N-SET-SCU
This section includes the dataset specific behavior, i.e. error codes, error and exception handling, time-outs, etc. Table 28: MPPS Request Identifiers for N-SET-RQ
Attribute Name Tag VR Value Comment
Performed Procedure Step Description Performed Procedure Step End Date Performed Procedure Step End Time Performed Procedure Step Status Procedure Code Sequence >Code Meaning >Code Value >Coding Scheme Designator Performed Protocol Code Sequence >Code Meaning >Code Value >Coding Scheme Designator Performed Series Sequence >Operators' Name >Performing Physician's Name >Protocol Name >Retrieve AE Title >Series Description >Series Instance UID >Referenced Image Sequence >Referenced Non-Image Composite SOP Instance Sequence
0040,0254 0040,0250 0040,0251 0040,0252
Performed Procedure Step Information Module LO DA TM CS COMPLETED, DISCONTINUED, IN PROGRESS Start of the examination Start of the examination
0008,1032 0008,0104 0008,0100 0008,0102 0040,0260 0008,0104 0008,0100 0008,0102 0040,0340 0008,1070 0008,1050 0018,1030 0008,0054 0008,103E 0020,000E 0008,1140 0040,0220
SQ LO SH SH Image Acquisition Results Module SQ LO SH SH SQ PN PN LO AE LO UI SQ SQ length of: 0 Copied from Performed Protocol Code Sequence - Item code Value. N-Values
17-Jun-2011
Page 31 of 79
Attribute Name
Tag
VR
Value Radiation Dose Module
Comment
Entrance Dose Image and Fluoroscopy Area Dose Product Total Number of Exposures Total Time of Fluoroscopy Exposure Dose Sequence Image and Fluoroscopy Area Dose Product Total Time of Fluoroscopy Total Number of Exposures Entrance Dose Comments on Radiation Dose Entrance Dose in mGy Exposure Dose Sequence >Image Type
0040,0302 0018,115E 0040,0301 0040,0300 0040,030E 0018,115E 0040,0300 0040,0301 0040,0302 0040,0310 0040,8302 0040,030E 0008,0008
US DS US US SQ DS US US US ST DS SQ CS POSTBIOPSY, STEREO_MINUS/STER EO_PLUS, STEREO_SCOUT, ORIGINAL, PRIMARY -15, 0, 15 0 STEREO, CONTACT, MAG For Scout Views the value STEREO_SCOUT shall be used. For all paired Stereo and Control Views the values STEREO_MINUS / STEREO_PLUS shall be used. For Control 0 Views the value POSTBIOPSY shall be used. Not accumulating: reprocessed images, non-digital images. Not sent in case of appended MPPS instances. Not accumulating: reprocessed images, non-digital images. Not sent in case of appended MPPS instances. Not accumulating: reprocessed images, non-digital images. Not sent in case of appended MPPS instances. Not accumulating: reprocessed images, non-digital images. Not sent in case of appended MPPS instances.
>Detector Primary Angle >Detector Secondary Angle >View Position >Detector Mode >Frame of Reference UID >Position Reference Indicator >Overlay Rows >Overlay Columns >Overlay Description >Overlay Type >Overlay Origin >Overlay Bits Allocated >Overlay Bit Position >Overlay Label >Overlay Data
0018,1530 0018,1531 0018,5101 0018,7008 0020,0052 0020,1040 6000,0010 6000,0011 6000,0022 6000,0040 6000,0050 6000,0100 6000,0102 6000,1500 6000,3000
DS DS CS LT UI LO US US LO CS SS US US LO O W/ OB DS CS SQ SQ
G 1 0
>Organ Dose >Organ Exposed >View Code Sequence >>View Modifier Code Sequence Film Consumption Sequence >Film Size ID >Medium Type >Number of Films
0040,0316 0040,0318 0054,0220 0054,0222
0040,0321 2010,0050 2000,0030 2100,0170
Billing And Material Management Code Module SQ CS CS IS
17-Jun-2011
Page 32 of 79
Service Status Success Failure Error Code 0000 0110 xxxx Confirmation Processing failure - performed procedure step object may no longer be updated (any other failure) Further Meaning Behavior The association is released. The reason is logged. The reason is logged.

Exception Timeout Association aborted Behavior The Association is aborted using AP-ABORT and command marked as failed. The reason is logged and reported to the user. The command is marked as failed. The reason is logged and reported to the user.
4.2.1.3.4. 4.2.1.3.4.1.
(Real-World) Activity Image Export Description and Sequencing of Activities
Figure 6: (Real World) Activity - Image Export Export means that MammoDiagnost DR 2.0 stores images without Storage Commitment. This RWA may be initiated in two ways. Manually in the viewer, after clicking the Store button the Eleva AE will Store the selected images at the selected Storage SCP. Automatically during an examination, after clicking the Confirm button the Eleva AE will automatically store the related images or the performed procedure step at the configured Storage SCP.
The Eleva AE will request an association with the remote Storage SCP for the applicable Storage SOP classes. After accepting the association the Eleva AE will send the store request, wait for response, and then release the association. The store response status may be inspected on the UI. Depending on the status of the store the Eleva AE may queue store requests for retries. The queued store requests can be cancelled form the UI. 4.2.1.3.4.2. Proposed Presentation Contexts
17-Jun-2011
Page 33 of 79
Table 31: Proposed Presentation Contexts for (Real-World) Activity Image Export
Presentation Context Table Abstract Syntax Name Computed Radiography Image Storage SOP Class UID 1.2.840.10008.5.1.4.1.1.1 Transfer Syntax Role Name List Explicit VR Big Endian Explicit VR Little Endian Implicit VR Little Endian Digital Mammography X-Ray Image Storage - Pres. SOP 1.2.840.10008.5.1.4.1.1.1.2 Explicit VR Big Endian Explicit VR Little Endian Implicit VR Little Endian Digital Mammography X-Ray Image Storage - Proc. SOP 1.2.840.10008.5.1.4.1.1.1.2.1 Explicit VR Big Endian Explicit VR Little Endian Implicit VR Little Endian UID List 1.2.840.10008.1.2.2 1.2.840.10008.1.2.1 1.2.840.10008.1.2 1.2.840.10008.1.2.2 1.2.840.10008.1.2.1 1.2.840.10008.1.2 1.2.840.10008.1.2.2 1.2.840.10008.1.2.1 1.2.840.10008.1.2 SCU None SCU None SCU Extended Negotiation None
Note: Only the MG export provides the full set of mammography data attributes (e.g. the IHE MAMMO set), and CR is merely a fall back option. By default, all images are DICOM Stored according to the SOP Class Digital Mammography X-Ray Image storage - for Presentation attributes that are undefined for MG Images are stored in private attributes. CR Image attributes that are undefined for DX Images are stored in private attributes. The Digital Mammography X-Ray Image IOD is used in two SOP Classes as defined in the DICOM Standard, a SOP Class for storage of images intended for Presentation and a SOP Class for storage of images intended for further Processing before presentation. These are distinguished by their SOP Class UID and by the Enumerated Value of the mandatory Attribute in the DX Series Module, Presentation Intent Type (0008,0068). The SOP Class Digital Mammography X-Ray Image storage - for Processing will be exported if the hospital wants that the Processing DICOM information is also sent to the archive and/or a CAD device is connected for scanning the "for Processing" images for calcification/nodes. The Numbering Scheme shall support 'Hanging Protocols' of PACS systems & Viewing Stations: 1. The Series Number shall start with 1 for the first Series of every Study Instance, identified by Study Instance UID. 2. The Series Number shall increase by 1 for every new Series Instance within the same Study Instance, by the timely order, the Series Instances are created. 3. The Image Number shall start with 1 for every new Series Instance. 4. The Image Number shall increase by 1 for every new Image Instance within the same Series Instance, by the timely order, the Images are created. For Digital Mammography X-Ray image Storage SOP Classes is in the DICOM Standard defined: The Digital Mammography X-Ray Image IOD specifies an image that has been created by a digital mammography imaging device. A MG image shall consist of the result of a single X-Ray exposure, in order to ensure that the anatomical and orientation attributes are meaningful for the image, permitting safe annotation, appropriate image processing and appropriate dissemination. 4.2.1.3.4.3. SOP Specific Conformance for Storage SOP Classes
This section includes the SOP specific behavior, i.e. error codes, error and exception handling, time-outs, etc. Behavior of an Application Entity SOP class is summarized as shown in next Table. The standard as well as the manufacturer specific status codes and their corresponding behavior are specified. 4.2.1.3.4.3.1. Dataset Specific Conformance for C-STORE-RQ
Detail regarding the Dataset Specific response behavior will be reported in this section. This includes the dataset specific behavior, i.e. error codes, error and exception handling, time-outs, etc.
17-Jun-2011
Page 34 of 79
Table 32: Status Response

Service Status Success Failure Error Code 0000 A7xx A9xx Cxxx Warning B000 B007 B006 Further Meaning Storage is complete Refused: Out of Resources Error: Data Set does not match SOP Class Error: cannot understand Coercion of Data Elements Data Set does not match SOP Class Elements Discarded UI status is updated The association is released. The reason is logged. The user is informed. The association is released. The reason is logged. The user is informed. The association is released. The reason is logged. The user is informed. The association is released. The reason is logged. The user is informed. The association is released. The reason is logged. The user is informed. The association is released. The reason is logged. The user is informed. Behavior
Note that the status can be inspected via the user interface. Table 33: DICOM Command COmmunication Failure Behavior
Exception Timeout Association aborted Behavior The Association is aborted using A-ABORT and command marked as failed. The reason is logged and reported to the user. The command is marked as failed. The reason is logged and reported to the user.
4.2.1.3.5.
(Real-World) Activity Storage Commitment Push Model as SCU
4.2.1.3.5.1.
Description and Sequencing of Activities
17-Jun-2011
Page 35 of 79
Figure 7: (Real World) Activaty - Storage Commitment Push Model as SCU (Asynchronous)
Figure 8: (Real World) Activity - Storage Commitment Push Model as SCU (Synchronous) Archive means that MammoDiagnost DR 2.0 stores images with Storage Commitment. This RWA may be initiated in two ways: Manually in the viewer, after clicking the store button the Eleva AE will store the selected images at the selected Storage SCP. Automatically during examination, after clicking the confirm button the Eleva AE will automatically store the related images of the performed procedure step at the configured storage SCP.
The Eleva AE will request an association with the remote Storage SCP for the applicable Storage SCP classes. After accepting the association the Eleva AE will send the store request, wait for response, and the release the association. The store response status may be inspected on the UI. The Transferred image shall not be deleted from the system until the Storage Commit N-EVENT is received.
17-Jun-2011
Page 36 of 79
Depending on the status of the store the Eleva AE may queue store requests for retries. The queued store requests can be cancelled form the UI. When an archive supports DICOM Storage Commitment, this node can be configured for it. For each image that is sent to this node, also a Storage Commitment Request is sent. The image is delete-protected until the Storage Commit Response has been received. The current status is shown in the Image Info Panel. In case of a wrong configuration (an archive is configured to support Storage Commitment, but does not really do so), the system recognizes this, and our application sees a successful Storage Commitment. 4.2.1.3.5.2. Proposed Presentation Contexts
The presentation contexts are defined in the next table. Table 34: Proposed Presentation Contexts for (Real-World) Activity Storage Commitment Push Model AS SCU
Presentation Context Table Abstract Syntax Name Storage Commitment Push Model SOP Class UID 1.2.840.10008.1.20.1 Transfer Syntax Role Name List Explicit VR Big Endian Explicit VR Little Endian Implicit VR Little Endian UID List 1.2.840.10008.1.2.2 1.2.840.10008.1.2.1 1.2.840.10008.1.2 SCU Extended Negotiation None
4.2.1.3.5.3.
SOP Specific Conformance for Storage Commitment Push Model SOP Class
This section includes the SOP specific behavior, i.e. error codes, error and exception handling, time-outs, etc. Behavior of an Application Entity SOP class is summarized as shown in next Table. The standard as well as the manufacturer specific status codes and their corresponding behavior are specified. 4.2.1.3.5.3.1. Dataset Specific Conformance for Storage Commitment Push Model SOP Class N-EVENT-REPORT-SCP
This part of the section includes the dataset specific behavior, i.e. error codes, error and exception handling, time-outs, etc. Table 35: DICOM Command Communication Failure Behavior
4.2.1.3.5.3.2.
Dataset Specific Conformance for Storage Commitment Push Model SOP Class N-ACTION-SCU
Detail regarding the Dataset Specific response behavior will be reported in this section. Table 36: Storage Commitment Attribute for N-ACTION-RQ
Attribute Name Tag Storage Commitment Module Transaction UID Referenced SOP Sequence >Referenced SOP Class UID >Referenced SOP Instance UID 0008,1195 0008,1199 0008,1150 0008,1155 Comment
This part of the section includes the dataset specific behavior, i.e. error codes, error and exception handling, time-outs, etc.
17-Jun-2011
Page 37 of 79
Table 37: Status Response

Service Status Success Refused Error Warning Error Code 0000 A7xx A9xx Cxxx B000 B006 B007 Further Meaning Storage is complete Out of resources Data set does not match SOP Class Cannot understand Coercion of data elements Elements discarded Data set does not match SOP Class UI status is updated The association is released. The reason is logged. The user is informed The association is released. The reason is logged. The user is informed The association is released. The reason is logged. The user is informed The association is released. The reason is logged. The user is informed The association is released. The reason is logged. The user is informed The association is released. The reason is logged. The user is informed Behavior

Exception Association aborted Behavior The command is marked as failed. The reason is logged and reported to the user.
4.2.1.3.6. 4.2.1.3.6.1.
(Real-World) Activity Print Management as SCU Description and Sequencing of Activities
Figure 9: (Real World) Activity - Print Management as SCU The Eleva AE cannot handle any N-EVENT-REPORT messages. A print job (film session) comprises one single film box with one single image (that is composed of 1..N modality images).
17-Jun-2011
Page 38 of 79
Behavior of the Print Component: The print component of the MammoDiagnost DR 2.0 mainly provides three different print modes, ranging from a highly automated print mode that does not interrupt the clinical acquisition workflow, over a semi-automated print mode which automatically composes the print films but gives the user the opportunity to review and manipulate these films before they are printed, to a fully manual print mode where the user has the full control over the composition of the printed films. These modes are called 'autoprint', 'autoprint with user check', and 'manual print'. Additionally the print component provides a mechanism to solve conflicts in automatically composed print films. This can be configured to be done either automatically or manually. Autoprint: The application gives the user the opportunity to make several settings, stored in a persistent database, that define how the images of an examination should be laid out when they are automatically printed. These settings include the number of images on one film, the medium to print on, the scaling of the images etc. Some of these settings are stored in a so called print template which provides a generic stencil of how images and annotations should be placed on a film. These templates are also used for manual printing. Once these settings are done, the print component is capable of printing all images of the according examination type fully automatically and without any further user interaction. Autoprint with User Check: When an examination is configured to be printed with 'autoprint with user check', the layout of the images on the film will be done according to the same settings that are also used for 'autoprint'. But instead of sending the composed print pages directly to the printer when they are ready to be printed, the user has the opportunity to review these films and to change the layout of the films as (s)he desires. The display of the composed films and the changes to the layout are done via the same user interface as used f or manual printing. When all changes are done, the user triggers the printout manually. Manual Print: For manual printing, the application provides a user interface that gives the user the opportunity to freely define the layout and content of a print page. Therefore (s)he is provided with a list of images for the selected patient and a section where the film to be printed is displayed. To fill the film the user can simply insert the images via point and click. The layout of the film c an be predefined by selecting one of the templates also used for 'autoprint'. Furthermore it is also possible to create new templates or to temporarily change the layout of an existing template. The user interface for manual printing is the same as for 'autoprint with user check'. Conflict Check: On some occasions there might be conflicts in automatically laid out print films. One kind of conflict occurs if a film is ready to be printed but not all image placeholders of the according print template are filled. This conflict is called 'incomplete page c onflict'. Another conflict might occur if the predefined scale for an image causes it to be cropped when printed on a film. This conflict is called 'scaling conflict'. The user has the opportunity to configure if these conflicts should be solved automatically or if they should be solved by user interaction. If the user chooses to solve these conflicts manually, (s)he will be informed that a conflict occurred, the film will not be printed and the user can review the conflicting film via the user interface in the same manner as if 'autoprint with user check' was configured for this film. After solving the conflict (or not if desired), the user must trigger the printout of the according film manually. To solve a 'scaling conflict' automatically the user has the opportunity to decide that the image should been 'cut', which means that the image will be printed with the predefined scale and eventually be cropped, or (s) he can decide to 'fit' the image, which means that the scale for the image will be recalculated in a way, that it will fully fit into the according placeholder. In both cases no user interaction is required. The automatic solution of an 'incomplete page conflict' can either be done by telling the print component to print the incomplete page or to change the template. The former option causes the print component to print the incomplete page without informing the user about the occurrence of the conflict, the latter causes the print component to automatically change the template so that it only contains the required number of image placeholders. The film will then be printed according to the layout of the newly selected template. 4.2.1.3.6.2. Proposed Presentation Contexts
17-Jun-2011
Page 39 of 79
Table 39: Proposed Presentation Contexts for (Real-World) Activity Print Management as SCU
Presentation Context Table Abstract Syntax Name Basic Grayscale Print Management Meta SOP Class >Basic Film Session SOP Class UID 1.2.840.10008.5.1.1.9 1.2.840.10008.5.1.1.1 Explicit VR Big Endian Explicit VR Little Endian Implicit VR Little Endian >Basic Film Box SOP Class 1.2.840.10008.5.1.1.2 Explicit VR Big Endian Explicit VR Little Endian Implicit VR Little Endian >Basic Grayscale Image Box SOP Class 1.2.840.10008.5.1.1.4 Explicit VR Big Endian Explicit VR Little Endian Implicit VR Little Endian >Printer SOP Class 1.2.840.10008.5.1.1.16 Explicit VR Big Endian Explicit VR Little Endian Implicit VR Little Endian >Presentation LUT SOP Class 1.2.840.10008.5.1.1.23 Explicit VR Big Endian Explicit VR Little Endian Implicit VR Little Endian 1.2.840.10008.1.2.2 1.2.840.10008.1.2.1 1.2.840.10008.1.2 1.2.840.10008.1.2.2 1.2.840.10008.1.2.1 1.2.840.10008.1.2 1.2.840.10008.1.2.2 1.2.840.10008.1.2.1 1.2.840.10008.1.2 1.2.840.10008.1.2.2 1.2.840.10008.1.2.1 1.2.840.10008.1.2 1.2.840.10008.1.2.2 1.2.840.10008.1.2.1 1.2.840.10008.1.2 SCU None SCU None SCU None SCU None Transfer Syntax Role Name List UID List SCU SCU Extended Negotiation None None
The behavior of the AE during responses and communication are describes in the next tables. Table 40: DICOM Command Response Status Handling Behavior for Grayscale Print Management Meta SOP Class
Service Status Success Failure Code 0000 xxxx Further Meaning Successful operation Any failure Behavior The print job continues. In the AutoPrint mode a GUI is invoked. The status panel of this GUI displays a message based on the "Further Meaning". The warning or failure response of a print request that is invoked by the Manual Print Composer GUI will be displayed by a pop-up window (if the user has not closed the GUI before the printer status was delivered. In the AutoPrint mode a GUI is invoked. The status panel of this GUI displays a message based on the "Further Meaning". The warning or failure response of a print request that is invoked by the Manual Print Composer GUI will be displayed by a pop-up window (if the user has not closed the GUI before the printer status was delivered.
Warning
xxxx
Any warning

Exception Timeout Association aborted Failed to connect Behavior The Association is aborted using A-Abort and the command is marked as failed. The reason is logged. After a maximum number of retries the user is notified via pop-up (in preview mode only). The command is marked as failed. The reason is logged. After a maximum number of retries the user is notified via pop-up (in preview mode only) Log entry. After a maximum number of retries the user is notified via pop-up (in preview mode only).
17-Jun-2011
Page 40 of 79
This section specifies each IOD created (including private IODs). Abbreviations used in the Module table for the column "Presence of Value" are: ALWAYS The attribute is always present with a value EMPTY The attribute is always present without any value (attribute sent zero length) VNAP The attribute is always present and its Value is Not Always Present (attribute sent zero length if no value is present) ANAP The attribute is present under specified condition if present then it will always have a value VNAPCV The attribute is present under specified condition if present then its Value is Not Always Present (attribute sent zero length if condition applies and no value is present) ANAPEV The attribute is present under specified condition if present then it will not have any value The abbreviations used in the Module table for the column "Source" are: AUTO The attribute value is generated automatically CONFIG The attribute value source is a configurable parameter COPY The attribute value source is another SOP instance FIXED The attribute value is hard-coded in the application IMPLICIT The attribute value source is a user-implicit setting MPPS The attribute value is the same as that use for Modality Performed Procedure Step MWL The attribute value source is a Modality Worklist USER The attribute value source is explicit user input 4.2.1.3.6.3. SOP Class SOP Specific Conformance for Basic Film Session SOP Class of the Basic Grayscale Print Management Meta
This section includes the SOP specific behavior, i.e. error codes, error and exception handling, time-outs, etc. Behavior of an Application Entity SOP class is summarized as shown in next Table. The standard as well as the manufacturer specific status codes and their corresponding behavior are specified. 4.2.1.3.6.3.1. Dataset Specific Conformance for Basic Film Session SOP Class N-CREATE-SCU
Detail regarding the Dataset Specific response behavior will be reported in this section. Table 42: Basic Film Session Presentation Module
Attribute Name Number of Copies Print Priority Medium Type Film Destination Film Session Label Tag 2000,0010 2000,0020 2000,0030 2000,0040 2000,0050 VR IS CS CS CS LO Value Presence of Value ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS Source AUTO AUTO USER CONFIG AUTO Comment
4.2.1.3.6.4.
SOP Specific Conformance for Printer SOP Class of the Basic Grayscale Print Management Meta SOP Class
This section and sub-section include the manufacturer SOP and Dataset specific information as well the status codes and their corresponding behavior. 4.2.1.3.6.4.1. Dataset Specific Conformance for Printer SOP Class N-EVENT-REPORT-SCP
Not applicable, since MammoDiagnost does not support N-EVENT-REPORT for printing.
17-Jun-2011
Page 41 of 79
4.2.1.3.6.5. Class
SOP Specific Conformance for Basic Film Box SOP Class of the Basic Grayscale Print Management Meta SOP
This section includes the SOP specific behavior, i.e. error codes, error and exception handling, time-outs, etc. Behavior of an Application Entity SOP class is summarized as shown in next Table. The standard as well as the manufacturer specific status codes and their corresponding behavior are specified. 4.2.1.3.6.5.1. Dataset Specific Conformance for Basic Film Box SOP Class N-CREATE-SCU
Detail regarding the Dataset Specific response behavior will be reported in this section. Table 43: Basic Film Box Presentation Module
Attribute Name Image Display Format Film Orientation Film Size ID Magnification Type Max Density Trim Configuration Information Tag 2010,0010 2010,0040 2010,0050 2010,0060 2010,0130 2010,0140 2010,0150 VR ST CS CS CS US CS ST Value Presence of Value ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS Source CONFIG CONFIG CONFIG CONFIG CONFIG CONFIG CONFIG Comment
Table 44: Basic Film Box Relationship Module

Attribute Name Referenced Film Session Sequence >Referenced SOP Class UID >Referenced SOP Instance UID Tag 2010,0500 0008,1150 0008,1155 VR SQ UI UI Value Presence of Value ALWAYS ALWAYS ALWAYS Source AUTO AUTO AUTO Comment
4.2.1.3.6.5.2.
Dataset Specific Conformance for Basic Film Box SOP Class N-ACTION-SCU
This part of the section includes the dataset specific behavior, i.e. error codes, error and exception handling, time-outs, etc. There are no DICOM attribute defined for N-ACTION. 4.2.1.3.6.6. SOP Specific Conformance for Presentation LUT SOP Class
This section includes the SOP specific behavior, i.e. error codes, error and exception handling, time-outs, etc. Behavior of an Application Entity SOP class is summarized as shown in next Table. The standard as well as the manufacturer specific status codes and their corresponding behavior are specified 4.2.1.3.6.6.1. Dataset Specific Conformance for Presentation LUT SOP Class N-CREATE-SCU
This section includes the dataset specific behavior, i.e. error codes, error and exception handling, time-outs, etc. Table 45: Presentation LUT Module
Attribute Name Presentation LUT Shape Tag 2050,0020 VR CS Value Value 1: IDENTITY Presence of Value ALWAYS Source Auto Comment
17-Jun-2011
Page 42 of 79
4.2.1.3.6.7. SOP Specific Conformance for Basic Grayscale Image Box SOP Class of the Basic Grayscale Print Management Meta SOP Class This section includes the SOP specific behavior, i.e. error codes, error and exception handling, time-outs, etc. Behavior of an Application Entity SOP class is summarized as shown in next Table. The standard as well as the manufacturer specific status codes and their corresponding behavior are specified. 4.2.1.3.6.7.1. Dataset Specific Conformance for Basic Grayscale Image Box SOP Class N-SET-SCU
This section includes the dataset specific behavior, i.e. error codes, error and exception handling, time-outs, etc. Table 46: Image Box Pixel Presentation Module
Attribute Name Image Box Position Polarity Basic Grayscale Image Sequence >Samples per Pixel >Photometric Interpretation >Rows >Columns >Bits Allocated >Bits Stored >High Bit >Pixel Representation >Pixel Data Tag 2020,0010 2020,0020 2020,0110 0028,0002 0028,0004 0028,0010 0028,0011 0028,0100 0028,0101 0028,0102 0028,0103 7FE0,0010 VR US CS SQ US CS US US US US US US O W/ OB 16, 8 12, 8 11, 7 0x0000 1 MONOCHROME1, MONOCHROME2 Value Presence of Value ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS Source AUTO AUTO AUTO AUTO CONFIG IMPLICIT IMPLICIT AUTO IMPLICIT AUTO AUTO AUTO Depending on the selected printer type and film size Depending on the selected printer type and film size Comment
17-Jun-2011
Page 43 of 79
4.2.1.4.
Association Acceptance Policy
This section describes the conditions under which the AE will initiate an association. The behavior of the AE during association rejection is summarized in next table. The ELEVA AE accepts associations to allow remote applications to verify application level communication. The ELEVA AE rejects association requests from unknown applications, i.e. applications that offer an unknown "calling AE title". An application is known if and only if it is defined per configuration. The ELEVA AE rejects association requests from applications that do not address the ELEVA AE, i.e. that offer a wrong "called AE title". Table 47: Association Reject Reasons
Result 1 - rejected permanent Source 1 - DICOM UL service-user Reason/Diagnosis 1 - no-reason-given Behavior Association is not established due to any problem other than that specified in the rows below. (Example: Problem while decoding the DICOM stream). An application context name other than 1.2.840.10008.3.1.1.1 is requested by the SCU during association. - The configuration does not contain a repository having the Calling AE Title as per the association request.- There is a problem in configuration (related to composing the configuration from the SCU and the SCP configuration). The called AE Title in the association request does not match the AE Title as per the configuration. Not used. Not used. Not used. Not used. Not used. Not used. Not used. Not used. Maximum number of associations is exceeded and an association request is received. Not used. Not used. Not used.
2 - application-contextname-not-supported 3 - calling-AE-title-notrecognized
7 - called-AE-title-notrecognized 2 - DICOM UL service provider (ACSE related function) 3 - DICOM UL service provider (Presentation related function) 2 - rejectedtransient 1 - DICOM UL service-user 1 - no-reason-given 2 - protocol-version-notsupported 1 - temporarycongestion 2 - local-limit-exceeded 1 - no-reason-given 2 - application-contextname-not-supported 3 - calling-AE-title-notrecognized 7 - called-AE-title-notrecognized 2 - DICOM UL service provider (ACSE related function) 1 - no-reason-given 2 - protocol-version-notsupported 3 - DICOM UL service provider (Presentation related function) 1 - temporarycongestion 2 - local-limit-exceeded
The behavior of the AE for sending an Association abort is summarized in next table. Table 48: Association Abort Policies
Source 0 - DICOM UL service-user (initiated abort) Reason/Diagnosis 0 - reason-notspecified Behavior When received, the Eleva Workspot terminates the connection with the following log: Association ABORTED by peer (0: ABORT_SOURCE_dul_user, 0: ABORT_REASON_not specified).Sent when: Association times out due to inactivity. Any other problem than ones specified in the rows below. (Example: Problem while decoding the DICOM stream, Invalid request, Echo SCP was unable to send the Response to SCU, Error writing to SCU stream).
17-Jun-2011
Page 44 of 79
Source 2 - DICOM UL serviceprovider (initiated abort)
Reason/Diagnosis 0 - reason-notspecified 1 - unrecognizedPDU 2 - unexpected-PDU
Behavior When received, the Eleva Workspot terminates the connection with the following log: Association ABORTED by peer (2: ABORT_SOURCE_dul_provider,0: ABORT_REASON_not_specified). When received, the Eleva Workspot terminates the connection with the following log: Association ABORTED by peer (2: ABORT_SOURCE_dul_provider,1: ABORT_REASON_unrecognized_pdu). Sent when: An unrecognized PDU type is received. When received, the Eleva Workspot terminates the connection wiht the following log: Association ABORTED by peer (2: ABORT_SOURCE_dul_provider, 2: ABORT_REASON_unexpected_pdu). Sent when: The received PDU type is not expected in the current state of connection. When received, the Eleva Workspot terminates the connection with the following log: Association ABORTED by peer( 2: ABORT_SOURCE_dul_provider, 4: ABORT_REASON_unrecognized_pdu_parameter). Sent when: An unrecognized Associate PDU item is received. When received, the Eleva Workspot terminates the connection with the following log: Association ABORTED by peer ( 2: ABORT_SOURCE_dul_provider, 5: ABORT_REASON_unexpected_pdu_parameter). Sent when: One of the Associate PDU items is received more than once. One of the Associate PDU items is received unexpectedly When received, the Eleva Workspot terminates the connection with the following log: association ABORTED by peer ( 2: ABORTED_SOURCE_dul_provider, 6: ABORTED_REASON_invalid_pdu_parameter). Sent when: One of the Associate PDU items is received more than once. One of the Associate PDU items is not received. Empty Called AE Title string (spaceonly) is received. Unknown abstract syntax is received. The length or the format of the received PDU item is invalid.
4 - unrecognizedPDU parameter
5 - unexpected-PDU parameter
6 - invalid-PDUparameter value
4.2.1.4.1. 4.2.1.4.1.1.
(Real-World) Activity Verification as SCP Description and Sequencing of Activities
Figure 10: (Real World) Activity - Verification as SCP
The Eleva AE accepts associations from systems that which to verify application level communication using the C-ECHO command. 4.2.1.4.1.2. Accepted Presentation Contexts
17-Jun-2011
Page 45 of 79
Table 49: Acceptable Presentation Contexts for (Real-World) Activity Verification as SCP
Presentation Context Table Abstract Syntax Name Verification SOP Class UID 1.2.840.10008.1.1 Transfer Syntax Role Name List Explicit VR Big Endian Explicit VR Little Endian Implicit VR Little Endian UID List 1.2.840.10008.1.2.2 1.2.840.10008.1.2.1 1.2.840.10008.1.2 SCP Extended Negotiation None
4.2.1.4.1.3.
SOP Specific Conformance for Verification SOP Class
This section includes the SOP specific behavior, i.e. error codes, error and exception handling, time-outs, etc. Behavior of an Application Entity SOP class is summarized as shown in next Table. The standard as well as the manufacturer specific status codes and their corresponding behavior are specified. 4.2.1.4.1.3.1. Dataset Specific Conformance for Verification C-ECHO SCP
Detail regarding the Dataset Specific response behavior will be reported in this section. Table 50: Status Response
Service Status Success Error Code 0000 Further Meaning Verification is complete Behavior The MammoDiagnost DR 2.0 has successfully received the verification request

Exception Timeout Association aborted Behavior The Association is aborted using AP-ABORT and command marked as failed. The reason is logged and reported to the user. The command is marked as failed. The reason is logged and reported to the user.
17-Jun-2011
Page 46 of 79
4.3. Network Interfaces

4.3.1. Physical Network Interfaces
The MammoDiagnost DR 2.0 provides DICOM 3.0 TCP/IP Network Communication Support as defined in Part 8 of the DICOM 3.0 Standard. TCP/IP is the only protocol stack supported. Supported physical medium include: IEEE 802-3-1995 1000Base-TX (Gigabit Ethernet) The TCP/IP Stack supported by the underlying Operating System. The API is the WinSock 2 interface as supported by the underlying Operating System. The MammoDiagnost DR 2.0 system shall not be connected to a 10 Mb/s (10Base T) network.
4.3.2.
Additional Protocols
No additional protocols are used.
4.4. Configuration
Any implementation's DICOM conformance may be dependent upon configuration, which takes place at the time of installation. Issues concerning configuration are addressed in this section.
4.4.1.
AE Title/Presentation Address Mapping
An important installation issue is the translation from AE title to presentation address. How this is to be performed is described here. 4.4.1.1. Local AE Titles
The local AE title mapping and configuration are specified as:
Table 52: AE Title configuration table

Application Entity Eleva AE ELEVA Default AE Title 3010 Default TCP/IP Port
4.4.1.2.
Remote AE Title/Presentation Address Mapping
All remote applications to be selected as destination (SCP) are configurable for the following items: The Application Entity Title of the remote application. The Presentation Address or where the remote application accepts association requests.
4.4.2.
Parameters
The specification of important operational parameters, their default value and range (if configurable) are specified here.
17-Jun-2011
Page 47 of 79
Table 53: Configuration Parameters Table

Parameter General Parameter Maximum PDU received size Maximum PDU send size Maximum number of simultaneous associations Artim Timeout Specifies the time in seconds of the ARTIM (Association Request/Reject/Release Timer Allowed values: 0: unlimited waiting time 0 < n: real time in seconds Automatic Association Timeout Specifies the association inactivity timeout in seconds after which the association is closed automatically Allow values: -1: immediate timeout 0: unlimited waiting time 0 < n: real time in seconds Transfer Syntax support: ILE, ELE, EBE Storage Specific Parameters Automatic export to a configurable destination Storage Commitment Specific Parameters Storage Commit Max Reply Waiting Time. Specifies the time in seconds that is waited for a storage commitment event report message. After this time the association will be terminated Allow values: -1: immediate timeout 0: unlimited waiting time 0 < n: real time in seconds Basic Worklist Management Specific Parameters RIS query timeout Specifies the time after which the query is automatically aborted Allow values: 1-300 minutes Background broad query time interval Specifies the time until the background query will be repeated. Allow values: 0: no broad query 0 < n: real time in minutes Print Management Specific Parameters Automatic print to a configurable destination Yes Yes Yes 240 [minutes] 0 [no broad query] Yes -1 [asynchronous] Yes No Yes Yes Yes Yes 16384 2 60 [seconds] 0 [unlimited] Configurable Default Value
Yes
ILE, ELE, EBE
17-Jun-2011
Page 48 of 79
5. Media Interchange
5.1. Implementation model
The implementation model identifies the DICOM Application Entities for Media in specific implementation and relates the Application Entities to Real-World Activities.
5.1.1.
Application Data Flow Diagram
The Eleva Workspot system consists of one single application entity only: the Eleva Workspot Application Entity (Eleva AE). Next figure shows the Media Interchange application data flow as a functional overview of the Eleva AE.
Figure 11: Media Interchange Application Data Flow Diagram The Eleva AE will act as a FSR when reading the directory of the medium. The Eleva AE will act as a FSC.FSU when writing the selected images in a patient folder onto the CD-R medium.
5.1.2.
Functional Definitions of AE's
This section shall describe in general terms the functions to be performed by the AE, and the DICOM services used to accomplish these functions. Functional Definition of MammoDiagnost DR 2.0: The Eleva AE is the one and only application entity within the MammoDiagnost DR 2.0. It includes the following service class. Media Storage Service Class: The Eleva AE can perform the Media Storage service as SCU, with capabilities for RWA Display Directory (as FSR, DICOMDIR only) and RWA Write Images (as FSC/FSU).
5.1.3.
Sequencing of Real World Activities
Write image can be initiated by selecting a proper export destination, selecting requested images and clicking the export button. Whenever a CD-R has to be written the Eleva AE first tries to read the DICOMDIR. The Eleva AE will compile the updated DICOMDIR and any required DICOM images into a CD session image; this CD session image will be written to CD-R.
5.2. AE Specifications
This section in the DICOM Conformance Statement specifies a set of Media Application Entities.
17-Jun-2011
Page 49 of 79
5.2.1.
Eleva Media - Specification
The Eleva AE provides Standard Conformance to the DICOM Media Storage Service and File Format ([DICOM] PS 3.10) and the Media Storage Application Profiles STD-GEN-CD ([DICOM] PS 3.11) for reading. Eleva AE supports Multi-Patient and Multi-Session CD-R disks. On the Eleva AE is only "adding on" of instances is supported for the FSU, deleting is not supported. The supported Application Profiles, their Roles and the Service Class (SC) options, all defined in DICOM terminology, are listed in next table. Only adding one of instances is supported for the FSU, deleting is not supported.
Table 54: AE Eleva related Application Profiles, RWA activities and roles
Supported Application Profile General Purpose CD-R Interchange STD-GEN-CD Identifier Real-World Activities Update File-set Create File-set Display Directory Roles FSU FSC DD
5.2.1.1.
File Meta Information for the Eleva
This next table specified the list of values assigned to the File Meta Information attributes that pertain to the Implementation Class and Version. Table 55: File Meta Information for the Eleva
Implementation Class UID Implementation Version Name 1.3.46.670589.30.32.0 PMS_ELEVA_32.0
5.2.1.2.
Real-World Activities
The AE specification contains a description of the Real-World Activities, which invoke the particular AE. 5.2.1.2.1. RWA - Create File-set
When an image transfer to CD-R is initiated then the Eleva AE acts as an FSC or FSU using the interchange option to export SOP Instances from the local database to a CD-R medium. 5.2.1.2.1.1. Media Storage Application Profile
The Eleva AE supports the RWA - Write Images for the STD-GEN-CD Application Profile. 5.2.1.2.1.1.1. Options
The DICOMDIR file will be extended when new images are written. In case some attributes are not present in an image but are specified as mandatory in the DICOMDIR definition in DICOM Media, a generated value will be filled in. 5.2.1.2.2. RWA - Update File-set
When an image transfer to CD-R is initiated then the Eleva AE acts as an FSC or FSU using the interchange option to export SOP Instances form the local database to a CD-R medium. 5.2.1.2.2.1. Media Storage Application Profile
The Eleva AE supports the RWA - Update File-set for the STD-GEN-CD Application Profile.
17-Jun-2011
Page 50 of 79
5.2.1.2.2.1.1.
Options
The DICOMDIR file will be extended when new images are written. In case some attributes are not present in an image but are specified as mandatory in the DICOMDIR definition in DICOM Media, a generated value will filled in. 5.2.1.2.3. RWA - Display Directory
This Media Application Entity can display the DICOMDIR (directory) of the multimedia. The ELEVA AE will act as an FSR when reading the directory of the medium. This will result in an overview of the images on the MammoDiagnost DR 2.0 screen. 5.2.1.2.3.1. Media Storage Application Profile
The Eleva AE supports the RWA Display Directory for the STD-GEN-CD Application Profile. 5.2.1.2.3.1.1. Not applicable. Options
5.3. Augmented and Private Application Profiles

Not applicable
5.4. Media Configuration

By Anonymous patient on CD where change the following DICOM attributes Table 56: Anonymous patient on CD
Attribute Media Storage SOP Instance UID Referenced SOP Instance UID in File SOP Instance UID Accession Number Institution Name Institution Address Referring Physician's Name Station Name Study Description Series Description Institutional Department Name Performing Physicians' Name Name of Physician(s) Reading Study Operators' Name Patient's Name Patient ID Patient's Birth Data Patient's Sex Other Patient Ids Patient's Age Patient's Size Patient's Weight Ethnic Group Additional Patient's History 0002,0003 0004,1511 0008,0018 0008,0050 0008,0080 0008,0081 0008,0090 0008,1010 0008,1030 0008,103E 0008,1040 0008,1050 0008,1060 0008,1070 0010,0010 0010,0020 0010,0030 0010,0040 0010,1000 0010,1010 0010,1020 0010,1030 0010,2160 0010,21B0 Tag New UID New UID New UID empty empty empty empty empty empty empty empty empty empty empty New ID New UID empty empty empty empty 0 0 empty empty Change to
17-Jun-2011
Page 51 of 79
Attribute Patient Comments Device Serial Number Protocol Name Study Instance UID Series Instance UID Study ID Frame of Reference UID Image Comments Requesting Physician Requested Attributes Sequence Requested Procedure ID 0010,4000 0018,1000 0018,1030 0020,000D 0020,000E 0020,0010 0020,0052 0020,4000 0032,1032 0040,0275 0040,1001
Tag empty anon string empty New UID New UIID New String New UID empty empty
Change to
empty Sequence New ID
17-Jun-2011
Page 52 of 79
6. Support of Character Sets

Any support for character sets in Network and Media services is described here. Table 57: Supported DICOM Character Sets
ESC Sequence ISO Registration Number ISO-IR 6 ISO-IR 100 Code Eleme nt G0 G1
Character Set Description Latin alphabet No. 1
Defined Term ISO_IR 100
Character Set ISO 646 Supplementary set of ISO 8859
17-Jun-2011
Page 53 of 79
7. Security
7.1. Security Profiles
Not applicable
7.1.1.
Security use Profiles
Not applicable
7.1.2.
Security Transport Connection Profiles
Eleva AE conforms to the Basic TLS Secure Transport Connection Profile. Eleva AE provides a service accessible tool to configure private keys and certificates of the local and remote DICOM nodes.
7.1.3.
Digital Signature Profiles
Not applicable
7.1.4.
Media Storage Security Profiles
Not applicable
7.1.5.
Attribute Confidentiality Profiles
Not applicable
7.1.6.
Network Address Management Profiles
Not applicable
7.1.7.
Time Synchronization Profiles
MammoDiagnost DR 2.0 conforms to the Basic Time Synchronization Profile as NTP client. MammoDiagnost DR 2.0 does not support secure transactions.
7.1.8.
Application Configuration Management Profiles
Eleva AE conforms to the Basic Application Level Confidentiality Profile as de-identifier. De-identified SOP Instances will be created on DICOM Media if specified by the user. No instances of the Encrypted Attributes Data Set are created. No Transfer Syntaxes are supported for encoding/decoding of Encrypted Attributes Data Sets.
17-Jun-2011
Page 54 of 79
7.1.9.
Audit Trail Profiles
MammoDiagnost DR 2.0 creates audit messages according to the IHE Basic Security Integration Profile. These messages may contain information that identifies the patient. The following messages will be created and sent to a central Audit Record Repository: ActorConfig (when security or networking configuration of the MammoDiagnost DR 2.0 is modified via the field service functionality). ActorStartStop (when MammoDiagnost DR 2.0 starts or shuts down). BeginStoringIntances and InstancesSent (when an examination is transferred from the MammoDiagnost DR 2.0 to a remote network node). DICOMInstancesDeleted (when an examination is deleted for the internal database). DICOMInstancesUsed (when an examination is selected in the patient list). UserAuthenticated (when the user logs in or logs out). SecurityAlert (when an authentication of a secure node during TLS negotiation fails, e.g. due to an invalid certificate). Export (when printing job is started).
The time that is part of the audit message is the time provided by the NTP Server.
7.2. Association Level Security

Not supported.
7.3. Application Level Security

Not applicable
17-Jun-2011
Page 55 of 79
8. Annexes of application "Eleva"

8.1. IOD Contents
8.1.1. Created SOP Instance
This section specifies each IOD created (including private IODs). It should specify the attribute name, tag, VR, and value. The value should specify the range and source (e.g. user input, Modality Worklist, automatically generated, etc.). For content items in templates, the range and source of the concept name and concept values should be specified. Whether the value is always prese nt or not shall be specified. Abbreviations used in the IOD tables for the column "Presence of Module" are: ALWAYS The module is always present CONDITIONAL The module is used under specified condition Abbreviations used in the Module table for the column "Presence of Value" are: ALWAYS The attribute is always present with a value EMPTY The attribute is always present without any value (attribute sent zero length) VNAP The attribute is always present and its Value is Not Always Present (attribute sent zero length if no value is present) ANAP The attribute is present under specified condition if present then it will always have a value ANAPCV The attribute is present under specified condition if present then its Value is Not Always Present (attribute sent zero length if condition applies and no value is present) ANAPEV The attribute is present under specified condition if present then it will not have any value The abbreviations used in the Module table for the column "Source" are: AUTO The attribute value is generated automatically CONFIG The attribute value source is a configurable parameter COPY The attribute value source is another SOP instance FIXED The attribute value is hard-coded in the application IMPLICIT The attribute value source is a user-implicit setting MPPS The attribute value is the same as that use for Modality Performed Procedure Step MWL The attribute value source is a Modality Worklist USER The attribute value source is explicit user input 8.1.1.1. List of created SOP Classes for Export Table 58: List of created SOP Classes for Export
SOP Class Name Computed Radiography Image Storage SOP Class Digital Mammography X-Ray Image Storage - Pres. SOP Digital Mammography X-Ray Image Storage - Proc. SOP 1.2.840.10008.5.1.4.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 SOP Class UID
8.1.1.2.
Computed Radiography Image Storage SOP Class Table 59: IOD of Created Computed Radiography Image Storage SOP Class Instances
Information Entity Module Patient Module General Study Module Patient Study Module General Series Module CR Series Module Presence Of Module ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS
Patient Study Study Series Series
17-Jun-2011
Page 56 of 79
Equipment Image Image Image Image Image Image Image
General Equipment Module General Image Module Image Pixel Module CR Image Module Overlay Plane Module Modality LUT Module VOI LUT Module SOP Common Module Extended Dicom and Private attributes
ALWAYS ALWAYS ALWAYS ALWAYS CONDITIONAL ALWAYS ALWAYS ALWAYS ALWAYS
Table 60: Patient Module

Attribute Name Patient's Name Patient ID Patient's Birth Date Patient's Sex Other Patient IDs Ethnic Group Patient Comments Issuer of Patient ID Tag 0010,0010 0010,0020 0010,0030 0010,0040 0010,1000 0010,2160 0010,4000 0010,0021 VR PN LO DA CS LO SH LT LO F, M, O Value Presence of Value VNAP ALWAYS VNAP ANAP ANAPCV ANAP ANAP ANAPCV Source MWL, USER AUTO, MWL MWL, USER MWL, USER MWL, USER AUTO MWL, USER MWL, USER Comment
Table 61: General Study Module

Attribute Name Study Date Study Time Accession Number Referring Physician's Name Study Description Procedure Code Sequence >Code Value >Coding Scheme Designator >Coding Scheme Version >Code Meaning Referenced Study Sequence >Referenced SOP Class UID >Referenced SOP Instance UID Study Instance UID Study ID Tag 0008,0020 0008,0030 0008,0050 0008,0090 0008,1030 0008,1032 0008,0100 0008,0102 0008,0103 0008,0104 0008,1110 0008,1150 0008,1155 0020,000D 0020,0010 VR DA TM SH PN LO SQ SH SH SH LO SQ UI UI UI SH Value Presence of Value VNAP VNAP VNAP VNAP ANAP ANAP ALWAYS ALWAYS ALWAYS ALWAYS ANAP ANAPEV ANAPEV ALWAYS VNAP Source AUTO AUTO MWL, USER MWL, USER MWL, USER MWL MWL MWL MWL MWL MWL MWL MWL AUTO, MWL AUTO, MWL Comment
17-Jun-2011
Page 57 of 79
Table 62: Patient Study Module

Attribute Name Patient's Age Patient's Size Patient's Weight Occupation Additional Patient History Tag 0010,1010 0010,1020 0010,1030 0010,2180 0010,21B0 VR AS DS DS SH LT Value Presence of Value ANAP ANAP ANAP ANAP ANAP Source MWL, USER MWL, USER MWL, USER MWL, USER MWL, USER Default: 0.0 Default: 0.0 Comment
Table 63: General Series Module

Attribute Name Series Date Series Time Modality Series Description Performing Physician's Name Operators' Name Referenced Performed Procedure Step Sequence >Referenced SOP Class UID >Referenced SOP Instance UID Protocol Name Series Instance UID Series Number Laterality Request Attributes Sequence >Scheduled Procedure Step Description >Scheduled Protocol Code Sequence >>Code Value >>Coding Scheme Designator >>Coding Scheme Version >>Code Meaning >Scheduled Procedure Step ID >Requested Procedure ID Performed Procedure Step Start Date Performed Procedure Step Start Time Tag 0008,0021 0008,0031 0008,0060 0008,103E 0008,1050 0008,1070 0008,1111 0008,1150 0008,1155 0018,1030 0020,000E 0020,0011 0020,0060 0040,0275 0040,0007 0040,0008 0008,0100 0008,0102 0008,0103 0008,0104 0040,0009 0040,1001 0040,0244 0040,0245 VR DA TM CS LO PN PN SQ UI UI LO UI IS CS SQ LO SQ SH SH SH LO SH SH DA TM CR Value Presence of Value ANAP ANAP ALWAYS ANAP ANAP ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS VNAP ANAP ANAP ANAP ALWAYS ALWAYS ALWAYS ALWAYS ANAPEV ANAPEV ANAP ANAP Source AUTO AUTO CONFIG MPPS, USER MPPS, USER MPPS, USER AUTO AUTO AUTO MWL, USER AUTO, MPPS AUTO, MPPS CONFIG MWL MWL MWL MWL MWL MWL MWL MWL MWL AUTO, MPPS AUTO, MPPS Required if the body part examined is a paired structure Default: Emergency Comment
17-Jun-2011
Page 58 of 79
Performed Procedure Step ID Performed Procedure Step Description Performed Protocol Code Sequence >Code Value >Coding Scheme Designator >Code Meaning
0040,0253 0040,0254 0040,0260 0008,0100 0008,0102 0008,0104
SH LO SQ SH SH LO
ANAP ANAP ANAP ALWAYS ALWAYS ALWAYS
AUTO, MPPS AUTO, MPPS MWL MWL MWL MWL
Table 64: CR Series Module

Attribute Name Body Part Examined View Position Tag 0018,0015 0018,5101 VR CS CS Value Presence of Value VNAP VNAP Source MPPS, USER AUTO Comment
Table 65: General Equipment Module

Attribute Name Manufacturer Institution Name Institution Address Station Name Institutional Department Name Manufacturer's Model Name Device Serial Number Software Version(s) Spatial Resolution Tag 0008,0070 0008,0080 0008,0081 0008,1010 0008,1040 0008,1090 0018,1000 0018,1020 0018,1050 VR LO LO ST SH LO LO LO LO DS MammoDiagnost DR Value Philips Medical Systems Presence of Value ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS Source AUTO CONFIG CONFIG CONFIG CONFIG AUTO CONFIG AUTO AUTO Comment
Table 66: General Image Module

Attribute Name Image Type Acquisition Date Content Date Acquisition Time Content Time Instance Number Patient Orientation Quality Control Image Burned In Annotation Lossy Image Compression Presentation LUT Shape Tag 0008,0008 0008,0022 0008,0023 0008,0032 0008,0033 0020,0013 0020,0020 0028,0300 0028,0301 0028,2110 2050,0020 VR CS DA DA TM TM IS CS CS CS CS CS NO, YES 00 IDENTITY Value Value 1: ORIGINAL, Value 2: PRIMARY Presence of Value ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS VNAP ALWAYS VNAP ALWAYS ALWAYS ALWAYS Source AUTO AUTO AUTO AUTO AUTO AUTO AUTO, CONFIG AUTO AUTO, USER AUTO AUTO Comment
Table 67: Image Pixel Module

Attribute Name Samples per Pixel Rows Tag 0028,0002 0028,0010 VR US US 1 Value Presence of Value ALWAYS ALWAYS Source AUTO AUTO Comment
17-Jun-2011
Page 59 of 79
Columns Bits Allocated Bits Stored High Bit Pixel Representation Pixel Data
0028,0011 0028,0100 0028,0101 0028,0102 0028,0103 7FE0,0010
US US US US US O W/ OB 16 10, 12, 15 11, 14, 9 0x0000
ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS
AUTO AUTO CONFIG AUTO AUTO AUTO
Table 68: CR Image Module

Attribute Name KVP Distance Source to Detector Distance Source to Patient Exposure Time Exposure Exposure in As Imager Pixel Spacing Acquisition Device Processing Description Relative X-ray Exposure Photometric Interpretation Tag 0018,0060 0018,1110 0018,1111 0018,1150 0018,1152 0018,1153 0018,1164 0018,1400 0018,1405 0028,0004 VR DS DS DS IS IS IS DS LO IS CS MONOCHROME2 Value Presence of Value ANAP ANAP ANAP ANAP ANAP ANAPCV ALWAYS ANAPCV ANAP ALWAYS Source AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO Comment
Table 69: Overlay Plane Module

Attribute Name Overlay Rows Overlay Columns Overlay Type Overlay Origin Overlay Bits Allocated Overlay Bit Position Overlay Data Tag 6000,0010 6000,0011 6000,0040 6000,0050 6000,0100 6000,0102 6000,3000 VR US US CS SS US US O W/ OB G Value 1: 1, Value 2: 1 1 0 Value Presence of Value ANAP ANAP ANAP ANAP ANAP ANAP ANAP Source AUTO AUTO AUTO AUTO AUTO AUTO AUTO Comment
Table 70: Modality LUT Module

Attribute Name Rescale Intercept Rescale Slope Rescale Type Tag 0028,1052 0028,1053 0028,1054 VR DS DS LO 0.0 1.0 US Value Presence of Value ALWAYS ALWAYS ALWAYS Source AUTO AUTO AUTO Comment
Table 71: VOI LUT Module

Attribute Name Window Center Window Width Tag 0028,1050 0028,1051 VR DS DS Value Value 1: 2047.0 Value 1: 4095.0 Presence of Value ANAP ANAP Source AUTO AUTO Comment
17-Jun-2011
Page 60 of 79
Table 72: SOP Common Module

Attribute Name Specific Character Set SOP Class UID SOP Instance UID Tag 0008,0005 0008,0016 0008,0018 VR CS UI UI Value Presence of Value ANAPEV ANAPEV ANAPEV Source AUTO AUTO AUTO Comment
8.1.1.3.
Digital Mammography X-Ray Image Storage - Pres. SOP Table 73: IOD of Created Digital Mammography X-Ray Image Storage - Pres. SOP Instances
Information Entity Module Patient Module General Study Module Patient Study Module General Series Module Mammography Series Module DX Series Module Frame of Reference Module General Equipment Module General Image Module Image Pixel Module Contrast/Bolus Module Acquisition Context Module Display Shutter Module DX Image Module X-Ray Collimator Module DX Detector Module DX Positioning Module X-Ray Acquisition Dose Module X-Ray Generation Module X-Ray Filtration Module X-Ray Grid Module Mammography Image Module Overlay Plane Module SOP Common Module Extended Dicom and Private attributes Presence Of Module ALWAYS ALWAYS CONDITIONAL ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS CONDITIONAL ALWAYS CONDITIONAL ALWAYS CONDITIONAL ALWAYS CONDITIONAL CONDITIONAL CONDITIONAL CONDITIONAL CONDITIONAL ALWAYS CONDITIONAL ALWAYS CONDITIONAL
Patient Study Study Series Series Series Frame of Reference Equipment Image Image Image Image Image Image Image Image Image Image Image Image Image Image Image Image

Attribute Name Patient's Name Patient ID Patient's Birth Date Patient's Sex Other Patient IDs Tag 0010,0010 0010,0020 0010,0030 0010,0040 0010,1000 VR PN LO DA CS LO F, M, O Value Presence of Value VNAP ALWAYS VNAP VNAP ANAP Source MWL, USER MWL, USER MWL, USER MWL, USER MWL, USER Comment
17-Jun-2011
Page 61 of 79
Ethnic Group Patient Comments Issuer of Patient ID
0010,2160 0010,4000 0010,0021
SH LT LO
ANAP ANAP ANAP
MWL, USER MWL, USER MWL, USER

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

Attribute Name Patient's Age Patient's Size Patient's Weight Additional Patient History Tag 0010,1010 0010,1020 0010,1030 0010,21B0 VR AS DS DS LT Value Presence of Value VNAP ANAP ANAP ANAP Source MWL, USER MWL, USER MWL, USER MWL, USER Comment

Attribute Name Series Date Series Time Series Description Performing Physician's Name Operators' Name Body Part Examined Tag 0008,0021 0008,0031 0008,103E 0008,1050 0008,1070 0018,0015 VR DA TM LO PN PN CS Value Presence of Value ANAP ANAP ANAP ANAP ANAP ANAP Source MPPS MPPS MPPS, USER MPPS, USER MPPS, USER USER Comment
17-Jun-2011
Page 62 of 79
Protocol Name Series Instance UID Series Number Performed Procedure Step Start Date Performed Procedure Step Start Time Performed Procedure Step ID Performed Procedure Step Description Performed Protocol Code Sequence >Code Value >Coding Scheme Designator >Code Meaning
0018,1030 0020,000E 0020,0011 0040,0244 0040,0245 0040,0253 0040,0254 0040,0260 0008,0100 0008,0102 0008,0104
LO UI IS DA TM SH LO SQ SH SH LO
ANAP ALWAYS VNAP ANAPCV ANAPCV ANAPCV ANAPCV ANAP ALWAYS ALWAYS ALWAYS
MPPS, USER AUTO, MPPS AUTO MPPS MPPS MPPS MPPS MWL MWL MWL MWL
Table 78: Mammography Series Module

Attribute Name Modality Request Attributes Sequence >Scheduled Procedure Step Description >Scheduled Protocol Code Sequence >>Code Value >>Coding Scheme Designator >>Code Meaning >Scheduled Procedure Step ID >Requested Procedure ID Tag 0008,0060 0040,0275 0040,0007 0040,0008 0008,0100 0008,0102 0008,0104 0040,0009 0040,1001 VR CS SQ LO SQ SH SH LO SH SH MG Value Presence of Value ALWAYS ANAP ANAP ANAP ALWAYS ALWAYS ALWAYS ANAPEV ANAPEV Source AUTO MWL MWL MWL MWL MWL MWL MWL MWL Comment
Table 79: DX Series Module

Attribute Name Presentation Intent Type Referenced Performed Procedure Step Sequence >Referenced SOP Class UID >Referenced SOP Instance UID Tag 0008,0068 0008,1111 0008,1150 0008,1155 VR CS SQ UI UI 1.2.840.10008.3.1.2.3.3 Value FOR PRESENTATION Presence of Value ALWAYS ANAP ANAP ANAP Source AUTO AUTO AUTO AUTO Comment
Table 80: Frame of Reference Module

Attribute Name Frame of Reference UID Position Reference Indicator Tag 0020,0052 0020,1040 VR UI LO Value Presence of Value ALWAYS VNAP Source AUTO AUTO Comment

Attribute Name Manufacturer Institution Name Institution Address Tag 0008,0070 0008,0080 0008,0081 VR LO LO ST Value Philips Medical Systems Presence of Value ALWAYS ALWAYS ALWAYS Source AUTO CONFIG CONFIG Comment
17-Jun-2011
Page 63 of 79
Station Name Institutional Department Name Manufacturer's Model Name Device Serial Number Software Version(s) Spatial Resolution Pixel Padding Value
0008,1010 0008,1040 0008,1090 0018,1000 0018,1020 0018,1050 0028,0120
SH LO LO LO LO DS US /SS MammoDiagnost DR
ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS
CONFIG CONFIG AUTO CONFIG AUTO AUTO AUTO

Attribute Name Acquisition Date Content Date Acquisition Time Content Time Source Image Sequence >Spatial Locations Preserved >Referenced SOP Class UID >Referenced SOP Instance UID Instance Number Quality Control Image Icon Image Sequence >Rows >Columns >Pixel Aspect Ratio >Pixel Data Tag 0008,0022 0008,0023 0008,0032 0008,0033 0008,2112 0028,135A 0008,1150 0008,1155 0020,0013 0028,0300 0088,0200 0028,0010 0028,0011 0028,0034 7FE0,0010 VR DA DA TM TM SQ CS UI UI IS CS SQ US US IS O W/ OB Value Presence of Value ANAPCV ANAPCV ANAPCV ANAPCV ANAPCV ANAPCV ALWAYS ALWAYS VNAP ANAPCV ANAP ALWAYS ALWAYS ANAP ANAP Source AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO Comment

Attribute Name Rows Columns Pixel Data Tag 0028,0010 0028,0011 7FE0,0010 VR US US O W/ OB Value Presence of Value ALWAYS ALWAYS ANAP Source AUTO AUTO AUTO Comment
Table 84: Contrast/Bolus Module

Attribute Name Contrast/Bolus Agent Tag 0018,0010 VR LO Value Presence of Value VNAP Source AUTO Comment
Table 85: Acquisition Context Module

Attribute Name Acquisition Context Sequence Tag 0040,0555 VR SQ Value Presence of Value VNAP Source AUTO Comment
Table 86: Display Shutter Module

Attribute Name Shutter Shape Tag 0018,1600 VR CS Value Presence of Value ALWAYS Source AUTO Comment
17-Jun-2011
Page 64 of 79
Shutter Left Vertical Edge Shutter Right Vertical Edge Shutter Upper Horizontal Edge Shutter Lower Horizontal Edge Center of Circular Shutter Radius of Circular Shutter Vertices of the Polygonal Shutter
0018,1602 0018,1604 0018,1606 0018,1608 0018,1610 0018,1612 0018,1620
IS IS IS IS IS IS IS
ANAPEV ANAPEV ANAPEV ANAPEV ANAPEV ANAPEV ANAPEV
AUTO AUTO AUTO AUTO AUTO AUTO AUTO
Table 87: DX Image Module

Attribute Name Acquisition Device Processing Description Patient Orientation Samples per Pixel Photometric Interpretation Bits Allocated Bits Stored High Bit Pixel Representation Burned In Annotation Pixel Intensity Relationship Pixel Intensity Relationship Sign Window Center Window Width Rescale Intercept Rescale Slope Rescale Type Lossy Image Compression Presentation LUT Shape Tag 0018,1400 0020,0020 0028,0002 0028,0004 0028,0100 0028,0101 0028,0102 0028,0103 0028,0301 0028,1040 0028,1041 0028,1050 0028,1051 0028,1052 0028,1053 0028,1054 0028,2110 2050,0020 VR LO CS US CS US US US US CS CS SS DS DS DS DS LO CS CS 00 IDENTITY LOG 1 Value 1: 2047.0 Value 1: 4095.0 MONOCHROME2 16 10, 12, 15 11, 14, 9 Value Presence of Value ANAPCV ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ANAP ANAP ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS Source AUTO AUTO AUTO AUTO AUTO CONFIG AUTO AUTO CONFIG AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO Comment
Table 88: X-Ray Collimator Module

Attribute Name Collimator Shape Collimator Left Vertical Edge Collimator Right Vertical Edge Collimator Upper Horizontal Edge Collimator Lower Horizontal Edge Tag 0018,1700 0018,1702 0018,1704 0018,1706 0018,1708 VR CS IS IS IS IS Value Presence of Value ALWAYS ANAP ANAP ANAP ANAP Source AUTO AUTO AUTO AUTO AUTO Comment
Table 89: DX Detector Module

Attribute Name Field of View Shape Field of View Dimension(s) Imager Pixel Spacing Field of View Origin Field of View Rotation Field of View Horizontal Flip Tag 0018,1147 0018,1149 0018,1164 0018,7030 0018,7032 0018,7034 VR CS IS DS DS DS CS Value Presence of Value ANAPCV ANAPCV ALWAYS ANAPEV ANAPEV ANAPEV Source AUTO AUTO AUTO AUTO AUTO AUTO Comment
17-Jun-2011
Page 65 of 79
Detector Temperature Detector Type Detector Mode Detector ID Date of Last Detector Calibration Detector Active Shape Detector Active Dimension(s) Detector Active Origin Detector Manufacturer Name Detector Manufacturer's Model Name
0018,7001 0018,7004 0018,7008 0018,700A 0018,700C 0018,7024 0018,7026 0018,7028 0018,702A 0018,702B
DS CS LT SH DA CS DS DS LO LO CONTACT, MAG, STEREO
ANAPCV VNAP ANAPCV VNAP ANAP ANAPCV ANAPCV ANAPCV ANAPCV ANAPCV
AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO for non-stereo images CONTACT or MAG
Table 90: DX Positioning Module

Attribute Name Distance Source to Detector Distance Source to Patient Estimated Radiographic Magnification Factor Body Part Thickness Compression Force Detector Primary Angle Detector Secondary Angle View Position View Code Sequence >View Modifier Code Sequence Tag 0018,1110 0018,1111 0018,1114 0018,11A0 0018,11A2 0018,1530 0018,1531 0018,5101 0054,0220 0054,0222 VR DS DS DS DS DS DS DS CS SQ SQ -15, 0, 15 0 Value Presence of Value ANAP ANAP ANAP ANAP ANAP ANAP ANAP ANAP ANAPCV ANAPCV Source AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO 0 for all non-stereo images. 0 for all images. Comment
Table 91: X-Ray Acquisition Dose Module

Attribute Name KVP Exposure Time Exposure Exposure in As Image and Fluoroscopy Area Dose Product Relative X-ray Exposure Entrance Dose Organ Dose Entrance Dose in mGy Tag 0018,0060 0018,1150 0018,1152 0018,1153 0018,115E 0018,1405 0040,0302 0040,0316 0040,8302 VR DS IS IS IS DS IS US DS DS Value Presence of Value ANAP ANAP ANAP ANAP ANAP ANAP ANAP ANAP ANAP Source AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO Comment
Table 92: X-Ray Generation Module

Attribute Name Focal Spot(s) Anode Target Material Exposure Control Mode Exposure Time in mS Tag 0018,1190 0018,1191 0018,7060 0018,8150 VR DS CS CS DS Value Presence of Value ANAP ANAP ANAP ANAP Source AUTO AUTO AUTO AUTO Comment
17-Jun-2011
Page 66 of 79
Table 93: X-Ray Filtration Module

Attribute Name Filter Material Tag 0018,7050 VR CS Value Presence of Value ANAP Source AUTO Comment
Table 94: X-Ray Grid Module

Attribute Name Grid Tag 0018,1166 VR CS Value FOCUSED, NONE, PARALLEL, RECIPROCATING Presence of Value VNAP Source AUTO Comment For Magnification-Exposures the applied value is "NONE". For Non-Magnification-Exposures the applied values are "RECIPROCATING\PARALLEL\FOCUS ED
Table 95: Mammography Image Module

Attribute Name Image Type Tag 0008,0008 VR CS Value Value 1: ORIGINAL, Value 2: PRIMARY, Value 3: POSTBIOPSY, STEREO_MINUS/STER EO_PLUS, STEREO_SCOUT MAMMOGRAPHIC Presence of Value ALWAYS Source AUTO Comment
Positioner Type Positioner Primary Angle Image Laterality Breast Implant Present Partial View Organ Exposed View Code Sequence >View Modifier Code Sequence >>Code Value >>Coding Scheme Designator >>Code Meaning >Code Value >Coding Scheme Designator >Code Meaning Anatomic Region Sequence >Anatomic Region Modifier Sequence >>Code Value >>Coding Scheme Designator >>Code Meaning >Code Value >Coding Scheme Designator >Code Meaning
0018,1508 0018,1510 0020,0062 0028,1300 0028,1350 0040,0318 0054,0220 0054,0222 0008,0100 0008,0102 0008,0104 0008,0100 0008,0102 0008,0104 0008,2218 0008,2220 0008,0100 0008,0102 0008,0104 0008,0100 0008,0102 0008,0104
CS DS CS CS CS CS SQ SQ SH SH LO SH SH LO SQ SQ SH SH LO SH SH LO
ALWAYS ANAPCV ALWAYS ANAPCV ANAPCV
AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO
BREAST
ALWAYS ALWAYS VNAP ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ANAP ANAP ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS

Attribute Name Overlay Rows Tag 6000,0010 VR US Value Presence of Value ALWAYS Source AUTO Comment Up to 10 Overlays may be included in Stereo Images
17-Jun-2011
Page 67 of 79
Overlay Columns Overlay Description Overlay Type Overlay Origin Overlay Bits Allocated Overlay Bit Position Overlay Label Overlay Data
6000,0011 6000,0022 6000,0040 6000,0050 6000,0100 6000,0102 6000,1500 6000,3000
US LO CS SS US US LO O W/ OB 1 0 G
ALWAYS ANAPCV ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS
AUTO AUTO AUTO AUTO AUTO AUTO AUTO, USER AUTO
Up to 10 Overlays may be included in Stereo Images May stay empty Up to 10 Overlays may be included in Stereo Images
Up to 10 Overlays may be included in Stereo Images

Attribute Name Specific Character Set SOP Class UID SOP Instance UID Tag 0008,0005 0008,0016 0008,0018 VR CS UI UI Value ISO_IR 100 1.2.840.10008.5.1.4.1.1. 1.2 Presence of Value ANAP ALWAYS ALWAYS Source AUTO AUTO AUTO Comment
8.1.1.4.
Digital Mammography X-Ray Image Storage - Proc. SOP Table 98: IOD of Created Digital Mammography X-Ray Image Storage - Proc. SOP Instances
Information Entity Module Patient Module General Study Module Patient Study Module General Series Module Mammography Series Module DX Series Module Frame of Reference Module General Equipment Module General Image Module Image Pixel Module Contrast/Bolus Module Acquisition Context Module Display Shutter Module DX Image Module X-Ray Collimator Module DX Detector Module DX Positioning Module X-Ray Acquisition Dose Module X-Ray Generation Module X-Ray Filtration Module X-Ray Grid Module Mammography Image Module Overlay Plane Module SOP Common Module Extended Dicom and Private attributes Presence Of Module ALWAYS ALWAYS CONDITIONAL ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS CONDITIONAL ALWAYS CONDITIONAL ALWAYS CONDITIONAL ALWAYS CONDITIONAL CONDITIONAL CONDITIONAL CONDITIONAL CONDITIONAL ALWAYS CONDITIONAL ALWAYS CONDITIONAL
Patient Study Study Series Series Series Frame of Reference Equipment Image Image Image Image Image Image Image Image Image Image Image Image Image Image Image Image
17-Jun-2011
Page 68 of 79

Attribute Name Patient's Name Patient ID Patient's Birth Date Patient's Sex Other Patient IDs Ethnic Group Patient Comments Issuer of Patient ID Tag 0010,0010 0010,0020 0010,0030 0010,0040 0010,1000 0010,2160 0010,4000 0010,0021 VR PN LO DA CS LO SH LT LO F, M, O Value Presence of Value VNAP ALWAYS VNAP VNAP ANAP ANAP ANAP ANAP Source MWL, USER MWL, USER MWL, USER MWL, USER MWL, USER MWL, USER MWL, USER MWL, USER Comment

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

Attribute Name Patient's Age Patient's Size Patient's Weight Additional Patient History Tag 0010,1010 0010,1020 0010,1030 0010,21B0 VR AS DS DS LT Value Presence of Value VNAP ANAP ANAP ANAP Source MWL, USER MWL, USER MWL, USER MWL, USER Comment
17-Jun-2011
Page 69 of 79

Attribute Name Series Date Series Time Series Description Performing Physician's Name Operators' Name Body Part Examined Protocol Name Series Instance UID Series Number Performed Procedure Step Start Date Performed Procedure Step Start Time Performed Procedure Step ID Performed Procedure Step Description Performed Protocol Code Sequence >Code Value >Coding Scheme Designator >Code Meaning Tag 0008,0021 0008,0031 0008,103E 0008,1050 0008,1070 0018,0015 0018,1030 0020,000E 0020,0011 0040,0244 0040,0245 0040,0253 0040,0254 0040,0260 0008,0100 0008,0102 0008,0104 VR DA TM LO PN PN CS LO UI IS DA TM SH LO SQ SH SH LO Value Presence of Value ANAP ANAP ANAP ANAP ANAP ANAP ANAP ALWAYS VNAP ANAPCV ANAPCV ANAPCV ANAPCV ANAP ALWAYS ALWAYS ALWAYS Source MPPS MPPS MPPS, USER MPPS, USER MPPS, USER USER MPPS, USER AUTO, MPPS AUTO, MPPS MPPS MPPS MPPS MPPS MWL MWL MWL MWL Comment
Table 103: Mammography Series Module

Attribute Name Modality Request Attributes Sequence >Scheduled Procedure Step Description >Scheduled Protocol Code Sequence >>Code Value >>Coding Scheme Designator >>Code Meaning >Scheduled Procedure Step ID >Requested Procedure ID Tag 0008,0060 0040,0275 0040,0007 0040,0008 0008,0100 0008,0102 0008,0104 0040,0009 0040,1001 VR CS SQ LO SQ SH SH LO SH SH MG Value Presence of Value ALWAYS ANAP ANAP ANAP ALWAYS ALWAYS ALWAYS ANAPEV ANAPEV Source AUTO MWL MWL MWL MWL MWL MWL MWL MWL Comment
Table 104: DX Series Module

Attribute Name Presentation Intent Type Referenced Performed Procedure Step Sequence >Referenced SOP Class UID Tag 0008,0068 0008,1111 0008,1150 VR CS SQ UI Value PROCESSING Presence of Value ALWAYS ANAP ALWAYS Source AUTO AUTO AUTO Comment
17-Jun-2011
Page 70 of 79
>Referenced SOP Instance UID
0008,1155
UI
1.2.840.10008.3.1.2.3.3
ALWAYS
AUTO
Table 105: Frame of Reference Module

Attribute Name Frame of Reference UID Position Reference Indicator Tag 0020,0052 0020,1040 VR UI LO Value Presence of Value ALWAYS VNAP Source AUTO AUTO Comment

Attribute Name Manufacturer Institution Name Institution Address Station Name Institutional Department Name Manufacturer's Model Name Device Serial Number Software Version(s) Spatial Resolution Pixel Padding Value Tag 0008,0070 0008,0080 0008,0081 0008,1010 0008,1040 0008,1090 0018,1000 0018,1020 0018,1050 0028,0120 VR LO LO ST SH LO LO LO LO DS US /SS MammoDiagnost DR Value Philips Medical Systems Presence of Value ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS Source AUTO CONFIG CONFIG CONFIG CONFIG AUTO CONFIG AUTO AUTO AUTO Comment

Attribute Name Acquisition Date Content Date Acquisition Time Content Time Source Image Sequence >Spatial Locations Preserved >Referenced SOP Class UID >Referenced SOP Instance UID Instance Number Quality Control Image Icon Image Sequence >Rows >Columns >Pixel Aspect Ratio >Pixel Data Tag 0008,0022 0008,0023 0008,0032 0008,0033 0008,2112 0028,135A 0008,1150 0008,1155 0020,0013 0028,0300 0088,0200 0028,0010 0028,0011 0028,0034 7FE0,0010 VR DA DA TM TM SQ CS UI UI IS CS SQ US US IS O W/ OB Value Presence of Value ANAPCV ANAPCV ANAPCV ANAPCV ANAPCV ANAPCV ALWAYS ALWAYS VNAP ANAPCV ANAP ALWAYS ALWAYS ANAP ANAP Source AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO Comment

Attribute Name Columns Bits Allocated Pixel Data Tag 0028,0011 0028,0100 7FE0,0010 VR US US O W/ OB Value Presence of Value ALWAYS ALWAYS ANAP Source AUTO AUTO AUTO Comment
17-Jun-2011
Page 71 of 79
Table 109: Contrast/Bolus Module

Attribute Name Contrast/Bolus Agent Tag 0018,0010 VR LO Value Presence of Value VNAP Source AUTO Comment
Table 110: Acquisition Context Module

Attribute Name Acquisition Context Sequence Tag 0040,0555 VR SQ Value Presence of Value VNAP Source AUTO Comment
Table 111: Display Shutter Module

Attribute Name Shutter Shape Shutter Left Vertical Edge Shutter Right Vertical Edge Shutter Upper Horizontal Edge Shutter Lower Horizontal Edge Center of Circular Shutter Radius of Circular Shutter Vertices of the Polygonal Shutter Tag 0018,1600 0018,1602 0018,1604 0018,1606 0018,1608 0018,1610 0018,1612 0018,1620 VR CS IS IS IS IS IS IS IS Value Presence of Value ALWAYS ANAPEV ANAPEV ANAPEV ANAPEV ANAPEV ANAPEV ANAPEV Source AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO Comment
Table 112: DX Image Module

Attribute Name Acquisition Device Processing Description Patient Orientation Samples per Pixel Photometric Interpretation Bits Allocated Bits Stored High Bit Pixel Representation Burned In Annotation Pixel Intensity Relationship Pixel Intensity Relationship Sign Window Center Window Width Rescale Intercept Rescale Slope Rescale Type Lossy Image Compression Presentation LUT Shape Tag 0018,1400 0020,0020 0028,0002 0028,0004 0028,0100 0028,0101 0028,0102 0028,0103 0028,0301 0028,1040 0028,1041 0028,1050 0028,1051 0028,1052 0028,1053 0028,1054 0028,2110 2050,0020 VR LO CS US CS US US US US CS CS SS DS DS DS DS LO CS CS 00 IDENTITY LOG 1 Value 1: 2047.0 Value 1: 4095.0 MONOCHROME2 16 10, 12, 15 11, 14, 9 Value Presence of Value ANAPCV ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ANAP ANAP ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS Source AUTO AUTO AUTO AUTO AUTO CONFIG AUTO AUTO CONFIG AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO Comment
Table 113: X-Ray Collimator Module

Attribute Name Collimator Shape Collimator Left Vertical Edge Collimator Right Vertical Edge Tag 0018,1700 0018,1702 0018,1704 VR CS IS IS Value Presence of Value ALWAYS ANAP ANAP Source AUTO AUTO AUTO Comment
17-Jun-2011
Page 72 of 79
Collimator Upper Horizontal Edge Collimator Lower Horizontal Edge
0018,1706 0018,1708
IS IS
ANAP ANAP
AUTO AUTO
Table 114: DX Detector Module

Attribute Name Field of View Shape Field of View Dimension(s) Imager Pixel Spacing Field of View Origin Field of View Rotation Field of View Horizontal Flip Detector Temperature Detector Type Detector Mode Detector ID Date of Last Detector Calibration Detector Active Shape Detector Active Dimension(s) Detector Active Origin Detector Manufacturer Name Detector Manufacturer's Model Name Tag 0018,1147 0018,1149 0018,1164 0018,7030 0018,7032 0018,7034 0018,7001 0018,7004 0018,7008 0018,700A 0018,700C 0018,7024 0018,7026 0018,7028 0018,702A 0018,702B VR CS IS DS DS DS CS DS CS LT SH DA CS DS DS LO LO CONTACT, MAG, STEREO Value Presence of Value ANAPCV ANAPCV ALWAYS ANAPEV ANAPEV ANAPEV ANAPCV VNAP ANAPCV ANAPCV ANAPCV ANAPCV ANAPCV ANAPCV ANAPCV ANAPCV Source AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO for non-stereo images CONTACT or MAG Comment
Table 115: DX Positioning Module

Attribute Name Distance Source to Detector Distance Source to Patient Estimated Radiographic Magnification Factor Body Part Thickness Compression Force Detector Primary Angle Detector Secondary Angle View Position View Code Sequence >View Modifier Code Sequence Tag 0018,1110 0018,1111 0018,1114 0018,11A0 0018,11A2 0018,1530 0018,1531 0018,5101 0054,0220 0054,0222 VR DS DS DS DS DS DS DS CS SQ SQ -15, 0, 15 0 Value Presence of Value ANAP ANAP ANAP ANAP ANAP ANAP ANAP ANAP ANAPCV ANAPCV Source AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO 0 for all non-stereo images. 0 for all images. Comment
Table 116: X-Ray Acquisition Dose Module

Attribute Name KVP Exposure Exposure in As Image and Fluoroscopy Area Dose Product Relative X-ray Exposure Exposure Time in mS Tag 0018,0060 0018,1152 0018,1153 0018,115E 0018,1405 0018,8150 VR DS IS IS DS IS DS Value Presence of Value ANAP ANAP ANAP ANAP ANAP ANAP Source AUTO AUTO AUTO AUTO AUTO AUTO Comment
17-Jun-2011
Page 73 of 79
Entrance Dose Organ Dose Entrance Dose in mGy
0040,0302 0040,0316 0040,8302
US DS DS
ANAP ANAP ANAP
AUTO AUTO AUTO
Table 117: X-Ray Generation Module

Attribute Name Focal Spot(s) Anode Target Material Exposure Control Mode Exposure Time in mS Tag 0018,1190 0018,1191 0018,7060 0018,8150 VR DS CS CS DS Value Presence of Value ANAP ANAP ANAP ANAP Source AUTO AUTO AUTO AUTO Comment
Table 118: X-Ray Filtration Module

Attribute Name Filter Material Tag 0018,7050 VR CS Value Presence of Value ANAP Source AUTO Comment
Table 119: X-Ray Grid Module

Attribute Name Grid Tag 0018,1166 VR CS Value FOCUSED, NONE, PARALLEL, RECIPROCATING Presence of Value VNAP Source AUTO Comment For Magnification-Exposures the applied value is "NONE". For Non-Magnification-Exposures the applied values are "RECIPROCATING\PARALLEL\FOCUS ED
Table 120: Mammography Image Module

Attribute Name Image Type Tag 0008,0008 VR CS Value Value 1: ORIGINAL, STEREO_MINUS, STEREO_PLUS, Value 2: PRIMARY, Value 3: POSTBIOPSY, STEREO_MINUS/STER EO_PLUS, STEREO_SCOUT MAMMOGRAPHIC Presence of Value ALWAYS Source AUTO Comment
Positioner Type Positioner Primary Angle Image Laterality Breast Implant Present Partial View Organ Exposed View Code Sequence >View Modifier Code Sequence >>Code Value >>Coding Scheme Designator >>Code Meaning >Code Value >Coding Scheme Designator >Code Meaning Anatomic Region Sequence
0018,1508 0018,1510 0020,0062 0028,1300 0028,1350 0040,0318 0054,0220 0054,0222 0008,0100 0008,0102 0008,0104 0008,0100 0008,0102 0008,0104 0008,2218
CS DS CS CS CS CS SQ SQ SH SH LO SH SH LO SQ
ALWAYS ANAPCV ALWAYS ANAPCV ANAPCV
AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO
BREAST
ALWAYS ALWAYS VNAP ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS
17-Jun-2011
Page 74 of 79
>Anatomic Region Modifier Sequence >>Code Value >>Coding Scheme Designator >>Code Meaning >Code Value >Coding Scheme Designator >Code Meaning
0008,2220 0008,0100 0008,0102 0008,0104 0008,0100 0008,0102 0008,0104
SQ SH SH LO SH SH LO
ANAP ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS
AUTO AUTO AUTO AUTO AUTO AUTO AUTO

Attribute Name Overlay Rows Overlay Columns Overlay Description Overlay Type Overlay Origin Overlay Bits Allocated Overlay Bit Position Overlay Label Overlay Data Tag 6000,0010 6000,0011 6000,0022 6000,0040 6000,0050 6000,0100 6000,0102 6000,1500 6000,3000 VR US US LO CS SS US US LO O W/ OB Value Presence of Value ALWAYS ALWAYS ANAPCV ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS ALWAYS Source AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO, USER AUTO Up to 10 overlays may be included in Stereo Images Up to 10 overlays may be included in Stereo Images Comment Up to 10 overlays may be included in Stereo Images Up to 10 overlays may be included in Stereo Images May stay empty

Attribute Name Specific Character Set SOP Class UID SOP Instance UID Tag 0008,0005 0008,0016 0008,0018 VR CS UI UI Value ISO_IR 100 1.2.820.10008.5.1.4.1.1. 1.2.1 Presence of Value ANAP ALWAYS ALWAYS Source Comment
8.1.2.
Usage of Attributes from Received IOD
The MammoDiagnost DR 2.0 has only an export side. The modality cannot read/view images from CD or by import.
8.1.3.
Attribute Mapping
Table 123: Attribute mapping during Modality Workflow
Name WLM tag 0008,0050 0008,0090 0008,1110 MPPS Create tag (0040,0270) >0008,0050 0008,0060 (0040,0270) >0008,1110 0008,1070 MPPSSet tag Image IOD tag 0008,0050 0008,0060 0008,0090 0008,1070 0008,1110
Accession Number Modality Referring Physician's Name Operators' Name Referenced Study Sequence
17-Jun-2011
Page 75 of 79
Name Referenced Image Sequence>Referenced SOP Class UID SOP Class UID Referenced Image Sequence> Referenced SOP Instance UID SOP Instance UID Patient's Name Patient ID Issuer of Patient ID Patient's Birth Date Patient's Sex Other Patient IDs Medical Alerts Contrast Allergies Ethnic group Additional Patient History Pregnancy Status Patient Comments Protocol Name Study Instance UID Series Instance UID Study ID Request Service Requested Procedure Description Requested Procedure Code Sequence Performed Procedure Code Sequence Special Needs Patient State Scheduled Procedure Step Description Performed Procedure Step Description Scheduled Protocol Code Sequence Scheduled Protocol Code Sequence Scheduled Procedure Step ID Performed Procedure Step Start Date Performed Procedure Step Start Time Performed Procedure Step ID Requested Procedure ID
2 2 1
WLM tag -
MPPS Create tag
MPPSSet tag (0040,0340) (>0008,1140) >>0008,1150 (0040,0340) (>0008,1140) >>0008,1155 (0040,0340) >0018,1030 0020,000E 0032,1032 -
Image IOD tag 0008,0016
0008,0018
0010,0010 0010,0020 0010,0021 0010,0030 0010,0040 0010,1000 0010,2000 0010,2110 0010,2160 0010,21B0 0010,21C0 0010,4000 0020,000D 0032,1033 0032,1060 0032,1064 0038,0050 0038,0500 (0040,0100) >0040,0007 (0040,0100) >0040,0008 (0040,0100) >0040,0009 0040,1001
0010,0010 0010,0020 0010,0021 0010,0030 0010,0040 0010,1000 (0040,0270) >0020,000D 0020,0010 (0040,0270) >0032,1060 0032,1032 (0040,0270) >0040,0007 0040,254 (0040,0270) >0040,0008 0040,0260 (0040,0270) >0040,0009 0040,0244 0040,0245 0040,0253 (0040,0270) >0040,1001
0010,0010 0010,0020 0010,0021 0010,0030 0010,0040 0010,1000 0010,2000 0010,2110 0010,2160 0010,21B0 0010,21C0 0010,4000 0018,1030 0020,000D 0020,000E 0020,0010 0032,1033 0032,1032 0038,0050 0038,0500 (0040,0275) >0040,0007 0040,254 (0040,0275) >0040,0008
0040,0260 -
0040,0260 (0040,0270) >0040,0009 0040,0244 0040,0245 0040,0253 (0040,0275) >0040,1001
Note1: If procedure is performed as requested. Note 2: If protocol is performed as scheduled.
8.1.4.
Coerced/Modified fields
Not applicable.
17-Jun-2011
Page 76 of 79
8.2. Data Dictionary of Private Attributes

Not applicable.
8.3. Coded Terminology and Templates

Not applicable.
8.3.1.
Context Groups
Not applicable.
8.3.2.
Template Specifications
Not applicable.
8.3.3.
Private code definitions
Not applicable.
8.4. Grayscale Image consistency

The monitor of MammoDiagnost DR 2.0 system can be calibrated according Grayscale Display Function Standard. The pixel values exported and printed must be interpreted as P-Value. If the export destination or the printer does not support GSDF, MammoDiagnost DR 2.0 provides calibration and takes into account ambient luminance and light box luminance.
8.5. Standard Extended/Specialized/Private SOPs

Not applicable. Table 124: List of created SOP Classes
SOP Class Name Computed Radiography Image Storage SOP Class Digital Mammography X-Ray Image Storage - Pres. SOP Digital Mammography X-Ray Image Storage - Proc. SOP 1.2.840.10008.5.1.4.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 SOP Class UID
8.5.1.
8.5.1.1.
Standard Extended/Specialized/Private SOP Instance

Computed Radiography Image Storage SOP Class
Table 125: Extended DICOM and private attributes for Computed Radiography Image Storage SOP Class Instances
Attribute Name Medical Alerts Allergies Pregnancy Status Image and Fluoroscopy Area Dose Product Tag 0010,2000 0010,2110 0010,21C0 (0018,115E) VR LO LO US DS 0001, 0002, 0003, 0004 Value Presence of Value VNAP VNAP VNAP VNAP Source MWL, USER AUTO MWL, USER AUTO Comment
17-Jun-2011
Page 77 of 79
Grid
(0018,1166)
CS
FOCUSED, RECIPROCATING, PARALLEL, NONE
VNAP
AUTO
For Magnification-Exposures the applied value is "NONE". For Non-Magnification-Exposures the applied values are "RECIPROCATING\PARALLEL\FOCUS ED.
Filter Material Frame of Reference UID Pixel Spacing Requesting Physician Requesting Service
0018,7050 0020,0052 0028,0030 0032,1032 0032,1033
CS UI DS PN LO
VNAP VNAP ANAP VNAP VNAP
AUTO AUTO AUTO MWL, USER AUTO, MWL, USER MWL, USER MWL, USER MWL, USER MWL MWL MWL AUTO, MPPS AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO MWL, USER
Requested Procedure Description Special Needs Patient State Performed Station AE Title Performed Procedure Step End Date Performed Procedure Step End Time Performed Procedure Step Status Total Number of Exposures Exposure Dose Sequence Organ Exposed Film Consumption Sequence Requested Procedure ID Reason for the Requested Procedure Requested Procedure Priority Patient Transport Arrangements Names of Intended Recipients of Results Reason for the Imaging Service Request (retired) Issue Date of Imaging Service Request Imaging Service Request Comments
0032,1060 0038,0050 0038,0500 0040,0241 0040,0250 0040,0251 0040,0252
LO LO LO AE DA TM CS COMPLETED, DISCONTINUED, IN PROGRESS
VNAP VNAP VNAP VNAP VNAP VNAP VNAP
0040,0301 0040,030E 0040,0318 0040,0321 0040,1001 0040,1002 0040,1003 0040,1004 0040,1010 0040,2001 0040,2004 0040,2400
US SQ CS SQ SH LO SH LO PN LO DA LT
ALWAYS VNAP ALWAYS VNAP VNAP VNAP VNAP VNAP VNAP VNAP VNAP VNAP
8.5.1.2.
Digital Mammography X-Ray Image Storage - Pres. SOP
Table 126: Extended DICOM and private attributes for Digital Mammography X-Ray Image Storage - Pres. SOP Instances
Attribute Name Medical Alerts Allergies Tag 0010,2000 0010,2110 VR LO LO Value Presence of Value VNAP VNAP Source MWL, USER MWL, USER Comment
17-Jun-2011
Page 78 of 79
Pregnancy Status Pixel Spacing Requesting Physician Requesting Service
0010,21C0 0028,0030 0032,1032 0032,1033
US DS PN LO
VNAP ANAP VNAP VNAP
MWL, USER AUTO MWL, USER AUTO, MWL, USER MWL, USER MWL, USER MWL, USER AUTO, MPPS AUTO, MPPS AUTO, MPPS AUTO, MPPS AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO
Requested Procedure Description Special Needs Patient State Performed Station AE Title Performed Procedure Step End Date Performed Procedure Step End Time Performed Procedure Step Status Total Number of Exposures Exposure Dose Sequence >Radiation Mode Film Consumption Sequence Requested Procedure ID Reason for the Requested Procedure Requested Procedure Priority Patient Transport Arrangements Names of Intended Recipients of Results Requested Procedure Comments Reason for the Imaging Service Request (retired) Issue Date of Imaging Service Request Imaging Service Request Comments
0032,1060 0038,0050 0038,0500 0040,0241 0040,0250 0040,0251 0040,0252
0040,0301 0040,030E 0018,115A 0040,0321 0040,1001 0040,1002 0040,1003 0040,1004 0040,1010 0040,1400 0040,2001 0040,2004 0040,2400
US SQ CS SQ SH LO SH LO PN LT LO DA LT
ALWAYS VNAP ALWAYS VNAP VNAP VNAP VNAP VNAP VNAP ANAP VNAP VNAP VNAP
8.5.1.3.
Digital Mammography X-Ray Image Storage - Proc. SOP
Table 127: Extended DICOM and private attributes for Digital Mammography X-Ray Image Storage - Proc. SOP Instances
Attribute Name Medical Alerts Allergies Pregnancy Status Tag 0010,2000 0010,2110 0010,21C0 VR LO LO US Value Presence of Value VNAP VNAP VNAP Source MWL, USER MWL, USER MWL, USER Comment
17-Jun-2011
Page 79 of 79
Pixel Spacing Requesting Physician Requesting Service
0028,0030 0032,1032 0032,1033
DS PN LO
ANAP VNAP VNAP
AUTO MWL, USER AUTO, MWL, USER MWL, USER MWL, USER MWL, USER AUTO, MPPS AUTO, MPPS AUTO, MPPS AUTO, MPPS AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO AUTO
Requested Procedure Description Special Needs Patient State Performed Station AE Title Performed Procedure Step End Date Performed Procedure Step End Time Performed Procedure Step Status Total Number of Exposures Exposure Dose Sequence >Radiation Mode Film Consumption Sequence Requested Procedure ID Reason for the Requested Procedure Requested Procedure Priority Patient Transport Arrangements Names of Intended Recipients of Results Requested Procedure Comments Reason for the Imaging Service Request (retired) Issue Date of Imaging Service Request Imaging Service Request Comments
0032,1060 0038,0050 0038,0500 0040,0241 0040,0250 0040,0251 0040,0252
0040,0301 0040,030E 0018,115A 0040,0321 0040,1001 0040,1002 0040,1003 0040,1004 0040,1010 0040,1400 0040,2001 0040,2004 0040,2400
US SQ CS SQ SH LO SH LO PN LT LO DA LT
ALWAYS VNAP ALWAYS VNAP VNAP VNAP VNAP VNAP VNAP ANAP VNAP VNAP VNAP
8.6. Private Transfer Syntaxes

Not applicable.
17-Jun-2011

DICOMConformance Statement Mammo Diagnost DR

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

DICOMConformance Statement Mammo Diagnost DR

Uploaded by

Copyright:

Available Formats

DICOM Conformance Statement

Koninklijke Philips Electronics N.V. 2011 All rights are reserved.

DICOM Conformance Statement: MammoDiagnost DR 2.0

1. DICOM Conformance Statement Overview

Koninklijke Philips Electronics N.V.

DICOM Conformance Statement: MammoDiagnost DR 2.0

Table 1: Network Services

Koninklijke Philips Electronics N.V.

DICOM Conformance Statement: MammoDiagnost DR 2.0

Koninklijke Philips Electronics N.V.

DICOM Conformance Statement: MammoDiagnost DR 2.0

Koninklijke Philips Electronics N.V.

DICOM Conformance Statement: MammoDiagnost DR 2.0

3.1. Revision History

Koninklijke Philips Electronics N.V.

DICOM Conformance Statement: MammoDiagnost DR 2.0

3.4. Definitions, Terms and Abbreviations

Koninklijke Philips Electronics N.V.

DICOM Conformance Statement: MammoDiagnost DR 2.0

4.1. Implementation model

Application Data Flow

Koninklijke Philips Electronics N.V.

DICOM Conformance Statement: MammoDiagnost DR 2.0

Figure 2: Application Data Flow Diagram

Koninklijke Philips Electronics N.V.

DICOM Conformance Statement: MammoDiagnost DR 2.0

Functional Definition of AEs

Koninklijke Philips Electronics N.V.

DICOM Conformance Statement: MammoDiagnost DR 2.0

Sequencing of Real World Activities

Figure 3: Sequence of an examination

Koninklijke Philips Electronics N.V.

DICOM Conformance Statement: MammoDiagnost DR 2.0

Koninklijke Philips Electronics N.V.

DICOM Conformance Statement: MammoDiagnost DR 2.0

Table 8: Number of associations as an Association Acceptor for this AE

Implementation Identifying Information

Communication Failure Handling

Association Initiation Policy

Koninklijke Philips Electronics N.V.

DICOM Conformance Statement: MammoDiagnost DR 2.0

2 - DICOM UL serviceprovider (ACSE related function)

3 - DICOM UL serviceprovider(Presentation related function)

2 - DICOM UL serviceprovider (ACSE related function)

3 - DICOM UL serviceprovider (Presentation related function)

Koninklijke Philips Electronics N.V.

DICOM Conformance Statement: MammoDiagnost DR 2.0

Table 13: Association Abort Handling

4 - unrecognized-PDUparameter 5 - unexpected-PDUparameter 6 - invalid-PDUparameter-value

(Real-World) Activity Verification as SCU Description and Sequencing of Activities

The presentation contexts are defined in the next table.

Koninklijke Philips Electronics N.V.

DICOM Conformance Statement: MammoDiagnost DR 2.0

SOP Specific Conformance for Verification SOP Class

(Real-World) Activity Modality worklist as SCU Description and Sequencing of Activities

Koninklijke Philips Electronics N.V.

DICOM Conformance Statement: MammoDiagnost DR 2.0

Koninklijke Philips Electronics N.V.

DICOM Conformance Statement: MammoDiagnost DR 2.0

Other Patient IDs Patient ID Patient's Name

0010,1000 0010,0020 0010,0010

Patient Identification Module X X X X X X X Single Value,Universal Single Value,Universal, WildCard

Koninklijke Philips Electronics N.V.