Skip to content
Search to learn about InterSystems products and solutions, career opportunities, and more.

Alert: HS2020-03: Multiple HealthShare Alerts

March 25, 2020

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

There are 7 alerts in the HealthShare HS2020-03 Alert communication, including the previously posted " Alert: Possible Data Integrity Issues after Compaction or Defragmentation"  The Alert Summary is in the table below, and the detail is contained in the attached document: HS2020-03-Communication

AlertProduct & Versions AffectedRisk Category & Score
HS2020-03-01: Break-the-Glass Events not Properly Audited for ODSHealthShare Unified Care Record 2019.1 and 2019.2 using the Operational Data Store4-High Risk (Privacy)
HS2020-03-02: Archiving of Historical Aliases Causes System HangHealthShare Patient Index 2018.1, 2019.1, and 2019.23-Medium Risk (Operational)
HS2020-03-03: Permissions to Access Patient Records Vary Between Clinical Viewer v1 and v2HealthShare Information Exchange and Unified Care Record v2 viewer in 2018.1, 2019.1 and 2019.24-High Risk (Privacy)
HS2020-03-04: Invalid Handling of Improperly Formatted Reference Ranges in HL7 V2 Result MessagesHealthShare Information Exchange 15.03 and 2018.1; Unified Care Record 2019.1 and 2019.23-Medium Risk (Clinical)
HS2020-03-05: AngularJS 1.5.8 VulnerabilityAll versions of HealthShare Personal CommunityExternal (Security)
HS2020-03-06: “LogCounter” in Access Gateway is Reset on UpgradeAll versions of HealthShare Information Exchange and Unified Care Record up to and including 2019.13-Medium Risk (Operational)
HS2020-03-07: Possible Data Integrity Issues after Compaction or Defragmentation

All HealthShare products starting from HealthShare 15.x and Personal Community 12.x and above.

HealthShare Health Connect 2019.1.0 and 2019.1.1 based on InterSystems IRIS®, and older Health Connect versions built on Cache/Ensemble 2016.2 and above.

2-Low Risk (Operational)

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

RELATED TOPICS

Latest Alerts & Advisories

Aug 15, 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.
Jul 25, 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.
Jun 24, 2024
Broadcom recently announced a problem that can cause data consistency errors in database applications. The Broadcom article is available here:
May 30, 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.
May 01, 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.
Apr 09, 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.
Mar 19, 2024
In evaluating an IBM Support notification, InterSystems has determined a potential impact for our customers. The notification in question is:
Feb 27, 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.
Feb 01, 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.