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

VSee Messenger
VSee Messenger 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: VSee Messenger is a telehealth application that provides live streaming of high definition (HD) video, text chat, document-sharing, and peripheral image sharing via Universal Serial Bus (USB) using the internet or Third Generation (3G)/Fourth Generation (4G) mobile communications. This software is available as desktop software and as a mobile application. Additionally, by default VSee Messenger transmits data via User Datagram Protocol (UDP), Hypertext Transfer Protocol (HTTP), or Secure Sockets Layer (SSL) to the Amazon S3 Cloud for storage, however an option exists to install and use private servers within the VA.

All VSee Messenger traffic is encrypted with Federal Information Processing Standard (FIPS) 140-2 certified 256 bit Advanced Encryption Standard (AES). This technology allows users to record videoconferences and keeps chat history. These files are stored locally on a user`s computer and are not accessible to VSee Messenger, though users have the ability to save recorded conferences or chat histories to Electronic Health Record (EHRs) systems. Also, please note that VSee Messenger does not store any data while in streaming mode. However, this technology has the ability to store data in a Microsoft Structured Query Language (SQL) Server database while in `Store and Forward` mode.

This technology is available in three editions: Basic Messenger, Pro Messenger, and Peripheral Streaming. This entry covers all three.

This entry covers the Desktop Edition of this technology and not any mobile versions. Please note that the implementation of mobile technology applications that operate on Mobile Operating Systems must be reviewed and approved by the Mobile Technology and Endpoint Security Engineering Team:

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 v20.8
Decision Date: 08/03/2020 at 21:15:24 UTC
Aliases: VSee
Introduced By: TRM Request
Vendor Name: VSee
- The information contained on this page is accurate as of the Decision Date (08/03/2020 at 21:15:24 UTC).