Change Healthcare Radiology Solution

General Information

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:	Change Healthcare Radiology Solution is a Picture Archiving and Communication System (PACS). This technology stores, transmits, manages, and displays medical images for clinicians and clinical staff. Additionally, this technology enables users to visualize and analyze diagnostic images based on the user`s specialty. This technology allows users to access patient images from both their mobile devices, as well as a desktop client. Change Healthcare Radiology Solution utilizes an Oracle Database to store data. McKesson Radiology was rebranded to Change Healthcare Radiology Solution as of July 10, 2018. 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: http://vaww.eie.va.gov/SysDesign/CS/MT/default.aspx
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 v23.2
Decision Date:	02/21/2023 at 19:00:02 UTC
Aliases:	McKesson Radiology
Introduced By:	TRM Request
Vendor Name:	Change Healthcare

Vendor Release Information

The Vendor Release table provides the known releases for the TRM Technology, obtained from the vendor (or from the release source).

Version	Release Date	Vendor End of Life Date
12.0	08/15/2013
12.1.x	01/10/2015
12.2.x	03/31/2016
12.3.x	06/23/2017	09/30/2022
12.4.x	07/10/2018	03/31/2023
14.x	10/27/2019

Current Decision Matrix (02/17/2023)

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.

The VA Decision Matrix displays the current and future VA IT position regarding different releases of a TRM entry. These decisions are based upon the best information available as of the most current date. The consumer of this information has the responsibility to consult the organizations responsible for the desktop, testing, and/or production environments to ensure that the target version of the technology will be supported. Any major.minor version that is not listed in the VA Decision Matrix is considered unapproved for use.

Legend:

White	Approved: The technology/standard has been approved for use.
Yellow	Approved w/Constraints: The technology/standard can be used within the specified constraints located below the decision matrix in the footnote[1] and on the General tab.
Gray	Unapproved: This technology or standard can be used only if a POA&M review is conducted and signed by the Authorizing Official Designated Representative (AODR) as designated by the Authorizing Official (AO) or designee and based upon a recommendation from the POA&M Compliance Enforcement, has been granted to the project team or organization that wishes to use the technology.
Orange	Divest: VA has decided to divest itself on the use of the technology/standard. As a result, all projects currently utilizing the technology/standard must plan to eliminate their use of the technology/standard. Additional information on when the entry is projected to become unapproved may be found on the Decision tab for the specific entry.
Black	Prohibited: The technology/standard is not (currently) permitted to be used under any circumstances.
Blue	Planning/Evaluation Constraint:The period of time this technology is currently being evaluated, reviewed, and tested in controlled environments. Use of this technology is strictly controlled and not available for use within the general population. If a customer would like to use this technology, please work with your local or Regional OI&T office and contact the appropriate evaluation office displayed in the notes below the decision matrix. The Local or Regional OI&T office should submit an inquiry to the TRM if they require further assistance or if the evaluating office is not listed in the notes below.

Release/Version Information:

VA decisions for specific versions may include a ‘.x’ wildcard, which denotes a decision that pertains to a range of multiple versions.

For example, a technology approved with a decision for 7.x would cover any version of 7.(Anything) - 7.(Anything). However, a 7.4.x decision would cover any version of 7.4.(Anything), but would not cover any version of 7.5.x or 7.6.x on the TRM.

VA decisions for specific versions may include ‘+’ symbols; which denotes that the decision for the version specified also includes versions greater than what is specified but is not to exceed or affect previous decimal places.

For example, a technology approved with a decision for 12.6.4+ would cover any version that is greater than 12.6.4, but would not exceed the .6 decimal ie: 12.6.401 is ok, 12.6.5 is ok, 12.6.9 is ok, however 12.7.0 or 13.0 is not.

<Past

CY2023

CY2024

CY2025

Future>

Release

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

12.0

Unapproved

12.1.x

Unapproved

12.2.x

Unapproved

12.3.x

Unapproved

12.4.x

Divest
[4, 11, 12, 13]

Unapproved

14.x

Approved w/Constraints
[4, 11, 12, 13]

Approved w/Constraints
[4, 11, 12, 14]

Approved w/Constraints
[4, 11, 14, 15]

Decision Constraints


[1]	Veterans Affairs (VA) users must ensure VA sensitive data is protected properly in accordance with VA Handbook 6500 and the Federal Information Security Management Act (FISMA). Per VA Handbook 6500, Federal Information Processing Standards (FIPS) 140-2 certified encryption must be used to protect and encrypt data in transit and at rest if Personally Identifiable Information/Protected Health Information/VA (PII/PHI/VA) sensitive information is involved. If FIPS 140-2 certified encryption is not used, additional mitigating controls must be documented in an approved System Security Plan (SSP). In addition, the technology must be implemented within the VA production network (not in a Demilitarized Zone (DMZ)), unless the specific uses and instances of the technology are approved by the Enterprise Security Change Control Board (ESCCB). All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500. In cases where the technology is used for external connections, a full ESCCB review is required in accordance VA Directive 6004, VA Directive 6517 and VA Directive 6513.

[2]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

[3]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP).

[4]	Technology must remain patched and operated in accordance with Federal and Department security policies and guidelines in order to mitigate known and future security vulnerabilities.

[5]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

[6]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP).

[7]	Users must ensure that Acrobat Reader, Google Chrome, Microsoft .NET Framework, Microsoft Internet Explorer (IE), and Oracle Database are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) This technology can be deployed with Secure Hypertext Transfer Protocol (S-HTTP) which is unapproved for use on the TRM. Users must ensure they are using this technology without Secure Hypertext Transfer Protocol (S-HTTP).

[8]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information Security Officer (ISO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP).

[9]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500.

[10]	Users must ensure that Acrobat Reader, Google Chrome, Microsoft .NET Framework, Microsoft Internet Explorer (IE), and Oracle Database are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) This technology can be deployed with Secure Hypertext Transfer Protocol (S-HTTP) which is unapproved for use on the TRM. Users must ensure they are using this technology without Secure Hypertext Transfer Protocol (S-HTTP). Users must Divest the use of Internet Explorer with this technology. Other approved internet browsers are available. See Category Tab for details.

[11]	Users must ensure that Oracle Database is implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) This technology can be deployed with Secure Hypertext Transfer Protocol (S-HTTP) which is unapproved for use on the TRM. Users must ensure they are using this technology without Secure Hypertext Transfer Protocol (S-HTTP). Users must utilize approved internet browsers, as Microsoft Internet Explorer has reached End of Life status. See Category Tab for details.

[12]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information System Security Officer (ISSO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP).

[13]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISSO (Information System Security Officer) to ensure compliance with VA Handbook 6500.

[14]	Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations. All instances of deployment using this technology should be reviewed by the local ISSO (Information System Security Officer) to ensure compliance with both VA Handbook 6500 and VA Directive 6500.

[15]	Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 or its successor to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 or 140-3 compliant full disk encryption (FOE) must be implemented on the storage device where the DBMS resides. Appropriate access enforcement and physical security control must also be implemented. All instances of deployment using this technology should be reviewed to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards. It is the responsibility of the system owner to work with the local CIO (or designee) and Information System Security Officer (ISSO) to ensure that a compliant DBMS technology is selected and that if needed, mitigating controls are in place and documented in a System Security Plan (SSP). By September 22, 2026, all FIPS 140-2 certificate validations will be placed on the Historical List, please refer to FIPS Transition Effort for further guidance and timeline of changes.

Note:

At the time of writing, version 14.1 is the most current version, released 05/05/2022.

References

The following reference(s) are associated with this entry:
Type	Name	Source	Description
Vendor Provided*	Change Healthcare Support Documentation		The link below provides support documentation for Change Healthcare.
*NOTE: Vendor provided information is subject to the accuracy of the manufacturer.

Technology Components

Note: This list may not be complete. No component, listed or unlisted, may be used outside of the technology in which it is released. The usage decision for a component is found in the Decision and Decision Constraints.
Name	Description
Clinical Reference Viewer	This component is a medical image viewer that enables users to access patient studies stored in the technology`s database.
Control Station	This is a system administration and management component that enables users to find studies based on a wide range of search criteria, view study and image details, group and ungroup studies, move and delete Digital Imaging and Communications in Medicine (DICOM) and non-DICOM objects associated with studies, export and print information about studies displayed in the Study Finder, and resend study status change notifications to external systems.
Exception Tracker	This is a system management component that enables users to identify and resolve issues encountered during system interface actions such as merging patient records and synchronizing data.
McKesson Radiology Collaboration	This component enables users to contact other medical staff and collaborate with them on patient studies. This component was introduced in version 12.3.x.
McKesson Radiology Disc	This component enables users to display study images and information on a workstation that cannot access the McKesson Radiology Station application. The study images and information are exported from a McKesson Radiology Station workstation to a removable media, a folder accessible from another workstation, or a third-party disc publishing device.
McKesson Radiology e-Jacket	This is a web browser-based component that provides quick access to patient information, patient documentation, and images for users who do not use image manipulation and navigation aids.
McKesson Radiology Quality Workflow Solutions	This component provides automated reporting and tracking of critical results, evaluating the interpretation of a previously reported study for accuracy and the appropriateness of the examination, and provides feedback to the imaging technologist on the accuracy and quality of images in a study and on the image acquisition techniques.
McKesson Radiology Report	This component enables users to complete diagnostic imaging reports. This component also enables users to view clinical reports, scanned documents, and study details, as well as create and/or play voice clips.
McKesson Radiology Station	This component is a multi-modality image viewer for viewing grayscale diagnostic Digital Imaging and Communications in Medicine (DICOM) medical images. This component is accessed through a web browser. This component enables users to view and manipulate images and studies, view and manage images and studies information, and view and create patient documentation.
McKesson Radiology Station Lite	This component is a DICOM-compliant image viewer used to view multi-modality, grayscale, cross-sectional images. This component offers a subset of the features offered by McKesson Radiology Station.
Picture Archiving Communication System (PACS) Admin	This is a system and site management component for configuring, maintaining, and updating user accounts and connected devices, as well as administrative information contained in the database.
Quality Assurance (QA) Manager	This component that helps users ensure the integrity of patient records and study information stored in the database. It raises a QA issue when suspicious, missing, or invalid items are detected. Users can then resolve any patient information, study information, and work list issues.
Retention Manager	This is a system administration and management component that enables the user to perform administrative tasks related to the retention and deletion of records. It identifies studies that can be deleted based on the retention rules defined by each medical institution.
Route Manager	This is a study management component for creating, modifying, and removing study-routing schedules to specific Digital Imaging and Communications in Medicine (DICOM) locations.
System Dashboard	This component enables users to access, evaluate, and monitor various statuses of the technology, including network connectivity and bandwidth, infrastructure processes and interfaces executed on the servers, archive capacities, and online storage capacity.

VA Categories View the VA Categorization Framework

Domain Area	Category	Customer Guidance	Category Locked By ELT Date
Health Care Health Services	Imaging
Health Care Administrative	Health Delivery Support

Operating Systems Supported by the Technology

macOS - Approved w/Constraints
Windows Client - Approved w/Constraints
Windows Server - Approved w/Constraints

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

This technology supports role-based authentication and authorization capabilities.
The vendor asserts this technology supports Health Insurance Portability and Accountability Act (HIPAA) regulations and protects patient security and confidentiality.
This technology may improve productivity for specific staff whose responsibilities include the exchange of medical data.
This is a well-documented technology.
At the time of writing, no National Institute of Standards and Technology (NIST) vulnerabilities had been reported and no VA Cyber Security Operations Center (CSOC) bulletins had been issued for the latest versions of this technology.
This technology is Federal Information Processing (FIPS) 140-2 compliant.

Adoption Risks

Microsoft Internet Explorer, a dependency of this technology, is in End of Life status and must no longer be used.
This technology can integrate with and alter database technologies.
The potential exists to store Personally Identifiable Information (PII), Protected Health Information (PHI) and/or VA Sensitive data and proper security standards must be followed in these cases.
Due to the rapid release schedule of this technology, the VA may be unable to update to the most recent patch and may require a deployment model requiring the use of specific versions.
There are other approved solutions that provide similar functionality available on the TRM. The use of several similar solutions may increase organization requirements for support and maintenance.

Architectural Benefits

This technology supports Health Level Seven (HL7) and Digital Imaging and Communications in Medicine (DICOM) to reduce transcription errors.
This technology is portable as it runs on multiple TRM-approved operating systems.
This technology can use a VA-preferred database.

Architectural Risks

This technology can be deployed with Secure Hypertext Transfer Protocol (S-HTTP) which is unapproved for use on the TRM.

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 24.3

General Information

Vendor Release Information

Current Decision Matrix (02/17/2023)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 24.3

General Information

Vendor Release Information

Current Decision Matrix (02/17/2023)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

EMAIL UPDATES