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.