GE Healthcare, LLC

Technical Publications

DOC0506131
Revision 3

GE MR DICOM CONFORMANCE
STATEMENT
Supported product :
TM
• Discovery MR450

Operating Documentation
Copyright 2009 GE Healthcare LLC, All Rights Reserved
 DOC0506131 rev3

Table of Contents

1 INTRODUCTION 8

1.0 Overview 8

1.1 Scope and Field of Application 9

1.2 Important Remarks 9

1.3 References 10

1.4 Definitions 10

1.5 Symbols and Abbreviations 10

2 NETWORK CONFORMANCE STATEMENT 11

2.0 INTRODUCTION 11

2.1 IMPLEMENTATION MODEL 11

2.1.1 Application Data Flow Diagram 12
2.1.2 Functional Definition of AE’s 13
2.1.3 Sequencing of Real-World Activities 14

2.2 AE SPECIFICATIONS 14
2.2.1 DICOM Server AE Specification 14

2.3 COMMUNICATION PROFILES 29

2.3.1 Supported Communication Stacks (parts 8,9) 29
2.3.2 TCP/IP Stack 29

2.4 EXTENSIONS / SPECIALIZATIONS / PRIVATIZATIONS 29

2.4.1 Specialized Information Object Definition 29
2.4.2 Private Data Elements 31

2.5 CONFIGURATION 31
2.5.1 AE Title/Presentation Address Mapping 31
2.5.2 Configurable Parameters 31

2.6 SUPPORT OF EXTENDED CHARACTER SETS 32

2.7 CODES AND CONTROLLED TERMINOLOGY 32

2.8 SECURITY PROFILES 32

3 MEDIA STORAGE CONFORMANCE STATEMENT 33

3.0 Introduction 33

3.1 IMPLEMENTATION MODEL 33

3.1.1 Application Data Flow Diagram 33

Copyright 2009 General Electric Company. All rights reserved

Page 2 of 126
 DOC0506131 rev3

3.1.2 Functional Definitions of AE's 34

3.1.3 Sequencing Requirements 34

3.2 AE SPECFICIATIONS 35
3.2.1 DICOM CD-R/DVD-R Interchange Archive Server AE Specification 35
3.2.2 File Meta Information for Implementation Class and Version 38

3.3 Standard, Augmented and Private Application Profiles 39

3.3.1 Class and Profile Identification 39
3.3.2 Clinical Contexts 39
3.3.3 Standard Application Profiles 40
3.3.4 Private Application Profiles 43

3.4 Extensions, Specialization’s and Privatization’s of SOP Classes and Transfer Syntaxes 43
3.4.1 Extensions, Specialization’s and Privatization’s of SOP Classes 43
3.4.2 Private Transfer Syntax Specification 44

3.5 Configuration 44

3.6 Support of Extended Character Sets 44

4 PRINT SCU CONFORMANCE STATEMENT 45

4.0 Introduction 45

4.1 IMPLEMENTATION MODEL : PRINT SCU 45

4.1.1 Application Data Flow Diagram 45
4.1.2 Functional Definition of AE’s 45
4.1.3 Sequencing of Real-World Activities 46

4.2 AE SPECIFICATIONS 46
4.2.1 DICOM Print SCU AE Specification 46
4.2.2 Basic Film Session SOP Class 48
4.2.3 Basic Film Box SOP Class 49
4.2.4 Basic Grayscale Image Box SOP Class 50
4.2.5 Basic Color Image Box SOP Class 51
4.2.6 Printer SOP Class 51
4.2.7 Print Job SOP Class 52

4.3 Association Acceptance Policy 52

4.4 COMMUNICATION PROFILES 52

4.4.1 Supported Communication Stacks (parts 8,9) 52
4.4.2 TCP/IP Stack 52
4.4.3 API 52
4.4.4 Physical Media Support 52
4.4.5 Standard Extended/Specialized/Private SOPs 53

4.5 AE Title/Presentation Address Mapping 53

4.5.1 Configurable Parameters 53
4.5.2 Support of Extended Character Set 53

5 ENHANCED MODALITY WORKLIST CONFORMANCE STATEMENT 54

Copyright 2009 General Electric Company. All rights reserved

Page 3 of 126
 DOC0506131 rev3

5.0 INTRODUCTION 54

5.1 IMPLEMENTATION MODEL 54

5.1.1 Application Data Flow Diagram 54
5.1.2 Functional Definition of AE's 55
5.1.3 Sequencing of Real-World Activities 55

5.2 AE SPECIFICATIONS 55
5.2.1 Worklist Server AE Specification 55

5.3 MODALITY WORKLIST INFORMATION MODEL DESCRIPTION 58

5.4 MODALITY WORKLIST INFORMATION MODEL ENTITY-RELATIONSHIP MODEL 58

5.4.1 ENTITY DESCRIPTIONS 59
5.4.2 MR Systems Mapping of DICOM Entities 60

5.5 INFORMATION MODEL MODULE 60

5.6 INFORMATION MODEL KEYS 61

5.6.1 Supported Matching 62
5.6.2 Scheduled Procedure Step Entity 62
5.6.3 Requested Procedure Entity 63
5.6.4 Imaging Service Request Entity 64
5.6.5 Visit Entity 65
5.6.6 Patient Entity 66

5.7 PRIVATE DATA DICTIONARY 67

6 PERFORMED PROCEDURE STEP CONFORMANCE STATEMENT 68

6.0 Introduction 68

6.1 Implementation Model 68

6.1.1 Application Data Flow Diagram 68
6.1.2 Functional Definition of AEs 68
6.1.3 Sequencing of Real-World Activities 69

6.2 AE Specification 70
6.2.1 PPS DICOM SCU Specification 70

6.3 COMMUNICATION PROFILES 71

6.3.1 Supported Communication Stacks (PS 3.8) 71
6.3.2 OSI Stack 72
6.3.3 TCP/IP Stack 72
6.3.4 Point-to-Point Stack 72

6.4 EXTENSIONS/SPECIALIZATION/PRIVATIZATION 72
6.4.1 Standard Extended/Specialized/Private SOPs 72
6.4.2 Private Transfer Syntaxes 72

6.5 CONFIGURATION 72
6.5.1 AE Title/Presentation address Mapping 73
6.5.2 Configurable Parameters 73

Copyright 2009 General Electric Company. All rights reserved

Page 4 of 126
 DOC0506131 rev3

6.6 SUPPORT OF EXTENDED CHARACTER SETS 73

6.7 CODES AND CONTROLLED TERMINOLOGY 73

6.7.1 Mapped Coded Terminology 73

6.8 SECURITY PROFILES 73

6.9 N-CREATE & NSET REQUEST MESSAGE 73

6.10 ERROR HANDLING AND RECOVERY 74

6.11 Use of Specific DICOM Data 75

6.12 USE OF SPECIFIC DICOM DATA 78

6.12.1 Patient Level 78
6.12.2 Study Level 79
6.12.3 Series Level 79

7 STORAGE COMMITMENT CONFORMANCE 80

7.0 Introduction 80

7.1 Implementation Model 80

7.1.1 Application data flow diagram 80
7.1.2 Functional definitions 80
7.1.3 Sequencing of real-world activities 81

7.2 AE Specifications 81
7.2.1 DICOM Server AE specifications for Storage Commitment 81
7.2.2 Request Processing 82
7.2.3 Response Processing 83
7.2.4 Association Acceptance Policy 84

8 GRAYSCALE SOFTCOPY PRESENTATION STATE INFORMATION OBJECT

IMPLEMENTATION 85

8.0 IOD MODULE TABLE 85

8.1 GSPS-Specific INFORMATION MODULE DEFINITIONS 85

8.1.1 Presentation Series Module 86
8.1.2 Presentation State Modules Attributes 86
8.1.3 Display Shutter Module 87
8.1.4 Bitmap Display Shutter Module 87
8.1.5 Overlay/Curve Activation Module 87
8.1.6 Displayed Area Module 88
8.1.7 Graphic Annotation Module 89
8.1.8 Spatial Transformation Module 89
8.1.9 Graphic Layer Module 90
8.1.10 Softcopy VOI LUT Acquisition Module 90
8.1.11 Softcopy Presentation LUT Module 90

9 ENHANCED STRUCTURED REPORT INFORMATION OBJECT IMPLEMENTATION

91

Copyright 2009 General Electric Company. All rights reserved

Page 5 of 126
 DOC0506131 rev3

9.0 IOD MODULE TABLE 91

9.1 INFORMATION MODULE DEFINITIONS 91

9.1.1 SR Document Series Module 91
9.1.2 SR Document General Module 91
9.1.3 SR Document Content Module 93
9.1.4 SOP Common Module 94

9.2 Standard Extended and Private Data Attributes 95

9.2.1 Private Group GEMS_0039 95

9.3 Standard Extended and Private CONTEXT Groups 95

9.4 Standard Extended and Private Templates 95

10 SECURITY CONFORMANCE STATEMENT 96

10.0 DE-IDENTIFICATION 96

10.1 ASSOCIATION LEVEL SECURITY 100

A. APPENDIX STANDARD DATA ELEMENTS 101

A.1. MR Specific IOD Definition 101

A.1.1 MR Image IOD Modules 101

A.1.2 MR Image Module 101

A.2. SC Specific IOD Definition 102

A.2.1 SC Image IOD Modules 102

A.3. MR/SC IOD Module Definitions 103

A.3.1 Patient Module 103
A.3.2 General Study Module 103
A.3.3 Patient Study Module 104
A.3.4 General Series Module 105
A.3.5 General Equipment Module 106
A.3.6 General Image Module 106
A.3.7 Image Plane Module 107
A.3.8 Image Pixel Module 107
A.3.9 Contrast Bolus Module 108
A.3.10 SOP Common Module 108
A.3.12 VOI LUT Module 108
A.3.13 Frame of Reference Module 109
A.3.14 SC Equipment Module 109
A.3.15 Additional Attributes 109

B. APPENDIX PRIVATE DATA ELEMENTS 111

B.1 MR Image IOD Private Data Elements Definition 111

B.1.1. Private Creator Identification (GEMS_IDEN_01) 111
B.1.2. Private Creator Identification (GEMS_PATI_01) 111

Copyright 2009 General Electric Company. All rights reserved

Page 6 of 126
 DOC0506131 rev3

B.1.3. Private Creator Identification (GEMS_ACQU_01) 111

B.1.4. Private Creator Identification (GEMS_RELA_01) 113
B.1.5. Private Creator Identification (GEMS_STDY_01) 114
B.1.6. Private Creator Identification (GEMS_SERS_01) 114
B.1.7. Private Creator Identification (GEMS_IMAG_01) 115
B.1.8. Private Creator Identification (GEMS_IMPS_01) 115
B.1.9. Private Creator Identification (GEMS_PARM_01) 115
B.1.10. Private Creator Identification (BrainWave: 1.2.840.113819.3) 119
B.1.11. Private Creator Identification (GEMS_MR_RAW_01) 119
B.1.12. Private Creator Identification (GEMS_FUNCTOOL_01) 120

APPENDIX C DICOMDIR DIRECTORY INFORMATION 121

C.1 DICOMDIR Directory Information 121

C.1.1 Basic Directory IOD Definition 121
C.1.2 Directory Information Module 121
C.1.2.1 CD-R/DVD-R Directory Information Module 121

C.1.3 CD-R/DVD-R Directory Record Selection Keys 122

C.1.3.1 CD-R/DVD-R Patient Keys 122
C.1.3.2 CD-R/DVD-R Study Keys 122
C.1.3.3 CD-R/DVD-R Series Keys 123
C.1.3.4 CD-R/DVD-R Image Keys 123

• THIS DIRECTION IS AVAILABLE IN ENGLISH ONLY.

WARNING • IF A CUSTOMER’S SERVICE PROVIDER REQUIRES A LANGUAGE

OTHER THAN ENGLISH, IT IS THE CUSTOMER’S RESPONSIBILITY TO
PROVIDE TRANSLATION SERVICES.
• DO NOT ATTEMPT TO SERVICE THE EQUIPMENT UNLESS THE
DIRECTION HAS BEEN CONSULTED AND UNDERSTOOD.
• FAILURE TO HEED THIS WARNING MAY RESULT IN INJURY TO THE
SERVICE PROVIDER, OPERATOR OR PATIENT FROM ELECTRIC
SHOCK, MECHANICAL OR OTHER HAZARDS.

Copyright 2009 General Electric Company. All rights reserved

Page 7 of 126
 DOC0506131 rev3

1 INTRODUCTION

1.0 Overview

Section 1, Introduction, provides general information about the content and scope of this document.

Section 2, Network Conformance Statement, is the DICOM Conformance Statement related to this
product Conformance Statements define the subset of options selected from those offered by the
DICOM standard.

Section 3, Media Storage Conformance Statement, is the DICOM Conformance Statement related
to Media Storage Application Profile.

Section 4, Print SCU Conformance Statement, is the DICOM Conformance Statement related to
DICOM Print SCU.

Section 5 Modality Worklist is the DICOM Conformance Statement related to the DICOM Modality
Worklist implementation on the covered systems.

Section 6 Performed Procedure Step Conformance Statement, is the DICOM Conformance

Statement related to the DICOM PPS implementation on the covered systems.

Section 7 Storage Commitment Conformance Statement is the DICOM Conformance Statement

related to the DICOM storage commitment implementation on the covered systems.

Section 8 Grayscale Softcopy Presentation State Information Object specifies the compliance to the
DICOM requirements of Grayscale Softcopy Presentation State features.

Section 9 Enhanced Structured Report Information Object specifies the compliance to the DICOM
requirements of Structured Report features.

Section 10 Security Conformance Statement specifies the compliance to the DICOM requirements
of Security features.

Copyright 2009 General Electric Company. All rights reserved

Page 8 of 126
 DOC0506131 rev3

1.1 Scope and Field of Application

This document is the DICOM Conformance Statement for GE MR systems and is necessary to insure proper
processing and interpretation of GE medical image data exchanged using DICOM. The GE Healthcare
Conformance Statements are available to the public.

The reader of this conformance statement should be aware that different GE devices are capable of using
different Information Object Definitions. For example, a GE CT scanner may send images using the CT
Information Object, MR Information Object, Secondary Capture Object, etc.

Included in this Conformance Statement are Module Definitions which define all data elements used by this
GE Healthcare implementation. If the user encounters unspecified private data elements while parsing a GE
Data Set, the user is well advised to ignore those data elements (per the DICOM standard). Unspecified
private data element information is subject to change without notice. If, however, the device is acting as a
“full fidelity storage device”, it should retain and retransmit all of the private data elements which are sent by
GE devices.

Private data elements may be updated from one release to the next release. This is done in order to add
additional information or remove information that does not apply to the image object. Please refer to the
appropriate product release DICOM Conformance Statement for the list of private elements supported.

The following table provides the GE MR product(s) covered in this document and their specific details.

Software Product name Product Implementation CD/DVD DICOM Implementation

version UID version name
TM
20.1 Discovery 1.2.840.113619.6.260 MergeCOM3_300
MR450

1.2 Important Remarks

The use of these Conformance Statements, in conjunction with the DICOM Standards, is intended to
facilitate communication with GE imaging equipment. However, by itself, it is not sufficient to insure that
inter-operation will be successful. The user (or user’s agent) needs to proceed with caution and address
at least four issues:

• Integration - The integration of any device into an overall system of interconnected devices goes
beyond the scope of standards (DICOM), and of this introduction and associated Conformance
Statements when interoperability with non-GE equipment is desired. The responsibility to analyze the
applications requirements and to design a solution that integrates GE imaging equipment with non-GE
systems is the user’s responsibility and should not be underestimated. The user is strongly advised to
ensure that such integration analysis is correctly performed.

• Validation - Testing the complete range of possible interactions between any GE device and non-GE
devices, before the connection is declared operational, should not be overlooked. Therefore, the user
should ensure that any non-GE provider accepts full responsibility for all validation required for their
connection with GE devices. This includes the accuracy of the image data once it has crossed the
interface between the GE imaging equipment and the non-GE device and the stability of the image data
for the intended applications.
Such a validation is required before any clinical use (diagnosis and/or treatment) is performed. It applies
when images acquired 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 on a GE console or workstation.

Copyright 2009 General Electric Company. All rights reserved

Page 9 of 126
 DOC0506131 rev3

• Future Evolution - GE understands that the DICOM Standard will evolve to meet the user’s growing
requirements. GE is actively involved in the development of the DICOM Standard. DICOM will
incorporate new features and technologies and GE may follow the evolution of the Standard. The GE
Healthcare protocol is based on DICOM as specified in each DICOM Conformance Statement. Evolution
of the Standard may require changes to devices which have implemented DICOM. In addition, GE
reserves the right to discontinue or make changes to the support of communications features
(on its products) reflected by these DICOM Conformance Statements. The user should ensure that
any non-GE provider, which connects with GE devices, also plans future evolution of the DICOM
standard. Failure to do so will likely result in the loss of function and/or connectivity as the DICOM
Standard changes and GE products are enhanced to support these changes.

• Interaction - It is the sole responsibility of the non-GE provider to ensure that communications with the
interfaced equipment does not cause degradation of GE imaging equipment performance and/or
function.

1.3 References
See Digital Imaging and Communications in Medicine (DICOM) parts 1 through 18 (NEMA PS 3.1-18).

1.4 Definitions
See Digital Imaging and Communications in Medicine (DICOM) parts 1 through 18 (NEMA PS 3.1-18).

1.5 Symbols and Abbreviations

See Digital Imaging and Communications in Medicine (DICOM) parts 1 through 18 (NEMA PS 3.1-18).

Copyright 2009 General Electric Company. All rights reserved

Page 10 of 126
 DOC0506131 rev3

2 NETWORK CONFORMANCE STATEMENT

2.0 INTRODUCTION

This Conformance Statement specifies the GE MR system’s compliance to the DICOM standards assembled
with image object networking. It details the DICOM Service Classes and roles which are supported by this
product in the versions listed in Section 1.1.

The GE MR system uses DICOM services to import images for possible further analysis and/or processing. It
also uses DICOM services to export images to other DICOM-compliant machines.

Note the format of this section follows the format of the DICOM Standard Part 2 (conformance) Annex A
hence the paragraph numbering scheme. Please refer to that part of the standard while reading this section.

2.1 IMPLEMENTATION MODEL

All DICOM functionality on the GE MR system is handled by the DICOM Server Application Entity (AE). The
DICOM Server AE is commanded to perform DICOM services through the buttons and menu selections on
the main user interface panel. The DICOM Server AE is also listening to a pre-defined port for incoming
connections.

Copyright 2009 General Electric Company. All rights reserved

Page 11 of 126
 DOC0506131 rev3

2.1.1 Application Data Flow Diagram

ILLUSTRATION 2.0
IMPLEMENTATION MODEL DATA FLOW DIAGRAM DICOM Standard
Interface
Choose Image
Push Remotely
Sent
1 1
Choose Remote
Query Query
Remote Retrieve
2 2

Choose DICOM SERVER Remote

Pull AE Pull
3 Request
3

Choose Image
Remote Remotely
Archive Archived
4 4

Choose Verify
DICOM Request
Ping 5
5

Remote
Image system
Installation requests
7 image storage
7

Query Remote
Retrieve Query
SCP Request
8 8

There are several Real-World Activities that will cause the DICOM Server Application Entity (DICOM Server
AE) to initiate a DICOM association to a remote DICOM Application Entity. Illustration 2.0 above shows
basic Real-World Activities. In addition, Sections 3, 4, 5, 6, and 7 cover Media Storage, Print, Modality
Worklist, Performed Procedure Step, and Storage Commit in more detail.

The following paragraphs describe the Real-World Activities of Illustration 2.0:

1. The Choose Push Real-World Activity consists of an operator selecting one or more studies,
series, or images in the local database browser. The operator then clicks on the destination button in
the network panel at the bottom of the local database browser. Real-World Activity, Query Remote,
causes the DICOM Server AE to initiate an association to the Remote DICOM AE and request the
list of all studies. Once the DICOM Server AE receives the list of studies, the operator will have to
choose the study and the local database browser will list the series of the study chosen. After

Copyright 2009 General Electric Company. All rights reserved

Page 12 of 126
 DOC0506131 rev3

receiving the list of series the DICOM Server AE will ask for the list of images for the series chosen
by the operator

2. Real-World Activity, Choose Pull, will be available once the Query Remote activity is performed.
The operator can now select one or more studies (series or images) and ask the DICOM Server AE
to retrieve the selected image(s) from the Remote DICOM AE by clicking on the “Local DB” button at
the bottom of the local database browser.

3. The Choose Remote Archive Real-World activity consists of an operator choosing a remote
DICOM AE that supports Storage Commitment as provider from the archive panel at the bottom of
the local database browser. The operator chooses the exam or series in the local database browser
and clicks on the archival destination from the archive list at the bottom of the local database
browser. The Commitment request for the transferred image instances is sent after the complete
image transfer. The Commitment response can come on same association or on a different
association. Refer to Section 7 for details on the Storage Commitment implementation.

4. Real-World Activity, Click Ping, consists of an operator selecting the a Remote DICOM AE from the
“Network Configuration” window and clicking on “Ping” on the right side-bar. This is to check to
check the status of the selected remote DICOM AE.

5. Real-World Activity, the operator needs to configure the Remote DICOM AE for the DICOM Server
AE to be able to communicate with the Remote DICOM AE .

6. The DICOM Server AE will perform the Real-World activity is Image Installation after the remote AE
sends an image to the GE MR system.

7. Once a Query Retrieve request is received, the DICOM Server AE will search the local database for
all entries that match the keys requested by the Remote DICOM AE and send back the list of
matches. The DICOM Server AE will also respond to an incoming retrieval request from a Remote
AE by sending the image(s) to the Destination AE.

2.1.2 Functional Definition of AE’s

DICOM Server Application Entity initiates the following operations:

• Initiate an association to a Remote AE for the purpose of sending images to the Remote AE. If the
Remote AE accepts the presentation context applicable to the image(s) being sent, the DICOM Server
AE will send the image(s) to the receiving Remote AE by invoking the C-STORE-RQ operation for each
image on the same association.
• Initiate an association to a Remote AE for the purpose of committing images previously sent successfully
to the Remote AE for the purpose of the remote AE to commit to the storage of those images. If the
Remote AE accepts the presentation context, a storage commitment will be established with the Remote
AE with the DICOM Server AE sending the N-Action Request. The Remote AE completes the
commitment by sending the N-EVENT REPORT. The DICOM Server AE updates the archive flag in the
image browser for successful instances.
• Initiate an association with a Remote AE to query for images on the remote host. A Study-Root Study-
Level C-FIND-RQ request will be sent to the Remote AE once an association has been established.
Once all the responses have been received, the operator needs to select an exam in the local database
browser, on selection of the exam the DICOM Server AE will issue a Series-Level C-FIND-RQ request to
get the series for a study in the list. Similarly the Image-Level C-FIND-RQ will be issued for the series
selected from the series list.
• Send a C-MOVE-RQ request to a Remote AE for retrieve of images after successful association
establishment. The DICOM Server AE’s Storage SCP will receive the images over a separate
association.

Copyright 2009 General Electric Company. All rights reserved

Page 13 of 126
 DOC0506131 rev3

• Initiate an association with a Remote AE to verify its status with a C-ECHO-RQ. The Remote AE will
report its status in a C-ECHO-RSP.

The DICOM Server AE waits for association requests from Remote AEs that wish to perform the following
operations:

• Verification: If a C-ECHO-RQ message is received, the DICOM Server AE will send back a C-ECHO-
RSP message with a status of “success”.
• Image Storage: If a C-STORE-RQ message is received, the DICOM Server AE will receive the image
and try to update the local database. If the image is stored successfully on storage media and the
database updated a status of “success” will be returned in a C-STORE-RSP message.
• Query: If a C-FIND-RQ message is received the DICOM Server AE will search the database for the
requested attributes and send back a C-FIND-RSP message containing a match and a status of
“pending”. After all matching records have been sent, a status of “success’ will be returned in a C-FIND-
RSP message. The Remote AE can terminate the query by sending a C-CANCEL-FIND-RQ message.
• Retrieve: If a C-MOVE-RQ message is received the DICOM Server AE will lookup its list of configured
Remote AEs for the Destination AE. If the Destination AE is configured, the DICOM Server AE will open
a new association to the Destination AE and use C-STORE-RQ to send the image(s). The DICOM
Server AE will send a C-MOVE-RSP message with a status of “pending” after every five images are
sent. When all images are sent or if DICOM Server AE receives a C-CANCEL-MOVE-RQ a final C-
STORE-RSP will be sent back with an appropriate status.

2.1.3 Sequencing of Real-World Activities

2.1.3.1 Query Remote

Real-World Activity Query Remote must be performed before Choose Pull Option can be performed.

2.1.3.2 Storage Commitment

The user has to select exam\series from the local database browser and click on the archive destination in
the archive panel at the bottom of the local database browser.

2.2 AE SPECIFICATIONS

2.2.1 DICOM Server AE Specification

The following tables detail the DICOM Classes supported as an SCP and an SCU. Although the GE MR
systems accept other modality image types (CT, PET, RT, etc.), this conformance statement does not cover
other modality image and derived image types. Please refer to each modality DICOM Conformance
Statement for specific details.

This Application Entity provides Standard Conformance to the following DICOM SOP Classes as an SCU:

SOP Class Name (SCU) SOP Class UID

Verification (Echo) 1.2.840.10008.1.1
CT Image Information Storage 1.2.840.10008.5.1.4.1.1.2

Copyright 2009 General Electric Company. All rights reserved

Page 14 of 126
 DOC0506131 rev3

MR Image Information Storage 1.2.840.10008.5.1.4.1.1.4

PET Image Information Storage 1.2.840.10008.5.1.4.1.1.128
RT Structure Set Storage 1.2.840.10008.5.1.4.1.1.481.3
GEMS PET Raw Information Storage 1.2.840.113619.4.30
Secondary Capture image storage 1.2.840.10008.5.1.4.1.1.7
Grayscale Softcopy Presentation State Storage* 1.2.840.10008.5.1.4.1.1.11.1
Enhanced Structured Report 1.2.840.10008.5.1.4.1.1.88.22
Study Root Query/Retrieve – FIND 1.2.840.10008.5.1.4.1.2.2.1
Study Root Query/Retrieve – MOVE 1.2.840.10008.5.1.4.1.2.2.2
Storage Commitment Push model SOP class 1.2.840.10008.1.20.1
* This implementation does not support the following features of Grayscale Softcopy Presentation State:
Mask, Bitmap Display Shutter, Overlay Plane, Overlay/Curve Activation, and Modality LUT. All other
modules are supported. The GE MR systems can receive this object from other systems, but does not
support Mask, Bitmap Display Shutter, Overlay Plane, Overlay/Curve Activation, and Modality LUT.

This Application Entity provides Standard Conformance to the following DICOM SOP classes as an SCP:

SOP Class Name (SCP) SOP Class UID

Verification (Echo) 1.2.840.10008.1.1
CT Information Storage 1.2.840.10008.5.1.4.1.1.2
MR Information Storage 1.2.840.10008.5.1.4.1.1.4
PET Image Information Storage 1.2.840.10008.5.1.4.1.1.128
RT Structure Set Storage 1.2.840.10008.5.1.4.1.1.481.3
GEMS PET Raw Information Storage 1.2.840.113619.4.30
Secondary Capture Image storage 1.2.840.10008.5.1.4.1.1.7
Enhanced Structured Report 1.2.840.10008.5.1.4.1.1.88.22
Study Root Query/Retrieve – FIND 1.2.840.10008.5.1.4.1.2.2.1
Study Root Query/Retrieve – MOVE 1.2.840.10008.5.1.4.1.2.2.2

2.2.1.1 Association Establishment Policy

2.2.1.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 association initiated by the DICOM Server AE is:

Maximum Length PDU 64 kbytes

SOP class Extended Negotiation is not supported.

The maximum number of Presentation Context Items supported is 60. Note that the same Abstract Syntax
may be offered multiple times with different Transfer Syntaxes.

The user information items sent by this product are: Maximum PDU Length and, Implementation UID

2.2.1.1.2 Number of Associations

Copyright 2009 General Electric Company. All rights reserved

Page 15 of 126
 DOC0506131 rev3

The DICOM Server AE (SCU) will initiate only one DICOM association at a time to perform an image store to
a remote host or retrieve image(s) from a Remote AE.

The DICOM Server AE (SCP) can have a maximum of four DICOM associations open simultaneously to
receive and store image or respond to an echo.

A single association is used to send the commitment request. This waits for the response from the
commitment provider on the same association for a configurable amount of time. It will also accept an
association for receiving the response from the commitment provider at any time.

2.2.1.1.3 Asynchronous Nature

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

2.2.1.1.4 Implementation Identifying Information

The Implementation UID allows unique identification of a set of products that share the same
implementation.

Please refer to Section 1.1 for details on specific GE MR system information.

2.2.1.2 Association Initiation by Real-World Activity

2.2.1.2.1 Push Image(s) to Remote AE

2.2.1.2.1.1 Associated Real-World Activity

The operator must first select the exam\series\image on the local database browser and click on the Remote
DICOM AE in the network panel at the bottom of the local database browser to which the operator desires to
send the exam\series\image to.

Note: If multiple study, series, or images are chosen to be pushed, one association will be established for
each of the studies, series, or images. A single association for a single series will be used for the multiple C-
STORE operations necessary for the images in the series.

2.2.1.2.1.2 Proposed Presentation Contexts

The following table shows the proposed presentation contexts for the DICOM Server AE after Real-World
Activity “Push” Operation has been performed. The following selection method is used when choosing from
multiple accepted transfer syntaxes:

1. If image is stored locally in Implicit VR the order of preference is as follows:

i) Implicit VR Little Endian

2. If image is stored locally in Explicit VR the order of preference is as follows:

i) Explicit VR Little Endian
ii) Implicit VR Little Endian
iii) Explicit VR Big Endian

Copyright 2009 General Electric Company. All rights reserved

Page 16 of 126
 DOC0506131 rev3

Table 2.2.1.2.1.2-1 Proposed Presentation Contexts for DICOM Server AE and Real-World
activity Push Image(s)

Presentation Context Table - Proposal

Abstract Syntax Transfer Syntax Role Extended
Negotiation
Name UID Name List UID List
CT Image Storage 1.2.840.10008.5.1.4.1.1.2 Implicit VR Little 1.2.840.10008.1.2 SCU None
Endian
CT Image Storage 1.2.840.10008.5.1.4.1.1.2 Explicit VR Little 1.2.840.10008.1.2.1 SCU None
Endian
Explicit VR Big 1.2.840.10008.1.2.2
Endian
MR Image 1.2.840.10008.5.1.4.1.1.4 Implicit VR Little 1.2.840.10008.1.2 SCU None
Storage Endian
MR Image 1.2.840.10008.5.1.4.1.1.4 Explicit VR Little 1.2.840.10008.1.2.1 SCU None
Storage Endian
Explicit VR Big 1.2.840.10008.1.2.2
Endian
PET Image 1.2.840.10008.5.1.4.1.1.12 Implicit VR Little 1.2.840.10008.1.2 SCU None
Information 8 Endian
Storage
PET Image 1.2.840.10008.5.1.4.1.1.12 Explicit VR Little 1.2.840.10008.1.2.1 SCU None
Information 8 Endian
Storage Explicit VR Big 1.2.840.10008.1.2.2
Endian
RT Structure Set 1.2.840.10008.5.1.4.1.1.48 Implicit VR Little 1.2.840.10008.1.2 SCU None
Storage 1.3 Endian
RT Structure Set 1.2.840.10008.5.1.4.1.1.48 Explicit VR Little 1.2.840.10008.1.2.1 SCU None
Storage 1.3 Endian
Explicit VR Big 1.2.840.10008.1.2.2
Endian
GEMS PET Raw 1.2.840.113619.4.30 Implicit VR Little 1.2.840.10008.1.2 SCU None
Information Endian
Storage
GEMS PET Raw 1.2.840.113619.4.30 Explicit VR Little 1.2.840.10008.1.2.1 SCU None
Information Endian
Storage Explicit VR Big 1.2.840.10008.1.2.2
Endian
Secondary 1.2.840.10008.5.1.4.1.1.7 Implicit VR Little 1.2.840.10008.1.2 SCU None
Capture Endian
Secondary 1.2.840.10008.5.1.4.1.1.7 Explicit VR Little 1.2.840.10008.1.2.1 SCU None
Capture Endian
Explicit VR Big 1.2.840.10008.1.2.2
Endian
Grayscale 1.2.840.10008.5.1.4.1.1.11 Implicit VR Little 1.2.840.10008.1.2 SCU None
Softcopy .1 Endian
Presentation State
Grayscale 1.2.840.10008.5.1.4.1.1.11 Explicit VR Little 1.2.840.10008.1.2.1 SCU None
Softcopy .1 Endian
Presentation State Explicit VR Big 1.2.840.10008.1.2.2
Endian
Enhanced 1.2.840.10008.5.1.4.1.1.88 Implicit VR Little 1.2.840.10008.1.2 SCU None
Structured Report .22 Endian
Enhanced 1.2.840.10008.5.1.4.1.1.88 Explicit VR Little 1.2.840.10008.1.2.1 SCU None
Structured Report .22 Endian
Explicit VR Big 1.2.840.10008.1.2.2
Endian

2.2.1.2.1.2.1 SOP Specific Conformance Statement for Image Storage SOP Classes

This implementation can perform multiple C-STORE operations over a single association.

Copyright 2009 General Electric Company. All rights reserved

Page 17 of 126
 DOC0506131 rev3

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

Upon receiving a C-STORE confirmation containing a Refused status, this implementation will terminate the
association.

Upon receiving a C-STORE confirmation containing any status that is not Success or Refused, this
implementation will consider the current request to be a failure but will continue to attempt to send the
remaining images in the request on the same association.

Each C-STORE operation supports an “Association Timer”. This timer starts when the association request is
sent and stops when the association is established. The time-out is configurable in network-cfg.xml file as
StoreAssociationTimeout. Default is 60 seconds

Each C-STORE operation also supports an “Operation Inactivity Timer”. This time-out starts once the first C-
STORE request has been issued (on association) or received and is reset each time a C-STORE response
has been received or when subsequent C-STORES are sent. This time-out is configurable in network-
cfg.xml file as StoreAssociationTimeout.. Default is 5 minutes.

If any of the three timers mentioned above expires, the connection is closed and the operation in progress is
considered failed.

When DICOM Server AE initiates an association to issue a C-STORE, the image will be transmitted by the
DICOM Server AE with the same elements as was originally received or created locally. Note, to retain all
private elements in non-GE images, the image must have been originally received using Explicit transfer
syntax.

2.2.1.2.2 Query Remote AE

2.2.1.2.2.1 Associated Real-World Activity

The operator must select the Remote DICOM AE from the “Source” pull-down on the local database browser
and select the hostname of the source from where the images are to be retrieved.

Provided that the operator had set "Custom search" to "Off" when setting the Remote host parameters, the
“Query” operation will cause the DICOM Server AE to initiate an association (with zero length Patient name,
Patient id, Study date, Accession number, and Study id) to the selected Remote AE when the “Hostname”
entry is selected from the “Source” pull-down menu.

Otherwise, if the operator had set "Custom search" to "On" when setting the Remote host parameters, the
“Query” operation will cause a Customize search parameters menu to appear. The operator can enter
values for Patient name, Patient id, Study date, Accession number, and Study id. Not entering a value
means match on any value for that field. Patient name will match on any patient name that contains what
the operator entered. Patient id, Study id, and Accession number will match on what the operator enters.
For Study date, the operator selects a range type from the "Exam date" pull down menu, where the choices
are Equals, Before, Between, or Exactly. Once a range type is selected, the correct number of fields appear
and the operator enters dates into those fields. Once the desired parameters are entered the operator
chooses "Ok" and that will cause the DICOM Server AE to initiate an association to the selected Remote AE.

Once a list of Study/Series/Image is retrieved, the operator can invoke the “Pull” operation by clicking on the
“Local DB” button at the bottom of the local database browser .

Copyright 2009 General Electric Company. All rights reserved

Page 18 of 126
 DOC0506131 rev3

2.2.1.2.2.2 Proposed Presentation Contexts

When the Real-World activity “Query” or “Pull” is initiated all presentation contexts shown in Table
2.2.1.2.1.2-1 are proposed during association establishment, but only the Query/Retrieve-FIND related
contexts are applicable to this activity.

2.2.1.2.2.2.1 SOP Specific Conformance Statement for C-FIND SCU

After the Query operation is initiated, the DICOM Server AE will perform a study-root C-FIND-RQ request at
each of the three levels (Study, Series, and Image) in succession.

The Initial Study-Level request will ask for studies in the Remote database that match the user specified
Patient name, Patient id, Study date, Accession number, and Study id. Zero length data in any of those
fields means match on any value. Zero length data is the default value if the user does not specify a value.
The user specified Patient name will come surrounded by single asterisks (asterisk is a wild card that
matches any number of characters). The Study date is a range of dates where a date is exactly 8 characters
long and the format of the range is:
"" is any date,
"yyyymmdd-" is any date on or after that year/month/day,
"-yyyymmdd" is any date on or before that year/month/day,
"yyyymmdd-yyyymmdd" is any date on or between those dates,
"yyyymmdd" is only on that date.

The C-FIND SCU will not perform any extended negotiation and so will only perform a hierarchical query.

Each C-FIND SCU operation supports an “Association Timer” and “Operation Inactivity Timer” using
QueryAssociationTimeout and QueryResponseTimeout, in network-cfg.xml configuration file. Default values
are 30 seconds, 5 minutes respectively.

If a “Cancel” or “Refused” status is returned from the Remote AE the association is closed and the operation
terminated.

The user can cancel the C-FIND request by moving to another network node or clicking on the local
database.

The DICOM Server AE will parse each matching C-FIND-RSP reply and ignore the entries that do not
contain a valid DICOM data stream. No VR validation is performed which means that syntax errors will be
ignored.

Tables 2.2.1.2.2.2.1-1 - 2.2.1.2.2.2.1-3 show the various fields that are requested at the Study, Series, and
Image levels of the C-FIND request.

Note: In the following Tables the Type field has the following meaning:
R - Required
U - Unique
O - Optional
P - Private

Table 2.2.1.2.2.2.1-1: Requested Study Level Keys

Description Type Tag Value

Study date R 0008,0020 Zero length for any Study
date, or "yyyymmdd-

Copyright 2009 General Electric Company. All rights reserved

Page 19 of 126
 DOC0506131 rev3

Description Type Tag Value

yyyymmdd" matches
inclusive range of 'from-
to' Study dates. 'From' or
'To' date can be zero
length meaning that side
of the range is any date.
Study time R 0008,0030 Zero length
Accession number R 0008,0050 Zero length for any
Accession number, or
Accession number
matches this value
Patient’s name R 0010,0010 Zero length for any
Patient name, or
Patient's name matches
this value
Patient id R 0010,0020 Zero length for any
Patient id, or Patient id
matches this value
Study id R 0020,0010 Zero length for any Study
id, or Study id matches
this value
Study Instance UID U 0020,000D Zero length for Study
level query. Study
Instance UID of study for
which matches are
requested at a lower
level
Study description O 0008,1030 Zero length

Table 2.2.1.2.2.2.1-2: Requested Series Level Keys

Description Type Tag Value

Modality R 0008,0060 Zero length
Series number R 0020,0011 Zero length
Series Instance UID U 0020,000E Zero length for Series
level query. Series
instance UID of series for
which matches are
requested at a lower
level
Series description O 0008,103E Zero length
Manufacturer O 0008,0070 Zero length

Number of Series Related Instances O 0020,1209 Zero length

Table 2.2.1.2.2.2.1-3: Requested Image Level Keys

Description Type Tag Value

Image number R 0020,0013 Zero length
Image Instance UID U 0008,0018 Zero length
Rows O 0028,0010 Zero length
Columns O 0028,0011 Zero length
Slice thickness O 0018,0050 Zero length

Copyright 2009 General Electric Company. All rights reserved

Page 20 of 126
 DOC0506131 rev3

Description Type Tag Value

Slice spacing O 0018,0088 Zero length
Gantry tilt O 0018,1120 Zero length
Convolution kernel O 0018,1210 Zero length
Reconstruction diameter O 0018,1100 Zero length
Data collection diameter O 0018,0090 Zero length
Flip angle O 0018,1314 Zero length
Echo number O 0018,0086 Zero length
Echo time O 0018,0081 Zero length
Inversion time O 0018,0082 Zero length
Repetition time O 0018,0080 Zero length

2.2.1.2.3 Get Image(s) from Remote AE

The “Get Images from Remote AE” provides the capability for the operator to retrieve image
(MR/SC/GSPS/SR) objects from a remote storage node via a pull operation from the system console.

2.2.1.2.3.1 Associated Real-World Activity

The operator must select the Remote DICOM AE from the “Source” pull-down on the local database browser
and select the hostname of the source from where the images are to be retrieved. Once a list of
Study/Series/Image is retrieved, the operator can invoke the “Pull” operation by clicking on the “Local DB”
button at the bottom of the local database browser .

2.2.1.2.3.2 Proposed Presentation Contexts

When the Real-World activity “Get” is initiated all presentation contexts shown in Table 2.2.1.2.1.2-1 are
proposed during association establishment, but only the Query/Retrieve-MOVE related contexts are
applicable to this activity.

2.2.1.2.3.2.1 SOP Specific Conformance Statement for C-MOVE SCU

When the operator starts a Get operation at any level (Study, Series, Image) the DICOM Server AE will
initiate a C-MOVE-RQ request with UIDs at the appropriate level (Study, Series, Image) to the Remote AE
with the DICOM Server AE as the Destination AE. The Storage SCP will handle the incoming images as
described in section 2.2.1.3.1.

Each C-MOVE SCU operation supports an “Association Timer” and “Operation Inactivity Timer” with time out
values of 30 seconds and 15 seconds respectively.

The DICOM Server AE will send a C-CANCEL-MOVE-RQ to the Remote AE if the operator “Pauses” or
“Clears” the job from the local database manager Network queue.

2.2.1.2.4 DICOM Ping to Remote AE

Ping to remote AE provides the user the capability to verify that the selected remote AE is accessible across
the network and can recognize DICOM requests from this system.

2.2.1.2.4.1 Associated Real-World Activity

Copyright 2009 General Electric Company. All rights reserved

Page 21 of 126
 DOC0506131 rev3

The operator must first select a destination by choosing “Selected remote host:” from “Network” pull-down
menu on the local database manager and then choose a hostname. The operator then has to perform the
Real-World activity “Choose DICOM PING” to send a C-ECHO request to get the status of the Remote AE.

If the C-ECHO response is received with a success, the DICOM Server will post a pop-up to the operator
indicating that the remote device is alive.

2.2.1.2.4.2 Presentation Context Table

Table 2.2.1.3.2.2-1: Acceptable Presentation Contexts for DICOM Server AE and Real-World Activity
DICOM Ping

Presentation Context Table

Abstract Syntax Transfer Syntax Role Extended
Negotiation
Name UID Name List UID List
Verification 1.2.840.10008.1.1 Implicit VR Little 1.2.840.10008.1.2 SCU None
Endian

2.2.1.2.4.2.1 SOP Specific Conformance Statement to Verification SOP Class

The DICOM Server AE provides standard conformance to the DICOM Verification Service Class.

Each ECHO operation supports supports “Association Timer” with EchoAssociationTimeout, in network-
cfg.xml configuration file. Default values are 20 seconds

Upon receiving a C-ECHO-RSP, containing a successful status, a message will be posted to the operator
indicating success.

2.2.1.2.5 Save exam/series to Remote AE

The user selects the exam/series to be committed. All the images currently in the selected exam/series will
be sent to the selected remote archive node(which is also the Storage commitment SCP) using DICOM C-
STORE operations. Once all the images are transferred the commitment request will be sent on a separate
association.

2.2.1.2.6 Auto Archive exam/series to Remote AE

The Auto archive user interface is used to archive the exams/series onto local archive media or the remote
archive node ( which shall be a Storage Commitment SCP) without manual interface. If the default device
selected for Auto Archive is a remote Storage Commitment SCP then all the images currently in the specified
exam/series will be sent to the selected Storage commitment SCP using C-STORE operations. On
successful transfer of all the images the Storage Commitment request will be sent. See Section 7 for more
information.

2.2.1.3 Association Acceptance Policy

The DICOM Server AE has to have the Remote DICOM AE as a configured destination for it be able to
communicate with it.

When the DICOM Server AE accepts an association for image storage, it will receive any images transmitted
on that association and store the images on disk.

Copyright 2009 General Electric Company. All rights reserved

Page 22 of 126
 DOC0506131 rev3

It will also respond to queries from Remote AEs by sending matching entries. Any Remote AE can request
and receive a list of images on the local database. The Remote AE must be configured in the local database
manager’s list of Remote AE for it to be able to retrieve images from DICOM Server AE.

Any remote AE can open an association to the DICOM Server AE for the purpose of verification.

2.2.1.3.1 Receive Image(s)

This AE is indefinitely listening for associations. No operator action is required to receive an image.

2.2.1.3.1.1 Associated Real-World Activity

The Real-World Activity associated with the Receive Image(s) operation is the storage of the image on the
disk drive of the GE MR system.
The acceptable Presentation Contexts for DICOM Server AE and Real-World Activity Receive Image(s) is
given in the following Presentation Context Table.

Table 2.2.1.3.1.2-1: Presentation Contexts for Image Receive

Presentation Context Table

Abstract Syntax Transfer Syntax Role Extended
Negotiation
Name UID Name List UID List
Verification 1.2.840.10008.1.1 Implicit VR Little 1.2.840.10008.1.2 SCP None
Endian
CT Image Storage 1.2.840.10008.5.1.4.1.1.2 Implicit VR Little 1.2.840.10008.1.2 SCP None
Endian
CT Image Storage 1.2.840.10008.5.1.4.1.1.2 Explicit VR Little 1.2.840.10008.1.2.1 SCP None
Endian
CT Image Storage 1.2.840.10008.5.1.4.1.1.2 Explicit VR Big 1.2.840.10008.1.2.2 SCP None
Endian
MR Image 1.2.840.10008.5.1.4.1.1.4 Implicit VR Little 1.2.840.10008.1.2 SCP None
Storage Endian
MR Image 1.2.840.10008.5.1.4.1.1.4 Explicit VR Little 1.2.840.10008.1.2.1 SCP None
Storage Endian
MR Image 1.2.840.10008.5.1.4.1.1.4 Explicit VR Big 1.2.840.10008.1.2.2 SCP None
Storage Endian
PET Image 1.2.840.10008.5.1.4.1.1.128 Implicit VR Little 1.2.840.10008.1.2 SCP None
Information Endian
Storage
PET Image 1.2.840.10008.5.1.4.1.1.128 Explicit VR Little 1.2.840.10008.1.2.1 SCP None
Information Endian
Storage
PET Image 1.2.840.10008.5.1.4.1.1.128 Explicit VR Big 1.2.840.10008.1.2.2 SCP None
Information Endian
Storage
RT Structure Set 1.2.840.10008.5.1.4.1.1.481 Implicit VR Little 1.2.840.10008.1.2 SCP None
Storage .3 Endian
RT Structure Set 1.2.840.10008.5.1.4.1.1.481 Explicit VR Little 1.2.840.10008.1.2.1 SCP None
Storage .3 Endian
RT Structure Set 1.2.840.10008.5.1.4.1.1.481 Explicit VR Big 1.2.840.10008.1.2.2 SCP None
Storage .3 Endian
GEMS PET Raw 1.2.840.113619.4.30 Implicit VR Little 1.2.840.10008.1.2 SCP None
Information Endian
Storage
GEMS PET Raw 1.2.840.113619.4.30 Explicit VR Little 1.2.840.10008.1.2.1 SCP None
Information Endian
Storage
GEMS PET Raw 1.2.840.113619.4.30 Explicit VR Big 1.2.840.10008.1.2.2 SCP None
Information Endian
Storage
Secondary 1.2.840.10008.5.1.4.1.1.7 Implicit VR Little 1.2.840.10008.1.2 SCP None
Capture Endian

Copyright 2009 General Electric Company. All rights reserved

Page 23 of 126
 DOC0506131 rev3

Secondary 1.2.840.10008.5.1.4.1.1.7 Explicit VR Little 1.2.840.10008.1.2.1 SCP None

Capture Endian
Secondary 1.2.840.10008.5.1.4.1.1.7 Explicit VR Big 1.2.840.10008.1.2.2 SCP None
Capture Endian
Enhanced 1.2.840.10008.5.1.4.1.1.88. Implicit VR Little 1.2.840.10008.1.2 SCP None
Structured Report 22 Endian

Enhanced 1.2.840.10008.5.1.4.1.1.88. Explicit VR Little 1.2.840.10008.1.2.1 SCP None

Structured Report 22 Endian

Enhanced 1.2.840.10008.5.1.4.1.1.88. Explicit VR Big 1.2.840.10008.1.2.2 SCP None

Structured Report 22 Endian

Note: The SCP does not have a default acceptance policy if more than one acceptable transfer syntaxes are
proposed by the SCU. It is the responsibility of the SCU to make a selection from more than one transfer
syntaxes accepted. If multiple transfer syntaxes are proposed in the same presentation context, the SCP will
accept the first one.

2.2.1.3.1.1.1 SOP Specific Conformance to Storage SOP Classes

The DICOM Server AE conforms to the SOP’s of the Storage Service Class at level 1 (base).

Each C-STORE SCP operation supports an “Association Timer” and “Operation Inactivity Timer” with time
out values of 30 seconds and 15 seconds respectively.

Image Reception

If the DICOM Server AE returns one of the following status codes, then the C-STORE operation was
unsuccessful and no image will be installed:

0110 (Processing Failure) Indicates that an internal system call has failed while processing an image.

A700 (Out of Resources) Indicates that probably there was not enough disk space to store the image. The
user should attempt recovery by removing some images from the GE MR system.

A700 (Out of Resources) Indicates that there was not enough resource (such as memory) to store the
image.

In the event of a successful C-STORE operation, the image has successfully been written to disk. The image
will then be accessed in the same manner as any other image by the applications on the GE MR system.

Images may be deleted when instructed to do so by the user. Thus the duration of the storage of the image
is determined by the users of the GE MR system.

Image Installation

If the image installation is unsuccessful, a message will appear in the Message Log informing the user of the
failure and the image will be removed.

If the image installation process finds that an element is not encoded according to the DICOM standard, it
will fail to install the image and the file will be removed.

Image Installation of non-GE Created MR or CT Images

Copyright 2009 General Electric Company. All rights reserved

Page 24 of 126
 DOC0506131 rev3

Images received from non GE products are installed as the appropriate image object. Their private data
elements will be maintained if the negotiated transfer syntax is Explicit Little or Big Endian. Also if any
critical fields (mandatory) are missing, then the image will not be installed.

2.2.1.3.2 Verification Request from Remote AE

This AE is indefinitely listening for associations. No operator action is required to respond to a verification
message.

2.2.1.3.2.1 Associated Real-World Activity

The Real-World Activity associated with the verification request is to send a C-ECHO response message
with a status of “success” to the requesting AE.

2.2.1.3.2.2 Presentation Context Table

Table 2.2.1.3.2.2-1: Acceptable Presentation Contexts for DICOM Server AE and Real-World Activity
Verification Request

Presentation Context Table

Abstract Syntax Transfer Syntax Role Extended
Negotiation
Name UID Name List UID List
Verification 1.2.840.10008.1.1 Explicit VR Little 1.2.840.10008.1.2.1 SCP None
Endian
Verification 1.2.840.10008.1.1 Explicit VR Big 1.2.840.10008.1.2.2 SCP None
Endian
Verification 1.2.840.10008.1.1 Implicit VR Little 1.2.840.10008.1.2 SCP None
Endian

2.2.1.3.2.2.1 SOP Specific Conformance to Verification SOP Class

The DICOM Server AE provides standard conformance to the DICOM Verification Service Class.

Each ECHO operation supports an “Association Timer” and “Operation Inactivity Timer” with a time out
values of 30 seconds and 15 seconds respectively.

2.2.1.3.3 Query Request from Remote AE

This AE is indefinitely listening for associations. No operator action is required to respond to a query request.

2.2.1.3.3.1 Associated Real-World Activity

The Real-World Activity associated with the query request is to search the local database for entries that
match the request and send a C-FIND response message with a status of “pending” for each matching entry.

Copyright 2009 General Electric Company. All rights reserved

Page 25 of 126
 DOC0506131 rev3

2.2.1.3.3.2 Presentation Context Table

Table 2.2.1.3.1.2-1: Acceptable Presentation Contexts for DICOM Server AE and Real-World Activity Query Request
Presentation Context Table
Abstract Syntax Transfer Syntax Role Extended
Negotiation
Name UID Name List UID List
Study Root 1.2.840.10008.5.1.4.1.2.2. Explicit VR Little 1.2.840.10008.1.2.1 SCP None
Query/Retrieve 1 Endian
FIND
Study Root 1.2.840.10008.5.1.4.1.2.2. Explicit VR Big 1.2.840.10008.1.2.2 SCP None
Query/Retrieve 1 Endian
FIND
Study Root 1.2.840.10008.5.1.4.1.2.2. Implicit VR Little 1.2.840.10008.1.2 SCP None
Query/Retrieve 1 Endian
FIND

2.2.1.3.3.2.1 SOP Specific Conformance to C-FIND SCP

Each C-FIND SCP operation supports an “Association Timer” and “Operation Inactivity Timer” with a time out
values of 30 seconds and 15 seconds respectively.

All Required( R) and Unique(U) study, series, and image level keys for the Study-Root Query/Retrieve
information model are supported. Some optional (O) keys are also supported as described in the following
tables.
Note:
In the following tables the Type field has the following meaning:
R - Required U - Unique O - Optional P - Private

Only keys with Usage type Matched will be matched against values in the database.

Values in keys of type Returned will be ignored and will be filled in with data from the database.

If an optional key is requested that does not appear in any of the tables above, that key will be ignored and
no corresponding element will be returned.

If the database does not have a value corresponding to any requested optional key a zero-length element
will be returned.

Except sequence matching all other matchings are supported. (i.e. wildcard (“*”, “?”) and range (“-“)
matching is supported as defined in DICOM PS3.4 Section C.2 Query/Retrieve Information Model Definition.)

Only hierarchical query is supported. Therefore, the C-FIND SCP will not perform any extended negotiation.

Copyright 2009 General Electric Company. All rights reserved

Page 26 of 126
 DOC0506131 rev3

Table 2.2.1.3.3.2.1-1 Supported Study Level Keys

Description Type Tag Usage

Study date R 0008,0020 Matched
Study time R 0008,0030 Matched
Accession number R 0008,0050 Matched
Patient’s name R 0010,0010 Matched
Patient id R 0010,0020 Matched
Study id R 0020,0010 Matched
Study Instance UID U 0020,000D Matched
Study description O 0008,1030 Returned

Note: The local database does not store the different components of the patient’s name in separate fields
so it is not possible to query for studies by last name or any other component.

Table 2.2.1.3.3.2.1-2 Supported Series Level Keys

Description Type Tag Usage

Modality R 0008,0060 Matched
Series number R 0020,0011 Matched
Series Instance UID U 0020,000E Matched
Number of Series Related Instances U 0020,1209 Matched
Series description O 0008,103E Returned
Manufacturer O 0008,0070 Returned
Images in Acquisition * O 0020,1002 Returned
* Images in Acquisition is filled with number of images in series from legacy GE SCPs, hence series level is
used.
Table 2.2.1.3.3.2.1-3 Supported Image Level Keys

Description Type Tag Usage

Image number R 0020,0013 Matched
Image Instance UID U 0008,0018 Matched
Image type O 0008,0008 Returned
Rows O 0028,0010 Returned
Columns O 0028,0011 Returned
Image position O 0020,0032 Returned
Image orientation O 0020,0037 Returned
Slice thickness O 0018,0050 Returned
Slice spacing O 0018,0088 Returned
Gantry tilt *CT field O 0018,1120 Returned
Convolution kernel *CT field O 0018,1210 Returned
Reconstruction diameter O 0018,1100 Returned
Data collection diameter *CT field O 0018,0090 Returned
Flip angle O 0018,1314 Returned
Echo number O 0018,0086 Returned
Echo time O 0018,0081 Returned
Repetition time O 0018,0080 Returned
Private Creator Identification P 0027,0010 GEMS_IMAG_01
Location RAS P 0027,1040 Returned
Location P 0027,1041 Returned
Image Dimension X P 0027,1060 Returned
Image Dimension Y P 0027,1061 Returned

Copyright 2009 General Electric Company. All rights reserved

Page 27 of 126
 DOC0506131 rev3

2.2.1.3.4 Retrieve Request From Remote AE

This AE is indefinitely listening for associations. No operator action is required to respond to a retrieve
request.

2.2.1.3.4.1 Associated Real-World Activity

The Real-World Activity associated with the Retrieve Request is to send all images corresponding to the C-
MOVE request to the destination AE through a separate association.

2.2.1.3.4.2 Presentation Context Table

Table 2.2.1.3.4.2-1: Acceptable Presentation Contexts for DICOM Server AE and Real-World Activity
Retrieve Request.

Presentation Context Table

Abstract Syntax Transfer Syntax Role Extended
Negotiation
Name UID Name List UID List
Study Root 1.2.840.10008.5.1.4.1.2.2. Explicit VR Little 1.2.840.10008.1.2.1 SCU None
Query/Retrieve 2 Endian
MOVE
Study Root 1.2.840.10008.5.1.4.1.2.2. Explicit VR Big 1.2.840.10008.1.2.2 SCU None
Query/Retrieve 2 Endian
MOVE
Study Root 1.2.840.10008.5.1.4.1.2.2. Implicit VR Little 1.2.840.10008.1.2 SCU None
Query/Retrieve 2 Endian
MOVE

2.2.1.3.4.2.1 SOP Specific Conformance to C-MOVE SCP

The DICOM Server AE provides standard conformance to the baseline Study-root C-MOVE Service Class
SCP.

Each C-MOVE SCP operation supports an “Association Timer” and “Operation Inactivity Timer” with a time
out values of 30 seconds and 15 seconds respectively.

All images requested in a C-MOVE-RQ will be sent over a single association. A C-MOVE-RSP with a
“pending” status will be returned to the requester every five images.

The C-MOVE SCP will invoke C-STORE requests for the following SOP classes:

Copyright 2009 General Electric Company. All rights reserved

Page 28 of 126
 DOC0506131 rev3

SOP Class Name SOP Class UID

CT Image Information Storage 1.2.840.10008.5.1.4.1.1.2
MR Image Information Storage 1.2.840.10008.5.1.4.1.1.4
PET Image Information Storage 1.2.840.10008.5.1.4.1.1.128
RT Structure Set Storage 1.2.840.10008.5.1.4.1.1.481.3
GEMS PET Raw Information Storage 1.2.840.113619.4.30
Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7
Grayscale Softcopy Presentation State Storage 1.2.840.10008.5.1.4.1.1.11.1
Enhanced Structured Report 1.2.840.10008.5.1.4.1.1.88.22

In addition to the C-MOVE response status values defined in DICOM part 4 the following status values will
be returned:

• C000 - Indicates that an error occurred while retrieving records from the local database.
• C001 - Indicates all other processing error.
• C011 - If the Destination AE returns a “Storage Full” condition this status will be returned. This status will
only be sent if the Destination AE returns a status of A711 and is only applicable if the Destination AE is
an SdC-based product.

2.2.1.3.4.3 Presentation Context Acceptance Criteria

No criterion.

2.2.1.3.4.4 Transfer Syntax Selection Policy

The SCP does not have a default acceptance policy if more that one acceptable transfer syntaxes are
proposed for the same SOP class (in separate presentation contexts). It is the responsibility of the SCU to
make a selection from the list of accepted presentation contexts that apply to any particular SOP class. If
multiple transfer syntaxes are proposed in the same presentation context, the SCP will accept the first one.

2.3 COMMUNICATION PROFILES

2.3.1 Supported Communication Stacks (parts 8,9)

DICOM Upper Layer (Part 8) is supported using TCP/IP.

2.3.2 TCP/IP Stack

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

2.3.2.1 Physical Media Support

Ethernet v2.0, IEEE 802.3.

2.4 EXTENSIONS / SPECIALIZATIONS / PRIVATIZATIONS

2.4.1 Specialized Information Object Definition

Copyright 2009 General Electric Company. All rights reserved

Page 29 of 126
 DOC0506131 rev3

Following is a list of additional GE specific attributes for (0008,0008) and (0018,0022) defined for a standard
MR IOD. For incoming third-party DICOM images the values in these elements are retained without
modification.
rd th
(0008,0008) Image Types (private attributes for 3 and 4 values)

Acquisition Data Types:

ORIGINAL\PRIMARY\OTHER
ORIGINAL\PRIMARY\OTHER\SUBTRACTION
ORIGINAL\PRIMARY\EPI\NONE
ORIGINAL\PRIMARY\T2\NONE
ORIGINAL\PRIMARY\PROPELLER\NONE
ORIGINAL\PRIMARY\DIFFUSION\NONE
ORIGINAL\PRIMARY\CARDIACREALTIME\NONE
ORIGINAL\PRIMARY\CARDIAC\NONE
DERIVED\PRIMARY\PROJECTION IMAGE\COLLAPSE
DERIVED\PRIMARY\PROJECTION IMAGE\VASCULAR

Post Processed Data Types:

DERIVED\PRIMARY\ADC\ADC
DERIVED\PRIMARY\CMB\CMB
DERIVED\PRIMARY\EADC\EADC
DERIVED\PRIMARY\PROJECTION IMAGE\IVI
DERIVED\PRIMARY\VAR\VAR
DERIVED\SECONDARY\COMBINED
DERIVED\SECONDARY\PROCESSED
DERIVED\SECONDARY\OTHER\SCREEN SAVE
DERIVED\SECONDARY\PJN
DERIVED\SECONDARY\PJN\MIP
DERIVED\SECONDARY\PJN\HD MIP
DERIVED\SECONDARY\PJN\MIN IP
DERIVED\SECONDARY\PJN\RAYSUM
DERIVED\SECONDARY\PJN\INTEGRAL
DERIVED\SECONDARY\REFORMATTED
DERIVED\SECONDARY\REFORMATTED\MIP
DERIVED\SECONDARY\REFORMATTED\MIN IP
DERIVED\SECONDARY\REFORMATTED\AVERAGE
DERIVED\SECONDARY\REFORMATTED\VOLREN
DERIVED\SECONDARY\3D
DERIVED\SECONDARY\3D\SURFACE
DERIVED\SECONDARY\3D\MIP
DERIVED\SECONDARY\3DHD MIP
DERIVED\SECONDARY\3D\MIN IP
DERIVED\SECONDARY\3D\VOLREN
DERIVED\SECONDARY\3D\RAYSUM
DERIVED\SECONDARY\3D\INTEGRAL
DERIVED\SECONDARY\SCREEN SAVE
DERIVED\SECONDARY\SCREEN SAVE\MIP
DERIVED\SECONDARY\SCREEN SAVE\MIN IP
DERIVED\SECONDARY\SCREEN SAVE\AVERAGE
DERIVED\SECONDARY\SCREEN SAVE\VOLREN

(0018,0022) Scan Options : Defined Terms

Copyright 2009 General Electric Company. All rights reserved

Page 30 of 126
 DOC0506131 rev3

NONE RAMP_AP_GEMS
CINE_GEMS RAMP_IS_GEMS
CL_GEMS RAMP_LR_GEMS
CS_GEMS RAMP_PA_GEMS
DEP_GEMS RAMP_RL_GEMS
EDR_GEMS RAMP_SI_GEMS
EPI_GEMS RT_GEMS
FAST_GEMS RTR_GEMS
FC_FREQ_AX_GEMS SAT_GEMS
FC_SLICE_AX_GEMS SEQ_GEMS
FILTERED_GEMS SQPIX_GEMS
FT_GEMS SS_GEMS
GRAPH_GEMS TRF_GEMS
IIC_GEMS VASCANGIO_GEMS
IRP_GEMS VASCPC_GEMS
MP_GEMS VASCPC_GEMS
MT_GEMS VASCTOF_GEMS
NF_GEMS VASCTOF_GEMS
NPW VB_GEMS
POMP_GEMS MART_GEMS
SPIRAL_GEMS PROP_GEMS
VRG_GEMS ARTM_GEMS
ARTH_GEMS

Also refer to section A.3.15 for standard DICOM elements that are not part of the MR IOD.

2.4.2 Private Data Elements

Refer to Appendix B for a complete listing of private data elements used with this implementation.

2.5 CONFIGURATION

2.5.1 AE Title/Presentation Address Mapping

The GE MR system allows the user to “Add”, “Remove”, or “Edit” the mapping of remote AE Titles to IP
Addresses and Ports. These options can be selected from the “Network Configuration” dialog box displayed
by choosing “Network Configuration” from the “Tools” pull-down menu from the local database browser.

2.5.2 Configurable Parameters

The following fields are configurable for the DICOM Server AE:
• Local AE Title (the machine hostname)
• Local IP Address
• Local IP Netmask
• Max PDU length
• Timeouts are set in network-cfg.xml and mergecom.pro files.
note: * denotes any SOP class (time in sec)
* Association time-out - ARTIM_TIMEOUT
* Inactivity time-out - INACTIVITY_TIMEOUT
* Move operation time-out - RetrieveAssociationTimeout
* Find time-out - QueryAssociationTimeout

Copyright 2009 General Electric Company. All rights reserved

Page 31 of 126
 DOC0506131 rev3

* Store time-out - StoreAssociationTimeout

Note: All configurations should be performed by a GE Field Service Engineer.

Note: The local port on which the GE MR system receives DICOM incoming TCP connections is port 4006.

2.6 SUPPORT OF EXTENDED CHARACTER SETS

In addition to the DICOM default character set, the GE MR system supports the ISO IR 100 Latin alphabet
#1 supplementary set for the purpose of interchange.

2.7 CODES AND CONTROLLED TERMINOLOGY

The product does not use any special coded terminology.

2.8 SECURITY PROFILES

The product does not conform to any defined DICOM Security Profiles.
It is assumed that the product is used within a secured environment. It is assumed that a secured
environment includes at a minimum:
1. Firewall or router protections to ensure that only approved external hosts have network access
to the product.
2. Firewall or router protections to ensure that the product only has network access to approved
external hosts and services.
3. Any communications with external hosts and services outside the locally secured environment
use appropriate secure network channels (such as a Virtual Private Network (VPN))

Copyright 2009 General Electric Company. All rights reserved

Page 32 of 126
 DOC0506131 rev3

3 MEDIA STORAGE CONFORMANCE STATEMENT

3.0 Introduction
This Conformance Statement specifies the GE MR system’s compliance to DICOM Media Interchange. It
details the DICOM Media Storage Application Profiles and roles which are supported by this product.
The GE MR system provides capabilities to DICOM interchange on CD-R (Compact Disc-Recordable) and
DVD-R(Digital Video Disc –Recordable). The GE MR system works with most of the IOD’s like Computed
Tomography (CT), Magnetic Resonance (MR), Computed Radiography (CR), Positron Emission
Tomography (PET), and Digital X-Ray images.

Note the format of this section follows the format of the DICOM Standard Part 2 (conformance) Annex C
hence the paragraph numbering scheme. Please refer to that part of the standard while reading this section.

3.1 IMPLEMENTATION MODEL

The DICOM Interchange Archive Server Application Entity (AE) handles all DICOM media storage
functionality on the GE MR system. The DICOM Interchange Archive Server AE is commanded to perform
DICOM services through the buttons and menu selections on the user interface. It also uses the appropriate
recorders to provide the service Interchange Media profiles.

3.1.1 Application Data Flow Diagram

The Basic and Specific Application models for the CD-R/DVD-R devices are shown in the following
Illustrations.

SPECIFIC AE APPLICATION MODEL FOR THE CD-R/DVD-R DEVICE

• Description of the Data Flow Diagram for the CD-R/DVD-R device.

The DICOM Interchange Archive Server Application Entity (AE) handles the DICOM CREATE CD (/DVD) /
RESTORE CD (/DVD) functionality for the CD-R/DVD-R media. The DICOM Interchange Archive Server
Application Entity (AE) is commanded by the user to perform DICOM services operating on the DICOM
media through the use of buttons and menu selections on the graphical user interface of the platform.

The user requests the creation of a DICOM File Set and the writing of this DICOM File Set on blank
Interchange Media by selecting images in the local Browser and selecting the Interchange Media as being
the selected device. Then, the iso9660 image of the CD/DVD to burn will be generated. Once the generation
has been done, it burns the complete set of data on the selected Interchange Media.

The Media Interchange Application Model for the GE MR system is shown in Illustration 3-1:

Copyright 2009 General Electric Company. All rights reserved

Page 33 of 126
 DOC0506131 rev3

CD/DVD DICOM Interchange Archive Server AE Model

Illustration 3-1

Display
Directory/
QUERY FSC
DICOM
Archive Media
Server
Recorder 1 Storage 2

FSR
Local Storage/
RESTORE

FSC
Recorder 2 Media
Storage 1
FSR
Record Media/
RECORD

The DICOM Interchange Archive Server AE has a local storage that may contain various SOP instances.
These may have been obtained by original creation, network (DICOM or proprietary) or by removable media
using other application entities. These instances are external to this conformance claim and the origin of
SOP instances is outside the scope of this claim.

The DICOM Interchange Archive Server AE can initialize Media by acting as an FSC to create a new DICOM
File-set on a 700MB/4.7GB blank Interchange Media. It initializes the DICOM File-set and writes all the
specified SOP instances onto the Interchange Media at once. The SOP instances written will be limited to
instances that match the criteria of one of the Application Profiles that is supported. Updating the media is
not supported.

3.1.2 Functional Definitions of AE's

3.1.2.1 Functional Definition of the CD-R/DVD-R DICOM Media Server AE

The CD-R/DVD-R DICOM Interchange Archive Server Application Entity supports the following functions:
• Generate and write a DICOM File Set (FSC) in a one shot activity. (SAVE).
• Read a DICOM File Set (FSR) on a Interchange Media (QUERY).
• It can copy SOP instances from the media onto local storage. (RESTORE).

3.1.3 Sequencing Requirements

3.1.3.1 Sequencing of CD-R/DVD-R Real World Activities

The display function (QUERY) can only be performed on a piece of media that already has a DICOM File-set
created. With no SOP instances having been added, the directory will be displayed empty.

The save function can only be performed on a blank (unused) Interchange Media. Updates to an already
recorded Interchange Medium is not supported.

There are no other sequencing requirements.

Copyright 2009 General Electric Company. All rights reserved

Page 34 of 126
 DOC0506131 rev3

3.2 AE SPECFICIATIONS

3.2.1 DICOM CD-R/DVD-R Interchange Archive Server AE Specification

The DICOM CD-R/DVD-R Interchange Archive Server AE provides standard conformance to DICOM
Interchange Option of the Media Storage Service Class. The supported Application Profiles and roles are
listed below.
Table 3-1 DICOM CD-R/DVD-R Supported Application Profiles
Supported Application Profile Real World Activity Role Option
STD-GEN-CD CREATE CD FSC Interchange

STD-GEN-CD QUERY CD FSR Interchange

STD-GEN-CD RESTORE CD FSR Interchange
STD-GEN-DVD-JPEG CREATE DVD FSC Interchange
STD-GEN-DVD-JPEG QUERY DVD FSR Interchange
STD-GEN-DVD-JPEG RESTORE DVD FSR Interchange

Note: JPEG compressed images are supported for DVD restore only

3.2.1.1 File Meta Information for the CD-R/DVD-R DICOM Interchange Archive
Server Application Entity
Following are the values set in the File Meta Information for this AE Title. Please refer to Section 1.1 for
details on specific GE MR system information.

Source Application Entity Title ARCHIVE

Implementation UID See section 1.1
Implementation version name See section 1.1

3.2.1.2 Real-World Activities for the CD-R/DVD-R DICOM Interchange Archive

Server Application Entity

3.2.1.2.1 Real-World Activity (RWA) Create (Generate and Write) CD/DVD

The DICOM Media Server acts as an FSC using the interchange option when requested to copy
SOP Instances from the local database to a CD-R/DVD-R.

The user selects the entries in the local database that he/she wants the DICOM Media Server to
copy onto Interchange Media.

The graphic interface allows the user to select the entries (patients, studies, series or images) in the
local database to be copied onto to the selected Interchange Media.

The DICOM Media Server creates one File Set per generated Interchange Media.
• A user can only create one copy of CD/DVD image for a drive at a time; any other attempt of
creation will wait until the first one is complete.
• A user cannot create CD/DVD while restore CD/DVD is in process.
• A DICOM CD-Viewer is provided along with the selected object instances on the
interchange media. This viewer can be loaded on a standard PC running Windows2000 or
WindowsXP.

Before writing on the Interchange Medium, the DICOM Media Server checks for the following
condition:

Copyright 2009 General Electric Company. All rights reserved

Page 35 of 126
 DOC0506131 rev3

• The inserted media is blank and write-able. If the condition is not met, an error is displayed
and the user needs to replace it with a blank media.
Note:
Since JPEG compression is not enabled, the transfer syntax for SOP Instances will always be
Explicit VR Little Endian (ELE) Uncompressed Transfer Syntax, UID 1.2.840.10008.1.2.1. For any
other IODs with Transfer syntax other than ELE, the corresponding SOP instance data are
converted to ELE and then copied to CD/DVD. During the conversion to ELE, the private tags are
stored with VR as UN if the syntax is implicit to facilitate fidelity.

The Object SOP instances have to be encoded with the ISO_IR 100 Specific Character set or
DICOM Default Character Set.

3.2.1.2.1.1 Application Profiles for the RWA: Create CD/DVD

For the list of Application Profiles that invoke this AE for the Create CD /DVD RWA.

3.2.1.2.1.1.1 Options for STD-GEN-CD and STD-GEN-DVD-JPEG Application Profile:

Following are the SOP Classes supported by the RWA “Create CD/DVD”. All SOP Instances use
the Explicit VR Little Endian Uncompressed Transfer Syntax, UID 1.2.840.10008.1.2.1. for creating
CD/DVD.

Copyright 2009 General Electric Company. All rights reserved

Page 36 of 126
 DOC0506131 rev3

SOP Class SOP Class UID

CT Image Storage 1.2.840.10008.5.1.4.1.1.2
MR Image Storage 1.2.840.10008.5.1.4.1.1.4
PET Image Information Storage 1.2.840.10008.5.1.4.1.1.128
RT Structure Set Storage 1.2.840.10008.5.1.4.1.1.481.3
GEMS PET Raw Information Storage 1.2.840.113619.4.30
Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7
Grayscale Softcopy Presentation State Storage 1.2.840.10008.5.1.4.1.1.11.1
Enhanced Structured Report 1.2.840.10008.5.1.4.1.1.88.22

3.2.1.2.1.1.2 FSC Directory Options

The DICOMDIR Directory Records created by RWA “Create CD/DVD” will include key attributes as
described in Appendix C.

3.2.1.2.2 Real-World Activity (RWA) Display Directory -QUERY

The DICOM Media Server AE acts as an FSR using the interchange option when requested to
browse the Interchange Media.

When the DICOM Media Server AE is requested to provide a directory listing, it reads the File-set
and displays the DICOMDIR directory entries, according to the STUDY Root paradigm.

If the media is not blank, then Interchange Media gets mounted. To remove the media, the user has
to select the eject button on user interface for the appropriate drive.

A user can display the directory even when create/restore CD/DVD is in progress. During a create
CD/DVD operation, the results of the QUERY will show everything that will be saved on the CD,
once the create operation is over. It does reflect the actual contents of the CD/DVD until the create
CD/DVD operation is over.

3.2.1.2.2.1 Application Profiles for the RWA: Display Directory

For the list of Application Profiles that invoke this AE for the Display Directory CD/DVD RWA, see
the Table in Section 3.2.1.2.2.2 below.

3.2.1.2.2.2 Media Storage Application Profile for the RWA: Display Directory
Following are the SOP Classes supported by the RWA “Display Directory of CD/DVD”:

Information SOP Class UID Transfer Syntax Transfer Syntax

Object UID
Definition
Media 1.2.840.10008.1.3.10 Explicit VR Little 1.2.840.10008.1.2.1
Storage Endian
Directory
Storage

3.2.1.2.3 Real-World Activity (RWA): Restore CD/DVD

The CD-R/DVD-R DICOM Interchange Archive Server AE acts as an FSR using the interchange
option when requested to copy SOP instances from the CD/DVD to the local database.

Copyright 2009 General Electric Company. All rights reserved

Page 37 of 126
 DOC0506131 rev3

The user selects the SOP instances that he wants the DICOM Media Server AE to copy on the local
database by selecting appropriate P/E/S/I instances and clicking on the suitable restore buttons.
Once selected, the SOP instances are copied from the media to the local database.

If the media is not blank, then the Interchange Media gets mounted. To remove the media, the user
has to select the eject button on the User Interface for the appropriate drive.

A user cannot restore CD/DVD while create CD/DVD is in process.

A user can only restore selected composite objects at a time from a media; any other attempt of
selections to restore CD/DVD on media in same drive will wait until the first one is completed.

3.2.1.2.3.1 Application Profiles for the RWA: Restore CD-R/DVD-R

For the list of Application Profiles that invoke this AE for the Restore RWA, see the Table in Section
3.2.1.2.3.1.1 below.

3.2.1.2.3.1.1 Options for STD-GEN-CD and STD-GEN-DVD-JPEG Application Profile

Following are the SOP Classes supported by the RWA “Restore CD/DVD”. All SOP Instances use
the Explicit VR Little Endian Uncompressed Transfer Syntax, UID 1.2.840.10008.1.2.1 for Restore
CD/DVD. Compressed images on a DVD, with only the following formats are decompressed before
restoring to the local database:

1.2.840.10008.1.2.4.70, 1.2.840.10008.1.2.4.50 and 1.2.840.10008.1.2.4.51

SOP Class SOP Class UID

CT Image Storage 1.2.840.10008.5.1.4.1.1.2
MR Image Storage 1.2.840.10008.5.1.4.1.1.4
PET Image Information Storage 1.2.840.10008.5.1.4.1.1.128
RT Structure Set Storage 1.2.840.10008.5.1.4.1.1.481.3
GEMS PET Raw Information Storage 1.2.840.113619.4.30
Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7
Grayscale Softcopy Presentation State Storage 1.2.840.10008.5.1.4.1.1.11.1
Enhanced Structured Report 1.2.840.10008.5.1.4.1.1.88.22

3.2.2 File Meta Information for Implementation Class and Version

The File Meta-Information for this implementation is given below. Please refer to Section 1.1 for details on
specific GE MR system information.

File Meta-Information Version 1

Product name and See Section 1.1
Implementation UID
Implementation Version Name <Software Release Build (varies)>

Copyright 2009 General Electric Company. All rights reserved

Page 38 of 126
 DOC0506131 rev3

3.3 Standard, Augmented and Private Application Profiles

3.3.1 Class and Profile Identification

The Class of Application Profiles defined here is for Computed Tomography and Magnetic Resonance
Imaging Clinical applications.
The specific Application Profile in this class is shown below:
Table 3-3 CT/MR Profiles

Application Profile Identifier Description

CT/MR Studies on CD-R STD-GEN-CD Handles single 12 or 16 bit
grayscale uncompressed
images.
CT/MR Studies on DVD-R STD-GEN-DVD-JPEG Handles single 12 or 16 bit
grayscale compressed /
uncompressed images.

3.3.2 Clinical Contexts

This Application Profile facilitates the interchange of primary CT and MR images as well as processed CT
and MR images such as Secondary Capture, Grayscale Softcopy Presentation State, and Structured Report.
Please refer to Appendix A for the IOD definitions. CT, MR, SC, GSPS, and SR objects may co-exist within
the same File-set.
Typical interchanges would be between acquisition devices, archives and workstations within and between
institutions.

3.3.2.1 Roles and Service Class Options

This Application Profile Class uses the Media Storage Service Class defined in PS3.4 with the Interchange
Option.
The Application Entity shall support one or more roles of the File-set Creator, File-set Reader and File-set
Updater defined in PS3.10.

3.3.2.1.1 File Set Creator

The Application Entity acting as a File-set Creator generates a File Set under the Application Profiles listed in
Table 3-3. Typical entities using this role would include CT or MR equipment and archive systems which
generate a patient record to transfer to another institution. File Set Creator shall be able to generate the
Basic Directory SOP Class in the DICOMDIR File with all types of Directory Records related to the SOP
Classes stored in the File-set.

3.3.2.1.2 File Set Reader

The role of File Set Reader is used by the Application Entities which receive a transferred File Set. Typical
entities using this role would include display workstations and archive systems which receive a patient record
transferred from another institution. File Set Readers shall be able to read all the SOP Classes defined for
the specific Application Profile for which a Conformance Statement is made using all the defined Transfer
Syntaxes.

3.3.2.1.3 File Set Updater

Copyright 2009 General Electric Company. All rights reserved

Page 39 of 126
 DOC0506131 rev3

The role of File Set Updater is used by Application Entities which receive a transferred File Set and update it
by the addition of information. Typical entities using this role would include analytic workstations which for
instance may add to the File-set an information object containing a processed (e.g., edge-enhanced) image.
File-set Updaters do not have to read the images. File-set Updaters shall be able to generate one or more of
the SOP Instances defined for the specific Application Profile for which a conformance statement is made
and to read and update the DICOMDIR file.
The FSU role is not applicable for CD-R/DVD-R.

3.3.3 Standard Application Profiles

3.3.3.1 The CD/DVD Archive Server supports the standard Application Profiles:
STD-GEN-CD and STD-GEN-DVD.STD-GEN Class Profile

3.3.3.1.1 SOP Classes and Transfer Syntaxes

The class of Application Profile is based on the Media Storage Service Class with the Interchange Option.
(see PS3.4)

SOP Classes and corresponding Transfer Syntaxes supported by the STD-GEN-CD and
STD-GEN-DVD-JPEG Application Profiles are specified in Table 3-8.

Table 3-8 IOD's and Transfer Syntaxes for STD-GEN-CD and STD-GEN-DVD-JPEG Application
Profiles
Information SOP Class UID Transfer Syntax and UID FSC FSR FSU
Object Req. Req. Req.
Definition
Basic 1.2.840.10008.1.3.10 Explicit VR Little Endian M M M
Directory Uncompressed
1.2.840.10008.1.2.1
CT Image 1.2.840.10008.5.1.4.1.1.2 Explicit VR Big Endian O M O
Storage Uncompressed
1.2.840.10008.1.2.2
CT Image 1.2.840.10008.5.1.4.1.1.2 JPEG Lossless Process O M O
Storage Selection Value 14
1.2.840.10008.1.2.4.70
MR Image 1.2.840.10008.5.1.4.1.1.4 Explicit VR Big Endian O M O
Storage Uncompressed
1.2.840.10008.1.2.2
MR Image 1.2.840.10008.5.1.4.1.1.4 JPEG Lossless Process O M O
Storage Selection Value 14
1.2.840.10008.1.2.4.70
PET Image 1.2.840.10008.5.1.4.1.1.128 Explicit VR Big Endian O M O
Information Uncompressed
Storage 1.2.840.10008.1.2.2
PET Image 1.2.840.10008.5.1.4.1.1.128 JPEG Lossless Process O M O
Information Selection Value 14
Storage 1.2.840.10008.1.2.4.70
RT Structure 1.2.840.10008.5.1.4.1.1.481.3 Explicit VR Big Endian O M O
Set Storage Uncompressed
1.2.840.10008.1.2.2
RT Structure 1.2.840.10008.5.1.4.1.1.481.3 JPEG Lossless Process O M O
Set Storage Selection Value 14
1.2.840.10008.1.2.4.70
GEMS PET 1.2.840.113619.4.30 Explicit VR Big Endian O M O
Raw Uncompressed
Information 1.2.840.10008.1.2.2
Storage
GEMS PET 1.2.840.113619.4.30 JPEG Lossless Process O M O
Raw Selection Value 14
Information 1.2.840.10008.1.2.4.70

Copyright 2009 General Electric Company. All rights reserved

Page 40 of 126
 DOC0506131 rev3

Storage
SC Image 1.2.840.10008.5.1.4.1.1.7 Explicit VR Big Endian O M O
Storage Uncompressed
1.2.840.10008.1.2.2
SC Image 1.2.840.10008.5.1.4.1.1.7 JPEG Lossless Process O M O
Storage Selection Value 14
1.2.840.10008.1.2.4.70
GSPS Storage 1.2.840.10008.5.1.4.1.1.11.1 Explicit VR Big Endian O M O
Uncompressed
1.2.840.10008.1.2.2
GSPS Storage 1.2.840.10008.5.1.4.1.1.11.1 JPEG Lossless Process O M O
Selection Value 14
1.2.840.10008.1.2.4.70
Enhanced 1.2.840.10008.5.1.4.1.1.88.22 Explicit VR Big Endian O M O
Structured Uncompressed
Report 1.2.840.10008.1.2.2
Enhanced 1.2.840.10008.5.1.4.1.1.88.22 JPEG Lossless Process O M O
Structured Selection Value 14
Report 1.2.840.10008.1.2.4.70
M : Mandatory O : Optional

3.3.3.1.2 Physical Media and Media Formats

The STD-GEN-CD application profile requires the 120 mm CD-R physical medium with the ISO/IEC 9660
Media Format, as defined in PS3.12. The physical format of DICOM CD-R discs shall comply with the
applicable definitions within ISO/IEC 10149, Part II: CD-WO and CD-ROM-XA (extended Architecture) with
the additional modifications described below.

The STD-GEN-DVD-JPEG application profile requires any of the 120 mm DVD media other than DVD-RAM,
as defined in PS 3.12.

3.3.3.1.2.1 STD-GEN-CD Media Details

Only one File-set shall be stored onto a single CD-R.

The ISO 9660 Standard provides a Volume Identifier in byte position 41 to 72 of the Primary Volume
Descriptor. A DICOM File-Set is defined to be one volume, and the File-Set ID shall be placed in the Volume
Identifier, starting with byte position 41. Extra bytes within the Volume Identifier shall be spaces (20H). The
Volume Identifier for a File-Set ID consisting of zero characters shall consist of all spaces (20H).
Notes: 1. The character set for File IDs and File-set IDs (see PS 3.10) is a subset of the ISO 9660 character
set, therefore no further restrictions need to be imposed.
2. Multiple ISO 9660 File-Sets on a single volume are achievable, but this profile does not support
multiple file-sets.

The ISO 9660 standard provides a hierarchical structure for directories and files within directories. Each
volume has a root directory that may contain references to both files and subdirectories. Subdirectories may
contain reference to both files and other subdirectories.

A volume may have at most 8 levels of directories, where the root directory is defined as level 1. The
nomenclature for referring to a file in the ISO 9660 standard is dependent upon the receiving system. For the
purposes of this document, the following notation will be used:
a) / – For the root directory
b) /FILENAME.;1 – For a file in the root directory
c) /SUBDIR – For a subdirectory in the root directory
d) /SUBDIR/FILENAME.;1 – For a file in the subdirectory

Copyright 2009 General Electric Company. All rights reserved

Page 41 of 126
 DOC0506131 rev3

Given a File ID consisting of N components, referred to as Comp1 through CompN, then the corresponding
ISO 9660 file shall be named /Comp1/.../CompN.;1
The ISO 9660 File Name Extension shall not be used.
The ISO 9660 standard requires the two separators "." and ";" to demarcate a "File Name Extension" and a
"Version Number". To remain compatible with the ISO standard, the version number shall be 1.

Notes: 1. The above specified file ID mapping corresponds to ISO 9660 Level 1 compliance. This ensures thegreatest
level of compatibility across receiving systems.
The following is an example of the DICOM to ISO 9660 file mapping:
DICOM File ID ISO 9660 File Name
DICOMDIR /DICOMDIR.;1
SUBDIRA\IMAGE1 /SUBDIRA/IMAGE1.;1

A DICOMDIR file in a DICOM File-set shall reside in the root directory of the directory hierarchy, and shall be
named /DICOMDIR.;1.
Multiple DICOMDIR files shall not be stored on a single volume.

A Directory record in ISO 9660 provides for a Recording Data and Time field which shall be set to the
creation date of the file. File modification data, file owner identification, and permissions are part of the ISO
9660 – Extended Attribute Record. The Extended Attribute Record is not required by this annex and shall be
ignored at this time. To ensure future backwards compatibility and file accessibility, the Extended Attribute
Record Length and File Flag of the Directory record shall be set as follows for each file. The Extended
Attribute Record Length (byte position 2) shall be zero. The File Flags (byte position 26) shall have bit
positions 3 and 4 set to zero.

3.3.3.1.2.1.1 CD-R Sector Format

All DICOM files and all data that comprise the ISO 9660 file system of the DICOM CD-R disc shall be
stored either:
- within Mode 1 sectors, or
- within Mode 2, Form 1 sectors with CD-ROM-XA File Number = 0, Channel Number = 0 and
Coding Information Byte = 0.

3.3.3.1.2.2 DVD-R Media Format Details

The reader shall be able to read a logical format conforming to UDF and ISO 9660 filesystems. The creator
shall be able to create a logical format conforming to UDF or ISO 9660 filesystems or both, as defined below.
No requirements are defined for an updater.

Note: The intent of these requirements is to insist that a reader be able to read media created by any creator,
but not to require that media created by a particular creator can necessarily be updated by a different
updater.

For more information on DICOM UDF requirements, refer to PS3.12.

3.3.3.1.3 Logical Format

The logical format of CD-R/DVD-R shall conform to ISO 9660 level 1, with the following extensions:

The ISO 9660 System Identifier Field of the PVD (Primary Volume Descriptor) shall contain "CD-
RTOS CD-BRIDGE" if a CD-I (Compact Disc-Interactive) application is present. If a CD-I application
is not present, then this field shall be padded with space characters.

The ISO 9660 System and Volume Descriptor Area (SVD) from the last session points to the set of
ISO 9660 Path Tables and Directory Records that describes the file system of the DICOM CD-R
disc. The SVD area starts at the first logical sector of each session and continues through to the first
instance of the Volume Descriptor Set Terminator. Adding, replacing or deleting files from the disc is

Copyright 2009 General Electric Company. All rights reserved

Page 42 of 126
 DOC0506131 rev3

accomplished by opening a new session and writing within the new session new data (if any), a new
set of Path Tables, and Directory Records that reflect the changes, and an SVD area that points to
the new set of Path Tables and Directory records.

3.3.3.1.4 Directory Information in DICOMDIR

Conformant Application Entities shall include in the DICOMDIR File the Basic Directory IOD containing
Directory Records at the Patient and the subsidiary Study and Series levels, appropriate to the SOP Classes
in the File Set. All DICOM files in the File Set incorporating SOP Instances defined for the specific
Application Profile shall be referenced by Directory Records.

Note: DICOMDIRs with no directory information are not allowed by this Application Profile.

All implementations shall include the DICOM Media Storage Directory in the DICOMDIR file. There shall
only be one DICOMDIR file per File Set. The DICOMDIR file shall be in the root directory of the medium.

Refer to Appendix C for a complete listing of all the optional modules and optional attributes used in
the DICOMDIR definition. Please note that the mandatory attributes in each of the directory records
as mentioned in Part 3 Addendum (Basic Directory Information Object Definition) are not listed in
the appendix, but are supported by the implementation.
NOTE:
The modality attribute (0008,0060) in the DICOMDIR Series records should be CT/MR for Secondary
Capture SOP Class Images. Otherwise the GE MR system’s DICOM media display browser will not list-up
the series for contents rendering the retrieval to local storage impossible.

3.3.3.1.4.1 Additional Keys

None.

3.3.3.1.5 Other Parameters

3.3.3.1.5.1 DVD MultiFrame JPEG Format

The JPEG encoding of pixel data shall use Interchange Format (with table specification) for all frames.

3.3.3.1.5.2 Image Attribute Values

None.

3.3.3.1.5.2.1 Attribute Value Precedence

None.

3.3.4 Private Application Profiles

The CD/DVD Archive Server does not support any private Application Profiles.

3.4 Extensions, Specialization’s and Privatization’s of SOP Classes and Transfer

Syntaxes

3.4.1 Extensions, Specialization’s and Privatization’s of SOP Classes

The CT/MR SOP Class Images have definitions extended for Defined Terms and include GE specific Private
Data elements. The following sections describe the details for these SOP classes.

Copyright 2009 General Electric Company. All rights reserved

Page 43 of 126
 DOC0506131 rev3

3.4.1.1 SOP Specific Conformance Statement for CT SOP Class

Please refer to the appropriate CT DICOM Conformance Statement.

3.4.1.2 SOP Specific Conformance Statement for MR SOP Class

Refer to section 2.4 for standard extensions and Appendix B for private data elements.

3.4.2 Private Transfer Syntax Specification

None specified.

3.5 Configuration
For the CD/DVD Archive Application, the source AE Title encoded in the File Meta-Information cannot be
modified.

3.6 Support of Extended Character Sets

The CD/DVD Archive Application will support copy of SOP instances containing the ISO IR 100 (Latin
alphabet No. 1, supplementary set) and DICOM default character sets as defined in PS3.5. Any incoming
SOP instances encoded using another extended character set will not be installed in the GE MR system
database.

Copyright 2009 General Electric Company. All rights reserved

Page 44 of 126
 DOC0506131 rev3

4 PRINT SCU CONFORMANCE STATEMENT

4.0 Introduction

This section of the Conformance Statement specifies the compliance to DICOM conformance requirements
for the relevant Grayscale and Color Network Printing features on the GE MR system. It details the DICOM
Service Classes and roles that are supported by this product.

The GE MR system uses DICOM services to provide the DICOM Print SCU Application Profile. The GE MR
system uses DICOM Print SCU to print images on DICOM Compliant Printers.

Note the format of this section follows the format of the DICOM Standard Part 2 (conformance) Annex A
hence the paragraph numbering scheme. Please refer to that part of the standard while reading this section.

4.1 IMPLEMENTATION MODEL : PRINT SCU

The DICOM Print SCU is a DICOM print filter, which provides the capability to print images to DICOM
printers. The DICOM Print filter acts as an SCU of the DICOM print management SOP class.

4.1.1 Application Data Flow Diagram

DICOM print SCU Implementation model

DICOM INTERFACE

Film DICOM
Composer Print SCU Printer

Film Composer is the User Interface and is used to initiate the local real world activity. The user issues the
print request using Film Composer. Film Composer allows printer selection and composes the preformatted
film file. The film file is interpreted by the SCU, which sends the appropriate messages to DICOM print SCP
running on the DICOM printer.

4.1.2 Functional Definition of AE’s

DICOM Print SCU Establishes the Association with requested printer to print the composed film. If the
Remote AE accepts the presentation context applicable to the print job, the DICOM Print AE SCU will send
the print job to the receiving Remote AE by using the N-CREATE and N-SET services.

Copyright 2009 General Electric Company. All rights reserved

Page 45 of 126
 DOC0506131 rev3

4.1.3 Sequencing of Real-World Activities

• User has to select the DICOM printer from the Film Composer Interface.
• The images to be printed shall be dragged and dropped into Film Composer slots from Viewing
Applications either manually or automatically.
• In case of manual drag and drop, the user has to press the Print Button to print the images .
• The Print SCU will start the Print Session. The Print Session involves establishing association with
the printer followed by the next sequence of activities:
o The Print SCU gets the Printer status using N-GET service. If the Printer returns FAILURE
status the print session will be terminated and the requester will be notified of the printer
status.
o The film session is created using N-CREATE service. In case of error, the print session will
be terminated. The attribute values for the Film session will be specified with the film session
request.
o The film box is created using N-CREATE service. The print session will be terminated if the
printer fails to create the film box. The film box attribute values will be sent in the film box
create request.
o The image attributes for the images to be printed in this session will be set using the N-SET
service. If the printer fails to accommodate the images in the image set, the print session
will be terminated.
o The film will be printed using the N-ACTION service. Only film box printing is supported. In
case of error, the print session will be terminated.
o The Film Box instance will be deleted using the N-DELETE service.
o The SCU does not wait for N-EVENT-REPORT from the Printer after deleting the film box
instance. The N-EVENT-REPORT received when the association was still active is handled,
but the data received will be ignored.
o Finally the association will be terminated and if all the above operations are successful the
requester will be notified of the successful print session. This status just indicates that the
images to be printed have been successfully sent to the printer.

4.2 AE SPECIFICATIONS

4.2.1 DICOM Print SCU AE Specification

Print SCU provides Standard Conformance to the following DICOM 3.0 SOP classes as an SCU:

SOP Class Name SOP Class UID

Basic Grayscale Print Management Meta SOP Class 1.2.840.10008.5.1.1.9
Basic Color Print Management Meta SOP Class 1.2.840.10008.5.1.1.18
Print Job SOP Class 1.2.840.10008.5.1.1.14

Note: Support of the Basic Grayscale Print Management Meta SOP Class as an SCU
mandates support for the Basic Film Session, Basic Film Box, Basic Grayscale Image
Box, and Printer SOP Classes as an SCU.
Note: Support of the Basic Color Print Management Meta SOP Class as an SCU mandates
support for the Basic Film Session, Basic Film Box, Basic Color Image Box, and Printer
SOP Classes as an SCU.

4.2.1.1 Association Establishment Policies

4.2.1.1.1 General

Copyright 2009 General Electric Company. All rights reserved

Page 46 of 126
 DOC0506131 rev3

The Print SCU provides options to indicate the printer AE title, Printer host name. In this product, these
inputs are provided by Film Composer. Depending on these inputs the Print SCU will establish the
association with the desired printer.

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

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 association initiated by the DICOM Print SCU AE is:

Maximum Length PDU 10 kbytes

4.2.1.1.2 Number of Associations

The Print SCU will initiate only one association with a printer. This will not initiate any other associations
while the current association is active.

4.2.1.1.3 Asynchronous Nature

The print SCU does not support asynchronous operations. All operations will be performed synchronously.

4.2.1.1.4 Implementation Identifying Information

The Implementation UID allows unique identification of a set of products that share the same
implementation. Please refer to Section 1.1 for details on specific GE MR system information.

4.2.1.1.5 Association Initiation Policy

Print SCU initiates association with the Printer (which is running DICOM Print SCP) provided as input to Print
SCU by Film Composer.

4.2.1.1.6 Real-World Activity: Print

4.2.1.1.6.1 Associated Real-World Activity

The Film Composer allows the user to select printers and it also allows the user to drag and drop the images
(from viewer application) into the film. It also allows the user to manipulate some print parameters like film
format and number of copies to print. When user presses the "Print" Button, the Film Composer
communicates this request to Print SCU, which then tries to establish the association with requested printer
and sends the images for printing.

4.2.1.1.6.2 Proposed Presentation Contexts

The Proposed Presentation Context table for the Print SCU is as shown in following Table.

Presentation Context Table

Abstract Syntax Transfer Syntax Role Extended
Negotiation

Copyright 2009 General Electric Company. All rights reserved

Page 47 of 126
 DOC0506131 rev3

Name UID Name UID

Verification SOP 1.2.840.10008.1.1 DICOM Implicit VR 1.2.840.10008.1.2 SCU None
Class Little Endian
Transfer Syntax
Basic Grayscale DICOM Implicit VR
Print Management 1.2.840.10008.5.1.1.9 Little Endian 1.2.840.10008.1.2 SCU None
Meta SOP Class Transfer Syntax
Print Job SOP 1.2.840.10008.5.1.1.14 DICOM Implicit VR
Class Little Endian 1.2.840.10008.1.2 SCU None
Transfer Syntax
Printer SOP Class 1.2.840.10008.5.1.1.16 DICOM Implicit VR 1.2.840.10008.1.2 SCU None
Little Endian
Transfer Syntax
Basic Color Print 1.2.840.10008.5.1.1.18 DICOM Implicit VR 1.2.840.10008.1.2 SCU None
Management Meta Little Endian
SOP Class Transfer Syntax

4.2.1.1.6.2.1 SOP Specific Conformance Statement for Print Management SOP Classes

The Print SCU supports the following mandatory SOP classes, which are defined under the Basic Grayscale
Print Management Meta SOP Class and Basic Color Print Management Meta SOP Class.

NAME UID
Basic Film Session SOP Class 1.2.840.10008.5.1.1.1
Basic Film Box SOP Class 1.2.840.10008.5.1.1.2
Basic Grayscale Image Box SOP Class 1.2.840.10008.5.1.1.4
Basic Color Image Box SOP Class 1.2.840.10008.5.1.1.4.1
Printer SOP Class 1.2.840.10008.5.1.1.16

Optional Print SOP Classes supported by Print SCU :

NAME UID
Print Job SOP Class 1.2.840.10008.5.1.1.14

4.2.2 Basic Film Session SOP Class

The Print SCU supports the following DIMSE Service Elements for the Basic Film Session SOP Class.

N-CREATE - Requests the Print SCP to create an instance of Basic Film Session.

The following table shows the attribute values supported by the N-CREATE operation. Although these
attributes are optional for the SCU, we provide values for all of these optional attributes. If the SCP does not
support the requested value it may choose to either return a failure status or ignore the value provided and
use its default value.

Attribute DICOM Tag Valid Range Default Value

Number of Copies ( 2000,0010 ) 1-99 Set by user
Print Priority ( 2000,0020 ) HIGH/MED/LOW Set when a device is added
using the Film Composer
Tool.

Copyright 2009 General Electric Company. All rights reserved

Page 48 of 126
 DOC0506131 rev3

Medium Type ( 2000,0030 ) CLEAR FILM Set when a device is added

BLUE FILM using the Film Composer
PAPER Tool.
Film Destination ( 2000,0040 ) MAGAZINE Set when a device is added
PROCESSOR using the Film Composer
Tool.

If Failure status is returned during N-CREATE operation of Film Session the following action will be taken:
0x213 "Resource Limitation" message will be sent. All other status "Failure" message will be sent. In all
cases the print session will be terminated.

If a Warning status is returned during the N-CREATE operation of the Film Session the association will be
terminated.

4.2.3 Basic Film Box SOP Class

The Print SCU supports the following DIMSE Service Elements for the Basic Film Box SOP Class.

N-CREATE - Requests the Print SCP to create an instance of Film Box.

N-ACTION - Requests the Print SCP to print the Film Box onto Printer.
N-DELETE - Requests the Print SCP to delete the Film Box Instance.

The following Attribute values are supported:

Attribute DICOM Tag Valid Range Default Value

Image Display Format ( 2010,0010 ) STANDARD\C,R Set in User Interface
Printer Dependent
Reference Film Session ( 2010,0500) Always set
Sequence
Film Orientation ( 2010,0040 ) PORTRAIT Set when a device is
added using the Film
Composer Tool.
Film Size ID ( 2010,0050 ) (zero length), Set when a device is
“14INX17IN” added using the Film
Composer Tool.
Magnification type ( 2010,0060 ) BILINEAR Set when a device is
CUBIC added using the Film
REPLICATE Composer Tool.
NONE
Trim ( 2010,0140 ) YES/NO/Not Sent NO
Max Density ( 2010,0130 ) 0-4095 Set when a device is
added using the Film
Composer Tool.
Configuration Information ( 2010,0150 ) Printer Dependent Set when a device is
added using the Film
Composer Tool.
Smoothing type ( 2010,0080 ) Printer Dependent Set when a device is
added using the Film
Composer Tool.
Border density ( 2010,0100 ) BLACK/WHITE/Not Set when a device is
Sent added using the Film
Composer Tool.

Copyright 2009 General Electric Company. All rights reserved

Page 49 of 126
 DOC0506131 rev3

Empty image density ( 2010,0110 ) BLACK/WHITE/Not Set when a device is

Sent added using the Film
Composer Tool.
Min density ( 2010,0120 ) 0-4095, Not Sent Set when a device is
added using the Film
Composer Tool.

Note: Attributes “sent zero length” use the camera default values.

If a Failure status is returned during the N-CREATE operation of the Film Box the association will be
terminated.

If a Warning status is returned during the N-CREATE operation of the Film Box the association will be
terminated.

The product shows an error message [FSA/Film Composer] when receiving statuses other than success for N-ACTION
and N-DELETE DIMSE services.

4.2.4 Basic Grayscale Image Box SOP Class

The Print SCU supports the following DIMSE Service Elements for Grayscale Image Box SOP Class.

N-SET - Requests the Printer to set the image box attributes.

The following Attribute values are supported:

Attribute DICOM Tag Valid Range Default Value

Image Position ( 2020,0010 ) Based on Image No Default Value
Display Format
Preformatted Grayscale ( 2020,0110)
Image Sequence
>Samples per pixel ( 0028,0002 ) 1 1
>Photometric Interpretation ( 0028,0004 ) MONOCHROME2 MONOCHROME2
>Rows ( 0028,0010 ) Image Dependent Image Dependent
>Columns ( 0028,0011 ) Image Dependent Image Dependent
>Pixel Aspect Ratio ( 0028,0034 ) 1/1 1/1
>Bits Allocated ( 0028,0100 ) 8 or 16 8 (if Bits Stored=8)
16 (if Bits Stored=12)
>Bits Stored ( 0028,0101 ) 8 or 12 8 or 12
>High Bit ( 0028,0102 ) 7 or 11 7 (if Bits Stored=8)
11 (if Bits Stored=12)
>Pixel Representation ( 0028,0103 ) 0 (unsigned integer) 0 (unsigned integer)
>Pixel Data ( 7FE0,0010 ) Pixel data Pixel data
Polarity ( 2020,0020 ) NORMAL NORMAL

If a Failure status is returned during the N-SET operation of the Image Box the association will be
terminated.

If a Warning status is returned during the N-SET operation of the Imaqge Box the association will be
terminated.

Copyright 2009 General Electric Company. All rights reserved

Page 50 of 126
 DOC0506131 rev3

4.2.5 Basic Color Image Box SOP Class

The Print SCU supports the following DIMSE Service Elements for Basic Color Image Box SOP Class.

N-SET - Requests the Printer to set the image box attributes.

The following Attribute values are supported:

Attribute DICOM Tag Valid Range Default Value

Image Position ( 2020,0010 ) Based on Image No Default Value
Display Format
Preformatted Color Image ( 2020, 0111 )
Sequence
>Samples per pixel ( 0028,0002 ) 3 3
>Photometric Interpretation ( 0028,0004 ) RGB RGB
>Planar Configuration ( 0028,0006 ) 1 1
>Rows ( 0028,0010 ) Image Dependent Image Dependent
>Columns ( 0028,0011 ) Image Dependent Image Dependent
>Pixel Aspect Ratio ( 0028,0034 ) 1/1 1/1
>Bits Allocated ( 0028,0100 ) 8 8
>Bits Stored ( 0028,0101 ) 8 8
>High Bit ( 0028,0102 ) 7 7
>Pixel Representation ( 0028,0103 ) 0 (unsigned integer) 0 (unsigned integer)
>Pixel Data ( 7FE0,0010 ) Pixel data Pixel data
Polarity ( 2020,0020 ) NORMAL NORMAL

If a Failure status is returned during the N-SET operation of the Image Box the association will be
terminated.

If a Warning status is returned during the N-SET operation of the Image Box the association will be
terminated.

4.2.6 Printer SOP Class

The N-GET DIMSE service is supported for the Printer SOP Class. If an N-EVENT-REPORT DIMSE service
is received when the association is active, the Print SCU handles the relevant states but the data received is
ignored.

The Print SCU issues the request to retrieve following attributes:

Optional Attribute DICOM Tag

Printer Status ( 2110,0010 )
Printer Status Info ( 2110,0020 )
Printer Name ( 2110,0030 )
Manufacturer ( 0008,0070 )
Manufacturer Model Name ( 0008,1090 )
Device Serial No. ( 1800,1000 )
Software Versions ( 1800,1020 )
Date Last Calibrated ( 1800,1200 )
Time Last Calibrated ( 1800,1201 )

Copyright 2009 General Electric Company. All rights reserved

Page 51 of 126
 DOC0506131 rev3

The Print SCU issues the N-GET service to retrieve the printer status. The statuses are processed as
follows:

• If Printer status (2110,0010) is NORMAL, the film is printed.

• If Printer status (2110,0010) is FAILURE the print job is terminated. The Printer Status Info
(2110,0020) attribute is not processed.
• If Printer status (2110,0010) is WARNING one of three things will happen:
a) If the Printer Status Info (2110,0020) is “SUPPLY LOW” the status is displayed to the user
and the print job continues.
b) If the Printer Status Info (2110,0020) is “RECEIVER FULL” or “SUPPLY EMPTY”, or “FILM
JAM” the status is displayed to the user and the print job is aborted.
c) For all other Printer Status Info (2110,0020) values, the status is ignored and the print job
continues.

4.2.7 Print Job SOP Class

Print SCU looks for the following attributes in N-EVENT REPORT data received from Print SCP. If Print
SCU does not receive N-EVENT_REPORT, it requests the Print SCP to retrieve the following set of
attributes:

Attribute Name DICOM Tag Default Value

Execution Status ( 2100,0020 ) Printer Shall return Value
Execution Status Info ( 2100,0030 ) Printer Shall return Value
Print Priority ( 2000,0020 ) Printer Shall return Value
Creation Date ( 2100,0040 ) Printer may return Value
Creation Time ( 2100,0050 ) Printer may return Value
Printer Name ( 2110,0030 ) Printer may return Value
Originator ( 2100,0070 ) Printer may return Value

4.3 Association Acceptance Policy

The Print SCU does not accept associations.

4.4 COMMUNICATION PROFILES

4.4.1 Supported Communication Stacks (parts 8,9)

DICOM Upper Layer (Part 8) is supported using TCP/IP.

4.4.2 TCP/IP Stack

The TCP/IP stack is inherited from the UNIX Operating System.

4.4.3 API
Not Applicable

4.4.4 Physical Media Support

Ethernet v2.0, IEEE 802.3.

Copyright 2009 General Electric Company. All rights reserved

Page 52 of 126
 DOC0506131 rev3

4.4.5 Standard Extended/Specialized/Private SOPs

None.

4.5 AE Title/Presentation Address Mapping

4.5.1 Configurable Parameters

The GE MR system allows the user to “Add”, “Remove”, or “Update the mapping of remote DICOM Printer
AE Titles to IP Addresses and Ports. These options can be selected from the “Remote Printer Selection”
menu displayed by choosing “Configure” button from the Film Composer.

Time-outs, which are set for all hosts, are configurable in the dprint.cfg file. The following table lists the
parameters and default values:

Timeout Description Default Value Configuration Parameter Name

Association Time out 120 seconds bi_assoc_tio
Session Time out 1200 seconds bi_session_tio
Echo Time out 200 seconds bi_echo_tio
N-SET Time out 300 seconds bi_nset_tio
N-ACTION Time out 300 seconds bi_naction_tio
N-CREATE Time out 300 seconds bi_ncreate_tio
N-DELETE Time out 300 seconds bi_ndelete_tio
N-GET Time out 100 seconds bi_nget_tio

The following DICOM print parameters are configurable. The valid ranges are shown in earlier sections of
this document.
Attribute Name DICOM Tag
Medium Type (2000,0030)
Film Destination (2000,0040)
Magnification Type (2010,0060)
Min Density (2010,0120)
Max Density (2010,0130)
Empty Image Density (2010,0110)
Border Density (2010,0100)
Configuration Information (2010,0150)
Smoothing Type (2010,0080)

Note: All configurations should be performed by a GE Field Service Engineer.

4.5.2 Support of Extended Character Set

The Print SCU does not support any Extended Character Set.

Copyright 2009 General Electric Company. All rights reserved

Page 53 of 126
 DOC0506131 rev3

5 Enhanced Modality Worklist Conformance Statement

5.0 INTRODUCTION
This section specifies the use of the DICOM Modality Worklist Information Model used to organize data and
against which a Modality Worklist Query will be performed. The overall content of this specification is an
enhancement to the existing capability.

5.1 IMPLEMENTATION MODEL

All Modality Worklist DICOM functionality provided by the GE MR system is logically provided by the Worklist
Server DICOM AE. The Worklist Server DICOM AE is commanded to perform DICOM modality worklist
query services through the use of the Scanner’s user interface.
5.1.1 Application Data Flow Diagram
The Basic and Specific Application models for this device are shown in the following illustration:

Association Initiation

Modality CT/MR Remote

Worklist Worklist Worklist
SCU Server SCP
AE

Association Acceptance

DICOM
Standard
Interface

Copyright 2009 General Electric Company. All rights reserved

Page 54 of 126
 DOC0506131 rev3

5.1.2 Functional Definition of AE's

The Worklist Server AE is implemented as an application process on the scanner host computer. It runs as a
daemon serving requests from the user interface to obtain modality worklist, query remote AE’s and return
the results to the user interface.
The Worklist Server AE initiates the following functions:
Query: Initiates a DICOM association in order to query a remote AE. If the remote AE accepts a
presentation context applicable to modality worklist, the Worklist Server AE will issue a modality worklist
query request via the C-FIND service.
5.1.3 Sequencing of Real-World Activities
1. The user or the system initiates a modality worklist query (as a modality worklist SCU) to the modality
worklist SCP with a given set of query parameters.
2. The modality worklist SCP returns responses, which match the query parameters.
3. Items from the returned worklist responses are presented to the user.
4. A subset of attributes corresponding to operator selected returned worklist responses will be included in
acquired DICOM images related to the responses.
5.2 AE SPECIFICATIONS
5.2.1 Worklist Server AE Specification
This Application Entity provides Standard Conformance to the following DICOM SOP Classes as an SCU:
SOP Class Name SOP Class UID

Modality Worklist Information Model – FIND 1.2.840.10008.5.1.4.31

Verification (Echo) 1.2.840.10008.1.1

5.2.1.1 Association Establishment Policies

5.2.1.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 DICOM Worklist Server is:
Maximum Length PDU 16 kbytes

The SOP Class Extended Negotiation is not supported.

The maximum number of Presentation Context Items that will be proposed is 1.
The user information Items sent by this product are:
• Maximum PDU Length
• Implementation UID

5.2.1.1.2 Number of Associations

The Worklist Server AE (SCU) will initiate only one DICOM association at a time to perform a modality
worklist query of a single remote AE.
5.2.1.1.3 Asynchronous Nature
Asynchronous mode is not supported. All operations are performed synchronously.

Copyright 2009 General Electric Company. All rights reserved

Page 55 of 126
 DOC0506131 rev3

5.2.1.1.4 Implementation Identifying Information

The Implementation UID allows unique identification of a set of products that share the same
implementation.

The Implementation UID for this GE Healthcare Implementation is:

Modality Worklist Implementation UID 1.2.826.0.1.3680043.2.60.0.1

5.2.1.2 Association Initiation Policy

The Worklist Server AE initiates a new association due to an update operation being initiated from the GE
MR system user interface. The association is closed upon receipt of the final query response from the
remote AE. The association can also be closed by the Worklist Server AE upon receipt of error status from
the remote AE or upon expiration of association timers.
5.2.1.2.1 Real-World Activity: Worklist Query

5.2.1.2.1.1 Associated Real-World Activity

The operator of the system initiates a query for a modality worklist by either opening the Schedule screen or
by opening the Schedule screen and pressing the Update button. The choice of which of these two
behaviors occurs is user configurable. The Worklist Server will then initiate an association with the remote
AE in order to query for the worklist.
A user can configure a number of parameters, which directly control the worklist query request. The user can
request worklist items that are intended for the scanner the user is working at, all items that apply to the
modality of the scanner the user is working at or all worklist items available. These selections and their
effects on worklist query parameters are given below:
This System:
• Modality, (0008,0060) - set to MR
• Scheduled Station AE Title, (0040,0001) - set to Station name AE title
This Modality:
• Modality, (0008,0060) - set to MR
• Scheduled Station AE Title , (0040,0001) - zero-length (universal matching)
All Modalites:
• Modality, (0008,0060) - zero-length (universal matching)
• Scheduled Station AE Title, (0040,0001) - zero-length (universal matching)
Note that the All Modalities query above can return worklist items for modalities other than MR if such items
exist. The system will warn the operator and disallow selection if a dissimilar modality is selected from the
worklist.
The scheduled dates of procedures of interest can be specified for query by selecting a specific date range.
The date ranges available are Today, Date Range and Any Days. These selections and their affects on
worklist query parameters are given below:
Today:
Scheduled Procedure Step Start Date, (0040,0002) - set to YYYYMMDD, where this date is the
current date.
Date Range:
Scheduled Procedure Step Start Date, (0040,0002) - set to YYYYMMDD-YYYYMMDD, where this
date range represents the specified number of days before today and/or after today. Note that
number of days both before and after can be specified in the same query and that each always
includes today.
Any Days:
Scheduled Procedure Step Start Date, (0040,0002) - zero-length (universal matching)

Copyright 2009 General Electric Company. All rights reserved

Page 56 of 126
 DOC0506131 rev3

Note that selecting All Scanners and All Days with no worklist specific fields specified results in an
unconstrained worklist query. The response to an unconstrained worklist query can differ between different
modality worklist SCP implementations. Consult the modality worklist SCP manufacturer if difficulties occur
when attempting unconstrained queries.

Worklist specific fields targeted to retrieve a single or very small set of related entries may also be specified.
These fields may be used for a query combined with scanner and scheduled time to provide a very specific
query to the worklist server. The specific fields are specified below:

Patient Name (0010,0010)

Matching with leading and trailing wildcards is allowed on either Patient Last Name or Patient First
Name (user selectable), zero length matches all values.

Patient ID (0010,0020)
Zero length or single value matching only of value entered.

Requested Procedure ID (0040,1001)

Zero length or single value matching only of value entered.

Accession Number (0008,0050)

Leading and trailing wildcard matching for value entered.

5.2.1.2.1.2 Proposed Presentation Context

Table 5-1 shows the proposed presentation contexts for the Worklist Server AE after real-world activity
“Worklist Query” has been initiated:
Table 5-1 Proposed Presentation Context

Presentation Context Table – Proposed

Abstract Syntax Transfer Syntax Role Extended
Name UID Name List UID List Negotiation
Modality Worklist 1.2.840.10008.5.1.4.31 Explicit VR Big Endian 1.2.840.10008.1.2.2 SCU None
Information Model –
FIND
Modality Worklist 1.2.840.10008.5.1.4.31 Implicit VR Little Endian 1.2.840.10008.1.2 SCU None
Information Model –
FIND

5.2.1.2.1.2.1 SOP Specific DICOM Conformance Statement for the Worklist SOP Class
If the remote AE does not support the proposed Presentation Context, an appropriate error is logged and the
operator is notified.
This implementation can receive multiple C-FIND results over a single association. Only one association is
opened at a time.
Each C-FIND response received from the remote AE is parsed to verify the length/type of the items in the
response. Upon detecting any error in the response data, the response is discarded and the next response
(if any) is considered.

All errors and failures detected by the Worklist Server AE are logged to the log file /usr/g/service/log

5.2.1.2.1.2.2 Record Acceptance Policy

Copyright 2009 General Electric Company. All rights reserved

Page 57 of 126
 DOC0506131 rev3

The GE MR system has a lenient policy regarding the rejection of the MWL. In case certain parameters
retrieved from the MWL is invalid, the system will require\allow the user to enter the value through the UI.

5.2.1.3 Association Acceptance Policy

The Worklist Server AE does not respond to attempts by a remote AE to open an association.
5.3 MODALITY WORKLIST INFORMATION MODEL DESCRIPTION
In order to serve as a Service Class Provider (SCP) of the Modality Worklist Service Class, a DICOM
Application Entity (AE) possesses information about the attributes of a number of managed worklist items.
These items are organized into Modality Worklist Information Modules. In this Service Class, the Information
Model plays a role similar to an Information Object Definition of most other DICOM Service Classes.
5.4 MODALITY WORKLIST INFORMATION MODEL ENTITY-RELATIONSHIP MODEL
The Entity-Relationship diagram for the Modality Worklist Information Model schema is shown in Figure 5-1.
It represents the information that composes a Worklist Item. In this figure, the following diagrammatic
convention is established to represent 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 corresponding
entity boxes to the relationship boxes.

Copyright 2009 General Electric Company. All rights reserved

Page 58 of 126
 DOC0506131 rev3

Scheduled Worklist
Procedure Step Item

contained in

Requested
Procedure

requested for

Imaging Service
Request

done for

Patient

is included

0,1

Visit

Figure 5-1
Modality Worklist Information Model E/R DIAGRAM

5.4.1 ENTITY DESCRIPTIONS

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 within the Modality Worklist Information
Model.
5.4.1.1 Scheduled Procedure Step
A Scheduled Procedure Step is an arbitrarily defined scheduled unit of service that is specified by the
Procedure Plan for a Requested Procedure. It specifies one or more Action Items (events) involving
equipment (i.e. imaging modality equipment), human resources, location and time (i.e. start time, stop time,
duration).

Copyright 2009 General Electric Company. All rights reserved

Page 59 of 126
 DOC0506131 rev3

5.4.1.2 Requested Procedure Entity Description

A Requested Procedure is an instance of a Procedure of a given Procedure Type. An instance of a
Requested Procedure includes all of the items of information that are specified by an instance of a
Procedure Plan that is selected for the Requested Procedure by the imaging service provider.
5.4.1.3 Imaging Service Request Entity Description
An Imaging Service Request is a set of one or more Requested Procedures selected from a list of Procedure
Types. An Imaging Service Request is submitted by one authorized imaging service requester to one
authorized imaging service provider in the context of one Service Episode.
5.4.1.4 Visit Entity Description
A Visit is the context in which the treatment or management of an arbitrary subset of a Patient’s medical
conditions occurs. A Visit is limited to the description of a Patient’s activities at a single facility.
5.4.1.5 Patient Entity Description
A Patient is a person receiving, or registered to receive, healthcare services.
5.4.2 MR Systems Mapping of DICOM Entities
Table 5-2
Mapping of DICOM Entities to MR Systems Entities

DICOM MR Systems Entity

Scheduled Procedure Step Exam
Requested Procedure Exam
Imaging Service Request Exam
Visit Exam
Patient Patient

5.5 INFORMATION MODEL MODULE

Within an entity of the DICOM Modality Worklist Information Model, attributes are grouped together into
related set of attributes called modules. A module facilitates the understanding of the semantics concerning
the attributes and how the attributes relate to one another. A module grouping does not infer any encoding of
information into datasets.
Table 5-3 identifies the defined modules within the entities which comprise the DICOM Modality Worklist
Information Model. Modules are identified by Module Name.
See DICOM PS 3.3 and PS 3.4 for a complete definition of the entities, modules, and attributes.

Copyright 2009 General Electric Company. All rights reserved

Page 60 of 126
 DOC0506131 rev3

Table 5-3
Modality Worklist Information Model Modules
Entity Name Module Name Reference
Scheduled Procedure Step SOP Common 5.6.2.1
Scheduled Procedure Step 5.6.2.2
Requested Procedure Requested Procedure 5.6.3.1
Imaging Service Request Imaging Service Request 5.6.4.1
Visit Visit Identification 5.6.5.1
Visit Status 5.6.5.2
Visit Relationship 5.6.5.3
Visit Admission 5.6.5.4
Patient Patient Relationship 5.6.6.1
Patient Identification 5.6.6.2
Patient Demographic 5.6.6.3
Patient Medical 5.6.6.4

5.6 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 within the Modality Worklist Information
Model.
The following Module descriptions contain the attributes, which are present in a C-FIND request message
sent by the Worklist Server AE to a remote AE. It should be noted that they are the same as those defined in
the DICOM Standard, PS 3.4 (Service Class Specifications). Required attributes for the GE MR systems are
also indicated.
• Attribute Name
• Tag: group and element numbers
• Required for MWL: These attributes are required for GE MR systems configured with Modality
Worklist. { Yes=required; No=Not required }
• Mapped into The Image: Whether this data is mapped into subsequently acquired images
• Notes: Clarification of this implementation’s use/treatment of this attribute

All data elements in the following Module descriptions are requested by the Worklist Server AE if requested
by the operator. Values of data elements that are not mapped into images, and are not otherwise dealt with
(displayed on the user interface, etc.), are not used and are, thus, discarded upon receipt – although they
may be used to filter the entries returned.
Data elements for which values can be sent for matching purposes are described as such. Data elements for
which values are not sent are sent with zero length and universal matching will apply. This is the default case
if no other description to the contrary is provided.

Copyright 2009 General Electric Company. All rights reserved

Page 61 of 126
 DOC0506131 rev3

5.6.1 Supported Matching

The following are the types of matching that can be requested by the implementation:
• Single Value matching
• Universal Matching
• Range of date/time

5.6.2 Scheduled Procedure Step Entity

5.6.2.1 SOP Common Module
Table 5-4 SOP Common Module Attributes
Attribute Name Tag Required Mapped Note
for into the
Modality Image?
Worklist?
Specific Character Set (0008,0005) No No The value of “ISO_IR 100” is always
sent in the query, however the
returned value is ignored.

5.6.2.2 Scheduled Procedure Step Module

Table 5-5 Scheduled Procedure Step Module Attributes
Attribute Name Tag Required Mapped Note
for into the
Modality Image?
Worklist?
Scheduled Procedure (0040,0100) No No
Step Sequence
>Scheduled Station AE (0040,0001) No No Matching is supported as follows:
Title either no AE title is supplied (universal
matching), or the scanner’s Worklist
Server Station Name is supplied for
matching; this is user selectable.
>Scheduled Procedure (0040,0002) No No Matching is supported as one of the
Step Start Date following; this is user selectable:
• all days,
• today only,
• today and a number of days before
today,
• today and a number of days after
today,
• today and a number of days before
today and a number of days after
today.
The number of days before/after is
specified by the user.
Displayed on “Worklist Schedule”
Screen.
>Scheduled Procedure (0040,0003) No No Displayed on “Worklist Schedule”
Step Start Time Screen.

Copyright 2009 General Electric Company. All rights reserved

Page 62 of 126
 DOC0506131 rev3

>Modality (0008,0060) No No Matching is supported as follows:

either no Modality is supplied
(universal matching), or the scanner’s
Modality is supplied for matching; this
is user selectable.
Displayed on “Worklist Schedule”
Screen.
>Scheduled Performing (0040,0006) No No Not used
Physician's Name
>Scheduled Procedure (0040,0007) No Yes Displayed on “Worklist Schedule”
Step Description Screen.
>Scheduled Station Name (0040,0010) No No Not used.
>Scheduled Procedure (0040,0011) No No Not used
Step Location
>Scheduled Protocol (0040,0008) No No Not used.
Code Sequence
>>Code Value (0008,0100) No No For MR systems, when a procedure
step is selected from the schedule, the
returned value is used to automatically
select and launch a protocol for MR
systems (if the appropriate mapping
has been established). See the MR
system documentation for further
details

>>Coding Scheme (0008,0102) No No

Designator
>>Code Meaning (0008,0104) No No
>Pre-Medication (0040,0012) No No Displayed on “Other Information”
screen.
>Scheduled Procedure (0040,0009) No Yes Displayed in MWL Detail Panel as
Step ID ‘Procedure Id’
>Requested Contrast (0032,1070) No No Can be configured for user display
Agent

5.6.3 Requested Procedure Entity

5.6.3.1 Requested Procedure Module
Table 5-6 Requested Procedure Module Attributes
Attribute Name Tag Required Mapped Note
for into the
Modality Image?
Worklist?
Requested Procedure ID (0040,1001) No Yes Zero length or single value
matching only of value entered
Requested Procedure (0032,1060) No Yes
Description
Requested Procedure Code (0032,1064) No No Not used
Sequence
>Code Value (0008,0100) No No
>Coding Scheme Designator (0008,0102) No No

Copyright 2009 General Electric Company. All rights reserved

Page 63 of 126
 DOC0506131 rev3

>Code Meaning (0008,0104) No No

Study Instance UID (0020,000D) Yes Yes
Referenced Study Sequence (0008,1110) No No Not used
>Referenced SOP Class (0008,1150) No Yes
UID
>Referenced SOP Instance (0008,1155) No Yes
UID
Requested Procedure (0040,1003) No No Not used
Priority
Requested Procedure (0040,1400) No No Not used
Comments
Name of Intended recipients (0040,1010) No No Not used
of results
Patient Transport (0040,1004) No No Not used
Arrangements
Requested Procedure (0040,1005) No No Not used
Location
Confidentiality Code (0040,1008) No No Not used

5.6.4 Imaging Service Request Entity

5.6.4.1 Imaging Service Request Module
Table 5-7 Imaging Service Request Module Attributes
Attribute Name Tag Required Mapped Note
for into the
Modality Image?
Worklist?
Accession Number (0008,0050) No Yes Displayed on “Worklist Schedule
screen. Leading and trailing
wildcard matching for value
entered.
Requesting (0032,1032) No No
Physician
Referring (0008,0090) No Yes
Physician's Name
Imaging Service (0040,2400) No No Not used
Request Comments
Requesting Service (0032,1033) No No Not used

Copyright 2009 General Electric Company. All rights reserved

Page 64 of 126
 DOC0506131 rev3

5.6.5 Visit Entity

5.6.5.1 Visit Identification
Table 5-8 Visit Identification Module Attributes
Attribute Name Tag Required Mapped Note
for into the
Modality Image?
Worklist?
Admission ID (0038,0010) No No
Institution Name (0008.0080) No No Not used

5.6.5.2 Visit Status

Table 5-9 Visit Status Module Attributes
Attribute Name Tag Required Mapped Note
for into the
Modality Image?
Worklist?
Current Patient Location (0038,0300) No No

5.6.5.3 Visit Relationship

Table 5-10 Visit Relationship Module Attributes
Attribute Name Tag Required Mapped Note
for into the
Modality Image?
Worklist?
Referenced Patient Sequence (0008,1120) No No Not used
>Referenced SOP Class UID (0008,1150) No No Not used
>Referenced SOP Instance UID (0008,1155) No No Not used

5.6.5.4 Visit Admission

No data elements are requested from the Visit Admission Module.

Copyright 2009 General Electric Company. All rights reserved

Page 65 of 126
 DOC0506131 rev3

5.6.6 Patient Entity

5.6.6.1 Patient Relationship
No data elements are requested from the Patient Relationship Module.
5.6.6.2 Patient Identification
Table 5-11 Patient Identification Module Attributes
Attribute Name Tag Required Mapped Note
for into the
Modality Image?
Worklist?
Patient's Name (0010,0010) Yes Yes Matching is supported as follows:
either no Patient’s Name is supplied
(universal matching), the patient’s last
(family) name specified on the
scanner’s Preferences screen is
supplied, or the Patient’s first name for
matching; this is user selectable. Wild
card matching is implemented for
leading and trailing characters.
Patient Name is displayed on the
“Worklist Schedule” screen.
Patient ID (0010,0020) Yes Yes Matching is supported using single
value matching from the scanner’s
Preferences page.
Patient ID is displayed on the “Worklist
Schedule” screen.
Other Patient ID’s (0010,1000) No No Displayed on “More Info...” screen.

5.6.6.3 Patient Demographic

Table 5-12 Patient Demographic Module Attributes
Attribute Name Tag Required Mapped Note
for into the
Modality Image?
Worklist?
Patient’s Birth Date (0010,0030) No Yes Displayed on the “More Info..“
screen.
Patient's Sex (0010,0040) No Yes Displayed on the “More Info..”
screen.
Patient's Weight (0010,1030) No No Limited to maximum value of
999 kg.
Displayed on “More Info...”
screen.
Weight is an operator entry
requirement for MR on the
“Patient Information” screen.
Confidentiality constraint on (0040,3001) No No Not used
patient data
Patient’s Size (0010,1020) No No Not used
Patient’s Address (0010,1040) No No Not used

Copyright 2009 General Electric Company. All rights reserved

Page 66 of 126
 DOC0506131 rev3

Patient’s Telephone (0010,2154) No No Not used

Numbers
Patient Comments (0010,4000) No No Displayed on “More Info...”
screen.
Ethnic Group (0010,2160) No No Displayed on “More Info...”
screen.

5.6.6.4 Patient Medical

Table 5-13 Patient Medical Module Attributes
Attribute Name Tag Required Mapped Note
for into the
Modality Image?
Worklist?
Patient State (0038,0500) No No Not used
Pregnancy Status (0010,21C0) No No Displayed on “Other Information”
screen.
Medical Alerts (0010,2000) No No
Contrast Allergies (0010,2110) No No Displayed on “Other Information”
screen.
Special Needs (0038,0050) No No Can be configured for user display
Additional Patient History (0010,21B0) No Yes Displayed on “Other Information”
screen.

5.7 PRIVATE DATA DICTIONARY

The GE MR system does not define any private attributes within the Modality Worklist Information Model.
Private attributes received from a remote AE are discarded.

Copyright 2009 General Electric Company. All rights reserved

Page 67 of 126
 DOC0506131 rev3

6 PERFORMED PROCEDURE STEP CONFORMANCE STATEMENT

6.0 Introduction

This section of the DICOM Conformance Statement specifies the compliance to DICOM conformance
requirements for the Performed Procedure Step feature on this GEHC product. Note that the format of this
section strictly follows the format defined in DICOM Standard PS 3.2 (Conformance). Please refer to that
part of the standard while reading this section. The PPS option for the GE MR system allows a Modality
Performed Procedure Step to be communicated to the Hospital/Radiology information system. The PPS
feature is providing the DICOM Modality Performed Procedure Step service as a service class user (SCU).

This feature works in conjunction with DICOM Modality Work-list feature, if installed. However the
conformance of this feature is independent of Modality work-list feature. For information on conformance of
Modality Work-List feature to DICOM standard please refer to the appropriate section of the document.

6.1 Implementation Model

The DICOM ‘Performed Procedure Step’ service is provided by the MPPS DICOM SCU. The MPPS DICOM
SCU is commanded to perform Modality Performed Procedure Step services automatically at the beginning
and end of acquisition.

6.1.1 Application Data Flow Diagram

The basic Application models for the feature are shown in the following illustration:

Patient Scan with

MWL data

MPPS Remote
Patient Scan DICOM MPPS SCP
without MWL data SCU

DICOM
Standard
Interface

6.1.2 Functional Definition of AEs

The PPS DICOM SCU is implemented as an application process on the scanner host computer. It runs as a
daemon serving requests from other applications to send the PPS information to the remote AE and return
the results to the requesting application.

Copyright 2009 General Electric Company. All rights reserved

Page 68 of 126
 DOC0506131 rev3

The PPS DICOM SCU initiates the following functions.

• Start PPS: Initiates a DICOM association in order to create a DICOM Modality Performed Procedure
Step SOP instance in the remote AE. If the remote AE accepts a presentation context applicable to Modality
performed Procedure Step, the PPS DICOM SCU will issue a request to create the SOP instance in the
remote AE via the N-CREATE service.

• Complete PPS: Initiates a DICOM association in order to update a DICOM Modality Performed Step
instance that is already created with the remote AE. If the remote AE accepts a presentation context
applicable to Modality performed Procedure Step, the PPS DICOM SCU will issue a request to update the
SOP instance in the remote AE via the N-SET service. The PPS Status is set to ‘COMPLETED’.

• Discontinue PPS: Initiates a DICOM association in order to update a DICOM Modality Performed Step
instance that is already created with the remote AE. If the remote AE accepts a presentation context
applicable to Modality performed Procedure Step, the PPS DICOM SCU will issue a request to update the
SOP instance in the remote AE via the N-SET service. The PPS Status is set to ‘DISCONTINUED’.

6.1.3 Sequencing of Real-World Activities

6.1.3.1 PPS from Acquisition System with MWL data

The system has a Modality Work-list Server AE installed. Work-List information is obtained from HIS/RIS
system through the use of Basic Work-list Management Service. Use of the information retrieved in the
creation of Image SOP instance is described in the Modality Work-list Conformance statement. Use of the
information retrieved in MPPS SOP instances is described later in this document.

• The system initiates a ‘Start PPS’ after the first image is acquired into the database. The system
retrieves necessary information related to the Scheduled Procedure Step from Modality Work-list Server.
PPS DICOM SCU initiates a MPPS (Modality Performed Procedure Step) N-CREATE request to the remote
AE (MPPS SCP), in-order to create a MPPS SOP instance at the remote AE.

• The MPPS SCP returns response indicating the success/failure of the request execution. The PPS state
information is updated in the system based on the response data. The DICOM association is closed.

• Please refer to Section 6.12 for specific Scheduled Procedure Step and Performed Procedure Step
information included by the system.

• At the end of image acquisition, system initiates a ‘Complete PPS’ or ‘Discontinue PPS’ based on the
choice selected by the user using the user interface provided.

• The remote AE returns response indicating the success/failure of the request execution. The PPS state
information is updated in the system based on the response data.

6.1.3.2 PPS from acquisition system without MWL data

The system either does not have a Modality Work-list Server AE installed or a Modality Work-list Server AE
installed but no Work-List information is obtained from HIS/RIS system for the current procedure that is being
performed. The information required for performing the procedure is supplied through the user interface of
the system. The use of this information in MPPS SOP instances is described later in this document.

• The system initiates a ‘Start PPS’ after the first image is acquired into the database. PPS DICOM SCU
initiates a MPPS (Modality Performed Procedure Step) N-CREATE request to the remote AE (MPPS SCP),
in-order to create a MPPS SOP instance at the remote AE.

Copyright 2009 General Electric Company. All rights reserved

Page 69 of 126
 DOC0506131 rev3

• The MPPS SCP returns response indicating the success/failure of the request execution. The PPS state
information is updated in the system based on the response data. The DICOM association is closed.

• At the end of image acquisition, system initiates a ‘Complete PPS’ or ‘Discontinue PPS’ based on the
choice selected by the user using the user interface provided.

• The remote AE returns response indicating the success/failure of the request execution. The PPS state
information is updated in the system based on response data.

6.2 AE Specification

6.2.1 PPS DICOM SCU Specification

This Application Entity provides Standard Conformance to the following DICOM SOP Classes as an SCU:

SOP Class Name SOP Class UID

Modality Performed Procedure Step 1.2.840.10008.3.1.2.3.3

6.2.1.1 Association Establishment Policies

6.2.1.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 from an association initiated by the PPS DICOM SCU is:

Maximum Length PDU 32 Kbytes

The SOP Class Extended negotiation is not supported.

The maximum number of presentation negotiation items that will be proposed is 1.

The user information items sent by this AE are

• Maximum PDU Length

• Implementation UID

6.2.1.1.2 Number of Associations

The PPS DICOM SCU will initiate only one DICOM association at any time to perform a PPS operation to the
remote AE.

6.2.1.1.3 Asynchronous Nature

Asynchronous mode is not supported. All operations are performed synchronously.

Copyright 2009 General Electric Company. All rights reserved

Page 70 of 126
 DOC0506131 rev3

6.2.1.1.4 Implementation identifying information

Please refer to Section 1.1 for details on specific GE MR system information.

6.2.1.2 Association Initiation Policy

The PPS DICOM SCU initiates a new association for every PPS operation initiated.

6.2.1.2.1 Real-World Activity: Performed Procedure Step creation and update

6.2.1.2.1.1 Associated Real-World Activity

The real-world activities are mentioned in section 6.1.3 Sequencing of Real-World Activities. Each of the real
world activity results in either creating a new Performed procedure Step SOP instance at the remote SCP or
updating an already created Performed Procedure Step SOP instance as per the DICOM standard.

6.2.1.2.1.2 Proposed Presentation Context Table

The following table shows the proposed presentation contexts for the PPS DICOM SCU after any of the real-
world activity listed in section 6.1.3 Sequencing of Real-World Activities, is initiated.

Presentation Context Table – Proposed

Abstract Syntax Transfer Syntax Role Extended
Name UID Name List UID List Negotiation

Modality 1.2.840.10008.3.1.2.3.3 Implicit VR 1.2.840.10008.1.2 SCU None

Performed Little Endian
Procedure Step

6.2.1.2.1.2.1 SOP Specific DICOM Conformance Statement for MPPS SOP class
If the remote AE does not support the proposed Presentation context, an appropriate error message is
logged. Only one association is opened at a time.
Please refer to section 6.10 for details about Status codes.

6.2.1.3 Association Acceptance Policy

The PPS DICOM SCU does not respond to attempts by remote AE to open an association.

6.3 COMMUNICATION PROFILES

6.3.1 Supported Communication Stacks (PS 3.8)

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

Copyright 2009 General Electric Company. All rights reserved

Page 71 of 126
 DOC0506131 rev3

6.3.2 OSI Stack

The OSI Communication stack is not supported by this implementation.

6.3.3 TCP/IP Stack

The TCP/IP stack is inherited from the operating system

6.3.3.1 API

Not Applicable to this product.

6.3.3.2 Physical Media Support

Ethernet 802.3 provides the physical network layer for this product.

6.3.4 Point-to-Point Stack

The Point-to-Point Stack is not supported by this implementation.

6.4 EXTENSIONS/SPECIALIZATION/PRIVATIZATION

6.4.1 Standard Extended/Specialized/Private SOPs

PPS for the GE MR system does not implement any private SOP classes.

6.4.2 Private Transfer Syntaxes

PPS for the GE MR system does not implement any private Transfer Syntaxes.

6.5 CONFIGURATION

The PPS feature is configured by GEHC Field Service Engineers. The DICOM configuration items below are
configurable or re-configurable by the Field Service Engineer

Copyright 2009 General Electric Company. All rights reserved

Page 72 of 126
 DOC0506131 rev3

6.5.1 AE Title/Presentation address Mapping

PPS allows for the configuration of the following parameters that pertain to the remote AE.

• Remote MPPS AE IP Address: IP Address used to contact the remote MPPS AE

• Remote AE (HIS/RIS) IP Port: IP Port used to contact the remote MPPS AE

• Remote MPPS AE Title: Application Entity Title used to contact the remote
MPPS AE

These parameters define where the MPPS requests will be directed. Configuration of these parameters is
performed by GEMS Field Service engineers, using the installation facilities.

6.5.2 Configurable Parameters

The max PDU length is configurable and the default value set is 32K. The association timeout is infinite and
not configurable.

6.6 SUPPORT OF EXTENDED CHARACTER SETS

PPS feature for the GE MR system does not support any extended character set.

6.7 CODES AND CONTROLLED TERMINOLOGY

The product uses coded terminology as defined below.

6.7.1 Mapped Coded Terminology

The product maps, without change, coded terminology values supplied in Modality Worklist Scheduled
Procedure Steps into Image SOP Instance and Modality Performed Procedure Step attributes, as described
in Sections 5 and 6.

6.8 SECURITY PROFILES

The product does not conform to any defined DICOM Security Profiles. It is assumed that the product is used
within a secure environment. It is assumed that a secure environment includes at a minimum:
• Firewall or router protections to ensure that only approved external hosts have network access to the
product.
• Firewall or router protections to ensure that the product only has network access to approved
external hosts and services.
• Any communications with external hosts and services outside the locally secured environment use
appropriate secure network channels (such as a Virtual Private Network (VPN)).

6.9 N-CREATE & NSET REQUEST MESSAGE

PPS Feature for the GE MR system supports subset of named attributes listed in Table F.7.2.1 in PS3.4 of
DICOM standard. That is, attributes that are not explicitly referenced by name in the table are not supported.

Copyright 2009 General Electric Company. All rights reserved

Page 73 of 126
 DOC0506131 rev3

(Example is last row in the table reads “All other attributes from Radiation Dose Module and Billing and
Material Code Module”. The attributes referenced here are not supported).

For the MPPS associated with an acquisition & inline post processing apps, the following attributes are
copied from the Modality Work-list SCU into the MPPS request Message, if procedure performed
corresponds to the SPS information retrieved through the Modality Work-list.

The GE MR system supports selection of single SPS for acquisition and inline post processing operations

• Single SPS selection results in single PPS message

• Referenced Study Sequence -. This attribute will be present only if SPS information is available from
Modality Work-list SCU.
• Mapping of SPS data to MPPS SOP instance is explained in section 6.11
• Mapping of specific SPS data to MR DICOM IMAGE HEADER , for PPS is explained in section 6.12
• Referenced Study Sequence – The sequence is sent empty in the MPPS message if not available in the
image
• Scheduled Step Attribute Sequence – a maximum of ONE item is supported.
• Referenced Patient Sequence – This sequence is sent empty if not available in image
• Scheduled Protocol Code Sequence – The sequence is sent empty if not available in the image.
• Performed Procedure Step Start date & Performed Procedure Step start time – corresponds to the date
and time of the first image generated in acquisition.
• Performed Procedure Step end date & Performed Procedure Step end time – corresponds to the date
and time of user choosing COMPLETE or DISCONTINUE.
• Procedure Code Sequence – This sequence is sent with ZERO items in the MPPS message
• Performed Protocol Code Sequence – This sequence is sent with ZERO items in the MPPS message.

• Referenced Non Image Composite SOP Instance Sequence – The sequence is sent with ZERO items in
the MPPS message since MPPS is not supported for GSPS and SR

6.10 ERROR HANDLING AND RECOVERY

PPS DICOM SCU does not define any extended error codes. The standard error codes are handled. On a
response with status ‘success’ for the N-CREATE or N-SET request, the system updates the state and
indicates the same on the user interface. On a response with status other than ‘success’ the operation is
deemed ‘Failed’.

If the operation is ‘Failed’, detailed message is logged into system log-file and system automatically retries
the failed operation.

Copyright 2009 General Electric Company. All rights reserved

Page 74 of 126
 DOC0506131 rev3

6.11 Use of Specific DICOM Data

The following table (along with the Note at the end) gives specific usage of some of attributes in the MPPS
SOP instance created, with reference to each of the real-world scenarios mentioned in section 6.1.3 of this
document.

Convention used for tag types for NCREATE and N-SET IOD are as follows

NA : Shall not be present

Type 1 : Mandatory. Both tag and value shall be present.
Type 2 : Tag shall be present. Value is optional.

Example: If a particular tag say, patient name (0x10,0x10) is marked as (2/NA) , then (0x10,0x10) tag shall
be present in MPPS Ncreate IOD with tag value being optional. Further, tag (0x10,0x10) shall not be part of
MPPS NSET IOD.

Attribute Name Tag Usage in MPPS Instance

(Ncreate/Nset Acquisition Acquisition In-line Post-
type) with MWL without MWL data Processing
data
Specific Character Set (0008,0005) Not sent
(1C/1C) Not sent Not sent
Scheduled Step Attribute (0040,0270) Only one item Only one item Only one item
Sequence (1/NA)
>Study Instance UID (0020,000D) Copied from Created at the Same as in the case
(1/NA) SPS, if option to scanner of MR images
copy is selected
or else created
at the scanner
>Referenced Study (0008,1110) Copied from Sent empty Same as for the
Sequence (2/NA) SPS if selected, source images if
else sent empty present, else sent
empty
>Accession Number (0008,0050) Copied from User input on the Same as for the
(2/NA) SPS if selected, scanner, if entered., source images
else sent empty else sent empty
>Placer Order (0040,2016) Copied from Not sent as part of Same as for the
Number/Imaging Service (3/NA) SPSif selected, the header source images
Request else sent empty
>Filler Order (0040,2017) Copied from Not sent as part of Same as for the
Number/Imaging Service (3/NA) SPS if selected, the header source images
Request else sent empty
>Requested Procedure ID (0040,1001) Copied from User Input in the Same as for the
(2/NA) SPS if selected, scanner, else sent source images if
else sent empty empty present, else sent
empty
>Requested Procedure (0032,1060) Copied from Sent empty Same as for the
Description (2/NA) SPS if selected, source images if
else sent empty present, else sent

Copyright 2009 General Electric Company. All rights reserved

Page 75 of 126
 DOC0506131 rev3

Attribute Name Tag Usage in MPPS Instance

(Ncreate/Nset Acquisition Acquisition In-line Post-
type) with MWL without MWL data Processing
data
empty
>Scheduled Procedure (0040,0009) Copied from Sent empty Same as for the
Step ID (2/NA) SPS if selected, source images if
else sent empty present, else sent
empty
>Scheduled Procedure (0040,0007) Copied from Sent empty Same as for the
Step Description (2/NA) SPS if selected, source images if
else sent empty present, else sent
empty
>Scheduled Protocol Code (0040,0008) Copied from Sent empty Same as for the
Sequence (2/NA) SPS if selected, source images if
else sent empty present, else sent
empty
Patient's Name (0010,0010) Copied from User input on the Same as for the
(2/NA) SPS if selected, scanner. If not source images
else sent empty entered, sent empty
Patient ID (0010,0020) Copied from User input on the Same as for the
(2/NA) SPS, if selected scanner source images
Patient's Birth Date (0010,0030) Copied from User input on the Same as for the
(2/NA) SPS, if selected, scanner. If not source images
else left empty entered, sent empty
Patient's Sex (0010,0040) Copied from User input on the Same as for the
(2/NA) SPS, if selected, scanner, if not source images
else sent empty entered, sent empty
Referenced Patient (0008,1120) Copied from Sent empty Same as for the
Sequence (2/NA) SPS, if selected, source images
else sent empty
Performed Procedure Step (0040,0253) Unique string Unique string Unique string
ID (1/NA) generated at generated at scanner generated at
scanner for for entire session. scanner for entire
entire session. session.
Performed Station AE Title (0040,0241) Local system Local system host- Local system host-
(1/NA) host-name name name
Performed Station Name (0040,0242) Copied from Copied from Station Same as for the
(2/NA) Station name name (0008,1010) source images
(0008,1010)
Performed Location (0040,0243) Copied from Copied from suite id Same as for the
(2/ NA) suite id (0009,1002) source images
(0009,1002)
Performed Procedure Step (0040,0244) Same as date of Same as date of first Same as date of first
Start Date (1/ NA) first scan scan scan
Performed Procedure Step (0040,0245) Same as time of Same as time of first Same as time of first
Start Time (1/ NA) first scan scan scan
Performed Procedure Step (0040,0254) Copied from Copied from Same as for the
Description (2/2) (0008,1030) if (0008,1030) if source images
available; available; otherwise
otherwise left left blank
blank
Performed Procedure Step (0040,0252) Status is one of Status is one of IN
status (1/1) IN PROGRESS, PROGRESS, Status is one of IN
COMPLETED or COMPLETED or PROGRESS,

Copyright 2009 General Electric Company. All rights reserved

Page 76 of 126
 DOC0506131 rev3

Attribute Name Tag Usage in MPPS Instance

(Ncreate/Nset Acquisition Acquisition In-line Post-
type) with MWL without MWL data Processing
data
DISCONTINUE DISCONTINUED COMPLETED or
D DISCONTINUED
Performed Procedure Type (0040,0255) Set as empty in Set as empty in Set as empty in
Description (2/2) MPPS header MPPS header MPPS header
Procedure Code Sequence (0008,1032) Left blank if Left blank if Left blank if
(2/2) performed performed procedure performed
procedure and and requested procedure and
requested procedure is different. requested procedure
procedure is Else copy from 0032, is different. Else
different. Else 1064 when present in copy from 0032,
copy from 0032, the MWL. 1064 when present
1064 when in the MWL.
present in the
MWL.
Performed Procedure Step (0040,0250) Date when user Date when user Date when user
End Date (2/1) chooses chooses Complete or chooses Complete
Complete or Discontinue action or Discontinue
Discontinue action
action
Performed Procedure Step (0040,0251) Time when user Time when user Time when user
End Time (2/1) chooses chooses Complete or chooses Complete
Complete or Discontinue action or Discontinue
Discontinue action
action
Modality (0008,0060) Value “MR” is Value “MR” is stored Same as for the
(1/ NA) stored in mpps in mpps header source images
header
Study ID (0020,0010) Same as exam Same as exam Same as exam
(2/ NA) number number number
Performed Protocol Code (0040,0260) Copied from Copied from image if same as source
Sequence (2/2) image if present, present, else sent image
else sent empty empty
Performed Series (0040,0340) Sent in the Sent in the MPPS Sent in the MPPS
Sequence (2/1) MPPS header header header
>Performing Physician's (0008,1050) copied from copied from image if Same as source
Name (2/2) image if present, present, else sent image
else sent empty empty
>Protocol Name (0018,1030) The name of the The name of the The name of the
(1/1) protocol protocol selected on protocol selected on
selected on the the scanner. Copied the scanner. Same
scanner. Copied from scanner as source image
from image
>Operator's Name (0008,1070) Copied from User input on the Same as for the
(2/2) SPS if selected, scanner. Sent empty source images
else sent empty if not entered.
> Series Instance UID (0020,000E) Copied from Copied from Image Copied from Image
(1/1) Image
>Series Description (0008,103E) Copied from Copied from Image Copied from Image
(2/2) Image
>Retrieve AE Title (0008,0054) Sent empty Sent empty Sent empty

Copyright 2009 General Electric Company. All rights reserved

Page 77 of 126
 DOC0506131 rev3

Attribute Name Tag Usage in MPPS Instance

(Ncreate/Nset Acquisition Acquisition In-line Post-
type) with MWL without MWL data Processing
data
(2/2)
>Referenced Image (0008,1140) One item for One item for each One item for each
Sequence (2/2) each image image created within image created within
created within the series the series
the series
>Referenced Non Image (0040,0220) Sent empty Sent empty Sent empty
Composite SOP Instance (2/2)
Sequence
>All other attributes from All type 1 and type 2
Performed Series All type 1 and All type 1 and type 2 tags sent
Sequence (which Table type 2 tags sent tags sent
F.7.2.1 of DICOM standard
PS3.4 does not explicitly
list)
All other attributes from Not sent as part Not sent as part of Not sent as part of
Radiation Dose Module and of mpps header mpps header mpps header
Billing and Material Code
Module (which Table
F.7.2.1 of DICOM standard
PS3.4 does not explicitly
list)

Note 1: • When PPS start ( N-CREATE) message is sent, this element will have the value “IN
PROGRESS”
• When PPS end ( N-SET) message is sent, this element will have either “COMPLETE”
or “DISCONTINUE” based on user selection

6.12 USE OF SPECIFIC DICOM DATA

6.12.1 Patient Level

Attribute Name Tag Usage in MR DICOM Image Header

Patient Name (0010,0010) Copied from SPS, if selected
Patient ID (0010,0020) Copied from SPS, if selected
Patient Birthdate (0010,0030) Copied from SPS, if selected
Patient Sex (0010,0040) Copied from SPS, if selected
Referenced Patient Sequence (0008,1120) Copied from SPS, if selected. Added in the private
sequence 0023,1080
Ref. SOP class uid (0008,1150)
Ref. SOP Instance uid (0008,1155)

Copyright 2009 General Electric Company. All rights reserved

Page 78 of 126
 DOC0506131 rev3

6.12.2 Study Level

Attribute Name Tag Usage in MR DICOM Image Header

Study Instance UID (0020,000D) Copied from SPS, if selected
Study Description (0008,1030) Copied from SPS description field or user input in
MWL screen
Study ID (0020,0010) Scanner generated study ID
Referring Physicians name (0008,0090) Copied from SPS, if selected
Accession Number (0008,0050) Copied from SPS, if selected
Referenced Study Sequence (0008,1110) Copied from SPS, if selected
Ref. SOP class uid (0008,1150)
Ref. SOP Instance uid (0008,1155)

6.12.3 Series Level

Attribute Name Tag Usage in MR DICOM Image Header

Modality (0008,1060) Value “MR” is copied
Protocol Name (0018,1030) Name of the selected protocol is copied
Operator Name (0008,1070) Copied from SPS or user input on MWL screen
available. >.
Referenced Performed (0008,1111) Sequence present only if PPS option key is enabled
Procedure Step Sequence
Ref. SOP class uid (0008,1150) Value of MPPS SOP class UID
Ref. SOP Instance uid (0008,1155) Scanner generated unique MPPS SOP Instance UID
Requested Attribute Sequence (0040,0275) Will be present only if SPS, obtained from HIS/RIS is
selected for scanning.
Requested Procedure Id (0040,1001) Copied from SPS, if selected
Scheduled Procedure Step (0040,0009) Copied from SPS, if selected
Id
Scheduled Procedure Step (0040,0007) Copied from SPS, if selected
description
Scheduled Protocol Code (0040,0008) Copied from SPS, if selected
Sequence
Performed Procedure Step Id (0040,0253) Created at the scanner to be added into the N-
Create/N-Set messages. But not included into the
image.
Performed Procedure Step start (0040,0244) Created at the scanner to be added into the N-
date Create/N-Set messages. But not included into the
image.
Performed Procedure Step start (0040,0245) Created at the scanner to be added into the N-
time Create/N-Set messages. But not included into the
image.
Performed Procedure Step (0040,0254) Value copied and set from 0008,1030.
description

Copyright 2009 General Electric Company. All rights reserved

Page 79 of 126
 DOC0506131 rev3

7 Storage Commitment Conformance

7.0 Introduction
The MR system implements the DICOM Storage Commitment Push Model SOP Class. This system
supports Storage Commitment as an SCU only.

7.1 Implementation Model

7.1.1 Application data flow diagram

Illustration 7-0 below shows the data flow diagram for Storage Commitment operation.

Illustration 7-0: Application Data Flow Diagram

Choose
Archive
SAVE
Option DICOM Storage
Server Commitment
Provider
AE
Set
Archive
State

DICOM Standard
Interface

There is only one Real-World activity that will cause the DICOM Server Application Entity (DICOM Server
AE) to initiate an association to a remote DICOM entity that is a Service Class Provider (SCP) of the Storage
Commitment SOP class.

The Choose Archive Save Option Real-World activity consists of an operator choosing a remote DICOM AE
that supports Storage Commitment as provider as the archive device and selecting one or more exam or
series from the local database and choosing either Save Exam or Save Series from the archive menu. The
images to be committed are sent to the remote provider entity first. The Commitment request for the
transferred image instances is sent after the complete image transfer. The Commitment response can come
on same association or on a different association.

The Real-World activity Set Archive State is performed by the DICOM Server AE to respond to an incoming
Storage Commitment response from the remote DICOM AE.

7.1.2 Functional definitions

DICOM Server AE initiates the following operations:
• Negotiates and establishes association with remote Storage Commitment Provider
• Sends the selected images to the remote DICOM AE.
• Closes the association.

Copyright 2009 General Electric Company. All rights reserved

Page 80 of 126
 DOC0506131 rev3

• If all the images are transferred without failures the following steps will be executed. If there are any
failures the job will marked as failed and the Storage Commitment request will not be sent.
• Establishes a new association for sending the commitment request. Note that a Storage
Commitment request does not imply that the acquisition of images is complete.
• R
 eceives the response on same association or on a different association.
• U pdates the archive flag information for successful instances. The archive flag is shared with the
local archive and the two can not be distinguished.

7.1.3 Sequencing of real-world activities

The user has to select the remote commitment provider and the exams/series to be pushed before clicking
Save Exam/Series button on the Archive menu.

7.2 AE Specifications

7.2.1 DICOM Server AE specifications for Storage Commitment

In addition to the SOP Classes defined in Section 2.2.1, the DICOM Server AE provides
Standard Conformance to the following SOP class as an SCU:

SOP class name SOP class UID

Storage Commitment Push model SOP class 1.2.840.10008.1.20.1

7.2.1.1 Association establishment policies

The association establishment policies for the DICOM Server AE are described in Section 2.2.1.1.

7.2.1.2 Association initiation policy

An association is initiated by the Storage SCU to the provider to send the images to be committed. A
separate association is established to send the commitment request.

7.2.1.3 Real World Activity

7.2.1.3.1 Associated Real World Activity - ”Save exam/series”

See Section 2.2.1.2.1. The user selects the exam/series to be archived. All the images currently in the
selected exam/series will be sent to the selected remote archive node (which is also the Storage
Commitment SCP) using DICOM C-STORE operations. Once all the images are transferred the
Commitment request will be sent on a separate association.

7.2.1.3.2 Associated Real World Activity - ”Auto Archive exam/series”

The Auto archive user interface is used to archive the exams/series onto local archive media or the remote
archive node (which shall be a Storage Commitment SCP) without manual interface. If the default device
selected for Auto Archive is a remote Storage Commitment SCP then all the images currently in the specified
exam/series will be sent to the selected Storage commitment SCP using C-STORE operations. On
successful transfer of all the images the Storage Commitment request will be sent.

7.2.1.4 Proposed Presentation Contexts

The Proposed Presentation Context table for the DICOM Storage Commitment SCU is as shown in following
Table.

Copyright 2009 General Electric Company. All rights reserved

Page 81 of 126
 DOC0506131 rev3

Presentation Context Table - Proposal

Abstract Syntax Transfer Syntax Role Extended
Name UID Name List UID List Negotiation
Storage 1.2.840.10008.1.20.1 DICOM Implicit VR 1.2.840.10008.1.2 SCU None
Commitment Push Little Endian
Model

The Storage Commitment SCU can send the commitment request for the following DICOM 3.0 SOP classes.
NAME UID
CT Image Storage SOP Class 1.2.840.10008.5.1.4.1.1.2
MR Image storage SOP Class 1.2.840.10008.5.1.4.1.1.4
PET Image Information Storage 1.2.840.10008.5.1.4.1.1.128
RT Structure Set Storage 1.2.840.10008.5.1.4.1.1.481.3
GEMS PET Raw Information Storage 1.2.840.113619.4.30
Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7
Grayscale Softcopy Presentation State 1.2.840.10008.5.1.4.1.1.11.1
Storage
Enhanced Structured Report 1.2.840.10008.5.1.4.1.1.88.22

7.2.2 Request Processing

The images in the selected exam/series are sent to the remote commitment provider entity using DICOM C-
STORE operations. If there are any failures in the image transfers the Storage commitment request will not
be sent. The corresponding job will be marked as failed and user will be notified of the status of job.

If all the images are successfully transferred then the commitment request will be sent on a different
association with the list of SOP instances.

If the N_ACTION request fails, the job will be marked as failed; otherwise following sequence of actions will
take place:

The SCU waits for N_ACTION_RSP from the provider on the same association for a configurable amount of
time. If it does not receive N_ACTION_RSP during this time it will close the association. It changes the Job
state to ”Wait” indicating the job is waiting for the response from commitment provider. The job will be
marked as failed if the response is not received by “stop job time”. “stop job time” is the maximum duration
the job can wait for responses.

A new Transaction UID will be created for each retry by the user. The old Transaction UID is not applicable
for these requests.

The following DIMSE service elements are supported for the Storage Commitment request and response
processing:

N_ACTION: Requests the remote Storage Commitment SCP to commit to storing the image instances.

N_EVENT_REPORT: The response sent by the remote Storage Commitment SCP. The following attributes
are sent as part of the data set for the N_ACTION:

Copyright 2009 General Electric Company. All rights reserved

Page 82 of 126
 DOC0506131 rev3

STORAGE COMMITMENT MODULE FOR N-ACTION

Attribute Name Tag SCU Use

Transaction UID (0008,1195) Generated for each retry
Storage Media File-Set ID (0088,0130) Not supported
Storage Media File-Set UID (0088,0140) Not supported
Referenced SOP Sequence (0008,1199)
>Referenced SOP Class UID (0008,1150)
>Referenced SOP Instance (0008,1155)
UID
>Storage Media File-Set ID (0088,0130) Not supported
>Storage Media File-Set UID (0088,0140) Not supported

7.2.3 Response Processing

Once the N_EVENT_REPORT response is received, the following actions will be taken depending on the
status of response. The following table lists the attributes supported for the N_EVENT_REPORT from the
SCP. “*” indicates that a value is returned.

STORAGE COMMITMENT MODULE FOR N-EVENT-REPORT

Attribute Name Tag SCU Use Success Failure

Case Case
Transaction UID (0008,1195) Value received from * *
SCP
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) Value received from *
SCP
>Referenced SOP Class UID (0008,1150) Value received from *
SCP
>Referenced SOP Instance (0008,1155) Value received from *
UID SCP
>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) Value received from *
SCP
>Referenced SOP Class UID (0008,1150) Value received from *
SCP
>Referenced SOP Instance (0008,1155) Value received from *
UID SCP
>Failure Reason (0008,1197) Value received from *
SCP

Copyright 2009 General Electric Company. All rights reserved

Page 83 of 126
 DOC0506131 rev3

7.2.3.1 Commit response with SUCCESS status

The Archive flag information in the browser for all the successful instances will be updated. The status will be
changed to “Y”. The job queue entry will be removed.

N_EVENT_REPORT response will be sent on the same association itself. No data set will be sent along with
the response.

7.2.3.2 Commit response with FAILURE status

In the event of complete/partial failure the user will be notified about the status and the job entry will be
paused. There is no attempt made to automatically retry the failed SOP instances. However the user can
manually retry the failed jobs. Such requests will be treated as new requests. This will go through the whole
sequence of operations once again.

The failure reason is ignored. Failed SOP instances will have their archive flag information unaltered.

Note :
The archive status flag in the browser is a shared flag with local archive. When the
status is “Y”, it means that the images are archived but doesn’t specify whether on local
archive device or remote archive device. It is left to the user’s discretion whether the
local SOP instances (with their archive flag set to “Y” ) are to be deleted.

N_EVENT_REPORT response will be sent on the same association itself. No data set will be sent along with
the response.

7.2.4 Association Acceptance Policy

A single association will be accepted at any time to receive Storage Commitment responses. Network
parameters are configurable. Please reference Section 2.5.2.

Copyright 2009 General Electric Company. All rights reserved

Page 84 of 126
 DOC0506131 rev3

8 Grayscale Softcopy Presentation State INFORMATION OBJECT

IMPLEMENTATION
Note: GSPS is supported as an SCU and not as a full SCP. GSPS objects that are produced by the scanner can be
processed as an SCP by the scanner. Other GSPS objects may not be fully supported.

8.0 IOD MODULE TABLE

The Grayscale Softcopy Presentation State Information Object Definition comprises the modules of the
following table, plus Standard Extended and Private attributes. Common modules are described in Appendix
A. GSPS-specific modules are described in Section 8.1. Standard Extended and Private attributes are
described in Appendix B.
Table 8-1 GSPS OBJECT IOD MODULES

Entity Name Module Name Reference

Patient Patient A.3.1
Study General Study A.3.2
Patient Study A.3.3
Series General Series A.3.4
Presentation Series 8.1.1
Equipment General Equipment A.3.5
Presentation State Presentation State Identification 8.1.2
Presentation State Relationship 8.1.2
Presentation State Shutter 8.1.2
Presentation State Mask 8.1.2
Mask Not supported
Display Shutter 8.1.3
Bitmap Display Shutter Not supported
(8.1.4)
Overlay Plane Not supported
Overlay Activation 8.1.5
Displayed Area 8.1.6
Graphic Annotation 8.1.7
Spatial Transformation 8.1.8
Graphic Layer 8.1.9
Softcopy VOI LUT 8.1.10
Softcopy Presentation LUT 8.1.11
SOP Common A.3.10

8.1 GSPS-Specific INFORMATION MODULE DEFINITIONS

Please refer to DICOM Part 3 (Information Object Definitions) for a description of each of the entities,
modules, and attributes contained within the GSPS Information Object.

Copyright 2009 General Electric Company. All rights reserved

Page 85 of 126
 DOC0506131 rev3

8.1.1 Presentation Series Module

Table 8.1-2
Presentation Series MODULE ATTRIBUTES
Attribute Name Tag Type Use
Modality (0008,0060) 1 Value = PR

8.1.2 Presentation State Modules Attributes

The presence of the following characters in the “Use” column indicate the associated module that the attribute is part of:
I- Presentation State Identification
R - Presentation State Relationship
S - Presentation State Shutter
M - Presentation State Mask
Table 8.1-3
Presentation State MODULE ATTRIBUTES
Attribute Name Tag Type Use
Instance Number (0020,0013) 1 [I] Hard coded to 24
Content Label (0070,0080) 1 [I] Value= JAMI_GSPS
Content Description (0070,0081) 2 [I] Value= Original series num & image
range
Presentation Creation Date (0070,0082) 1 [I] Generated
Presentation Creation Time (0070,0083) 1 [I] Generated
Content Creator’s Name (0070,0084) 2 [I] Value= hostname
Referenced Series Sequence (0008,1115) 1 [R] Generated
>Series Instance UID (0020,000E) 1C [R] Filled

>Referenced Image Sequence (0008,1140) 1C [R] Filled

>>Referenced SOP Class UID (0008,1150) 1C [R] Filled
>>Referenced SOP Instance UID (0008,1155) 1C [R] Filled
>>Referenced Frame Number (0008,1160) 1C [R] Not Filled
Shutter Presentation Value (0018,1622) 1C [S] Generated
Mask Subtraction Sequence (0028,6100) 1C [M] Not Filled
>Mask Operation (0028,6101) 1 [M] Not Filled
>Contrast Frame Averaging (0028,6112) 1C [M] Not Filled
Recommended Viewing Mode (0028,1090) 1C [M] Not Filled

Copyright 2009 General Electric Company. All rights reserved

Page 86 of 126
 DOC0506131 rev3

8.1.3 Display Shutter Module

This is present when the image viewport has a rectangular, circular or polygonal clip shape applied to it.
Table 8.1-4
Display Shutter MODULE ATTRIBUTES
Attribute Name Tag Type Use
Shutter Shape (0018,1600) 1 Generated – support one of
RECTANGULAR, CIRCULAR,
POLYGONAL
Shutter Left Vertical Edge (0018,1602) 1C Generated
Shutter Right Vertical Edge (0018,1604) 1C Generated
Shutter Upper Horizontal Edge (0018,1606) 1C Generated
Shutter Lower Horizontal Edge (0018,1608) 1C Generated
Center of Circular Shutter (0018,1610) 1C Generated
Radius of Circular Shutter (0018,1612) 1C Generated
Vertices of the Polygonal Shutter (0018,1620) 1C Generated
Shutter Presentation Value (0018,1622) 1 Generated

8.1.4 Bitmap Display Shutter Module

This Module is not supported.
Table 8.1-5
Bitmap Display Shutter MODULE ATTRIBUTES
Attribute Name Tag Type Use
Shutter Shape (0018,1600) 1 Not Filled
Shutter Overlay Group (0018,1623) 1 Not Filled
Shutter Presentation Value (0018,1622) 1 Not Filled

8.1.5 Overlay/Curve Activation Module

Table 8.1-6
Overlay/Curve Activation MODULE ATTRIBUTES
Attribute Name Tag Type Use
Overlay Activation Layer (60xx,1001) 2C Not supported

Copyright 2009 General Electric Company. All rights reserved

Page 87 of 126
 DOC0506131 rev3

8.1.6 Displayed Area Module

Table 8.1-7
Displayed Area MODULE ATTRIBUTES
Attribute Name Tag Type Use
Displayed Area Selection (0070,005A) 1 Generated
Sequence
>Referenced Image Sequence (0008,1140) 1C Generated
>>Referenced SOP Class UID (0008,1150) 1C Generated
>>Referenced SOP Instance UID (0008,1155) 1C Generated
>>Referenced Frame Number (0008,1160) 1C Not Filled.
>Displayed Area Top Left Hand (0070,0052) 1 Generated
Corner
>Displayed Area Bottom Right (0070,0053) 1 Generated
Hand Corner
>Presentation Size Mode (0070,0100) 1 Generated (Supports SCALE TO FIT,
TRUE SIZE, MAGNIFY)
>Presentation Pixel Spacing (0070,0101) 1C Generated
>Presentation Pixel Aspect Ratio (0070,0102) 1C Not filled
>Presentation Pixel Magnification (0070,0103) 1C Element present only when Presentation
Ratio Size Mode equal to MAGNIFY

Copyright 2009 General Electric Company. All rights reserved

Page 88 of 126
 DOC0506131 rev3

8.1.7 Graphic Annotation Module

Table 8.1-8
Graphic Annotation MODULE ATTRIBUTES
Attribute Name Tag Type Use
Graphic Annotation Sequence (0070,0001) 1 Generated
>Referenced Image Sequence (0008,1140) 1C Generated; present if used.
>>Referenced SOP Class UID (0008,1150) 1C Generated; present if used
>>Referenced SOP Instance UID (0008,1155) 1C Generated; present if used
>>Referenced Frame Number (0008,1160) 1C Generated; present if used
>Graphic Layer (0070,0002) 1 Generated
>Text Object Sequence (0070,0008) 1C Generated; present if used
>>Bounding Box Annotation Units (0070,0003) 1C Generated (PIXEL, DISPLAY); present if
used.
>>Anchor Point Annotation Units (0070,0004) 1C Generated (PIXEL, DISPLAY); present if
used.
>>Unformatted Text Value (0070,0006) 1 Generated
>>Bounding Box Top Left Hand (0070,0010) 1C Generated; present if used
Corner
>>Bounding Box Bottom Right (0070,0011) 1C Generated; present if used
Hand Corner
>>Bounding Box Text Horizontal (0070,0012) 1C Generated (LEFT, RIGHT, CENTER);
Justification present if used
>>Anchor Point (0070,0014) 1C Generated; present if used
>>Anchor Point Visibility (0070,0015) 1C Generated; present if used
>Graphic Object Sequence (0070,0009) 1C Generated; present if used
>>Graphic Annotation Units (0070,0005) 1 Generated
>>Graphic Dimensions (0070,0020) 1 Generated (always “2”)
>>Number of Graphic Points (0070,0021) 1 Generated
>> Graphic Data (0070,0022) 1 Generated
>>Graphic Type (0070,0023) 1 Generated (POINT, POLYLINE,
INTERPOLATED, CIRCLE, ELLIPSE)
>>Graphic Filled (0070,0024) 1C Generated (YES, NO); present if used

8.1.8 Spatial Transformation Module

Table 8.1-9
Spatial Transformation MODULE ATTRIBUTES
Attribute Name Tag Type Use
Image Rotation (0070,0042) 1 Generated (0, 90, 180, 270)
Image Horizontal Flip (0070,0041) 1 Generated (YES, NO)

Copyright 2009 General Electric Company. All rights reserved

Page 89 of 126
 DOC0506131 rev3

8.1.9 Graphic Layer Module

Table 8.1-10
Graphic Layer MODULE ATTRIBUTES
Attribute Name Tag Type Use
Graphic Layer Sequence (0070,0060) 1 Generated
>Graphic Layer (0070,0002) 1 Generated
>Graphic Layer Order (0070,0062) 1 Generated
>Graphic Layer Recommended (0070,0066) 3 Generated
Display Grayscale Value
>Graphic Layer Recommended (0070,0067) 3 Generated
Display RGB Value
>Graphic Layer Description (0070,0068) 3 Generated

8.1.10 Softcopy VOI LUT Acquisition Module

This Module is supported for color tables and window center/window width.
Table 8.1-11
Softcopy VOI LUT MODULE ATTRIBUTES
Attribute Name Tag Type Use
Softcopy VOI LUT Sequence (0028,3110) 1 Generated
>Referenced Image Sequence (0008,1140) 1C Generated
>>Referenced SOP Class UID (0008,1150) 1C Generated
>>Referenced SOP Instance UID (0008,1155) 1C Generated
>>Referenced Frame Number (0008,1160) 1C Not Filled
>VOI LUT Sequence (0028,3010) 1C Not Filled
>>LUT Descriptor (0028,3002) 1C Not Filled
>>LUT Explanation (0028,3003) 3 Not Filled
>>LUT Data (0028,3006) 1C Not Filled
>Window Center (0028,1050) 1C Generated
>Window Width (0028,1051) 1C Generated
>Window Center & Width (0028,1055) 3 Generated
Explanation

8.1.11 Softcopy Presentation LUT Module

Table 8.1-12
Softcopy Presentation LUT MODULE ATTRIBUTES
Attribute Name Tag Type Use
Presentation LUT Sequence (2050,0010) 1C Generated
>LUT Descriptor (0028,3002) 1C Generated
>LUT Explanation (0028,3003) 3 Generated
>LUT Data (0028,3006) 1C Generated
Presentation LUT Shape (2050,0020) 1C Generated (IDENTITY, INVERSE)

Copyright 2009 General Electric Company. All rights reserved

Page 90 of 126
 DOC0506131 rev3

9 ENHANCED STRUCTURED REPORT INFORMATION OBJECT

IMPLEMENTATION

9.0 IOD MODULE TABLE

The Enhanced Structured Report Information Object Definitions comprise the modules of the following
tables, plus Standard Extended and Private attributes. Common modules are described in Appendix A. SR
specific modules are described in Section 9.1. Standard Extended and Private attributes are described in
Section 9.2.

Table 9-1 ENHANCED SR DOCUMENT IOD MODULES

Entity Name Module Name Reference

Patient Patient A.3.1
Study General Study A.3.2
Patient Study A.3.3
Series SR Document Series 9.1.1
Equipment General Equipment A.3.5
Document SR Document General 9.1.2
SR Document Content 9.1.3
SOP Common 9.1.4

9.1 INFORMATION MODULE DEFINITIONS

Please refer to DICOM Part 3 (Information Object Definitions) for a description of each of the entities,
modules, and attributes contained within the SR Information Objects.

9.1.1 SR Document Series Module

Table 9.1-2 SR DOCUMENT SERIES MODULE ATTRIBUTES
Attribute Name Tag Type Use
Modality (0008,0060) 1 Value = SR
Series Instance UID (0020,000E) 1 Generated
Series Number (0020,0011) 1 Generated
Referenced Performed Procedure (0008,1111) 2 Empty – zero length
Step Sequence

9.1.2 SR Document General Module

Copyright 2009 General Electric Company. All rights reserved

Page 91 of 126
 DOC0506131 rev3

Table 9.1-3
SR DOCUMENT GENERAL MODULE ATTRIBUTES
Attribute Name Tag Type Use
Instance Number (0020,0013) 1 Generated.
Completion Flag (0040,A491) 1 Copied from source DICOM header or
entered by the user.
Enumerated Values:
PARTIAL = Partial content.
COMPLETE = Complete content.
Completion Flag Description (0040,A492) 3 Copied from source DICOM header.
Verification Flag (0040,A493) 1 Set to ‘UNVERIFIED’
Content Date (0008,0023) 1 Current date of creation.
Content Time (0008,0033) 1 Current time of creation.
Verifying Observer Sequence (0040,A073) 1C
>Verifying Observer Name (0040,A075) 1 Copied from source DICOM header or
entered by the user.
>Verifying Observer Identification (0040,A088) 2 Empty.
Code Sequence
>Verifying Organization (0040,A027) 1 Copied from source DICOM header or
entered by the user.
>Verification DateTime (0040,A030) 1 Current date and time of verification.
Predecessor Documents (0040,A360) 1C Not supported
Sequence
Identical Documents Sequence (0040,A525) 1C Not supported
Referenced Request Sequence (0040,A370) 1C Not supported
Performed Procedure Code (0040,A372) 2 Empty.
Sequence
Current Requested Procedure (0040,A375) 1C Generated using
Evidence Sequence Source’s Study Instance UID, Series
Instance UID, SOP Instance UID and
SOP Class UID.
> Referenced Series Sequence 0008,1115 1C Generated using
Source’s Series Instance UID, SOP
Instance UID and SOP Class UID.
>> Referenced SOP Sequence 0008,1199 1C Generated using
Source’s SOP Instance UID and SOP
Class UID.
>>> Referenced SOP Class UID 0008,1150 1C Copied from source DICOM header.
(Source’s SOP Class UID)
>>> Referenced SOP Instance 0008,1155 1C Copied from source DICOM header
UID
>> Series Instance UID 0020,000E 1C Generated
> Study Instance UID 0020,000D 1C Copied from source DICOM header
Pertinent Other Evidence (0040,A385) 1C Empty.
Sequence

Copyright 2009 General Electric Company. All rights reserved

Page 92 of 126
 DOC0506131 rev3

9.1.3 SR Document Content Module

Table 9.1-4
SR DOCUMENT CONTENT MODULE ATTRIBUTES
Attribute Name Tag Type Use
Observation DateTime (0040,A032) 1C Copied from source DICOM header.
Content Template Sequence (0040,A504) 1C
> Mapping Resource (0008,0105) 1 DCMR
> Template Identifier (0040,DB00) 1 2000
Value Type (0040,A040) 1 Copied from source DICOM header.
Defined Terms:
TEXT, NUM, IMAGE, CONTAINER
Continuity of Content (0040,A050) 1C Copied from source header.
Enumerated Values:
SEPARATE, CONTINUOUS
Concept Name Code Sequence (0040,A043) 1C Copied from source DICOM header.
> Code Value (0008,0100) 1 Defined terms: (Also see Table 9.1-5)
18755-9, G-C1E8, 121064,
121070, 120172, 121062,
121060, Functool-0051,
Functool-0052, Functool-0053,
Functool-0055, Functool-0057,
Functool-0050, CAPTURE,
20298-6, mm2
> Code Scheme Designator 0008,0102 1 Defined terms: (Also see Table 9.1-5)
LN, SNM3, DCM, 99GEMS,
UCUM
> Code Meaning 0008,0104 1 Defined terms: (Also see Table 9.1-5)
MRI Report, Best Illustrations,
Current Procedure Description,
Findings, Impressions, Request,
History, Series Images,
Functional Images, Functio,
Name, ROI ID, Description,
Location, Image Capture, ROI
Square millimeter
Text Value 0040,A160 1C Text of items like Description, Findings,
Procedure, etc.
Content Sequence (0040,A730) 1C SR content: the sequence of top level
content items.
> Relationship Type (0040,A010) 1 Copied from source header.
Defined Terms:
CONTAINS, HAS PROPERTIES,
HAS OBS CONTEXT, HAS ACQ
CONTEXT, INFERRED FROM,
SELECTED FROM, HAS CONCEPT
MOD
> Referenced Content Item (0040,DB73) 1C Not used.
Identifier

Copyright 2009 General Electric Company. All rights reserved

Page 93 of 126
 DOC0506131 rev3

9.1.3.1 SR Document Content Descriptions

The following table describes defined terms for the SR Document Module.
Table 9.1-5
SR DOCUMENT GENERAL MODULE ATTRIBUTES
Code Value Code Scheme Designator Code Meaning Use
(0008,0100) (0008,0102) (0008,0104)
18755-9 LN MRI Report Generated
G-C1E8 DCM Best Illustrations Generated
121064 DCM Current Procedure Descriptions Generated
121070 DCM Findings Generated
120172 DCM Impressions Generated
121062 DCM Request Generated
121060 DCM History Generated
Functool-0051 99GEMS Series Images Generated
Functool-0052 99GEMS Functional Images Generated
Functool-0053 99GEMS Function Name Generated
Functool-0055 99GEMS ROI ID Generated
Functool-0057 99GEMS Description Generated
Functool-0050 99GEMS Location Generated
CAPTURE DCM Image Capture Generated
20298-6 SNM3 ROI Generated
mm2 UCUM Square millimeter Generated

9.1.4 SOP Common Module

Table 9.1-6
SOP COMMON MODULE ATTRIBUTES

Attribute Name Tag Type Attribute Description

SOP Class UID (0008,0016) 1 Enumerated Values:
1.2.840.10008.5.1.4.1.1.88.22

SOP Instance UID (0008,0018) 1 Unique UID auto generated by system.

Specific Character Set (0008,0005) 1C Copied from source DICOM header.
Instance Creation Date (0008,0012) 3 Current date of creation.
Instance Creation Time (0008,0013) 3 Current time of creation.
Instance Creator UID (0008,0014) 3 Empty.
Instance Number (0020,0013) 3 Copied from source DICOM header.

Copyright 2009 General Electric Company. All rights reserved

Page 94 of 126
 DOC0506131 rev3

9.2 Standard Extended and Private Data Attributes

The Product supports the Standard and Private Attributes defined in the following sections in Standard
Extended SR SOP Instances as Type 3 data elements.

9.2.1 Private Group GEMS_0039

Table 9.2-1
Private Group GEMS_0039

Attribute Name Tag VR VM Attribute Description and Use

Application specific data (0039,1095) LO 1 VV#<application_version>#<applic
ation_name>

9.3 Standard Extended and Private CONTEXT Groups

Not used.

9.4 Standard Extended and Private Templates

Not used.

Copyright 2009 General Electric Company. All rights reserved

Page 95 of 126
 DOC0506131 rev3

10 SECURITY CONFORMANCE STATEMENT

10.0 DE-IDENTIFICATION
The GE MR system satisfies the following requirements for de-identification as documented in DICOM Part
15 (PS3.15 Security Profiles.) De-identification occurs, for example, when an anonymous patient operation
is performed. This de-identification only covers DICOM attributes that contain protected patient information.
The encrypted data capability is not supported, so once an image has been de-identified no facility is
provided to recover the lost information.

The de-identification specified in this section only applies to GE generated images. All third party images
have only the standard DICOM elements de-identified, all private tags (non-GE private tags) within these
images are dropped.

De-identification supports the following object types:

• MR Image Objects
De-identification does not support the following object types:
• Secondary capture images
• Structured reports
• Grayscale presentation state objects

This de-identification specification applies when the GE MR system is configured for full de-identification. If
the system is configured for partial de-identification, some attributes will remain unchanged.

Table 10.0-1 provides the list of attributes and the expected action when de-identifying images.
Table 10.0-1
DICOM Attributes De-Identified

DICOM Tag Attribute Name Action Comments

0008,0014 Instance Creator UID element dropped Refer to Note 1
0008,0018 SOP Instance UID assign new UID
0008,0050 Accession Number made zero length
0008,0080 Institution Name made zero length
0008,0081 Institution Address element dropped Refer to Note 1
0008,0090 Referring Physician’s Name made zero length
0008,0092 Referring Physician’s element dropped Refer to Note 1
Address
0008,0094 Referring Physician’s element dropped Refer to Note 1
Telephone Numbers
0008,1010 Station Name made zero length
0008,1030 Study Description “ANONYMIZED”
0008,103E Series Description “ANONYMIZED”

Copyright 2009 General Electric Company. All rights reserved

Page 96 of 126
 DOC0506131 rev3

DICOM Tag Attribute Name Action Comments

0008,1040 Institutional Department element dropped Refer to Note 1
Name
0008,1048 Physicians of Record element dropped Refer to Note 1
0008,1050 Performing Physicians’ Name element dropped Refer to Note 1
0008,1060 Name of Physicians Reading made zero length
Study
0008,1070 Operators’ Name made zero length
0008,1080 Admitting Diagnoses element dropped Refer to Note 1
Description
0008,1110 Referenced Study Sequence drop sequence
>0008,1150 Referenced SOP Class UID element dropped
>0008,1155 Referenced SOP Instance element dropped
UID
0008,1140 Referenced Image Sequence drop sequence Special handling is
performed when the
entire exam in de-
identified in one
operation. See Table
10.0-2 for details.
>0008,1150 Referenced SOP Class UID element dropped
>0008,1155 Referenced SOP Instance element dropped
UID
0008,2111 Derivation Description element dropped
0009,1001 Genesis FF Flag element dropped
0010,0010 Patient’s Name “ANONxxxx” xxxx = study id
0010,0020 Patient ID “ANONxxxx” xxxx = study id
0010,0030 Patient’s Birth Date made zero length
0010,0032 Patient’s Birth Time element dropped Refer to Note 1
0010,0040 Patient’s Sex made zero length
0010,1000 Other Patient Ids element dropped Refer to Note 1
0010,1001 Other Patient Names element dropped Refer to Note 1
0010,1010 Patient’s Age made zero length
0010,1020 Patient’s Size element dropped Refer to Note 1

Copyright 2009 General Electric Company. All rights reserved

Page 97 of 126
 DOC0506131 rev3

DICOM Tag Attribute Name Action Comments

0010,1030 Patient’s Weight made zero length
0010,1090 Medical Record Locator element dropped Refer to Note 1
0010,2160 Ethnic Group element dropped Refer to Note 1
0010,2180 Occupation element dropped Refer to Note 1
0010,21B0 Additional Patient’s History made zero length
0010,4000 Patient Comments element dropped Refer to Note 1
0018,1000 Device Serial Number made zero length
0018,1030 Protocol Name made zero length
0020,000D Study Instance UID Assign new UID This value is used for
all images in exam
0020,000E Series Instance UID Assign new UID This value is used for
all images in series
0020,0010 Study ID Retain Study ID This value is used in
patient ID
0020,0052 Frame of Reference UID Assign new UID This value is used for
all images sharing this
UID
0020,0200 Synchronization Frame of element dropped Refer to Note 1
Reference UID
0020,4000 Image Comments element dropped
0040,0275 Request Attributes Sequence drop sequence
>0040,1001 Requested Procedure ID element dropped
>0040,0009 Scheduled Procedure Step ID element dropped
>0040,0007 Scheduled Procedure Step element dropped
Description
>0040,0253 Performed Procedure Step ID element dropped
>0040,0254 Performed Procedure Step
Description
0040,A124 UID element dropped Refer to Note 1
0040,A730 Content Sequence drop sequence Refer to Note 1

Copyright 2009 General Electric Company. All rights reserved

Page 98 of 126
 DOC0506131 rev3

DICOM Tag Attribute Name Action Comments

0043,1061 Scanner Study Entity UID Set to same value as Element may be
(0020,000D) dropped.
0043,1062 Scanner Study ID Set to same value as Element may be
(0020,0010) dropped.
0043,1088 PURE calibration series UID element dropped Special handling is
performed when the
entire exam in de-
identified in one
operation. See Table
10.0-2 for details.
0043,1098 ASSET calibration series UID element dropped Special handling is
performed when the
entire exam in de-
identified in one
operation. See Table
10.0-2 for details.
0045,1000 Annotation group UID set to same value as
(0008,0018)
0088,0140 Storage Media File-set UID element dropped Refer to Note 1
3006,0024 Referenced Frame of element dropped Refer to Note 1
Reference UID
3006,00C2 Related Frame of Reference element dropped Refer to Note 1
UID
Note 1: these elements are not currently present in GE images, however, the described action will occur on
rd
3 party images.

The following additional de-identification occurs when processing an entire exam (create anonymous exam
function.)
Table 10.0-2
Additional De-identification By Element For Exam-based Processing

DICOM Tag Attribute Name Action Comments

0008,1140 Referenced Image Sequence regenerated This sequence is
Sequence regenerated using the
new UIDs generated
for the images within
the exam
>0008,1150 Referenced SOP Class UID
>0008,1155 Referenced SOP Instance element contents updated
UID
0043,1088 PURE calibration image UID set to value assigned to
associated PURE image

Copyright 2009 General Electric Company. All rights reserved

Page 99 of 126
 DOC0506131 rev3

DICOM Tag Attribute Name Action Comments

0043,1098 ASSET calibration series set to value assigned to
UID calibration series

The following special processing is performed based on image type:

Table 10.0-3
De-identification Processing by Image Type

Image Type Processing

MR Image de-identified based on the tables above
SC Image image discarded
GSPS object discarded
SR object discarded

10.1 ASSOCIATION LEVEL SECURITY

The GE MR system provides association level security for Query Retrieve operations. The system will only
allow remote DICOM servers to pull images if the remote DICOM server is defined on the GE MR system.
The remote DICOM server’s IP address, AE title, and Port number must be configured on the GE MR system
for the networking pull to begin.

Note that this association level security only applies to the retrieve request, query operations will be
accepted from any connected DICOM client.

Copyright 2009 General Electric Company. All rights reserved

Page 100 of 126
 DOC0506131 rev3

A. Appendix Standard Data Elements

Enclosed is a listing of the modules/attributes used by this implementation for MR and SC IODs.
Attributes marked with ♠ and shaded are not generated by this software release but were supported in
prior releases. Refer to each product’s DICOM Conformance Statement for details specific to that
release. Refer to the appropriate CT DICOM Conformance Statement for details on the CT IOD.
Enhanced Structured Report IODs are defined in Section 9. Greyscale Softcopy Presentation State
(GSPS) IODs are defined in Section 8. Note that attributes from the DICOM standard that are not part of
the standard MR IOD are also included in this Appendix under section A.3.15.

A.1. MR Specific IOD Definition

A.1.1 MR Image IOD Modules
Entity Name Module Name Reference
Patient Patient A.3.1
Study General Study A.3.2
Patient Study A.3.3
Series General Series A.3.4
Frame of Frame of Reference A.3.13
Reference
Equipment General Equipment A.3.5
Image General Image A.3.6
Image Plane A.3.7
Image Pixel A.3.8
Contrast/Bolus A.3.9
MR Image A.1.2
SOP Common A.3.10

A.1.2 MR Image Module

Attribute Name Tag Type Notes
Image Type (0008,0008) 1 Always sent. See section 2.4.1 for
image type values
Samples per pixel (0028,0002) 1 Always sent.
Photometric Interpretation (0028,0004) 1 Always sent.
Bits Allocated (0028,0100) 1 Always sent.
Scanning Sequence (0018,0020) 1 Always sent.
Sequence Variant (0018,0021) 1 Always sent.
Scan Options (0018,0022) 2 Always sent. (even if value is zero
length)
MR Acquisition Type (0018,0023) 2 2D or 3D depending on acquisition
type.
Sequence Name (0018,0024) 3 Not Used.
Repetition Time (0018,0080) 2C Sent if Scanning Sequence is EP and
Sequence Variant is not SK. Also sent
for non-EP.
Echo Time (0018,0081) 2 Always Sent. (even if value is zero
length)
Inversion Time (0018,0082) 2C Always Sent. (even if value is zero
length)
Echo Train Length (0018,0091) 2 Always Sent. (even if value is zero
length)
Trigger Time (0018,1060) 2C Always Sent. (even if value is zero
length)
Angio Flag (0018,0025) 3 Sent ‘Y’ or ‘N’ from some pulse
sequences

Copyright 2009 General Electric Company. All rights reserved

Page 101 of 126
 DOC0506131 rev3

Attribute Name Tag Type Notes

Number Of Averages (0018,0083) 3 Always sent (even if value is zero
length)
Imaging Frequency (0018,0084) 3 Always sent.
Imaged Nucleus (0018,0085) 3 1H or SPECT
Echo Number (0018,0086) 3 Always sent.
Magnetic Field Strength (0018,0087) 3 Always sent.
Spacing Between Slices (0018,0088) 3 Always sent (even if value is zero
length)
Number of Phase Encoding (0018,0089) 3 Not Used
Steps
Percent Sampling (0018,0093) 3 Always sent (even if value is zero
length)
Percent Phase Field of View (0018,0094) 3 Always sent (even if value is zero
length)
Pixel Bandwidth (0018,0095) 3 Sent if available, else not sent
Nominal Interval (0018,1062) 3 Sent if available, else not sent
Beat Rejection Flag (0018,1080) 3 Not used.
Low R-R Value (0018,1081) 3 Not used.
High R-R Value (0018,1082) 3 Not used.
Intervals Acquired (0018,1083) 3 Sent for Propeller & MR-Echo only.
Intervals Rejected (0018,1084) 3 Not used.
PVC Rejection (0018,1085) 3 Not used.
Skip Beats (0018,1086) 3 Not used.
Heart Rate (0018,1088) 3 Sent if available, else not sent
Cardiac Number of Images (0018,1090) 3 Sent if available, else not sent
Trigger Window (0018,1094) 3 Sent if available, else not sent
Reconstruction Diameter (0018,1100) 3 Always sent. (even if value is zero
length)
Receiving Coil (0018,1250) 3 Sent if available, else not sent.
Transmitting Coil (0018,1251) 3 Sent if available, else not sent.
Acquisition Matrix (0018,1310) 3 Sent if available, else not sent.
Phase Encoding Direction (0018,1312) 3 Always sent.
Flip Angle (0018,1314) 3 Sent if available, else not sent.
Variable Flip Angle Flag (0018,1315) 3 Always sent. Value is ‘Y’ for
RAMPED_x: where x is AP, IS, IR, PA,
SI, or AL, else value is ‘N’.
SAR (0018,1316) 3 Sent if available, else not sent.
DB/dt (0018,1318) 3 Not used.
Temporal Position Identifier (0020,0100) 3 Filled in for some applications only.
Number of Temporal (0020,0105) 3 Filled in for some applications only.
Positions
Temporal Resolution (0020,0110) 3 Always sent. (even if value is zero
length)

A.2. SC Specific IOD Definition

A.2.1 SC Image IOD Modules
Entity Name Module Name Reference
Patient Patient A.3.1
Study General Study A.3.2
Patient Study A.3.3
Series General Series A.3.4

Copyright 2009 General Electric Company. All rights reserved

Page 102 of 126
 DOC0506131 rev3

Equipment General Equipment A.3.5

SC Equipment A.3.14
Image General Image A.3.6
Image Pixel A.3.8
SC Image Not sent (consists of type 3 or
conditional elements where the condition
does not apply)
Modality LUT Only the type 1C elements are sent.
(A.3.11)
VOI LUT A.3.12
SOP Common A.3.10

A.3. MR/SC IOD Module Definitions

A.3.1 Patient Module
Attribute Name Tag Type Notes
Patient's Name (0010,0010) 2 As entered at the user interface or from
worklist. Supports 5 different components
delimited by “^”. Supports a maximum
length of 64 characters including the
delimiter. Delimiters must be set by the
operator, entered from the user interface.
Patient ID (0010,0020) 2 As entered at user interface or from
worklist.
Patient's Birth Date (0010,0030) 2 As entered at user interface or from
worklist.
Patient's Sex (0010,0040) 2 As entered at user interface or from
worklist.
Referenced Patient Sequence (0008,1120) 3 Copied from SPS into private sequence
(0023,1080)
>Referenced SOP Class UID (0008,1150) 1C Copied from SPS into private sequence
(0023,1080).
>Referenced SOP Instance UID (0008,1155) 1C Copied from SPS into private sequence
(0023,1080).
Patient's Birth Time (0010,0032) 3 Not used.
Other Patient IDs (0010,1000) 3 Not used.
Other Patient Names (0010,1001) 3 Not used.
Ethnic Group (0010,2160) 3 Not used.
Patient Comments (0010,4000) 3 Not used.

A.3.2 General Study Module

Attribute Name Tag Type Notes
Study Instance UID * (0020,000D) 1 Value from worklist is used if present.
Value is generated uniquely for each exam
if worklist entry is not present.

Copyright 2009 General Electric Company. All rights reserved

Page 103 of 126
 DOC0506131 rev3

Attribute Name Tag Type Notes

Study Date (0008,0020) 2 Generated for each exam and always
sent.
Study Time (0008,0030) 2 Generated for each exam and always
sent.
Referring Physician's Name (0008,0090) 2 Value from user interface or modality
worklist.
Referring Physician Identification (0008,0096) 3 Not used.
Sequence
Study ID * (0020,0010) 2 Auto-generated sequential number.
Accession Number (0008,0050) 2 Value from user interface or worklist sent.
Study Description (0008,1030) 3 Value from user interface or worklist sent.
Procedure Code Sequence (0008,1032) 3 Not used.
Physician(s) of Record (0008,1048) 3 Not Used.
Physician(s) of Record (0008,1049) 3 Not Used.
Identification Sequence
Name of Physician(s) Reading (0008,1060) 3 Value from user interface or worklist sent.
Study Worklist value of (0008,1060) is used for
the copy if not overridden by the UI.
Physician(s) Reading Study (0008,1062) 3 Not Used.
Identification Sequence
Referenced Study Sequence (0008,1110) 3 Value from the worklist
>Referenced SOP Class UID (0008,1150) 1C Value from the worklist
>Referenced SOP Instance UID (0008,1155) 1C Value from the worklist

* When modality worklist is used, the Study ID associated with a Study Instance UID is not guaranteed to be
constant. If multiple exams are created on the scanner by reusing a single worklist entry, then each use will
be assigned a new study ID. Although all exams will share the same Study Instance UID, each exam will
have its own Study ID. Within the data base browser, each exam will be listed separately by its study ID
(exam number), however, on some PACS systems the exams will be joined into a single study based solely
on the Study Instance UID.

A.3.3 Patient Study Module

Attribute Name Tag Type Notes
Admitting Diagnoses Description (0008,1080) 3 Not Supported. Information will be
removed.
Admitting Diagnoses Code (0008,1084) 3 Not Used.
Sequence
Patient's Age (0010,1010) 3 Calculated from Date of Birth entered at
user interface.
Patient's Size (0010,1020) 3 Not Used.

Copyright 2009 General Electric Company. All rights reserved

Page 104 of 126
 DOC0506131 rev3

Patient's Weight (0010,1030) 3 Value from user interface.

Occupation (0010,2180) 3 Not Used.
Additional Patient’s History (0010,21B0) 3 Value from modality worklist or user
interface. Truncated to 60 characters

A.3.4 General Series Module

Attribute Name Tag Type Notes
Modality (0008,0060) 1 MR
Series Instance UID (0020,000E) 1 Locally Generated UID
Series Number (0020,0011) 2 Generated and always sent.
Laterality (0020,0060) 2C Not sent for some pulse sequences; other
pulse sequences send zero length.
Series Date (0008,0021) 3 Generated for each series and always
sent.
Series Time (0008,0031) 3 Generated for each series and always
sent.
Performing Physicians’ Name (0008,1050) 3 Not Used.
Performing Physician Identification (0008,1052) 3 Not Used.
Sequence
Protocol Name (0018,1030) 3 Filled with series description if series not
from protocol. Can also be entered at the
user interface. Limited to 24 characters.
Series Description (0008,103E) 3 Value from user interface is sent.
Operators' Name (0008,1070) 3 Value from user interface is sent. Limited
to 4 characters.
Operator Identification Sequence (0008,1072) 3 Not Used.
Referenced Performed Procedure (0008,1111) 3 Value used for performed procedure step
Step Sequence
>Referenced SOP Class UID (0008,1150) 1C Value used for performed procedure step
>Referenced SOP Instance UID (0008,1155) 1C Value used for performed procedure step
Body Part Examined (0018,0015) 3 Not Used.
Patient Position (0018,5100) 2C Always sent. As selected by operator when
patient is positioned.
Smallest Pixel Value in Series (0028,0108) 3 Not Used.
Largest Pixel Value in Series (0028,0109) 3 Not Used.
Performed Procedure Step Start (0040,0244) 3 Created at the scanner to be added into
Date the N-Create/N-Set messages. But not
included into the image.
Performed Procedure Step Start (0040,0245) 3 Created at the scanner to be added into
Time the N-Create/N-Set messages. But not
included into the image.
Performed Procedure Step ID (0040,0253) 3 Created at the scanner to be added into
the N-Create/N-Set messages. But not
included into the image.
Performed Procedure Step (0040,0254) 3 Value copied and set from (0008,1030)
Description
Performed Protocol Code (0040,0260) 3 Not Used.
Sequence
Request Attribute Sequence (0040,0275) 3 Will be present only if SPS, obtained from
HIS/RIS is selected for scanning
>Scheduled Procedure Step (0040,0007) 3 Will be present only if SPS, obtained from
Description HIS/RIS is selected for scanning.

Copyright 2009 General Electric Company. All rights reserved

Page 105 of 126
 DOC0506131 rev3

>Scheduled Protocol Code (0040,0008) 3 Will be present only if SPS, obtained from
Sequence HIS/RIS is selected for scanning.
>Scheduled Procedure Step ID (0040,0009) 1C Will be present only if SPS, obtained from
HIS/RIS is selected for scanning.
>Requested Procedure ID (0040,1001) 1C Will be present only if SPS, obtained from
HIS/RIS is selected for scanning.
Comments on Performed (0040,0280) 3 Not Used.
Procedure Step

A.3.5 General Equipment Module

Attribute Name Tag Type Notes
Manufacturer (0008,0070) 2 Always sent as “GE MEDICAL
SYSTEMS”
Institution Name (0008,0080) 3 Sent. Value is configurable. Limited to
32 characters.
Institution Address (0008,0081) 3 Not Used.
Station Name (0008,1010) 3 Sent. Value is configurable. Limited to 8
characters
Institutional Department Name (0008,1040) 3 Not Used.
Manufacturers Model Name (0008,1090) 3 Always sent.
Device Serial Number (0018,1000) 3 Always sent.
Software Versions (0018,1020) 3 Always sent as
“<<SW ver>>\<<plat>>\MR Software
release:<<SW build>>”
Where <<plat>> is “LX” or “MX”
and
Where <<SW build>> is of the example
form “14.0_M4_0620.a”
Full example:
14\LX\MR Software release:14.0_M4_0620.a
Spatial Resolution (0018,1050) 3 Sent only for pre-11.0 GE MR images.
Date of Last Calibration (0018,1200) 3 Not Used.
Time of Last Calibration (0018,1201) 3 Not Used.
Pixel Padding Value ♠ (0028,0120) 3 Not Used.

A.3.6 General Image Module

Attribute Name Tag Type Notes
Image Type (0008,0008) 3 Always sent. See section 2.4.1 for
image type values
Acquisition Date (0008,0022) 3 Generated for each acquisition, always
sent.
Image Date (0008,0023) 2C Generated for each image, always sent.
Acquisition Date/Time (0008,002A) 3 Not Used.
Acquisition Time (0008,0032) 3 Value set at each series prep time,
always sent.
Image Time (0008,0033) 2C Value set at each series prep time,
always sent.
Referenced Image Sequence (0008,1140) 3 Sent for GRx prescribed series images,
1-4 referenced images may be provided
>Referenced SOP Class UID (0008,1150) 1C
>Referenced SOP Instance UID (0008,1155) 1C
>Referenced Frame Number (0008,1160) 3 Not Used.
Derivation Description (0008,2111) 3 Not Used.
Source Image Sequence (0008,2112) 3 Not Used.

Copyright 2009 General Electric Company. All rights reserved

Page 106 of 126
 DOC0506131 rev3

Derivation Code Sequence (0008,9215) 3 Not Used.

Referenced Waveform Sequence (0008,113A) 3 Not Used.
Acquisition Number (0020,0012) 3 Generated for each acquisition, always
sent.
Image Number (0020,0013) 2 Generated sequentially, always sent.
Patient Orientation (0020,0020) 2C Not Used.
Images in Acquisition (0020,1002) 3 Always sent. (Not sent for pre-12.0 GE
MR systems).
Image Comments (0020,4000) 3 Not Used.
Quality Control Image (0028,0300) 3 Not Used.
Burned in Annotation (0028,0301) 3 Used on SC images only.
Lossy Image Compression (0028,2110) 3 Not Used.

A.3.7 Image Plane Module

Attribute Name Tag Type Notes
Slice Thickness (0018,0050) 2 Value always sent.
Image Orientation (Patient) (0020,0037) 1 Value always sent.
Image Position (Patient) (0020,0032) 1 Value always sent.
Slice Location (0020,1041) 3 Value always sent.
Pixel Spacing (0028,0030) 1 Value always sent.

A.3.8 Image Pixel Module

Attribute Name Tag Type Notes
Samples per Pixel (0028,0002) 1 Value always sent.
Photometric Interpretation (0028,0004) 1 Value always sent.
Rows (0028,0010) 1 Value always sent.
Collumns (0028,0011) 1 Value always sent.
Bits Allocated (0028,0100) 1 Value always sent.
Bits Stored (0028,0101) 1 Value always sent.
High Bit (0028,0102) 1 Value always sent.
Pixel Presentation (0028,0103) 1 Value always sent.
Smallest Pixel Value (0028,0106) 3 Sent for some pulse sequences.
Largest Pixel Value (0028,0207) 3 Sent for some pulse sequences.
Planar Configuration (0028,0006) 1C Not Used.
Pixel Aspect Ratio (0028,0034) 1C Not Used.
Red Palette Color Lookup Table (0028,1101) 1C Not Used.
Descriptor
Green Palette Color Lookup Table (0028,1102) 1C Not Used.
Descriptor
Blue Palette Color Lookup Table (0028,1103) 1C Not Used.
Descriptor
Red Palette Color Lookup Table (0028,1201) 1C Not Used.
Data
Green Palette Color Lookup Table (0028,1202) 1C Not Used.
Data
Blue Palette Color Lookup Table (0028,1203) 1C Not Used.
Data

Copyright 2009 General Electric Company. All rights reserved

Page 107 of 126
 DOC0506131 rev3

Attribute Name Tag Type Notes

Pixel Data (7FE0,0010) 1 Value always sent.

A.3.9 Contrast Bolus Module

Attribute Name Tag Type Notes
Contrast/Bolus Agent (0018,0010) 2 Sent if contrast exam, as entered in user
interface.
Contrast/Bolus Agent Sequence (0018,0012) 3 Not Used.

>Code Value (0008,0100) 1C Not Used.

>Coding Scheme Designator (0008,0102) 1C Not Used.

>Code Meaning (0008,0104) 3 Not Used.

Contrast/Bolus Route (0018,1040) 3 Sent if contrast exam, as entered in user

interface.
Contrast/Bolus Administration (0018,0014) 3 Not Used.
Route Sequence
Contrast/Bolus Volume (0018,1041) 3 Not Used.

Contrast/Bolus Start Time (0018,1042) 3 Not Used.

Contrast/Bolus Stop Time (0018,1043) 3 Not Used.

Contrast/Bolus Total Dose (0018,1044) 3 Not Used.

Contrast Flow Rate(s) (0018,1046) 3 Not Used.

Contrast Flow Duration(s) (0018,1047) 3 Not Used.

Contrast/Bolus Ingredient (0018,1048) 3 Not Used.

Contrast/Bolus Ingredient (0018,1049) 3 Not Used.

Concentration

A.3.10 SOP Common Module

Attribute Name Tag Type Notes
SOP Class UID (0008,0016) 1 Always sent

SOP Instance UID (0008,0018) 1 Always sent

Specific Character Set (0008,0005) 1C ISO_IR 100
Instance Creation Date (0008,0012) 3 Not Used.

Instance Creation Time (0008,0013) 3 Not Used.

Instance Creator UID (0008,0014) 3 Not Used.

Instance Number (0020,0013) 3 Always sent.

A.3.12 VOI LUT Module

Attribute Name Tag Type Notes
Window Center (0028,1050) 3 Always sent for secondary capture (one
value)
Window Width (0028,1051) 1C Always sent for secondary capture (one
value)
Window Center & Width (0028,1055) 3 Not Used.

Copyright 2009 General Electric Company. All rights reserved

Page 108 of 126
 DOC0506131 rev3

Explanation
VOI LUT Sequence (0028,3010) 3 Not Used.

>LUT Descriptor (0028,3002) 1C Not Used.

>LUT Explanation (0028,3003) 3 Not Used.

>LUT Data (0028,3006) 1C Not Used.

A.3.13 Frame of Reference Module

Attribute Name Tag Type Notes
Frame of Reference UID (0020,0052) 1 Always sent
Position Reference Indicator (0020,1040) 2 Set to zero length

A.3.14 SC Equipment Module

Attribute Name Tag Type Notes
Modality (0008,0060) 3 Modality of original image (MR or CT)
Conversion Type (0008,0064) 1 Always sent.

A.3.15 Additional Attributes

Attribute Name Tag Type Notes
Trigger Delay Time (0020,9153) 3 Filled in for some applications only.
Time delta from peak of the R wave
and the peak of the echo produced in
ms.
Stack ID (0020,9056) 3 Filled in for some applications only.
Number (starting at 1) of the graphic
prescription slice group the image
belongs to.
In-Stack Position Number (0020,9057) 3 Filled in for some applications only.
Slice number within the stack that this
image belongs to.
Real World Value Mapping (0040,9096) 3 Filled in for some applications only.
Sequence
Real World Value Intercept >0040,9224 3(1C)* Filled in for some applications only.
Real World Value Slope >0040,9225 3(1C) Filled in for some applications only.
*
Real World Value First Value >0040,9216 3(1C) Filled in for some applications only.
Mapped *
Real World Value Last Value >0040,9211 3(1C) Filled in for some applications only.
Mapped *
LUT Explanation >0028,3003 3(1)* Filled in for some applications only.

LUT Label >0040,9210 3(1)* Filled in for some applications only.

Measurement units Code >0040,08EA 3(1C) Filled in for some applications only.
Sequence *
Code value >>0008,0100 3(1C) Filled in for some applications only.
*
Coding Scheme Designator >>0040,0102 3(1C) Filled in for some applications only.
*
Coding Scheme Version >>0040,0103 3(1C) Filled in for some applications only.
*
Code Meaning >>0040,0104 3(1C) Filled in for some applications only.
*
Relative Opacity (0070,0403) 3 Filled in for some applications only.

Copyright 2009 General Electric Company. All rights reserved

Page 109 of 126
 DOC0506131 rev3

♠ indicates: No longer generated

* indicates: While required by the standard to be type 3, elements within a sequence have the intended type
in parentheses.

Copyright 2009 General Electric Company. All rights reserved

Page 110 of 126
 DOC0506131 rev3

B. Appendix Private Data Elements

Below is a listing of private data elements used in this implementation for MR Image IOD definition. This is a
full list of all defined private elements, not all private elements will exist in all images. Attributes marked with
♠ and shaded are not generated by this software release but were supported in prior releases. Refer to each
product’s DICOM Conformance Statement for details specific to that release.

Refer to the appropriate CT DICOM Conformance statement for information on CT Private elements.

B.1 MR Image IOD Private Data Elements Definition

B.1.1. Private Creator Identification (GEMS_IDEN_01)

Attribute Name Tag VR VM
GEHC Private Creator ID (0009,0010) LO 1
Full fidelity ♠ (0009,1001) LO 1
Suite id (0009,1002) SH 1
Product id (0009,1004) SH 1
Image actual date (0009,1027) SL 1
Service id (0009,1030) SH 1
Mobile location number (0009,1031) SH 1
Equipment UID (0009,10E3) UI 1
Genesis Version - now ♠ (0009,10E6) SH 1
Exam Record checksum ♠ (0009,10E7) UL 1
Actual series data time stamp (0009,10E9) SL 1

B.1.2. Private Creator Identification (GEMS_PATI_01)

Attribute Name Tag VR VM
GEHC Private Creator ID (0011,0010) LO 1
Patient Status (0011,1010) SS 1

B.1.3. Private Creator Identification (GEMS_ACQU_01)

Attribute Name Tag VR VM
GEHC Private Creator ID (0019,0010) LO 1
Horiz. Frame of ref. (0019,100F) DS 1
Series contrast (0019,1011) SS 1
Last pseq ♠ (0019,1012) SS 1
Series plane ♠ (0019,1017) SS 1
First scan ras ♠ Not supported for 3plane & RTIA (0019,1018) LO 1
First scan location ♠ Not supported for 3plane & RTIA (0019,1019) DS 1
Last scan ras ♠ Not supported for 3plane & RTIA (0019,101A) LO 1
Last scan loc ♠ Not supported for 3plane & RTIA (0019,101B) DS 1
Display field of view (0019,101E) DS 1
Acquisition Duration (0019,105A) FL 1
Second echo (0019,107D) DS 1
Number of echoes (0019,107E) SS 1
Table delta (0019,107F) DS 1
Contiguous (0019,1081) SS 1
Peak SAR ♠ (0019,1084) DS 1

Copyright 2009 General Electric Company. All rights reserved

Page 111 of 126
 DOC0506131 rev3

Attribute Name Tag VR VM

Monitor SAR ♠ (0019,1085) SS 1
Cardiac repetition time (0019,1087) DS 1
Images per cardiac cycle (0019,1088) SS 1
Actual receive gain analog (0019,108A) SS 1
Actual receive gain digital (0019,108B) SS 1
Delay after trigger (0019,108D) DS 1
Swappf (0019,108F) SS 1
Pause Interval (0019,1090) SS 1
Pause Time (0019,1091) DS 1
Slice offset on freq axis (0019,1092) SL 1
Auto Prescan Center Frequency (0019,1093) DS 1
Auto Prescan Transmit Gain (0019,1094) SS 1
Auto Prescan Analog receiver gain (0019,1095) SS 1
Auto Prescan Digital receiver gain (0019,1096) SS 1
Bitmap defining CVs (0019,1097) SL 1
Center freq. Method (0019,1098) SS 1
Pulse Sequence Mode (0019,109B) SS 1
Pulse Sequence Name (0019,109C) LO 1
Pulse Sequence Date (0019,109D) DT 1
Internal Pulse Sequence Name (0019,109E) LO 1
Transmitting Coil Type (0019,109F) SS 1
Surface Coil Type (0019,10A0) SS 1
Extremity Coil flag (0019,10A1) SS 1
Raw data run number (0019,10A2) SL 1
Calibrated Field strength (0019,10A3) UL 1
SAT fat/water/bone (0019,10A4) SS 1
Receive bandwidth ♠ (0019,10A5) DS 1
User data 0 (0019,10A7) DS 1
User data 1 (0019,10A8) DS 1
User data 2 (0019,10A9) DS 1
User data 3 (0019,10AA) DS 1
User data 4 (0019,10AB) DS 1
User data 5 (0019,10AC) DS 1
User data 6 (0019,10AD) DS 1
User data 7 (0019,10AE) DS 1
User data 8 (0019,10AF) DS 1
User data 9 (0019,10B0) DS 1
User data 10 (0019,10B1) DS 1
User data 11 (0019,10B2) DS 1
User data 12 (0019,10B3) DS 1
User data 13 (0019,10B4) DS 1
User data 14 (0019,10B5) DS 1
User data 15 (0019,10B6) DS 1
User data 16 (0019,10B7) DS 1
User data 17 (0019,10B8) DS 1
User data 18 (0019,10B9) DS 1
User data 19 (0019,10BA) DS 1
User data 20 (0019,10BB) DS 1
User data 21 (0019,10BC) DS 1
User data 22 (0019,10BD) DS 1
Projection angle (0019,10BE) DS 1

Copyright 2009 General Electric Company. All rights reserved

Page 112 of 126
 DOC0506131 rev3

Attribute Name Tag VR VM

Saturation planes (0019,10C0) SS 1
Surface coil intensity ♠ (0019,10C1) SS 1
SAT location R (0019,10C2) SS 1
SAT location L (0019,10C3) SS 1
SAT location A (0019,10C4) SS 1
SAT location P (0019,10C5) SS 1
SAT location H (0019,10C6) SS 1
SAT location F (0019,10C7) SS 1
SAT thickness R/L (0019,10C8) SS 1
SAT thickness A/P (0019,10C9) SS 1
SAT thickness H/F (0019,10CA) SS 1
Phase Contrast flow axis (0019,10CB) SS 1
Velocity encoding (0019,10CC) SS 1
Thickness disclaimer (0019,10CD) SS 1
Prescan type (0019,10CE) SS 1
Prescan status (0019,10CF) SS 1
Raw data type (0019,10D0) SH 1
Projection Algorithm (0019,10D2) SS 1
Projection Algorithm Name (0019,10D3) SH 1
Fractional echo (0019,10D5) SS 1
Prep pulse ♠ (0019,10D6) SS 1
Cardiac phase number (0019,10D7) SS 1
Variable echoflag (0019,10D8) SS 1
Concatenated SAT {# DTI Diffusion Dir., release 9.0 & (0019,10D9) DS 1
below}
User data 23 {# DTI Diffusion Dir., release 9.0 & below} (0019,10DF) DS 1
User data 24 {# DTI Diffusion Dir., release 10.0 & above} (0019,10E0) DS 1
Velocity Encode Scale (0019,10E2) DS 1
Fast phases (0019,10F2) SS 1
Transmit gain (0019,10F9) DS 1

B.1.4. Private Creator Identification (GEMS_RELA_01)

Attribute Name Tag VR VM
GEHC Private Creator ID (0021,0010) LO 1
Series from which Prescribed ♠ (0021,1003) SS 1
Genesis Version – now ♠ (0021,1005) SH 1
Series Record checksum ♠ (0021,1007) UL 1
Genesis version – Now ♠ (0021,1018) SH 1
Acq recon record checksum ♠ (0021,1019) UL 1
Table start location ♠ (0021,1020) DS 1
Series from which prescribed (0021,1035) SS 1
Image from which prescribed (0021,1036) SS 1
Screen Format (0021,1037) SS 1
Locations in acquisition (0021,104F) SS 1
Graphically prescribed (0021,1050) SS 1
Rotation from source x rot (0021,1051) DS 1
Rotation from source y rot (0021,1052) DS 1
Rotation from source z rot (0021,1053) DS 1
Image position ♠ (0021,1054) SH 3

Copyright 2009 General Electric Company. All rights reserved

Page 113 of 126
 DOC0506131 rev3

Attribute Name Tag VR VM

Image orientation ♠ (0021,1055) SH 6
Num 3D slabs (0021,1056) SL 1
Locs per 3D slab (0021,1057) SL 1
Overlaps (0021,1058) SL 1
Image Filtering 0.5/0.2T (0021,1059) SL 1
Diffusion direction (0021,105A) SL 1
Tagging Flip Angle (0021,105B) DS 1
Tagging Orientation (0021,105C) DS 1
Tag Spacing (0021,105D) DS 1
RTIA_timer (0021,105E) DS 1
Fps (0021,105F) DS 1
Auto window/level alpha ♠ (0021,1081) DS 1
Auto window/level beta ♠ (0021,1082) DS 1
Auto window/level window (0021,1083) DS 1
Auto window/level level (0021,1084) DS 1

B.1.5. Private Creator Identification (GEMS_STDY_01)

The entire GEMS_STDY_01 group is no longer supported with the GE MR system release.

Attribute Name Tag VR VM

GEHC Private Creator ID (0023,0010) LO 1
Number of series in Study ♠ (0023,1001) SL 1
Number of unarchived Series ♠ (0023,1002) SL 1
Reference image field ♠ (0023,1010) SS 1
Summary image ♠ (0023,1050) SS 1
Start time(secs) in first axial ♠ (0023,1070) FD 1
No. of updates to header ♠ (0023,1074) SL 1
Indicates study has complete info (DICOM/genesis) ♠ (0023,107D) SS 1
Has MPPS related tags♠ (0023,1080) SQ 1

B.1.6. Private Creator Identification (GEMS_SERS_01)

Attribute Name Tag VR VM
GEHC Private Creator ID (0025,0010) LO 1
Last pulse sequence used ♠ (0025,1006) SS 1
Images in Series (0025,1007) SL 1
Landmark Counter (0025,1010) SL 1
Number of Acquisitions (0025,1011) SS 1
Indicates no. of updates to header ♠ (0025,1014) SL 1
Series Complete Flag ♠ (0025,1017) SL 1
Number of images archived ♠ (0025,1018) SL 1
Last image number used (0025,1019) SL 1
Primary Receiver Suite and Host (0025,101A) SH 1
Protocol Data Block (compressed) (0025,101B) OB 1

Copyright 2009 General Electric Company. All rights reserved

Page 114 of 126
 DOC0506131 rev3

B.1.7. Private Creator Identification (GEMS_IMAG_01)

Attribute Name Tag VR VM
GEHC Private Creator ID (0027,0010) LO 1
Image archive flag ♠ (0027,1006) SL 1
Scout Type ♠ (0027,1010) SS 1
Foreign Image Revision ♠ (0027,1030) SH 1
Imaging Mode (0027,1031) SS 1
Pulse Sequence (0027,1032) SS 1
Imaging Options (0027,1033) SL 1
Plane Type (0027,1035) SS 1
Oblique Plane ♠ (0027,1036) SL 1
RAS letter of image location (0027,1040) SH 1
Image location (0027,1041) FL 1
Center R coord of plane image ♠ (0027,1042) FL 1
Center A coord of plane image ♠ (0027,1043) FL 1
Center S coord of plane image ♠ (0027,1044) FL 1
Normal R coord ♠ (0027,1045) FL 1
Normal A coord ♠ (0027,1046) FL 1
Normal S coord ♠ (0027,1047) FL 1
R Coord of Top Right Corner ♠ (0027,1048) FL 1
A Coord of Top Right Corner ♠ (0027,1049) FL 1
S Coord of Top Right Corner ♠ (0027,104A) FL 1
R Coord of Bottom Right Corner ♠ (0027,104B) FL 1
A Coord of Bottom Right Corner ♠ (0027,104C) FL 1
S Coord of Bottom Right Corner ♠ (0027,104D) FL 1
Image dimension - X (0027,1060) FL 1
Image dimension - Y (0027,1061) FL 1
Number of Excitations (0027,1062) FL 1

B.1.8. Private Creator Identification (GEMS_IMPS_01)

Attribute Name Tag VR VM
GEHC Private Creator ID (0029,0010) LO 1
Lower range of Pixels1 (0029,1015) SL 1
Upper range of Pixels1 (0029,1016) SL 1
Lower range of Pixels2 ♠ (0029,1017) SL 1
Upper range of Pixels2 ♠ (0029,1018) SL 1
Len of tot hdr in bytes ♠ (0029,101A) SL 1
Version of the hdr struct ♠ (0029,1026) SS 1
Advantage comp. Overflow ♠ (0029,1034) SL 1
Advantage comp. Underflow ♠ (0029,1035) SL 1

B.1.9. Private Creator Identification (GEMS_PARM_01)

Attribute Name Tag VR VM
GEHC Private Creator ID (0043,0010) LO 1
Bitmap of prescan options (0043,1001) SS 1
Gradient offset in X (0043,1002) SS 1
Gradient offset in Y (0043,1003) SS 1

Copyright 2009 General Electric Company. All rights reserved

Page 115 of 126
 DOC0506131 rev3

Attribute Name Tag VR VM

Gradient offset in Z (0043,1004) SS 1
Img is original or unoriginal ♠ (0043,1005) SS 1
Number of EPI shots (0043,1006) SS 1
Views per segment (0043,1007) SS 1
Respiratory rate, bpm (0043,1008) SS 1
Respiratory trigger point (0043,1009) SS 1
Type of receiver used (0043,100A) SS 1
DB/dt Peak rate of change of gradient field (0043,100B) DS 1
dB/dt Limits in units of percent (0043,100C) DS 1
PSD estimated limit (0043,100D) DS 1
PSD estimated limit in tesla per second (0043,100E) DS 1
Saravghead ♠ (0043,100F) DS 1
Window value ♠ (0043,1010) US 1
GE image integrity (0043,101C) SS 1
Level value ♠ (0043,101D) SS 1
Unique image iden ♠ (0043,1028) OB 1
Histogram tables (0043,1029) OB 1
User defined data (0043,102A) OB 1
Private Scan Options ♠ (0043,102B) SS 4
Effective echo spacing (0043,102C) SS 1
Filter Mode (String slop field 1 in legacy GE MR (0043,102D) SH 1
images)
String slop field 2 (0043,102E) SH 1
Image Type (real, imaginary, phase, magnitude) (0043,102F) SS 1
Vas collapse flag (0043,1030) SS 1
RA cord of target recon center ♠ (0043,1031) DS 2
Vas flags (0043,1032) SS 1
Neg_scanspacing (0043,1033) FL 1
Offset Frequency (0043,1034) IS 1
User_usage_tag (0043,1035) UL 1
User_fill_map_MSW (0043,1036) UL 1
User_fill_map_LSW (0043,1037) UL 1
User data 25...User data 48 {User48=Effective (0043,1038) FL 24
Resolution for spiral}
Slop_int_6... slop_int_9 (0043,1039) IS 4
6: b_value
7: private imaging options 2
8: ihtagging
9: ihtagspc
Slop_int_10...slop_int_17 (0043,1060) IS 8
10: ihfcineim
11: ihfcinent
12: Reserved
13: oprtarr
14: averages
15: Current Station #
16: Total # of Stations
17: private imaging options 3
Scanner Study Entity UID ♠ (0043,1061) UI 1
Scanner Study ID ♠ (0043,1062) SH 1
Scanner Table Entry (single gradient coil systems (0043,106f) DS 3 or
only) 4

Copyright 2009 General Electric Company. All rights reserved

Page 116 of 126
 DOC0506131 rev3

Attribute Name Tag VR VM

Scanner Table Entry + Gradient Coil Selected
1:table entry, 2: table swing angle, 3: table lateral
offset, 4: gradient coil selected (multiple gradient
systems only)
Paradigm Name 0043,1070 LO 1
Paradigm Description 0043,1071 ST 1
Paradigm UID 0043,1072 UI 1
Experiment Type 0043,1073 US 1
#rest volumes 0043,1074 US 1
#active volumes 0043,1075 US 1
#dummy scans 0043,1076 US 1
Application Name 0043,1077 SH 1
Application Version 0043,1078 SH 1
Slices Per Volume 0043,1079 US 1
Expected Time Points 0043,107A US 1
Regressor Values 0043,107B FL 1..n
Delay after slice group 0043,107C FL 1
Recon mode flag word 0043,107D US 1
PACC specific information 0043,107E LO 1..n
Reserved 0043,107F DS 1..n
Coil ID Data 0043,1080 LO 1..n
GE Coil Name 0043,1081 LO 1
System Configuration Information 0043,1082 LO 1..n
Asset R Factors 0043,1083 DS 1..2
Additional Asset Data 0043,1084 LO 5
Debug Data (text format) 0043,1085 UT 1
Debug Data (binary format) 0043,1086 OB 1
Reserved 0043,1087 UT 1
PURE Acquisition Calibration Series UID 0043,1088 UI 1
Governing Body, dB/dt, and SAR definition 0043,1089 LO 3
Private In-Plane Phase Encoding Direction 0043,108A CS 1
FMRI Binary Data Block 0043,108B OB 1
Voxel Location 0043,108C DS 6
SAT Band Locations 0043,108D DS 7n
Spectro Prescan Values 0043,108E DS 3
Spectro Parameters 0043,108F DS 3
SAR Definition 0043,1090 LO 1..n
SAR value 0043,1091 DS 1..n
Image Error Text 0043,1092 LO 1
Spectro Quantitation Values 0043,1093 DS 1..n
Spectro Ratio Values 0043,1094 DS 1..n
Prescan Reuse String 0043,1095 LO 1
Content Qualification 0043,1096 CS 1
Image Filtering Parameters 0043,1097 LO 8
ASSET Acquisition Calibration Series UID 0043,1098 UI 1
Extended Options 0043,1099 LO 1..n
Rx Stack Identification 0043,109A IS 1
NPW factor 0043,109B DS 1

Copyright 2009 General Electric Company. All rights reserved

Page 117 of 126
 DOC0506131 rev3

Attribute Name Tag VR VM

Research Tag 1 0043,109C OB 1
Research Tag 2 0043,109D OB 1
Research Tag 3 0043,109E OB 1
Research Tag 4 0043,109F OB 1

Copyright 2009 General Electric Company. All rights reserved

Page 118 of 126
 DOC0506131 rev3

B.1.10. Private Creator Identification (BrainWave: 1.2.840.113819.3)

Attribute Name Tag VR VM

Private Creator ID 2001,0010 LO 1
DICOM Implementation UID 2001,1010 UI 1
DICOM Implementation Version 2001,1011 SH 1
Within-DICOM-Implementation SOP Instance UID 2001,1012 UI 1
Application Name 2001,1013 SH 1
Application Version 2001,1014 SH 1
Compatibility Version 2001,1015 SH 1
Referenced Series UID 2001,1021 UI 1-n
Number of Objects Averaged 2001,1031 US 1
Number of Expected Time Points 2001,1041 US 1
Number of Slices Per Volume 2001,1051 US 1
BW Image Type 2001,1060 US 1
Experiment Type 2001,1061 US 1
Paradigm UID 2001,1071 UI 1
Paradigm Name 2001,1072 LO 1
Paradigm Description 2001,1073 ST 1
Contrast 2001,1080 OB 1
Regressor Values 2001,1081 FL 1-n
Number of Degrees of Freedom 2001,1086 US 1
Z Threshold 2001,108A FL 1
p Threshold 2001,108B FL 1
Motion Parameters 2001,10A0 FL 1-n
Registration Parameters 2001,10A1 FL 1-n
Subject Data 2001,10A2 FL 1-n
DTI Parameters 2001,10B0 OB 1
Paradigm Info 2001,10C0 OB 1

B.1.11. Private Creator Identification (GEMS_MR_RAW_01)

Attribute Name Tag VR VM

GEHC Private Creator ID 7001,0010 LO 1
rdb_hdr_rec 7001,1001 OB 1
rdb_hdr_per_pass_tab 7001,1002 OB 1
rdb_hdr_unlock_raw 7001,1003 OB 1
rdb_hdr_data_acq_tab 7001,1004 OB 1
rdb_hdr_nex_tab 7001,1005 OB 1
rdb_hdr_nex_abort_tab 7001,1006 OB 1
rdb_hdr_tool 7001,1007 OB 1
rdb_raw_data 7001,1008 OB 1
SSP save 7001,1009 OB 1
UDA save 7001,100A OB 1
rdb_chemsat_data 7001,100B OB 1

Copyright 2009 General Electric Company. All rights reserved

Page 119 of 126
 DOC0506131 rev3

Attribute Name Tag VR VM

B.1.12. Private Creator Identification (GEMS_FUNCTOOL_01)

Attribute Name Tag VR VM
GEHC Private Creator ID 0051,0010 LO 1
Functional Proc Group Name 0051,1001 LO 1
Functional Processing Name 0051,1002 LO 1
Bias of Functional Image 0051,1003 SL 1
Scale of Functional Image 0051,1004 FL 1
Length of Parameters String 0051,1005 SL 1
Store Parameters string, delimited by character 0051,1006 LT 1
ESC=0x1B (27)
Functional Image Version 0051,1007 LO 1
Store Color Ramp 0051,1008 SL 1
Store Width of Functional Image 0051,1009 SL 1
Store level of Functional Image 0051,100A SL 1
Store B-Value with Functional Image 0051,100B FL 1
Analysis Package 0051,100C LO 1
♠ indicates: No longer generated

Copyright 2009 General Electric Company. All rights reserved

Page 120 of 126
 DOC0506131 rev3

Appendix C DICOMDIR Directory Information

C.1 DICOMDIR Directory Information

Enclosed here is a listing of only the optional (conditional) modules and optional attributes used by this
implementation in the DICOMDIR definition. All standard attributes as defined in Part 3 Addendum (Basic
Directory Information Object) are supported by this implementation but not listed here.

C.1.1 Basic Directory IOD Definition

Module Reference Usage Notes
Directory Information B.X.3.2.1 (DICOM PS3.10) U Sent

C.1.2 Directory Information Module

C.1.2.1 CD-R/DVD-R Directory Information Module

Attribute Name Tag Type Notes
Offset of the First Directory Record (0004,1200) 1 Set by application
of the Root Directory Entity
Offset of the Last Directory Record of (0004,1202) 1 Set by application
the Root Directory Entity
File-set Consistency Flag (0004,1212) 1 0000H: no known inconsistencies.
Directory Record Sequence (0004,1220) 2 Supported.
>Offset of the Next Directory Record (0004,1400) 1C Set by application
>Record In-use Flag (0004,1410) 1C FFFFH: record is in use
>Offset of Referenced Lower-Level (0004,1420) 1C Set by application
Directory Entity
>Directory Record Type (0004,1430) 1C PATIENT, STUDY, SERIES and
IMAGE

>Private Record UID (0004,1432) 1C Not supported

>Referenced File ID (0004,1500) 1C Generated only for Image Directory

Record, starting with A/A/A/A/Z01.
>MRDR Directory Record Offset (0004,1504) 1C Not generated
>Referenced SOP Class UID in File (0004,1510) 1C Generated for Image Directory
Record.
>Referenced SOP Instance UID in (0004,1511) 1C Generated for Image Directory Record.
File Set to SOP Instance UID (0008,0018)
during save to media.
>Referenced Transfer Syntax UID in (0004,1512) 1C Not supported
File

Copyright 2009 General Electric Company. All rights reserved

Page 121 of 126
 DOC0506131 rev3

C.1.3 CD-R/DVD-R Directory Record Selection Keys

The STD-GEN-CD and STD-GEN-DVD Application Profiles will have only the Patient, Study, Series, and
Image directory record types. Given below are the attributes supported under each of these directories

C.1.3.1 CD-R/DVD-R Patient Keys

Key Tag Type Notes
Specific Character Set (0008,0005) 1C ISO_IR 100
.
Patient's Name (0010,0010) 2 If present in composite object
instances it will be set to same value,
other wise set to NULL
.
Patient ID (0010,0020) 1 If present in composite object
instances it will be set to same value,
other wise an error is returned
.
Patient Birth Date (0010,0030) 1C If present in composite object
instances it will be set to same value,
other wise not present
Patient Birth Time (0010,0032) 3 If present in composite object
instances it will be set to same value,
other wise set to NULL
Patient Sex (0010,0040) 1C If present in composite object
instances it will be set to same value,
other wise not present

C.1.3.2 CD-R/DVD-R Study Keys

Key Tag Type Notes
Specific Character Set (0008,0005) 1C ISO_IR 100
.
Study Date (0008,0020) 1 If present in composite object
instances it will be set to same value,
other wise an error is returned

Study Time (0008,0030) 1 If present in composite object

instances it will be set to same value,
other wise an error is returned

Study Description (0008,1030) 2 If present in composite object

instances it will be set to same value,
other wise set to NULL

Study Instance UID (0020,000D) 1C This is set to value that is present in

the composite object instances,
otherwise composite object instances
are not Archived.

Study ID (0020,0010) 1 If present in composite object

instances it will be set to same value,
other wise an error is returned

Copyright 2009 General Electric Company. All rights reserved

Page 122 of 126
 DOC0506131 rev3

Accession Number (0008,0050) 2 If present in composite object

instances it will be set to same value,
other wise set to NULL

C.1.3.3 CD-R/DVD-R Series Keys

Key Tag Type Notes
Specific Character Set (0008,0005) 1C ISO_IR 100

Modality (0008,0060) 1 If present in composite object instance

it will be set to same value, other wise
an error is returned and the object not
put on media
Series Instance UID (0020,000E) 1 This is set to value that is present in
the composite object instance,
otherwise check for presence of
Referenced SOP Instance UID in File
(0004,1511), if both not present,
instance is not put on media.
Series Number (0020,0011) 1 If present in composite object instance
it will be set to same value, other wise
an error is returned and the object not
put on media.
Icon Image Sequence (0088,0200) 3 Not supported
Manufacturer (0008,0070) 3 Not included
Series Description (0008,103E) 3 Not included
Manufacturer’s Model Name (0008,1090) 3 Not included
Image Type (0008,0008) 2 If present in composite object instances
it will be set to same value, other wise
set to NULL
Series Date (0008,0021) 3 Not included
Performing Physician’s Name (0008,1050) 1C If present in composite object instances
it will be set to same value, other wise
not sent
Institution Name (0008,0080) 1C If present in composite object instances
it will be set to same value, other wise
not sent
Institution Address (0008,0081) 1C If present in composite object instances
it will be set to same value, other wise
not sent
Series Type (0054,1000) 3 Not included.

C.1.3.4 CD-R/DVD-R Image Keys

Copyright 2009 General Electric Company. All rights reserved

Page 123 of 126
 DOC0506131 rev3

Key Tag Type Notes

Specific Character Set (0008,0005) 1C ISO_IR 100
.
Image Type (0008,0008) 1C Not supported
Acquisition Datetime (0008,002A) 1C Not supported
Referenced Image Sequence (0008,1140) 1C Not supported
Instance Number (0020,0013) 1 If present in composite object
instances it will be set to same
value, other wise set to NULL
Icon Image Sequence (0088,0200) 3 Not supported
SOP Class UID (0008,0016) 3 Not included
Slice Thickness (0018,0050) 3 Not included

Repetition Time (0018,0080) 3 Not included

Echo Time (0018,0081) 3 Not included
Inversion Time (0018,0082) 3 Not included
Number of Averages (0018,0083) 3 Not included
Spacing Between Slices (0018,0088) 3 Not included
Data Collection Diameter (0018,0090) 3 Not included
Contrast Bolus Route (0018,1040) 3 Not included
Trigger Time (0018,1060) 3 Not included
Reconstruction Diameter (0018,1100) 3 Not included
Gantry Detector Tilt (0018,1120) 3 Not included
Flip Angle (0018,1314) 3 Not included
Acquisition Time Synchronized (0018,1800)
Synchronization Frame of Reference UID (0020,0200) 1C Not supported
Slice Location (0020,1041) 3 Not included
Number of Frames (0028,0008) 1C Not supported
Rows (0028,0010) 1 If present in composite object
instances it will be set to same
value, other wise an error is
returned
Columns (0028,0011) 1 If present in composite object
instances it will be set to same
value, other wise an error is
returned
Echo Numbers (0008,0086) 3 Not included
Samples Per Pixel (0028,0002) 3 Not included
Bits Allocated (0028,0100) 3 Not included
Bits Stored (0028,0101) 3 Not included
Lossy Image Compression Ratio (0028,2112 1C Not supported
Frame of Reference UID (0020,0052) 1C If present in composite object
instances it will be set to same
value, other wise not sent
Sequence Variant (0018,0021) 3 Not included
Convolution Kernel (0018,1210) 3 Not included
Image Position Patient (0020,0032) 1C If present in composite object
instances it will be set to same
value, other wise not sent
Image Orientation Patient (0020,0037) 1C If present in composite object
instances it will be set to same
value, other wise not sent

Copyright 2009 General Electric Company. All rights reserved

Page 124 of 126
 DOC0506131 rev3

Pixel Spacing (0028,0030) 1C If present in composite object

instances it will be set to same
value, other wise not sent
Calibration Image (0050,0004) 1C Not supported

GE Healthcare, LLC
GE Healthcare, LLC: Telex 3797371
P.O. Box 414, Milwaukee, Wisconsin 53201-0414 USA
(Asia, Pacific, Latin America, North America)

GE Healthcare – Europe: Telex 261794

Shortlands, Hammersmith, London W6 8Bx U.K.

http://www.gehealthcare.com

Copyright 2009 General Electric Company. All rights reserved

Page 125 of 126
 DOC0506131 rev3

Copyright 2009 General Electric Company. All rights reserved

Page 126 of 126