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

Advisory: Using Browser Back Button may result in user seeing two patients data at once in Classic Clinical Viewer

December 3, 2020 – Advisory: Using Browser Back Button may result in user seeing two patient's data at once in Classic Clinical Viewer

InterSystems has identified an issue affecting the Classic Clinical Viewer, when users use the back button in a specific sequence.

This problem exists for:

  • HealthShare Unified Care Record 15.03x, 2018.1.x, 2019.1.x, 2019.2.x
  • HealthShare Clinical Viewer 2020.1.x, 2020.2.x

This issue occurs when users use the browser back button within the Classic Clinical Viewer in this precise sequence:

  1. Access patient A through Patient Search Results page
  2. On Clinical Summary of patient A, select Patient Search
  3. Select patient B
  4. When on Clinical Summary of Patient B, click browser back button twice (now user will be on the Clinical Summary for Patient A)
  5. Select "View Summary"  "Download Summary"  or "Send Summary": Data for Patient B appears
  6. The patient identifiers and data matching are consistent (i.e. Patient A data displays with Patient A identifiers Patient B data displays with Patient B identifiers).

This issue requires the user to follow the precise workflow above as outlined and only occurs in the Classic Clinical Viewer. It does not occur in the Clinical Viewer. InterSystems recommends all users review patient identifiers when viewing patient data in either the Classic Clinical Viewer or the Clinical Viewer.

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.