| 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 System Security Officer (ISSO), 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 VAIT
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.
|
|
|
| Legend: |
| White |
Authorized: The technology/standard has been authorized for use.
|
| Yellow |
Authorized 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 |
Unauthorized, Conditions Required[a]
: 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 |
Unauthorized, Conditions Required[b]
: 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 unauthorized may be
found on the Decision tab for the specific entry.
|
| Black |
Unauthorized: The technology/standard is not (currently) permitted to be used under any circumstances.
|
| Blue |
Unauthorized, Conditions Required[c]
: 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 authorized 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 authorized 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.
|
| Any major.minor version that is not listed in the VA Decision Matrix is considered Unauthorized, Conditions Required
[a]
. |
|
<Past |
Future> |
| STU 1 |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (DIVEST)
|
Authorized w/ Constraints (DIVEST)
|
Authorized w/ Constraints (DIVEST)
|
Unauthorized, Conditions Required[b]
|
Unauthorized, Conditions Required[b]
|
Unauthorized, Conditions Required[b]
|
Unauthorized, Conditions Required[b]
|
Unauthorized, Conditions Required[b]
|
Unauthorized, Conditions Required[b]
|
Unauthorized, Conditions Required[b]
|
Unauthorized, Conditions Required[b]
|
| STU 2 |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (DIVEST)
|
Authorized w/ Constraints (DIVEST)
|
Authorized w/ Constraints (DIVEST)
|
Unauthorized, Conditions Required[b]
|
Unauthorized, Conditions Required[b]
|
Unauthorized, Conditions Required[b]
|
Unauthorized, Conditions Required[b]
|
Unauthorized, Conditions Required[b]
|
Unauthorized, Conditions Required[b]
|
Unauthorized, Conditions Required[b]
|
Unauthorized, Conditions Required[b]
|
| STU 3 |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (DIVEST)
|
Authorized w/ Constraints (DIVEST)
|
Authorized w/ Constraints (DIVEST)
|
Unauthorized, Conditions Required[b]
|
Unauthorized, Conditions Required[b]
|
Unauthorized, Conditions Required[b]
|
Unauthorized, Conditions Required[b]
|
Unauthorized, Conditions Required[b]
|
Unauthorized, Conditions Required[b]
|
Unauthorized, Conditions Required[b]
|
Unauthorized, Conditions Required[b]
|
| STU 4 |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (DIVEST)
|
Authorized w/ Constraints (DIVEST)
|
Authorized w/ Constraints (DIVEST)
|
Unauthorized, Conditions Required[b]
|
Unauthorized, Conditions Required[b]
|
Unauthorized, Conditions Required[b]
|
Unauthorized, Conditions Required[b]
|
Unauthorized, Conditions Required[b]
|
Unauthorized, Conditions Required[b]
|
Unauthorized, Conditions Required[b]
|
Unauthorized, Conditions Required[b]
|
| STU 5 |
Authorized w/ Constraints (POA&M) |
Authorized w/ Constraints (DIVEST)
|
Authorized w/ Constraints (DIVEST)
|
Authorized w/ Constraints (DIVEST)
|
Unauthorized, Conditions Required[b]
|
Unauthorized, Conditions Required[b]
|
Unauthorized, Conditions Required[b]
|
Unauthorized, Conditions Required[b]
|
Unauthorized, Conditions Required[b]
|
Unauthorized, Conditions Required[b]
|
Unauthorized, Conditions Required[b]
|
Unauthorized, Conditions Required[b]
|
| STU 6 |
Authorized w/ Constraints (POA&M) |
Authorized |
Authorized |
Authorized |
Authorized |
Authorized |
Authorized |
Authorized |
Authorized |
Authorized |
Authorized |
Authorized |
| Note: |
The integration with US Core is essential for ensuring measures and CDS artifacts use data that maintains consistent meaning during routine data capture and sharing (interoperability). The Assistant Secretary for Technology Policy (ASTP)/Office of the National Coordinator for Health Information Technology (ONC) defines requirements by publishing the United States Core Data for Interoperability (USCDI) versions. Each QI-Core version builds upon the newest US Core version, which is based upon the current USCDI version. For example, QI-Core 6.0 builds upon US Core version 6.1.0, which incorporates USCDI version 3, required for clinical vendor certification effective January 2026. Please contact the VHA Office of Standards & Interoperability (Mailgroup: vhas&iresponseteam@va.gov) prior to implementation to obtain guidance and the VHA-endorsed version of this standard. |
