direction # 2162114-100 rev. 0

GE Medical Systems

TechnicalPublications

Direction 2162114-100Revision 0

HiSpeed Advantage CT/iCONFORMANCE STATEMENT

for DICOM v3.0 (ID/Net v3.0)

do not duplicate

Copyright 1997 by General Electric Company

GE Medical Systems HiSpeed Advantage CT/i CONFORMANCE STATEMENTREV 0 Direction 2162114-100

2

Notes

Rev. 0

GE Medical Systems

Direction 2162114–100

HiSpeed Advantage CT/i CONFORMANCE STATEMENT

3

THIS SERVICE MANUAL ISAVAILABLE IN ENGLISH ONLY.WARNING

� IF A CUSTOMER’S SERVICE PROVIDER REQUIRES ALANGUAGE OTHER THAN ENGLISH, IT IS THE CUSTOMER’SRESPONSIBILITY TO PROVIDE TRANSLATION SERVICES.

� DO NOT ATTEMPT TO SERVICE THE EQUIPMENT UNLESS THISSERVICE MANUAL HAS BEEN CONSULTED AND IS UNDERSTOOD.

� FAILURE TO HEED THIS WARNING MAY RESULT IN INJURY TOTHE SERVICE PROVIDER, OPERATOR OR PATIENT FROMELECTRIC SHOCK, MECHANICAL OR OTHER HAZARDS.

CE MANUEL DEMAINTENANCE N’ESTDISPONIBLE QU’EN ANGLAIS.

AVERTISSEMENT

� SI LE TECHNICIEN DU CLIENT A BESOIN DE CE MANUELDANS UNE AUTRE LANGUE QUE L’ANGLAIS, C’EST AU CLIENTQU’IL INCOMBE DE LE FAIRE TRADUIRE.

� NE PAS TENTER D’INTERVENTION SUR LES ÉQUIPEMENTSTANT QUE LE MANUEL SERVICE N’A PAS ÉTÉ CONSULTÉ ETCOMPRIS.

� LE NON-RESPECT DE CET AVERTISSEMENT PEUT ENTRAÎNERCHEZ LE TECHNICIEN, L’OPÉRATEUR OU LE PATIENT DESBLESSURES DUES À DES DANGERS ÉLECTRIQUES, MÉCANIQUESOU AUTRES.

DIESES KUNDENDIENST–HANDBUCHEXISTIERT NUR IN ENGLISCHERSPRACHE.

WARNUNG

� FALLS EIN FREMDER KUNDENDIENST EINE ANDERESPRACHE BENÖTIGT, IST ES AUFGABE DES KUNDEN FÜR EINEENTSPRECHENDE ÜBERSETZUNG ZU SORGEN.

� VERSUCHEN SIE NICHT, DAS GERÄT ZU REPARIEREN, BEVORDIESES KUNDENDIENST–HANDBUCH NICHT ZU RATE GEZOGENUND VERSTANDEN WURDE.

� WIRD DIESE WARNUNG NICHT BEACHTET, SO KANN ES ZUVERLETZUNGEN DES KUNDENDIENSTTECHNIKERS, DESBEDIENERS ODER DES PATIENTEN DURCH ELEKTRISCHESCHLÄGE, MECHANISCHE ODER SONSTIGE GEFAHRENKOMMEN.

ESTE MANUAL DE SERVICIOSÓLO EXISTE EN INGLÉS.AVISO

� SI ALGÚN PROVEEDOR DE SERVICIOS AJENO A GEMSSOLICITA UN IDIOMA QUE NO SEA EL INGLÉS, ESRESPONSABILIDAD DEL CLIENTE OFRECER UN SERVICIO DETRADUCCIÓN.

� NO SE DEBERÁ DAR SERVICIO TÉCNICO AL EQUIPO, SINHABER CONSULTADO Y COMPRENDIDO ESTE MANUAL DESERVICIO.

� LA NO OBSERVANCIA DEL PRESENTE AVISO PUEDE DARLUGAR A QUE EL PROVEEDOR DE SERVICIOS, EL OPERADOR OEL PACIENTE SUFRAN LESIONES PROVOCADAS POR CAUSASELÉCTRICAS, MECÁNICAS O DE OTRA NATURALEZA.

ESTE MANUAL DE ASSISTÊNCIATÉCNICA SÓ SE ENCONTRADISPONÍVEL EM INGLÊS.

ATENÇÃO

� SE QUALQUER OUTRO SERVIÇO DE ASSISTÊNCIA TÉCNICA,QUE NÃO A GEMS, SOLICITAR ESTES MANUAIS NOUTRO IDIOMA,É DA RESPONSABILIDADE DO CLIENTE FORNECER OS SERVIÇOSDE TRADUÇÃO.

� NÃO TENTE REPARAR O EQUIPAMENTO SEM TERCONSULTADO E COMPREENDIDO ESTE MANUAL DEASSISTÊNCIA TÉCNICA.

� O NÃO CUMPRIMENTO DESTE AVISO PODE POR EM PERIGO ASEGURANÇA DO TÉCNICO, OPERADOR OU PACIENTE DEVIDO A‘CHOQUES ELÉTRICOS, MECÂNICOS OU OUTROS.

IL PRESENTE MANUALE DIMANUTENZIONE È DISPONIBILESOLTANTO IN INGLESE.

AVVERTENZA

� SE UN ADDETTO ALLA MANUTENZIONE ESTERNO ALLAGEMS RICHIEDE IL MANUALE IN UNA LINGUA DIVERSA, ILCLIENTE È TENUTO A PROVVEDERE DIRETTAMENTE ALLATRADUZIONE.

� SI PROCEDA ALLA MANUTENZIONE DELL’APPARECCHIATURASOLO DOPO AVER CONSULTATO IL PRESENTE MANUALE EDAVERNE COMPRESO IL CONTENUTO.

� NON TENERE CONTO DELLA PRESENTE AVVERTENZAPOTREBBE FAR COMPIERE OPERAZIONI DA CUI DERIVINOLESIONI ALL’ADDETTO ALLA MANUTENZIONE,ALL’UTILIZZATORE ED AL PAZIENTE PER FOLGORAZIONEELETTRICA, PER URTI MECCANICI OD ALTRI RISCHI.

Rev. 0

GE Medical Systems

Direction 2162114–100

HiSpeed Advantage CT/i CONFORMANCE STATEMENT

4

IMPORTANT! . . . X-RAY PROTECTION

X-ray equipment if not properly used may causeinjury. Accordingly, the instructions herein con-tained should be thoroughly read and understoodby everyone who will use the equipment before youattempt to place this equipment in operation. TheGeneral Electric Company, Medical Systems Group,will be glad to assist and cooperate in placing thisequipment in use.

Although this apparatus incorporates a high degree ofprotection against x-radiation other than the usefulbeam, no practical design of equipment can providecomplete protection. Nor can any practical designcompel the operator to take adequate precautions toprevent the possibility of any persons carelesslyexposing themselves or others to radiation.

It is important that everyone having anything to do withx-radiation be properly trained and fully acquainted withthe recommendations of the National Council onRadiation Protection and Measurements as published inNCRP Reports available from NCRP Publications, 7910Woodmont Avenue, Room 1016, Bethesda, Maryland20814, and of the International Commission onRadiation Protection, and take adequate steps to protectagainst injury.

The equipment is sold with the understanding that theGeneral Electric Company, Medical Systems Group, itsagents, and representatives have no responsibility forinjury or damage which may result from improper use ofthe equipment.

Various protective material and devices are available. Itis urged that such materials or devices be used.

CERTIFIED ELECTRICAL CONTRACTOR STATEMENT

All electrical installations that are preliminary to positioningof the equipment at the site prepared for the equipmentshall be performed by licensed electrical contractors. Inaddition, electrical feeds into the Power Distribution Unitshall be performed by licensed electrical contractors. Otherconnections between pieces of electrical equipment,calibrations, and testing shall be performed by qualified GEMedical personnel. The products involved (and theaccompanying electrical installations) are highly sophisti-cated, and special engineering competence is required.

In performing all electrical work on these products, GE willuse its own specially trained field engineers. All of GE’selectrical work on these products will comply with therequirements of the applicable electrical codes.

The purchaser of GE equipment shall only utilize qualifiedpersonnel (i.e., GE’s field engineers, personnel ofthird-party service companies with equivalent training, orlicensed electricians) to perform electrical servicing on theequipment.

DAMAGE IN TRANSPORTATION

All packages should be closely examined at time ofdelivery. If damage is apparent, have notation “damagein shipment ” written on all copies of the freight orexpress bill before delivery is accepted or “signed for” bya General Electric representative or a hospital receivingagent. Whether noted or concealed, damage MUST bereported to the carrier immediately upon discovery, or inany event, within 14 days after receipt, and the contentsand containers held for inspection by the carrier. Atransportation company will not pay a claim for damage if

an inspection is not requested within this 14 day period.

Call Traffic and Transportation, Milwaukee, WI (414)827–3449 / 8*285–3449 immediately after damage isfound. At this time be ready to supply name of carrier,delivery date, consignee name, freight or express billnumber, item damaged and extent of damage.

Complete instructions regarding claim procedure arefound in Section “S” of the Policy & Procedure Bulletins.

OMISSIONS & ERRORS

GE personnel, please use the GEMS CQA Process toreport all omissions, errors, and defects in this

documentation. Customers, please contact your GESales or Service represenatives.


5

TABLE OF CONTENTS

1 SECTION 1 - INTRODUCTION 9

1.0 Overview 9

1.1 Overall Conformance Statement Documentation Structure 10

1.2 Intended Audience 12

1.3 Scope and Field of Application 12

1.4 Important Remarks 13

1.5 References 14

1.6 Definitions 14

1.7 Symbols and Abbreviations 14

2 SECTION 2 - CONFORMANCE STATEMENT 15

2.0 INTRODUCTION 15

2.1 IMPLEMENTATION MODEL 152.1.1 Application Data Flow Diagram 162.1.2 Functional Definition of AE’s 172.1.3 Sequencing of Real-World Activities 18

2.2 AE SPECIFICATIONS 182.2.1 DICOM Server AE Specification 18

2.2.1.1 Association Establishment Policy 182.2.1.1.1 General 182.2.1.1.2 Number of Associations 192.2.1.1.3 Asynchronous Nature 192.2.1.1.4 Implementation Identifying Information 19

2.2.1.2 Association Initiation by Real-World Activity 192.2.1.2.1 Push Image(s) to Remote AE 19

2.2.1.2.1.1 Associated Real-World Activity 202.2.1.2.1.2 Proposed Presentation Contexts 20

2.2.1.2.1.2.1 SOP Specific Conformance Statement for Image Storage SOP Classes 212.2.1.2.2 Query Remote AE 21


2.2.1.2.2.2.1 SOP Specific Conformance Statement for C-FIND SCU 232.2.1.2.3 Get Image(s) from Remote AE 24


2.2.1.2.3.2.1 SOP Specific Conformance Statement for C-MOVE SCU 252.2.1.3 Association Acceptance Policy 25

2.2.1.3.1 Receive Image(s) 25


6

2.2.1.3.1.1 Associated Real-World Activity 262.2.1.3.1.2 Presentation Context Table 26

2.2.1.3.1.2.1 SOP Specific Conformance to Storage SOP Classes 262.2.1.3.2 Verification Request from Remote AE 27


2.2.1.3.2.2.1 SOP Specific Conformance to Verification SOP Class 282.2.1.3.3 Query Request from Remote AE 28


2.2.1.3.3.2.1 SOP Specific Conformance to C-FIND SCP 292.2.1.3.4 Retrieve Request From Remote AE 31


2.2.1.3.4.2.1 SOP Specific Conformance to C-MOVE SCP 312.2.1.3.4.3 Presentation Context Acceptance Criteria 322.2.1.3.4.4 Transfer Syntax Selection Policy 32

2.3 SECTION 3 - COMMUNICATION PROFILES 332.3.1 Supported Communication Stacks (parts 8,9) 332.3.2 TCP/IP Stack 33

2.3.2.1 Physical Media Support 332.3.3 Point-to-Point Stack 33

2.4 SECTION 4 - EXTENSIONS / SPECIALIZATIONS / PRIVATIZATIONS 342.4.1 Specialized Information Object Definition 342.4.2 Private SOP’s 352.4.3 Private Data Elements 36

2.5 SECTION 5 - CONFIGURATION 362.5.1 AE Title/Presentation Address Mapping 362.5.2 Configurable Parameters 36

2.6 SECTION 6 - SUPPORT OF EXTENDED CHARACTER SETS 36

3 MOD ARCHIVE CONFORMANCE 36

3.0 Introduction 36

3.1 Implementation Model : MOD Archive Server 363.1.1 Application Data Flow Diagram 373.1.2 Functional Definitions of AE's 373.1.3 Sequencing of Real World Activities 383.1.4 File Meta Information for Implementation Class and Version 38

3.2 AE Specifications 383.2.1 MOD Archive Specification 38

3.2.1.1 File Meta Information for the Application Entity 383.2.1.2 Real World Activities 38

3.2.1.2.1 Real World Activity: Create MOD Request 383.2.1.2.1.1 Application Profiles for the RWA: Create MOD 39

3.2.1.2.2 Real World Activity: Display Directory 393.2.1.2.2.1 Application Profiles for the RWA: MOD Directory Listing 39

3.2.1.2.3 Real World Activity: Copy to Local Storage 39


7

3.2.1.2.3.1 Application Profiles for the RWA: Copy to Local Storage 393.2.1.2.4 Real World Activity: Update MOD 39

3.2.1.2.4.1 Application Profiles for the RWA: Update MOD Request 40

3.3 Augmented and Private Application Profiles 403.3.1 Private Application Profiles 40

3.3.1.1 Class and Profile Identification 403.3.1.2 Clinical Contexts 40

3.3.1.2.1 Roles and Service Class Options 403.3.1.2.1.1 File Set Creator 413.3.1.2.1.2 File Set Reader 413.3.1.2.1.3 File Set Updater 41

3.3.1.3 PRI-CTMR-MOD12 Class Profile 413.3.1.3.1 SOP Classes and Transfer Syntaxes 413.3.1.3.2 Physical Media and Media Formats 423.3.1.3.3 Logical Format 423.3.1.3.4 Directory Information in DICOMDIR 43

3.3.1.3.4.1 Additional Keys 433.3.1.3.5 Other Parameters 43

3.3.1.3.5.1 Image Attribute Values 433.3.1.3.5.1.1 Attribute Value Precedence 44

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

3.4.1.1 SOP Specific Conformance Statement for CT SOP Class 443.4.1.2 SOP Specific Conformance Statement for MR SOP Class 44

3.4.2 Private Transfer Syntax Specification 44

3.5 Configuration 44

3.6 Support of Extended Character Sets 45

Appendix A Optional/Conditional Modules/Attributes 46

Appendix B Private Data Elements 50

Appendix C DICOMDIR Directory Information 59


8

Notes


9

1 SECTION 1 - INTRODUCTION

1.0 Overview

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

Section 2, Conformance Statement, is the DICOM v3.0 ConformanceStatement related to this product Conformance Statements define the subset ofoptions selected from those offered by the DICOM v3.0 standard.

Section 3, MOD Archive Conformance, is the DICOM v3.0 ConformanceStatement related to Media Storage Application Profile.


10

1.1 Overall Conformance Statement Documentation Structure

The documentation structure of the ID/Net v3.0 Conformance Statements andtheir relationship with the DICOM v3.0 Conformance Statements is shown inIllustration 1-1.

Illustration 1-1DOCUMENTATION STRUCTURE

ID/Net v3.0

APPLICATION ENTITY SPECIFICATION(SERVICES CLASSES, INFORMATION OBJECTS, MESSAGE EXCHANGES, ETC.)

Product Implementation:

DICOM STANDARD

Specification Standard:

DICOMv3.0

PART 8

DICOMv3.0

PART 7

DICOMv3.0

PART 6DICOM

v3.0PART 4

DICOMv3.0

PART 3

DICOMv3.0

PART 2

Introductionto the

IntegratedDICOM/Network

v3.0(ID/Net v3.0)Conformance

StatementDirection:2118780

MR AdvantageConformance

Statementfor DICOM v3.0CT Advantage

ConformanceStatement

for DICOM v3.0HiSpeedAdvantage CT/iConformance

Statementfor DICOM v3.0

(ID/Net v3.0)Direction:

2162114-100

DICOMv3.0

PART 5

DICOMv3.0

PART 10

DICOMv3.0

PART 1


11

The Documentation structure given in Illustration 1-1 shows the overall documentation structure for all ofthe GE ID/Net v3.0 Conformance Statements.

ID/Net v2.0 documentation is also openly available, but the two documentationstructures are independent of each other. Refer to Direction 46-269546G2.

This document specifies the DICOM v3.0 implementation supported by theHiSpeed Advantage CT/i. It is entitled:

HiSpeed Advantage CT/iConformance Statement for DICOM v3.0 (ID/Net v3.0)Direction 2162114-100

This Conformance Statement documents the DICOM v3.0 ConformanceStatement and Technical Specification required to interoperate with the GEID/Net v3.0 network interface. Introductory information, which is applicable to allGE ID/Net v3.0 Conformance Statements, is described in the document:

Introduction to the Integrated DICOM/Network v3.0 (ID/Net v3.0)Conformance StatementsDirection 2118780

This introduction familiarizes the reader with DICOM terminology and generalconcepts. It should be read prior to reading individual products’ ID/Net v3.0Conformance Statements.

The ID/Net v3.0 Conformance Statement, contained in this document, alsospecifies the Lower Layer communications which it supports (e.g. TCP/IP).However, the Technical Specifications are defined in the DICOM v3.0 Part 8standard.

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

For the convenience of developers, there is a “collector” Direction available. Byordering the collector, the Introduction described above and all of the currentlypublished ID/Net v3.0 Product Conformance Statements will be received. Thecollector Direction is:

ID/Net v3.0 Conformance StatementsDirection 2117016

For more information regarding DICOM v3.0, copies of the Standard may beobtained by written request by contacting:

ACR-NEMA RepresentativeNEMA1300 N. 17th Street, Suite 1847Rosslyn, VA 22209 USA


12

1.2 Intended Audience

The reader of this document is concerned with software design and/or systemintegration issues. It is assumed that the reader of this document is familiar withthe DICOM v3.0 standards and with the terminology and concepts which areused in those standards.

If readers are unfamiliar with DICOM v3.0 terminology they should first refer tothe document listed below, then read the DICOM v3.0 Standard itself, prior toreading this Conformance Statement document.

Introduction to the Integrated DICOM/Network v3.0 (ID/Net v3.0)Conformance StatementsDirection 2118780

1.3 Scope and Field of Application

It is the intent of this document, in conjunction with the Introduction to theIntegrated DICOM/Network v3.0 (ID/Net v3.0) Conformance StatementsDirection 2118780, to provide an unambiguous specification for GE ID/Net v3.0implementations. This specification, called a Conformance Statement, includes aDICOM v3.0 Conformance Statement and is necessary to insure properprocessing and interpretation of GE medical image data exchanged usingDICOM v3.0. The GE ID/Net v3.0 Conformance Statements are available to thepublic.

The reader of this conformance statement should be aware that different GEdevices are capable of using different Information Object Definitions. Forexample, 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 alldata elements used by the GE ID/Net v3.0 implementation. If the userencounters unspecified private data elements while parsing a GE Data Set, theuser is well advised to ignore those data elements (per the DICOM v3.0standard). Unspecified private data element information is subject to changewithout 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 byGE devices.


13

1.4 Important Remarks

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

• Integration - The integration of any device into an overall system ofinterconnected devices goes beyond the scope of standards (DICOM v3.0),and of this introduction and associated Conformance Statements wheninteroperability with non-GE equipment is desired. The responsibility toanalyze the applications requirements and to design a solution thatintegrates GE imaging equipment with non-GE systems is the user’sresponsibility and should not be underestimated. The user is stronglyadvised 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 declaredoperational, should not be overlooked. Therefore, the user should ensurethat any non-GE provider accepts full responsibility for all validation requiredfor their connection with GE devices. This includes the accuracy of the imagedata once it has crossed the interface between the GE imaging equipmentand the non-GE device and the stability of the image data for the intendedapplications.Such a validation is required before any clinical use (diagnosis and/ortreatment) is performed. It applies when images acquired on GE imagingequipment are processed/displayed on a non-GE device, as well as whenimages acquired on non-GE equipment is processed/displayed on a GEconsole or workstation.

• Future Evolution - GE understands that the DICOM Standard will evolve

to meet the user’s growing requirements. GE is actively involved in thedevelopment of the DICOM v3.0 Standard. DICOM v3.0 will incorporate newfeatures and technologies and GE may follow the evolution of the Standard.ID/Net v3.0 is based on DICOM v3.0 as specified in each ID/Net DICOMConformance Statement. Evolution of the Standard may require changes todevices which have implemented DICOM v3.0. In addition, GE reserves theright to discontinue or make changes to the support of communicationsfeatures (on its products) reflected on by these ID/Net DICOM ConformanceStatements. The user should ensure that any non-GE provider, whichconnects with GE devices, also plans future evolution of the DICOMstandard. Failure to do so will likely result in the loss of function and/orconnectivity as the DICOM Standard changes and GE products areenhanced to support these changes.

To be kept informed of the evolution of the implementation described inthis document, the user should register on the GE Internet server, accessiblevia anonymous ftp, by entering his/her e-mail address (GE Internet ServerAddress: ftp.med.ge.com : 192.88.230.11).


14

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

1.5 References

A list of references which is applicable to all ID/Net v3.0 ConformanceStatements is included in the Introduction to the Integrated DICOM/Networkv3.0 (ID/Net v3.0) Conformance Statements Direction 2118780.

1.6 Definitions

A set of definitions applicable to all ID/Net v3.0 Conformance Statements isincluded in the Introduction to the Integrated DICOM/Network v3.0 (ID/Netv3.0) Conformance Statements Direction 2118780.

1.7 Symbols and Abbreviations

A list of symbols and abbreviations which is applicable to all ID/Net v3.0Conformance Statements is included in the Introduction to the IntegratedDICOM/Network v3.0 (ID/Net v3.0) Conformance Statements Direction2118780.


15

2 SECTION 2 - CONFORMANCE STATEMENT

2.0 INTRODUCTION

This Conformance Statement (CS) specifies the HiSpeed Advantage CT/icompliance to DICOM v3.0. It details the DICOM Service Classes and roleswhich are supported by this product in it’s version 3.6.

The HiSpeed Advantage CT/i product uses DICOM services to import images forpossible further analysis and/or processing. It also uses DICOM services toexport 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 tothat part of the standard while reading this section.

2.1 IMPLEMENTATION MODEL

All DICOM functionality on the HiSpeed Advantage CT/i product is handled bythe DICOM Server Application Entity (AE). The DICOM Server AE iscommanded to perform DICOM services through the buttons and menuselections on the main user interface panel. The DICOM Server AE is alsolistening to a pre-defined port for incoming connections.


16

2.1.1 Application Data Flow Diagram

ILLUSTRATION 2-0IMPLEMENTATION MODEL DATA FLOW DIAGRAM

There are three Real-World Activities that will cause the DICOM ServerApplication Entity (DICOM Server AE) to initiate a DICOM association to aremote DICOM Application Entity.

The Choose “Push” Option Real-World activity consists of an operator selectingone or more study, series or image in the local database manager and choosingeither “Push Examination”, “Push Series” or “Push Image from the “Network”pulldown menu on the local database manager to send the image(s) to aselected destination.

Real-World Activity, Query Remote, causes the DICOM Server AE to initiate anassociation to the Remote DICOM AE and request the list of all studies. Oncethe DICOM Server AE receives the list of studies, it will select the first study (asdetermined through the local database manager list sort criterion) and requestthe list of series for that study. After receiving the list of series the DICOM ServerAE will ask for the list of images for the first series in the list. The operator canthen select any study in the study list to retrieve the list of series and images.

Real-World Activity, Choose “Pull” Option, will be available once the QueryRemote activity is performed. The operator can now select one or more study(series or image) and ask the DICOM Server AE to retrieve the selectedimage(s) from the Remote DICOM AE by choosing either “Get Examination”,“Get Series”, or “Get Images”.

There is no Real-World activity required for the DICOM Server AE to respond toan incoming DICOM store, query or retrieve. The DICOM Server AE is always

DICOM SERVERAE

DICOM StandardInterface

ImageRemotely

Stored

ChoosePush

Option

Remote systemrequests image

storage

ImageInstallation

ChooseQuery

RemoteOption

ChooseGet Option

QueryRetrieve

SCP

RemoteQuery

RetrieveSCP

RemoteQuery

Request

RemotePull

RequestVerify

Request


17

prepared to respond to a DICOM Store, Query, or Retrieve by any remoteDICOM AE.

The DICOM Server AE will perform the Real-World activity Image Installationafter the remote AE sends an image to the HiSpeed Advantage CT/i product.

Once a Query request is received, the DICOM Server AE will search the localdatabase for all entries that match the keys requested by the Remote DICOM AEand send back the list of matches. The DICOM Server AE will also respond to anincoming retrieval request from a Remote AE by sending the image(s) to theDestination AE.

2.1.2 Functional Definition of AE’s

DICOM Server Application Entity initiates the following operations:

• Initiate an association to a Remote AE to send image(s). If the Remote AEaccepts the presentation context applicable to the image(s) being sent, theDICOM Server AE will send the image(s) by invoking C-STORE-RQoperation for each image on the same association.

• Initiate an association with a Remote AE to query for images on the remotehost. A Study-Root Study-Level C-FIND-RQ request will be sent to theRemote AE once an association has been established. After all responsesare received, DICOM Server AE will issue a Series-Level C-FIND-RQrequest to get the series for a study in the list. An Image-Level C-FIND-RQwill be issued for the first series in the series list.

• Send a C-MOVE-RQ request to a Remote AE after successful associationestablishment. The DICOM Server AE’s Storage SCP will receive the imagesover a separate association.

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

• Verification: If a C-ECHO-RQ message is received, the DICOM Server AEwill send back a C-ECHO-RSP message with a status of “success”.

• Image Storage: If a C-STORE-RQ message is received, the DICOM ServerAE will receive the image and try to update the local database. If the imageis stored successfully on storage media and the database updated a statusof “success” will be returned in a C-STORE-RSP message.

• Query: If a C-FIND-RQ message is received the DICOM Server AE willsearch the database for the requested attributes and send back a C-FIND-RSP message containing a match and a status of “pending”. After allmatching records have been sent, a status of “success’ will be returned in aC-FIND-RSP message. The Remote AE can terminate the query by sendinga C-CANCEL-FIND-RQ message.

• Retrieve: If a C-MOVE-RQ message is received the DICOM Server AE willlookup its list of configured Remote AEs for the Destination AE. If theDestination AE is configured, the DICOM Server AE will open a newassociation to the Destination AE and use C-STORE-RQ to send theimage(s). The DICOM Server AE will send a C-MOVE-RSP message with astatus of “pending” after every five images are sent. When all images aresent or if DICOM Server AE receives a C-CANCEL-MOVE-RQ a final C-STORE-RSP will be sent back with an appropriate status.


18

2.1.3 Sequencing of Real-World Activities

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

2.2 AE SPECIFICATIONS

2.2.1 DICOM Server AE Specification

This Application Entity provides Standard Conformance to the following DICOMv3.0 SOP Classes as an SCU:

SOP Class Name (SCU) SOP Class UIDCT Image Information Storage 1.2.840.10008.5.1.4.1.1.2MR Image Information Storage 1.2.840.10008.5.1.4.1.1.4Secondary Capture image storage 1.2.840.10008.5.1.4.1.1.7Standalone Overlay storage 1.2.840.10008.5.1.4.1.1.8Study Root Query/Retrieve - FIND 1.2.840.10008.5.1.4.1.2.2.1Study Root Query/Retrieve - MOVE 1.2.840.10008.5.1.4.1.2.2.2

This Application Entity provides Standard Conformance to the following DICOMv3.0 SOP classes as an SCP:

SOP Class Name (SCP) SOP Class UIDVerification (Echo) 1.2.840.10008.1.1CT Information Storage 1.2.840.10008.5.1.4.1.1.2MR Information Storage 1.2.840.10008.5.1.4.1.1.4Secondary Capture image storage 1.2.840.10008.5.1.4.1.1.7Standalone Overlay storage 1.2.840.10008.5.1.4.1.1.8Study Root Query/Retrieve - FIND 1.2.840.10008.5.1.4.1.2.2.1Study 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 GeneralThe DICOM Application Context Name (ACN), which is always proposed, is:

Application Context Name 1.2.840.10008.3.1.1.1


19

The Maximum Length PDU negotiation is included in all associationestablishment requests. The maximum length PDU for association initiated bythe DICOM Server AE is:

Maximum Length PDU 10 Kbytes

SOP class Extended Negotiation is not supported.

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

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

2.2.1.1.2 Number of Associations

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

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

2.2.1.1.3 Asynchronous Nature

Asynchronous mode is not supported. All operations will be performedsynchronously.

2.2.1.1.4 Implementation Identifying Information

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

The Implementation UID for this ID/Net v3.0 Implementation is:

HiSpeed Advantage CT/i Implementation UID 1.2.840.113619.6.5

2.2.1.2 Association Initiation by Real-World Activity

This AE attempts to initiate a new association due to a “Push” operation initiatedby the user. A new association is also initiated when the user performs a “QueryRemote” operation or issues a retrieve operation by performing a “Get”operation at Study/Series/Image level.

2.2.1.2.1 Push Image(s) to Remote AE


20

2.2.1.2.1.1 Associated Real-World Activity

The operator must first select a destination by choosing “Select Remote Host”from the “Network” pull-down menu on the local database manager and thenchoose a hostname.

The “Push” operation will cause the DICOM server AE to initiate an Associationwhen the operator selects one or more study, series, or images in the localdatabase manager and then chooses either “Push Examination”, “Push Series”,or “Push Image” from the “Network” pull-down menu on the local databasemanager.

Note: If multiple study, series, or images are chosen to be pushed, one association will be establishedfor each of the studies, series, or images.

2.2.1.2.1.2 Proposed Presentation Contexts

The following table shows the proposed presentation contexts for the DICOMServer AE after Real-World Activity “Push” Operation has been performed.

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 - ProposalAbstract Syntax Transfer Syntax Role Extended

NegotiationName UID Name List UID List

CT Image Storage 1.2.840.10008.5.1.4.1.1.2 Implicit VR LittleEndian

1.2.840.10008.1.2 SCU None

CT Image Storage 1.2.840.10008.5.1.4.1.1.2 JPEG LosslessHierarchicalFirst-OrderPrediction

1.2.840.10008.1.2.4.70 SCU None

MR ImageStorage

1.2.840.10008.5.1.4.1.1.4 Implicit VR LittleEndian

1.2.840.10008.1.2 SCU None

MR ImageStorage

1.2.840.10008.5.1.4.1.1.4 JPEG LosslessHierarchicalFirst-OrderPrediction

1.2.840.10008.1.2.4.70 SCU None

SecondaryCapture


1.2.840.10008.1.2 SCU None

SecondaryCapture


1.2.840.10008.1.2.2.4.70 SCU None

Stand-aloneOverlay


1.2.840.10008.1.2 SCU None

Stand-aloneOverlay


1.2.840.10008.1.2.2.4.70 SCU None

Study RootQuery/Retrieve

FIND

1.2.840.10008.5.1.4.1.2.2.1

Implicit VR LittleEndian

1.2.840.10008.1.2 SCU None


MOVE

1.2.840.10008.5.1.4.1.2.2.2


1.2.840.10008.1.2 SCU None


21

Note: Other Abstract Syntax and Transfer Syntax names may be offered whenestablishing an association. These are private syntaxes which may be ignored.See section 5.

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 singleassociation.

Upon receiving a C-STORE confirmation containing a Successful status, thisimplementation will perform the next C-STORE operation. The association will bemaintained if possible.

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

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

Each C-STORE operation supports an “Association Timer”. This timer startswhen the association request is sent or received and stops when the associationis established. The time-out is 900 seconds.

Each C-STORE operation also supports an “Operation Inactivity Timer”. Thistime-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 orwhen subsequent C-STORES are sent. This time-out is 900 seconds.

Each C-STORE operation also supports a “Session Timer”. This timer startswhen the association is established and stops when the association is ended.This time-out is 60 minutes.

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

When DICOM Server AE initiates an association to issue a C-STORE, one of thefollowing two operations will be performed: If the image is stored locally on the HiSpeed Advantage CT/i in DICOM format(“Dic” appears in the “Fmt” column at the exam level of the local databasemanager), the image will be transmitted by the DICOM Server AE with the sameelements as was originally received or created locally (for the standard elementsonly).

If the image is stored locally on the HiSpeed Advantage CT/i in a non-DICOMAdvantage format (“Adv appears in the “Fmt” field at the exam level of the localdatabase manager), the image will be translated and then transmitted by theDICOM Server AE to the identical profiles specified by the CT AdvantageConformance Statement for DICOM v3.0 (Direction 2118781) and the MR SignaAdvantage Conformance Statement for DICOM v3.0 (Direction 2118782).

2.2.1.2.2 Query Remote AE


22


The operator must first select a destination by choosing “Select Remote Host”from “Network” pull-down menu on the local database manager and then choosea hostname.

The “Query” operation will cause the DICOM Server AE to initiate an associationto the selected Remote AE when the “Query Remote Host” entry is selectedfrom the “Network” pull-down menu. Once a list of Study/Series/Image isretrieved, the operator can invoke the “Pull” operation by choosing “Get Exam”or “Get Series” or “Get Image” from the “Network” pull-down menu.


23


When the Real-World activity “Query” or “Pull” is initiated all presentationcontexts shown in table 2.2.1.2.1.2-1 are proposed during associationestablishment, but only the Query/Retrieve-FIND related contexts are applicableto 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) insuccession. The Initial Study-Level request will ask for all studies in the Remotedatabase.The C-FIND SCU will not perform any extended negotiation and so will onlyperform hierarchical query.

Each C-FIND SCU operation supports an “Association Timer”, “OperationInactivity Timer” and “Session Timer” with time out values of 900 seconds, 900seconds and 60 minutes respectively.

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

The DICOM Server AE will parse each matching C-FIND-RSP reply and ignorethe entries it fails to parse.

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

Table 2.2.1.2.2.2.1-1: Requested Study Level Keys

Description Type Tag ValueStudy date R 0008,0020 Zero lengthStudy time R 0008,0030 Zero lengthPatient’s name R 0010,0010 Zero lengthStudy id R 0020,0010 Zero lengthStudy Instance UID U 0020,000D Zero lengthStudy description O 0008,1030 Zero lengthPrivate Creator Indentification P1 0009,00xx GEMS_IDEN_01Suite Id P2 0009,xx02 Zero Length

Table 2.2.1.2.2.2.1-2: Requested Series Level Keys

Description Type Tag ValueModality R 0008,0060 Zero lengthSeries number R 0020,0011 Zero length

1 Private data element

2 Private data element


24

Description Type Tag ValueSeries Instance UID U 0020,000E Series UIDSeries description O 0008,103E Zero lengthManufacturer O 0008,0070 Zero lengthImages in series O 0020,1002 Zero length

Table 2.2.1.2.2.2.1-3: Requested Image Level Keys

Description Type Tag ValueImage number R 0020,0013 Zero lengthImage Instance UID U 0008,0018 Image UIDImage type O 0008,0008 Zero lengthRows O 0028,0010 Zero lengthColumns O 0028,0011 Zero lengthImage position O 0020,0032 Zero lengthImage orientation O 0020,0037 Zero lengthSlice thickness O 0018,0050 Zero lengthSlice spacing O 0018,0088 Zero lengthGantry tilt O 0018,1120 Zero lengthConvolution kernel O 0018,1210 Zero lengthReconstruction diameter O 0018,1100 Zero lengthData collection diameter O 0018,0090 Zero lengthFlip angle O 0018,1314 Zero lengthEcho number O 0018,0086 Zero lengthEcho time O 0018,0081 Zero lengthInversion time O 0018,0082 Zero lengthRepetition time O 0018,0080 Zero lengthTrigger time O 0018,1060 Zero lengthDfov Rect P 0019,001E Zero LengthMidscan Time P 0019,0024 Zero LengthAzimuth P 0019,0026 Zero LengthNumber of Echo P 0019,007E Zero LengthScout Anref P 0021,004A Zero LengthLocation RAS P 0027,0040 Zero LengthLocation P 0027,0041 Zero LengthCenter R Coordinate P 0027,0042 Zero LengthCenter A Coordinate P 0027,0043 Zero LengthTable Start Location P 0027,0050 Zero LengthTable End Location P 0027,0051 Zero LengthRAS Letter for Side of Image P 0027,0052 Zero LengthRAS Letter for Anterior/Posterior P 0027,0053 Zero LengthRAS Letter for Scout Start Location P 0027,0054 Zero LengthRAS Letter for Scout End Location P 0027,0055 Zero LengthImage Dimension X P 0027,0060 Zero LengthImage Dimension Y P 0027,0061 Zero Length

2.2.1.2.3 Get Image(s) from Remote AE



25

The operator must first select a destination by choosing “Select Remote Host”from “Network” pull-down menu on the local database manager and then choosea hostname. The operator then has to perform the Real-World activity “Query” toget a list of Study/Series/Image. Once the list of Study/Series/Image is retrieved,the operator can invoke the “Get” operation by choosing “Get Exam” or “GetSeries” or “Get Image” from the “Network” pull-down menu.


When the Real-World activity “Get” is initiated all presentation contexts shown intable 2.2.1.2.1.2-1 are proposed during association establishment, but only theQuery/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) theDICOM Server AE will initiate a C-MOVE-RQ request to the Remote AE with theDICOM Server AE as the Destination AE. The Storage SCP will handle theincoming images as described in section 2.1.3.1.

Each C-MOVE SCU operation supports an “Association Timer”, “OperationInactivity Timer” and “Session Timer” with time out values of 900 seconds, 300seconds and 60 minutes respectively.

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

2.2.1.3 Association Acceptance Policy

The DICOM Server AE places no limitations on who may connect to it.

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

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 ofRemote 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 thepurpose of verification.

2.2.1.3.1 Receive Image(s)

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


26


The Real-World Activity associated with the Receive Image(s) operation is thestorage of the image on the disk drive of the HiSpeed Advantage CT/i.

2.2.1.3.1.2 Presentation Context Table

Table 2.2.1.3.1.2-1: Acceptable Presentation Contexts for DICOM Server AE and Real-WorldActivity

Receive Image(s)

Presentation Context TableAbstract Syntax Transfer Syntax Role Extended


Verification 1.2.840.10008.1.1 Implicit VR LittleEndian

1.2.840.10008.1.2 SCP None

CT Image Storage 1.2.840.10008.5.1.4.1.1.2 Implicit VR LittleEndian

1.2.840.10008.1.2 SCP None

CT Image Storage 1.2.840.10008.5.1.4.1.1.2 JPEG LosslessHierarchicalFirst-OrderPrediction

1.2.840.10008.1.2.4.70 SCP None

MR ImageStorage


1.2.840.10008.1.2 SCP None

MR ImageStorage


1.2.840.10008.1.2.4.70 SCP None

SecondaryCapture


1.2.840.10008.1.2 SCP None

SecondaryCapture


1.2.840.10008.1.2.2.4.70 SCP None

Stand-aloneOverlay


1.2.840.10008.1.2 SCP None

Stand-aloneOverlay


1.2.840.10008.1.2.2.4.70 SCP None

2.2.1.3.1.2.1 SOP Specific Conformance to Storage SOP Classes

The DICOM Server AE conforms to the SOP’s of the Storage Service Class atlevel 1 (base). Private elements will be discarded from the image when receivingimages containing non-GE private data elements.

Each C-STORE SCP operation supports an “Association Timer”, “OperationInactivity Timer” and “Session Timer” with time out values of 900 seconds, 900seconds and 60 minutes 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:


27

• 0110 (Processing Failure) Indicates that an internal system call has failedwhile processing an image.

• A711 (Out of Resources) Indicates that probably there was not enough disk

space to store the image. The user should attempt recovery by removingsome images from the HiSpeed Advantage CT/i system.

• A712 (Out of Resources) Indicates that there was not enough resource (such

as memory) to store the image. • A800 (SOP Class not supported)

In the event of a successful C-STORE operation, the image has successfullybeen written to disk. The image will then be accessed in the same manner asany other image by the applications on the HiSpeed Advantage CT/i system.

Images may be deleted when instructed to do so by the user. Thus the durationof the storage of the image is determined by the users of the HiSpeed AdvantageCT/i system.

Image Installation

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

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

Image Installation of GE Created MR or CT Images

Images that were originally created on recent GE MR and CT scanners will beconverted from their native Advantage Proprietary Format to DICOM format fortransmission. If the images are stored as full fidelity representations and aresubsequently returned to recent GE scanners, then the images will betransformed back to Advantage Proprietary Format.

There is an assumption made by such GE scanners: The private element (0009,xx01) is used as the full fidelity flag. If this flag

contains the string: “GE_GENESIS_FF” when received by a scanner, then itis assumed that the image object was originally a GE created image objectand contains all private elements that it was sent with.

If not all the elements are sent back as sent (i.e., not full fidelity) there are 2

possible actions:1. the translator will do its best to convert the image and will use default values

where DICOM fields are missing2. If certain critical information is not provided then the image will be stored as

a screen save It is strongly suggested that if GE private element (0009,xx01) is present then all

GE private elements originally associated with the image be preserved.

2.2.1.3.2 Verification Request from Remote AE


28

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


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.



Verification Request



Verification 1.2.840.10008.1.1 Implicit VR LittleEndian

1.2.840.10008.1.2 SCP None

2.2.1.3.2.2.1 SOP Specific Conformance to Verification SOP Class

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

Each ECHO operation supports an “Association Timer”, “Operation InactivityTimer” and “Session Timer” with a time out values of 900 seconds, 30 secondsand 60 minutes respectively.

2.2.1.3.3 Query Request from Remote AE

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


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



29


Query Request




FIND

1.2.840.10008.5.1.4.1.2.2.1


1.2.840.10008.1.2 SCU None

2.2.1.3.3.2.1 SOP Specific Conformance to C-FIND SCP

Each C-FIND SCP operation supports an “Association Timer”, “OperationInactivity Timer” and “Session Timer” with a time out values of 900 seconds, 900seconds and 60 minutes respectively.

All Required( R) and Unique(U) study, series, and image level keys for theStudy-Root Query/Retrieve information model are supported. Some optional (O)keys are also supported as described in the following tables.

Table 2.2.1.3.3.2.1-1 Supported study level keys

Description Type Tag UsageStudy date R 0008,0020 MatchedStudy time R 0008,0030 MatchedAccession number R 0008,0050 MatchedPatient’s name R 0010,0010 Matched3

Patient id R 0010,0020 MatchedStudy id R 0020,0010 MatchedStudy Instance UID U 0020,000D MatchedStudy description O 0008,1030 ReturnedSuite Id P 0009,0002 Returned

Table 2.2.1.3.3.2.1-2 Supported series level keys

Description Type Tag UsageModality R 0008,0060 MatchedSeries number R 0020,0011 MatchedSeries Instance UID U 0020,000E MatchedSeries description O 0008,103E ReturnedManufacturer O 0008,0070 ReturnedImages in series O 0020,1002 Returned

Table 2.2.1.3.3.2.1-3 Supported image level keys

Description Type Tag Usage

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


30

Description Type Tag UsageImage number R 0020,0013 MatchedImage Instance UID U 0008,0018 MatchedImage type O 0008,0008 ReturnedRows O 0028,0010 ReturnedColumns O 0028,0011 ReturnedImage position O 0020,0032 ReturnedImage orientation O 0020,0037 ReturnedSlice thickness O 0018,0050 ReturnedSlice spacing O 0018,0088 ReturnedGantry tilt O 0018,1120 ReturnedConvolution kernel O 0018,1210 ReturnedReconstruction diameter O 0018,1100 ReturnedData collection diameter O 0018,0090 ReturnedFlip angle O 0018,1314 ReturnedEcho number O 0018,0086 ReturnedEcho time O 0018,0081 ReturnedInversion time O 0018,0082 ReturnedRepetition time O 0018,0080 ReturnedTrigger time O 0018,1060 ReturnedDfov Rect P 0019,001E ReturnedMidscan Time P 0019,0024 ReturnedAzimuth P 0019,0026 ReturnedNumber of Echo P 0019,007E ReturnedScout Anref P 0021,004A ReturnedLocation RAS P 0027,0040 ReturnedLocation P 0027,0041 ReturnedCenter R Coordinate P 0027,0042 ReturnedCenter A Coordinate P 0027,0043 ReturnedTable Start Location P 0027,0050 ReturnedTable End Location P 0027,0051 ReturnedRAS Letter for Side of Image P 0027,0052 ReturnedRAS Letter for Anterior/Posterior P 0027,0053 ReturnedRAS Letter for Scout Start Location P 0027,0054 ReturnedRAS Letter for Scout End Location P 0027,0055 ReturnedImage Dimension X P 0027,0060 ReturnedImage Dimension Y P 0027,0061 Returned

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

Values in keys of type Returned will be ignored and will be filled in with data fromthe 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 optionalkey a zero-length element will be returned.

Sequence matching is not supported.

Range matching is supported for attributes of type date and time.


31

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

2.2.1.3.4 Retrieve Request From Remote AE

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


The Real-World Activity associated with the Retrieve Request is to send allimages corresponding to the C-MOVE request to the destination AE through aseparate association.



Retrieve Request.




MOVE

1.2.840.10008.5.1.4.1.2.2.2


1.2.840.10008.1.2 SCU None

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”, “OperationInactivity Timer” and “Session Timer” with a time out values of 900 seconds, 300seconds and 60 minutes respectively.

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

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

SOP Class Name SOP Class UIDCT Image Information Storage 1.2.840.10008.5.1.4.1.1.2MR Image Information Storage 1.2.840.10008.5.1.4.1.1.4Secondary Capture image storage 1.2.840.10008.5.1.4.1.1.7Standalone Overlay storage 1.2.840.10008.5.1.4.1.1.8


32

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

• C000 - Indicates that an error occurred while retrieving records from the localdatabase.

• 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 astatus of A711 and is only applicable if the Destination AE is an SdC-basedproduct.

2.2.1.3.4.3 Presentation Context Acceptance Criteria

No criterion.

2.2.1.3.4.4 Transfer Syntax Selection Policy

All protocols detailed above in the tables are supported, no priority selection isgiven.


33

2.3 SECTION 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.3.3 Point-to-Point StackA 50-pin ACR-NEMA connection is not applicable to this product.


34

2.4 SECTION 4 - EXTENSIONS / SPECIALIZATIONS / PRIVATIZATIONS

2.4.1 Specialized Information Object Definition

Following is a list of additional private attributes defined for a standard MR IOD.

(0008,0008) Value 3: MR Image IOD specific specializationsPROJECTION IMAGEREFORMATTEDSCREEN SAVEPROCCOMB

Value 4 : MR Image implementation specificCOLLAPSEVASCULARIVI

(0018,0022) Scan Options : Defined TermsVASCTOF_GEMSVASCPC_GEMSCINE_GEMSFAST_GEMSIIC_GEMSGRAPH_GEMSIRP_GEMSDEP_GEMSCL_GEMSSAT_GEMSNPWRT_GEMSVB_GEMSPOMP_GEMSVB_GEMSEDR_GEMSSEQ_GEMSCS_GEMSMP_GEMSSQPIX_GEMSMT_GEMSEPI_GEMSTRF_GEMSRTR_GEMSFT_GEMSNF_GEMSRAMP_RL_GEMSRAMP_LR_GEMSRAMP_AP_GEMSRAMP_PA_GEMSRAMP_SI_GEMSRAMP_IS_GEMSFC_FREQ_AX_GEMS


35

FC_SLICE_AX_GEMSSS_GEMSVASCANGIO_GEMS

2.4.2 Private SOP’sID/Net v2.0 Private IOD’s are based upon the April 1993 draft version of theDICOM v3.0. ID/Net v2.0 IOD’s are supported for backward compatibility.

Note: See the “ID/Net v2.0 Implementation Profiles” (Direction 46-269546G2) fordefinitions of Information Objects.

Presentation Context Table - Accepted / ProposedAbstract Syntax Transfer Syntax Role Extended


GE PrivateDICOM MR ImageInformation Object

(ID/Net v2.0compatible)

1.2.840.113619.4.2 Implicit VR LittleEndian

1.2.840.10008.1.2 Both None

GE PrivateDICOM MR ImageInformation Object


1.2.840.113619.4.2 Implicit VR BigEndian

(GE Private)

1.2.840.113619.5.2 Both None

GE PrivateDICOM CT ImageInformation Object



1.2.840.10008.1.2 Both None

GE PrivateDICOM CT ImageInformation Object



(GE Private)

1.2.840.113619.5.2 Both None

GE PrivateDICOM Display

Information Object(ID/Net v2.0compatible)


1.2.840.10008.1.2 Both None

GE PrivateDICOM Display

Information Object(ID/Net v2.0compatible)


(GE Private)

1.2.840.113619.5.2 Both None


36

2.4.3 Private Data Elements

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

2.5 SECTION 5 - CONFIGURATION

2.5.1 AE Title/Presentation Address Mapping

The HiSpeed Advantage CT/i system allows the user to “add”, “Remove”, or“Update the mapping of remote AE Titles to IP Addresses and Ports. Theseoptions can be selected from the “Remote Host Selection” menu displayed bychoosing “Select Remote Host” from the “Network” pull-down menu from thelocal database manager.

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

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

Note: The local port on which the HiSpeed Advantage CT/i system receives DICOMincoming TCP connections is port 4006.

2.6 SECTION 6 - SUPPORT OF EXTENDED CHARACTER SETS

In addition to the DICOM default character set, HiSpeed Advantage CT/isupports the ISO IR 100 Latin alphabet #1 supplementary set for thepurpose of interchange.

3 SECTION 3 - MOD Archive Conformance

3.0 Introduction

This conformance statement specifies the HiSpeed Advantage CT/i conformance to the DICOM Media StorageApplication Profile.

3.1 Implementation Model : MOD Archive Server


37

The MOD Archive Server creates and/or updates the 5 1/4 inch MOD media with various DICOM SOPinstances. It can process CT, MR, Secondary Capture and Overlay IOD's.

3.1.1 Application Data Flow Diagram

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

The MOD Archive Server AE can initialize Media by acting as an FSC to create a new DICOM File-set on1.2GB MOD media. It initializes the DICOM File-set and writes the specified SOP instances onto the MOD.The SOP instances written will be limited to instances that match the criteria of one of the Application Profilesthat is supported. When updating media, a pre-existing File-set will be updated with the selected SOP instancesthat match one of the supported Application Profiles

3.1.2 Functional Definitions of AE's

This Server has only one Application Entity: the MOD Archive Application

The MOD Archive Application can perform these functions:

• It can initialize (create DOS filesystem) a piece of media, writing a new label and DICOM File-set onto themedia;

• It can update a piece of media by adding new SOP instances to an already existing DICOM File-set fromlocal storage;

• It can display a directory listing of the File-set on a piece of media;

DisplayDirectory

Real-WorldActivity

Create MODReal-World

Activity

LocalStorage

Real-WorldActivity

UpdateMOD Real-

WorldActivity

MOD Archive ApplicationEntity

MODStorageMedium


38

• It can copy SOP instance from the MOD onto local storage

3.1.3 Sequencing of Real World Activities

The updating function can only be performed on a piece of media that has already had a DICOM File-setcreated. There are no other sequencing requirements.

3.1.4 File Meta Information for Implementation Class and Version

Implementation Class UID = 1.2.840.113619.6.13Implementation Version Name = 1.2.5

3.2 AE Specifications

3.2.1 MOD Archive Specification

The MOD Archive provides standard conformance to DICOM Interchange Option of the Media Storage ServiceClass. The Application Profiles and roles are listed in Table 3.1-1.

Table 3.1-1 : Application Profile, Activities and Roles for MOD UpdateApplication Profiles

SupportedReal World Activity Role SC Option

PRI-CTMR-MOD12 Create MOD FSC InterchangeUpdate MOD FSU Interchange

Display Directory FSR InterchangeCopy To Local Storage FSR Interchange

The MOD Archive Application will query the user before initializing media when a File-set is found on themedia and an initialize operation has been requested.

3.2.1.1 File Meta Information for the Application Entity

The Source Application Entity Title is not set for the MOD Archive Application.

3.2.1.2 Real World Activities

3.2.1.2.1 Real World Activity: Create MOD Request

The MOD Archive Application acts as an FSC using the Interchange option when requested to initialize media.

The MOD Archive Application will label the media and take the user provided list of SOP instances eliminatingany SOP instances on that list does not correspond to one of the Application Profiles in Table 3.1-1. These SOP


39

instances are written to the media and a corresponding DICOMDIR is created. The determination of thepotentially applicable Application Profile is dependent on the type of media and the associated software onwhich the AE has been invoked.

3.2.1.2.1.1 Application Profiles for the RWA: Create MOD

For the list of Application Profiles that invoke this AE for the Create MOD RWA, see Table 3.1-1. Forextensions and specialization’s see section 5.

3.2.1.2.2 Real World Activity: Display Directory

The MOD Archive Application acts as an FSR using the Interchange option when requested to provide adirectory listing.

When an MOD update Application is requested to provide a directory listing it will read the File-set and displaythe DICOMDIR directory entries for those SOP instances in the File-set that correspond to the user selectedApplication Profile.

3.2.1.2.2.1 Application Profiles for the RWA: MOD Directory Listing

For the list of Application Profiles that invoke this AE for the MOD directory listing RWA, see Table 3.1-1.There are no extensions or specialization’s.

3.2.1.2.3 Real World Activity: Copy to Local Storage

The MOD Archive Application acts as an FSR when copying from the MOD to local storage.

The MOD Archive Application will copy any SOP Instance selected from an MOD Directory list from theMOD to the local storage upon request. The MOD Directory listing Real-World Application will filter out theSOP Instances that do not match the Application Profile.

3.2.1.2.3.1 Application Profiles for the RWA: Copy to Local Storage

For the list of Application Profiles that invoke this AE for the MOD Copy to Local Storage RWA, see Table3.1-1. For extensions and specialization’s see section 5.

3.2.1.2.4 Real World Activity: Update MOD

The MOD Archive Application acts as an FSU using the Interchange option when requested to update an MOD.

The MOD Archive Application will take the selected list of SOP instances and eliminate any SOP instance thatdoes not correspond to permissible SOP instances listed in the Application Profiles Table 3.1-1. The remainingSOP instances are written to the media that is found in the MOD Archive Application disk drive. Thedetermination of the potentially applicable Application Profile is dependent on the type of media and associatedsoftware on which the AE has been invoked.


40

3.2.1.2.4.1 Application Profiles for the RWA: Update MOD Request

For the list of Application Profiles that invoke this AE for the MOD Copy to Local Storage RWA, see Table3.1-1. For extensions and specialization’s see section 5.

3.3 Augmented and Private Application Profiles

3.3.1 Private Application Profiles

The MOD Archive Server supports only one private Application Profile: PRI-CTMR-MOD12.

3.3.1.1 Class and Profile Identification

The Class of Application Profiles defined here is for Computed Tomography and Magnetic Resonance ImagingClinical applications.

The identifier for this class is PRI-CTMR-MOD12.

The specific Application Profile in this class is shown in Table 3.3.1-1.

Table 3.3.1-1 : CTMR MOD ProfilesApplication Profile Identifier Description

CT/MR Studies on MOD media PRI-CTMR-MOD12 It handles single frame 12 or 16bit grayscale

compressed/uncompressedimages.

3.3.1.2 Clinical Contexts

This Application Profile facilitates the interchange of primary CT and MR images as well as processed CT andMR images as Secondary Capture and Standalone Overlay Images with certain defined attributes. CT, MR, SCand OV images may co-exist within the same File-set.

Typical interchanges would be between acquisition devices, archives and workstations within and betweeninstitutions.

3.3.1.2.1 Roles and Service Class Options

This Application Profile Class uses the Media Storage Service Class defined in PS3.4 with the InterchangeOption.

The Application Entity shall support one or more roles of the File-set Creator, File-set Reader and File-setUpdater defined in PS3.10.


41

3.3.1.2.1.1 File Set Creator

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

FSC shall offer the ability to either finalize the disc at the completion of most recent write session (noadditional information can be subsequently added to the disc) or to allow multi-session (additional informationmay be subsequently added to the volume).

3.3.1.2.1.2 File Set Reader

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

3.3.1.2.1.3 File Set Updater

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

FSU shall offer the ability to allow multi-session (additional information may be subsequently added to thevolume) writes.

3.3.1.3 PRI-CTMR-MOD12 Class Profile

3.3.1.3.1 SOP Classes and Transfer Syntaxes

This class of Application Profiles is based on the Media Storage Service Class with the Interchange Option. (seePS3.4).

SOP Classes and corresponding Transfer Syntaxes supported by these Application Profiles are specified in theTable 3.3.3.1-1.

Table 3.3.3.1-1 : IOD's and Transfer Syntaxes for PRI-CTMR-MOD12Information

ObjectSOP Class UID Transfer Syntax and UID FSC

Req.FSRReq.

FSUReq.


42

DefinitionBasic

Directory1.2.840.10008.1.3.10 Explicit VR Little Endian

Uncompressed1.2.840.10008.1.2.1

M M M

CT ImageStorage

1.2.840.10008.5.1.4.1.1.2 Explicit VR Little EndianUncompressed

1.2.840.10008.1.2.2

O M O

CT ImageStorage

1.2.840.10008.5.1.4.1.1.2 JPEG Lossless ProcessSelection Value 14

1.2.840.10008.1.2.4.70

O M O

MR ImageStorage


1.2.840.10008.1.2.2

O M O

MR ImageStorage


1.2.840.10008.1.2.4.70

O M O

SC ImageStorage


1.2.840.10008.1.2.2

O M O

SC ImageStorage


1.2.840.10008.1.2.4.70

O M O

StandaloneOverlay


1.2.840.10008.1.2.2

O O O

StandaloneOverlay


1.2.840.10008.1.2.4.70

O O O

M : MandatoryO : Optional

NOTE:The MOD Archive Application chooses the JPEG Lossless compression (selection value 1) as the defaulttransfer syntax for storing images on the media. But the transfer syntax is selectable on a per media basis atinstall time using a method defined by the Application.

3.3.1.3.2 Physical Media and Media Formats

The CT/MR Application Profiles in the PRI-CTMR-MOD12 require the 130mm 1.2GB Magneto-OpticalRewritable physical media with the PC File System as defined in PS3.12.

3.3.1.3.3 Logical Format

The PRI-CTMR-MOD12 Application profile media format conforms to the Logical Format specification inPS3.12. Table 3.3.3.3-1 defines the specific values used for this profile.

Table 3.3.3.3-1 : Boot SectorBytes(s) Value Description00 - 02 0xEB3C90 Jump instruction to loader (NOPs)03 - 10 “MSDOS4.0” The formatting DOS (vendor specific)


43

11 - 12 0200H 512 bytes/sector13 32 sectors/cluster14-15 0001H 1 sector in boot record16 02H 2 File Allocation Tables (FAT)17 - 18 200H 512 root directory entries19 - 20 0000H Flag for more than 65536 sector/disk. Use offset 32 value21 0xF8 Flag for disk type; F0H if not otherwise specified22 - 23 143 sectors/FAT24 - 25 31 sectors/track26 - 27 1 side (head) per disk28 - 31 00000000 0 reserved or hidden sectors32 - 35 1163337 Total sector/disk. Varies from disk to disk36 - 37 0000 Physical Drive number = 038 29H Extended boot record signature = 4139 - 42 Date Stamp Volume serial number43 - 53 “GEMS-DICOM”54 - 61 - The file system label62 - 509 - Don’t care. Any contents acceptable510 - 511 0xAA55 Signature flag

3.3.1.3.4 Directory Information in DICOMDIR

Conformant Application Entities shall include in the DICOMDIR File a Basic Directory IOD containingDirectory Records at the Patient and subsidiary levels appropriate to the SOP Classes in the File-set. AllDICOM files in the File-set incorporating SOP Instances defined for the specific Application Profile shall bereferenced by the Directory Records.

NOTE:The modality attribute (0008,0060) in the DICOMDIR Series records should be CT/MR for Secondary Captureand Standalone Overlay SOP Class Images. Otherwise the HiSpeed Advantage CT/i DICOM media displaybrowser will not list-up the series for contents rendering the retrieval to local storage impossible.

Also refer to Appendix C for a complete listing of all the optional modules and attributes used in theDICOMDIR definition.

3.3.1.3.4.1 Additional Keys

None.

3.3.1.3.5 Other Parameters

This section defines other parameters common to all specific Application Profiles in the PRI-CTMR-MOD12class which need to be specified in order to ensure interoperable information interchange.

3.3.1.3.5.1 Image Attribute Values


44

The attributes listed in Table 3.3.3.5.1-1 used within the CT/MR/SC/Standalone Overlay Image files, shall takethe values specified.

Table 3.3.3.5.1-1: PRI-CTMR-MOD12 Required Image Attribute Values for CT and MR, SCand OV Images

Attribute Tag ValueModality (0008,0060) CT/MR

Photometric Interpretation (0028,0004) MONOCHROME2Bits Allocated (0028,0100) 16

Bits Stored (0028,0101) 16

Overlay data if present shall be encoded in Overlay Data (60XX,3000).

3.3.1.3.5.1.1 Attribute Value Precedence

None.

3.4 Extensions, Specialization’s and Privatization’s of SOP Classesand Transfer Syntaxes

3.4.1 Extensions, Specialization’s and Privatization’s of SOPClasses

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

3.4.1.1 SOP Specific Conformance Statement for CT SOP Class

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

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.

3.5 Configuration

The MOD Archive Application will have only 1.2GB drive installed.


45

Table 3.5-1 : Supported Profiles for various Drive ConfigurationsDisk Drive Installed Profiles Supported

1.2GB-Only Drive PRI-CTMR-MOD12

3.6 Support of Extended Character Sets

The MOD Archive Application will support copy of SOP instances containing the ISO-IR 100 (Latin alphabetNo. 1, supplementary set) and DICOM default character sets as defined in PS3.5.


46

Appendix A Optional/Conditional Modules/AttributesEnclosed is a listing of only the Optional/Conditional modules/attributes used by this implementation forCT/MR/SC and Standalone Overlay IOD’s.

NOTE: All other modules which are mandatory and attributes which are type 1 & 2 in nature per the DICOMstandard are supported by this implementation but are not explicitly listed here.

A.1 CT Specific IOD Definition

A.1.1 CT Image IOD ModulesIE Module Reference UsageStudy Patient Study C.7.2.2 (DICOM

PS3.3)U

Image Contrast Bolus C.7.6.4 (DICOMPS3.3)

C

A.1.2 CT Image ModuleAttribute Name Tag Type NotesScan Options (0018,0022) 3Date CollectionDiameter

(0018,0090) 3

ReconstructionDiameter

(0018,1100) 3

Distance Source toDetector

(0018,1110) 3

Distance Source toPatient

(0018,1111) 3

Gantry / Detector Tilt (0018,1120) 3Table Height (0018,1130) 3Rotation Direction (0018,1140) 3Exposure Time (0018,1150) 3Xray Tube Current (0018,1151) 3Exposure (0018,1152) 3Filter Type (0018,1160) 3Focal Spot (0018,1190) 3Convolution Kernel (0018,1210) 3

A.2 MR Specific IOD Definition

A.2.1 MR Image IOD ModulesIE Module Reference UsageStudy Patient Study C.7.2.2 (DICOM

PS3.3)U

Image Contrast Bolus C.7.6.4 (DICOMPS3.3)

C

A.2.2 MR Image ModuleAttribute Name Tag Type Notes


47

Trigger Time (0018,1060) 2CAngio Flag (0018,0025) 2CNumber Of Averages (0018,0083) 3Imaging Frequency (0018,0084) 3Imaged Nucleaus (0018,0085) 3Echo Number (0018,0086) 3Magnetic FieldStrength

(0018,0087) 3

Spacing Between Slices (0018,0088) 3Percent Sampling (0018,0093) 3Percent Phase Field ofView

(0018,0094) 3

Pixel Bandwidth (0018,0095) 3Nominal Interval (0018,1062) 3Heart Rate (0018,1088) 3Cardiac Number ofImages

(0018,1090) 3

Trigger Window (0018,1094) 3ReconstructionDiameter

(0018,1100) 3

Receiving Coil (0018,1250) 3Transmitting Coil (0018,1251) 3Acquisition Matrix (0018,1310) 3Phase EncodingDirection

(0018,1312) 3

Flip Angle (0018,1314) 3Variable Flip AngleFlag

(0018,1315) 3

SAR (0018,1316) 3Temporal Resolution (0020,0110) 3

A.3 SC Specific IOD Definition

A.3.1 SC Image IOD ModulesIE Module Reference UsageStudy Patient Study C.7.2.2 (DICOM

PS3.3)U

Equipment General Equipment C.7.5.1 (DICOMPS3.3)

U

Image Overlay Plane C.7.9.2 (DICOMPS3.3)

U

A.4 Standalone Overlay Specific IOD Definition

A.4.1 Standalone Overlay Image IOD ModulesIE Module Reference UsageStudy Patient Study C.7.2.2 (DICOM

PS3.3)U


48

A.5 CT/MR/SC/Standalone Overlay IOD Common Table Definitions

A.5.1 General Study ModuleAttribute Name Tag Type NotesStudy Description (0008,1030) 3Name of Physician(s)Reading Study

(0008,1060) 3

A.5.2 Patient Study ModuleAttribute Name Tag Type NotesPatient’s Age (0010,1010) 3Patient’s Weight (0010,1030) 3Additional Patient’sHistory

(0010,21b0) 3

A.5.3 General Series ModuleAttribute Name Tag Type NotesLaterality (0020,0060) 2CSeries Date (008,0021) 3Series Time (0008,0031) 3Performing Physicians’Name

(0008,1050) 3

Protocol Name (0008,1030) 3Series Description (0008,103E) 3Operators Name (0008,1070) 3Patient Position (0018,5100) 2C

A.5.4 General Equipment ModuleAttribute Name Tag Type NotesInstitution Name (0008,0080) 3Station Name (0008,1010) 3Manufacturers ModelName

(0008,1090) 3

Device Serial Number (0018,1000) 3

Software Versions (0018,1020) 3

Spatial Resolution (0018,1050) 3 Only for CT/MR IOD’s

Pixel Padding Value (0028,0120) 3 Only for CT/MR IOD’s

A.5.5 General Image ModuleAttribute Name Tag Type NotesImage Date (0008,0023) 2CImage Time (0008,0033) 2CImage Type (0008,0008) 3Acquisition Number (0020,0012) 3Acquisition Date (0008,0022) 3Acquisition Time (0008,0032) 3


49

A.5.6 Image Plane ModuleAttribute Name Tag Type NotesImage Slice Location (0020,1041) 3

A.5.7 Contrast Bolus ModuleAttribute Name Tag Type NotesContrast/Bolus Route (0018,1040) 2C

A 5.8 SOP Common ModuleAttribute Name Tag Type NotesSpecific Character Set (0008,0005) 1C ISO IR 100

A 5.9 Overlay Plane ModuleAttribute Name Tag Type NotesOverlay Data (60xx,3000) 1C Only for SC &

Standalone OverlayIOD Definitions


50

Appendix B Private Data Elements

Enclosed is a listing of private data elements used in this implementation for CT/MR Image IOD definition.

B.1 CT Image IOD Private Data Elements Definition;;Grp Elm VR VM Type Definition;0009 00xx LO S 3 Private Creator Identification (GEMS_IDEN_01)0009 xx01 LO S 3 full fidelity0009 xx02 SH S 3 suite id0009 xx04 SH S 3 product id0009 xx27 SL S 3 image actual date0009 xx30 SH S 3 service id0009 xx31 SH S 3 mobile location number0009 xxE3 UI S 3 equipment UID0009 xxE6 SH S 3 Genesis Version - now0009 xxE7 UL S 3 Exam Record checksum0009 xxE9 SL S 3 Actual series data time stamp

0011 00xx LO S 3 Private Creator Identification (GEMS_PATI_01)0011 xx10 SS S 3 Patient Status

0019 00xx LO S 3 Private Creator Identification (GEMS_ACQU_01)0019 xx02 SL S 3 number of cells I in Detector0019 xx03 DS S 3 cell number at Theta0019 xx04 DS S 3 cell spacing0019 xx0F DS S 3 Horiz. frame of ref.0019 xx11 SS S 3 series contrast0019 xx13 SS S 3 start number for baseline0019 xx14 SS S 3 end number for baseline0019 xx15 SS S 3 start number for enhanced scans0019 xx16 SS S 3 end number for enhanced scans0019 xx17 SS S 3 series plane0019 xx18 LO S 3 first scan ras0019 xx19 DS S 3 first scan location0019 xx1A LO S 3 last scan ras0019 xx1B DS S 3 last scan loc0019 xx1E DS S 3 display field of view0019 xx23 DS S 3 table speed0019 xx24 DS S 3 mid scan time0019 xx25 SS S 3 mid scan flag0019 xx26 SL S 3 degrees of azimuth0019 xx27 DS S 3 gantry period0019 xx2A DS S 3 X-Ray On position0019 xx2B DS S 3 X-Ray Off position0019 xx2C SL S 3 number of triggers0019 xx2E DS S 3 angle of first view0019 xx2F DS S 3 trigger frequency0019 xx39 SS S 3 scan FOV type0019 xx40 SS S 3 stat recon flag0019 xx41 SS S 3 compute type0019 xx42 SS S 3 segment number


51

0019 xx43 SS S 3 total segments requested0019 xx44 DS S 3 interscan delay0019 xx47 SS S 3 view compression factor0019 xx4A SS S 3 total no. of ref channels0019 xx4B SL S 3 data size for scan data0019 xx52 SS S 3 recon post proc. flag0019 xx57 SS S 3 CT water number0019 xx58 SS S 3 CT bone number0019 xx5E SL S 3 number of channels (1...512)0019 xx5F SL S 3 increment between channels0019 xx60 SL S 3 starting view0019 xx61 SL S 3 number of views0019 xx62 SL S 3 increment between views0019 xx6A SS S 3 dependant on #views processed0019 xx6B SS S 3 field of view in detector cells0019 xx70 SS S 3 value of back projection button0019 xx71 SS S 3 set if fatq estimates were used0019 xx72 DS S 3 Z chan avg over views0019 xx73 DS S 3 avg of left ref chans over views0019 xx74 DS S 3 max left chan over views0019 xx75 DS S 3 avg of right ref chans over views0019 xx76 DS S 3 max right chan over views0019 xxDA SS S 3 reference channel used0019 xxDB DS S 3 back projector coefficient0019 xxDC SS S 3 primary spped correction used0019 xxDD SS S 3 overrange correction used0019 xxDE DS S 3 dynamic Z alpha value

0021 00xx LO S 3 Private Creator Identification (GEMS_RELA_01)0021 xx03 SS S 3 Series from which Prescribed0021 xx05 SH S 3 Genesis Version - now0021 xx07 UL S 3 Series Record checksum0021 xx18 SH S 3 Genesis version - Now0021 xx19 UL S 3 Acqrecon record checksum0021 xx37 SS S 3 Screen Format0021 xx4A LO S 3 anatomical reference for scout0021 xx90 SS S 3 tube focal spot position0021 xx91 SS S 3 biopsy position0021 xx92 FL S 3 biopsy T location0021 xx93 FL S 3 biopsy ref location

0023 00xx LO S 3 Private Creator Identification (GEMS_STDY_01)0023 xx70 FD S 3 Start time(secs) in first axial0023 xx74 SL S 3 No. of updates to header0023 xx7D SS S 3 indicates if the study has complete info (DICOM/genesis)

0025 00xx LO S 3 Private Creator Identification (GEMS_SERS_01)0025 xx06 SS S 3 Last pulse sequence used0025 xx07 SL S 3 Images in Series0025 xx10 SL S 3 Landmark Counter0025 xx11 SS S 3 Number of Acquisitions0025 xx17 SL S 3 Series Complete Flag0025 xx18 SL S 3 Number of images archived0025 xx19 SL S 3 Last image number used


52

0025 xx1A SH S 3 Primary Receiver Suite and Host

0027 00xx LO S 3 Private Creator Identification (GEMS_IMAG_01)0027 xx06 SL S 3 Image archive flag0027 xx10 SS S 3 Scout Type0027 xx1C SL S 3 vma mamp0027 xx1D SS S 3 vma phase0027 xx1E SL S 3 vma mod0027 xx1F SL S 3 vma clip0027 xx20 SS S 3 smart scan ON/OFF flag0027 xx30 SH S 3 Foreign Image Revision0027 xx35 SS S 3 Plane Type0027 xx40 SH S 3 RAS letter of image location0027 xx41 FL S 3 Image location0027 xx42 FL S 3 Center R coord of plane image0027 xx43 FL S 3 Center A coord of plane image0027 xx44 FL S 3 Center S coord of plane image0027 xx45 FL S 3 Normal R coord0027 xx46 FL S 3 Normal A coord0027 xx47 FL S 3 Normal S coord0027 xx48 FL S 3 R Coord of Top Right Corner0027 xx49 FL S 3 A Coord of Top Right Corner0027 xx4A FL S 3 S Coord of Top Right Corner0027 xx4B FL S 3 R Coord of Bottom Right Corner0027 xx4C FL S 3 A Coord of Bottom Right Corner0027 xx4D FL S 3 S Coord of Bottom Right Corner0027 xx50 FL S 3 table start location0027 xx51 FL S 3 table end location0027 xx52 SH S 3 RAS letter for side of image0027 xx53 SH S 3 RAS letter for anterior/posterior0027 xx54 SH S 3 RAS letter for scout start loc0027 xx55 SH S 3 RAS letter for scout end loc

0029 00xx LO S 3 Private Creator Identification (GEMS_IMPS_01)0029 xx04 SL S 3 Lower range of Pixels10029 xx05 DS S 3 Lower range of Pixels10029 xx06 DS S 3 Lower range of Pixels10029 xx07 SL S 3 Lower range of Pixels10029 xx08 SH S 3 Lower range of Pixels10029 xx09 SH S 3 Lower range of Pixels10029 xx0A SS S 3 Lower range of Pixels10029 xx26 SS S 3 version of the hdr struct0029 xx34 SL S 3 advantage comp. overflow

0043 00xx LO S 3 Private Creator Identification (GEMS_PARM_01)0043 xx10 US S 3 window value0043 xx11 US S 3 total input views0043 xx12 SS 3 3 X-Ray chain0043 xx13 SS 5 3 decon kernel parameters0043 xx14 SS 3 3 calibration parameters0043 xx15 SS 3 3 total output views0043 xx16 SS 5 3 number of overranges0043 xx17 DS S 3 IBH image scale factors0043 xx18 DS 3 3 BBH coefficients


53

0043 xx19 SS S 3 number of BBH chains to blend0043 xx1A SL S 3 starting channel number0043 xx1B SS S 3 Ppscan parameters0043 xx1C SS S 3 GE image integrity0043 xx1D SS S 3 Level value0043 xx1E DS S 3 delta start time0043 xx1F SL S 3 max overranges in a view0043 xx20 DS S 3 avg overranges all views0043 xx21 SS S 3 corrected after glow terms0043 xx25 SS 6 3 reference channels0043 xx26 US 6 3 no views ref chans blocked0043 xx27 SH S 3 scan pitch ratio0043 xx28 OB S 3 Unique image iden0043 xx29 OB S 3 Histogram tables0043 xx2A OB S 3 User defined data0043 xx2B SS 4 3 Private Scan Options0043 xx31 DS 2 3 RA cord of target recon centre0043 xx40 FL 4 3 trigger on position0043 xx41 FL 4 3 degree of rotation0043 xx42 SL 4 3 DAS trigger source0043 xx43 SL 4 3 DAS fpa gain0043 xx44 SL 4 3 DAS output source0043 xx45 SL 4 3 DAS ad input0043 xx46 SL 4 3 DAS cal mode0043 xx47 SL 4 3 DAS cal frequency0043 xx48 SL 4 3 DAS reg xm0043 xx49 SL 4 3 DAS auto zero0043 xx4A SS 4 3 starting channel of view0043 xx4B SL 4 3 DAS xm pattern0043 xx4C SS 4 3 TGGC trigger mode0043 xx4D FL 4 3 start scan to Xray on delay0043 xx4E FL 4 3 duration of xray on

B.2 MR Image IOD Private Data Elements Definition;;Grp Elm VR VM Type Definition;0009 00xx LO S 3 Private Creator Identification (GEMS_IDEN_01)0009 xx01 LO S 3 full fidelity0009 xx02 SH S 3 suite id0009 xx04 SH S 3 product id0009 xx27 SL S 3 image actual date0009 xx30 SH S 3 service id0009 xx31 SH S 3 mobile location number0009 xxE3 UI S 3 equipment UID0009 xxE6 SH S 3 Genesis Version - now0009 xxE7 UL S 3 Exam Record checksum0009 xxE9 SL S 3 Actual series data time stamp

0011 00xx LO S 3 Private Creator Identification (GEMS_PATI_01)0011 xx10 SS S 3 Patient Status

0019 00xx LO S 3 Private Creator Identification (GEMS_ACQU_01)0019 xx0F DS S 3 Horiz. frame of ref.


54

0019 xx11 SS S 3 series contrast0019 xx12 SS S 3 last pseq0019 xx17 SS S 3 series plane0019 xx18 LO S 3 first scan ras0019 xx19 DS S 3 first scan location0019 xx1A LO S 3 last scan ras0019 xx1B DS S 3 last scan loc0019 xx1E DS S 3 display field of view0019 xx5A FL S 3 Acquisition Duration0019 xx7D DS S 3 Second echo0019 xx7E SS S 3 number of echos0019 xx7F DS S 3 table delta0019 xx81 SS S 3 contiguous0019 xx84 DS S 3 peak SAR0019 xx85 SS S 3 monitor SAR0019 xx87 DS S 3 Cardiac repetition time0019 xx88 SS S 3 images per cardiac cycle0019 xx8A SS S 3 actual receive gain analog0019 xx8B SS S 3 actual receive gain digital0019 xx8D DS S 3 delay after trigger0019 xx8F SS S 3 swappf0019 xx90 SS S 3 Pause Interval0019 xx91 DS S 3 Pulse Time0019 xx92 SL S 3 Slice offset on freq axis0019 xx93 DS S 3 Center Frequency0019 xx94 SS S 3 Transmit Gain0019 xx95 SS S 3 analog receiver gain0019 xx96 SS S 3 digital receiver gain0019 xx97 SL S 3 Bitmap defining CVs0019 xx98 SS S 3 Center freq. Method0019 xx9B SS S 3 Pulse seq. mode0019 xx9C LO S 3 pulse seq. name0019 xx9D DT S 3 pulse seq. date0019 xx9E LO S 3 internal pulse seq. name0019 xx9F SS S 3 Transmitting coil0019 xxA0 SS S 3 Surface Coil Type0019 xxA1 SS S 3 Extremity Coil flag0019 xxA2 SL S 3 raw data run number0019 xxA3 UL S 3 Calibrated Field strength0019 xxA4 SS S 3 SAT fat/water/bone0019 xxA5 DS S 3 receive bandwidth0019 xxA7 DS S 3 user data0019 xxA8 DS S 3 user data0019 xxA9 DS S 3 user data0019 xxAA DS S 3 user data0019 xxAB DS S 3 user data0019 xxAC DS S 3 user data0019 xxAD DS S 3 user data0019 xxAE DS S 3 user data0019 xxAF DS S 3 user data0019 xxB0 DS S 3 user data0019 xxB1 DS S 3 user data0019 xxB2 DS S 3 user data0019 xxB3 DS S 3 user data


55

0019 xxB4 DS S 3 user data0019 xxB5 DS S 3 user data0019 xxB6 DS S 3 user data0019 xxB7 DS S 3 user data0019 xxB8 DS S 3 user data0019 xxB9 DS S 3 user data0019 xxBA DS S 3 user data0019 xxBB DS S 3 user data0019 xxBC DS S 3 user data0019 xxBD DS S 3 user data0019 xxBE DS S 3 projection angle0019 xxC0 SS S 3 saturation planes0019 xxC1 SS S 3 surface coil intensity0019 xxC2 SS S 3 SAT location R0019 xxC3 SS S 3 SAT location L0019 xxC4 SS S 3 SAT location A0019 xxC5 SS S 3 SAT location P0019 xxC6 SS S 3 SAT location H0019 xxC7 SS S 3 SAT location F0019 xxC8 SS S 3 SAT thickness R/L0019 xxC9 SS S 3 SAT thickness A/P0019 xxCA SS S 3 SAT thickness H/F0019 xxCB SS S 3 prescribed flow axis0019 xxCC SS S 3 velocity encoding0019 xxCD SS S 3 thickness disclaimer0019 xxCE SS S 3 prescan type0019 xxCF SS S 3 prescan status0019 xxD0 SH S 3 raw data type0019 xxD2 SS S 3 Projection Algorithm0019 xxD3 SH S 3 projection algorithm0019 xxD5 SS S 3 fractional echo0019 xxD6 SS S 3 prep pulse0019 xxD7 SS S 3 cardiac phases0019 xxD8 SS S 3 variable echoflag0019 xxD9 DS S 3 concatenated SAT0019 xxDF DS S 3 user data0019 xxE0 DS S 3 user data0019 xxE2 DS S 3 Velocity Encode Scale0019 xxF2 SS S 3 fast phases0019 xxF9 DS S 3 transmission gain

0021 00xx LO S 3 Private Creator Identification (GEMS_RELA_01)0021 xx03 SS S 3 Series from which Prescribed0021 xx05 SH S 3 Genesis Version - now0021 xx07 UL S 3 Series Record checksum0021 xx18 SH S 3 Genesis version - Now0021 xx19 UL S 3 Acq recon record checksum0021 xx20 DS S 3 Table start location0021 xx35 SS S 3 Series from which prescribed0021 xx36 SS S 3 image from which prescribed0021 xx37 SS S 3 Screen Format0021 xx4F SS S 3 locations in acquisition0021 xx50 SS S 3 graphically prescribed0021 xx51 DS S 3 rotation from source x rot


56

0021 xx52 DS S 3 rotation from source y rot0021 xx53 DS S 3 rotation from source z rot0021 xx54 SH 3 3 image position0021 xx55 SH 6 3 image orientation0021 xx56 SL S 3 integer slop0021 xx57 SL S 3 integer slop0021 xx58 SL S 3 integer slop0021 xx59 SL S 3 integer slop0021 xx5A SL S 3 integer slop0021 xx5B DS S 3 float slop0021 xx5C DS S 3 float slop0021 xx5D DS S 3 float slop0021 xx5E DS S 3 float slop0021 xx5F DS S 3 float slop0021 xx81 DS S 3 auto window/level alpha0021 xx82 DS S 3 auto window/level beta0021 xx83 DS S 3 auto window/level window0021 xx84 DS S 3 to window/level level

0023 00xx LO S 3 Private Creator Identification (GEMS_STDY_01)0023 xx01 SL S 3 Number of series in Study0023 xx02 SL S 3 Number of unarchived Series0023 xx10 SS S 3 reference image field0023 xx50 SS S 3 summary image0023 xx70 FD S 3 Start time(secs) in first axial0023 xx74 SL S 3 No. of updates to header0023 xx7D SS S 3 indicates if study has complete info (DICOM/genesis)

0025 00xx LO S 3 Private Creator Identification (GEMS_SERS_01)0025 xx06 SS S 3 Last pulse sequence used0025 xx07 SL S 3 Images in Series0025 xx10 SL S 3 Landmark Counter0025 xx11 SS S 3 Number of Acquisitions0025 xx14 SL S 3 indicates no. of updates to header0025 xx17 SL S 3 Series Complete Flag0025 xx18 SL S 3 Number of images archived0025 xx19 SL S 3 Last image number used0025 xx1A SH S 3 Primary Receiver Suite and Host

0027 00xx LO S 3 Private Creator Identification (GEMS_IMAG_01)0027 xx06 SL S 3 Image archive flag0027 xx10 SS S 3 Scout Type0027 xx30 SH S 3 Foreign Image Revision0027 xx31 SS S 3 Imaging Mode0027 xx32 SS S 3 Pulse Sequence0027 xx33 SL S 3 Imaging Options0027 xx35 SS S 3 Plane Type0027 xx36 SL S 3 Oblique Plane0027 xx40 SH S 3 RAS letter of image location0027 xx41 FL S 3 Image location0027 xx42 FL S 3 Center R coord of plane image0027 xx43 FL S 3 Center A coord of plane image0027 xx44 FL S 3 Center S coord of plane image0027 xx45 FL S 3 Normal R coord


57

0027 xx46 FL S 3 Normal A coord0027 xx47 FL S 3 Normal S coord0027 xx48 FL S 3 R Coord of Top Right Corner0027 xx49 FL S 3 A Coord of Top Right Corner0027 xx4A FL S 3 S Coord of Top Right Corner0027 xx4B FL S 3 R Coord of Bottom Right Corner0027 xx4C FL S 3 A Coord of Bottom Right Corner0027 xx4D FL S 3 S Coord of Bottom Right Corner0027 xx60 FL S 3 Image dimension - X0027 xx61 FL S 3 Image dimension - Y0027 xx62 FL S 3 Number of Excitations

0029 00xx LO S 3 Private Creator Identification (GEMS_IMPS_01)0029 xx15 SL S 3 Lower range of Pixels10029 xx16 SL S 3 Lower range of Pixels10029 xx17 SL S 3 Lower range of Pixels20029 xx18 SL S 3 Upper range of Pixels20029 xx1A SL S 3 Len of tot hdr in bytes0029 xx26 SS S 3 version of the hdr struct0029 xx34 SL S 3 advantage comp. overflow0029 xx35 SL S 3 advantage comp. underflow

0043 00xx LO S 3 Private Creator Identification (GEMS_PARM_01)0043 xx01 SS S 3 bitmap of prescan options0043 xx02 SS S 3 gradient offset in X0043 xx03 SS S 3 gradient offset in Y0043 xx04 SS S 3 gradient offset in Z0043 xx05 SS S 3 image is original or unoriginal0043 xx06 SS S 3 number of EPI shots0043 xx07 SS S 3 views per segment0043 xx08 SS S 3 respiratory rate,bpm0043 xx09 SS S 3 respiratory trigger point0043 xx0A SS S 3 type of receiver used0043 xx0B DS S 3 peak rate of change of gradient field0043 xx0C DS S 3 limits in units of percent0043 xx0D DS S 3 PSD estimated limit0043 xx0E DS S 3 PSD estimated limit in tesla per second0043 xx0F DS S 3 saravghead0043 xx10 US S 3 Window value0043 xx1C SS S 3 GE image integrity0043 xx1D SS S 3 Level value0043 xx28 OB S 3 Unique image iden0043 xx29 OB S 3 Histogram tables0043 xx2A OB S 3 User defined data0043 xx2B SS 4 3 Private Scan Options0043 xx2C SS S 3 Effective echo spacing0043 xx2D SH S 3 String slop field 10043 xx2E SH S 3 String slop field 20043 xx2F SS S 3 Raw data type0043 xx30 SS S 3 Raw data type0043 xx31 DS 2 3 RA cord of target recon centre0043 xx32 SS S 3 Raw data type0043 xx33 FL S 3 neg_scanspacing0043 xx34 IS S 3 Offset Frequency


58

0043 xx35 UL S 3 User_usage_tag0043 xx36 UL S 3 User_fill_map_MSW0043 xx37 UL S 3 User_fill_map_LSW0043 xx38 FL 24 3 User25...User480043 xx39 IS 4 3 slop_int_6... slop_int_9


59

Appendix C DICOMDIR Directory Information

C.1 DICOMDIR Directory Information

Enclosed here is a listing of only the optional (conditional) modules and attributes used by this implementationin the DICOMDIR definition.

C.1.1 Basic Directory IOD DefinitionModule Reference Usage NotesDirectory Information B.X.3.2.1 (DICOM

PS3.10)U

C.1.2 Directory Information ModuleAttribute Name Tag Type NotesOffset of the NextDirectory Record

(0004,1400) 1C

Record In-use Flag (0004,1410) 1COffset of ReferencedLower-Level DirectoryEntity

(0004,1420) 1C

Directory Record Type (0004,1430) 1C PATIENT, STUDY,SERIES and IMAGE

Referenced File ID (0004,1500) 1C Present only in IMAGEDirectory Record

Referenced SOP ClassUID in file

(0004,1510) 1C Present only in IMAGEDirectory Record

Referenced SOPInstance UID in File


Referenced TransferSyntax UID in File


C.1.3 Directory Record Selection Keys

As indicated in table C.1.2, the PRI-CTMR-MOD12 application profile will have only the Patient, Study, Seriesand Image directory record types. Given below are the list of attributes supported under each of thesedirectories.

C.1.3.1 Patient KeysAttribute Name Tag Type NotesSpecific Character Set (0008,0005) 1C ISO IR 100

C.1.3.2 Study KeysAttribute Name Tag Type NotesSpecific Character Set (0008,0005) 1C ISO IR 100

C.1.3.3 Series KeysAttribute Name Tag Type NotesSpecific Character Set (0008,0005) 1C ISO IR 100Image Type (0008,0008) 3


60

(0008,0070) 3(0008,103E) 3(0008,1090) 3

C.1.3.4 Image KeysAttribute Name Tag Type NotesSpecific Character Set (0008,0005) 1C ISO IR 100SOP Instance UID (0008,0018) 3Sequence Variant (0018,0021) 3Slice Thickness (0018,0050) 3Repetition Time (0018,0080) 3Echo Time (0018,0081) 3Inversion Time (0018,0082) 3Number of Averages (0018,0083) 3Echo Number (0018,0086) 3Spacing Between Slices (0018,0088) 3Data CollectionDiameter

(0018,0090) 3

Contrast/Bolus Route (0018,1040) 3Trigger Time (0018,1060) 3ReconstructionDiameter

(0018,1100) 3

Gantry/Detector Tilt (0018,1120) 3Convolution Kernel (0018,1210) 3Flip Angle (0018,1314) 3Image Number (0020,0013) 3Image Position(Patient)

(0020,0032) 3

Image Orientation(Patient)

(0020,0037) 3

Slice Location (0020,1041) 3Rows (0028,0010) 3Columns (0028,0011) 3Pixel Spacing (0028,0030) 3

CT SERVICE ENGINEERING, NB–918P.O. BOX 414MILWAUKEE WISCONSIN 53201–0414 U.S.A.Fax: (414) 785–5874

direction # 2162114-100 rev. 0

Documents