viewray™ system version 3 · 2018-06-12 · viewray™ system version 3.0 dicom conformance...
TRANSCRIPT
ViewRay™ System Version 3.0
DICOM Conformance Statement 2/2/12
Document No. L-0020 Rev. A February 2, 2012
This document contains information of ViewRay, Incorporated. Neither this document nor any of the information contained is to be modified, either in whole or in part, except as specifically authorized by ViewRay, Incorporated.
ViewRay Incorporated ViewRay™ System ii
Copyright Statement
Copyright © 2012 ViewRay Incorporated. All rights reserved. No part of this statement may be modified or translated into another language without written permission from ViewRay Incorporated (“ViewRay”).
ViewRay has taken care to ensure the accuracy of this Conformance Statement; however, ViewRay assumes no liability for errors or omissions and reserves the right to make changes without further notice to this Conformance Statement and any products herein to improve accuracy, reliability, function or design without obligation on the part of ViewRay to provide notification of such change.
ViewRay provides this Conformance Statement without warranty of any kind, either implied or expressed, including but not limited to, the implied warranties of merchantability, non-infringement, and fitness for a particular purpose. ViewRay hereby disclaims any incidental and/or consequential damages that arise in connection with this Conformance Statement.
This Conformance Statement contains proprietary information that is protected by copyright and other intellectual property laws. This Conformance Statement or any part hereof may not be modified, reproduced, translated, distributed, disseminated, or used to create a derivative work without the express written consent of ViewRay.
Scope
The scope of this Conformance Statement is to facilitate communication between the ViewRay System and other vendor’s medical equipment. The Conformance Statement should be read and understood in conjunction with the DICOM standard. DICOM is the usual choice for exchanging data with an open standard protocol for most vendors and institutions. ViewRay is committed to standard-based cross-vendor interoperability as well as making use of the DICOM protocol among its own products.
Conformance with DICOM, by itself, does not guarantee interoperability. However, the Conformance Statement guides validation for interoperability between different applications supporting the same DICOM functionality.
This Conformance Statement is not intended to replace physical validation with other DICOM equipment to ensure proper exchange of information.
Because the DICOM standard is subject to ongoing changes, enhancements and improvements, ViewRay reserves the right to change their products by making use of upcoming DICOM features without prior announcement.
ViewRay Incorporated ViewRay™ System iii
1. CONFORMANCE STATEMENT OVERVIEW
The ViewRay™ System contains two applications that utilize DICOM. The Remote Import Service provides the sole endpoint for DICOM network communications. It queries external systems to fulfill requests made by the user on one of many planning or delivery consoles, and receives image, and dose data from external systems. The ViewRay Console Software provides the user with options to import and create DICOM data files including image data, and RT dose, structure and point data.
Table 1-1: Network Services
SOP Classes User of Service (SCU) Provider of Service (SCP)
Transfer
CT Image Storage No Yes
MR Image Storage No Yes
Positron Emission Tomography Image Storage
No Yes
RT Dose Storage No Yes
Query/Retrieve
Study Root Query/Retrieve Information Model – FIND
Yes No
Study Root Query/Retrieve Information Model – MOVE
Yes No
Table 1-2: Media Services
Media Storage Application Profile
Write Files (FSC or FSU) Read Files (FSR)
Compact Disk – Recordable
General Purpose CD-R No Yes
CT/MR CD-R No Yes
DVD
General Purpose DVD No Yes
CT/MR DVD No Yes
The ViewRay Console software provides the user with the ability to create DICOM files compliant with part PS 3.10 of the DICOM standard to any user-specified directory. However, it does not meet the definition of a File Set Creator or File Set Updater defined for any of the application profiles in part PS 3.11.
ViewRay Incorporated ViewRay™ System iv
2. TABLE OF CONTENTS
1. CONFORMANCE STATEMENT OVERVIEW .................................................................................... iii
2. TABLE OF CONTENTS .................................................................................................................. iv
3. INTRODUCTION ..........................................................................................................................1
3.1 Revision History ......................................................................................................................... 1
3.2 Audience .................................................................................................................................... 1
3.3 Remarks ..................................................................................................................................... 1
3.4 Terms and Definitions ............................................................................................................... 1
3.5 Basics of DICOM Communication .............................................................................................. 3
3.6 Abbreviations ............................................................................................................................ 4
3.7 References ................................................................................................................................. 4
4. NETWORKING .............................................................................................................................5
4.1 Implementation Model ............................................................................................................. 5
4.2 AE Specifications ....................................................................................................................... 6
4.3 Network Interfaces .................................................................................................................. 13
4.4 Configuration ........................................................................................................................... 14
5. MEDIA INTERCHANGE ............................................................................................................... 16
5.1 Implementation Model ........................................................................................................... 16
5.2 AE Specifications ..................................................................................................................... 17
5.3 Augmented and Private Application Profiles .......................................................................... 17
5.4 Media Configuration ............................................................................................................... 17
6. SUPPORT OF CHARACTER SETS .................................................................................................. 18
7. SECURITY .................................................................................................................................. 19
Appendix A speciAlization ............................................................................................................ 20
A.1 IOD Contents ........................................................................................................................... 20
A.2 Data Dictionary of Private Attributes ...................................................................................... 20
A.3 Coded Terminology and Templates ........................................................................................ 20
A.4 Grayscale Image Consistency .................................................................................................. 20
A.5 Standard Extended/Specialized/Private Sop Classes .............................................................. 20
A.6 Private Transfer Syntaxes ........................................................................................................ 20
Appendix B Created SOP Instances ............................................................................................... 21
B.1 IOD Definitions ........................................................................................................................ 21
B.2 Module Definitions .................................................................................................................. 24
ViewRay Incorporated ViewRay™ System 1
3. INTRODUCTION
3.1 Revision History
Rev. Rev. Date Submitted by Description of Changes Reason for changes
A 2/2/2012 JA Initial Release
3.2 Audience
This document is intended for those that need to understand how the ViewRay System will integrate into their healthcare facility. This includes both anyone responsible for overall 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 ViewRay System and other DICOM compliant systems. 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 supposed 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:
The comparison of different Conformance Statements is just the first step towards assessing interconnectivity and interoperability between the ViewRay System 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.4 Terms and Definitions
Informal definitions are provided for the following terms used in this Conformance Statement. The DICOM Standard is the authoritative source for formal definitions of these terms.
Abstract Syntax – the information agreed to be exchanged between applications, generally equivalent to a Service/Object Pair (SOP) Class. Examples: Verification SOP Class, Modality Worklist Information Model Find SOP Class, Computed Radiography Image Storage SOP Class.
Application Entity (AE) – an end point of a DICOM information exchange, including the DICOM network or media interface software; i.e., the software that sends or receives DICOM information objects or messages. A single device may have multiple Application Entities.
Application Entity Title – the externally known name of an Application Entity, used to identify a DICOM application to other DICOM applications on the network.
Application Context – the specification of the type of communication used between Application Entities. Example: DICOM network protocol.
Association – a network communication channel set up between Application Entities.
ViewRay Incorporated ViewRay™ System 2
Attribute – a unit of information in an object definition; a data element identified by a tag. The information may be a complex data structure (Sequence), itself composed of lower level data elements. Examples: Patient ID (0010,0020), Accession Number (0008,0050), Photometric Interpretation (0028,0004), Procedure Code Sequence (0008,1032).
Information Object Definition (IOD) – the specified set of Attributes that comprise a type of data object; does not represent a specific instance of the data object, but rather a class of similar data objects that have the same properties. The Attributes may be specified as Mandatory (Type 1), Required but possibly unknown (Type 2), or Optional (Type 3), and there may be conditions associated with the use of an Attribute (Types 1C and 2C). Examples: MR Image IOD, CT Image IOD, Print Job IOD.
Joint Photographic Experts Group (JPEG) – a set of standardized image compression techniques, available for use by DICOM applications.
Media Application Profile – the specification of DICOM information objects and encoding exchanged on removable media (e.g., CDs)
Module – a set of Attributes within an Information Object Definition that are logically related to each other. Example: Patient Module includes Patient Name, Patient ID, Patient Birth Date, and Patient Sex.
Negotiation – first phase of Association establishment that allows Application Entities to agree on the types of data to be exchanged and how that data will be encoded.
Presentation Context – the set of DICOM network services used over an Association, as negotiated between Application Entities; includes Abstract Syntaxes and Transfer Syntaxes.
Protocol Data Unit (PDU) – a packet (piece) of a DICOM message sent across the network. Devices must specify the maximum size packet they can receive for DICOM messages.
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.
ViewRay Incorporated ViewRay™ System 3
Unique Identifier (UID) – a globally unique “dotted decimal” string that identifies a specific object or a class of objects; an ISO-8824 Object Identifier. Examples: Study Instance UID, SOP Class UID, SOP Instance UID.
Value Representation (VR) – the format type of an individual DICOM data element, such as text, an integer, a person’s name, or a code. DICOM information objects can be transmitted with either explicit identification of the type of each data element (Explicit VR), or without explicit identification (Implicit VR); with Implicit VR, the receiving application must use a DICOM data dictionary to look up the format of each data element.
3.5 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 a number of 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 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.
ViewRay Incorporated ViewRay™ System 4
3.6 Abbreviations
Acronym / Term Definition
AE Application Entity
AET Application Entity Title
CD-R Compact Disk Recordable
CT Computed Tomography
DHCP Dynamic Host Configuration Protocol
DICOM Digital Imaging and Communications in Medicine
FSC File-Set Creator
FSU File-Set Updater
FSR File-Set Reader
IOD Information Object Definition
IPv4 Internet Protocol version 4
MR Magnetic Resonance Imaging
MTU Maximum Transmission Unit (IP)
O Optional (Key Attribute)
OSI Open Systems Interconnection
PACS Picture Archiving and Communication System
PET Positron Emission Tomography
R Required (Key Attribute)
RT Radiotherapy
SCP Service Class Provider
SCU Service Class User
SOP Service-Object Pair
TCP/IP Transmission Control Protocol/Internet Protocol
U Unique (Key Attribute)
VR Value Representation
3.7 References
NEMA PS3 Digital Imaging and Communications in Medicine (DICOM) Standard, available free at http://medical.nema.org/
ViewRay Incorporated ViewRay™ System 5
4. NETWORKING
4.1 Implementation Model
4.1.1 Application Data Flow
Figure 4.1-1: Functional Overview
The three application endpoints shown here all reside within the remote import service. This is a single application that runs as a component of the overall ViewRay System.
The Query Application Entity is responsible for performing queries requested by the user application.
The Transfer Application Entity is responsible for initiating data transfers on behalf of the user application.
The Receiver Application Entity receives any inbound image and dose data. This data may be due to a transfer request, or it may be unsolicited by the ViewRay system.
All of these application entities share a single (configurable) AE Title.
ViewRay Incorporated ViewRay™ System 6
4.1.2 Functional Definition of AE’s
4.1.2.1 Query AE
Whenever the Remote Import Service receives a request to perform a DICOM query, the Query AE establishes an association with a remote server and performs the query using the study-root information model. The Query AE acts solely as an SCU, and cannot receive an association request.
4.1.2.2 Transfer AE
When the Remote Import Service receives a request to transfer data, the Transfer AE establishes an association with a remote server and retrieves the SOP Instance UIDs for the data to be transferred. It then requests the transfer to begin. All transfers are requested using the C-MOVE SOP. The Transfer AE acts solely as an SCU, and cannot receive an association request.
4.1.2.3 Receiver AE
The Receiver AE waits for an association to be made. It accepts associations where it will act as an ECHO-SCP or as an SCP for storage of any of the IODs that the system supports. Receiver AE receives all association requests made to the (configured) AE Title. All data transferred to the Receiver AE is stored in the ViewRay Database for later use.
4.1.3 Sequencing of Real World Activities
The Remote Import Service does not enforce any sequence between activities. As a matter of workflow, query operations are always performed before transfer requests. Data may be received at any time. Data is received and stored even if the transfer was not initiated by the Transfer AE.
4.2 AE Specifications
4.2.1 Query AE
4.2.1.1 SOP Classes
Query AE provides Standard Conformance to the following SOP Class:
Table 4.2-1: SOP Classes Supported by Query AE
SOP Class Name SOP Class UID SCU SCP
Study Root Query/Retrieve Information Model – FIND
1.2.840.10008.5.1.4.1.2.2.1 Yes No
4.2.1.2 Association Policies
4.2.1.2.1 General
The DICOM standard application context name for DICOM 3.0 is always proposed:
Table 4.2-2: DICOM Application Context for Query AE
Application Context Name 1.2.840.10008.3.1.1.1
4.2.1.2.2 Number of Associations
Each query request will result in at most one association. The number of requests is not limited by Remote Import Service, but is limited by workflow to the number of Treatment Planning and Treatment Delivery systems installed at a site.
ViewRay Incorporated ViewRay™ System 7
Table 4.2-3: Number of Associations as an Association Initiator for Query AE
Maximum number of simultaneous associations Unlimited
4.2.1.2.3 Asynchronous Nature
Only one transaction per association is permitted.
4.2.1.2.4 Implementation Identifying Information
Table 4.2-4: DICOM Implementation Class and Version for Query AE
Implementation Class UID 2.16.840.1.114493.1.2.1.1
Implementation Version Name ViewRay TPDS v3.0
4.2.1.3 Association Initiation Policy
4.2.1.3.1 User Performs Query
A query is performed from one of the treatment or delivery consoles.
4.2.1.3.1.1 Description and Sequencing of Activities
When a user performs a query, the request is sent to the Remote Import Service which initiates an association and performs the query using the Query AE. The results of the query that are received by the AE are then returned and displayed to the user.
4.2.1.3.1.2 Proposed Presentation Contexts
Table 4.2-5: Proposed Presentation Context for Query AE
Presentation Context Table
Abstract Syntax Transfer Syntax Role
Extended Negotiation Name UID Name List UID List
Storage Commitment Push Model SOP Class1
1.2.840.10008.1.20.1
Implicit VR Little Endian
1.2.840.10008.1.2 SCU None
Patient Root Query/Retrieve Information Model - FIND1
1.2.840.10008.5.1.4.1.2.1.1
Implicit VR Little Endian
1.2.840.10008.1.2
SCU None
Study Root Query/Retrieve Information Model – FIND2
1.2.840.10008.5.1.4.1.2.2.1
Implicit VR Little Endian
1.2.840.10008.1.2
SCU None
Patient Root Query/Retrieve Information Model - MOVE1
1.2.840.10008.5.1.4.1.2.1.2
Implicit VR Little Endian
1.2.840.10008.1.2
SCU None
Study Root Query/Retrieve Information Model - MOVE1
1.2.840.10008.5.1.4.1.2.2.2
Implicit VR Little Endian
1.2.840.10008.1.2
SCU None
ViewRay Incorporated ViewRay™ System 8
Presentation Context Table
Abstract Syntax Transfer Syntax Role
Extended Negotiation Name UID Name List UID List
Study Root Query/Retrieve Information Model - GET1
1.2.840.10008.5.1.4.1.2.2.3
Implicit VR Little Endian
1.2.840.10008.1.2
SCU None
Verification SOP Class1 1.2.840.10008.1.1
Implicit VR Little Endian
1.2.840.10008.1.2
SCU None
Note 1 – This presentation context is proposed, but not used.
Note 2 – If this presentation context is not accepted, the AE will not continue.
4.2.1.3.1.3 SOP Specific Conformance for SOP Class
The table below describes the behavior of the software in response to the status codes received in response to a query.
Table 4.2-6: Query Response Status Handling Behavior
Service Status Further Meaning Error Code Behavior
Failure * A700 A900 Cxxx
The association is closed and a message is displayed to the user describing the error. No results are returned to the user.
Cancel Matching terminated due to Cancel request
FE00 The association is closed. No results are returned to the user.
Success Matching is complete – No final identifier is supplied
0000 The association is closed, and the list of results is returned to the user.
Pending Matches are continuing – Current Match is supplied and any Optional Keys were supported in the same manner as Required Keys.
FF00 The result is added to the list of results to be returned to the user.
Matches are continuing – Warning that one or more Optional Keys were not supported for existence and/or matching for this Identifier.
FF01
Table 4.2-7: Query Communication Failure Behavior
Exception Behavior
Association Aborted A message is displayed to the user indicating that communication has failed, and providing a reason when possible. No results are returned to the user.
ViewRay Incorporated ViewRay™ System 9
4.2.1.4 Association Acceptance Policy
The Query AE does not accept associations.
4.2.2 Transfer AE
4.2.2.1 SOP Classes
Transfer AE provides Standard Conformance to the following SOP Classes:
Table 4.2-8: SOP Classes Supported by Transfer AE
SOP Class Name SOP Class UID SCU SCP
Study Root Query/Retrieve Information Model – FIND
1.2.840.10008.5.1.4.1.2.2.1 Yes No
Study Root Query/Retrieve Information Model – MOVE
1.2.840.10008.5.1.4.1.2.2.2 Yes No
4.2.2.2 Association Policies
4.2.2.2.1 General
The DICOM standard application context name for DICOM 3.0 is always proposed:
Table 4.2-9: DICOM Application Context for Transfer AE
Application Context Name 1.2.840.10008.3.1.1.1
4.2.2.2.2 Number of Associations
Each transfer request will result in two associations. The first association is closed before the second is established. In the event of a system failure, the Transfer AE will retry the transfer, resulting in two additional associations. The number of requests is not limited by Remote Import Service.
Table 4.2-10: Number of Associations as an Association Initiator for Transfer AE
Maximum number of simultaneous associations Unlimited
4.2.2.2.3 Asynchronous Nature
Only one transaction is permitted per association.
4.2.2.2.4 Implementation Identifying Information
Table 4.2-11: DICOM Implementation Class and Version for transfer AE
Implementation Class UID 2.16.840.1.114493.1.2.1.2
Implementation Version Name ViewRay TPDS v3.0
4.2.2.3 Association Initiation Policy
4.2.2.3.1 User Requests a Transfer
The user selects one or more search results to be transferred, and submits a transfer request.
ViewRay Incorporated ViewRay™ System 10
4.2.2.3.1.1 Description and Sequencing of Activities
After performing a search using the Query AE, the user is presented with a list of search results. The user may then select one or more of these results to be transferred, and submits the transfer job/request to the Transfer AE.
The Transfer AE establishes an association and performs a query to retrieve all of the SOP Instance UIDs of the instances to be transferred which is used to monitor the transfer of data. This association is closed, and another is established to perform a C-MOVE request on the data specified in the transfer job. Transfer requests are made at a series level.
The Receiver AE coordinates with the Transfer AE to provide feedback to the user.
4.2.2.3.1.2 Proposed Presentation Contexts
Table 4.2-12: Proposed Presentation Context for Transfer AE
Presentation Context Table
Abstract Syntax Transfer Syntax Role
Extended Negotiation Name UID Name List UID List
Storage Commitment Push Model SOP Class1
1.2.840.10008.1.20.1
Implicit VR Little Endian
1.2.840.10008.1.2
SCU None
Patient Root Query/Retrieve Information Model - FIND1
1.2.840.10008.5.1.4.1.2.1.1
Implicit VR Little Endian
1.2.840.10008.1.2
SCU None
Study Root Query/Retrieve Information Model – FIND2
1.2.840.10008.5.1.4.1.2.2.1
Implicit VR Little Endian
1.2.840.10008.1.2
SCU None
Patient Root Query/Retrieve Information Model - MOVE1
1.2.840.10008.5.1.4.1.2.1.2
Implicit VR Little Endian
1.2.840.10008.1.2
SCU None
Study Root Query/Retrieve Information Model - MOVE2
1.2.840.10008.5.1.4.1.2.2.2
Implicit VR Little Endian
1.2.840.10008.1.2
SCU None
Study Root Query/Retrieve Information Model - GET1
1.2.840.10008.5.1.4.1.2.2.3
Implicit VR Little Endian
1.2.840.10008.1.2
SCU None
Verification SOP Class1 1.2.840.10008.1.1
Implicit VR Little Endian
1.2.840.10008.1.2
SCU None
Note 1 – This presentation context is proposed, but not used.
Note 2 – If this presentation context is not accepted, the AE will not continue.
ViewRay Incorporated ViewRay™ System 11
4.2.2.3.1.3 SOP Specific Conformance for SOP Class
The table below describes the behavior of the software in response to the status codes received in response to a request.
Table 4.2-13: Query Response Status Handling Behavior
Service Status Further Meaning Error Code Behavior
Failure Cancel
* A700 A900 Cxxx FE00
The association is closed and a message is displayed to the user describing the error. The transfer is canceled.
Success Matching is complete – No final identifier is supplied
0000 The association is closed. The Transfer AE opens another connection and performs a MOVE operation.
Pending Matches are continuing – Current Match is supplied and any Optional Keys were supported in the same manner as Required Keys.
FF00 The result is added to the list of expected SOP Instance UIDs.
Matches are continuing – Warning that one or more Optional Keys were not supported for existence and/or matching for this Identifier.
FF01
Table 4.2-14: MOVE Response Status Handling Behavior
Service Status Further Meaning Error Code Behavior
Failure Cancel
* A701 A702 A801 A900 Cxxx FE00
The association is closed and a message is displayed to the user describing the error. The transfer is canceled.
Warning Sub-operations Complete – One or more Failures
B000
Success Sub-operations Complete – No Failures
0000 The association is closed. Once all instances are received, the user is notified that the job is complete (if listening).
Pending Sub-operations are continuing FF00 No response required.
Table 4.2-15: Communication Failure Behavior
Exception Behavior
Association Aborted A message is displayed to the user indicating that communication has failed, and providing a reason when possible.
ViewRay Incorporated ViewRay™ System 12
Exception Behavior
Timeout Receiving Instances After Move Operation Responds Completed.
If the move operation reports Success, the system waits for all expected instances to be received. If there are instances expected by the Transfer AE that have not received, and no instance is received for 2 minutes, the system reports an error the user.
4.2.2.4 Association Acceptance Policy
The Transfer AE does not accept associations.
4.2.3 Receiver AE
4.2.3.1 SOP Classes
Receiver AE provides Standard Conformance to the following SOP Class(es):
Table 4.2-16: SOP Classes Supported by Receiver AE
SOP Class Name SOP Class UID SCU SCP
CT Image Storage 1.2.840.10008.5.1.4.1.1.2 No Yes
MR Image Storage 1.2.840.10008.5.1.4.1.1.4 No Yes
Positron Emission Tomography Image Storage 1.2.840.10008.5.1.4.1.1.128 No Yes
RT Dose Storage1 1.2.840.10008.5.1.4.1.1.481.2 No Yes
Verification SOP Class 1.2.840.10008.1.1 No Yes
Note 1: Only grid-based doses are supported.
4.2.3.2 Association Policies
4.2.3.2.1 General
The DICOM standard application context name for DICOM 3.0 is always proposed:
Table 4.2-17: DICOM Application Context for Receiver AE
Application Context Name 1.2.840.10008.3.1.1.1
4.2.3.2.2 Number of Associations
Table 4.2-18: Number of Associations as an Association Acceptor for Receiver AE
Maximum number of simultaneous associations Unlimited
4.2.3.2.3 Asynchronous Nature
The Receiver AE does not support multiple outstanding transactions on the same association.
4.2.3.2.4 Implementation Identifying Information
Table 4.2-19: DICOM Implementation Class and Version for Receiver AE
Implementation Class UID 2.16.840.1.114493.1.2.1.3
Implementation Version Name ViewRay TPDS v3.0
ViewRay Incorporated ViewRay™ System 13
4.2.3.3 Association Initiation Policy
The Receiver AE does not initiate associations.
4.2.3.4 Association Acceptance Policy
The Receiver AE handles all association requests to the Remote Import Service.
4.2.3.4.1 Storage Requested
An external system requests that an instance is stored in the ViewRay system. This request may be the result of a transfer job controlled by the Transfer AE, or it may be unsolicited.
4.2.3.4.1.1 Description and Sequencing of Activities
The Transfer AE performs a MOVE request on a DICOM system, which initiates a STORE operation on the Remote Import Service AE Title. This is received by the Receiver AE.
OR
A user of another DICOM-compliant system initiates a STORE operation on the Remote Import Service AE Title.
4.2.3.4.1.2 Accepted Presentation Contexts
Table 4.2-20: Acceptable Presentation Context for receiver AE
Presentation Context Table
Abstract Syntax Transfer Syntax Role
Extended Negotiation Name UID Name List UID List
See Table 4.2-16 Implicit VR Little
Endian
1.2.840.10008.1.2 SCP None
4.2.3.4.1.3 SOP Specific Conformance for SOP Class
The table below describes the behavior of the software in indicated by each error code that the Receiver AE may produce.
Table 4.2-21: Storage C-STORE Response Status
Service Status Further Meaning Error Code Reason
Success Success 0000 The data was stored.
Error There was an error interpreting the data.
C000 The data was either not supported, or invalid. The data was not stored.
4.3 Network Interfaces
4.3.1 Physical Network Interface
The ViewRay Database Server system has an Ethernet connector reserved for hospital communication. All DICOM communication is done through this connection using TCP/IP.
ViewRay Incorporated ViewRay™ System 14
4.3.2 Additional Protocols
Table 4.3-1:System Management Profiles Table
Profile Name Actor Protocols Used Optional Transactions Security Support
Network Address Management
DHCP Client DHCP N/A
DNS Client DNS N/A
The Remote Import Service uses the facilities of the underlying operating system to configure IP address by DHCP, and provide name resolution by DNS.
4.3.3 IPv4 and IPv6 Support
This product supports only IPv4.
4.4 Configuration
4.4.1 AE Title/Presentation Address Mapping
4.4.1.1 Local AE Titles
All AEs share the one AE Title which is configurable by a service engineer. This AE Title functions as both the calling AE Title for the Query and Transfer AEs, and the destination AE Title for the Receiver AE. All association requests received by the Remote Import Service for this AE title are handled by the Receiver AE. The listening TCP/IP port is also configurable.
Table 4.4-1: AE Title Configuration Table
Application Entity Default AE Title Default TCP/IP Port
Query AE No Default Not Applicable
Transfer AE No Default Not Applicable
Receiver AE No Default 11112
4.4.1.2 Remote AE Title/Presentation Address Mapping
Remote host names, TCP/IP ports, and AE Titles can be modified by the user whenever they initiate a search. These settings may also be stored for easy retrieval in the future. In this case, the entries are referenced by AE Title which must be unique.
4.4.1.2.1 Receiver
The Receiver SCP accepts associations form any host/AE Title.
4.4.2 Parameters
Table 4.4-2: Configuration Parameters Table
Parameter Configurable
(Yes/No) Default Value
General Parameters
Time-out waiting for acceptance or rejection response to an Association Open Request. (Application Level timeout)
No None
ViewRay Incorporated ViewRay™ System 15
Parameter Configurable
(Yes/No) Default Value
General Parameters
Time-out waiting for a response to TCP/IP connect request (Low-level timeout)
No 9 s
Time-out for waiting for data between TCP/IP packets (Low-level timeout)
No Dynamically adjusted per connection.
Maximum PDU size the AE can receive No 64 KB
Maximum PDU size the AE can send No 64 KB
ViewRay Incorporated ViewRay™ System 16
5. MEDIA INTERCHANGE
5.1 Implementation Model
5.1.1 Application Data Flow Diagram
Figure 5.1-1: Application Data Flow Diagram
The ViewRay System treatment planning and treatment delivery consoles provide the user with the capability of importing and exporting data using files compliant with part PS 3.10 of the DICOM standard.
5.1.2 Functional definitions of the ViewRay Console Software
The user has the option to import data into the ViewRay Database. The user is prompted to select the files to import from the file system. All selected instances are checked for compatibility, and imported into the ViewRay database for future use.
When exporting, the user selects the data to be exported, and specifies a directory to output the data to. All selected data are written to the specified location.
5.1.3 Sequencing of Real World Activities
No sequencing of real world activities is defined.
5.1.4 File Meta Information for Implementation Class and Version
Implementation Class UID 2.16.840.1.114493.1.2.1.4
Implementation Version Name ViewRay TPDS v3.0
ViewRay Incorporated ViewRay™ System 17
5.2 AE Specifications
5.2.1 ViewRay Console Software – Specification
Table 5.2-1: AE RELATED APPLICATION PROFILES, REAL-WORLD ACTIVITIES, AND ROLES
Supported Application Profile Real-World Activity Roles
STD-CTMR Import Data FSR
STD-GEN Export Data See Note 1
Note 1: The ViewRay Console software provides the user with the ability to create DICOM files compliant with part PS 3.10 of the DICOM standard to any user-specified directory. However, it does not meet the definition of a File Set Creator or File Set Updater for any of the application profiles defined in part PS 3.11.
5.2.1.1 File Meta Information for the ViewRay Console Software
The ViewRay Console software uses the configurable AE Title as the Source Application Entity Title. No private data is written to the File Meta Information.
5.2.1.2 Real-World Activities
5.2.1.2.1 Import Data
The system acts as a FSR when importing data. The user is prompted for the location of the data to be imported. These data are then loaded into the ViewRay Database for later use.
5.2.1.2.1.1 Media Storage Application Profiles
The STD-CTMR and STD-GEN profiles
5.2.1.2.2 Export Data
The system writes files compliant with part PS 3.10 of the DICOM standard when exporting data from the database. These data may have originated on the system, or they may be data that has been previously imported into the ViewRay database. The user selects what data are to be exported, and the output location to write the files.
5.2.1.2.2.1 Media Storage Application Profiles
The ViewRay Console software does not fully meet the definition of any FSC as defined in part PS 3.11.
5.3 Augmented and Private Application Profiles
5.3.1 Augmented Application Profiles
There are no augmented Application Profiles defined.
5.3.2 Private Application Profiles
There are no private Application Profiles defined.
5.4 Media Configuration
A service user may configure the AE Title used by the ViewRay Console Software as the Source AE Title. This shall be configured to match the AE Title used by the Remote Import Service.
ViewRay Incorporated ViewRay™ System 18
6. SUPPORT OF CHARACTER SETS
The ViewRay System uses only the default character repertoire (ISO 646).
All instances will be created with this character set.
Any instance received or imported into the ViewRay system that does not use this character set will be rejected.
ViewRay Incorporated ViewRay™ System 19
7. SECURITY
The ViewRay System does not support any specific Security Profiles. It is assumed that the system operates in a secured environment. Specifically it is assumed that:
a. There is a firewall or router that prevents unauthorized network access to the ViewRay System.
b. There is a firewall or router that prevents the ViewRay System from accessing unauthorized systems via the network.
c. Any access made by a system outside of this secured network is made via an appropriate security mechanism such as VPN.
More generally, it is assumed that any access to or from the ViewRay System is authorized by virtue of the fact that the network is configured to permit this access.
ViewRay Incorporated ViewRay™ System 20
APPENDIX A SPECIALIZATION
A.1 IOD Contents
A.1.1 Created SOP Instance(s)
Any instance imported into the ViewRay System is written without modification when exported. The instance is written into a file with a ViewRay-created File Meta Information.
See Appendix B for information on instances created by the ViewRay System.
A.1.2 Usage of Attributes from received IOD’s
The ViewRay System requires all type 1 fields to be present and have a value.
For 4-D image data (volumetric data in time) where all of the data is contained in one series, the ViewRay System uses the value of the Instance Number (0020,0013) field to order the image data. If this field is not present on such a series, the system will not be able to divide the image data into volumes.
A.1.3 Attribute Mapping
See Appendix B for attribute mapping information.
A.1.4 Coerced/Modified fields
All imported instances are written unmodified when exporting data. This section describes the coercion of data within the ViewRay System.
When the system imports a new instance, if the database already contains data for a patient with matching patient id, the system verifies that the patient’s sex and birth date are also a match. If they do, all other fields in the Patient Identification Module are coerced to the values already in the database. If they do not match, the instance is rejected.
When the system imports a new instance, if the database already contains data with the same Study Instance UID, the instance is checked to ensure that it has the same Patient ID as the existing study. If so, all fields in the Patient Identification Module and the General Study module are coerced to the existing values. If they do not match, the instance is rejected.
When the system imports a new instance, if the database already contains data with the same Series Instance UID, the instance is checked to ensure that it has the same Study Instance UID as the existing series. If it does, all fields in the Patient Identification Module, the General Study Module, and the General Series Module are coerced to the existing values. If they do not match, the instance is rejected.
A.2 Data Dictionary of Private Attributes
The ViewRay System does not use any private attributes.
A.3 Coded Terminology and Templates
The ViewRay System does not use coded terminology.
A.4 Grayscale Image Consistency
The ViewRay System does not provide support for the DICOM Grayscale Standard Display Function.
A.5 Standard Extended/Specialized/Private Sop Classes
No extended, specialized or private SOP classes are used by the ViewRay System.
A.6 Private Transfer Syntaxes
The ViewRay System does not use private transfer syntaxes.
ViewRay Incorporated ViewRay™ System 21
APPENDIX B CREATED SOP INSTANCES
This appendix is intended to provide information about what data will be present when exporting data that originates from the ViewRay System. The first section of this appendix lists all of the IODs created by the system, and an indication of which modules will be present when exporting instances of that type. The second section lists all of the modules used by the system, and identifies the source of the data for each field.
Throughout this appendix, we reference part PS 3.3 of the DICOM standard. Such references are made in square brackets. As an example, [A.3] refers to the section of the standard identifying the CT Image IOD. The section numbers referenced are taken from the 2008 standard.
B.1 IOD Definitions
This section identifies each IOD exported by the system, the conditions under which an instance of the IOD would be created, and which modules are populated at export.
The following definitions are used in this section
INCLUDED The module is included in the instance
NOT SUPPORTED The module is not included in the instance
B.1.1 CT Image IOD [A.3]
CT Images may be created as a result of image registration or interpolation.
IE Module Reference Support
Patient Patient [C.7.1.1] INCLUDED
Clinical Trial Subject [C.7.1.3] NOT SUPPORTED
Study General Study [C.7.2.1] INCLUDED
Patient Study [C.7.2.2] NOT SUPPORTED
Clinical Trial Study [C.7.2.3] NOT SUPPORTED
Series General Series [C.7.3.1] INCLUDED
Clinical Trial Series [C.7.3.2] NOT SUPPORTED
Frame of Reference Frame of Reference [C.7.4.1] INCLUDED
Equipment General Equipment [C.7.5.1] INCLUDED
Image General Image [C.7.6.1] INCLUDED
Image Plane [C.7.6.2] INCLUDED
Image Pixel [C.7.6.3] INCLUDED
Contrast/bolus [C.7.6.4] NOT SUPPORTED
Device [C.7.6.12] NOT SUPPORTED
CT Image [C.8.2.1] INCLUDED
Overlay Plane [C.9.2] NOT SUPPORTED
VOI LUT [C.11.2] NOT SUPPORTED
SOP Common [C.12.1] INCLUDED
ViewRay Incorporated ViewRay™ System 22
B.1.2 MR Image IOD [A.4]
MR Images may be created as a result of image registration or interpolation, or may be created as a result of a scan run on the system including standard imaging, and patient setup scans.
IE Module Reference Support
Patient Patient [C.7.1.1] INCLUDED
Clinical Trial Subject [C.7.1.3] NOT SUPPORTED
Study General Study [C.7.2.1] INCLUDED
Patient Study [C.7.2.2] NOT SUPPORTED
Clinical Trial Study [C.7.2.3] NOT SUPPORTED
Series General Series [C.7.3.1] INCLUDED
Clinical Trial Series [C.7.3.2] NOT SUPPORTED
Frame of Reference Frame of Reference [C.7.4.1] INCLUDED
Equipment General Equipment [C.7.5.1] INCLUDED
Image General Image [C.7.6.1] INCLUDED
Image Plane [C.7.6.2] INCLUDED
Image Pixel [C.7.6.3] INCLUDED
Contrast/bolus [C.7.6.4] NOT SUPPORTED
Device [C.7.6.12] NOT SUPPORTED
MR Image [C.8.3.1] INCLUDED
Overlay Plane [C.9.2] NOT SUPPORTED
VOI LUT [C.11.2] NOT SUPPORTED
SOP Common [C.12.1] INCLUDED
B.1.3 RT Dose IOD [A.18]
RT Dose data may be created as the result of image registration (dose registration) or interpolation, or may be created as a result of dose calculations made within the ViewRay System.
IE Module Reference Support
Patient Patient [C.7.1.1] INCLUDED
Clinical Trial Subject [C.7.1.3] NOT SUPPORTED
Study General Study [C.7.2.1] INCLUDED
Patient Study [C.7.2.2] NOT SUPPORTED
Clinical Trial Study [C.7.2.3] NOT SUPPORTED
Series RT Series [C.8.8.1] INCLUDED
Clinical Trial Series [C.7.3.2] NOT SUPPORTED
Frame of Reference Frame of Reference [C.7.4.1] INCLUDED
Equipment General Equipment [C.7.5.1] INCLUDED for grid-based dose data.
ViewRay Incorporated ViewRay™ System 23
IE Module Reference Support
Dose General Image [C.7.6.1] INCLUDED for grid-based dose data.
Image Plane [C.7.6.2] INCLUDED for grid-based dose data.
Image Pixel [C.7.6.3] INCLUDED for grid-based dose data.
Multi-Frame [C.7.6.6] INCLUDED for grid-based dose data.
Overlay Plane [C.9.2] NOT SUPPORTED
Multi-Frame Overlay [C.9.3] NOT SUPPORTED
Modality LUT [C.11.1] NOT SUPPORTED
RT Dose [C.8.8.3] INCLUDED
RT DVH [C.8.8.4] NOT SUPPORTED
Structure Set [C.8.8.5] INCLUDED for point-based dose data.
ROI Contour [C.8.8.6] INCLUDED for point-based dose data.
RT Dose ROI [C.8.8.7] INCLUDED for point-based dose data.
SOP Common [C.12.1] INCLUDED
B.1.4 RT Structure Set IOD [A.19]
RT Structure sets are created as a result of contouring operations on a plan.
IE Module Reference Support
Patient Patient [C.7.1.1] INCLUDED
Clinical Trial Subject [C.7.1.3] NOT SUPPORTED
Study General Study [C.7.2.1] INCLUDED
Patient Study [C.7.2.2] NOT SUPPORTED
Clinical Trial Study [C.7.2.3] NOT SUPPORTED
Series RT Series [C.8.8.1] INCLUDED
Clinical Trial Series [C.7.3.2] NOT SUPPORTED
Equipment General Equipment [C.7.5.1] INCLUDED
Structure Set Structure Set [C.8.8.5] INCLUDED
ROI Contour [C.8.8.6] INCLUDED
RT ROI Observations [C.8.8.8] INCLUDED
Approval [C.8.8.16] NOT SUPPORTED
SOP Common [C.12.1] INCLUDED
ViewRay Incorporated ViewRay™ System 24
B.1.5 PET Image IOD [A.21]
PET Images may be created as a result of image registration or interpolation.
IE Module Reference Support
Patient Patient [C.7.1.1] INCLUDED
Clinical Trial Subject [C.7.1.3] NOT SUPPORTED
Study General Study [C.7.2.1] INCLUDED
Patient Study [C.7.2.2] NOT SUPPORTED
Clinical Trial Study [C.7.2.3] NOT SUPPORTED
Series General Series [C.7.3.1] INCLUDED
Clinical Trial Series [C.7.3.2] NOT SUPPORTED
PET Series [C.8.9.1] INCLUDED
PET Isotope [C.8.9.2] INCLUDED
PET Multi-gated Acquisition
[C.8.9.3] NOT SUPPORTED
NM/PET Patient Orientation
[C.8.4.6] INCLUDED
Frame of Reference Frame of Reference [C.7.4.1] INCLUDED
Equipment General Equipment [C.7.5.1] INCLUDED
Image General Image [C.7.6.1] INCLUDED
Image Plane [C.7.6.2] INCLUDED
Image Pixel [C.7.6.3] INCLUDED
Device [C.7.6.12] NOT SUPPORTED
PET Image [C.8.9.4] INCLUDED
Overlay Plane [C.9.2] NOT SUPPORTED
VOI LUT [C.11.2] NOT SUPPORTED
Acquisition Context [C.7.6.14] NOT SUPPORTED
SOP Common [C.12.1] INCLUDED
B.2 Module Definitions
This section lists all of the modules indicated as INCLUDED in the previous section, and provides information about the source of each field.
This section uses the following definitions
ANAP Attribute Not Always Present.
AUTO The attribute value is generated automatically.
CONFIG The attribute value is taken from a configuration parameter.
COPY The attribute value is taken from the original source of the data. For example, many attributes are taken from an original image set when registration is performed.
ViewRay Incorporated ViewRay™ System 25
DB The Attribute value is taken from the database and originated from user input.
EMPTY Attribute is sent without a value.
USER The attribute value is from user input at the time of export.
B.2.1 Patient Module [C.7.1.1]
Attribute Name Tag Type Value Handling
Patient's Name (0010,0010) 2 COPY for interpolation DB otherwise
Patient ID (0010,0020) 2 COPY for interpolation DB otherwise
Issuer of Patient ID (0010,0021) 3 ANAP
Patient's Birth Date (0010,0030) 2 COPY for interpolation DB otherwise
Patient's Sex (0010,0040) 2 COPY for interpolation DB otherwise
Referenced Patient Sequence (0008,1120) 3 COPY for interpolation ANAP otherwise
>Include SOP Instance Reference Macro [Table 10-11]
Patient's Birth Time (0010,0032) 3 COPY for interpolation ANAP otherwise
Other Patient IDs (0010,1000) 3 COPY for interpolation ANAP otherwise
Other Patient IDs Sequence (0010,1002) 3 ANAP
>Patient ID (0010,0020) 1
>Issuer of Patient ID (0010,0021) 1
>Type of Patient ID (0010,0022) 1
Other Patient Names (0010,1001) 3 COPY for interpolation EMPTY otherwise
Ethnic Group (0010,2160) 3 COPY for interpolation ANAP otherwise
Patient Comments (0010,4000) 3 COPY for interpolation ANAP otherwise
Patient Species Description (0010,2201) 1C ANAP
Patient Species Code Sequence (0010,2202) 1C ANAP
>Include ‘Code Sequence Macro’ [Table 8.8-1]
Patient Breed Description (0010,2292) 2C ANAP
Patient Breed Code Sequence (0010,2293) 2C ANAP
>Include ‘Code Sequence Macro’ [Table 8.8-1]
Breed Registration Sequence (0010,2294) 2C ANAP
>Breed Registration Number (0010,2295) 1
>Breed Registry Code Sequence (0010,2296) 1
ViewRay Incorporated ViewRay™ System 26
Attribute Name Tag Type Value Handling
>>Include ‘Code Sequence Macro’ [Table 8.8-1]
Responsible Person (0010,2297) 2C ANAP
Responsible Person Role (0010,2298) 1C ANAP
Responsible Organization (0010,2299) 2C ANAP
Patient Identity Removed (0012,0062) 3 ANAP
De-identification Method (0012,0063) 1C ANAP
De-identification Method Code Sequence
(0012,0064) 1C ANAP
>Include Code Sequence Macro [Table 8.8-1]
B.2.2 General Study Module [C.7.2.1]
Attribute Name Tag Type Value Handling
Study Instance UID (0020,000D) 1 AUTO
Study Date (0008,0020) 2 AUTO
Study Time (0008,0030) 2 AUTO
Referring Physician's Name (0008,0090) 2 EMPTY
Referring Physician Identification Sequence
(0008,0096) 3 ANAP
>Include ‘Person Identification Macro’ [Table 10-1]
Study ID (0020,0010) 2 EMPTY
Accession Number (0008,0050) 2 EMPTY
Study Description (0008,1030) 3 ANAP
Physician(s) of Record (0008,1048) 3 ANAP
Physician(s) of Record Identification Sequence
(0008,1049) 3 ANAP
>Include ‘Person Identification Macro’ [Table 10-1]
Name of Physician(s) Reading Study (0008,1060) 3 ANAP
Physician(s) Reading Study Identification Sequence
(0008,1062) 3 ANAP
>Include ‘Person Identification Macro’ [Table 10-1]
Referenced Study Sequence (0008,1110) 3 ANAP
>Include SOP Instance Reference Macro [Table 10-11]
Procedure Code Sequence (0008,1032) 3 ANAP
>Include ‘Code Sequence Macro’ [Table 8.8-1]
ViewRay Incorporated ViewRay™ System 27
B.2.3 General Series Module [C.7.3.1]
Attribute Name Tag Type Value Handling
Modality (0008,0060) 1 The appropriate value for the given modality is written.
Series Instance UID (0020,000E) 1 AUTO
Series Number (0020,0011) 2 EMPTY
Laterality (0020,0060) 2C COPY for interpolation EMPTY otherwise
Series Date (0008,0021) 3 AUTO for interpolation ANAP otherwise
Series Time (0008,0031) 3 AUTO for interpolation ANAP otherwise
Performing Physicians’ Name (0008,1050) 3 ANAP
Performing Physician Identification Sequence
(0008,1052) 3 ANAP
>Include ‘Person Identification Macro’ [Table 10-1]
Protocol Name (0018,1030) 3 COPY for interpolation ANAP otherwise
Series Description (0008,103E) 3 DB
Operators' Name (0008,1070) 3 ANAP
Operator Identification Sequence (0008,1072) 3 ANAP
>Include ‘Person Identification Macro’ [Table 10-1]
Referenced Performed Procedure Step Sequence
(0008,1111) 3 ANAP
>Include SOP Instance Reference Macro [Table 10-11]
Related Series Sequence (0008,1250) 3 ANAP
>Study Instance UID (0020,000D) 1
>Series Instance UID (0020,000E) 1
>Purpose of Reference Code Sequence (0040,A170) 2
>>Include Code Sequence Macro [Table 8.8-1]
Body Part Examined (0018,0015) 3 COPY for interpolation ANAP otherwise
Patient Position (0018,5100) 2C DB
Smallest Pixel Value in Series (0028,0108) 3 COPY for interpolation ANAP otherwise
Largest Pixel Value in Series (0028,0109) 3 COPY for interpolation ANAP otherwise
Request Attributes Sequence (0040,0275) 3 ANAP
>Include Request Attributes Macro [Table 10-9]
Performed Procedure Step ID (0040,0253) 3 ANAP
Performed Procedure Step Start Date (0040,0244) 3 ANAP
ViewRay Incorporated ViewRay™ System 28
Attribute Name Tag Type Value Handling
Performed Procedure Step Start Time (0040,0245) 3 ANAP
Performed Procedure Step Description (0040,0254) 3 ANAP
Performed Protocol Code Sequence (0040,0260) 3 ANAP
>Include ‘Code Sequence Macro’ [Table 8.8-1]
>Protocol Context Sequence (0040,0440) 3 ANAP
>>Include ‘Content Item Macro’ [Table 10-2]
>> Content Item Modifier Sequence (0040,0441) 3 ANAP
>>>Include ‘Content Item Macro’ [Table 10-2]
Comments on the Performed Procedure Step
(0040,0280) 3 ANAP
B.2.4 Frame Of Reference Module [C.7.4.1]
Attribute Name Tag Type Value Handling
Frame of Reference UID (0020,0052) 1 AUTO
Position Reference Indicator (0020,1040) 2 EMPTY
B.2.5 General Equipment Module [C.5.5.1]
Attribute Name Tag Type Value Handling
Manufacturer (0008,0070) 2 AUTO
Institution Name (0008,0080) 3 CONFIG
Institution Address (0008,0081) 3 CONFIG
Station Name (0008,1010) 3 ANAP
Institutional Department Name (0008,1040) 3 CONFIG
Manufacturer's Model Name (0008,1090) 3 CONFIG
Device Serial Number (0018,1000) 3 CONFIG
Software Versions (0018,1020) 3 CONFIG
Gantry ID (0018,1008) 3 ANAP
Spatial Resolution (0018,1050) 3 ANAP
Date of Last Calibration (0018,1200) 3 ANAP
Time of Last Calibration (0018,1201) 3 ANAP
Pixel Padding Value (0028,0120) 1C ANAP
B.2.6 General Image Module [C.7.6.1]
Attribute Name Tag Type Value Handling
Instance Number (0020,0013) 2 COPY for interpolation AUTO otherwise
ViewRay Incorporated ViewRay™ System 29
Attribute Name Tag Type Value Handling
Patient Orientation (0020,0020) 2C COPY for interpolation EMPTY otherwise
Content Date (0008,0023) 2C AUTO for interpolation EMPTY otherwise
Content Time (0008,0033) 2C AUTO for interpolation EMPTY otherwise
Image Type (0008,0008) 3 Value 1 is always set to “DERIVED”. Value 2 is copied for interpolation, and set to “SECONDARY” otherwise. See other modules for specialization of values 3 and 4.
Acquisition Number (0020,0012) 3 ANAP
Acquisition Date (0008,0022) 3 ANAP
Acquisition Time (0008,0032) 3 ANAP
Acquisition DateTime (0008,002A) 3 COPY for interpolation ANAP otherwise
Referenced Image Sequence (0008,1140) 3 ANAP
>Include ‘Image SOP Instance Reference Macro’ [Table 10-3]
>Purpose of Reference Code Sequence (0040,A170) 3
>>Include ‘Code Sequence Macro’ [Table 8.8-1]
Derivation Description (0008,2111) 3 ANAP
Derivation Code Sequence (0008,9215) 3 ANAP
>Include ‘Code Sequence Macro’ [Table 8.8-1]
Source Image Sequence (0008,2112) 3
>Include ‘Image SOP Instance Reference Macro’ [Table 10-3]
>Purpose of Reference Code Sequence (0040,A170) 3
>>Include ‘Code Sequence Macro’ [Table 8.8-1]
>Spatial Locations Preserved (0028,135A) 3
>Patient Orientation (0020,0020) 1C
Referenced Instance Sequence (0008,114A) 3 ANAP
>Include SOP Instance Reference Macro [Table 10-11]
>Purpose of Reference Code Sequence (0040,A170) 1
>>Include 'Code Sequence Macro' [Table 8.8-1]
Images in Acquisition (0020,1002) 3 ANAP
Image Comments (0020,4000) 3 ANAP
Quality Control Image (0028,0300) 3 ANAP
Burned In Annotation (0028,0301) 3 COPY for interpolation ANAP otherwise
ViewRay Incorporated ViewRay™ System 30
Attribute Name Tag Type Value Handling
Lossy Image Compression (0028,2110) 3 ‘N’ for interpolation ANAP otherwise
Lossy Image Compression Ratio (0028,2112) 3 ANAP
Lossy Image Compression Method (0028,2114) 3 ANAP
Icon Image Sequence (0088,0200) 3 ANAP
> Include ‘Image Pixel Macro’ [Table C.7-11b]
Presentation LUT Shape (2050,0020) 3 ANAP
Irradiation Event UID (0008,3010) 3 ANAP
B.2.7 Image Plane Module [C.7.6.2]
Attribute Name Tag Type Value Handling
Pixel Spacing (0028,0030) 1 Set to the pixel spacing of the resulting volume
Image Orientation (Patient) (0020,0037) 1 Set according to the orientation of the pixel data relative to the patient
Image Position (Patient) (0020,0032) 1 Set to the location of the first pixel in the image
Slice Thickness (0018,0050) 2 COPY for interpolation Set to the distance between slices otherwise
Slice Location (0020,1041) 3 ANAP
B.2.8 Image Pixel Module [C.7.6.3]
Attribute Name Tag Type Value Handling
Samples per Pixel (0028,0002) 1 AUTO
Photometric Interpretation (0028,0004) 1 AUTO
Rows (0028,0010) 1 Number of rows in the image.
Columns (0028,0011) 1 Number of columns in the image
Bits Allocated (0028,0100) 1 All instances generated by the ViewRay system are 16-bit.
Bits Stored (0028,0101) 1 COPY for interpolation AUTO otherwise
High Bit (0028,0102) 1 COPY for interpolation AUTO otherwise
Pixel Representation (0028,0103) 1 COPY for interpolation AUTO otherwise
Pixel Data (7FE0,0010) 1C AUTO
Planar Configuration (0028,0006) 1C ANAP – Only data with 1 sample per pixel are supported.
Pixel Aspect Ratio (0028,0034) 1C ANAP – Pixel Spacing is used to determine pixel aspect ratio
ViewRay Incorporated ViewRay™ System 31
Attribute Name Tag Type Value Handling
Smallest Image Pixel Value (0028,0106) 3 ANAP
Largest Image Pixel Value (0028,0107) 3 ANAP
Red Palette Color Lookup Table Descriptor
(0028,1101) 1C ANAP – LUT not supported
Green Palette Color Lookup Table Descriptor
(0028,1102) 1C ANAP – LUT not supported
Blue Palette Color Lookup Table Descriptor
(0028,1103) 1C ANAP – LUT not supported
Red Palette Color Lookup Table Data (0028,1201) 1C ANAP – LUT not supported
Green Palette Color Lookup Table Data
(0028,1202) 1C ANAP – LUT not supported
Blue Palette Color Lookup Table Data (0028,1203) 1C ANAP – LUT not supported
ICC Profile (0028,2000) 3 ANAP
Pixel Data Provider URL (0028,7FE0) 1C ANAP – DICOM JPNP not supported
Pixel Padding Range Limit (0028,0121) 1C ANAP – Padding range not supported
B.2.9 Multi-Frame Module [C.7.6.6]
Attribute Name Tag Type Value Handling
Number of Frames (0028,0008) 1 Number of frames in a Multi-frame Image.
Frame Increment Pointer (0028,0009) 1 AUTO
B.2.10 CT Image [C.8.2.1]
Attribute Name Tag Type Value Handling
Image Type (0008,0008) 1 Values 3 and 4 are copied for interpolated volumes. Value 3 is set to “AXIAL” and value 4 is note sent otherwise.
Samples per Pixel (0028,0002) 1 These values are defined as stated in section B.2.6. The values are compliant with the definitions in [C.8.2.1.1].
Photometric Interpretation (0028,0004) 1
Bits Allocated (0028,0100) 1
Bits Stored (0028,0101) 1
High Bit (0028,0102) 1
Rescale Intercept (0028,1052) 1 AUTO
Rescale Slope (0028,1053) 1 AUTO
KVP (0018,0060) 2 COPY for interpolation EMPTY otherwise
Acquisition Number (0020,0012) 2 EMPTY
ViewRay Incorporated ViewRay™ System 32
Attribute Name Tag Type Value Handling
Scan Options (0018,0022) 3 COPY for interpolation ANAP otherwise
Data Collection Diameter (0018,0090) 3 COPY for interpolation ANAP otherwise
Data Collection Center (Patient) (0018,9313) 3 COPY for interpolation ANAP otherwise
Reconstruction Diameter (0018,1100) 3 COPY for interpolation ANAP otherwise
Reconstruction Target Center (Patient) (0018,9318) 3 COPY for interpolation ANAP otherwise
Distance Source to Detector (0018,1110) 3 COPY for interpolation ANAP otherwise
Distance Source to Patient (0018,1111) 3 COPY for interpolation ANAP otherwise
Gantry/Detector Tilt (0018,1120) 3 COPY for interpolation ANAP otherwise
Table Height (0018,1130) 3 COPY for interpolation ANAP otherwise
Rotation Direction (0018,1140) 3 COPY for interpolation ANAP otherwise
Exposure Time (0018,1150) 3 COPY for interpolation ANAP otherwise
X-Ray Tube Current (0018,1151) 3 COPY for interpolation ANAP otherwise
Exposure (0018,1152) 3 COPY for interpolation ANAP otherwise
Exposure in As (0018,1153) 3 COPY for interpolation ANAP otherwise
Filter Type (0018,1160) 3 COPY for interpolation ANAP otherwise
Generator Power (0018,1170) 3 COPY for interpolation ANAP otherwise
Focal Spot (0018,1190) 3 COPY for interpolation ANAP otherwise
Convolution Kernel (0018,1210) 3 COPY for interpolation ANAP otherwise
Revolution Time (0018,9305) 3 COPY for interpolation ANAP otherwise
Single Collimation Width (0018,9306) 3 COPY for interpolation ANAP otherwise
Total Collimation Width (0018,9307) 3 COPY for interpolation ANAP otherwise
Table Speed (0018,9309) 3 COPY for interpolation ANAP otherwise
Table Feed per Rotation (0018,9310) 3 COPY for interpolation ANAP otherwise
ViewRay Incorporated ViewRay™ System 33
Attribute Name Tag Type Value Handling
Spiral Pitch Factor (0018,9311) 3 COPY for interpolation ANAP otherwise
Exposure Modulation Type (0018,9323) 3 COPY for interpolation ANAP otherwise
Estimated Dose Saving (0018,9324) 3 COPY for interpolation ANAP otherwise
CTDIvol (0018,9345) 3 COPY for interpolation ANAP otherwise
CTDI Phantom Type Code Sequence (0018,9346) 3 COPY for interpolation ANAP otherwise
>Include Code Sequence Macro [Table 8.8-1]
Anatomic Region Sequence (0008,2218) 3 ANAP
>Include ‘Code Sequence Macro’ Table [8.8-1]
>Anatomic Region Modifier Sequence (0008,2220) 3
>>Include ‘Code Sequence Macro’ [Table 8.8-1]
Primary Anatomic Structure Sequence (0008,2228) 3 ANAP
>Include ‘Code Sequence Macro’ [Table 8.8-1]
>Primary Anatomic Structure Modifier Sequence
(0008,2230) 3
>>Include ‘Code Sequence Macro’ [Table 8.8-1]
Calcium Scoring Mass Factor Patient (0018,9351) 3 COPY for interpolation ANAP otherwise
Calcium Scoring Mass Factor Device (0018,9352) 3 COPY for interpolation ANAP otherwise
CT Additional X-Ray Source Sequence (0018,9360) 3 COPY for interpolation ANAP otherwise >kVP (0018,0060) 1
>X-Ray Tube Current in mA (0018,9330) 1
>Data Collection Diameter (0018,0090) 1
>Focal Spot(s) (0018,1190) 1
>Filter Type(s) (0018,1160) 1
>Filter Material (0018,7050) 1
B.2.11 MR Image Module [C.8.3.1]
Attribute Name Tag Type Value Handling
Image Type (0008,0008) 1 Values 3 and 4 are copied for interpolation. Value 3 is “OTHER” and value 4 is not sent otherwise.
Samples per Pixel (0028,0002) 1 Send as described in section B.2.6
Photometric Interpretation (0028,0004) 1
Bits Allocated (0028,0100) 1
ViewRay Incorporated ViewRay™ System 34
Attribute Name Tag Type Value Handling
Scanning Sequence (0018,0020) 1 COPY for interpolation and registration AUTO for new images
Sequence Variant (0018,0021) 1 COPY for interpolation and registration AUTO for new images
Scan Options (0018,0022) 2 COPY for interpolation EMPTY otherwise
MR Acquisition Type (0018,0023) 2 COPY for interpolation EMPTY otherwise
Repetition Time (0018,0080) 2C COPY for interpolation EMPTY otherwise
Echo Time (0018,0081) 2 COPY for interpolation EMPTY otherwise
Echo Train Length (0018,0091) 2 COPY for interpolation EMPTY otherwise
Inversion Time (0018,0082) 2C COPY for interpolation EMPTY otherwise
Trigger Time (0018,1060) 2C COPY for interpolation EMPTY otherwise
Sequence Name (0018,0024) 3 COPY for interpolation ANAP otherwise
Angio Flag (0018,0025) 3 COPY for interpolation ANAP otherwise
Number of Averages (0018,0083) 3 COPY for interpolation ANAP otherwise
Imaging Frequency (0018,0084) 3 COPY for interpolation ANAP otherwise
Imaged Nucleus (0018,0085) 3 COPY for interpolation ANAP otherwise
Echo Number (0018,0086) 3 COPY for interpolation ANAP otherwise
Magnetic Field Strength (0018,0087) 3 COPY for interpolation ANAP otherwise
Spacing Between Slices (0018,0088) 3 COPY for interpolation ANAP otherwise
Number of Phase Encoding Steps (0018,0089) 3 COPY for interpolation ANAP otherwise
Percent Sampling (0018,0093) 3 COPY for interpolation ANAP otherwise
Percent Phase Field of View (0018,0094) 3 COPY for interpolation ANAP otherwise
Pixel Bandwidth (0018,0095) 3 COPY for interpolation ANAP otherwise
Nominal Interval (0018,1062) 3 COPY for interpolation ANAP otherwise
ViewRay Incorporated ViewRay™ System 35
Attribute Name Tag Type Value Handling
Beat Rejection Flag (0018,1080) 3 COPY for interpolation ANAP otherwise
Low R-R Value (0018,1081) 3 COPY for interpolation ANAP otherwise
High R-R Value (0018,1082) 3 COPY for interpolation ANAP otherwise
Intervals Acquired (0018,1083) 3 COPY for interpolation ANAP otherwise
Intervals Rejected (0018,1084) 3 COPY for interpolation ANAP otherwise
PVC Rejection (0018,1085) 3 COPY for interpolation ANAP otherwise
Skip Beats (0018,1086) 3 COPY for interpolation ANAP otherwise
Heart Rate (0018,1088) 3 COPY for interpolation ANAP otherwise
Cardiac Number of Images (0018,1090) 3 COPY for interpolation ANAP otherwise
Trigger Window (0018,1094) 3 COPY for interpolation ANAP otherwise
Reconstruction Diameter (0018,1100) 3 COPY for interpolation ANAP otherwise
Receive Coil Name (0018,1250) 3 COPY for interpolation ANAP otherwise
Transmit Coil Name (0018,1251) 3 COPY for interpolation ANAP otherwise
Acquisition Matrix (0018,1310) 3 COPY for interpolation ANAP otherwise
In-plane Phase Encoding Direction (0018,1312) 3 COPY for interpolation ANAP otherwise
Flip Angle (0018,1314) 3 COPY for interpolation ANAP otherwise
SAR (0018,1316) 3 COPY for interpolation ANAP otherwise
Variable Flip Angle Flag (0018,1315) 3 COPY for interpolation ANAP otherwise
dB/dt (0018,1318) 3 COPY for interpolation ANAP otherwise
Temporal Position Identifier (0020,0100) 3 COPY for interpolation ANAP otherwise
Number of Temporal Positions (0020,0105) 3 COPY for interpolation ANAP otherwise
Temporal Resolution (0020,0110) 3 COPY for interpolation ANAP otherwise
Anatomic Region Sequence (0008,2218) 3 ANAP
>Include ‘Code Sequence Macro’ [Table 8.8-1]
ViewRay Incorporated ViewRay™ System 36
Attribute Name Tag Type Value Handling
>Anatomic Region Modifier Sequence (0008,2220) 3
>>Include ‘Code Sequence Macro’ [Table 8.8-1]
Primary Anatomic Structure Sequence (0008,2228) 3 ANAP
>Include ‘Code Sequence Macro’ [Table 8.8-1]
>Primary Anatomic Structure Modifier Sequence
(0008,2230) 3
>>Include ‘Code Sequence Macro’ [Table 8.8-1]
B.2.12 NM/PET Patient Orientation Module [C.8.4.6]
Attribute Name Tag Type Value Handling
Patient Orientation Code Sequence (0054,0410) 2 COPY
>Include ‘Code Sequence Macro’ [Table 8.8-1]
> Patient Orientation Modifier Code Sequence
(0054,0412) 2C
>>Include ‘Code Sequence Macro’ [Table 8.8-1]
Patient Gantry Relationship Code Sequence
(0054,0414) 2 COPY
>Include ‘Code Sequence Macro’ [Table 8.8-1]
B.2.13 RT Series Module [C.8.8.1]
Attribute Name Tag Type Value Handling
Modality (0008,0060) 1 AUTO
Series Instance UID (0020,000E) 1 AUTO
Series Number (0020,0011) 2 EMPTY
Series Description (0008,103E) 3 COPY for interpolation ANAP AUTO otherwise
Referenced Performed Procedure Step Sequence
(0008,1111) 3 ANAP
>Include ‘SOP Instance Reference Macro' [Table 10-11]
Request Attributes Sequence (0040,0275) 3 ANAP
>Include Request Attributes Macro [Table 10-9]
Performed Procedure Step ID (0040,0253) 3 ANAP
Performed Procedure Step Start Date (0040,0244) 3 ANAP
Performed Procedure Step Start Time (0040,0245) 3 ANAP
Performed Procedure Step Description (0040,0254) 3 ANAP
Performed Protocol Code Sequence (0040,0260) 3 ANAP
>Include ‘Code Sequence Macro’ [Table 8.8-1]
ViewRay Incorporated ViewRay™ System 37
Attribute Name Tag Type Value Handling
>Protocol Context Sequence (0040,0440) 3 ANAP
>>Include ‘Content Item Macro’ [Table 10-2]
>> Content Item Modifier Sequence (0040,0441) 3 ANAP
>>>Include ‘Content Item Macro’ [Table 10-2]
Comments on the Performed Procedure Step
(0040,0280) 3 ANAP
B.2.14 RT Dose Module [C.8.8.3]
Attribute Name Tag Type Value Handling
Samples per Pixel (0028,0002) 1C The value 1 is always given
Photometric Interpretation (0028,0004) 1C The value MONOCHROME2 is always given
Bits Allocated (0028,0100) 1C The value 16 is always given
Bits Stored (0028,0101) 1C The value 16 is always given
High Bit (0028,0102) 1C The value 15 is always given
Pixel Representation (0028,0103) 1C COPY for interpolation The value 0 (Unsigned) is always given otherwise
Dose Units (3004,0002) 1 COPY for interpolation The value GY is always given otherwise
Dose Type (3004,0004) 1 COPY for interpolation The value PHYSICAL is always given otherwise
Instance Number (0020,0013) 3 COPY for interpolation ANAP otherwise
Dose Comment (3004,0006) 3 COPY for interpolation ANAP otherwise
Normalization Point (3004,0008) 3 COPY for interpolation ANAP otherwise
Dose Summation Type (3004,000A) 1 COPY for interpolation PLAN of FRACTION otherwise depending on the source of the data
Referenced RT Plan Sequence (300C,0002) 1C COPY for interpolation AUTO otherwise
>Include ‘SOP Instance Reference Macro' [Table 10-11]
>Referenced Fraction Group Sequence (300C,0020) 1C
>>Referenced Fraction Group Number (300C,0022) 1
>>Referenced Beam Sequence (300C,0004) 1C
>>>Referenced Beam Number (300C,0006) 1
>>>Referenced Control Point Sequence
(300C,00F2) 1C
ViewRay Incorporated ViewRay™ System 38
Attribute Name Tag Type Value Handling
>>>>Referenced Start Control Point Index
(300C,00F4) 1
>>>>Referenced Stop Control Point Index
(300C,00F6) 1
>>Referenced Brachy Application Setup Sequence
(300C,000A) 1C
>>>Referenced Brachy Application Setup Number
(300C,000C) 1
Grid Frame Offset Vector (3004,000C) 1C COPY for interpolation The plane location of each frame relative to the first frame (option a in [C.8.8.3.2]) otherwise.
Dose Grid Scaling (3004,000E) 1 AUTO
Tissue Heterogeneity Correction (3004,0014) 3 COPY for interpolation ANAP otherwise.
B.2.15 Structure Set Module [C.8.8.5]
Attribute Name Tag Type Value Handling
Structure Set Label (3006,0002) 1 DB – Matches the plan label
Structure Set Name (3006,0004) 3 ANAP
Structure Set Description (3006,0006) 3 ANAP
Instance Number (0020,0013) 3 ANAP
Structure Set Date (3006,0008) 2 AUTO
Structure Set Time (3006,0009) 2 AUTO
Referenced Frame of Reference Sequence
(3006,0010) 3
>Frame of Reference UID (0020,0052) 1 AUTO - Matches the frame of reference UID of the primary image set
>Frame of Reference Relationship Sequence
(3006,00C0) 3 ANAP
>>Related Frame of Reference UID (3006,00C2) 1
>>Frame of Reference Transformation Type
(3006,00C4) 1C
>>Frame of Reference Transformation Matrix
(3006,00C6) 1
>>Frame of Reference Transformation Comment
(3006,00C8) 3
>RT Referenced Study Sequence (3006,0012) 3 ANAP
>>Include ‘SOP Instance Reference Macro' [Table 10-11]
>>RT Referenced Series Sequence (3006,0014) 1
>>>Series Instance UID (0020,000E) 1
ViewRay Incorporated ViewRay™ System 39
Attribute Name Tag Type Value Handling
>>>Contour Image Sequence (3006,0016) 1
>>>>Include ‘Image SOP Instance Reference Macro’ [Table 10-3]
Structure Set ROI Sequence (3006,0020) 3
>ROI Number (3006,0022) 1 AUTO
>Referenced Frame of Reference UID (3006,0024) 1 AUTO
>ROI Name (3006,0026) 2 DB
>ROI Description (3006,0028) 3 DB
>ROI Volume (3006,002C) 3 ANAP
>ROI Generation Algorithm (3006,0036) 2 EMPTY
>ROI Generation Description (3006,0038) 3 ANAP
B.2.16 ROI Contour Module [C.8.8.5]
Attribute Name Tag Type Value Handling
ROI Contour Sequence (3006,0039) 1 Introduces sequence of Contour Sequences defining ROIs. One or more items may be included in this sequence.
>Referenced ROI Number (3006,0084) 1 AUTO
>ROI Display Color (3006,002A) 3 DB
>Contour Sequence (3006,0040) 3
>>Contour Number (3006,0048) 3 ANAP
>>Attached Contours (3006,0049) 3 ANAP
>>Contour Image Sequence (3006,0016) 3 ANAP
>>>Include ‘Image SOP Instance Reference Macro’ [Table 10-3]
>>Contour Geometric Type (3006,0042) 1 CLOSED_PLANAR or POINT depending on data
>>Contour Slab Thickness (3006,0044) 3 ANAP
>>Contour Offset Vector (3006,0045) 3 ANAP
>>Number of Contour Points (3006,0046) 1 AUTO
>>Contour Data (3006,0050) 1 DB
B.2.17 RT Dose ROI [C.8.8.7]
Attribute Name Tag Type Value Handling
RT Dose ROI Sequence (3004,0010) 1
>Referenced ROI Number (3006,0084) 1 AUTO
>Dose Units (3004,0002) 1 The value GY is always given
ViewRay Incorporated ViewRay™ System 40
Attribute Name Tag Type Value Handling
>Dose Value (3004,0012) 1 The dose at the user-selected point
B.2.18 RT ROI Observations [C.8.8.8]
Attribute Name Tag Type Value Handling
RT ROI Observations Sequence (3006,0080) 1
>Observation Number (3006,0082) 1 AUTO
>Referenced ROI Number (3006,0084) 1 AUTO
>ROI Observation Label (3006,0085) 3 ANAP
>ROI Observation Description (3006,0088) 3 ANAP
>RT Related ROI Sequence (3006,0030) 3 ANAP
>>Referenced ROI Number (3006,0084) 1 ANAP
>>RT ROI Relationship (3006,0033) 3
>RT ROI Identification Code Sequence (3006,0086) 3 ANAP
>>Include ‘Code Sequence Macro’ [Table 8.8-1]
>Related RT ROI Observations Sequence
(3006,00A0) 3 ANAP
>>Observation Number (3006,0082) 1
>RT ROI Interpreted Type (3006,00A4) 2 EMPTY
>ROI Interpreter (3006,00A6) 2 EMPTY
>Material ID (300A,00E1) 3 ANAP
>ROI Physical Properties Sequence (3006,00B0) 3 ANAP
>>ROI Physical Property (3006,00B2) 1
>>ROI Elemental Composition Sequence
(3006,00B6) 1C
>>>ROI Elemental Composition Atomic Number
(3006,00B7) 1
>>>ROI Elemental Composition Atomic Mass Fraction
(3006,00B8) 1
>>ROI Physical Property Value (3006,00B4) 1
B.2.19 PET Series [C.8.9.1]
Attribute Name Tag Type Value Handling
Series Date (0008,0021) 1 COPY
Series Time (0008,0031) 1 COPY
Units (0054,1001) 1 COPY
Counts Source (0054,1002) 1 COPY
ViewRay Incorporated ViewRay™ System 41
Attribute Name Tag Type Value Handling
Series Type (0054,1000) 1 COPY for interpolation The value STATIC is always given for registration.
Reprojection Method (0054,1004) 2C COPY
Number of R-R Intervals (0054,0061) 1C COPY
Number of Time Slots (0054,0071) 1C COPY
Number of Time Slices (0054,0101) 1C COPY
Number of Slices (0054,0081) 1 COPY
Corrected Image (0028,0051) 2 COPY
Randoms Correction Method (0054,1100) 3 COPY
Attenuation Correction Method (0054,1101) 3 COPY
Scatter Correction Method (0054,1105) 3 COPY
Decay Correction (0054,1102) 1 COPY
Reconstruction Diameter (0018,1100) 3 COPY
Convolution Kernel (0018,1210) 3 COPY
Reconstruction Method (0054,1103) 3 COPY
Detector Lines of Response Used (0054,1104) 3 COPY
Acquisition Start Condition (0018,0073) 3 COPY
Acquisition Start Condition Data (0018,0074) 3 COPY
Acquisition Termination Condition (0018,0071) 3 COPY
Acquisition Termination Condition Data
(0018,0075) 3 COPY
Field of View Shape (0018,1147) 3 COPY
Field of View Dimensions (0018,1149) 3 COPY
Gantry/Detector Tilt (0018,1120) 3 COPY
Gantry/Detector Slew (0018,1121) 3 COPY
Type of Detector Motion (0054,0202) 3 COPY
Collimator Type (0018,1181) 2 COPY
Collimator/Grid Name (0018,1180) 3 COPY
Axial Acceptance (0054,1200) 3 COPY
Axial Mash (0054,1201) 3 COPY
Transverse Mash (0054,1202) 3 COPY
Detector Element Size (0054,1203) 3 COPY
Coincidence Window Width (0054,1210) 3 COPY
Energy Window Range Sequence (0054,0013) 3
>Energy Window Lower Limit (0054,0014) 3 COPY
ViewRay Incorporated ViewRay™ System 42
Attribute Name Tag Type Value Handling
>Energy Window Upper Limit (0054,0015) 3 COPY
Secondary Counts Type (0054,1220) 3 COPY
B.2.20 PET Isotope Module [C.8.9.2]
Attribute Name Tag Type Value Handling
Radiopharmaceutical Information Sequence
(0054,0016) 2 COPY
>Radionuclide Code Sequence (0054,0300) 2
>>Include ‘Code Sequence Macro’ [Table 8.8-1]
>Radiopharmaceutical Route (0018,1070) 3
>Administration Route Code Sequence (0054,0302) 3
>>Include ‘Code Sequence Macro’[ Table 8.8-1]
>Radiopharmaceutical Volume (0018,1071) 3
>Radiopharmaceutical Start Time (0018,1072) 3
>Radiopharmaceutical Start DateTime (0018,1078) 3
>Radiopharmaceutical Stop Time (0018,1073) 3
>Radiopharmaceutical Stop DateTime (0018,1079) 3
>Radionuclide Total Dose (0018,1074) 3
>Radionuclide Half Life (0018,1075) 3
>Radionuclide Positron Fraction (0018,1076) 3
>Radiopharmaceutical Specific Activity (0018,1077) 3
>Radiopharmaceutical (0018,0031) 3
>Radiopharmaceutical Code Sequence (0054,0304) 3
>>Include ‘Code Sequence Macro’ [Table 8.8-1]
Intervention Drug Information Sequence
(0018,0026) 3
>Intervention Drug Name (0018,0034) 3
>Intervention Drug Code Sequence (0018,0029) 3
>>Include ‘Code Sequence Macro’ [Table 8.8-1]
>Intervention Drug Start Time (0018,0035) 3
>Intervention Drug Stop Time (0018,0027) 3
>Intervention Drug Dose (0018,0028) 3
ViewRay Incorporated ViewRay™ System 43
B.2.21 PET Image Module [C.8.9.4]
Attribute Name Tag Type Value Handling
Image Type (0008,0008) 1 Assigned as described in section B.2.6
Samples per Pixel (0028,0002) 1 Assigned as described in section B.2.8 Photometric Interpretation (0028,0004) 1
Bits Allocated (0028,0100) 1
Bits Stored (0028,0101) 1
High Bit (0028,0102) 1
Rescale Intercept (0028,1052) 1 AUTO
Rescale Slope (0028,1053) 1 AUTO
Frame Reference Time (0054,1300) 1 EMPTY – This data is not available after interpolation or registration
Trigger Time (0018,1060) 1C ANAP
Frame Time (0018,1063) 1C ANAP
Low R-R Value (0018,1081) 1C COPY for interpolation ANAP otherwise
High R-R Value (0018,1082) 1C COPY for interpolation ANAP otherwise
Lossy Image Compression (0028,2110) 1C ANAP
Image Index (0054,1330) 1 AUTO
Acquisition Date (0008,0022) 2 EMPTY
Acquisition Time (0008,0032) 2 EMPTY
Actual Frame Duration (0018,1242) 2 EMPTY
Nominal Interval (0018,1062) 3 ANAP
Intervals Acquired (0018,1083) 3 ANAP
Intervals Rejected (0018,1084) 3 ANAP
Primary (Prompts) Counts Accumulated
(0054,1310) 3 ANAP
Secondary Counts Accumulated (0054,1311) 3 ANAP
Slice Sensitivity Factor (0054,1320) 3 ANAP
Decay Factor (0054,1321) 1C ANAP
Dose Calibration Factor (0054,1322) 3 ANAP
Scatter Fraction Factor (0054,1323) 3 ANAP
Dead Time Factor (0054,1324) 3 ANAP
Anatomic Region Sequence (0008,2218) 3 ANAP
>Include ‘Code Sequence Macro’ [Table 8.8-1]
>Anatomic Region Modifier Sequence (0008,2220) 3
ViewRay Incorporated ViewRay™ System 44
Attribute Name Tag Type Value Handling
>>Include ‘Code Sequence Macro’ [Table 8.8-1]
Primary Anatomic Structure Sequence (0008,2228) 3 ANAP
>Include ‘Code Sequence Macro’ [Table 8.8-1]
>Primary Anatomic Structure Modifier Sequence
(0008,2230) 3
>>Include ‘Code Sequence Macro’ [Table 8.8-1]
Slice Progression Direction (0054,0500) 3 ANAP
View Code Sequence (0054,0220) 3 ANAP
> Include ‘Code Sequence Macro’ [Table 8.8-1]
> View Modifier Code Sequence (0054,0222) 2C
>> Include ‘Code Sequence Macro’ [Table 8.8-1]
B.2.22 SOP Common Module [C.12.1]
Attribute Name Tag Type Value Handling
SOP Class UID (0008,0016) 1 AUTO
SOP Instance UID (0008,0018) 1 AUTO
Specific Character Set (0008,0005) 1C ANAP – Only the default character repertoire is supported
Instance Creation Date (0008,0012) 3 ANAP
Instance Creation Time (0008,0013) 3 ANAP
Instance Creator UID (0008,0014) 3 ANAP
Related General SOP Class UID (0008,001A) 3 ANAP
Original Specialized SOP Class UID (0008,001B) 3 ANAP
Coding Scheme Identification Sequence
(0008,0110) 3 ANAP
>Coding Scheme Designator (0008,0102) 1
>Coding Scheme Registry (0008,0112) 1C
>Coding Scheme UID (0008,010C) 1C
>Coding Scheme External ID (0008,0114) 2C
>Coding Scheme Name (0008,0115) 3
>Coding Scheme Version (0008,0103) 3
>Coding Scheme Responsible Organization
(0008,0116) 3
Timezone Offset From UTC (0008,0201) 3 ANAP
Contributing Equipment Sequence (0018,A001) 3 ANAP
>Purpose of Reference Code Sequence (0040,A170) 1
>>Include ‘Code Sequence Macro’ [Table 8.8-1]
ViewRay Incorporated ViewRay™ System 45
Attribute Name Tag Type Value Handling
>Manufacturer (0008,0070) 1
>Institution Name (0008,0080) 3
>Institution Address (0008,0081) 3
>Station Name (0008,1010) 3
>Institutional Department Name (0008,1040) 3
>Manufacturer’s Model Name (0008,1090) 3
>Device Serial Number (0018,1000) 3
>Software Versions (0018,1020) 3
>Spatial Resolution (0018,1050) 3
>Date of Last Calibration (0018,1200) 3
>Time of Last Calibration (0018,1201) 3
>Contribution DateTime (0018,A002) 3
>Contribution Description (0018,A003) 3
Instance Number (0020,0013) 3 ANAP
SOP Instance Status (0100,0410) 3 ANAP
SOP Authorization Date and Time (0100,0420) 3 ANAP
SOP Authorization Comment (0100,0424) 3 ANAP
Authorization Equipment Certification Number
(0100,0426) 3 ANAP
Include ‘Digital Signatures Macro’ [Table C.12-6]
Encrypted Attributes Sequence (0400,0500) 1C ANAP
>Encrypted Content Transfer Syntax UID
(0400,0510) 1
>Encrypted Content (0400,0520) 1
Original Attributes Sequence (0400,0561) 3 ANAP
>Source of Previous Values (0400,0564) 2
>Attribute Modification DateTime (0400,0562) 1
>Modifying System (0400,0563) 1
>Reason for the Attribute Modification
(0400,0565) 1
>Modified Attributes Sequence (0400,0550) 1
HL7 Structured Document Reference Sequence
(0040,A390) 1C ANAP
>Referenced SOP Class UID (0008,1150) 1
>Referenced SOP Instance UID (0008,1155) 1
>HL7 Instance Identifier (0040,E001) 1
>Retrieve URI (0040,E010) 3