philips medical systems dicom conformance statement r6.2

PhiliMedSyst

Philips Medical Systems

DICOM Conformance Statement

Gyroscan NT R6.2 & R6.1 & R5.6 & R4.6

Document Number 4522 131 70041 17 September 1999

© Copyright Philips Medical Systems Nederland B.V. 1999

All rights reserved

psicalems

� PHILIPS

Page ii DICOM Conformance Statement 4522 131 70041 - 17 Sep 99

Issued by:Philips Medical Systems Nederland B.V.Integrated Clinical Solutions, Marketing & CommunicationsBuilding QP-2129P.O. Box 10.0005680 DA Best The NetherlandsTel.: +31 40 2762818Fax.: +31 40 2762673email: [email protected] (with the latest versions of Conformance Statements and other DICOM information):

http://www.philips.com/ms/solution/connect ftp://ftp.philips.com/pub/ms/dicom/Conformance_Stmnts

All rights reserved

© Philips Medical Systems Nederland B.V. 1999

4522 131 70041 - 17 Sep 99 DICOM Conformance Statement Page iii

Table of Contents

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1 Scope and field of application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.2 Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.3 Contents and structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.4 Used definitions, terms and abbreviations . . . . . . . . . . . . . . . . . . . . . . 11.5 References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.6 Important note to the reader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.7 General Acronyms and Abbreviations. . . . . . . . . . . . . . . . . . . . . . . . . 32 Implementation model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42.1 Application Data Flow Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42.2 Functional definition of Application Entities . . . . . . . . . . . . . . . . . . . . 52.3 Sequencing of Real World Activities . . . . . . . . . . . . . . . . . . . . . . . . . . 53 AE Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63.1 Gyroscan DICOM Image Export AE Specification . . . . . . . . . . . . . . . 63.1.1 Association Establishment Policies . . . . . . . . . . . . . . . . . . . . . . . . . 63.1.2 Association Initiation Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73.1.3 Association Acceptance Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83.2 Gyroscan DICOM Worklist AE Specification . . . . . . . . . . . . . . . . . . . 93.2.1 Association Establishment Policies . . . . . . . . . . . . . . . . . . . . . . . . . 93.2.2 Association Initiation Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103.2.3 Association Acceptance Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Communication Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124.1 Supported Communication Stacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124.2 TCP/IP Stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124.2.1 Physical Media Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 Extensions/Specializations/Privatizations . . . . . . . . . . . . . . . . . . . . . . . 126 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136.1 AE Title/Presentation Address mapping . . . . . . . . . . . . . . . . . . . . . . . 136.1.1 Local AE Titles and Presentation Addresses . . . . . . . . . . . . . . . . . . 136.1.2 Remote AE Titles and Presentation Addresses . . . . . . . . . . . . . . . . 136.2 Configurable parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 Support of Extended Character Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 Overview applied MR Image IOD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 Overview applied Modality Worklist Information Model . . . . . . . . . . 2210 Remarks, Implementation restrictions and choices. . . . . . . . . . . . . . . . 24

All rights reserved


Page iv DICOM Conformance Statement 4522 131 70041 - 17 Sep 99

All rights reserved


4522 131 70041 - 17 Sep 99 DICOM Conformance Statement Page 1 of 24

Introduction

con-

and

ement.

1 Introduction

This section provides general information about the scope, intended audience and contents ofthis Conformance Statement and how to use it.

1.1 Scope and field of applicationThe scope of this DICOM Conformance Statement is to facilitate data exchange betweenequipment of Philips Medical Systems and with equipment of other vendors. This documentspecifies the compliance to the DICOM standard, formally called the NEMA PS 3.X-1996standards. It contains a short description of the applications involved and provides technicalinformation about the data exchange capabilities of the equipment. The main elements describ-ing these capabilities are: the supported DICOM Service Object Pair (SOP) Classes, Roles,Information Object Definitions (IOD), Service Elements and Transfer Syntaxes.

The field of application is the integration of the Philips Medical Systems equipment into anenvironment of medical devices. This Conformance Statement should be read in conjunction with the DICOM standard and itsaddenda. The conformance to the DICOM standard is a key element of the Inturis Program(see [INTURIS]).

1.2 Intended audienceThis Conformance Statement is intended for:• (potential) clients,• marketing staff interested in data exchange functionality,• system integrators and Customer Support Engineers of medical equipment,• software engineers implementing DICOM interfaces.

It is assumed that the reader is familiar with the DICOM standard.

1.3 Contents and structure The DICOM Conformance Statement is contained in section 2 through 7 and follows thetents and structuring requirements of DICOM PS 3.2-1996.Additionally, the sections following 7 (if present) specify the details of the applied IODsService Elements.

1.4 Used definitions, terms and abbreviationsDICOM definitions, terms and abbreviations are used throughout this Conformance StatFor a description of these, see NEMA PS 3.3-1996.The word Philips in this document refers to Philips Medical Systems.

1.5 References[DICOM] The Digital Imaging and Communications in Medicine (DICOM) standard:

NEMA PS 3.X (X refers to the part 1 - 13)National Electrical Manufacturers Association (NEMA) Publication Sales1300 N. 17th Street, Suite 1847

All rights reserved


of 24 DICOM Conformance Statement 4522 131 70041 - 17 Sep 99

Introduction

he fol-

spec-

t suite

nd ton anddo so,y., alsoOM

twork-

Rosslyn, Va. 22209, United States of America

[INTURIS] Philips Inturis ProgramIntegrated Clinical SolutionsPhilips Medical Systems Nederland B.V. (see address at page ii)

1.6 Important note to the readerThis Conformance Statement by itself does not guarantee successful interoperability of Philipsequipment with non-Philips equipment. The user (or user’s agent) should be aware of tlowing issues:

• InteroperabilityInteroperability refers to the ability of application functions, distributed over two or moresystems, to work successfully together. The integration of medical devices into a networkedenvironment may require application functions that are not specified within the scope ofDICOM. Consequently, using only the information provided by this Conformance State-ment does not guarantee interoperability of Philips equipment with non-Philips equipment. It is the user’s responsibility to analyse thoroughly the application requirements and toify a solution that integrates Philips equipment with non-Philips equipment.

• ValidationPhilips equipment has been carefully tested to assure that the actual implementation of theDICOM interface corresponds with this Conformance Statement.Where Philips equipment is linked to non-Philips equipment, the first step is to compare therelevant Conformance Statements. If the Conformance Statements indicate that successfulinformation exchange should be possible, additional validation tests will be necessary toensure the functionality, performance, accuracy and stability of image and image relateddata. It is the responsibility of the user (or user’s agent) to specify the appropriate tesand to carry out the additional validation tests.

• New versions of the DICOM StandardThe DICOM Standard will evolve in future to meet the user’s growing requirements aincorporate new features and technologies. Philips is actively involved in this evolutioplans to adapt its equipment to future versions of the DICOM Standard. In order to Philips reserves the right to make changes to its products or to discontinue its deliverThe user should ensure that any non-Philips provider linking to Philips equipmentadapts to future versions of the DICOM Standard. If not, the incorporation of DICenhancements into Philips equipment may lead to loss of connectivity (in case of neing) and incompatibility (in case of media).

All rights reserved



Introduction

1.7 General Acronyms and Abbreviations.The following acronyms and abbreviations are used in the document.• ACC American College of Cardiology• AE Application Entity• ACR American College of Radiology• ANSI American National Standard Institute• BOT Basic Offset Table• CD-R CD Recordable• CD-M CD Medical• DCI Digital Cardio Imaging• DCR Dynamic Cardio Review• DICOM Digital Imaging and Communication in Medicine• DIMSE DICOM Message Service Element• DIMSE-C DICOM Message Service Element-Composite• DIMSE-N DICOM Message Service Element-Normalized• ELE Explicit VR Little Endian• EBE Explicit VR Big Endian• FSC File Set Creator• GUI Graphic User Interface• HIS Hospital Information System• HL7 Health Level Seven• ILE Implicit VR Little Endian• IOD Information Object Definition• ISIS Information System - Imaging System• NEMA National Electrical Manufacturers Association• PDU Protocol Data Unit• RIS Radiology Information System• RWA Real World Activity• SC Secondary Capture• SCM Study Component Management• SCP Service Class Provider• SCU Service Class User• SOP Service Object Pair• TCP/IP Transmission Control Protocol/Internet protocol• UID Unique Identifier• WLM Worklist Management

All rights reserved



Implementation model

data

tion

tation

r. The imagesion is

Theseersec- MPR, of the

am-mina-

sed as

2 Implementation model

The Gyroscan NT system of Philips Medical Systems is an MR image generating system. Thesystem contains:• a DICOM Image Export function to transfer DICOM MR images and image related

from Gyroscan to a remote system,• a DICOM Radiology Information System (RIS) interface to retrieve the next examina

from the worklist to be examined.These DICOM functions are described in this document.

2.1 Application Data Flow DiagramGyroscan behaves as a system with two Application Entities (AE). The related ImplemenModel is shown in Figure 2-1 on page 5.

The Gyroscan DICOM Image Export function can be activated by the Gyroscan operatoimages to be sent are selected from one or more examinations. At export request thewill be converted into DICOM format and sent out to a remote destination. This destinatpreviously selected by the operator from the user interface. The images transferred are instances of the DICOM Magnetic Resonance (MR) Class.images are intended for viewing purposes, including planscan viewing by calculating inttions with reference images. Not included is graphics (annotations). Post-processing likeMIP, 3D reconstruction and rendering may be possible, depending on the capabilitiesworkstation receiving the MR images.

The Gyroscan DICOM Modality Worklist function makes it possible to retrieve the next exination to be performed. This worklist is normally registered in a RIS and the current exation for the Gyroscan should be selected at the RIS side. A part of the received examination data will be shown on the user interface and is uimage attribute values when exporting or printing these images.

All rights reserved



Implementation model

2.2 Functional definition of Application EntitiesThe Gyroscan DICOM Image Export AE acts as a Service Class User (SCU) of the StorageService Class. When the export is initiated, the AE will open an association to the remote sys-tem. The selected images and related image data are converted into a DICOM message to besent to the remote system.

The Gyroscan DICOM Worklist AE acts as a Service Class User (SCU) of the Basic WorklistManagement Service Class. After requesting for the next examination, it will receive theexamination data from the RIS and displays (a part of) this data on the user interface and storesthis data in resulting images of the examination.

Gyroscan does not support Service Classes as Service Class Provider (SCP).

2.3 Sequencing of Real World ActivitiesWhen a RIS interface is configured, the Next Patients Examination data can be requested fromthe worklist.The next examination must be defined at the RIS side. After import of patient data, missingdata can be added and erroneous data can be modified by the user.

Now the examination scan(s) are performed. After reconstruction the resulting images can beexported via DICOM. The required DICOM node can be selected by the operator from theinternal node list.

Request fornext exami-nation(3.2.2.1)

ImageExportRequest(3.1.2.1)

Register &Select Examination(at RIS)

Local Remote

DICOM Standard Interface

Figure 2-1: The Gyroscan DICOM Implementation Model (with references to the related sections)

StoreImage

Gyroscan DICOM

Worklist AE(section 3.2)

Gyroscan DICOM Image

Export AE (section 3.1)

All rights reserved



AE Specifications

3 AE Specifications

Gyroscan contains two independent Application Entities.

3.1 Gyroscan DICOM Image Export AE SpecificationThe Gyroscan DICOM Image Export Application Entity provides Standard Conformance tothe following DICOM V3.0 SOP Classes as an SCU:

The Gyroscan DICOM Image Export Application Entity does not support DICOM V3.0 SOPClasses as an SCP.

3.1.1 Association Establishment Policies

3.1.1.1 GeneralGyroscan has a configurable maximum PDU size. The Maximum PDU might be 0 to identifyno maximum size but any size during transfer. See “Configurable parameters” on page 13.

3.1.1.2 Number of AssociationsGyroscan will attempt to establish one association at a time.

3.1.1.3 Asynchronous NatureGyroscan does not support asynchronous operations and will not perform asynchronous win-dow negotiation.

3.1.1.4 Implementation Identifying InformationThe Implementation Class UID is: “1.3.46.670589.11.0.0.11.4.1.1”The implementation version name is: “MR STORE 1.1”

Table 3-1: Supported SOP Classes by the Gyroscan DICOM Image Export AE as SCU

SOP Class Name UID

MR Image Storage - STORE 1.2.840.10008.5.1.4.1.1.4

All rights reserved



AE Specifications

tatus

wn.

ypes and

3.1.2 Association Initiation PolicyGyroscan initiates associations as a result of one Real-World activity: the Gyroscan operatorrequests for Image Export, i.e. send the selected images from the Gyroscan to a remote system.

3.1.2.1 Image Export Request

3.1.2.1.1 Associated Real-World Activity

After selection of a remote station and after selection of one of more images, these images willbe sent when initiating the Export command. Gyroscan initiates one association to the selectedremote entity and uses it to send the selected images via C-STORE requests (and receives theassociated C-STORE Responses). The association is released by Gyroscan after successful transfer of the images or when anerror occurs.

3.1.2.1.2 Proposed Presentation Contexts

Gyroscan will propose the following presentation contexts:

3.1.2.1.3 C-STORE SCU Conformance

Gyroscan provides standard conformance.

Gyroscan has the following behaviour on successful (with or without warnings) and unsuc-cessful transfer of images:• Success (return status 0000)

The successful transfer is indicated on the console: ‘Done’.• Refused (return status A7xx), Error (return status A9xx or Cxxx) and Warning (return s

B00x)The failed transfer is indicated on the console: ‘Network Error’. The reason is not sho

While busy with transfer, the status Busy is shown on the Gyroscan console.

Table 3-3 lists the applied Conditional (DICOM Type 1C and 2C) and Optional (DICOM T3) attributes of the standard MR Image IOD. A detailed overview of all applied attribute

Table 3-2: Proposed Presentation Contexts for Image Export Request

Presentation Context table

Abstract Syntax Transfer SyntaxRole

ExtendedNegotiation

Name UID Name List UID List

MR Image Storage -STORE

1.2.840.10008.5.1.4.1.1.4

ILE 1.2.840.10008.1.2 SCU None


1.2.840.10008.5.1.4.1.1.4

ELI 1.2.840.10008.1.2.1 SCU None


1.2.840.10008.5.1.4.1.1.4

EBE 1.2.840.10008.1.2.2 SCU None

All rights reserved



AE Specifications

additional notes are given in section 8 on page 14.

3.1.3 Association Acceptance PolicyThe Gyroscan Application Entity does not accept associations.

Table 3-3: Applied Conditional and Optional Attributes of the MR Image IOD

Information Entity

Module Conditional Attributes Optional Attributes

Patient Patient - -

Study General Study - Study Description

Patient Study - Patient Weight

Study Classification

Series General Series Patient Position Series Date, Series Time, Series Descrip-tion, Protocol Name

Frame of Reference

Frame of Reference - -

Equipment General Equipment - Institution Name, Manufacturer’s Model Name, Device Serial Number, Software Version(s)

Image General Image Image Date, Image Time Referenced Image Sequence, Acquisition Number, Image Comments.

Image Plane - -

Image Pixel - -

MR Image Repetition Time, Inversion Time, Trigger Time

Number of Averages, Imaging Fre-quency, Imaged Nucleus, Echo Number(s), Magnetic Field Strength, Spacing Between Slices, Number of Phase Encoding Steps, Percent Sampling, Percent Phase Field of View, Low R-R Value, High R-R Value, Intervals Acquired, Intervals Rejected, Heart Rate, Receiving Coil, Transmitting Coil, Phase Encoding Direction, Flip Angle, Temporal Position Identifier.

Modality LUT Rescale Intercept, Rescale Slope, rescale Type.

VOI LUT Window Width Window Center

SOP Common Specific Character Set Instance Creation Date, Instance Creation Time, Instance Creator UID

All rights reserved



AE Specifications

3.2 Gyroscan DICOM Worklist AE SpecificationThe Gyroscan DICOM Worklist Application Entity provides Standard Extended Conformanceto the following DICOM 3.0 SOP class as an SCU:

The Gyroscan DICOM Worklist Application Entity does not support DICOM V3.0 SOPClasses as an SCP.

3.2.1 Association Establishment Policies

3.2.1.1 GeneralGyroscan has a configurable maximum PDU size.

3.2.1.2 Number of AssociationsGyroscan will attempt to establish one association at a time.

3.2.1.3 Asynchronous NatureGyroscan does not support asynchronous operations and will not perform asynchronous win-dow negotiation.

3.2.1.4 Implementation Identifying InformationThe Implementation Class UID is: “1.3.46.670589.11.0.0.51.4.1.1The implementation version name is: “MR WLM 1.1”

Table 3-4: Supported SOP class by the Gyroscan DICOM Worklist AE as SCU

SOP class Name UID

Modality Worklist Information Model - FIND 1.2.840.10008.5.1.4.31

All rights reserved



AE Specifications

y in

alue

ept the

3.2.2 Association Initiation PolicyGyroscan DICOM Worklist AE initiates associations as a result of one Real-World Activity:the Gyroscan NT operator requests for a new examination.

3.2.2.1 Next Examination Request

3.2.2.1.1 Associated Real-World Activity

This Gyroscan DICOM Worklist function will be accessible through the Gyroscan User Inter-face. An association will be set-up to the configured remote system (usually a RIS). After receiving the worklist the association is released.

3.2.2.1.1.1 Proposed Presentation Contexts

Gyroscan DICOM Worklist AE will propose the following presentation contexts:

3.2.2.1.1.2 SOP Specific Conformance to Modality Worklist Management

Gyroscan provides standard conformance. However, this release of Gyroscan contains someimplementation restrictions w.r.t. the use of the examination data resulting from ModalityWorklist Management, see below.

An indication of the status of the C-FIND Responses (Success, Refused, Error) is displayed onthe user interface. The “New Examination” screen on the Gyroscan console will be emptcase of an error.

Table 3-6 lists the applied optional Matching Keys in the C-FIND Requests. Single VMatching is applied.

Only the type 1 and 2 Return Key attributes (see DICOM Supplement 10) are used, excoptional and conditional Return Keys in Table 3-7.

Table 3-5: Proposed Presentation Contexts for the New Examination Request

Presentation Context table

Abstract Syntax Transfer SyntaxRole

ExtendedNegotiation

Name UID Name List UID List

Modality Worklist Infor-mation Model - FIND

1.2.840.10008.5.1.4.31

ILE 1.2.840.10008.1.2 SCU None


1.2.840.10008.5.1.4.31

ELI 1.2.840.10008.1.2.1 SCU None


1.2.840.10008.5.1.4.31

EBE 1.2.840.10008.1.2.2 SCU None

All rights reserved



AE Specifications

Section 9 on page 22 gives a detailed overview of all applied (mandatory/optional) Matchingand Return Keys and additional notes.

Important Note for this Modality Worklist implementation:

This system release expects one Worklist entry as result of a C-FIND Request. This impliesthat one Scheduled Procedure Step out of the Gyroscan worklist must be selected first on theRIS before the next examination is requested on the Gyroscan NT.When more then one Worklist entry is returned, the Gyroscan will reject these entries andissues a C-CANCEL-FIND Request as indication of a unexpected transfer by the RIS.

3.2.3 Association Acceptance PolicyThe Gyroscan DICOM Worklist AE does not accept associations.

Table 3-6: The applied optional Matching Keys

Module Applied optional Matching Keys

Scheduled Procedure Step Scheduled Procedure Step Status (present in Scheduled Procedure Step Sequence)

Table 3-7: The applied optional and conditional Return Keys

Module Applied optional Return Keys

Scheduled Procedure Step Scheduled Procedure Step Description (present in Scheduled Procedure Step Sequence)

All rights reserved



Communication Profiles

4 Communication Profiles

4.1 Supported Communication StacksGyroscan provides DICOM V3.0 TCP/IP Network Communication Support as defined in Part8 of the DICOM Standard.

4.2 TCP/IP StackGyroscan uses the TCP/IP program installed on the DEC Alpha where the Gyroscan Applica-tion Entities are running on. This is a subroutine library that is based on a Berkeley socketinterface.

4.2.1 Physical Media SupportGyroscan supports (dependent on the hardware configuration) ISO 8802-3 10BASE5 (Thick-wire), 10BASE2 (Thin-wire), 10BASE-T (Twisted-pair) and 100BASE-T (Twisted-pair)Ethernet.

5 Extensions/Specializations/Privatizations

The following Standard Extensions are applied for the MR Image Storage SOP Class. See alsothe overview of the applied MR Image IOD in section 8 on page 14.

Table 5-1: Applied Standard Extensions

Module Attribute Note

Gyroscan Series (private module)

Reconstruction Number(0021,xx01)

Identifies the applied reconstruction on acquisition data.

Study Classification Study Comments

Modality LUT Rescale Intercept Present if configured. Must be applied when viewing the image.

Rescale Slope See note Rescale Intercept above.

Rescale Type See note Rescale Intercept above.

Gyroscan Image (private module)

Chemical Shift Number(0019,xx11)

Identifies the chemical shift interval for spectro-scopic reconstruction.

Phase Number (Philips)(0019,xx12)

Identifies a phase interval of the cardiac cycle.

Slice Number0021,xx02

identifies a slice (=image plane) for an acquisition and/or a reconstruction

All rights reserved



Configuration

imum

8K,sible.

No 1,

6 Configuration

The Gyroscan system is configured by Philips engineer only.

6.1 AE Title/Presentation Address mapping

6.1.1 Local AE Titles and Presentation AddressesThe IP address and both AE Titles of the Gyroscan are configurable. Both are allowed to beequal.

6.1.2 Remote AE Titles and Presentation AddressesThe following information of remote systems (acting as Service Class Provider) must be con-figured on Gyroscan: • The AE title.

Default character Repertoire excluding control characters LF, FF, CR and ESC, max16 bytes.

• The host name and IP addresses.• The port number at which the remote system accepts association requests.

6.2 Configurable parameters• The maximum PDU size (of incoming PDUs) is configurable in steps of 1K, 2K, 4K,

32K, 16K or more e.g. 64K. In principle any value in between these values is posDefault is 16K = 16384 bytes.

• Export or do not export the Rescale attributes, see Table 5-1 on page 12.• The time-out value on waiting on the RIS Response Message of Modality Worklist.• Institution Name, Table 8-9 on page 17.• Software version, Table 8-9 on page 17.

7 Support of Extended Character Sets

Gyroscan supports Extended Character Set “ISO_IR 100” which is the Latin alphabet supplementary set.

All rights reserved



Overview applied MR Image IOD

8 Overview applied MR Image IOD

The modules selected from the MR Image IOD module table of DICOM and the modulesextended are given in the table below.

The details of these applied modules are given in the tables below. The list of possible values are given (if applicable). The situation that an attribute is present conditionally/optionally or that an attribute may contain a zero length value, is indicated too. Conditions and Defined/Enu-merated Values of DICOM 3.0 are applicable but are not shown in the tables.

Table 8-1: Applied Modules in the MR Image IOD

Information Entity Module

Patient Patient

Study General Study

Patient Study

Study Classification

Series General Series

Gyroscan Series (private module)

Frame of Reference Frame of Reference

Equipment General Equipment

Image General Image

Image Plane

Image Pixel

MR Image

Gyroscan Image (private module)

Modality LUT

VOI LUT

SOP Common

Table 8-2: MR Image Storage SOP Class - Patient Module

Attribute Name Tag Note

Patient’s Name 0010,0010 Received from RIS or entered by the operator

Patient ID 0010,0020 Received from RIS or entered by the operator (this is the Registration Number)

All rights reserved




Patient’s Birth Date 0010,0030 Received from RIS or entered by the operator

Patient’s Sex 0010,0040 Received from RIS or entered by the operatorApplied value(s): F, M, O

Table 8-3: MR Image Storage SOP Class - General Study Module


Study Date 0008,0020 Received from RIS, entered by the oper-ator or has zero length value.

Study Time 0008,0030

Accession Number 0008,0050 Received from RIS, entered by the oper-ator or has a zero length value.

Referring Physician’s Name 0008,0090 Received from RIS, entered by the oper-ator or has a zero length value.

Study Description 0008,1030 This is the Exam Name. Default value may be received from RIS (as Return Key Scheduled Procedure Step Description)

Study Instance UID 0020,000D From RIS or created dynamically at export.

Study ID 0020,0010

Table 8-4: MR Image Storage SOP Class - Patient Study Module


Patient’s Weight 0010,1030 Received from RIS or entered by the operator

Table 8-2: MR Image Storage SOP Class - Patient Module (Continued)


All rights reserved




Table 8-5: MR Image Storage SOP Class - Study Classification Module


Study Comments 0032,4000 User defined comments about the Study.

Table 8-6: MR Image Storage SOP Class - General Series Module


Series Date 0008,0021 Date of the scan or reconstruction.

Series Time 0008,0031

Modality 0008,0060 Applied value(s): MR

Series Description 0008,103E Short description of the scan.

Protocol Name 0018,1030 This is the Scan Name.

Patient Position 0018,5100 Applied value(s): FFDL, FFDR, FFP, FFS, HFDL, HFDR, HFP, HFS

Series Instance UID 0020,000E

Series Number 0020,0011 Created dynamically at export.

Table 8-7: MR Image Storage SOP Class - Gyroscan Series Module


Private Creator Group 0021 0021,00xx Value Representation = LO, Multiplicity = 1.Contains the Private Creator Identification Code.Applied value(s): PHILIPS-MR-1

Reconstruction Number 0021,xx01 Value Representation = IS, Multiplicity = 1.This is the sequence number of the reconstruc-tions (=series) for a given scan (=acquisition)

All rights reserved




Table 8-8: MR Image Storage SOP Class - Frame of Reference Module


Frame of Reference UID 0020,0052

Position Reference Indicator 0020,1040 Has a zero length value.

Table 8-9: MR Image Storage SOP Class - General Equipment Module


Manufacturer 0008,0070 For locally created images this is “Philips Medical Systems”.

Institution Name 0008,0080 “Hospital Name” name as configured on the system, for locally created images.

Manufacturer's Model Name 0008,1090 For locally created images this is “Gyro-scan NT”.

Device Serial Number 0018,1000 For locally created images this is the SRN.

Software Version(s) 0018,1020 “FOREIGN” if non-Philips

Table 8-10: MR Image Storage SOP Class - General Image Module


Image Date 0008,0023 Present if image is part of a dynamic scan.

Image Time 0008,0033 Present if image is part of a dynamic scan.

Referenced Image Sequence 0008,1140 Planscan information, a maximum of 3 earlier images on which the orientation of the current image has been defined.

> Referenced SOP Class UID 0008,1150 Uniquely identifies the referenced SOP Class.

> Referenced SOP Instance UID 0008,1155 Uniquely identifies the Referenced SOP Class.

Acquisition Number 0020,0012 This is the Scan Number.

All rights reserved




Image Number 0020,0013 Created dynamically at export.

Image Comments 0020,4000 User defined comments about the Image.

Table 8-11: MR Image Storage SOP Class - Image Plane Module


Slice Thickness 0018,0050

Image Position (Patient) 0020,0032

Image Orientation (Patient) 0020,0037

Pixel Spacing 0028,0030

Table 8-12: MR Image Storage SOP Class - Image Pixel Module


Samples per Pixel 0028,0002 Applied value(s): 1

Photometric Interpretation 0028,0004 Applied value(s): MONOCHROME2

Rows 0028,0010 This is the Reconstruction Resolution.

Columns 0028,0011 This is the Reconstruction Resolution.

Bits Allocated 0028,0100 Applied value(s): 16

Bits Stored 0028,0101 Applied value(s): 12, 8

High Bit 0028,0102 Equals Bits Stored - 1

Pixel Representation 0028,0103 Applied Value(s): 0 = unsigned integer.

Pixel Data 7FE0,0010

Table 8-10: MR Image Storage SOP Class - General Image Module (Continued)


All rights reserved




Table 8-13: MR Image Storage SOP Class - MR Image Module


Image Type 0008,0008 Applied value(s): DERIVED, ORIGI-NAL \ PRIMARY, SECONDARY \ DENSITY MAP, OTHER, PHASE MAP, T1 MAP, T2 MAP, VELOCITY MAP \ CR, DERIVED, I, M, P, R, RHO, T1, T2 \ DERIVED, FFE, IR, PCA, SE, SI, US

Scanning Sequence 0018,0020 Applied value(s): GR, IR, RM, SE

Sequence Variant 0018,0021 Applied value(s): MTC, OTHER

Scan Options 0018,0022 Applied value(s): CG, FC, FS, PER, PFP, RG

MR Acquisition Type 0018,0023 Applied value(s): 2D, 3D

Repetition Time 0018,0080

Echo Time 0018,0081

Inversion Time 0018,0082

Number of Averages 0018,0083

Imaging Frequency 0018,0084

Imaged Nucleus 0018,0085 Applied value(s): 1H, 31P

Echo Number(s) 0018,0086

Magnetic Field Strength 0018,0087

Spacing Between Slices 0018,0088 This is the center-to-center distance; do not confuse it with Slice Gap.

Number of Phase Encoding Steps 0018,0089

Echo Train Length 0018,0091 This is the Turbo Factor.

Percent Sampling 0018,0093 This is the Reduction Factor or Scan Percentage.

Percent Phase Field of View 0018,0094 This is the Rectangular FOV.

Trigger Time 0018,1060 Present for Scan Options which include triggering (e.g. CG).

Low R-R Value 0018,1081

High R-R Value 0018,1082

Intervals Acquired 0018,1083

Intervals Rejected 0018,1084

All rights reserved




Heart Rate 0018,1088 Heart Rate as established as scan param-eter prior to scan.

Receiving Coil 0018,1250

Transmitting Coil 0018,1251

Phase Encoding Direction 0018,1312 This is the Preparation Direction or Foldover Direction.

Flip Angle 0018,1314

Temporal Position Identifier 0020,0100 Dynamic Scan Number

Number of Temporal Positions 0020,0105 No. of Dynamic Scans

Table 8-14: MR Image Storage SOP Class - Gyroscan Image Module


Private Creator Group 0019 0019,00xx Value Representation = LO, Multiplicity = 1. Contains the Private Creator Identification Code.Applied value(s): PHILIPS-MR-1

Chemical Shift Number 0019,xx11 Value Representation = IS, Multiplicity = 1.Identifies the chemical shift interval for spec-troscopic reconstruction.

Phase Number (Philips) 0019,xx12 Value Representation = IS, Multiplicity = 1.Identifies a phase interval of the cardiac cycle.

Private Creator Group 0021 0021,00xx Value Representation = LO, Multiplicity = 1.Contains the Private Creator Identification Code.Applied value(s): PHILIPS-MR-1

Slice Number 0021,xx02 Value Representation = IS, Multiplicity = 1.identifies a slice (=image plane) for an acqui-sition and/or a reconstruction.

Table 8-15: MR Image Storage SOP Class - Modality LUT Module


Rescale Intercept 0028,1052 Present if not disabled in Gyroscan con-figuration file.

Rescale Slope 0028,1053 See Rescale Intercept.

Table 8-13: MR Image Storage SOP Class - MR Image Module (Continued)


All rights reserved




Rescale Type 0028,1054 See Rescale Intercept. Applied value(s): US

Table 8-16: MR Image Storage SOP Class - VOI LUT Module


Window Center 0028,1050 To be applied after Modality LUT (=Rescaling).

Window Width 0028,1051 See Window Center.

Table 8-17: MR Image Storage SOP Class - SOP Common Module


Specific Character Set 0008,0005 Received from RIS or determined by Gyroscan.Applied value: “ISO_IR 100" = Latin alphabet No. 1 supplementary set.

Instance Creation Date 0008,0012

Instance Creation Time 0008,0013

Instance Creator UID 0008,0014

SOP Class UID 0008,0016 Applied value(s): 1.2.840.10008.5.1.4.1.1.4

SOP Instance UID 0008,0018

Table 8-15: MR Image Storage SOP Class - Modality LUT Module (Continued)


All rights reserved



Overview applied Modality Worklist Information Model

9 Overview applied Modality Worklist Information Model

This chapter specifies in detail the applied attributes in the C-FIND Service Element of thissupported SOP Class.The list of possible values are given (if applicable).

Table 9-1: Modality Worklist Information Model - FIND SOP Class - SOP Common Module


Specific Character Set 0008,0005 Conditionally present in the Response.

Table 9-2: Modality Worklist Information Model - FIND SOP Class - Patient Identification Module


Patient’s Name 0010,0010 Return key

Patient ID 0010,0020 Return key

Table 9-3: Modality Worklist Information Model - FIND SOP Class - Patient Demographic Module


Patient’s Birth Date 0010,0030 Return key

Patient’s Sex 0010,0040 Return key

Patient’s Weight 0010,1030 Return key

Table 9-4: Modality Worklist Information Model - FIND SOP Class - Scheduled Procedure Step Module


Scheduled Procedure Step Sequence 0040,0100 Return key

> Scheduled Station AE Title 0040,0001 This attribute serves as Matching Key. The Gyroscan WLM AE Title is used as value.

> Scheduled Procedure Step Description

0040,0007 Return key. The value is used as default for Study Description in generated MR Images.

> Scheduled Procedure Step ID 0040,0009 Return key

All rights reserved



Overview applied Modality Worklist Information Model

> Scheduled Procedure Step Status 0040,0020 This attribute may serve as Matching Key.Applied value(s): ARRIVED

Table 9-5: Modality Worklist Information Model - FIND SOP Class - Requested Procedure Module


Study Instance UID 0020,000D Return key

Table 9-6: Modality Worklist Information Model - FIND SOP Class - Imaging Service Request Module


Accession Number 0008,0050 Return key

Referring Physician’s Name 0008,0090 Return key

Table 9-4: Modality Worklist Information Model - FIND SOP Class - Scheduled Procedure Step Module


All rights reserved



Remarks, Implementation restrictions and choices.

nning con-on. Atly thistoragetocols been

ate the

10 Remarks, Implementation restrictions and choices.

• Gyroscan-NT systems are provided with scan protocols that allow for appropriate scain case of administration of contrast media like Gadolinium. In general it can not befirmed that Contrast Medium has indeed been administered, nor at which concentratithis moment the user interface of the Gyroscan-NT does not allow the user to suppinfo yet. However, most users modify the Scan Name (see Table 8-6, “MR Image SSOP Class - General Series Module,” on page 16, under Protocol Name) of the prosuch that on the film or printout it can be recognised that a protocol for contrast hasused.

In the future, scanner controlled contrast injectors or added operator control may creopportunity to provide more detailed contrast information.

• Matching Data Model.

Table 10-1: Matching of the Data Model of the Gyroscan USER Interface to DICOM (Export/RIS)

Gyroscan User Interface DICOM (Export/RIS) Table Reference

Registration Number Patient ID Table 8-2 on page 14

not visible Study Instance UID Table 8-3 on page 15

Accession Number Accession Number Table 8-3 on page 15

Exam Date Study Date Table 8-3 on page 15

not visible Study ID Table 8-3 on page 15

not visible Scheduled procedure Step ID Table 9-4 on page 22

not visible Series Instance UID Table 8-6 on page 16

not visible Series Number Table 8-6 on page 16

Scan Number Acquisition Number Table 8-10 on page 17

not visible Image Number Table 8-10 on page 17

‘Image Type’ (incl. Scanning Sequence) Image Type [4], [5] Table 8-13 on page 19

Reconstruction Number Reconstruction Number Table 8-7 on page 16

Slice Number Slice Number Table 8-14 on page 20

Echo Number Echo Number Table 8-13 on page 19

Phase Number Phase Number Table 8-14 on page 20

Dynamic Scan Number Temporal Position Identifier Table 8-13 on page 19

Chemical Shift Number Chemical Shift Number Table 8-14 on page 20

All rights reserved


philips medical systems dicom conformance statement r6.2

Documents