DICOM Conformance Statement IVUE

Doc#: 200-53659
DICOM Conformance Statement

Rev: A
Optovue DICOM Module

Optovue DICOM Conformance Statement

Copyright © 2018 Optovue, Incorporated
Doc#: 200-53659
Rev: A
Optovue DICOM Conformance Statement Page | 1

Doc#: 200-53659
Rev: A
1 CONFORMANCE STATEMENT OVERVIEW
The Optovue DICOM Module provides DICOM support for Optovue DICOM ophthalmic imaging devices in conformance
with the DICOM 3.0 standard. Support is provided to import patient information from a Modality Worklist Server, generate
DICOM files, and transfer generated DICOM files to a networked PACS system. This DICOM Conformance Statement
describes conformance for all available options.
The Optovue DICOM Module provides DICOM support for the RTVue XR OCT Avanti, iVue, iScan, iFusion, and iCam
applications. Support is dependent on the product software version and licensing. Generation of OP and OPT DICOM files
is supported for selected scan types as described in this document.
The following table is an overview of the network interfaces provided by the Optovue DICOM module.
Table 1-1 Network Services
NETWORK SERVICES
SOP Classes User of Provider of
Service (SCU) Service (SCP)
Transfer
Encapsulated PDF Storage Yes No
Ophthalmic Photography 8 Bit Image Storage Yes No
Ophthalmic Tomography Image Storage Yes No
Secondary Capture Image Storage Yes No
Workflow Management
Modality Worklist Information Model - FIND Yes No
Verification Yes No

Doc#: 200-53659
Rev: A
2 TABLE OF CONTENTS
1 ... CONFORMANCE STATEMENT OVERVIEW .................................................................................................2
2 ... Table of Contents .................................................................................................................................................3
3 ... INTRODUCTION ..................................................................................................................................................8
3.1 ....... REVISION HISTORY ............................................................................................................................8
3.2 ....... AUDIENCE .............................................................................................................................................8
3.3 ....... REMARKS ..............................................................................................................................................8
3.3.1 .... DICOM Supported Optovue Products and Scan Types ...........................................................9
3.4 ....... TERMS AND DEFINITIONS ..............................................................................................................10
3.5 ....... BASICS OF DICOM COMMUNICATION .........................................................................................12
3.6 ....... ABBREVIATIONS ................................................................................................................................13
3.7 ....... REFERENCES .....................................................................................................................................14
4 ... NETWORKING ...................................................................................................................................................15
4.1 ....... IMPLEMENTATION MODEL – VERIFICATION .............................................................................15
4.1.1 .... Application Data Flow ..................................................................................................................15
4.1.2 .... Functional Definitions of AEs ......................................................................................................16
4.1.3 .... Sequencing of Real-World Activities ..........................................................................................16

4.2 ....... IMPLEMENTATION MODEL – MODALITY WORKLIST ...............................................................17
4.2.2 .... Functional Definition of AETs .....................................................................................................18
4.2.5 .... Functional Definition of AETs .....................................................................................................22

4.3 ....... AE SPECIFICATIONS ........................................................................................................................24
4.3.1 .... SOP Class Specification ..............................................................................................................24
4.3.2 .... Association Policies ......................................................................................................................24

Doc#: 200-53659
Rev: A
4.3.3 .... Association initiation by Real-World Activity .............................................................................25

4.4 ....... NETWORK INTERFACES .................................................................................................................30
4.4.1 .... Physical Network Interfaces ........................................................................................................30
4.4.2 .... Additional Protocols ......................................................................................................................30

4.5 ....... CONFIGURATION...............................................................................................................................30
4.5.1 .... AE Title/Presentation Address Mapping ...................................................................................30
4.5.2 .... Parameters ....................................................................................................................................30

5 ... MEDIA INTERCHANGE....................................................................................................................................32
6 ... SUPPORT OF CHARACTER SETS ...............................................................................................................32
7 ... Security ................................................................................................................................................................32
8 ... ANNEXES ...........................................................................................................................................................33
8.1 ....... IOD CONTENTS ..................................................................................................................................33
8.1.1 .... Created SOP Instances ...............................................................................................................33
8.1.2 .... Usage of Attributes from Received IODs ..................................................................................69
8.1.3 .... Attribute mapping..........................................................................................................................70
8.1.4 .... Coerced/Modified Fields ..............................................................................................................70

8.2 ....... DATA DICTIONARY OF PRIVATE ATTRIBUTES .........................................................................70
8.3 ....... CODED TERMINOLOGY AND TEMPLATES .................................................................................70
8.4 ....... GRAYSCALE IMAGE CONSISTENCY ............................................................................................70
8.5 ....... STANDARD EXTENDED / SPECIALIZED / PRIVATE SOP CLASSES .....................................70
8.6 ....... PRIVATE TRANSFER SYNTAXES ..................................................................................................70
A. .. APPENDIX A – Secondary Capture IOD for ODM Conversion Option .....................................................70
Table 1-1 Network Services .................................................................................................................................................................. 2
Table 3-1 DICOM Supported Scan Types per Product ..................................................................................................................... 9
Figure 1 Application Data Flow Diagram - Verification for Modality Worklist SCP ...................................................................... 15
Figure 2 Application Data Flow Diagram - Verification for Data Storage SCP ............................................................................ 16

Doc#: 200-53659
Rev: A
Figure 3 Sequencing of Real-World Activities - Verification ........................................................................................................... 17
Figure 4 Application Data Flow - Modality Worklist Query .............................................................................................................. 18
Figure 5 Sequencing of Real World Activities - MWL Query .......................................................................................................... 21
Figure 6 Application Data Flow - Storage .......................................................................................................................................... 22
Figure 7 Sequencing of Real-World Activities - Storage ................................................................................................................. 23
Figure 8 Implementation Class and Version ..................................................................................................................................... 25
Table 4-1 Presentation Contexts for Verification .............................................................................................................................. 25
Table 4-3 SOP Specific Conformance for Modality Worklist .......................................................................................................... 27
Table 8-1 Ophthalmic Photography 8 Bit - Patient Module ............................................................................................................. 35
Table 8-2 Ophthalmic Photography 8 Bit - General Study Module ................................................................................................ 35
Table 8-3 Ophthalmic Photography 8 Bit - General Series Module ............................................................................................. 35
Table 8-4 Ophthalmic Photography 8 Bit - Ophthalmic Photography Series Module ................................................................. 36
Table 8-5 Ophthalmic Photography 8 Bit - Synchronization Module ............................................................................................. 36
Table 8-6 Ophthalmic Photography 8 Bit - General Equipment Module ....................................................................................... 37
Table 8-7 Ophthalmic Photography 8 Bit - General Image Module ............................................................................................... 37
Table 8-8 Ophthalmic Photography 8 Bit - Image Pixel Module .................................................................................................... 38
Table 8-9 Ophthalmic Photography 8 Bit - Multi Frame Module .................................................................................................... 39
Table 8-10 Ophthalmic Photography 8 Bit - Ophthalmic Photography Image Module ............................................................... 40
Table 8-11 Ophthalmic Photography 8 Bit - Ocular Region Imaged Module ............................................................................... 41
Table 8-12 Ophthalmic Photography 8 Bit - Ophthalmic Photography Acquisition Parameters Module ................................. 41
Table 8-13 Ophthalmic Photography 8 Bit - Ophthalmic Photographic Parameters Module ..................................................... 42
Table 8-14 Ophthalmic Photography 8 Bit - SOP Common Module ............................................................................................. 45
Table 8-15 Ophthalmic Tomography Image - Patient Module ........................................................................................................ 47

Doc#: 200-53659
Rev: A
Table 8-16 Ophthalmic Tomography Image - General Study Module........................................................................................... 47
Table 8-17 Ophthalmic Tomography Image - General Series Module ......................................................................................... 48
Table 8-18 Ophthalmic Tomography Image - Ophthalmic Tomography Series Module ............................................................ 48
Table 8-19 Ophthalmic Tomography Image - Frame of Reference Module ................................................................................. 48
Table 8-20 Ophthalmic Tomography Image - Synchronization Module ........................................................................................ 49
Table 8-21 Ophthalmic Tomography Image - General Equipment Module .................................................................................. 49
Table 8-22 Ophthalmic Tomography Image - Enhanced General Equipment Module ............................................................... 49
Table 8-23 Ophthalmic Tomography Image - Image Pixel Module ............................................................................................... 50
Table 8-24 Ophthalmic Tomography Image - Multi Frame Functional Groups Module ............................................................. 51
Table 8-25 Ophthalmic Tomography Image - Multi Frame Dimension Module ........................................................................... 55
Table 8-26 Ophthalmic Tomography Image - Acquisition Context Module .................................................................................. 55
Table 8-27 Ophthalmic Tomography Image - Ophthalmic Tomography Image Module ............................................................ 56
Table 8-28 Ophthalmic Tomography Image - Ophthalmic Tomography Acquisition Parameters Module ............................... 58
Table 8-29 Ophthalmic Tomography Image - Ophthalmic Tomography Parameters Module ................................................... 58
Table 8-30 Ophthalmic Tomography Image - Ocular Region Imaged Module ............................................................................ 59
Table 8-31 Ophthalmic Tomography Image - SOP Common Module .......................................................................................... 60
Table 8-32 Encapsulated PDF - Patient Module .............................................................................................................................. 61
Table 8-33 Encapsulated PDF - General Study Module ................................................................................................................. 62
Table 8-34 Encapsulated PDF - Encapsulated Document Series Module ................................................................................... 62
Table 8-35 Encapsulated PDF - General Equipment Module ........................................................................................................ 63
Table 8-36 Encapsulated PDF - SC Equipment Module ................................................................................................................. 63
Table 8-37 Encapsulated PDF - Encapsulated Document Module ............................................................................................... 63
Table 8-38 Encapsulated PDF - SOP Common Module ................................................................................................................. 64

Doc#: 200-53659
Rev: A
Table 8-39 Secondary Capture - Patient Module ............................................................................................................................. 65
Table 8-40 Secondary Capture - General Study Module ................................................................................................................ 66
Table 8-41 Secondary Capture - General Series Module ............................................................................................................... 66
Table 8-42 Secondary Capture - General Equipment Module ....................................................................................................... 67
Table 8-43 Secondary Capture - SC Equipment Module ................................................................................................................ 67
Table 8-44 Secondary Capture - General Image Module ............................................................................................................... 67
Table 8-45 Secondary Capture - Image Pixel Module ..................................................................................................................... 68
Table 8-46 Secondary Capture - SOP Common Module ................................................................................................................ 69

Doc#: 200-53659
Rev: A
3 INTRODUCTION
3.1 REVISION HISTORY
Document Version Date of Issue Author Description

1.0 September 2, 2012 James C Brock Pope Initial Version
1.1 October 18,2012 James C Brock Pope Revision to reflect version 1.0.1.013
1.2 December 14, 2012 James C Brock Pope Elaborated Optovue product support
2.03 December 15, 2014 James C Brock Pope Updated SOP Class conformance
2.04 June 18, 2015 Per Pedersen Updated SOP Class conformance
3.01 June 20, 2018 Marilyn Dunn Updated for ODM version 3.0 and
Haichou Fan support for OP, OPT, Secondary
James C Brock Pope Capture, and Encapsulated PDF IODs.
3.2 AUDIENCE
This document is written for the people that need to understand how the Optovue DICOM Module will integrate into their
healthcare facility. This includes both those responsible for overall imaging network policy and architecture, as well as
integrators who need to have a detailed understanding of the DICOM features of the product. This document contains
some basic DICOM definitions so that any reader may understand how this product implements DICOM features.
However, integrators are expected to fully understand all the DICOM terminology, how the tables in this document relate
to the product’s functionality, and how that functionality integrates with other devices that support compatible DICOM
features
3.3 REMARKS
The scope of this DICOM Conformance Statement is to facilitate integration between the Optovue DICOM Module and
other DICOM products. The Conformance Statement should be read and understood in conjunction with the DICOM
Standard. DICOM by itself does not guarantee interoperability. The Conformance Statement does, however, facilitate a
first-level comparison for interoperability between different applications supporting compatible DICOM functionality.
This Conformance Statement is not intended to replace validation with other DICOM equipment to ensure proper
exchange of intended information. In fact, the user should be aware of the following important issues:

Doc#: 200-53659
Rev: A
• The comparison of different Conformance Statements is just the first step towards assessing interconnectivity and
interoperability between the product and other DICOM conformant equipment.
• Test procedures should be defined and executed to validate the required level of interoperability with specific
compatible DICOM equipment, as established by the healthcare facility.
3.3.1 DICOM SUPPORTED OPTOVUE PRODUCTS AND SCAN TYPES
The Optovue DICOM Module 3.0 is supported for use with the following Optovue products:
• RTVue XR OCT Avanti Software Version 2017.1 and above

• iVue Software Version 2018.0 and above
• iScan Software Version 2018.0 and above
• iCam Software Version 2018.0 and above
• iFusion: Refer to iVue and iCam Software Versions above
• Optovue DICOM Module Dashboard Version 3.0
An Optovue DICOM license is required for use with each device using DICOM features in Optovue applications.
DICOM support is provided for the following scan types:
Table 3-1 DICOM Supported Scan Types per Product
Product
Scan iVue
RTVue XR OCT Avanti iCam iFusion
Type iScan
Cross Line OP/OPT OP/OPT --- OP/OPT
Enhanced HD
OP/OPT --- --- ---
Line
GCC OP/OPT OP/OPT --- OP/OPT
Grid OP/OPT --- --- ---
Line OP/OPT --- --- ---
OP/OPT (Radial lines OP/OPT (Radial lines OP/OPT (Radial lines

ONH ---
only) only) only)
Radial Lines OP/OPT --- --- ---
Raster OP/OPT --- --- ---

Doc#: 200-53659
Rev: A
Product
Scan iVue
RTVue XR OCT Avanti iCam iFusion
Type iScan
Retina Map OP/OPT OP/OPT --- OP/OPT
iWellness --- OP/OPT --- OP/OPT
3D Retina --- OP/OPT --- OP/OPT
Fundus --- --- OP OP
3.4 TERMS AND DEFINITIONS
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.

Doc#: 200-53659
Rev: A
Joint Photographic Experts Group (JPEG) – a set of standardized image compression techniques, available for use by
DICOM applications.
Module – a set of Attributes within an Information Object Definition that are logically related to each other. Example:
Patient Module includes Patient Name, Patient ID, Patient Birth Date, and Patient Sex.
Negotiation – first phase of Association establishment that allows Application Entities to agree on the types of data to be
exchanged and how that data will be encoded.
Presentation Context – the set of DICOM network services used over an Association, as negotiated between Application
Entities; includes Abstract Syntaxes and Transfer Syntaxes.
Protocol Data Unit (PDU) – a packet (piece) of a DICOM message sent across the network. Devices must specify the
maximum size packet they can receive for DICOM messages.
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.

Doc#: 200-53659
Rev: A
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.
C-Echo - DICOM Service used to verify end-to-end DICOM communication. Very similar to a ping request.
C-Store - DICOM Service used to store DICOM Objects (such as images) to a PACS system.
C-Find - DICOM Service used to find or retrieve various DICOM Objects (e.g. worklist or images).
3.5 BASICS OF DICOM COMMUNICATION
This section describes terminology used in this Conformance Statement for the non-specialist. The key terms used in the
Conformance Statement are highlighted in italics below. This section is not a substitute for training about DICOM, and it
makes many simplifications about the meanings of DICOM terms.
Two Application Entities (devices) that want to communicate with each other over a network using DICOM protocol must
first agree on several things during an initial network “handshake”. One of the two devices must initiate an Association (a
connection to the other device), and ask if specific services, information, and encoding can be supported by the other
device (Negotiation).
DICOM specifies several network services and types of information objects, each of which is called an Abstract Syntax for
the Negotiation. DICOM also specifies a variety of methods for encoding data, denoted Transfer Syntaxes. The
Negotiation allows the initiating Application Entity to propose combinations of Abstract Syntax and Transfer Syntax to be
used on the Association; these combinations are called Presentation Contexts. The receiving Application Entity accepts
the Presentation Contexts it supports.
For each Presentation Context, the Association Negotiation also allows the devices to agree on Roles – which one is the
Service Class User (SCU - client) and which is the Service Class Provider (SCP - server). Normally the device initiating
the connection is the SCU, i.e., the client system calls the server, but not always.
The Association Negotiation finally enables exchange of maximum network packet (PDU) size, security information, and
network service options (called Extended Negotiation information).
The Application Entities, having negotiated the Association parameters, may now commence exchanging data. Common
data exchanges include queries for worklists and lists of stored images, transfer of image objects and analyses (structured
reports), and sending images to film printers. Each exchangeable unit of data is formatted by the sender in accordance
with the appropriate Information Object Definition and sent using the negotiated Transfer Syntax. There is a Default
Transfer Syntax that all systems must accept, but it may not be the most efficient for some use cases. Each transfer is

Doc#: 200-53659
Rev: A
explicitly acknowledged by the receiver with a Response Status indicating success, failure, or that query or retrieve
operations are still in process.
Two Application Entities may also communicate with each other by exchanging media (such as a CD-R). Since there is
no Association Negotiation possible, they both use a Media Application Profile that specifies “pre-negotiated” exchange
media format, Abstract Syntax, and Transfer Syntax.
3.6 ABBREVIATIONS
AE Application Entity
AET Application Entity Title
DHCP Dynamic Host Configuration Protocol
DICOM Digital Imaging and Communications in Medicine
DNS Domain Name System
EPDF Encapsulated PDF
HIS Hospital Information System
HL7 Health Level 7 Standard
IHE Integrating the Healthcare Enterprise
IOD Information Object Definition
ISO International Organization for Standards
JPEG Joint Photographic Experts Group
MWL Modality Worklist
O Optional (Key Attribute)
ODM Optovue DICOM Module
OP Ophthalmic Photography
OPT Ophthalmic Tomography
OT Other (for DICOM Modality type)
OSI Open Systems Interconnection

Doc#: 200-53659
Rev: A
PACS Picture Archiving and Communication System
R Required (Key Attribute)
SC Secondary Capture
SCP Service Class Provider
SCU Service Class User
SOP Service-Object Pair
TCP/IP Transmission Control Protocol / Internet Protocol
U Unique (Key Attribute)
UID Unique Identifier
VR Value Representation
3.7 REFERENCES
NEMA PS3 Digital Imaging and Communications in Medicine (DICOM) Standard 3.0, available free at
http://medical.nema.org/
Optovue DICOM Module Setup and Operation Manual Version 3.0.0.6

Doc#: 200-53659
Rev: A
4 NETWORKING
The Optovue DICOM Module supports the following DICOM workflows in its DICOM implementation model:
• Verification Service
• Modality Worklist
• Network Storage
The Optovue DICOM Module includes a standalone configuration and service application that supports entry of user
configuration information for DICOM connections with a Modality Worklist SCP and a DICOM Storage SCP.
4.1 IMPLEMENTATION MODEL – VERIFICATION
4.1.1 APPLICATION DATA FLOW
The Optovue DICOM Module supports configuration of a Modality Worklist Server and a DICOM Storage Server, and it
allows entry of an Application Entity Title for each configuration. The Verification Service is used to confirm that a DICOM
connection can be established with the configured servers.
Figure 1 Application Data Flow Diagram - Verification for Modality Worklist SCP

Doc#: 200-53659
Rev: A
Figure 2 Application Data Flow Diagram - Verification for Data Storage SCP
4.1.2 FUNCTIONAL DEFINITIONS OF AES
For verification of a DICOM connection with a Modality Worklist SCP or DICOM Storage SCP, the Optovue DICOM
Module opens an association with the configured DICOM SCP (Modality Worklist Server or DICOM Storage Server) and
uses the C-Echo message protocol to verify a DICOM connection with the server.
4.1.3 SEQUENCING OF REAL-WORLD ACTIVITIES
The user enters the configuration information for the DICOM service providers in the Optovue DICOM Module
configuration application. Then the user can request an “Echo Test” for the configured servers. The ODM application uses
the DICOM Verification Service protocol to confirm that a DICOM association can be established with the configured
servers.

Doc#: 200-53659
Rev: A
Figure 3 Sequencing of Real-World Activities - Verification
4.2 IMPLEMENTATION MODEL – MODALITY WORKLIST
The Optovue DICOM Module Application Entity queries a Modality Worklist Server to retrieve patient record information.
The patient record information from the worklist can be used to create patient records in the Optovue patient database.

Doc#: 200-53659
Rev: A
Figure 4 Application Data Flow - Modality Worklist Query
4.2.2 FUNCTIONAL DEFINITION OF AETS
The Optovue DICOM Module Modality Worklist Application Entity connects and queries a MWL server as a Modality
Worklist SCU.
The Optovue DICOM Module supports several configuration options for DICOM query requests of a Modality Worklist
SCP:
• Worklist Query Mode:

o General Worklist Query (Default)
• Option to always include end date in worklist query request.
• Station Name and Station AET
The user enters the configuration information for the Modality Worklist SCP in the Optovue DICOM Module standalone
configuration application.
The user can request a Modality Worklist query when using the machine (scanning device) application. When the user
requests a MWL query, the application queries the MWL server using the configured MWL information. The patient

Doc#: 200-53659
Rev: A
records retrieved from the MWL server are displayed in a spreadsheet dialog. The user selects a patient record from the
spreadsheet to start a visit for the patient.

Doc#: 200-53659
Rev: A

Doc#: 200-53659
Rev: A
Figure 5 Sequencing of Real World Activities - MWL Query

Doc#: 200-53659
Rev: A
Implementation Model – Storage
The Optovue DICOM Module Application Entity sends generated DICOM files to a DICOM Storage SCP (PACS).
Figure 6 Application Data Flow - Storage
4.2.5 FUNCTIONAL DEFINITION OF AETS
The Optovue DICOM Module functions as a DICOM Storage SCU.
The user enters the configuration information for the DICOM Storage SCP in the Optovue DICOM Module standalone
configuration application.
The user can request generation and transfer of DICOM files when using the machine (scanning device) and ReVue
applications. DICOM user preference settings are supported in the machine and ReVue applications to customize
application DICOM support.
When a report is displayed in the application, the following options are available:

Doc#: 200-53659
Rev: A
• For OCT scans, when the report DICOM button is selected, OP (for the IR or SLO En Face image) and OPT DICOM
files are generated and stored on the DICOM Storage SCP.
The generation of OP and OPT DICOM files for OCT scans is supported for the scan types listed in Table 3-1..
• For Fundus scans, when the report DICOM button is selected, an OP (for the fundus image) is generated and stored
on the DICOM Storage SCP.
• When the “camera” tool is selected for a report, an ePDF or Secondary Capture DICOM file is generated and stored
on the DICOM Storage SCP.
Figure 7 Sequencing of Real-World Activities - Storage

Doc#: 200-53659
Rev: A
4.3 AE SPECIFICATIONS
4.3.1 SOP CLASS SPECIFICATION
The Optovue DICOM Module provides Standard Conformance to the following DICOM SOP classes as an SCU:
SOP Class Name SOP Class UID SCU
Verification Service Class 1.2.840.10008.1.1 Yes
Ophthalmic Tomography Image Storage 1.2.840.10008.5.1.4.1.1.77.1.5.4 Yes
Ophthalmic Photography 8 Bit Image Storage 1.2.840.10008.5.1.4.1.1.77.1.5.1 Yes

(for IR, SLO En Face and fundus images)
Encapsulated PDF Storage 1.2.840.10008.5.1.4.1.1.104.1 Yes
Secondary Capture Image Storage 1.2.840.10008.5.1.4.1.1.7 Yes
Modality Worklist Information Model - FIND 1.2.840.10008.5.1.4.31 Yes
4.3.2 ASSOCIATION POLICIES
4.3.2.1 GENERAL
The specifications for DICOM communication are configured in the standalone Optovue DICOM Module configuration
application. These specifications are required for Modality Worklist and DICOM Data Storage usage.
4.3.2.2 NUMBER OF ASSOCIATIONS
The Optovue DICOM Module supports a single association as an SCU.
4.3.2.3 ASYNCHRONOUS NATURE
The Optovue DICOM Module does not support asynchronous communication.

Doc#: 200-53659
Rev: A
4.3.2.4 IMPLEMENTATION IDENTIFYING INFORMATION
The DICOM Implementation Class and Version for generated files is as follows:
Implementation Class UID 1.2.276.0.7230010.3.0.3.60
Implementation Version Name OFFIS_DCMTK_360
Figure 8 Implementation Class and Version
4.3.3 ASSOCIATION INITIATION BY REAL-WORLD ACTIVITY
The following services are initiated by the Optovue DICOM Module:
• C-ECHO
• C-FIND
• C-STORE
4.3.3.1 REAL-WORLD ACTIVITY FOR VERIFICATION
The Optovue DICOM module initiates an association for C-ECHO.
4.3.3.2 ASSOCIATED REAL WORLD ACTIVITY FOR VERIFICATION
The user enters configuration information for the Modality Worklist SCP and the Data Storage SCP in the Optovue
DICOM Module standalone configuration application. After entering the SCP configuration information, the user may
initiate verification tests from within the configuration screen to the configured SCPs.
4.3.3.3 PRESENTATION CONTEXTS FOR VERIFICATION

Table 4-1 Presentation Contexts for Verification
PRESENTATION CONTEXTS FOR VERIFICATION

Doc#: 200-53659
Rev: A
Presentation Context Table
Abstract Syntax Transfer Syntax

Extended
Name UID Name List UID List
Role Negotiation
Verification Service Implicit VR Little Endian 1.2.840.10008.1.2

1.2.840.10008.1.1 SCU None
Class Explicit VR Little Endian 1.2.840.10008.1.2.1
4.3.3.4 REAL WORLD ACTIVITY FOR MODALITY WORKLIST
The Optovue DICOM module initiates an association for C-FIND.
4.3.3.5 ASSOCIATED REAL WORLD ACTIVITY FOR MODALITY WORKLIST
The user requests the Modality Worklist dialog. The user may enter worklist search criteria in the Modality Worklist dialog
and then start the worklist query.
The Optovue DICOM Module opens an association with the Modality Worklist SCP and sends a C-FIND request with the
user’s search criteria. The C-FIND request is sent with the worklist query mode configured in the Optovue DICOM
Module. The MWL server sends C-FIND responses to the Optovue DICOM Module with matching patient records from the
worklist entries. The matching patient records are displayed in the Optovue DICOM Module worklist spreadsheet.
4.3.3.6 PRESENTATION CONTEXTS FOR MODALITY WORKLIST
Table 4-2 Presentation Contexts for Modality Worklist
PRESENTATION CONTEXTS FOR MODALITY WORKLIST

Extended
Role Negotiation
Implicit VR Little Endian 1.2.840.10008.1.2

Modality Worklist Information
1.2.840.10008.5.1.4.31 SCU None
Model – C-FIND
Explicit VR Little Endian 1.2.840.10008.1.2.1
4.3.3.7 SOP SPECIFIC CONFORMANCE FOR MODALITY WORKLIST

Doc#: 200-53659
Rev: A
The following table outlines the attributes that are accepted and placed into the images. Any unexpected values are not
used.
Table 4-3 SOP Specific Conformance for Modality Worklist
Module Name Tag VR M R Q D IOD

Attribute Name
SOP Common
Specific Character Set (0008,0005) CS x
Scheduled Procedure Step

Scheduled Procedure Step Sequence (0040,0100) SQ x
> Scheduled Station AET (0040,0001) AE (S) x x
> Scheduled Procedure Step Start Date (0040,0002) DA S x x
> Scheduled Procedure Step Start Time (0040,0003) TM x
> Modality (0008,0060) CS S x x x x
> Scheduled Performing Physician’s Name (0040,0006) PN x
> Scheduled Procedure Step Description (0040,0007) LO x
> Scheduled Station Name (0040,0010) SH x
> Scheduled Procedure Step Location (0040,0011) SH x
> Scheduled Protocol Code Sequence (0040,0008) SQ x
> Pre-Medication (0040,0012) LO
> Scheduled Procedure Step ID (0040,0009) SH x x
> Requested Contrast Agent (0032,1070) LO
Requested Procedure
Requested Procedure ID (0040,1001) SH x x
Requested Procedure Description (0032,1060) LO x x
Study Instance UID (0020,000D) UI x x x
Requested Procedure Priority (0040,1003) SH x
Patient Transport Arrangements (0040,1004) LO x
Referenced Study Sequence (0008,1110) SQ x
Requested Procedure Code Sequence (0032,1064) SQ x
Imaging Service Request

Accession Number (0008,0050) SH x x x
Requesting Physician (0032,1032) PN x
Referring Physician's Name (0008,0090) PN x x x

Doc#: 200-53659
Rev: A
Module Name Tag VR M R Q D IOD

Attribute Name
Visit Identification
Admission ID (0038,0010) LO x
Visit Status
Current Patient Location (0038,0300) LO x
Visit Admission
Admitting Diagnosis Description (0008,1080) LO x
Patient Identification
Patient Name (0010,0010) PN x x x x
Patient ID (0010,0020) LO x x x x
Patient Demographic
Patient’s Birth Date (0010,0030) DA x x x
Patient’s Sex (0010,0040) CS x x x
Patient’s Weight (0010,1030) DS
Confidentiality constraint on patient data (0040,3001) LO
Patient Medical
Patient State (0038,0500) LO
Pregnancy Status (0010,21C0) US
Medical Alerts (0010,2000) LO
Allergies (0010,2110) LO
Special Needs (0038,0050) LO
The above table should be read as follows:
Module Name: The name of the associated module for supported worklist attributes.
Attribute Name: Attributes supported to build a Modality Worklist Request Identifier.
Tag: DICOM tag for this attribute.
VR: DICOM VR for this attribute.

Doc#: 200-53659
Rev: A
M: Matching keys for (automatic) Worklist Update. A "S" indicates that Optovue DICOM Module will supply
an attribute value for Single Value Matching. It can be configured if “Scheduled Station AE Title” is
additionally supplied “(S)” and if Modality is configured.
R: Return keys. An "x" will indicate that Optovue DICOM Module will supply this attribute as Return Key
with zero length for Universal Matching. The Optovue DICOM Module will support retired date format
(yyyy.mm.dd) for "Patient’s Birth Date" and "Scheduled Procedure Step Start Date" in the response
identifiers. For "Scheduled Procedure Step Start Time" also retired time format as well as unspecified
time components are supported.
Q: Interactive Query Key. An “x” " will indicate that Optovue DICOM Module will supply this attribute as
matching key, if entered in the Modality Worklist Query dialog. For example, the Patient Name can be
entered thereby restricting worklist responses to Procedure Steps scheduled for the patient.
D: Displayed keys. An “x” indicates that this worklist attribute is displayed to the user in the modality
worklist spreadsheet or in the patient dialog.
IOD: An "x" indicates that this Worklist attribute is included into all Object Instances created during
performance of the related Procedure Step.
4.3.3.8 ASSOCIATED REAL WORLD ACTIVITY FOR STORE IMAGES
After exporting an image from the software, the converted DICOM image object is sent to the DICOM Storage SCP.
4.3.3.9 PRESENTATION CONTEXTS FOR STORAGE
Table 4-4 Presentation Contexts for Storage
PRESENTATION CONTEXTS FOR STORAGE

Extended
Role Negotiation

Ophthalmic Tomography Image
1.2.840.10008.5.1.4.1.1.77.1.5.4 SCU None
Storage

Doc#: 200-53659
Rev: A
Ophthalmic Photography 8 Bit

Image Storage
1.2.840.10008.5.1.4.1.1.77.1.5.1 SCU None
(for IR, SLO En Face and
fundus images)

Secondary Capture Image
1.2.840.10008.5.1.4.1.1.7 SCU None
Storage

Encapsulated PDF Storage 1.2.840.10008.5.1.4.1.1.104.1 SCU None
4.4 NETWORK INTERFACES
The Optovue DICOM Module provides DICOM TCP/IP support as defined by PS 3.8.
4.4.1 PHYSICAL NETWORK INTERFACES
The Optovue DICOM Module inherits TCP/IP support from the operating system. Therefore, whichever interfaces are
supported by the operating system may be used.
4.4.2 ADDITIONAL PROTOCOLS
No additional protocols are used.
4.5 CONFIGURATION
4.5.1 AE TITLE/PRESENTATION ADDRESS MAPPING
The Optovue DICOM Module configuration application supports entry of the Application Entity Title for the Optovue
DICOM Module as a Modality Worklist SCU and as a C-Store SCU.
The Optovue DICOM Module configuration application also supports entry of the Application Entity Title, host name or
address, and port for the communication with a Modality Worklist SCP and with a C-Store SCP.
4.5.2 PARAMETERS

Doc#: 200-53659
Rev: A
Refer to the Optovue DICOM Module user manual for the configuration application for a complete description of
configuration options.

Doc#: 200-53659
Rev: A
5 MEDIA INTERCHANGE
No media interchange is supported.
6 SUPPORT OF CHARACTER SETS
The Optovue DICOM Module supports the following character set in generated DICOM files:
ISO_IR 192 - UTF-8 Encoded Unicode
7 SECURITY
The Optovue DICOM Module does not provide any specific security measures. It is assumed that the DICOM Module will
be used within a secure network that has appropriate security policies and safeguards. These safeguards include firewall,
intrusion detection, and anti-virus software.

Doc#: 200-53659
Rev: A
8 ANNEXES
8.1 IOD CONTENTS
8.1.1 CREATED SOP INSTANCES

The following abbreviations are used in the “Presence of Value” column in the IOD attribute tables:
VNAP Value Not Always Present (attribute sent zero length if no value is present)
ANAP Attribute Not Always Present
ALWAYS Attribute always present with a value
EMPTY Attribute is sent without a value
The following abbreviations are used in the "Source" column in the IOD attribute tables:
MWL The attribute value source is a Modality Worklist entry
USER The attribute value source is user input
AUTO The attribute value is generated automatically
CONFIG The attribute value source is a configurable parameter
Note: All dates and times are encoded in the local configured calendar and time.
8.1.1.1 OPHTHALMIC PHOTOGRAPHY 8 BIT IMAGE IOD
IE Module Reference Presence of Module
Patient Patient Table 8-1 ALWAYS

Doc#: 200-53659
Rev: A
Study General Study Table 8-2 ALWAYS
Series General Series Table 8-3 ALWAYS
Ophthalmic Photography Series Table 8-4 ALWAYS
Frame of Reference Synchronization Table 8-5 ALWAYS
Equipment General Equipment Table 8-6 ALWAYS
Image General Image Table 8-7 ALWAYS
Image Pixel Table 8-8 ALWAYS
Multi-frame Table 8-9 ALWAYS
Ophthalmic Photography Image Table 8-10 ALWAYS
Ocular Region Imaged Table 8-11 ALWAYS
Ophthalmic Photography Acquisition Table 8-12 ALWAYS

Parameters
Ophthalmic Photographic Parameters Table 8-13 ALWAYS
SOP Common Table 8-14 ALWAYS

Doc#: 200-53659
Rev: A
8.1.1.1.1 MODULE ATTRIBUTES FOR OPHTHALMIC PHOTOGRAPHY 8 BIT IMAGE
Table 8-1 Ophthalmic Photography 8 Bit - Patient Module
Attribute Name Tag VR Value Presence Source

of Value
Patient's Name (0010,0010) PN Patient's full name. ALWAYS MWL/
USER
Patient ID (0010,0020) LO Primary identifier for the patient VNAP MWL/
USER
Issuer of Patient (0010,0021) LO Identifier of the Assigning Authority that issued the VNAP MWL
ID Patient ID.
Patient's Birth (0010,0030) DA Birth date of the patient. ALWAYS MWL/
Date USER
Patient's Sex (0010,0040) CS Sex of the named patient. ALWAYS MWL/
Enumerated Values: USER
M = male
F = female
O = other
Table 8-2 Ophthalmic Photography 8 Bit - General Study Module

of Value
Study Instance (0020,000D) UI Unique identifier for the Study. ALWAYS MWL/
UID AUTO
Study Date (0008,0020) DA Date the Study started. ALWAYS AUTO
Study Time (0008,0030) TM Time the Study started. ALWAYS AUTO
Referring (0008,0090) PN Name of the patient's referring physician. VNAP MWL/
Physician's USER
Name
Study ID (0020,0010) SH User or equipment generated Study identifier. VNAP MWL
Accession (0008,0050) SH A RIS generated number that identifies the order VNAP MWL
Number for the Study.
Table 8-3 Ophthalmic Photography 8 Bit - General Series Module

Doc#: 200-53659
Rev: A
Attribute Name Tag VR Description Presence Source

of Value
Modality (0008,0060) CS Type of equipment that originally acquired the data ALWAYS AUTO
used to create the images in this Series.
Value: OP
Series Instance (0020,000E) UI Unique identifier of the Series. ALWAYS AUTO
UID
Series Number (0020,0011) IS A number that identifies this Series. ALWAYS AUTO
Value: 2 (for OP)

Series Date (0008,0021) DA Date the Series started. ALWAYS AUTO
Series Time (0008,0031) TM Time the Series started. ALWAYS AUTO
Series (0008,103E) LO Description of the series. ALWAYS AUTO
Description This tag value provides the scan type name.
Performed (0040,0244) DA Date on which the Performed Procedure Step ANAP AUTO
Procedure Step started.
Start Date
Performed (0040,0245) TM Time on which the Performed Procedure Step ANAP AUTO
Start Time
Performed (0040,0253) SH User or equipment generated identifier of that part ANAP MWL
Procedure Step of a Procedure that has been carried out within this
ID step.
Performed (0040,0254) LO Institution-generated description or classification of ANAP AUTO
Procedure Step the Procedure Step that was performed.
Description
Operator’s Name (0008,1070) PN Name(s) of the operator(s) supporting the Series. VNAP USER
Table 8-4 Ophthalmic Photography 8 Bit - Ophthalmic Photography Series Module

of Value
Modality (0008,0060) CS Source equipment that produced the Ophthalmic ALWAYS AUTO
Photography Series.
Value: OP
Table 8-5 Ophthalmic Photography 8 Bit - Synchronization Module

of Value
Synchronization (0020,0200) UI UID of common synchronization environment. ALWAYS AUTO
Frame of
Reference UID

Doc#: 200-53659
Rev: A

of Value
Synchronization (0018,106A) CS Data acquisition synchronization with external ALWAYS AUTO
Trigger 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.
Value: NO TRIGGER
Acquisition Time (0018,1800) CS Acquisition DateTime (0008, 002A) synchronized ALWAYS AUTO
Synchronized with external time reference.
Enumerated Values: “Y”, “N”.
Value: N
Table 8-6 Ophthalmic Photography 8 Bit - General Equipment Module

of Value
Manufacturer (0008,0070) LO Manufacturer of the equipment that produced the ALWAYS AUTO
composite instances.
Value: Optovue
Institution Name (0008,0080) LO Institution where the equipment that produced the VNAP USER
composite instances is located.
Manufacturer's (0008,1090) LO Manufacturer's model name of the equipment that ALWAYS AUTO
Model Name produced the composite instances.
Value: XR, IVUE, or ICAM
Device Serial (0018,1000) LO Manufacturer's serial number of the equipment that ALWAYS AUTO
Number produced the composite instances.
Software (0018,1020) LO Manufacturer's designation of software version of ALWAYS AUTO
Versions the equipment that produced the composite
instances.
Table 8-7 Ophthalmic Photography 8 Bit - General Image Module

Doc#: 200-53659
Rev: A

of Value
Instance Number (0020,0013) IS A number that identifies this image. ALWAYS AUTO
Value: 1
Patient (0020,0020) CS Patient direction of the rows and columns of the ALWAYS AUTO
Orientation image.
Table 8-8 Ophthalmic Photography 8 Bit - Image Pixel Module

of Value
Samples per (0028,0002) US Number of samples (planes) in this image. ALWAYS AUTO
Pixel Enumerated Values: 1 = grayscale, 3 = RGB.
Value:
For XR and iCam: 3
For iVue: 1
Photometric (0028,0004) CS Specifies the intended interpretation of the pixel ALWAYS AUTO
Interpretation data.
Value:
For XR and iCam: RGB
For iVue: MONOCHROME2
Rows (0028,0010) US Number of rows in the image. ALWAYS AUTO
Columns (0028,0011) US Number of columns in the image. ALWAYS AUTO
Bits Allocated (0028,0100) US Number of bits allocated for each pixel sample. ALWAYS AUTO
Each sample shall have the same number of bits
allocated.
Enumerated Values: 8, 16
Value: 8
Bits Stored (0028,0101) US Number of bits stored for each pixel sample. Each ALWAYS AUTO
sample shall have the same number of bits stored.
Enumerated Values: 8, 12, 16
Value: 8
High Bit (0028,0102) US Most significant bit for pixel sample data. Each ALWAYS AUTO
sample shall have the same high bit.
High Bit (0028, 0102) shall be one less than Bits
Stored (0028, 0101).
Value: 7

Doc#: 200-53659
Rev: A

of Value
Pixel (0028,0103) US Data representation of the pixel samples. Each ALWAYS AUTO
Representation sample shall have the same pixel representation.
Enumerated Values:
“0” = unsigned integer;
“1” = 2's complement.
Value: 0
Planar (0028,0006) US Indicates whether the pixel data are sent color-by- ANAP AUTO
Configuration plane or color-by-pixel. Required if Samples per
Pixel (0028,0002) has a value greater than 1. It
shall not be present otherwise.
Enumerated Values:
0 = The sample values for the first pixel are
followed by the sample values for the second pixel,
etc. For RGB images, this means the order of the
pixel values sent shall be R1, G1, B1, R2, G2,
B2, ..., etc.
1 = Each color plane shall be sent contiguously.
For RGB images, this means the order of the pixel
values sent is R1, R2, R3, ..., G1, G2, G3, ..., B1,
B2, B3, etc.
This tag is absent if Samples per Pixel is not 3.
Value: 0
Pixel Data (7FE0,0010) OW A data stream of the pixel samples that comprise ALWAYS AUTO
the Image.
The order of pixels sent for each image plane is left
to right, top to bottom, i.e., the upper left pixel
(labeled 1,1) is sent first followed by the remainder
of row 1, followed by the first pixel of row 2 (labeled
2,1) then the remainder of row 2 and so on.
Table 8-9 Ophthalmic Photography 8 Bit - Multi Frame Module

of Value
Number of (0028,0008) IS Number of frames in a Multi-frame Image. ALWAYS AUTO
Frames
Value: 1
Frame Increment (0028,0009) AT Contains the Data Element Tag of the attribute that ALWAYS AUTO
Pointer is used as the frame increment in Multi-frame pixel
data.
Value: (0018, 1063) for Frame Time
Frame Time (0018,1063) DS Nominal time (in msec) per individual frame. ALWAYS AUTO

Doc#: 200-53659
Rev: A
Table 8-10 Ophthalmic Photography 8 Bit - Ophthalmic Photography Image Module

of Value
Image Type (0008,0008) CS Image identification characteristics. ALWAYS AUTO
Value: ORIGINAL\PRIMARY\\<Scan Type>

Where “Scan Type” is the name of the scan type.
Value: 1
Pixel Enumerated Values:
1 = grayscale,
3 = RGB.
Value:
For XR and iCam: 3
For iVue: 1
Value:
For XR and iCam: RGB
For iVue: MONOCHROME2
Pixel (0028,0103) US Data representation of the pixel samples. ALWAYS AUTO
Representation Enumerated Values:
0000H = unsigned integer.
0001H = 2's complement
Value: 0
Content Time (0008,0033) TM The time the image pixel data creation started. ALWAYS AUTO
Content Date (0008,0023) DA The date the image pixel data creation started. ALWAYS AUTO
Acquisition (0008,002A) DT The date and time that the acquisition of data ALWAYS AUTO
DateTime started.
Lossy Image (0028,2110) CS Specifies whether an Image has undergone lossy ALWAYS AUTO
Compression compression (at a point in its lifetime).
Enumerated Values:
“00” = Image has NOT been subjected to lossy
compression.
“01” = Image has been subjected to lossy
compression.
Value: 00

Doc#: 200-53659
Rev: A

of Value
Burned In (0028,0301) CS Indicates whether image contains sufficient burned ALWAYS AUTO
Annotation in annotation to identify the patient and date the
image was acquired. Identification of patient and
date as text in an encapsulated document (e.g., in
an XML attribute or element) is equivalent to
"burned in annotation".
Enumerated Values: “YES”, “NO”.
Value: NO
Table 8-11 Ophthalmic Photography 8 Bit - Ocular Region Imaged Module

of Value
Image Laterality (0020,0062) CS Laterality of object imaged (as described in ALWAYS AUTO
Anatomic Region Sequence (0008, 2218))
examined.
Enumerated Values:
“R” = right eye
“L” = left eye
“B” = both left and right eye
Anatomic Region (0008,2218) SQ Sequence that identifies the anatomic region of ALWAYS AUTO
Sequence interest in this frame (i.e. external anatomy, surface
anatomy, or general region of the body). Only a
single Item shall be permitted in this Sequence.
> Code Value (0008,0100) SH An identifier that is unambiguous within the Coding ALWAYS AUTO
Scheme denoted by Coding Scheme Designator
(0008, 0102) and Coding Scheme Version (0008,
0103).
Value: “T-AA610” for Retina

“T-AA630” for Optic nerve head
> Coding (0008,0102) SH Identifies the coding scheme in which the code for ALWAYS AUTO
Scheme a term is defined.
Designator
Value: “SRT”
> Code Meaning (0008,0104) LO Text that has meaning to a human and conveys the ALWAYS AUTO
meaning of the term defined by the combination of
Code Value and Coding Scheme Designator.
Value: “Retina”, “Optic nerve head”
Table 8-12 Ophthalmic Photography 8 Bit - Ophthalmic Photography Acquisition Parameters Module

Doc#: 200-53659
Rev: A

of Value
Horizontal Field (0022,000C) FL The horizontal field of view in degrees. EMPTY AUTO
of View
Patient Eye (0022,0005) CS Enumerated Values: “YES”, “NO”. EMPTY AUTO
Movement
Commanded
Refractive State (0022,001B) SQ The refractive state of the imaged eye at the time EMPTY AUTO
Sequence of acquisition.
Zero or one Item shall be included in this
Sequence. Zero length means the refractive state
was not measured.
Emmetropic (0022,000A) FL Emmetropic magnification value (dimensionless). EMPTY AUTO
Magnification Zero length means the emmetropic magnification
was not measured.
Intra Ocular (0022,000B) FL Value of intraocular pressure in mmHg. EMPTY AUTO
Pressure Zero length means the pressure was not measured
Pupil Dilated (0022,000D) CS Whether or not the patient's pupils were EMPTY AUTO
pharmacologically dilated for this acquisition.
Enumerated Values: “YES”, “NO”. If this tag is
empty, no information is available.
Table 8-13 Ophthalmic Photography 8 Bit - Ophthalmic Photographic Parameters Module

of Value
Acquisition (0022,0015) SQ Describes the type of acquisition device. ALWAYS AUTO
Device Type Only a single Item shall be included in this
Code Sequence Sequence.
0103).
Value:
For XR and iVue: A-00EBA
For Fundus on iCam: R-1021A
Designator
Value: “SRT”

Doc#: 200-53659
Rev: A

of Value
Value:
For XR and iVue: “Scanning Laser
Ophthalmoscope”
For Fundus on iCam: “Fundus Camera”

Illumination Type (0022,0016) SQ Coded value for illumination. EMPTY AUTO
Code Sequence Zero or one Item shall be included in this
Sequence.
Light Path Filter (0022,0017) SQ Filters used in the light source path. VNAP AUTO
Type Stack Code Zero or more Items shall be included in this
Sequence Sequence.
> Code Value (0008,0100) SH An identifier that is unambiguous within the Coding ANAP AUTO
0103).
Value:
For XR: A-010DC
For iVue and iCam: N/A (Sequence is empty)

> Coding (0008,0102) SH Identifies the coding scheme in which the code for ANAP AUTO
Designator
Value:
For XR: “SRT”

> Code Meaning (0008,0104) LO Text that has meaning to a human and conveys the ANAP AUTO
Value:
For XR: “Infrared optical filter”

Image Path Filter (0022,0018) SQ Describes stack of filters used in image path. VNAP AUTO
Sequence Sequence.

Doc#: 200-53659
Rev: A

of Value
0103).
Value:
For XR: R-102BE

Designator
Value:
For XR: “SRT”

Value:
For XR: “Infrared”

Lenses Code (0022,0019) SQ Lenses that were used during the image VNAP AUTO
Sequence acquisition.
Zero or more Items shall be included in this
Sequence.
0103).
Value: For XR: R-10210
For iVue and iCam: N/A (Sequence is empty.)

Designator
Value: For XR: SRT

Value: For XR: “Indirect ophthalmoscopy lens”

Doc#: 200-53659
Rev: A

of Value
Detector Type (0018,7004) CS Type of detector used for creating this image. ALWAYS AUTO
Value:
XR and iVue: CCD = Charge Coupled Device
iCam1 (image 2560x1280): CCD = Charge

Coupled Device
iCam2 (image 2592x1944): CMOS =

Complementary Metal Oxide Semiconductor
Table 8-14 Ophthalmic Photography 8 Bit - SOP Common Module

of Value
SOP Class UID (0008,0016) UI Uniquely identifies the SOP Class. ALWAYS AUTO
Value: 1.2.840.10008.5.1.4.1.1.77.1.5.1
SOP Instance (0008,0018) UI Uniquely identifies the SOP Instance. ALWAYS AUTO
UID
Specific (0008,0005) CS Character Set that expands or replaces the Basic ALWAYS AUTO
Character Set Graphic Set. Required if an expanded or
replacement character set is used.
Value: ISO_IR_192 for UTF-8 encoded Unicode
8.1.1.2 OPHTHALMIC TOMOGRAPHY IMAGE IOD

Doc#: 200-53659
Rev: A
Ophthalmic Tomography Series Table 8-18 ALWAYS
Frame of Reference Frame of Reference Table 8-19 ALWAYS
Synchronization Table 8-20 ALWAYS
Enhanced General Equipment Table 8-22 ALWAYS
Image Image Pixel Table 8-23 ALWAYS
Multi-frame Functional Groups Table 8-24 ALWAYS
Multi-frame Dimension Table 8-25 ALWAYS
Acquisition Context Table 8-26 ALWAYS
Ophthalmic Tomography Image Table 8-27 ALWAYS
Ophthalmic Tomography Acquisition Table 8-28 ALWAYS

Parameters
Ophthalmic Tomography Parameters Table 8-29 ALWAYS
Ocular Region Imaged Table 8-30 ALWAYS

Doc#: 200-53659
Rev: A
8.1.1.2.1 MODULE ATTRIBUTES FOR OPHTHALMIC TOMOGRAPHY IMAGE
Table 8-15 Ophthalmic Tomography Image - Patient Module

of Value
USER
USER
ID Patient ID.
Date USER
USER
Enumerated Values:
M = male
F = female
O = other
Table 8-16 Ophthalmic Tomography Image - General Study Module

of Value
UID AUTO
Physician's Name USER

Doc#: 200-53659
Rev: A
Table 8-17 Ophthalmic Tomography Image - General Series Module

of Value
Value: OPT
UID
Value: 1
Description This tag value provides the scan type name.
Performed (0040,0244) DA Date on which the Performed Procedure Step ANAP AUTO
Start Date
Performed (0040,0245) TM Time on which the Performed Procedure Step ANAP AUTO
Start Time
Performed (0040,0253) SH User or equipment generated identifier of that part ANAP MWL
Procedure Step of a Procedure that has been carried out within this
ID step.
Performed (0040,0254) LO Institution-generated description or classification of ANAP AUTO
Procedure Step the Procedure Step that was performed.
Description
Table 8-18 Ophthalmic Tomography Image - Ophthalmic Tomography Series Module

of Value
Value: OPT
Value: 1
Table 8-19 Ophthalmic Tomography Image - Frame of Reference Module

Doc#: 200-53659
Rev: A

of Value
Frame of (0020,0052) UI Uniquely identifies the frame of reference for a ALWAYS AUTO
Reference UID Series. See NEMA PS 3.3 Section C.7.4.1.1.1 for
further explanation.
For an OPT image, the frame of reference UID
identifies the associated OP image.
Position (0020,1040) LO Part of the imaging target used as a reference. See EMPTY AUTO
Reference NEMA PS 3.3 Section C.7.4.1.1.2 for further
Indicator explanation.
Table 8-20 Ophthalmic Tomography Image - Synchronization Module

of Value
Synchronization (0020,0200) UI UID of common synchronization environment. ALWAYS AUTO
Frame of
Reference UID
Synchronization (0018,106A) CS Data acquisition synchronization with external ALWAYS AUTO
Trigger equipment
Value: NO TRIGGER
Acquisition Time (0018,1800) CS Acquisition DateTime (0008, 002A) synchronized ALWAYS AUTO
Synchronized with external time reference.
Value: N
Table 8-21 Ophthalmic Tomography Image - General Equipment Module

of Value
Value: “Optovue”
Value: “XR”, “IVUE”, or “ICAM”
instances.
Table 8-22 Ophthalmic Tomography Image - Enhanced General Equipment Module

Doc#: 200-53659
Rev: A

of Value
Value: “Optovue”
Value: “XR”, “IVUE”, or “ICAM”
instances.
Table 8-23 Ophthalmic Tomography Image - Image Pixel Module

of Value
Value: 1
Value: MONOCHROME2

allocated.
Value: 16
Value: 12
Stored (0028, 0101).
Value: 11

Doc#: 200-53659
Rev: A

of Value
Enumerated Values:
Value: 0
the Image.
Table 8-24 Ophthalmic Tomography Image - Multi Frame Functional Groups Module

of Value
Shared (5200,9229) SQ Sequence that contains the Functional Group ALWAYS AUTO
Functional Macros that are shared for all frames in this SOP
Groups Instance and Concatenation.
Sequence
Only a single Item shall be included in this
Sequence. The Item may be empty if the
requirements for inclusion of the Functional Groups
are not satisfied.
> Pixel Measures (0028,9110) SQ Identifies the physical characteristics of the pixels ALWAYS AUTO
Sequence of this frame.
sequence.
>> Pixel Spacing (0028,0030) DS Physical distance in the imaging target patient ALWAYS AUTO
between the centers of each pixel, specified by a
numeric pair - adjacent row spacing (delimiter)
adjacent column spacing in mm.
>> Slice (0018,0050) DS Nominal reconstructed slice thickness for ALWAYS AUTO
Thickness tomographic imaging in mm.
> Referenced (0008,1140) SQ The set of images or other composite SOP ALWAYS AUTO
Image Sequence Instances used to plan the acquisition, if any, and
other significant related images.
Sequence.
>> Referenced (0008,1150) UI Uniquely identifies the referenced SOP Class. ALWAYS AUTO
SOP Class UID For an OPT image, the referenced SOP Class is
OP 8 Bit Image Storage.
Value: 1.2.840.10008.5.1.4.1.1.77.1.5.1
>> Referenced (0008,1155) UI Uniquely identifies the referenced SOP Instance. ALWAYS AUTO
SOP Instance This is the UID of the referenced OP image.
UID

Doc#: 200-53659
Rev: A

of Value
>> Purpose of (0040,A170) SQ Describes the purpose for which the reference is ALWAYS AUTO
Reference Code made.
Sequence Only a single Item shall be included in this
sequence.
>>> Code Value (0008,0100) SH An identifier that is unambiguous within the Coding ALWAYS AUTO
0103).
Value: 121311
>>> Coding (0008,0102) SH Identifies the coding scheme in which the code for ALWAYS AUTO
Designator
Value: “DCM”
>>> Code (0008,0104) LO Text that has meaning to a human and conveys the ALWAYS AUTO
Meaning meaning of the term defined by the combination of
Value: “Localizer”
> Frame (0020,9071) SQ Identifies anatomic characteristics of this frame. ALWAYS AUTO
Anatomy Only a single Item shall be included in this
Sequence sequence.
>> Anatomic (0008,2218) SQ Sequence that identifies the anatomic region of ALWAYS AUTO
Region interest in this Instance (i.e., external anatomy,
Sequence surface anatomy, or general region of the body).
sequence.
>>> Code Value (0008,0100) SH An identifier that is unambiguous within the Coding ALWAYS AUTO
0103).

>>> Coding (0008,0102) SH Identifies the coding scheme in which the code for ALWAYS AUTO
Designator
Value: “SRT”
>>> Code (0008,0104) LO Text that has meaning to a human and conveys the ALWAYS AUTO
Meaning meaning of the term defined by the combination of

Doc#: 200-53659
Rev: A

of Value
>> Frame (0020,9072) CS Laterality of (possibly paired) body parts (as ALWAYS AUTO
Laterality described in Anatomic Region Sequence (0008,
2218)) examined.
Enumerated Values:
“R” = right
“L” = left
“U” = unpaired
“B” = both left and right
Per-frame (5200,9230) SQ Sequence that contains the Functional Group ALWAYS AUTO
Functional Sequence Attributes corresponding to each frame
Groups of the Multi-frame Image. The first Item
Sequence corresponds with the first frame, and so on.
One or more Items shall be included in this

Sequence. The number of Items shall be the same
as the number of frames.
> Frame Content (0020,9111) SQ Identifies general characteristics of this frame. ALWAYS AUTO
Sequence Only a single Item shall be permitted in this
sequence
>> Frame (0018,9151) DT The point in time that is most representative of ALWAYS AUTO
Reference when data was acquired for this frame.
Datetime
>> Frame (0018,9074) DT The date and time that the acquisition of data that ALWAYS AUTO
Acquisition resulted in this frame started.
Datetime
>> Frame (0018,9220) FD The actual amount of time [in milliseconds] that ALWAYS AUTO
Acquisition was used to acquire data for this frame.
Duration
>> Stack ID (0020,9056) SH Identification of a group of frames, with different ALWAYS AUTO
positions and/or orientations that belong together,
within a dimension organization.
>> In-Stack (0020,9057) UL The ordinal number of a frame in a group of ALWAYS AUTO
Position Number frames, with the same Stack ID Required if Stack
ID (0020, 9056) is present.
>> Dimension (0020,9157) UL Contains the values of the indices defined in the ALWAYS AUTO
Index Values Dimension Index Sequence (0020,9222) for this
multi-frame header frame. The number of values is
equal to the number of Items of the Dimension
Index Sequence and shall be applied in the same
order. See NEMA PS 3.3 Section C.7.6.17.1 for a
description. Required if the value of the Dimension
Index Sequence (0020,9222) contains Items.
> Plane Position (0020,9113) SQ Identifies the position of the plane of this frame. ALWAYS AUTO
Sequence Only a single Item shall be permitted in this
sequence.
>> Image (0020,0032) DS The x, y, and z coordinates of the upper left hand ALWAYS AUTO
Position (Patient) corner (center of the first voxel transmitted) of the
frame, in mm.

Doc#: 200-53659
Rev: A

of Value
> Plane (0020,9116) SQ Identifies orientation of the plane of this frame. ALWAYS AUTO
Orientation Only a single Item shall be included in this
Sequence sequence.
>> Image (0020,0037) DS The direction cosines of the first row and the first ALWAYS AUTO
Orientation column with respect to the patient.
(Patient)
Required if Frame Type (0008,9007) Value 1 of this
frame is ORIGINAL and Volumetric Properties
(0008,9206) of this frame is other than
DISTORTED. May be present otherwise.
Additional constraints apply:
The row and column direction cosine vectors shall

be orthogonal, i.e., their dot product shall be zero.
The row and column direction cosine vectors shall

be normal, i.e., the dot product of each direction
cosine vector with itself shall be unity.
> Ophthalmic (0022,0031) SQ Specifies the column locations for this frame in ALWAYS AUTO
Frame Location terms of locations on a referenced image. The
Sequence referenced image is an OP 8 Bit Image.
>> Referenced (0008,1150) UI Uniquely identifies the referenced SOP Class. ALWAYS AUTO
SOP Class UID
Value: 1.2.840.10008.5.1.4.1.1.77.1.5.1 for OP 8
Bit Image
>> Referenced (0008,1155) UI Uniquely identifies the referenced SOP Instance. ALWAYS AUTO
SOP Instance
UID
>> Reference (0022,0032) FL Image coordinates for the points on the referenced ALWAYS AUTO
Coordinates OP image that correspond to the points on this
frame.
>> Ophthalmic (0022,0039) CS Enumerated Values: ALWAYS AUTO
Image LINEAR
Orientation NONLINEAR
TRANSVERSE
Value: “LINEAR”
Instance Number (0020,0013) IS A number that identifies this instance. The value ALWAYS AUTO
shall be the same for all SOP Instances of a
Concatenation, and different for each separate
Concatenation and for each SOP Instance not
within a Concatenation in a series.
Content Date (0008,0023) DA The date the data creation was started. ALWAYS AUTO
Content Time (0008,0033) TM The time the data creation was started. ALWAYS AUTO
Number of (0028,0008) IS Number of frames in a multi-frame image. ALWAYS AUTO
Frames

Doc#: 200-53659
Rev: A
Table 8-25 Ophthalmic Tomography Image - Multi Frame Dimension Module

of Value
Dimension (0020,9221) SQ Sequence that lists the Dimension Organization ALWAYS AUTO
Organization UIDs referenced by the containing SOP Instance.
Sequence
Sequence.
> Dimension (0020,9164) UI Uniquely identifies a set of dimensions referenced ALWAYS AUTO
Organization UID within the containing SOP Instance.
Dimension Index (0020,9222) SQ Identifies the sequence containing the indices used ALWAYS AUTO
Sequence to specify the dimension of the multi-frame object.

sequence.
> Item1
> Dimension (0020,9165) AT Contains the Data Element Tag that is used to ALWAYS AUTO
Index Pointer identify the Attribute connected with the index.
The first index is the Stack ID.
Value: (0020,9056) for Stack ID

> Functional (0020,9167) AT Contains the Data Element Tag of the Functional ALWAYS AUTO
Group Pointer Group Sequence that contains the Attribute
referenced by the Dimension Index Pointer.
Value: (0020,9111) for Frame Content Sequence

> Item2
> Dimension (0020,9165) AT Contains the Data Element Tag that is used to ALWAYS AUTO
Index Pointer identify the Attribute connected with the index.
The second index is the In-Stack Position Number.
Value: (0020,9057) for In-Stack Position Number

> Functional (0020,9167) AT Contains the Data Element Tag of the Functional ALWAYS AUTO
Group Pointer Group Sequence that contains the Attribute
referenced by the Dimension Index Pointer.
Value: (0020,9111) for Frame Content Sequence
Table 8-26 Ophthalmic Tomography Image - Acquisition Context Module

of Value
Acquisition (0040,0555) SQ A sequence of Items that describes the conditions EMPTY AUTO
Context present during the acquisition of the data of the
Sequence SOP Instance.

Doc#: 200-53659
Rev: A

of Value
Sequence.
Table 8-27 Ophthalmic Tomography Image - Ophthalmic Tomography Image Module

of Value
Image Type (0008,0008) CS Image identification characteristics. ALWAYS AUTO
Value: ORIGINAL\PRIMARY\\<Scan Type>.

Where Scan Type is the name of the scan type for
the image.
Samples Per (0028,0002) US Number of samples (planes) in this image. ALWAYS AUTO
Value: 1
Acquisition (0008,002A) DT The date and time that the acquisition of data ALWAYS AUTO
DateTime started.
Acquisition (0018,9073) FD The scan time in seconds used to create all frames ALWAYS AUTO
Duration of an Ophthalmic Tomography image.
Acquisition (0020,0012) IS A number identifying the single continuous ALWAYS AUTO
Number gathering of data over a period of time that resulted
in this image.
Value: MONOCHROME2
Pixel (0028,0103) US Data representation of pixel samples. ALWAYS AUTO

Representation Enumerated Values:
0000H = unsigned integer.
0001H = 2's complement
Value: 0
allocated.
Value: 16
Value: 12

Doc#: 200-53659
Rev: A

of Value
Stored (0028, 0101).
Value: 11
Presentation LUT (2050,0020) CS Specifies an identity transformation for the ALWAYS AUTO
Shape 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” if Photometric

Interpretation is MONOCHROME2 images, not
present for RGB.
Value: IDENTITY
Lossy Image (0028,2110) CS Specifies whether an Image has undergone lossy ALWAYS AUTO
Compression compression (at a point in its lifetime).
Enumerated Values:
00 = Image has NOT been subjected to lossy
compression;
01 = Image has been subjected to lossy
compression.
Value: 00
Burned In (0028,0301) CS Indicates whether or not image contains sufficient ALWAYS AUTO
Annotation burned in annotation to identify the patient and date
the image was acquired. Identification of patient
and date as text in an encapsulated document
(e.g., in an XML attribute or element) is equivalent
to "burned in annotation".
Enumerated Values: “YES”, “NO”.
Value: NO
Concatenation (0020,9161) UI Identifier of all SOP Instances that belong to the ALWAYS AUTO
UID same concatenation.
SOP Instance (0020,0242) UI The SOP Instance UID of the single composite ALWAYS AUTO
UID of SOP Instance of which the Concatenation is a part.
Concatenation All SOP Instances of a concatenation shall use the
Source same value for this attribute. Required if
Concatenation UID (0020, 9161) is present.
Concatenation (0020,9228) UL Offset of the first frame in a multi-frame image of a ALWAYS AUTO
Frame Offset concatenation. Required if Concatenation UID
Number (0020, 9161) is present.
Value: 0
In-concatenation (0020,9162) US Identifier for one SOP Instance belonging to a ALWAYS AUTO
Number concatenation. Required if Concatenation UID
(0020, 9161) is present.

Doc#: 200-53659
Rev: A

of Value
Value: 1
In-concatenation (0020,9163) US The number of SOP Instances sharing the same ALWAYS AUTO
Total Number Concatenation UID (0020, 9161). Required if
Concatenation UID (0020, 9161) is present.
Value: 1
Table 8-28 Ophthalmic Tomography Image - Ophthalmic Tomography Acquisition Parameters Module

of Value
Axial Length of (0022,0030) FL Axial length of the eye in mm. EMPTY AUTO
the Eye
Horizontal Field (0022,000C) FL The horizontal field of view in degrees. EMPTY AUTO
of View
Refractive State (0022,001B) SQ The refractive state of the imaged eye at the time EMPTY AUTO
Sequence of acquisition.
Zero or one Item shall be included in this
Sequence. Zero length means the refractive state
was not measured.
Emmetropic (0022,000A) FL Emmetropic magnification value (dimensionless). EMPTY AUTO
Magnification Zero length means the emmetropic magnification
was not measured.
Intra Ocular (0022,000B) FL Value of intraocular pressure in mmHg. Zero length EMPTY AUTO
Pressure means the pressure was not measured.
Pupil Dilated (0022,000D) CS Whether or not the patient's pupils were EMPTY AUTO
pharmacologically dilated for this acquisition.
Enumerated Values: “YES”, “NO”. If this tag is
empty, no information is available.
Table 8-29 Ophthalmic Tomography Image - Ophthalmic Tomography Parameters Module

of Value
Acquisition (0022,0015) SQ Describes the type of acquisition device. ALWAYS AUTO
Device Type Only a single Item shall be included in this
Code Sequence Sequence.
0103).

Doc#: 200-53659
Rev: A

of Value
Value: A-00FBE
Designator
Value : “SRT”
Value: “Optical Coherence Tomography Scanner”

Light Path Filter (0022,0017) SQ Filters used in the light source path. EMPTY AUTO
Sequence Sequence.
Detector Type (0018,7004) CS Type of detector used for creating this image. ALWAYS AUTO
Value: “CCD” for Charge Coupled Device
Illumination (0022,0055) FL Wavelength of the illuminator in nm. ALWAYS AUTO

Wave Length
Illumination (0022,0056) FL Power of the illuminator in microwatts at corneal ALWAYS AUTO
Power plane.
Illumination (0022,0057) FL Bandwidth of the illuminator in nm. ALWAYS AUTO
Bandwidth
Depth Spatial (0022,0035) FL The inherent limiting resolution in microns for depth ALWAYS AUTO
Resolution of the acquisition equipment for high contrast
objects for the data gathering and reconstruction
technique chosen. If variable, the value at the
center of the scanning volume.
Maximum Depth (0022,0036) FL Maximum distortion in depth direction in % of ALWAYS AUTO
Distortion Depth Spatial Resolution.
Along-scan (0022,0037) FL The inherent limiting resolution in microns of the ALWAYS AUTO
Spatial acquisition equipment in the direction of a row.
Resolution
Maximum Along- (0022,0038) FL Maximum distortion in along-scan direction in % of ALWAYS AUTO
scan Distortion Along-scan Spatial Resolution.
Across-scan (0022,0048) FL The inherent limiting resolution in microns of the ALWAYS AUTO
Spatial acquisition equipment perpendicular to the slice.
Resolution
Maximum (0022,0049) FL Maximum distortion in across-scan direction in % of ALWAYS AUTO
Across-scan cross-scan Spatial Resolution.
Distortion
Table 8-30 Ophthalmic Tomography Image - Ocular Region Imaged Module

Doc#: 200-53659
Rev: A

of Value
Image Laterality (0020,0062) CS Laterality of object imaged (as described in ALWAYS AUTO
Anatomic Region Sequence (0008, 2218))
examined.
Enumerated Values:
“R” = right eye
“L” = left eye
“B” = both left and right eye
Anatomic Region (0008,2218) SQ Sequence that identifies the anatomic region of ALWAYS AUTO
Sequence interest in this frame (i.e. external anatomy, surface
anatomy, or general region of the body). Only a
single Item shall be permitted in this Sequence.
0103).

Designator
Value: “SRT”
Table 8-31 Ophthalmic Tomography Image - SOP Common Module

of Value
Value: 1.2.840.10008.5.1.4.1.1.77.1.5.4
UID

Doc#: 200-53659
Rev: A
8.1.1.3 ENCAPSULATED PDF IOD
Series Encapsulated Document Series Table 8-34 ALWAYS
SC Equipment Table 8-36 ALWAYS
Encapsulated Encapsulated Document Table 8-37 ALWAYS

Document
8.1.1.3.1 MODULE ATTRIBUTES FOR ENCAPSULATED PDF
Table 8-32 Encapsulated PDF - Patient Module

of Value
USER

Doc#: 200-53659
Rev: A

of Value
USER
ID Patient ID.
Date USER
M = male
F = female
O = other
Table 8-33 Encapsulated PDF - General Study Module

of Value
UID AUTO
Physician's USER
Name
Table 8-34 Encapsulated PDF - Encapsulated Document Series Module

of Value
Value: OT
UID
Value: 3

Doc#: 200-53659
Rev: A

of Value
Description
Value: <Scan Type> report
the image.
Table 8-35 Encapsulated PDF - General Equipment Module

of Value
Value: Optovue
instances.
Table 8-36 Encapsulated PDF - SC Equipment Module

of Value
Conversion Type (0008,0064) CS Describes the kind of image conversion. ALWAYS AUTO
Value: WSD for Workstation
Table 8-37 Encapsulated PDF - Encapsulated Document Module

of Value
Instance Number (0020,0013) IS A number that identifies this SOP Instance. The ALWAYS AUTO
value shall be unique within a series.

Doc#: 200-53659
Rev: A

of Value
Content Date (0008,0023) DA The date the document content creation was ALWAYS AUTO
started.
Content Time (0008,0033) TM The time the document content creation was ALWAYS AUTO
started.
Acquisition (0008,002A) DT The date and time that the original generation of ALWAYS AUTO
DateTime the data in the document started.
Burned In (0028,0301) CS Indicates whether or not the encapsulated ALWAYS CONFIG
Annotation document contains sufficient burned in annotation
to identify the patient and date the data was
acquired.
Enumerated Values:
YES
NO
Document Title (0042,0010) ST The title of the document. ALWAYS AUTO

The value describes the report encapsulated in the
document, e.g. PachymetryWide Change Analysis.
Concept Name (0040,A043) SQ A coded representation of the document title. EMPTY AUTO
Code Sequence Zero or one Item shall be included in this
Sequence.
MIME Type of (0042,0012) LO The type of the encapsulated document stream ALWAYS AUTO
Encapsulated described using the MIME Media Type (see RFC
Document 2046).
Value: “application/pdf”
Encapsulated (0042,0011) OB Encapsulated Document stream containing a ALWAYS AUTO
Document document encoded according to the MIME Type.
Table 8-38 Encapsulated PDF - SOP Common Module

of Value
Value: 1.2.840.10008.5.1.4.1.1.104.1
UID

Doc#: 200-53659
Rev: A
8.1.1.4 SECONDARY CAPTURE IMAGE IOD
SC Equipment Table 8-43 ALWAYS
Image General Image Table 8-44 ALWAYS
Image Pixel Table 8-45 ALWAYS
8.1.1.4.1 MODULE ATTRIBUTES FOR SECONDARY CAPTURE
Table 8-39 Secondary Capture - Patient Module

of Value
USER

Doc#: 200-53659
Rev: A

of Value
USER
ID Patient ID.
Date USER
M = male
F = female
O = other
Table 8-40 Secondary Capture - General Study Module

of Value
UID AUTO
Physician's Name USER
Table 8-41 Secondary Capture - General Series Module

of Value
Value: OT
UID
Value: 4

Doc#: 200-53659
Rev: A

of Value
Description
Value: <Scan Type> report
the image.
Table 8-42 Secondary Capture - General Equipment Module

of Value
Value: Optovue
instances.
Table 8-43 Secondary Capture - SC Equipment Module

of Value
Conversion Type (0008,0064) CS Describes the kind of image conversion. ALWAYS AUTO
Defined Terms :
Value: WSD for Workstation
Table 8-44 Secondary Capture - General Image Module

of Value

Doc#: 200-53659
Rev: A

of Value
Patient (0020,0020) CS Patient direction of the rows and columns of the ALWAYS AUTO
Orientation image. Required if image does not require Image
Orientation (Patient) (0020, 0037) and Image
Position (Patient) (0020, 0032).
Table 8-45 Secondary Capture - Image Pixel Module

of Value
Value: 3
Value: RGB
allocated.
Value: 8
Value: 8
Stored (0028, 0101).
Value: 7
Enumerated Values:
Value: 0

Doc#: 200-53659
Rev: A

of Value
Planar (0028,0006) US Indicates whether the pixel data are sent color-by- ALWAYS AUTO
Configuration plane or color-by-pixel. Required if Samples per
Pixel (0028,0002) has a value greater than 1. It
shall not be present otherwise.
Enumerated Values:
0 = The sample values for the first pixel are
followed by the sample values for the second pixel,
etc. For RGB images, this means the order of the
pixel values sent shall be R1, G1, B1, R2, G2,
B2, ..., etc.
1 = Each color plane shall be sent contiguously.
For RGB images, this means the order of the pixel
values sent is R1, R2, R3, ..., G1, G2, G3, ..., B1,
B2, B3, etc.
This tag is absent if Samples per Pixel is not 3.
Value: 0
the Image.
The order of pixels sent for each image plane is left
to right, top to bottom, i.e., the upper left pixel
(labeled 1,1) is sent first followed by the remainder
of row 1, followed by the first pixel of row 2 (labeled
2,1) then the remainder of row 2 and so on.
Table 8-46 Secondary Capture - SOP Common Module

of Value
Value: 1.2.840.10008.5.1.4.1.1.7
UID
8.1.2 USAGE OF ATTRIBUTES FROM RECEIVED IODS
None

Doc#: 200-53659
Rev: A
8.1.3 ATTRIBUTE MAPPING
Refer to section 4.3.3.7 for information on SOP Specific Conformance for Modality Worklist.
8.1.4 COERCED/MODIFIED FIELDS
Not applicable.
8.2 DATA DICTIONARY OF PRIVATE ATTRIBUTES
Not applicable.
8.3 CODED TERMINOLOGY AND TEMPLATES
Not applicable.
8.4 GRAYSCALE IMAGE CONSISTENCY
Not applicable.
8.5 STANDARD EXTENDED / SPECIALIZED / PRIVATE SOP CLASSES
None.
8.6 PRIVATE TRANSFER SYNTAXES
No Private Transfer Syntaxes are supported.
A. APPENDIX A – Secondary Capture IOD for ODM Conversion Option
The following sections document the IOD conformance for Secondary Capture images generated using the ODM
“Conversion” option supported by the Optovue DICOM Module configuration and service application. The “Conversion”
option is provided for compatibility with previous software versions.
CREATED SOP INSTANCES

The following tables use several abbreviations.

Doc#: 200-53659
Rev: A
The abbreviations used in the “Presence of …” column are:
VNAP Value Not Always Present (attribute sent zero length if no value is present)
ANAP Attribute Not Always Present
ALWAYS Always Present with a value
EMPTY Attribute is sent without a value
The abbreviations used in the “Source” column:
MWL The attribute value source is a Modality Worklist entry

USER The attribute value source is user input
AUTO The attribute value is generated automatically
CONFIG The attribute value source is a configurable parameter
NOTE: All dates and times are encoded in the local configured calendar and time
SECONDARY CAPTURE IOD – ODM CONVERSION OPTION

Patient Patient Patient ALWAYS
Study General Study General Study ALWAYS
Series General Series General Series ALWAYS
Equipment General Equipment General
ALWAYS
Equipment
SC Equipment SC Equipment ALWAYS
Image General Image General Image ALWAYS
Image Pixel Image Pixel ALWAYS
SOP Common SOP Common ALWAYS
PATIENT MODULE

Doc#: 200-53659
Rev: A
Presence of
Attribute Name Tag VR Value Source
Value
Patient’s full name from MWL entry or user MWL/
Patient’s Name (0010,0010) PN ALWAYS
input. USER
Primary identifier for the patient from MWL MWL/
Patient ID (0010,0020) LO VNAP
entry or user input. USER
Identifier of the Assigning Authority that
MWL/
Issuer of Patient ID (0010,0021) LO issued the Patient ID from MWL entry or user ANAP
USER
input.
Birth date of the patient from MWL entry or MWL/
Patient’s Birth Date (0010,0030) DA ALWAYS
user input. USER
Sex of the named patient from MWL entry or MWL/
Patient’s Sex (0010,0040) CS VNAP
user input. USER
Patient Comments (0010,4000) LT Patient comments from Modality Worklist ANAP MWL
GENERAL STUDY MODULE OF CREATED SOP INSTANCES
Presence of
Value
From Modality Worklist or generated by MWL/
Study Instance UID (0020,000D) UI ALWAYS
device AUTO
Study Date (0008,0020) DA Date the Study started ALWAYS AUTO
Study Time (0008,0030) TM Time the Study started <hhmmss> ALWAYS AUTO
Referring Physician’s Name (0008,0090) PN From Modality Worklist VNAP MWL
Requested Procedure ID from Worklist MWL/
Study ID (0020,0010) SH VNAP
or User Input USER
MWL/
Accession Number (0008,0050) SH From Modality Worklist or user input VNAP
USER
Comment text in study list. Maximum
Study Description (0008,1030) LO VNAP USER
1024 characters.
Referenced Study Sequence (0008,1110) SQ From Modality Worklist VNAP MWL
>Referenced SOP Class UID (0008,1150) UI From Modality Worklist VNAP MWL
>Referenced SOP Instance UID (0008,1155) UI From Modality Worklist VNAP MWL

Doc#: 200-53659
Rev: A
GENERAL SERIES MODULE OF CREATED SOP INSTANCES
Attribute Name Tag VR Value Presence of Value Source

Modality (0008,0060) CS OT ALWAYS AUTO
Series Instance UID (0020,000E) UI Generated by device ALWAYS AUTO
Series Number (0020,0011) IS Generated by device ALWAYS AUTO
GENERAL EQUIPMENT MODULE OF CREATED SOP INSTANCES
Presence
of Value
Manufacturer (0008,0070) LO Optovue ALWAYS AUTO
Institution Name (0008,0080) LO From Configuration VNAP CONFIG
Station Name (0008,1010) SH From Configuration ALWAYS CONFIG
Manufacturer’s Model Name (0008,1090) LO From Configuration ALWAYS AUTO
Device Serial Number (0018,1000) LO From Configuration ALWAYS CONFIG
Software Version (0018,1020) LO From Configuration ALWAYS CONFIG
SC EQUIPMENT MODULE OF CREATED SOP INSTANCES
Presence
of Value
Conversion Type (0008,0064) CS WSD ALWAYS AUTO
GENERAL IMAGE MODULE OF CREATED SOP INSTANCES
Presence
of Value
Image Number (0020,0013) IS 1 ALWAYS AUTO

Doc#: 200-53659
Rev: A
IMAGE PIXEL MODULE OF CREATED SOP INSTANCES
Presence of
Value
Pixel Data (7FE0,0010) OW Pixel Data ALWAYS AUTO
SOP COMMON MODULE OF CREATED SOP INSTANCES
Attribute Name Tag VR Value Presence of Value Source

SOP Class UID (0008,0016) UI 1.2.840.10008.5.1.4.1.1.7 ALWAYS AUTO
SOP Instance UID (0008,0018) UI Uniquely identifies the SOP class ALWAYS AUTO


DICOM Conformance Statement IVUE

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

DICOM Conformance Statement IVUE

Uploaded by

Copyright:

Available Formats

Doc#: 200-53659

DICOM Conformance Statement

Optovue DICOM Module

Optovue DICOM Conformance Statement

Optovue DICOM Conformance Statement Page | 1

1 CONFORMANCE STATEMENT OVERVIEW

Table 1-1 Network Services

Optovue DICOM Conformance Statement Page | 2

4.1.1 .... Application Data Flow ..................................................................................................................15

4.1.2 .... Functional Definitions of AEs ......................................................................................................16

4.1.3 .... Sequencing of Real-World Activities ..........................................................................................16

4.2.1 .... Application Data Flow ..................................................................................................................17

4.2.2 .... Functional Definition of AETs .....................................................................................................18

4.2.3 .... Sequencing of Real-World Activities ..........................................................................................18

4.2.4 .... Application Data Flow ..................................................................................................................22

4.2.5 .... Functional Definition of AETs .....................................................................................................22

4.2.6 .... Sequencing of Real-World Activities ..........................................................................................22

4.3.1 .... SOP Class Specification ..............................................................................................................24

4.3.2 .... Association Policies ......................................................................................................................24

Optovue DICOM Conformance Statement Page | 3

4.3.3 .... Association initiation by Real-World Activity .............................................................................25

4.4.1 .... Physical Network Interfaces ........................................................................................................30

4.4.2 .... Additional Protocols ......................................................................................................................30

4.5.1 .... AE Title/Presentation Address Mapping ...................................................................................30

4.5.2 .... Parameters ....................................................................................................................................30

8.1.1 .... Created SOP Instances ...............................................................................................................33

8.1.2 .... Usage of Attributes from Received IODs ..................................................................................69

8.1.3 .... Attribute mapping..........................................................................................................................70

8.1.4 .... Coerced/Modified Fields ..............................................................................................................70

Table 1-1 Network Services .................................................................................................................................................................. 2

Table 3-1 DICOM Supported Scan Types per Product ..................................................................................................................... 9

Optovue DICOM Conformance Statement Page | 4

Figure 3 Sequencing of Real-World Activities - Verification ........................................................................................................... 17

Figure 4 Application Data Flow - Modality Worklist Query .............................................................................................................. 18

Figure 5 Sequencing of Real World Activities - MWL Query .......................................................................................................... 21

Figure 6 Application Data Flow - Storage .......................................................................................................................................... 22

Figure 7 Sequencing of Real-World Activities - Storage ................................................................................................................. 23

Figure 8 Implementation Class and Version ..................................................................................................................................... 25

Table 4-1 Presentation Contexts for Verification .............................................................................................................................. 25

Table 4-3 SOP Specific Conformance for Modality Worklist .......................................................................................................... 27

Table 8-1 Ophthalmic Photography 8 Bit - Patient Module ............................................................................................................. 35

Table 8-2 Ophthalmic Photography 8 Bit - General Study Module ................................................................................................ 35

Table 8-3 Ophthalmic Photography 8 Bit - General Series Module ............................................................................................. 35

Table 8-5 Ophthalmic Photography 8 Bit - Synchronization Module ............................................................................................. 36

Table 8-6 Ophthalmic Photography 8 Bit - General Equipment Module ....................................................................................... 37

Table 8-7 Ophthalmic Photography 8 Bit - General Image Module ............................................................................................... 37

Table 8-8 Ophthalmic Photography 8 Bit - Image Pixel Module .................................................................................................... 38

Table 8-9 Ophthalmic Photography 8 Bit - Multi Frame Module .................................................................................................... 39

Table 8-14 Ophthalmic Photography 8 Bit - SOP Common Module ............................................................................................. 45

Table 8-15 Ophthalmic Tomography Image - Patient Module ........................................................................................................ 47

Optovue DICOM Conformance Statement Page | 5

Table 8-16 Ophthalmic Tomography Image - General Study Module........................................................................................... 47

Table 8-17 Ophthalmic Tomography Image - General Series Module ......................................................................................... 48

Table 8-19 Ophthalmic Tomography Image - Frame of Reference Module ................................................................................. 48

Table 8-20 Ophthalmic Tomography Image - Synchronization Module ........................................................................................ 49

Table 8-21 Ophthalmic Tomography Image - General Equipment Module .................................................................................. 49

Table 8-23 Ophthalmic Tomography Image - Image Pixel Module ............................................................................................... 50

Table 8-26 Ophthalmic Tomography Image - Acquisition Context Module .................................................................................. 55

Table 8-31 Ophthalmic Tomography Image - SOP Common Module .......................................................................................... 60

Table 8-32 Encapsulated PDF - Patient Module .............................................................................................................................. 61

Table 8-33 Encapsulated PDF - General Study Module ................................................................................................................. 62

Table 8-34 Encapsulated PDF - Encapsulated Document Series Module ................................................................................... 62

Table 8-35 Encapsulated PDF - General Equipment Module ........................................................................................................ 63

Table 8-36 Encapsulated PDF - SC Equipment Module ................................................................................................................. 63