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

Health Harmony
Health Harmony 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: Health Harmony is a telehealth remote care management platform. This remote care system uses peripheral Hub devices chosen by the users which connect to the platform to collect vital health data. These Hub devices include a digital weight scale, blood pressure monitors, thermometers, pulse oximeters, pedometers, stethoscopes, and spirometers. Also, this platform transmits the user`s health data to clinicians and caregivers and provides educational content and other information services.

This technology provides a web viewer portal for clinicians to access data from the tablets running Health Harmony Mobile. The software is capable of storing and retrieving patient identification information in accordance with Health Level-7 (HL7). The system is able to record and store patient information simultaneously by an Integration Control Number (ICN) and a Social Security Number (SSN). Patient information is retrievable by both ICN and SSN.

This technology uses a Microsoft Structured Query Language (SQL) Server Database and a Redis Database to store data. No patient data is stored on the hub device since a Plain Old Telephone System (POTS) modem bridge is used for the tablet. Data is encrypted at rest on the tablet and the server using 140-2 validated ciphers. In other words, the application data is encrypted on the file system, and the physical storage is also encrypted at the block level. Data exchanged between tablet and server is only transported over 140-2 validated Transport Layer Security (TLS), regardless if being transmitted over cellular, Wi-Fi, or a POTS hub device.

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:
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 v19.4
Decision Date: 04/09/2019 at 21:30:07 UTC
Introduced By: TRM Request
Vendor Name: Care Innovations, LLC.
- The information contained on this page is accurate as of the Decision Date (04/09/2019 at 21:30:07 UTC).