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 20.8

Medicom Imagex Service
Medicom Imagex Service 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: Medicom Imagex Service is a technology intended for use by radiology and other medical practices to transfer imaging studies across the Internet. Medicom is designed to improve the way patient information is exchanged by creating a peer-to-peer communication network for physicians, radiologists, radiology technologists, and medical records staff.

This technology is hosted on VA premises as well as through Amazon Web Services (AWS). The Medicom Imagex Service is an executable file (.exe) that must be downloaded and installed on VA network in order to interface with the Veterans Health Information Systems and Technology Architecture (VistA) Importer and Picture Archiving and Communication System (PACS). It can be downloaded on the VistA Importer Workstations or on a separate centralized Virtual Machine on the network.

The only system handling patient-specific information is located on VA premises; all other access points related to the software are for administrative purposes. All Protected Health Information (PHI) flows through the software running on VA premises. There are no databases or storage associated with this flow of information, and therefore this information is never saved or stored. The only information recorded is an audit trail, which is encrypted with a Rivest-Shamir-Adleman (RSA) key and accessible only to VA Information Technology (IT) administrators.

The servers that load the content for the webpages are hosted through Amazon Web Services (AWS). Medicom uses the AWS cloud in order to maintain audit logs for application entry, in addition to application activity. This cloud deployment is used to verify the authenticity of requests for image transfers/pushes through the network, and to serve the webpage available to site administrators. It is not used for handling, storing, or copying patient-specific information.

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: https://dvagov.sharepoint.com/sites/OITEPMOECSO
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 Section508@va.gov.
Decision: View Decisions

Decision Source: TRM Mgmt Group
Decision Process: One-VA TRM v20.8
Decision Date: 08/13/2020
Aliases: Medicom; Medicom Windows Service
Introduced By: TRM Request
Vendor Name: Medicom
- The information contained on this page is accurate as of the Decision Date (08/13/2020).