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: Health Insight Data Can Point to the Wrong Patient's Encounter

This problem affects the following products:

  • All versions of Health Insight up to and including 2021.2

Many types of clinical data – such as diagnoses, documents, and observations – point back to a particular encounter. When clinical data is fed into Health Insight, it is usually accompanied by the relevant encounter data as well, and the resulting Health Insight relational data table entry will have a pointer to its encounter. For example, an HSAA.Diagnosis entry will have an Encounter property that points to the HSAA.Encounter entry that it relates to.

However, there are certain cases where Health Insight can receive clinical data without the relevant encounter data. In these cases, Health Insight will search through its existing collection of encounters and find one that matches. If the data source does not enforce uniqueness of encounters based on Facility and EncounterNumber, the incoming clinical data can end up pointing to the encounter of another patient.

The impact of this issue depends on how you are structuring your queries; if your queries are dependent on the Encounter field of the clinical data, then you may be affected by this issue.

If you are affected by this issue, contact the Worldwide Response Center to request an ad hoc correction for this issue, HSHI-6196, and apply the adhoc to your Health Insight instance. The correction will include a code change that will prevent the issue going forward and a utility that can identify and correct existing bad entries.

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.