#InterSystems Official

InterSystems has corrected a defect that can result in skipping a transaction rollback. This can only occur after activation or addition of a mirrored database on a primary mirror member.

Dear HealthShare Customer:

This post is part of the HealthShare HS2020-08 Alert communications process. The same information is also distributed:

InterSystems has corrected a defect that could lead to invalid backups on Windows platforms. The defect causes upgrades to disable the EnableVSSBackup setting. By default, EnableVSSBackup is enabled (value set to 1) and the upgrade sets its value to 0. Windows VSS backups taken with this setting disabled may contain invalid CACHE.DAT files.

This problem is limited to Windows platforms on the following versions:

• Caché and Ensemble 2018.1.0, 2018.1.1, and 2018.1.2
• HealthShare Health Connect (HSAP) 15.032 on Core versions 2018.1.0, 2018.1.1, and 2018.1.2
• HealthShare 2019.1 (Unified Care Record, Patient Index, Health Insight, Personal Community, and Provider Directory) on Core version 2018.1.2
• HealthShare 2018.1 (Information Exchange, Patient Index, Health Insight, and Personal Community) on Core versions 2018.1.1 or 2018.1.0

The defect only occurs if you are upgrading to a version listed above. Once you have upgraded to an affected version, you must manually enable the setting; otherwise, it will be disabled on future upgrades, even when upgrading to versions containing the correction.

For customers using Windows VSS backups, InterSystems recommends enabling this setting on any 2018.1 instances of Caché or Ensemble. Once you have enabled the setting, future upgrades (including to affected versions) will preserve its value.

InterSystems has corrected a defect that can cause FHIR searches to return incomplete results. The defect manifests because a FHIR update interaction deletes an incorrect resource from the search index.

February 11, 2021 – Advisory: Incomplete Query Results with ‘ORDER BY <row ID field> DESC’ – HealthShare

InterSystems has corrected a defect that can cause incomplete query results. This defect affects the platforms underlying HealthShare and HealthShare Health Connect:

This message contains two recent HealthShare Advisories, which are available below.

• Advisory: Consent API allows for the creation of consent policies for non-existing MPI IDs
• Advisory: Issue with Consent Processing in the Operational Data Store

These advisories are also on the InterSystems Product Alerts and Advisories page

InterSystems has corrected two defects regarding connectivity. These defects and their corrections are independent of each other.

This alert addresses them both because there are point releases containing both corrections.

This message contains three recent HealthShare Advisories, which are available below.

These advisories are also on the InterSystems Product Alerts and Advisories page

Dear HealthShare Customer:

This post is part of the HealthShare HS2020-09 Alert communications process. The same information is also distributed:

InterSystems has corrected a defect that can lead to missing resource data in FHIR search results.

This problem exists for:

• HealthShare Unified Care Record 2020.1.0 b7015

This defect occurs due to an incorrect resource being deleted from the search index. Subsequent FHIR Resource requests against the FHIR Repository may return incomplete results due to that missing index. Any type of FHIR resource data can be lost, and depending on when the defect occurs, the same FHIR request could return different result sets.

Dear HealthShare Customer:

This post is part of the HealthShare HS2020-03 Alert communications process. The same information is also distributed:

This message contains four recent HealthShare Advisories, which are available below.