Locator

Contact

Locator

Vet Centers

Regional Benefits Offices

Regional Loan Centers

Cemetery Locations

VA Technical Reference Model v 24.7

HealthShare

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:	HealthShare is a solution used for strategic interoperability and analytics for action within a single facility, or across a hospital network. This product provides Representational State Transfer (REST) services to multiple instances or an entire enterprise. HealthShare supports the standards and profiles required for interoperability and document-based health information exchange with other healthcare organizations, clinicians, and public health agencies. This software aggregates and normalizes clinical and demographic data, including documents, from multiple facilities and locations into a consistent, patient-centric record. The record can be made available in a variety of formats, including all major health information exchange standards. HealthShare can connect to any database, Structured Query Language (SQL) or non SQL-based, or external cloud storage as it follows standard-based interoperability and open connectivity. This technology stores and transmits Personally Identifiable Information (PII)/Protected Health Information (PHI) data which can be stored in encrypted databases. However, the data can be de-identified when queried and displays the information requested by the user depending on the administrative rights that user has when submitting a query. The TRM decisions in this entry only apply to technologies and versions owned, operated, managed, patched, and version-controlled by VA. This includes technologies deployed as software installations on VMs within VA-controlled cloud environments (e.g. VA Enterprise Cloud (VAEC)). Cloud services provided by the VAEC, which are listed in the VAEC Service Catalog, and those controlled and managed by an external Cloud Service Provider (i.e. SaaS) are not in the purview of the TRM. For more information on the use of cloud services and cloud-based products within VA, including VA private clouds, please see the Enterprise Cloud Solutions Office (ECSO) Portal at: https://dvagov.sharepoint.com/sites/OITECSO Note: VA is moving towards adoption of Intersystems HealthShare as a standard interfacing solution between VISTA and non-VISTA product technologies. Due to the vision of Electronic Health Record Management (eHRM), implementers of other VA and non-VA previously implemented solutions need to plan for the migration to use of HealthShare as a best practice for interfacing VISTA products to non-VISTA products.
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 v23.10
Decision Date:	10/10/2023 at 16:08:25 UTC
Introduced By:	TRM Request
Vendor Name:	InterSystems

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
2015.1.x	03/17/2015
2015.2.x	08/18/2015
2016.1.x	04/04/2016
2017.1.x	03/23/2017
2017.2.x	10/13/2017
2018.1.x	09/01/2018
2019.1.x	04/12/2019
2020.1.x
2021.1.x
2022.1.x
2022.2.x
2023.1.x	10/03/2023

Current Decision Matrix (10/05/2023)

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

CY2021

CY2022

CY2023

Future>

Release

2015.1.x

Unapproved

2016.1.x

Unapproved

2017.1.x

Unapproved

2017.2.x

Divest
[5, 11, 12, 13, 14]

Unapproved

2018.1.x

Divest
[5, 11, 12, 13, 14]

Divest
[5, 11, 12, 14, 15]

Divest
[5, 12, 14, 15, 16]

Unapproved

2019.1.x

Divest
[5, 11, 12, 13, 14]

Divest
[5, 11, 12, 14, 15]

Divest
[5, 12, 14, 15, 16]

Unapproved

2020.1.x

Approved w/Constraints
[5, 11, 12, 13, 14]

Approved w/Constraints
[5, 11, 12, 14, 15]

Divest
[5, 12, 14, 15, 16]

Approved w/Constraints
[5, 12, 14, 15, 16]

Approved w/Constraints
[5, 12, 14, 16, 17]

Approved w/Constraints
[5, 12, 14, 17, 18]

Approved w/Constraints
[5, 17, 18, 19, 20]

Divest
[5, 17, 20, 21, 22]

2021.1.x

Unapproved

Approved w/Constraints
[5, 12, 14, 15, 16]

Approved w/Constraints
[5, 12, 14, 16, 17]

Approved w/Constraints
[5, 12, 14, 17, 18]

Approved w/Constraints
[5, 17, 18, 19, 20]

Divest
[5, 17, 20, 21, 22]

2022.1.x

Unapproved

Approved w/Constraints
[5, 12, 14, 17, 18]

Approved w/Constraints
[5, 17, 18, 19, 20]

Divest
[5, 17, 20, 21, 22]

2022.2.x

Unapproved

Approved w/Constraints
[5, 12, 14, 17, 18]

Approved w/Constraints
[5, 17, 18, 19, 20]

Divest
[5, 17, 20, 21, 22]

2023.1.x

Unapproved

Approved w/Constraints
[5, 17, 20, 21, 22]

Decision Constraints


[1]	Due to potential information security risks, cloud based versions of this product are not permitted without a waiver signed by the Deputy CIO of ASD based upon a recommendation from the Architecture and Engineering Review Board (AERB). In addition, cloud based features of this software may not be used without an Enterprise Security Change Control Board (ESCCB) approval to ensure that confidential organization and/or PII/PHI data are not compromised (ref: VA Directive 6004, VA Directive 6517 and VA Directive 6513). Use of public cloud storage requires documented Federal Risk and Authorization Management Program (FedRAMP) compliance and a Memorandum of Understanding / Interconnection Security Agreement (MOU/ISA) between the vendor and VA prior to ESCCB review.

[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]	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]	Due to potential information security risks, cloud based technologies may not be used without an Enterprise Security Change Control Board (ESCCB) approval. This body is in part responsible for ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[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]	Due to potential information security risks, cloud based technologies may not be used without the approval of the VA Enterprise Cloud Services (ECS) Group. This body is in part responsible for ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[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]	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]	Due to potential information security risks, cloud based technologies may not be used without the approval of the Enterprise Cloud Solution Office (ECSO). This body is in part responsible for ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[10]	Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request with the Project Special Forces (SPF) team, please use their online form. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[11]	Users must ensure that Firefox, Microsoft Internet Explorer (IE), and Microsoft Internet Information Services (IIS) are implemented within VA-approved baselines.

[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]	Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request with the Project Special Forces (SPF) team, please use their online form. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

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

[15]	Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request with the Project Special Forces (PSF) team, please use their online form. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[16]	Users must ensure that Google Chrome, Firefox, Microsoft Internet Explorer (IE), Microsoft Internet Information Services (IIS), Oracle Database, Microsoft Structured Query Language (SQL) Server, and Apache Hypertext Transfer Protocol (HTTP) Server are implemented within VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) This technology must use the latest TRM-approved version of Java Development Kit (JDK) - Oracle. Users must Divest the use of Internet Explorer with this technology. Other approved internet browsers are available. See Category Tab for details.

[17]	Due to potential information security risks for cloud-based technologies, users should coordinate closely with their facility ISSO for guidance and assistance on cloud products. If further guidance is needed contact the Enterprise Cloud Solution Office (ECSO), which is the body responsible for new software development in and migration of existing systems to the VA Enterprise Cloud (VAEC) and ensuring organizational information, Personally Identifiable Information (PII), Protected Health Information (PHI), and VA sensitive data are not compromised within the VAEC. For information about Software as a Service (SaaS) products or to submit a SaaS product request with the VA OIT Product Engineering team, please use their online form. (Ref: VA Directive 6004, VA Directive 6517, VA Directive 6513 and VA Directive 6102).

[18]	Users must ensure that Microsoft Internet Information Services (IIS), Oracle Database, Microsoft Structured Query Language (SQL) Server, and Apache Hypertext Transfer Protocol (HTTP) Server are implemented within VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) This technology must use the latest TRM-approved version of Java Development Kit (JDK) - Oracle. Users must utilize approved internet browsers, as Microsoft Internet Explorer has reached End of Life status. See Category Tab for details.

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

[21]	Users must ensure that Google Chrome, Firefox, Microsoft Edge, Microsoft Internet Information Services (IIS), Oracle Database, Microsoft Structured Query Language (SQL) Server, RedHat Enterprise (Linux), and Apache Hypertext Transfer Protocol (HTTP) Server are implemented within VA-approved baselines. (refer to the ‘Category’ tab under ‘Runtime Dependencies’) This technology must use the latest TRM-approved version of Java Development Kit (JDK) - Oracle. Users must utilize approved internet browsers, as Microsoft Internet Explorer has reached End of Life status. See Category Tab for details. Users must not utilize the Secure Sockets Layer (SSL) protocol, as it is unapproved for use on the TRM.

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

Note:

At the time of writing, version 2023.1 is the most current version released on 10/03/2023.

The following reference(s) are associated with this entry:
Type	Name	Source	Description
Vendor Provided*	Documentation	Publicly Available	This webpage offers an extensive library of the technical specifications for the HealthShare technology.
Vendor Provided*	What's New in 2023.1	Publicly Available	This site provides updated information for the latest release of this technology.
*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
HealthShare Connect	HealthShare Health Connect is an enterprise service bus (ESB) component created for rapid integration associated with messaging engines.
HealthShare Health Informatics Platform	HealthShare Health Informatics Platform is composed of an enterprise-scale database, data management, connectivity, messaging, user interface frameworks, and analytics technology. This module is used for building health informatics solutions.
HealthShare Health Insight	HealthShare Health Insight is used to add an analytics data model, infrastructure, and starter sets to HealthShare Information Exchange.
HealthShare Information Exchange	HealthShare Information Exchange provides the functionality and technology needed to build a standards-based health information exchange. The application enables secure sharing of composite clinical records and financial claims on demand. The module also facilitates clinical alerts for members of the patient`s care team and provides health managers with views of the patient populations they care for.
HealthShare Patient Index	HealthShare Patient Index is an automated identity management solution. The module can recognize the creation of a duplicate record and trigger corrective action to prevent medical errors or adverse events. Within an information exchange, advanced probabilistic and deterministic logic supports the automatic creation of multi-source, comprehensive patient records.
HealthShare Personal Community	HealthShare Personal Community is used in combination with HealthShare Information Exchange to provide a portal for patients. Patients are able to view, download and transmit their composite medical record, send secure messages to providers and request services. Family members and others authorized by the patient can be granted access to their medical record.
HealthShare Referral Manager	HealthShare Referral Manager is a referral management solution, designed to provide full lifecycle management of electronic and paper-based referrals. HealthShare Referral Manager enables staff to complete all the steps needed to move a Referral from receipt through to contracting for service and/or treatment delivery. Referral Manager also provides tools and workflows that help staff review received Referral Requests which can, when completed and approved, be allocated to the necessary healthcare organization or facility for service delivery. HealthShare Referral Manager is currently not listed on the InterSystems website.


Health Care Administrative	Health Delivery Support
Health Care Health Services	Medicine Services

- The information contained on this page is accurate as of the Decision Date (10/10/2023 at 16:08:25 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 (10/05/2023)

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 (10/05/2023)

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