TrueBeam Treatment Delivery Console 4.

0
4D Integrated Treatment Console 13.0
DICOM Conformance Statement

Version 7.0

L4472 Rev 0
P1064013-001-A APRIL 2023
 Publication ID
P1064013-001-A

Publication Title
TrueBeam Treatment Delivery Console V4.0 DICOM Conformance Statement

Abstract
The document provides information about DICOM conformance with TrueBeam 4.0 and 4D Integrated Treatment Console
13.0.
This publication is the English-language original.

Trademarks
Varian Medical Systems, Inc. or its affiliates own the names of our products and services referenced herein. These names are
either registered trademarks (®) or trademarks (™) in the United States and/or other countries. All other trademarks are the
property of their respective owners. Any rights not expressly granted herein are reserved.

Copyright
© 2023 Varian Medical Systems, Inc. All rights reserved. Published in the United States of America.
No part of this publication may be reproduced, translated, or transmitted without the express written permission of Varian
Medical Systems, Inc.

Notice
Information in this publication is subject to change without notice and does not represent a commitment on the part of Varian.

Electronic Labeling
This symbol on the label indicates that the Instructions for Use for the corresponding product are available at
www.MyVarian.com. Access the Instructions for Use in electronic form by logging in with your assigned MyVarian user
credentials.
In compliance with Anvisa and EU regulations, Varian will send Brazil and EU customers a
free printed copy of the Instructions for Use within 7 days. Use the “Paper Publication
Request” form provided on the Varian webpage to order your copy.

Legal Manufacturer
Varian Medical Systems, Inc.
3100 Hansen Way
Palo Alto, CA 94304
United States of America

Contact Varian Customer Support / Report Incidents

For customer support, go to www.MyVarian.com and select Contact Us. Use MyVarian to report incidents. If you do not have
access to MyVarian, contact your local representative or call +41-41-749-8844.
Any serious incident that has occurred while using the device should be reported to the manufacturer and the competent
authority of the Member State in which the user or patient is established.

FDA 21 CFR 820 Quality System Regulations (cGMPs)

Varian Medical Systems, Oncology Systems products are designed and manufactured in accordance with the requirements
specified within this federal regulation.

CAUTION: US Federal law restricts this device to sale by or on the order of a physician.

WHO
ICD-O codes and terms used by permission of WHO, from:
• International Classification of Diseases for Oncology, Third Edition.
ICD-10 codes and terms used by permission of WHO, from:
• International Statistical Classification of Diseases and Related Health Problems, Tenth Revision (ICD-10).

2 of 151 Varian Treatment Delivery Console

 EU REACH SVHC Disclosure
The link to the current EU REACH SVHC disclosure statement can be found at
http://www.varian.com/us/corporate/legal/reach.html

ISO 13485
Varian Medical Systems, Oncology Systems products are designed and manufactured in accordance with the requirements
specified within the ISO 13485 quality standard.

Medical Device

Authorized Representative in the EU

Varian Medical Systems Nederland B.V.
Kokermolen 2
3994 DH Houten
The Netherlands

DICOM Conformance Statement 3 of 151

Document History

Version: Date: Changes, Remarks

1.0 July 28, 2014 Initial version
1.1 Oct 19, 2015 Added Frame of Reference for TB 2.5 MR2
2.0 Jan 04, 2016 Ready for Approval
2.1 May 31, 2016 Added support for Delta Couch, Unicode and updated
SetupTechnique. Maximum Treatment Time is not
supported TrueBeam 2.7 onwards.
3.0 June 15, 2016 Ready for Approval
4.0 October 10, 2016 Re approval after one documentation comment
correction.
5.0 June 06, 2018 Treatment record now sends back MLC leaf position
values for each control point.

6.0 August 04, 2021 Treatment record only reports two control points.
7.0 April 04, 2023 Interlock sequence, Beam Gating Hold Device gating
sequence and Treatment sites support added to
TrueBeam 4.0

4 of 151 Varian Treatment Delivery Console

Contents

Document History .............................................................................................. 4

1. Introduction 8
1.1 Audience ...................................................................................................... 8
1.2 Scope ............................................................................................................ 8
1.3 Visual Cues .................................................................................................. 8
1.4 Contact Varian Customer Support ............................................................. 9
1.5 Definitions .................................................................................................. 10
1.6 Related Documents ................................................................................... 10
2. Implementation Model ............................................................................... 11
2.1 Application Data Flow Diagram ................................................................ 11
2.2 Functional Definition of AE’s .................................................................... 14
2.3 Sequencing of Real-World Activities ....................................................... 14
3. AE Specifications ....................................................................................... 16
3.1 Treatment Delivery Console Entity Specification ................................... 16
3.1.1 Association Establishment Policies.................................................... 16
3.1.2 Association Initiation Policy ............................................................... 19
3.1.3 Load and Save of Imager Positions ................................................... 21
3.1.4 RT Image Position vs. Imager Position in cation Image Sequence” .. 22
3.1.5 Primary Fluence Mode....................................................................... 22
3.1.6 Association Acceptance Policy .......................................................... 28
4. Communication profiles ............................................................................ 31
4.1 Supported communications stacks ......................................................... 31
4.1.1 TCP/IP stack ...................................................................................... 31
5. Configuration .............................................................................................. 32
5.1 4DITC DICOM Configuration ..................................................................... 32
5.1.1 AE Title/Presentation Address Mapping ............................................ 32
5.1.2 Configurable Parameters ................................................................... 32
5.2 Treatment delivery console DICOM Configuration ................................. 33
6. Media Interchange ...................................................................................... 34
7. Support of Extended Character Sets ....................................................... 34
8. Security 34
8.1 Security Profiles ........................................................................................ 34
8.2 Association Level Security ....................................................................... 34
8.3 Application Level Security ........................................................................ 34
Specialization ........................................................................ 35
DICOM Conformance Statement 5 of 151
 A.1 IOD Contents .............................................................................................. 35
A.1.1 Created SOP Instances ..................................................................... 35
A.1.2 Usage of Attributes from received IOD’s............................................ 35
A.2 Data Dictionary of Private Attributes ....................................................... 37
A.2.1 Privatization for RT Plan Storage SOP class ..................................... 37
A.2.2 Privatization for RT Beams Treatment Record Storage SOP class ... 39
A.2.3 Privatization for RT Treatment Summary Record Storage SOP ........ 40
DICOM Query Retrieve Service Class Object Matching ... 41
B.1 IOD Specific Matching Criteria ................................................................. 41
B.1.1 Supported Keys ................................................................................. 42
IOD Details ............................................................................. 45
C.1 Supported IODs ......................................................................................... 45
C.2 Modules and Attributes ............................................................................. 49
C.2.1 Patient – C.7.1.1 ................................................................................ 49
C.2.2 General Study - C.7.2.1 ..................................................................... 51
C.2.3 Frame of Reference – C.7.4.1 ........................................................... 58
C.2.4 General Equipment – C.7.5.1 ............................................................ 58
C.2.5 RT Series – C.8.8.1 ........................................................................... 60
C.2.6 RT General Plan – C.8.8.9 ................................................................ 68
C.2.7 RT Prescription – C.8.8.10 ................................................................ 71
C.2.8 RT Tolerance Tables – C.8.8.11 ........................................................ 74
C.2.9 RT Patient Setup – C.8.8.12 .............................................................. 76
C.2.10 RT Fraction Scheme – C.8.8.13 ........................................................ 81
C.2.11 RT Beams – C.8.8.14 ........................................................................ 86
C.2.12 Approval – C.8.8.16 ......................................................................... 114
C.2.13 RT General Treatment Record – C.8.8.17 ....................................... 115
C.2.14 RT Beams Session Record – C.8.8.21 ............................................ 115
C.2.15 SOP Common – C.12.1 ................................................................... 132
C.2.16 Extended Interface – Private ........................................................... 142
Extended Interface .............................................................. 145
D.1 RT Plan ..................................................................................................... 145
D.2 RT Beams Treatment Record ................................................................. 148

6 of 151 Varian Treatment Delivery Console

Table of Figures

Figure 1: SCU Role Application Data Flow Diagram for Loading Patient 12
Figure 2: SCP Role Application Data Flow Diagram for Loading 13
Figure 3: SCU Role Application Data Flow Diagram for Saving Patient Data 14
Figure 4: Associations Used for 4DITC 17
Figure 5: 4DITC Administration Setup 32
Figure 6: AE Title/Presentation Address Mapping 33

DICOM Conformance Statement 7 of 151

1. Introduction
The definition of the DICOM standard for radiotherapy data started in 1994, and has now reached a
productive state. Today, DICOM is the primary choice for exchanging data with an open standard
protocol for the majority of vendors and institutions. Varian Medical Systems is committed to this
notion and supports the full range of radiotherapy objects (e.g. RT Plan, RT Image, RT Beams
Treatment Record) for their V & R system.
This conformance statement specifies the conformance of the TrueBeam Treatment delivery
console version 4.0 and 4D Integrated Treatment Console version 13.0 with the DICOM V 3.0
standard.

1.1 Audience
This document is intended for the following groups of persons:
Marketing and Sales.
System Integrators of medical equipment.
Other vendors interfacing via DICOM
It is assumed that the reader is familiar with the DICOM standard.

1.2 Scope
This Conformance Statement is applicable to the following Varian treatment delivery consoles:
TrueBeam Treatment Console version 4.0
4D Console version 13.0.
The general DICOM conformance statement for Varian Medical Systems products is defined in [2]
(see section 1.7).
This Conformance Statement describes only the specials and the variations as implemented in
TrueBeam Treatment delivery console version 4.0 and 4D Integrated Treatment Console version 13.0
The scope and format of this document are defined by Part 2 of the DICOM V3.0 standard. Some
sections defined in the standard that are not applicable to the software are left out for clarity.

1.3 Visual Cues

This document uses the following visual cues to help you locate and find information:

Note A note describes practices not related to physical injury.

CAUTION A caution describes a hazardous situation which, if not avoided,

could result in minor or moderate injury.

WARNING A warning describes a hazardous situation which, if not avoided,

could result in death or serious injury.

8 of 151 Varian Treatment Delivery Console

1.4 Contact Varian Customer Support
Varian Customer Support is available on the internet, by e-mail, and by telephone. Support services
are available without charge during the initial warranty period.
The MyVarian website provides contact information, product documentation, and other resources for
all Varian products.
1. Go to www.MyVarian.com.
2. Choose an option:
If you have an account, enter your User login information (email and password).
If you do not have an account, click Create New Account and follow the instructions.
Establishing an account may take up to two working days.
3. Click Contact Us at the top of the window to display customer support and training options, and
international e-mail addresses and telephone numbers.
4. From the Contact Us page, choose an option:
Call Varian Medical Systems support using a phone support number for your geographic area.
Complete the form corresponding to your request for use on a call with a live Varian
representative; then follow the instructions to complete the remote connect options, and click
Submit.
You can order documents by phone, request product or applications support, and report product-
related issues. Links on the MyVarian website navigate to other support resources for products,
services, and education.
5. To find documents, click Product Documentation.
Online documents in PDF format include customer technical bulletins (CTBs,) manuals, and customer
release notes (CRNs).

DICOM Conformance Statement 9 of 151

1.5 Definitions
This section provides the definitions of terms, acronyms, and abbreviations, which are used throughout
the document.
4DITC 4D Integrated Treatment Console
AE Application Entity
DB Database
DICOM Digital Imaging and Communications in Medicine
DIMSE DICOM Message Service element
DNS Domain Name System
EMPTY Attribute is sent without a value
IOD Information Object Definition
TrueBeam Varian Digital Platform
Management System DICOM entity from which TREATMENT DELIVERY
retrieves patient data
Multi-Frame Image Image that contains multiple two-dimensional pixel planes
NEMA National Electrical Manufacturers Association
PDU Protocol Data Unit (a DICOM term)
PVA Patient Verification Application (a TrueBeam Imaging
Application)
SCU Service Class User
SCP Service Class Provider
SOP Service Object Pair
TCP/IP Transmission Control Protocol / Internet Protocol
TXA TrueBeam Treatment Application
VNAP Value Not Always Present (attribute sent zero length if no
value is present)
VR Value Representation

1.6 Related Documents

NEMA PS3/ISO 12052,
Digital Imaging and Communications in Medicine (DICOM) Standard,
National Electrical Manufacturers Association (NEMA),
Rosslyn, Virginia, United States of America
https://www.dicomstandard.org/current/
ARIA Radiation Therapy Management 18.0 DICOM Conformance Statement
P/N P1061149
Varian Medical Systems International AG
Baden, Switzerland

10 of 151 Varian Treatment Delivery Console

2. Implementation Model
Three diagrams illustrating the application model, two for the SCU and one for the SCP role, are
shown in Figure 1, Figure 2, and Figure 3.

2.1 Application Data Flow Diagram

The initial function to load the plan into the treatment delivery console application is represented by
Load RT Plan (This function is typically performed by the application after the Patient and the Plan
UIDs have been received by the Management System). The treatment delivery console invokes a
move command for each DICOM RT Plan. This requires the treatment delivery console application to
provide the RT Plan Storage SCP. Figure 2 shows the Service Class Providers (SCP) role supported
by the treatment delivery console. The treatment delivery console then issues a move command to
request and retrieve the RT Treatment Summary Record. Based on the last fraction state, a find
command is executed to request the Load Beam Record Information (shown in Figure 1) to recover
from a partial treatment.
A Save issued by the operator will invoke a storage command, which requires the remote application
to provide a storage SCP as shown in Figure 3.
Closing the patient in the treatment delivery console will result in a Save if the plan data has been
modified and/or treatment records and images have been created. The treatment delivery console will
delete the objects temporarily stored. In case the Management System is not accessible, The
treatment delivery console will save the changes into one or several DICOM Media files.

DICOM Conformance Statement 11 of 151

 SCU Role SCP Role

Query/
Load RT Retrieve
Plan SCP
(C-Move)

Load RT Query/
Treatment Retrieve
Summary SCP
Record (C-Move)

Treatment
Delivery
Console
Query/
Load RT
Retrieve
Beams
SCP
Record
(C-Find)

Query/
Retrieve
Load RT
SCP
Image
(C-Move)

DICOM
Standard
Interface

Figure 1: SCU Role Application Data Flow Diagram for Loading Patient Data

12 of 151 Varian Treatment Delivery Console

 SCP Role SCU Role

RT Plan
Store Storage
Plan SCU

RT Treatment
Store RT
Summary
Treatment Treatment Record
summary Delivery Storage SCU
Record Console

RT
Store Image
image Storage
SCU

DICOM Standard
Interface

Figure 2: SCP Role Application Data Flow Diagram for Loading Patient Data

DICOM Conformance Statement 13 of 151

 SCU Role SCP Role

RT Plan
Store RT
Storage
Plan
SCP

Store RT RT Beams
Treatment Treatment
Beams
Delivery Record
Treatment
Console Storage
Record
SCP

RT
Store RT Image
Image Storage
SCP

DICOM Standard Interface

Figure 3: SCU Role Application Data Flow Diagram for Saving Patient Data

2.2 Functional Definition of AE’s

The treatment delivery console entity’s main responsibility is to execute a patient treatment. Before
treating, the treatment delivery console loads the patient data from the Management System using
DICOM services. After treating, the treatment delivery console generates RT Beams Treatment
Record(s) and RT Image(s). The treatment delivery console then stores them back to the Management
System again using DICOM services.
The treatment delivery console is also capable of modifying RT Plan(s) and/or creating new RT
Plan(s).

2.3 Sequencing of Real-World Activities

The treatment delivery console executes the activities for loading a patient in the following order.
1. C-Find RT Plan SOP class (see section 3.1.2.2.3.2).
2. C-Move RT Plan SOP class.
3. C-Move RT Treatment Summary Record SOP class.
4. C-Find RT Beams Treatment Record SOP class if needed.

14 of 151 Varian Treatment Delivery Console

 No C-Find RT Beams Treatment Record query is only executed in order to
te finalize the previous treated fraction.

The 4DITC console also retrieves referenced RT Images. The steps below only apply to
the 4DITC console.
5. C-Move RT Image SOP class (for Reference Images if referred in the RT Plan)
6. C-Find RT Image SOP class (for query Portal Images).
7. C-Move RT Image SOP class (for Portal Images if query returned Portal Image Instance
[UIDs]).

The only requirement is to load the RT Plan first before the others. This sequence may be performed
for more than one plan at the beginning of a treatment session.
The patient record is saved in the following order to treatment delivery console:
1. C-Store RT Plan SOP class (executed if a plan is changed in treatment delivery console).
2. C-Store RT Beams Treatment Record SOP class (executed if a beam was treated).
3. C-Store RT Image SOP class (executed if a Portal Image was acquired) (4DITC only).
The only requirement is to save RT Plans first before the RT Beam Records and RT Images. This is
because the RT Beams Treatment Record and/or RT Image may refer to the new RT Plan.

DICOM Conformance Statement 15 of 151

3. AE Specifications
3.1 Treatment Delivery Console Entity Specification
The treatment delivery console entity provides standard conformance to the following DICOM V3.0
SOP classes:

SOP Class Name SCU/SCP Role SOP Class UID

Verification (Echo) SCU / SCP 1.2.840.10008.1.1

RT Image Storage SCU / SCP 1.2.840.10008.5.1.4.1.1.481.1
RT Plan Storage SCU / SCP 1.2.840.10008.5.1.4.1.1.481.5
RT Treatment Summary SCP 1.2.840.10008.5.1.4.1.1.481.7
Record Storage
Study Root Query/Retrieve SCU 1.2.840.10008.5.1.4.1.2.2.1
information model- FIND
Study Root Query/Retrieve SCU 1.2.840.10008.5.1.4.1.2.2.2
information model- MOVE
RT Beams Treatment SCU 1.2.840.10008.5.1.4.1.1.481.4
Record Storage

Table 1: Supported SCU/SCP SOP Classes for the Treatment Delivery Console Entity

3.1.1 Association Establishment Policies

3.1.1.1 General
See details in Related Documents.
There are a total of three associations. The treatment delivery console establishes two associations
while the Management System establishes one association. The first association established by
treatment delivery console is to support the C-Move and C-Find services. The second association
established by treatment delivery console is to support the C-Store service. The association
established by the Management System is for storing patient data to treatment delivery console.
All of the association supports the C-Echo service to determine whether the association is still alive or
not.
A diagram of the associations is in Figure 4.
4DITC accepts any maximum PDU size for incoming data streams and suggests the size of 65536 for
outgoing data streams.

16 of 151 Varian Treatment Delivery Console

 C-Find/Move
C-Echo

C-Store RT Plan

Management System
C-Store RT Image
C-Store RT Treatment Summary
4DITC

Record
Association
C-Echo

C-Store RT Plan
C-Store RT Beams Treatment
Record
C-Store RT Image
C-Echo

Figure 4: Associations Used for 4DITC

3.1.1.2 Number of Associations

The treatment delivery consoles support a total of three associations as shown in Figure 4. They
support having one association for each batch of services at a time.
A batch of services refers to the list of services contained in an arrow in Figure 4.
3.1.1.3 Asynchronous Nature
Asynchronous operation is not supported.

DICOM Conformance Statement 17 of 151

3.1.1.4 Implementation identifying information

UID Value UID Name Notes

1.2.246.352.70.2.1.9 VMS Console System 6.5 SCU TrueBeam and 4DITC
(VMS Console Interface 1)
1.2.246.352.70.2.1.10 VMS Console System 6.5 SCP —
1.2.246.352.70.2.1.17 VMS Console Interface 3 4DITC 8.8 and higher
1.2.246.352.70.2.1.18 VMS Console System 8.8 SCP Treatment Daemon 8.8
1.2.246.352.70.2.1.19 VMS Console Interface 3 QA Mode 4DITC 8.8 (for QA
Mode) and higher
1.2.246.352.70.2.1.20 VMS Console System 8.8 QA Mode Treatment Daemon 8.8
SCP
1.2.246.352.70.2.1.81.4.1 VMS Console Interface 4 4DITC 10 and higher
1.2.246.352.70.2.1.82.4.1 VMS Treatment Daemon 10.0 SCP Treatment Daemon 10.0
1.2.246.352.70.2.1.81.4.2 VMS Console Interface 4 QA Mode 4DITC 10.0 (for QA
Mode) and higher
1.2.246.352.70.2.1.82.4.2 VMS Treatment Daemon 10.0 QA Treatment Daemon 10.0
Mode SCP
1.2.246.352.70.2.1.81.5.1 VMS Console Interface 5 4DITC 11 and higher
1.2.246.352.70.2.1.82.5.1 VMS Treatment Daemon 11.0 SCP Treatment Daemon 11
1.2.246.352.70.2.1.81.5.2 VMS Console Interface 5 QA Mode 4DITC 11 ( for QA
Mode) and higher
1.2.246.352.70.2.1.82.5.2 VMS Treatment Daemon 11.0 QA Treatment Daemon 11
Mode SCP
1.2.246.352.70.2.1.81.6.1 VMS Console Interface 6 4DITC 13 and higher
1.2.246.352.70.2.1.81.6.2 VMS Treatment Daemon 13.0 SCP Treatment Daemon 13
1.2.246.352.70.2.1.82.6.1 VMS Console Interface 6 QA Mode 4DITC 13 ( for QA
Mode) and higher
1.2.246.352.70.2.1.82.6.2 VMS Treatment Daemon 13.0 SCP Treatment Daemon 13

Table 2: 4DITC List of implementation UIDs and application support

1.2.246.352.70.2.1.9 VMS Console System 6.5 SCU —

(VMS Console Interface 1)
1.2.246.352.70.2.1.10 VMS Console System 6.5 SCP —
1.2.246.352.70.2.1.17 VMS Console Interface 3 —
1.2.246.352.70.2.1.18 VMS Console System 8.8 SCP —
1.2.246.352.70.2.1.19 VMS Console Interface 3 QA Mode —
1.2.246.352.70.2.1.20 VMS Console System 8.8 QA Mode —
SCP

Table 3: TrueBeam Treatment delivery console list of implementation UIDs supported and used

18 of 151 Varian Treatment Delivery Console

 3.1.2 Association Initiation Policy
The treatment delivery console entity will initiate one association for all Query/Retrieve Services (Q/R
SCU) that contains the C-Find and the C-Move service. When the user starts up 4DITC and clicks on
“Open Patient”, 4DITC initiates an association for all Query/Retrieve Services for the first time.
The 4DITC Entity will initiate one association for all Storage Services where it acts as a user (Storage
SCU). When the user clicks “Save Images” ("Save images" is applicable to 4DITC only) or “Close
Patient”, 4DITC checks if an association already exists for all Storage Services. If an association does
not exist for all Storage Services, 4DITC initiates an association for all Storage Services. Otherwise,
4DITC uses the existing association.
The Management System will initiate one association for all C-Store services used for sending all
patient data. In this association, 4DITC acts as a provider (Storage SCP).
The Echo/Verification service is used prior to any other DICOM service to verify whether an
established association exists.
3.1.2.1 Storage SCU

3.1.2.1.1 Associated Real-World Activity

The C-Store service is used by 4DITC to store patient data into the Management System. This service
gets executed whenever the operator selects ‘Close Patient’ or ‘Save Image’.

3.1.2.1.2 Presentation Context Table

Presentation Context Table

Abstract Syntax Transfer Syntax Role Extended TRUE 4DITC
Negotia- BEAM 13.0
tion 3.0
Name UID Name UID
RT Plan 1.2.840.10008.5. DICOM Implicit 1.2.840 SCU None Yes Yes
Storage 1.4.1.1.481.5 VR Little .10008.
Endian 1.2
RT Beams 1.2.840.10008.5. DICOM Implicit 1.2.840 SCU None Yes Yes
Treatment 1.4.1.1.481.4 VR Little .10008.
Record Endian 1.2
Storage
RT Image 1.2.840.10008.5. DICOM Implicit 1.2.840 SCU None Yes Yes
Storage 1.4.1.1.481.1 VR Little .10008.
Endian 1.2

Table 4: Proposed Presentation Contexts for Storage SCU

3.1.2.1.3 SOP Specific Conformance

SOP Specific Conformance for All Storage SOP Classes

After a successful C-STORE operation, the treatment delivery console does not display any
information to the user but returns to its normal state. If the C-STORE operation results with a warning
or an error, the treatment delivery console displays the appropriate warning or error message to the
operator.

DICOM Conformance Statement 19 of 151

 SOP Specific Conformance for the RT Plan Storage SOP Class

3.1.2.1.3.2.1 4DITC and TRUEBEAM 4.0 with implementation UID ‘Varian Console Interface 4’ and ‘Varian
Console Interface 4 QA Mode’ or later
These tags are in addition to conformance rules applied for lower version of implementation UIDs
supported in older version of Varian treatment delivery console.
Varian treatment delivery consoles use the following tags from ‘Patient Setup Sequence (300A,
0180):
Table Top Vertical Setup Displacement (300A, 01d2).
Table Top Longitudinal Setup Displacement (300A, 01d4).
Table Top Lateral Setup Displacement (300A, 01d6).
Also, when SOP object has at least one table top setup displacement defined, 4DITC (only)
considers zero value for remaining undefined table top setup displacements.

3.1.2.1.3.2.2 Varian treatment delivery consoles communicating on implementation UID “Varian Console
Interface 3” and “Varian Console Interface 3 QA Mode” or later:
These tags are in addition to conformance rules applied for lower version of implementation UIDs
supported in older version of 4DITC.
Treatment Delivery Type (300A, 00CE) supports new defined Term SETUP attribute for Setup
Fields.
Accessory Code (300A, 00F9) for Wedge, Compensator, Block and Applicator.
Varian treatment delivery consoles do not accept Arc-Dynamic Beam(s), which contain gantry
rotations that are not equally spaced (e.g. 0, 10, 30, 100).
Only the first Fraction Group sequence (300A, 0070) is read. The others are discarded.
A maximum of two wedges per field are supported.
A maximum of one MLC per field is supported.
Beam energy, table parameter and rotation direction changes in the control points are not
supported.
Whenever an operator changes a dose relevant attribute from the RT Plan in 4DITC, a new RT
Plan is created. The new RT Plan will refer to the originally loaded RT Plan through the
Referenced RT Plan Sequence (300C, 0002). The Referenced RT Plan Sequence (300C,
0002) can only contain at most one item.
General Accessory Sequence (300A,0420) used for empty Trays.
RT Plan extended interface and privatization are described in section 4.
Replacement for Field Type
In Extended Interface FieldType is used to distinguish between treatment and setup fields (values:
TREATMENT, SETUP) while DICOM attribute Treatment Delivery Type (300A, 00CE) always
contains value TREATMENT. When FieldType is removed from Extended Interface, the new value
SETUP for Treatment Delivery Type (300A,00CE) is used to designate setup fields.
Replacement for CustomAddOn for Block and Compensator
For Block and Compensator the Extended Interface has been used only to transport the accessory
code. This has been added to the DICOM standard and is now available in various accessory
sequences as attribute Accessory Code (300A,00F9), RT Beams Module.

20 of 151 Varian Treatment Delivery Console

 Compensator Sequence (300A,00E3): Accessory Code (300A,00F9).
Block Sequence (300A, 00F4):Accessory Code (300A,00F9)
Replacement for CustomAddOn for Empty Trays
Empty trays are trays that are not used for mounting a block or compensator but for different
purposes not supported specifically by DICOM. With the introduction of the General Accessory
Sequence (300A,0420) in RT Beams Module the CustomAddOn attribute in Extended Interface
gets obsolete for empty trays.
Empty Trays in General Accessory Sequence
General Accessory Sequence (300A,0420):
General Accessory Number (300A,0424)
General Accessory ID (300A,0421) – Replaces TrayID
General Accessory Description (300A,0422) –
General Accessory Type (300A,0423) – Defined Term: TRAY
Accessory Code (300A,00F9) – Replaces CustomCode
Bolus Support
Number of Boli (300A, 00ED) in Beam Sequence (300A, 00B0) is used for manual verification.
Referenced ROI number (3006, 0084) is used to identify the bolus is same or different within a
plan.

3.1.3 Load and Save of Imager Positions

It is possible to transfer the imager positions between the management system and 4DITC
Applications even if no verification images are planned or taken and thus “Planned Verification Image
Sequence” (300A,00CA) in RT Beams Module is empty.
If the “Planned Verification Image Sequence” is empty, a pseudo verification image will be added to
this sequence whose only purpose is to transmit the imager positions. This is done by adding an item
to this sequence containing only the following attributes:
X-Ray Image Receptor Angle (3002,000E)
RT Image Position (3002,0012)
RT Image SID (3002,0026)
Imaging Device-Specific Acquisition Parameters (300A,00CC) containing the string “Default
Imaging Parameters”
When 4DITC Application sends back a plan to the management System it may omit the tag “X-Ray
Image Receptor Angle” (3002,000E) because this value must be 0.0 (zero) anyway.
When imager positions are changed on 4DITC Application they will be saved back to the
management system when closing the patient. Management system saves imager positions that are
listed in the “Planned Verification Image Sequence” for sending them again to 4DITC Application when
the plan is requested next time.

DICOM Conformance Statement 21 of 151

3.1.4 RT Image Position vs. Imager Position in “Planned Verification Image
Sequence”
The DICOM standard defines the “RT Image Position” (3002,0012) as “The x and y coordinates […] of
the upper left hand corner […] of the image [...]”.
Because the size of an image to be taken is not known in advance, a width and height of zero pixels is
assumed in the “Planned Verification Image Sequence” of an RT Plan IOD. Therefore the position of
the center of the image receptor will be used for the “RT Image Position” tag instead. This is because
these are the same coordinates as those of the upper left hand corner of an image with zero pixels in x
and y directions.
The treatment delivery consoles will only accept the Beam Limiting Device if the verification of
the treatment machine settings and the Beam Limiting Device were successful. The same rule
applies to the imported Wedge, Block and Applicator data.
The treatment delivery console does not accept Arc-Dynamic Beam(s), which contains gantry
rotations that is not equally spaced (e.g. 0, 10, 30, and 100).
Only the first Fraction Group sequence (300A, 0070) is read. The others are discarded.
A maximum of two wedges per field are supported.
A maximum of one MLC per field is supported.
Beam energy, table parameter and rotation direction changes in the control points are not
supported.
Wedge position changes are only supported for static technique (motorized wedge).

3.1.5 Primary Fluence Mode

3.1.5.1 TrueBeam Treatment delivery console
The supported combination of High dose technique, Dose rate, Primary fluence mode and
energy are listed in Table 5.

Nominal Beam Dose Rate Set MU/Min Primary Fluence Mode High-Dose
Energy (300A, 0115) (3002,0051)* Technique Type
(300A,00C7)
(MV/MeV)
(300A,0114)
2.5x 60  STANDARD  Normal
 NON_STANDARD  TBI
 HDR
 SRS
4x 5, 10, 15, 20, 30, 40, 50, 100, 150, 200, 250  STANDARD  Normal
 NON_STANDARD  TBI
 HDR
 SRS
6x 5, 10, 15, 20, 40, 60, 80, 100, 200, 300, 400, 500,  STANDARD  Normal
600  NON_STANDARD  TBI
 HDR
 SRS
6x FFF 400, 600, 800, 1000, 1200, 1400  STANDARD  Normal
 NON_STANDARD  TBI
 HDR
 SRS

22 of 151 Varian Treatment Delivery Console

 8x 5, 10, 15, 20, 40, 60, 80, 100, 200, 300, 400, 500,  STANDARD  Normal
600  NON_STANDARD  TBI
 HDR
 SRS
10x 5, 10, 15, 20, 40, 60, 80, 100, 200, 300, 400, 500,  STANDARD  Normal
600  NON_STANDARD  TBI
 HDR
 SRS
10x FFF 400, 600, 800, 1000, 1200, 1400, 2400  STANDARD  Normal
 NON_STANDARD  TBI
 HDR
 SRS

15x 20, 40, 60, 80, 100, 200, 300, 400, 500, 600  STANDARD  Normal
 NON_STANDARD  TBI
 HDR
 SRS
18x 20, 40, 60, 80, 100, 200, 300, 400, 500, 600  STANDARD  Normal
 NON_STANDARD  TBI
 HDR
 SRS
20x 20, 40, 60, 80, 100, 200, 300, 400, 500, 600  STANDARD  Normal
 NON_STANDARD  TBI
 HDR
 SRS
4e 100, 200, 300, 400, 500, 600, 700, 800, 900,  STANDARD  Normal
1000  NON_STANDARD  TBI
 HDR
 SRS
6e 100, 200, 300, 400, 500, 600, 700, 800, 900,  STANDARD  Normal
1000  NON_STANDARD  TBI
 HDR
 SRS
2500 for HDR
9e 100, 200, 300, 400, 500, 600, 700, 800, 900,  STANDARD  Normal
1000  NON_STANDARD  TBI
 HDR
 SRS
2500 for HDR
12e 100, 200, 300, 400, 500, 600, 700, 800, 900,  STANDARD  Normal
1000  NON_STANDARD  TBI
 HDR
 SRS
15e 100, 200, 300, 400, 500, 600, 700, 800, 900,  STANDARD  Normal
1000  NON_STANDARD  TBI
 HDR
 SRS
16e 100, 200, 300, 400, 500, 600, 700, 800, 900,  STANDARD  Normal
1000  NON_STANDARD  TBI
 HDR
 SRS
18e 100, 200, 300, 400, 500, 600, 700, 800, 900,  STANDARD  Normal
1000  NON_STANDARD  TBI
 HDR
 SRS
20e 100, 200, 300, 400, 500, 600, 700, 800, 900,  STANDARD  Normal
1000  NON_STANDARD  TBI
 HDR
 SRS
22e 100, 200, 300, 400, 500, 600, 700, 800, 900,  STANDARD  Normal
1000  NON_STANDARD  TBI
 HDR
 SRS

Table 5: Supported combinations for Primary Fluence Mode, Dose Rate, Energy,
and High Dose Technique

DICOM Conformance Statement 23 of 151

3.1.5.2 4DITC
4DITC supports the following for Primary Fluence mode

Attribute Name Tag Type Attribute Description

> Primary Fluence Mode (3002,0050) 3 Sequence defining whether the primary
Sequence fluence of the treatment beam uses a
non-standard fluence-shaping. Only a
single Item shall be permitted in this
sequence.
>> Fluence Mode (3002,0051) 1 Describes whether the fluence shaping
is the standard mode for the beam or an
alternate.
Enumerated Values:
STANDARD = Uses standard fluence-
shaping
NON_STANDARD = Uses a non-
standard fluence-shaping mode
>> Fluence Mode ID (3002,0052) 1C Identifier for the specific fluence-shaping
mode. Required if Fluence Mode (3002,
0051) has value NON_STANDARD.
4DITC has supports the following mode
IDs
- SRS
- FFF
Fluence modes IDs are displayed along with energy in 4DITC display
Fluence modes IDs are displayed along with energy in 4DITC display.
Example
6X- SRS, 6X- FFF and 10X-FFF
Nonstandard Fluence mode and ModeID SRS and FFF are supported for the following Energy and
Dose Rate. But the following are machine specific – so it can be removed from DCS.

Nominal Beam Dose Rate Set Primary Fluence Fluence Mode ID

Energy MU/Min Mode
(3002,0052)
(MV/MeV) (300A, 0115) (3002,0051)*
(300A,0114)
6X 800, 1000 NON_STANDARD SRS

6X 140, 280, 420, … NON_STANDARD FFF

1400
[Steps of 140]
10X 400, 800 ,… 2400 NON_STANDARD FFF
[Steps of 400]

24 of 151 Varian Treatment Delivery Console

3.1.5.2.1 SOP Specific Conformance for the RT Beams Treatment Record storage SOP Class
With delivery systems prior to the TrueBeam 2.7 MR3 Platform release the Beam Limiting Device
Position Sequence (300A,011A) only contains collimator jaws positions. It does not contain any MLC
leaf position information. MLC leaf positions will not be reported within the RT Beams Treatment
Record IOD.
In TrueBeam 2.7 MR3 Platform release MLC leaf positions are reported for each control point in the
RT Beams Treatment Record storage record.
In TrueBeam 3.0 release the behavior is reverted. The Beam Limiting Device Position Sequence
(300A,011A) only contains collimator jaws positions. It does not contain any MLC leaf position
information. MLC leaf positions will not be reported within the RT Beams Treatment Record IOD.
In TrueBeam 4.0 Platform release MLC leaf positions are reported for each control point in the RT
Beams Treatment Record storage record if enabled in the system settings.Beams with Treatment
Delivery Type (300A,00CE) set to OPEN_PORTFILM or TRMT_PORTFILM are Image Beams. Beams
with Treatment Delivery Type set to TREATMENT are Treatment Beams.
All image beams attached to a treatment beam refer to the corresponding treatment beam. Similarly,
all image beams attached to a setup beam refer to that setup beam. Beams refer to a Treatment Beam
through the attribute Related Referenced Beam Number defined in section 4.2.1.
The Treatment Termination Status (3008,002A) specifies whether the treatment was completed or
partially completed.
If MU Subtraction is set for an Image Beam, the treated MU count will be deducted from the related
Treatment Beam. For Treatment Beams, MU Subtraction is always set. The following attributes are
used to determine whether the MU Subtraction is set or not set:

Treatment Delivery Type Related Treatment Termination MU Subtraction

(300A,00CE) Beam Status (3008, 002A)
Number (*)
OPEN_PORTFILM set MACHINE Set
TRMT_PORTFILM
OPEN_PORTFILM set NORMAL not set
TRMT_PORTFILM
TREATMENT — — Set

Table 6: MU Subtraction Status

Note The MU subtraction feature is available only on 4DITC console.

(*) Related Beam Number is a private tag added to the RT Beams Session Record module (see
section 4.1.2).
In TrueBeam 4.0 Platform release Interlock Sequence(300A,0740) and Beam Gating Hold Transition
Sequence(300C,0125) are recorded in the RT Beams Session Record module.
RT Beams Treatment Record Extended Interface and Privatizations are described in section 4.
The following SOP specific conformance rules apply to 4DITC with implementation UID ‘Varian
Console Interface 4’ or later.

DICOM Conformance Statement 25 of 151

 Varian treatment delivery consoles support Treatment notes to be saved as part of RT Beams
Treatment Record when patient session is closed. To store Treatment Notes in RT Beams Treatment
Record, standard DICOM tag “Beam Description (300A, 00C3) is used.
Actual SSD is saved to RT Beams Treatment Record when patient session is closed. To store SSD in
RT Beams Treatment Record, the Dicom tag “Source to Surface Distance (300A, 0130)” is used.

3.1.5.2.2 SOP specific conformance for the RT Image Storage SOP class
The 4DITC Entity only stores images with the Image Type (0008,0008) set to PORTAL.

3.1.5.3 Query/Retrieve SCU

3.1.5.3.1 Associated Real-World Activity

Varian treatment delivery consoles use the Query/Retrieve information model MOVE for retrieving
patient data from the Management System. After a successful query, the Management System sends
the requested data with the C-Store service.
Varian treatment delivery consoles uses the Query/Retrieve information model FIND for gathering
information from the Management System. In order to determine whether a Beam was partially treated
or completed, Varian treatment delivery consoles queries for several attributes in the RT Beams
Treatment Record stored in the management.

3.1.5.3.2 Presentation Context Table

Presentation Context Table

Abstract Syntax Transfer Syntax Role Extende TRUEBE 4DITC

d AM 3.0 13.0
Negotia-
tion

Name UID Name UID

Study Root 1.2.840.10008.5.1.4.1 DICOM 1.2.840.10008.1. SCU None Yes Yes

Query/ .2.2.1 Implicit VR 2
Retrieve Little
Information Endian
Model - FIND
Study Root 1.2.840.10008.5.1.4.1 DICOM 1.2.840.10008.1. SCU None Yes Yes
Query/ .2.2.2 Implicit VR 2
Retrieve Little
Information Endian
Model - MOVE

Table 7: Proposed Presentation Contexts for Query/Retrieve SCU

3.1.5.3.3 SOP Specific Conformance

The following Query/Retrieve SOP classes are used by Varian treatment delivery consoles as a
Service Class User (SCU):
C-Move RT Plan
C-Move RT Treatment Summary Record

26 of 151 Varian Treatment Delivery Console

 C-Move RT Image
C-Find RT Beams Treatment Record
C-Find RT Plan
C-Find RT Image (4DITC only)

SOP specific Conformance for the C-Move SOP Classes

For all C-Move SOP classes, the query key is always the SOP Instance UID of the particular DICOM
IOD that 4DITC requests. There are no other matching criteria’s for the C-Move key. All keys used for
the C-Move service are defined in section B 1.1.
The C-Move service requires 4DITC to be an SCP of the C-Store service for the same DICOM IOD.
For example whenever 4DITC is a SCU of C-Move RT Plan it implies that 4DITC is a SCP of C-Store
RT Plan (see Table 1).

SOP specific Conformance for the C–Find RT Beams Treatment Record SOP Class
The C-Find RT Beams Treatment Record SOP class will be used for calculating the remaining MU.
The remaining monitor units are calculated with the Beam Meterset (300A,0086) in the RT Fraction
Scheme module (provided from the Plan IOD) minus the Delivered Primary Meterset (3008, 0036)
(provided from the Beam Record Information) -see Table 18). If the monitor units were overridden, the
Beam Record Information contains the overridden value in the Specified Meterset (3008, 0042). In this
case, the overridden Specified Meterset (3008, 0042) is used instead of the Beam Meterset
(300A,0086) to calculate the remaining monitor units.
Calculation of Remaining MU when monitor units are not overriden:
Remaining MU = Beam Meterset (300A,0086) – Delivered Primary Meterset (3008,0036)
Calculation of Remaining MU when monitor units are overriden:
Remaining MU = Specified Meterset (3008, 0042) – Delivered Primary Meterset (3008,0036)
The Treatment Record key contains the matching criteria for the RT Beams Treatment Record.
Whenever the key matches the particular RT Beams Treatment Record, the attributes defined in Table
18 (SCP column) gets filled in. Note that the Treatment Session Beam Sequence may contain one or
more item. It is up to the Management System to decide whether for each Treatment Session Beam
one Treatment Record key gets sent or if all Treatment Session Beams are sent within one Treatment
Record key.
Only the last treated fraction is the fraction of interest.

SOP specific conformance for the C – Find RT Plan SOP class

Plans may be loaded into 4DITC without having them scheduled for the current session. Therefore
4DITC has to know how many treatment plans a patient has. This information gets retrieved with the C
– Find RT Plan SOP Class. The Plan key contains the matching criteria and the placeholder for all
attributes. The Plan key is defined in Table 17. The SOP Instance UID defined in the Plan key is the
Plan Instance UID which will be used to load an unscheduled Plan in 4DITC.

Note The unscheduled plan load feature is available only on 4DITC console.

SOP specific conformance for the C – Find RT Image SOP class

Since Portal Images are not referenced within the RT Plan, 4DITC queries the Portal Images from the
Management System with the C – Find RT Image service SOP class. The Image key is defined in
Table 16. The Referenced SOP Instance UID (i.e. the Plan Instance UID) and the Referenced Beam
DICOM Conformance Statement 27 of 151
 Number uniquely identifies the Beam, which 4DITC needs to query the Portal Images from. 4DITC
uses the SOP Instance UID (i.e. the RT Image Instance UID ) to retrieve previous acquired Portal
Image. The C – Find confirmation returns as many Image keys as Portal Images stored in the
Management System for that particular beam.

3.1.6 Association Acceptance Policy

The treatment delivery console entity accepts association requests for the supported service classes
shown in Figure 2. Varian treatment delivery consoles accept only one Management System
Application Entity for the possible association.
3.1.6.1 Storage SCP

3.1.6.1.1 Associated Real-World Activity

The patient data is sent from the Management System to Varian treatment delivery console using the
C- Store service. This is the only service that Varian treatment delivery consoles support as an SCP.

3.1.6.1.2 Presentation Context Table

Presentation Context Table

Abstract Syntax Transfer Syntax Role Extend TRUE 4DITC
ed BEA 13.0
Negotia M 4.0
tion

Name UID Name UID

RT Plan 1.2.840.10008.5.1.4. DICOM Implicit VR 1.2.840.10008.1.2 SCP None Yes Yes
Storage 1.1.481.5 Little Endian
DICOM Explicit VR 1.2.840.10008.1.2.1 SCP None Yes Yes
Little Endian
RT 1.2.840.10008.5.1.4.1. DICOM Implicit VR 1.2.840.10008.1.2 SCP None No Yes
Image 1.481.1 Little Endian
Storage
DICOM Explicit VR 1.2.840.10008.1.2.1 SCP None No Yes
Little Endian
RT 1.2.840.10008.5.1.4. DICOM Implicit VR 1.2.840.10008.1.2 SCP None Yes Yes
Treatme 1.1.481.7 Little Endian
nt
Summar DICOM Explicit VR 1.2.840.10008.1.2.1 SCP None Yes Yes
y Record Little Endian
Storage

Table 8: Acceptable Presentation Contexts for Storage SCP

3.1.6.1.3 SOP Specific Conformance for the Storage SOP class

Varian treatment delivery consoles are not an archive system. Thus DICOM IOD’s are temporarily stored
during a treatment session and deleted once the session is finished.

SOP specific conformance for RT Plan Storage SOP Class

28 of 151 Varian Treatment Delivery Console

 SOP specific conformance for RT Image Storage SOP class (4DITC only)
The 4DITC Entity supports the following image types: DRR, PORTAL, and SIMULATOR.
To represent portal dose, RT Images of image type PORTAL are used. This is based on DICOM
standard Part 3, section A.17.3 (RT Image IOD Module Table), Notes 2. The conversion between
portal image pixel values and portal dose is defined by the Modality LUT module through re-scale
Slope and Intercept. The unit depends on the re-scale Type. The image type in Table 9 distinguishes
the two types of portal doses:
Image Type Meaning
DERIVED\SECONDARY\PORTAL\CALCULAT Portal dose predicted by a treatment planning
ED_DOSE system, i.e. an estimate of the dose that will
be perceived by the portal imaging device.
ORIGINAL\PRIMARY\PORTAL\ACQUIRED_D Portal dose actually measured by the portal
OSE imaging device based on its calibration.

Table 9: Image Type

RT Image Geometrical Values

RT Images (used as reference images) require a sufficient amount of geometrical parameters that will
define the position of RT Images with respect to the machine. The following parameters are required
for proper operation of image verification applications associated with 4DITC:
X-Ray Image Receptor Translation (3002,000D)
Value must be present.
X-Ray Image Receptor Angle (3002,000E)
Value must be present.

Note In the current release, only 0 is supported. Providing this value will
ensure safe interpretation.

RT Image Position (3002,0012)

It is recommended to have this value defined. If the value is not defined, the application will
assume that the image was centered on the X-Ray Image Receptor System.
Radiation Machine SAD (3002,0022) or RT Image SID (3002,0026)
At least one of the two values must be present.
Image Plane Pixel Spacing (3002,0011)
Value must be present.
Gantry Angle (300A,011E)
Value must be present. This value shall represent the angle (in IEC GANTRY system
coordinates) where the physical or virtual (in case of DRR) source of radiation is located.

Note When kV images are used as Reference Images, this value describes
the projection geometry. Therefore, this value may not coincide with the
Gantry Hardware Readout of the linear accelerator since the kV Image
radiation source may be on a different position than the linear
accelerator’ target focus.

DICOM Conformance Statement 29 of 151

 RT Orientation (3002,0010)
In the future, it is recommended to have this value defined for images that have the RT Image
Plane set to NORMAL (this value is required for NON-NORMAL images). This is because the
DICOM standard does not unambiguously define the position of the RT Image pixel area in the
IEC Image Receptor system when this value is missing. If this value is not provided, the
application assumes that the value is (1,0,0,0,-1,0).

SOP specific conformance for the RT Treatment Summary Record SOP class
RT Treatment Summary Record IOD contains additional private tags defined in section 4.1.3.
3.1.6.2 Presentation Context Acceptance Criterion
The Varian treatment delivery console entity will accept the presentation contexts listed in Table 4:
Proposed Presentation Contexts for Query/Retrieve SCU.
3.1.6.3 Transfer Syntax Selection Policies
Varian treatment delivery consoles accept both Implicit VR Little Endian and Explicit VR Little Endian
as shown in Table 5. 4DITC does not prefer one presentation context over the other.

30 of 151 Varian Treatment Delivery Console

4. Communication profiles
4.1 Supported communications stacks
The Varian treatment delivery console entity provides DICOM V3.0 TCP/IP Network Communication
Support as defined in PS 3.8 (part 8 of the DICOM V3.0 standard).

4.1.1 TCP/IP stack

The Varian treatment delivery console entity uses the TCP/IP stack of Microsoft Windows Operating
Systems (Winsock).
4.1.1.1 Physical media support
The Varian treatment delivery console entity can run on any physical network media that is supported
by the underlying hardware and operating system. These include, but are not limited to: thin, thick, and
twisted-pair Ethernet, token ring network and FDDI.

DICOM Conformance Statement 31 of 151

5. Configuration

5.1 4DITC DICOM Configuration

4DITC is configured through the 4DITC Administration application.

5.1.1 AE Title/Presentation Address Mapping

4DITC Administration provides a mapping of an Application Entity Title to a Presentation Address. A
Presentation Address consists of a host name and a port number. In 4DITC Administration, the related
Application Entity Title, host name, and port number are grouped under the section Daemon (remote)
that is within the DICOM Configuration box (see Figure 5).

Figure 5: 4DITC Administration Setup

5.1.2 Configurable Parameters

The configurable parameters are located within the “DICOM Configuration” box of 4DITC
Administration. The destination’s AE Title, hostname or TCP/IP address, and port number can be
configured under the “Daemon (remote)” section. The local AE Title and port number can be
configured under the “Treatment (local)” section (see Figure 5).

Note In case warnings or errors are encountered after configuration, there

are logs available to assist in determining the cause of the problem.
4DITC Administration has a “4D Console Application Configuration”
section with a Log Level setting. When this Log Level is set to
“Detailed” 4DITC writes more information to the log that will help in
debugging the problem.

32 of 151 Varian Treatment Delivery Console

5.2 Treatment delivery console DICOM Configuration
The Treatment Preference Utility provides a mapping of an Application Entity Title to a Presentation Address.
A Presentation Address consists of a host name and a port number. In Treatment Preferences Utility, the
related Application Entity Title, host name, and port number are can be found in the Treatment Preference
Utility, Advanced tab page (see Figure 6). The Client AE Title is the TXA application title, whereas Server AE
Title represents the management system entity. Note that the connection can be tested only for TREATMENT
DELIVERY CONSOLE in the SCU and the management system in the SCP role within the Treatment
Preference Utility Application.

Figure 6: AE Title/Presentation Address Mapping

DICOM Conformance Statement 33 of 151

6. Media Interchange
The Varian treatment delivery console Application Entity does not support Media Interchange.

7. Support of Extended Character Sets

No dedicated support for Character Sets beyond the Default Repertoire is available. However, text
fields containing characters not in the Default Character Repertoire when importing an instance will
appear unchanged when re-exporting the same instance again
The following character set encodings are supported.

Encoding Value Database supported

West European (Code Page) "ISO_IR 100", or ARIA 11, and other non -
“WINDOWS 1252” Unicode supporting
Databases

Chinese Simplified (Code Page) “WINDOWS 936" ARIA 11, and other non -
Unicode supporting
Databases
Japanese (Code page) “WINDOWS 932" ARIA 11, and other non -
Unicode supporting
Databases
Unicode (UTF8) "ISO_IR 192" ARIA 13, and future Unicode
supporting Databases

TRUEBEAM 4.0 and 4DITC with implementation UID ‘Varian Console Interface 6’ or later supports:
UTF-8
Correct display of characters not in the Default Character Repertoire depends on available/configured
operating system support.

8. Security
8.1 Security Profiles
No Security Profiles are supported.

8.2 Association Level Security

The treatment delivery console checks the following values when determining whether to accept Association
Open Requests:
Called AE Title

8.3 Application Level Security

Local administrative rights are required for installing Varian treatment delivery consoles.

34 of 151 Varian Treatment Delivery Console

 Specialization
A.1 IOD Contents
A.1.1 Created SOP Instances
IODs created by TREATMENT DELIVERY CONSOLE Entities are listed in Appendix C along with
supported modules and its attributes.

A.1.2 Usage of Attributes from received IOD’s

This section describes the required or optional presence of Type 1, 2 and 3 attributes which Varian
treatment delivery consoles implement to pass the Plan IOD validation on load.
Type 1 attributes need to be present.
Type 2 attributes are distinguished as mandatory or optional attributes (similar to Type 1 and
Type 3)
For all Type 2 RT Plan IOD attributes listed in Table 10, the roundtrip will be supported. This
means that the attribute, if defined (attribute length greater than zero) while loading the RT Plan
IOD, will be unchanged and present in the edited and saved RT Plan IOD.
For all Type 2 RT Plan IOD attributes not listed in Table 10 are deemed as optional and roundtrip
is not supported.
Term used in the Handling
Description
column
The attribute must be present and defined (attribute length
Mandatory greater than zero) if corresponding DICOM Module and
Sequence is sent.
Optional The attribute is being present with zero length or absent.

The table below summarizes the handling of RT Plan IOD Type 2 data elements in treatment delivery
consoles.
TRUEBEAM 4DITC v
Attribute Name Tag Module/Sequence
v 4.0 13.0
Id (0010, 0020) Patient Mandatory. Mandatory.

Sex (0010, 0040) Patient Optional. Optional.

Name (0010, 0010 Patient Mandatory. Mandatory.

Birth Date (0010, 0030) Patient Optional. Optional.

Manufacturer (0008, 0070) General Equipment Mandatory. Mandatory

Leaf Position Optional
(300A, 00BE) RT Beam Limiting Device Mandatory.
Boundaries

Reviewer Name (300E, 0008) Approval Mandatory. Optional

Review Date (300E, 0004) Approval Mandatory. Optional
Treatment Date (3008, 0250) General Treatment Record Mandatory. Mandatory.

DICOM Conformance Statement 35 of 151

 Treatment Time (3008, 0251) General Treatment Record Mandatory. Mandatory.

Treatment Machine Mandatory.

(300A, 00B2) Beam Mandatory.
Name
Radiation Type (300A, 00C6) Beam Optional. Optional.
Fraction Group Mandatory.
(300A, 0071) Fraction Group Mandatory.
Number
Operators Name (0008, 1070) RT General Plan Optional. Optional

Date (300A, 0006) RT General Plan Mandatory. Optional

Time (300A, 0007) RTGeneralPlan Mandatory. Optional

Cumulative Meterset Mandatory

(300A, 0134) Control Point Mandatory.
Weight
Table Top Vertical Optional
(300A, 0128) Contro lPoint Optional.
Position
Table Top Optional
Longitudinal (300A, 0129) Control Point Optional.
Position

Table Top Optional

(300A, 012A) Control Point Optional.
LateralPosition
Isocenter Position (300A, 012C) Control Point Optional. Optional

WedgeType (300A, 00D3) Wedge Mandatory Mandatory

Wedge Angle (300A, 00D5) Wedge Mandatory Mandatory

Wedge Factor (300A, 00D6) Wedge Optional Optional

Wedge Orientation (300A, 00D8) Wedge Mandatory Mandatory

Comp Material ID (300A, 00E1) Compensator Mandatory Mandatory
Source Comp Tray Optional
(300A, 00E6) Compensator Optional
Distance

Source Block Tray Optional

(300A, 00F6) Block Optional
Distance

Block Divergence (300A, 00FA) Block Optional Optional

Block MaterialID (300A, 00E1) Block Mandatory Optional

Block Thickness (300A, 0100) Block Optional Optional

Block Transmission (300A, 0102) Block Optional Optional

Block Number Of Optional
(300A, 0104) Block Mandatory
Points

Block Data (300A, 0106) Block Mandatory Optional

Table 10: Treatment Delivery Console handling of RT Plan IOD DICOM Type 2 attributes

36 of 151 Varian Treatment Delivery Console

 Type 3 attributes are optional and may be absent except the attributes listed in Table 11.
TRUEBEAM 4DITC v13.0
Attribute Name Tag Module/Sequence
v4.0
Mandatory Optional
Unique beam
Beam Name (300A,00C2) Beam
identification for the
User Interface.

Treatment Delivery Type (300A,00CE Beam Mandatory Optional

)

Mandatory Optional
This attribute is
(300A,
Tolerance Table Label Tolerance Table being used for
0043)
unique tolerance
table identification.

Mandatory Mandatory
This attribute is
(300A, Dose Reference being used for
Dose Reference Description
0016) Sequence unique dose
reference
identification.

Table 11: Treatment Delivery Console handling of RT Plan IOD DICOM Type 3 attributes

A.2 Data Dictionary of Private Attributes

A.2.1 Privatization for RT Plan Storage SOP class
The DICOM Extended Interface is a private group added to the RT Plan IOD. This group
contains an XML stream that contains the Plan Extended Interface described in Appendix D.

Attribute Name Tag Type Attribute Description VR

Extended Interface Data (3253,xx00) 3 XML stream. LT

Extended Interface Length (3253,xx01) 3 Data length of the XML stream IS

Extended Interface Format (3253,xx02) 3 Extended Interface Format tag. CS

A possible value is: ‘ExtendedIF’

Table 12: RT Plan Module Privatization

DICOM Conformance Statement 37 of 151

 Attribute Name Tag Type Attribute Description VR
Fraction Group Sequence (300A,0070) 1 -STANDARD DICOM- SQ
Introduces sequence of Fraction Groups in
current Fraction Scheme.

> Referenced Beam (300C,0080) 3 -STANDARD DICOM- SQ

Sequence Related instances of RT Dose (for grids,
iso-dose curves and named/unnamed point
doses).

>> Maximum Treatment (3249,xx00) 3 The maximum treatment time, which DS

Time should not be exceeeded (in min). This
item serves as a secondary safety limit
besides the Beam Meterset (300A,0086)
value itself.

Table 13: RT Fraction Scheme Module Privatization

Attribute Name Tag Type Attribute Description VR

Beam Sequence (300A,00B0) 1 -STANDARD DICOM- SQ
Introduces sequence of treatment beams
for current RT Plan.

> Beam Secondary Name (3243,xx09) 3 Second user-defined beam name LO

> Accessory Sequence (300A,0420) 3 -STANDARD DICOM- SH

Introduces a Sequence of General
Accessories associated with this Beam.
>> General Accessory (300A, 0423) 3 Additionally to the already defined terms, SH
Type TRAY will be added defining accessory
trays different than graticule, image
detector and reticle.
Defined Terms:
GRATICULE
IMAGE_DETECTOR
RETICLE
TRAY

Table 14: RT Beams Module Privatization

38 of 151 Varian Treatment Delivery Console

A.2.2 Privatization for RT Beams Treatment Record Storage SOP
class
Attribute Name Tag Type Attribute Description VR
Treatment Session Beam (3008,0020) 1 SQ
-STANDARD DICOM-
Sequence
Introduces sequence of Beams
administered during treatment
session.
> Treatment Machine Note (3251, xx00) 3 A description of the treatment machine LO
details.
>Beam Description (300A,00C3) 3 User-defined description for delivered ST
Beam. A treatment history note.
> Treatment Session Beam Data (3261,xx2A) 3 Extended interface in XML format. OB

> Related Referenced Beam (3243,xx28) 3 If TreatmentDeliveryType of the IS

Number treated beam is either
OPEN_PORTFILM or
TRMT_PORTFILM then the Related
Referenced Beam Number must be
used instead of the Referenced Beam
Number (300C, 0006). The Related
Referenced Beam Number refers to
the treatment field for which the image
was taken.
>Source to Surface Distance* (300A,0130) 3 Source to Patient Surafce distance DS
(mm)

Table 15: RT Beams Session Record Module Privatization

DICOM Conformance Statement 39 of 151

A.2.3 Privatization for RT Treatment Summary Record Storage SOP
class
*Note: Standard Extended attribute

Attribute Name Tag Type Attribute Description VR

Total Number of Fractions (3265,xx00) 1 Total number of Fractions planned for SL
the current plan and all its former
plans.

Last Treated Fraction (3265,xx01) 1 The index of the last fraction treated SL
across the current plan and all its
former plans. In other words, this tag
will always contain the fraction, which
was last treated (completely or
partially). So it will be the same as in
the Fraction Status Summary
Sequence (3008,0240) on the last item
of the sequence in the tag Referenced
Fraction Number (3008,0223), as soon
as the sequence is not empty any
more (so after the 1st treatment has
got at least 1 MU).
In case of completing a partial
treatment, the plan’s current fraction
number is equal to Last Treated
Fraction (3265, 1001).
Additional Dose Value (3259,xx00) 3 Introduces sequence of Actual Session SQ
Sequence Dose Sequence. The sequence may
contain one or more items.
Sequence for additional Dose
Information to a Reference Point.
The ReferencePoint must be
connected to Referenced Plan
of this TreatmentSummary
Record, but also the Dose of
other Plans which have the
same Reference Point have
influence on this values.
> Actual Session Dose (3259,xx02) 1C Session Dose Delivered of Actual DS
Session
Required if Actual Session Dose
Sequence is sent.
> Daily Dose (3259,xx04) 1C Daily Dose of current day. DS
Required if Actual Session Dose
Sequence is sent.
> Life Time Total Dose (3259,xx06) 1C Total Dose of Reference Point over all DS
Plans.
Required if Actual Session Dose
Sequence is sent.
Table 16: Treatment Summary Record Module Privatization

40 of 151 Varian Treatment Delivery Console

 DICOM Query Retrieve
Service Class Object
Matching Criteria (SCU Role)
This section describes the Conformance Statement for information query and data retrieval functions
used in Treatment. They are implemented as the SCU role of the DICOM Query/Retrieve SOP
Classes.

B.1 IOD Specific Matching Criteria

Table 17: Supported Query/Retrieve Levels for Query/Retrieve SCU shows the supported values
for the tag Query/Retrieve Level (0008,0052):

Query/Retrieve Level Value in (0008,0052)

Study Information STUDY
Series Information SERIES
Composite Object Plan Information PLAN
Instance Information
Treatment Record Information TREATMENTRECORD
Treatment Summary Record TREATMENTSUMMARYRECORD
Information

Treatment Summary Record TREATMENTSUMREC

Information

Note: Treatment Delivery

Console uses this value
when association is
established with Varian
Console Interface 3 or higher.

Table 17: Supported Query/Retrieve Levels for Query/Retrieve SCU

Note In addition to the IMAGE value for the Composite Object Instance
Level, we expect the following values for querying/retrieving the
respective objects: PLAN, TREATMENTRECORD,
TREATMENTSUMMARYRECORD, TREATMENTSUMREC.

DICOM Conformance Statement 41 of 151

B.1.1 Supported Keys
Varian treatment delivery consoles are not an SCP of any C-Find service. The tables in the
following sub section show which keys the Treatment SCU is capable of generating query
requests in order to perform a hierarchical search.
The following conventions are used to define the types of keys used by Treatment (SCU) in
Query/Retrieve request sent to the management systems (SCP).

Symbol Description
U Unique Key Attribute
R Required Key Attribute
O Optional Key Attribute

B.1.1.1 Study Level

Description Tag Type

Query Level STUDY (0008,0052) R
Study Date (0008,0020) R
Study Time (0008,0030) R
Accession Number (0008,0050) R
Patient's Name (0010,0010) R
Patient ID (0010,0020) R
Study ID (0020,0010) R
Study Instance UID (0020,000D) U

Table 18: Study key

B.1.1.2 Series Level

Description Tag Type

Query Level SERIES (0008,0052) R
Modality (0008,0060) R
Series Number (0020,0011) R
Series Instance UID (0020,000E) U
Study Instance UID (0020,000D) U

Table 19: Series key

42 of 151 Varian Treatment Delivery Console

B.1.1.3 Composite Object Instance Level

B.1.1.3.1 Plan

Description Tag Type

Query Level PLAN (0008,0052) R
SOP Instance UID (0008,0018) U
Series Instance UID (0020,000E) U
Study Instance UID (0020,000D) U
Patient's Name (0010,0010) O
Patient ID (0010,0020) O
Plan Label (300A,0002) O
Plan Date (300A,0006) O
Plan Time (300A,0007) O
Number of Beams (300A,0080) O
Referenced RT Plan Sequence (300C,0002) O
>Referenced SOP Class UID (0008,1150) O
>Referenced SOP Instance UID (0008,1155) O
>RT Plan Relationship (300A,0055) O
Field Type (3257,xx00) O
Plan Type (3257,xx01) O

Table 20: Plan key

B.1.1.3.2 Treatment Record Key

Description Tag Type

Query Level TREATMENTRECORD (0008,0052) R
SOP Instance UID (0008,0018) U
Series Instance UID (0020,000E) U
Study Instance UID (0020,000D) U
Referenced SOP Class UID (0008,1150) O
Referenced SOP Instance UID (0008,1155) O
Treatment Date (3008,0250) O
Treatment Time (3008,0251) O
Referenced Fraction Group Number (300C,0022) O
Treatment Session Beam Sequence (3008,0020) O
>Referenced Beam Number (300C,0006) O
>Treatment Delivery Type (300A,00CE) O
>Treatment Termination Status (3008,002A) O
>Delivered Primary Meterset (3008,0036) O

DICOM Conformance Statement 43 of 151

 >Current Fraction Number (3008,0022) O
>Referenced Calculated Dose Reference (3008,0090) O
Sequence
>>Referenced Dose Reference Number (300C,0051) O
>>Calculated Dose Reference Value (3008,0076) O
>Control Point Delivery Sequence (3008,0040) O
>>Referenced Control Point Index (300C,00F0) O
>>Specified Meterset (3008,0042) O
>>Override Sequence (3008,0060) O
>>>Override Parameter Pointer (3008,0062) O

Table 21: Treatment Record key

B.1.1.3.3 Treatment Summary Record

Description Tag Type

Query Level (0008,0052) R
- VMS Console System6.5:
TREATMENTSUMMARYRECORD
- VMS Console System 8.8 and VMS
Console System 8.8 QA:
TREATMENTSUMMARYREC

Referenced SOP Class UID (0008,1150) O

Referenced SOP Instance UID (0008,1155) O
Current Treatment Status (3008,0200) O
Number of Fractions Delivered (3008,005A) O
Treatment Summary Calculated (3008,0050) O
Dose Reference Sequence
>Referenced Dose Reference (300C,0051) O
Number
>Dose Reference Description (300A,0016) O
>Cumulative Dose to Dose (3008,0052) O
Reference

Table 22: Treatment Record key

44 of 151 Varian Treatment Delivery Console

 IOD Details
C.1 Supported IODs
The following tables define the modules that are and are not supported for a particular IOD. For
specific IOD details, refer to Related Documents [2].
The “Not supported” entries in the Support column indicate that the import of module is not
supported or it is discarded on import of this IOD and will never appear in exported IOD.

RT Plan IOD Module Table

IE Module Reference DICOM Usage Support
Patient Patient C.7.1.1 M
Study General Study C.7.2.1 M
Patient Study C.7.2.2 U Not supported
Series RT Series C.8.8.1 M
Frame of Frame Of C.7.4.1 U
Reference Reference
Equipment General C.7.5.1 M
Equipment
Plan RT General Plan C.8.8.9 M
RT Prescription C.8.8.10 U
RT Tolerance C.8.8.11 U
Tables
RT Patient Setup C.8.8.12 U
RT Fraction C.8.8.13 U
Scheme
RT Beams C.8.8.14 C
RT Brachy C.8.8.15 C Not supported
Application
Setups
Approval C.8.8.16 U
Audio C.10.3 U Not supported
SOP Common C.12.1 M
DICOM Private module C Additional
Extended (see C.2.16) features are
Interface supported with
this module.
Table 23: RT Plan IOD Module

DICOM Conformance Statement 45 of 151

 RT Beams Treatment Record IOD Module Table
IE Module Reference DICOM Usage Notes
Patient Patient C.7.1.1 M
Study General Study C.7.2.1 M
Patient Study C.7.2.2 U Not supported
Series RT Series C.8.8.1 M
Equipment General C.7.5.1 M
Equipment
Treatment RT General C.8.8.17 M
Record Treatment
Record
RT Patient Setup C.8.8.12 U Not supported
RT Treatment C.8.8.18 M
Machine Record
Measured Dose C.8.8.19 U Not supported
Reference
Record
Calculated Dose C.8.8.20 U Not supported
Reference
Record
RT Beams C.8.8.21 M
Session Record
RT Treatment C.8.8.22 U Not supported
Summary
Record
SOP Common C.12.1 M
Table 24: RT Beams Treatment Record IOD Module

RT Treatment Summary Record Module Table

IE Module Reference DICOM Usage Notes
Patient Patient C.7.1.1 M
Study General Study C.7.2.1 M
Patient Study C.7.2.2 U Not supported
Series RT Series C.8.8.1 M
Equipment General C.7.5.1 M
Equipment
Treatment RT General C.8.8.17 M
Record Treatment
Record
RT Treatment C.8.8.23 M
Summary
Record

46 of 151 Varian Treatment Delivery Console

 SOP Common C.12.1 M
Table 25: RT Treatment Summary Record Module

RT Image IOD Module Table (4DITC only)

IE Module Reference DICOM Usage Notes
Patient Patient C.7.1.1 M —
Study General Study C.7.2.1 M —
Patient Study C.7.2.2 U Not supported
Series RT Series C.8.8.1 M —
Frame Of Frame of C.7.4.1 U —
Reference Reference
Equipment General C.7.5.1 M —
Equipment
Image General Image C.7.6.1 M —
Image Pixel C.7.6.1 M —
Contrast/bolus C.7.6.3 C Not supported
Cine C.7.6.5 C Not supported
Multi-Frame C.7.6.6 C Not supported
RT Image C.8.8.2 M —
Modality LUT C.11.1 U —
VOI LUT C.11.2 U —
Approval C.8.8.16 U —
Audio C.10.3 U Not supported
SOP Common C.12.1 M —

Table 26: RT Image Module (4DITC only)

DICOM Conformance Statement 47 of 151

 IOD Details, Supported Keys

C.2 Modules and Attributes

For better reference with DICOM Standard, section titles of the following sub-sections are decorated
with section number of DICOM Standard Part 3 where the corresponding Module Attribute table can
be found. The first four columns in the following tables contain definitions from the DICOM standard.
All references in those columns refer to the DICOM standard and not to this document.
Note that Varian treatment delivery consoles only support roundtrip with RT Plan IOD’s. Thus this
section is focusing solely on RT Plan IOD attributes.
Column TrueBeam 4.0 and 4DITC v13.0 support describes for each attribute whether it is supported
thus maintained when loading the plan for these respective consoles.

Value in “TXA Description

Model Support”
column

*** not supported *** Attribute is unknown and therefore ignored by TXA. This means that the Rountrip
(load, edit and save) will result in erasing this attribute in the RT Plan IOD..
Roundtrip supported. Complete roundtrip is guaranteed. Loading, editing and saving will maintain
(unless edited) the original value in the exported RT Plan IOD.

C.2.1 Patient – C.7.1.1

Attribute Name Tag Type Attribute Description TrueBeam 4DITC v13.0

4.0

Patient’s Name (0010,0010) 2 Patient's full name. Roundtrip Roundtrip

supported. supported.
Patient ID (0010,0020) 2 Primary hospital identification Roundtrip Roundtrip
number or code for the supported. supported.
patient.
Issuer of Patient (0010,0021) 3 Identifier of the Assigning *** not Not
ID Authority that issued the supported *** supported
Patient ID.
Patient's Birth (0010,0030) 2 Birth date of the patient. Roundtrip Roundtrip
Date supported. supported.
Patient's Sex (0010,0040) 2 Sex of the named patient. Roundtrip Roundtrip
Enumerated Values: supported. supported.
M = male
F = female
O = other
Referenced (0008,1120) 3 A sequence that provides *** not Not
Patient reference to a Patient SOP supported *** supported
Sequence Class/Instance pair. Only a
single Item shall be permitted
in this Sequence.

Treatment Delivery Console 49 of 151

 IOD Details, Supported Keys
Attribute Name Tag Type Attribute Description TrueBeam 4DITC v13.0
4.0

> Referenced (0008,1150) 1C Uniquely identifies the *** not Not

SOP Class UID referenced SOP Class. supported *** supported
Required if Referenced
Patient Sequence
(0008,1120) is sent.
> Referenced (0008,1155) 1C Uniquely identifies the *** not Not
SOP Instance referenced SOP Instance. supported *** supported
UID Required if Referenced
Patient Sequence
(0008,1120) is sent.
Patient's Birth (0010,0032) 3 Birth time of the Patient. Roundtrip Roundtrip
Time supported. supported.
Other Patient (0010,1000) 3 Other identification numbers Roundtrip Roundtrip
IDs or codes used to identify the supported. supported.
patient.
Other Patient (0010,1001) 3 Other names used to identify *** not Not
Names the patient. supported *** supported
Ethnic Group (0010,2160) 3 Ethnic group or race of the Roundtrip Roundtrip
patient. supported. supported.
Patient (0010,4000) 3 User-defined additional Roundtrip Roundtrip
Comments information about the patient. supported.d. supported.
Patient Identify (0012,0062) 3 The true identity of the patient *** not Not
Removed has been removed from the supported *** supported
Attributes and the Pixel Data
Enumerated Values:
YES
NO
De-identification (0012,0063) 1C A description or label of the *** not Not
Method mechanism or method use to supported *** supported
remove the patient's identity.
May be multi-valued if
successive de-identification
steps have been performed.
Note:
This may be used to describe
the extent or thoroughness of
the de- identification, for
example whether or not the
de-identification is for a
"Limited Data Set" (as per
HIPAA Privacy Rule).
Required if Patient Identity
Removed (0012,0062) is
present and has a value of
YES and De-identification
Method Code Sequence
(0012,0064) is not present.

50 of 151 Varian Treatment Delivery

Console
 IOD Details, General Study - C.7.2.1
Attribute Name Tag Type Attribute Description TrueBeam 4DITC v13.0
4.0

De-identification (0012,0064) 1C A code describing the *** not Not

Method Code mechanism or method use to supported *** supported
Sequence remove the patient's identity.
One or more Items shall be
present. Multiple items are
used if successive de-
identification steps have been
performed
Required if Patient Identity
Removed (0012,0062) is
present and has a value of
YES and De-identification
Method (0012,0063) is not
present.
> Code Value (0008,0100) 1C See Section 8.1. Required if a *** not Not
sequence item is present. supported *** supported
> Coding (0008,0102) 1C See Section 8.2. Required if a *** not Not
Scheme sequence item is present. supported *** supported
Designator
> Coding (0008,0103) 1C See Section 8.2. Required if a *** not Not
Scheme sequence item is present and supported *** supported
Version the value of Coding Scheme
Designator (0008,0102) is not
sufficient to identify the Code
Value (0008,0100)
unambiguously.
> Code (0008,0104) 1C See Section 8.3. Required if a *** not Not
Meaning sequence item is present. supported *** supported

C.2.2 General Study - C.7.2.1

Attribute Name Tag Type Attribute Description TrueBeam 4DITC

4.0 v13.0

Study Instance (0020,000D 1 Unique identifier for the Study. Roundtrip Roundtrip
UID ) supported supported
Study Date (0008,0020) 2 Date the Study started. Roundtrip Roundtrip
supported supported
Study Time (0008,0030) 2 Time the Study started. Roundtrip Roundtrip
supported supported
Referring (0008,0090) 2 Name of the patient's referring Roundtrip Roundtrip
Physician’s physician supported supported
Name
Referring (0008,0096) 3 Identification of the patient's *** not Not
Physician referring physician. Only a supported *** supported
Identification single item shall be permitted
Sequence in this sequence.

Treatment Delivery Console 51 of 151

 IOD Details, General Study - C.7.2.1
Attribute Name Tag Type Attribute Description TrueBeam 4DITC
4.0 v13.0

> Person (0040,1101) 1 A coded entry which identifies *** not Not
Identification a person. The Code Meaning supported *** supported
Code Sequence attribute, though it will be
encoded with a VR of LO, may
be encoded according to the
rules of the PN VR (e.g. caret
'^' delimiters shall separate
name components), except
that a single component (i.e.
the whole name unseparated
by caret delimiters) is not
permitted. Name component
groups for use with multi-byte
character sets are permitted,
as long as they fit within the 64
characters (the length of the
LO VR). One or more Items
may be permitted in this
Sequence.
>> Code Value (0008,0100) 1C See Section 8.1. Required if a *** not Not
sequence item is present. supported *** supported
>> Coding (0008,0102) 1C See Section 8.2. Required if a *** not Not
Scheme sequence item is present. supported *** supported
Designator
>> Coding (0008,0103) 1C See Section 8.2. Required if a *** not Not
Scheme sequence item is present and supported *** supported
Version the value of Coding Scheme
Designator (0008,0102) is not
sufficient to identify the Code
Value (0008,0100)
unambiguously.
>> Code (0008,0104) 1C See Section 8.3. Required if a *** not Not
Meaning sequence item is present. supported *** supported
> Person’s (0040,1102) 3 Person's mailing address *** not Not
Address supported *** supported
> Person’s (0040,1103) 3 Person's telephone number(s) *** not Not
Telephone supported *** supported
Numbers
> Institution (0008,0080) 1C Institution or organization to *** not Not
Name which the identified individual supported *** supported
is responsible or accountable.
Shall not be present if
Institution Code Sequence
(0008,0082) is present.
> Institution (0008,0081) 3 Mailing address of the *** not Not
Address institution or organization to supported *** supported
which the identified individual
is responsible or accountable.

52 of 151 Varian Treatment Delivery

Console
 IOD Details, General Study - C.7.2.1
Attribute Name Tag Type Attribute Description TrueBeam 4DITC
4.0 v13.0

> Institution (0008,0082) 1C Institution or organization to *** not Not

Code Sequence which the identified individual supported *** supported
is responsible or accountable.
Shall not be present if
Institution Name (0008,0080)
is present. Only a single Item
shall be permitted in this
Sequence.
>> Code Value (0008,0100) 1C See Section 8.1. Required if a *** not Not
sequence item is present. supported *** supported
>> Coding (0008,0102) 1C See Section 8.2. Required if a *** not Not
Scheme sequence item is present. supported *** supported
Designator
>> Coding (0008,0103) 1C See Section 8.2. Required if a *** not Not
Scheme sequence item is present and supported *** supported
Version the value of Coding Scheme
Designator (0008,0102) is not
sufficient to identify the Code
Value (0008,0100)
unambiguously.
>> Code (0008,0104) 1C See Section 8.3. Required if a *** not Not
Meaning sequence item is present. supported *** supported
Study ID (0020,0010) 2 User or equipment generated Roundtrip Roundtrip
Study identifier. supported supported
Accession (0008,0050) 2 A RIS generated number that Roundtrip Roundtrip
Number identifies the order for the supported supported
Study.
Study (0008,1030) 3 Institution-generated Roundtrip Roundtrip
Description description or classification of supported supported
the Study (component)
performed.
Physician(s) of (0008,1048) 3 Names of the physician(s) who Roundtrip Roundtrip
Record are responsible for overall supported supported
patient care at time of Study
(see Section C.7.3.1 for
Performing Physician)
Physician(s) of (0008,1049) 3 Identification of the *** not Not
Record physician(s) who are supported *** supported
Identification responsible for overall patient
Sequence care at time of Study. One or
more items shall be included in
this sequence. If more than
one Item, the number and
order shall correspond to the
value of Physician(s) of Record
(0008,1048), if present.

Treatment Delivery Console 53 of 151

 IOD Details, General Study - C.7.2.1
Attribute Name Tag Type Attribute Description TrueBeam 4DITC
4.0 v13.0

> Person (0040,1101) 1 A coded entry which identifies *** not Not
Identification a person. The Code Meaning supported *** supported
Code Sequence attribute, though it will be
encoded with a VR of LO, may
be encoded according to the
rules of the PN VR (e.g. caret
'^' delimiters shall separate
name components), except
that a single component (i.e.
the whole name unseparated
by caret delimiters) is not
permitted. Name component
groups for use with multi-byte
character sets are permitted,
as long as they fit within the 64
characters (the length of the
LO VR). One or more Items
may be permitted in this
Sequence.
>> Code Value (0008,0100) 1C See Section 8.1. Required if a *** not Not
sequence item is present. supported *** supported
>> Coding (0008,0102) 1C See Section 8.2. Required if a *** not Not
Scheme sequence item is present. supported *** supported
Designator
>> Coding (0008,0103) 1C See Section 8.2. Required if a *** not Not
Scheme sequence item is present and supported *** supported
Version the value of Coding Scheme
Designator (0008,0102) is not
sufficient to identify the Code
Value (0008,0100)
unambiguously.
>> Code (0008,0104) 1C See Section 8.3. Required if a *** not Not
Meaning sequence item is present. supported *** supported
> Person’s (0040,1102) 3 Person's mailing address *** not Not
Address supported *** supported
> Person’s (0040,1103) 3 Person's telephone number(s) *** not Not
Telephone supported *** supported
Numbers
> Institution (0008,0080) 1C Institution or organization to *** not Not
Name which the identified individual supported *** supported
is responsible or accountable.
Shall not be present if
Institution Code Sequence
(0008,0082) is present.
> Institution (0008,0081) 3 Mailing address of the *** not Not
Address institution or organization to supported *** supported
which the identified individual
is responsible or accountable.

54 of 151 Varian Treatment Delivery

Console
 IOD Details, General Study - C.7.2.1
Attribute Name Tag Type Attribute Description TrueBeam 4DITC
4.0 v13.0

> Institution (0008,0082) 1C Institution or organization to *** not Not

Code Sequence which the identified individual supported *** supported
is responsible or accountable.
Shall not be present if
Institution Name (0008,0080)
is present. Only a single Item
shall be permitted in this
Sequence.
>> Code Value (0008,0100) 1C See Section 8.1. Required if a *** not Not
sequence item is present. supported *** supported
>> Coding (0008,0102) 1C See Section 8.2. Required if a *** not Not
Scheme sequence item is present. supported *** supported
Designator
>> Coding (0008,0103) 1C See Section 8.2. Required if a *** not Not
Scheme sequence item is present and supported *** supported
Version the value of Coding Scheme
Designator (0008,0102) is not
sufficient to identify the Code
Value (0008,0100)
unambiguously.
>> Code (0008,0104) 1C See Section 8.3. Required if a *** not Not
Meaning sequence item is present. supported *** supported
Name of (0008,1060) 3 Names of the physician(s) *** not Not
Physician(s) reading the Study. supported *** supported
Reading Study
Physician(s) (0008,1062) 3 Identification of the *** not Not
Reading Study physician(s) reading the Study. supported *** supported
Identification One or more items shall be
Sequence included in this sequence. If
more than one Item, the
number and order shall
correspond to the value of
Name of Physician(s) Reading
Study (0008,1060), if present.

Treatment Delivery Console 55 of 151

 IOD Details, General Study - C.7.2.1
Attribute Name Tag Type Attribute Description TrueBeam 4DITC
4.0 v13.0

> Person (0040,1101) 1 A coded entry which identifies *** not Not
Identification a person. The Code Meaning supported *** supported
Code Sequence attribute, though it will be
encoded with a VR of LO, may
be encoded according to the
rules of the PN VR (e.g. caret
'^' delimiters shall separate
name components), except
that a single component (i.e.
the whole name unseparated
by caret delimiters) is not
permitted. Name component
groups for use with multi-byte
character sets are permitted,
as long as they fit within the 64
characters (the length of the
LO VR). One or more Items
may be permitted in this
Sequence.
>> Code Value (0008,0100) 1C See Section 8.1. Required if a *** not Not
sequence item is present. supported *** supported
>> Coding (0008,0102) 1C See Section 8.2. Required if a *** not Not
Scheme sequence item is present. supported *** supported
Designator
>> Coding (0008,0103) 1C See Section 8.2. Required if a *** not Not
Scheme sequence item is present and supported *** supported
Version the value of Coding Scheme
Designator (0008,0102) is not
sufficient to identify the Code
Value (0008,0100)
unambiguously.
>> Code (0008,0104) 1C See Section 8.3. Required if a *** not Not
Meaning sequence item is present. supported *** supported
> Person’s (0040,1102) 3 Person's mailing address *** not Not
Address supported *** supported
> Person’s (0040,1103) 3 Person's telephone number(s) *** not Not
Telephone supported *** supported
Numbers
> Institution (0008,0080) 1C Institution or organization to *** not Not
Name which the identified individual supported *** supported
is responsible or accountable.
Shall not be present if
Institution Code Sequence
(0008,0082) is present.
> Institution (0008,0081) 3 Mailing address of the *** not Not
Address institution or organization to supported *** supported
which the identified individual
is responsible or accountable.

56 of 151 Varian Treatment Delivery

Console
 IOD Details, General Study - C.7.2.1
Attribute Name Tag Type Attribute Description TrueBeam 4DITC
4.0 v13.0

> Institution (0008,0082) 1C Institution or organization to *** not Not

Code Sequence which the identified individual supported *** supported
is responsible or accountable.
Shall not be present if
Institution Name (0008,0080)
is present. Only a single Item
shall be permitted in this
Sequence.
>> Code Value (0008,0100) 1C See Section 8.1. Required if a *** not Not
sequence item is present. supported *** supported
>> Coding (0008,0102) 1C See Section 8.2. Required if a *** not Not
Scheme sequence item is present. supported *** supported
Designator
>> Coding (0008,0103) 1C See Section 8.2. Required if a *** not Not
Scheme sequence item is present and supported *** supported
Version the value of Coding Scheme
Designator (0008,0102) is not
sufficient to identify the Code
Value (0008,0100)
unambiguously.
>> Code (0008,0104) 1C See Section 8.3. Required if a *** not Not
Meaning sequence item is present. supported *** supported
Referenced (0008,1110) 3 A sequence that provides *** not Not
Study reference to a Study SOP supported *** supported
Sequence Class/Instance pair. The
sequence may have zero or
more Items.
> Referenced (0008,1150) 1C Uniquely identifies the *** not Not
SOP Class UID referenced SOP Class. supported *** supported
Required if Referenced Study
Sequence (0008,1110) is sent.
> Referenced (0008,1155) 1C Uniquely identifies the *** not Not
SOP Instance referenced SOP Instance. supported *** supported
UID Required if Referenced Study
Sequence (0008,1110) is sent.
Procedure (0008,1032) 3 A Sequence that conveys the *** not Not
Code Sequence type of procedure performed. supported *** supported
One or more Items may be
included in this Sequence.
> Code Value (0008,0100) 1C See Section 8.1. Required if a *** not Not
sequence item is present. supported *** supported
> Coding (0008,0102) 1C See Section 8.2. Required if a *** not Not
Scheme sequence item is present. supported *** supported
Designator

Treatment Delivery Console 57 of 151

 IOD Details, Frame of Reference – C.7.4.1
Attribute Name Tag Type Attribute Description TrueBeam 4DITC
4.0 v13.0

> Coding (0008,0103) 1C See Section 8.2. Required if a *** not Not
Scheme sequence item is present and supported *** supported
Version the value of Coding Scheme
Designator (0008,0102) is not
sufficient to identify the Code
Value (0008,0100)
unambiguously.
> Code (0008,0104) 1C See Section 8.3. Required if a *** not Not
Meaning sequence item is present. supported *** supported

C.2.3 Frame of Reference – C.7.4.1

TRUEBEAM 4DITC
Attribute Name Tag Type Attribute Description
4.0 v13.0

Frame of (0020,0052) 1 Uniquely identifies the frame Roundtrip Not

Reference UID of reference for a Series. supported supported
Position (0020.1040 2 Part of the imaging target Roundtrip Not
Reference used as a reference supported supported
Indicator

C.2.4 General Equipment – C.7.5.1

TRUEBEAM 4DITC v13.0

Attribute Name Tag Type Attribute Description
4.0

Manufacturer (0008,0070) 2 Manufacturer of the Roundtrip Roundtrip

equipment that produced the supported supported
composite instances.
Institution Name (0008,0080) 3 Institution where the Roundtrip Roundtrip
equipment that produced the supported supported
composite instances is
located.
Institution (0008,0081) 3 Mailing address of the Roundtrip Roundtrip
Address institution where the supported supported
equipment that produced the
composite instances is
located.
Station Name (0008,1010) 3 User defined name identifying Roundtrip Roundtrip
the machine that produced the supported supported
composite instances.
Institutional (0008,1040) 3 Department in the institution Roundtrip Roundtrip
Department where the equipment that supported supported
Name produced the composite
instances is located.

58 of 151 Varian Treatment Delivery

Console
 IOD Details, General Equipment – C.7.5.1
TRUEBEAM 4DITC v13.0
Attribute Name Tag Type Attribute Description
4.0

Manufacturer’s (0008,1090) 3 Manufacturer's model name of Roundtrip Roundtrip

Model Name the equipment that produced supported supported
the composite instances.
Device Serial (0018,1000) 3 Manufacturer's serial number Roundtrip Roundtrip
Number of the equipment that supported supported
produced the composite
instances.
Software (0018,1020) 3 Manufacturer's designation of Roundtrip Roundtrip
Version(s) software version of the supported supported
equipment that produced the
composite instances.
Spatial (0018,1050) 3 The inherent limiting Roundtrip Roundtrip
Resolution resolution in mm of the supported supported
acquisition equipment for high
contrast objects for the data
gathering and reconstruction
technique chosen. If variable
across the images of the
series, the value at the image
center.
Date of Last (0018,1200) 3 Date when the image Roundtrip Roundtrip
Calibration acquisition device calibration supported supported
was last changed in any way.
Multiple entries may be used
for additional calibrations at
other times. See C.7.5.1.1.1
for further explanation.
Time of Last (0018,1201) 3 Time when the image Roundtrip Roundtrip
Calibration acquisition device calibration supported supported
was last changed in any way.
Multiple entries may be used.
See C.7.5.1.1.1 for further
explanation.
Pixel Padding (0028,0120) 3 Value of pixels not present in Roundtrip Roundtrip
Value the native image added to an supported supported
image to pad to rectangular
format. See C.7.5.1.1.2 for
further explanation.
Note:
The Value Representation of
this Attribute is determined by
the value of Pixel
Representation (0028,0103).

Treatment Delivery Console 59 of 151

 IOD Details, RT Series – C.8.8.1
C.2.5 RT Series – C.8.8.1

Attribute Name Tag Type Attribute Description TrueBeam 4DITC v13.0

4.0
Modality (0008,0060) 1 Type of equipment that Roundtrip Roundtrip
originally acquired the data. supported supported
Enumerated Values:
RTIMAGE = RT Image
RTDOSE = RT Dose
RTSTRUCT = RT Structure
Set
RTPLAN = RT Plan
RTRECORD = RT Treatment
Record
See C.8.8.1.1.
Series Instance (0020,000E) 1 Unique identifier of the series. Roundtrip Roundtrip
UID supported supported
Series Number (0020,0011) 2 A number that identifies this Roundtrip Roundtrip
series. supported supported
Series (0008,103E) 3 User provided description of Roundtrip Roundtrip
Description the series. supported. supported.
Referenced (0008,1111) 3 Uniquely identifies the *** not Not supported
Performed Performed Procedure Step supported ***
Procedure Step SOP Instance to which the
Sequence Series is related (e.g. a
Modality or General-Purpose
Performed Procedure Step
SOP Instance). One or more
items may be included in this
sequence.
> Referenced (0008,1150) 1C Uniquely identifies the *** not Not supported
SOP Class UID referenced SOP Class. supported ***
Required if Referenced
Performed Procedure Step
Sequence (0008,1111) is sent.
> Referenced (0008,1155) 1C Uniquely identifies the *** not Not supported
SOP Instance referenced SOP Instance. supported ***
UID Required if Referenced
Performed Procedure Step
Sequence (0008,1111) is sent.
Request (0040,0275) 3 Sequence that contains *** not Not supported
Attributes attributes from the Imaging supported ***
Sequence Service Request. The
sequence may have one or
more Items.
> Requested (0040,1001) 1 Identifier that identifies the *** not Not supported
Procedure ID Requested Procedure in the supported ***
Imaging Service Request.

60 of 151 Varian Treatment Delivery

Console
 IOD Details, RT Series – C.8.8.1
Attribute Name Tag Type Attribute Description TrueBeam 4DITC v13.0
4.0
> Reason for (0040,1002) 3 Reason for requesting this *** not Not supported
the Requested procedure. supported ***
Procedure
> Reason for (0040,100A) 3 Coded Reason for requesting *** not Not supported
Requested this procedure. supported ***
Procedure
Code Sequence
>> Code Value (0008,0100) 1C See Section 8.1. Required if a *** not Not supported
sequence item is present. supported ***
>> Coding (0008,0102) 1C See Section 8.2. Required if a *** not Not supported
Scheme sequence item is present. supported ***
Designator
>> Coding (0008,0103) 1C See Section 8.2. Required if a *** not Not supported
Scheme sequence item is present and supported ***
Version the value of Coding Scheme
Designator (0008,0102) is not
sufficient to identify the Code
Value (0008,0100)
unambiguously.
>> Code (0008,0104) 1C See Section 8.3. Required if a *** not Not supported
Meaning sequence item is present. supported ***
> Scheduled (0040,0009) 1 Identifier that identifies the *** not Not supported
Procedure Step Scheduled Procedure Step. supported ***
ID
> Scheduled (0040,0007) 3 Institution-generated *** not Not supported
Procedure Step description or classification of supported ***
Description the Scheduled Procedure Step
to be performed.
> Scheduled (0040,0008) 3 Sequence describing the *** not Not supported
Protocol Code Scheduled Protocol following a supported ***
Sequence specific coding scheme. This
sequence contains one or
more Items.
>> Code Value (0008,0100) 1C See Section 8.1. Required if a *** not Not supported
sequence item is present. supported ***
>> Coding (0008,0102) 1C See Section 8.2. Required if a *** not Not supported
Scheme sequence item is present. supported ***
Designator
>> Coding (0008,0103) 1C See Section 8.2. Required if a *** not Not supported
Scheme sequence item is present and supported ***
Version the value of Coding Scheme
Designator (0008,0102) is not
sufficient to identify the Code
Value (0008,0100)
unambiguously.
>> Code (0008,0104) 1C See Section 8.3. Required if a *** not Not supported
Meaning sequence item is present. supported ***

Treatment Delivery Console 61 of 151

 IOD Details, RT Series – C.8.8.1
Attribute Name Tag Type Attribute Description TrueBeam 4DITC v13.0
4.0
>> Protocol (0040,0440) 3 Sequence that specifies the *** not Not supported
Context context for the Scheduled supported ***
Sequence Protocol Code Sequence Item.
One or more items may be
included in this sequence.
>>> Code Value (0008,0100) 1C See Section 8.1. Required if a *** not Not supported
sequence item is present. supported ***
>>> Coding (0008,0102) 1C See Section 8.2. Required if a *** not Not supported
Scheme sequence item is present. supported ***
Designator
>>> Coding (0008,0103) 1C See Section 8.2. Required if a *** not Not supported
Scheme sequence item is present and supported ***
Version the value of Coding Scheme
Designator (0008,0102) is not
sufficient to identify the Code
Value (0008,0100)
unambiguously.
>>> Code (0008,0104) 1C See Section 8.3. Required if a *** not Not supported
Meaning sequence item is present. supported ***
>>> Content (0040,0441) 3 Sequence that specifies *** not Not supported
Item Modifier modifiers for a Protocol supported ***
Sequence Context Content Item. One or
more items may be included in
this sequence. See Section
C.4.10.1.
>>>> Code (0008,0100) 1C See Section 8.1. Required if a *** not Not supported
Value sequence item is present. supported ***
>>>> Coding (0008,0102) 1C See Section 8.2. Required if a *** not Not supported
Scheme sequence item is present. supported ***
Designator
>>>> Coding (0008,0103) 1C See Section 8.2. Required if a *** not Not supported
Scheme sequence item is present and supported ***
Version the value of Coding Scheme
Designator (0008,0102) is not
sufficient to identify the Code
Value (0008,0100)
unambiguously.
>>>> Code (0008,0104) 1C See Section 8.3. Required if a *** not Not supported
Meaning sequence item is present. supported ***
Performed (0040,0253) 3 User or equipment generated *** not Not supported
Procedure Step identifier of that part of a supported ***
ID Procedure that has been
carried out within this step.
Performed (0040,0244) 3 Date on which the Performed *** not Not supported
Procedure Step Procedure Step started. supported ***
Start Date

62 of 151 Varian Treatment Delivery

Console
 IOD Details, RT Series – C.8.8.1
Attribute Name Tag Type Attribute Description TrueBeam 4DITC v13.0
4.0
Performed (0040,0245) 3 Time on which the Performed *** not Not supported
Procedure Step Procedure Step started. supported ***
Start Time
Performed (0040,0254) 3 Institution-generated *** not Not supported
Procedure Step description or classification of supported ***
Description the Procedure Step that was
performed.
Performed (0040,0260) 3 Sequence describing the *** not Not supported
Protocol Code Protocol performed for this supported ***
Sequence Procedure Step. One or more
Items may be included in this
Sequence.
> Code Value (0008,0100) 1C See Section 8.1. Required if a *** not Not supported
sequence item is present. supported ***
> Coding (0008,0102) 1C See Section 8.2. Required if a *** not Not supported
Scheme sequence item is present. supported ***
Designator
> Coding (0008,0103) 1C See Section 8.2. Required if a *** not Not supported
Scheme sequence item is present and supported ***
Version the value of Coding Scheme
Designator (0008,0102) is not
sufficient to identify the Code
Value (0008,0100)
unambiguously.
> Code (0008,0104) 1C See Section 8.3. Required if a *** not Not supported
Meaning sequence item is present. supported ***
> Protocol (0040,0440) 3 Sequence that specifies the *** not Not supported
Context context for the Performed supported ***
Sequence Protocol Code Sequence Item.
One or more items may be
included in this sequence.
>> Value Type (0040,A040) 1 The type of the value encoded *** not Not supported
in this name-value Item. supported ***
Defined Terms:
DATETIME
DATE
TIME
PNAME
UIDREF
TEXT
CODE
NUMERIC.
>> Concept (0040,A043) 1 Coded concept name of this *** not Not supported
Name Code name-value Item. supported ***
Sequence
>>> Code Value (0008,0100) 1C See Section 8.1. Required if a *** not Not supported
sequence item is present. supported ***

Treatment Delivery Console 63 of 151

 IOD Details, RT Series – C.8.8.1
Attribute Name Tag Type Attribute Description TrueBeam 4DITC v13.0
4.0
>>> Coding (0008,0102) 1C See Section 8.2. Required if a *** not Not supported
Scheme sequence item is present. supported ***
Designator
>>> Coding (0008,0103) 1C See Section 8.2. Required if a *** not Not supported
Scheme sequence item is present and supported ***
Version the value of Coding Scheme
Designator (0008,0102) is not
sufficient to identify the Code
Value (0008,0100)
unambiguously.
>>> Code (0008,0104) 1C See Section 8.3. Required if a *** not Not supported
Meaning sequence item is present. supported ***
>> DateTime (0040,A120) 1C Datetime value for this name- *** not Not supported
value Item. Required if Value supported ***
Type (0040,A040) is
DATETIME.
>> Date (0040,A121) 1C Date value for this name-value *** not Not supported
Item. Required if Value Type supported ***
(0040,A040) is DATE.
>> Time (0040,A122) 1C Time value for this name-value *** not Not supported
Item. Required if Value Type supported ***
(0040,A040) is TIME.
>> Person (0040,A123) 1C Person name value for this *** not Not supported
Name name-value Item. Required if supported ***
Value Type (0040,A040) is
PNAME.
>> UID (0040,A124) 1C UID value for this name-value *** not Not supported
Item. Required if Value Type supported ***
(0040,A040) is UIDREF.
>> Text Value (0040,A160) 1C Text value for this name-value *** not Not supported
Item. Required if Value Type supported ***
(0040,A040) is TEXT.
>> Concept (0040,A168) 1C Coded concept value of this *** not Not supported
Code Sequence name-value Item. Required if supported ***
Value Type (0040,A040) is
CODE.
>>> Code Value (0008,0100) 1C See Section 8.1. Required if a *** not Not supported
sequence item is present. supported ***
>>> Coding (0008,0102) 1C See Section 8.2. Required if a *** not Not supported
Scheme sequence item is present. supported ***
Designator

64 of 151 Varian Treatment Delivery

Console
 IOD Details, RT Series – C.8.8.1
Attribute Name Tag Type Attribute Description TrueBeam 4DITC v13.0
4.0
>>> Coding (0008,0103) 1C See Section 8.2. Required if a *** not Not supported
Scheme sequence item is present and supported ***
Version the value of Coding Scheme
Designator (0008,0102) is not
sufficient to identify the Code
Value (0008,0100)
unambiguously.
>>> Code (0008,0104) 1C See Section 8.3. Required if a *** not Not supported
Meaning sequence item is present. supported ***
>> Numeric (0040,A30A 1C Numeric value for this name- *** not Not supported
Value ) value Item. Required if Value supported ***
Type (0040,A040) is
NUMERIC.
>> (0040,08EA 1C Units of measurement for a *** not Not supported
Measurement ) numeric value in this supported ***
Units Code namevalue Item. Required if
Sequence Value Type (0040,A040) is
NUMERIC.
>>> Code Value (0008,0100) 1C See Section 8.1. Required if a *** not Not supported
sequence item is present. supported ***
>>> Coding (0008,0102) 1C See Section 8.2. Required if a *** not Not supported
Scheme sequence item is present. supported ***
Designator
>>> Coding (0008,0103) 1C See Section 8.2. Required if a *** not Not supported
Scheme sequence item is present and supported ***
Version the value of Coding Scheme
Designator (0008,0102) is not
sufficient to identify the Code
Value (0008,0100)
unambiguously.
>>> Code (0008,0104) 1C See Section 8.3. Required if a *** not Not supported
Meaning sequence item is present. supported ***
>> Content Item (0040,0441) 3 Sequence that specifies *** not Not supported
Modifier modifiers for a Protocol supported ***
Sequence Context Content Item. One or
more items may be included in
this sequence. See Section
C.4.10.1.

Treatment Delivery Console 65 of 151

 IOD Details, RT Series – C.8.8.1
Attribute Name Tag Type Attribute Description TrueBeam 4DITC v13.0
4.0
>>> Value Type (0040,A040) 1 The type of the value encoded *** not Not supported
in this name-value Item. supported ***
Defined Terms:
DATETIME
DATE
TIME
PNAME
UIDREF
TEXT
CODE
NUMERIC.
>>> Concept (0040,A043) 1 Coded concept name of this *** not Not supported
Name Code name-value Item. supported ***
Sequence
>>>> Code (0008,0100) 1C See Section 8.1. Required if a *** not Not supported
Value sequence item is present. supported ***
>>>> Coding (0008,0102) 1C See Section 8.2. Required if a *** not Not supported
Scheme sequence item is present. supported ***
Designator
>>>> Coding (0008,0103) 1C See Section 8.2. Required if a *** not Not supported
Scheme sequence item is present and supported ***
Version the value of Coding Scheme
Designator (0008,0102) is not
sufficient to identify the Code
Value (0008,0100)
unambiguously.
>>>> Code (0008,0104) 1C See Section 8.3. Required if a *** not Not supported
Meaning sequence item is present. supported ***
>>> DateTime (0040,A120) 1C Datetime value for this name- *** not Not supported
value Item. Required if Value supported ***
Type (0040,A040) is
DATETIME.
>>> Date (0040,A121) 1C Date value for this name-value *** not Not supported
Item. Required if Value Type supported ***
(0040,A040) is DATE.
>>> Time (0040,A122) 1C Time value for this name-value *** not Not supported
Item. Required if Value Type supported ***
(0040,A040) is TIME.
>>> Person (0040,A123) 1C Person name value for this *** not Not supported
Name name-value Item. Required if supported ***
Value Type (0040,A040) is
PNAME.
>>> UID (0040,A124) 1C UID value for this name-value *** not Not supported
Item. Required if Value Type supported ***
(0040,A040) is UIDREF.

66 of 151 Varian Treatment Delivery

Console
 IOD Details, RT Series – C.8.8.1
Attribute Name Tag Type Attribute Description TrueBeam 4DITC v13.0
4.0
>>> Text Value (0040,A160) 1C Text value for this name-value *** not Not supported
Item. Required if Value Type supported ***
(0040,A040) is TEXT.
>>> Concept (0040,A168) 1C Coded concept value of this *** not Not supported
Code Sequence name-value Item. Required if supported ***
Value Type (0040,A040) is
CODE.
>>>> Code (0008,0100) 1C See Section 8.1. Required if a *** not Not supported
Value sequence item is present. supported ***
>>>> Coding (0008,0102) 1C See Section 8.2. Required if a *** not Not supported
Scheme sequence item is present. supported ***
Designator
>>>> Coding (0008,0103) 1C See Section 8.2. Required if a *** not Not supported
Scheme sequence item is present and supported ***
Version the value of Coding Scheme
Designator (0008,0102) is not
sufficient to identify the Code
Value (0008,0100)
unambiguously.
>>>> Code (0008,0104) 1C See Section 8.3. Required if a *** not Not supported
Meaning sequence item is present. supported ***
>>> Numeric (0040,A30A 1C Numeric value for this name- *** not Not supported
Value ) value Item. Required if Value supported ***
Type (0040,A040) is
NUMERIC.
>>> (0040,08EA 1C Units of measurement for a *** not Not supported
Measurement ) numeric value in this supported ***
Units Code namevalue Item. Required if
Sequence Value Type (0040,A040) is
NUMERIC.
>>>> Code (0008,0100) 1C See Section 8.1. Required if a *** not Not supported
Value sequence item is present. supported ***
>>>> Coding (0008,0102) 1C See Section 8.2. Required if a *** not Not supported
Scheme sequence item is present. supported ***
Designator
>>>> Coding (0008,0103) 1C See Section 8.2. Required if a *** not Not supported
Scheme sequence item is present and supported ***
Version the value of Coding Scheme
Designator (0008,0102) is not
sufficient to identify the Code
Value (0008,0100)
unambiguously.
>>>> Code (0008,0104) 1C See Section 8.3. Required if a *** not Not supported
Meaning sequence item is present. supported ***

Treatment Delivery Console 67 of 151

 IOD Details, RT General Plan – C.8.8.9
C.2.6 RT General Plan – C.8.8.9

Attribute Name Tag Type Attribute Description TrueBeam 4DITC

4.0 v13.0

RT Plan Label (300A,0002) 1 User-defined label for Roundtrip Roundtrip

treatment plan. supported supported
RT Plan Name (300A,0003) 3 User-defined name for Roundtrip Roundtrip
treatment plan. supported supported
RT Plan (300A,0004) 3 User-defined description of Roundtrip Roundtrip
Description treatment plan. supported supported
Instance (0020,0013) 3 A number that identifies this *** not Not
Number object instance. supported *** supported
Operators’ (0008,1070) 2 Name of operator(s) creating Roundtrip Roundtrip
Name treatment plan. supported supported
RT Plan Date (300A,0006) 2 Date treatment plan was last Roundtrip Roundtrip
modified. supported supported
RT Plan Time (300A,0007) 2 Time treatment plan was last Roundtrip Roundtrip
modified. supported supported
Treatment (300A,0009) 3 Planned treatment protocols. *** not Not
Protocols supported *** supported
Plan Intent (300A,000A 3 Intent of this plan. Roundtrip Roundtrip
) Defined Terms: supported supported
CURATIVE = curative therapy
on patient
PALLIATIVE = palliative
therapy on patient
PROPHYLACTIC =
preventative therapy on patient
VERIFICATION = verification
of patient plan using phantom
MACHINE_QA = Quality
assurance of the delivery
machine (independently of a
specific patient)
RESEARCH = Research
project
SERVICE = Machine repair or
maintenance operation
Treatment Sites (300A,000B 3 Planned treatment sites. Roundtrip Not
) supported supported

68 of 151 Varian Treatment Delivery

Console
 IOD Details, RT General Plan – C.8.8.9
Attribute Name Tag Type Attribute Description TrueBeam 4DITC
4.0 v13.0

RT Plan (300A,000C 1 Describes whether RT Plan is Roundtrip Roundtrip

Geometry ) based on patient or treatment supported supported
device geometry. See
C.8.8.9.1.
Defined Terms:
PATIENT = RT Structure Set
exists
TREATMENT_DEVICE = RT
Structure Set does not exist
Referenced (300C,0060 1C Introduces sequence of one Roundtrip Roundtrip
Structure Set ) Class/Instance pair describing supported supported
Sequence instance of RT Structure Set
on which the RT Plan is based.
Only a single item shall be
permitted in this sequence.
Required if RT Plan Geometry
(300A,000C) is PATIENT.
> Referenced (0008,1150) 1C Uniquely identifies the Roundtrip Roundtrip
SOP Class UID referenced SOP Class. supported supported
Required if Referenced
Structure Set Sequence
(300C,0060) is sent.
> Referenced (0008,1155) 1C Uniquely identifies the Roundtrip Roundtrip
SOP Instance referenced SOP Instance. supported supported
UID Required if Referenced
Structure Set Sequence
(300C,0060) is sent.
Referenced (300C,0080 3 Introduces sequence of related *** not Not
Dose Sequence ) SOP Class/Instance pairs supported *** supported
describing related instances of
RT Dose (for grids and
named/unnamed point doses).
One or more items may be
included in this sequence. See
Note 1.
> Referenced (0008,1150) 1C Uniquely identifies the *** not Not
SOP Class UID referenced SOP Class. supported *** supported
Required if Referenced RT
Dose Sequence (300C,0080)
is sent.
> Referenced (0008,1155) 1C Uniquely identifies the *** not Not
SOP Instance referenced SOP Instance. supported *** supported
UID Required if Referenced RT
Dose Sequence (300C,0080)
is sent.

Treatment Delivery Console 69 of 151

 IOD Details, RT General Plan – C.8.8.9
Attribute Name Tag Type Attribute Description TrueBeam 4DITC
4.0 v13.0

Referenced RT (300C,0002 3 Introduces sequence of related Roundtrip Roundtrip

Plan Sequence ) SOP Class/Instance pairs supported supported
describing related instances of
RT Plan. One or more items
may be included in this
sequence.
> Referenced (0008,1150) 1C Uniquely identifies the Roundtrip Roundtrip
SOP Class UID referenced SOP Class. supported supported
Required if Referenced RT
Plan Sequence (300C,0002) is
sent.
> Referenced (0008,1155) 1C Uniquely identifies the Roundtrip Roundtrip
SOP Instance referenced SOP Instance. supported supported
UID Required if Referenced RT
Plan Sequence (300C,0002) is
sent.
> RT Plan (300A,0055) 1C Relationship of referenced Roundtrip Roundtrip
Relationship plan with respect to current supported supported
plan. Required if Referenced
RT Plan Sequence
(300C,0002) is sent.
Defined Terms:
PRIOR = plan delivered prior
to current treatment
ALTERNATIVE = alternative
plan prepared for current
treatment
PREDECESSOR = plan used
in derivation of current plan
VERIFIED_PLAN = plan which
is verified using the current
plan. This value shall only be
used if Plan Intent
(300A,000A) is present and
has a value of VERIFICATION.
Beam Line Data (300B,1008) 3 Version Number that is set for *** not Not
Table Version Look-up Table (and/or for each supported *** supported
beam tune in Look-up Table in
future)
Plan Integrity (3287,XX00 3 Introduces sequence of Roundtrip Roundtrip
Sequence ) checksum on dose-relevant supported supported
data in this RT Plan. Exactly
one item may be included in
this sequence.

70 of 151 Varian Treatment Delivery

Console
 IOD Details, RT Prescription – C.8.8.10
Attribute Name Tag Type Attribute Description TrueBeam 4DITC
4.0 v13.0

> Plan Integrity (3287,XX01 1 Hash value calculated from Roundtrip Roundtrip
Hash ) selected data of this RT Plan supported supported
along a specific algorith whose
version number is specified in
Plan Integrity Hash Version
(3287,xx02).
> Plan Integrity (3287,XX02 1 Version of hash algorithm used Roundtrip Roundtrip
Hash Version ) to calculate value of Plan supported supported
Integrity Hash (3287,xx01).

C.2.7 RT Prescription – C.8.8.10

TrueBeam 4DITC v13.0

Attribute Name Tag Type Attribute Description
4.0

Prescription (300A,000E 3 User-defined description of Roundtrip Roundtrip

Description ) treatment prescription. supported supported
Dose Reference (300A,0010) 3 Introduces sequence of Dose Roundtrip Roundtrip
Sequence References. One or more items supported supported
may be included in this
sequence.
> Dose (300A,0012) 1C Identification number of the Roundtrip Roundtrip
Reference Dose Reference. The value of supported supported
Number Dose Reference Number
(300A,0012) shall be unique
within the RT Plan in which it is
created. Required if Dose
Reference Sequence
(300A,0012) is sent.
> Dose (300A,0013) 3 A unique identifier for a Dose *** not Roundtrip
Reference UID Reference that can be used to supported supported
link the same entity across ***
multiple RT Plan objects.
> Dose (300A,0014) 1C Structure type of Dose Roundtrip Roundtrip
Reference Reference. supported supported
Structure Type Required if Dose Reference
Sequence (300A,0010) is sent.
Defined Terms:
POINT = dose reference point
specified as
ROI
VOLUME = dose reference
volume specified as ROI
COORDINATES = point
specified by Dose Reference
Point Coordinates (300A,0018)
SITE = dose reference clinical
site
Treatment Delivery Console 71 of 151
 IOD Details, RT Prescription – C.8.8.10
TrueBeam 4DITC v13.0
Attribute Name Tag Type Attribute Description
4.0

> Dose (300A,0016) 3 User-defined description of Roundtrip Roundtrip

Reference Dose Reference. supported supported
Description
> Referenced (3006,0084) 1C Uniquely identifies ROI Roundtrip Roundtrip
ROI Number representing the dose supported supported
reference specified by ROI
Number (3006,0022) in
Structure Set ROI Sequence
(3006,0020) in Structure Set
Module within RT Structure Set
in Referenced Structure Set
Sequence (300C,0060) in RT
General Plan Module.
Required if Dose Reference
Structure Type (300A,0014) is
POINT or VOLUME and Dose
Reference Sequence
(300A,0010) is sent.
> Dose (300A,0018) 1C Coordinates (x,y,z) of Roundtrip Roundtrip
Reference Point Reference Point in the patient supported supported
Coordinates based coordinate system
described in C.7.6.2.1.1 (mm).
Required if Dose Reference
Structure Type (300A,0014) is
COORDINATES and Dose
Reference Sequence
(300A,0010) is sent.
> Nominal Prior (300A,001A 3 Dose (in Gy) from prior Roundtrip Roundtrip
Dose ) treatment to this Dose supported supported
Reference (e.g. from a
previous course of treatment).
> Dose (300A,0020) 1C Type of Dose Reference. Roundtrip Roundtrip
Reference Type Required if Dose Reference supported supported
Sequence (300A,0010) is sent.
Defined Terms:
TARGET = treatment target
(corresponding to GTV, PTV,
or CTV in ICRU50)
ORGAN_AT_RISK = Organ at
Risk (as defined in ICRU50)
> Constraint (300A,0021) 3 Relative importance of Roundtrip Roundtrip
Weight satisfying constraint, where supported supported
high values represent more
important constraints.
> Delivery (300A,0022) 3 The dose (in Gy) which when Roundtrip Roundtrip
Warning Dose reached or exceeded should supported supported
cause some action to be taken.

72 of 151 Varian Treatment Delivery

Console
 IOD Details, RT Prescription – C.8.8.10
TrueBeam 4DITC v13.0
Attribute Name Tag Type Attribute Description
4.0

> Delivery (300A,0023) 3 The maximum dose (in Gy) Roundtrip Roundtrip
Maximum Dose which can be delivered to the supported supported
dose reference.
> Target (300A,0025) 3 Minimum permitted dose (in *** not Roundtrip
Minimum Dose Gy) to Dose Reference if Dose supported supported
Reference Type (300A,0020) is ***
TARGET.
> Target (300A,0026) 3 Prescribed dose (in Gy) to Roundtrip Roundtrip
Prescription Dose Reference if Dose supported supported
Dose Reference Type (300A,0020) is
TARGET.
> Target (300A,0027) 3 Maximum permitted dose (in Roundtrip Roundtrip
Maximum Dose Gy) to Dose Reference if Dose supported supported
Reference Type (300A,0020) is
TARGET.
> Referenced (3267,XX00 3 *** not Not
Patient Volume ) supported ** supported
Id
> Target (300A,0028) 3 Maximum permitted fraction (in *** not Not
Underdose percent) of Target to receive supported supported
Volume less than the Target ***
Fraction Prescription Dose if Dose
Reference Type (300A,0020) is
TARGET and Dose Reference
Structure Type (300A,0014) is
VOLUME. See C.8.8.10.1.
> Organ at Risk (300A,002A 3 Maximum dose (in Gy) to entire *** not Not
Full-volume ) Dose Reference if Dose supported supported
Dose Reference Type (300A,0020) is ***
ORGAN_AT_RISK and Dose
Reference Structure Type
(300A,0014) is VOLUME.
> Organ at Risk (300A,002B 3 Maximum permitted dose (in Roundtrip Roundtrip
Limit Dose ) Gy) to any part of Dose supported supported
Reference if Dose Reference
Type (300A,0020) is
ORGAN_AT_RISK and Dose
Reference Structure Type
(300A,0014) is VOLUME.
> Organ at Risk (300A,002C 3 Maximum dose (in Gy) to non- Roundtrip Roundtrip
Maximum Dose ) overdosed part of Dose supported supported
Reference if Dose Reference
Type (300A,0020) is
ORGAN_AT_RISK and Dose
Reference Structure Type
(300A,0014) is VOLUME.

Treatment Delivery Console 73 of 151

 IOD Details, RT Tolerance Tables – C.8.8.11
TrueBeam 4DITC v13.0
Attribute Name Tag Type Attribute Description
4.0

> Organ at Risk (300A,002D 3 Maximum permitted fraction (in Roundtrip Roundtrip
Overdose ) percent) of the Organ at Risk to supported supported
Volume receive more than the Organ at
Fraction Risk Maximum Dose if Dose
Reference Type (300A,0020) is
ORGAN_AT_RISK and Dose
Reference Structure Type
(300A,0014) is VOLUME.

C.2.8 RT Tolerance Tables – C.8.8.11

TrueBeam 4DITC
Attribute Name Tag Type Attribute Description
4.0 v13.0
Tolerance Table (300A,0040) 3 Introduces sequence of Roundtrip Roundtrip
Sequence tolerance tables to be used for supported supported
delivery of treatment plan. One
or more items may be included
in this sequence. See Note 1.
> Tolerance (300A,0042) 1C Identification number of the Roundtrip Roundtrip
Table Number Tolerance Table. The value of supported. supported.
Tolerance Table Number
(300A,0042) shall be unique
within the RT Plan in which it is
created. Required if Tolerance
Table Sequence (300A,0040) is
sent.
> Tolerance (300A,0043) 3 User-defined label for Roundtrip Roundtrip
Table Label Tolerance Table. supported supported.
> Gantry Angle (300A,0044) 3 Maximum permitted difference Roundtrip Roundtrip
Tolerance (in degrees) between planned supported supported.
and delivered Gantry Angle.
> Gantry Pitch (300A,014E 3 Maximum permitted difference *** not *** not
Angle Tolerance ) (in degrees) between planned supported supported
and delivered Gantry Pitch *** ***
Angle.
> Beam Limiting (300A,0046) 3 Maximum permitted difference Roundtrip Roundtrip
Device Angle (in degrees) between planned supported supported
Tolerance and delivered Beam Limiting
Device Angle.
> Beam Limiting (300A,0048) 3 Introduces sequence of beam Roundtrip Roundtrip
Device limiting device (collimator) supported supported
Tolerance tolerances. One or more items
Sequence may be included in this
sequence.

74 of 151 Varian Treatment Delivery

Console
 IOD Details, RT Tolerance Tables – C.8.8.11
TrueBeam 4DITC
Attribute Name Tag Type Attribute Description
4.0 v13.0
>> RT Beam (300A,00B8 1C Type of beam limiting device Roundtrip Roundtrip
Limiting Device ) (collimator). supported supported
Type Required if Beam Limiting
Device Tolerance Sequence
(300A,0048) is sent.
Enumerated Values:
X = symmetric jaw pair in IEC X
direction
Y = symmetric jaw pair in IEC Y
direction
ASYMX = asymmetric jaw pair
in IEC X direction
ASYMY = asymmetric pair in
IEC Y direction
MLCX = multileaf (multi-
element) jaw pair in IEC X
direction
MLCY = multileaf (multi-
element) jaw pair in IEC Y
direction
>> Beam (300A,004A 1C Maximum permitted difference Roundtrip Roundtrip
Limiting Device ) (in mm) between planned and supported supported
Position delivered leaf (element) or jaw
Tolerance positions for current beam
limiting device (collimator).
Required if Beam Limiting
Device Tolerance Sequence
(300A,0048) is sent.
> Patient (300A,004C 3 Maximum permitted difference Roundtrip Roundtrip
Support Angle ) (in degrees) between planned supported supported
Tolerance and delivered Patient Support
Angle.
> Table Top (300A,004E 3 Maximum permitted difference Roundtrip Roundtrip
Eccentric Angle ) (in degrees) between planned supported supported
Tolerance and delivered Table Top
Eccentric Angle.
> Table Top (300A,004F 3 Maximum permitted difference Beam will *** not
Pitch Angle ) (in degrees) between the be valid if supported
Tolerance planned and delivered Table the tag is ***
Top Pitch Angle. not
available or
has any
value.
This value
will be read
and
ignored.

Treatment Delivery Console 75 of 151

 IOD Details, RT Patient Setup – C.8.8.12
TrueBeam 4DITC
Attribute Name Tag Type Attribute Description
4.0 v13.0
> Table Top Roll (300A,0050) 3 Maximum permitted difference Beam will *** not
Angle Tolerance (in degrees) between the be valid if supported
planned and delivered Table the tag is ***
Top Roll Angle. not
available or
has any
value.
This value
will be read
and
ignored.
> Table Top (300A,0051) 3 Maximum permitted difference Roundtrip Roundtrip
Vertical Position (in mm) between planned and supported supported
Tolerance delivered Table Top Vertical
Position.
> Table Top (300A,0052) 3 Maximum permitted difference Roundtrip Roundtrip
Longitudinal (in mm) between planned and supported supported
Position delivered Table Top
Tolerance Longitudinal Position.
> Table Top (300A,0053) 3 Maximum permitted difference Roundtrip Roundtrip
Lateral Position (in mm) between planned and supported supported
Tolerance delivered Table Top Lateral
Position.

C.2.9 RT Patient Setup – C.8.8.12

Attribute Name Tag Type Attribute Description TrueBeam 4DITC

4.0 v13.0

Patient Setup (300A,0180) 1 Introduces sequence of patient Roundtrip Roundtrip

Sequence setup data for current plan. One supported supported
or more items may be included
in this sequence.
> Patient Setup (300A,0182) 1 Identification number of the Roundtrip Roundtrip
Number Patient Setup. The value of supported supported
Patient Setup Number
(300A,0182) shall be unique
within the RT Plan in which it is
created.
> Patient Setup (300A,0183) 3 The user-defined label for the *** not *** not
Label patient setup. supported supported
*** ***

76 of 151 Varian Treatment Delivery

Console
 IOD Details, RT Patient Setup – C.8.8.12
Attribute Name Tag Type Attribute Description TrueBeam 4DITC
4.0 v13.0

> Patient (0018,5100) 1C Patient position descriptor Roundtrip Roundtrip

Position relative to the equipment. supported supported
Required if Patient Additional
Position (300A,0184) is not
present. See Section
C.7.3.1.1.2 for Defined Terms
and further explanation.
> Patient (300A,0184) 1C User-defined additional *** not *** not
Additional description of patient position. supported supported
Position Required if Patient Position *** ***
(0018,5100) is not present.
> Referenced (300A,0401) 3 Introduces sequence of setup Roundtrip *** not
Image Setup verification images for this supported supported
Sequence patient setup. One or more ***
items may be included in this
sequence. See C.8.8.12.1.1
>> Setup Image (300A,0402) 3 Comment on the Setup Image. *** not *** not
Comment supported supported
*** ***
>> Referenced (0008,1150) 1 Uniquely identifies the *** not *** not
SOP Class UID referenced SOP Class. supported supported
*** ***
>> Referenced (0008,1155) 1 Uniquely identifies the *** not *** not
SOP Instance referenced SOP Instance. supported supported
UID *** ***
>> Referenced (0008,1160) 1 Identifies the frame numbers *** not *** not
Frame Number within the Referenced SOP supported supported
Instance to which the reference *** ***
applies. The first frame shall be
denoted as frame number 1.
Note: This Attribute may be
multi-valued.
Required if the Referenced
SOP Instance is a multi-frame
image and the reference does
not apply to all frames.
> Fixation (300A,0190) 3 Introduces sequence of Fixation *** not *** not
Device Devices used in Patient Setup. supported supported
Sequence One or more items may be *** ***
included in this sequence.

Treatment Delivery Console 77 of 151

 IOD Details, RT Patient Setup – C.8.8.12
Attribute Name Tag Type Attribute Description TrueBeam 4DITC
4.0 v13.0

>> Fixation (300A,0192) 1C Type of Fixation Device used *** not *** not
Device Type during in Patient Setup. supported supported
Required if Fixation Device *** ***
Sequence (300A,0190) is sent.
Defined Terms:
BITEBLOCK
HEADFRAME
MASK
MOLD
CAST
HEADREST
BREAST_BOARD
BODY_FRAME
VACUUM_MOLD
WHOLE_BODY_POD
RECTAL_BALLOON
>> Fixation (300A,0194) 2C User-defined label identifier for *** not *** not
Device Label Fixation Device. Required if supported supported
Fixation Device Sequence *** ***
(300A,0190) is sent.
>> Fixation (300A,0196) 3 User-defined description of *** not *** not
Device Fixation Device. supported supported
Description *** ***
>> Fixation (300A,0198) 3 Position/Notch number of *** not *** not
Device Position Fixation Device. supported supported
*** ***
>> Fixation (300A,0199) 3 The Fixation Device Pitch *** not *** not
Device Pitch Angle, i.e. orientation of supported supported
Angle PITCHED FIXATION DEVICE *** ***
coordinate system with respect
to IEC PATIENT SUPPORT
coordinate system (degrees).
Pitching is the rotation around
IEC PATIENT SUPPORT X-
axis.
>> Fixation (300A,019A) 3 The Fixation Device Roll Angle, *** not *** not
Device Roll i.e. orientation of ROLLED supported supported
Angle FIXATION DEVICE coordinate *** ***
system with respect to IEC
PITCHED FIXATION DEVICE
coordinate system (degrees).
Rolling is the rotation around
IEC PATIENT SUPPORT Y-
axis.
>> Accessory (300A,00F9) 3 An identifier for the accessory *** not *** not
Code intended to be read by a device supported supported
such as a bar-code reader. *** ***
78 of 151 Varian Treatment Delivery
Console
 IOD Details, RT Patient Setup – C.8.8.12
Attribute Name Tag Type Attribute Description TrueBeam 4DITC
4.0 v13.0

> Shielding (300A,01A0) 3 Introduces sequence of *** not *** not

Device Shielding Devices used in supported supported
Sequence Patient Setup. One or more *** ***
items may be included in this
sequence.
>> Shielding (300A,01A2) 1C Type of Shielding Device used *** not *** not
Device Type in Patient Setup. Required if supported supported
Shielding Device Sequence *** ***
(300A,01A0) is sent.
Defined Terms:
GUM
EYE
GONAD
>> Shielding (300A,01A4) 2C User-defined label for Shielding *** not *** not
Device Label Device. supported supported
Required if Shielding Device *** ***
Sequence (300A,01A0) is sent.
>> Shielding (300A,01A6) 3 User-defined description of *** not *** not
Device Shielding Device. supported supported
Description *** ***
>> Shielding (300A,01A8) 3 Position/Notch number of *** not *** not
Device Position Shielding Device. supported supported
*** ***
>> Accessory (300A,00F9) 3 An identifier for the accessory *** not *** not
Code intended to be read by a device supported supported
such as a bar-code reader. *** ***
> Setup (300A,01B0) 3 Setup Technique used in Roundtrip Roundtrip
Technique Patient Setup. supported supported
Defined Terms:
ISOCENTRIC
FIXED_SSD
TBI
BREAST_BRIDGE
SKIN_APPOSITION
VMS_CSC_1 Collision Safety
Checked ver 1.0
> Setup (300A,01B2) 3 User-defined description of Roundtrip Roundtrip
Technique Setup Technique. supported supported
Description
> Setup Device (300A,01B4) 3 Introduces sequence of devices *** not *** not
Sequence used for patient alignment in supported supported
Patient Setup. One or more *** ***
items may be included in this
sequence.

Treatment Delivery Console 79 of 151

 IOD Details, RT Patient Setup – C.8.8.12
Attribute Name Tag Type Attribute Description TrueBeam 4DITC
4.0 v13.0

>> Setup (300A,01B6) 1C Type of Setup Device used for *** not *** not
Device Type Patient alignment. Required if supported supported
Setup Device Sequence *** ***
(300A,01B4) is sent.
Defined Terms:
LASER_POINTER
DISTANCE_METER
TABLE_HEIGHT
MECHANICAL_PTR
ARC
>> Setup (300A,01B8) 2C User-defined label for Setup *** not *** not
Device Label Device used for patient supported supported
alignment. Required if Setup *** ***
Device Sequence (300A,01B4)
is sent.
>> Setup (300A,01BA) 3 User-defined description for *** not *** not
Device Setup Device used for patient supported supported
Description alignment. *** ***
>> Setup (300A,01BC) 2C Setup Parameter for Setup *** not *** not
Device Device in appropriate IEC supported supported
Parameter 61217 coordinate system. Units *** ***
shall be mm for distances and
degrees for angles. Required if
Setup Device Sequence
(300A,011B4) is sent.
>> Setup (300A,01D0) 3 User-defined description of *** not *** not
Reference Setup Reference used for supported supported
Description patient alignment. *** ***
> Table Top (300A,01D2) 3 Vertical Displacement in IEC Roundtrip Roundtrip
Vertical Setup TABLE TOP coordinate system supported supported
Displacement (in mm) relative to initial Setup
Position, i.e. vertical offset
between patient positioning
performed using setup and
treatment position.
> Table Top (300A,01D4) 3 Longitudinal Displacement in Roundtrip Roundtrip
Longitudinal IEC TABLE TOP coordinate supported supported
Setup system (in mm) relative to initial
Displacement Setup Position, i.e. longitudinal
offset between patient
positioning performed using
setup and treatment position.

80 of 151 Varian Treatment Delivery

Console
 IOD Details, RT Fraction Scheme – C.8.8.13
Attribute Name Tag Type Attribute Description TrueBeam 4DITC
4.0 v13.0

> Table Top (300A,01D6) 3 Lateral Displacement in IEC Roundtrip Roundtrip

Lateral Setup TABLE TOP coordinate system supported supported
Displacement (in mm) relative to initial Setup
Position, i.e. lateral offset
between patient positioning
performed using setup and
treatment position.

C.2.10 RT Fraction Scheme – C.8.8.13

Attribute Name Tag Type Attribute Description TrueBeam 4DITC

4.0 v13.0

Fraction Group (300A,0070) 1 Introduces sequence of Roundtrip Roundtrip

Sequence Fraction Groups in current supported supported
Fraction Scheme. One or more
items may be included in this
sequence.
> Fraction (300A,0071) 1 Identification number of the Roundtrip Roundtrip
Group Number Fraction Group. The value of supported supported
Fraction Group Number
(300A,0071) shall be unique
within the RT Plan in which it is
created.
> Fraction (300A,0072) 3 The user defined description for *** not *** not
Group the fraction group. supported supported
Description *** ***
> Referenced (300C,0080) 3 Introduces sequence of related *** not *** not
Dose Sequence SOP Class/Instance pairs supported supported
describing related instances of *** ***
RT Dose (for grids, isodose
curves and named/unnamed
point doses). One or more
items may be included in this
sequence. See Note 1.
>> Referenced (0008,1150) 1C Uniquely identifies the *** not *** not
SOP Class UID referenced SOP Class. supported supported
Required if Referenced Dose *** ***
Sequence (300C,0080) is sent.
>> Referenced (0008,1155) 1C Uniquely identifies the *** not *** not
SOP Instance referenced SOP Instance. supported supported
UID Required if Referenced Dose *** ***
Sequence (300C,0080) is sent.
> Referenced (300C,0050) 3 Introduces sequence of Dose *** not *** not
Dose Reference References for the current supported supported
Sequence Fraction Group. One or more *** ***
items may be included in this
sequence.

Treatment Delivery Console 81 of 151

 IOD Details, RT Fraction Scheme – C.8.8.13
Attribute Name Tag Type Attribute Description TrueBeam 4DITC
4.0 v13.0

>> Referenced (300C,0051) 1C Uniquely identifies Dose *** not *** not
Dose Reference Reference specified by Dose supported supported
Number Reference Number (300A,0012) *** ***
within Dose Reference
Sequence (300A,0010) in RT
Prescription Module. Required if
Referenced Dose Reference
Sequence (300C,0050) is sent.
>> Constraint (300A,0021) 3 Relative importance of *** not *** not
Weight satisfying constraint, where high supported supported
values represent more *** ***
important constraints.
>> Delivery (300A,0022) 3 The dose (in Gy) which when *** not *** not
Warning Dose reached or exceeded should supported supported
cause some action to be taken. *** ***
>> Delivery (300A,0023) 3 The maximum dose (in Gy) *** not *** not
Maximum Dose which can be delivered to the supported supported
dose reference. *** ***
>> Target (300A,0025) 3 Minimum permitted dose (in Gy) *** not *** not
Minimum Dose to Dose Reference if Dose supported supported
Reference Type (300A,0020) of *** ***
referenced Dose Reference is
TARGET.
>> Target (300A,0026) 3 Prescribed dose (in Gy) to Dose *** not *** not
Prescription Reference if Dose Reference supported supported
Dose Type (300A,0020) of referenced *** ***
Dose Reference is TARGET.
>> Target (300A,0027) 3 Maximum permitted dose (in *** not *** not
Maximum Dose Gy) to Dose Reference if Dose supported supported
Reference Type (300A,0020) of *** ***
referenced Dose Reference is
TARGET.
>> Target (300A,0028) 3 Maximum permitted fraction (in *** not *** not
Underdose percent) of Target to receive supported supported
Volume less than the Target *** ***
Fraction Prescription Dose (300A,0027)
if Dose Reference Type
(300A,0020) of referenced
Dose Reference is TARGET
and Dose Reference Structure
Type (300A,0014) of referenced
Dose Reference is VOLUME.

82 of 151 Varian Treatment Delivery

Console
 IOD Details, RT Fraction Scheme – C.8.8.13
Attribute Name Tag Type Attribute Description TrueBeam 4DITC
4.0 v13.0

>> Organ at (300A,002A) 3 Maximum dose (in Gy) to entire *** not *** not
Risk Full- Dose Reference if Dose supported supported
volume Dose Reference Type (300A,0020) of *** ***
referenced Dose Reference is
ORGAN_AT_RISK and Dose
Reference Structure Type
(300A,0014) of referenced
Dose Reference is VOLUME.
>> Organ at (300A,002B) 3 Maximum permitted dose (in *** not *** not
Risk Limit Dose Gy) to any part of Dose supported supported
Reference if Dose Reference *** ***
Type (300A,0020) of referenced
Dose Reference is
ORGAN_AT_RISK and Dose
Reference Structure Type
(300A,0014) of referenced
Dose Reference is VOLUME.
>> Organ at (300A,002C) 3 Maximum dose (in Gy) to non- *** not *** not
Risk Maximum overdosed part of Dose supported supported
Dose Reference if Dose Reference *** ***
Type (300A,0020) of referenced
Dose Reference is
ORGAN_AT_RISK and Dose
Reference Structure Type
(300A,0014) of referenced
Dose Reference is VOLUME.
>> Organ at (300A,002D) 3 Maximum permitted fraction (in *** not *** not
Risk Overdose percent) of Organ at Risk to supported supported
Volume receive more than the Organ at *** ***
Fraction Risk Maximum Dose if Dose
Reference Type (300A,0020) of
referenced Dose Reference is
ORGAN_AT_RISK and Dose
Reference Structure Type
(300A,0014) of referenced
Dose Reference is VOLUME.
> Number of (300A,0078) 2 Total number of treatments Roundtrip Roundtrip
Fractions (Fractions) prescribed for supported supported
Planned current Fraction Group.
> Number of (300A,0079) 3 Number of digits in Fraction *** not Roundtrip
Fraction Pattern Pattern (300A,007B) used to supported supported
Digits Per Day represent one day. See Note 2. ***
> Repeat (300A,007A) 3 Number of weeks needed to *** not Roundtrip
Fraction Cycle describe treatment pattern. See supported supported
Length Note 2. ***

Treatment Delivery Console 83 of 151

 IOD Details, RT Fraction Scheme – C.8.8.13
Attribute Name Tag Type Attribute Description TrueBeam 4DITC
4.0 v13.0

> Fraction (300A,007B) 3 String of 0's (no treatment) and Roundtrip Roundtrip
Pattern 1's (treatment) describing supported supported
treatment pattern. Length of
string is 7 x Number of Fraction
Pattern Digits Per Day x Repeat
Fraction Cycle Length. Pattern
shall start on a Monday. See
Note 2.
> Number of (300A,0080) 1 Number of Beams in current Import only Import only
Beams Fraction Group. If Number of
Beams is greater then zero,
Number of Brachy Application
Setups (300A,00A0) shall equal
zero.
> Referenced (300C,0004) 1C Introduces sequence of Roundtrip Roundtrip
Beam treatment beams in current supported supported
Sequence Fraction Group. Required if
Number of Beams (300A,0080)
is greater than zero. One or
more items may be included in
this sequence.
>> Referenced (300C,0006) 1C Uniquely identifies Beam Roundtrip Roundtrip
Beam Number specified by Beam Number supported supported
(300A,00C0) within Beam
Sequence (300A,00B0) in RT
Beams Module. Required if
Referenced Beam Sequence
(300C,0004) is sent.
>> Beam Dose (300A,0082) 3 Coordinates (x,y,z) of point at Roundtrip Roundtrip
Specification which Beam Dose is specified supported supported
Point in the patient based coordinate
system described in C.7.6.2.1.1
(mm). See Note 3.
>> Beam Dose (300A,0084) 3 Dose (in Gy) at Beam Dose Roundtrip Roundtrip
Specification Point (300A,0082) supported supported
due to current Beam.
>> Beam (300A,0086) 3 Machine setting to be delivered Roundtrip Roundtrip
Meterset for current Beam, specified in supported supported
Monitor Units (MU) or minutes
as defined by Primary
Dosimeter Unit (300A,00B3) (in
RT Beams Module) for
referenced Beam. See Note 4.

84 of 151 Varian Treatment Delivery

Console
 IOD Details, RT Fraction Scheme – C.8.8.13
Attribute Name Tag Type Attribute Description TrueBeam 4DITC
4.0 v13.0

>> Maximum (3249,XX00) 3 The maximum treatment time, *** not Roundtrip
Treatment Time which should not be supported supported
exceeeded. This items serves ***
as a secondary safety limit
besides the Beam Meterset
value (300A,0086) itself. Units
in [min].
> Number of (300A,00A0) 1 Number of Brachy Application *** not *** not
Brachy Setups in current Fraction supported supported
Application Group. If Number of Brachy *** ***
Setups Application Setups is greater
then zero, Number of Beams
(300A,0080) shall equal zero.
> Referenced (300C,000A) 1C Introduces sequence of *** not *** not
Brachy treatment Brachy Application supported supported
Application Setups in current Fraction *** ***
Setup Group. Required if Number of
Sequence Brachy Application Setups
(300A,00A0) is greater than
zero. One or more items may
be included in this sequence.
>> Referenced (300C,000C) 1C Uniquely identifies Brachy *** not *** not
Brachy Application Setup specified by supported supported
Application Brachy Application Setup *** ***
Setup Number Number (300A,0234) within
Brachy Application Setup
Sequence (300A,0230) in RT
Brachy Application Setups
Module.
Required if Referenced Brachy
Application Setup Sequence
(300C,000A) is sent.
>> Brachy (300A,00A2) 3 Coordinates (x,y,z) of point in *** not *** not
Application the patient based coordinate supported supported
Setup Dose system described in C.7.6.2.1.1 *** ***
Specification at which Brachy Application
Point Setup Dose (300A,00A4) is
specified (mm).
>> Brachy (300A,00A4) 3 Dose (in Gy) at Brachy *** not *** not
Application Application Setup Dose supported supported
Setup Dose Specification Point (300A,00A2) *** ***
due to current Brachy
Application Setup.
> Prescribed (3269,XX00) 3 *** not *** not
Dose per supported supported
Fraction *** ***
> Prescribed (3269,XX01) 3 *** not *** not
Percentage supported supported
*** ***

Treatment Delivery Console 85 of 151

 IOD Details, RT Beams – C.8.8.14
Attribute Name Tag Type Attribute Description TrueBeam 4DITC
4.0 v13.0

> Plan (3269,XX02) 3 *** not *** not

Normalization supported supported
Factor *** ***

C.2.11 RT Beams – C.8.8.14

TrueBeam 4DITC
Attribute Name Tag Type Attribute Description
4.0 v13.0
Beam Sequence (300A,00B0) 1 Introduces sequence of Roundtrip Roundtrip
treatment beams for current RT supported supported
Plan. One or more items may
be included in this sequence.
> Beam Number (300A,00C0) 1 Identification number of the Roundtrip Roundtrip
Beam. The value of Beam supported supported
Number (300A,00C0) shall be
unique within the RT Plan in
which it is created. See Note 1.
> Beam Name (300A,00C2) 3 User-defined name for Beam. Roundtrip Roundtrip
See Note 1. supported supported
> Beam (3243,XX09) 3 User-defined secondary name Roundtrip Roundtrip
Seconary Name for Beam. supported supported
> Beam (300A,00C3) 3 User-defined description for Roundtrip Roundtrip
Description Beam. See Note 1. supported supported
> Beam Type (300A,00C4) 1 Motion characteristic of Beam. Roundtrip Roundtrip
See Note 5. supported supported
Enumerated Values:
STATIC = All Control Point
Sequence (300A,0111)
attributes remain unchanged
between consecutive pairs of
control points with changing
Cumulative Meterset Weight
(300A,0134).
DYNAMIC = One or more
Control Point Sequence
(300A,0111) attributes change
between one or more
consecutive pairs of control
points with changing
Cumulative Meterset Weight
(300A,0134).

86 of 151 Varian Treatment Delivery

Console
 IOD Details, RT Beams – C.8.8.14
TrueBeam 4DITC
Attribute Name Tag Type Attribute Description
4.0 v13.0
> Radiation Type (300A,00C6) 2 Particle type of Beam. Roundtrip Roundtrip
Defined Terms: supported supported
PHOTON
ELECTRON
NEUTRON
PROTON
> Primary (3002,0050) 3 Sequence defining whether the Roundtrip Roundtrip
Fluence Mode primary fluence of the treatment supported supported
Sequence beam uses a non-standard
fluence-shaping. Only a single
Item shall be permitted in this
sequence.
>u> Fluence (3002,0051) 1 Describes whether the fluence Roundtrip Roundtrip
Mode shaping is the standard mode supported supported
for the beam or an alternate.
Enumerated Values:
STANDARD = Uses standard
fluence-shaping
NON_STANDARD = Uses a
non-standard fluence-shaping
mode
>> Fluence Mode (3002,0052) 1C Identifier for the specific Roundtrip Roundtrip
ID fluence-shaping mode. supported supported
Required if Fluence Mode
(3002,0051) has value
NON_STANDARD.
> Primary (3285,XX00) 3 See Primary Fluence Mode Roundtrip Roundtrip
Fluence Mode Sequence (3002,0050). supported supported
Sequence
(PRIVATE)
>> Fluence Mode (3285,XX01) 1 See Fluence Mode Roundtrip Roundtrip
(PRIVATE) (3002,0051). supported supported
>> Fluence Mode (3285,XX02) 1C See Fluence Mode ID Roundtrip Roundtrip
ID (PRIVATE) (3002,0052). supported supported

Treatment Delivery Console 87 of 151

 IOD Details, RT Beams – C.8.8.14
TrueBeam 4DITC
Attribute Name Tag Type Attribute Description
4.0 v13.0
> High-Dose (300A,00C7) 1C Type of high-dose treatment Roundtrip Roundtrip
Technique Type technique. supported supported
Defined Terms:
NORMAL = Standard treatment
TBI = Total Body Irradiation
HDR = High Dose Rate

Following defined term is

supported additionally:
SRS = Stereotactic
Radiosurgery

Required if treatment technique

requires a dose that would
normally require overriding of
treatment machine safety
controls.
> Treatment (300A,00B2) 2 User-defined name identifying Roundtrip Roundtrip
Machine Name treatment machine to be used supported supported
for beam delivery. See Note 2.
> Manufacturer (0008,0070) 3 Manufacturer of the equipment Roundtrip Roundtrip
to be used for beam delivery. supported supported
> Institution (0008,0080) 3 Institution where the equipment Roundtrip Roundtrip
Name is located that is to be used for supported supported
beam delivery.
> Institution (0008,0081) 3 Mailing address of the *** not *** not
Address institution where the equipment supported supported
is located that is to be used for *** ***
beam delivery.
> Institutional (0008,1040) 3 Department in the institution Roundtrip Roundtrip
Department where the equipment is located supported supported
Name that is to be used for beam
delivery.
> Manufacturer’s (0008,1090) 3 Manufacturer's model name of Roundtrip Roundtrip
Model Name the equipment that is to be used supported supported
for beam delivery.
> Device Serial (0018,1000) 3 Manufacturer's serial number of Roundtrip Roundtrip
Number the equipment that is to be used supported supported
for beam delivery.
> Primary (300A,00B3) 3 Measurement unit of machine Roundtrip Roundtrip
Dosimeter Unit dosimeter. See C.8.8.14.1. supported supported
Enumerated Values:
MU = Monitor Unit
MINUTE = minute

88 of 151 Varian Treatment Delivery

Console
 IOD Details, RT Beams – C.8.8.14
TrueBeam 4DITC
Attribute Name Tag Type Attribute Description
4.0 v13.0
> Referenced (300C,00A0) 3 Uniquely identifies Tolerance Roundtrip Roundtrip
Tolerance Table Table specified by Tolerance supported supported
Number Table Number (300A,0042)
within Tolerance Table
Sequence in RT Tolerance
Tables Module. These
tolerances are to be used for
verification of treatment
machine settings.
> Source-Axis (300A,00B4) 3 Radiation source to Gantry Roundtrip Roundtrip
Distance rotation axis distance of the supported supported
equipment that is to be used for
beam delivery (mm).
> Beam Limiting (300A,00B6) 1 Introduces sequence of beam Roundtrip Roundtrip
Device Sequence limiting device (collimator) jaw supported supported
or leaf (element) sets. One or
more items may be included in
this sequence.
>> RT Beam (300A,00B8) 1 Type of beam limiting device Roundtrip Roundtrip
Limiting Device (collimator). supported supported
Type Enumerated Values:
X = symmetric jaw pair in IEC X
direction
Y = symmetric jaw pair in IEC Y
direction
ASYMX = asymmetric jaw pair
in IEC X direction
ASYMY = asymmetric pair in
IEC Y direction
MLCX = multileaf (multi-
element) jaw pair in IEC X
direction
MLCY = multileaf (multi-
element) jaw pair in IEC Y
direction
>> Source to (300A,00BA) 3 Radiation source to beam Roundtrip Roundtrip
Beam Limiting limiting device (collimator) supported supported
Device Distance distance of the equipment that
is to be used for beam delivery
(mm).
>> Number of (300A,00BC) 1 Number of leaf (element) or jaw Roundtrip Roundtrip
Leaf/Jaw Pairs pairs (equal to 1 for standard supported supported
beam limiting device jaws).

Treatment Delivery Console 89 of 151

 IOD Details, RT Beams – C.8.8.14
TrueBeam 4DITC
Attribute Name Tag Type Attribute Description
4.0 v13.0
>> Leaf Position (300A,00BE) 2C Boundaries of beam limiting Roundtrip Roundtrip
Boundaries device (collimator) leaves (in supported supported
mm) in IEC BEAM LIMITING
DEVICE coordinate axis
appropriate to RT Beam
Limiting Device Type
(300A,00B8), i.e. X-axis for
MLCY, Y- axis for MLCX.
Contains N+1 values, where N
is the Number of Leaf/Jaw Pairs
(300A,00BC), starting from Leaf
(Element) Pair 1. Required if
Beam Limiting Device
Sequence (300A,00B6) is sent
and RT Beam Limiting Device
Type (300A,00B8) is MLCX or
MLCY. See Note 3.
> Referenced (300C,006A) 3 Uniquely identifies Patient Roundtrip Roundtrip
Patient Setup Setup to be used for current supported supported
Number beam, specified by Patient
Setup Number (300A,0182)
within Patient Setup Sequence
of RT Patient Setup Module.
> Referenced (300C,0042) 3 Introduces sequence of Roundtrip Roundtrip
Reference Image reference images used for supported supported
Sequence validation of current beam. One
or more items may be included
in this sequence.
>> Referenced (0008,1150) 1C Uniquely identifies the Roundtrip Roundtrip
SOP Class UID referenced SOP Class. supported supported
Required if Referenced
Reference Image Sequence
(300C,0042) is sent.
>> Referenced (0008,1155) 1C Uniquely identifies the Roundtrip Roundtrip
SOP Instance referenced SOP Instance. supported supported
UID Required if Referenced
Reference Image Sequence
(300C,0042) is sent.
>> Reference (300A,00C8) 1C Uniquely identifies Reference Roundtrip Roundtrip
Image Number Image within Referenced supported supported
Reference Image Sequence
(300A,0042). Required if
Referenced Reference Image
Sequence (300A,0042) is sent.
>> Start (300C,0008) 3 Cumulative Meterset Weight *** not *** not
Cumulative within current Beam at which supported supported
Meterset Weight image acquisition starts. *** ***

90 of 151 Varian Treatment Delivery

Console
 IOD Details, RT Beams – C.8.8.14
TrueBeam 4DITC
Attribute Name Tag Type Attribute Description
4.0 v13.0
>> End (300C,0009) 3 Cumulative Meterset Weight *** not *** not
Cumulative within current Beam at which supported supported
Meterset Weight image acquisition ends. *** ***

> Planned (300A,00CA) 3 Introduces sequence of planned Roundtrip Roundtrip

Verification verification images to be supported supported
Image Sequence acquired during current beam.
One or more items may be
included in this sequence. See
C.8.8.14.2.
>> Start (300C,0008) 3 Cumulative Meterset Weight Roundtrip Roundtrip
Cumulative within current Beam at which supported supported
Meterset Weight image acquisition will start.
>> Meterset (3002,0032) 3 Meterset duration over which Roundtrip *** not
Exposure image is to be acquired, supported supported
specified in Monitor units (MU) ***
or minutes as defined by
Primary Dosimeter Unit
(300A,00B3).
>> End (300C,0009) 3 Cumulative Meterset Weight *** not *** not
Cumulative within current Beam at which supported supported
Meterset Weight image acquisition will end. *** ***
>> RT Image (3002,000C) 3 Describes whether or not image Roundtrip Roundtrip
Plane plane is normal to beam axis. supported supported
Enumerated Values:
NORMAL = image plane normal
to beam axis
NON_NORMAL = image plane
non-normal to beam axis
>> X-Ray Image (3002,000E) 3 X-Ray Image Receptor Angle Roundtrip Roundtrip
Receptor Angle i.e. orientation of IEC X-RAY supported supported
IMAGE RECEPTOR coordinate
system with respect to IEC
GANTRY coordinate system
(degrees). See C.8.8.14.3.
>> RT Image (3002,0010) 3 The direction cosines of the first *** not *** not
Orientation row and the first column with supported supported
respect to the IEC XRAY *** ***
IMAGE RECEPTOR coordinate
system.
>> RT Image (3002,0012) 3 The x and y coordinates (in Roundtrip Roundtrip
Position mm) of the upper left hand supported supported
corner of the image, in the IEC
X-RAY IMAGE RECEPTOR
coordinate system. This is the
center of the first pixel
transmitted.
>> RT Image SID (3002,0026) 3 Radiation machine source to Roundtrip Roundtrip
image plane distance (mm). supported supported

Treatment Delivery Console 91 of 151

 IOD Details, RT Beams – C.8.8.14
TrueBeam 4DITC
Attribute Name Tag Type Attribute Description
4.0 v13.0
>> Imaging (300A,00CC) 3 User-specified device-specific Roundtrip Roundtrip
Device-Specific parameters that describe how supported supported
Acquisition the imager will acquire the Type/quality
Parameters image. used to
acquire
verification
image.
This field
can have
one of the
following
values:
PortImageH
ighQuality
Single port
image
optimized
for image
quality.
PortImageL
owDose
Single port
image
optimized
for low
dose.
PortImageC
ontinuous
Multiple port
images
acquired at
highest
possible
rate. Start
Cumulative
Meterset
Weight
(300C,0008
) must be 0.
PortImageIn
tegrated
Integrated
port image
with frames
averaged
during the
entire beam
on time.

92 of 151 Varian Treatment Delivery

Console
 IOD Details, RT Beams – C.8.8.14
TrueBeam 4DITC
Attribute Name Tag Type Attribute Description
4.0 v13.0
>> Referenced (300C,0007) 3 Uniquely identifies Reference *** not *** not
Reference Image Image to which planned supported supported
Number verification image is related, *** ***
specified by Reference Image
Number (300A,00C8) within
Referenced Reference Image
Sequence (300A,0042).
> Treatment (300A,00CE) 3 Delivery Type of treatment. Roundtrip Roundtrip
Delivery Type Defined Terms: supported supported
TREATMENT = normal patient
treatment
SETUP = setup verification
OPEN_PORTFILM = portal
image acquisition with open
field
TRMT_PORTFILM = portal
image acquisition with
treatment port
CONTINUATION = continuation
of interrupted treatment
> Referenced (300C,0080) 3 Introduces sequence of related Roundtrip Roundtrip
Dose Sequence SOP Class/Instance pairs supported supported
describing related instances of
RT Dose (for grids, isodose
curves, and named/unnamed
point doses). One or more
items may be included in this
sequence.
>> Referenced (0008,1150) 1C Uniquely identifies the Roundtrip Roundtrip
SOP Class UID referenced SOP Class. supported supported
Required if Referenced Dose
Sequence (300C,0080) is sent.
>> Referenced (0008,1155) 1C Uniquely identifies the Roundtrip Roundtrip
SOP Instance referenced SOP Instance. supported supported
UID Required if Referenced Dose
Sequence (300C,0080) is sent.
> Number of (300A,00D0) 1 Number of wedges associated Roundtrip Roundtrip
Wedges with current Beam. supported supported
> Wedge (300A,00D1) 1C Introduces sequence of Roundtrip Roundtrip
Sequence treatment wedges. supported supported
Required if Number of Wedges
(300A,00D0) is non-zero. One
or more items may be included
in this sequence.

Treatment Delivery Console 93 of 151

 IOD Details, RT Beams – C.8.8.14
TrueBeam 4DITC
Attribute Name Tag Type Attribute Description
4.0 v13.0
>> Wedge (300A,00D2) 1C Identification number of the Roundtrip Roundtrip
Number Wedge. The value of Wedge supported supported
Number (300A,00D2) shall be
unique within the Beam in
which it is created. Required if
Wedge Sequence (300A,00D1)
is sent.
>> Wedge Type (300A,00D3) 2C Type of wedge (if any) defined Roundtrip Roundtrip
for Beam. supported supported
Required if Wedge Sequence
(300A,00D1) is sent.
Defined Terms:
STANDARD = standard (static)
wedge
DYNAMIC = moving beam
limiting device (collimator) jaw
simulating wedge
MOTORIZED = single wedge
which can be removed from
beam remotely
>> Wedge ID (300A,00D4) 3 User-supplied identifier for Roundtrip Roundtrip
Wedge. supported supported
>> Accessory (300A,00F9) 3 An identifier for the accessory Roundtrip *** not
Code intended to be read by a device supported supported
such as a bar-code reader. ***
>> Wedge Angle (300A,00D5) 2C Nominal wedge angle Roundtrip Roundtrip
(degrees). Required if Wedge supported supported
Sequence (300A,00D1) is sent.
>> Wedge Factor (300A,00D6) 2C Nominal wedge factor under Roundtrip Roundtrip
machine calibration conditions supported supported
at the beam energy specified by
the Nominal Beam Energy
(300A,0114) of the first Control
Point of the Control Point
Sequence (300A,0111).
Required if Wedge Sequence
(300A,00D1) is sent.
>> Wedge (300A,00D8) 2C Orientation of wedge, i.e. Roundtrip Roundtrip
Orientation orientation of IEC WEDGE supported supported
FILTER coordinate system with
respect to IEC BEAM LIMITING
DEVICE coordinate system
(degrees). Required if Wedge
Sequence (300A,00D1) is sent.
>> Source to (300A,00DA) 3 Radiation source to wedge tray Roundtrip Roundtrip
Wedge Tray attachment edge distance (in supported supported
Distance mm) for current wedge.

94 of 151 Varian Treatment Delivery

Console
 IOD Details, RT Beams – C.8.8.14
TrueBeam 4DITC
Attribute Name Tag Type Attribute Description
4.0 v13.0
> Number of (300A,00E0) 1 Number of compensators Roundtrip Import only.
Compensators associated with current Beam. supported

> Total (300A,00E2) 3 Compensator Tray transmission *** not Roundtrip

Compensator factor (between 0 and 1), at the supported supported
Tray Factor beam energy specified by the ***
Nominal Beam Energy
(300A,0114) of the first Control
Point of the Control Point
Sequence (300A,0111).
> Compensator (300A,00E3) 1C Introduces sequence of Roundtrip Roundtrip
Sequence treatment compensators. supported supported
Required if Number of
Compensators (300A,00E0) is
non-zero. One or more items
may be included in this
sequence.
>> Compensator (300A,02EB) 3 User defined description for the *** not *** not
Description compensator supported supported
*** ***
>> Compensator (300A,00EE) 3 Type of compensator (if any). Roundtrip Roundtrip
Type Defined Terms: supported supported
STANDARD = physical (static)
compensator
DYNAMIC = moving Beam
Limiting Device (collimator)
simulating physical
compensator
>> Material ID (300A,00E1) 2C User-supplied identifier for Roundtrip Roundtrip
material used to manufacture supported supported
Compensator. Required if
Number of Compensators
(300A,00E0) is non-zero.
>> Compensator (300A,00E5) 3 User-supplied identifier for Roundtrip Roundtrip
ID compensator. supported supported
>> Accessory (300A,00F9) 3 An identifier for the accessory Roundtrip Roundtrip
Code intended to be read by a device supported supported
such as a bar-code reader.
>> Source to (300A,00E6) 2C Radiation source to Roundtrip Roundtrip
Compensator compensator tray attachment supported supported
Tray Distance edge distance (in mm) for
current compensator. Required
if Compensator Sequence
(300A,00E3) is sent.

Treatment Delivery Console 95 of 151

 IOD Details, RT Beams – C.8.8.14
TrueBeam 4DITC
Attribute Name Tag Type Attribute Description
4.0 v13.0
>> Compensator (300A,02E0) 3 Indicates presence or absence *** not Roundtrip
Divergence of geometrical divergence of the supported supported
compensator. ***
Enumerated Values:
PRESENT = the compensator
is shaped according to the
beam geometrical divergence.
ABSENT = the compensator is
not shaped according to the
beam geometrical divergence.
>> Compensator (300A,02E1) 3 Indicates on which side of the *** not Roundtrip
Mounting Position Compensator Tray the supported supported
compensator is mounted. ***
Enumerated Values:
PATIENT_SIDE = the
compensator is mounted on the
side of the Compensator Tray
which is towards the patient.
SOURCE_SIDE = the
compensator is mounted on the
side of the Compensator Tray
which is towards the radiation
source.
DOUBLE_SIDED = the
compensator has a shaped (i.e.
non-flat) surface on both sides
of the Compensator Tray.
>> Compensator (300A,00E7) 1C Number of rows in the Roundtrip Roundtrip
Rows compensator. supported supported
Required if Compensator
Sequence (300A,00E3) is sent.
>> Compensator (300A,00E8) 1C Number of columns in the Roundtrip Roundtrip
Columns compensator. supported supported
Required if Compensator
Sequence (300A,00E3) is sent.
>> Compensator (300A,00E9) 1C Physical distance (in mm) Roundtrip Roundtrip
Pixel Spacing between the center of each supported supported
pixel projected onto machine
isocentric plane. Specified by a
numeric pair - adjacent row
spacing (delimiter) adjacent
column spacing.
Required if Compensator
Sequence (300A,00E3) is sent.

96 of 151 Varian Treatment Delivery

Console
 IOD Details, RT Beams – C.8.8.14
TrueBeam 4DITC
Attribute Name Tag Type Attribute Description
4.0 v13.0
>> Compensator (300A,00EA) 1C The x and y coordinates of the Roundtrip Roundtrip
Position upper left hand corner (first supported supported
pixel transmitted) of the
compensator, projected onto
the machine isocentric plane in
the IEC BEAM LIMITING
DEVICE coordinate system
(mm). Required if Compensator
Sequence (300A,00E3) is sent.
>> Compensator (300A,00EB) 1C A data stream of the pixel Roundtrip Roundtrip
Transmission samples which comprise the supported supported
Data compensator, expressed as
broad-beam transmission
values (between 0 and 1) along
a ray line passing through the
pixel, at the beam energy
specified by the Nominal Beam
Energy (300A,0114) of the first
Control Point of the Control
Point Sequence (300A,0111).
The order of pixels sent is left to
right, top to bottom, i.e., the
upper left pixel is sent first
followed by the remainder of the
first row , followed by the first
pixel of the 2nd row, then the
remainder of the 2nd row and
so on) when viewed from the
radiation source. Required if
Compensator Sequence
(300A,00E3) is sent and
Material ID (300A,00E1) is
zero- length. See C.8.8.14.10.
Note:
Compensator Transmission
Data may not be properly
encoded if Explicit-VR transfer
syntax is used and the VL of
this attribute exceeds 65534
bytes.

Treatment Delivery Console 97 of 151

 IOD Details, RT Beams – C.8.8.14
TrueBeam 4DITC
Attribute Name Tag Type Attribute Description
4.0 v13.0
>> Compensator (300A,00EC) 1C A data stream of the pixel Roundtrip Roundtrip
Thickness Data samples which comprise the supported supported
compensator, expressed as
thicknesses (in mm). The order
of pixels sent is left to right, top
to bottom, i.e., the upper left
pixel is sent first followed by the
remainder of the first row ,
followed by the first pixel of the
2nd row, then the remainder of
the 2nd row and so on) when
viewed from the radiation
source. Required if
Compensator Sequence
(300A,00E3) is sent and
Material ID (300A,00E1) is
nonzero length. See C.8.8.14.9
and C.8.8.14.10.
Note:
Compensator Thickness Data
may not be properly encoded if
Explicit- VR transfer syntax is
used and the VL of this attribute
exceeds 65534 bytes.
>> Source to (300A,02E2) 1C A data stream of the pixel Roundtrip Roundtrip
Compensator samples which comprise the supported supported
Distance distance from the radiation
source to the compensator
surface closest to the radiation
source (in mm). The order of
pixels sent is left to right, top to
bottom (upper left pixel,
followed by the remainder of
row 1, followed by the
remainder of the columns).
Required if Compensator
Sequence (300A,00E3) is sent,
Material ID (300A,00E1) is non-
zero length, and Compensator
Mounting Position (300A,02E1)
is DOUBLE_SIDED. See
C.8.8.14.9.
> Number of Boli (300A,00ED) 1 Number of boli associated with Roundtrip Roundtrip
current Beam. supported supported
> Referenced (300C,00B0) 1C Introduces sequence of boli Roundtrip Roundtrip
Bolus Sequence associated with Beam. supported supported
Required if Number of Boli
(300A,00ED) is non-zero. One
or more items may be included
in this sequence.

98 of 151 Varian Treatment Delivery

Console
 IOD Details, RT Beams – C.8.8.14
TrueBeam 4DITC
Attribute Name Tag Type Attribute Description
4.0 v13.0
>> Referenced (3006,0084) 1C Uniquely identifies ROI Roundtrip Roundtrip
ROI Number representing the Bolus specified supported supported
by ROI Number (3006,0022) in
Structure Set ROI Sequence
(3006,0020) in Structure Set
Module within RT Structure Set
in Referenced Structure Set
Sequence (300C,0060) in RT
General Plan Module.
Required if Referenced Bolus
Sequence (300C,00B0) is sent.
>> Bolus ID (300A,00DC) 3 User-supplied identifier for the *** not *** not
Bolus. supported supported
*** ***
>> Bolus (300A,00DD) 3 User-defined description for the *** not *** not
Description Bolus. supported supported
*** ***
>> Accessory (300A,00F9) 3 An identifier for the accessory Roundtrip Roundtrip
Code intended to be read by a device supported supported
such as a bar-code reader.
> Number of (300A,00F0) 1 Number of shielding blocks Roundtrip Roundtrip
Blocks associated with Beam. supported supported
> Total Block (300A,00F2) 3 Total block tray transmission for Roundtrip Roundtrip
Tray Factor all block trays (between 0 and supported supported
1) at the beam energy specified
by the Nominal Beam Energy
(300A,0114) of the first Control
Point of the Control Point
Sequence (300A,0111).
> Block (300A,00F4) 1C Introduces sequence of blocks Roundtrip Roundtrip
Sequence associated with Beam. supported supported
Required if Number of Blocks
(300A,00F0) is non-zero. One
or more items may be included
in this sequence.
>> Block Tray ID (300A,00F5) 3 User-supplied identifier for Roundtrip Roundtrip
block tray. supported supported
>> Accessory (300A,00F9) 3 An identifier for the accessory Roundtrip Roundtrip
Code intended to be read by a device supported supported
such as a bar-code reader.
>> Source to (300A,00F6) 2C Radiation Source to attachment Roundtrip Roundtrip
Block Tray edge of block tray assembly supported supported
Distance (mm). Required if Block
Sequence (300A,00F4) is sent.

Treatment Delivery Console 99 of 151

 IOD Details, RT Beams – C.8.8.14
TrueBeam 4DITC
Attribute Name Tag Type Attribute Description
4.0 v13.0
>> Block Type (300A,00F8) 1C Type of block. Required if Block Roundtrip Roundtrip
Sequence (300A,00F4) is sent. supported supported
See C.8.8.14.4.
Enumerated Values:
SHIELDING = blocking material
is inside contour
APERTURE = blocking material
is outside contour
>> Block (300A,00FA) 2C Indicates presence or otherwise Roundtrip Roundtrip
Divergence of geometrical divergence. supported supported
Required if Block Sequence
(300A,00F4) is sent.
Enumerated Values:
PRESENT = block edges are
shaped for beam divergence
ABSENT = block edges are not
shaped for beam divergence
>> Block (300A,00FB) 3 Indicates on which side of the *** not *** not
Mounting Position Block Tray the block is supported supported
mounted. *** ***
Enumerated Values:
PATIENT_SIDE = the block is
mounted on the side of the
Block Tray which is towards the
patient.
SOURCE_SIDE = the block is
mounted on the side of the
Block Tray which is towards the
radiation source.
>> Block Number (300A,00FC) 1C Identification number of the Roundtrip Roundtrip
Block. The value of Block supported supported
Number (300A,00FC) shall be
unique within the Beam in
which it is created. Required if
Block Sequence (300A,00F4) is
sent.
>> Block Name (300A,00FE) 3 User-defined name for block. Roundtrip Roundtrip
supported supported
>> Material ID (300A,00E1) 2C User-supplied identifier for Roundtrip Roundtrip
material used to manufacture supported supported
Block. Required if Block
Sequence (300A,00F4) is sent.

100 of 151 Varian Treatment Delivery

Console
 IOD Details, RT Beams – C.8.8.14
TrueBeam 4DITC
Attribute Name Tag Type Attribute Description
4.0 v13.0
>> Block (300A,0100) 2C Physical thickness of block (in Roundtrip Roundtrip
Thickness mm) parallel to radiation beam supported supported
axis. Required if Block
Sequence (300A,00F4) is sent
and Material ID (300A,00E1) is
non-zero length. See
C.8.8.14.4.
>> Block (300A,0102) 2C Transmission through the block Roundtrip Roundtrip
Transmission (between 0 and 1) at the beam supported supported
energy specified by the Nominal
Beam Energy (300A,0114) of
the first Control Point of the
Control Point Sequence
(300A,0111). Required if Block
Sequence (300A,00F4) is sent
and Material ID (300A,00E1) is
zero length. See C.8.8.14.4.
>> Block Number (300A,0104) 2C Number of (x,y) pairs defining Roundtrip Roundtrip
of Points the block edge. Required if supported supported
Block Sequence (300A,00F4) is
sent.
>> Block Data (300A,0106) 2C A data stream of (x,y) pairs Roundtrip Roundtrip
which comprise the block edge. supported supported
The number of pairs shall be
equal to Block Number of
Points (300A,0104), and the
vertices shall be interpreted as
a closed polygon. Coordinates
are projected onto the machine
isocentric plane in the IEC
BEAM LIMITING DEVICE
coordinate system (mm).
Required if Block Sequence
(300A,00F4) is sent. See Note
4.
> Applicator (300A,0107) 3 Introduces sequence of Roundtrip Roundtrip
Sequence Applicators associated with supported supported
Beam. Only a single item shall
be permitted in this sequence.
>> Applicator ID (300A,0108) 1C User or machine supplied Roundtrip Roundtrip
identifier for Applicator. supported supported
Required if Applicator
Sequence (300A,0107) is sent.
>> Accessory (300A,00F9) 3 An identifier for the accessory Roundtrip Roundtrip
Code intended to be read by a device supported supported
such as a bar-code reader.

Treatment Delivery Console 101 of 151

 IOD Details, RT Beams – C.8.8.14
TrueBeam 4DITC
Attribute Name Tag Type Attribute Description
4.0 v13.0
>> Applicator (300A,0109) 1C Type of Applicator. Required if Roundtrip Roundtrip
Type Applicator Sequence supported supported
(300A,0107) is sent.
Defined Terms:
ELECTRON_SQUARE =
square electron applicator
ELECTRON_RECT =
rectangular electron applicator
ELECTRON_CIRC = circular
electron applicator
ELECTRON_SHORT = short
electron applicator
ELECTRON_OPEN = open
(dummy) electron applicator
INTRAOPERATIVE =
intraoperative (custom)
applicator
STEREOTACTIC = stereotactic
applicator
>> Applicator (300A,010A) 3 User-defined description for Roundtrip Roundtrip
Description Applicator. supported supported
> General (300A,0420) 3 Introduces a Sequence of Roundtrip Roundtrip
Accessory General Accessories supported supported
Sequence associated with this Beam. One
or more items may be included
in this sequence.
>> General (300A,0424) 1 Identification Number of the Roundtrip Roundtrip
Accessory General Accessory. The value supported supported
Number shall be unique within the
sequence.
>> General (300A,0421) 1 User or machine supplied Roundtrip Roundtrip
Accessory ID identifier for General Accessory. supported supported
>> General (300A,0422) 3 User supplied description of Roundtrip Roundtrip
Accessory General Accessory. supported supported
Description
>> General (300A,0423) 3 Specifies the type of accessory. Roundtrip Roundtrip
Accessory Type Defined Terms: supported supported
GRATICULE = Accessory tray
with a radio-opaque grid
IMAGE_DETECTOR = Image
acquisition device positioned in
the beam line
RETICLE = Accessory tray with
radio-transparent markers or
grid

102 of 151 Varian Treatment Delivery

Console
 IOD Details, RT Beams – C.8.8.14
TrueBeam 4DITC
Attribute Name Tag Type Attribute Description
4.0 v13.0
>> Accessory (300A,00F9) 3 Machine-readable identifier for Roundtrip Roundtrip
Code this accessory supported supported
>> Source to (3291,XX00) 3 Radiation source to accessory Roundtrip Roundtrip
General distance of the equipment that supported supported
Accessory is to be used for beam delivery
Distance (mm).
> Final (300A,010E) 1C Value of Cumulative Meterset Roundtrip Roundtrip
Cumulative Weight (300A,0134) for final supported supported
Meterset Weight Control Point in Control Point
Sequence (300A,0111).
Required if Cumulative
Meterset Weight is non-null in
Control Points specified within
Control Point Sequence
(300A,0111). See C.8.8.14.1.
> Number of (300A,0110) 1 Number of control points in Roundtrip Roundtrip
Control Points Beam. supported supported
> Control Point (300A,0111) 1 Introduces sequence of Roundtrip Roundtrip
Sequence machine configurations supported supported
describing treatment beam.
Two or more items may be
included in this sequence. See
C.8.8.14.5 and C.8.8.14.6.
>> Control Point (300A,0112) 1C Index of current Control Point, Roundtrip Roundtrip
Index starting at 0 for first Control supported supported
Point. Required if Control Point
Sequence (300A,0111) is sent.
>> Cumulative (300A,0134) 2C Cumulative weight to current Roundtrip Roundtrip
Meterset Weight control point. Cumulative supported supported
Meterset Weight for the first
item in Control Point Sequence
shall always be zero.
Cumulative Meterset Weight for
the final item in Control Point
Sequence shall always be
equal to Final Cumulative
Meterset Weight. Required if
Control Point Sequence
(300A,0111) is sent. See
C.8.8.14.1.
>> Referenced (300C,0050) 3 Introduces a sequence of Dose Roundtrip Roundtrip
Dose Reference References for current Beam. supported supported
Sequence One or more items may be
included in this sequence.

Treatment Delivery Console 103 of 151

 IOD Details, RT Beams – C.8.8.14
TrueBeam 4DITC
Attribute Name Tag Type Attribute Description
4.0 v13.0
>>> Referenced (300C,0051) 1C Uniquely identifies Dose Roundtrip Roundtrip
Dose Reference Reference specified by Dose supported supported
Number Reference Number (300A,0012)
in Dose Reference Sequence
(300A,0010) in RT Prescription
Module.
Required if Referenced Dose
Reference Sequence
(300C,0050) is sent.
>>> Cumulative (300A,010C) 2C Coefficient used to calculate Roundtrip Roundtrip
Dose Reference cumulative dose contribution supported supported
Coefficient from this Beam to the
referenced Dose Reference at
the current Control Point.
Required if Referenced Dose
Reference Sequence
(300C,0050) is sent. See
C.8.8.14.7.
>> Referenced (300C,0080) 1C Sequence describing related *** not *** not
Dose Sequence instances of RT Dose (for grids, supported supported
isodose curves, and *** ***
named/unnamed point doses).
One or more items may be
included in this sequence.
Required if RT Dose is being
sent, and Dose Summation
Type (3004,000A) equals
CONTROL_POINT.
>>> Referenced (0008,1150) 1 Uniquely identifies the *** not *** not
SOP Class UID referenced SOP Class. supported supported
*** ***
>>> Referenced (0008,1155) 1 Uniquely identifies the *** not *** not
SOP Instance referenced SOP Instance. supported supported
UID *** ***
>> Nominal (300A,0114) 3 Nominal Beam Energy at Roundtrip Roundtrip
Beam Energy control point (MV/MeV). supported supported

>> Dose Rate Set (300A,0115) 3 Dose Rate to be set on Roundtrip Roundtrip
treatment machine for segment supported supported
beginning at current control
point (e.g. MU/min).

104 of 151 Varian Treatment Delivery

Console
 IOD Details, RT Beams – C.8.8.14
TrueBeam 4DITC
Attribute Name Tag Type Attribute Description
4.0 v13.0
>> Wedge (300A,0116) 3 A Sequence of Items describing Roundtrip Roundtrip
Position Wedge Positions for the current supported supported
Sequence control point. Required for first
item of Control Point Sequence
if Number of Wedges
(300A,00D0) is non-zero, and in
subsequent control points if
Wedge Position (300A,0118)
changes during Beam. See
C.8.8.14.5. The number of
items in this sequence shall
equal the value of Number of
Wedges (300A,00D0).
>>> Referenced (300C,00C0) 1C Uniquely references Wedge Roundtrip Roundtrip
Wedge Number described by Wedge Number supported supported
(300A,00D2) in Wedge
Sequence (300A,00D1).
Required if Wedge Position
Sequence (300A,0116) is sent.
>>> Wedge (300A,0118) 1C Position of Wedge at current Roundtrip Roundtrip
Position Control Point. supported supported
Required if Wedge Position
Sequence (300A,0116) is sent.
Enumerated Values:
IN
OUT
>> Beam Limiting (300A,011A) 1C Introduces sequence of beam Roundtrip Roundtrip
Device Position limiting device (collimator) jaw supported supported
Sequence or leaf (element) positions.
Required for first item of Control
Point Sequence, or if Beam
Limiting Device changes during
Beam. One or more items may
be included in this sequence.

Treatment Delivery Console 105 of 151

 IOD Details, RT Beams – C.8.8.14
TrueBeam 4DITC
Attribute Name Tag Type Attribute Description
4.0 v13.0
>>> RT Beam (300A,00B8) 1C Type of beam limiting device Roundtrip Roundtrip
Limiting Device (collimator). The value of this supported supported
Type attribute shall correspond to RT
Beam Limiting Device Type
(300A,00B8) defined in an item
of Beam Limiting Device
Sequence (300A,00B6).
Required if Beam Limiting
Device Position Sequence
(300A,011A) is sent.
Enumerated Values:
X = symmetric jaw pair in IEC X
direction
Y = symmetric jaw pair in IEC Y
direction
ASYMX = asymmetric jaw pair
in IEC X direction
ASYMY = asymmetric pair in
IEC Y direction
MLCX = multileaf (multi-
element) jaw pair in IEC X
direction
MLCY = multileaf (multi-
element) jaw pair in IEC Y
direction
>>> Leaf/Jaw (300A,011C) 1C Positions of beam limiting Roundtrip Roundtrip
Positions device (collimator) leaf supported supported
(element) or jaw pairs (in mm) If values If values are
in IEC BEAM LIMITING are not not defined
DEVICE coordinate axis defined then
appropriate to RT Beam then 88888888
Limiting Device Type 88888888 will be sent.
(300A,00B8), e.g. X- axis for will be
MLCX, Y-axis for MLCY. sent.
Contains 2N values, where N is
the Number of Leaf/Jaw Pairs
(300A,00BC) in Beam Limiting
Device Sequence (300A,00B6).
Values shall be listed in IEC
leaf (element) subscript order
101, 102, ... 1N, 201, 202, ...
2N. Required if Beam Limiting
Device Position Sequence
(300A,011A) is sent. See Note
2.

106 of 151 Varian Treatment Delivery

Console
 IOD Details, RT Beams – C.8.8.14
TrueBeam 4DITC
Attribute Name Tag Type Attribute Description
4.0 v13.0
>> Gantry Angle (300A,011E) 1C Gantry angle of radiation Roundtrip Roundtrip
source, i.e. orientation of IEC supported supported
GANTRY coordinate system If values If values are
with respect to IEC FIXED are not not defined
REFERENCE coordinate defined then
system (degrees). Required for then 88888888
first item of Control Point 88888888 will be sent.
Sequence, or if Gantry Angle will be
changes during Beam. sent.
>> Gantry (300A,011F) 1C Direction of Gantry Rotation Roundtrip Roundtrip
Rotation Direction when viewing gantry from supported supported
isocenter, for segment following
Control Point. Required for first
item of Control Point Sequence,
or if Gantry Rotation Direction
changes during Beam. See
C.8.8.14.8.
Enumerated Values:
CW = clockwise
CC = counter-clockwise
NONE = no rotation
>> Gantry Pitch (300A,014A) 3 Gantry Pitch Angle. i.e. the *** not *** not
Angle rotation of the IEC GANTRY supported supported
coordinate system about the X- *** ***
axis of the IEC GANTRY
coordinate system (degrees). If
used, must be present for first
item of Control Point Sequence,
or if used and Gantry Pitch
Rotation Angle changes during
Beam, must be present.
>> Gantry Pitch (300A,014C) 3 Direction of Gantry Pitch Angle *** not *** not
Rotation Direction when viewing along the positive supported supported
X-axis of the IEC GANTRY *** ***
coordinate system, for segment
following Control Point. If used,
must be present for first item of
Control Point Sequence, or if
used and Gantry Pitch Rotation
Direction changes during Beam,
must be present. See
C.8.8.14.8 and C.8.8.25.6.5.
Enumerated Values: CW =
clockwise CC = counter-
clockwise NONE = no rotation

Treatment Delivery Console 107 of 151

 IOD Details, RT Beams – C.8.8.14
TrueBeam 4DITC
Attribute Name Tag Type Attribute Description
4.0 v13.0
>> Beam Limiting (300A,0120) 1C Beam Limiting Device angle, Roundtrip Roundtrip
Device Angle i.e. orientation of IEC BEAM supported supported
LIMITING DEVICE coordinate
system with respect to IEC
GANTRY coordinate system
(degrees). Required for first
item of Control Point Sequence,
or if Beam Limiting Device
Angle changes during Beam.
>> Beam Limiting (300A,0121) 1C Direction of Beam Limiting Roundtrip Roundtrip
Device Rotation Device Rotation when viewing supported supported
Direction beam limiting device
(collimator) from radiation
source, for segment following
Control Point. Required for first
item of Control Point Sequence,
or if Beam Limiting Device
Rotation Direction changes
during Beam. See C.8.8.14.8.
Enumerated Values:
CW = clockwise
CC = counter-clockwise
NONE = no rotation
>> Patient (300A,0122) 1C Patient Support angle, i.e. Roundtrip Roundtrip
Support Angle orientation of IEC PATIENT supported supported
SUPPORT (turntable)
coordinate system with respect
to IEC FIXED REFERENCE
coordinate system (degrees).
Required for first item of Control
Point Sequence, or if Patient
Support Angle changes during
Beam.
>> Patient (300A,0123) 1C Direction of Patient Support Roundtrip Roundtrip
Support Rotation Rotation when viewing table supported supported
Direction from above, for segment
following Control Point.
Required for first item of Control
Point Sequence, or if Patient
Support Rotation Direction
changes during Beam. See
C.8.8.14.8.
Enumerated Values:
CW = clockwise
CC = counter-clockwise
NONE = no rotation

108 of 151 Varian Treatment Delivery

Console
 IOD Details, RT Beams – C.8.8.14
TrueBeam 4DITC
Attribute Name Tag Type Attribute Description
4.0 v13.0
>> Table Top (300A,0124) 3 Distance (positive) from the IEC Roundtrip Roundtrip
Eccentric Axis PATIENT SUPPORT vertical supported supported
Distance axis to the IEC TABLE TOP
ECCENTRIC vertical axis (mm).
>> Table Top (300A,0125) 1C Table Top (non-isocentric) Roundtrip Roundtrip
Eccentric Angle angle, i.e. orientation of IEC supported supported
TABLE TOP ECCENTRIC
coordinate system with respect
to IEC PATIENT SUPPORT
coordinate system (degrees).
Required for first item of Control
Point Sequence, or if Table Top
Eccentric Angle changes during
Beam.
>> Table Top (300A,0126) 1C Direction of Table Top Eccentric Roundtrip Roundtrip
Eccentric Rotation when viewing table supported supported
Rotation Direction from above, for segment
following Control Point.
Required for first item of Control
Point Sequence, or if Table Top
Eccentric Rotation Direction
changes during Beam. See
C.8.8.14.8.
Enumerated Values:
CW = clockwise
CC = counter-clockwise
NONE = no rotation
>> Patient (300A,0140) 1C Table Top Pitch Angle, i.e. the *** not *** not
Support Pitch rotation of the IEC TABLE TOP supported supported
Angle coordinate system about the X- *** ***
axis of the IEC TABLE TOP
coordinate system (degrees). If
required by treatment delivery
device, shall be present for first
item of Control Point Sequence.
If required by treatment delivery
device and if Table Top Pitch
Angle changes during Beam,
shall be present in all
subsequent items of Control
Point Sequence. See
C.8.8.25.6.2.

Treatment Delivery Console 109 of 151

 IOD Details, RT Beams – C.8.8.14
TrueBeam 4DITC
Attribute Name Tag Type Attribute Description
4.0 v13.0
>> Patient (300A,0142) 1 C Direction of Table Top Pitch *** not *** not
Support Pitching Rotation when viewing the table supported supported
Direction along the positive X-axis of the *** ***
IEC TABLE TOP coordinate
system, for segment following
Control Point. If required by
treatment delivery device, shall
be present for first item of
Control Point Sequence. If
required by treatment delivery
device and if Table Top Pitch
Rotation Direction changes
during Beam, shall be present
in all subsequent items of
Control Point Sequence. See
C.8.8.14.8 and C.8.8.25.6.2.
Enumerated Values: CW =
clockwise CC = counter-
clockwise NONE = no rotation
>> Patient (300A,0144) 1C Table Top Roll Angle, i.e. the *** not *** not
Support Roll rotation of the IEC TABLE TOP supported supported
Angle coordinate system about the *** ***
IEC Y-axis of the IEC TABLE
TOP coordinate system
(degrees). If required by
treatment delivery device, shall
be present for first item of
Control Point Sequence. If
required by treatment delivery
device and if Table Top Roll
Angle changes during Beam,
shall be present in all
subsequent items of Control
Point Sequence. See
C.8.8.25.6.2.

110 of 151 Varian Treatment Delivery

Console
 IOD Details, RT Beams – C.8.8.14
TrueBeam 4DITC
Attribute Name Tag Type Attribute Description
4.0 v13.0
>> Patient (300A,0146) 1C Direction of Table Top Roll *** not *** not
Support Rolling Rotation when viewing the table supported supported
Direction along the positive Y-axis of the *** ***
IEC TABLE TOP coordinate
system, for segment following
Control Point. If required by
treatment delivery device, shall
be present for first item of
Control Point Sequence. If
required by treatment delivery
device and if Table Top Roll
Rotation Direction changes
during Beam, shall be present
in all subsequent items of
Control Point Sequence. See
C.8.8.14.8 and C.8.8.25.6.2.
Enumerated Values: CW =
clockwise CC = counter-
clockwise NONE = no rotation
>> Table Top (300A,0128) 2C Table Top Vertical position in Roundtrip Roundtrip
Vertical Position IEC TABLE TOP coordinate supported supported
system (mm). Required for first
item of Control Point Sequence,
or if Table Top Vertical Position
changes during Beam. See
C.8.8.14.6.
>> Table Top (300A,0129) 2C Table Top Longitudinal position Roundtrip Roundtrip
Longitudinal in IEC TABLE TOP coordinate supported supported
Position system (mm). Required for first
item of Control Point Sequence,
or if Table Top Longitudinal
Position changes during Beam.
See C.8.8.14.6.
>> Table Top (300A,012A) 2C Table Top Lateral position in Roundtrip Roundtrip
Lateral Position IEC TABLE TOP coordinate supported supported
system (mm). Required for first
item of Control Point Sequence,
or if Table Top Lateral Position
changes during Beam. See
C.8.8.14.6.
>> Virtual SAD (3243,XX1A) 3 The virtual SAD for this control *** not *** not
point. This SAD denotes the supported supported
physical focus of the beam if it *** ***
is different than the nominal
Source Axis Distance
(300A,00B4).

Treatment Delivery Console 111 of 151

 IOD Details, RT Beams – C.8.8.14
TrueBeam 4DITC
Attribute Name Tag Type Attribute Description
4.0 v13.0
>> Table Top (300A,0140) 3 Table Top Pitch Angle, i.e. the Beam will *** not
Pitch Angle rotation of the IEC TABLE TOP be valid if supported
coordinate system about the X- the tag is ***
axis of the IEC TABLE TOP not
coordinate system (degrees). If available
required by treatment delivery or has ‘0’
device, shall be present for first (zero)
item of Control Point Sequence. value.
If required by treatment delivery For non-
device and if Table Top Pitch zero
Angle changes during Beam, values,
shall be present in all beam will
subsequent be marked
items of Control Point as invalid.
Sequence
>> Table Top (300A,0142) 1C Direction of Table Top Pitch Beam will *** not
Pitch Rotation Rotation when viewing the table be valid if supported
Direction along the positive X-axis of the the tag is ***
IEC TABLE TOP coordinate not
system, for segment following available
Control Point. If required by or has any
treatment delivery device, shall value.
be present for first item of This value
Control Point Sequence. If will be read
required by treatment delivery and
device and if Table Top Pitch ignored.
Rotation
Direction changes during Beam,
shall be present in all
subsequent items of Control
Point Sequence. See
C.8.8.14.8 and C.8.8.25.6.2.
Enumerated Values:
CW = clockwise
CC = counter-clockwise
NONE = no rotation

112 of 151 Varian Treatment Delivery

Console
 IOD Details, RT Beams – C.8.8.14
TrueBeam 4DITC
Attribute Name Tag Type Attribute Description
4.0 v13.0
>> Table Top Roll (300A,0144) 1C Table Top Roll Angle, i.e. the Beam will *** not
Angle rotation of the IEC TABLE TOP be valid if supported
coordinate system about the the tag is ***
IEC Y-axis of the IEC TABLE not
TOP coordinate system available
(degrees). If required by or has ‘0’
treatment delivery device, shall (zero)
be present for first item of value.
Control Point Sequence. If For non-
required by treatment delivery zero
device and if Table Top Roll values,
Angle changes during Beam, beam will
shall be present in all be marked
subsequent as invalid.
items of Control Point
Sequence
>> Table Top Roll (300A,0146) 1C Direction of Table Top Roll Beam will *** not
Rotation Direction Rotation when viewing the table be valid if supported
along the positive Y-axis of the the tag is ***
IEC TABLE TOP coordinate not
system, for segment following available
Control Point. If required by or has any
treatment delivery device, shall value.
be present for first item of This value
Control Point Sequence. If will be read
required by treatment delivery and
device and if Table Top Roll ignored.
Rotation
Direction changes during Beam,
shall be present in all
subsequent items of Control
Point Sequence. See
C.8.8.14.8 and C.8.8.25.6.2.
Enumerated Values:
CW = clockwise
CC = counter-clockwise
NONE = no rotation
>> Isocenter (300A,012C) 2C Isocenter coordinates (x,y,z) in Roundtrip Roundtrip
Position the patient based coordinate supported supported
system described in C.7.6.2.1.1
(mm). Required for first item of
Segment Control Point
Sequence, or if Segment
Isocenter Position changes
during Beam.
>> Surface Entry (300A,012E) 3 Patient surface entry point *** not *** not
Point coordinates (x,y,z) in the patient supported supported
based coordinate system *** ***
described in C.7.6.2.1.1 (mm).

Treatment Delivery Console 113 of 151

 IOD Details, Approval – C.8.8.16
TrueBeam 4DITC
Attribute Name Tag Type Attribute Description
4.0 v13.0
>> Source to (300A,0130) 3 Source to Patient Surface Roundtrip Roundtrip
Surface Distance distance (mm). supported supported

>> Referenced (0008,1150) 1 Uniquely identifies the *** not *** not
SOP Class UID referenced SOP Class. supported supported
*** ***
>> Referenced (0008,1155) 1 Uniquely identifies the *** not *** not
SOP Instance referenced SOP Instance. supported supported
UID *** ***

C.2.12 Approval – C.8.8.16

Attribute Name Tag Type Attribute Description TrueBeam 4DITC

4.0 v13.0

Approval Status (300E,0002) 1 Approval status at the time the Roundtrip Roundtrip
SOP Instance was created. supported supported
Enumerated Values:
APPROVED = Reviewer
recorded that object met an
implied criterion
UNAPPROVED = No review of
object has been recorded
REJECTED = Reviewer
recorded that object failed to
meet an implied criterion
Review Date (300E,0004) 2C Date on which object was Roundtrip Roundtrip
reviewed. supported supported
Required if Approval Status
(300E,0002) is APPROVED or
REJECTED.
Review Time (300E,0005) 2C Time at which object was Roundtrip Roundtrip
reviewed. supported supported
Required if Approval Status
(300E,0002) is APPROVED or
REJECTED.
Reviewer Name (300E,0008) 2C Name of person who reviewed Roundtrip Roundtrip
object. supported supported
Required if Approval Status
(300E,0002) is APPROVED or
REJECTED.

114 of 151 Varian Treatment Delivery

Console
 IOD Details, RT General Treatment Record – C.8.8.17
C.2.13 RT General Treatment Record – C.8.8.17

Attribute Name Tag Type Attribute Description TrueBeam 4DITC

4.0 v13.0

Instance Number (0020,0013) 1 Instance number identifying this Supported Supported

particular Instance of the object.

Treatment Date (3008,0250) 2 Date when current fraction was Supported Supported
delivered, or Date last fraction
was delivered in case of RT
Treatment Summary Record
IOD. See Note.
Treatment Time (3008,0251) 2 Time when current fraction was Supported Supported
delivered (begun), or Time last
fraction was delivered (begun)
in case of RT Treatment
Summary Record IOD.
Referenced RT (300C,0002) 2 Reference to a RT Plan. Supported Supported
Plan Sequence One item shall be included in
this sequence.
>Include Table 10-11 “SOP Instance Reference Macro Attributes”
Referenced (3008,0030) 3 Reference to RT Treatment Supported Supported
Treatment Records to which the current
Record RT Treatment Record is
Sequence significantly related.
>Include Table 10-11 “SOP Instance Reference Macro Attributes”

C.2.14 RT Beams Session Record – C.8.8.21

Attribute Name Tag Type Attribute Description TrueBeam 4DITC

4.0 v13.0

Number of (300A,0078) 2 Total number of treatments Supported Supported

Fractions Planned (Fractions) planned for current
Fraction Group.

Primary Dosimeter (300A,00B3) 1 Measurement unit of machine Supported Supported

Unit dosimeter.
Enumerated Values:
MU Monitor Unit
MINUTE minute

Treatment Session (3008,0020) 1 Sequence of Beams administered Supported Supported

Beam Sequence during treatment session.
One Item shall be included in this
Sequence.

>Referenced Beam (300C,0006) 3 References Beam specified by Beam Supported Supported

Number Number (300A,00C0) in Beam
Sequence (300A,00B0) in RT Beams
Module within referenced RT Plan.

Treatment Delivery Console 115 of 151

 IOD Details, RT Beams Session Record – C.8.8.21
Attribute Name Tag Type Attribute Description TrueBeam 4DITC
4.0 v13.0

>Beam Name (300A,00C2) 3 User-defined name for delivered Supported Supported

Beam.

>Beam Type (300A,00C4) 1 Motion characteristic of delivered Supported Supported

Beam.
Enumerated Values:
STATIC All Control Point Sequence
(300A,0111) Attributes remain
unchanged between consecutive
pairs of control points with changing
Cumulative Meterset Weight
(300A,0134).
DYNAMIC One or more Control
Point Sequence (300A,0111)
Attributes change between one or
more consecutive pairs of control
points with changing Cumulative
Meterset Weight (300A,0134).

>Radiation Type (300A,00C6) 1 Particle type of delivered Beam. Supported Supported

Defined Terms:
PHOTON
ELECTRON
NEUTRON
PROTON

>High-Dose (300A,00C7) 1C Type of high-dose treatment Supported Supported

Technique Type technique.
Defined Terms:
TBI Total Body Irradiation
HDR High Dose Rate
Required if treatment technique
requires a dose that would normally
require overriding of treatment
machine safety controls.

>Referenced (300C,0040) 3 Sequence of verification images Supported Supported

Verification Image obtained during delivery of current
Sequence beam.
One or more Items are permitted in
this Sequence.

>>Include Table 10-11 “SOP Instance

Reference Macro Attributes”

>>Start Meterset (3008,0078) 3 Cumulative Meterset Weight within Supported Supported

Beam referenced by Referenced
Beam Number at which image
acquisition starts.

>>End Meterset (3008,007A) 3 Cumulative Meterset Weight within Supported Supported

116 of 151 Varian Treatment Delivery
Console
 IOD Details, RT Beams Session Record – C.8.8.21
Attribute Name Tag Type Attribute Description TrueBeam 4DITC
4.0 v13.0
Beam referenced by Referenced
Beam Number at which image
acquisition ends.

>Referenced (3008,0090) 3 Sequence of doses estimated for Supported Supported

Calculated Dose each treatment delivery.
Reference One or more Items are permitted in
Sequence this Sequence.

>>Referenced (300C,0051) 1C Uniquely identifies Dose Reference Supported Supported

Dose Reference specified by Dose Reference Number
Number (300A,0012) in Dose Reference
Sequence (300A,0010) in RT
Prescription Module of referenced RT
Plan. Required if Referenced
Calculated Dose Reference Number
(3008,0092) is not present.

>>Calculated Dose (3008,0076) 1 Calculated Dose (Gy). Supported Supported

Reference Dose
Value

>Source-Axis (300A,00B4) 3 Radiation source to gantry rotation Supported Supported

Distance axis distance of the equipment that
was used for beam delivery (mm).

>Beam Limiting (3008,00A0) 1C Sequence of beam limiting device Supported Supported

Device Leaf Pairs (collimator) jaw or leaf (element) leaf
Sequence pair values.
Required if Enhanced RT Beam
Limiting Device Definition Flag
(3008,00A3) is absent, or is present
and has the value NO.
One or more Items shall be included
in this Sequence.

>>RT Beam (300A,00B8) 1 Type of beam limiting device Supported Supported

Limiting Device (collimator).
Type Enumerated Values:
X symmetric jaw pair in IEC X
direction
Y symmetric jaw pair in IEC Y
direction
ASYMX asymmetric jaw pair in IEC X
direction
ASYMY asymmetric jaw pair in IEC Y
direction
MLCX single layer multileaf
collimator in IEC X direction
MLCY single layer multileaf
collimator in IEC Y direction

>>Number of (300A,00BC) 1 Number of leaf (element) or jaw pairs Supported Supported

Leaf/Jaw Pairs (equal to 1 for standard beam limiting

Treatment Delivery Console 117 of 151

 IOD Details, RT Beams Session Record – C.8.8.21
Attribute Name Tag Type Attribute Description TrueBeam 4DITC
4.0 v13.0
device jaws).

>Number of (300A,00D0) 1 Number of wedges associated with Supported Supported

Wedges current delivered Beam.

>Recorded Wedge (3008,00B0) 1C Sequence of treatment wedges Supported Supported

Sequence present during delivered Beam.
Required if Number of Wedges
(300A,00D0) is non-zero.
One or more Items shall be included
in this Sequence.

>>Wedge Number (300A,00D2) 3 Identification number of the Wedge. Supported Supported

The value of Wedge Number
(300A,00D2) shall be unique within
the wedge Sequence.

>>Wedge Type (300A,00D3) 2 Type of wedge defined for delivered Supported Supported
Beam.
Defined Terms:
STANDARD standard (static)
wedge
DYNAMIC moving Beam
Limiting Device (collimator) jaw
simulating wedge
MOTORIZED single wedge that can
be removed from beam remotely

>>Wedge ID (300A,00D4) 3 User-supplied identifier for wedge. Supported Supported

>>Accessory Code (300A,00F9) 3 An identifier for the accessory Supported Supported

intended to be read by a device such
as a bar-code reader.

>>Wedge Angle (300A,00D5) 3 Nominal wedge angle delivered Supported Supported

(degrees).

>>Wedge (300A,00D8) 3 Orientation of wedge, i.e., orientation Supported Supported

Orientation of IEC WEDGE FILTER coordinate
system with respect to IEC BEAM
LIMITING DEVICE coordinate system
(degrees).

>Number of (300A,00E0) 2 Number of compensators associated Supported Supported

Compensators with current delivered Beam.

>Recorded (3008,00C0) 3 Sequence of treatment compensators Supported Supported

Compensator associated with current Beam.
Sequence One or more Items are permitted in
this Sequence.

>>Referenced (300C,00D0) 1 Uniquely identifies compensator Supported Supported

Compensator specified by Compensator Number

118 of 151 Varian Treatment Delivery

Console
 IOD Details, RT Beams Session Record – C.8.8.21
Attribute Name Tag Type Attribute Description TrueBeam 4DITC
4.0 v13.0
Number (300A,00E4) within Beam referenced
by Referenced Beam Number
(300C,0006).

>>Compensator (300A,00EE) 2 Type of compensator (if any). Supported Supported

Type Defined Terms:
STANDARD physical (static)
compensator
DYNAMIC moving Beam
Limiting Device (collimator) simulating
compensator

>>Compensator ID (300A,00E5) 3 User-supplied identifier for Supported Supported

compensator.

>>Accessory Code (300A,00F9) 3 An identifier for the Compensator Supported Supported

intended to be read by a device such
as a bar-code reader.

>Number of Boli (300A,00ED) 2 Number of boli used with current Supported Supported
Beam.

>Referenced Bolus (300C,00B0) 3 Sequence of boli associated with Supported Supported

Sequence Beam.
One or more Items are permitted in
this Sequence.

>>Referenced ROI (3006,0084) 1 Uniquely identifies ROI representing Supported Supported

Number the bolus specified by ROI Number
(3006,0022) in Structure Set ROI
Sequence (3006,0020) in Structure
Set Module within RT Structure Set
IOD referenced by referenced RT
Plan in Referenced RT Plan
Sequence (300C,0002) in RT General
Treatment Record Module.

>Number of Blocks (300A,00F0) 2 Number of shielding blocks or Supported Supported

Electron Inserts associated with
Beam.

>Recorded Block (3008,00D0) 3 Sequence of blocks associated with Supported Supported

Sequence current Beam.
One or more Items are permitted in
this Sequence.

>>Block Tray ID (300A,00F5) 3 User-supplied identifier for block tray Supported Supported
or Electron Insert.

>>Accessory Code (300A,00F9) 3 An identifier for the Block intended to Supported Supported
be read by a device such as a bar-
code reader.

>>Block Name (300A,00FE) 2 User-defined name for block. Supported Supported

>Applicator (300A,0107) 3 Sequence of Applicators associated Supported Supported

Treatment Delivery Console 119 of 151

 IOD Details, RT Beams Session Record – C.8.8.21
Attribute Name Tag Type Attribute Description TrueBeam 4DITC
4.0 v13.0
Sequence with Beam.
Only a single Item is permitted in this
Sequence.

>>Applicator ID (300A,0108) 1 User or machine supplied identifier for Supported Supported

Applicator.

>>Accessory Code (300A,00F9) 3 An identifier for the accessory Supported Supported

intended to be read by a device such
as a bar-code reader.

>>Applicator Type (300A,0109) 1 Type of Applicator. Supported Supported

Defined Terms:
ELECTRON_SQUARE square
electron applicator
ELECTRON_RECT rectangular
electron applicator
ELECTRON_CIRC circular
electron applicator
ELECTRON_SHORT short electron
applicator
ELECTRON_OPEN open
(dummy) electron applicator
PHOTON_SQUARE square
photon applicator
PHOTON_RECT rectangular
photon applicator
PHOTON_CIRC circular
photon applicator
INTRAOPERATIVE intraoperative
(custom) applicator
STEREOTACTIC stereotactic
applicator (deprecated)

>>Applicator (300A,010A) 3 User-defined description for Supported Supported

Description Applicator.

>General (300A,0420) 3 A Sequence of General Accessories Supported Supported

Accessory associated with this Beam.
Sequence One or more Items are permitted in
this Sequence.

>>General (300A,0424) 1 Identification Number of the General Supported Supported

Accessory Number Accessory. The value shall be unique
within the Sequence.

>>General (300A,0421) 1 User or machine supplied identifier for Supported Supported

Accessory ID General Accessory.

>>General (300A,0422) 3 User supplied description of General Supported Supported

Accessory Accessory.

120 of 151 Varian Treatment Delivery

Console
 IOD Details, RT Beams Session Record – C.8.8.21
Attribute Name Tag Type Attribute Description TrueBeam 4DITC
4.0 v13.0
Description

>>General (300A,0423) 3 Specifies the type of accessory. Supported Supported

Accessory Type Defined Terms:
GRATICULE Accessory tray with a
radio-opaque grid
IMAGE_DETECTOR Image
acquisition device positioned in the
beam line
RETICLE Accessory tray with
radio-transparent markers or grid

>>Accessory Code (300A,00F9) 3 Machine-readable identifier for this Supported Supported

accessory.

>>Source to (300A,0425) 3 Radiation source to general Supported Supported

General Accessory accessory distance (in mm) for
Distance current accessory.

>Current Fraction (3008,0022) 2 Fraction number for this beam Supported Supported
Number administration.

>Treatment (300A,00CE) 2 Delivery Type of treatment. Supported Supported

Delivery Type Defined Terms:
TREATMENT Normal patient
treatment
OPEN_PORTFILM Portal image
acquisition with open field
TRMT_PORTFILM Portal image
acquisition with treatment port
CONTINUATION Continuation
of interrupted treatment
SETUP No treatment beam is applied
for this RT Beam. To be used for
specifying the gantry, couch, and
other machine positions where X-Ray
set-up images or measurements are
to be taken.
VERIFICATION Treatment used for
Quality Assurance rather than patient
treatment

>Treatment (3008,002A) 1 Conditions under which treatment Supported Supported

Termination Status was terminated.
Enumerated Values:
NORMAL treatment terminated
normally
OPERATOR operator terminated
treatment
MACHINE machine terminated
treatment
UNKNOWN status at termination

Treatment Delivery Console 121 of 151

 IOD Details, RT Beams Session Record – C.8.8.21
Attribute Name Tag Type Attribute Description TrueBeam 4DITC
4.0 v13.0
unknown

> Treatment (300A,002B) 2 The reason code why the current Supported Supported
Termination Code treatment beam has terminated.
Expected if the Treatment
Termination Status (3008,002A) is not
NORMAL.
Enumerated Values:
OPERATOR operator terminated
treatment
FAULT machine terminated
treatment
UNKNOWN status at termination
unknown

>Treatment (3008,002C) 2 Conditions under which treatment Supported Supported

Verification Status was verified by a verification system.
Enumerated Values:
VERIFIED treatment verified
VERIFIED_OVR treatment
verified with at least one out-of-range
value overridden
NOT_VERIFIED treatment
verified manually

>Interlock (300A,0740) 3 Interlocks which occurred prior, during Supported

Sequence or after the delivery of radiation of this *** not
beam. supported
One or more Items are permitted in ***
this Sequence.

Date and Time when the Interlock

occurred.
*** not
>>Interlock The date and time of occurrence may Supported
(300A,0741) 1 supported
DateTime be when the interlock occurred (e.g. ***
by a real-time system) or when the
interlock was recorded.

*** not
>>Interlock User-readable description of the
(300A,0742) 1 Supported supported
Description interlock.
***

Code(s) that describe the interlock(s)

that occurred. *** not
>>Interlock Code
(300A,0744) 1 Supported supported
Sequence One or more Items shall be included ***
in this Sequence.

The identifier of the Coded Entry.

*** not
>>>Code Value (0008,0100) 1C Shall be present if the code value Supported supported
length is 16 characters or less, and ***
the code value is not a URN or URL.

122 of 151 Varian Treatment Delivery

Console
 IOD Details, RT Beams Session Record – C.8.8.21
Attribute Name Tag Type Attribute Description TrueBeam 4DITC
4.0 v13.0

The value of a Coding Scheme *** not

>>>Code Scheme
(0008,0102) 1 Designator, used in this SOP Supported supported
Designator
Instance, which is being mapped. ***

*** not
Text that conveys the meaning of the
>>>Code Meaning (0008,0104) 1C Supported supported
Coded Entry.
***

The action applied to resolve the

>> Interlock interlock. *** not
Resolution Code (300A,0745) 1 Supported supported
Sequence One or more Items shall be included ***
in this Sequence.

The identifier of the Coded Entry.

*** not
>>>Code Value (0008,0100) 1C Shall be present if the code value Supported supported
length is 16 characters or less, and ***
the code value is not a URN or URL.

The value of a Coding Scheme *** not

>>>Code Scheme
(0008,0102) 1 Designator, used in this SOP Supported supported
Designator
Instance, which is being mapped. ***

*** not
Text that conveys the meaning of the
>>>Code Meaning (0008,0104) 1C Supported supported
Coded Entry.
***

>>Interlock The user that resolved the interlock. *** not

Resolution User (300A,0746) 2 Zero or more Items shall be included Supported supported
Sequence in this Sequence. ***

Institution or organization to which the

identified individual is responsible or *** not
>>>Institution
(0008,0080) 1C accountable. Supported supported
Name
***
Required if Institution Code Sequence

Mailing address of the institution or

*** not
>>>Institution organization to which the identified
(0008,0081) 1C Supported supported
Address individual is responsible or
***
accountable.

A coded entry that identifies a person.

The Code Meaning Attribute, though it
will be encoded with a VR of LO, may
be encoded according to the rules of
the PN VR (e.g., caret '^' delimiters
shall separate name components),
>>>Personal except that a single component (i.e., *** not
Identification Code (0040,1101) 1 the whole name unseparated by caret Supported supported
Sequence delimiters) is not permitted. Name ***
component groups for use with multi-
byte character sets are permitted, as
long as they fit within the 64
characters (the length of the LO VR).
One or more Items shall be included
in this Sequence.

Treatment Delivery Console 123 of 151

 IOD Details, RT Beams Session Record – C.8.8.21
Attribute Name Tag Type Attribute Description TrueBeam 4DITC
4.0 v13.0

The identifier of the Coded Entry.

*** not
>>>>Code Value (0008,0100) 1 Shall be present if the code value Supported supported
length is 16 characters or less, and ***
the code value is not a URN or URL.

The value of a Coding Scheme *** not

>>>>Code Scheme
(0008,0102) 1C Designator, used in this SOP Supported supported
Designator
Instance, which is being mapped. ***

*** not
>>>>Code Text that conveys the meaning of the
(0008,0104) 1 Supported supported
Meaning Coded Entry.
***

Description of the origin of the

interlock. *** not
>>Interlock Origin
(300A,0783) 1C Required if Interlock Originating Supported supported
Description
Device Sequence (300A,0743) is not ***
present.

>Delivered (3008,003B) 3 Treatment Time actually delivered

Supported Supported
Treatment Time (sec).

>Gating Beam Hold (300C,0125) 3 The beam hold transitions due to

Transition beam gating function according to *** not
Sequence [IEC 60601-2-1]. Supported supported
One or more items are permitted in ***
this Sequence.

>>Beam Hold (300C,0126) 1 Beam hold transition during

Transition irradiation. *** not
Enumerated Values: Supported supported
HOLD Beam held. ***
RESTART Beam restarted.

>>Beam Hold (300C,0127) 1 DateTime of the beam hold transition. *** not
Transition Supported supported
DateTime ***

>>Beam Hold (300C,0128) 1C The device that triggered the beam

Originating Device hold.
Sequence Required if there are multiple devices *** not
in the treatment delivery device that Supported supported
can trigger the beam hold. ***
Only a single Item shall be included in
this Sequence.

Manufacturer's serial number of the *** not

>>>Device Serial
(0018,1000) 3 equipment that is to be used for beam Supported supported
Number
delivery. ***

>>>Software Manufacturer's designation of *** not

(0018,1020) 3 Supported
Versions software version of the identified supported

124 of 151 Varian Treatment Delivery

Console
 IOD Details, RT Beams Session Record – C.8.8.21
Attribute Name Tag Type Attribute Description TrueBeam 4DITC
4.0 v13.0
device. ***

*** not
>>>Long Device User-defined description for this
(0050,0021) 3 Supported supported
Description device.
***

*** not
>>>Device An identifier intended to be read by a
(3010,001B) 2 Supported supported
Alternate Identifier device such as a bar code reader.
***

Defines the type of Device Alternate

Identifier.
>>>Device Required if Device Alternate Identifier *** not
Alternate Identifier (3010,001C) 1C (3010,001B) has a value. Supported supported
Type Defined Terms: ***
BARCODE
RFID

Description of the format in which the

>>>Device Device Alternate Identifier *** not
Alternate Identifier (3010,001D) 1C (3010,001B) is issued. Supported supported
Format Required if Device Alternate Identifier ***
(3010,001B) has a value.

*** not
>>>Device Label (3010,002D) 1 User-defined label for this device Supported supported
***

The type of the device. *** not

>>>Device Type
(3010,002E) 1 Only a single Item shall be included in Supported supported
Code Sequence
this Sequence. ***

The identifier of the Coded Entry.

*** not
>>>>Code Value (0008,0100) 1C Shall be present if the code value Supported supported
length is 16 characters or less, and ***
the code value is not a URN or URL.

The identifier of the coding scheme in

which the Coded Entry is defined.
*** not
>>>>Coding Shall be present if Code Value
(0008,0102) 1C Supported supported
Scheme Designator (0008,0100) or Long Code Value ***
(0008,0119) is present. May be
present otherwise.

*** not
>>>>Code Text that conveys the meaning of the
(0008,0104) 1 Supported supported
Meaning Coded Entry.
***

*** not
>>> Manufacturer’s An identifier issued by the
(3040,0043) 2 Supported supported
Device Identifier manufacturer.
***

>Number of Control (300A,0110) 1 Number of control points delivered. Supported Supported

Points Value shall be greater than or equal

Treatment Delivery Console 125 of 151

 IOD Details, RT Beams Session Record – C.8.8.21
Attribute Name Tag Type Attribute Description TrueBeam 4DITC
4.0 v13.0
to 2.

>Control Point (3008,0040) 1 Sequence of beam control points for Supported Supported
Delivery Sequence current treatment beam.
The number of Items in this Sequence
shall equal the value of Number of
Control Points (300A,0110).

>>Referenced (300C,00F0) 3 Uniquely identifies Control Point Supported Supported

Control Point Index specified by Control Point Index
(300A,0112) within Beam referenced
by Referenced Beam Number
(300C,0006).

>>Treatment (3008,0024) 1 Date when the delivery of radiation at Supported Supported

Control Point Date this control point began. For the final
control point this shall be the Date
when the previous control point
ended.

>>Treatment (3008,0025) 1 Time when the delivery of radiation at Supported Supported

Control Point Time this control point began. For the final
control point this shall be the Time
when the previous control point
ended.

>>Specified (3008,0042) 2 Desired machine setting for current Supported Supported

Meterset control point.

>>Delivered (3008,0044) 1 Machine setting actually delivered at Supported Supported

Meterset current control point.

>>Dose Rate Set (300A,0115) 2 Dose Rate set on treatment machine Supported Supported
for segment beginning at current
control point (Meterset/min).

>>Dose Rate (3008,0048) 2 Dose Rate actually delivered for Supported Supported
Delivered segment beginning at current control
point (Meterset/min).

>>Nominal Beam (300A,0114) 3 Nominal Beam Energy at control Supported Supported

Energy point.

>>Nominal Beam (300A,0015) 1C Units used for Nominal Beam Energy Supported Supported
Energy Unit (300A,0114). Required if Nominal
Beam Energy (300A,0114) is present.
Defined Terms:
MV Megavolt
MEV Mega electron-Volt
If Radiation Type (300A,00C6) is
PHOTON, Nominal Beam Energy Unit
(300A,0015) shall be MV. If Radiation
Type (300A,00C6) is ELECTRON,
Nominal Beam Energy Unit
126 of 151 Varian Treatment Delivery
Console
 IOD Details, RT Beams Session Record – C.8.8.21
Attribute Name Tag Type Attribute Description TrueBeam 4DITC
4.0 v13.0
(300A,0015) shall be MEV.

>>Wedge Position (300A,0116) 3 Sequence of Wedge positions for Supported Supported

Sequence current control point.
One or more Items are permitted in
this Sequence.

>>>Referenced (300C,00C0) 1 Uniquely identifies wedge specified by Supported Supported

Wedge Number Wedge Number (300A,00D2) within
the Recorded Wedge Sequence
(3008,00B0).

>>>Wedge Position (300A,0118) 1 Position of Wedge at current control Supported Supported

point.
Enumerated Values:
IN
OUT

>>Beam Limiting (300A,011A) 1C Sequence of beam limiting device Supported Supported

Device Position (collimator) jaw or leaf (element)
Sequence positions.
One or more Items shall be included
in this Sequence.
Required for the first Control Point of
Control Point Delivery Sequence
(3008,0040), or if beam limiting
device (collimator) changes during
beam administration and if Enhanced
RT Beam Limiting Device Definition
Flag (3008,00A3) is absent, or is
present has the value NO.

>>>RT Beam (300A,00B8) 1 Type of beam limiting device. The Supported Supported
Limiting Device value of this Attribute shall
Type correspond to RT Beam Limiting
Device Type (300A,00B8) defined in
an element of Beam Limiting Device
Leaf Pairs Sequence (3008,00A0).
Enumerated Values:
X symmetric jaw pair in IEC X
direction
Y symmetric jaw pair in IEC Y
direction
ASYMX asymmetric jaw pair in IEC X
direction
ASYMY asymmetric jaw pair in IEC Y
direction
MLCX multileaf (multi-element) jaw
pair in IEC X direction
MLCY multileaf (multi-element) jaw
pair in IEC Y direction

Treatment Delivery Console 127 of 151

 IOD Details, RT Beams Session Record – C.8.8.21
Attribute Name Tag Type Attribute Description TrueBeam 4DITC
4.0 v13.0

>>>Leaf/Jaw (300A,011C) 1 Positions of beam limiting device Supported Supported

Positions (collimator) leaf (element) or jaw pairs
(mm) in IEC BEAM LIMITING
DEVICE coordinate axis appropriate
to RT Beam Limiting Device Type
(300A,00B8), e.g., X-axis for MLCX,
Y-axis for MLCY. Contains 2N values,
where N is the Number of Leaf/Jaw
Pairs (300A,00BC) defined in element
of Beam Limiting Device Leaf Pairs
Sequence (3008,00A0). Values shall
be in IEC leaf subscript order 101,
102, … 1N, 201, 202 … 2N.

>>Gantry Angle (300A,011E) 1C Treatment machine gantry angle, i.e., Supported Supported
orientation of IEC GANTRY
coordinate system with respect to IEC
FIXED REFERENCE coordinate
system (degrees). Required for
Control Point 0 of Control Point
Delivery Sequence (3008,0040) or if
Gantry Angle changes during beam
administration.

>>Gantry Rotation (300A,011F) 1C Direction of Gantry Rotation when Supported Supported

Direction viewing gantry from isocenter, for
segment beginning at current Control
Point. Required for Control Point 0 of
Control Point Delivery Sequence
(3008,0040), or if Gantry Rotation
Direction changes during beam
administration.
Enumerated Values:
CW clockwise
CC counter-clockwise
NONE no rotation

>>Beam Limiting (300A,0120) 1C Beam Limiting Device (collimator) Supported Supported

Device Angle angle, i.e., orientation of IEC BEAM
LIMITING DEVICE coordinate system
with respect to IEC GANTRY
coordinate system (degrees).
Required for Control Point 0 of
Control Point Delivery Sequence
(3008,0040) or if beam limiting device
(collimator) angle changes during
beam delivery.

>>Beam Limiting (300A,0121) 1C Direction of Beam Limiting Device Supported Supported

Device Rotation Rotation when viewing beam limiting
Direction device (collimator) from radiation
source, for segment beginning at
current Control Point. Required for
128 of 151 Varian Treatment Delivery
Console
 IOD Details, RT Beams Session Record – C.8.8.21
Attribute Name Tag Type Attribute Description TrueBeam 4DITC
4.0 v13.0
Control Point 0 of Control Point
Delivery Sequence (3008,0040) or if
Beam Limiting Device Rotation
Direction changes during beam
administration.
Enumerated Values:
CW clockwise
CC counter-clockwise
NONE no rotation

>>Patient Support (300A,0122) 1C Patient Support angle, i.e., orientation Supported Supported
Angle of IEC PATIENT SUPPORT
(turntable) coordinate system with
respect to IEC FIXED REFERENCE
coordinate system (degrees).
Required for Control Point 0 of
Control Point Delivery Sequence
(3008,0040) or if Patient Support
Angle changes during beam
administration.

>>Patient Support (300A,0123) 1C Direction of Patient Support Rotation Supported Supported

Rotation Direction when viewing table from above, for
segment beginning at current Control
Point. Required for Control Point 0 of
Control Point Delivery Sequence
(3008,0040), or if Patient Support
Rotation Direction changes during
beam administration.
Enumerated Values:
CW clockwise
CC counter-clockwise
NONE no rotation

>>Table Top (300A,0124) 3 Distance (positive) from the IEC Supported Supported
Eccentric Axis PATIENT SUPPORT vertical axis to
Distance the IEC TABLE TOP ECCENTRIC
vertical axis (mm).

>>Table Top (300A,0125) 1C Table Top (non-isocentric) angle, i.e., Supported Supported
Eccentric Angle orientation of IEC TABLE TOP
ECCENTRIC coordinate system with
respect to IEC PATIENT SUPPORT
coordinate system (degrees).
Required for Control Point 0 of
Control Point Delivery Sequence
(3008,0040) or if Table Top Eccentric
Angle changes during beam
administration.

>>Table Top (300A,0126) 1C Direction of Table Top Eccentric Supported Supported

Eccentric Rotation Rotation when viewing table from
Direction above, for segment beginning at
current Control Point. Required for

Treatment Delivery Console 129 of 151

 IOD Details, RT Beams Session Record – C.8.8.21
Attribute Name Tag Type Attribute Description TrueBeam 4DITC
4.0 v13.0
Control Point 0 of Control Point
Delivery Sequence (3008,0040) or if
Table Top Eccentric Rotation
Direction changes during beam
administration.
Enumerated Values:
CW clockwise
CC counter-clockwise
NONE no rotation

>>Table Top Pitch (300A,0140) 1C Table Top Pitch Angle, i.e., the Supported Supported
Angle rotation of the IEC TABLE TOP
coordinate system about the X-axis of
the IEC TABLE TOP coordinate
system (degrees). If required by
treatment delivery device, shall be
present for first Item of Control Point
Sequence. If required by treatment
delivery device and if Table Top Pitch
Angle changes during Beam, shall be
present in all subsequent Items of
Control Point Sequence.

>>Table Top Pitch (300A,0142) 1C Direction of Table Top Pitch Rotation Supported Supported
Rotation Direction when viewing the table along the
positive X-axis of the IEC TABLE
TOP coordinate system, for segment
following Control Point. If required by
treatment delivery device, shall be
present for first Item of Control Point
Sequence. If required by treatment
delivery device and if Table Top Pitch
Rotation Direction changes during
Beam, shall be present in all
subsequent Items of Control Point
Sequence.
Enumerated Values:
CW clockwise
CC counter-clockwise
NONE no rotation

>>Table Top Roll (300A,0144) 1C Table Top Roll Angle, i.e., the rotation Supported Supported
Angle of the IEC TABLE TOP coordinate
system about the IEC Y-axis of the
IEC TABLE TOP coordinate system
(degrees). If required by treatment
delivery device, shall be present for
first Item of Control Point Sequence. If
required by treatment delivery device
and if Table Top Roll Angle changes
during Beam, shall be present in all
subsequent Items of Control Point

130 of 151 Varian Treatment Delivery

Console
 IOD Details, RT Beams Session Record – C.8.8.21
Attribute Name Tag Type Attribute Description TrueBeam 4DITC
4.0 v13.0
Sequence.

>>Table Top Roll (300A,0146) 1C Direction of Table Top Roll Rotation Supported Supported
Rotation Direction when viewing the table along the
positive Y-axis of the IEC TABLE
TOP coordinate system, for segment
following Control Point. If required by
treatment delivery device, shall be
present for first Item of Control Point
Sequence. If required by treatment
delivery device and if Table Top Roll
Rotation Direction changes during
Beam, shall be present in all
subsequent Items of Control Point
Sequence.
Enumerated Values:
CW clockwise
CC counter-clockwise
NONE no rotation

>>Table Top (300A,0128) 2C Table Top Vertical position in IEC Supported Supported
Vertical Position TABLE TOP coordinate system (mm).
This value is interpreted as an
absolute, rather than relative, Table
setting. Required for Control Point 0
of Control Point Delivery Sequence
(3008,0040) or if Table Top Vertical
Position changes during beam
administration.

>>Table Top (300A,0129) 2C Table Top Longitudinal position in IEC Supported Supported
Longitudinal TABLE TOP coordinate system (mm).
Position This value is interpreted as an
absolute, rather than relative, Table
setting. Required for Control Point 0
of Control Point Delivery Sequence
(3008,0040) or if Table Top
Longitudinal Position changes during
beam administration.

>>Table Top (300A,012A) 2C Table Top Lateral position in IEC Supported Supported
Lateral Position TABLE TOP coordinate system (mm).
This value is interpreted as an
absolute, rather than relative, Table
setting. Required for Control Point 0
of Control Point Delivery Sequence
(3008,0040) or if Table Top Lateral
Position changes during beam
administration.

>>Override (3008,0060) 3 Sequence of parameters that were Supported Supported

Sequence overridden during the administration
of the beam segment immediately
prior to the current control point.
One or more Items are permitted in

Treatment Delivery Console 131 of 151

 IOD Details, SOP Common – C.12.1
Attribute Name Tag Type Attribute Description TrueBeam 4DITC
4.0 v13.0
this Sequence.

>>>Override (3008,0062) 2 Contains the Data Element Tag of the Supported Supported
Parameter Pointer Attribute that was overridden.

>>>Operators' (0008,1070) 2 Name of operator who authorized Supported Supported

Name override.

C.2.15 SOP Common – C.12.1

Attribute Name Tag Type Attribute Description TrueBeam 4DITC

4.0 v13.0

SOP Class UID (0008,0016) 1 Uniquely identifies the SOP Roundtrip Roundtrip
Class. See C.12.1.1.1 for supported supported
further explanation. See also
PS 3.4.
SOP Instance (0008,0018) 1 Uniquely identifies the SOP Roundtrip Roundtrip
UID Instance. See C.12.1.1.1 for supported supported
further explanation. See also
PS 3.4.
Specific (0008,0005) 1C Character Set that expands or Roundtrip Roundtrip
Character Set replaces the Basic Graphic Set. supported supported
Required if an expanded or
replacement character set is
used. See C.12.1.1.2 for
Defined Terms.
Instance (0008,0012) 3 Date the SOP Instance was Roundtrip Roundtrip
Creation Date created. supported supported

Instance (0008,0013) 3 Time the SOP Instance was Roundtrip Roundtrip

Creation Time created. supported supported

Instance Creator (0008,0014) 3 Uniquely identifies device which Roundtrip Roundtrip

UID created the SOP Instance. supported supported

Related General (0008,001A) 3 Uniquely identifies a Related *** not *** not
SOP Class UID General SOP Class for the SOP supported supported
Class of this Instance. See PS *** ***
3.4.

132 of 151 Varian Treatment Delivery

Console
 IOD Details, SOP Common – C.12.1
Attribute Name Tag Type Attribute Description TrueBeam 4DITC
4.0 v13.0

Original (0008,001B) 3 The SOP Class in which the *** not *** not
Specialized SOP Instance was originally supported supported
Class UID encoded, but which has been *** ***
replaced during a fall-back
conversion to the current
Related General SOP Class.
See PS 3.4.
Coding Scheme (0008,0110) 3 Sequence of items that map *** not *** not
Identification values of Coding Scheme supported supported
Sequence Designator (0008,0102) to an *** ***
external coding system
registration, or to a private or
local coding scheme. One or
more items may be present in
the sequence.
> Coding (0008,0102) 1 The value of a Coding Scheme *** not *** not
Scheme Designator, used in this SOP supported supported
Designator Instance, which is being *** ***
mapped.

> Coding (0008,0112) 1C The name of the external *** not *** not
Scheme Registry registry where further definition supported supported
of the identified coding scheme *** ***
may be obtained. Required if
coding scheme is registered.
Defined term:
HL7

> Coding (0008,010C) 1C The coding scheme UID *** not *** not
Scheme UID identifier. supported supported
Required if coding scheme is *** ***
identified by an ISO 8824 object
identifier compatible with the UI
VR.

Treatment Delivery Console 133 of 151

 IOD Details, SOP Common – C.12.1
Attribute Name Tag Type Attribute Description TrueBeam 4DITC
4.0 v13.0

> Coding (0008,0114) 2C The coding scheme identifier as *** not *** not
Scheme External defined in an external registry. supported supported
ID Required if coding scheme is *** ***
registered and Coding Scheme
UID (0008,010C) is not present.
> Coding (0008,0115) 3 The coding scheme full *** not *** not
Scheme Name common name supported supported
*** ***
> Coding (0008,0103) 3 The coding scheme version *** not *** not
Scheme Version associated with the Coding supported supported
Scheme Designator *** ***
(0008,0102).
> Responsible (0008,0116) 3 Name of the organization *** not *** not
Organization responsible for the Coding supported supported
Scheme. May include *** ***
organizational contact
information.

134 of 151 Varian Treatment Delivery

Console
 IOD Details, SOP Common – C.12.1
Attribute Name Tag Type Attribute Description TrueBeam 4DITC
4.0 v13.0

Timezone Offset (0008,0201) 3 Contains the offset from UTC to *** not *** not
From UTC the timezone for all DA and TM supported supported
Attributes present in this SOP *** ***
Instance. Encoded as an ASCII
string in the format "&ZZZZ".
The components of this string,
from left to right, are & = "+" or
"-", and ZZZZ = Hours and
Minutes of offset.
Notes:
1. This encoding is the same as
described in PS 3.5 for the DT
Value Representation.
2. This Attribute does not apply
to values with a DT Value
Representation, which may
contain an explicitly encoded
timezone.
3. The corrected time may
cross a 24 hour boundary. For
example, if Local Time = 1.00
a.m. and Offset = +0200, then
UTC = 11.00 p.m. (23.00) the
day before.
4. The "+" sign may not be
omitted. Time earlier than UTC
is expressed as a negative
offset.
Note:
For example: UTC = 5.00 a.m.
Local Time = 3.00 a.m. Offset =
-0200 The local timezone offset
is undefined if this Attribute is
absent.
Contributing (0018,A001) 3 Sequence of Items containing *** not *** not
Equipment descriptive attributes of related supported supported
Sequence equipment which has *** ***
contributed to the acquisition,
creation or modification of the
composite instance. One or
more Items may be included in
this Sequence. See C.12.1.1.5
for further explanation.
> Purpose of (0040,A170) 1 Describes the purpose for *** not *** not
Reference Code which the related equipment is supported supported
Sequence being reference. Only a single *** ***
Item shall be permitted in this
sequence. See C.12.1.1.5 for
further explanation.
>> Code Value (0008,0100) 1C See Section 8.1. Required if a *** not *** not
sequence item is present. supported supported
*** ***
Treatment Delivery Console 135 of 151
 IOD Details, SOP Common – C.12.1
Attribute Name Tag Type Attribute Description TrueBeam 4DITC
4.0 v13.0

>> Coding (0008,0102) 1C See Section 8.2. Required if a *** not *** not
Scheme sequence item is present. supported supported
Designator *** ***
>> Coding (0008,0103) 1C See Section 8.2. Required if a *** not *** not
Scheme Version sequence item is present and supported supported
the value of Coding Scheme *** ***
Designator (0008,0102) is not
sufficient to identify the Code
Value (0008,0100)
unambiguously.
>> Code (0008,0104) 1C See Section 8.3. Required if a *** not *** not
Meaning sequence item is present. supported supported
*** ***
> Manufacturer (0008,0070) 1 Manufacturer of the equipment *** not *** not
that contributed to the supported supported
composite instance. *** ***
> Institution (0008,0080) 3 Institution where the equipment *** not *** not
Name that contributed to the supported supported
composite instance is located. *** ***
> Institution (0008,0081) 3 Address of the institution where *** not *** not
Address the equipment that contributed supported supported
to the composite instance is *** ***
located.
> Station Name (0008,1010) 3 User defined name identifying *** not *** not
the machine that contributed to supported supported
the composite instance. *** ***
> Institutional (0008,1040) 3 Department in the institution *** not *** not
Department where the equipment that supported supported
Name contributed to the composite *** ***
instance is located.
> Manufacturer’s (0008,1090) 3 Manufacturer's model name of *** not *** not
Model Name the equipment that contributed supported supported
to the composite instance. *** ***
> Device Serial (0018,1000) 3 Manufacturer's serial number of *** not *** not
Number the equipment that contributed supported supported
to the composite instance. *** ***
> Software (0018,1020) 3 Manufacturer's designation of *** not *** not
Version(s) the software version of the supported supported
equipment that contributed to *** ***
the composite instance.

136 of 151 Varian Treatment Delivery

Console
 IOD Details, SOP Common – C.12.1
Attribute Name Tag Type Attribute Description TrueBeam 4DITC
4.0 v13.0

> Spatial (0018,1050) 3 The inherent limiting resolution *** not *** not
Resolution in mm of the acquisition supported supported
equipment for high contrast *** ***
objects for the data gathering
and reconstruction technique
chosen. If variable across the
images of the series, the value
at the image center.
> Date of Last (0018,1200) 3 Date when the image *** not *** not
Calibration acquisition device calibration supported supported
was last changed in any way. *** ***
Multiple entries may be used for
additional calibrations at other
times. See C.7.5.1.1.1 for
further explanation.
> Time of Last (0018,1201) 3 Time when the image *** not *** not
Calibration acquisition device calibration supported supported
was last changed in any way. *** ***
Multiple entries may be used.
See C.7.5.1.1.1 for further
explanation.
> Contribution (0018,A002) 3 The Date & Time when the *** not *** not
Date Time equipment contributed to the supported supported
composite instance. *** ***
> Contribution (0018,A003) 3 Description of the contribution *** not *** not
Description the equipment made to the supported supported
composite instance. *** ***
Instance Number (0020,0013) 3 A number that identifies this *** not *** not
Composite object instance. supported supported
*** ***

Treatment Delivery Console 137 of 151

 IOD Details, SOP Common – C.12.1
Attribute Name Tag Type Attribute Description TrueBeam 4DITC
4.0 v13.0

SOP Instance (0100,0410) 3 A flag that indicates the storage *** not *** not
Status status of the SOP Instance. Not supported supported
Specified (NS) implies that this *** ***
SOP Instance has no special
storage status, and hence no
special actions need be taken.
Original (OR) implies that this is
the primary SOP instance for
the purpose of storage, but that
it has not yet been authorized
for diagnostic use. Authorized
Original (AO) implies that this is
the primary SOP instance for
the purpose of storage, which
has been authorized for
diagnostic use. Any copies of
an Authorized Original should
be given the status of
Authorized Copy. Authorized
Copy (AC) implies that this is a
copy of an Authorized Original
SOP Instance.
Enumerated Values:
NS, OR, AO, AC
Note:
Proper use of these flags is
specified in Security Profiles.
Implementations that do not
conform to such Security
Profiles may not necessarily
handle these flags properly.
SOP (0100,0420) 3 The date and time when the *** not *** not
Authorization SOP Instance Status supported supported
Date and Time (0100,0410) was set to AO. *** ***
SOP (0100,0424) 3 Any comments associated with *** not *** not
Authorization the setting of the SOP Instance supported supported
Comment Status (0100,0410) to AO. *** ***
Authorization (0100,0426) 3 The certification number issued *** not *** not
Equipment to the Application Entity that set supported supported
Certification the SOP Instance Status *** ***
Number (0100,0410) to AO.
MAC Parameters (4FFE,0001) 3 A sequence of one or more *** not *** not
Sequence items that describe the supported supported
parameters used to calculate a *** ***
MAC for use in Digital
Signatures.
> MAC ID (0400,0005) 1 A number used to identify this *** not *** not
Number MAC Parameters Sequence supported supported
item. *** ***

138 of 151 Varian Treatment Delivery

Console
 IOD Details, SOP Common – C.12.1
Attribute Name Tag Type Attribute Description TrueBeam 4DITC
4.0 v13.0

> MAC (0400,0010) 1 The Transfer Syntax UID used *** not *** not
Calculation to encode the values of the supported supported
Transfer Syntax Data Elements included in the *** ***
UID MAC calculation. Only Transfer
Syntaxes that explicitly include
the VR and use Little Endian
encoding shall be used. Notes:
Certain Transfer Syntaxes,
particularly those that are used
with compressed data, allow the
fragmentation of the pixel data
to change. If such
fragmentation changes, Digital
Signatures generated with such
Transfer Syntaxes could
become invalid.
> MAC Algorithm (0400,0015) 1 The algorithm used in *** not *** not
generating the MAC to be supported supported
encrypted to form the Digital *** ***
Signature. Defined Terms:
RIPEMD160
MD5
SHA1. Note: Digital Signature
Security Profiles (see PS 3.15)
may require the use of a
restricted subset of these terms.
> Data Elements (0400,0020) 1 A list of Data Element Tags in *** not *** not
Signed the order they appear in the supported supported
Data Set which identify the Data *** ***
Elements used in creating the
MAC for the Digital Signature.
See Section C.12.1.1.3.1.1.
Digital (FFFA,FFFA) 3 Sequence holding one or more *** not *** not
Signatures Digital Signatures. supported supported
Sequence *** ***
> MAC ID (0400,0005) 1 A number used to identify which *** not *** not
Number MAC Parameters Sequence supported supported
item was used in the calculation *** ***
of this Digital Signature.
> Digital (0400,0100) 1 A UID that can be used to *** not *** not
Signature UID uniquely reference this supported supported
signature. *** ***

Treatment Delivery Console 139 of 151

 IOD Details, SOP Common – C.12.1
Attribute Name Tag Type Attribute Description TrueBeam 4DITC
4.0 v13.0

> Digital (0400,0105) 1 The date and time the Digital *** not *** not
Signature Signature was created. The supported supported
DateTime time shall include an offset (i.e., *** ***
time zone indication) from
Coordinated Universal Time.
Note: This is not a certified
timestamp, and hence is not
completely verifiable. An
application can compare this
date and time with those of
other signatures and the validity
date of the certificate to gain
confidence in the veracity of this
date and time.
> Certificate (0400,0110) 1 The type of certificate used in *** not *** not
Type (0400,0115). Defined Term: supported supported
X509_1993_SIG Note: Digital *** ***
Signature Security Profiles (see
PS 3.15) may require the use of
a restricted subset of these
terms.
> Certificate of (0400,0115) 1 A certificate that holds the *** not *** not
Signer identity of the entity producing supported supported
this Digital Signature, that *** ***
entity's public key or key
identifier, and the algorithm and
associated parameters with
which that public key is to be
used. Algorithms allowed are
specified in Digital Signature
Security Profiles (see PS 3.15).
Notes:
1. As technology advances,
additional encryption algorithms
may be allowed in future
versions. Implementations
should take this possibility into
account.
2. When symmetric encryption
is used, the certificate merely
identifies which key was used
by which entity, but not the
actual key itself. Some other
means (e.g., a trusted third
party) must be used to obtain
the key.

140 of 151 Varian Treatment Delivery

Console
 IOD Details, SOP Common – C.12.1
Attribute Name Tag Type Attribute Description TrueBeam 4DITC
4.0 v13.0

> Signature (0400,0120) 1 The MAC generated as *** not *** not
described in Section 12.2.1.1 supported supported
and encrypted using the *** ***
algorithm, parameters, and
private key associated with the
Certificate of the Signer
(0400,0115). See Section
C.12.1.1.3.1.2.
> Certified (0400,0305) 1C The type of certified timestamp *** not *** not
Timestamp Type used in the Certified Timestamp supported supported
(0400,0310) Attribute. Required *** ***
if Certified Timestamp
(0400,0310) is present. Defined
Terms:
CMS_TSP û Internet X.509
Public Key Infrastructure Time
Stamp Protocol Note: Digital
Signature Security Profiles (see
PS 3.15) may require the use of
a restricted subset of these
terms.
> Certified (0400,0310) 3 A certified timestamp of the *** not *** not
Timestamp Digital Signature (0400,0120) supported supported
Attribute Value, which shall be *** ***
obtained when the Digital
Signature is created. See
Section C.12.1.1.3.1.3.
Encrypted (0400,0500) 1C Sequence of Items containing *** not *** not
Attributes encrypted DICOM data. One or supported supported
Sequence more Items shall be present. *** ***
Required if application level
confidentiality is needed and
certain recipients are allowed to
decrypt all or portions of the
Encrypted Attributes Data Set.
See C.12.1.1.4.1.
> Encrypted (0400,0510) 1 Transfer Syntax used to encode *** not *** not
Content Transfer the encrypted content. Only supported supported
Syntax UID Transfer Syntaxes that explicitly *** ***
include the VR and use Little
Endian encoding shall be used.
> Encrypted (0400,0520) 1 Encrypted data. See *** not *** not
Content C.12.1.1.4.2. supported supported
*** ***

Treatment Delivery Console 141 of 151

 IOD Details, Extended Interface – Private
Attribute Name Tag Type Attribute Description TrueBeam 4DITC
4.0 v13.0

HL7 Structured (0040,A390) 1C Sequence of items defining *** not *** not
Document mapping and/or access supported supported
Reference mechanism for HL7 Structured *** ***
Sequence Documents referenced from the
current SOP Instance. One or
more Items may be included in
this sequence. See C.12.1.1.6.
Required if HL7 Structured
Documents are referenced
within the Instance.
> Referenced (0008,1150) 1 Unique identifier for the class of *** not *** not
SOP Class UID HL7 Structured Document. supported supported
*** ***
> Referenced (0008,1155) 1 Unique identifier for the HL7 *** not *** not
SOP Instance Structured Document as used supported supported
UID in DICOM instance references. *** ***
> HL7 Instance (0040,E001) 1 Instance Identifier of the *** not *** not
Identifier referenced HL7 Structured supported supported
Document, encoded as a UID *** ***
(OID or UUID), concatenated
with a caret ("^") and Extension
value (if Extension is present in
Instance Identifier).
> Retrieve URI (0040,E010) 3 Retrieval access path to HL7 *** not *** not
Structured Document. Includes supported supported
fully specified scheme, *** ***
authority, path, and query in
accordance with RFC 2396

C.2.16 Extended Interface – Private

Attribute Name Tag Type Attribute Description TrueBeam 4DITC

4.0 v13.0

Extended (3253,XX02) 1 Identifier string defining format Roundtrip Roundtrip

Interface Format of Extended Interface Data supported supported
(3253,xx00). Applications
should be able to
unambiguously map this string
to an XML schema definition.
Extended (3253,XX00) 1 Contains private extensions as Roundtrip Roundtrip
Interface Data an XML stream. Schema of supported supported
XML is defined by Extended
Interface Format (3253,xx02).

142 of 151 Varian Treatment Delivery

Console
 IOD Details, Extended Interface – Private
Attribute Name Tag Type Attribute Description TrueBeam 4DITC
4.0 v13.0

Extended (3253,XX01) 1 Length of XML stream Roundtrip Roundtrip

Interface Length contained in Extended Interface supported supported
Data (3253,xx00). Usually is
equal to attribute length of
Extended Interface Data
(3253,xx00) if length is even
and is one less than attribute
length if length is odd.

Treatment Delivery Console 143 of 151

 Extended Interface
The following IODs have private Attributes containing an XML data structure for
transporting structured non-DICOM data:
• RT Plan
• RT Beams Treatment Record
The following sections specify Attributes containing the XML data and describe the
structure of the XML data.

D.1 RT Plan
The XML data structure for RT Plan IODs is contained in private Extended Interface
Module which is optional within RT Plan IOD.
The structure of the XML data structure is described in the following table.
Column “Operational Mode” indicates the presence for certain XML nodes depending of
the applications Operational Mode.
Legend for column “Operational Mode”:
✓ Attribute supported
 Attribute not supported
1) Present for Block, Compensator and empty Trays
1)* Present for empty Trays
Attributes not supported anymore in the Extended Interface XML data are covered by
standard DICOM attributes.
 Extended Interface, Extended Interface – Private

Node Name Occurrence Data Node Description Operational

Type Mode

VMS Console System

VMS Console System

Min Max

8.8 / QA
6.5
ExtendedVAPlanInterface 0 1 ✓ ✓

> Beams 0 1 ✓ ✓

>> Beam 0 ∞ ✓ ✓

>>> ReferencedBeamNumber 1 1 int Beam identifier ✓ ✓

>>> BeamExtension 1 1 Additional items provided from Vision to ✓ ✓

expand the features of RT Beams.
>>>> FieldType 1 1 string TREATMENT or SETUP ✓ 

>>>> RelatedTreatBeamNumber 0 1 int Relation from the image beams to the ✓ ✓

treatment and/or setup beams.
>>>> FieldOrder 1 1 int Order in which the fields are shown ✓ ✓

>>>> GantryRtnExtendedStart 0 1 int When true, gantry angle position is in the ✓ ✓

extended range, which means it has an over
travel (a Gantry can move most typical 400'
and not only 360').
>>>> GantryRtnExtendedStop 0 1 int When true, gantry angle position is in the ✓ ✓
extended range, which means it has an over
travel (a Gantry can move most typical 400'
and not only 360').
>>>> MUSubtraction 0 1 int Although the extended interface contains the ✓ ✓
MUSubstraction attribute, it is not used in
TXA.
>>>> FieldSetupPhotos 0 1 ✓ ✓

>>>>> FieldSetupPhoto 0 2 Two setup photos max ✓ ✓

>>>>>> SetupPhotoNumber 1 1 int Increasing number of setup photos. The ✓ ✓
value has to start from 1 and up.
>>>>>> SetupPhotoFormat 1 1 string The format of the pixel information. ✓ ✓
Supported values are 'JPG' and 'BMP'
>>>>>> SetupPhotoPicture 1 1 hex Pixel information of the photo in the ✓ ✓
binary corresponding format.
>>>>>> PhotoModified 1 1 string Photo has been modified. ✓ ✓
PhotoModified may have ‘true’ or ‘false’
>>>> CustomAddOns 0 1 ✓ 

>>>>> CustomAddOn 0 4 1) 
>>>>>> CustomAddOnType 1 1 string Three Add On Type to choose from: 1) 
BLOCK
COMPENSATOR
TRAY
>>>>>> CustomCode 0 1 int Codes for accessory which may be custom 1) 
made or factory made (in that case the

146 of 151 DICOM Conformance Statement

 Extended Interface, Extended Interface – Private

Node Name Occurrence Data Node Description Operational

Type Mode

VMS Console System

VMS Console System

Min Max

8.8 / QA
6.5
internal code in equal the custom code.)
>>>>>> ReferencedAddOnNumber 0 1 int Reference to the identification number of the 1) 
Block or Compensator.
>>>>>> TraySpecification 0 1 In case the CustomAddOn is a tray, it gets 1)* 
reported back through this node
>>>>>>> TrayID 1 1 string User-supplied identifier for tray. Max length 1)* 
is 16 characters.
>>>>>>> SourceTrayDistance 0 1 int The distance from source to slot. This 1)* 
information is needed to distinguish the slot
> ToleranceTables 0 1 ✓ ✓

>> ToleranceTable 0 ∞ Additional items provided from Vision to ✓ ✓

expand the features of Tolerance Tables with
AutoSetup capabilities
>>> 1 1 int Refers to the tolerance table in RT Tolerance ✓ ✓
ReferencedToleranceTableNumber Table module
>>> ToleranceTableExtension 1 1 ✓ ✓

>>>> GantryRtnSetup 0 1 string Setup attributes may have following type: ✓ ✓

Automatic
Manual
Remote
>>>> CollRtnSetup 0 1 string ✓ ✓

>>>> CollXSetup 0 1 string ✓ ✓

>>>> CollYSetup 0 1 string ✓ ✓

>>>> PatientSupportAngleSetup 0 1 string ✓ ✓

>>>> CouchLngSetup 0 1 string ✓ ✓

>>>> CouchVrtSetup 0 1 string ✓ ✓

>>>> CouchLatSetup 0 1 string ✓ ✓

>>>> TableTopEccentricAngleSetup 0 1 string ✓ ✓

> DoseReferences 0 1 ✓ ✓

>> DoseReference 0 ∞ ✓ ✓

>>> 1 1 int Reference to the identification number of the ✓ ✓

ReferencedDoseReferenceNumber Dose Reference (300A,0012) in the RT
Prescription module which is a
representation of our reference point
>>> DoseReferenceExtension 1 1 Additional items provided from Vision to ✓ ✓
expand the features of reference points.
>>>> DailyDoseLimit 0 1 decimal Unit is [Gy] ✓ ✓

>>>> SessionDoseLimit 0 1 decimal Unit is [Gy] ✓ ✓

>>>> Breakpoints 0 1 ✓ ✓

Varian Treatment Delivery Console 147

 Extended Interface, Extended Interface – Private

Node Name Occurrence Data Node Description Operational

Type Mode

VMS Console System

VMS Console System

Min Max

8.8 / QA
6.5
>>>>> Breakpoint 0 ∞ Breakpoint extension since DICOM has just ✓ ✓
one DeliveryWarningDose without a
description.
>>>>>> BreakpointDose 1 1 decimal Unit is [Gy] ✓ ✓
>>>>>> BreakpointWarning 1 1 string Text which describes the breakpoint. Max ✓ ✓
length is 254 characters

Table 27: RT Plan Extended Interface XML Structure

D.2 RT Beams Treatment Record

The XML data structure for RT Beams Session Record IOD is contained in RT Beams
Session Record Module in private Treatment Session Beam Data Attribute with tag
(3261,102A).
The structure of the XML data structure is described in the following table.
Column “Operational Mode” indicates the presence for certain XML nodes depending of
the applications Operational Mode
Legend for column “Operational Mode”:
✓ Attribute supported
 Attribute not supported
Attributes not supported anymore in the Extended Interface XML data are covered by
standard DICOM attributes.

Node Name Occurrence Data Node Description Operational

Type Mode
VMS Console System

VMS Console System

Min Max
8.8 / QA
6.5

RTBeamSessionRecordExtendedIF 0 1 ✓ ✓
> DoseOverrides 0 1 ✓ ✓

>> DoseOverride 0 ∞ There may be as many DoseOverride nodes ✓ ✓

as Reference Points.
>>> DoseOverrideType 1 1 string Type of dose overrides. Supported are: ✓ ✓
BREAKPOINT: Breakpoint dose limit
overridden

148 of 151 DICOM Conformance Statement

 Extended Interface, Extended Interface – Private

Node Name Occurrence Data Node Description Operational

Type Mode

VMS Console System

VMS Console System

Min Max

8.8 / QA
6.5
DAILYDOSE: Daily dose limit overridden
SESSIONDOSE: Session dose limit
overridden
TOTALDOSE:
>>> Dose 0 1 decimal Contains the specific overridden/authorized ✓ ✓
dose for DoseOverrideType ‘BREAKPOINT’
at the Reference Point referenced by Dose
Reference Number. Unit is [Gy]
>>> DoseReferenceNumber 1 1 non- References the Reference Point on which ✓ ✓
negative the dose was applied.
int
>>> OperatorsName 1 1 Operator Name who overrode/approved the ✓ ✓
specific doses.
>>>> FamilyName 0 1 string Max length is 64 characters. ✓ ✓

>>>> GivenName 0 1 string Max length is 64 characters ✓ ✓

>>>> MiddleName 0 1 string Max length is 64 characters ✓ ✓

>>>> Prefix 0 1 string Max length is 64 characters ✓ ✓

>>>> Suffix 0 1 string Max length is 64 characters ✓ ✓

> TraySpecifications 0 1 ✓ 

>> TraySpecification 1 ∞ As many nodes as tray applied for the ✓ 

treated beam.
>>> TrayID 1 1 string That's the parameter which needs to be ✓ 
defined when a tray is defined/acquired. Max
length is 16 characters
>>> SourceTrayDistance 0 1 int Radiation Source to attachment edge of tray ✓ 
assembly (mm).
> AdditionalOperators 0 1 ✓ ✓

>> OperatorsName 1 2 If the ‘Show Sign Off Dialog’ is checked in ✓ ✓

ITAdmin -> MachineConfiguration ->
Preferences, the Sign Off Dialog will be
shown after closing the patient. Three
OperatorsName may be entered in this
dialog. The first OperatorsName will be sent
through the standard attribute Operator
Name (0008,1070) in the RT Beams Session
Record module, the remaining two names if
available will be sent here in the Extended
Interface
>>> FamilyName 0 1 string Max length is 64 characters. ✓ ✓

>>> GivenName 0 1 string Max length is 64 characters ✓ ✓

>>> MiddleName 0 1 string Max length is 64 characters ✓ ✓

>>> Prefix 0 1 string Max length is 64 characters ✓ ✓

>>> Suffix 0 1 string Max length is 64 characters ✓ ✓

Varian Treatment Delivery Console 149

 Extended Interface, Extended Interface – Private

Table 28: RT Beams Treatment Record Extended Interface XML Structure

150 of 151 DICOM Conformance Statement

 Extended Interface, Extended Interface – Private

Varian Treatment Delivery Console 151