Skip to content
Busque para obtener información sobre los productos y soluciones de InterSystems, las oportunidades de carrera y más.

Advisory: FHIR Searches that Specify a Time Range may Improperly Include or Exclude some Data

March 1, 2022 – Advisory: FHIR Searches that Specify a Time Range may Improperly Include or Exclude some Data

InterSystems has corrected a defect in Unified Care Record version 2020.1 and 2020.2 that could cause FHIR searches to improperly include or exclude dates from a time range.
This defect was due to FHIR "instant"-typed properties being indexed as strings instead of timestamps in the FHIR repository search tables, and therefore not being adjusted to UTC. A FHIR search that specifies a time range might therefore erroneously include or exclude some data.

The indexing of instant-typed properties has been fixed in Unified Care Record version 2021.1 and later versions. In addition, an ad hoc correction is available for customers on version 2020.2.

Customers on affected versions have several options for correcting this defect, depending on their current version:

If you are on version 2020.1, you must upgrade to correct this issue. You have two options:

  1. You may upgrade to Unified Care Record version 2021.1, where the issue is corrected. Reactivation of the ODS namespace after the upgrade will flag the appropriate FHIR repository search tables for re-indexing. After reactivation, navigate to Home > HealthShare > ODS > ODS Configuration > FHIR > Server Configuration. Select the "Reindex Now" links to trigger the re-indexing of the tables.
  2. You may upgrade only the ODS component to version 2020.2 and apply the ad hoc correction identified as IF-589. If you apply the correction, you must also flag and re-index the FHIR repository search tables that include instant-typed properties by following the instructions included with the ad hoc correction. Using version 2020.2 of the ODS component with version 2020.1 of Unified Care Record has been fully tested. Contact the InterSystems Worldwide Response Center (WRC) for details on this option.

If you are on version 2020.2, you have two options:

  1. You may upgrade to version 2021.1, where the issue is corrected. Reactivation of the ODS namespace after the upgrade will flag the appropriate FHIR repository search tables for re-indexing. After reactivation, navigate to Home > HealthShare > ODS > ODS Configuration > FHIR > Server Configuration. Select the "Reindex Now" links to trigger the re-indexing of the tables.
  2. You may apply an ad hoc correction identified as IF-589. If you apply the correction, you must also flag and re-index the FHIR repository search tables that include instant-typed properties by following the instructions included in the ad hoc correction.
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.
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.
Jan 17, 2024
This problem affects the following products: