Skip to content
Pesquise para saber mais sobre produtos e soluções da InterSystems, oportunidades de carreira e muito mais.

Advisory: UTC timestamps stored in Health Insight are Incorrect for a Certain Input Timestamp Format

This problem affects the following products:

  • HealthShare Health Insight 2021.1 and 2021.2

Health Insight 2021.1 introduced support for time zone offsets by adding additional UTC timestamped fields to most datetime fields. Health Insight correctly populates the UTC timestamped fields for most input timestamp formats:

  • YYYY-MM-DDThh:mm:ssZ, such as 2020-12-18T11:30:00Z
  • YYYY-MM-DDThh:mm:ss-TimezoneOffset, such as 2020-12-18T11:30:00-04:00
  • YYYY-MM-DDThh:mm:ss+TimezoneOffset, such as 2020-12-18T11:30:00+05:00

However, Health Insight fails to account for incoming timestamps in the format:

  • YYYY-MM-DDThh:mm:ss, such as 2020-12-18T11:30:00

For these type of timestamps, the UTC value will be identical to the original value, which is incorrect. The correct UTC time should have the timezone offset taken into account, either coming from the facility's specific timezone or the system default timezone.
This behavior has been resolved in Health Insight 2022.1.

If you are affected by this issue, contact the Worldwide Response Center (WRC) to request an ad hoc correction for this issue, HSHI-5892, and apply the adhoc to your Health Insight instance and your Feeder gateway instance.

Applying the ad hoc correction will prevent this issue going forward – any new incoming data will have correct UTC timestamps. Any old data will still retain the erroneous UTC timestamps. Erroneous UTC data for a patient will be corrected any time there is a full resend of the patient.

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 30, 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.