United States Department of Veterans Affairs
One-VA Technical Reference Model v15.9
Clinical Video Teleconference (CVT) Into the Home
Clinical Video Teleconference (CVT) Into the Home Technology

General InformationClick for 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: Clinical Video Teleconference (CVT) Into the Home (CVTH - previously called Video Anywhere) is a custom video teleconference solution that allows patients to participate in video appointments from their home with a VA clinician. The solution is comprised of Cisco hardware and software components and custom Iron Bow applications running on two Microsoft Hyper-V virtual machine (VM) Internet Information Services (IIS) systems. The custom Iron Bow middleware applications include:

Scheduling Web Application: VA personnel approved for scheduler access log into this site to create new appointments or to view/edit existing appointments. Creating a new appointment results in an email sent to the patient with a link to confirm the meeting and instructions for retrieving temporary credentials. The email also provides instructions regarding how to launch the Jabber client and how to use the username and password from the confirmation page to log into Jabber at the time of the meeting. Providers receive a copy of the patient appointment email for verification.

Software Download Web Application: The patient appointment email contains a link to this site with instructions for downloading the Windows or Mac Jabber client.

Confirmation Web Application: The patient appointment email contains a link to this site with instructions for confirming the appointment and receiving their temporary credentials.

Service Middleware Application (VidAnySrvc.exe): Sends out a copy of the reservation email the day before the meeting as a reminder. The service also accesses a proxy IIS app on the Cisco TelePresence Management Suite (TMS) server to create a temporary account in TMS for the patient the morning of the meeting, and then removes it after the meeting. The account is currently valid from midnight to midnight on the appointment day.

Proxy Application: This application runs on the TMS server and uses TMS API calls to add/remove the temporary patient accounts to the TMS server to permit the scheduled video conferences.
Section 508 Information:
Decision: View Decisions
Decision Constraints: As of April 23, 2015, per the Deputy CIO of Architecture, Strategy and Design (ASD), all technologies in use by the VA require an assessment by the VA Section 508 office. Section 508 of the Rehabilitation Act Amendments of 1998 is a federal law that sets the guidelines for technology accessibility. A VA Section 508 assessment of this technology has not been completed at the time of publication. Therefore, as of April 23, 2015 only users of this technology who have deployed the technology to the production environment, or have project design and implementation plans approved, may continue to operate this technology. In the case of a project that has implemented, or been approved for a specific site or number of users, and that project needs to expand operations to other sites or to an increased user base, it may do so as long as the project stays on the existing version of the technology that was approved or implemented as of April 22, 2015. Use of this technology in all other cases is prohibited.

Solution components must remain patched and operated in accordance with Federal and Department security and privacy policies and guidelines to mitigate any current and future vulnerabilities. Please see additional constraints for the following solution components: Microsoft .NET Framework, Microsoft SQL Server and Cisco TelePresence Movi/Jabber.

Decision Source: TRM Mgmt Group
Decision Process: One-VA TRM v14.10
Decision Date: 10/31/2014
Introduced By: TRM Request
Vendor Name: Iron Bow Technologies
- The information contained on this page is accurate as of the Decision Date (10/31/2014).
Reviewed/Updated Date: Thursday, September 03, 2015