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

HeartFlow Connect
HeartFlow Connect 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: HeartFlow Connect is a FFRCT Analysis software that allows providers to perform an advanced test that assesses coronary artery disease. From any modality, such as a computerized tomography (CT) scanner or picture archiving and communication system (PACS)/Workstation, users are able to perform a Digital Imaging and Communications in Medicine (DICOM) push to the HeartFlow Connect Appliance (a VMWare Virtual Appliance) in order to send the data to the HeartFlow Services web application firewall where all data is analyzed in the HeartFlow Network (which is either AWS Cloud or a Virtual Private Cloud). After the analysis a Portable Document Format (PDF) is generated with the results which will be pushed to the clinical web application where providers can access it. Ultimately, the analysis provides a patient and vessel specific interactive three-dimensional (3D) model and a color-coded map of coronary arteries, showing the extent to which any blockages impair blood flow.

This product does not utilize a database to store data.

Please note that there is no specific product page for this technology and thus the vendor webpage is used in its place.

This technology is deployed via Virtual Local Area Network (VLAN). A Virtual Appliance is installed on the local VA network in order to allow data to be sent out to HeartFlow Services to be analyzed. The server is a gateway and has no persistent data on it.

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. 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 v22.9
Decision Date: 09/08/2022 at 21:00:46 UTC
Introduced By: TRM Request
Vendor Name: HeartFlow
- The information contained on this page is accurate as of the Decision Date (09/08/2022 at 21:00:46 UTC).