Locator

Contact

Locator

Vet Centers

Regional Benefits Offices

Regional Loan Centers

Cemetery Locations

VA Technical Reference Model v 24.11

Visual Health Information (VHI) Personal Computer (PC)-Kits

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:	Visual Health Information (VHI) Personal Computer (PC)-Kits is an evidence-based exercise research solution that develops rehabilitation or fitness exercise programs. This technology allows users to custom home exercise programs and therapy recommendations based on individualized problems and goals. It also provides functionalities like create, customize and print an exercise routine. Additionally, it can be used by physical therapist, occupational therapists, certified athletic trainers, strength and conditioning coaches, and fitness directors of health clubs. VHI PC-Kits has two editions: Desktop and Network Editions. The Desktop Edition is licensed to be used on a single computer. The Network Edition is licensed by the number of simultaneous users, not by the number of installations and is installed on a network allowing multiple computers access to the same data. This entry covers both editions. This technology comes with Microsoft Structured Query Language (SQL) Server 2014 Express Edition for versions 4.2 and later; however, this technology will work with any edition of Microsoft SQL Server. The exercise kits have been listed on the components tab. If additional kits are needed they must be requested. Both the vendor and technology page no longer exist for this software. The vendor has decided to shut down its business operation
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.7
Decision Date:	07/10/2020 at 14:35:09 UTC
Introduced By:	TRM Request
Vendor Name:	Visual Health Information

Vendor Release Information

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

You must be logged into the RSAA website prior to clicking the Attestation URLs or the URLs won't open.

Version	Release Date	Vendor End of Life Date	Vendor Desupport Date
3.4	09/01/2010
4.0	06/17/2013
4.1	03/15/2015
4.2	05/24/2016
5.0	01/22/2018

Current Decision Matrix (06/22/2020)

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 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	Authorized w/ Constraints (POA&M): 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	Authorized w/ Constraints (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 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	Authorized w/ Constraints (PLANNING/EVALUATION): 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 Authorized w/ Constraints (POA&M).

<Past

CY2023

CY2024

CY2025

Future>

Release

4.0

Unapproved

Authorized w/ Constraints (POA&M)

4.1

Unapproved

Authorized w/ Constraints (POA&M)

4.2

Unapproved

Authorized w/ Constraints (POA&M)

5.0

Unapproved

Authorized w/ Constraints (POA&M)

Decision Constraints


[1]	Projects using this technology must meet Veterans Affairs (VA) Directive 6500 and implement Federal Information Processing Standards (FIPS 199) for all laptop devices and National Institute of Standards and Technology Special Publication 800-53 for all desktop devices when VA sensitive information is involved, or additional mitigating controls must be documented in an authorized System Security Plan (SSP) to prevent potential disclosure of PII/PHI data. Additionally, projects which interface with external VA partner must have a Memorandum of Understanding and Interconnection Security Agreements (MOU/ISA), which detail the security requirements for users and systems that share information and resources outside of the VA production network.

[2]	As of April 23, 2015, per the Deputy CIO of Architecture, Strategy and Design (ASD), all technologies in use by the VA require an assessment by the VA Section 508 office. Section 508 of the Rehabilitation Act Amendments of 1998 is a federal law that sets the guidelines for technology accessibility. A VA Section 508 assessment of this technology has not been completed at the time of publication. Therefore, as of April 23, 2015 only users of this technology who have deployed the technology to the production environment, or have project design and implementation plans authorized, may continue to operate this technology. In the case of a project that has implemented, or been authorized for a specific site or number of users, and that project needs to expand operations to other sites or to an increased user base, it may do so as long as the project stays on the existing version of the technology that was authorized or implemented as of April 22, 2015. Use of this technology in all other cases is prohibited.

[3]	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.

[4]	This technology should only be used when required by a Veterans Affairs (VA) business partner for an authorized VA Project. Use of this technology must comply with ESCCB requirements which include: Signed Interconnection Agreements/Memorandum of Understanding agreements (MOU/ISA) with each external business partner, compliance with VA Handbook 6500, and must implement appropriate National Institute of Standards and Technology (NIST) Federal Information Processing Standards (FIPS) requirements for all devices interacting with this technology. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with VA Handbook 6500 and National Institute of Standards and Technology (NIST) standards and an ISO Risk Based Decision (RBD) must be authorized by the local ISO/CIO before it can be used in the VA Production Environment. In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance VA Directive 6004, VA Directive 6517 and VA Directive 6513. The local ISO can advise on the ESCCB review process and ensure privacy of information compliance protections are in place.

[5]	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).

[6]	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.

[7]	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).

[8]	If free trialware is utilized, the software must be purchased or removed at the end of the trial period.

[9]	Users should check with their supervisor, Information Security Office (ISO) or local OIT representative for permission to download and use this software. Downloaded software must always be scanned for viruses prior to installation to prevent adware or malware. Freeware may only be downloaded directly from the primary site that the creator of the software has advertised for public download and user or development community engagement. Users should note, any attempt by the installation process to install any additional, unrelated software is not authorized and the user should take the proper steps to decline those installations.

Type	Name	Source	Description
Guideline	VHI PC-Kits User Guide	Publicly available	This link points to the user guide for Visual Health Information (VHI) Personal Computer (PC)-Kits.

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
Geriatric Exercise Resource Library	Geriatric Exercise Resource Library is a library of 457 illustrated exercises with 31 tip sheets focusing on Orthopedic, Mobility, Health Promotion and Special Conditions.
Orthopedic Exercise & Rehab Prescription Kit	Orthopedic Exercise & Rehab Prescription Kit is a library of 574 illustrated exercises related to orthopedic physical therapy.
Pilates Mat Exercises	Pilates Mat Exercises is developed from the Pilates vocabulary on the mat or derived from the original exercises created by Joseph Pilates on his machines. This collection contains authentic Pilates exercises.
Tai Chi Fundamentals Program (TCF)	Tricia Yu`s Tai Chi Fundamentals Program (TCF) makes Tai Chi accessible to individuals with a wide range of abilities and physical conditions, with modifications for seated and supported standing activities. This collection of exercises follows a motor developmental sequence and includes Tai Chi Warm-Ups, Movement Patterns, and Flexibility. This program integrates mind/body principles to further enhance mental focus, breath awareness, and relaxation. This collection is an ideal way to train functional movements needed for activities of daily living and improve postural stability necessary for both static and dynamic balance.


Health Care Health Services	Rehabilitation Services

General Analysis

Adoption Benefits

At the time of writing, no National Institute of Standards and Technology (NIST) vulnerabilities had been reported for this technology.
This is a well-documented technology.
Users can add new exercises to this technology. These exercises can be line drawings (as are used in the kits purchased) or they can be photographs that have been scanned or taken with a digital camera.
This technology uses role-based Authentication and Authorization (A&A) capabilities.

Adoption Risks

The vendor has shut down business operations as of April 30, 2018.
The technology may collect, store or transmit Personally Identifiable Information (PII)/Protected Health information (PHI) or VA sensitive data.
This technology leverages database technologies which may result in potential security risks.

Architectural Benefits

This technology offers both desktop and network configurations. The Network Edition can be installed in client-server, peer-to-peer, and terminal server configurations.

Architectural Risks

This technology is not portable as it runs only on Windows platforms.

- The information contained on this page is accurate as of the Decision Date (07/10/2020 at 14:35:09 UTC).

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 24.11

General Information

Vendor Release Information

Current Decision Matrix (06/22/2020)

Decision Constraints

References

Technology Components

VA Categories

View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Optional 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.11

General Information

Vendor Release Information

Current Decision Matrix (06/22/2020)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Operating Systems Supported by the Technology

Technologies/Standards Relationships

Runtime Dependencies:

Optional Dependencies:

Comparable Technologies:

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

Adoption Risks

Architectural Benefits

Architectural Risks

EMAIL UPDATES

VA Categories

View the VA Categorization Framework