March 23, 2020 – Multiple HealthShare Advisories

Primary tabs

This message contains three recent HealthShare Advisories, which are available below.

These advisories are also on the InterSystems Product Alerts and Advisories page

  • Advisory: Patient data is missing in the HSAA.PatientNumber table
  • Advisory: The UpdatePlan for all cubes and cube groups is set to be Manual instead of BuildSynch
  • Advisory: Slow DELETE query during Health Insight data ingestion

March 23, 2020 – Advisory: Patient data is missing in the HSAA.PatientNumber table

InterSystems has corrected a defect affecting how existing Patient data is handled during a Health Insight upgrade.

This problem exists for:

  • HealthShare Health Insight customers upgrading from 15.03 to 2018.1 or above.

This defect occurs when Health Insight customers upgrade from version 15.03 to a newer Health Insight version.  Starting with HealthShare Unified Care Record 2018.1, there is a new table called HSAA.PatientNumber that stores a variety of identifiers or numbers associated with a patient.

An issue was identified for customers upgrading from Health Insight 15.03 to a later version where data from preexisting patients did not populate the new table as expected. Instead, the 'Number' and 'NumberType' fields for preexisting patients were empty.

The fix populates all fields in the HSAA.PatientNumber table as intended. Health Insight customers upgrading to UCR 2019.1.2 will have the option to run this post-activation step in a deferred manner as a background job after the upgrade is completed and when the instance is in normal operations (e.g., ingesting data into Health Insight). Customers who have upgraded to UCR 2019.1 will need to re-run this step as a background job.

This issue does not impact new data that is coming into HealthShare's Information Exchange or Unified Care Record after the upgrade. The issue only impacts patient data that existed prior to the upgrade.

This issue is resolved starting with version 2019.1.2. Customers using earlier versions of Health Insight can request an Ad hoc .

The corrections for this issue are identified as TH1299, BAW136, BAW138, which will be included in product releases starting with Health Insight 2020.1. They are also available via Ad hoc change files (patch) or full kit distribution from the Worldwide Response Center (WRC).

March 23, 2020 – Advisory: The UpdatePlan for all cubes and cube groups is set to be Manual instead of BuildSynch

InterSystems has corrected a defect affecting the UpdatePlan setting and how often all cubes are built and synchronized.

This problem exists for:

  • HealthShare Health Insight customers upgrading from 15.03 to 2018.1 or above.

When a Health Insight customer is upgrading from Health Insight version 15.03 to a later version of Health Insight, the Cube Registry UpdatePlan should be set to “Manual”, which allows Health Insight to manage cube updates during and after the upgrade process.

However, if the HSAA.CubeRegistry has all of the cubes using a "BuildSynch" UpdatePlan, when the Registry is activated (either by a user or as one of the Upgrade Steps), a task will be created that schedules all cubes to be built once per week and synchronized once per day, which does not allow Health Insight to manage updates.

Setting the Cube Registry UpdatePlan to “Manual” resolves this issue.

Starting with version Health Insight 2019.1.2, the UpdatePlan for all cube groups and cubes in Health Insight is correctly set to Manual.

The correction for this defect is identified as HSHI-3350 and will be included in all future product releases. It is also available via Ad hoc change file (patch) or full kit distribution from the Worldwide Response Center (WRC).

March 23, 2020 – Advisory: Slow DELETE query during Health Insight data ingestion

InterSystems has corrected a defect affecting the population of Health Insight data.

This problem exists for:

  • HealthShare Health Insight customers upgrading from 15.03 to 2018.1 or above.

An issue was reported by a customer upgrading from Health Insight 15.03 to Health Insight 2019.1.  Their Health Insight instance had over 227 million records in the HSAA.Observation Table, whereas the HSAA.Outcome table was empty. The delete query was taking an average of 67 seconds (to delete zero records). This resulted in a large queue on the HSAA.TransferSDA3.Operation.Transfer component that was processing very slowly, causing Health Insight data ingestion to be slowed.

An Ad hoc software fix is available to correct this issue.

The correction for this defect is identified as AK1005 and will be included in all future product releases starting with Health Insight 2019.1.1. It is also available via Ad hoc change file (patch) or full kit distribution from the Worldwide Response Center (WRC).

If you have any questions regarding these advisories, please contact the Worldwide Response Center (WRC).