innova single plane cardiovascular imaging system …/media/documents/us-global/products/... ·...

GE Healthcare

Innova Single Plane CardiovascularImaging SystemConformance Statement for DICOM V3.0

OPERATING DOCUMENTATION

5191829-1-800Revision 1

Innova Single Plane Cardiovascular Imaging System Conformance Statement for DICOM V3.0

GE Healthcare Direction 5191829-1-800, Revision 1

2



Important InformationLANGUAGE

Important Information 3



4 Important Information



This page left intentionally blank.




Revision History

Part / Rev Date Reason for change Pages

5191829-1-800 March 18, 2008 Initial release of direction5191829-1-800

102

Revision History 13




14 Revision History



Table of Contents

CHAPTER 1 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

1.2 Overall Dicom Conformance Statement Document Structure . . . . . . . . . . . . 21

1.3 Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

1.4 Scope and Field Application . . . . . . . . . . . . . . . . . . . . . . . . . . 23

1.5 Important Remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

1.6 References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

1.7 Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

1.8 Symbols and Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . 25

CHAPTER 2 NETWORK CONFORMANCE STATEMENT . . . . . . . . . . . . . . . . . . 27

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

2 Implementation Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

2.1 Application Data Flow Diagram . . . . . . . . . . . . . . . . . . . . . . . . . 28

2.2 Functional Definition of AE’s . . . . . . . . . . . . . . . . . . . . . . . . . . 29

2.3 Sequencing of Real–World Activities . . . . . . . . . . . . . . . . . . . . . . 30

3 AE Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

3.1 Association Establishment Policies . . . . . . . . . . . . . . . . . . . . . . . 31

3.1.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

3.1.2 Number of Associations . . . . . . . . . . . . . . . . . . . . . . . . . 32

3.1.3 Asynchronous Nature . . . . . . . . . . . . . . . . . . . . . . . . . . 32

3.1.4 Implementation Identifying Information for Innova 2100-IQ, 3100/3100-IQ,4100/4100-IQ systems . . . . . . . . . . . . . . . . . . . . . . . 32

3.2 Association Initiation Policy . . . . . . . . . . . . . . . . . . . . . . . . . . 32

3.2.1 Real–World Activity Copy Images . . . . . . . . . . . . . . . . . . . . . 32

3.2.1.1 Associated Real–World Activity . . . . . . . . . . . . . . . . . . . 32

3.2.1.2 Proposed Presentation Context Table . . . . . . . . . . . . . . . . . 33

3.2.2 Real–World Activity Verification Acknowledge . . . . . . . . . . . . . . . . 34



3.2.3 Real–World Activity Get Worklist . . . . . . . . . . . . . . . . . . . . . 34

Table of Contents 15





3.2.4 Real–World Activity Request Storage Commitment . . . . . . . . . . . . . 35



3.2.4.3 SOP Specific DICOM Conformance Statement for the StorageCommitment Push Model SOP Class SCU . . . . . . . . . . . . . 36

3.3 Association Acceptance Policy . . . . . . . . . . . . . . . . . . . . . . . . . 37

3.3.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

3.3.2 Real–World Activity Verification Acknowledge . . . . . . . . . . . . . . . . 37


3.3.2.2 Accepted Presentation Context Table . . . . . . . . . . . . . . . . . 37

3.3.2.3 Real–World Activity Request Storage Commitment . . . . . . . . . . . 38

4 Communication Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

4.1 Supported Communication Stacks (PS 3.8, PS 3.9) . . . . . . . . . . . . . . . . 40

4.2 OSI Stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

4.3 TCP/IP Stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

4.3.1 API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

4.3.2 Physical Media Support . . . . . . . . . . . . . . . . . . . . . . . . . 40

4.4 Point–to–Point Stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

5 Extensions / Specializations / Privatizations . . . . . . . . . . . . . . . . . . . . . . 41

6 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

6.1 AE Title/Presentation Address Mapping . . . . . . . . . . . . . . . . . . . . . 42

6.2 Configurable Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

7 Support of Extented Character Sets . . . . . . . . . . . . . . . . . . . . . . . . . 43

CHAPTER 3 X-RAY ANGIOGRAPHY (XA) INFORMATION OBJECT IMPLEMENTATION . . . 45

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

2 XA Entity Relationship Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

2.1 Entity Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

2.2 Innova Mapping of DICOM Entities . . . . . . . . . . . . . . . . . . . . . . . 47

3 IOD Module Table and Information Module Definitions . . . . . . . . . . . . . . . . . 48

3.1 IOD Module Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

3.2 Information Module Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 49

16 Table of Contents



3.2.1 Common Study Entity Modules . . . . . . . . . . . . . . . . . . . . . . 49

3.2.1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

3.2.1.2 Patient Module . . . . . . . . . . . . . . . . . . . . . . . . . . . 49


3.2.2.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

3.2.2.2 General Study Module . . . . . . . . . . . . . . . . . . . . . . . 50

3.2.2.3 Patient Study Module . . . . . . . . . . . . . . . . . . . . . . . . 50

3.2.2.4 Dose Study Module . . . . . . . . . . . . . . . . . . . . . . . . . 50

3.2.3 Common Series Entity Modules . . . . . . . . . . . . . . . . . . . . . . 51

3.2.3.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

3.2.3.2 General Series Module . . . . . . . . . . . . . . . . . . . . . . . 51

3.2.4 Common Equipment Entity Modules . . . . . . . . . . . . . . . . . . . . 51

3.2.4.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

3.2.4.2 General Equipment Module . . . . . . . . . . . . . . . . . . . . . 52

3.2.5 Common Image Entity Modules . . . . . . . . . . . . . . . . . . . . . . 52

3.2.5.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

3.2.5.2 General Image Module . . . . . . . . . . . . . . . . . . . . . . . 52

3.2.5.3 Image Pixel Module . . . . . . . . . . . . . . . . . . . . . . . . . 53

3.2.5.4 Contrast/Bolus Module . . . . . . . . . . . . . . . . . . . . . . . 53

3.2.5.5 Cine Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

3.2.5.6 Multi–Frame Module . . . . . . . . . . . . . . . . . . . . . . . . 54

3.2.5.7 Frame Pointers Module . . . . . . . . . . . . . . . . . . . . . . . 54

3.2.5.8 Mask Module . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

3.2.5.9 Display Shutter Module . . . . . . . . . . . . . . . . . . . . . . . 55

3.2.5.10 Device Module . . . . . . . . . . . . . . . . . . . . . . . . . . 55

3.2.5.11 Therapy Module . . . . . . . . . . . . . . . . . . . . . . . . . . 55

3.2.5.12 Common Overlay Modules . . . . . . . . . . . . . . . . . . . . . 55

3.2.5.13 Curve Module . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

3.2.5.14 Common Lookup Table Modules . . . . . . . . . . . . . . . . . . 56

3.2.5.15 SOP Common Module . . . . . . . . . . . . . . . . . . . . . . . 56

3.2.5.16 X–Ray Modules . . . . . . . . . . . . . . . . . . . . . . . . . . 57

3.2.5.17 Private General Frame Module . . . . . . . . . . . . . . . . . . . 63

4 Private Data Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65




CHAPTER 4 SC INFORMATION OBJECT IMPLEMENTATION . . . . . . . . . . . . . . . 71

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

2 SC Entity Relationship Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72



3 IOD Module Table and Information Module Definitions . . . . . . . . . . . . . . . . . 74

3.1 IOD Module Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

3.2 Information Module Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 74

3.2.1 Common Patient Entity Modules . . . . . . . . . . . . . . . . . . . . . . 74

3.2.1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

3.2.1.2 Patient Module . . . . . . . . . . . . . . . . . . . . . . . . . . . 75


3.2.2.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

3.2.2.2 General Study Module . . . . . . . . . . . . . . . . . . . . . . . 75

3.2.2.3 Patient Study Module . . . . . . . . . . . . . . . . . . . . . . . . 76

3.2.2.4 Dose Study Module . . . . . . . . . . . . . . . . . . . . . . . . . 76

3.2.3 Common Series Entity Modules . . . . . . . . . . . . . . . . . . . . . . 76

3.2.3.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

3.2.3.2 General Series Module . . . . . . . . . . . . . . . . . . . . . . . 76

3.2.4 Common Equipment Entity Modules . . . . . . . . . . . . . . . . . . . . 77

3.2.4.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

3.2.4.2 General Equipment Module . . . . . . . . . . . . . . . . . . . . . 77

3.2.5 Common Image Entity Modules . . . . . . . . . . . . . . . . . . . . . . 78

3.2.5.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

3.2.5.2 General Image Module . . . . . . . . . . . . . . . . . . . . . . . 78

3.2.5.3 Image Pixel Module . . . . . . . . . . . . . . . . . . . . . . . . . 79

3.2.5.4 Overlay Plane Module . . . . . . . . . . . . . . . . . . . . . . . . 80

3.2.5.5 Common Lookup Table Modules . . . . . . . . . . . . . . . . . . . 80


3.2.5.7 SC Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

3.2.5.8 XA Positioner Module . . . . . . . . . . . . . . . . . . . . . . . . 81

3.2.5.9 Photo QCA Module . . . . . . . . . . . . . . . . . . . . . . . . . 81

3.2.5.10 Photo QVA Module Attributes . . . . . . . . . . . . . . . . . . . . 83




4 Private Data Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

CHAPTER 5 MODALITY WORKLIST INFORMATION MODEL DEFINITION . . . . . . . . . 89

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

2 Modality Worklist Information Model Entity Relationship Model . . . . . . . . . . . . . 90



3 Information Model Module Table . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

4 Information Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

4.1 Information Model Module Table . . . . . . . . . . . . . . . . . . . . . . . . 93

4.2 Information Model Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

4.2.1 Supported Matching . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

4.2.2 Scheduled Procedure Step Entity . . . . . . . . . . . . . . . . . . . . . 94

4.2.2.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94


4.2.2.3 Scheduled Procedure Step Module . . . . . . . . . . . . . . . . . . 94

4.2.3 Requested Procedure Entity . . . . . . . . . . . . . . . . . . . . . . . 95

4.2.3.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

4.2.3.2 Requested Procedure Module . . . . . . . . . . . . . . . . . . . . 95

4.2.4 Imaging Service Request Entity . . . . . . . . . . . . . . . . . . . . . . 95

4.2.4.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

4.2.4.2 Imaging Service Request Module . . . . . . . . . . . . . . . . . . . 96

4.2.5 Visit Entity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

4.2.5.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

4.2.5.2 Visit Identification Module . . . . . . . . . . . . . . . . . . . . . . 96

4.2.5.3 Visit Status Module . . . . . . . . . . . . . . . . . . . . . . . . . 96

4.2.5.4 Visit Relationship Module . . . . . . . . . . . . . . . . . . . . . . 96

4.2.5.5 Visit Admission Module . . . . . . . . . . . . . . . . . . . . . . . 96

4.2.6 Patient Entity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

4.2.6.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

4.2.6.2 Patient Relationship Module . . . . . . . . . . . . . . . . . . . . . 96

4.2.6.3 Patient Identification Module . . . . . . . . . . . . . . . . . . . . . 97

4.2.6.4 Patient Demographic Module . . . . . . . . . . . . . . . . . . . . 97

4.2.6.5 Patient Medical Module . . . . . . . . . . . . . . . . . . . . . . . 97




CHAPTER 6 STORAGE COMMITMENT PUSH MODEL IMPLEMENTATION . . . . . . . . . 99

1 Storage commitment push model information object definition . . . . . . . . . . . . . . 99

1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

1.2 Storage Commitment Module for N-Action . . . . . . . . . . . . . . . . . . . . 99

1.3 Storage Commitment Module for N-Event-Report . . . . . . . . . . . . . . . . . 99




Chapter 1 Introduction1 Introduction

1.1 Overview

This DICOM Conformance Statement is divided into Sections as described below:

• Chapter 1 (Introduction), which describes the overall structure, intent, and referencesfor this Conformance Statement

• Chapter 2 (Network Conformance Statement), which specifies the GEMS equipmentcompliance to the DICOM requirements for the implementation of Networking features.

• Chapter 3 (X–Ray Angiography Information Object Implementation), which specifiesthe GEMS equipment compliance to DICOM requirements for the implementation of aX–Ray Angiography Information Object.

• Chapter 4 (Secondary capture Information Object Implementation), which specifiesthe GEMS equipment compliance to DICOM requirements for the implementation of aSecondary capture Information Object.

• Chapter 5 (Modality Worklist Information Model), which specifies the GEMSequipment compliance to DICOM requirements for the implementation of the ModalityWorklist service.

• Chapter 6 (Storage Commitment Information Model Implementation), which specifiesthe GEMS equipment compliance to DICOM requirements for the implementationof the Storage Commitment service.

1.2 Overall Dicom Conformance Statement Document Structure

The Documentation Structure of the GEMS Conformance Statements and their relationshipwith the DICOM v3.0 Conformance Statements is shown in the Illustration below.

Chapter 1 Introduction 21



Illustration 1-1: ID/Net v3.0

This document specifies the DICOM v3.0 implementation. It is entitled:

1. INNOVA 2100-IQ, 3100/3100-IQ, 4100/4100-IQ

2. Conformance Statement for DICOM v3.0

3. Direction 5191829–100

This DICOM Conformance Statement documents the DICOM v3.0 Conformance Statementand Technical Specification required to interoperate with the GEMS network interface.

22 1 Introduction



Introductory information, which is applicable to all GEMS Conformance Statements, isdescribed in the document:

1. Introduction to the Integrated DICOM/Network v3.0 (ID/Net v3.0)

2. Conformance Statement

3. Direction: 2118780.

This Introduction familiarizes the reader with DICOM terminology and general concepts. Itshould be read prior to reading the individual products’ GEMS Conformance Statements.

The GEMS Conformance Statement, contained in this document, also specifies the LowerLayer communications which it supports (e.g., TCP/IP). However, the Technical Specificationsare defined in the DICOM v3.0 Part 8 standard.

For more information including Network Architecture and basic DICOM concepts, pleaserefer to the Introduction.

For more information regarding DICOM, copies of the Standard may be obtained on theInternet at http://medical.nema.org. Comments on the standard may be addressed to:

DICOM Secretariat, NEMA, Suite 1847, Rosslyn, VA 22209USA Phone: +1.703.841.3200

1.3 Intended Audience

The reader of this document is concerned with software design and/or system integrationissues. It is assumed that the reader of this document is familiar with the DICOM v3.0Standards and with the terminology and concepts which are used in those Standards.

If readers are unfamiliar with DICOM v3.0 terminology they should first refer to the documentlisted below, then read the DICOM v3.0 Standard itself, prior to reading this DICOMConformance Statement document.

1. Introduction to the Integrated DICOM/Network v3.0 (ID/Net v3.0)

2. Conformance Statement

3. Direction: 2118780

1.4 Scope and Field Application

It is the intent of this document, in conjunction with the Introduction to the IntegratedDICOM/Network v3.0 (ID/Net v3.0) Conformance Statement, Direction: 2118780, to providean unambiguous specification for GEMS implementations. This specification, called aConformance Statement, includes a DICOM v3.0 Conformance Statement and is necessaryto ensure proper processing and interpretation of GEMS medical data exchanged usingDICOM v3.0. The GEMS Conformance Statements are available to the public.

The reader of this DICOM Conformance Statement should be aware that different GEMSdevices are capable of using different Information Object Definitions. For example, a GEMSCT Scanner may send images using the CT Information Object, MR Information Object,Secondary Capture Object, etc.

Included in this DICOM Conformance Statement are the Module Definitions which defineall data elements used by this GEMS implementation. If the user encounters unspecified




private data elements while parsing a GEMS Data Set, the user is well advised to ignorethose data elements (per the DICOM v3.0 standard). Unspecified private data elementinformation is subject to change without notice. If, however, the device is acting as a ”fullfidelity storage device”, it should retain and re–transmit all of the private data elementswhich are sent by GEMS devices.

1.5 Important Remarks

The use of these DICOM Conformance Statements, in conjunction with the DICOM v3.0Standards, is intended to facilitate communication with GE imaging equipment. However, byitself, it is not sufficient to ensure that inter–operation will be successful. The user (or user’sagent) needs to proceed with caution and address at least four issues:

• Integration – The integration of any device into an overall system of interconnecteddevices goes beyond the scope of standards (DICOM v3.0), and of this introductionand associated DICOM Conformance Statements when interoperability with non–GEequipment is desired. The responsibility to analyze the applications requirements andto design a solution that integrates GE imaging equipment with non–GE systemsis the user’s responsibility and should not be underestimated. The user is stronglyadvised to ensure that such an integration analysis is correctly performed.

• Validation – Testing the complete range of possible interactions between any GEdevice and non–GE devices, before the connection is declared operational, shouldnot be overlooked. Therefore, the user should ensure that any non–GE provideraccepts full responsibility for all validation required for their connection with GEdevices. This includes the accuracy of the image data once it has crossed theinterface between the GE imaging equipment and the non–GE device and the stabilityof the image data for the intended applications. Such a validation is required beforeany clinical use (diagnosis and/or treatment) is performed. It applies when imagesacquired on GE imaging equipment are processed/displayed on a non–GE device,as well as when images acquired on non–GE equipment is processed/displayed ona GE console or workstation.

• Future Evolution – GE understands that the DICOM Standard will evolve to meetthe user’s growing requirements. GE is actively involved in the development of theDICOM v3.0 Standard. DICOM v3.0 will incorporate new features and technologiesand GE may follow the evolution of the Standard. The GEMS protocol is based onDICOM v3.0 as specified in each DICOM Conformance Statement. Evolution of theStandard may require changes to devices which have implemented DICOM v3.0.In addition, GE reserves the right to discontinue or make changes to the support ofcommunications features (on its products) reflected on by these DICOM ConformanceStatements. The user should ensure that any non–GE provider, which connects withGE devices, also plans for the future evolution of the DICOM Standard. Failure to doso will likely result in the loss of function and/or connectivity as the DICOM Standardchanges and GE Products are enhanced to support these changes.

• Interaction – It is the sole responsibility of the non–GE provider to ensure thatcommunication with the interfaced equipment does not cause degradation of GEimaging equipment performance and/or function.

1.6 References

A list of references which is applicable to all GEMS Conformance Statements is includedin the Introduction to the Integrated DICOM/Network v3.0 (ID/Net v3.0) ConformanceStatement, Direction: 2118780.

24 1 Introduction



The information object implementation refers to DICOM PS 3.3 (Information Object Definition).

1.7 Definitions

A set of definitions which is applicable to all GEMS Conformance Statements is includedin the Introduction to the Integrated DICOM/Network v3.0 (ID/Net v3.0) ConformanceStatement, Direction: 2118780.

1.8 Symbols and Abbreviations

A list of symbols and abbreviations which is applicable to all GEMS Conformance Statementsis included in the Introduction to the Integrated DICOM/Network v3.0 (ID/Net v3.0)Conformance Statement, Direction: 2118780.





26 1 Introduction



Chapter 2 Network Conformance Statement1 Introduction

This section of the DICOM Conformance Statement specifies the compliance to DICOMconformance requirements for the relevant Networking features on GE INNOVA product.Note that the format of this section strictly follows the format defined in DICOM Standard PS3.2 (Conformance). Please refer to that part of the standard while reading this section.

The INNOVA System provides sophisticated image processing and storage functions.INNOVA System will provide support for DICOM 3.0 to achieve interoperability acrossequipment produced by different vendors.

This section details the roles and the DICOM Service Classes the INNOVA System supports.

The INNOVA System DICOM implementation allows:

• The user to copy INNOVA images acquired through the system to a remote DICOMApplication Entity, using the Standard Storage DICOM Service as a Service ClassUser

• The user to request storage commitment for INNOVA images that were previouslysent trough the system to a remote DICOM application entity, using the StorageCommitment Service as a Service Class User

• The user to check the application level communication from the INNOVA DICOMServer to a remote DICOM Application Entity. To this aim the INNOVA System usesthe Verification DICOM Service Class as a Service Class User

• The user to get from the Radiology Information System (RIS) the list of procedure tobe performed. This is done using the Basic Worklist Management DICOM Service asa Service Class User.

• A remote Application Entity to check the application level communication with theINNOVA System. This is done by providing the Verification DICOM Service Classas a Service Class Provider.

The details of the DICOM conformance related to other Information Objects and InformationModels supported by this product are included in subsequent sections of this DICOMConformance Statement.

Chapter 2 Network Conformance Statement 27



2 Implementation Module

2.1 Application Data Flow Diagram

All DICOM functionality on the INNOVA product is provided by the DL DICOM Server AE.

The Basic and Specific Application models for this device are shown in the followingIllustration :

Illustration 2-1:

The INNOVA DICOM Application Entity is an application which handles DICOM protocolcommunication. INNOVA DICOM AE is automatically brought up when the INNOVA system ispowered on.

All remote DICOM AE must be manually configured on the INNOVA, usually at the softwareinstallation time, by a GE Field Engineer.

There are four local Real World activities: Copy Images, Request Storage Commitment fora set of images, Get Worklist and Verification which can cause the INNOVA DICOM AEto initiate a DICOM association.

28 2 Implementation Module



Copy Image consists of an operator selecting one or several images through the UserInterface known as ”Browser” and ”Viewer”. Selection of Remote System and visualizationof the transfer status is done in a specific screen. The remote system can be any DICOMstorage SCP supporting XA modality.

Request storage commitment consists of an automatic request performed by the systemafter each successful image transfer to request Transfer of Ownership for the Images thathave been transferred earlier by the Copy Image real world activity. The remote system canbe a DICOM Storage Commitment SCP.

Get Worklist activity consists of an operator request for the transfer of a list of procedureto be performed on the INNOVA acquisition system from a remote HIS/RIS system. TheRemote system can be any DICOM modality worklist SCP.

Query keys can be entered for the following items:

• Patient Name• Patient ID• Accession number• Procedure ID

The system can be configured to query for its own modality (XA) or AE Title.

A date or a date range for the query can also be specified.

Verification consists of an operator request for the verification of the availability of a remotestation.

2.2 Functional Definition of AE’s

The INNOVA DICOM Application Entity supports the following three SCU functions

1. Copy images:• Access to patient demographics and pixel Data in the local database• Build a DICOM Dataset• Initiate a DICOM Association to send the image(s).

2. Request Storage Commitment:• Initiate a DICOM Association in order to request Storage Commitment for the

sent image(s).• Send the N–ACTION request• Wait for the N–ACTION–RSP response• Wait for a configurable delay the N–EVENT–REPORT request• Send the N–EVENT–REPORT response• Close the association.• Optionally the system will accept a configurable number of DICOM associations

from the Storage Commitment SCP to receive storage commitment responses.

3. Get worklist:• Build a DICOM formatted basic worklist management data request




• Initiate a DICOM Association to send the request• Wait for worklist response(s)• Access to the local database to add new patient / exam demographic data• Close the association

4. Verification:• Initiate a DICOM Association• Send the C–ECHO request• Wait for the C–ECHO response• Close the Association

The INNOVA DICOM Application Entity also serves a default SCP function, the VerificationService Class, independently from others SCU functions.

2.3 Sequencing of Real–World Activities

Not Applicable.

30 2 Implementation Module



3 AE Specifications

Innova Dicom AE Specification:

This Application Entity provides Standard Conformance to the following DICOM V3.0 SOPClasses as an SCU:

SOP Class Name SOP Class UID

Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7

X–Ray Angiographic Image Storage 1.2.840.10008.5.1.4.1.1.12.1

Modality Worklist Information Model – FIND 1.2.840.10008.5.1.4.31

Verification SOP Class 1.2.840.10008.1.1

Storage Commitment Push Model 1.2.840.10008.1.20.1

This Application Entity provides Standard Conformance to the following DICOM V3.0 SOPClasses as an SCP :

SOP Class Name SOP Class UID

Verification SOP Class 1.2.840.10008.1.1

3.1 Association Establishment Policies

3.1.1 General

The DICOM Application Context Name (ACN), which is always proposed, is:

Application Context Name 1.2.840.10008.3.1.1.1

The Maximum Length PDU negotiation is included in all association establishment requests.

The maximum length PDU for an association initiated by the INNOVA DICOM ApplicationEntity is:

Maximum Length PDU 1024 Kbytes

The SOP Class Extended Negotiation is not supported.

The maximum number of Presentation Context Items that will be proposed is 5

The user information Items sent by this product are :

• Maximum PDU Length• Implementation UID• Implementation Version Name




3.1.2 Number of Associations

The INNOVA DICOM AE will support a configurable number of simultaneous associationsinitiated by remote nodes with the Storage Commitment Push Model presentation context.

3.1.3 Asynchronous Nature

Asynchronous mode is not supported. All operations will be performed synchronously.

3.1.4 Implementation Identifying Information for Innova 2100-IQ, 3100/3100-IQ,4100/4100-IQ systems

(For systems without Tilt table) The Implementation UID for this DICOM v3.0Implementation is:

INNOVA DL Implementation UID 1.2.840.113619.6.199

(For systems with Tilt table) The Implementation UID for this DICOM v3.0 Implementationis:

INNOVA DL Implementation UID 1.2.840.113619.6.220

The Implementation Version Name for this DICOM v3.0 Implementation is:

INNOVA DL Implementation Version Name INNOVA_2100_3100_4100

3.2 Association Initiation Policy

3.2.1 Real–World Activity Copy Images

3.2.1.1 Associated Real–World Activity

The operator must select a destination in the User Interface towards which the imageswill be transferred.

Then one of the two following scenarios is possible:

1. The operator selects data to be sent to the destination though the User Interface.Once these selections are done, the user clicks on the “Network” button to initiatea “Copy images” operation. The INNOVA DICOM AE will then initiate a DICOMassociation with the selected destination and transfer the selected images on thisassociation.

2. If system is configured for autoarchive, the INNOVA DICOM AE will automaticallyinitiate a DICOM association with the selected destination to transfer any new imagecreated on the system.

32 3 AE Specifications



3.2.1.2 Proposed Presentation Context Table

Presentation Context Table – Proposed

Abstract Syntax Transfer Syntax

Name UID Name List UID List

Role ExtendedNegotiation

Secondary CaptureImage Storage

1.2.840.10008.5.1.4.1.1.7 Implicit VR LittleEndian

1.2.840.10008.1.2 SCU None

Secondary CaptureImage Storage

1.2.840.10008.5.1.4.1.1.7 Explicit VR LittleEndian

1.2.840.10008.1.2.1 SCU None

X–Ray AngiographicImage Storage

1.2.840.10008.5.1.4.1.1.12.1 Implicit VR LittleEndian

1.2.840.10008.1.2 SCU None

X–Ray AngiographicImage Storage

1.2.840.10008.5.1.4.1.1.12.1 Explicit VR LittleEndian

1.2.840.10008.1.2.1 SCU None

SOP Specific DICOM Conformance Statement for all Storage SOP Classes:

This implementation can perform multiple C–STORE operation over a single association.

Upon receiving a C–STORE confirmation containing a Successful status, this implementationwill perform the next C–STORE operation. The association will be maintained if possible.

Upon receiving a C–STORE confirmation containing a Refused status, this implementationwill terminate the association. No new assocation will be opened to send remaining images.

Upon receiving a C–STORE confirmation containing a status other than Successful orRefused, this implementation will consider the current request to be a failure but will continueto attempt to send any remaining images in the request over a different association.

Establishing an association supports an “Association Timer”. This timer starts when theassociation request is sent and stops when the Association response is received. The timeout value is 10 seconds.

If the above time outs expires, the association is closed and the operation in progress isconsidered to be failed.

Following are the status codes that are more specifically processed when receivingmessages from a Storage SCP equipment:

Service Status Status Codes Further Meaning Application Behavior Whenreceiving Status Codes

Related Fields Processed ifreceived

A7xx Out of resources “Send” operation failed. Root causeindicated in error log.

(0000,0902)Refused

0122 SOP Class notSupported

“Send” operation failed. Root causeindicated in error log.

(0000,0902)

Cxxx Cannot Understand “Send” operation failed (0000,0901) (0000,0902)Error

A9xx Data Set does notmatch SOP Class

“Send” operation failed (0000,0901) (0000,0902)





Related Fields Processed ifreceived

B000 Coercion of DataElements

“Send” operation successful None

B007 Data Set does notmatch SOP Class

“Send” operation successful None

Warning

B006 Elements Discarded “Send” operation successful None

Success 0000 Success “Send” operation successful None

3.2.2 Real–World Activity Verification Acknowledge


The operator must select a destination in the User Interface and press the “Verification”button. These operations will cause:

• the INNOVA DICOM Application Entity to initiate a DICOM association• the INNOVA DICOM Application Entity to emit a C–ECHO command to check if the

remote AE is available




Name UID Name List UID ListRole

ExtendedNegotiation

Verification 1.2.840.10008.1.1 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None

SOP Specific DICOM Conformance Statement for Verification SOP Class:

The INNOVA DICOM AE provides standard conformance to the DICOM Verification SOPclass.

3.2.3 Real–World Activity Get Worklist


The worklist transfer can be initiated either automatically when the DL application starts,or manually by either clicking the “Refresh” button in the Patient Browser interface or the“Refresh now” button in the “Define Worklist Settings” screen.

These operation will cause:

• the INNOVA Application Entity to initiate a DICOM association• the INNOVA DL application to build the C–FIND request• the INNOVA Application Entity to emit the C–FIND request• the INNOVA Application Entity to receive the C–FIND Reponse(s)• the INNOVA Application Entity to close the association• the possibility for the user to add a new item to the local database




While the query is in progress, it is possible to cancel it by pressing a button on the patientbrowser. This will cause a C–FIND cancel to be sent.





ExtendedNegotiation

Modality WorklistInformationModel – FIND

1.2.840.10008.5.1.4.31 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None

SOP Specific DICOM Conformance Statement for the Modality Worklist Information Model –FIND SOP Class:

Following are the status codes that are more specifically processed when receivingmessages from a Modality Worklist SCP equipment :


Related Fields Processedif received

A700 Out of resources A message is displayed; with text“Last query failed” (more detailedinformation is logged in the errorlog).

(0000,0902)Refused

0122 SOP Class not Supported A message is displayed; with text“Last query failed” (more detailedinformation is logged in the errorlog).

(0000,0902)

A900 Identifier does not match SOPclass

Class A message is displayed;with text “Last query failed” (moredetailed information is logged in theerror log).

(0000,0901) (0000,0902)Failed

Cxxx Unable to process A message is displayed; with text“Last query failed” (more detailedinformation is logged in the errorlog).

(0000,0901) (0000,0902)

Cancel FE00 Matching terminated due to cancel A message is displayed; with text“Canceled”

None

Success 0000 Matching is complete – No finalidentifier is supplied

Worklist matches are displayed. None

FF00 Matches are continuing – CurrentMatch is supplied and any OptionalKeys were supported in the samemanner as Required Keys.

None NonePending

FF01 Matches are continuing – Warningthat one or more Optional Keyswere not supported for existencefor this Identifier

None None

3.2.4 Real–World Activity Request Storage Commitment


The operator may configure the image storage destination host to have an associatedStorage Commitment SCP AE (this can be the same AE as the Storage SCP). If there is an




associated Storage Commitment SCP specified, after each successful image transfer thesystem will automatically.

1. Wait for a configurable delay time (this allows re–routing of images from Storage SCPto the Storage Commitment SCP, if needed),

2. Initiate a DICOM association to the Storage Commitment SCP to send the storagecommitment request.





ExtendedNegotiation

StorageCommitmentPush Model

1.2.840.10008.20.1 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None


1.2.840.10008.20.1 Explicit VR Little Endian 1.2.840.10008.1.2.1 SCU None

3.2.4.3 SOP Specific DICOM Conformance Statement for the Storage Commitment Push ModelSOP Class SCU

The Storage Commitment will be requested for all SOP Instances for which the imagetransfer was successful. Each request may include one or more SOP Instances, dependingon the number of images that were transferred.

The AE uses DICOM network storage services to transfer SOP Instances which are tobe committed.

It does not support the optional Storage Media File–Set ID and UID Attributes in the StorageCommitment N–ACTION for transfer of SOP Instances by media for Storage Commitment.

The AE may request Storage Commitment for Instances of any of the Composite SOPClasses it supports as an SCU (see Section 3.2.3.2 )

The Storage Commitment Information Object is described in Chapter 6, Section 1, Storagecommitment push model information object definition.

The AE will generate a new transaction UID at each new N–Action request. Any time afterthe N–Action request was sent, AE will accept storage commitment responses sent by theremote SCP for the SOP instances referenced in the request.

The association opened to send the storage commitment request will be kept open by theAE for a configurable delay. This enables the remote SCP to send the storage commitmentresponse on the same association as the request was received. The association is closedwhen this timeout expires and there is no active transaction performed by the system linkedto this association.

If an N–EVENT–REPORT request is received on this association, the AE will process it, andsend an N–EVENT–REPORT response on the same association. The association will not beclosed by the AE even if the N–EVENT–REPORT conveys failure. If the N–ACTION responseconveys failure status, the association is closed by the AE. If a Storage Commitment




N–EVENT–REPORT is received on the Association initiated by the Storage CommitmentSCP Application Entity, it will be processed as described for Association initiated by theStorage Commitment SCP (see Chapter 3.3.2.3). Following are the status codes that aremore specifically processed when receiving messages from a Storage Commitment SCP AE:

N-ACTION response Status Codes

Service Status Status Codes Further Meaning Application Behavior WhenReceiving Status Codes

Related Fields Processedif Received

Success 0000H successful request Waiting for storage commitmentresponse

None

Failed 0213H Resource limitation Automatic retry of storagecommitment request for aconfigurable number of timeswith a configurable delay betweenretries

None

Failed Other thanabove

Failure reason other than resourcelimitation

Display error status in networkqueue

None

3.3 Association Acceptance Policy

3.3.1 Introduction

The INNOVA DICOM AE places no limitation on who may connect to it.

Any remote AE can open an association to the INNOVA DICOM AE for the purpose ofapplication level communication verification.

3.3.2 Real–World Activity Verification Acknowledge


The INNOVA DICOM AE is always listening to associations. No operator action is required torespond to a Verification request from any DICOM node.

3.3.2.2 Accepted Presentation Context Table




ExtendedNegotiation

Verification SOPClass

1.2.840.10008.1.1

Implicit VR Little Endian

Explicit VR Little Endian

Explicit VR Big Endian

1.2.840.10008.1.2

1.2.840.10008.1.2.1

1.2.840.10008.1.2.1.2

SCP None

SOP Specific Conformance Statement for Verification SOP Class:

INNOVA DICOM Application provides standard conformance to the DICOM VerificationService Class




3.3.2.3 Real–World Activity Request Storage Commitment

Associated Real–World Activity

The AE will accept a configurable number of DICOM associations to receive the storagecommitment responses. The number of accepted associations can be configured from 1 to 5.

Accepted Presentation Context Table:




ExtendedNegotiation


1.2.840.10008.1.20.1 Implicit VR Little Endian 1.2.840.10008.1.2 SCU RoleSelectionNegotiation


1.2.840.10008.1.20.1 Explicit VR Little Endian 1.2.840.10008.1.2.1 SCU RoleSelectionNegotiation


1.2.840.10008.1.20.1 Implicit VR Big Endian 1.2.840.10008.1.2.2 SCU RoleSelectionNegotiation

SOP Specific DICOM Conformance Statement for the Storage Commitment Push ModelSOP Class SCU:

The Innova accept the SCU role (which must be proposed via SCP/SCU Role SelectionNegotiation) within a Presentation Context for the Storage Commitment Push Model SOPClass.

Upon receiving a Storage Commitment N–EVENT–REPORT (Storage Commitment Result),the Innova will mark all SOP Instances for which a success status is indicated with anArchived flag, shown on the user interface as “ARCHIVED”. When all Instances associatedwith a Study or a Patient are Archived, the Study or Patient will also be shown on the userinterface with status “ARCHIVED”. Only Patients, Studies or Instances marked “ARCHIVED”may be deleted by user action without double confirmation.

If the Storage Commitment Result indicates any failure status, an error message will bedisplayed to the user, and the error, including the Failure Reason (0008,1197) attribute values,will be written to the error log. Any retry will be manually reinitiated. On retry the AE willtransfer again the instances, and then initiate a new Storage Commitment Request for them(see Section 3.2.4 ). The AE will process each Failure Reason Code as described above.

FailureReason

Meaning Application Behavior When Receiving Reason Code

0110H Processing failure Display error in network queue

0112H No such object instance Display error in network queue

0213H Resource limitation Display error in network queue

0122H Referenced SOP Class not supported Display error in network queue

0119H Class/Instance conflict Display error in network queue

0131H Duplicate transaction UID Display error in network queue




The AE will return the standard status codes in N–EVENT–REPORT–RSP message asspecified in DICOM v3.0.




4 Communication Profiles

4.1 Supported Communication Stacks (PS 3.8, PS 3.9)

DICOM Upper Layer (PS 3.8) is supported using TCP/IP.

4.2 OSI Stack

OSI stack not supported

4.3 TCP/IP Stack

The TCP/IP stack is inherited from a Windows NT Operating System.

4.3.1 API

Not applicable to this product.

4.3.2 Physical Media Support

DICOM is indifferent to the Physical medium over which TCP/IP executes (e.g. EthernetV2.0,IEEE 802.3, ATM, FDDI)

NOTE: For more information about the Physical Media available on INNOVA System, please refer tothe Product Data Sheet.

4.4 Point–to–Point Stack

A 50–pin ACR–NEMA connection is not applicable to this product.

40 4 Communication Profiles



5 Extensions / Specializations / Privatizations

None




6 Configuration

GEMS Field Service Engineers configure the INNOVA System. The DICOM configurationitems below are configurable or re–configurable by a Field Service Engineer.

6.1 AE Title/Presentation Address Mapping

The INNOVA System DICOM SERVER AE allows for the configuration of the mapping ofremote AE titles to IP addresses and ports. The IP address of a remote AE may be in adifferent sub net (using routing). GEMS Field Service Engineers perform this configuration.

6.2 Configurable Parameters

The following fields are configurable for this AE (local):

• Local AE Title• Local IP Address• Local IP Netmask

NOTE: The local listening port number is not configurable for this product, and is equal to 4002.

The following fields are configurable for the DICOM AE used as worklist SCP:

• Remote AE Title• Remote IP Address• Listening TCP/IP Port Number

NOTE: A GE Field Engineer must perform all the above configurations.

The following fields are configurable for every remote DICOM AE used as storage SCP:

• Remote AE Title• Remote IP Address• Listening TCP/IP Port Number• Is archive or not• If archive:• Remote Storage Commitment SCP AE Title• Remote Storage Commitment SCP IP Address• Remote Storage Commitment SCP Listening TCP/IP Port Number• Array size of the pixel data to be transferred (512x512, or any size up to 1024x1024).

The following fields are configurable:

• Number of automatic retries and the delay between retries of storage commitmentrequests

• Maximum number of associations accepted for storage commitment responses• Delay between image transfer and storage commitment request• Delay of releasing the association after sending the storage commitment request

42 6 Configuration



7 Support of Extented Character Sets

The INNOVA System will support only the ISO_IR 100 (ISO 8859–1:1987 Latin alphabetN 1. supplementary set) as extended character sets. Any incoming worklist entry that isencoded using another extended character set will display as if it were IS0_IR 100, and anySOP Instances created for these entries will reference ISO_IR 100.





44 7 Support of Extented Character Sets



Chapter 3 X-Ray Angiography (XA) InformationObject Implementation1 Introduction

This section specifies the use of the DICOM XA Image IOD to represent the informationincluded in X–Ray Angiography images produced by this implementation. Correspondingattributes are conveyed using the module construct.

Chapter 3 X-Ray Angiography (XA) Information Object Implementation 45



2 XA Entity Relationship Model

The Entity–Relationship diagram for the XA Image interoperability schema is shown inillustration 1 . In this figure, the following diagrammatic convention is established to representthe information organization :

• each entity is represented by a rectangular box• each relationship is represented by a diamond shaped box.• the fact that a relationship exists between two entities is depicted by lines connecting

the corresponding entity boxes to the relationship boxes.

The relationships are fully defined with the maximum number of possible entities in therelationship shown. In other words, the relationship between Series and Image can have upto n Images per Series, between Patient and Study can have up to n Studies per Patient, butthe Study to Series has 1 Series for each Study.

Illustration 3-1: XA Image Entity Relationship Diagram

46 2 XA Entity Relationship Model



2.1 Entity Descriptions

Please refer to DICOM Standard Part 3 (Information Object Definitions) for a description ofeach of the entities contained within the XA Information Object.

2.2 Innova Mapping of DICOM Entities

Table 3-1: Mapping of DICOM Entities to Innova Entities

DICOM INNOVA Entity

Patient Patient

Study Exam

Series Exam

Image Sequence

Frame Not Applicable




3 IOD Module Table and Information Module Definitions

3.1 IOD Module Table

Within an entity of the DICOM v3.0 XA IOD, attributes are grouped into related setof attributes. A set of related attributes is termed a module. A module facilitates theunderstanding of the semantics concerning the attributes and how the attributes are relatedwith each other. A module grouping does not infer any encoding of information into datasets.

Table 3-2 identifies the defined modules within the entities which comprise the DICOM v3.0XA IOD. Modules are identified by Module Name.

See DICOM v3.0 Part 3 for a complete definition of the entities, modules, and attributes.

Table 3-2: XA Image IOD Modules

Entity Name Module Name Reference

Patient Patient Section 3.2.1.2

Study General Study Section 3.2.2.2

Patient Study Section 3.2.2.3

Dose Study Section 3.2.2.4

Series General Series Section 3.2.3.2

Equipment General Equipment Section 3.2.4.2

Image General Image Section 3.2.5.2

Image Pixel Section 3.2.5.3

Contrast/Bolus Section 3.2.5.4

Cine Section 3.2.5.5

Multi–frame Section 3.2.5.6

Frame Pointers Section 3.2.5.7

Mask Section 3.2.5.8

Display Shutter Section 3.2.5.9

Device Section 3.2.5.10

Therapy Section 3.2.5.11

X-Ray Image Table 3-20

X-Ray Acquisition Table 3-21

X-Ray Collimator Table 3-22

X-Ray Table Table 3-23

X-Ray 3D Acquisition Table 3-24

X-Ray 3D Calibration Table 3-25

X-Ray Filtration Table 3-26

XA Positioner Table 3-27

Overlay Plane Section 3.2.5.12

Multi–frame Overlay Section 3.2.5.12

Curve Section 3.2.5.13

48 3 IOD Module Table and Information Module Definitions



Table 3-2: XA Image IOD Modules (cont'd)Entity Name Module Name Reference

Modality LUT Section 3.2.5.14

VOI LUT Table 3-18

SOP Common Section 3.2.5.15

SUB LUT Table 3-28

Gereral Frame Section 3.2.5.17

3.2 Information Module Definitions

Please refer to DICOM v3.0 Standard Part 3 (Information Object Definitions) for a descriptionof each of the entities and modules contained within the XA Information Object.

The following modules are included to convey Enumerated Values, Defined Terms, andOptional Attributes supported. Type 1 & Type 2 Attributes are also included for completenessand to define what values they may take and where these values are obtained from. Itshould be noted that they are the same ones as defined in the DICOM v3.0 Standard Part 3(Information Object Definitions).

3.2.1 Common Study Entity Modules

3.2.1.1 Introduction

This section describes the modules of Common Patient Entity.

3.2.1.2 Patient Module

This section specifies the Attributes of the Patient that describe and identify the Patientwho is the subject of a diagnostic Study. This Module contains Attributes of the patientthat are needed for diagnostic interpretation of the Image and are common for all studiesperformed on the patient.

Table 3-3: Patient Module Attributes

Attribute Name Tag Type Attribute Description

Patient’s Name (0010,0010) 2 From user interface or worklist. When from userinterface, value contains only last_name(restricted to32 chars)^first_name(restricted to 31 chars). Whenfrom worklist, equals first component group.

Patient ID (0010,0020) 2 From worklist or user interface. Restricted to 64 chars.

Patient’s Birth Date (0010,0030) 2 From user interface or worklist. Restricted to 8 chars.YYYYMMDD.

Patient’s Sex (0010,0040) 2 From user interface or worklist. ”M”, ”F” or ”O”.


The following Study IE Modules are common to all Composite Image IODs which referencethe Study IE. These Module contain Attributes of the patient and study that are neededfor diagnostic interpretation of the image.


This section describes the modules of Common Study Entity




3.2.2.2 General Study Module

This section specifies the Attributes which describe and identify the Study performed uponthe Patient.

Table 3-4: General Study Module Attributes


Study Instance UID (0020,000D) 1 Restricted to 64 characters, internally generated as follows:”registered prefix for GEMS” + ”.2. Registered prefix withinGEMS” + ”.a.b.c” encoded mac address of the DL host +”.x.y.z”unique id protected against reinstallation and reentrance.

Study Date (0008,0020) 2 YYYYMMDD, restricted to 8 characters.

Study Time (0008,0030) 2 HHMMSS.XXX, restricted to 10 characters.

Referring Physician’s Name (0008,0090) 2 From User Interface or worklist, restricted to 64 characters.

Study ID (0020,0010) 2 From User Interface or worklist, restricted to 64 characters.

Accession Number (0008,0050) 2 From User Interface or worklist, restricted to 64 characters.

Study Description (0008,1030) 3 From User Interface or worklist, restricted to 64 characters. (Maynot be sent).

Name of Physician(s) ReadingStudy

(0008,1060) 3 From User Interface, restricted to 64 characters. Value containsonly one component. (May not be sent).

study_number (0015,xx8F) 3 Internally generated, starting at 1. (May not be sent).

3.2.2.3 Patient Study Module

This section defines Attributes that provide information about the Patient at the time theStudy was performed.

Table 3-5: Patient Study Module Attributes


Patient’s Age (0010,1010) 3 Either from User Interface or Calculated from Patient’s Birth Date(0010,0030). Three digits followed by one letter: In Years (Y),Months (M), Weeks (W) or Days (D). (May not be sent).

Patient’s Size (0010,1020) 3 From User Interface or worklist, restricted to 16 characters. (Maynot be sent).

Patient’s Weight (0010,1030) 3 From User Interface or worklist, restricted to 16 characters. (Maynot be sent).

Admission ID (0038,0010) 3 Identification number of the visit as assigned by the healthcareprovider

3.2.2.4 Dose Study Module

This section defines Attributes that provide information about the Dose at the time the Studywas performed.

Table 3-6:


Study Dose (0015, xx80) 3 Total dose delivered to the patient during the study.




Table 3-6: (cont'd)Study total DAP (0015, xx81) 3 Cumulative dose area product for the study.

Study Fluoro dap (0015, xx82) 3 Cumulative dose area product for the fluoro acquisitionsperformed during the study.

Study fluoro time (0015, xx83) 3 Total time of fluoroscopy during the study.

Study record dap (0015, xx84) 3 Cumulative dose area product for the record acquisitionsperformed during the study.

Study record time (0015, xx85) 3 Total time of record acquisitions during the study.

3.2.3 Common Series Entity Modules

The following Series IE Modules are common to all Composite Image IODs which referencethe Series IE.


This section describes the modules of Common Series Entity.

3.2.3.2 General Series Module

This section specifies the Attributes which identify and describe general information aboutthe Series within a Study.

Table 3-7: General Series Module Attributes


Modality (0008,0060) 1 XA

Series Instance UID (0020,000E) 1 Restricted to 64 characters, internally generated as follows:”registered prefix for GEMS” + ”.2. Registered prefix within GEMS”+ ”.a.b.c” encoded mac address of the DL host +”.x.y.z” unique idprotected against reinstallation and reentrance.

Series Number (0020,0011) 2 Internally generated, starting at 1.

Series Date (0008,0021) 3 YYYYMMDD, restricted to 8 characters.

Series Time (0008,0031) 3 HHMMSS.XXX, restricted to 10 characters.

Performing Physicians’Name

(0008,1050) 3 From User Interface, restricted to 64 characters. (May not be sent).

Protocol Name (0018,1030) 3 From User Interface, user defined description of the acquisitionprotocol.

Series Description (0008,103E) 3 From User Interface, restricted to 64 characters. (May not be sent).

Operators’ Name (0008,1070) 3 From User Interface, restricted to 64 characters. (May not be sent).

Request attribute sequence (0040,0275) 3 Sequence that contains attributes from the Imaging Service Request.In this implementation, this sequence contains only two items.

>Request procedure id (0040,1001) 1C Identifier that identifies the Requested Procedure in the ImagingService Request. Required if Sequence Item is present.

>Scheduled Procedure StepID

(0040,0009) 1C Field always contains the value "Unknown" in the image header.

3.2.4 Common Equipment Entity Modules

The following Equipment IE Module is common to all Composite Image IODs which referencethe Equipment IE.





This section describes the modules of Common Equipment Entity.

3.2.4.2 General Equipment Module

This section specifies the attributes which identify and describe the piece of equipmentwhich produced a series of images.

Table 3-8: General Equipment Module Attributes


Manufacturer (0008,0070) 2 GE MEDICAL SYSTEMS

Institution Name (0008,0080) 3 From ”Service User Interface”, configured at the installationof the system. Restricted to 64 characters.

Institution Address (0008,0081) 3 From ”Service User Interface”, configured at the installationof the system. Restricted to 1024 characters.

Station name (0008,1010) 3 AE Title of the system that created the DICOM image.

Manufacturer’s Model Name (0008,1090) 3 DL

Device Serial Number (0018,1000) 3 From internal configuration of the machine.

Software Versions (0018,1020) 3 DL application version.

3.2.5 Common Image Entity Modules

The following Image IE Modules are common to all Composite Image IODs which referencethe Image IE.


This section describes the modules of Common Image Entity.

3.2.5.2 General Image Module

This section specifies the Attributes which identify and describe an image within a particularseries.

Table 3-9: General Image Module Attributes


Image Type (0008,0008) Always ORIGINAL/PRIMARY/SINGLE PLANE

Acquisition Date (0008,0022) 3 YYYYMMDD, restricted to 8 characters, date the sequencewas acquired.

Image Date (0008,0023) 2C Same as acquisition date (0008,0022)

Acquisition Time (0008,0032) 3 HHMMSS.XXX, restricted to 10 characters.

Image Time (0008,0033) 2C Same as acquisition time (0008,0032)

Image number (0020,0013) 2 Internally generated, starting at 1.

Patient Orientation (0020,0020) 2C Patient direction of the rows and columns of the image.Required if image does not require Image Orientation(0020,0037) and Image Position (0020,0032). This attributecontains the values corresponding to the first frame




Table 3-9: General Image Module Attributes (cont'd)Attribute Name Tag Type Attribute Description

Instance Comments (0020,4000) 3 From User Interface, restricted to 64 characters. (May notbe sent).

patient position per image (0019,xxC7) 3 Patient position descriptor relative to the equipment :

• head first-prone = HFP

• head first supine = HFS

• head first decubitus right = HFDR

• head first decubitus left = HFDL

• feet first decubitus right = FFDR

• feet first decubitus left = FFDL

• Feet First-Prone = FFP

• Feet First-Supine = FFS

3.2.5.3 Image Pixel Module

This section specifies the Attributes that describe the pixel data of the image.

Table 3-10: Image Pixel Module Attributes


Samples per Pixel (0028,0002) 1 1

Photometric Interpretation (0028,0004) 1 MONOCHROME1 or MONOCHROME2

Rows (0028,0010) 1 Depends on the size of the FOV (imaged region of theX–ray detector), and the re– sampling applied during theDICOM conversion. Possible values are 608, 750, 800,1000 and 512.

Columns (0028,0011) 1 Depends on the size of the FOV (imaged region of theX–ray detector), and the re– sampling applied during theDICOM conversion. Possible values are 608, 750, 800,1000 and 512.

Bits Allocated (0028,0100) 1 8 or 16

Bits Stored (0028,0101) 1 8 or 12

High Bit (0028,0102) 1 7 or 11

Pixel Representation (0028,0103) 1 0x0000

Pixel Data (7FE0,0010) 1 Data stream of the pixel samples.

3.2.5.4 Contrast/Bolus Module

This section specifies the Attributes that describe the contrast/bolus used in the acquisitionof the Image.

Table 3-11: Contrast/Bolus Module Attributes


Auto injection enabled (0019,xxA4) 3 YES/NO

Injection phase (0019,xxA5) 3 PRE/POST




Table 3-11: Contrast/Bolus Module Attributes (cont'd)Attribute Name Tag Type Attribute Description

Injection delay (0019,xxA6) 3 Number of milliseconds between the injection and thereference frame. Always positive.

Reference injection framenumber

(0019,xxA7) 3 Frame number of the reference frame related to theauto–injection delay.

Contrast/Bolus Agent (0018,0010) 2 No value, zero length.

3.2.5.5 Cine Module

The table in this section specifies the Attributes of a Multi–frame Cine Image.

Table 3-12: Cine Module Attributes


Start Trim (0008,2142) 3 1

Stop Trim (0008,2143) 3 Last frame of the multi–frame image.

Recommended Display FrameRate

(0008,2144) 3 Number of frames per second (truncated to integer).

Cine Rate (0018,0040) 3 Number of frames per second (truncated to integer).

Frame Time (0018,1063) 1C Nominal time (in msec) between frames.

Frame Delay (0018,1066) 3 0.0

Frame time vector (0018,1065) 1C An array which contains the real time increments (in msec)between frames for a Multi-frame image. Required if FrameIncrement Pointer (0028,0009) points to Frame Time Vector.

Recommended display framerate float

(0019,xxB8) 3 Recommended rate (float) at which the frames of aMulti-frame image should be displayed in frames/second

3.2.5.6 Multi–Frame Module

This section specifies the Attributes of a Multi–frame pixel data Image.

Table 3-13: Multi–Frame Module Attributes


Number of Frames (0028,0008) 1 Internally generated by acquisition system. Maximum: 460.

Frame Increment Pointer (0028,0009) 1 Frame Increment Pointer (0028,0009) points to Frame Time(0018,1063) or Frame Time Vector (0018, 1065)

3.2.5.7 Frame Pointers Module

This section specifies the attributes of a Frame Pointer Module.

Table 3-14: Frame Pointers Module Attributes


Representative Frame Number (0028,6010) 3 Calculated as ”number of frames (0028,0008)” divided by 2.




3.2.5.8 Mask Module

Table 3-15: Mask Module Attributes


Recommended viewing mode (0028,1090) 2 SUB or NAT

Mask substraction sequence (0028,6100) 1 Defines a sequence which describe mask subtractionoperations for a Multi–frame Image.

>Mask operation (0028,6101) 1 AVG_SUB or NONE

>Applicable frame range (0028,6102) 3 Frames of the mask operation applied during the lastreview.

>Mask frame numbers (0028,6110) 1C Frames selected as Mask during the last review. Requiredif Mask Operation (0028,6101) is AVG_SUB.

>Mask subpixel shift (0028,6114) 3 Pixel shift applied during the last review.

3.2.5.9 Display Shutter Module

Table 3-16: Display Shutter Module Attributes


Shutter Shape (0018,1600) 1 RECTANGULAR

Shutter Left Vertical Edge (0018,1602) 1C Internally generated by acquisition system.

Shutter Right Vertical Edge (0018,1604) 1C Internally generated by acquisition system.

Shutter Upper Horizontal Edge (0018,1606) 1C Internally generated by acquisition system.

Shutter Lower Horizontal Edge (0018,1608) 1C Internally generated by acquisition system.

3.2.5.10 Device Module

This module is not sent.

3.2.5.11 Therapy Module


3.2.5.12 Common Overlay Modules

• Overlay Plane ModuleThis module is not sent

• Multi–Frame Overlay ModuleThis module is not sent.




3.2.5.13 Curve Module

Table 3-17: Curve Module Attributes


LV Diastolic contour (0019,xx0D) 3 Diastolic contour image coordinates. Three or morepairs of values with the coordinates of the contour points[row and column - starting at 1,1] with respect to theorigin (upper-left corner) of the pixel data.

LV Systolic contour (0019,xx0D) 3 Systolic contour image coordinates. Three or more pairsof values with the coordinates of the contour points [rowand column - starting at 1,1] with respect to the origin(upper-left corner) of the pixel data.

3.2.5.14 Common Lookup Table Modules

VOI LUT module

This section specifies the Attributes that describe the VOI LUT.

Table 3-18: VOI LUT Module Attributes


Window center (0028,1050) 3 Value of the window center optimized at the imageacquisition.

Window width (0028,1051) 3 Value of the window width optimized at the imageacquisition.

default brightness contrast (0019,xx4E) 3 The brightness/contrast applied by IPOpt to the VOIduring the image acquisition

user brightness contrast (0019,xx4F) 3 The brightness/contrast modified by the user to the VOIduring the image review

Modality LUT Module


3.2.5.15 SOP Common Module

The SOP Common Module is mandatory for all DICOM IODs.

This section defines the Attributes which are required for proper functioning and identificationof the associated SOP Instances. They do not specify any semantics about the Real–WorldObject represented by the IOD.

Table 3-19: SOP Common Module Attributes


SOP Instance UID (0008,0018) 1 Restricted to 64 characters, internally generated asfollows: ”registered prefix for GEMS” + ”.2. Registeredprefix within GEMS” + ”.a.b.c” encoded mac addressof the DL host +”.x.y.z” unique id protected againstreinstallation and reentrance.

SOP Class UID (0008,0016) 1 1.2.840.10008.5.1.4.1.1.12.1

Specific Character Set (0008,0005) 1C ISO_IR 100




3.2.5.16 X–Ray Modules

This Section describes Modules used in one or more X–Ray IODs. These Modules containAttributes that are specific to X–Ray images.

X–Ray Image Module

Table 3-20: X–Ray Image Module Attributes


Pixel Intensity Relationship (0028,1040) 1 DRM or SQRT

Calibration image (0050,0004) 3 Indicates whether a reference object (phantom) ofknown size is present in the image and was used forcalibration. Defined terms are: YES and NO

Scan options (0018,0022) 3 Parameters of scanning sequence

X–Ray Acquisition Module

Table 3-21: X–Ray Acquisition Module Attributes


KVP (0018,0060) 2 No value, Zero length.

Radiation Setting (0018,1155) 1 GR

Exposure Time (0018,1150) 2C No value, Zero length.

X–Ray Tube Current (0018,1151) 2C No value, Zero length.

Exposure

(0018,1152) 2C

The product of exposure time and X-Ray tube currentexpressed in mAs. Required if either Exposure Time(0018,1150) or X-Ray tube current (0018,1151) are notpresent.

Radiation Mode (0018,115A) 3 PULSED

Intensifier Size (0018,1162) 3 204.8 for 20" detector, 307.2 for 30” detector and 409.6for 40” detector.

Field of View Shape (0018,1147) 3 RECTANGLE

Field of View Dimension(s)

(0018,1149) 3

From user selection in the User Interface of theacquisition system. Possible values are "400\400" OR"320\320" OR "300\300" OR "200\200" OR OR "172\172"OR "170\170" OR "160\160" OR "150\150" OR "147\147"OR "121\121" OR "120\120".

Image Pixel Spacing (0018,1164) 3 Is the ratio between the field of view dimension and thenumber of rows and columns.

Field of View Origin (0018,7030) 3Depends on the size of the FOV (imaged region of theX–ray detector).

FOV dimension double

(0019,xx0B) 3

Value in floating point resolution, whose truncature is(0018,1149). Possible values are "400.0\400.0" OR"320.0\320.0" OR "300.0\300.0" OR "200.0\200.0" OROR "172.8\172.8" OR "170.0\170.0" OR "160.0\160.0"OR "150.0\150.0" OR "147.2\147.2" OR "121.6\121.6"OR "120.0\120.0".

Detector rotation angle (0019,xx92) 3 Image rotation at the detector reading, before image flip.

Lambda cm pincushion distortion

(0019,xx24) 3

”0.0”. Coefficient of the pincushion distortion model ofthe Image Intensifier, in cm–1. This model allows tocorrect the position of a point of the image as function ofthe distance to the center of the image.




Table 3-21: X–Ray Acquisition Module Attributes (cont'd)Attribute Name Tag Type Attribute Description

Slope LV regression

(0019,xx25) 3

”0.85”. Slope coefficient (unitless) of the linearregression correction of the Left Ventricular volume. Thislinear regression corrects the Left Ventricular volumecalculated by the Dodge’s method from the contour ofthe left ventricle traced by an expert.

Intercept LV regression

(0019,xx26) 3

”4.72”. Intercept coefficient (in cm3) of the linearregression correction of the Left Ventricular volume. Thislinear regression corrects the Left Ventricular volumecalculated by the Dodge’s method from the contour ofthe left ventricle traced by an expert.

Average pulse width (0018,1154) 3 Average width of X-Ray pulse in msec.

adx acq mode

(0019,xx14) 3

This is a “numerical code” of the acquisition mode, andis used in AW to auto-start applications. Defined codesfor Innova are:

100: Fluoro Store

2: Cardiac NO Sub

32: Auto DSA

116: Bolus for Pasting (Angio Sub)

126: Chase

129: 3D Calibration

140: NoSub 3D

current spatial filter strength (0019,xxAB) 3The strength of the spatial filters selected by the user inDL during the image Review. Values from 1 to 9.

EPT (0019,xxA9) 3 Exposure optimization conditions (cm).

can downscan 512 (0019,xxAA) 3Indicates the possibility to downscan the pixel data to512x512 for exchange purposes (YES/NO).

sensor feedback (0019,xx9A) 3 Internally generated.

Image sweep(0019,xx95) 3

Horizontal and vertical image sweep performed by theacquisition system before sending the DICOM image.Defined terms are YES and NO.

Grid (0018,1166) 3Identify the grid. Defined Terms are IN (a grid ispositioned) and NONE (no grid is used).

Focal spot (0018, 1190) 3 Nominal focal spot size in mm used to acquire this image.

IP address (0019,xx20) 3 IP address of the machine that sends the serie.

Preselected pivot rotation speed (0019,xxC5) 3Speed of the pivot rotation, in degrees per second, asspecified by the operator before the acquisition.

Detection gain value (0019,xxD4) 3 Value in nGy/counts computed at start of acquisition.

mR mAs calibration value (0019,xxD5) 3 The value of the mR/mAs calibration.

DRM LUT file name (0019,xxDC) 3 Name of the file where the DRM lookup table can befound.

DRM Strength (0019,xxDD) 3 DRM Strength.

Acquisition Protocol User Name (0019,xxB3) 3Protocol name as it was entered by the user duringprotocol edit

Acquisition Region(0019,xxBA) 3

Coded String to determine whether the acquisition isCardiac or Angio. Defined terms are CARDIAC, ANGIOand UNKNOWN




Table 3-21: X–Ray Acquisition Module Attributes (cont'd)Attribute Name Tag Type Attribute Description

Acquisition SUB mode

(0019,xxBB) 3

Coded String to determine whether the acquisition modewas designed for a subtracted or non-subtracted review.Note that this indicates if one or more masks wereacquired, which is independent from the fact that theacquisition is reviewed in Sub or No-Sub

Acquisition Mode Description(0019,xxB1) 3

The precise description of the “numerical code” (Adx acqmode). May bel be used by the “one touch protocol”editor in AW.

Acquisition Mode Display Label (0019,xxB2) 3Label that shall be displayed on the AW browser, foreach sequence

kVp actual vector (0019,xxAF) 3Exposure conditions (kVp). This is a multi-valuedattribute that contains the kVp for each frame

mAs actual vector (0019,xxB0) 3 Exposure conditions (mAs). This is a multi-valuedattribute that contains the mAs for each frame

Pw actual vector (0019,xxC2) 3Exposure conditions (pw). This is a multi-valued attributethat contains the pw for each frame

Detector gain (0019,xx34) 3 Gain of detector.

X–Ray Collimator Module

Table 3-22: X–Ray Collimator Module Attributes


Collimator Shape (0018,1700) 1 RECTANGULAR

Collimator Left Vertical Edge (0018,1702) 1C Internally generated by the acquisition system.

Collimator Right Vertical Edge (0018,1704) 1C Internally generated by the acquisition system.

Collimator Upper Horizontal Edge (0018,1706) 1C Internally generated by the acquisition system.

Collimator Lower Horizontal Edge (0018,1708) 1C Internally generated by the acquisition system.

X–Ray Table Module

Table 3-23: X–Ray Table Module Attributes


Table Motion (0018,1134) 2 Will be DYNAMIC if table moves in at least onedirection.

Table Vertical Increment (0018,1135) 2C Value will be filled in if Table Motion is DYNAMIC.For STATIC, will be sent as no value, zero length.

Table Longitudinal Increment (0018,1137) 2C Value will be filled in if Table Motion is DYNAMIC.For STATIC, will be sent as no value, zero length.

Table Lateral Increment (0018,1136) 2C Value will be filled in if Table Motion is DYNAMIC.For STATIC, will be sent as no value, zero length.

Table vertical position (0019,xx21) 3 Absolute vertical position of the table with respectto the table referential. Down moving is positive.

Table longitudinal position (0019,xx22) 3 Absolute longitudinal position of the table withrespect to the table referential. Head moving ispositive.

Table lateral position (0019,xx23) 3 Absolute lateral position of the table with respectto the table referential. Left moving is positive.

Table head tilt angle(1) (0018,1138) 3 0.0




Table 3-23: X–Ray Table Module Attributes (cont'd)Attribute Name Tag Type Attribute Description

Table rotation status vector (0019,xxBD) 3 Status of the rotation of the table in the horizontalplane for each frame of the multi-frame image.Two values are defined: YES, NO.

Table cradle angle(1) (0019,xxBC) 3 Angle of the left-right axis of the table in degreesrelative to the horizontal plane. Positive valuesindicate that the left of the table is upwards

Table rotation angle(1) (0019,xxEA) 3 Status of the rotation of the table in the horizontalplane for each frame of the multi-frame image.Two values are defined: YES, NO

Table rotation angle increment(1) (0019,xxC3) 3 Rotation of the table in the horizontal plane(clockwise when looking from above the table)for each frame of the multi-frame image

Table X Position to Isocenter(1) (0019,xxEB) 3 X position of the Table Reference Point withrespect to the Isocenter (mm).

Table Y Position to Isocenter(1) (0019,xxEC) 3 Y position of the Table Reference Point withrespect to the Isocenter (mm).

Table Z Position to Isocenter(1) (0019,xxED) 3 Z position of the Table Reference Point withrespect to the Isocenter (mm).

Table X Position to isocenter increment(1) (0019,xxD7) 3 X position of the Table Reference Point withrespect to the Isocenter (mm).

Table Y Position to Isocenter increment(1) (0019,xxD8) 3 Y position of the Table Reference Point withrespect to the Isocenter (mm).

Table Z Position to Isocenter increment(1) (0019,xxD9 3 Z position of the Table Reference Point withrespect to the Isocenter (mm).

Table Head Tilt Angle increment(1) (0019,xxDA) 3 Angle of the head-feet axis of the table indegrees relative to the horizontal plane.

Table Cradle Tilt Angle increment(1) (0019,xxDB) 3 Angle of the left-right axis of the table in degreesrelative to the horizontal plane.

NOTE: (1) : applicable only for systems with Tilt table

X–Ray 3D Acquisition Module

Table 3-24: X-Ray 3D Acquisition Module Attributes


3D structure of interest (0019,xxC8) 3 Defined terms: VASCULAR, OTHER

3D calibration out of date flag (0019,xxC9) 3 Defined terms: YES, NO

3D spin expected number of frames (0019,xxCA) 3

X–Ray 3D Calibration Module

Table 3-25: X–Ray 3D Calibration Module Attributes


3Dcal image rows (0021,xx01) 3 Number of rows of the image of the calibrationphantom (helix) that has been used to determinethe projection matrices.

3Dcal image columns (0021,xx02) 3 Number of columns of the image of the calibrationphantom (helix) that has been used to determinethe projection matrices.




Table 3-25: X–Ray 3D Calibration Module Attributes (cont'd)Attribute Name Tag Type Attribute Description

3Dcal field of view (0021,xx03) 3 Field of View in mm applied to the acquisition ofthe calibration phantom (helix). NOTE: the sizeof the image of the calibration phantom may bebigger than the Field of View region.

3Dcal acquisition date (0021,xx04) 3 Date of the acquisition of the calibration phantom.

3Dcal acquisition time (0021,xx05) 3 Time of the acquisition of the calibrationphantom.

3Dcal calibration processing date (0021,xx06) 3 Date of the processing of the calibration that hasdetermined the projection matrices.

3Dcal calibration processing time (0021,xx07) 3 Time of the processing of the calibration that hasdetermined the projection matrices.

3Dcal L arm angle (0021,xx08) 3 Mechanical angle of the L-arm corresponding tothe first image of the acquisition of the calibrationphantom.

3Dcal Pivot angle vector (0021,xx09) 3 Vector of the mechanical angles of the Pivotcorresponding to all the images of the acquisitionof the calibration phantom. The number of valuesof this attribute must be equal to the attribute(0021,xx13) "3Dcal number of images".

3Dcal C arm angle (0021,xx0A) 3 Mechanical angle of the C-arm corresponding tothe first image of the acquisition of the calibrationphantom.

3Dcal matrix sequence (0021,xx0B) 3 Sequence containing the elements of thecalibration matrices. The number of items ofthis sequence must be equal to the attribute(0021,xx13) "3Dcal number of images".

>3Dcal matrix elements (0021,xx0C) 3 Elements of the projection matrices. Eachelement is a real number represented by amaximum of 5 digits in its integer part, then acomma, then 15 digits in its fractional part.

3Dcal algorithm version (0021,xx0D) 3 Version of the calibration algorithm.

3Dcal 3D frame unit size (0021,xx0E) 3 Size in mm of the unity used to describe the 3Dframe dimensions.

3Dcal calibration mode (0021,xx0F) 3 Internal code used to classify the different modesof calibration.

3Dcal image frame origin row (0021,xx10) 3 Vertical coordinate of the origin of the imageframe used for the calculation of the projectionmatrices, given as row of the calibration image(starts at 0).

3Dcal image frame origin column (0021,xx11) 3 Horizontal coordinate of the origin of the imageframe used for the calculation of the projectionmatrices, given as column of the calibrationimage (starts at 0).

3Dcal positioner pivot rotation speed (0021,xx12) 3 Speed of the pivot rotation, in degrees persecond, as specified by the operator before theacquisition of the calibration phantom.NOTE: This speed may be slightly

different from the actual speedof the gantry due to mechanicalconstraints like accelerate.

3Dcal number of images (0021,xx13) 3 Number of projections acquired during theacquisition of the calibration phantom.

3Dcal Instance UID (0021,xx14) 3 SOP Instance UID of the DICOM imagecorresponding to the acquisition of the calibrationphantom.




Table 3-25: X–Ray 3D Calibration Module Attributes (cont'd)Attribute Name Tag Type Attribute Description

3Dcal image pixel spacing (0021,xx15) 3 Distance between the center of each pixel ofthe image of the calibration phantom, specifiedby a pair -row spacing value (delimiter) columnspacing value in mm.

3Dcal centering mode (0021,xx16) 3 Type of algorithm that centers the projectionmatrices: defined values are: "ISOCENTER","HELIX", "RECTIFIED", "OTHER".

X–Ray Filtration Module

Table 3-26: X–Ray Filtration Module Attributes


Contour filter type (0018,1160) 3 Type of filter(s) inserted into the X-Ray beam(e.g. wedges). Defined Terms: STRIP WEDGEBUTTERFLY MULTIPLE NONE

XA Positioner Module

Table 3-27: XA Positioner Module Attributes


Distance Source to Detector (0018,1110) 3 Internally generated by the acquisition system.

Distance Source to Patient (0018,1111) 3 Internally generated by the acquisition system.

Estimated Radiographic MagnificationFactor

(0018,1114) 3 Calculated from (0018,1110) and (0018,1111)

Positioner Motion (0018,1500) 2C Will be DYNAMIC if Pivot or C_ARM moves. Ifno motion, or if L only moves, will be sent asSTATIC.

Positioner Primary Angle (0018,1510) 2 For multi–frame images, value of the first frame.

Positioner Secondary Angle (0018,1511) 2 For multi–frame images, value of the first frame.

Positioner Primary Angle Increment (0018,1520) 2C Value of the RAO/LAO increments relative to thefirst frame. If positioner motions is STATIC, willbe sent zero length.

Positioner Secondary Angle Increment (0018,1521) 2C Value of the CRA/CAU increments relative tothe first frame. If positioner motions is STATIC,will be sent zero length.

Angle value 1 (0019,xx01) 3 Positioner angle for L arm (in degrees). Leftmoving is positive.

Angle value 2 (0019,xx02) 3 Positioner angle for Pivot arm (in degrees). Leftmoving is positive.

Angle value 3 (0019,xx03) 3 Positioner angle for C arm (in degrees). Headmoving is positive.

Angle 1 increment (0019,xx97) 3 Incremental change in L arm with respect to theangle of the first frame. Present only if positionermotion is DYNAMIC.

Angle 2 increment (0019,xx98) 3 Incremental change in Pivot arm with respectto the angle of the first frame. Present only ifpositioner motion is DYNAMIC.




Table 3-27: XA Positioner Module Attributes (cont'd)Attribute Name Tag Type Attribute Description

Angle 3 increment (0019,xx99) 3 Incremental change in C arm with respect to theangle of the first frame. Present only if positionermotion is DYNAMIC.

SID vector (0019,xxBE) 3 Distance in mm from source to detector centerfor each frame of the multi-frame image.

SUB LUT Module

Table 3-28: SUB LUT Module Attributes


Applicable review mode (0019,xx9D) 3 Review mode in which the SUB LUT module isapplicable. Defined terms re NONE, NAT, SUBand BOTH

Log LUT control points (0019,xx9E) 3 Control points of the log LUT.

Exp LUT SUB control points (0019,xx9F) 3 Control points of the exp LUT for SUB review.

Exp LUT NOSUB control points (0019,xxAD) 3 Control points of the exp LUT for NOSUB review.

ABD value (0019,xxA0) 3 Average gray level value of the histogram.

Sub window center (0019,xxA1) 3 window center applicable when the SUB LUTmodule is applied.

Sub window width (0019,xxA2) 3 window width applicable when the SUB LUTmodule is applied.

SUB operator LUTs names (0019,xxAE) 3 Three LUT files’ name (2 ExpLUTs, 1 LogLUT)in the database for the Viewer to be able toconfigure the IP SUB operator with the LUTsused for acquisition. Names are given in followingorder : SUB exp LUT\NOSUB exp LUT\ log LUT

ABD Vector (0019,xxB9) 3 Average gray level value of the histogram.Multi-values that contains the value of eachsingle frame.

3.2.5.17 Private General Frame Module

Table 3-29: Private General Frame Module Attributes


frame_sequence (0025,xx0A) 3 Sequence with as many items as number of frames inthe image, containing data of related to the acquisition ofeach frame.

>frame_id (0025,xx02) 3 Frame identification inside the frame sequence, startingat 1.

Private Presentation Module

Table 3-30: Private Presentation Module Attributes


User zoom factor (0019,xx18) 3 Zoom factor (integer) applied by the user to the defaultimage displayed.




Table 3-30: Private Presentation Module Attributes (cont'd)Attribute Name Tag Type Attribute Description

X zoom (0019,xx19) 3 Row number of the origin of the zoomed area with respectto the origin of the FOV area (starting at 0).

Y zoom (0019,xx1A) 3 Column number of the origin of the zoomed area withrespect to the origin of the FOV area (starting at 0).

Private Spectral Filters Module

Table 3-31: Private Spectral Filters Module Attributes


Spectral filter thickness (0019,xxC4) 3C Thickness of the spectral filter applied to optimize the IQ(in µm).

Private Spatial Filters Module

Table 3-32: Private Spatial Filters Module Attributes


user spatial filter strength (0019,xx17) 3 The strength of the spatial filters selected by the userduring the image Review, which is equivalent to the DLXstrength. Values from 1 to 7.

Default spatial filter family (0019,xx31) 3 The family of the spatial filters applied during the imageacquisition.

Default spatial filter strength (0019,xx32) 3 The strength of the spatial filters applied during the imageacquisition. Values from 1 to 9.

Current spatial filter strength (0019,xxAB) 3 The strength of the spatial filters selected by the user inDL during the image Review. Values from 1 to 9.




4 Private Data Dictionary

Table 3-33: Private Creator Identification (GEMS_DL_STUDY_01)

Attribute Name Tag VR VM

Study dose (0015,xx80) DS 1

Study total dap (0015,xx81) DS 1

Study fluoro dap (0015,xx82) DS 1

Study fluoro time (0015,xx83) IS 1

Study record dap (0015,xx84) DS 1

Study record time (0015,xx85) IS 1

Study_number (0015,xx8F) IS 1

Table 3-34: Private Creator Identification (GEMS_DL_IMG_01)

Attribute Name Tag VR VM Description

patient position per image (0019,xxC7) CS 1

Patient position descriptor relative to the equipment.Required for CT and MR images; shall not be presentif Patient Orientation Code Sequence (0054,0410) ispresent; may be present otherwise.

Defined terms are:

• HFP = Head First-Prone

• head first supine = HFS

• head first decubitus right = HFDR

• head first decubitus left = HFDL

• feet first decubitus right = FFDR

• feet first decubitus left = FFDL

• Feet First-Prone = FFP

• Feet First-Supine = FFS

NOTE: It is assumed that the patient is layingon the table (i.e. recumbent), notstanding or semi-erect.

auto injection enabled (0019,xxA4)CS CS 1 YES/NO

injection phase (0019,xxA5) CS 1 PRE/POST

injection delay (0019,xxA6) DS 1 Number of milliseconds between the injection andthe reference frame. Always positive.

reference injection frame number (0019,xxA7) IS 1 Frame number of the reference frame related to theauto-injection delay.

recommended display frame rate float (0019,xxB8) FL 1 Recommended rate (float) at which the framesof a Multi-frame image should be displayed inframes/second.

calibration sw version (0019,xx8F) LO 1 String containing algorithm generation, algorithmversion and algorithm release. A new release doesnot change the algorithm, only change code structure(I/O, code optimization...)




Table 3-34: Private Creator Identification (GEMS_DL_IMG_01) (cont'd)Attribute Name Tag VR VM Description

fov dimension double (0019,xx0B) DS 1-2 Dimensions of the image Intensifier Field of View inmm (double resolution). If Rectangle, row dimensionfollowed by column. If Round, diameter

image detector rotation angle (0019,xx92) DS 1 Image rotation at the detector reading, before imageflip.

image flip (0019,xx95) CS 2 If the reading order of the pixels of the detector areequivalent to a horizontal flip, vertical flip or both (e.g.in order to correct for different patient positions), thevalue of "image sweep": (0019,XX95) shall containtwo defined terms, First value : YES if horizontalflip NO elseSecond value : YES if vertical flip NOelse.NOTE: this flip is performed before sending theDICOM image (usually on IDC)

sensor feedback (0019,xx9A) DS 1-N Internally calculated dose per frame

EPT (0019,xxA9) DS 1-N Exposure optimization conditions: equivalent patientthickness in cm. If it contains only one value, itcorresponds to the last frame of the multi-frameimage. If it contains more than one, it shall containas many values as frames in the image.

can downscan 512 (0019,xxAA) CS 1 Indicates the possibility to downscan the pixel data to512x512 for exchange purposes (YES/NO)

kVp actual vector (0019,xxAF) DS 1-N Exposure conditions (kVp). This is a multi-valuedattribute that contains the kVp for each frame

mAs actual vector (0019,xxB0) DS 1-N Exposure conditions (mAs). This is a multi-valuedattribute that contains the mAs for each frame

Acquisition Mode Description (0019,xxB1) LO 1 The precise description of the “numerical code” (Adxacq mode). May bel be used by the “one touchprotocol” editor in AW.

Acquisition Mode Display Label (0019,xxB2) LO 1 Label that shall be displayed on the AW browser, foreach sequence

Acquisition Protocol User Name (0019,xxB3) LO 1 Protocol name as it was entered by the user duringprotocol edit

Acquisition Region (0019,xxBA) CS 1 Coded String to determine whether the acquisitionis Cardiac or Angio. Defined terms are CARDIAC,ANGIO and UNKNOWN

Acquisition SUB mode (0019,xxBB) CS 1 Coded String to determine whether the acquisitionmode was designed for a subtracted ornon-subtracted review. Note that this indicates if oneor more masks were acquired, which is independentfrom the fact that the acquisition is reviewed in Subor No-Sub mode. Defined terms are SUB, NOSUBand UNKNOWN

pw actual vector (0019,xxC2) DS 1-N Exposure conditions (pw). This is a multi-valuedattribute that contains the pw for each frame

preselected pivot rotation speed (0019,xxC5) FL 1

detection gain value (0019,xxD4) FL 1 Value in nGy/counts computed at start of acquisitionby DIGABD

mR mAs calibration value (0019,xxD5) FL 1 The value of the mR/mAs calibration

DRM LUT file name (0019,xxDC) LO 1 Name fo the file where the DRM lookup table canbe found.

DRM Strength (0019,xxDD) DS 1-N DRM Strength

LV Diastolic contour (0019,xx0C) FL 2-2N Diastolic contour image coordinates. Three or morepairs of values with the coordinates of the contourpoints [row and column - starting at 1,1] with respectto the origin (upper-left corner) of the pixel data.

66 4 Private Data Dictionary




LV Systolic contour (0019,xx0D) FL 2-2N Systolic contour image coordinates. Three or morepairs of values with the coordinates of the contourpoints [row and column - starting at 1,1] with respectto the origin (upper-left corner) of the pixel data.

applicable review mode (0019,xx9D) CS 1 Review mode in which the SUB lut module isapplicable. Defined terms re NONE, NAT, SUB andBOTH

log lut control points (0019,xx9E) DS 1-N Control points of the log LUT

exp lut SUB control points (0019,xx9F) DS 1-N Control points of the exp LUT for SUB review

ABD value (0019,xxA0) DS 1 Average gray level value of the histogram

sub window center (0019,xxA1) DS 1 window center applicable when the SUB lut moduleis applied

sub window width (0019,xxA2) DS 1 window width applicable when the SUB lut moduleis applied

exp lut NOSUB control points (0019,xxAD) DS 1-N Control points of the exp LUT for NOSUB review

SUB operator LUTs names (0019,xxAE) LO 1-N Three LUT files’name (2 ExpLUTs, 1 LogLUT) in thedatabase for the Viewer to be able to configure theIP SUB operator with the LUTs used for acquisition.Names are given in following order : SUB expLUT\NOSUB exp LUT\ log LUT

ABD Vector (0019,xxB9) FL 1-N ABD for each frame. This vector contains thesame number of values as number of frames in themulti-frame image.

spectral filter thickness (0019,xxC4) IS 1 Thickness of the spectral filter applied to optimizethe IQ (in µm)

default spatial filter family (0019,xx31) IS 1 The family of the spatial filters applied during theimage acquisition

default spatial filter strength (0019,xx32) IS 1 The strength of the spatial filters applied during theimage acquisition. Values from 1 to 9.

current spatial filter strength (0019,xxAB) IS 1 The strength of the spatial filters selected by the userin DL during the image Review. Values from 1 to 9.

3D structure of interest (0019,xxC8) CS 1 Defined terms: VASCULAR, OTHER

3D calibration out of date flag (0019,xxC9) CS 1 Defined terms: YES, NO

3Dspin expected number of frames (0019,xxCA) IS 1

Table cradle angle(1) (0019,xxBC) FL 1 Angle of the left-right axis of the table in degreesrelative to the horizontal plane. Positive valuesindicate that the left of the table is upwards. Thevalue of this attribute applies to the first frame of theMulti-frame image.

Table rotation angle(1) (0019,xxEA) FL 1 Rotation angle in degrees of the table in thehorizontal plane (clockwise when looking from abovethe table). The value of this attribute applies to thefirst frame of the multi-frame image.

Table rotation status vector (0019,xxBD) CS 1-N Status of the rotation of the table in the horizontalplane (YES or NO). This is a multi-valued attributethat contains the Table Rotation Status for each frame

Table rotation angle increment(1) (0019,xxC3) FL 1-N Incremental change in the rotation of the table in thehorizontal plane (clockwise when looking from abovethe table) relative to the first frame of the Multi-frameimage. Contains as many values as number offrames. Required if Table Motion is DYNAMIC.





Table X Position to Isocenter(1) (0019,xxEB) FL 1 X position of the Table Reference Point with respectto the Isocenter (mm). Positive values are towardsthe LAO direction of the Isocenter. The value of thisattribute applies to the first frame of the Multi-frameimage.

Table Y Position to Isocenter(1) (0019,xxEC) FL 1 Y position of the Table Reference Point with respectto the Isocenter (mm). positive values are downwardsthe horizontal plane in the vertical direction. Thevalue of this attribute applies to the first frame of theMulti-frame image.

Table Z Position to Isocenter(1) (0019,xxED) FL 1 Z position of the Table Reference Point with respectto the Isocenter (mm). Positive values are towardsthe CRA direction of the Isocenter. The value of thisattribute applies to the first frame of the Multi-frameimage.

Table X Position to Isocenterincrement(1)

(0019,xxD7) FL 1-N Incremental change in X position of the TableReference Point with respect to the Isocenter (inmm), relative to the first frame of the Multi-frameimage. Positive values are towards the LAO directionof the Isocenter. Contains as many values as numberof frames. Required if Table Motion is DYNAMIC.

Table Y Position to Isocenterincrement(1)

(0019,xxD8) FL 1-N Incremental change in Y position of the TableReference Point with respect to the Isocenter (inmm), relative to the first frame of the Multi-frameimage. Positive values are downwards the horizontalplane in the vertical direction. Contains as manyvalues as number of frames. Required if Table Motionis DYNAMIC.

Table Z Position to Isocenterincrement(1)

(0019,xxD9) FL 1-N Incremental change in Z position of the TableReference Point with respect to the Isocenter (inmm), relative to the first frame of the Multi-frameimage. Positive values are towards the CRA directionof the Isocenter. Contains as many values as numberof frames. Required if Table Motion is DYNAMIC.

Table Head Tilt Angle increment(1) (0019,xxDA) FL 1-N Incremental change in the angle of the head-feet axisof the table in degrees with respect to the horizontalplane, relative to the first frame of the Multi-frameimage. Zero means when the head-feet axis is in thehorizontal plane. Positive values are when the headof the table is upwards the horizontal plane. Containsas many values as number of frames. Required ifTable Motion is DYNAMIC.

Table Cradle Tilt Angle increment(1) (0019,xxDB) FL 1-N Incremental change in the angle of the left-right axisof the table in degrees with respect to the horizontalplane, relative to the first frame of the Multi-frameimage. Zero means when the left-right axis is in thehorizontal plane. Positive values are when the left ofthe table is upwards the horizontal plane. Containsas many values as number of frames. Required ifTable Motion is DYNAMIC.

angle 1 increment (0019,xx97) DS 1-N Incremental change in angle_value_1, sent ifpositioner motion is dynamic.



SID vector (0019,xxBE) FL 1-N Distance in mm from source to detector center. Thisis a multi-valued attribute that contains the SID foreach frame





default brightness contrast (0019,xx4E) DS 2 The brightness/contrast applied by IPOpt to the VOIduring the image acquisition

user brightness contrast (0019,xx4F) DS 2 The brightness/contrast modified by the user to theVOI during the image review

NOTE: (1) : applicable only for systems with Tilt table

Table 3-35: Private Creator Identification (DLX_SERIE_01)


adx acq mode (0019,XX14) IS 1

ip address (0019,XX20) LO 1

Lambda cm pincushion distorsion (0019,XX24) DS 1

Slope LV regression (0019,XX25) DS 1

Intercept LV regression (0019,XX26) DS 1

Table vertical position (0019,XX21) DS 1

Table longitudinal position (0019,XX22) DS 1

Table Lateral position (0019,XX23) DS 1

Angle value 1 (0019,XX01) DS 1



User zoom factor (0019,XX18) IS 1

X zoom (0019,XX19) IS 1

Y zoom (0019,XX1A) IS 1

User spatial filter strengh (0019,XX17) IS 1

Table 3-36: Private Creator Identification (GEMS_DL_FRAME_01)


frame_sequence (0025,XX0A) SQ 1

>frame_id (0025,XX02) IS 1

Table 3-37: Private Creator Identification (GEMS_XR3DCAL_01)


3Dcal image rows (0021,XX01) IS 1

3Dcal image columns (0021,XX02) IS 1

3Dcal field of view (0021,XX03) FL 1

3Dcal acquisition date (0021,XX04) DA 1

3Dcal acquisition time (0021,XX05) TM 1

3Dcal calibration processing date (0021,XX06) DA 1

3Dcal calibration processing time (0021,XX07) TM 1




Table 3-37: Private Creator Identification (GEMS_XR3DCAL_01) (cont'd)Attribute Name Tag VR VM

3Dcal L arm angle (0021,XX08) FL 1

3Dcal Pivot angle vector (0021,XX09) FL 1-N

3Dcal C arm angle (0021,XX0A) FL 1

3Dcal matrix sequence (0021,XX0B) SQ 1

>3Dcal matrix elements (0021,XX0C) LO 1-N

3Dcal algorithm version (0021,XX0D) LO 1

3Dcal 3D frame unit size (0021,XX0E) FL 1

3Dcal calibration mode (0021,XX0F) LO 1

3Dcal image frame origin row (0021,XX10) FL 1

3Dcal image frame origin column (0021,XX11) FL 1

3Dcal positioner pivot rotation speed (0021,XX12) IS 1

3Dcal number of images (0021,XX13) IS 1

3Dcal Instance UID (0021,XX14) UI 1

3Dcal image pixel spacing (0021,XX15) FL 2

3Dcal centering mode (0021,XX16) CS 1




Chapter 4 SC Information Object Implementation1 Introduction

This section specifies the use of the DICOM SC Image IOD to represent the informationincluded in SC images produced by this implementation. Corresponding attributes areconveyed using the module construct.

Chapter 4 SC Information Object Implementation 71



2 SC Entity Relationship Model

The Entity–Relationship diagram for the SC Image interoperability schema is shown inIllustration 4-1 . In this figure, the following diagrammatic convention is established torepresent the information organization :

• Each entity is represented by a rectangular box• Each relationship is represented by a diamond shaped box.• The fact that a relationship exists between two entities is depicted by lines connecting


The relationships are fully defined with the maximum number of possible entities in therelationship shown. In other words, the relationship between Series and Image can have upto n Images per Series, between Patient and Study can have up to n Studies per Patient, butthe Study to Series has 1 Series for each Study.

Illustration 4-1: SC Image Entity Relationship Diagram

72 2 SC Entity Relationship Model




Please refer to DICOM Standard Part 3 (Information Object Definitions) for a description ofeach of the entities contained within the SC Information Object.


Table 4-1: Mapping of DICOM Entities to INNOVA Entities

DICOM <Name of the product> Entity

Patient Patient

Study Exam

Series Exam

Image Photo

Frame Not Applicable




3 IOD Module Table and Information Module Definitions

3.1 IOD Module Table

Within an entity of the DICOM v3.0 SC IOD, attributes are grouped into related setof attributes. A set of related attributes is termed a module. A module facilitates theunderstanding of the semantics concerning the attributes and how the attributes are relatedwith each other. A module grouping does not infer any encoding of information into datasets.The table in this section identifies the defined modules within the entities which comprise theDICOM v3.0 SC IOD. Modules are identified by Module Name.See DICOM v3.0 Part 3 for acomplete definition of the entities, modules, and attributes.

Table 4-2: SC Image IOD Modules


Patient Patient Section 3.2.1.2

Study General Study Section 3.2.2.2

Patient Study Section 3.2.2.3

Series General Series Section 3.2.3.2

Equipment General Equipment Section 3.2.4.2

SC Equipment Table 4-13

Image General Image Section 3.2.5.2

Image Pixel Section 3.2.5.3

SC Image Table 4-14

Overlay Plane Section 3.2.5.4

Modality LUT Section 3.2.5.5

VOI LUT Table 4-11

SOP Common Section 3.2.5.6

XA Positioner Section 3.2.5.8

Photo QCA Table 4-16

Photo QVA Table 4-17

3.2 Information Module Definitions

Please refer to DICOM v3.0 Standard Part 3 (Information Object Definitions) for a descriptionof each of the entities and modules contained within the SC Information Object. Thefollowing modules are included to convey Enumerated Values, Defined Terms, and OptionalAttributes supported. Type 1 & Type 2 Attributes are also included for completeness andto define what values they may take and where these values are obtained from. It shouldbe noted that they are the same ones as defined in the DICOM v3.0 Standard Part 3(Information Object Definitions).

3.2.1 Common Patient Entity Modules


This section describes the modules of Common Patient Entity




3.2.1.2 Patient Module

This section specifies the Attributes of the Patient that describe and identify the Patientwho is the subject of a diagnostic Study. This Module contains Attributes of the patientthat are needed for diagnostic interpretation of the Image and are common for all studiesperformed on the patient.

Table 4-3: Patient Module Attributes


Patient’s Name (0010,0010) 2 From user interface or worklist. When from userinterface, value contains only last_name(restricted to 32chars)^first_name(restricted to 31 chars). When fromworklist, equals first component group.

Patient ID (0010,0020) 2 From worklist or user interface. Restricted to 64 chars.

Patient’s Birth Date (0010,0030) 2 From user interface or worklist. Restricted to 64 chars.YYYYMMDD.

Patient’s Sex (0010,0040) 2 From user interface or worklist. ”M”, ”F” or “O”


The following Study IE Modules are common to all Composite Image IODs which referencethe Study IE. These Module contain Attributes of the patient and study that are neededfor diagnostic interpretation of the image.


This section describes the modules of Common Study Entity.

3.2.2.2 General Study Module

This section specifies the Attributes which describe and identify the Study performed uponthe Patient.

Table 4-4: General Study Module Attributes


Study Instance UID (0020,000D) 1 Restricted to 64 characters, internally generated as follows:“registred prefix for GEMS” + “.2. registred identificationof Innova System within GEMS” + “.a.b.c” encoded macaddress of the DL host + “.x.y.z” unique id protected againstreinstallation and reentrance.

Study Date (0008,0020) 2 YYYYMMDD, restricted to 8 characters.

Study Time (0008,0030) 2 HHMMSS.XXX, restricted to 10 characters.

Referring Physician’s Name (0008,0090) 2 From User Interface, restricted to 64 characters.

Study ID (0020,0010) 2 From User Interface, restricted to 64 characters.

Accession Number (0008,0050) 2 From User Interface, restricted to 64 characters

Study Description (0008,1030) 3 From User Interface, restricted to 64 characters. (May notbe sent).

Name of Physician(s)Reading Study

(0008,1060) 3 From User Interface, restricted to 64 characters. (May notbe sent).

study_number (0015,XX8F) 3 Internally generated, starting at 1. (May not be sent).




3.2.2.3 Patient Study Module

This section defines Attributes that provide information about the Patient at the time theStudy was performed.

Table 4-5: Patient Study Module Attributes


Patient’s Age (0010,1010) 3 Either from User Interface or Calculated from Patient’sBirth Date (0010,0030). Three digits followed by oneletter: In Years (Y), Months (M), Weeks (W) or Days (D).(May not be sent).

Patient’s Size (0010,1020) 3 From User Interface or worklist, restricted to 16 characters.(May not be sent).

Patient’s Weight (0010,1030) 3 From User Interface or worklist, restricted to 16 characters.(May not be sent).

3.2.2.4 Dose Study Module

This section defines Attributes that provide information about the Dose at the time the Studywas performed.

Table 4-6: Dose Study Module Attributes


Study Dose (0015, xx80) 3 Total dose delivered to the patient during the study.

Study total DAP (0015, xx81) 3 Cumulative dose area product for the study.

Study Fluoro DAP (0015, xx82) 3 Cumulative dose area product for the fluoro acquisitionsperformed during the study.

Study fluoro time (0015, xx83) 3 Total time of fluoroscopy during the study.

Study record dap (0015, xx84) 3 Cumulative dose area product for the record acquisitionsperformed during the study

Study record time (0015, xx85) 3 Total time of record acquisitions during the study.

3.2.3 Common Series Entity Modules

The following Series IE Modules are common to all Composite Image IODs which referencethe Series IE.


This section describes the modules of Common Series Entity.

3.2.3.2 General Series Module

This section specifies the Attributes which identify and describe general information aboutthe Series within a Study.




Table 4-7: General Series Study Module Attributes


Modality (0008,0060) 1 XA

Series Instance UID (0020,000E) 1 Restricted to 64 characters, internally generated as follows:“registred prefix for GEMS” + “.2. registred identification of InnovaSystem within GEMS” + “.a.b.c” encoded mac address of theDL host + “.x.y.z” unique id protected against reinstallation andreentrance.

Series Number (0020,0011) 2 Internally generated, starting at 1. Series Date (0008,0021) 3YYYYMMDD, restricted to 8 characters.

Series Time (0008,0031) 3 HHMMSS.XXX, restricted to 10 characters.

Performing Physicians’Name

(0008,1050) 3 From User Interface, restricted to 64 characters. (May not besent).

Protocol Name (0018,1030) 3 From User Interface

Series Description (0008,103E) 3 From User Interface, restricted to 64 characters. (May not besent).

Operators’ Name (0008,1070) 3 From User Interface, restricted to 64 characters. (May not besent).

request attributesequence

(0040,0275) 3 Sequence that contains attributes from the Imaging ServiceRequest. In this implementation, this sequence contains only twoitems.

>request procedure id (0040,1001) 1C Identifier that identifies the Requested Procedure in the ImagingService Request. Required if Sequence Item is present.

>Scheduled ProcedureStep ID

(0040,0009) 1C Field always contains the value "Unknown" in the image header.

3.2.4 Common Equipment Entity Modules

The following Equipment IE Module is common to all Composite Image IODs which referencethe Equipment IE.


This section describes the modules of Common Equipment Entity

3.2.4.2 General Equipment Module

This section specifies the Attributes which identify and describe the piece of equipmentwhich produced a Series of Images.

Table 4-8: General Equipment Module Attributes


Manufacturer (0008,0070) 2 GE MEDICAL SYSTEMS

Institution Name (0008,0080) 3From ”Service User Interface”, configured at theinstallation of the system. Restricted to 64 characters.

Institution Address (0008,0081) 3From ”Service User Interface”, configured at theinstallation of the system. Restricted to 1024characters.

Manufacturer’s Model (0008,1090) 3 DL

Device Serial Number (0018,1000) 3 Serial Number From internal configuration of themachine.




Table 4-8: General Equipment Module Attributes (cont'd)Attribute Name Tag Type Attribute Description

Software Versions (0018,1020) 3 DL application version.

Station name (0018,1010) 3AE Title of the system that generates the DICOMimage.

3.2.5 Common Image Entity Modules

The following Image IE Modules are common to all Composite Image IODs which referencethe Image IE.


This section describes the modules of Common Image Entity.

3.2.5.2 General Image Module

This section specifies the Attributes which identify and describe an image within a particularseries.

Table 4-9: General Image Module Attributes

Attribute Name Tag

Typenum-ber of thesource se-ries for a

photo

Attribute Description

source series number (0019,xx50) 3 Always DERIVED\SECONDARY

source image number (0019,xx51) 3 number of the source image for a photo.

source frame number (0019,xx52) 3 number of the source frame for a photo

image type (0008,0008) 3 Image identification characteristics

acquisition date (0008,0022) 3 The date the acquisition of data that resulted in this imagestarted

content date (0008,0023) 2CThe date the image pixel data creation started. Requiredif image is part of a series in which the images aretemporally related

Acquisition Time (0008,0032) 3 The time the acquisition of data that resulted in this imagestarted

Content Time (0008,0033) 2CThe time the image pixel data creation started. Requiredif image is part of a series in which the images aretemporally related

Source Image Sequence (0008,2112) 3A sequence which identifies the set of Image SOPClass/Instance pairs of the images which were used toderive this image

>Referenced SOP Class UID (0008,2112)>(0008,1150) 1C Uniquely identifies the referenced SOP Class

>Referenced SOP Instance UID (0008,2112)>(0008,1155) 1C Uniquely identifies the referenced SOP Instance

>Referenced Frame Number (0008,1160) 1Creferences one or more frames of a multi-frame image,identifying which frames were used to derive this image

instance number (0020,0013) 2 A number that identifies the image in the Series

Patient Orientation (0020,0020) 2C

Patient direction of the rows and columns of the image.Required if image does not require Image Orientation(0020,0037) and Image Position (0020,0032). Thisattribute contains the values corresponding to the firstframe




Table 4-9: General Image Module Attributes (cont'd)

Attribute Name Tag

Typenum-ber of thesource se-ries for a

photo

Attribute Description

Image comments (0020,4000) 3 User-defined comments about the image

Burned In Annotation (0028,0301) 3

Indicates whether or not the image contains sufficientburned in annotation to identify the patient and date theimage was acquired. Enumerated values: YES and NO.If this attribute is absent, then the image may or may notcontain burned in annotation.

>Purpose of Referenced CodeSequence (0040,A170) 3

Describes the purpose for which thereference is made.Only a single Itemshall be permitted in this sequence.Defined Context ID 7201.

>>Code Value (0008,0100) 1C Required if a sequence item is present

>>Code schema designator (0008,0102) 1C Required if a sequence item is present

>>Code meaning (0008,0104) 1C Required if a sequence item is present

patient position per image (0019,xxC7) 3

Patient position descriptor relative to the equipment.Required for CT and MR images; shall not be presentif Patient Orientation Code Sequence (0054,0410) ispresent; may be present otherwise.

Defined terms are:

• HFP = Head First-Prone

• HFS = Head First-Supine

• HFDR = Head First-Decubitus Right

• HFDL = Head First-Decubitus Left

• FFDR = Feet First-Decubitus Right

• FFDL = Feet First-Decubitus Left

• FFP = Feet First-Prone

• FFS = Feet First-Supine

3.2.5.3 Image Pixel Module

This section specifies the Attributes that describe the pixel data of the image.

Table 4-10: Image Pixel Module Attributes


Samples per Pixel (0028,0002) 1 1

Photometric Interpretation (0028,0004) 1 MONOCHROME1 or MONOCHROME2

Rows (0028,0010) 1 1024

Columns (0028,0011) 1 1024

Bits Allocated (0028,0100) 1 8

Bits Stored (0028,0101) 1 8




Table 4-10: Image Pixel Module Attributes (cont'd)Attribute Name Tag Type Attribute Description

High Bit (0028,0102) 1 7

Pixel Representation (0028,0103) 1 0000H (unsigned integer)

Pixel Data (7FE0,0010) 1 Data stream of the pixel samples.

3.2.5.4 Overlay Plane Module

This module is not sent

3.2.5.5 Common Lookup Table Modules

VOI LUT Module

This section specifies the Attributes that describe the VOI LUT.

Table 4-11: VOI LUT Module Attributes


Window center (0028,1050) 3Value of the window center optimized at theimage acquisition.

Window width (0028,1051) 3Value of the window width optimized at theimage acquisition.

default brightness contrast (0019,xx4E) 3The brightness/contrast applied by IPOpt tothe VOI during the image acquisition

user brightness contrast (0019,xx4F) 3The brightness/contrast modified by the userto the VOI during the image review

Modality LUT Module

The Modality LUT module is not sent.


The SOP Common Module is mandatory for all DICOM IODs.

This section defines the Attributes which are required for proper functioning and identificationof the associated SOP Instances. They do not specify any semantics about the Real–WorldObject represented by the IOD.



SOP Instance UID (0008,0018) 1

Restricted to 64 characters, internallygenerated as follows: “registred prefix forGEMS” + “.2. registred identification ofInnova System within GEMS” + “.a.b.c”encoded mac address of the DL host+ “.x.y.z” unique id protected againstreinstallation and reentrance.

SOP Class UID (0008,0016) 1 1.2.840.10008.5.1.4.1.1.12.1

Specific Character Set (0008,0005) 1C ISO_IR 100




3.2.5.7 SC Modules

This Section describes SC Equipment, and Image Modules. These Modules containAttributes that are specific to SC Image IOD.

SC Equipment Module

This Module describes equipment used to convert images into a DICOM format.

Table 4-13: SC Image Equipment Module Attributes


Conversion type (0008,0064) 1

Describes the kind of image conversion.Defined terms are: DV=Digitized Video,DI=Digital Interface, DF=Digitized Film,WSD=Workstation

SC manufacturer (0018,1016) 3 Manufacturer of the Secondary CaptureDevice

SC manufacturer model name (0018,0018) 3Manufacturer's model number of theSecondary Capture Device

SC Image Module

The table in this Section contains IOD Attributes that describe SC images.

Table 4-14: SC Image Module Attributes


Date of Secondary Capture (0018,1012) 3 Date the SC image was captured

Time of Secondary Capture (0018,1014) 3 Time the SC image was captured

3.2.5.8 XA Positioner Module

Table 4-15: XA Positioner Equipment Module Attributes


Positioner Primary Angle (0018,1510) 2 LAO/RAO angle for the SC image.

Positioner Secondary Angle (0018,1511) 2 CRA/CAU angle for the SC image.

3.2.5.9 Photo QCA Module

Table 4-16: Photo QCA Module Attributes


Analysis Views (0009,XX00) 1Enumerated type containing one of the following values:PRE, POST and PRE_POST.

Segment (0009,XX10) 2

ACC segment name. Defined terms: ProximalRCARCA OstiumMid RCADistal RCARight PDARightLV–BRLMCALMCA OstiumProximal LADMid LADDistalLAD1st Diagonal2nd Diagonal1st Septal- ProximalCircumflexMid Circumflex1st Marginal2nd Marginal3rdMarginalDistal CircumflexL




Table 4-16: Photo QCA Module Attributes (cont'd)Attribute Name Tag Type Attribute Description

Pre Catheter Name (0009,XX11) 2CUser description of pre–procedure catheter. Required ifAnalysis Type (0009,XX00) is ”PRE” or ”PRE_POST”.(May not be sent).

Pre Catheter Size (0009,XX12) 1CSize of pre–procedure catheter in millimeters. Requiredif Analysis Type (0009,XX00) is ”PRE” or ”PRE_POST”.(May not be sent).

Pre Reference Diameter (0009,XX13) 1CPre–procedure Reference Diameter, in millimeters.Required if Analysis Type (0009,XX00) is ”PRE” or”PRE_POST”. (May not be sent).

Pre Minimum Lumen Diameter (0009,XX14) 1CPre–procedure Minimum Lumen Diameter, inmillimeters. Required if Analysis Type (0009,XX00) is”PRE” or ”PRE_POST”. (May not be sent).

Pre Average Diameter (0009,XX15) 2CPre–procedure Average Diameter, in millimeters.Required if Analysis Type (0009,XX00) is ”PRE” or”PRE_POST”. (May not be sent).

Pre Stenosis Length (0009,XX16) 2CPre–procedure Stenosis Length, in millimeters.Required if Analysis Type (0009,XX00) is ”PRE” or”PRE_POST”. (May not be sent).

Pre Stenosis % (0009,XX17) 2CPre–procedure Stenosis as a percentage. Required ifAnalysis Type (0009,XX00) is ”PRE” or ”PRE_POST”.(May not be sent).

Pre Geometric Area Reduction % (0009,XX18) 2CPre–procedure Geometric Area Reduction as apercentage. Required if Analysis Type (0009,XX00) is”PRE” or ”PRE_POST”. (May not be sent).

Post Catheter Name (0009,XX21) 2CUser description of post–procedure catheter. Required ifAnalysis Type (0009,XX00) is ”POST” or ”PRE_POST”.(May not be sent).

Post Catheter Size (0009,XX22) 1CSize of post–procedure catheter in millimeters. Requiredif Analysis Type (0009,XX00) is ”POST” or ”PRE_POST”.(May not be sent).

Post Reference Diameter (0009,XX23) 1CPost–procedure Reference Diameter, in millimeters.Required if Analysis Type (0009,XX00) is ”POST” or”PRE_POST”. (May not be sent).

Post Minimum Lumen Diameter (0009,XX24) 1CPost–procedure Minimum Lumen Diameter, inmillimeters. Required if Analysis Type (0009,XX00) is”POST” or ”PRE_POST”. (May not be sent).

Post Average Diameter (0009,XX25) 2CPost–procedure Average Diameter, in millimeters.Required if Analysis Type (0009,XX00) is ”POST” or”PRE_POST”. (May not be sent).

Post Stenosis Length (0009,XX26) 2CPost–procedure Stenosis Length, in millimeters.Required if Analysis Type (0009,XX00) is ”POST” or”PRE_POST”. (May not be sent).

Post Stenosis % (0009,XX27) 2CPost–procedure Stenosis as a percentage. Required ifAnalysis Type (0009,XX00) is ”POST” or ”PRE_POST”.(May not be sent) .

Post Geometric Area Reduction % (0009,XX28) 2CPost–procedure Geometric Area Reduction as apercentage. Required if Analysis Type (0009,XX00) is”POST” or ”PRE_POST”. (May not be sent).




3.2.5.10 Photo QVA Module Attributes

Table 4-17: Photo QVA Module Attributes


Dodge End Diastolic Volume ml (0009,xx60) 3 Dodge's End Diastolic Volume ml

Dodge End Systolic Volume ml (0009,xx61) 3 Dodge's End Systolic Volume ml

Dodge Stroke Volume ml (0009,xx62) 3 Dodge's Stroke Volume ml

Dodge Ejection Fraction (0009,xx63) 3 Dodge's Ejection Fraction

Simspon End Diastolic Volume ml (0009,xx64) 3 Simspon's End Diastolic Volume ml

Simspon End Systolic Volume ml (0009,xx65) 3 Simspon's End Systolic Volume ml

Simspon Stroke Volume ml (0009,xx66) 3 Simspon's Stroke Volume ml

= Simspon Ejection Fraction 0009,xx67) 3 Simspon's Ejection Fraction

CFX Single Hypokinesia in Region (0009,xx68) 3 CFX Single Hypokinesia in Region

CFX Single Hyperkinesia inOpposite Region (0009,xx69) 3 CFX Single Hyperkinesia in Opposite Region

CFX Single Total LV contourPercent

(0009,xx6A) 3 Desc for DCS = CFX Single Total LV contour Percent

CFX Multiple Hypokinesia inRegion (0009,xx6B) 3 CFX Multiple Hypokinesia in Region

CFX Multiple Hyperkinesia inOpposite Region (0009,xx6C) 3 CFX Multiple Hyperkinesia in Opposite Region

CFX Multiple Total LV contourPercent

(0009,xx6D) 3 CFX Multiple Total LV contour Percent

RCA Single Hypokinesia in Region (0009,xx6E) 3 RCA Single Hypokinesia in Region

RCA Single Hyperkinesia inOpposite Region (0009,xx6F) 3 RCA Single Hyperkinesia in Opposite Region

RCA Single Total LV contourPercent

(0009,xx70) 3 RCA Single Total LV contour Percent

RCA Multiple Hypokinesia inRegion (0009,xx71) 3 RCA Multiple Hypokinesia in Region

RCA Multiple Hyperkinesia inOpposite Region (0009,xx72) 3 RCA Multiple Hyperkinesia in Opposite Region

RCA Multiple Total LV contourPercent

(0009,xx73) 3 RCA Multiple Total LV contour Percent

LAD Single Hypokinesia in Region (0009,xx74) 3 LAD Single Hypokinesia in Region

LAD Single Hyperkinesia inOpposite Region (0009,xx75) 3 LAD Single Hyperkinesia in Opposite Region

LAD Single Total LV contourPercent

(0009,xx76) 3 LAD Single Total LV contour Percent

LAD Multiple Hypokinesia inRegion (0009,xx77) 3 LAD Multiple Hypokinesia in Region

LAD Multiple Hyperkinesia inOpposite Region (0009,xx78) 3 LAD Multiple Hyperkinesia in Opposite Region

LAD Multiple Total LV contourPercent

(0009,xx79) 3 LAD Multiple Total LV contour Percent

Dodge End Diastolic Volumeml/m2

(0009,xx7A) 3 Dodge's End Diastolic Volume ml_m2

Dodge End Systolic Volume ml/m2 (0009,xx7C) 3 Dodge's End Systolic Volume ml_m2




Table 4-17: Photo QVA Module Attributes (cont'd)Attribute Name Tag Type Attribute Description

Dodge Stroke Volume ml/m2 (0009,xx7E) 3 Dodge's Stroke Volume ml_m2

Simspon End Diastolic Volumeml/m2

(0009,xx80) 3 Simspon's End Diastolic Volume ml_m2

Simspon End Systolic Volumeml/m2

(0009,xx82) 3 Simspon's End Systolic Volume ml_m2

Simspon Stroke Volume ml/m2 (0009,xx84) 3 Simspon's Stroke Volume ml_m2




4 Private Data Dictionary

Table 4-18: Private Creator Identification (GEMS_DL_STUDY_01)


study_number (0015,XX8F) IS 1

Table 4-19: Private Creator Identification (GEMS_DL_IMG_01)


Image file name (0019,xx30) LO 1

Source series number (0019,xx50) IS 1

Source image number (0019,xx51) IS 1

Source frame number (0019,xx52) IS 1

Acquisition plane (0019,xxDE) CS 1

Patient Position per Image (0019,xxC7) CS 1

Image flip (0019,xx95) CS 2

SID vector (0019,xxBE) FL 1-N

SOD vector (0019,xxE9) FL 1-N

LV Diastolic contour (0019,xx0C) FL 2-2N

LV Systolic contour (0019,xx0D) FL 2-2N

Default brightness contrast (0019,xx4E) DS 2

User brightness contrast (0019,xx4F) DS 2

Table rotation status vector (0019,xxBD) CS 1-N Status of the rotation of the table in the horizontalplane (YES or NO). This is a multi-valuedattribute that contains the Table Rotation Statusfor each frame

Table 4-20: Private Creator Identification (QCA_Results)


Analysis Views (0009,XX00) CS 1

Segment (0009,XX10) LO 1

Pre Catheter Name 2C (0009,XX11) LO 1

Pre Catheter Size (0009,XX12) DS 1

Pre Reference Diameter (0009,XX13) DS 1

Pre Minimum Lumen Diameter (0009,XX14) DS 1

Pre Average Diameter (0009,XX15) DS 1

Pre Stenosis Length (0009,XX16) DS 1

Pre Stenosis % (0009,XX17) IS 1

Pre Geometric Area Reduction % (0009,XX18) IS 1

Post Catheter Name (0009,XX21) LO 1

Post Catheter Size (0009,XX22) DS 1

Post Reference Diameter (0009,XX23) DS 1




Table 4-20: Private Creator Identification (QCA_Results) (cont'd)Attribute Name Tag VR VM

Post Minimum Lumen Diameter (0009,XX24) DS 1

Post Average Diameter (0009,XX25) DS 1

Post Stenosis Length (0009,XX26) DS 1

Post Stenosis % (0009,XX27) IS 1

Post Geometric Area Reduction % (0009,XX28) IS 1

Table 4-21: Private Creator Identification (GEMS_QVA_PHOTO_01)


Dodge End Diastolic Volume ml (0009,xx60) FL 1

Dodge End Systolic Volume ml (0009,xx61) FL 1

Dodge Stroke Volume ml (0009,xx62) FL 1

Dodge Ejection Fraction (0009,xx63) IS 1

Simspon End Diastolic Volume ml (0009,xx64) FL 1

Simspon End Systolic Volume ml (0009,xx65) FL 1

Simspon Stroke Volume ml (0009,xx66) FL 1

Simspon Ejection Fraction (0009,xx67) IS 1

CFX Single Hypokinesia inRegion

(0009,xx68) FL 1

CFX Single Hyperkinesia inOpposite Region

(0009,xx69) FL 1

CFX Single Total LV contourPercent

(0009,xx6A) IS 1

CFX Multiple Hypokinesia inRegion

(0009,xx6B) FL 1

CFX Multiple Hyperkinesia inOpposite Region

(0009,xx6C) FL 1

CFX Multiple Total LV contourPercent

(0009,xx6D) IS 1

RCA Single Hypokinesia inRegion

(0009,xx6E) FL 1

RCA Single Hyperkinesia inOpposite Region

(0009,xx6F) FL 1

RCA Single Total LV contourPercent

(0009,xx70) IS 1

RCA Multiple Hypokinesia inRegion

(0009,xx71) FL 1

RCA Multiple Hyperkinesia inOpposite Region

(0009,xx72) FL 1

RCA Multiple Total LV contourPercent

(0009,xx73) IS 1

LAD Single Hypokinesia inRegion

(0009,xx74) FL 1

LAD Single Hyperkinesia inOpposite Region

(0009,xx75) FL 1

LAD Single Total LV contourPercent

(0009,xx76) IS 1




Table 4-21: Private Creator Identification (GEMS_QVA_PHOTO_01) (cont'd)LAD Multiple Hypokinesia inRegion

(0009,xx77) FL 1

LAD Multiple Hyperkinesia inOpposite Region

(0009,xx78) FL 1

LAD Multiple Total LV contourPercent

(0009,xx79) IS 1

Dodge End Diastolic Volumeml/m2

(0009,xx7A) FL 1

Simspon End Systolic Volumeml/m2

(0009,xx82) FL 1

Table 4-22: Private Creator Identification (QUANTITATIVE_RESULTS)


Number of Diseased Vessels (0009,xx50) IS 1

Hypokinesis in Region (0009,xx51) DS 1

Hyperkinesis in Opposite Region (0009,xx52) DS 1

Percent Total LV Hypokinesis (0009,xx53) IS 1

Calibration Factor (0009,xx55) DS 1




Chapter 5 Modality Worklist Information ModelDefinition1 Introduction

This section specifies the use of the DICOM Modality Worklist Information Model used toorganize data and against which a Modality Worklist Query will be performed.

Chapter 5 Modality Worklist Information Model Definition 89



2 Modality Worklist Information Model Entity Relationship Model

The Entity–Relationship diagram for the Modality Worklist Information Model schema isshown in Illustration 5-1 . It represents the information that composes a Worklist Item. Inthis figure, the following diagrammatic convention is established to represent the informationorganization :

• Each entity is represented by a rectangular box.• Each relationship is represented by a diamond shaped box..• The fact that a relationship exists between two entities is depicted by lines connecting


Illustration 5-1: Modality Worklist Information Model E/R DIAGRAM

90 2 Modality Worklist Information Model Entity Relationship Model




Please refer to DICOM Standard PS 3.3. (Information Object Definitions) and PS 3.4(Service Class Specifications) for a description of each of the Entities contained withinthe Modality Worklist Information Model.


Table 5-1: Mapping of DICOM Entities to INNOVA Entities

DICOM INNOVA Entity

Scheduled Procedure Step

Requested Procedure Exam

Imaging Service Request Exam

Visit

Patient Patient




3 Information Model Module Table

Within an entity of the DICOM v3.0 Modality Worklist Information Model, attributes aregrouped into related set of attributes. A set of related attributes is termed a module. Amodule facilitates the understanding of the semantics concerning the attributes and how theattributes are related with each other. A module grouping does not infer any encoding ofinformation into datasets.

The table in this section identifies the defined modules within the entities which comprise theDICOM v3.0 Modality Worklist Information Model. Modules are identified by Module Name.

See DICOM v3.0 PS 3.3 and PS 3.4 for a complete definition of the entities, modules,and attributes.

Table 5-2: Modality Worklist Information Model Modules


Scheduled Procedure Step SOP Common 4.2.2

Scheduled Procedure Step 4.2.3

Requested Procedure Requested Procedure 4.3.2

Imaging Service Request Imaging Service Request 4.4.2

Visit Visit Identification 4.5.2

Visit Status 4.5.3

Visit Relationship 4.5.4

Visit Admission 4.5.5

Patient Patient Relationship 4.6.2

Patient Identification 4.6.3

Patient Demographic 4.6.4

Patient Medical 4.6.5

92 3 Information Model Module Table



4 Information Model

4.1 Information Model Module Table

Within an entity of the DICOM v3.0 Modality Worklist Information Model, attributes aregrouped into related set of attributes. A set of related attributes is termed a module. Amodule facilitates the understanding of the semantics concerning the attributes and how theattributes are related with each other. A module grouping does not infer any encoding ofinformation into datasets.

The table in this section identifies the defined modules within the entities which comprise theDICOM v3.0 Modality Worklist Information Model. Modules are identified by Module Name.

See DICOM v3.0 PS 3.3 and PS 3.4 for a complete definition of the entities, modules,and attributes.

Table 5-3: Modality Worklist Information Model Modules


Scheduled Procedure Step SOP Common Section 4.2.2.2

Scheduled Procedure Step Section 4.2.2.3

Requested Procedure Requested Procedure Section 4.2.3.2

Imaging Service Request Imaging Service Request Section 4.2.4.2

Visit Visit Identification Section 4.2.5.2

Visit Status Section 4.2.5.3

Visit Relationship Section 4.2.5.4

Visit Admission Section 4.2.5.5

Patient Patient Relationship Section 4.2.6.2

Patient Identification Section 4.2.6.3

Patient Demographic Section 4.2.6.4

Patient Medical Section 4.2.6.5

4.2 Information Model Keys

Please refer to DICOM Standard PS 3.3. (Information Object Definitions) and PS 3.4(Service Class Specifications) for a description of each of the Entities contained withinthe Modality Worklist Information Model. The following Module descriptions are includedto specify what data elements are supported and what type of matching can be applied. Itshould be noted that they are the same ones as defined in the DICOM v3.0 Standard PS3.4 (Service Class Specifications).

4.2.1 Supported Matching

Following are the types of matching that can be request by the implementation :

• Single Value matching• Universal Matching• Wild Card Matching• Range of date, Range of Time




4.2.2 Scheduled Procedure Step Entity


This section describes the modules of Scheduled Procedure Step Entity.



Attribute Name Tag Expected MatchingKey Type

Expected ReturnedKey Type

Mapped into theImage

Note

Specific Character Set (0008,0005) O 1C No Matching on this tagis not supported. ISOIR_100 is alwaysassumed.

4.2.2.3 Scheduled Procedure Step Module

Table 5-5: Scheduled Procedure Step Module Attributes




Note

Scheduled Procedure StepSequence

(0040,0100) R 1 No

>Scheduled Station AETitle

(0040,0001) R 1 No Matching issupported. Thematching value isthe AE– Title of theInnova system.

>Scheduled ProcedureStep Start Date

(0040,0002) R 1 No Matching value can beconfigured for date ordate range.

>Scheduled ProcedureStep Start Time

(0040,0003) R 1 No Requested, zerolength.

>Modality (0008,0060) R 1 No This is requestedeither as zero lengthor as XA, userconfigurable.

>Scheduled PerformingPhysician’s Name

(0040,0006) R 2 Yes Requested, zerolength. After userconfirmation, the firstvalue can be mappedinto PerformingPhysician (0008,1050)

>Scheduled ProcedureStep Description

(0040,0005) O 1C No After userconfirmation, canbe mapped into Studydescription (0008,1030)

>Scheduled Action ItemCode Sequence

(0040,0008) O 1C No

>>Code Value (0008,0100) O 1C No

>>Coding SchemeDesignator

(0008,0102) O 1C No

94 4 Information Model



Table 5-5: Scheduled Procedure Step Module Attributes (cont'd)Attribute Name Tag Expected Matching

Key TypeExpected Returned

Key TypeMapped into the

ImageNote

>>Code Meaning (0008,0104) O 3 No

>Scheduled ProcedureStep ID

(0040,0009) O 1 No

4.2.3 Requested Procedure Entity


This section describes the modules of Requested Procedure Entity.

4.2.3.2 Requested Procedure Module

Table 5-6: Requested Procedure Module Attributes



Mapped intothe Image

Note

Requested Procedure ID (0040,1001) O 1 Yes This information can bemapped into Study ID(0020,0010) after userconfirmation.

Requested ProcedureDescription

(0032,1060) O 1C No

Requested ProcedureCode Sequence

(0032,1064) O 1C No

>Code Value (0008,0100) O 1C No

>Coding SchemeDesignator

(0008,0102) O 1C No

>Code Meaning (0008,0104) O 3 No

Study Instance UID (0020,000D) O 1 Yes If one SPS is selected, orif multiple SPSs with thesame Study Instance UIDare selected, the value ismapped in the images.Else, a Study InstanceUID is generated by theimplementatoin.

Referenced StudySequence

(0008,1110) O 2 No

>Referenced SOP ClassUID

(0008,1150) O 1C No

>Referenced SOPInstance UID

(0008,1155) O 1C No

4.2.4 Imaging Service Request Entity


This section describes the modules of Imaging Service Request Entity.




4.2.4.2 Imaging Service Request Module

Table 5-7: Imaging Service Request Module Attributes




Note

Accession Number (0008,0050) O 2 Yes Matching is supported,user entered value issent.

Referring Physician’sName

(0008,0090) O 2 Yes Requested, zerolength. The first personname componentgroup is mapped in theimage. No truncationis performed. Valuesmay be trucnated fordisplay only.

4.2.5 Visit Entity


This section describes the modules of Visit Entity.

4.2.5.2 Visit Identification Module

Table 5-8: Visit Identification Module Attribute


Expected Returned KeyType


Note

Admission ID (0038,0010) O 2 Yes

4.2.5.3 Visit Status Module

No attribute from this module is requested in the modality worklist query.

4.2.5.4 Visit Relationship Module


4.2.5.5 Visit Admission Module


4.2.6 Patient Entity


This section describes the modules of Patient Entity.

4.2.6.2 Patient Relationship Module





4.2.6.3 Patient Identification Module

Table 5-9: Patient Identification Module Attributes


Expected Returned KeyType


Note

Patient’s Name (0010,0010) R 1 Yes Matching is supported,user entered value is sent.Wildcards are appenedin the query at theend of the components(first name and lastname). The first personname component groupreturned is mapped in theimage. No truncation isperformed. Values maybe trucnated for displayonly

Patient ID (0010,0020) R 1 Yes Matching is supported,user entered value is sent.

4.2.6.4 Patient Demographic Module

Table 5-10: Patient Demographic Module Attributes

Attribute Name Tag Expected Matching KeyType



Note

Patients Birth Date (0010,0030) O 2 Yes

Patient’s Sex (0010,0040) O 2 Yes

Patient’s Weight (0010,1030) O 2 Yes

Patient’s Size (0010,1020) O 3 Yes

4.2.6.5 Patient Medical Module





Chapter 6 Storage Commitment Push ModelImplementation1 Storage commitment push model information object definition

1.1 Introduction

The Storage Commitment Information Object is used both for N–ACTION StorageCommitment Requests by the SCU and N–EVENT–REPORT Storage CommitmentNotifications by the SCP

1.2 Storage Commitment Module for N-Action

The INNOVA uses the DIMSE service element N–ACTION to send the Storage Commitmentrequest.

The INNOVA supports the following data elements in the part of data set of the N–ACTIONrequest:

Table 6-1: Storage Commitment Module for N-Action-RQ

Attribute Name Tag AE Use

Transaction UID (0008,1195) Restricted to 64 characters, internallygenerated as follows:”registered prefix forGEMS”

+ ”.2” Registered prefix of Innova Systemwithin GEMS

+ ”.a.b.c” encoded mac address of the DLhost

+”.x.y.z” unique id protected againstreinstallation and re–en-trance

Storage Media File–Set ID (0088,0130) Not used

Storage Media File–Set UID (0088,0140) Not used

Referenced SOP Sequence (0008,1199)

>Referenced SOP Class UID (0008,1150)

>Referenced SOP Instance UID (0008,1155)

>Storage Media File–Set ID (0088,0130) Not used

>Storage Media File–Set UID (0088,0140) Not used

1.3 Storage Commitment Module for N-Event-Report

The INNOVA uses the DIMSE service element N–EVENT–REPORT to receive a StorageCommitment response.

The INNOVA supports the following data elements in the part of data set in a receivedN–EVENT–REPORT request:

Chapter 6 Storage Commitment Push Model Implementation 99



Table 6-2: Storage Commitment Module for N-Event-Report-RQ

Attribute Name Tag AE Use

Transaction UID (0008,1195) Not used

Retrieve AE Title (0008,0054) Not used

Storage Media File–Set ID (0088,0130) Not used

Storage Media File–Set UID (0088,0140) Not used

Referenced SOP Sequence (0008,1199) The AE considers the SOP Instancesreferenced by this sequence as successfullyarchived.



>Retrieve AE Title (0008,0054) Not used

>Storage Media File–Set ID (0088,0130) Not used

>Storage Media File–Set UID (0088,0140) Not used

Failed SOP Sequence (0008,1198) The AE considers the SOP Instancesreferenced by this sequence as not archived;the application will display an error status inthe network queue.



>Failure Reason (0008,1197) The failure reason is logged in the applicationerror log.

100 1 Storage commitment push model information object definition

© 2008 General Electric Company.GE Medical Systems, a General Electric Company, going to market as GE Healthcare.283, rue de la Minière78530, BucFRANCE

www.gehealthcare.com

innova single plane cardiovascular imaging system …/media/documents/us-global/products/... ·...

Documents