Locator

Contact

Locator

Vet Centers

Regional Benefits Offices

Regional Loan Centers

Cemetery Locations

VA Technical Reference Model v 24.7

Aria Oncology Information System (OIS)

General Information

Technologies must be operated and maintained in accordance with Federal and Department security and privacy policies and guidelines. More information on the proper use of the TRM can be found on the TRM Proper Use Tab/Section.

Website:	Go to site
Description:	Aria Oncology Information System (OIS) is a comprehensive treatment record verification and image management system that aggregates patient data into a single, organized, oncology-specific Electronic Medical Record (EMR). This technology enables users to digitize paper charts and oversee all aspects of oncology patients. Aria OIS combines radiology, medical, and surgical information that supports the patient treatment stages, from initial diagnosis through post-treatment follow-up. Additionally, Aria OIS provides access to patient schedules, prescriptions, laboratory results, and toxicity profiles to assist healthcare providers in assessing a patient`s response to treatment, and uses this information to inform future treatment decisions. This product uses the Varian System Database to store data, which is a Microsoft Structured Query Language (SQL) Server database. A Health Level Seven (HL7) interface is used to transfer data between the System Database and other third party systems. Also, Aria OIS has the ability to save data to local hard drives, online storage devices, or Digital Imaging and Communications in Medicine (DICOM)-compliant Picture Archiving and Communication Systems (PACS).
Technology/Standard Usage Requirements:	Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.
Section 508 Information:	This technology has not been assessed by the Section 508 Office. The Implementer of this technology has the responsibility to ensure the version deployed is 508-compliant. Section 508 compliance may be reviewed by the Section 508 Office and appropriate remedial action required if necessary. For additional information or assistance regarding Section 508, please contact the Section 508 Office at Section508@va.gov.
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v24.5
Decision Date:	05/24/2024 at 16:48:47 UTC
Aliases:	Varian OIS
Introduced By:	TRM Request
Vendor Name:	Varian Medical Systems

Vendor Release Information

The Vendor Release table provides the known releases for the TRM Technology, obtained from the vendor (or from the release source).

Version	Release Date	Vendor End of Life Date	Vendor Desupport Date
10	07/18/2010
11	02/12/2012
12
13	09/01/2013
13.6	10/09/2015
13.7	06/23/2016
15.x	06/12/2017
16.x	06/01/2020
17.x	03/01/2022
18.x	08/01/2023

Current Decision Matrix (05/21/2024)

Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.

The VA Decision Matrix displays the current and future VA IT position regarding different releases of a TRM entry. These decisions are based upon the best information available as of the most current date. The consumer of this information has the responsibility to consult the organizations responsible for the desktop, testing, and/or production environments to ensure that the target version of the technology will be supported. Any major.minor version that is not listed in the VA Decision Matrix is considered unapproved for use.

Legend:

White	Approved: The technology/standard has been approved for use.
Yellow	Approved w/Constraints: The technology/standard can be used within the specified constraints located below the decision matrix in the footnote[1] and on the General tab.
Gray	Unapproved: This technology or standard can be used only if a POA&M review is conducted and signed by the Authorizing Official Designated Representative (AODR) as designated by the Authorizing Official (AO) or designee and based upon a recommendation from the POA&M Compliance Enforcement, has been granted to the project team or organization that wishes to use the technology.
Orange	Divest: VA has decided to divest itself on the use of the technology/standard. As a result, all projects currently utilizing the technology/standard must plan to eliminate their use of the technology/standard. Additional information on when the entry is projected to become unapproved may be found on the Decision tab for the specific entry.
Black	Prohibited: The technology/standard is not (currently) permitted to be used under any circumstances.
Blue	Planning/Evaluation Constraint:The period of time this technology is currently being evaluated, reviewed, and tested in controlled environments. Use of this technology is strictly controlled and not available for use within the general population. If a customer would like to use this technology, please work with your local or Regional OI&T office and contact the appropriate evaluation office displayed in the notes below the decision matrix. The Local or Regional OI&T office should submit an inquiry to the TRM if they require further assistance or if the evaluating office is not listed in the notes below.

Release/Version Information:

VA decisions for specific versions may include a ‘.x’ wildcard, which denotes a decision that pertains to a range of multiple versions.

For example, a technology approved with a decision for 7.x would cover any version of 7.(Anything) - 7.(Anything). However, a 7.4.x decision would cover any version of 7.4.(Anything), but would not cover any version of 7.5.x or 7.6.x on the TRM.

VA decisions for specific versions may include ‘+’ symbols; which denotes that the decision for the version specified also includes versions greater than what is specified but is not to exceed or affect previous decimal places.

For example, a technology approved with a decision for 12.6.4+ would cover any version that is greater than 12.6.4, but would not exceed the .6 decimal ie: 12.6.401 is ok, 12.6.5 is ok, 12.6.9 is ok, however 12.7.0 or 13.0 is not.

<Past

CY2023

CY2024

CY2025

Future>

Release

Unapproved

13.6

Unapproved

13.7

Divest
[5, 14, 15, 16]

Unapproved

Divest
[5, 16, 17, 18]

Divest
[5, 17, 18, 19]

Divest
[5, 18, 19, 20, 21]

Unapproved

15.x

Approved w/Constraints
[5, 14, 15, 16]

Approved w/Constraints
[5, 16, 17, 18]

Approved w/Constraints
[5, 17, 18, 19]

Approved w/Constraints
[5, 18, 19, 20, 21]

Divest
[5, 18, 19, 20, 21]

16.x

Approved w/Constraints
[5, 14, 15, 16]

Approved w/Constraints
[5, 16, 17, 18]

Approved w/Constraints
[5, 17, 18, 19]

Approved w/Constraints
[5, 18, 19, 20, 21]

Divest
[5, 18, 19, 20, 21]

17.x

Divest
[5, 14, 15, 16]

Unapproved

Approved w/Constraints
[5, 16, 17, 18]

Approved w/Constraints
[5, 17, 18, 19]

Approved w/Constraints
[5, 18, 19, 20, 21]

Decision Constraints


[1]	Veterans Affairs (VA) clinical offices must ensure that VA sensitive data is properly protected in accordance to VA Handbook 6500, Federal Information Security Management Act (FISMA), and Federal Information Processing Standard (FIPS) 140-2 compliant.

[2]	Veterans Affairs (VA) users must ensure VA sensitive data is protected properly in accordance with VA Handbook 6500 and the Federal Information Security Management Act (FISMA). Per VA Handbook 6500, Federal Information Processing Standard (FIPS) 140-2 certified encryption must be used to protect and encrypt data in transit and at rest if Personally Identifiable Information/Protected Health Information/VA (PII/PHI/VA) sensitive information is involved. If FIPS 140-2 certified encryption in not used, additional mitigating controls must be documented in an approved System Security Plan (SSP). In addition, the technology must be implemented within the VA production network (not in a Demilitarized Zone (DMZ)), unless the specific uses and instances of the technology are approved by the Enterprise Security Change Control Board (ESCCB). All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. In cases where the technology is used for external connections, a full ESCCB review is required in accordance VA Directive 6004, VA Directive 6517 and VA Directive 6513.

[3]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

[4]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP).

[5]	Technology must remain patched and operated in accordance with Federal and Department security policies and guidelines in order to mitigate known and future security vulnerabilities.

[6]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP).

[7]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

[8]	Users must ensure that Microsoft Structured Query Language (SQL) Server, Microsoft Internet Explorer (IE), and Microsoft .NET Framework are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)

[9]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

[10]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP).

[11]	Users must ensure that Microsoft Structured Query Language (SQL) Server, Microsoft Internet Explorer (IE), and Microsoft .NET Framework are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) This technology can only use the TRM approved version(s) of Citrix Virtual Apps and Desktops.

[12]	Users must ensure that Microsoft Structured Query Language (SQL) Server, Microsoft Internet Explorer (IE), Microsoft Outlook, Microsoft .NET Framework, Adobe Acrobat, Google Chrome, and Firefox are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) This technology can only use the TRM approved version(s) of Citrix Virtual Apps and Desktops. This technology requires using a Universal Service Bus (USB) technology to transfer data into the records. As such, proper precautions need to be taken to protect data. Users must Divest the use of Internet Explorer with this technology. Other approved internet browsers are available. See Category Tab for details.

[13]	Users must ensure that Microsoft Structured Query Language (SQL) Server, Microsoft Outlook, Microsoft .NET Framework, Adobe Acrobat, Google Chrome, and Firefox are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) This technology can only use the TRM approved version(s) of Citrix Virtual Apps and Desktops. This technology requires using a Universal Service Bus (USB) technology to transfer data into the records. As such, proper precautions need to be taken to protect data. Users must utilize approved internet browsers, as Microsoft Internet Explorer has reached End of Life status. See Category Tab for details.

[14]	Users must ensure that Microsoft Structured Query Language (SQL) Server is implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) This technology can only use the TRM approved version(s) of Citrix Virtual Apps and Desktops. This technology requires using a Universal Service Bus (USB) technology to transfer data into the records. As such, proper precautions need to be taken to protect data. Users must utilize approved internet browsers, as Microsoft Internet Explorer has reached End of Life status. See Category Tab for details.

[15]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISSO (Information System Security Officer) to ensure compliance with VA Handbook 6500.

[16]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information System Security Officer (ISSO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP).

[17]	Users must ensure that Firefox, Google Chrome, Microsoft Internet Information Services (IIS), Microsoft Edge, and Microsoft Structured Query Language (SQL) Server is implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) This technology can only use the TRM approved version(s) of Citrix Virtual Apps and Desktops. This technology requires using a Universal Service Bus (USB) technology to transfer data into the records. As such, proper precautions need to be taken to protect data. Users must utilize approved internet browsers, as Microsoft Internet Explorer has reached End of Life status. See Category Tab for details.

[18]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISSO (Information System Security Officer) to ensure compliance with both VA Handbook 6500 and VA Directive 6500.

[19]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 or its successor to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 or 140-3 compliant full disk encryption (FOE) must be implemented on the storage device where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information System Security Officer (ISSO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP). By September 22, 2026, all FIPS 140-2 certificate validations will be placed on the Historical List, please refer to FIPS Transition Effort for further guidance and timeline of changes.

[20]	Users must ensure that Google Chrome, Microsoft Internet Information Services (IIS), Microsoft Edge, Microsoft Word, Citrix Virtual Apps and Desktops (CVAD), and Microsoft Structured Query Language (SQL) Server is implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) This technology requires using a Universal Service Bus (USB) technology to transfer data into the records. As such, proper precautions need to be taken to protect data.

[21]	The Federal Information Processing standards (FIPS) 140-2 certification status of this technology was not able to be verified. This technology will require a 3rd party FIPS 140-2 or 140-3 certified solution for any data containing PHI/PII or VA sensitive information, where applicable. More information regarding the Cryptographic Module Validation Program (CMVP) can be found on the NIST website.

Note:

At the time of writing, version 18.0 is the most current version, released 08/01/2023.

The following reference(s) are associated with this entry:
Type	Name	Source	Description
*NOTE: Vendor provided information is subject to the accuracy of the manufacturer.

Note: This list may not be complete. No component, listed or unlisted, may be used outside of the technology in which it is released. The usage decision for a component is found in the Decision and Decision Constraints.
Name	Description
Aria Connect	Aria Connect is a Health Level Seven (HL7) interface that will replace the Interface Exchange Manager (IEM) in future versions of this product. It is designed to transfer data between the Varian System Database and third party systems in HL7 format. Both Aria Connect and IEM are actively supported at the time of writing.
Aria Unified Reporting Application (AURA)	This application queries the data warehouse for data analysis and report generation.
Docs2EHR	Docs2EHR can manage incoming faxes, scanned documents, and files in various formats such as images or PDFs. The software utilizes the Varian Document Services API, which imports documents into ARIA without interfering with the clinic’s ARIA database.
Interface Exchange Manager (IEM)	IEM exchanges patient centric messages with hospital information systems and other Health Level Seven (HL7) -compliant systems.


Collaboration and Electronic Workplace Productivity Software	Health Care
Health Care Administrative	Health Delivery Support
Health Care Health Services	Radiation Oncology

- The information contained on this page is accurate as of the Decision Date (05/24/2024 at 16:48:47 UTC).

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (05/21/2024)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (05/21/2024)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

EMAIL UPDATES