Skip to content
Puede usar nuestro buscador para encontrar información sobre los productos y soluciones de InterSystems, las oportunidades de desarrollo profesional, los casos de uso, novedades y mucho más.

Advisory: HS.Stream Global in Edge Gateways Not Cleared After Errors

March 1, 2022 – Advisory: HS.Stream Global in Edge Gateways Not Cleared After Errors

InterSystems has corrected a defect where an unsuccessful patient registration does not clear data written to the HS.Stream global in Edge Gateway namespaces. This global can grow over time, fill up storage, and potentially cause system stability issues.

This defect affects all HealthShare Information Exchange/Unified Care Record versions up to and including HealthShare 2021.1.

Data is written to the HS.Stream global in Edge Gateway namespaces when registering a patient in the Registry. If the registration is successful, the data is cleared for that session. However, if the registration is unsuccessful, the data is not cleared. As a result, the HS.Stream global will grow, causing a potential system stability concern if it fills up the storage on the Edge Gateway's server.

Customers who frequently encounter errors in patient registration are more likely to be impacted by this issue. Routine monitoring of disk space helps to reduce the likelihood of encountering system stability issues. For information on monitoring disk space, see the HealthShare Monitoring and Operations Guide (specifically the Monitor Disk Space section).

The correction for this defect is identified as HSIEC-5002. It is available via Ad hoc change file (patch) or full kit distribution from the Worldwide Response Center (WRC). The correction ensures that the global data is cleared after errors are encountered. InterSystems recommends that customers running an affected version apply this correction. This correction was included in HealthShare 2021.2 and all future product releases.

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 24 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 08 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.