Skip to content
Use the search to find information about InterSystems products and solutions, career opportunities, and more.

Alert: HS2020-05: HealthShare Alerts

May 20, 2020

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

There are 3 alerts in the HealthShare HS2020-05 Alert communication, including the previously posted " Alert: Possible Data Integrity Issues with Online Backup of Large Databases."  The Alert Summary is in the table below, and the detail is contained in the attached document: HealthShare HS2020-05

Alert
HS2020-05-01: On an Android device that is in sleep mode, the standalone v2 Clinical Viewer using Chrome does not time out

Information Exchange 2018.1

Unified Care Record 2019.1, 2019.1.2, 2019.2

3-Medium Risk (Security)
HS2020-05-02: FHIR Request from ODS Not Logged in ATNA if Custom Pairs are Used on the Patient Streamlet

Information Exchange 2018.1

Unified Care Record 2019.1, 2019.2, 2020.1

3-Medium Risk (Privacy)
HS2020-05-03: Possible Data Integrity Issues with Online Backup of Large DatabasesAll versions of all InterSystems HealthShare products5-Very High Risk (Operational)

If you have any questions regarding this advisory, please contact the Worldwide Response Center (WRC).

RELATED TOPICS

Latest Alerts & Advisories

15 Aug 2024
InterSystems has corrected a defect that can cause database corruption or errors with multi-volume databases under extremely rare circumstances. Only databases that have been truncated are at risk.
24 Jul 2024
There are four alerts in the HS2024-03 Alert Communication. A summary of each alert is shown below. Details for each alert are contained in the linked document.
24 Jun 2024
Broadcom recently announced a problem that can cause data consistency errors in database applications. The Broadcom article is available here:
30 May 2024
Beginning with the release of InterSystems IRIS® data platform 2022.3, InterSystems corrected the license enforcement mechanism to include REST and SOAP requests. Due to this change, environments with non-core-based licenses that use REST or SOAP may experience greater license utilization after upgrading. To determine if this advisory applies to your InterSystems license, follow the instructions in the FAQ linked below.
01 May 2024
InterSystems has corrected an issue that can cause a small number of SQL queries to return incorrect results. See below for the specifics on impacted queries.
08 Apr 2024
InterSystems has encountered a defect that causes some upgrades of HealthShare® Health Connect to fail. This only affects instances that are not licensed for the use of FHIR® and that have interoperability-enabled namespaces. Under these conditions, the upgrade fails with an error.
19 Mar 2024
In evaluating an IBM Support notification, InterSystems has determined a potential impact for our customers. The notification in question is:
27 Feb 2024
There is 1 alert in the HealthShare HS2024-limited Alert communication. An alert summary for the issue is shown is in the table below. Details for the alert are contained in the attached document: HS2024 Limited Communication.
01 Feb 2024
There are 2 alerts in the HealthShare HS2024-02 Alert communication. An alert summary for each issue is shown is in the table below. Details for each alert are contained in the attached document: HS2024-02-Communication.