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

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

Apr 17, 2025
InterSystems has addressed security vulnerabilities that impact applications using OAuth2 Client configurations on InterSystems IRIS, InterSystems IRIS for Health, HealthShare, HealthShare HealthConnect, TrakCare, Caché, and Ensemble. Remediation steps and additional guidance documentation are available from the InterSystems Worldwide Response Center (WRC).
Apr 02, 2025
Product & Versions Affected Explicit Requirements DP-439207 InterSystems IRIS® data platform 2024.3 (AIX) AIX installations Using JSON processing and Unicode non-Latin-1 character sets DP-439280 InterSystems IRIS 2024.3 (containers with IntegratedML) IntegratedML Containers using TensorFlow
Mar 04, 2025
This problem affects the following products:
Mar 04, 2025
This problem affects the following products: