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 23.5

LibreView 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: LibreView is an installable client that communicates with the cloud-based diabetes management system. This is intended for use by individuals to aid in the review, analysis, and evaluation of historical glucose data, glucose test results, and ketone test results to support an effective diabetes health management program. The software enables patients to upload glucose data from a glucose monitor and then share that data with their clinician.

LibreView runs on Amazon Web Services` (AWS) cloud services. The device drivers reside on the network but data resides on the cloud and is accessed via a web browser. The product utilizes AWS Elastic Block Store (EBS) and Simple Storage Service (S3) storage for application data, log data, backups, and database storage. LibreView uses encrypted volumes (Advanced Encryption Standard-256) for all sensitive Protected Health Information (PHI) and Personally Identifiable Information (PII) data, with each type of data utilizing a different encryption key. All data communication between a user`s web browser, mobile application, partner application, or other service interaction with the platform is encrypted using the HyperText Transfer Protocol Secure (HTTPS) protocol and Federal Information Processing Standards (FIPS)-certified Transport Layer Security (TLS) ciphers using Secure Sockets Layer (SSL) certificates.

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:

This entry covers the Desktop Edition of this technology and not any mobile versions. See Category tab/Comparable for the corresponding Mobile entry. Note: 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 been assessed by the Section 508 Office and found non-conformant. 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 Please see reference tab for more information concerning product versions.
Decision: View Decisions

Decision Source: TRM Mgmt Group
Decision Process: One-VA TRM v23.5
Decision Date: 05/01/2023
Introduced By: TRM Request
Vendor Name: Abbott Diabetes Care
- The information contained on this page is accurate as of the Decision Date (05/01/2023).