Attention A T users. To access the menus on this page please perform the following steps. 1. Please switch auto forms mode to off. 2. Hit enter to expand a main menu option (Health, Benefits, etc). 3. To enter and activate the submenu links, hit the down arrow. You will now be able to tab or arrow up or down through the submenu options to access/activate the submenu links.

VA Technical Reference Model v 24.4

Channels Technology

General InformationGeneral Information help

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: Channels is an extensible framework used to define and optimize specialized health and social care programs, leveraging real-time data to standardize workflows, guide user actions, and improve outcomes. This technology automates the enrollment of a Veteran in programs such as COVID-19 screening, suicide prevention, fall risk management, social determinants of health evaluation, and other Veteran health and social care programs. Channels users are guided in assessing and addressing the Veteran’s needs, providing educational materials, reviewing empirical data, making service referrals, and following up with the Veteran after service visits are performed. Additionally, through customizable dashboards, program leaders may ascertain overall program effectiveness based on key metrics such as team performance, task status, and resulting outcome.

Channels is a thin client application that runs in any VA-supported web browser and is a natural extension of the Data Integration and Federation Enterprise Platform (VDIF-EP). This technology uses real-time content from integrating with Veterans Health Information Systems and Technology Architecture (VistA), by way of VDIF.

Channels requires the use of a relational database for storing Veteran case data. By default, Channels uses Amazon Relational Database Service (RDS), which is a cloud-hosted instance of PostgreSQL in Amazon Web Services (AWS) Government Cloud (GovCloud). Optionally, InterSystems Caché or another Java Database Connectivity (JDBC)-enabled database can be used as an alternative to Relational Database Service (RDS). Data is encrypted using the Advanced Encryption Standards (AES) algorithm as specified by Federal Information Processing Standards Publications (FIPS)- 197.

The TRM decisions in this entry only apply to technologies and versions owned, operated, managed, patched, and version-controlled by VA. This includes technologies deployed as software installations on VMs within VA-controlled cloud environments (e.g. VA Enterprise Cloud (VAEC)). Cloud services provided by the VAEC, which are listed in the VAEC Service Catalog, and those controlled and managed by an external Cloud Service Provider (i.e. SaaS) are not in the purview of the TRM. For more information on the use of cloud services and cloud-based products within VA, including VA private clouds, please see the Enterprise Cloud Solutions Office (ECSO) Portal at:
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
Decision: View Decisions

Decision Source: TRM Mgmt Group
Decision Process: One-VA TRM v24.4
Decision Date: 04/11/2024 at 15:53:29 UTC
Aliases: Channels360
Introduced By: TRM Request
Vendor Name: Ready Computing
- The information contained on this page is accurate as of the Decision Date (04/11/2024 at 15:53:29 UTC).