Locator

Contact

Locator

Vet Centers

Regional Benefits Offices

Regional Loan Centers

Cemetery Locations

VA Technical Reference Model v 24.7

Mirth Connect

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:	Mirth Connect is a cross-platform Health Level-7 (HL7) interface engine that enables bi-directional sending of HL7 messages between systems and applications over multiple transports. The technology transforms non-standard data in standard forms and can monitor multiple interfaces.
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 been assessed by the Section 508 Office and found non-conformant. 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. Please see reference tab for more information concerning product versions.
Decision:	View Decisions

Decision Source:	TRM Mgmt Group
Decision Process:	One-VA TRM v24.5
Decision Date:	05/30/2024 at 02:59:23 UTC
Aliases:	NextGen Connect
Introduced By:	CDCO Supported Architecture Components
Vendor Name:	NextGen

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
1.6	08/16/2006
1.7	04/25/2008
1.8	01/15/2009
2.0	10/27/2010
2.1.x	04/26/2011
2.2.x	01/23/2012
3.0.x	10/01/2013
3.1.x	10/15/2014
3.2.x	02/23/2015
3.3.x	05/15/2015
3.4.1	06/16/2016
3.4.2	09/14/2016
3.5.x	09/01/2017
3.6	05/29/2018
3.7.x	12/19/2018
3.8.x	01/09/2020
3.9.x	04/22/2020
3.10.x	11/13/2020
3.11.x	04/26/2021
3.12.x	10/08/2021
4.1.x	07/29/2022
4.2.x	12/13/2022
4.3.x	04/03/2023
4.4.x	10/16/2023
4.5.x	01/31/2024

Current Decision Matrix (05/23/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

1.6

Unapproved

1.7

Unapproved

1.8

Unapproved

2.0

Unapproved

2.1.x

Unapproved

2.2.x

Unapproved

3.0.x

Unapproved

3.1.x

Unapproved

3.2.x

Unapproved

3.3.x

Unapproved

3.4.1

Unapproved

3.4.2

Unapproved

3.5.x

Unapproved

3.6

Unapproved

3.7.x

Unapproved

3.8.x

Unapproved

3.9.x

Unapproved

3.10.x

Divest
[4, 11, 12, 13, 14, 15, 16]

Divest
[4, 11, 12, 13, 15, 16, 17]

Divest
[4, 11, 12, 13, 15, 16, 18]

Unapproved

3.11.x

Divest
[4, 11, 12, 13, 14, 15, 16]

Divest
[4, 11, 12, 13, 15, 16, 17]

Divest
[4, 11, 12, 13, 15, 16, 18]

Unapproved

3.12.x

Approved w/Constraints
[4, 11, 12, 13, 14, 15, 16]

Divest
[4, 11, 12, 13, 15, 16, 17]

Divest
[4, 11, 12, 13, 15, 16, 18]

Divest
[13, 16, 18, 19, 20, 21, 22]

Divest
[13, 16, 19, 20, 21, 22, 23, 24]

Divest
[13, 16, 20, 21, 22, 24, 25]

Unapproved

4.1.x

Unapproved

Approved w/Constraints
[4, 11, 12, 13, 15, 16, 17]

Divest
[4, 11, 12, 13, 15, 16, 18]

Divest
[13, 16, 18, 19, 20, 21, 22]

Divest
[13, 16, 19, 20, 21, 22, 23, 24]

Divest
[13, 16, 20, 21, 22, 24, 25]

Divest
[13, 16, 20, 21, 24, 25, 26, 27]

Prohibited

4.2.x

Unapproved

Approved w/Constraints
[4, 11, 12, 13, 15, 16, 18]

Approved w/Constraints
[13, 16, 18, 19, 20, 21, 22]

Divest
[13, 16, 19, 20, 21, 22, 23, 24]

Divest
[13, 16, 20, 21, 22, 24, 25]

Divest
[13, 16, 20, 21, 24, 25, 26, 27]

Prohibited

4.3.x

Unapproved

Approved w/Constraints
[13, 16, 19, 20, 21, 22, 23, 24]

Divest
[13, 16, 20, 21, 22, 24, 25]

Divest
[13, 16, 20, 21, 24, 25, 26, 27]

Prohibited

4.4.x

Unapproved

Approved w/Constraints
[13, 16, 20, 21, 22, 24, 25]

Divest
[13, 16, 20, 21, 24, 25, 26, 27]

Prohibited

4.5.x

Unapproved

Approved w/Constraints
[13, 16, 20, 21, 24, 25, 26, 27]

Approved w/Constraints
[13, 16, 20, 21, 24, 26, 27, 28]

Decision Constraints


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

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

[4]	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 approved and the user should take the proper steps to decline those installations.

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

[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]	This technology must run on an approved version of the Oracle JRE (Java Runtime Environment). .

[10]	This technology must run on an approved version of a Java Runtime Environment. Users must ensure that Microsoft Structured Query Language (SQL) Server, PostgreSQL, and Oracle Database are implemented with VA-approved baselines.

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

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

[13]	This product can be configured with a PostgreSQL Database, which currently has TRM constraints limiting its use to Red Hat Enterprise Linux (RHEL) only due to its many known security issues on other platforms. If PostgreSQL is selected for use with this product, these factors must be considered especially when an instance of this product will be considered a Moderate or High-Risk system. See PostgreSQL Database TRM entry for more details.

[14]	This technology must run on an approved version of a Java Runtime Environment. Users must ensure that Microsoft Structured Query Language (SQL) Server, Google Chrome, Firefox, PostgreSQL, and Oracle Database are implemented with VA-approved baselines. (See `Categories` Tab under `Runtime Dependencies`). The user should not use the Secure Sockets Layer (SSL) protocols with this technology, SSL is unapproved at this time. This technology must use the latest TRM-approved version of Java Development Kit (JDK) - Oracle. This technology should not be used with MySQL Database - Community Edition, it is unapproved for use. There are other approved options available. See `Categories` Tab under `Runtime Dependencies`.

[15]	Due to National Institute of Standards and Technology (NIST) identified security vulnerabilities, extra vigilance should be applied to ensure the versions remain properly patched to mitigate known and future vulnerabilities. The local ISO can provide assistance in reviewing the NIST vulnerabilities.

[16]	If this product uses a MySQL database, the product must be configured with a commercial edition of the MySQL Database, which currently has TRM constraints limiting its use for intranet and non-sensitive data only due to its many known security issues. If a commercial edition of MySQL is selected for use with this product, these factors must be considered especially when an instance of this product will be considered a Moderate or High-Risk system. See MySQL Database – Commercial Edition TRM entry for more details.

[17]	This technology must use the latest TRM-approved version of Java Runtime Environment (JRE) - Oracle. Users must ensure that Microsoft Structured Query Language (SQL) Server, Google Chrome, Firefox, PostgreSQL, and Oracle Database are implemented with VA-approved baselines. (See `Categories` Tab under `Runtime Dependencies`). The user should not use the Secure Sockets Layer (SSL) protocols with this technology, SSL is unapproved at this time. This technology must use the latest TRM-approved version of Java Development Kit (JDK) - Oracle. This technology should not be used with MySQL Database - Community Edition, it is unapproved for use. There are other approved options available. See `Categories` Tab under `Runtime Dependencies`. The File Transfer Protocol (FTP) features of this software must not be used as the FTP protocol is prohibited for use on the VA network. (For further information see: VA Policy Memo VAIQ 7615193 on Prohibited Use of File Transfer Protocol (FTP) and Telnet Services)

[18]	This technology must use the latest TRM-approved version of Java Runtime Environment (JRE) - Oracle. Users must ensure that Microsoft Structured Query Language (SQL) Server, PostgreSQL, and Oracle Database are implemented with VA-approved baselines. (See `Categories` Tab under `Runtime Dependencies`). The user should not use the Secure Sockets Layer (SSL) protocols with this technology, SSL is unapproved at this time. This technology must use the latest TRM-approved version of Java Development Kit (JDK) - Oracle. This technology should not be used with MySQL Database - Community Edition, it is unapproved for use. There are other approved options available. See `Categories` Tab under `Runtime Dependencies`. The File Transfer Protocol (FTP) features of this software must not be used as the FTP protocol is prohibited for use on the VA network. (For further information see: VA Policy Memo VAIQ 7615193 on Prohibited Use of File Transfer Protocol (FTP) and Telnet Services)

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

[20]	Users should check with their supervisor, Information System Security Officer (ISSO) 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 approved and the user should take the proper steps to decline those installations.

[21]	Due to National Institute of Standards and Technology (NIST) identified security vulnerabilities, extra vigilance should be applied to ensure the versions remain properly patched to mitigate known and future vulnerabilities. The local ISSO (Information System Security Officer) can provide assistance in reviewing the NIST vulnerabilities.

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

[23]	This technology must use the latest TRM-approved version of Java Runtime Environment (JRE) - Oracle. Users must ensure that Microsoft Structured Query Language (SQL) Server, MySQL - Commerical, and Oracle Database are implemented with VA-approved baselines. (See `Categories` Tab under `Runtime Dependencies`). The user should not use the Secure Sockets Layer (SSL) protocols with this technology, SSL is unapproved at this time. This technology must use the latest TRM-approved version of Java Development Kit (JDK) - Oracle. This technology should not be used with MySQL Database - Community Edition, it is unapproved for use. There are other approved options available. See `Categories` Tab under `Runtime Dependencies`. The File Transfer Protocol (FTP) features of this software must not be used as the FTP protocol is prohibited for use on the VA network. (For further information see: VA Policy Memo VAIQ 7615193 on Prohibited Use of File Transfer Protocol (FTP) and Telnet Services)

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

[25]	This technology must use the latest TRM-approved version of Java Runtime Environment (JRE) - Oracle. Users must ensure that PostgreSql, Microsoft Structured Query Language (SQL) Server, MySQL - Commerical, and Oracle Database are implemented with VA-approved baselines. (See `Categories` Tab under `Runtime Dependencies`). The user should not use the Secure Sockets Layer (SSL) protocols with this technology, SSL is unapproved at this time. This technology must use the latest TRM-approved version of Java Development Kit (JDK) - Oracle. Users are not permitted to utilize My Structured Query Language (MySQL) Database - Community Editions, as it is unapproved for use on the TRM. The File Transfer Protocol (FTP) features of this software must not be used as the FTP protocol is prohibited for use on the VA network. (For further information see: VA Policy Memo VAIQ 7615193 on Prohibited Use of File Transfer Protocol (FTP) and Telnet Services)

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

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

[28]	This technology must use the latest TRM-approved version of Java Runtime Environment (JRE) - Oracle. Users must ensure that PostgreSql, Microsoft Structured Query Language (SQL) Server, MySQL - Commerical, and Oracle Database are implemented with VA-approved baselines. (See `Categories` Tab under `Runtime Dependencies`). The user should not use the Secure Sockets Layer (SSL) protocols with this technology, SSL is unapproved at this time. This technology must use the latest TRM-approved version of Java Development Kit (JDK) - Oracle. The File Transfer Protocol (FTP) features of this software must not be used as the FTP protocol is prohibited for use on the VA network. (For further information see: VA Policy Memo VAIQ 7615193 on Prohibited Use of File Transfer Protocol (FTP) and Telnet Services)

Note:

At the time of writing, version 4.5.0 is the most current version, released 01/31/2024.

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.

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
Apache Derby	Apache Derby, an Apache DB subproject, is an open source relational database implemented entirely in Java and available under the Apache License, Version 2.0.
Mirth Connect Administrator Launcher	Mirth Connect Administrator Launcher is a graphical user interface (GUI) that connects to the Mirth Connect Server and allows users to configure interfaces, monitor interface activity, and browse the message store.
Mirth Connect Command Line Interface (CLI)	Mirth Connect Command Line Interface (CLI) is a command line application that allows connections to the Mirth Connect Server to deploy/import/export channels and perform other administrative tasks.
Mirth Connect Server	Mirth Connect Server contains the back-end for the management interface and the integration engine component, which performs message filtering, transformation, and transmission.
Mirth Connect Server Manager	Mirth Connect Server Manager is a graphical user interface (GUI) that manages the Mirth Connect Service, displays log files, and contains other configuration settings for the Mirth Connect Server.


Application Technology Integration Software	Messaging Oriented Middleware (MOM)

- The information contained on this page is accurate as of the Decision Date (05/30/2024 at 02:59:23 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 (05/23/2024)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Open Source

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

CONNECT

VA HOME

QUICK LIST

RESOURCES

ADMINISTRATION

VA Technical Reference Model v 24.7

General Information

Vendor Release Information

Current Decision Matrix (05/23/2024)

Decision Constraints

References

Technology Components

VA Categories View the VA Categorization Framework

Open Source

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

EMAIL UPDATES