Coding and Reimbursement System Plus (CRS+)

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:	3M Coding & Reimbursement System (CRS/CRS+) is a Commercial-off-the-shelf (COTS) encoder software solution which enables health record coding to Veterans Health Administration (VHA) coders and Health Information Management (HIM) Department users. CRS+, as an enterprise product, will integrate with the DSS, Inc. applications currently in use throughout VHA by HIM and revenue cycle users. It is an Application Programming Interface (API) that provides users with support for selecting, Evaluation & Management (E/M) codes, International Classification of Diseases 10 (ICD10) code lookup, Healthcare Common Procedure Coding System (HCPCS) code look up, supporting utilities. In a pre-solicitation phase, 3M to provide implementation plans upon award.
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/14/2024 at 03:14:53 UTC
Aliases:	CRS, CRS+
Introduced By:	TRM Request
Vendor Name:	3M

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
CRSv 20.1.x	03/03/2020
CRSv 21.1.x
CRSv 22.x	02/24/2022
CRSv 23.x
CRSv 24.x

Current Decision Matrix (02/12/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

CY2024

CY2025

CY2026

Future>

Release

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

Q1

Q2

Q3

Q4

CRSv 20.1.x

Unapproved

CRSv 21.1.x

Unapproved

CRSv 22.x

Divest
[5, 10, 12, 13]

Unapproved

CRSv 23.x

Divest
[5, 10, 12, 13]

Unapproved

CRSv 24.x

Approved w/Constraints
[5, 10, 12, 13]

Decision Constraints


[1]	Users must ensure that Microsoft .NET Framework and Microsoft Internet Explorer (IE) are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)

[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]	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]	Users must ensure that Google Chrome, Microsoft .NET Framework and Microsoft Internet Explorer (IE) are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)

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

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

[7]	Users must ensure that Google Chrome, Adobe Acrobat DC, Microsoft .NET Framework and Microsoft Internet Explorer (IE) are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) Users must Divest the use of Internet Explorer with this technology. Other approved internet browsers are available. See Category Tab for details.

[8]	Users must ensure that Microsoft Structured Query Language (SQL) Server and Apache Hypertext Transfer Protocol (HTTP) 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.

[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 ISSO (Information System Security Officer) to ensure compliance with VA Handbook 6500.

[10]	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 ISSO (Information System Security Officer) can advise on the ESCCB review process.

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

[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 Citrix Virtual Apps and Desktops (CVAD), Google Chrome, Microsoft Edge, Microsoft Structured Query Language (SQL) Server and Apache Hypertext Transfer Protocol (HTTP) Server are implemented with VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’)

Note:

At the time of writing, version 24.0.0.0 is the most current version.

References

The following reference(s) are associated with this entry:
Type	Name	Source	Description
*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
3M 360 Encompass System	Is the only computer-assisted coding and clinical documentation improvement (CDI) solution fully integrated with the 3M CRS+. It was developed to help coders realize the significant productivity gains from natural language processing (NLP) technology, without sacrificing the ability to understand the expert logic behind each computer-suggested code.
3M Advanced Analyzer Software	Helps coders pick up the specificity in clinical documentation and obtain the most precise and comprehensive set of codes; also provides suggestions for frequently missed codes that impact Medicare Severity-Diagnosis related group (MS-DRG) and 3M All Patients Refined (APR) Diagnosis related group (DRG) assignment, as well as severity of illness and risk of mortality, important quality metrics.
3M APCfinder Software	Calculates Ambulatory Payment Classifications (APCs) incorporating outpatient prospective payment system regulations for editing, grouping and reimbursement.
3M Codefinder Software	Manages the complex rules and terminology found in mandated rules, principles and guidelines.
3M DRGfinder Software	Provides accurate Medicare Severity-Diagnosis related group (MS-DRG) grouping capabilities for Medicare and other payers. DRGs are automatically computed to help improve coder productivity, and multiple DRGs can be calculated at the same time. Also indicates whether a code is an major complication or comorbidity (MCC) or a complication or comorbidity (CC).
3M Healthcare Common Procedure Coding System/Current Procedural Terminology (HCPCS/CPT)finder Software	Determines the standard five-digit code for outpatient procedures and services.
3M Reimbursement Calculation Software	Calculates instantly the reimbursement based on formulas that use appropriate national and hospital-specific variables. It includes Medicare inpatient and outpatient formulas and accommodates various other pay.
3M WinAppLink	The 3M WinAppLink application transfers information to and from CRS+ and VistA integrator applications.

VA Categories View the VA Categorization Framework

Domain Area	Category	Customer Guidance	Category Locked By ELT Date
Collaboration and Electronic Workplace Productivity Software	Accounting and Finance

Operating Systems Supported by the Technology

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

Technologies/Standards Relationships

Runtime Dependencies:

Adobe Acrobat Document Cloud (DC)
Apache Hypertext Transfer Protocol (HTTP) Server
Citrix Virtual Apps and Desktops (CVAD) - (required for some configurations)
Microsoft .NET Framework
Microsoft Edge. - (required for some configurations)
Microsoft Structured Query Language (SQL) Server

Comparable Technologies:

No comparable entries have been identified.

Companion Technologies/Supported Standards:

General Analysis

Adoption Benefits

This technology provides a sophisticated, easy-to-learn solution for accurate, complete and compliant coding.
This technology delivers simplified International Classification of Diseases (ICD) 10 Procedure Coding System (PCS) ICD-10-PCS coding with combined logic-based and table-driven workflow.
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 utilizes built-in Authentication and Authorization (A&A) capabilities.
This technology is Federal Information Processing (FIPS) 140-2 compliant.

Adoption Risks

There is limited publicly available technical documentation for this technology.
This technology can integrate with and alter database technologies.
This technology may utilize external data connections.
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.

Architectural Benefits

This technology can use a VA-preferred database.
This technology is compatible with virtual machines, therefore consistent with the enterprise Server Virtualize First Policy (VAIQ 7266972 08-27-2012).

Architectural Risks

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

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/12/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/12/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