Skip to content
Telusuri untuk mempelajari tentang produk dan solusi InterSystems, peluang karier, dan banyak lagi.

Advisory: When Transformed into SDA, Planned Acts Do Not Contain Status and Effective Time

This problem affects the following products:

  • HealthShare Unified Care Record: all versions
  • HealthShare Health Connect: all versions
  • InterSystems IRIS for Health: all versions

CDA/CCDA documents can represent events that are planned to occur. For example, the Plan of Treatment CCDA 2.1 section is described as “contains data that define pending orders, interventions, encounters, services, and procedures for the patient. It is limited to prospective, unfulfilled, or incomplete orders and requests only.”

These Plan of Care/Treatment entries, when received in the CDA/CCDA, can be imported into SDA as an OtherOrder, Document, Appointment Streamlet(s), Procedure Streamlet(s), Medication Streamlet(s) or Goal Streamlet(s) depending on the type of information received in the “Plan of Care” and “Assessment and Plan” section of a C32/CCDA1.1 Document or a “Plan of Treatment” and “Assessment and Plan” section of a CCDA2.1 document.

Currently HealthShare does not record the effectiveTime or Status for such planned entries in the SDA. A clinical safety risk arises when for example, a procedure is planned but not yet ordered; no ‘status’ is recorded in SDA. When the planned date has passed the system simply displays the date with no indication that the procedure (or other event) has actually occurred.

A fix is not yet available for this issue.

Affected customers may contact InterSystems Worldwide Response Center (WRC) for assistance regarding this advisory and reference HSIEC-6954.

Latest Alerts & Advisories

15 August, 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.
25 July, 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.
24 June, 2024
Broadcom recently announced a problem that can cause data consistency errors in database applications. The Broadcom article is available here:
30 May, 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.
01 May, 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.
08 April, 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.
19 March, 2024
In evaluating an IBM Support notification, InterSystems has determined a potential impact for our customers. The notification in question is:
27 February, 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.
01 February, 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.
17 January, 2024
This problem affects the following products: