DICOM Conformance Statement - ZEISS · 2020-02-05 · the format type of an individual DICOM data...

Revision: G Date: 2015-02-13

Document: DICOM_Conformance_Statement_HFA3_V1.0.Docx of 97

Copyright: © Carl Zeiss Meditec, Inc. Revision: G

DICOM Conformance Statement

Humphrey® Field Analyzer - HFA™ 3 Series

Version 1.0

Carl Zeiss Meditec, Inc.

5160 Hacienda Drive

Dublin, CA 94568

USA

www.meditec.zeiss.com

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



1 Conformance Statement Overview

The Humphrey Field Analyzer is an automated perimeter intended to identify visual field defects for the purposes of screening, monitoring and assisting in the diagnosis and management of ocular diseases such as glaucoma, and related neurological disorders. The HFA 3 Series uses FORUM® to store patient and exam data and FORUM Glaucoma Workplace to provide the data analysis. The HFA 3 Series instrument operates as an Acquisition Modality AE.

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)

Transfer

Raw Data Storage Yes Yes

Ophthalmic Photography 8 Bit Image Storage Yes No

Ophthalmic Visual Field Static Perimetry Measurements Storage

No 2) No 2)

Encapsulated PDF Storage No 1) No 1)

Workflow Management

Verification Yes Yes

Storage Commitment Push Model SOP Class Yes No

Modality Worklist Information Model - FIND Yes No

Query / Retrieve

Patient Root Query/Retrieve Information Model – FIND Yes No

Study Root Query/Retrieve Information Model – FIND Yes No

Study Root Query/Retrieve Information Model – MOVE Yes No

The HFA 3 does not support Media Interchange.

1) HFA 3 relies on FORUM Glaucoma Workplace to provide ePDF objects. HFA 3 doesn’t consume and cannot provide ePDF.

2) In local database mode (without DICOM Connectivity) HFA 3 offers the function to export OPV IOD’s to a local file path only.



2 Table of Contents 1 Conformance Statement Overview ........................................................................................................ 2 2 Table of Contents ............................................................................................................................. 3 3 Introduction .................................................................................................................................... 5

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

4 Networking ..................................................................................................................................... 9 4.1 Implementation Model ............................................................................................................... 9

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

4.1.2.1 Functional Definition of HFA 3 ....................................................................................... 10 4.1.3 Sequencing of Real-World Activities .................................................................................... 10

4.1.3.1 Acquisition Modality activities ........................................................................................ 11 4.1.3.2 Scheduled case with Acquisition Modality ......................................................................... 11 4.1.3.3 Unscheduled case ..................................................................................................... 12

4.2 AE Specifications ................................................................................................................... 14 4.2.1 HFA 3 Humphrey Field Analyzer - HFA 3 Series AE Specification ................................................. 14

4.2.1.1 SOP Classes ........................................................................................................... 14 4.2.1.2 Associations Policies .................................................................................................. 14

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

4.2.1.3 Association Initiation Policy .......................................................................................... 15 4.2.1.3.1 Activity – Verify Communication ................................................................................ 15 4.2.1.3.2 Activity – Query Modality Worklist ............................................................................. 16 4.2.1.3.3 Activity - Query remote AE for patients ....................................................................... 23 4.2.1.3.4 Activity – Acquire data ........................................................................................... 30 4.2.1.3.5 Activity – Store data to remote AE ............................................................................. 30 4.2.1.3.6 Activity - Retrieve data from remote AE ....................................................................... 33 4.2.1.3.7 Activity – File Import .............................................................................................. 41 4.2.1.3.8 Activity – File Export (OPV and PDF Data) ................................................................... 41 4.2.1.3.9 Activity – Delete data ............................................................................................. 41

4.2.1.4 Association Acceptance Policy ...................................................................................... 42 4.2.1.4.1 Activity – Verify Communication ................................................................................ 42 4.2.1.4.2 Activity – Store data to remote AE ............................................................................. 42 4.2.1.4.3 Activity - Retrieve data from remote AE ....................................................................... 44

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

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

4.4.1.1 Local AE Titles ......................................................................................................... 45 4.4.1.2 Remote AE Titles ...................................................................................................... 45 4.4.1.3 Auto Connect ........................................................................................................... 45

4.4.2 Parameters .................................................................................................................. 45



4.4.2.1 General Parameters ................................................................................................... 45 5 Media Interchange .......................................................................................................................... 48 6 Support of Character Sets ................................................................................................................. 49 7 Security ....................................................................................................................................... 50 8 Annexes ...................................................................................................................................... 51

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

8.1.1.1 Ophthalmic Photography 8Bit Information Object Definition .................................................... 52 8.1.1.2 Raw IOD Information Entities ........................................................................................ 63 8.1.1.3 Ophthalmic Visual Field Static Perimetry Measurements Information Object Definition ................... 72

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

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



3 Introduction

3.1 Revision History Document

Version Date Author Changes

A 2014-2-21 Peter Freimanis Initial Version

F 2015-2-4 Peter Freimanis Updated document according to final release builds: Instrument software for HFA3 version 1.0 one of “1.0.1.159”, “1.0.2.9”, “1.0.3.6” or higher 1.0.x versions.

G 2015-2-13 Mshnau Updated FORUM and FORUM Glaucoma Versions

Update of functional description

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.

Network Integration Manager (NIM) Software component that handles DICOM for Carl Zeiss Meditec, Inc. Ophthalmic systems. Please note: This software component is found in may Zeiss Meditec Ophthalmic systems and is used to handle DICOM objects and Transfer Syntax but each different product uses this component differently and different versions of a product may include different levels of functionality.

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.

Visual Field Test A visual field test is an eye examination that can detect dysfunction in central and peripheral vision which may be caused by various medical conditions such as glaucoma, stroke, brain tumors or other neurological deficits.

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

ILE Implicit Little Endian

ELE Explicit Little Endian

HFA Humphrey Field Analyzer

IOD Information Object Definition

JPG-1 JPEG Coding Process 1 transfer syntax; JPEG Baseline; ISO 10918-1

OP Ophthalmic Photography 8 Bit Image

OPV Ophthalmic Visual Field Static Perimetry Measurements

MWL Modality Worklist

NIM Network Integration Manager (a software component that handles DICOM for Carl Zeiss Meditec, Inc. Ophthalmic systems)

OD Oculus Dexter, the right eye

OS Oculus Sinister, the left eye

OU Oculus Uterque, both eyes

PBQ Patient Root Query



SCP Service Class Provider

SCU Service Class User

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

SRQ Study Root Query

TCP/IP Transmission Control Protocol / Internet Protocol

UID Unique Identifier

IM Information Model

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

DICOM Conformance Statements for FORUM Version 3.2 and higher and FORUM Glaucoma Workplace Version 2.0.3, (available at http://www.meditec.zeiss.com/dcs)

http://medical.nema.org/

http://www.ihe.net/Technical_Framework/index.cfm



4 Networking

4.1 Implementation Model

4.1.1 Application Data Flow

Figure 4-1 HFA 3 Application Software as Acquisition Modality

Note: HFA 3 complies with the DICOM standard but requires the presence of a FORUM Archive 3.2 or higher and a FORUM Glaucoma Workplace Version 2.0.3 for full functionality. Consequently you must also refer to the respective DICOM conformance statements (mentioned in the references) when you assess the DICOM behavior of HFA 3.



4.1.2 Functional Definition of AEs

4.1.2.1 Functional Definition of HFA 3

The Humphrey Field Analyzer is an automated perimeter intended to identify visual field defects for the purposes of screening, monitoring and assisting in the diagnosis and management of ocular diseases such as glaucoma, and related neurological disorders.

The HFA 3 Application Software allows to:

query modality work list

query patients

query studies (in local database mode)

export exam data and eye field of view images

retrieve last exam data/patient prescription for selected patient

The HFA 3 Application Software AE uses several DICOM Services as a Service Class User.

Verification

Modality Worklist Information Model – FIND

Patient Root Query/Retrieve Information Model – FIND

Study Root Query/Retrieve Information Model – FIND

Study Root Query/Retrieve Information Model – MOVE

RAW Data Storage

Ophthalmic Photography 8 Bit Image Storage

Storage Commitment Push Model

HFA3 acts as a service class provider when:

When performing a verification of the configured AEs. The result of this verification contains information about the supported SOP Classes and Transfer Syntaxes.

When retrieving last exam (RAW Data Storage).

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.



4.1.3.1 Acquisition Modality activities

Query Modality Worklist When the patient arrives at the HFA 3 the operator queries the worklist. The user can invoke this by simply selecting the “Today” Tab in the main view which lists all worklist items scheduled today and all completed examinations for today for this instrument (identified by the HFA 3 AE Title) and Scheduled procedure step start date from today. For more specific worklist queries and a detailed view on the scheduled procedures the “Advanced” and then “Scheduled Patients” tab can be used.

The “Today” tab will only display the first procedure for the patient.

In either way the operator can select the patient from the result list to proceed with data acquisition. According to the transferred data HFA 3 creates an entry in the local database.

The HFA 3 supports only a 1:1 relationship between Requested Procedure and Scheduled Procedure Step. If the Requested Procedure contains more than one Scheduled Procedure Step the first Scheduled Procedure Step will be taken when the user starts the test by selecting the “Next” button.

To determine in which order multiple scheduled procedure steps will be processed HFA 3 software sorts the accession numbers of the procedure steps in alphabetical order and selects the first one from this list.

Query remote AE for patients When the patient arrives at the HFA 3 the operator can search patients stored at a remote AE. This can be done by using the “Quick search” in the main screen or by using “Advanced” and then the “All Patients” for a more detailed search. Any matching results will be listed in patient list.

This activity generates an unscheduled case.

The operator can then select the patient for data acquisition or analysis.

Acquire data When a patient or worklist item is selected. The operator selects a Perimetry exam type and chooses the appropriate test parameters and then performs a visual field test. The Application Software allows the operator to review the visual field test data before permanently saving the exam results.

Store data to remote AE When the operator selects the “Save and Exit” button from the Results screen, the RAW Data and Ophthalmic Photography 8 Bit SOP Instances for the exam will be sent to the configured storage provider.

After a configurable amount of time, the Application Software asks the configured Storage Commitment Provider to take over responsibility on data persistence for the data previously transferred by the “Archive data” activity. When storage is committed the data will be removed in the next shutdown routine.

Retrieve data from remote AE A HFA 3 automatically retrieves the last exam as RAW IOD for the selected patient. The test preparation screen is prepopulated with the available settings from the patient’s last exam if it exists.

4.1.3.2 Scheduled case with Acquisition Modality

The normal case is that the patient arrives at the front desk. There can be two possibilities at this point:

The examination can be scheduled on an instrument.



The examination can be scheduled in advance and will be obtained by HFA3 via Modality Worklist query.

In either case all patient and study related information is available at the day the examination takes place. On the HFA 3 these patients appear in the “Todays” list in the main screen. This information is used to take the examination. HFA 3 queries the Archive Provider to obtain the most recent previous exam for the patient to obtain the vision prescription information.

Figure 4-2 Scheduled Case

4.1.3.3 Unscheduled case

In the unscheduled case the patient arrives immediately at the instrument, so that the patient was not registered at the front desk or the software does not support DICOM modality worklist. Thus the examination is not scheduled in the Modality Worklist. One option the operator has is to type in search criteria which filters the “Today” section of the patient selection screen, but it also queries matching patient demographic from the DICOM Server and the local database and displays them in the “Search results” section of the patient selection screen. If the unscheduled patient is in the DICOM Server or the local database, the operator can select the patient from the “Search results” section for data acquisition.

sd Scheduled case

Santa Cruz

Acquisition

Modality AE

Modality Worklist

AE

Query AE Retrieve AE Storage AE Storage

Commitment AE

loop Interv al

Query Modality Worklist()

Select Patient()

Select Requested

Procedure()

Query patient data - last exam (Study Root - Image Level)

Retrieve most recent RAW data IOD for selected Patient

(Retrieve the prescription of the patient)

Perform Exam()

Save Exam()

Store RAW and OP Data()

Request for commitment of data persistence()



Figure 4-3 Unscheduled Case

sd Unscheduled case

Storage

Commitment AE

Santa Cruz

Acquisition

Modality AE

Modality Worklist

AE

Query AE Retrieve AE Storage AE

alt Add new patient

alt Query patient

loop Interv al

Create new patient()

Query for patient (Patient Root - Patient Level)

Select Patient()

Query patient data - last exam (Study Root - Image Level )

Retrieve most recent RAW data IOD for selected patient

(Retrieve the prescription of the patient)

Perform Exam()

Save Exam()


Request for commitment of data persistence()



4.2 AE Specifications

4.2.1 HFA 3 Humphrey Field Analyzer - HFA 3 Series AE Specification

4.2.1.1 SOP Classes

Table 4-1 SOP Classes for HFA 3 AE

Note 1: C-FIND extended negotiation is offered. Relational-query support is required by the SCP.

Note 2: ePDF storage is not supported by HFA 3 itself but is available on the DICOM send side of FORUM derived from RAW data generated by HFA 3.

Note 3: HFA 3 does not transmit OPV IODs via DICOM. If enabled via license it will store OPV IODs to the local hard drive only.

4.2.1.2 Associations Policies

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 number of simultaneous associations depends on the usage profile. At a certain point of time there might be active simultaneously:

1 association for Verification

1 association for Storage

1 association for Storage Commitment

1 association for Query/Retrieve - MOVE

n associations for Modality Worklist - FIND, depending on whether search criteria are changed while a previous query is still active (no response yet)

SOP Class Name SOP Class UID SCU SCP

Verification 1.2.840.10008.1.1 Yes Yes

Storage Commitment Push Model SOP Class

1.2.840.10008.1.20.1 Yes No

Raw Data Storage 1.2.840.10008.5.1.4.1.1.66 Yes Yes


1.2.840.10008.5.1.4.1.1.77.1.5.1 Yes No

Ophthalmic Visual Field Static Perimetry Measurements Storage

1.2.840.10008.5.1.4.1.1.80.1 No 3)

No 3)

Encapsulated PDF Storage 1.2.840.10008.5.1.4.1.1.104.1 No 2)

No 2)


1.2.840.10008.5.1.4.1.2.1.1 Yes 1)

No

Study Root Query/Retrieve Information Model - FIND

1.2.840.10008.5.1.4.1.2.2.1 Yes 1)

No

Study Root Query/Retrieve

Information Model – MOVE

1.2.840.10008.5.1.4.1.2.2.2 Yes No

Modality Worklist

Information Model - FIND

1.2.840.10008.5.1.4.31 Yes No



n associations for Query/Retrieve - FIND, depending on whether search criteria are changed while a previous query is still active (no response yet)

Table 4-3 Number of associations

Maximum number of simultaneous associations 50

4.2.1.2.3 Asynchronous Nature

HFA 3 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.20

Implementation Version Name NIM-2.8

4.2.1.3 Association Initiation Policy

4.2.1.3.1 Activity – Verify Communication

4.2.1.3.1.1 Description and Sequencing of Activities

This activity is available during the configuration phase. It facilitates the setup and management of the DICOM Application Entities.

The user can test the application level communication between instrument’s software Application Entity and its peer DICOM Application Entities. During one test call, all peer DICOM Application Entities are contacted.

In the association request HFA 3 Application Software proposes not only Verification SOP Class, but also all other SOP Classes as supported by the instrument's DICOM interface.

The association is established when the peer DICOM entity accepts the verification related presentation context. In a sub-sequent step a C-ECHO message is exchanged.

The results of the “Verify Communication” activity are shown to the user as success or failure. For e. g. a Storage Provider not only the Verification information is evaluated, but also the acceptance of the proposed presentation context comprising the respective Storage SOP Classes.

4.2.1.3.1.2 Proposed Presentation Contexts

Following presentation contexts are offered for each initiated association. During this activity the Application Software uses only

Verification with Transfer Syntax ILE as SCU

Table 4-5 Presentation Contexts proposed by the HFA 3 AE

Presentation Context Table

Abstract Syntax Transfer Syntax Role Ext. Neg.

Name UID 1.2.840.10008. ...

Name List

UID List 1.2.840.10008. ...

Verification 1.1 ILE 1.2 BOTH 3) Yes

Storage Commitment Push Model 1.20.1 ILE 1.2 SCU No

Raw Data Storage 5.1.4.1.1.66 ILE 1.2 BOTH 3) No

ELE 1.2.1 BOTH 3) No




5.1.4.1.1.77.1.5.1 JPG-1 1.2.4.50 SCU No

Encapsulated PDF Storage 5.1.4.1.1.104.1 ILE 1.2 BOTH 3) No 2)

ELE 1.2.1 BOTH 3) No 2)


5.1.4.1.2.1.1 ILE 1.2 SCU Yes 1)


5.1.4.1.2.2.1 ILE 1.2 SCU Yes 1)

Study Root Query/Retrieve Information Model - MOVE

5.1.4.1.2.2.2 ILE 1.2 SCU No


5.1.4.31 ILE 1.2 SCU No


Note 2: HFA 3 relies on FORUM Glaucoma Workplace for ePDF creation. HFA 3 does not store or generate ePDF itself.

Note 3: Only acts as SCP when a C-Move-RQ was initiated first and this association is still open.

Note: HFA 3 in local database mode provides no DICOM connectivity. In this case the application can print pdf reports to a windows printer.

4.2.1.3.1.3 SOP Specific Conformance for Verification SOP Class

The HFA 3 Application Software provides standard conformance.

4.2.1.3.2 Activity – Query Modality Worklist

The worklist contains scheduling information for patients. Query Modality Worklist is used to search for the right scheduling information for this instrument. An operator has two options to perform this activity.


Option “Todays Patients query” In this case, the Application Software performs a query with predefined query keys. The operator cannot change the query key values. The applied query keys are:

Table 4-6 Modality Worklist Query for Today's Patients

Tag Attribute Name Description

(0040,0100) Scheduled Procedure Step Sequence

>(0040,0001) Scheduled Station Application Entity Title

Uses the value as configured for the HFA 3 instrument.

>(0040,0002) Scheduled procedure Step Start Date Uses the date of today.

All matching worklist items are subject to be imported into the local database.

This default query can be manually triggered by simply pressing the button in the header of the “Today” list. This default query is also triggered automatically in a configurable interval to keep the "Today" List up to date.

Option “Interactive query” The query keys of the “Interactive query” can be modified by the operator. To invoke this the operator has to use “Advanced” in the main screen and use the tab “Scheduled Patients”. This screen will provide all available search fields for the Modality Worklist search.



Figure 4-7 Interactive Query

Trigger “Query Modality Worklist” The activity “Query Modality Worklist” can be triggered by the operator at any time if no other activity is in progress. To invoke this the operator has to use “Advanced” in the main screen and use the tab “Scheduled Patients”. It is meaningful to perform the query when the patient arrives at the modality. Then the worklist contains latest information.

Edit or modify query keys The Modality Worklist query offers a GUI for interactive query. The “Station” is prefilled with the instrument AE title and the “Schedule date” is predefined with today. All predefined values can be changed. The operator can change or fill in search criteria in the shown dialog. For instance, the incomplete patient name or the patient ID can be used.

Trigger query The operator triggers the search after he filled in search criteria. The Application Software sends a DICOM C-FIND request, which contains the search criteria. The Application Software waits for the response from the partner Application Entity. Application Software will accept up to a configurable number of matches. The Application Software checks whether the number of received worklist items overstepped the configurable limit. If the number of received worklist items overstepped the limit, then the Application Software sends a C-CANCEL-RQ, then an A-RELEASE-RQ to the service provider and a message is displayed. Despite this warning, the operator gets the (partial) result in the result-list.

sd Interactiv e query

Santa Cruz

Acquisition

Modality AE

Modality Worklist

AE

opt

Trigger "Query Modality Worklist"()

Edit or modify query keys()

Trigger query()

C-FIND()

Response()

Update result l ist()

Select item from result l ist()

Detailed view()

Show worklist item in main screen()



After receiving the response, the pick-list is updated. The result-list provides the most important information for a quick overview (see section 4.2.1.3.2.3 for the supported set of tags).

The operator can start over, redefine query keys and trigger the query again. This can be performed as often as required, until the correct worklist item(s) are found.

Select item in result-list The operator can select one worklist item in the pick-list. The selected item becomes subject for a detailed view or it can be imported into the Application Software.

Activate detailed view The detailed view allows a closer look to the currently selected worklist item. Thus the operator can see more information about patient information and schedule information.

Show worklist item in main screen The operator can take over the selected item at any time. The data is stored in the list of “Today”. The Application does not persist this data yet. This is done when the instance is stored in the database.

After all that, the operator can start the examination of the patient and acquire scan data.



"Modality Worklist Information Model - FIND" with Transfer Syntax ILE as SCU

Table 4-8 Proposed Presentation Contexts by the HFA 3 AE



Name UID 1.2.840.10008. ...

Name List

UID List 1.2.840.10008. ...

Verification 1.1 ILE 1.2 BOTH No


Raw Data Storage 5.1.4.1.1.66 ILE 1.2 BOTH3 No

ELE 1.2.1 BOTH3 No


5.1.4.1.1.77.1.5.1 JPG-1 1.2.4.50 SCU No

Encapsulated PDF Storage 5.1.4.1.1.104.1 ILE 1.2 BOTH 3)

No 2)

ELE 1.2.1 BOTH 3)

No 2)


5.1.4.1.2.1.1 ILE 1.2 SCU Yes 1)


5.1.4.1.2.2.1 ILE 1.2 SCU Yes1)


5.1.4.1.2.2.2 ILE 1.2 SCU No


5.1.4.31 ILE 1.2 SCU No






4.2.1.3.2.3 SOP Specific Conformance for Modality Worklist SOP Class

Table 4-9 Modality Worklist C-FIND Response Status Handling Behavior

Service Status Further Meaning

Error Code Behavior

Failure Refused: Out of Resources

A700 Log message and display user alert message.

Failure Identifier Does Not Match SOP Class

A900 Log message and display user alert message.

Failure Unable to process

C000-CFFF Log message and display user alert message.

Failure Refused: SOP class not supported

0122 Log message and display user alert message.

Cancel Matching terminated due to Cancel request

FE00 Log message

Success Matching is complete

0000 The Software Application stops receiving worklist items. It finally updates the pick list.

Pending Matches are continuing – Current Match is supplied and any Optional Keys were supported in the same manner as Required Keys

FF00 Log message. The Application Software checks whether the number of received worklist items overstepped the configurable limit. If the number of received worklist items overstepped the limit, then the Application Software sends a C-CANCEL-RQ, then an A-RELEASE-RQ to the service provider and a message is displayed.

Pending Matches are continuing – Warning that one or more Optional Keys were not supported for existence and / or matching for this Identifier


Unknown All other responses with unknown code meaning

xxxx Log message and display user alert message



Table 4-10 Attributes involved in Modality Worklist C-FIND request and response

Tag Tag Name

Qu

ery

Ke

y

Imp

ort

ed

Dis

pla

yed

Mo

dif

iab

le

SO

P I

ns

tan

ce

Scheduled Procedure Step (SPS)


>(0040,0001) Scheduled Station Application Entity Title

BRQ, DEF X PLD X

>(0040,0003) Scheduled Procedure Step Start Time X PLD X

>(0040,0002) Scheduled Procedure Step Start Date BRQ, DEF X PLD X

>(0008,0060) Modality BRQ X PLD X

>(0040,0006) Scheduled Performing Physicians Name

>(0040,0007) Scheduled Procedure Step Description X PLD X

>(0040,0010) Scheduled Station Name

>(0040,0011) Scheduled Procedure Step Location

>(0040,0008) Scheduled Protocol Code Sequence X X

>>(0008,0100) Code Value X X

>>(0008,0102) Coding Scheme Designator X X

>>(0008,0103) Coding Scheme Version X X

>>(0008,0104) Code Meaning X PLD X

>(0040,0012) Pre-Medication

>(0040,0009) Scheduled Procedure Step ID X X

>(0032,1070) Requested Contrast Agent

Requested Procedure

(0040,1001) Requested Procedure ID PBQ X PLD X

(0032,1060) Requested Procedure Description X PLD X

(0032,1064) Requested Procedure Code Sequence X X

>(0008,0100) Code Value X X

>(0008,0102) Coding Scheme Designator X X

>(0008,0103) Coding Scheme Version X X

>(0008,0104) Code Meaning X PLD X

(0020,000D) Study Instance UID X X

(0008,1110) Referenced Study Sequence X X

>(0008,1150) Referenced SOP Class UID X X

>(0008,1155) Referenced SOP Instance UID X X

(0040,1003) Requested Procedure Priority

(0040,1004) Patient Transport Arrangements

(0040,1400) Requested Procedure Comments X

Imaging Service Request



Tag Tag Name

Qu

ery

Ke

y

Imp

ort

ed

Dis

pla

yed

Mo

dif

iab

le

SO

P I

ns

tan

ce

(0008,0050) Accession Number PBQ X PLD X

(0032,1032) Requesting Physician X

(0008,0090) Referring Physicians Name X PLD X

Visit Identification

(0038,0010) Admission ID

Visit Status

(0038,0300) Current Patient Location

Visit Relationship

(0008,1120) Referenced Patient Sequence

>(0008,1150) Referenced SOP Class UID

>(0008,1155) Referenced SOP Instance UID

Patient Identification

(0010,0010) Patients Name1 PBQ X PL, PLD, APP

X

(0010,0020) Patients ID PBQ X PL, PLD, APP

X

(0010,0021) Issuer of Patient ID X X

(0010,1000) Other Patient IDs X X

Patient Demographic

(0010,0030) Patients Birth Date X PL, PLD, APP

X

(0010,0040) Patients Sex X PL, PLD, APP

X

(0010,1030) Patients Weight

(0040,3001) Confidentiality Constraint on Patient Data Description

(0010,4000) Patients Comments X X

Patient Medical

(0038,0500) Patient State

(0010,21C0) Pregnancy Status

(0010,2000) Medical Alerts

(0038,0050) Special Needs

Note 1: If the multicomponent group name representation is enabled then the name components with Priority 1 are shown in the Pick List and Detail Dialog. The name components which have been entered as query key will be always sent in the Alphabetic group of the C-Find-RQ (see section 4.4.2.1 for the setting of multicomponent group names).



Values of column “Query Key”:

PBQ A tag that is marked with PBQ is used as query key in the Patient Based Query mode of the interactive Modality Worklist Query Dialog.

BRQ A tag that is marked with BRQ is used as query key in the Broad Query mode of the interactive Modality Worklist Query Dialog.

DEF A tag that is marked with DEF has a value assigned when the interactive Modality Worklist Query Dialog is shown the first time or when the Reset button is pushed.

Default values can get modified. The modifications will be stored for next use of Modality Worklist Query Dialog.

RNG The operator can apply a range as value for the query key.

SEL The operator can select a value from a given list of values.

Values of column “Imported”:

X The value gets imported in the application. Thus this value may have influence in Information Objects which will be created as a result of the performed examination.

Values of column “Displayed”:

PL Values of this tag are instantly visible in the pick list.

PLD Values of this tag are visible in the details dialog of the current selected pick list item.

APP Values of this tag are visible in the application.

Values of column “Modifiable”:

X A value which has been imported to the application might be modified inside the application.

Values of column SOP Instance:

X Values of marked tags will be stored in created SOP Instances. See section 8.1.3 “Attribute Mapping”.

Following set of tags can be used as query key in the so called “Patient Based Query”. The Patient Based Query is a working mode of the Modality Worklist Query Dialog.

Table 4-11 Modality Worklist query key details - Patient Based Query

Tag Tag Name Description

(0010,0010) Patients Name1)

The HFA 3 Application Software supports family name and given name only.

The operator can use ‘*’ or ‘?’ as wild cards. A “*” wildcard will automatically added at the end.

(0010,0020) Patient ID The operator can enter a string which conforms to the Value Representation LO.

(0008,0050) Accession Number The operator can enter a string which conforms to the Value Representation SH.

(0040,1001) Requested The operator can enter a string which conforms to the



Procedure ID Value Representation SH.

Note 1: If the multicomponent name representation is enabled than the name component what have been entered as query key (Alphabetic, Ideographic or Phonetic) will be always sent in the Alphabetic group of the C-Find-RQ (see section 4.4.2.1 for the setting of multicomponent group names).

Following set of tags can be used as query key in the so called “Broad Query”. The Broad Query is a working mode of the Modality Worklist Query Dialog.

Table 4-12 Modality Worklist query key details - Broad Query



This attribute is the container for the tags as listed below. The sequence contains one item.

>(0040,0002) Scheduled Procedure Step Start Date

The default value is today’s date.

The operator can change the value to tomorrow, week and can even enter date ranges.

>(0008,0060) Modality The operator can change the value and select one value of a predefined set of values including an empty string. Possible values are “OAM”, “OP”, “OPM”, “OPT”, “OPV”, “IOL”.

>(0040,0001) Scheduled Station AE Title

Value set from the DICOM configuration user interface on HFA 3

4.2.1.3.3 Activity - Query remote AE for patients

Query is used to get patient information and meta data of instances on a DICOM server.


There are two ways for the user to trigger a query request. The “Quick search” in the main screen will search in “Patient Given Name”, “Patient Last Name”, “Patient ID” and “Patient Birth Date” in parallel. The second way is the “Advanced” search. The user can select this search by clicking the “Advanced” button in the main screen.



Figure 4-4 Query remote AE for patients

Trigger “Query remote AE for patients” The activity “Query remote AE for patients and data” can be triggered by the operator by using the “Quick search” or change to the “Advanced” screen.

Edit or modify query keys The “Advanced” screen offers a GUI for interactive query. The operator can change or fill in search criteria in the shown search fields.

The top-most search field in the main screen is the “Quick search” field. Any value entered herein is applied to

(0010,0010) Patient’s Name – Family Name

(0010,0010) Patient’s Name – Given Name

(0010,0020) Patient ID

(0010,0030) Patient's Birth Date in DICOM date format.

and issued as three separate requests. In case Patient’s Birth Date is entered a forth request will be triggered. The entered value has automatically a trailing wildcard to fulfill the ‘contains’ condition.

For more details on supported query keys see Table 4-19 Query key details.

Trigger query The operator triggers the search after he or she filled in search criteria by either pressing the “Enter” key or click on the “Search” button. The Application Software sends a Patient Root based DICOM C-FIND request which contains the entered search criteria. The Application Software waits for the response from the Query AE and accepts up to a configurable number of matches. If the number of matches exceeds this limit, the Application Software shows an information about truncated search results and a request to apply more specific query keys. Despite this warning, the operator gets results in the pick-list.

sd Query remote AE for patients

Santa Cruz

Acquisition

Modality AE

Query AE

Trigger "Query remote AE for patients"()

Edit or modify query keys()

Trigger query()

C-FIND (Patient Root)

Response()

Update patient l ist()

sync with local data()



After receiving the response, the patient pick-list is updated. The patient pick-list provides the most important information for a quick overview.

The operator can start over, redefine query keys and trigger the query again. This can be performed as often as required, until he or she finds the correct patient entry.

Important note: For this activity it is required that the SCP supports the Relational query model since HFA 3 Application Software does not use the Hierarchical model.



"Patient Root Query/Retrieve Information Model - FIND" with Transfer Syntax ILE as SCU

"Study Root Query/Retrieve Information Model - FIND" with Transfer Syntax ILE as SCU

Important note: For this activity it is required that the SCP supports the Relational query model since Application Software does not use the Hierarchical model.




Name UID 1.2.840.10008. ...

Name List

UID List 1.2.840.10008. ...




ELE 1.2.1 BOTH3 No


5.1.4.1.1.77.1.5.1 JPG-1 1.2.4.50 SCU No


No 2)

ELE 1.2.1 BOTH 3)

No 2)


5.1.4.1.2.1.1 ILE 1.2 SCU Yes 1)


5.1.4.1.2.2.1 ILE 1.2 SCU Yes1)


5.1.4.1.2.2.2 ILE 1.2 SCU No


5.1.4.31 ILE 1.2 SCU No






4.2.1.3.3.3 SOP Specific Conformance for Patient Root and Study Root Query/Retrieve SOP Class as SCU

Table 4-14Query C-FIND Response Status Handling Behavior


Error Code behavior


A700 Log message and display user alert.

Failure Identifier does not match SOP Class

A900-A9FF Log message and display user alert.


C000-CFFF Log message and display user alert.


0122 Log message and display user alert


FE00 None

Success Matching is complete – No final Identifier is supplied




Pending Matches are continuing – Warning that one or more Optional Keys were not supported for existence and / or matching for this Identifier.



xxxx Log message and display user alert

Table 4-15 PATIENT level keys for the Patient Root Query/Retrieve Information Model (query and return keys)

Tag Tag Name

Qu

ery

Key

Imp

ort

ed

Dis

pla

yed

Mo

dif

iab

le

SO

P I

ns

tan

ce

(0010,0010) Patient’s Name1)

X X X

(0010,0020) Patient ID X X X



(0010,0021) Issuer of Patient ID X

(0010,0030) Patient’s Birth Date RNG X X

(0010,0032) Patient’s Birth Time X

(0010,0040) Patient’s Sex X X

(0010,1000) Other Patient IDs X

(0010,2160) Ethnic Group X

(0010,4000) Patient Comments X


Table 4-16 STUDY level keys for the Patient Root Query/Retrieve Information Model (query and return keys)

Tag Tag Name

Qu

ery

Ke

y

Imp

ort

ed

Dis

pla

yed

Mo

dif

iab

le

SO

P I

ns

tan

ce

(0008,0020) Study Date

(0008,0030) Study Time

(0008,0050) Accession Number X

(0008,0061) Modalities in Study

(0008,0090) Referring Physician’s Name X

(0008,0090) Study Description

(0008,1080) Admitting Diagnoses Description

(0020,0010) Study ID

(0020,000D) Study Instance UID

Table 4-17 SERIES level keys for the Patient Root Query/Retrieve Information Model (query and return keys)

Tag Tag Name

Qu

ery

Key

Imp

ort

ed

Dis

pla

yed

Mo

dif

iab

le

SO

P I

ns

tan

ce

(0008,0021) Series Date

(0008,0031) Series Time

(0008,0060) Modality SEL

(0008,103E) Series Description

(0008,1050) Performing Physician’s Name

(0008,1090) Manufacturer’s Model Name

(0020,000E) Series Instance UID



(0020,0011) Series Number

(0020,0060) Laterality

(0040,0244) Performed Procedure Step Start Date

(0040,0245) Performed Procedure Step Start Time

(0040,0275) Request Attributes Sequence

Table 4-18 IMAGE level keys for the Patient Root Query/Retrieve Information Model (query and return keys)

Tag Tag Name

Qu

ery

Ke

y

Imp

ort

ed

Dis

pla

yed

Mo

dif

iab

le

SO

P I

ns

tan

ce

(0008,0008) Image Type

(0008,0012) Instance Creation Date

(0008,0013) Instance Creation Time

(0008,0016) SOP Class UID

(0008,0018) SOP Instance UID

(0008,002A) Acquisition DateTime RNG

(0008,114A) Referenced Instance Sequence



(0020,0013) Instance Number

(0020,0062) Image Laterality


RNG The operator can apply a range as value for the query key.

SEL The operator can select a value from a given list of values.

X The value is included in the query request if not empty.

AUTO The value cannot be modified by the operator.




X Values of this tag are instantly visible in the pick list.







Table 4-19 Query key details



The default value is empty string.

Only family name, middle name and given name can be used as query keys. The operator can use '*' or '?' as wild cards.

This is a DICOM Standard query key on Patient level.

(0010,0020) Patient ID The default value is empty string.

The operator can enter each value that conforms to the Value Representation LO.


(0010,0030) Patient’s Birth Date The default value is empty date.

The operator can enter a specific value that conforms to the Value Representation DA. The operator can also select from a range of dates.

This is a DICOM Optional query key on Patient level, thus the effect of this query key on the query depends on Service Provider implementation.

(0008,0050) Accession Number The default value is empty string.

The operator can enter each value that conforms to the Value Representation SH.

This is a DICOM Standard query key on Study level.

(0008,0090) Referring Physician’s Name2)

The default value is empty string.

Only family name can be used as query key.

This is a DICOM Optional query key on Study level, thus the effect of this query key on the query depends on Service Provider implementation.

(0008,0060) Modality The default value is empty string.

The operator can select from a list of pre-defined values and the application software will convert the selection to a value that conforms to the Value Representation CS.

This is a DICOM Standard query key on Series level.




Note 2: Only Alphabetic part of the multicomponent group name is used as query key

4.2.1.3.4 Activity – Acquire data

After the operator selects a patient, a visual field exam can be performed. Before the operator starts the exam it is possible to change test profiles, test parameters, eye laterality and patient distance prescription. When the operator presses the “Next” button in the scheduled case the most recent scheduled procedure step will automatically be taken and all associated information will be mapped into the storage IOD instances.

The patient data, exam parameters and test data will be stored as Raw Data and Ophthalmic Photography 8 Bit SOP Instances. Ophthalmic Photography 8 Bit SOP Instances will only be stored if the RelEYE Eye Monitor is set to ON.

4.2.1.3.5 Activity – Store data to remote AE

When the operator selects the “Save and Exit” button from the Results screen, the RAW Data and Ophthalmic Photography 8 Bit SOP Instances for the exam will be sent to the configured storage provider.


Figure 4-5 Archive Data

Trigger “Save and Exit” This activity can be triggered in the patient details by clicking on the “Save and Exit” button from the Results screen.

The saved exam is send via a RAW Data Storage and Ophthalmic Photography 8 Bit Image Storage to the configured storage provider.

sd Archiv e data

Santa Cruz

Acquisition

Modality AE

Storage AE Storage

Commitment AE

loop Interv al

Save and Exit()

create DICOM

instances()


Request commitment for stored but uncommitted instances()

N-ACTION (SOP instance UIDs)

N-EVENT-REPORT()



Request commitment for stored but uncommitted instances To verify that the data has been archived, the Application Software asks the configured Storage Commitment AE in a configurable interval to commit storage of instances.

The application will verify commitment of instances after a predefined interval.

Data that has been successfully archived and storage committed is subject to be deleted at shutdown.



Raw Data Storage with Transfer Syntax ILE as SCU

OP 8Bit Image Storage with Transfer Syntax JPG-1 as SCU

Storage Commitment Push Model with Transfer Syntax ILE as SCU

Table 4-20 Presentation Contexts proposed by HFA 3 AE



Name UID 1.2.840.10008. ...

Name List

UID List 1.2.840.10008. ...




ELE 1.2.1 BOTH3 No


5.1.4.1.1.77.1.5.1 JPG-1 1.2.4.50 SCU No


No 2)

ELE 1.2.1 BOTH 3)

No 2)


5.1.4.1.2.1.1 ILE 1.2 SCU Yes 1)


5.1.4.1.2.2.1 ILE 1.2 SCU Yes1)


5.1.4.1.2.2.2 ILE 1.2 SCU No


5.1.4.31 ILE 1.2 SCU No




4.2.1.3.5.3 SOP Specific Conformance for Storage SOP Classes

Table 4-21 Storage C-STORE Response Status Handling behavior


Status Code Behavior




A700-A7FF Log message and retry c-store. If error persists then message to user.

Failure Error: Data Set does not match SOP Class

A900-AFF Log message and do not retry. Message to user.

Failure Error: Cannot understand

C000-CFFF Log message and do not retry. Message to user.


0122 Log message and show user alert.

Warning Coercion of data Elements

B000 The Application Software logs this event.

Warning Data Set does not match SOP Class


Warning Elements Discarded


Success Successful Storage

0000 None

Unknown All other responses with unknown code

xxxx Log message and do not retry. Message to user.

4.2.1.3.5.4 SOP Specific Conformance for Storage Commitment SOP Class

4.2.1.3.5.4.1 Storage Commitment Operations (N-ACTION)

The Application Software will request storage commitment for instances of the Raw Data and Ophthalmic Photography 8 Bit Image Storage if the Remote AE is configured as Storage Commitment Provider and a presentation context for the Storage Commitment Push Model has been accepted.

The Storage Commitment Request addresses at least one SOP Instance and at maximum 500 SOP instances.

The behavior of the Application Software when encountering status codes in a N-ACTION response is summarized in the table below:

Table 4-22 Storage Commitment N-ACTION Response Status Handling Behavior



Failure Class-instance conflict

0119 Log message and display user alert.

Failure Duplicate invocation

0210 Log message.

Failure Invalid argument value


Failure Invalid SOP Instance


Failure Mistyped argument


Failure No such action 0123 Log message and display user alert.

Failure No such argument




Failure No such SOP class


Failure No such SOP Instance

0112 Log message.

Failure Processing failure


Failure Resource limitation

0213 Log message.

Failure Unrecognized operation


Success Success 0000 The Application Software will wait for an incoming N-EVENT-REPORT.

Unknown All other responses with unknown code meaning.

xxxx Log message and display user alert.

4.2.1.3.5.4.2 Storage Commitment Communication Failure Behavior

If the Application Software runs in a timeout or if the association is aborted by the provider or network layer, or if waiting duration for Storage Commitment N-EVENT-REPORT oversteps a configurable time limit then the related SOP Instance is considered as not being committed. Then the SOP Instance is subject of a future Storage Commitment service call. It will be included again within next call of this activity.

In addition to that, the Application Software writes the SOP Instance UID to the log file, together with the failure reason.

4.2.1.3.6 Activity - Retrieve data from remote AE

When the user selects a patient, a Study Root Query is triggered to query for meta information of the most recent HFA exam. If a previous and most recent exam of the left and right eye was found for the selected patient, the HFA 3 automatically retrieves the associated Raw Data Storage SOP instance(s) to obtain the vision prescription data for that patient.




Figure 4-6 Get last exam

Select patient from patient list The operator can select one patient entry from the patient list. Once the item is selected the Application Software sends a DICOM C-FIND request using relational Study Root Query/Retrieve SOP Class on INSTANCE level. Within the DICOM C-FIND request all patient level return values from the previous Patient Root Query/Retrieve are used as query keys. Additionally it will use the SOP Class UID for RAW Data Storage and the modality (OPV) to get the exams (RAW Data Storage) from the selected patient in the DICOM C-FIND response. The result will be filtered afterwards to get only the prescription information from the last examination for the left and right eye .

The Application Software synchronize the local data model and query result information. If any synchronization problems appears the DICOM server is the leading system.

In general the combination of patient id + issuer of patient id is assumed to be unique for a patient. In case of a conflict, (the same patient id + issuer of patient id is used for a different patient), the application will only show the patient coming from the DICOM server. The application will trigger a storage request for the data of the conflicting local patient as this patient will become hidden and be deleted later on.

The operator can select another entry from the patient list even when an active request is still in progress. In this case another request will be started in parallel and the results from the previous request will get finished.

sd filter on last right and left eye examination - RAW IOD

Santa Cruz

Acquisition

Modality AE

Retrieve AEQuery AE

Select patient from patient l ist()

C-FIND (Study Root)

using defined query keys

Response()

C-MOVE (Study Instance UID, Series Instance

UID, SOP Instance UID)

C-STORE()

test screen prepopulated with

available settings ()



Important note: For this activity it is required that the SCP supports the Relational query model since HFA3 Application Software does not use the Hierarchical model.



“Study Root Q/R Information Model - FIND" with Transfer Syntax ILE as SCU

“Study Root Q/R Information Model - MOVE" with Transfer Syntax ILE as SCU

“Raw Data Storage” with Transfer Syntax ELE or ILE as SCP




Name UID 1.2.840.10008. ...

Name List

UID List 1.2.840.10008. ...



Raw Data Storage 5.1.4.1.1.66 ILE 1.2 BOTH3) No

ELE 1.2.1 BOTH3) No


5.1.4.1.1.77.1.5.1 JPG-1 1.2.4.50 SCU No


No 2)

ELE 1.2.1 BOTH 3)

No 2)


5.1.4.1.2.1.1 ILE 1.2 SCU Yes 1)


5.1.4.1.2.2.1 ILE 1.2 SCU Yes1)

Study Root Query/Retrieve IM - MOVE

5.1.4.1.2.2.2 ILE 1.2 SCU No


5.1.4.31 ILE 1.2 SCU No




4.2.1.3.6.3 SOP Specific Conformance for Patient Root and Study Root Query/Retrieve SOP Class as SCU

Table 4-24 Query C-FIND Response Status Handling behavior


Error Code behavior


A700 Log message and display user alert.




Error Code behavior


A900-A9FF Log message and display user alert.


C000-CFFF Log message and display user alert.




FE00 None





Pending Matches are continuing – Warning that one or more Optional Keys were not supported for existence and / or matching for this Identifier.




Table 4-25 Retrieve C-MOVE Response Status Handling Behavior


Error Code behavior

Failure Refused: Out of Resources – Unable to calculate number of matches

A701 Log message and retry. If error persists display user alert

Failure Refused: Out of Resources – Unable to perform sub-operations

A702 Log message and retry. If error persists display user alert

Failure Refused: Move Destination unknown

A801 Log message and display user alert




Error Code behavior


A900-A9FF Log message and display user alert

Failure Unable to Process

C000-CFFF Log message and display user alert



Cancel Sub-operations terminated due to Cancel Indication

FE00 Log message.

Warning Sub-operations Complete – One or more Failures

B000 Log message.


0000 The Application Software returns from this activity.


FF00 Log message.



Table 4-26STUDY level keys for the Study Root Query/Retrieve Information Model (query and return keys)

Tag Tag Name

Qu

ery

Key

Imp

ort

ed

Dis

pla

yed

Mo

dif

iab

le

SO

P I

ns

tan

ce

(0010,0010) Patient’s Name 1)

AUTO

(0010,0020) Patient ID AUTO

(0010,0021) Issuer of Patient ID AUTO

(0010,0030) Patient’s Birth Date AUTO

(0010,0032) Patient’s Birth Time

(0010,0040) Patient’s Sex AUTO

(0010,1000) Other Patient IDs

(0010,2160) Ethnic Group



(0010,4000) Patient Comments

(0008,0020) Study Date X

(0008,0030) Study Time X

(0008,0050) Accession Number X

(0008,0061) Modalities in Study

(0008,0090) Referring Physician’s Name X

(0008,1080) Admitting Diagnoses Description

(0020,0010) Study ID X

(0020,000D) Study Instance UID X

(0008,1030) Study Description X


Table 4-27SERIES level keys for the Study Root Query/Retrieve Information Model (query and return keys)

Tag Tag Name Q

ue

ry K

ey

Imp

ort

ed

Dis

pla

yed

Mo

dif

iab

le

SO

P I

ns

tan

ce

(0008,0021) Series Date X

(0008,0031) Series Time X

(0008,0060) Modality AUTO X

(0020,0011) Series Number X

(0020, 000E) Series Instance UID X

(0008, 103E) Series Description X

(0008,1050) Performing Physician's Name X

(0008,1090) Manufacturer’s Model Name X

(0020,0060) Laterality

(0040,0244) Performed Procedure Step Start Date X

(0040,0245) Performed Procedure Step Start Time X

(0040,0275) Request Attributes Sequence

Table 4-28 IMAGE level keys for the Study Root Query/Retrieve Information Model (query and return keys)

Tag Tag Name

Qu

ery

Key

Imp

ort

ed

Dis

pla

yed

Mo

dif

iab

le

SO

P I

ns

tan

ce

(0008,0008) Image Type



(0008,0012) Instance Creation Date

(0008,0013) Instance Creation Time

(0008,0016) SOP Class UID AUTO X

(0008,0018) SOP Instance UID X

(0008,002A) Acquisition DateTime X

(0008,114A) Referenced Instance Sequence



(0020,0013) Instance Number X

(0008,0023) Content Date X

(0020,0062) Image Laterality X


X The value is included in the query request if not empty.

AUTO The value cannot be modified by the operator.




X Values of this tag are instantly visible in the pick list.





Table 4-29 Query key details



This attribute is used as query key automatically when the operator selects a patient from the patient list and the application starts querying the remote AE for “Visits” and “Exams”.

The value assigned conforms to the value gathered from the previous Patient root Query.


(0010,0020) Patient ID This attribute is used as query key automatically



when the operator selects a patient from the patient list and the application starts querying the remote AE for “Visits” and “Exams”.


The value conforms to the Value Representation LO.


(0010,0021) Issuer of Patient ID This attribute is used as query key automatically when the operator selects a patient from the patient list and the application starts querying the remote AE for “Visits” and “Exams”.



(0010,0030) Patient’s Birth Date This attribute is used as query key automatically when the operator selects a patient from the patient list and the application starts querying the remote AE for “Visits” and “Exams”.


The value conforms to the Value Representation DA. This is a DICOM Optional query key on Patient level, thus the effect of this query key on the query depends on Service Provider implementation.

(0010,0040) Patient’s Sex This attribute is used as query key automatically when the operator selects a patient from the patient list and the application starts querying the remote AE for “Visits” and “Exams”.

The value assigned conforms to the value gathered from the previous Patient root Query. The value conforms to the Value Representation CS.


(0008,0060) Modality Value always “OPV”

(0008,0016) SOP Class UID Value: “1.2.840.10008.5.1.4.1.1.66” identifies RAW IOD.

Note 1: If the multicomponent name representation is enabled than all three name components are used as C-Find-RQ query key (Alphabetic, Ideographic and Phonetic) (see section 4.4.2.1 for the setting of multicomponent group names).



4.2.1.3.7 Activity – File Import

This Activity is only available in the local database mode. Therefore it has no effect on DICOM messaging.

The Operator can trigger “File import” at any time if no other activity is in progress.

During this activity, the Application Software imports scan data that has been created by the Application Software instances other than this instance. RAW and OP can be imported.

4.2.1.3.8 Activity – File Export (OPV and PDF Data)

This Activity is only available in the local database mode. Therefore it has no effect on DICOM messaging.

With a special license the HFA 3 can be configured to store the OPV IOD to the local hard drive. OPV IOD’s are never sent via DICOM.

Operator can trigger “File Export” for Reports (PDF and/or OPV Data) or Tests (RAW and OP Data).

4.2.1.3.9 Activity – Delete data

The activity "Delete data" can either be invoked manually by the operator or triggered automatically by software application. Typically this can be invoked for single data instances or a series of data instances or complete patient data.

HFA3 in Standalone Mode HFA3 in Connected Mode

Manual Deletion

Patients can be deleted from the patient list. Deletion will be immediate.

Not available

Automatic Deletion

Not available

Patients will be deleted from HFA 3 if storage commitment was successful.

Storage commitment will be attempted on system shutdown and on defined Storage Commitment interval.

Manual invocation:

The operator can invoke this activity from the "Patient" screen by pressing the "Delete" button shown for a certain measurement, a complete group of measurements or a patient. When connected to a DICOM network, an instance or a patient cannot be removed from the modality until the storage to a remote AE is successfully completed and committed.

Manually triggered deletion of data is performed immediately.

Automatic invocation: Automatically triggered deletion is done during the shutdown process and will be performed for any instance where the storage to a remote AE is successfully completed and committed. Patient demographic data will only be deleted from the modality after all related storage instances have been successfully deleted.

Furthermore the software application provides configurable options for automatic deletion of data in case of certain error conditions:

Delete Exam when "Instance not found":

When configured with Delete Exam, the affected instance, that cannot be found anymore on the remote AE, is flagged for deletion as soon as the Storage Commitment report contains a failure reason “instance not found” for this particular instance. The deletion of the instance happens on next shutdown.



Re-Archive when "Instance not found": When configured with Re-Archive, the affected instance is re-archived immediately when storage commitment reports a failure reason "Instance not found". New Storage Commitment will be requested in a future Storage Commitment call. In case the new Storage Commitment fails again it will be retried until the maximum number of retries (3 Storage Commitment calls) is reached.

Delete when "Failed Instances": When the user hits the Delete Button all instances which are in Storage Commitment error status (any error or failure reason other than “Instance not found”) will be marked for deletion when the maximum number of retries (3 Storage Commitment calls) is reached. Deletion happens on next shutdown.

Reset when "Failed Instances": When the user hits the Reset Button all instances which are in Storage Commitment error status (any error or failure reason other than “Instance not found”) will be marked as already archived, but not storage committed. The status for these instances will be reset as if no storage commitment has been ever requested before. In a future Storage Commitment call the Application Software will request again storage commitment for these particular instances and retries any future failed storage commitment until the maximum number of retries (3 Storage Commitment calls) is reached.

4.2.1.4 Association Acceptance Policy

4.2.1.4.1 Activity – Verify Communication

The activity can be performed from the network settings screen when an exam is not being performed.


The Software AE responds to verification requests made by remote AEs.

4.2.1.4.1.2 Accepted Presentation Contexts

Table 4-30 Presentation Context accepted by the HFA 3 AE


Abstract Syntax Transfer Syntax Role Ext. Neg. Name UID

1.2.840.10008. ... Name List

UID List 1.2.840.10008. ...

Verification … 1.1 ILE … 1.2 BOTH

No

4.2.1.4.1.3 SOP Specific Conformance for Verification SOP Class as SCP

The Application Software AE provides standard conformance.

4.2.1.4.2 Activity – Store data to remote AE

This chapter describes the aspect of association acceptance of the activity "Store date to remote AE". The activity stores biometry measurement data, IOL calculation results, reference images and evidence reports created at the modality and requests a storage commitment afterwards.


The description and sequencing of activities is covered by chapter “Activity - Store data to remote AE".




Table 4-31 Presentation Contexts accepted by the HFA 3 AE



Name UID 1.2.840.10008. ...

Name List

UID List 1.2.840.10008. ...



4.2.1.4.2.3 SOP Specific Conformance for Storage SOP Class as SCP


4.2.1.4.2.4 SOP Specific Conformance for Storage Commitment SOP Class

4.2.1.4.2.4.1 Storage Commitment Operations (N-EVENT-REPORT)

The Application Software is capable of receiving an N-EVENT-REPORT notification if it has successfully negotiated a Presentation Context for the Storage Commitment Push

The behavior of Application Software when receiving Event Types within the N-EVENT-REPORT is summarized in the table below.

Table 4-32 Storage Commitment N-EVENT-REPORT Request Failure Reasons



Failure Processing Failure

0110 The SOP Instance is also considered as not being committed. For a configurable amount of re-trials the SOP Instance is subject of a future Storage Commitment service request. It will be included again within next call of these activities.

In addition, the application software writes the SOP Instance UID to the log file with the failure reason.

Failure No such object instance

0112 The SOP Instance is also considered as not being committed. The application will repeat the storage or delete the local instance based on a setting (see section 4.4.2.1 General Parameters). The default setting is to re-archive the exam.


Failure Resource limitation



Failure Referenced SOP Class not supported

0122 The application software writes the SOP Instance UID to the log file with the failure reason.



Failure Class / Instance conflict

0119 The application software writes the SOP Instance UID to the log file with the failure reason.

Failure Duplicate transaction UID




xxxx Log message and retry storage commit for failed sop instance(s).

If the Application Software get a N-EVENT-REPORT with failed instances it depends on the status code what the application does (see table above). In general retry means a retry for 2 times, no retry will set the error counter to maximum. A reset of the error counter is possible in the application settings screen.

4.2.1.4.3 Activity - Retrieve data from remote AE

This chapter describes the aspect of association acceptance of the activity “Retrieve data from remote AE”. The activity retrieves meta data of last exam from a HFA 3 data belonging to a selected patient.


The description and sequencing of activities covered by chapter “Activity – Retrieve data from remote AE”


Table 4-33 Presentation Contexts accepted by the HFA 3 AE



Name UID 1.2.840.10008. ...

Name List

UID List 1.2.840.10008. ...


Raw Data Storage 5.1.4.1.1.66 ILE 1.2 SCP No

ELE 1.2.1 SCP No

4.2.1.4.3.3 SOP Specific Conformance for Storage SOP Class as SCP


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

HFA 3 software does only support IPv4 and does not support any IPv6 features.

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 set at the time of installation by Installation Personnel.

4.4.1.1 Local AE Titles

The IP is not configurable by the Configuration Tool. The IP is administrated by the Operating System. If the Application Software is running on a host with more than one network connection, the user should select the loopback adapter from the list of IP-addresses. The Application Entity Title as well as the port number is configurable. The default port number is 11112.

4.4.1.2 Remote AE Titles

The mapping of external AE Titles to TCP/IP addresses and ports is configurable. The HFA 3 Application Software allows setting up a remote Application Entity for each service. For all Application Entities, the host name or IP, the Port and the Application Entity Title must be known.

4.4.1.3 Auto Connect

The System makes use of the public domain auto connect component from Apple® to discover adjacent network nodes. It can then configure known nodes such as other Zeiss systems and the FORUM server automatically.

4.4.2 Parameters

4.4.2.1 General Parameters

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

Table 4-34 Configuration Parameters Table offered by HFA 3

Parameter Configurable (Yes/No)

Default Value

General Parameters

DIMSE RSP Timeout Yes

(10 – 60 sec.)

20 sec

Network Timeout Yes

(5-20 sec.)

20 sec.

Max. Association Idle Time Yes

(10 – 60 sec.)

30 sec



TCP IP port Yes

(1-65535)

11112

Network log level Yes

(debug, info, warning, error)

Warning

(0008,0080) Institution Name Yes Blank

(0008,1040) Institutional Department Name Yes Blank

(0008,0081) Institution Address Yes Blank

(0008,1010) Station Name Yes blank

(0010,0021) Issuer of Patient ID Yes Serial Number + HFA 3

AE Specific Parameters

Number of simultaneous Associations No 50

AE Title Yes “SCDEVICE”

Verification SCU Parameters

C-ECHO Interval No ?

Modality Worklist SCU Parameters

Maximum Query Responses (Modality Worklist IM, Patient Root Q/R Information Model and Study Root Q/R IM)

Yes

(10-999)

200

Automatic MWL update Yes Enabled

Today’s Patient List Refresh Rate (Modality Worklist Polling Interval)

Yes

(1-60 min)

5 min.

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

Maximum Query Responses (Modality Worklist IM, Patient Root Q/R Information Model and Study Root Q/R IM)

Yes

(10-999)

200

Extended Negotiation – relational query support negotiation

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

Yes

(enabled, disabled)

Enabled

Storage Commitment SCU Parameters

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

- -

Storage Commitment enable/disable Yes Enabled

reaction to “instance not found” Yes ( “delete Exam”, “re-archive”)

“re-archive”

Storage SCU 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).

- -

Storage SCP Parameters


Verification SCP Parameters



5 Media Interchange Media Interchange is not scope of this document since Media Interchange is not supported by HFA 3 Application Software.



6 Support of Character Sets All application entities described in the previous chapters support UTF-8 character set.

Table 6-1 Supported Character Set

Supported Specific Character Set

Character Set Description Defined Term

UTF-8 encoded Unicode ISO_IR 192



7 Security The DICOM capabilities of the HFA 3 Application Software do not support any specific security measures – but requires login credentials from any authorized user.

It is assumed that HFA 3 Application Software 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 HFA 3 Application Software

Firewall or router protections to ensure that the HFA 3 Application Software 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))

Customer provided Virus Scanner has been installed.

Any USB memory drives have been pre-scanned before being inserted.

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)

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.

SRQ The attribute value is same as the value received using a DICOM service such as Study Root Query.



8.1.1.1 Ophthalmic Photography 8Bit Information Object Definition

IE Module Usage

Patient

Patient MANDATORY

Study

General Study MANDATORY

Series

General Series ALWAYS

Ophthalmic Photography Series ALWAYS

Frame Of Reference

Synchronization ALWAYS

Equipment

General Equipment ALWAYS

Image

General Image ALWAYS

Image Pixel ALWAYS

Multi-frame ALWAYS

Ophthalmic Photography Image ALWAYS

Ocular Region Imaged ALWAYS

Ophthalmic Photography Acquisition Parameters ALWAYS

Ophthalmic Photography Parameters ALWAYS

SOP Common ALWAYS

Table 8-1 Ophthalmic Photography IOD - Module "Patient"

Tag Type VR Name Description PoV Source

(0010,0010) 2 PN Patient's Name

Patient's full name. VNAP USER, MWL, SRQ

(0010,0020) 2 LO Patient ID Primary hospital identification number or code for the patient.

ALWAYS USER, MWL, SRQ

(0010,0021) 3 LO Issuer of Patient ID

Identifier of the Assigning Authority (system, organization, agency, or department) that issued the Patient ID. Note: Equivalent to HL7 v2 CX component 4 subcomponent 1.

ANAP MWL, SRQ,

CONFIG

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

Birth date of the patient. ALWAYS MWL, USER, SRQ

(0010,0040) 2 CS Patient's Sex

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

VNAP MWL, USER, SRQ




(0010,0032) 3 TM Patient's Birth Time

Birth time of the Patient. ANAP MWL, SRQ

(0010,1000) 3 LO Other Patient IDs

Other identification numbers or codes used to identify the patient.

ANAP MWL, SRQ

(0010,2160) 3 SH Ethnic Group

Ethnic group or race of the patient. ANAP MWL, SRQ

(0010,4000) 3 LT Patient Comments

User-defined additional information about the patient.

ANAP MWL, SRQ, USER

Table 8-2 Ophthalmic Photography IOD - Module "General Study"


(0020,000D) 1 UI Study Instance UID

Unique identifier for the Study.

Uses value as given by the Modality Worklist service in scheduled case.

The software creates the UID in the unscheduled case. Then it uses “1.2.276.0.75.2.2.30.2.1 as DICOM root prefix for generated UIDs.

ALWAYS AUTO, MWL

(0008,0020) 2 DA Study Date Date the Study started. ALWAYS AUTO

(0008,0030) 2 TM Study Time Time the Study started. ALWAYS AUTO

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

Name of the patient's referring physician VNAP MWL

(0020,0010) 2 SH Study ID

User or equipment generated Study identifier.

In scheduled case: Copied from Requested Procedure ID.

For unscheduled case generated by System as “YYYYMMDDhhmmss”

ALWAYS AUTO, MWL

(0008,0050) 2 SH Accession Number

A RIS generated number that identifies the order for the Study.

For the scheduled case via MWL. For the unscheduled case empty.

VNAP MWL

(0008,1030) 3 LO Study Description

Institution-generated description or classification of the Study (component) performed.

Copied from Requested Procedure Description.

ANAP MWL

(0008,1110) 3 SQ Referenced Study Sequence

A sequence that provides reference to a Study SOP Class/Instance pair. One or more Items are permitted in this Sequence.

ANAP MWL

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

Uniquely identifies the referenced SOP Class. ALWAYS MWL

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

Uniquely identifies the referenced SOP Instance. ALWAYS MWL




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

ANAP MWL

>(0008,0100) 1 SH Code Value See Section 8.1.3 Attribute Mapping ALWAYS MWL

>(0008,0102) 1 SH Coding Scheme Designator

See Section 8.1.3 Attribute Mapping ALWAYS MWL

>(0008,0103) 1C SH Coding Scheme Version

See Section 8.2. Required if the value of Coding Scheme Designator (0008,0102) is not sufficient to identify the Code Value (0008,0100) unambiguously. May be present otherwise.

See Section 8.1.3 Attribute Mapping

ANAP MWL

>(0008,0104) 1 LO Code Meaning See Section 8.1.3 Attribute Mapping ALWAYS MWL

Table 8-3 Ophthalmic Photography IOD - Module “General Series"


(0020,000E) 1 UI Series Instance UID

Unique identifier of the Series.

“1.2.276.0.75.2.2.30.2.10” constant prefix for generated UIDs

ALWAYS AUTO

(0020,0011) 2 IS Series Number

A number that identifies this Series.

Set to “2”. ALWAYS AUTO

(0020,0060) 2C CS Laterality

Laterality of (paired) body part examined. Required if the body part examined is a paired structure and Image Laterality (0020,0062) or Frame Laterality (0020,9072) are not sent.

Enumerated Values: R = right. L = left,“” = both eyes (Esterman Binocular, Binocular Kinetic)

Note: Some IODs support Image Laterality (0020,0062) at the Image level or Frame Laterality(0020,9072) at the Frame level in the Frame Anatomy functional group macro or Measurement Laterality (0024,0113) at the Measurement level, which can provide a more comprehensive mechanism for specifying the laterality of the body part(s) being examined.

Note: 0020,0060 and 0020,0062 are always present.

ALWAYS USER

(0008,0021) 3 DA Series Date Date the Series started. ALWAYS AUTO

(0008,0031) 3 TM Series Time Time the Series started. ALWAYS AUTO

(0018,1030) 3 LO Protocol Name

User-defined description of the conditions under which the Series was performed. Note: This attribute conveys series-specific protocol identification and may or may not be identical to the one presented in the Performed Protocol Code Sequence (0040,0260).

Copied from Requested Procedure Description

ANAP MWL




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

Obtained from Worklist.

ANAP MWL

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

Identifier that identifies the Requested Procedure in the Imaging Service Request. Required if procedure was scheduled. May be present otherwise. Note: The condition is to allow the contents of this macro to be present (e.g., to convey the reason for the procedure, such as whether a mammogram is for screening or diagnostic purposes) even when the procedure was not formally scheduled and a value for this identifier is unknown, rather than making up a dummy value.

ANAP MWL

>(0032,1060) 3 LO Requested Procedure Description

Institution-generated administrative description or classification of Requested Procedure.

ANAP MWL

>(0032,1064) 3 SQ

Requested Procedure Code Sequence

A sequence that conveys the Procedure Type of the requested procedure. Only a single Item is permitted in this sequence.

ANAP MWL

>>(0008,0100) 1 SH Code Value See Section 8.1.3 Attribute Mapping. ALWAYS MWL

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

See Section 8.1.3 Attribute Mapping. ALWAYS MWL

>>(0008,0103) 1C SH Coding Scheme Version


See Section 8.1.3 Attribute Mapping.

ANAP MWL

>>(0008,0104) 1 LO Code Meaning

See Section 8.1.3 Attribute Mapping. ALWAYS MWL

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

Identifier that identifies the Scheduled Procedure Step. Required if procedure was scheduled. Note: The condition is to allow the contents of this macro to be present (e.g., to convey the reason for the procedure, such as whether a mammogram is for screening or diagnostic purposes) even when the procedure step was not formally scheduled and a value for this identifier is unknown, rather than making up a dummy value.

ANAP MWL

>(0040,0007) 3 LO

Scheduled Procedure Step Description

Institution-generated description or classification of the Scheduled Procedure Step to be performed.

ANAP MWL

>(0040,0008) 3 SQ

Scheduled Protocol Code Sequence

Sequence describing the Scheduled Protocol following a specific coding scheme. One or more Items are permitted in this sequence.

ANAP MWL

>>(0008,0100) 1 SH Code Value See Section 8.1.3 Attribute Mapping ALWAYS MWL









ANAP MWL



(0040,0244) 3 DA

Performed Procedure Step Start Date

Date on which the Performed Procedure Step started.

ALWAYS AUTO

(0040,0245) 3 TM

Performed Procedure Step Start Time

Time on which the Performed Procedure Step started.

ALWAYS AUTO

(0040,0254) 3 LO

Performed Procedure Step Description

Institution-generated description or classification of the Procedure Step that was performed.


ANAP MWL

Table 8-4 Ophthalmic Photography IOD - Module “Ophthalmic Photography Series"


(0008,0060) 1 CS Modality Source equipment that produced the Ophthalmic Photography Series. Enumerated Value: OP

ALWAYS AUTO

Table 8-5 Ophthalmic Photography IOD - Module “Synchronization "


(0020,0200) 1 UI

Synchronization Frame of Reference UID

UID of common synchronization environment. See C.7.4.2.1.1.

Value: 1.2.276.0.75.2.2.30.2.5.YYMMDDHHMMSSmmm.MACAddress.random_number

ALWAYS AUTO

(0018,106A) 1 CS Synchronization Trigger

Data acquisition synchronization with external equipment Enumerated Values:

SOURCE - this equipment provides synchronization channel or trigger to other equipment

EXTERNAL - this equipment receives synchronization channel or trigger from other equipment

PASSTHRU - this equipment receives synchronization channel or trigger and forwards it

NO TRIGGER - data acquisition not synchronized by common channel or trigger

Always “NO TRIGGER”

ALWAYS AUTO




(0018,1800) 1 CS

Acquisition Time Synchronized

Acquisition DateTime (0008,002A) synchronized with external time reference. Enumerated Values: Y, N See C.7.4.2.1.4

Always “N”

ALWAYS AUTO

Table 8-6 Ophthalmic Photography IOD - Module “General Equipment"


(0008,0070) 2 LO Manufacturer

Manufacturer of the equipment that produced the composite instances.

Always "Carl Zeiss Meditec”

ALWAYS AUTO

(0008,0080) 3 LO Institution Name Institution where the equipment that produced the composite instances is located.

ANAP CONFIG

(0008,0081) 3 ST Institution Address

Mailing address of the institution where the equipment that produced the composite instances is located.

ANAP CONFIG

(0008,1010) 3 SH Station Name User defined name identifying the machine that produced the composite instances.

ANAP CONFIG

(0008,1040) 3 LO Institutional Department Name

Department in the institution where the equipment that produced the composite instances is located.

ANAP CONFIG

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

Manufacturer’s model name of the equipment that produced the composite instances.

For HFA3: “HFA 3”

ALWAYS AUTO

(0018,1000) 3 LO Device Serial Number

Manufacturer’s serial number of the equipment that produced the composite instances. Note: This identifier corresponds to the device that actually created the images, such as a CR plate reader or a CT console, and may not be sufficient to identify all of the equipment in the imaging chain, such as the generator or gantry or plate.

ALWAYS AUTO

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

Manufacturer’s designation of software version of the equipment that produced the composite instances. See Section C.7.5.1.1.3.

For data generated by HFA3 version 1.0 one of “1.0.1.159”, “1.0.2.9”, “1.0.3.6” or higher 1.0.x versions.

ALWAYS AUTO

(0018,1200) 3 DA Date of Last Calibration

Date when the image acquisition device calibration was last changed in any way. Multiple entries may be used for additional calibrations at other times. See C.7.5.1.1.1 for further explanation.

ALWAYS AUTO

(0018,1201) 3 TM Time of Last Calibration

Time when the image acquisition device calibration was last changed in any way. Multiple entries may be used. See C.7.5.1.1.1 for further explanation.

ALWAYS AUTO

Table 8-7 Ophthalmic Photography IOD - Module “Image Pixel"




(0028,0010) 1 US Rows Number of rows in the image.

Always 200 ALWAYS AUTO

(0028,0011) 1 US Columns Number of columns in the image

Always 200 ALWAYS AUTO

(0028,0100) 1 US Bits Allocated

Number of bits allocated for each pixel sample. Each sample shall have the same number of bits allocated. See PS 3.5 for further explanation.

Always “8”

ALWAYS AUTO

(0028,0101) 1 US Bits Stored

Number of bits stored for each pixel sample. Each sample shall have the same number of bits stored. See PS 3.5 for further explanation.

Always “8”

ALWAYS AUTO

(0028,0102) 1 US High Bit

Most significant bit for pixel sample data. Each sample shall have the same high bit. See PS 3.5 for further explanation.

Always “7”

ALWAYS AUTO

(7FE0,0010) 1C OB|OW Pixel Data

A data stream of the pixel samples that comprise the Image. See C.7.6.3.1.4 for further explanation. Required if Pixel Data Provider URL (0028,7FE0) is not present.

ALWAYS AUTO

Table 8-8 Ophthalmic Photography IOD - Module “Cine"


(0018,1063) 1C DS Frame Time

Nominal time (in msec) per individual frame. See C.7.6.5.1.1 for further explanation. Required if Frame Increment Pointer (0028,0009) points to Frame Time.

ALWAYS AUTO

Table 8-9 Ophthalmic Photography IOD - Module “Multiframe"


(0028,0008) 1 IS Number of Frames

Number of frames in a Multi-frame Image. See C.7.6.6.1.1 for further explanation.

ALWAYS AUTO

(0028,0009) 1 AT Frame Increment Pointer

Contains the Data Element Tag of the attribute that is used as the frame increment in Multi-frame pixel data. See C.7.6.6.1.2 for further explanation.

Always “00181063” which is intended to refer to Frame Time DICOM tag.

ALWAYS AUTO

Table 8-10 Ophthalmic Photography IOD - Module “Ophthalmic Photography Image"


(0008,0008) 1 CS Image Type

Image identification characteristics. See C.8.17.2.1.4 for specialization.

Value 1: ORIGINAL

Value 2: PRIMARY

Value 3: <Not Present>

Value 4: <Not Present>

ALWAYS AUTO




(0020,0013) 1 IS Instance Number

A number that identifies this image.

Value: “1” ALWAYS AUTO

(0028,0002) 1 US Samples per Pixel

Number of samples (planes) in this image. Enumerated values: 1 or 3. See C.8.17.2.1.2 for further explanation.

Value: “1”

ALWAYS AUTO

(0028,0004) 1 CS Photometric Interpretation

Specifies the intended interpretation of the pixel data. See section C.8.17.2.1.3

Always MONOCHROME2

ALWAYS AUTO

(0028,0103) 1 US Pixel Representation

Data representation of the pixel samples. Each sample shall have the same pixel representation.

Enumerated Values:

0000H = unsigned integer.

0001H = 2's complement

Enumerated value: 0

ALWAYS AUTO

(0028,0006) 1C US Planar Configuration

Indicates whether the pixel data are sent color-by-plane or color-by-pixel. Required if Samples per Pixel (0028,0002) has a value greater than 1. Enumerated value shall be 0 (color-by-pixel).

ALWAYS AUTO

(0008,0033) 1 TM Content Time The time the image pixel data creation started. ALWAYS AUTO

(0008,0023) 1 DA Content Date The date the image pixel data creation started. ALWAYS AUTO

(0008,002A) 1C DT Acquisition DateTime

The date and time that the acquisition of data started. Note: The synchronization of this time with an external clock is specified in the synchronization Module in Acquisition Time Synchronized (0018,1800). Required if Image Type (0008,0008) Value 1 is ORIGINAL. May be present otherwise.

ALWAYS AUTO

(0028,2110) 1 CS Lossy Image Compression

Specifies whether an Image has undergone lossy compression. Enumerated Values: 00 = Image has NOT been subjected to lossy compression. 01 = Image has been subjected to lossy compression. See C.7.6.1.1.5

“01” if image is compressed

Value: 01

ALWAYS AUTO

(0028,2112) 1C DS Lossy Image Compression Ratio

Describes the approximate lossy compression ratio(s) that have been applied to this image. See C.7.6.1.1.5 for further explanation. May be multivalued if successive lossy compression steps have been applied. Notes: 1. For example, a compression ratio of 30:1 would be described in this Attribute with a single value of 30. 2. For historical reasons, the lossy compression ratio should also be described in Derivation Description (0008,2111) Required if Lossy Image Compression (0028,2110) has a value of "01".

ALWAYS AUTO




(0028,2114) 1C CS Lossy Image Compression Method

A label for the lossy compression method(s) that have been applied to this image. See C.7.6.1.1.5 for further explanation. May be multivalued if successive lossy compression steps have been applied; the value order shall correspond to the values of Lossy Image Compression Ratio (0028,2112). Required if Lossy Image Compression (0028,2110) has a value of "01". Note: For historical reasons, the lossy compression method should also be described in Derivation Description (0008,2111).

Always “ISO_10918_1”

ALWAYS AUTO

(2050,0020) 1C CS Presentation LUT Shape

Specifies an identity transformation for the Presentation LUT, such that the output of all grayscale transformations defined in the IOD containing this Module are defined to be P-Values. Enumerated Values:

IDENTITY - output is in P-Values.

Required if Photometric Interpretation (0028,0004) is MONOCHROME2

ALWAYS AUTO

(0028,0301) 1 CS Burned In Annotation

Indicates whether or not image contains sufficient burned in annotation to identify the patient and date the image was acquired. Enumerated Value: YES NO

Value: NO

ALWAYS AUTO

Table 8-11 Ophthalmic Photography IOD - Module “Ocular Region Imaged "


(0020,0062) 1 CS Image Laterality

Laterality of object imaged (as described in Anatomic Region Sequence (0008,2218)) examined.

Enumerated Values:

R = right eye

L = left eye

B = both left and right eye

Shall be consistent with any laterality information contained in Primary Anatomic Structure Modifier Sequence (0008,2230), if present.

Note: Laterality (0020,0060) is a Series level Attribute and must be the same for all Images in the Series. Since most Ophthalmic Photographic Image studies contain images of both eyes, the series level attribute will rarely be present.


ALWAYS AUTO

(0008,2218) 1 SQ Anatomic Region Sequence

Sequence that identifies the anatomic region of interest in this Instance (i.e. external anatomy, surface anatomy, or general region of the body). Only a single Item shall be included in this sequence.

ALWAYS AUTO

>(0008,0100) 1 SH Code Value See Section 8.1.

Always “T-AA000” ALWAYS AUTO





See Section 8.2.

Always “SRT” ALWAYS AUTO



ALWAYS AUTO

>(0008,0104) 1 LO Code Meaning

See Section 8.3.

Always “Eye” ALWAYS AUTO

Table 8-12 Ophthalmic Photography IOD - Module “Ophthalmic Photography Acquisition Parameters "


(0022,0005) 2 CS Patient Eye Movement Commanded

Enumerated Values: YES NO

Value: NO ALWAYS AUTO

(0022,001B) 2 SQ Refractive State Sequence

The refractive state of the imaged eye at the time of acquisition. Zero or one Item shall be included in this sequence. Zero length means the refractive state was not measured.

EMPTY AUTO

(0022,000A) 2 FL Emmetropic Magnification

Emmetropic magnification value (dimensionless). Zero length means the emmetropic magnification was not measured.

EMPTY AUTO

(0022,000B) 2 FL intraocular Pressure

Value of intraocular pressure in mmHg. Zero length means the pressure was not measured

EMPTY AUTO

(0022,000D) 2 CS Pupil Dilated

Whether or not the patient’s pupils were pharmacologically dilated for this acquisition. Enumerated Values: YES NO

If this tag is empty, no information is available.

EMPTY AUTO

Table 8-13 Ophthalmic Photography IOD - Module “Ophthalmic Photographic Parameters "


(0022,0015) 1 SQ Acquisition Device Type Code Sequence

Describes the type of acquisition device. A single item shall be included in this sequence.

ALWAYS AUTO

>(0008,0100) 1 SH Code Value See Section 8.1.

Always “R-1021B” ALWAYS AUTO


See Section 8.2.

Always “SRT” ALWAYS AUTO

>(0008,0104) 1 LO Code Meaning See Section 8.3.

Always “External Camera” ALWAYS AUTO

(0022,0016) 2 SQ Illumination Type Code Sequence

Coded value for illumination. Zero or one item shall be included in this sequence.

EMPTY AUTO

(0022,0017) 2 SQ Light Path Filter Type Stack Code Sequence

Filters used in the light source path. Zero or more items may be included in this sequence.

EMPTY AUTO




(0022,0018) 2 SQ Image Path Filter Type Stack Code Sequence

Describes stack of filters used in image path. Zero or more items shall be included in this sequence.

EMPTY AUTO

(0022,0019) 2 SQ Lenses Code Sequence

Lenses that were used during the image acquisition. Zero or more items shall be included in this sequence.

EMPTY AUTO

(0018,7004) 2 CS Detector Type

Type of detector used for creating this image. Defined terms:

CCD = Charge Coupled Devices

CMOS = Complementary Metal Oxide Semiconductor

EMPTY AUTO

Table 8-14 Ophthalmic Photography IOD - Module “SOP Common "


(0008,0016) 1 UI SOP Class UID

Uniquely identifies the SOP Class. See C.12.1.1.1 for further explanation. See also PS 3.4.

“1.2.840.10008.5.1.4.1.1.77.1.5.1”

ALWAYS AUTO

(0008,0018) 1 UI SOP Instance UID

Uniquely identifies the SOP Instance. See C.12.1.1.1 for further explanation. See also PS 3.4.

“1.2.276.0.75.2.2.30.2.” constant prefix for generated UIDs

ALWAYS AUTO

(0008,0012) 3 DA Instance Creation Date

Date the SOP Instance was created. ALWAYS AUTO

(0008,0013) 3 TM Instance Creation Time

Time the SOP Instance was created. ALWAYS AUTO



8.1.1.2 Raw IOD Information Entities

IE Module Usage

Patient

Patient ALWAYS

Study

General Study ALWAYS

Series


Frame Of Reference

Equipment


Raw Data

Acquisition Context ALWAYS– Zero items

Raw Data ALWAYS

SOP Common ALWAYS

Table 8-15 Raw IOD - Module "Patient"



Patient's full name. VNAP

USER,

MWL,

SRQ


ALWAYS

USER,

MWL,

SRQ



ANAP

MWL,

SRQ,

CONFIG


Birth date of the patient. ALWAYS MWL, USER, SRQ

(0010,0040) 2 CS Patient's Sex

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

VNAP MWL, USER, SRQ

(0010,0032) 3 TM Patient's Birth Time

Birth time of the Patient. ANAP MWL, SRQ



ANAP MWL, SRQ

(0010,2160) 3 SH Ethnic Group

Ethnic group or race of the patient. ANAP MWL,

SRQ





User-defined additional information about the patient.

ANAP MWL, SRQ, USER

Table 8-16 Raw Data IOD - Module "General Study"




Uses value as given by the Modality Worklist service in scheduled case.


ALWAYS AUTO, MWL

(0008,0020) 2 DA Study Date Date the Study started. ALWAYS AUTO

(0008,0030) 2 TM Study Time Time the Study started. ALWAYS AUTO


Name of the patient's referring physician VNAP MWL

(0020,0010) 2 SH Study ID



For the unscheduled case generated by System as “YYYYMMDDhhmmss”

ALWAYS AUTO, MWL




ANAP MWL



In scheduled case copied from Requested Procedure Description.

ANAP MWL



ANAP MWL


Uniquely identifies the referenced SOP Class. ALWAYS MWL


Uniquely identifies the referenced SOP Instance. ALWAYS MWL



ANAP MWL

>(0008,0100) 1 SH Code Value See Section 8.1.3 Attribute Mapping ALWAYS MWL









ANAP MWL

>(0008,0104) 1 LO Code Meaning See Section 8.1.3 Attribute Mapping ALWAYS MWL

Table 8-17 Raw Data IOD - Module "General Series”


((0008,0060) 1 CS Modality

Type of equipment that originally acquired the data used to create the images in this Series. See C.7.3.1.1.1 for Defined Terms.

Set to “OPV”

ALWAYS AUTO


Unique identifier of the Series.


ALWAYS AUTO

(0020,0011) 2 IS Series Number

A number that identifies this Series.

Set to “1” ALWAYS AUTO



Enumerated Values: R = right L = left, Use "" if Both Eyes (Esterman Binocular, Binocular Kinetic).



ALWAYS AUTO

(0008,0021) 3 DA Series Date Date the Series started. ALWAYS AUTO

(0008,0031) 3 TM Series Time Time the Series started. ALWAYS AUTO




ANAP MWL

(0040,0275) 3 SQ

Request Attributes Sequence


ANAP MWL






ANAP MWL



ANAP MWL

>(0032,1064) 3 SQ



ANAP MWL

>>(0008,0100)

1 SH Code Value See Section 8.1. ALWAYS MWL

>>(0008,0102)

1 SH Coding Scheme Designator

See Section 8.2. ALWAYS MWL

>>(0008,0103)

1C SH Coding Scheme Version


ANAP MWL

>>(0008,0104)

1 LO Code Meaning

See Section 8.3. ALWAYS MWL



ANAP MWL

>(0040,0007) 3 LO



ANAP MWL

>(0040,0008) 3 SQ



ANAP MWL

>>(0008,0100)

1 SH Code Value See Section 8.1.3 Attribute Mapping ALWAYS MWL

>>(0008,0102)






>>(0008,0103)




ANAP MWL

>>(0008,0104)

1 LO Code Meaning


(0040,0244) 3 DA


Date on which the Performed Procedure Step started.

ALWAYS AUTO

(0040,0245) 3 TM


Time on which the Performed Procedure Step started.

ALWAYS AUTO

(0040,0254) 3 LO



ALWAYS EMPTY

Table 8-18 Raw Data IOD – Module “General Equipment”




Always "Carl Zeiss Meditec”

ALWAYS AUTO


ANAP CONFIG



ANAP CONFIG

(0008,1010) 3 SH Station Name User defined name identifying the machine that produced the composite instances.

ANAP CONFIG



ANAP CONFIG



For HFA3: "HFA 3"

For HFA IIi: "HFA II-i"

ALWAYS AUTO


Manufacturer’s serial number of the equipment that produced the composite instances. Note: This identifier corresponds to the device that actually created the images, such as a CR plate reader or a CT console, and may not be sufficient to identify all of the equipment in the imaging chain, such as the generator or gantry or plate.

ALWAYS AUTO





Manufacturer’s designation of software version of the equipment that produced the composite instances. See Section C.7.5.1.1.3.

For data generated by HFA3 version 1.0 one of “1.0.1.159”, “1.0.2.9”, “1.0.3.6” or higher 1.0.x versions.

ALWAYS AUTO



This value is used by HFA 3, but not by HFA IIi.

ALWAYS AUTO



This value is used by HFA 3, but not by HFA IIi.

ALWAYS AUTO

Table 8-19 Raw Data IOD – Module “Acquisition Context”


(0040,0555) 2 SQ Acquisition Context Sequence

A sequence of Items that describes the conditions present during the acquisition of the data of the SOP Instance. Zero or more items shall be included in this sequence.

ALWAYS EMPTY

Table 8-20 Raw Data IOD – Module “Raw Data”


(0020,0013) 2 IS Instance Number

A number that identifies this raw data. The value shall be unique within a series.

Always "1" for CZM Perimetry.

ALWAYS AUTO

(0008,0023) 1 DA Content Date The date the raw data creation was started. ALWAYS AUTO

(0008,0033) 1 TM Content Time The time the raw data creation was started. ALWAYS AUTO

(0008,002A) 3 DT Acquisition Datetime

The date and time that the acquisition of data started. Note: The synchronization of this time with an external clock is specified in the synchronization Module in Acquisition Time synchronized (0018,1800).

ALWAYS AUTO

(0020,0062) 3 CS Image Laterality Laterality of (possibly paired) body part examined. Enumerated Values: R = right L = left U = unpaired B = both left and right

ALWAYS AUTO




(0008,9123) 1 UI Creator-Version UID

Unique identification of the equipment and version of the software that has created the Raw Data information. The UID allows one to avoid attempting to interpret raw data with an unknown format.

Shall be generated on export from the Perimetry root UID and the software version. The Perimetry root UID is 1.2.276.0.75.2.2.30.2. For the HFA IIi and below it will be the root UID and the software version (e.g. 1.2.276.0.75.2.2.30.2.5.1.1).

For Santa Cruz it will be the root UID.6.100.<model number>.<software version> (e.g. 1.2.276.0.75.2.2.30.2.6.100.800.1.0.0.386).

For data generated by HFA3 version 1.0 one of: - 1.2.276.0.75.2.2.30.2.6.100.800.1.0.1.159

- 1.2.276.0.75.2.2.30.2.6.100.800.1.0.2.9

- 1.2.276.0.75.2.2.30.2.6.100.800.1.0.3.6

Or 1.2.276.0.75.2.2.30.2.6.100.800.1.0.X for higher 1.0.x versions.

ALWAYS AUTO

(0008,114A) 3 SQ Referenced Instance Sequence

Other Instances significantly related to this Instance. One or more Items are permitted in this Sequence.

Reference to the Ophthalmic Photography 8 Bit IOD instance

ANAP AUTO


Uniquely identifies the referenced SOP Class.

The OP 8 bit SOP class:

1.2.840.10008.5.1.4.1.1.77.1.5.1

ANAP AUTO


Uniquely identifies the referenced SOP Instance.

ANAP AUTO

>(0040,A170) 1 SQ Purpose of Reference Code Sequence

Describes the purpose for which the reference is made. Only a single Item shall be included in this sequence. See C.7.6.16.2.5.1.

ALWAYS AUTO

>>(0008,0100) 1 SH Code Value See Section 8.1.

Value: “122400” ALWAYS AUTO


See Section 8.2.

Value: “DCM” ALWAYS AUTO

>>(0008,0104) 1 LO Code Meaning See Section 8.3.

Value: “Simultaneously Acquired” ALWAYS AUTO



Table 8-21 Raw Data IOD - Module "Sop Common”


(0008,0016) 1 UI SOP Class UID

Uniquely identifies the SOP Class. See C.12.1.1.1 for further explanation. See also PS 3.4.

Always “1.2.840.10008.5.1.4.1.1.66”

ALWAYS AUTO

(0008,0018) 1 UI SOP Instance UID

Uniquely identifies the SOP Instance. See C.12.1.1.1 for further explanation. See also PS 3.4.


ALWAYS AUTO

(0008,0005) 1C CS Specific Character Set

Character Set that expands or replaces the Basic Graphic Set. Required if an expanded or replacement character set is used. See C.12.1.1.2 for Defined Terms.

Always “ISO_IR 192” for UTF-8 encoded Unicode.

ALWAYS AUTO


Date the SOP Instance was created. ALWAYS AUTO


Time the SOP Instance was created. ALWAYS AUTO

(0018,A001) 3 SQ Contributing Equipment Sequence

Sequence of Items containing descriptive attributes of related equipment which has contributed to the acquisition, creation or modification of the composite instance. One or more Items are permitted in this Sequence. See C.12.1.1.5 for further explanation.

VNAP AUTO

>(0040,A170)

1 SQ Purpose of Reference Code Sequence

Describes the purpose for which the related equipment is being reference. Only a single Item shall be included in this sequence. See C.12.1.1.5 for further explanation.

ALWAYS AUTO

>>(0008,0100)

1 SH Code Value See Section 8.1. ALWAYS AUTO

>>(0008,0102)


See Section 8.2. ALWAYS AUTO

>>(0008,0103)



ALWAYS AUTO

>>(0008,0104)

1 LO Code Meaning See Section 8.3. ALWAYS AUTO

>>(0008,010F)

3 CS Context Identifier See Section 8.6. ALWAYS AUTO

>>(0008,0117)

3 UI Context UID See Section 8.6. ALWAYS AUTO

>(0008,0070)

1 LO Manufacturer Manufacturer of the equipment that contributed to the composite instance.

ALWAYS AUTO




>(0008,0080)

3 LO Institution Name Institution where the equipment that contributed to the composite instance is located.

ALWAYS AUTO

>(0008,1010)

3 SH Station Name User defined name identifying the machine that contributed to the composite instance.

ALWAYS AUTO



8.1.1.3 Ophthalmic Visual Field Static Perimetry Measurements Information Object Definition

Table 8-22 Ophthalmic Visual Field Static Perimetry Measurements Information Object Definition

IE Module Usage

Patient

Patient ALWAYS

Study

General Study ALWAYS

Series


Visual Field Static Perimetry Measurements Series ALWAYS

Equipment


Enhanced General Equipment ALWAYS

Measurements

Visual Field Static Perimetry Test Parameters ALWAYS

Visual Field Static Perimetry Test Reliability

ALWAYS

Visual Field Static Perimetry Test Measurements ALWAYS

Visual Field Static Perimetry Test Results ALWAYS

Sop Common ALWAYS

Czm Ophthalmic Visual Field Static Perimetry Measurements Extension

ALWAYS

Table 8-23 Ophthalmic Visual Field Static Perimetry Measurements IOD - Module "Patient"



Patient's full name. VNAP USER, IMPORT


ALWAYS USER, IMPORT



ANAP IMPORT, CONFIG


Birth date of the patient. ALWAYS USER, IMPORT

(0010,0040) 2 CS Patient's Sex Sex of the named patient. Enumerated Values: M = male F = female O = other

VNAP USER, IMPORT



ANAP IMPORT

(0010,2160) 3 SH Ethnic Ethnic group or race of the patient. ANAP IMPORT




Group


User-defined additional information about the patient. ANAP IMPORT

Table 8-24 Ophthalmic Visual Field Static Perimetry Measurements IOD - Module "General Study"





ALWAYS AUTO, IMPORT

(0008,0020) 2 DA Study Date Date the Study started. ALWAYS AUTO, IMPORT

(0008,0030) 2 TM Study Time Time the Study started. ALWAYS AUTO, IMPORT


Name of the patient's referring physician ANAP IMPORT

(0020,0010) 2 SH Study ID



For unscheduled case generated by System as “YYYYMMDDhhmmss”

ALWAYS AUTO, IMPORT




ANAP IMPORT



ANAP IMPORT



ANAP IMPORT


Uniquely identifies the referenced SOP Class. ALWAYS IMPORT


Uniquely identifies the referenced SOP Instance. ALWAYS IMPORT



ANAP IMPORT

>(0008,0100) 1 SH Code Value See NEMA PS3.3 Section 8.1. ALWAYS IMPORT


See NEMA PS3.3 Section 8.2. ALWAYS IMPORT

>(0008,0103) 1C SH Coding Scheme

See NEMA PS3.3 Section 8.2. Required if the value of Coding Scheme Designator (0008,0102) is not sufficient

VNAP IMPORT




Version to identify the Code Value (0008,0100) unambiguously. May be present otherwise.

>(0008,0104) 1 LO Code Meaning See NEMA PS3.3 Section 8.3. ALWAYS IMPORT

Table 8-25 Ophthalmic Visual Field Static Perimetry Measurements IOD - Module "General Series"



Unique identifier of the Series. Set to

1.2.276.0.75.2.2.30.2.12.yyyMMddHHmmss.<device serial number>

ALWAYS AUTO

(0020,0011) 2 IS Series Number A number that identifies this Series.

ALWAYS

AUTO, IMPORT



Enumerated Values: R = right L = left, Use "" if Both Eyes (Esterman Binocular, Binocular Kinetic).



ALWAYS AUTO, IMPORT

(0008,0021) 3 DA Series Date Date the Series started. ALWAYS AUTO, IMPORT

(0008,0031) 3 TM Series Time Time the Series started. ALWAYS AUTO, IMPORT




ANAP IMPORT

(0008,103E) 3 LO Series Description

Description of the Series

Set to “OPV” ALWAYS AUTO

Table 8-26 Ophthalmic Visual Field Static Perimetry Measurements IOD - Module "Visual Field Static Perimetry Measurements Series"


(0008,0060) 1 CS Modality

Type of equipment that originally acquired the data used to create the measurements in this Series. Enumerated Values: OPV

Set to: “OPV”

ALWAYS AUTO




(0040,0275) 3 SQ Request Attributes Sequence


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

ANAP IMPORT



ANAP IMPORT



ANAP IMPORT

>(0032,1064) 3 SQ



ANAP IMPORT

>>(0008,0100) 1 SH Code Value See NEMA PS3.3 Section 8.1. ALWAYS IMPORT




See NEMA PS3.3 Section 8.2. Required if the value of Coding Scheme Designator (0008,0102) is not sufficient to identify the Code Value (0008,0100) unambiguously. May be present otherwise.

ANAP IMPORT





ANAP IMPORT

>(0040,0007) 3 LO



ANAP IMPORT

>(0040,0008) 3 SQ



ANAP IMPORT

>>(0008,0100) 1 SH Code Value See NEMA PS3.3 Section 8.1. ALWAYS IMPORT








ANAP IMPORT



(0040,0244) 3 DA


Date on which the Performed Procedure Step started. ALWAYS AUTO, IMPORT

(0040,0245) 3 TM


Time on which the Performed Procedure Step started. ALWAYS AUTO, IMPORT

(0040,0254) 3 LO



ANAP IMPORT

Table 8-27 Ophthalmic Visual Field Static Perimetry Measurements IOD - Module "General Equipment"



ALWAYS CONFIG, IMPORT



ANAP CONFIG,

IMPORT

(0008,1010) 3 SH Station Name

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

Station Name of the machine used for creating the OPV.




ANAP CONFIG,

IMPORT



ANAP IMPORT



ANAP IMPORT

Table 8-28 Ophthalmic Visual Field Static Perimetry Measurements IOD - Module "Enhanced General Equipment"




Set to: “Carl Zeiss Meditec”

ALWAYS AUTO, IMPORT






Set to: “HFA 3”


Manufacturer’s serial number of the equipment that produced the composite instances.

Device serial number.



Manufacturer’s designation of software version of the equipment that produced the composite instances. See NEMA PS3.3 Section C.7.5.1.1.3.

Software version creating this IOD.


Table 8-29 Ophthalmic Visual Field Static Perimetry Measurements IOD - 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.

ALWAYS AUTO, IMPORT

(0024,0011) 1 FL Visual Field Vertical Extent

The maximum vertical angular subtend (diameter or height) of the tested visual field, in degrees.

ALWAYS AUTO, IMPORT

(0024,0012) 1 CS Visual Field Shape

The shape of the visual field tested. Defined Terms: RECTANGLE CIRCLE ELLIPSE

Always set to “CIRCLE”

ALWAYS AUTO, IMPORT

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

Mode used to determine how the starting luminance values and expected thresholds are chosen. Only a single Item shall be included in this sequence. Required if Content Item Modifier Sequence (0040,0441) within Performed Protocol Code Sequence (0040,0260) contains an item with the value (R-42453, SRT, "Screening"). May be present otherwise.

ANAP AUTO, IMPORT

>(0008,0100) 1 SH Code Value

Threshold Related (111839),

Age Corrected (111838),

Single Luminance (111840)

ALWAYS AUTO, IMPORT


Set to “DCM” ALWAYS AUTO, IMPORT

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

ALWAYS AUTO, IMPORT

(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 raw data source.

ALWAYS AUTO, IMPORT

(0024,0020) 1 FL Background Luminance

Background luminance of the device, in candelas per square meter (cd/m²). Note: This value is easily convertible to apostilb, which is used only in Perimetry and is not a standardized unit.

Calculated from binary data in the raw data source

ALWAYS AUTO, IMPORT

(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 raw data source

UseBlueYellow in applicable exams.

ALWAYS AUTO, IMPORT

>(0008,0100) 1 SH Code Value Possible values are: ALWAYS AUTO,



“G-A11D” (Yellow)

“G-A12B” (White)

“G-A11A” (Red)

“G-A12F” (Blue)

“G-A11E” (Green)

IMPORT


Set to “SRT” ALWAYS AUTO, IMPORT


Required if the value of Coding Scheme Designator (0008,0102) is not sufficient to identify the Code Value (0008,0100) unambiguously. May be present otherwise.

ANAP AUTO, IMPORT

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

“YELLOW”, “WHITE” ALWAYS

AUTO, IMPORT

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

Extracted from binary data in the raw data source.

UseBlueYellow in applicable exams.

ALWAYS AUTO, IMPORT

>(0008,0100) 1 SH Code Value

Possible values are:

“G-A11D” (Yellow)

“G-A12B” (White)

ALWAYS AUTO, IMPORT


Set to “SRT” ALWAYS AUTO, IMPORT



ANAP AUTO, IMPORT

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

“WHITE”, ”YELLOW” ALWAYS

AUTO, IMPORT

(0024,0025) 1 FL Stimulus Area

Area of light stimulus presented to the patient, in degrees squared.

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

ALWAYS AUTO, IMPORT

(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 Esterman tests, 200 for all others.

ALWAYS AUTO, IMPORT

Table 8-30 Ophthalmic Visual Field Static Perimetry Measurements IOD - Module "Visual Field Static Perimetry Test Reliability"


(0024,0032) 1 SQ Fixation Sequence

The patient’s gaze stability information during the visual field test. Only a single Item shall be included in this sequence.

Fixation Monitor in applicable exam types.

ALWAYS AUTO, IMPORT

>(0024,0033) 1 SQ Fixation Monitoring Code

The device strategy used to monitor the patient's fixation. One or more Items shall be included in this sequence.

ALWAYS AUTO, IMPORT



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

>>(0008,0100) 1 SH Code Value

Set to:

111844 for Blind Spot Monitoring

111843 for Automated Optical

R-40775 for NONE

ALWAYS AUTO, IMPORT


“DCM”, “SRT” for NONE ALWAYS AUTO, IMPORT


Required if the value of Coding Scheme Designator (0008,0102) is not sufficient to identify the Code Value (0008,0100) unambiguously. May be present otherwise.

ANAP AUTO,

IMPORT

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

ALWAYS AUTO, IMPORT

>(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") or (111845, DCM, "Macular Fixation Testing"). May be present otherwise.


ANAP AUTO, IMPORT

>(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") or (111845, DCM, "Macular Fixation Testing"). May be present otherwise.


ANAP AUTO, IMPORT

>(0024,0039) 1 CS

Excessive Fixation Losses Data Flag

Whether the device was able to determine excessive fixation losses. Enumerated Values: YES NO

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


ALWAYS AUTO, IMPORT

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

The number of fixation losses is outside of implementation-specific limits. Enumerated Values: YES NO Required if Excessive Fixation Losses Data Flag (0024,0039) is YES.

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 AUTO, IMPORT

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

The reliability of the patient’s responses to the visual field test. Only a single Item shall be included in this sequence.

ALWAYS AUTO, IMPORT

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

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


ALWAYS AUTO, IMPORT

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

Total number of times the patient’s visual attention was tested using stimuli brighter than previously seen

ANAP AUTO, IMPORT



Quantity luminance (negative catch trials). Required if Catch Trials Data Flag (0024,0055) is YES.


>(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 AUTO, IMPORT

>(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 AUTO, IMPORT

>(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 AUTO, IMPORT

>(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 AUTO, IMPORT

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


ANAP AUTO, IMPORT

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

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


ANAP AUTO, IMPORT

>(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 AUTO, IMPORT

>(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 AUTO, IMPORT

>(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 AUTO, IMPORT

>(0024,0061) 1 CS Excessive False

Whether the device was able to determine excessive ALWAYS AUTO,



Positives Data Flag

false positives. Enumerated Values: YES NO

Always set to: YES.

IMPORT

>(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 AUTO, IMPORT

(0024,0069) 3 LO Patient Reliability Indicator

Vendor implementation specific text to provide an analysis and/or summary of patient reliability indicator/indices.

“*** 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 AUTO, IMPORT

Table 8-31 Ophthalmic Visual Field Static Perimetry Measurements IOD - Module "Visual Field Static Perimetry Test Measurements"


(0024,0113) 1 CS Measurement Laterality

Laterality of body part (eye) examined. See NEMA PS3.3 Section C.8.26.4.1.1 for further explanation.

Enumerated Values: R = right L = left B = both left and right together

Note: This Attribute is mandatory, in order to ensure that measurements may be positioned correctly relative to one another for display.

Note: Laterality (0020,0060) is a Series level Attribute and must be the same for all Measurements in the Series, hence it must be absent if multiple instances from different eyes are encoded.

ALWAYS AUTO, IMPORT

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

Whether the device was able to determine presented visual stimuli. Enumerated Values: YES NO

Always set to “NO”

ALWAYS AUTO, IMPORT

(0024,0088) 1 FL Visual Field Test Duration

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


ALWAYS AUTO, IMPORT

(0024,0086) 1 CS Foveal Sensitivity Measured

Whether foveal sensitivity was measured. Enumerated Values: YES NO


ALWAYS AUTO, IMPORT

(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 NEMA PS3.3 Section C.8.26.4.1.2 for further explanation. Required if the value for Foveal Sensitivity Measured (0024,0086) is YES.


ANAP AUTO, IMPORT



(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 AUTO, IMPORT

(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 AUTO, IMPORT

(0024,0120) 1 CS Screening Baseline Measured

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


ALWAYS AUTO, IMPORT

(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 AUTO, IMPORT

>(0024,0124) 1 CS Screening Baseline Type

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


ALWAYS AUTO, IMPORT

>(0024,0126) 1 FL Screening Baseline Value

Visual Field screening baseline value, in dB.

Extracted from binary data in the raw data source ALWAYS

AUTO, IMPORT

(0024,0106) 1 CS Blind Spot Localized

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


ALWAYS AUTO, IMPORT

(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. See NEMA PS3.3 Section C.8.26.4.1.3 for further explanation.


ANAP AUTO, IMPORT

(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. See NEMA PS3.3 Section C.8.26.4.1.3 for further explanation.


ANAP AUTO, IMPORT

(0024,0105) 1 FL Minimum Sensitivity Value

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


ALWAYS AUTO, IMPORT

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


ALWAYS AUTO, IMPORT

(0024,0058) 1C SQ Test Point Normative data base used for this test sequence. ANAP AUTO,



Normals Sequence

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

IMPORT

>(0024,0306) 1 LO Data Set Name The name assigned to the data set.

Set to: “HFA test point normative data” ALWAYS

AUTO, IMPORT

>(0024,0307) 1 LO Data Set Version

The software version identifier assigned to the data set.

Set to: “1.0”

ALWAYS AUTO, IMPORT

>(0024,0308) 1 LO Data Set Source

Source of the data set e.g. the name of the manufacturer, researcher, university, etc.

Set to: “CZMI”

ALWAYS AUTO, IMPORT

(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, IMPORT

>(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, IMPORT

>>(0008,0100) 1 SH Code Value Set to: "PERIMETRY" ALWAYS AUTO, IMPORT


Set to: "99CZM_PERIMETRY" ALWAYS AUTO, IMPORT

>>(0008,0104) 1 LO Code Meaning Set to: "CZM Perimetry Algorithms" ALWAYS AUTO, IMPORT

>(0066,0036) 1 LO Algorithm Name

The name assigned by a manufacturer to a specific software algorithm.

Set to: “Total Deviation”

ALWAYS AUTO, IMPORT

>(0066,0031) 1 LO Algorithm Version

The software version identifier assigned by a manufacturer to a specific software algorithm.

Set to: “1.0”

ALWAYS AUTO, IMPORT

(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, IMPORT

>(0066,002F) 1 SQ Algorithm Family Code Sequence


ALWAYS AUTO, IMPORT

>>(0008,0100) 1 SH Code Value Set to: "PERIMETRY" ALWAYS AUTO, IMPORT



>>(0008,0104) 1 LO Code Meaning Set to: "CZM Perimetry Algorithms" ALWAYS AUTO, IMPORT

>(0066,0036) 1 LO Algorithm Name


Set to: “Pattern Deviation”

ALWAYS AUTO, IMPORT



>(0066,0031) 1 LO Algorithm Version


Set to: “1.0”

ALWAYS AUTO, IMPORT

(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 raw data source

ALWAYS AUTO, IMPORT

>(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 raw data source.

ALWAYS AUTO, IMPORT

>(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 raw data source.

ALWAYS AUTO, IMPORT

>(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 AUTO, IMPORT

>(0024,0094) 1C FL Sensitivity Value

If Stimulus Results (0024,0093) is SEEN then this value is the sensitivity, in dB. Required if Content Item Modifier Sequence (0040,0441) within Performed Protocol Code Sequence (0040,0260) contains an item with the value (R-408C3, SRT, "Diagnostic"). May be present otherwise. Note: If this is not present, refer to the attribute Minimum Sensitivity Value (0024,0105).

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

ANAP AUTO, IMPORT

>(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 AUTO, IMPORT

>(0024,0096) 3 FL Retest Sensitivity Value

If the Retest Stimulus Seen (0024,0095) is YES, then this value is the sensitivity, in dB. Note: If this is not present, refer to the attribute Minimum Sensitivity Value (0024,0105).

extracted from binary data in the raw data source.

ANAP AUTO, IMPORT

>(0024,0098) 3 FL Quantified Defect

Difference between the expected and the determined sensitivity, each in dB. Note: This field is only useful when the sensitivity is quantified. Some examples include Test Strategy Code Sequence (0024,0015) with items providing values such as Quantity-Defects, 2LT-Dynamic, 2LT-

ANAP AUTO, IMPORT



Normal.

Only for screening tests with strategy quantified defects.


>(0024,0097) 1C SQ Visual Field Test Point Normals Sequence

Information about normal values for each visual field test point. One or more items shall be included in this sequence. Required if Test Point Normals Data Flag (0024,0057) is YES.

ANAP AUTO, IMPORT

>>(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 AUTO, IMPORT

>>(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 AUTO, IMPORT

>>(0024,0102) 1 CS

Generalized Defect Corrected Sensitivity Deviation Flag

Whether generalized defect corrected data are available for this point. Enumerated Values: YES NO

Set to: “YES”

ALWAYS AUTO, IMPORT

>>(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 AUTO, IMPORT

>>(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 AUTO, IMPORT

Table 8-32 Ophthalmic Visual Field Static Perimetry Measurements IOD - 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. Required if Content Item Modifier Sequence (0040,0441) within the Performed Protocol Code Sequence (0040,0260) contains an item with the value (R-408C3, SRT, "Diagnostic"). May be present otherwise.

Only available for Threshold tests.


ANAP AUTO, IMPORT

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

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


ALWAYS AUTO, IMPORT

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

ANAP AUTO, IMPORT



>(0024,0306) 1 LO Data Set Name The name assigned to the data set. ALWAYS AUTO, IMPORT

>(0024,0307) 1 LO Data Set Version The software version identifier assigned to the data set.

ALWAYS AUTO, IMPORT

>(0024,0308) 1 LO Data Set Source Source of the data set e.g. the name of the manufacturer, researcher, university, etc.

ALWAYS AUTO, IMPORT

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

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


ALWAYS AUTO, IMPORT

>(0024,0059) 1 CS Global Deviation Probability Normals Flag

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


ALWAYS AUTO, IMPORT

>(0024,0083) 1C SQ Global Deviation Probability Sequence

Probability value and software algorithm used to provide the normality for the global deviation. Only a single Item shall be included in this sequence. Required if Global Deviation Probability Normals Flag (0024,0059) is YES.

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

ANAP AUTO, IMPORT

>>(0024,0071) 1 FL Global Deviation Probability

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


ANAP AUTO, IMPORT

>>(0066,002F) 1 SQ Algorithm Family Code Sequence


ALWAYS AUTO, IMPORT

>>>(0008,0100) 1 SH Code Value Set to: “PERIMETRY” ALWAYS AUTO, IMPORT

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

Set to: “99CZM_PERIMETRY” ALWAYS AUTO, IMPORT

>>>(0008,0104) 1 LO Code Meaning Set to: “CZM Perimetry Algorithms” ALWAYS AUTO, IMPORT

>>(0066,0036) 1 LO Algorithm Name


Set to: “MD Probability”

ALWAYS AUTO, IMPORT

>>(0066,0031) 1 LO Algorithm Version


Set to: “1.0”

ALWAYS AUTO, IMPORT

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

Weighted square root of loss variance, in dB.


ANAP AUTO, IMPORT

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

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


ALWAYS AUTO, IMPORT

>(0024,0085) 1C SQ Localized Deviation Probability

Probability value and software algorithm used to provide the normality for the local deviation. Only a single Item shall be included in this sequence.

ANAP AUTO, IMPORT



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

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

Currently not used.

>>(0024,0073) 1 FL Localized Deviation Probability

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


ANAP AUTO, IMPORT

>>(0066,002F) 1 SQ Algorithm Family Code Sequence


ALWAYS AUTO, IMPORT

>>>(0008,0100) 1 SH Code Value Set to: “PERIMETRY” ALWAYS AUTO, IMPORT


Set to: “99CZM_PERIMETRY” ALWAYS AUTO, IMPORT

>>>(0008,0104) 1 LO Code Meaning Set to: “CZM Perimetry Algorithms” ALWAYS AUTO, IMPORT

>>(0066,0036) 1 LO Algorithm Name


Set to: “PSD Probability”

ALWAYS AUTO, IMPORT

>>(0066,0031) 1 LO Algorithm Version


Set to: “1.0”

ALWAYS AUTO, IMPORT

(0024,0074) 1 CS Short Term Fluctuation Calculated

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


ALWAYS AUTO, IMPORT

(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 AUTO, IMPORT

(0024,0076) 1 CS

Short Term Fluctuation Probability Calculated

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


ALWAYS AUTO, IMPORT

(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 AUTO, IMPORT

(0024,0078) 1 CS

Corrected Localized Deviation From Normal Calculated

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


ALWAYS AUTO, IMPORT



(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 AUTO, IMPORT

(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


ALWAYS AUTO, IMPORT

(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 AUTO, IMPORT

(0024,0320) 3 SQ Visual Field Global Results Index Sequence

Information about various visual field indexes related to test results. One or more Items are permitted in this sequence.

Values extracted from binary data in the raw data source

ANAP AUTO, IMPORT

>(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, IMPORT

>>(0040,A040) 1 CS Value Type

The type of the value encoded in this name-value Item. Defined Terms: DATETIME DATE TIME PNAME UIDREF TEXT CODE NUMERIC COMPOSITE IMAGE

Set to: “NUMERIC”

ALWAYS AUTO, IMPORT

>>(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, IMPORT

>>>(0008,0100) 1 SH Code Value Set to: “111852” ALWAYS AUTO, IMPORT


Set to: “DCM” ALWAYS AUTO, IMPORT

>>>(0008,0104) 1 LO Code Meaning Set to: “Visual Field Index” ALWAYS AUTO, IMPORT

>>(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 AUTO, IMPORT

>>(0040,08EA) 1C SQ Measurement Units Code Sequence

Units of measurement for a numeric value in this name-value Item. Only a single Item shall be included in this Sequence. Required if Value Type (0040,A040) is NUMERIC.

The CodeSequence for %

ALWAYS AUTO, IMPORT



>>>(0008,0100) 1 SH Code Value Set to: “%” ALWAYS AUTO, IMPORT


Set to: “UCUM” ALWAYS AUTO, IMPORT

>>>(0008,0104) 1 LO Code Meaning Set to: “percent” ALWAYS AUTO, IMPORT

>(0024,0338) 1 CS Index Normals Flag

Whether normative data exists for this index. Enumerated Values: YES NO

Set to: “NO”

ALWAYS AUTO, IMPORT

Table 8-33 Ophthalmic Visual Field Static Perimetry Measurements IOD - 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.

ANAP AUTO, IMPORT

>(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, IMPORT

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

Sphere value in diopters.

Extracted from binary data in the raw data source. ALWAYS

AUTO, IMPORT

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

Cylinder value in diopters.


AUTO, IMPORT

>>(0022,0009) 1 FL Cylinder Axis Axis value in degrees.


AUTO, IMPORT

>(0046,0044) 2 FD Pupil Size

The horizontal diameter measurement of the pupil, in mm.


ALWAYS AUTO, IMPORT

>(0022,000D) 2 CS Pupil Dilated The patient’s pupils were pharmacologically dilated for this acquisition. Enumerated Values: YES NO If this tag is empty, no information is available.

EMPTY AUTO

>(0022,000B) 3 FL intraocular Pressure

Value of intraocular pressure in mmHg.

Extracted from binary data in the raw data source. ANAP

AUTO, IMPORT

>(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 AUTO, IMPORT

>>(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

ALWAYS AUTO, IMPORT



other customarily used display notation such as 20/20 in the US and 6/6 in Britain.


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

ANAP AUTO, IMPORT

>(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, IMPORT

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

Sphere value in diopters.


AUTO, IMPORT

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

Cylinder value in diopters.


AUTO, IMPORT

>>(0022,0009) 1 FL Cylinder Axis Axis value in degrees.


AUTO, IMPORT

>(0046,0044) 2 FD Pupil Size

The horizontal diameter measurement of the pupil, in mm.


ALWAYS AUTO, IMPORT

>(0022,000D) 2 CS Pupil Dilated The patient’s pupils were pharmacologically dilated for this acquisition. Enumerated Values: YES NO If this tag is empty, no information is available.

EMPTY AUTO

>(0022,000B) 3 FL intraocular Pressure

Value of intraocular pressure in mmHg.

Extracted from binary data in the raw data source. ANAP

AUTO, IMPORT

>(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 AUTO, IMPORT

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


ANAP AUTO, IMPORT

Table 8-34 Ophthalmic Visual Field Static Perimetry Measurements IOD - 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, IMPORT

(0008,0018) 1 UI SOP Instance UID Newly created with UID root: 1.2.276.0.75.2.2.30.2

ALWAYS AUTO, IMPORT

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



IMPORT


Date the SOP Instance was created.

Set to current date. ALWAYS

AUTO


Time the SOP Instance was created.

Set to current time ALWAYS

AUTO

Table 8-35 Ophthalmic Visual Field Static Perimetry Measurements IOD - 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 raw data source.

ALWAYS AUTO, IMPORT


Uniquely identifies the referenced SOP Class.

The source is always a raw IOD. ALWAYS

AUTO, IMPORT


Uniquely identifies the referenced SOP Instance.

The instance UID of the raw instance containing the source data of this instance.

ALWAYS AUTO, IMPORT

>(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, IMPORT

>>(0008,0100) 1 SH Code Value Set to: “RAW DATA SRC” ALWAYS AUTO, IMPORT



>>(0008,0104) 1 LO Code Meaning Set to: "CZM Perimetry Source Exam". ALWAYS AUTO, IMPORT

8.1.2 Usage of Attributes from Received IOD’s

Each Application that depends on certain fields to function correctly should specify which ones are required for it to perform its intended function.

The HFA 3 Application Software provides standard conformance..

8.1.3 Attribute Mapping

In scheduled case, the following attributes are mapped from Modality Worklist to instances of Ophthalmic Photography 8 Bit IOD and Raw Data IOD.

Table 8-36 Attribute Mapping

Modality Worklist Instance IOD Editable

(0010,0010) Patient's Name (0010,0010) Patient's Name No

(0010,0020) Patient ID (0010,0020) Patient ID No

(0010,0021) Issuer of Patient ID (0010,0021) Issuer of Patient ID No

(0010,1000) Other Patient IDs (0010,1000) Other Patient IDs No



(0010,0030) Patient's Birth Date (0010,0030) Patient's Birth Date No

(0010,0040) Patient's Sex (0010,0040) Patient's Sex No

(0010,2160) Ethnic Group (0010,2160) Ethnic Group No

(0010,4000) Patient Comments (0010,4000) Patient Comments No

(0008,0050) Accession Number (0008,0050) Accession Number No

(0008,0090) Referring Physicians Name (0008,0090) Referring Physicians Name No

(0040,1001) Requested Procedure ID

(0020,0010) Study ID No

(0040,0275)> (0040,1001)


> Requested Procedure ID No

(0032,1060) Requested Procedure Description

(0008,1030) Study Description No

(0040,0275)> (0032,1060)


> Requested Procedure Description

No

(0018,1030) Protocol Name No

(0040,0254) Performed Procedure Step Description

No

(0032,1064) Requested Procedure Code Sequence

(0008,1032) Procedure Code Sequence No

>(0008,0100) Code Value >(0008,0100) Code Value No

>(0008,0102) Coding Scheme Designator >(0008,0102) Coding Scheme Designator No

>(0008,0103) Coding Scheme Version >(0008,0103) Coding Scheme Version No

>(0008,0104) Code Meaning >(0008,0104) Code Meaning No

(0020,000D) Study Instance UID (0020,000D) Study Instance UID No

(0008,1110) Referenced Study Sequence (0008,1110) Referenced Study Sequence No

>(0008,1150) Referenced Sop Class UID >(0008,1150) Referenced Sop Class UID No

>(0008,1155) Referenced Sop Instance UID >(0008,1155) Referenced Sop Instance UID No


No

>(0040,0007) Scheduled Procedure Step Description

(0040,0275)> (0040,0007)


> Scheduled Procedure Step Description

No

>(0040,0008) Scheduled Protocol Code Sequence

(0040,0275)> (0040,0008)


> Scheduled Protocol Code Sequence

No

>>(0008,0100) Code Value >(0008,0100) Code Value No

>>(0008,0102) Coding Scheme Designator >(0008,0102) Coding Scheme Designator No

>>(0008,0103) Coding Scheme Version >(0008,0103) Coding Scheme Version No

>>(0008,0104) Code Meaning >(0008,0104) Code Meaning No



>(0040,0009) Scheduled Procedure Step ID (0040,0275)> (0040,0009)


> Scheduled Procedure Step ID

No

Note: In the unscheduled case some of these values are editable – but in the scheduled case all values that are retrieved are not editable by the user.

8.1.4 Coerced/Modified Files

Tags are listed in chapter 4.2.1.3.2 Activity – Query Modality Worklist..

Other attributes are lost and are not available in the HFA 3 Application Software.



8.2 Data Dictionary of Private Attributes The Application Software AE defines the following private attributes

Table 8-37 Private Dictionary Group 0301 “99CZM_Hfa_VisualField”

99CZM_Hfa_VisualField

Tag Name VR VM

(0301,xx00) test_type US 1

(0301,xx01) test_strategy US 1

(0301,xx02) test_pattern US 1

(0301,xx03) screening_mode US 1

(0301,xx04) stimulus_color US 1

(0301,xx05) stimulus_size US 1

(0301,xx06) blue_yellow US 1

(0301,xx07) pdb_version US 1

(0301,xx08) hfa_raw_data OB 1

(0301,xx09) kinetic_test_category US 1

(0301,xx0a) user_defined_pattern_name LO 1

(0301,xx0b) user_defined_pattern_id LO 1

(0301,xx26) pupil_diameter FD 1

(0301,xx27) trial_sphere_lens_power FD 1

(0301,xx28) trial_cylinder_lens_power FD 1

(0301,xx29) trial_cylinder_axis FD 1

(0301,xx2a) distance_sphere_lens_power FD 1

(0301,xx2b) distance_cylinder_lens_power FD 1

(0301,xx2c) distance_cylinder_axis FD 1

(0301,xx2d) visual_acuity US 1

(0301,xx2e) cup_disc_ratio_horizontal FD 1

(0301,xx2f) cup_disc_ratio_vertical FD 1

(0301,xx30) intraocular_pressure US 1

(0301,xx31) hfa_measurements_right_eye_sequence SQ 1

(0301,xx32) hfa_measurements_left_eye_sequence SQ 1

(0301,xx33) doctors_comments LT 1



(0301,xx34) chin_rest_location_x FD 1

(0301,xx35) chin_rest_location_y FD 1

(0301,xx36) user_profile_signature LO 1

(0301,xx37) user_profile_name LO 1

(0301,xx38) pupil_diameter_acqusition_mode US 1

(0301,xx39) report_type_sequence SQ 1

(0301,xx3a) report_type US 1

(0301,xx3b) screening_intensity US 1

(0301,xx3c) blind_spot_size US 1

(0301,xx3d) fixation_monitor US 1

(0301,xx3e) fixation_target US 1

(0301,xx3f) foveal_threshold US 1

(0301,xx40) fluctuation US 1

(0301,xx41) test_speed US 1

(0301,xx42) hfa_response_data OB 1

(0301,xx43) kinetic_scan_sequence SQ 1

(0301,xx44) scan_type US 1

(0301,xx45) isopter_identifier US 1

(0301,xx46) result_identifier US 1

(0301,xx47) scan_identifier US 1

(0301,xx48) begin_point_radius FD 1

(0301,xx49) begin_point_angle FD 1

(0301,xx4a) end_point_radius FD 1

(0301,xx4b) end_point_angle FD 1

(0301,xx4c) stop_point_radius FD 1

(0301,xx4d) stop_point_angle FD 1

(0301,xx4e) seen US 1

(0301,xx4f) retest US 1

(0301,xx50) stimulus_intensity US 1

(0301,xx51) scan_speed US 1



Table 8-38 Private Dictionary Group 0303 “99CZM_SantaCruz_Perimetry_8BitImage”

99CZM_SantaCruz_Perimetry_8BitImage

Tag Name VR VM

(0303,xx10) verify_eye_metadata SQ 1

(0303,xx11) time_stamp US 1

(0303,xx12) question_number US 1

(0303,xx13) question_x_coordinate SS 1

(0303,xx14) question_y_coordinate SS 1

(0303,xx15) question_notes SQ 1

(0303,xx16) note LO 1

(0303,xx17) pupil_diameter FD 1

(0303,xx18) gaze_x_delta US 1

(0303,xx19) gaze_y_delta US 1

(0303,xx1a) gaze_status US 1

(0303,xx1b) image_checksum LO 1

(0303,xx1c) question_type US 1

8.3 Coded Terminology and Templates The Application Software AE does not specify a custom coded terminology..

8.4 Greyscale Image Consistency 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-35 Ophthalmic Visual Field Static Perimetry Measurements IOD - Module "Czm Ophthalmic Visual Field Static Perimetry Measurements 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:

FORUM including FORUM Glaucoma Workplace

DICOM Conformance Statement - ZEISS · 2020-02-05 · the format type of an individual DICOM data...

Documents

Transcript of DICOM Conformance Statement - ZEISS · 2020-02-05 · the format type of an individual DICOM data...