Locator

Contact

Locator

Vet Centers

Regional Benefits Offices

Regional Loan Centers

Cemetery Locations

VA Technical Reference Model v 24.7

Huron Healthcare Revenue Workflow Management Tools

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:	The Huron Healthcare Revenue Workflow Management Tools system is a critical element of the Consolidated Patient Account Center (CPAC) operating model, and is composed of ONTRAC, Tracking, Reporting, and Communication (TRAC), and Veteran Services workflow. The Veterans Health Administration (VHA) CPAC strives to improve efficiency and accountability in revenue operations. This technology is designed to offer comprehensive and precise monitoring over all aspects of the complex revenue cycle system, and reinforce the desired revenue processes in a sustainable manner. Additionally, this technology allows for efficient work drivers, process monitoring, and performance reporting that are critical to the CPAC model. Data is extracted nightly from Veterans Health Information Systems and Technology Architecture (VistA) and is imported into the Workflow Management Tools to populate the work drivers and reporting. Key user information input into TRAC during the course of the workday is also uploaded back into the VistA Accounts Receivable (AR) package where new AR comment transactions are created and filed. Once an account is in the Workflow Management Tools, it is analyzed and assigned, as required, depending on the Workflow Tool requirements. For ONTRAC, TRAC, and Veteran Services, it is assigned to one or more worklists. The worklists allow for the ability to manage the workflow, as appropriate, through such processes as insurance verification, revenue utilization review, billing, accounts management, and denials. As data works through this process, information is passed through reporting modules to provide timely and accurate reporting for CPAC Management. This web-based application is hosted on VA premises. The servers are all physically housed at VA, in the Office of Community Care offices in Asheville, North Carolina (NC). Data is stored in a Microsoft Structured Query Language (SQL) Server database that is encrypted using Transparent Data Encryption (TDE). Please note that there is no dedicated webpage for this technology.
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 v24.2
Decision Date:	02/23/2024 at 02:59:39 UTC
Aliases:	Huron Workflow Tools; Workflow Management Tools
Introduced By:	TRM Request
Vendor Name:	Huron Consulting Group, Inc.

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	Vendor Desupport Date
10.x
11.x

Current Decision Matrix (02/09/2024)

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

CY2022

CY2023

CY2024

Future>

Release

10.x

Divest
[2, 4, 6, 7, 8, 9]

Unapproved

11.x

Approved w/Constraints
[2, 4, 6, 7, 8, 9]

Approved w/Constraints
[2, 4, 6, 7, 10, 11]

Approved w/Constraints
[2, 4, 6, 7, 11, 12]

Approved w/Constraints
[2, 4, 6, 12, 13, 14, 15]

Approved w/Constraints
[2, 6, 12, 13, 14, 15, 16]

Decision Constraints


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

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

[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]	This product is Class 2 or Class 3 VA-designed and built Local Software OR is a commercially-licensed software product purchased or leased that will run in a VA VISTA environment or integrate with Class 1 National VISTA Software. Presence of this software on the One-VA TRM does not equate to designation as a Class 1 National Software product and MUST NOT be assumed to comply with all VA programming standards, namespacing and interface control agreement standards, data management standards, documentation standards, information assurance standards, security standards and 508 compliance standards. As a Class 2 or Class 3 product, it MUST NOT be assumed to having been released into production through all OI&T product release and sustainment process controls for project management; requirements, development and testing management; and configuration, change, and release management necessary to satisfy OI&T process and product compliance. The OI&T Enterprise Program Management Office does not endorse nor support Class 2 and Class 3 products and does not support data usage or application programmer interfaces (APIs) between Class 1 National Software products and Class 2 or Class 3 products. Class 2 or Class 3 products must restrict their interfaces to Class 1 National Software to use of publicly-supported APIs ONLY. VA Directive 6402, Modifications to Standardized National Software, dictates the policy for Class 2 and Class 3 products and modifications to Class 1 National Software products. Local enhancements to, or modifications of, Class 1 Protected National Software (as listed in the Directive), in part or in whole, is PROHIBITED. Local enhancements to, or modifications of, Non-Protected Class 1 National Software is allowed ONLY with an approved waiver by the Software Modification Waiver Committee (SMWC). Class 2 and Class 3 software that does not modify the Class 1 National Software in any way must still adhere to namespacing and interface control agreement standards as well as National Field Operations Processes.

[5]	New installations or major expansions of this technology that transmit data over the VA Wide Area Network (WAN) must complete a WAN impact review (contact VA e-mail: [OIT ITOPS SD Engagement Requests]) prior to implementation to ensure proper compliance to VA network design and usage requirements.

[6]	New installations or major expansions of this technology that transmit data over the VA Wide Area Network (WAN) must complete a WAN impact review (yourIT Service Portal:[SNOW Service Requests]) prior to implementation to ensure proper compliance to VA network design and usage requirements.

[7]	Users must ensure that Acrobat Reader, Microsoft Excel, Microsoft Internet Explorer (IE), Microsoft .Net Framework, Microsoft Internet Information Service (IIS), and Microsoft Structured Query Language (SQL) Server are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)

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

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

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

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

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

[13]	Users must ensure that Microsoft Excel, Microsoft Internet Information Service (IIS), Microsoft Edge, and Microsoft Structured Query Language (SQL) Server are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) Users must utilize approved internet browsers, as Microsoft Internet Explorer has reached End of Life status. See Category Tab for details.

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

[15]	The Federal Information Processing standards (FIPS) 140-2 certification status of this technology was not able to be verified. This technology will require a 3rd party FIPS 140-2 or 140-3 certified solution for any data containing PHI/PII or VA sensitive information, where applicable. More information regarding the Cryptographic Module Validation Program (CMVP) can be found on the NIST website.

[16]	This product is Class 2 or Class 3 VA-designed and built Local Software OR is a commercially-licensed software product purchased or leased that will run in a VA VISTA environment or integrate with Class 1 National VISTA Software. Presence of this software on the One-VA TRM does not equate to designation as a Class 1 National Software product and MUST NOT be assumed to comply with all VA programming standards, namespacing and interface control agreement standards, data management standards, documentation standards, information assurance standards, security standards and 508 compliance standards. As a Class 2 or Class 3 product, it MUST NOT be assumed to having been released into production through all OI&T product release and sustainment process controls for project management; requirements, development and testing management; and configuration, change, and release management necessary to satisfy OI&T process and product compliance. The OI&T Enterprise Program Management Office does not endorse nor support Class 2 and Class 3 products and does not support data usage or application programmer interfaces (APIs) between Class 1 National Software products and Class 2 or Class 3 products. Class 2 or Class 3 products must restrict their interfaces to Class 1 National Software to use of publicly-supported APIs ONLY. VA Directive 6402, Modifications to Standardized National Software, dictates the policy for Class 2 and Class 3 products and modifications to Class 1 National Software products. Local enhancements to, or modifications of, Class 1 Protected National Software (as listed in the Directive), in part or in whole, is PROHIBITED. Local enhancements to, or modifications of, Non-Protected Class 1 National Software is allowed ONLY with an approved waiver by the Software Modification Waiver Committee (SMWC). Class 2 and Class 3 software that does not modify the Class 1 National Software in any way must still adhere to namespacing and interface control agreement standards as well as National Field Operations Processes.

Note:

At the time of writing, the most recent version of this technology is 11.3.

The following reference(s) are associated with this entry:
Type	Name	Source	Description
There are no references identified for this entry.

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
Enterprise Denials	Enterprise Denials enables users to view trends and complete root cause analysis on denials.
MD Clarity`s Payer Compliance Tool	MD Clarity`s Payer Compliance Tool enables users to view and report expected reimbursement amounts for payers whose contracts are modeled in Payer Compliance. Users can also view 835 billed, allowed, and paid charges at the detail account level.
ONTRAC	ONTRAC is designed to enable effective monitoring of the front-end process, including verification of third party insurance and related authorization or pre-certification activities. The workflow application and associated process changes are intended to support improved performance in CPAC units such as Insurance Verification, Revenue Utilization Review, and Facility Revenue.
Tracking, Reporting, and Communication (TRAC)	TRAC is designed to enable effective claim monitoring, follow-up, and account resolution processes, supporting improved performance in CPAC units, such as Billing and Accounts Management. Additionally, QUIC, a portion of TRAC, also includes communication regarding resolution of specific encounters across all areas of the CPAC revenue cycle.
Veteran Services	Veteran Services is designed to enable effective monitoring, communication, and resolution of various Veteran Services processes, including claims matching, bankruptcies, repayment plans, aged debt, etc.


Collaboration and Electronic Workplace Productivity Software	Accounting and Finance
Health Care Administrative	Health Delivery Support

- The information contained on this page is accurate as of the Decision Date (02/23/2024 at 02:59:39 UTC).

Inside VA

Budget and Performance

Inside the Media Room

National Observances

Special Events

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (02/09/2024)

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

General Information

Vendor Release Information

Current Decision Matrix (02/09/2024)

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