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

Advisory: ODS Not Storing Observations When Terminology Translations Are Used

June 30, 2020 – Advisory: ODS Not Storing Observations When Terminology Translations Are Used

InterSystems has corrected a defect that may be experienced if a terminology mapping profile is in use for Observations. The Operational Data Store (ODS) does not correctly process the terminology translation. As a result, no streamlet or FHIR resource is stored in the ODS for the affected Observation.  Once the fix is applied, there is no conversion task or backload required; the next time an affected record is queried via the ODS, the correct data will be returned.

This issue has been classified as a Patient Safety Risk as it affects the availability of patient data.

This problem exists for:

  • HealthShare Unified Care Record 2019.1 and 2019.1.2

The correction for this defect is identified as dev key MCZ114 and will be included in all product releases starting with HealthShare 2019.2 and later. It is also available via Adhoc change file (patch) or full kit distribution from the Worldwide Response Center (WRC).

If you have any questions regarding this advisory, please contact the 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 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.