DICOM Conformance Statement - ZEISS · 11/26/2014 · DICOM Conformance Statement 2.5) 2.6 2011-04-26 gws Revision for FORUM v2.6 (merged from CG-LEH-MS-254-DICOM Conformance Statement

Revision: 3.3

Date: 2014-11-26

Document: DICOM_Conformance_Statement_FORUM_4.0.Docx Page 1 of 86

Copyright: © Carl Zeiss Meditec AG Revision: 3.3

DICOM Conformance Statement

FORUM®

Version 4.0

Including

FORUM Glaucoma Workplace Version 2.0.3

Carl Zeiss Meditec AG

Goeschwitzer Strasse 51-52

07745 Jena

Germany

www.meditec.zeiss.com

http://www.meditec.zeiss.com/



1 Conformance Statement Overview

FORUM is a DICOM archive with query/retrieve functionalities. It also acts as a Modality Worklist Provider. It offers a viewer for patient and worklist administration, for reviewing images and PDF's.

Plugins: There are optional plugins to the FORUM Viewer which offer extended review capabilities, and possibly create new instances:

FORUM Glaucoma Workplace is an optional, additional application to FORUM (FORUM plugin), which is offered separately. It is intended for processing and displaying visual field data and optical coherence tomography data. It is also intended for generating visual field reports (OPV IODs), and reports that contain results from perimetry, optical coherence tomography and fundus photography (ePDF IODs).

This document is structured as suggested in the DICOM Standard (PS 3.2: Conformance).

Table 1-1 Network Services Supported

SOP Classes User of Service (SCU)

Provider of Service (SCP)

Verification

Verification Yes Yes

Transfer Image Storage SOP Classes

Secondary Capture Image Storage Yes Yes

Multi-frame Grayscale Byte Secondary Capture Image Storage

Yes Yes

Multi-frame True Color Secondary Capture Image Storage

Yes Yes

Visible Light Endoscopic Image Storage Yes Yes

Visible Light Microscopic Image Storage Yes Yes

Visible Light Photographic Image Storage Yes Yes

Ophthalmic Photography 8 Bit Image Storage Yes Yes

Ophthalmic Tomography Image Storage Yes Yes

Transfer Video Image Storage SOP Classes

Ophthalmic Photography 8 Bit Image Storage Yes Yes

Video Endoscopic Image Storage Yes Yes

Video Microscopic Image Storage Yes Yes

Video Photographic Image Storage Yes Yes

Transfer Other Storage SOP Classes

Encapsulated PDF Storage Yes Yes

Raw Data Storage Yes Yes

Lensometry Measurements Storage Yes Yes

Autorefraction Measurements Storage Yes Yes

Keratometry Measurements Storage Yes Yes

Subjective Refraction Measurements Storage Yes Yes

Visual Acuity Measurements Storage Yes Yes

Ophthalmic Axial Measurements Storage Yes Yes

Intraocular Lens Calculations Storage Yes Yes

Ophthalmic Visual Field Static Perimetry Measurements Storage

Yes Yes

Workflow Management



Storage Commitment Push Model SOP Class No Yes

Modality Worklist Information Model - FIND No Yes

Query / Retrieve

Patient Root Query/Retrieve Information Model – FIND No Yes

Study Root Query/Retrieve Information Model – FIND No Yes

Study Root Query/Retrieve Information Model – MOVE No Yes

FORUM does not support Media Interchange.



2 Table of Contents 1 Conformance Statement Overview ........................................................................................................ 2 2 Table of Contents ............................................................................................................................. 4 3 Introduction .................................................................................................................................... 6

3.1 Revision History ........................................................................................................................... 6 3.2 Audience .................................................................................................................................... 7 3.3 Remarks .................................................................................................................................... 7 3.4 Definitions and Terms .................................................................................................................... 7 3.5 Abbreviations .............................................................................................................................. 9 3.6 References ................................................................................................................................. 9

4 Networking ................................................................................................................................... 10 4.1 Implementation Model .................................................................................................................. 10

4.1.1 Application Data Flow .......................................................................................................... 10 4.1.2 Functional Definition of AEs ................................................................................................... 13

Functional Definition of FORUM Application Entity ................................................................... 13 4.1.2.1

Functional Definition of FORUM Worklist Application Entity ........................................................ 14 4.1.2.2

Functional Definition of FORUM Glaucoma Workplace .............................................................. 14 4.1.2.3

4.1.3 Sequencing of Real-World Activities ......................................................................................... 14 4.2 AE Specifications ........................................................................................................................ 17

4.2.1 FORUM Application Entity Specification .................................................................................... 17 SOP Classes ................................................................................................................ 17 4.2.1.1

Associations Policies ...................................................................................................... 18 4.2.1.2

4.2.1.2.1 General .................................................................................................................. 18 4.2.1.2.2 Number of Associations .............................................................................................. 18 4.2.1.2.3 Asynchronous Nature ................................................................................................. 18 4.2.1.2.4 Implementation Identifying Information ............................................................................ 18

Association Initiation Policy ............................................................................................... 18 4.2.1.3

4.2.1.3.1 Activity – User Requests Verification (SCU) ...................................................................... 18 4.2.1.3.2 Activity – FORUM Issues Storage Request (SCU)............................................................... 18 4.2.1.3.3 Activity - Remote AE Requests Storage Commitment (SCP) .................................................. 20

Association Acceptance Policy ........................................................................................... 20 4.2.1.4

4.2.1.4.1 Activity – Remote AE Requests Verification (SCP) .............................................................. 20 4.2.1.4.2 Activity - Remote AE issues Storage Request (SCP) ........................................................... 21 4.2.1.4.3 Activity – Remote AE Requests Storage Commitment (SCP).................................................. 22 4.2.1.4.4 Activity – Remote AE issues Patient or Study Root Query (SCP) ............................................. 23 4.2.1.4.5 Activity – Remote AE Issues Retrieve Command (SCP)........................................................ 27 4.2.1.4.6 Activity – Remote AE sends MWL Query (SCP) ................................................................. 28

4.3 Network Interfaces ...................................................................................................................... 31 4.3.1 Physical Network Interface .................................................................................................... 31 4.3.2 Additional Protocols ............................................................................................................. 31 4.3.3 IPv4 and IPv6 Support ......................................................................................................... 31

4.4 Configuration ............................................................................................................................. 31 4.4.1 AE Title/Presentation Address Mapping ..................................................................................... 31

Local AE Titles .............................................................................................................. 31 4.4.1.1

Remote AE Titles ........................................................................................................... 31 4.4.1.2

4.4.2 Parameters ....................................................................................................................... 32 General Parameters ....................................................................................................... 32 4.4.2.1

FORUM Glaucoma Workplace Configuration .......................................................................... 32 4.4.2.2

5 Media Interchange.......................................................................................................................... 34 6 Support of Character Sets ................................................................................................................ 35

6.1 Accepted Character Sets .............................................................................................................. 35 6.2 Returned Character Sets .............................................................................................................. 35



7 Security ...................................................................................................................................... 36 8 Annexes ...................................................................................................................................... 37

8.1 IOD Contents ............................................................................................................................ 37 8.1.1 Created SOP Instance(s) ...................................................................................................... 37

Secondary Capture Image Information Object Definition – File Import ............................................ 38 8.1.1.1

Encapsulated PDF Information Object Defintion ...................................................................... 41 8.1.1.2

Combined Report: EPDF Information Object Definition .............................................................. 44 8.1.1.3

SOP Instances Created by FORUM Glaucoma Workplace ......................................................... 47 8.1.1.4

8.1.1.4.1 Encapsulated PDF Information Object Defintion ................................................................. 47 8.1.1.4.2 Ophthalmic Visual Field Static Perimetry Measurement Information Object Definition .................... 58

8.1.2 Usage of Attributes from Received IOD’s ................................................................................... 78 8.1.3 Attribute Mapping ............................................................................................................... 78 8.1.4 Coerced/Modified Files ......................................................................................................... 80

Patient Edit/Merge or Instance Reassign ............................................................................... 80 8.1.4.1

Patient Information / Patient Matching .................................................................................. 81 8.1.4.2

Missing UIDs ................................................................................................................ 82 8.1.4.3

Patient Identification Conflict with Study Instance UID ............................................................... 82 8.1.4.4

8.2 Data Dictionary of Private Attributes ................................................................................................. 82 8.3 Coded Terminology and Templates .................................................................................................. 84 8.4 Greyscale Image Consistency ........................................................................................................ 85 8.5 Standard Extended / Specialized/ Private SOP Classes ......................................................................... 85 8.6 Private Transfer Syntaxes ............................................................................................................. 85



3 Introduction

3.1 Revision History Document

Version Date Author Changes

1.0 2008-11-25 tku Initial revision for FORUM v1.1

2.0 2009-07-23 tku Adjustments for FORUM v2.0

2.5 2010-05-17 gws Revision for FORUM v2.5 (merged from CG-LEH-MS-203-DICOM Conformance Statement 2.5)

2.6 2011-04-26 gws Revision for FORUM v2.6 (merged from CG-LEH-MS-254-DICOM Conformance Statement 2.6.doc)

3.0 2012-03-12 gws Revision for FORUM v3.0



Support Ophthalmic Visual Field Static Perimetry Measurements Storage

Patients Name matching

Patient matching

Query/Return key Creator-Version UID

Responses are sorted descending by Acquisition Date Time

3.2.1 2013-10-28 rms Update on phrasing of chapter 1 (for better readability)

Add description of optional, additional application “FORUM Glaucoma Workplace” revision 2.0:

Ophthalmic Visual Field Static Perimetry Measurement IOD generation

ePDF Report generation

3.3 2014-11-26 gws, rms Revision for FORUM v4.0

New supported SOP Classes:

Lensometry Measurements Storage

Autorefraction Measurements Storage

Keratometry Measurements Storage

Subjective Refraction Measurements Storage

Visual Acuity Measurements Storage

Ophthalmic Axial Measurements Storage

Intraocular Lens Calculations Storage

New supported C-FIND Attribute:

Referenced Refractive Measurements Sequence

Created SOP Instance Combined Report: Replaced Laterality by Image Laterality, Software Versions including patch and build level.

Table 430 Added Modality Worklist C-FIND response status code C001 "Too Many Results"

Table 4-20 New Query Return key "Measurement Laterality"

Chapter 8.1.4.1 Dicom Header Update, transcoding to UTF8

Updated description of FORUM Glaucoma Workplace to revision 2.0.3:

adding private attribute modules in ePDF IOD (CZM-HFA-Series Module and CZM-HFA-Analysis Module) and OPV IOD (HfaVisualFieldStaticPerimetryTestResults)



added attribute Performed Protocol Code Sequence to OPV IOD

extended standard ContextIDs 4250 and 4251

3.2 Audience This document is intended for hospital staff, health system integrators, software designers or implementers. The reader should have a basic understanding of DICOM.

3.3 Remarks If another device matches this conformance statement based on the comparison with its own conformance statement, there is a chance, but no guarantee, that they interoperate. DICOM deals only with communication; it does not specify what is needed for certain applications to run on a device.

3.4 Definitions and Terms Informal definitions are provided for the following terms used in this Conformance Statement.

The DICOM Standard is the authoritative source for formal definitions of these terms.

Abstract Syntax the information agreed to be exchanged between applications, generally equivalent to a Service/Object Pair (SOP) Class.

Examples: Verification SOP Class, Modality Worklist Information Model Find SOP Class, Computed Radiography Image Storage SOP Class.

Application Entity (AE) an end point of a DICOM information exchange, including the DICOM network or media interface software; i.e., the software that sends or receives DICOM information objects or messages. A single device may have multiple Application Entities.

Application Entity Title the externally known name of an Application Entity, used to identify a DICOM application to other DICOM applications on the network.

Application Context the specification of the type of communication used between Application Entities.

Example: DICOM network protocol.

Association a network communication channel set up between Application Entities.

Attribute a unit of information in an object definition; a data element identified by a tag. The information may be a complex data structure (Sequence), itself composed of lower level data elements.

Examples: Patient ID (0010,0020), Accession Number (0008,0050), Photometric Interpretation (0028,0004), Procedure Code Sequence (0008,1032).

Information Object Definition (IOD) the specified set of Attributes that comprise a type of data object; does not represent a specific instance of the data object, but rather a class of similar data objects that have the same properties. The Attributes may be specified as Mandatory (Type 1), Required but possibly unknown (Type 2), or Optional (Type 3), and there may be conditions associated with the use of an Attribute (Types 1C and 2C).

Examples: MR Image IOD, CT Image IOD, Print Job IOD.

Joint Photographic Experts Group (JPEG) a set of standardized image compression techniques, available for use by DICOM applications.



Media Application Profile the specification of DICOM information objects and encoding exchanged on removable media (e.g., CDs)

Module a set of Attributes within an Information Object Definition that are logically related to each other.

Example: Patient Module includes Patient Name, Patient ID, Patient Birth Date, and Patient Sex.

Negotiation first phase of Association establishment that allows Application Entities to agree on the types of data to be exchanged and how that data will be encoded.

Presentation Context the set of DICOM network services used over an Association, as negotiated between Application Entities; includes Abstract Syntaxes and Transfer Syntaxes.

Protocol Data Unit (PDU) a packet (piece) of a DICOM message sent across the network. Devices must specify the maximum size packet they can receive for DICOM messages.

Query Key A input value for a query process. Query Keys denote the set of DICOM tags that are sent from the SCU to SCP and thus control the query result.

Security Profile a set of mechanisms, such as encryption, user authentication, or digital signatures, used by an Application Entity to ensure confidentiality, integrity, and/or availability of exchanged DICOM data

Service Class Provider (SCP) role of an Application Entity that provides a DICOM network service; typically, a server that performs operations requested by another Application Entity (Service Class User).

Examples: Picture Archiving and Communication System (image storage SCP, and image query/retrieve SCP), Radiology Information System (modality worklist SCP).

Service Class User (SCU) role of an Application Entity that uses a DICOM network service; typically, a client.

Examples: imaging modality (image storage SCU, and modality worklist SCU), imaging workstation (image query/retrieve SCU)

Service/Object Pair (SOP) Class the specification of the network or media transfer (service) of a particular type of data (object); the fundamental unit of DICOM interoperability specification.

Examples: Ultrasound Image Storage Service, Basic Grayscale Print Management.

Service/Object Pair (SOP) Instance an information object; a specific occurrence of information exchanged in a SOP Class.

Examples: a specific x-ray image.

Tag a 32-bit identifier for a data element, represented as a pair of four digit hexadecimal numbers, the “group” and the “element”. If the “group” number is odd, the tag is for a private (manufacturer-specific) data element.

Examples: (0010,0020) [Patient ID], (07FE,0010) [Pixel Data], (0019,0210) [private data element]

Transfer Syntax the encoding used for exchange of DICOM information objects and messages.

Examples: JPEG compressed (images), little endian explicit value representation.

Unique Identifier (UID) a globally unique “dotted decimal” string that identifies a specific object or a class of objects; an ISO-8824 Object Identifier.

Examples: Study Instance UID, SOP Class UID, SOP Instance UID.



Value Representation (VR) the format type of an individual DICOM data element, such as text, an integer, a person’s name, or a code. DICOM information objects can be transmitted with either explicit identification of the type of each data element (Explicit VR), or without explicit identification (Implicit VR); with Implicit VR, the receiving application must use a DICOM data dictionary to look up the format of each data element.

3.5 Abbreviations Table 3-1 Abbreviations used in this document

Abbreviation Definition

AE Application Entity

AET Application Entity Title

DICOM Digital Imaging and Communications in Medicine

EBE Explicit Big Endian

ELE Explicit Little Endian

EMR Electronic Medical Record

EPDF Encapsulated Portable Document Format

HL7 Health Level Seven

ILE Implicit Little Endian

IOD Information Object Definition

MWL Modality Worklist

MPEG2 Motion Picture Expert Group 2; Abbreviation and synonym for video encoding and compression transfer syntax.

MPML MPEG2 Main Profile @ Main Level (as defined in the MPEG-2 standard)

MP HL MPEG2 Main Profile @ High Level (as defined in the MPEG-2 standard)

RLE Run Length Encoding

SCP Service Class Provider

SCU Service Class User

SOP Service Object Pair, union of a specific DICOM service and related IOD.

TCP/IP Transmission Control Protocol / Internet Protocol

UI User Interface

UID Unique Identifier

VL Visible Light

XML Extensible Markup Language

3.6 References NEMA PS3 / ISO 12052, Digital Imaging and Communications in Medicine (DICOM) Standard, National Electrical Manufacturers Association, Rosslyn, VA, USA (available free at http://medical.nema.org/)

Integrating the Healthcare Enterprise (IHE) EYECARE Technical Framework, rev 3.7, 2010 (available free at http://www.ihe.net/Technical_Framework/index.cfm

http://medical.nema.org/



4 Networking

4.1 Implementation Model

4.1.1 Application Data Flow Figure 4-1 FORUM Archive - Functional Overview

FORUM Application

Entity

User requests Verification

Remote AE receives Verification

FORUM issues Storage Request

Remote AE issues Patient or Study Root

Query

Remote AE requests Storage Commitment and receives Reports

Remote AE requests Verification

Remote AE issues Storage Request

Remote AE issues Retrieve Command

Requested Instances received by Remote AE

User edits patient demographics, merges

patients and moves instances to other studies (reassign)

User imports image and PDF files, which will be converted to DICOM

files

User exports DICOM files to local disk.

DICOM Standard Interface

User sets up Forwarding Rules



Figure 4-2 FORUM Worklist Provider - Functional Overview

The FORUM application can be configured in a way that the complete functionality is covered by one AE. The diagram above shows the configuration where Storage related activities and Worklist related activities are separate AEs.

Patients and Worklist Orders entered by

User, or received via EMR-XML or HL7

FORUM Worklist

Application Entity

Remote AE requests Verification

Remote AE sends MWL Query




Figure 4-3 FORUM Glaucoma Workplace - Functional Overview

The local activities described in



Figure 4-3 below are additional activities to the functional range of FORUM Archive described in Figure 4-1 FORUM Archive - Functional Overview. These additional activities are added with the installation of the Glaucoma Workplace as software plugin to FORUM. All DICOM related local and real world activities of FORUM Archive as described in Figure 4-1 remain valid.

4.1.2 Functional Definition of AEs

Functional Definition of FORUM Application Entity 4.1.2.1

The FORUM AE initiate an association and request verification to a remote AE.

The FORUM AE waits in the background for connections, and

Answers Verification requests

Responds to C-FIND queries

Stores Instances

Processes Storage Commitment requests, and therefore initiates an association and sends reports.

Processes Retrieve Command, and therefore initiates an association and send storage requests.

FORUM Application

Entity

User creates a report manually. Created

Reports are stored in FORUM


Reports and OPVs are created automatically

on arrival of an appropriate DICOM instance in FORUM

Reports are created automatically for

DICOM Instances already existing in FORUM Archive



Functional Definition of FORUM Worklist Application Entity 4.1.2.2

The FORUM Worklist AE waits in the background for connections, and

Answers Verification requests

Responds to C-FIND queries

Worklist items to be returned, can be created

Manually using the FORUM MWL Scheduler UI

Automatically through the EMR XML interface

Automatically through the HL7 interface

Functional Definition of FORUM Glaucoma Workplace 4.1.2.3

FORUM Glaucoma Workplace is a FORUM application intended for

Processing and displaying visual field data and optical coherence tomography data

Generating visual field reports.

Generating reports that contain results from perimetry, optical coherence tomography and fundus photography.

All instances generated by FORUM Glaucoma Workplace are automatically stored in FORUM Archive and made available for other DICOM activities like Storage to a remote AE, Query/Retrieve by a remote AE or export to local storage media.

4.1.3 Sequencing of Real-World Activities

To realize the real world activities, the different entities work together. The sequence diagrams shall depict the intended workflow.

The diagrams use slightly modified UML symbols. The asynchronous call is not depicted as suggested in UML. Some objects do have more than one dashed line. It symbolizes more than one thread.

The only sequencing constraint that exists across FORUM and the corresponding Application Entities, is the fact that a Composite SOP Instance must be received by FORUM before Storage Commitment Push Model or Query-Retrieve Requests related to this SOP Instance can be successfully handled.



Figure 4-4 Verification

Peer Verification

SCP AE

Peer Verification

SCU AE

FORUM AE

Send Verification Request

Send Verification

Request

FORUM Worklist

AE

Send Verification Request



Figure 4-5 FORUM Archive

Figure 4-6 FORUM Modality Worklist Provider

Peer Storage SCP AE

Peer Query-Retrieve SCP AE

Peer Storage SCU AE

FORUM AE

Send Storage Commitment Request

Return Storage Commitment Notification

Send Storage Request for SOP Instance

Send Study- or Patient- Root Query

Return Information on requested Query Retrieve Level

Send Retrieval Request for SOP Instance(s)

Send requested SOP Instance(s)

Peer Query-Retrieve SCP AE

FORUM Worklist

AE

Send Modality Worklist Query

Return Information related to Worklist



4.2 AE Specifications

4.2.1 FORUM Application Entity Specification

SOP Classes 4.2.1.1

Table 4-1 SOP Classes for FORUM AE and FORUM MWL AE

SOP Class Name SOP Class UID SCU SCP

Verification 1.2.840.10008.1.1 Yes Yes

Modality Worklist Information Model - FIND 1.2.840.10008.5.1.4.31 No Yes

Ophthalmic Photography 8 Bit Image Storage 1.2.840.10008.5.1.4.1.1.77.1.5.1 Yes Yes

Encapsulated PDF Storage 1.2.840.10008.5.1.4.1.1.104.1 Yes Yes

Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7 Yes Yes

Multi-frame Grayscale Byte Secondary Capture Image Storage

1.2.840.10008.5.1.4.1.1.7.2 Yes Yes

Multi-frame True Color Secondary Capture Image Storage

1.2.840.10008.5.1.4.1.1.7.4 Yes Yes

Raw Data Storage 1.2.840.10008.5.1.4.1.1.66 Yes Yes

Visible Light Endoscopic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.1 Yes Yes

Visible Light Microscopic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.2 Yes Yes

Visible Light Photographic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.4 Yes Yes

Video Endoscopic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.1.1 Yes Yes

Video Microscopic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.2.1 Yes Yes

Video Photographic Image Storage 1.2.840.10008.5.1.4.1.1.77.1.4.1 Yes Yes

Ophthalmic Tomography Image Storage 1.2.840.10008.5.1.4.1.1.77.1.5.4 Yes Yes

Lensometry Measurements Storage 1.2.840.10008.5.1.4.1.1.78.1 Yes Yes

Autorefraction Measurements Storage 1.2.840.10008.5.1.4.1.1.78.2 Yes Yes

Keratometry Measurements Storage 1.2.840.10008.5.1.4.1.1.78.3 Yes Yes

Subjective Refraction Measurements Storage 1.2.840.10008.5.1.4.1.1.78.4 Yes Yes

Visual Acuity Measurements Storage 1.2.840.10008.5.1.4.1.1.78.5 Yes Yes

Ophthalmic Axial Measurements Storage 1.2.840.10008.5.1.4.1.1.78.7 Yes Yes

Intraocular Lens Calculations Storage 1.2.840.10008.5.1.4.1.1.78.8 Yes Yes

Ophthalmic Visual Field Static Perimetry Measurements Storage

1.2.840.10008.5.1.4.1.1.80.1 Yes Yes

Patient Root Q/R Information Model – FIND 1.2.840.10008.5.1.4.1.2.1.1 No Yes

Study Root Q/R Information Model – FIND 1.2.840.10008.5.1.4.1.2.2.1 No Yes

Study Root Q/R Information Model – MOVE 1.2.840.10008.5.1.4.1.2.2.2 No Yes

Storage Commitment Push Model 1.2.840.10008.1.20.1 No Yes



Associations Policies 4.2.1.2

4.2.1.2.1 General

The DICOM standard Application Context Name for DICOM 3.0 is always proposed:

Table 4-2 DICOM Application Context

Application Context Name 1.2.840.10008.3.1.1.1

4.2.1.2.2 Number of Associations

The FORUM SW can be configured to use either one AE or two separate AEs for Storage and Worklist related activities. The maximum number of association applies per AE.

Table 4-3 Number of associations

Maximum number of simultaneous associations 50 per AE

4.2.1.2.3 Asynchronous Nature

FORUM Application Software does not support asynchronous communication (multiple outstanding transactions over a single Association).

4.2.1.2.4 Implementation Identifying Information

Table 4-4 DICOM implementation class and version

Implementation Class UID 1.2.276.0.75.2.5.30

Implementation Version Name F

Association Initiation Policy 4.2.1.3

4.2.1.3.1 Activity – User Requests Verification (SCU)

4.2.1.3.1.1 Description and Sequencing of Activities

The FORUM AE sends DICOM Verification requests when the user requests a test of validity of a DICOM connection through the GUI.

4.2.1.3.1.2 Proposed Presentation Contexts

Table 4-5 Presentation Contexts proposed by the FORUM AE

Presentation Context Table

Abstract Syntax Transfer Syntax Role Ext. Neg.

Name UID Name List

UID List

Verification 1.2.840.10008.1.1 ILE 1.2.840.10008.1.2 BOTH No

4.2.1.3.1.3 SOP Specific Conformance for Verification SOP Class

The FORUM Application Software provides standard conformance to the DICOM Verification Service Class as an SCU.

4.2.1.3.2 Activity – FORUM Issues Storage Request (SCU)


The FORUM AE will transmit instances either driven by an automated forwarding mechanism, or as reaction to a received C-MOVE request. The automatic forwarding can be configured by the user through



the UI. An association is established when the user or the forwarding mechanism initiates a transmit request.

The FORUM AE will establish an association automatically in response to a C-MOVE request.


The FORUM AE may request any of the Presentation Contexts listed in the following table for Storage. The FORUM AE will only propose the transfer syntax, which was used when the object was initially accepted by the server.

Table 4-6 Proposed Presentation Contexts by the FORUM AE



Name / UID Name List UID List

All SOP classes listed in section "Transfer Image Storage SOP Classes"

Implicit VR Little Endian

Explicit VR Little Endian

Explicit VR Big Endian

RLE Lossless

JPEG Baseline

JPEG Lossless

JPEG 2000 (Lossless Only)

JPEG 2000

1.2.840.10008.1.2

1.2.840.10008.1.2.1

1.2.840.10008.1.2.2

1.2.840.10008.1.2.5

1.2.840.10008.1.2.4.50

1.2.840.10008.1.2.4.70

1.2.840.10008.1.2.4.90

1.2.840.10008.1.2.4.91

BOTH No

All SOP classes listed in section "Transfer Video Image Storage SOP Classes"

MPEG2 MPML

MPEG2 MPHL

1.2.840.10008.1.2.4.100

1.2.840.10008.1.2.4.101

BOTH No

All SOP classes listed in section "Transfer Other Storage SOP Classes"




1.2.840.10008.1.2

1.2.840.10008.1.2.1

1.2.840.10008.1.2.2

BOTH No

4.2.1.3.2.3 SOP Specific Conformance – Store Objects

The FORUM AE provides limited standard conformance to the DICOM Storage Service Class as an SCU: Neither is it guaranteed that the DICOM Default Transfer Syntax (Implicit VR Little Endian) is always proposed in a presentation context. Nor is an “on-the-fly” transcoding to the DICOM Default Transfer Syntax supported for instances received and stored in lossless compression.

A successful C-Store response status will not generate any actions.

Table 4-7 C-STORE Response Status Handling Behavior

Service Status Further Meaning

Error Code Behavior

Other than SUCCESS

> 0000 For C-MOVE Requests they will be reported in the C-STORE-RESPOND under "Number Of Failed Suboperations" (0000,1022)

Duplicate SOP Instance

0111 For Forwarding jobs this job will be marked with "SUCCESS" and this job is done.

Other than SUCCESS and Duplicate SOP Instance

> 0000

< 0111

> 0111

For Forwarding jobs this job will be marked with "FAILED" failed and this job is pending. Also the Error Comment (0000,0902) will be saved with this job.



4.2.1.3.3 Activity - Remote AE Requests Storage Commitment (SCP)

4.2.1.3.3.1 Description and Sequencing of Activites

The FORUM AE will respond to N-ACTION requests, and initiate a N-EVENT-REPORT.


The FORUM AE may request the following Presentation Contexts listed in the following table.

Table 4-8 Proposed Presentation Contexts by the FORUM AE



Name UID Name List

UID List

Storage Commitment Push Model 1.2.840.10008.1.20.1 ILE

ELE

EBE

1.2.840.10008.1.2

1.2.840.10008.1.2.1

1.2.840.10008.1.2.2

SCP No

4.2.1.3.3.3 SOP Specific Conformance – Storage Commitment

The FORUM AE provides conformance to the DICOM Storage Commitment Service Class as an SCP.

The N-EVENT-REPORT contains the following Failure Reasons in the Failed SOP Sequence:

Table 4-9 Storage Commitment Failure Reasons


Failure Reason

Behavior

Failure No such object instance

0112 The SOP instance is not available in FORUM.

Failure Class / Instance conflict

0119 The SOP instance is stored with another SOP class UID in FORUM

Failure Referenced SOP Class not supported

0122 The SOP instance is not available in FORUM and the SOP Class is not supported by FORUM.

Association Acceptance Policy 4.2.1.4

FORUM accepts only associations from registered AE titles.

4.2.1.4.1 Activity – Remote AE Requests Verification (SCP)


Both the FORUM AE and the FORUM MWL AE will respond to Verification requests from a Verification SCU. This way the requesting SCU can determine whether the respective FORUM AEs are able to receive and handle incoming DICOM requests.

4.2.1.4.1.2 Accepted Presentation Contexts

Table 4-10 Presentation Context accepted by the FORUM and FORUM MWL AE


Abstract Syntax Transfer Syntax Role Ext. Neg. Name UID Name

List UID List

Verification 1.2.840.10008.1.1 ILE 1.2.840.10008.1.2 BOTH No



4.2.1.4.1.3 SOP Specific Conformance for Verification SOP Class as SCP

FORUM provides standard conformance to the DICOM Verification Service Class as an SCP. One of the following status codes are returned:


Error Code Behavior

Success Success 0000 Operation performed properly.

Both the FORUM AE and the FORUM MWL AE will always accept a Presentation Context for the Verification SOP Class with the default DICOM transfer syntax.

4.2.1.4.2 Activity - Remote AE issues Storage Request (SCP)


The FORUM AE will store DICOM instances that are sent to it from a remote SCU. All storage objects received by the FORUM AE can be retrieved at a later time from the FORUM AE.


Table 4-11 Presentation Contexts accpeted by the <instrument> AE



Name / UID Name List UID List

All SOP classes listed in section "Transfer Image Storage SOP Classes"




RLE Lossless

JPEG Baseline

JPEG Lossless

JPEG 2000 (Lossless Only)

JPEG 2000

1.2.840.10008.1.2

1.2.840.10008.1.2.1

1.2.840.10008.1.2.2

1.2.840.10008.1.2.5

1.2.840.10008.1.2.4.50

1.2.840.10008.1.2.4.70

1.2.840.10008.1.2.4.90

1.2.840.10008.1.2.4.91

BOTH No

All SOP classes listed in section "Transfer Video Image Storage SOP Classes"

MPEG2 MPML

MPEG2 MPHL

1.2.840.10008.1.2.4.100

1.2.840.10008.1.2.4.101

BOTH No

All SOP classes listed in section "Transfer Other Storage SOP Classes"




1.2.840.10008.1.2

1.2.840.10008.1.2.1

1.2.840.10008.1.2.2

BOTH No

4.2.1.4.2.3 SOP Specific Conformance – Store Objects

The FORUM AE conforms to the DICOM Storage Service Class as a Level 2 (Full) SCP. No elements are discarded. Certain Attribute will be coerced, see 8.1.4 Coerced/Modified Files. All Type 1, Type 2 and Type 3 attributes will be retained. Private attributes will be stored and included when the object is sent out later to a remote AE.

In case an instance is rejected, one of the following status codes is returned by the FORUM AE:

Service Status Further Meaning Status Code Behavior

Refused

Out Of Resources

A700 Error while storage space is less than 3GB.

Missing license for MPEG

No Such SOP class

0118 If a SOP Class is used, that was not negotiated.

Unrecognized 0211 Unrecognized value in Command Filed



Operation

Error Invalid Attribute Value

0106 Unsupported SOP Instance UID prefix. MpegFormatException

Processing Failure 0110 Unexpected internal errors.

Duplicate SOP instance

0111 SOP Instance UID is already present in this archive while a new C-STORE request is being processed.

Invalid Object Instance

0117 The series of an incoming C-STORE request is already attached to another study.

Missing Attribute Value

0121 An Instance UID is missing.

SOP class Not Supported

0122 Incoming SOP Class is not supported by FORUM

Unable To Process C000 Unexpected internal errors.


The FORUM AE will accept any number of Presentation Contexts per association request. Any single Abstract Syntax may be specified more than once in an association request, if the Transfer Syntaxes differ between the Presentation Contexts.

Explicit VR Little Endian is preferred over Implicit VR Little Endian as the accepted Transfer Syntax when both Transfer Syntaxes are offered in a Presentation Context in an Associate Request.

FORUM AE will only accept association requests for known (configured) remote AEs.

4.2.1.4.3 Activity – Remote AE Requests Storage Commitment (SCP)


When FORUM receives a storage commitment request, it checks whether the requested SOP instances are present in FORUM and sends an N-EVENT report. FORUM accepts a list of references to one or more DICOM SOP instances.


Table 4-12 Presentation Contexts accepted by the FORUM AE



Name UID 1.2.840.10008. ...

Name List

UID List 1.2.840.10008. ...

Storage Commitment Push Model 1.2.840.10008.1.20.1 ILE 1.2.840.10008.1.2 SCP No

4.2.1.4.3.3 SOP Specific Conformance – Storage Commitment

The FORUM AE provides conformance to the DICOM Storage Commitment Service Class as an SCP. The number of referenced instances within one request is limited to 500. The N-EVENT-REPORT message is always sent in a separate association from the N-ACTION operation.

For Storage Commitment operations, the FORUM AE will only accept association requests for known (configured) remote AEs.

One of the following Status codes is returned by the FORUM AE in a N-ACTION response:

Table 4-13 Storage Commitment N-ACTION-RSP Status Codes


Status Code Behavior

Error Processing 0110 Unexpected internal errors or too many items in



Failure the Referenced SOP Sequence (at least more than 500)

Success Success 0000 Operation performed properly

4.2.1.4.4 Activity – Remote AE issues Patient or Study Root Query (SCP)


The FORUM AE will respond to query requests that are sent to it by a remote SCU.


Table 4-14 Presentation Context accepted by the <instrument> AE



List UID List

Patient Root Q/R Information Model – FIND

1.2.840.10008.5.1.4.1.2.1.1 ILE 1.2.840.10008.1.2 SCP Yes

Study Root Q/R Information Model – FIND

1.2.840.10008.5.1.4.1.2.2.1 ILE 1.2.840.10008.1.2 SCP Yes

C-Find Extended Negotiation is supported: For the fields "Relational-queries" and "Date-time matching", the value “1” is returned, meaning that those are supported by the FORUM AE.

4.2.1.4.4.3 SOP Specific Conformance – Find Objects

The FORUM AE provides standard conformance to the DICOM Query/Retrieve Service Class as an SCP. The FORUM AE supports both Hierarchical Queries and the Relational-queries extended SCP behavior. Matching for attributes with VR PN (Person Name) is always done case-insensitive.

The following tables contain detailed information on matching and return keys.

Table 4-15 Matching Types

Abbreviation Description

U Universal Matching

S Single Value Matching

* Wildcard Matching

R Range Matching

CDT Combined Date Time Matching

UNIQUE Unique query key for the respective level

Table 4-16 Patient Root / Patient Level Attributes

Description Tag Matching Type

Patient's Name (0010,0010) U S * (*1)

Patient ID (0010,0020) U S *, UNIQUE together with Issuer of Patient ID

Issuer of Patient ID (0010,0021) U S *, UNIQUE together with Patient ID

Other Patient IDs (0010,1000) U S *

Patient's Birth Date (0010,0030) U S R



Patient's Sex (0010,0040) U S

Ethnic Group (0010,2160) U S

Patient Comments (0010,4000) U S *

Table 4-17 Patient Root / Study Level Attributes


Study Instance UID (0020,000D) U S, UNIQUE

Study ID (0020,0010) U S

Accession Number (0008,0050) U S *

Study Date (0008,0020) U CDT

Study Time (0008,0030) U CDT

Modalities in Study (*5) (0008,0061) U S

Referring Physician’s Name (0008,0090) U S *

Study Description (0008,1030) U S *

Admitting Diagnoses Description (0008,1080) U S *

Table 4-18 Study Root / Study Level Attributes


Study Instance UID (0020,000D) U S, UNIQUE

Study ID (0020,0010) U S

Accession Number (0008,0050) U S *

Study Date (0008,0020) U CDT

Study Time (0008,0030) U CDT

Modalities in Study (*5) (0008,0061) U S

Referring Physician’s Name (0008,0090) U S *

Study Description (0008,1030) U S *

Admitting Diagnoses Description (0008,1080) U S *

Patient's Name (0010,0010) U S * (*1)

Patient ID (0010,0020) U S *

Issuer of Patient ID (0010,0021) U S *

Other Patient IDs (0010,1000) U S *



Ethnic Group (0010,2160) U S


Table 4-19 Series Level Attributes


Modality (0008,0060) U S

Series Number (0020,0011) U S

Series Instance UID (0020,000E) U S, UNIQUE

Series Date (0008,0021) U CDT



Series Time (0008,0031) U CDT

Series Description (0008,103E) U S *

Laterality (0020,0060) U S

Number of Series Related Instances (0020,1209) return key only

Performing Physicians’ Name (0008,1050) U S *

Manufacturer's Model Name (0008,1090) U S *

Performed Procedure Step Start Date (0040,0244) U CDT

Performed Procedure Step Start Time (0040,0245) U CDT

Request Attributes Sequence (0040,0275)

›Requested Procedure ID (0040,1001) U S

›Scheduled Procedure Step ID (0040,0009) U S

Table 4-20 Instance Level Attributes


Image Type (*4) (0008,0008) U S *

Instance Number (0020,0013) U S

SOP Instance UID (0008,0018) U S, UNIQUE

SOP Class UID (0008,0016) U S

Instance Creation Date (0008,0012) U CDT

Instance Creation Time (0008,0013) U CDT

Acquisition Date Time (*2) (0008,002A) U CDT

Icon Image Sequence (0088,0200) return key only

Image Laterality (*6) (0020,0062) U S

Measurement Laterality (*6) (0024,0113) U S

Document Title (0042,0010) U S *

Creator-Version UID (0008,9123) U S

Referenced Image Sequence (*3) (0008,1140)

›Referenced SOP Instance UID (0008,1155) U S

›Referenced SOP Class UID (0008,1150) return key only

›Purpose Of Reference Code Sequence (0040,A170)

››Coding Scheme Designator (0008,0102) U S

››Coding Scheme Version (0008,0103) U S

››Code Value (0008,0100) U S

Referenced Instance Sequence (*3) (0008,114A)






››Code Value (0008,0100) U S

Source Instance Sequence (*3) (0042,0013)








››Code Value (0008,0100) U S

Referenced Refractive Measurements Sequence (*3)

(0046,0145)






››Code Value (0008,0100) U S

Remark (*1): Patients Name matching:

FORUM uses the first non-empty component group of the matching key attribute as a query key. A component group in this context is empty if it contains only one or more of the characters "^" or "*". FORUM matches always all component groups. For Example "Wem*" returns all Patients, whose last name starts with "Wem" regardless in which component group.

Double Wildcard Search "**":

If the last name of the first non-empty component group contains "**", then all other components of this component group of the matching key are ignored, and this last name query key matches all components of all component groups. For example "Wem**" returns all patients, who have any name part starting with "Wem" regardless in which component group they occur. “Wem**” returns names like "Wemmer^Peter", "Bauer^Wemam" or "xxx^yyy=a^b^wemu".

Remark (*2): The responses are sorted descending by Acquisition Date Time.

Remark (*3): Only one of "Referenced Image Sequence", "Referenced Instance Sequence" or " Source Instance Sequence" is supported in one C-FIND request.

Remark (*4): Although "Image Type" has a value multiplicity of greater than one, FORUM only returns valid matches if the order of the values in the query key matches the order of the values in the FORUM data objects.

Example: "aaa\xxx\yyy\ddd" in FORUM is matched by "xxx" or "xxx\yyy" or “x*\yy*”, but NOT by "yyy\xxx" and not by “aaa\yyy”

Remark (*5): "Modalities in Study" is supported ONLY on STUDY LEVEL.

Remark (*6): Only one of "Image Laterality" or "Measurement Laterality" is supported in one C-FIND request.



The FORUM AE returns one of the following status codes in a C-FIND response:

Service Status Further Meaning Error Code Behavior

Refused No Such SOP class


Unrecognized Operation

0211 Unrecognized value in Command Filed

Failed Invalid Attribute Value 0106 Wrong query retrieve level

Processing Failure 0110 Unexpected internal errors.

Unable To Process C000 Unexpected internal errors.

Cancel FE00 The original requester canceled this operation.

Pending Pending FF00 All Optional Keys are supported in the same manner as Required Keys.

Warning Too Many Results C001 If the received request leads to more than 5000 responses then these 5000 responses will be returned followed by this status. On Query Retrieve Level "IMAGE" the most recent SOP instances according to Acquisition Date Time will be returned.


For C-FIND operations, the FORUM AE will only accept association requests for known (configured) remote AEs.

A Patient Root Query in FORUM returns only patients who are not flagged as conflicted patients. See 8.1.4.2 Patient Information / Patient Matching for details on conflicted patients.

A Study Root Query in FORUM returns all patients..

4.2.1.4.5 Activity – Remote AE Issues Retrieve Command (SCP)


The FORUM AE will respond to C-MOVE requests that are sent to it by a remote SCU.

The FORUM AE will establish a new association with the remote AE specified in the move destination for the C-STORE sub operation. The FORUM AE will always only propose the transfer syntax used when the object was initially sent to the FORUM server.


Table 4-21 Presentation Context accepted by the FORUM AE



List UID List

Study Root Q/R Information Model – MOVE

1.2.840.10008.5.1.4.1.2.2.2 ILE 1.2.840.10008.1.2 SCP No



4.2.1.4.5.3 SOP Specific Conformance – Move Objects

The FORUM AE will establish an association with the destination specified in the C-MOVE request. One or more of the Presentation Contexts listed in chapter 4.2.1.4.2 “Activity - Remote AE issues Storage Request (SCP)” may be negotiated in this association.

The following tables contain detailed information on supported matching keys:

Table 4-22 Study Root / Study Level Attributes


Study Instance UID (0020,000D) List of UID Matching

Table 4-23 Series Level Attributes


Series Instance UID (0020,000E) List of UID Matching

Table 4-24 Instance Level Attributes


SOP Instance UID (0008,0018) List of UID Matching

The Query/Retrieve Level is identified implicitly by the key used.

If a non-empty SOP Instance UID is present, then those will be retrieved,

else if a non-empty Series Instance UID is present, then those will be retrieved,

else if a non-empty Study Instance UID is present, then those will be retrieved.

The FORUM AE returns one of the following status codes in a C-MOVE response:

Table 4-25 Possible C-MOVE response status codes

Service Status Further Meaning Error Code

Behavior




0211 Unrecognized value in command field

Error Processing Failure 0110 Unexpected internal errors

No Such Object Instance

0112 C-MOVE request for non-existing SOP instance

Unable To Process C000 Unexpected internal errors

Success Success 0000 Operation performed properly

4.2.1.4.6 Activity – Remote AE sends MWL Query (SCP)


The FORUM MWL AE will respond to DICOM C-FIND requests in response to a remote AE querying for a Modality Worklist.


Table 4-26 Presentation Context accepted by the FORUM MWL AE



List UID List



Modality Worklist Information Model - FIND

1.2.840.10008.5.1.4.31 ILE 1.2.840.10008.1.2 SCP Yes

4.2.1.4.6.3 SOP Specific Conformance for Modality Worklist SOP Class as SCP

The FORUM MWL AE provides standard conformance to the DICOM Basic Worklist Management Service Class.

The FORUM application can be configured to use only one AE for MWL and all the other described transactions.

Table 4-27 Matching Types

Abbreviation Description

U Universal Matching

S Single Value Matching

* Wildcard Matching

R Range Matching

CDT Combined Date Time Matching

UNIQUE Unique query key for the respective level

The following table contains detailed information on matching keys:

Table 4-28 Modality Worklist - Matching Keys


Accession Number (0008,0050) U S

Requested Procedure ID (0040,1001) U S

Scheduled Procedure Step Sequence (0040,0100)

›Scheduled Station AE Title (0040,0001) U S

›Scheduled Procedure Step Start Date (0040,0002) U CDT

›Scheduled Procedure Step Start Time (0040,0003) U CDT

›Modality (0008,0060) U S

Patient's Name (0010,0010) U S *

Patient ID (0010,0020) U S *

Issuer of Patient ID (0010,0021) U S *




The following table contains the supported return keys:

Table 4-29 Modality Worklist - Return Keys

Description Tag

Scheduled Procedure Step Sequence (0040,0100)

>Scheduled Station AE Title (0040,0001)

>Scheduled Procedure Step Start Date (0040,0002)

>Scheduled Procedure Step Start Time (0040,0003)

>Modality (0008,0060)



>Scheduled Performing Physician's Name (0040,0006)

>Scheduled Procedure Step Description (0040,0007)

> Scheduled Protocol Code Sequence (0040,0008)

>> Code Meaning (0008,0104)

>> Code Value (0008,0100)

>> Coding Scheme Designator (0008,0102)

>> Coding Scheme Version (0008,0103)

>Scheduled Procedure Step ID (0040,0009)

Requested Procedure ID (0040,1001)

Requested Procedure Comments (0040,1400)

Requested Procedure Description (0032,1060)

Study Instance UID (0020,000D)

Study Date (=Scheduled Procedure Step Start Date) (0008,0020)

Study Time (=Scheduled Procedure Step Start Time) (0008,0030)

Accession Number (0008,0050)

Requesting Physician (0032,1032)

Requested Procedure Code Sequence (=Scheduled Protocol Code Sequence)

(0032,1064)

> Code Meaning (0008,0104)

> Code Value (0008,0100)

> Coding Scheme Designator (0008,0102)

> Coding Scheme Version (0008,0103)

Referring Physician’s Name (0008,0090)

Patient's Name (0010,0010)

Patient ID (0010,0020)

Issuer of Patient ID (0010,0021)

Patient's Birth Date (0010,0030)

Patient's Sex (0010,0040)

Other Patient IDs (0010,1000)

Ethnic Group (0010,2160)

The FORUM MWL AE returns one of the following status codes in a C-FIND response:

Table 4-30 Modality Worklist C-FIND response status codes

Service Status

Further Meaning Error Code

Behavior


0118 If a SOP Class is used, which was not negotiated.


0211 Unrecognized value in command field

Failed Processing Failure

0110 Unexpected internal errors

Unable To Process C000 Unexpected internal errors



Cancel FE00 The original requester canceled this operation.

Pending Pending FF00 All optional keys are supported in the same manner as required keys.

Warning Too Many Results C001 If the received request leads to more than 1000 responses then these 1000 responses will be returned followed by this status.


FORUM assigns a different Study Instance UID to each Requested Procedure.

FORUM supports only one Scheduled Procedure Step per Requested Procedure.

If the Scheduled Protocol Code Sequence (0040,0008) or the Requested Procedure Code Sequence (0032,1064) is requested as a return key, and there are no items in a response, then this sequence will be returned without items instead of being removed.

MWL entries (Scheduled Procedure Steps) are removed from the FORUM MWL AE as soon as the first SOP Instance with the Study Instance UID from the respective Requested Procedure is received.

Furthermore MWL entries (Scheduled Procedure Steps) which are created via the "Automatic Order Functionality" or via the EMR Gateway are removed from the FORUM MWL AE at midnight.

4.3 Network Interfaces

4.3.1 Physical Network Interface

The physical network interface is not visible for the instrument application. The instrument application uses the communication stack as offered by the Operating System.

4.3.2 Additional Protocols

Both IP addresses and host names are supported and get resolved. Else no additional protocols are supported.

4.3.3 IPv4 and IPv6 Support

FORUM is released only for IPv4.

4.4 Configuration Local application entity and remote application entity information can be configured with the Networking Configuration Tool. It is also possible to configure timeout, institution, and worklist item limit parameters via Application Software, configuration tool, and configuration file.

4.4.1 AE Title/Presentation Address Mapping

The mapping from AE Title to TCP/IP addresses and ports is configurable and is stored in the local database. Along with this mapping, the database stores those AE titles that are allowed to communicate with the FORUM AE and the FORUM MWL AE.

Local AE Titles 4.4.1.1

The IP is not configurable by the FORUM UI. The IP is administrated by the Operating System. The AE titles for the FORUM AE and the FORUM MWL AE are configurable. The FORUM application can be configured to use only one AE for all transactions. The default port number is 11119.

Remote AE Titles 4.4.1.2

The mapping of remote AE Titles to TCP/IP addresses and ports is configurable. FORUM supports a proprietary auto configuration for corresponding external DICOM devices. The number of AE Titles is



limited according to the available licenses. Two types of licenses are available to distinguished between connected "Zeiss Devices" and "3

rd Party Devices". In addition the user can configure whether the

respective remote AE title can act as Modality Worklist User.

4.4.2 Parameters

General Parameters 4.4.2.1

The general parameters are shared for associations to any of the configured AE.

Table 4-31 Configuration Parameters Table

Parameter Configurable (Yes/No) Default Value

Verification SCU/SCP Parameters

No specific configuration required.

The configuration of port number and Application Entity Title are part of the Local Application Entity setup (see 4.4.1.1 Local AE Titles).

Modality Worklist SCP Parameters

Maximum Query Responses (Modality Worklist IM)

No

1000

Scheduled Station AE Title

Patient Root Q/R and Study Root Q/R SCP Parameters

Maximum Query Responses (Patient Root Q/R IM and Study Root Q/R IM)

No

5000

Extended Negotiation – relational query support negotiation

(Patient Root Q/R IM and Study Root Q/R IM)

No "Relational-queries" and "Date-time matching" are supported.

Storage SCP Parameters

No specific configuration required

The configuration of port number and Application Entity Title are part of the Local Application Entity setup (see 4.4.1.1 Local AE Titles).

FORUM Glaucoma Workplace Configuration 4.4.2.2

FORUM Glaucoma Workplace can be configured to create reports automatically. This configuration can be performed by the operator via GUI. Also some of the IOD Content is part of the configuration.

The automatic report creation is triggered when a DICOM Instance is stored in FORUM.

Parameter Configurable (Yes/No) Description

Default Value

Automatic Report Creation

Create Overview for 24-2/30-2 White Yes.

Creates a new Overview report for the patient if the stored IOD qualifies for 24-2/30-2 White

Disabled

Create Overview for 24-2/30-2 Blue-Yellow

Yes.

Creates a new Overview report for the patient if the stored IOD qualifies for 24-2/30-2 Blue-Yellow.

Disabled



Create Overview for 10-2 Yes.

Creates a new Overview report for the patient if the stored IOD qualifies for 10-2

Disabled

Create single exam reports. Yes.

Creates a single exam report, if the stored IOD qualifies for it.

Disabled

Create GPA Yes.

Creates a GPA report for the patient, if all necessary data is available. Which GPA is created, is set by: Automatically created GPA report type

Disabled

Automatically created GPA report type Yes.

Type of the created GPA Report, options are: GPA Summary , Full GPA, SFA GPA or GPA Last Three Follow-up.

GPA Summary

Create combined report Yes.

Creates a combined report, if all necessary data for the report creation is available

Disabled

Time span for creation of combined report (in days)

Yes.

Only if all data necessary for combined report creation is in this time span, a report will be created.

180 days

Create single exam reports for existing exams

Yes.

A single exam report for every IOD stored in FORUM that qualifies for report creation is created. Only one report is created, if a report for this IOD already exists, none is created.

Disabled

Data Export Option

Create OPV data format Yes.

For every IOD that is stored in FORUM and that qualifies for OPV, a OPV is created.

Disabled

Institution Settings

Institution Name Yes.

Used for the institution name in the DICOM Instances created by FORUM Glaucoma Workplace .

Empty



5 Media Interchange Media Interchange is not scope of this document since Media Interchange is not supported by FORUM.



6 Support of Character Sets

6.1 Accepted Character Sets Table 6-1 Supported Character Set

Supported Specific Character Set

Character Set Description Defined Term

US-ASCII

ISO-8859-1 ISO_IR 100

ISO-8859-2 ISO_IR 101

ISO-8859-3 ISO_IR 109

ISO-8859-4 ISO_IR 110

ISO-8859-5 ISO_IR 144

ISO-8859-6 ISO_IR 127

ISO-8859-7 ISO_IR 126

ISO-8859-8 ISO_IR 138

ISO-8859-9 ISO_IR 148

JIS_X0201 ISO_IR 13

TIS-620 ISO_IR 166

US-ASCII ISO 2022 IR 6

ISO-8859-1 ISO 2022 IR 100

ISO-8859-2 ISO 2022 IR 101

ISO-8859-3 ISO 2022 IR 109

ISO-8859-4 ISO 2022 IR 110

ISO-8859-5 ISO 2022 IR 144

ISO-8859-6 ISO 2022 IR 127

ISO-8859-7 ISO 2022 IR 126

ISO-8859-8 ISO 2022 IR 138

ISO-8859-9 ISO 2022 IR 148

JIS_X0201 ISO 2022 IR 13

TIS-620 ISO 2022 IR 166

JIS0208 ISO 2022 IR 87

JIS0212 ISO 2022 IR 159

cp949 ISO 2022 IR 149

UTF-8 ISO_IR 192

GB18030 GB18030

6.2 Returned Character Sets DICOM files will be returned as they are. In case of a modified DICOM file it will be changed to UTF-8 and will be returned with this character set.

No transcoding will be done with one exception: UTF-8 files will be returned as "ISO_IR 100" if the C-MOVE destination AE title contains the string "IR100".



7 Security FORUM accepts only associations from configured remote AE Titles.

Apart from that, the DICOM capabilities of the FORUM Application Software does not support any specific security measures.

It is assumed that FORUM is used within a secured environment. It is assumed that a secured environment includes at a minimum:

Firewall or router protections to ensure that only approved external hosts have network access to FORUM.

Firewall or router protections to ensure that FORUM only has network access to approved external hosts and services.

Any communication with external hosts and services outside the locally secured environment use appropriate secure network channels (e.g. such as a Virtual Private Network (VPN))

Other network security procedures such as automated intrusion detection may be appropriate in some environments. Additional security features may be established by the local security policy and are beyond the scope of this conformance statement.



8 Annexes

8.1 IOD Contents

8.1.1 Created SOP Instance(s)

FORUM creates new instances for manually imported image or PDF files.

FORUM creates new instances for "Combined Reports" either automatically according to certain rules or manually triggered by the user.

The prefixes for the created UIDs are:

Study Instance UID: 1.2.276.0.75.2.5.30.25.1.

Series Instance UID: 1.2.276.0.75.2.5.30.25.2.

SOP Instance UID: 1.2.276.0.75.2.5.30.25.3.

Abbreviations used for presence of values:

VNAP Value Not Always Present (attribute sent zero length if no value is present) – Applicable for Type 2, 2C.

ANAP Attribute is not always present – Applicable for Type 3

ALWAYS Attribute is always present with a value – Applicable for Type 1

EMPTY Attribute is sent without a value – Applicable for Type 2

Abbreviations used for sources of data:

USER The attribute value source is from User input

AUTO The attribute value is generated automatically

MWL, MPPS, etc. The attribute value is the same as the value received using a DICOM service such as Modality Worklist, Modality Performed Procedure Step, etc.

CONFIG The attribute value source is a configurable parameter

ACQUISITION The sources of data come from data acquisition process. Include Image and data relate to Image

ANALYSIS The sources of data come from data generate by application or add/edit/update by user when images are analyzed.

SRC The attribute value is the same as the value in the selected patient or source dataset

For FORUM Glaucoma Workplace generated IODs the following is valid: The attribute value is the same as in the DICOM IOD which contains the source raw data set of the report. In case of multiple sources, the latest source is used.

SRC/AUTO The attribute value is the same as in the DICOM IOD which contains the raw data source of the report, if the source was a single exam. If the sources are multiple exams (multi exam reports), this value is generated automatically.



Abbreviations used for Type:

PE Private Extension

Secondary Capture Image Information Object Definition – File Import 8.1.1.1

In FORUM the user has the possibility to import image files for a selected patient. Supported image files are:

JPEG

BMP (only 8 Bit and 24 Bit)

TIFF (only with three samples per pixel/24 Bit)

FORUM creates the following DICOM file as a result of this import operation.

IE Module Presence of Module

Patient Patient ALWAYS

Study General Study ALWAYS

Series General Series ALWAYS

Equipment General Equipment ALWAYS

SC Equipment ALWAYS

Image General Image ALWAYS

Image Pixel ALWAYS

Sop Common ALWAYS

Table 8-1 Secondary Capture Image IOD – File Import – File Meta Information

Tag Type VR Name Content (Description) PoV Source

(0002,0001) 1 OB File Meta Information Version

00\01 ALWAYS AUTO

(0002,0002) 1 UI Media Storage SOP Class UID

1.2.840.10008.5.1.4.1.1.7 (Secondary Capture Image Storage)

ALWAYS AUTO

(0002,0003) 1 UI Media Storage SOP Instance UID

The SOP instance UID has a prefix of 1.2.276.0.75.2.5.30.25.3.

ALWAYS AUTO

(0002,0010) 1 UI Transfer Syntax UID 1.2.840.10008.1.2.4.50 (JPEG Baseline Process 1, for imported JPG and TIFF Files)

1.2.840.10008.1.2 (Implicit VR Little Endian, for imported BMP Files)

ALWAYS AUTO

(0002,0012) 1 UI Implementation Class UID 1.2.276.0.75.2.5.30 ALWAYS AUTO

(0002,0013) 3 SH Implementation Version Name

FORUM 3.3 ALWAYS AUTO

Table 8-2 Secondary Capture Image IOD – File Import – Module "Patient"


(0010,0010) 2 PN Patient’s Name Name of selected patient. VNAP SRC

(0010,0020) 2 LO Patient ID Patient ID of selected patient. ALWAYS SRC



(0010,0021) 3 LO Issuer of Patient ID Issuer of Patient ID of selected patient.

VNAP SRC

(0010,0030) 2 DA Patient’s Birth Date Birth Date of selected patient. VNAP SRC

(0010,0040) 2 CS Patient’s Sex Gender of selected patient. VNAP SRC

(0010,1000) 3 LO Other Patient IDs Other Patient IDs of selected patient.

VNAP SRC

(0010,2160) 3 SH Ethnic Group Ethnic Group of selected patient.

VNAP SRC

(0010,4000) 3 LT Patient Comments Patient Comments of selected patient.

VNAP SRC

Table 8-3 Secondary Capture Image IOD – File Import – Module “General Study”


(0008,0020) 2 DA Study Date The value entered by the user via GUI as Content Date or if empty the current date.

ALWAYS USER or AUTO

(0008,0030) 2 TM Study Time The value entered by the user via GUI as Content Time or if empty the current date.

ALWAYS USER or AUTO

(0008,0050) 2 SH Accession Number Value entered by the user via GUI. Default: empty.

VNAP USER

(0008,0090) 2 PN Referring Physician’s Name

Value entered by the user via GUI (last name, first name, prefix). Default: empty.

VNAP USER

(0020,000D) 1 UI Study Instance UID The study instance UID has a prefix of 1.2.276.0.75.2.5.30.25.1.

ALWAYS AUTO

(0020,0010) 2 SH Study ID 1 ALWAYS AUTO

Table 8-4 Secondary Capture Image IOD – File Import – Module “General Series”


(0008,0021) 3 DA Series Date Current date ALWAYS AUTO

(0008,0031) 3 TM Series Time Current time ALWAYS AUTO

(0008,0060) 1 CS Modality Possible values : AR, DOC, GM, KER, LEN, OAM, OP, OPM, OPT, OPV, OT, SRF, US, VA, XC

ALWAYS USER

(0008,103E) 3 LO Series Description EMPTY

(0020,000E) 1 UI Series Instance UID The Series instance UID has a prefix of 1.2.276.0.75.2.5.30.25.2.

ALWAYS AUTO

(0020,0011) 2 IS Series Number 1 ALWAYS AUTO

(0020,0060) 2C CS Laterality Optional. The value is selectable from a drop-down list. Possible values are: “L”, “R”, “B”.

ANAP USER

Table 8-5 Secondary Capture Image IOD – File Import – Module “General Equipment”


(0008,0070) 2 LO Manufacturer EMPTY



(0008,0080) 3 LO Institution Name EMPTY

(0008,1010) 3 SH Station Name EMPTY

(0018,1020) 3 LO Software Version(s) EMPTY

(0008,1090) 3 LO Manufacturer’s Model Name EMPTY

Table 8-6 Secondary Capture Image IOD – File Import – Module “SC Equipment“


(0008,0064) 1 CS Conversion Type DI ALWAYS AUTO

Table 8-7 Secondary Capture Image IOD – File Import – Module “General Image”


(0008,0008) 3 CS Image Type ORIGINAL\PRIMARY

ORIGINAL\PRIMARY\\(+ user input, possible values: "COLOR", "REDFREE", "RED", "BLUE", "FA", "ICG")

ALWAYS AUTO

and

USER

(0008,0023) 2C DA Content Date The value entered by the user via GUI as Content Date or if empty the current date.

ALWAYS USER or AUTO

(0008,002A) 3 DT Acquisition DateTime The value entered by the user via GUI as Acquisition Date and Time or if empty the current date and time.

ALWAYS USER or AUTO

(0008,0033) 2C TM Content Time The value entered by the user via GUI as Content Time or if empty the current date.

ALWAYS USER or AUTO

(0022,000C) PE FL Horizontal Field of View Value entered by the user via GUI. Default value is empty.

ANAP USER

(0020,0013) 2 IS Instance Number 1 ALWAYS AUTO

(0020,0020) 2C CS Patient Orientation EMPTY

(0020,4000) 3 LT Image Comments Value entered by the user via GUI. Default value is empty.

VNAP USER

(0028,0301) 3 CS Burned In Annotation Value entered by the user via GUI. , Possible values: "YES", "NO"

ALWAYS USER

(0028,2110) 3 CS Lossy Image Compression 01 (set for JPEG Baseline only) ANAP AUTO

Table 8-8 Secondary Capture Image IOD – File Import – Module "Image Pixel"


(0028,0002) 1 US Samples per Pixel Value taken from the imported image

ALWAYS SRC

(0028,0004) 1 CS Photometric Interpretation YBR_FULL_422 (for color JPG)

RGB (for other color images)

MONOCHROME2 (for monochrome images)

ALWAYS AUTO

(0028,0006) 1C US Planar Configuration 0 ALWAYS AUTO

(0028,0008) PE IS Number of Frames 1 (import of multipage files not supported by FORUM)

ALWAYS AUTO



(0028,0010) 1 US Rows Value taken from the imported image

ALWAYS SRC

(0028,0011) 1 US Columns Value taken from the imported image

ALWAYS SRC

(0028,0100) 1 US Bits Allocated 8 ALWAYS AUTO

(0028,0101) 1 US Bits Stored 8 ALWAYS AUTO

(0028,0102) 1 US High Bit 7 ALWAYS AUTO

(0028,0103) 1 US Pixel Representation 0 ALWAYS AUTO

(7FE0,0010) 1C OB Pixel Data Data taken from the imported image.

ALWAYS SRC

Table 8-9 Secondary Capture Image IOD – File Import – Module "SOP Common"


(0008,0005) 1C CS Specific Character Set ISO_IR 192 ALWAYS

(0008,0012) 3 DA Instance Creation Date Current date ALWAYS USER or AUTO

(0008,0013) 3 TM Instance Creation Time Current time ALWAYS USER or AUTO

(0008,0016) 1 UI SOP Class UID 1.2.840.10008.5.1.4.1.1.7 (Secondary Capture Image Storage)

ALWAYS AUTO

(0008,0018) 1 UI SOP Instance UID The SOP instance UID has a prefix of 1.2.276.0.75.2.5.30.25.3.

ALWAYS AUTO


Encapsulated PDF Information Object Defintion 8.1.1.2

In FORUM the user is able to import PDF files for a selected patient. FORUM creates the following DICOM file as a result of this import operation.




Series Encapsulated Document Series ALWAYS


SC Equipment ALWAYS

Encapsulated Document

Encapsulated Document ALWAYS

Sop Common ALWAYS

Table 8-10 Encapsulated PDF IOD - "File Meta Information”



00\01 ALWAYS AUTO


1.2.840.10008.5.1.4.1.1.104.1 (Encapsulated PDF Storage)

ALWAYS AUTO

(0002,0003) 1 UI Media Storage SOP The SOP instance UID has a ALWAYS AUTO



Instance UID prefix of 1.2.276.0.75.2.5.30.25.3.

(0002,0010) 1 UI Transfer Syntax UID 1.2.840.10008.1.2 (Implicit VR Little Endian)

ALWAYS AUTO




Table 8-11 Encapsulated PDF IOD - Module “Patient”



(0010,0020) 2 LO Patient ID Patient ID of selected patient. ALWAYS SRC

(0010,0021) 3

LO Issuer of Patient ID Issuer of Patient ID of selected patient.

VNAP SRC

(0010,0030) 2 DA Patient’s Birth Date Birth Date of selected patient. VNAP SRC



VNAP SRC


VNAP SRC


VNAP SRC

Table 8-12 Encapsulated PDF IOD - Module “General Study”


(0008,0020) 2 DA Study Date The value entered by the user via GUI as Content Date or if empty the current date.

ALWAYS USER or AUTO

(0008,0030) 2 TM Study Time The value entered by the user via GUI as Content Time or if empty the current date.

ALWAYS USER or AUTO

(0008,0050) 2 SH Accession Number Value entered by the user via GUI. Default: empty

VNAP USER

(0008,0090) 2 PN Referring Physician’s Name Value entered by the user via GUI (last name, first name and prefix). Default: empty

VNAP USER

(0020,000D) 1 UI Study Instance UID The study instance UID has a prefix of: 1.2.276.0.75.2.5.30.25.1.

ALWAYS AUTO


Table 8-13 Encapsulated PDF IOD - Module “Encapsulated Document Series”


(0008,0021) PE DA Series Date Current date ALWAYS AUTO

(0008,0031) PE TM Series Time Current time ALWAYS AUTO

(0008,0060) 1 CS Modality Possible values : AR, DOC, GM, KER, LEN, OAM, OP, OPM, OPT, OPV, OT, SRF, US, VA, XC

ALWAYS USER

(0008,103E) 3 LO Series Description EMPTY



(0020,000E) 1 UI Series Instance UID The Series instance UID has a prefix of 1.2.276.0.75.2.5.30.25.2.

ALWAYS AUTO


Table 8-14 Encapsulated PDF IOD - Module “General Equipment”


(0008,0070) 2 LO Manufacturer EMPTY

(0008,0080) 3 LO Institution Name EMPTY

(0008,1010) 3 SH Station Name EMPTY

(0018,1020) 3 LO Software Version(s) EMPTY

(0008,1090) 3 LO Manufacturer’s Model Name EMPTY

Table 8-15 Encapsulated PDF IOD - Module “SC Equipment”


(0008,0064) 1 CS Conversion Type DI ALWAYS AUTO

Table 8-16 Encapsulated PDF IOD - Module “Encapsulated Document“


(0008,0023) 2 DA Content Date The value entered by the user via GUI as Content Date or if empty the current date.

ALWAYS USER or AUTO

(0008,002A) 2 DT Acquisition DateTime The value entered by the user via GUI as Acquisition Date and Time or if empty the current date and time.

ALWAYS USER or AUTO

(0008,0033) 2 TM Content Time The value entered by the user via GUI as Content Time or if empty the current date.

ALWAYS USER or AUTO

(0020,0013) 1 IS Instance Number 1 ALWAYS

(0020,0062) 3 CS Image Laterality Optional. The value is selectable from a drop-down list. Possible values are: “L”, “R”, “B”.

ANAP USER

(0028,0301) 1 CS Burned In Annotation Value entered by the user via GUI. , Possible values: "YES", "NO".

ALWAYS USER

(0042,0010) 2 ST Document Title Value entered by the user in the field “PDF Document Title” or file name of the PDF which was choosen by the user for import.

ALWAYS USER or AUTO

(0040,A043) 2 SQ Concept Name Code Sequence

EMPTY

(0042,0011) 1 OB Encapsulated Document The bytes of the imported PDF document.

ALWAYS SRC

(0042,0012) 1 LO MIME Type of Encapsulated Document

application/pdf ALWAYS AUTO



Table 8-17 Encapsulated PDF IOD - Module “SOP Common”


(0008,0005) 1C CS Specific Character Set ISO_IR 192 ALWAYS AUTO

(0008,0012) 3 DA Instance Creation Date Current date ALWAYS AUTO

(0008,0013) 3 TM Instance Creation Time Current time ALWAYS AUTO

(0008,0016) 1 UI SOP Class UID 1.2.840.10008.5.1.4.1.1.104.1 (Encapsulated PDF Storage)

ALWAYS


ALWAYS AUTO

Combined Report: EPDF Information Object Definition 8.1.1.3

FORUM creates automatically or per user request a combined report from other suitable instances For a list of suitable instance please refer to the FORUM User Manual or the FORUM Online Help.




Series Encapsulated Document Series ALWAYS


SC Equipment ALWAYS

Encapsulated Document

Encapsulated Document ALWAYS

Sop Common ALWAYS

Table 8-18 Encapsulated PDF IOD – Combined Report - File Meta Information



00\01 ALWAYS AUTO



ALWAYS AUTO



ALWAYS AUTO

(0002,0010) 1 UI Transfer Syntax UID 1.2.840.10008.1.2 (Implicit VR Little Endian)

ALWAYS AUTO




Table 8-19 Encapsulated PDF IOD – Combined Report - Module “Patient”



(0010,0020) 2 LO Patient ID Patient ID of selected patient.

VNAP SRC

(0010,0021) 3

LO Issuer of Patient ID Issuer of Patient ID of selected patient.

VNAP SRC



(0010,0030) 2 DA Patient’s Birth Date Birth Date of selected patient.

VNAP SRC



VNAP SRC


VNAP SRC


VNAP SRC

Table 8-20 Encapsulated PDF IOD – Combined Report - Module “General Study”


(0008,0020) 2 DA Study Date The value is set to the date at creation of the report.

ALWAYS AUTO

(0008,0030) 2 TM Study Time The value is set to the time at creation of the report.

ALWAYS AUTO

(0008,0050) 2 SH Accession Number The attribute is always empty. EMPTY

(0008,0090) 2 PN Referring Physician’s Name

The attribute is always empty. EMPTY

(0020,000D) 1 UI Study Instance UID The study instance uid has a prefix of 1.2.276.0.75.2.5.30.25.1.

ALWAYS AUTO


Table 8-21 Encapsulated PDF IOD – Combined Report - Module “Encapsulated Document Series”


(0008,0021) PE DA Series Date The value is set to the date at creation of the report.

ALWAYS AUTO

(0008,0031) PE TM Series Time The value is set to the time at creation of the report.

ALWAYS AUTO

(0008,0060) 1 CS Modality DOC ALWAYS AUTO

(0008,103E) 1 LO Series Description "HFA Visual Field and Cirrus RNFL Combined Report" or "HFA Visual Field and Cirrus ONH Combined Report"

ALWAYS AUTO

(0020,000E) 1 UI Series Instance UID The series instance uid has a prefix of 1.2.276.0.75.2.5.30.25.2.

ALWAYS AUTO


Table 8-22 Encapsulated PDF IOD – Combined Report - Module “General Equipment”


(0008,0070) 2 LO Manufacturer Carl Zeiss Meditec ALWAYS AUTO

(0008,0080) 3 LO Institution Name The value is taken from the most recent source instance regarding Acquisition Date Time.

VNAP AUTO

(0008,1010) 3 SH Station Name The value is taken from the most recent source instance regarding Acquisition Date Time.

VNAP AUTO

(0018,1020) 3 LO Software Version(s) Software Version including ALWAYS AUTO



patch and build level.

(0008,1090) 3 LO Manufacturer’s Model Name FORUM ALWAYS AUTO

Table 8-23 Encapsulated PDF IOD – Combined Report - Module “SC Equipment”


(0008,0064) 1 CS Conversion Type SYN ALWAYS AUTO

Table 8-24 Encapsulated PDF IOD – Combined Report - Module “Encapsulated Document”


(0008,0023) 2 DA Content Date The value is set to the date at creation of the report.

ALWAYS AUTO

(0008,002A) 2 DT Acquisition DateTime EMPTY

(0008,0033) 2 TM Content Time The value is set to the time at creation of the report.

ALWAYS AUTO


(0020,0062) 3 CS Image Laterality L, R, or B (depending on the selected source documents)

ALWAYS AUTO

(0028,0301) 1 CS Burned In Annotation YES ALWAYS AUTO

(0042,0010) 2 ST Document Title "HFA Visual Field and Cirrus RNFL Combined Report"

or

"HFA Visual Field and Cirrus ONH Combined Report"

ALWAYS AUTO


EMPTY

(0042,0011) 1 OB Encapsulated Document The bytes of the generated PDF document.

ALWAYS AUTO


application/pdf ALWAYS AUTO

(0042,0013) PE SQ Source Instance Sequence This Sequence references the source instances, from which this combined report was built. This sequence contains 2 or 3 items

ALWAYS AUTO

>(0008,1150) PE UI Referenced SOP Class UID 1.2.840.10008.5.1.4.1.1.104.1 (Encapsulated PDF Storage)

AUTO

>(0008,1155) PE UI Referenced SOP Instance UID

SOP Instance UID of the source document.

AUTO

Table 8-25 Encapsulated PDF IOD – Combined Report - Module “SOP Common”


(0008,0005) 1C CS Specific Character Set ISO_IR 192 ALWAYS AUTO

(0008,0012) 3 DA Instance Creation Date current date ALWAYS AUTO

(0008,0013) 3 TM Instance Creation Time current time ALWAYS AUTO

(0008,0016) 1 UI SOP Class UID 1.2.840.10008.5.1.4.1.1.104.1 (Encapsulated PDF Storage)

ALWAYS AUTO


ALWAYS AUTO



SOP Instances Created by FORUM Glaucoma Workplace 8.1.1.4

FORUM Glaucoma Workplace can generate visual field reports (OPV IODs), and reports that contain results from perimetry, optical coherence tomography and fundus photography (ePDF IODs).

In case new UIDs are created, they contain a constant prefix as follows:

Study Instance UID: 1.2.276.0.75.2.5.80.25.1

Series Instance UID: 1.2.276.0.75.2.5.80.25.2

SOP Instance UID: 1.2.276.0.75.2.5.80.25.3

8.1.1.4.1 Encapsulated PDF Information Object Defintion


Patient

Patient ALWAYS

ClinicalTrialSubject NEVER

Study

GeneralStudy ALWAYS

PatientStudy NEVER

ClinicalTrialStudy NEVER

Series

EncapsulatedDocumentSeries ALWAYS

ClinicalTrialSeries NEVER

CzmEncapsulatedPdfSeriesExtension ALWAYS

Equipment

GeneralEquipment ALWAYS

ScEquipment ALWAYS

EncapsulatedDocument

EncapsulatedDocument ALWAYS

SopCommon ALWAYS

CzmEncapsulatedPdfInstanceExtension ALWAYS

Table 8-26 Encapsulated PDF IOD – FGW – File Meta Information



00\01 ALWAYS AUTO



ALWAYS AUTO



ALWAYS AUTO

(0002,0010) 1 UI Transfer Syntax UID 1.2.840.10008.1.2.1 (Explicit VR Little Endian)

ALWAYS AUTO






(0002,0016) 3 AE Source Application Entity Title

Generated dynamically ALWAYS AUTO

Table 8-27 Encapsulated PDF IOD – FGW – Module "Patient"


(0010,0010) 2 PN Patient's Name Patient's full name from source raw data. ALWAYS SRC

(0010,0020) 2 LO Patient ID Patient ID from source raw data. ALWAYS SRC

(0010,0021) 3 LO Issuer of Patient ID

Issuer of Patient ID from source raw data. ANAP SRC

(0010,0030) 2 DA Patient's Birth Date

Birth date of the patient from source raw data.

ALWAYS SRC

(0010,0040) 2 CS Patient's Sex

Sex of the named patient from source raw data. Enumerated Values: M = male F = female O = other

Can be empty if empty in source raw data.

VNAP SRC

(0010,1000) 3 LO Other Patient IDs Other patient IDs from source raw data. ANAP SRC

(0010,2160) 3 SH Ethnic Group Ethnic group or race of the patient from source raw data.

ANAP SRC

(0010,4000) 3 LT Patient Comments

Patient Comments from source raw data. ANAP SRC

Table 8-28 Encapsulated PDF IOD – FGW – Module "General Study"


(0020,000D) 1 UI Study Instance UID

Study Instance UID from source

raw data for single exam report.

For study newly created, a new UID is generated with a UID prefix of 1.2.276.0.75.2.5.80.25.1

A new study is created, if the source of the report contains multiple DICOM instances.

ALWAYS SRC/AUTO

(0008,0020) 2 DA Study Date

Study Date from source raw data for single exam report.

Current date in case of multi exam reports.

ALWAYS SRC/AUTO

(0008,0030) 2 TM Study Time

Study Time from source raw data for single exam report.

Current time in case of multi exam reports.

ALWAYS SRC/AUTO

(0008,0090) 2 PN Referring Physician's Name

Name of the patient's referring physician from source raw data.

Can be empty if empty in the source raw data.

VNAP SRC

(0020,0010) 2 SH Study ID Study ID from source raw data for single exam report.

ALWAYS SRC/AUTO



(0008,0050) 2 SH Accession Number

Accession Number from source raw data.

Can be empty if empty in the source raw data.

VNAP SRC

(0008,1030) 3 LO Study Description

Study Description from source raw data for single field report.

For study newly created: The type of the generated report. (GPA, OVERVIEW, COMBINED_REPORT, STHRESHOLD_OU)

ALWAYS SRC/AUTO

(0008,1032) 3 SQ Procedure Code Sequence

Procedure Code Sequence from raw source data.

ANAP SRC

Table 8-29 Encapsulated PDF IOD – FGW – Module "Encapsulated Document Series"


(0008,0060) 1 CS Modality “OPV” for perimetry reports, “DOC” for combined reports.

ALWAYS AUTO

(0020,000E) 1 UI Series Instance UID

Newly created series instance UID with root:

1.2.276.0.75.2.5.80.25.2 ALWAYS AUTO

(0020,0011) 1 IS Series Number

Newly created and set to “1”. ALWAYS AUTO

(0008,103E) 3 LO Series Description

Name of the report: SFA, GPA, OVERVIEW, COMBINED_REPORT, STHRESHOLD, STHRESHOLD_OU, KINETIC_30, KINETIC_90, KINETIC_TABLE, NUMERIC, THREE_IN_ONE

ALWAYS AUTO

(0040,0275) 3 SQ Request Attributes Sequence

Request Attributes Sequence from source raw data.

Not available if not present in the source raw data.

ANAP SRC

>(0032,1060) 3 LO Requested Procedure Description

Requested Procedure Description from source raw data.

ANAP SRC

>(0040,0009) 1C SH Scheduled Procedure Step ID

Scheduled Procedure Step ID from source raw data.

ANAP SRC

>(0040,0007) 3 LO

Scheduled Procedure Step Description

Scheduled Procedure Step Description from source raw data.

ANAP SRC

>(0040,0008) 3 SQ Scheduled Protocol Code Sequence

Scheduled Protocol Code Sequence from source raw data.

ANAP SRC

(0040,0253) 3 SH Performed Procedure Step ID

Performed Procedure Step ID from raw source data for single exam report.

Newly created for multi exam reports.

ANAP SRC/

AUTO

(0040,0244) 3 DA Performed Procedure Step Start

Performed Procedure Step Start Date from raw source data for single field report.

Newly created for multi exam reports, set to

ANAP SRC/

AUTO



Date current date

(0040,0245) 3 TM

Performed Procedure Step Start Time

Performed Procedure Step Start Time from raw source data for single field report.

Newly created for multi exam reports, set to current time.

ANAP SRC/

AUTO

(0040,0254) 3 LO

Performed Procedure Step Description

Name of the report: SFA, GPA, OVERVIEW, COMBINED_REPORT, STHRESHOLD, STHRESHOLD_OU, KINETIC_30, KINETIC_90, KINETIC_TABLE, NUMERIC, THREE_IN_ONE

ALWAYS AUTO

Table 8-30 Encapsulated PDF IOD – FGW – Module "CZM Encapsulated PDF Series Extension"


(0020,0060) 3 CS Laterality Laterality from source raw data exam. Enumerated Values: R = right, L = left, B = both

ALWAYS SRC

Table 8-31 Encapsulated PDF IOD – FGW – Module "General Equipment"


(0008,0070) 2 LO Manufacturer Set to “Carl Zeiss Meditec” ALWAYS AUTO

(0008,0080) 3 LO Institution Name

Institution Name from the configuration. ANAP CONFIG

(0008,0081) 3 ST Institution Address

Institution Address from the configuration. ANAP CONFIG

(0008,1010) 3 SH Station Name Hostname of the machine used for creating the report. ALWAYS AUTO

(0008,1090) 3 LO Manufacturer's Model Name

Set to “Forum Glaucoma Workplace” ALWAYS AUTO

(0018,1020) 3 LO Software Version(s)

Multi valued:

1. FORUM Glaucoma Workplace version

2. … software version(s) from the source HFA raw data exam.

ALWAYS AUTO

Table 8-32 Encapsulated PDF IOD – FGW – Module "SC Equipment"


(0008,0064) 1 CS Conversion Type Set to: SYN = Synthetic Image ALWAYS AUTO

Table 8-33 Encapsulated PDF IOD – FGW – Module "Encapsulated Document"


(0020,0013) 1 IS Instance Number Set to 1. ALWAYS AUTO

(0008,0023) 2 DA Content Date Set to current date. ALWAYS AUTO

(0008,0033) 2 TM Content Time Set to current time. ALWAYS AUTO

(0008,002A) 2 DT Acquisition Datetime

Acquisition Datetime from raw data exam VNAP SRC

(0020,0062) 3 CS Image Laterality Laterality from source raw data exam. Enumerated Values: R = right, L = left, B = both.

ALWAYS SRC



(0028,0301) 1 CS Burned In Annotation

Set to “YES” ALWAYS AUTO

(0042,0013) 1C SQ Source Instance Sequence

Contains the UIDs from all source documents. Minimum one sequence item.

ALWAYS AUTO

>(0008,1150) 1 UI Referenced SOP Class UID

SOP Class UID from the source data. ALWAYS AUTO

>(0008,1155) 1 UI Referenced SOP Instance UID

SOP Instance UID from the source data. ALWAYS AUTO

(0042,0010) 2 ST Document Title

Name of the report.: SFA, GPA, OVERVIEW, COMBINED_REPORT, STHRESHOLD, STHRESHOLD_OU, KINETIC_30, KINETIC_90, KINETIC_TABLE, NUMERIC, THREE_IN_ONE

ALWAYS AUTO


This sequence is always empty. EMPTY


Set to “application/pdf” ALWAYS AUTO

(0042,0011) 1 OB Encapsulated Document

Encapsulated Document stream, containing the pdf report.

ALWAYS ANALYSIS

Table 8-34 Encapsulated PDF IOD – FGW – Module "SOP Common"


(0008,0016) 1 UI SOP Class UID Set to: “1.2.840.10008.5.1.4.1.1.104.1” ALWAYS AUTO

(0008,0018) 1 UI SOP Instance UID

Newly created with root: 1.2.276.0.75.2.5.80.25.3.

ALWAYS AUTO

(0008,0005) 1C CS Specific Character Set

Set to: “ISO_IR 192” (Unicode encoding) ALWAYS AUTO

(0008,0012) 3 DA Instance Creation Date

Current date. ALWAYS AUTO

(0008,0013) 3 TM Instance Creation Time

Current time ALWAYS AUTO

Table 8-35 Encapsulated PDF IOD – FGW – Module "SpecializedEncapsulatedDocument"


(22A1,xx01) 3 LO Document Type

The report type is set to:

“SFA” for SFA Reports

“GPA” for GPA Reports

“OVERVIEW” for Overview Reports

“COMBINED_REPORT” for Combined Reports

“STHRESHOLD” or “STHRESHOLD_OU” for Suprathreshold Reports

“KINETIC_30” or “KINETIC_90” or “KINETIC_TABLE” for Kinetic Reports

ALWAYS AUTO



“NUMERIC” for Numeric Reports

”THREE_IN_ONE” for Three-in-One Reports

Table 8-36 Encapsulated PDF IOD – FGW – Module “SollnSourceHfaExamEncapsulatedDocument”


(2501,xx07) 3 CS HFA Test Strategy

The CS value for the HFA Test Strategy from HFA Raw Data Exam

00=NONE, 01=FULL_THRESHOLD, 02=FASTPAC, 04=SITA_STANDARD, 05=FULL_FROM_PRIOR, 06=TWO_ZONE, 07=THREE_ZONE, 08=QUANTIFIED_DEFECTS, 10=OPTIMA, 11=SITA_FAST, 13=SITA_SWAP

ALWAYS SRC

(2501,xx08) 3 CS HFA Test Pattern

The CS value for the HFA Test Pattern from HFA Raw Data Exam

00=NONE, 01=CENTRAL_30_1_THRESHOLD_TEST, 02=CENTRAL_30_2_THRESHOLD_TEST, 03=PERIPHERAL_60_1_THRESHOLD_TEST, 04=PERIPHERAL_60_4_THRESHOLD_TEST, 05=TEMPORAL_CRESCENT_THRESHOLD_TEST, 06=NEUROLOGICAL_20_THRESHOLD_TEST, 07=NEUROLOGICAL_50_THRESHOLD_TEST, 08=MACULA_THRESHOLD_TEST, 09=NASAL_STEP_THRESHOLD_TEST, 10=CENTRAL_10_2_THRESHOLD_TEST, 11=CENTRAL_ARMALY_SCREENING_TEST, 12=FULL_FIELD_ARMALY_SCREENING_TEST, 13=CENTRAL_40_POINT_SCREENING_TEST, 14=PERIPHERAL_60_POINT_SCREENING_TEST, 15=CENTRAL_80_POINT_SCREENING_TEST, 16=CENTRAL_166_POINT_SCREENING_TEST, 17=FULL_FIELD_81_POINT_SCREENING_TEST, 18=FULL_FIELD_120_POINT_SCREENING_TEST, 19=FULL_FIELD_246_POINT_SCREENING_TEST, 20=AUTO_DIAGNOSTIC_TEST, 21=SUPERIOR_64_POINT_SCREENING_TEST, 22=NASAL_STEP_SCREENING_TEST, 23=CENTRAL_76_POINT_SCREENING_TEST, 24=CENTRAL_24_1_THRESHOLD_TEST, 25=CENTRAL_24_2_THRESHOLD_TEST, 26=BLINDENGELDGUTACHTEN, 27=FUEHRERSCHEINGUTACHTEN, 28=ESTERMAN_MONOCULAR, 29=ESTERMAN_BINOCULAR, 30=CENTRAL_64_POINT_SCREENING_TEST, 31=FULL_FIELD_12_POINT_QA_TEST, 32=USER_DEFINED_THRESHOLD_TEST, 33=USER_DEFINED_SCREENING_TEST, 34=KINETICTEST, 35=FULL_FIELD_135_POINT_SCREENING_TEST, 36=SUPERIOR_36_POINT_SCREENING_TEST, 83=CUSTOM_SCREENING_TEST, 84=CUSTOM_THRESHOLD_TEST

ALWAYS SRC

Table 8-37 Encapsulated PDF IOD – FGW – Module "SollnGpaEncapsulatedDocument"


(2501,xx00) 3 CS Report Type The CS value for the type of the GPA report ALWAYS AUTO



Values:

00=GpaSummary

01=SfaGpa

02=GpaComplete

03=GpaLastThreeFollowUp

04=GpaInteractive

with prefix GPA_

(2501,xx07) 3 CS HFA Test Strategy

The CS value for the HFA Test Strategy from HFA Raw Data Exam

00=NONE, 01=FULL_THRESHOLD, 02=FASTPAC, 04=SITA_STANDARD, 05=FULL_FROM_PRIOR, 06=TWO_ZONE, 07=THREE_ZONE, 08=QUANTIFIED_DEFECTS, 10=OPTIMA, 11=SITA_FAST, 13=SITA_SWAP

ALWAYS SRC

Table 8-38 Encapsulated PDF IOD – FGW – Module "SollnOverviewEncapsulatedDocument"


(2501,xx00) 3 CS Report Type

The CS value for the type of the Overview report:

Values:

00=OVERVIEW_10_2

01=OVERVIEW_24_2_30_2White

02=OVERVIEW_24_2_30_2BlueOnYellow

with prefix OVR_

ALWAYS AUTO

Table 8-39 Encapsulated PDF IOD – FGW – Module "SollnCombinedReportEncapsulatedDocument"



The CS value for the type of the Combined Report:

values:

00=OCTPerimetry_10_2

01=OCTPerimetry_24_2_30_2

with prefix OCT_CR_

ALWAYS AUTO

(2501,xx01) 3 CS Generated automatically

Information if the combined report creation was automatically (TRUE) or manually (FALSE) triggered

ALWAYS AUTO

(2501,xx02) 3 SQ Combined Report Source Instance Sequence

Sequence newly created by Forum Glaucoma Workplace, and filled with additional information about the source documents.

Values taken from the source Documents.

ALWAYS AUTO

› (2501,xx03)

1 UI Combined Report Source Instance UID

Taken from the source documents:

for each source document the value of element ‘SOP Instance UID’ (0008,0018)

ALWAYS SRC

› (2501,xx04)

1 UI Combined Report Source Class UID


for each source document the value of element ‘SOP Class UID’ (0008,0016)

ALWAYS SRC

› (2501,xx05)

1 CS Combined Report Source Laterality


for each source document the value of element Laterality (0020,0060

ALWAYS SRC

› 1 LO Combined Report Source IOD Meta

Taken from the source documents: ALWAYS SRC



(2501,xx06) Name for each source document the value of element ‘IOD Meta Name Info (2201,xx00) ’ which is written by the NIM during creation of the source document

Table 8-40 Encapsulated PDF IOD – FGW – Module “SollnReportTypeEncapsulatedDocument"

Applies to Kinetic, Three-in-One, Suprathreshold and Numeric Reports



The CS value for the type of the report:

STHRESHOLD, STHRESHOLD_OU, KINETIC_30, KINETIC_90, KINETIC_TABLE, NUMERIC, THREE_IN_ONE

ALWAYS AUTO

Table 8-41 Encapsulated PDF IOD – FGW – Module “CZM-HFA-Series"

Tag Type VR Name Description PoV Source

(7717,xx01) 1 LO Test Name

Name indicating test pattern and test type (Threshold, Screening, Kinetic)

The following test names are defined for HFA tests.

"Central 30-2 Threshold Test", "Peripheral 60-4 Threshold Test", "Macula Threshold Test", "Nasal Step Threshold Test", "Central 10-2 Threshold Test", "Central Armaly Screening Test", "Full Field Armaly Screening Test", "Central 40 Point Screening Test", "Peripheral 60 Point Screening Test", "Central 80 Point Screening Test", "Central 166 Point Screening Test", "Full Field 81 Point Screening Test", "Full Field 120 Point Screening Test", "Full Field 246 Point Screening Test", "Superior 64 Point Screening Test", "Nasal Step Screening Test", "Central 76 Point Screening Test", "Central 24-2 Threshold Test", "Blindengeldgutachten", "Fuehrerscheingutachten", "Esterman Monocular", "Esterman Binocular", "Central 64 Point Screening Test", "Full Field 12 Point QA Test", "User Defined Threshold Test", "User Defined Screening Test", "Kinetic Test", "Full Field 135 Point Screening Test", "Superior 36 Point Screening Test", "Custom Screening Test", "Custom Threshold Test"

ALWAYS SRC

(7717,xx02) 1 LO Test Strategy

Strategy (algorithm) used to perform the test.

The following test strategies are defined for HFA tests.

"Full Threshold", "FASTPAC", "SITA-Standard", "Full From Prior", "Two-Zone", "Three-Zone", "Quantify Defects", "Optima", "SITA-Fast", "Kinetic", "SITA-SWAP"

ALWAYS SRC

(7717,xx03) 1C CS Stimulus Goldmann size of the stimulus being ANAP SRC



Size presented.

NOTE: Not present if test strategy (7717,xx02) is Kinetic

Possible values are: I, II, III, IV, V, VI

(7717,xx04) 1C SH Stimulus Color

Color of stimulus being presented.


Possible values are: "White", "Red", "Green", "Blue"

ANAP SRC

(7717,xx05) 1C SH Background State

Indicates the color of background illumination used to perform the test.


Possible values are: "White", "Yellow"

ANAP SRC

(7717,xx06) 1C CS Foveal Result

Threshold result ("NOT TESTED", "SEEN", "NOT SEEN") of the test point at coordinates (0, 0) with respect to the fixation target.

NOTE: Present only if test is a Threshold Test

ANAP ANALYSIS

(7717,xx07) 1C LO Screening Mode

Indicates how starting stimulus intensities were chosen for screening tests

NOTE: Present only if test is a Screening Test

Possible values are: "Threshold Related", "Age Corrected", "Single Intensity"

ANAP SRC

(7717,xx08) 1C IS Fixation Trials

Number of stimulus presentations in the determined blind spot.

NOTE: Present only if Fixation Monitor is "Gaze / Blind Spot" or "Blind Spot"

ANAP ANALYSIS

(7717,xx09) 1C IS Fixation Errors

Number of stimulus presentations in the determined blind spot SEEN by the patient.

NOTE: Present only if Fixation Monitor is "Gaze / Blind Spot" or "Blind Spot"

ANAP ANALYSIS

(7717,xx10) 1C DS False Positive Percent

Estimated percent of False Positives.

NOTE: Present only if Test Strategy (7717,xx02) is SITA-Standard, SITA-Fast or SITA-SWAP.

ANAP ANALYSIS

(7717,xx11) 1C IS False Positive Trials

Number of false positive questions – stimulus is not actually presented, but time is allotted to it.

NOTE: Present only if test strategy (7717,xx02) is NOT SITA-Standard, SITA-Fast, SITA-SWAP or Kinetic

ANAP ANALYSIS



(7717,xx12) 1C IS False Positive Errors

Number of false positive questions the patient responds to.

Required if test strategy (7717,xx02) is NOT SITA-Standard, SITA-Fast, SITA-SWAP or Kinetic

ANAP ANALYSIS

(7717,xx13) 1C DS False Negative Percent

Estimated percent of False Negatives. NOTE: Present only if test strategy (7717,xx02) is SITA-Standard, SITA-Fast or SITA-SWAP

ANAP ANALYSIS

(7717,xx14) 1C IS False Negative Trials

Number of false negative questions – stimulus is presented several dB brighter than determined threshold for a given test point.

NOTE: Present only if test strategy (7717,xx02) is NOT SITA-Standard, SITA-Fast, SITA-SWAP or Kinetic

ANAP ANALYSIS

(7717,xx15) 1C IS False Negative Errors

Number of false negative questions the patient DOES NOT respond to.

NOTE: Present only if test strategy (7717,xx02) is NOT SITA-Standard, SITA-Fast, SITA-SWAP or Kinetic.

ANAP ANALYSIS

(7717,xx24) 1 LO Fixation Monitor

Method by which patient's fixation was monitored during testing.

Possible values are: "Gaze/Blind Spot", "Gaze Track", "Blind Spot", "OFF"

ALWAYS SRC

(7717,xx25) 1C LO Fixation Target

Location on the bowl where patient is to fixate. All test point locations are with respect to this location.

Possible values are: "Central", "Large Diamond", "Small Diamond", "Bottom LED"

ANAP SRC

(7717,xx26) 3 DS Pupil Diameter

Diameter of patient's pupil in mm.

NOTE: Not present for binocular tests.

ANAP SRC

(7717,xx27) 3 DS Sphere

Spherical corrective lens used during patient testing

NOTE: not present for binocular tests.

ANAP ANALYSIS

(7717,xx28) 3 DS Cylinder

Cylindrical corrective lens used during patient testing


ANAP ANALYSIS

(7717,xx29) 3 IS Axis

Meridian Cylinder correction is placed on.


ANAP ANALYSIS

(7717,xx30) 3 SH Visual Acuity

Patient's visual acuity

NOTE: Not present for binocular tests.

ANAP ANALYSIS

(7717,xx32) 1 DA Test Date Start date of most recent (key) exam. ALWAYS SRC

(7717,xx33) 1 TM Test Time Start time of most recent (key) exam ALWAYS SRC



Table 8-42 Encapsulated PDF IOD – FGW – Module "CZM-HFA-Analysis"


7717,xx16) 3 DS Mean Deviation

Weighted average deviation from the age corrected normal field, in dB.

ANAP ANALYSIS

(7717,xx17) 3 LO Mean Deviation Probability

Probability of normality for the Mean Deviation from Normal value, in percent.

Not present for 10-2 pattern tested with non-SITA test strategies.

ANAP ANALYSIS

(7717,xx18) 3 DS Pattern Standard Deviation

Weighted square root of loss variance, in dB.

ANAP ANALYSIS

(7717,xx19) 3 LO

Pattern Standard Deviation Probability

Probability of normality for the Pattern Standard Deviation from Normal value, in percent.

Not present for 10-2 pattern tested with non-SITA strategies

ANAP ANALYSIS

(7717,xx20) 3 DS Short-term Fluctuation

Average deviation of sensitivity for the repeated test locations, in dB. This is used to determine the consistency of the patient’s responses.

Not present for SITA test strategies.

ANAP ANALYSIS

(7717,xx21) 3 DS

Corrected Pattern Standard Deviation

Weighted square root of loss variance corrected for short term fluctuation, in dB.


ANAP ANALYSIS

(7717,xx22) 3 DS

Corrected Pattern Standard Deviation Probability

Probability of normality for the Corrected Pattern Standard Deviation from Normal value, in percent.


ANAP ANALYSIS

(7717,xx23) 3 LO Glaucoma Hemifield Test

A test of asymmetry between zones of the superior and inferior visual field. It is designed to be specific for defects due to glaucoma.

Not present if the test strategy (7717,xx02) is FASTPAC

ANAP ANALYSIS

(7717,xx31) 3 LO Short-term Fluctuation Probability

Probability of normality for the Pattern Deviation from Normal value, in percent.


ANAP ANALYSIS

(7717,xx34) 3 DS Visual Field Index

Index of a patient’s remaining visual field normalized for both age and generalized defect, in percent.

Not present if the test strategy (7717,xx02) is FASTPAC.

ANAP ANALYSIS

(7717,xx40) 3 SQ VFM Sequence

Visual Field Map. Containing items for the tested sections and the value of this section. ANAP ANALYSIS



Sequence shall contain 6 items if present.

Present only for SITA-Standard or SITA-Fast test strategy (7717,xx02) and 24-2 or 30-2 test pattern.

›

(7717,xx41) 1 IS

Section Number

1 - 6 ALWAYS AUTO

› (7717,xx42)

1 LO Section Value

Defined Terms:

"0" = Not Significant, "1" = P ‹ 5%, "2" = P ‹ 1%

ALWAYS ANALYSIS

8.1.1.4.2 Ophthalmic Visual Field Static Perimetry Measurement Information Object Definition


Patient

Patient ALWAYS

ClinicalTrialSubject NEVER

Study

GeneralStudy ALWAYS

PatientStudy NEVER

ClinicalTrialStudy NEVER

Series

GeneralSeries ALWAYS

ClinicalTrialSeries NEVER

VisualFieldStaticPerimetryMeasurementsSeries ALWAYS

Equipment

GeneralEquipment ALWAYS

EnhancedGeneralEquipment ALWAYS

Measurements

VisualFieldStaticPerimetryTestParameters ALWAYS

VisualFieldStaticPerimetryTestReliability ALWAYS

VisualFieldStaticPerimetryTestMeasurements ALWAYS

VisualFieldStaticPerimetryTestResults ALWAYS

OphthalmicPatientClinicalInformationAndTestLensParameters

CONDITIONAL

Available if the values are in the binary data of the source HFA raw data.

SopCommon ALWAYS

CzmOphthalmicVisualFieldStaticPerimetryMeasurementsExtension ALWAYS



Table 8-43 Ophthalmic Visual Field IOD – FGW – File Meta Information



00\01 ALWAYS AUTO


1.2.840.10008.5.1.4.1.1.80.1 (Ophthalmic Visual Field Static Perimetry Measurement)

ALWAYS AUTO



ALWAYS AUTO

(0002,0010) 1 UI Transfer Syntax UID 1.2.840.10008.1.2.1 (Explicit VR Little Endian)

ALWAYS AUTO




(0002,0016) 3 AE Source Application Entity Title

Generated dynamically ALWAYS AUTO

Table 8-44 Ophthalmic Visual Field IOD – FGW – Module "Patient"


(0010,0010) 2 PN Patient's Name Patient's full name from source HFA raw data.

ALWAYS SRC

(0010,0020) 2 LO Patient ID Primary hospital identification number or code for the patient from source HFA raw data.

ALWAYS SRC

(0010,0021) 3 LO Issuer of Patient ID

Identifier of the Assigning Authority (system, organization, agency, or department) that issued the Patient ID from source HFA raw data.

ANAP SRC

(0010,0030) 2 DA Patient's Birth Date Birth date of the patient from source HFA raw data.

VNAP SRC

(0010,0040) 2 CS Patient's Sex

Sex of the named patient from source HFA raw dataEnumerated Values: M = male F = female O = other

Can be empty if empty in source HFA raw data.

VNAP SRC

(0010,1000) 3 LO Other Patient IDs Other identification numbers or codes used to identify the patient from source HFA raw data.

ANAP SRC

(0010,2160) 3 SH Ethnic Group Ethnic group or race of the patient from source HFA raw data.

ANAP SRC

(0010,4000) 3 LT Patient Comments User-defined additional information about the patient from source HFA raw data.

ANAP SRC

Table 8-45 Ophthalmic Visual Field IOD – FGW – Module "General Study"


(0020,000D) 1 UI Study Instance UID Unique identifier for the Study, ALWAYS SRC



from source HFA raw data.

(0008,0020) 2 DA Study Date

Date the Study started, from source HFA raw data.


VNAP SRC

(0008,0030) 2 TM Study Time

Time the Study started, from source raw data.


VNAP SRC

(0008,0090) 2 PN Referring Physician's Name

Name of the patient's referring physician, from source HFA raw data.


VNAP SRC

(0020,0010) 2 SH Study ID

User or equipment generated Study identifier, from source HFA raw data.


VNAP SRC

(0008,0050) 2 SH Accession Number

A RIS generated number that identifies the order for the Study, from source HFA raw data.


VNAP SRC

(0008,1030) 3 LO Study Description

Institution-generated description or classification of the Study (component) performed from source HFA raw Data

ANAP SRC

(0008,1032) 3 SQ Procedure Code Sequence

A Sequence that conveys the type of procedure performed. One or more Items are permitted in this Sequence.

Procedure Code Sequence from source HFA raw data, including all items in the source.

ANAP SRC

Table 8-46 Ophthalmic Visual Field IOD – FGW – Module "General Series"


(0020,000E) 1 UI Series Instance UID

Unique identifier of the Series.

Newly created with root: 1.2.276.0.75.2.5.80.25.2

ALWAYS AUTO

(0020,0011) 2 IS Series Number Set to: “1” ALWAYS AUTO

(0020,0060) 2C CS Laterality Laterality from source HFA raw data. ALWAYS SRC

(0018,1030) 3 LO Protocol Name Protocol Name from source HFA raw data. ANAP SRC

(0008,103E) 3 LO Series Description

Set to “OPV” ALWAYS AUTO



Table 8-47 Ophthalmic Visual Field IOD – FGW – Module "Visual Field Static Perimetry Measurements Series"


(0008,0060) 1 CS Modality Set to: “OPV” ALWAYS AUTO

(0040,0275) 3 SQ Request Attributes Sequence

Sequence that contains attributes from the Imaging Service Request. One or more Items are permitted in this sequence.

The values are from the source HFA raw data. Available if the sequence is in the source.

ANAP SRC

>(0040,1001) 1C SH Requested Procedure ID

Requested Procedure ID from source HFA raw data.

ANAP SRC

>(0032,1060) 3 LO Requested Procedure Description

Requested Procedure from source HFA raw data.

ANAP SRC

>(0040,0009) 1C SH Scheduled Procedure Step ID

Scheduled Procedure Step ID from source HFA raw data.

ANAP SRC

>(0040,0007) 3 LO Scheduled Procedure Step Description

Scheduled Procedure Step Description from source HFA raw data

ANAP SRC

>(0040,0008) 3 SQ Scheduled Protocol Code Sequence

Scheduled Protocol Code Sequence from source HFA raw data.

ANAP SRC

(0040,0253) 3 SH Performed Procedure Step ID

Performed Procedure Step ID from source HFA raw data.

ANAP SRC

(0040,0244) 3 DA Performed Procedure Step Start Date

Date on which the Performed Procedure Step started, from source HFA raw data..

ANAP SRC

(0040,0245) 3 TM Performed Procedure Step Start Time

Time on which the Performed Procedure Step started, from source HFA raw data.

ANAP SRC

(0040,0254) 3 LO Performed Procedure Step Description

Set to: “OPV”. ALWAYS AUTO

(0040,0260) 3 SQ Performed Protocol Code Sequence

Sequence describing the Protocol performed for this Procedure Step. Contains sequence items for Test-Pattern and Test-Strategy from RAW Data Exam. Including Elements, from extended ContextIDs 4250 and 4251: - Code Value - Code Meaning - Coding Scheme Designator - Coding Scheme Version - only available if CZM Extension.

See chapter 8.3 for details.

ALWAYS AUTO



Table 8-48 Ophthalmic Visual Field IOD – FGW – Module "General Equipment"


(0008,0080) 3 LO Institution Name

Institution Name from FORUM Glaucoma Workplace configuration.

ANAP CONFIG

(0008,1010) 3 SH Station Name

User defined name identifying the machine that produced the composite instances.

Hostname of the machine used for creating the OPV.

ALWAYS AUTO

Table 8-49 Ophthalmic Visual Field IOD – FGW – Module "Enhanced General Equipment"


(0008,0070) 1 LO Manufacturer Set to: “Carl Zeiss Meditec” ALWAYS AUTO

(0008,1090) 1 LO Manufacturer's Model Name

Set to: “FORUM Glaucoma Workplace” ALWAYS AUTO

(0018,1000) 1 LO Device Serial Number

Device serial number from source HFA raw data.. If empty, set to: "not available"

ALWAYS SRC

(0018,1020) 1 LO Software Version(s)

Multi valued:

1. FORUM Glaucoma Workplace version (2.0)

2. … software version(s) from the source HFA raw data exam.

ALWAYS AUTO

Table 8-50 Ophthalmic Visual Field IOD – FGW – Module "Visual Field Static Perimetry Test Parameters"


(0024,0010) 1 FL Visual Field Horizontal Extent

The maximum horizontal angular subtend (diameter or width) of the tested visual field, in degrees, extracted from the binary data in the source HFA raw data.

AUTO ANALYSIS

(0024,0011) 1 FL Visual Field Vertical Extent

The maximum vertical angular subtend (diameter or height) of the tested visual field, in degrees, extracted from the binary data in the source HFA raw data.

AUTO ANALYSIS

(0024,0012) 1 CS Visual Field Shape

Always set to “CIRCLE” AUTO AUTO

(0024,0016) 1C SQ Screening Test Mode Code Sequence

The values in this CS are extracted from the source HFA raw data. Only present if the test is a screening test.

ANAP ANALYSIS

>(0008,0100) 1 SH Code Value Threshold Related (111839), Age Corrected (111838), Single Luminance (111840)

ALWAYS ANALYSIS

>(0008,0102) 1 SH Coding Scheme Designator

Set to “DCM” ALWAYS AUTO

>(0008,0104) 1 LO Code Meaning “Threshold Related”, “Age Corrected” or “Single Luminance”

ALWAYS ANALYSIS

(0024,0018) 1 FL Maximum Stimulus Luminance

Maximum luminance of stimulus, in candelas per square meter (cd/m²). Calculated from values in the binary data in the source HFA raw data.

ALWAYS ANALYSIS

(0024,0020) 1 FL Background Luminance

Background luminance of the device, in candelas per square meter (cd/m²).Note: This

ALWAYS ANALYSIS



value is easily convertible to apostilb, which is used only in perimetry and is not a standardized unit.

Calculated from binary data in the source HFA raw data.

(0024,0021) 1 SQ Stimulus Color Code Sequence

Color of light stimulus presented to the patient. Only a single Item shall be included in this sequence.

Extracted from binary data in the source HFA raw data.

ALWAYS AUTO

>(0008,0100) 1 SH Code Value

Possible values are:

“G-A12B” (White)

“G-A11A” (Red)

“G-A12E” (Green)

“G-A11F” (Blue)

ALWAYS ANALYSIS


Set to “SRT” ALWAYS AUTO

>(0008,0104) 1 LO Code Meaning The according color:

“WHITE”,”RED”,”GREEN”,”BLUE” ALWAYS ANALYSIS

(0024,0024) 1 SQ

Background Illumination Color Code Sequence

Color of the background illumination of the visual field device. Only a single Item shall be included in this sequence.


ALWAYS AUTO

>(0008,0100) 1 SH Code Value

Possible values are:

“G-A11D” (Yellow)

“G-A12B” (White)

ALWAYS ANALYSIS


Set to “SRT” ALWAYS AUTO

>(0008,0104) 1 LO Code Meaning The according color:

“WHITE”,”YELLOW” ALWAYS ANALYSIS

(0024,0025) 1 FL Stimulus Area

A calculated value of the surface area of the Goldmann stimulus used in the test.


ALWAYS ANALYSIS

(0024,0028) 1 FL Stimulus Presentation Time

The duration of time that a light stimulus is presented to a patient per each individual test point, in milliseconds. Note: This time is the same for each stimulus presentation.

Set to: 500ms for Estermann tests, 200 for all others.

The information if the test is an Estermann is extracted from binary data in the source HFA raw data.

ALWAYS ANALYSIS



Table 8-51 Ophthalmic Visual Field IOD – FGW – Module "Visual Field Static Perimetry Test Reliability"


(0024,0032) 1 SQ Fixation Sequence

The patient’s gaze stability information during the visual field test.

Extracted from binary data in the source HFA raw data

ALWAYS AUTO

>(0024,0033) 1 SQ Fixation Monitoring Code Sequence

The device strategy used to monitor the patient's fixation.


ALWAYS AUTO

>>(0008,0100) 1 SH Code Value

Set to:

111844 for Blind Spot Monitoring

111843 for Automated Optical

R-40775 for NONE

ALWAYS ANALYSIS

>>(0008,0102) 1 SH Coding Scheme Designator

“DCM”, “SRT” for NONE ALWAYS ANALYSIS

>>(0008,0104) 1 LO Code Meaning Set to: Blind Spot Monitoring, Automated Optical or NONE.

ALWAYS ANALYSIS

>(0024,0035) 1C US Fixation Checked Quantity

The number of times that the patient’s gaze fixation is checked. Required if Fixation Monitoring Code Sequence (0024,0033) contains an item with the value (111844, DCM, "Blind Spot Monitoring") .


ANAP ANALYSIS

>(0024,0036) 1C US Patient Not Properly Fixated Quantity

The number of times the patient’s gaze is not properly fixated. Required if Fixation Monitoring Code Sequence (0024,0033) contains an item with the value (111844, DCM, "Blind Spot Monitoring") .


ANAP ANALYSIS

>(0024,0039) 1 CS Excessive Fixation Losses Data Flag

“YES” if blind spot monitoring is enabled, “NO” otherwise.


ALWAYS ANALYSIS

>(0024,0040) 1C CS Excessive Fixation Losses

The number of fixation losses is outside of implementation-specific limits. YES if losses > = 20%, NO otherwise.

Condition: If Excessive Fixation Losses Data Flag is YES.


ANAP ANALYSIS

(0024,0034) 1 SQ Visual Field Catch Trial Sequence

The reliability of the patient’s responses to the visual field test.


ALWAYS AUTO



>(0024,0055) 1 CS Catch Trials Data Flag

Whether catch trials data were performed. Enumerated Values: YES NO.

Extracted from binary data in the source HFA raw data source

ALWAYS ANALYSIS

>(0024,0048) 1C US Negative Catch Trials Quantity

Total number of times the patient’s visual attention was tested using stimuli brighter than previously seen luminance (negative catch trials).

Required if Catch Trials Data Flag (0024,0055) is YES

Extracted from binary data in the source HFA raw data..

ANAP ANALYSIS

>(0024,0050) 1C US False Negatives Quantity

Total number of stimuli that were not seen by the patient but were previously seen at a lower luminance earlier in the visual field test (false negatives).

Required if Catch Trials Data Flag (0024,0055) is YES.


ANAP ANALYSIS

>(0024,0045) 1 CS False Negatives Estimate Flag

Whether the device was able to estimates false negatives. Enumerated Values: YES NO

YES if Test is a SITA Test.


ALWAYS ANALYSIS

>(0024,0046) 1C FL False Negatives Estimate

Estimated percentage of all stimuli that were not seen by the patient but were previously seen at a lower luminance earlier in the visual field test (false negative responses), as percent.

Required if False Negatives Estimate Flag (0024,0045) is YES.


ANAP ANALYSIS

>(0024,0051) 1 CS Excessive False Negatives Data Flag

Whether the device was able to determine excessive false negatives. Enumerated Values: YES NO

YES if Non-SITA Threshold test. NO otherwise.


ALWAYS ANALYSIS

>(0024,0052) 1C CS Excessive False Negatives

The false negative estimate is outside of implementation-specific limits. Enumerated Values: YES NO Required if Excessive False Negatives Data Flag (0024,0051) is YES.

If not SITA and FN Errors / FN Trials ›= 33% then YES. NO otherwise.

Extracted from binary data in the

ANAP ANALYSIS



source HFA raw data.

>(0024,0056) 1C US Positive Catch Trials Quantity

The total number of times the device behaved as if it was going to present a visual stimulus but did not actually present the stimulus (positive catch trials).

Required if Catch Trials Data Flag (0024,0055) is YES.


ANAP ANALYSIS

>(0024,0060) 1C US False Positives Quantity

The total number of patient responses that occurred at a time when no visual stimulus was present (false positive responses). Required if Catch Trials Data Flag (0024,0055) is YES.


ANAP ANALYSIS

>(0024,0053) 1 CS False Positives Estimate Flag

Whether the device was able to estimate false positives. Enumerated Values: YES NO

YES if SITA test, NO otherwise


ALWAYS ANALYSIS

>(0024,0054) 1C FL False Positives Estimate

Estimated percentage of all patient responses that occurred at a time when no visual stimulus was present (false positive responses), as percent. Required if False Positives Estimate Flag (0024,0053) is YES.


ANAP ANALYSIS

>(0024,0061) 1 CS Excessive False Positives Data Flag

Always set to: YES. ALWAYS AUTO

>(0024,0062) 1C CS Excessive False Positives

The false positive estimate is outside of implementation-specific limit. Enumerated Values: YES NO Required if Excessive False Positives Data Flag (0024,0061) is YES.

If not SITA and FP Errors / FP Trials ›= 33% or if SITA and FP Estimate ›= 15% then YES. NO otherwise.


ANAP ANALYSIS

(0024,0069) 3 LO Patient Reliability Indicator

“*** Excessive High False Positives ***” if Excessive False Positives is YES.

“*** Low Test Reliability ***” if Excessive False Negatives is YES or Excessive Fixation Losses is YES and the test was not a SITA-SWAP test.

ANAP ANALYSIS



Table 8-52 Ophthalmic Visual Field IOD – FGW – Module "Visual Field Static Perimetry Test Measurements"


(0024,0113) 1 CS Measurement Laterality

Laterality from source HFA raw data.

ALWAYS SRC

(0024,0037) 1 CS Presented Visual Stimuli Data Flag

Always set to “NO” ALWAYS AUTO

(0024,0088) 1 FL Visual Field Test Duration

Total time the visual field machine was actively presenting visual stimuli to patient, in seconds.


ALWAYS ANALYSIS

(0024,0086) 1 CS Foveal Sensitivity Measured

Whether foveal sensitivity was measured. Enumerated Values: YES NO


ALWAYS ANALYSIS

(0024,0087) 1C FL Foveal Sensitivity

Foveal Sensitivity is the reciprocal of foveal threshold (1/foveal threshold), in dB. Foveal Threshold is the minimum amount of luminance increment on a uniform background that can be detected by the patient at coordinates 0,0 (relative to the center of the patient’s fixation). See section C.8.26.4.1.2 for further explanation. Required if the value for Foveal Sensitivity Measured (0024,0086) is YES.


ANAP ANALYSIS

(0024,0117) 1 CS Foveal Point Normative Data Flag

Existence of normative data base for the foveal point sensitivity. Enumerated Values: YES, NO

This is YES if the test qualifies for a Single Field Analysis report.


ALWAYS ANALYSIS

(0024,0118) 1C FL Foveal Point Probability Value

The percentile of the foveal point sensitivity within an age corrected normal visual field, in percent. Required if the value for Foveal Sensitivity Measured (0024,0086) is YES and Foveal Point Normative Data Flag (0024,0117) is YES.


ANAP ANALYSIS

(0024,0120) 1 CS Screening Baseline Measured

Whether visual field screening baseline was measured. Enumerated Values: YES, NO


ALWAYS ANALYSIS

(0024,0122) 1C SQ

Screening Baseline Measured Sequence

Information about the starting luminance screening values. One or more Items shall be included in this sequence. Required if the value for Screening Baseline Measured (0024,0120) is YES.

ANAP ANALYSIS




>(0024,0124)

1 CS Screening Baseline Type

Method used to determine starting luminance screening values. Enumerated Values: CENTRAL PERIPHERAL


ALWAYS ANALYSIS

>(0024,0126)

1 FL Screening Baseline Value

Visual Field screening baseline value, in dB.


ALWAYS ANALYSIS

(0024,0106) 1 CS Blind Spot Localized

Whether the blind spot was measured. Enumerated Values: YES, NO


ALWAYS ANALYSIS

(0024,0107) 1C FL Blind Spot X-Coordinate

The horizontal coordinate of the patient’s blind spot relative to the center of the patient’s fixation, in degrees, such that toward the right is positive. Required if the value for Blind Spot Localized (0024,0106) is YES.


ANAP ANALYSIS

(0024,0108) 1C FL Blind Spot Y-Coordinate

The vertical coordinate of the patient’s blind spot relative to the center of the patient fixation, in degrees, such that up is positive. Required if the value for Blind Spot Localized (0024,0106) is YES.


ANAP ANALYSIS

(0024,0105) 1 FL Minimum Sensitivity Value

The minimum sensitivity value generated by the equipment used for this visual field test, in dB.


ALWAYS ANALYSIS

(0024,0057) 1 CS Test Point Normals Data Flag

Existence of normative data base for this set of test points. Enumerated Values: YES NO

YES if the tests qualifies for a Single Field Analysis report, NO otherwise


ALWAYS ANALYSIS

(0024,0058) 1C SQ Test Point Normals Sequence

Normative data base used for this test sequence. Only a single Item shall be included in this sequence. Required if Test Point Normals Data Flag (0024,0057) is YES.

ANAP AUTO

>(0024,0306)

1 LO Data Set Name Set to: “HFA test point normative data” ALWAYS AUTO

>(0024,0307)

1 LO Data Set Version

Set to: “1.0” ALWAYS AUTO



>(0024,0308)

1 LO Data Set Source

Set to: “CZMI” ALWAYS AUTO

(0024,0065) 1C SQ

Age Corrected Sensitivity Deviation Algorithm Sequence

Software algorithm used to provide the probability that the age corrected sensitivity deviation values at each test point belong to a normal visual field. Only a single Item shall be included in this sequence. Required if Test Point Normals Data Flag (0024,0057) is YES.

ANAP AUTO

>(0066,002F)

1 SQ Algorithm Family Code Sequence

The family of algorithm(s) that best describes the software algorithm used. Only a single item shall be included in this sequence.

ALWAYS AUTO

>>(0008,0100)

1 SH Code Value Set to: "PERIMETRY" ALWAYS AUTO

>>(0008,0102)

1 SH Coding Scheme Designator

Set to: "99CZM_PERIMETRY" ALWAYS AUTO

>>(0008,0104)

1 LO Code Meaning Set to: "CZM Perimetry Algorithms" ALWAYS AUTO

>(0066,0036)

1 LO Algorithm Name Set to: “Total Deviation” ALWAYS AUTO

>(0066,0031)

1 LO Algorithm Version


(0024,0067) 1C SQ

Generalized Defect Sensitivity Deviation Algorithm Sequence

Software algorithm used to provide the probability that the sensitivity deviation values at each test point belong to a normal visual field. Only a single Item shall be included in this sequence. Required if Test Point Normals Data Flag (0024,0057) is YES.

ANAP AUTO

>(0066,002F)



ALWAYS AUTO

>>(0008,0100)

1 SH Code Value Set to: "PERIMETRY" ALWAYS AUTO

>>(0008,0102)



>>(0008,0104)

1 LO Code Meaning Set to: "CZM Perimetry Algorithms" ALWAYS AUTO

>(0066,0036)

1 LO Algorithm Name Set to: “Pattern Deviation” ALWAYS AUTO

>(0066,0031)



(0024,0089) 1 SQ Visual Field Test Point Sequence

Information for each test point in the visual field. One or more items shall be included in this sequence.

The values of the test points are extracted from the binary data in the source HFA raw data.

ALWAYS ANALYSIS



>(0024,0090)

1 FL Visual Field Test Point X-Coordinate

The horizontal coordinate of a single test point relative to the center of the patient fixation, in degrees, such that toward the right is positive.

The x coordinate of the test point, extracted from the binary data in the source HFA raw data.

ALWAYS ANALYSIS

>(0024,0091)

1 FL Visual Field Test Point Y-Coordinate

The vertical coordinate of a single test point relative to the center of the patient fixation, in degrees, such that up is positive.

The y coordinate of the test point, extracted from the binary data in the source HFA raw data.

ALWAYS ANALYSIS

>(0024,0093)

1 CS Stimulus Results

Whether the patient saw a stimulus presented at a luminance other than maximum, a presentation at maximum luminance, or did not see any presented stimulus.

Enumerated Values:

SEEN = stimulus seen at a luminance value less than maximum

NOT SEEN = stimulus not seen

SEEN AT MAX = stimulus seen at the maximum luminance possible for the instrument

Note: SEEN AT MAX is a value only relevant to Screening tests.


ALWAYS ANALYSIS

>(0024,0094)

1C FL Sensitivity Value

Extracted from binary data in the source HFA raw data, only available for threshold tests.

ANAP ANALYSIS

>(0024,0095)

3 CS Retest Stimulus Seen

Whether the retested stimulus presented was seen by the patient. Enumerated Values: YES NO

The second threshold result, may only be available for non-SITA Threshold tests.


ANAP ANALYSIS

>(0024,0096)

3 FL Retest Sensitivity Value

If the Retest Stimulus Seen (0024,0095) is YES, then this value is the sensitivity, in dB.


ANAP ANALYSIS

>(0024,0098)

3 FL Quantified Defect

Difference between the expected and the determined sensitivity, each in dB.

Only for screening tests with strategy quantified defects.


ANAP ANALYSIS

>(0024,0097)

1C SQ Visual Field Test Point Normals

Information about normal values for each visual field test point. One or more items shall be included in this sequence.

ANAP AUTO



Sequence Required if Test Point Normals Data Flag (0024,0057) is YES.


>>(0024,0092)

1 FL Age Corrected Sensitivity Deviation Value

Difference between the patient’s local sensitivity and the age corrected normal sensitivity, in dB.


ALWAYS ANALYSIS

>>(0024,0100)

1 FL

Age Corrected Sensitivity Deviation Probability Value

The percentile of the age corrected sensitivity deviation within the normal population of visual field, in percent.


ALWAYS ANALYSIS

>>(0024,0102)

1 CS

Generalized Defect Corrected Sensitivity Deviation Flag

Set to: “YES” ALWAYS AUTO

>>(0024,0103)

1C FL

Generalized Defect Corrected Sensitivity Deviation Value

The age corrected sensitivity deviation after correction for the Generalized Defect, in dB. Generalized defect is proportional to the loss in sensitivity shared by all points in the visual field. Required if Generalized Defect Corrected Sensitivity Deviation Flag (0024,0102) is YES.


ANAP ANALYSIS

>>(0024,0104)

1C FL

Generalized Defect Corrected Sensitivity Deviation Probability Value

The percentile of the generalized defect corrected sensitivity deviation within the normal population of visual field, in percent. Required if Generalized Defect Corrected Sensitivity Deviation Flag (0024,0102) is YES.


ANAP ANALYSIS

Table 8-53 Ophthalmic Visual Field IOD – FGW – Module "Visual Field Static Perimetry Test Results"


(0024,0070) 1C FL Visual Field Mean Sensitivity

Average sensitivity of the test points of the visual field, in dB.

Only available for Threshold tests.


ANAP ANALYSIS

(0024,0063) 1 CS Visual Field Test Normals Flag

Whether normals exist for this patient’s results. Enumerated Values: YES NO


ALWAYS ANALYSIS

(0024,0064) 1C SQ Results Normals Sequence

Information that represents the statistically normal results for patients from a referenced data base. Only a single Item shall be included in this sequence. Required if Visual Field Test Normals Flag (0024,0063) is YES.

Extracted from binary data in the source

ANAP AUTO



HFA raw data.

>(0024,0306) 1 LO Data Set Name Set to: “HFA visual field test normative data”

ALWAYS AUTO

>(0024,0307) 1 LO Data Set Version


>(0024,0308) 1 LO Data Set Source

Set to: ”CZMI” ALWAYS AUTO

>(0024,0066) 1 FL Global Deviation From Normal

Weighted average deviation from the age corrected normal field, in dB.


ALWAYS ANALYSIS

>(0024,0059) 1 CS

Global Deviation Probability Normals Flag

Whether normals exist for the global deviation probability. Enumerated Values: YES NO


ALWAYS ANALYSIS

>(0024,0083) 1C SQ

Global Deviation Probability Sequence

Probability value and software algorithm used to provide the normality for the global deviation.

Required if Global Deviation Probability Normals Flag (0024,0059) is YES.


ANAP AUTO

>>(0024,0071)

1 FL Global Deviation Probability

The percentile of the Global Deviation from Normal (0024,0066) value within the normal population, in percent.


ALWAYS ANALYSIS

>>(0066,002F)


The family of algorithm(s) that best describes the software algorithm used.

ALWAYS AUTO

>>>(0008,0100)

1 SH Code Value Set to: “PERIMETRY” ALWAYS AUTO

>>>(0008,0102)


Set to: “99CZM_PERIMETRY” ALWAYS AUTO

>>>(0008,0104)

1 LO Code Meaning Set to: “CZM Perimetry Algorithms” ALWAYS AUTO

>>(0066,0036)

1 LO Algorithm Name Set to: “MD Probability” ALWAYS AUTO

>>(0066,0031)



>(0024,0068) 1 FL Localized Deviation from Normal

Weighted square root of loss variance, in dB.


ALWAYS ANALYSIS

>(0024,0072) 1 CS Local Deviation Probability Normals Flag

Whether normals exist for the local deviation probability. Enumerated Values: YES NO


ALWAYS ANALYSIS



>(0024,0085) 1C SQ

Localized Deviation Probability Sequence

Probability value and software algorithm used to provide the normality for the local deviation.

Required if Local Deviation Probability Normals Flag (0024,0072) is YES.


ANAP AUTO

>>(0024,0073)

1 FL Localized Deviation Probability

The percentile of the Localized Deviation from Normal (0024,0068) value within the normal population, in percent.


ALWAYS ANALYSIS

>>(0066,002F)



ALWAYS AUTO

>>>(0008,0100)

1 SH Code Value Set to: “PERIMETRY” ALWAYS AUTO

>>>(0008,0102)


Set to: “99CZM_PERIMETRY” ALWAYS AUTO

>>>(0008,0104)

1 LO Code Meaning Set to: “CZM Perimetry Algorithms” ALWAYS AUTO

>>(0066,0036)

1 LO Algorithm Name Set to: “PSD Probability” ALWAYS AUTO

>>(0066,0031)



(0024,0074) 1 CS Short Term Fluctuation Calculated

Whether the short term fluctuation was calculated. Enumerated Values: YES NO


ALWAYS ANALYSIS

(0024,0075) 1C FL Short Term Fluctuation

Average deviation of sensitivity for the repeated test locations, in dB. This is used to determine the consistency of the patient’s responses. Required if Short Term Fluctuation Calculated (0024,0074) is YES.


ANAP ANALYSIS

(0024,0076) 1 CS

Short Term Fluctuation Probability Calculated

Whether the short term fluctuation probability was calculated.

Enumerated Values: YES NO


ALWAYS ANALYSIS

(0024,0077) 1C FL Short Term Fluctuation Probability

The percentile of the Short Term Fluctuation (0024,0075) value within the normal population, in percent. Required if Short Term Fluctuation Probability Calculated (0024,0076) is YES.


ANAP ANALYSIS

(0024,0078) 1 CS Corrected Whether the corrected localized ALWAYS ANALYSIS



Localized Deviation From Normal Calculated

deviation from normal was calculated. Enumerated Values: YES NO


(0024,0079) 1C FL

Corrected Localized Deviation From Normal

Weighted square root of loss variance corrected for short term fluctuation, in dB. Required if Corrected Localized Deviation From Normal Calculated (0024,0078) is YES.


ANAP ANALYSIS

(0024,0080) 1 CS

Corrected Localized Deviation From Normal Probability Calculated

Whether the corrected localized deviation from Normal probability was calculated. Enumerated Values: YES NO

Extracted from binary data in the raw data source.

ALWAYS ANALYSIS

(0024,0081) 1C FL

Corrected Localized Deviation From Normal Probability

The percentile of the Corrected Localized Deviation From Normal (0024,0079) value within the normal population, in percent. Required if Corrected Localized Deviation From Normal Probability Calculated (0024,0080) is YES.


ANAP ANALYSIS

(0024,0320) 3 SQ

Visual Field Global Results Index Sequence

Information about various visual field indexes related to test results.

Values extracted from binary data in the source HFA raw data.

ANAP AUTO

>(0024,0325) 1 SQ Data Observation Sequence

Information about various visual field global indexes. Only a single Item shall be included in this sequence.

ALWAYS AUTO

>>(0040,A040)

1 CS Value Type Set to: “NUMERIC” ALWAYS AUTO

>>(0040,A043)

1 SQ Concept Name Code Sequence

Coded concept name of this name-value Item. Only a single Item shall be included in this Sequence.

ALWAYS AUTO

>>>(0008,0100)

1 SH Code Value Set to: “111852” ALWAYS AUTO

>>>(0008,0102)


Set to: “DCM” ALWAYS AUTO

>>>(0008,0104)

1 LO Code Meaning Set to: “Visual Field Index” ALWAYS AUTO

>>(0040,A30A)

1C DS Numeric Value

Numeric value for this name-value Item. Required if Value Type (0040,A040) is NUMERIC.


Valid values are 0 to 100

ALWAYS ANALYSIS

>>(0040,08EA)

1C SQ Measurement Units Code Sequence

The Code Sequence for % ALWAYS AUTO



>>>(0008,0100)

1 SH Code Value Set to: “%” ALWAYS AUTO

>>>(0008,0102)


Set to: “UCUM” ALWAYS AUTO

>>>(0008,0104)

1 LO Code Meaning Set to: “percent” ALWAYS AUTO

>(0024,0338) 1 CS Index Normals Flag

Set to: “NO” ALWAYS AUTO

Table 8-54 Ophthalmic Visual Field IOD – FGW – Module "Ophthalmic Patient Clinical Information and Test Lens Parameters"


(0024,0114) 1C SQ

Ophthalmic Patient Clinical Information Left Eye Sequence

Information used to represent a patient’s clinical parameters during an ophthalmic test. Only a single Item shall be included in this sequence. Required if Measurement Laterality (0024,0113) is L or B.

Filled if the data is available. Because the module is optional, this sequence is only than available.


ANAP AUTO

>(0024,0112) 2 SQ

Refractive Parameters Used on Patient Sequence

Refractive parameters used when performing visual field test. Zero or one Item shall be included in this sequence.

ALWAYS AUTO

>>(0022,0007) 1 FL Spherical Lens Power

Sphere value in diopters.


ALWAYS ANALYSIS

>>(0022,0008) 1 FL Cylinder Lens Power

Cylinder value in diopters.


ALWAYS ANALYSIS

>>(0022,0009) 1 FL Cylinder Axis

Axis value in degrees.


ALWAYS ANALYSIS

>(0046,0044) 2 FD Pupil Size

The horizontal diameter measurement of the pupil, in mm.


ALWAYS ANALYSIS

>(0022,000D) 2 CS Pupil Dilated Is always empty EMPTY

>(0022,000B) 3 FL Intra Ocular Pressure

Value of intraocular pressure in mmHg.


ANAP ANALYSIS

>(0024,0110) 3 SQ Visual Acuity Measurement Sequence

Measurements of a patient’s visual acuity. Only a single Item is permitted in this sequence.


ANAP ANALYSIS



>>(0046,0137) 1 FD Decimal Visual Acuity

A patient’s visual acuity specified in decimal. The value is derived from two values in a fraction where the numerator of the fraction is the nominal distance to the chart that the patient is reading. The denominator represents the line of smallest optotypes of which the patient can see more than half. Notes: 1. Typical examples--reference standard is 1, severe vision loss is 0.1 2. See PS 3.17 Ophthalmic Refractive Reports Use Cases for guidance in converting Decimal Visual Acuity to other customarily used display notation such as 20/20 in the US and 6/6 in Britain.


ALWAYS ANALYSIS

(0024,0115) 1C SQ

Ophthalmic Patient Clinical Information Right Eye Sequence

Information used to represent a patient’s clinical parameters during an ophthalmic test. Only a single Item shall be included in this sequence. Required if Measurement Laterality (0024,0113) is R or B.

Filled if the data is available. Because the module is optional, this sequence is only than available.


ANAP AUTO

>(0024,0112) 2 SQ

Refractive Parameters Used on Patient Sequence

Refractive parameters used when performing visual field test. Zero or one Item shall be included in this sequence.

ALWAYS AUTO

>>(0022,0007) 1 FL Spherical Lens Power

Sphere value in diopters.


ALWAYS ANALYSIS

>>(0022,0008) 1 FL Cylinder Lens Power

Cylinder value in diopters.


ALWAYS ANALYSIS

>>(0022,0009) 1 FL Cylinder Axis

Axis value in degrees.


ALWAYS ANALYSIS

>(0046,0044) 2 FD Pupil Size

The horizontal diameter measurement of the pupil, in mm.


ALWAYS ANALYSIS

>(0022,000D) 2 CS Pupil Dilated Is always empty EMPTY

>(0022,000B) 3 FL Intra Ocular Pressure

Value of intraocular pressure in mmHg.


ANAP ANALYSIS

>(0024,0110) 3 SQ Visual Acuity Measurement Sequence

Measurements of a patient’s visual acuity. Only a single Item is permitted in this sequence.


ANAP ANALYSIS

>>(0046,0137) 1 FD Decimal Visual Acuity

A patient’s visual acuity specified in decimal. The value is derived from two values in a fraction where the numerator of the fraction is

ANAP ANALYSIS



the nominal distance to the chart that the patient is reading. The denominator represents the line of smallest optotypes of which the patient can see more than half. Notes: 1. Typical examples--reference standard is 1, severe vision loss is 0.1 2. See PS 3.17 Ophthalmic Refractive Reports Use Cases for guidance in converting Decimal Visual Acuity to other customarily used display notation such as 20/20 in the US and 6/6 in Britain.


Table 8-55 Ophthalmic Visual Field IOD – FGW – Module "SOP Common"


(0008,0016) 1 UI SOP Class UID Set to: “1.2.840.10008.5.1.4.1.1.80.1” ALWAYS AUTO

(0008,0018) 1 UI SOP Instance UID Newly created with UID prefix of: 1.2.276.0.75.2.5.80.25.3

ALWAYS AUTO

(0008,0005) 1C CS Specific Character Set Set to: “ISO_IR 192” (Unicode encoding) ALWAYS AUTO

(0008,0012) 3 DA Instance Creation Date

Date the SOP Instance was created. Set to current date.

ALWAYS AUTO

(0008,0013) 3 TM Instance Creation Time

Time the SOP Instance was created. Set to current time

ALWAYS AUTO

Table 8-56 Ophthalmic Visual Field IOD – FGW – Module "CZM Ophthalmic Visual Field Static Perimetry Measurements Extension"


(0008,114A) 3 SQ Referenced Instance Sequence

This is a CZM specific extension. The referenced Instances are related to this Instance with a purpose for that reference. The sequence may contain zero, one or more items.

Contains the reference to the source HFA raw data.

ALWAYS AUTO

>(0008,1150) 1 UI Referenced SOP Class UID

Uniquely identifies the referenced SOP Class.

Set to: 1.2.840.10008.5.1.4.1.1.66 ALWAYS AUTO

>(0008,1155) 1 UI Referenced SOP Instance UID

Uniquely identifies the referenced SOP Instance. The instance UID of the raw instance containing the source data of this instance.

ALWAYS AUTO

>(0040,A170) 1 SQ

Purpose of Reference Code Sequence

The sequence shall contain one and may contain more items. The codes applied shall be CZM specific.

ALWAYS AUTO

>>(0008,0100) 1 SH Code Value Set to: “RAW DATA SRC” ALWAYS AUTO

>>(0008,0102) 1 SH Coding Scheme Designator


>>(0008,0104) 1 LO Code Meaning Set to: "CZM Perimetry Source Exam". ALWAYS AUTO

Table 8-57 Ophthalmic Visual Field IOD – FGW – Module "HfaVisualFieldStaticPerimetryTestResults"




(0305,xx00) 3 LO Glaucoma Staging Index

The Glaucoma Staging Index. ANAP ANALYSIS

8.1.2 Usage of Attributes from Received IOD’s

The acquisition date and time of a document in FORUM is defined by the following rules: If (0008,002A) Acquisition DateTime is not filled in the DICOM header, then (0008,0022) Acquisition Date and (0008,0032) Acquisition Time will be used as FORUM document acquisition date and time. If (0008,0022) Acquisition Date is not filled, then (0008,0021) Series Date and (0008,0031) Series Time will be used as FORUM document acquisition date and time.

If (0008,0021) Series Date and (0008,0031) Series Time are not filled, then (0008,0020) Study Date and (0008,0030) Study Time will be used as FORUM document acquisition date and time.

If (0008,0020) Study Date is not filled, then (0008,0023) Content Date and (0008,0033) Content Time will be used as FORUM document acquisition date and time.

The FORUM image laterality is defined by the following rule: If (0020,0062) Image Laterality is not filled, then Laterality (0020,0060) will be used as FORUM Image Laterality.

The resulting attributes Acquisition DateTime and Image Laterality will be used for display within the FORUM viewer as well as for the C-FIND request (matching/return keys, and sorting by Acquisition DateTime).

8.1.3 Attribute Mapping

Modality Worklist Instance IOD Editable

Study Instance UID Study Instance UID Yes/No

Referenced Study Sequence Referenced Study Sequence Yes/No

Accession Number Accession Number Yes/No

Requested Procedure ID Request Attributes Sequence > Requested Procedure ID

Yes/No

Study ID Yes/No

Requested Procedure Description Request Attributes Sequence > Requested Procedure Description

Yes/No

Performed Procedure Step Description Yes/No

Study Description Yes/No

Protocol Name Yes/No

Scheduled Procedure Step Sequence > Scheduled Procedure Step ID

Request Attributes Sequence > Scheduled Procedure Step ID

Yes/No

Scheduled Procedure Step Sequence > Scheduled Procedure Step Description

Request Attributes Sequence > Scheduled Procedure Step Description

Yes/No

Scheduled Procedure Step Sequence > Schedule Protocol Code Sequence

Request Attributes Sequence > Scheduled Protocol Code Sequence

Yes/No

Requested Procedure Code Sequence Procedure Code Sequence Yes/No

Referring Physicians Name Referring Physicians Name Yes/No

Patients Name Patients Name Yes/No

Patient ID Patient ID Yes/No

Issuer of Patient ID Issuer of Patient ID Yes/No



Other Patient IDs Other Patient IDs Yes/No

Patients Birth Date Patients Birth Date Yes/No

Patients Sex Patients Sex Yes/No

Patient Comments Patient Comments Yes/No

Ethnic Group Ethnic Group Yes/No

Attribute Mapping from Source Raw Data IOD into FORUM Glaucoma Workplace generated OPV or ePDF

Source Raw Data IOD OPV or ePDF IOD Editable

Study Instance UID Study Instance UID 1)

No

Study Date Study Date 1)

No

Study Time Study Time 1)

No

Study ID Study ID 1)

No

Study Description Study Description 1)

No

Accession Number Accession Number No

Procedure Code Sequence Procedure Code Sequence No

Request Attributes Sequence > Requested Procedure ID

Request Attributes Sequence > Requested Procedure ID

No

Request Attributes Sequence > Requested Procedure Description

Request Attributes Sequence > Requested Procedure Description

No



No



No



No

Performed Procedure Step ID Performed Procedure Step ID 1)

No

Performed Procedure Step Start Date Performed Procedure Step Start Date 1)

No

Performed Procedure Step Start Time Performed Procedure Step Start Time 1)

No

Laterality Laterality No

Acquisition Date Time Acquisition Date Time No

Image Laterality Image Laterality No

Referring Physicians Name Referring Physicians Name No

Patients Name Patients Name No

Patient ID Patient ID No

Issuer of Patient ID Issuer of Patient ID No

Other Patient IDs Other Patient IDs No

Patients Birth Date Patients Birth Date No

Patients Sex Patients Sex No

Patient Comments Patient Comments No

Ethnic Group Ethnic Group No

1) Only applies when the source is a single raw data object. In case of multiple source raw data sets the values in the resulting OPV and ePDF IOds are newly generated and not mapped from the source.



8.1.4 Coerced/Modified Files

Patient Edit/Merge or Instance Reassign 8.1.4.1

The following attributes are updated in the DICOM header of an IOD, in case they are edited in the FORUM Viewer, or if two patients are being merged:

Tag VR VM Name

(0010,0021) LO 1 Issuer of Patient ID

(0010,0020) LO 1 Patient ID

(0010,0010) PN 1 Patient’s Name

(0010,0030) DA 1 Patient’s Birth Date

(0010,0040) CS 1 Patient’s Sex

(0010,2160) SH 1 Ethnic Group

(0010,1000) LO 1-n Other Patient IDs

(0010,4000) LT 1 Patient Comments

If the Dicom Header does not support the changed characters of the changed attributes, then the Dicom File will be transcoded to UTF8. This includes all other String or Text attributes. If there is an unknown VR in the Dicom Header (in case of Implicit VR Little Endian Transfer Syntax with unknown Private Tags), then there will be no transcoding, and the unsupported characters will be replaced by a question mark "?".

All of the above patients attribute (if it is a study of another patient) and the following study and series level attributes are updated in the DICOM header of an IOD, in case a SOP Instance is reassigned to another study.

Tag VR VM Name

(0020,000D) UI 1 Study Instance UID

(0020,0010) SH 1 Study ID

(0008,0020) DA 1 Study Date

(0008,0030) TM 1 Study Time

(0008,0050) SH 1 Accession Number

(0008,0090) PN 1 Referring Physician’s Name

(0008,1080) LO 1-n Admitting Diagnoses Description

(0008,1030) LO 1 Study Description

(0020,000E) UI 1 Series Instance UID

(0008,103E) LO 1 Series Description

If reassigned to a new Study or Series FORUM generates a new Study- and Series Instance UID. FORUM uses Study Date and Time from the original Study. The user is asked to enter Accession Number, Referring Physician’s Name, Admitting Diagnoses Description and Study Description via the GUI.

If reassigned to a new Study or Series, the corresponding values of the destination Study or Series will be used to update the attribute values of the reassigned instance(s).

The SOP Instance UID will not be changed.



Patient Information / Patient Matching 8.1.4.2

The following terms and rules for patient identification are defined:

Strict Attributes: Patient ID

Patient Birth Date

Lax Attributes: Issuer of Patient ID

Patient's Sex

Lax Matching: Lax attributes match if they are equal

Lax attributes match if they are empty on either side

Corresponding Component Name Groups: Corresponding component group names have equal first- and last name

Corresponding component group names have lax matching middle name, prefix and suffix

Corresponding Patient: Corresponding patients have equal strict attributes

Corresponding patients have matching lax attributes

Corresponding patients have corresponding component group names regardless of the position of the component group name. Either one of the patients to be compared might have more filled component group names. For example the following two Patient's Names match: "aaa^bbb^dr=ggg^hhh" matches "xxx^yyy=aaa^bbb=ggg^hhh^^pref"

Conflicted Patient: A patient who has no Patient ID.

A patient who contains an existing combination of Issuer of Patient ID and a Patient ID and this existing patient is not a "corresponding patient" as defined above.

Patient Information attributes: Tag VR VM Name

(0010,0021) LO 1 Issuer of Patient ID

(0010,0020) LO 1 Patient ID

(0010,0010) PN 1 Patient’s Name

(0010,0030) DA 1 Patient’s Birth Date

(0010,0040) CS 1 Patient’s Sex

(0010,2160) SH 1 Ethnic Group

(0010,1000) LO 1-n Other Patient IDs

(0010,4000) LT 1 Patient Comments

Patient Information will be updated in the DICOM files: If the user edits one of the patient information attributes via the GUI.

If an incoming DICOM file has an existing corresponding patient in FORUM and differences in the patient information attributes.



Missing UIDs 8.1.4.3

Study Instance UID, Series Instance UID and SOP Instance UID will be auto generated if one of those is missing in an incoming DICOM file.

Patient Identification Conflict with Study Instance UID 8.1.4.4

If an incoming DICOM file belongs to an existing study in FORUM and this existing study belongs to a different patient already existing in FORUM (different patient is a “not corresponding patient" according to 8.1.4.2) then a new Study Instance UID will be automatically generated.

8.2 Data Dictionary of Private Attributes FORUM does not create any private attributes.

FORUM Glaucoma Workplace may use the following private attributes:

Group ID: 22A1

Private Creator String: “99CZM_SpecializedEncapsulatedDocument”

Occurs in: ePDF SOP Instance generated by FORUM Glaucoma Workplace

Table 8-58 Private Dictionary Group 22A1 "99CZM_SpecializedEncapsulatedDocument

Attribute Name Element ID VR VM

Document Type 01 LO 1

Group ID: 2501

Private Creator String: 99CZM_Solln

Occurs in: ePDF SOP Instance generated by FORUM Glaucoma Workplace

Table 8-59 Private Dictionary Group 2501 "99CZM_Solln


Report Type 00 CS 1

Generated automatically 01 CS 1

Combined Report Source Instance Sequence 02 SQ 0..n

Combined Report Source Instance UID 03 UI 1

Combined Report Source Class UID 04 UI 1

Combined Report Source Laterality 05 CS 1

Combined Report Source IOD Meta Name 06 LO 1

HFA Test Strategy 07 CS 1

HFA Test Pattern 08 CS 1

Group ID: 7717

Private Creator String: 99CZM_HFA_EMR_2

Occurs in ePDF SOP Instance generated by FORUM Glaucoma Workplace

Table 8-60 Private Dictionary Group 7717 "99CZM_HFA_EMR_2"


test_name 01 LO 1

test_strategy 02 LO 1

stimulus_size 03 CS 1



stimulus_color 04 SH 1

background_state 05 SH 1

foveal_result 06 CS 1

screening_mode 07 LO 1

fixation_trials 08 IS 1

fixation_errors 09 IS 1

false_positive_percent 10 DS 1

false_positive_trials 11 IS 1

false_positive_errors 1 IS 1

false_negative_percent 13 DS 1

false_negative_trials 14 IS 1

false_negative_errors 15 IS 1

mean_deviation 16 DS 1

mean_deviation_probability 17 LO 1

pattern_standard_deviation 18 DS 1

pattern_standard_deviation_probability 19 LO 1

short_term_fluctuation 20 DS 1

corrected_pattern_standard_deviation 21 DS 1

corrected_pattern_standard_deviation_probability 22 LO 1

glaucoma_hemifield_test 23 LO 1

fixation_monitor 24 LO 1

fixation_target 25 LO 1

pupil_diameter 26 DS 1

sphere 27 DS 1

cylinder 28 DS 1

axis 29 IS 1

visual_acuity 30 SH 1

short_term_fluctuation_probability 31 LO 1

test_date 32 DA 1

test_time 33 TM 1

visual_field_index 34 DS 1

vfm_sequence 40 SQ 1

section_number 41 IS 1

section_value 42 LO 1



Group ID: 0305

Private Creator String: 99CZM_Hfa_OphthalmicVisualFieldStaticPerimetry

Occurs in ePDF SOP Instance generated by FORUM Glaucoma Workplace

Table 8-61 Private Dictionary Group "99CZM_Hfa_OphtalmicVisualFieldStaticPerimetry"

glaucoma_staging_index 00 LO 1

8.3 Coded Terminology and Templates FORUM does not use or create any codes.

FORUM Glaucoma Workplace uses (0066,002F) Algorithm Family Code Sequence with following codes to specify the algorithms used.

Occurs in: Ophthalmic Visual Field Static Perimetry IOD

Code Value Coding Scheme

Designator Code Meaning

PERIMETRY 99CZM_PERIMETRY "CZM Perimetry Algorithms"

FORUM Glaucoma Workplace uses (0008,114A) Referenced Instance Sequence with following codes to specify the source HFA raw data.


Code Value Coding Scheme

Designator Code Meaning

RAW DATA SRC 99CZM_PERIMETRY "CZM Perimetry Source Exam"

FORUM Glaucoma Workplace uses (0040,0260) Performed Protocol Code Sequence with the following codes to specify test pattern and test strategy.

The standard ContextIDs 4250 and 4251 are extended.


Extension of CID 4250 Visual Field Static Perimetry Test Patterns

Code Value

Coding

Scheme

Designator

Code Meaning Coding Scheme

Version

OPVTP100 99CZM Visual Field Central 30-1 Threshold Test Pattern 20140605

OPVTP101 99CZM Visual Field Peripheral 60-1 Threshold Test Pattern 20140605

OPVTP102 99CZM Visual Field Temporal Crescent Threshold Test Pattern 20140605

OPVTP103 99CZM Visual Field Neurological 20 Threshold Test Pattern 20140605

OPVTP104 99CZM Visual Field Neurological 50 Threshold Test Pattern 20140605

OPVTP105 99CZM Visual Field Nasal Step Threshold Test Pattern 20140605

OPVTP106 99CZM Visual Field Central Armaly Screening Test Pattern 20140605

OPVTP107 99CZM Visual Field Full Field Armaly Screening Test Pattern 20140605

OPVTP108 99CZM Visual Field Central 80 Point Screening Test Pattern 20140605


OPVTP110 99CZM Visual Field Full Field 246 Point Screening Test Pattern 20140605

OPVTP111 99CZM Visual Field Auto Diagnostic Test Pattern 20140605



OPVTP112 99CZM Visual Field Superior 64 Point Screening Test Pattern 20140605

OPVTP113 99CZM Visual Field Nasal Step Screening Test Pattern 20140605

OPVTP114 99CZM Visual Field Central 24-1 Threshold Test Pattern 20140605

OPVTP115 99CZM Visual Field Blindengutachten Test Pattern 20140605

OPVTP116 99CZM Visual Field Fuehrerscheingutachten Test Pattern 20140605

OPVTP117 99CZM Visual Field Esterman Monocular Test Pattern 20140605

OPVTP118 99CZM Visual Field Esterman Binocular Test Pattern 20140605


OPVTP120 99CZM Visual Field Full Field 12 Point QA Test Pattern 20140605

OPVTP121 99CZM Visual Field User Defined Threshold Test Pattern 20140605

OPVTP122 99CZM Visual Field User Defined Screening Test Pattern 20140605

OPVTP123 99CZM Visual Field Kinetic Test Pattern 20140605

OPVTP124 99CZM Visual Field Full Field 135 Point Screening Test Pattern 20140605

OPVTP125 99CZM Visual Field Superior 36 Point Screening Test Pattern 20140605

OPVTP126 99CZM Visual Field Custom Screening Test Pattern 20140605

OPVTP127 99CZM Visual Field Custom Threshold Test Pattern 20140605


Extension of CID 4251 Visual Field Static Perimetry Test Strategies

Code Value

Coding

Scheme

Designator

Code Meaning Coding Scheme

Version

OPVTS100 99CZM Visual Field Threshold Fast Test Strategy 20140605

8.4 Greyscale Image Consistency This chapter is not applicable.

8.5 Standard Extended / Specialized/ Private SOP Classes The following standard extensions are used in the IODs described in chapter 8.1.1 Created SOP Instance(s).

Table 8-7 Secondary Capture Image IOD – File Import – Module “General Image”

Table 8-8 Secondary Capture Image IOD – File Import – Module "Image Pixel"

Table 8-13 Encapsulated PDF IOD - Module “Encapsulated Document Series”

Table 8-21 Encapsulated PDF IOD – Combined Report - Module “Encapsulated Document Series”

Table 8-24 Encapsulated PDF IOD – Combined Report - Module “Encapsulated Document”

Table 8-56 Ophthalmic Visual Field IOD – FGW – Module "CZM Ophthalmic Visual Field Static Perimetry Measurements Extension"

Table 8-30 Encapsulated PDF IOD – FGW – Module "CZM Encapsulated PDF Series Extension"

8.6 Private Transfer Syntaxes No Private Transfer Syntax is supported.



The products satisfy the fundamental requirements laid down in Annex I of the 93/42/EEC Directive governing medical devices.

The products are labeled with:

Carl Zeiss Meditec AG

Goeschwitzer Strasse 51-52

07745 Jena

Germany

www.meditec.zeiss.com/dicom

http://www.meditec.zeiss.com/dicom