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

ProFuse 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: ProFuse is a software application that is intended to be used as an image viewer of multi-modality, digital images, including ultrasound, computed tomography (CT), magnetic resonance (MR), and positron emission tomography (PET). This technology is used by physicians for two-dimensional (2D) and three-dimensional (3D) visualization, image registration, and fusion of MR images in conjunction with ultrasound images for mapping and planning.

This technology communicates with the local Picture Archiving and Communication System (PACS) and has the ability to query and pull from PACS, as well as push processed Digital Imaging and Communications in Medicine (DICOM) data back to PACS. ProFuse can also receive data from other DICOM-compliant software. For example, data can be pushed into ProFuse from an MR scanner.

At the time of writing, ProFuse utilizes a Maria Database (MariaDB) Server. The database parses the DICOM files downloaded from PACS, which have a combination of Protected Health Information (PHI) and certain DICOM information as the attributes. The DICOM files that are retrieved from PACS are then stored separately on a file server and pointers to those files are stored as an attribute in the database. Additionally, this technology allows for data to be stored in the cloud (Microsoft Azure).

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 on VMs within VA-controlled cloud environments (e.g. VA Enterprise Cloud (VAEC)). Cloud services provided by the VAEC 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:

Please note that there is no dedicated webpage for this product.
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.3
Decision Date: 03/12/2019 at 19:53:03 UTC
Aliases: ProFuse CAD
Introduced By: TRM Request
Vendor Name: Eigen
- The information contained on this page is accurate as of the Decision Date (03/12/2019 at 19:53:03 UTC).