Alerts

Syndicate content 4 

InterSystems has corrected a defect that can cause a build-up of orphaned processes consuming system resources. In extreme cases, this can cause a system to become unresponsive.

This defect affects the following versions:

20
0 1 172

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

  • Advisory: Consent API allows for the creation of consent policies for non-existing MPI IDs
  • Advisory: Issue with Consent Processing in the Operational Data Store

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

10
0 0 49

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

  • Advisory: ODS Not Storing Observations When Terminology Translations Are Used
  • Advisory: Composite Record Definition Must Reference Implemented Linkage Definition
  • Advisory: Potential for Outdated Terms of Use to be Presented in Personal Community

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

00
0 0 55

InterSystems has corrected a defect that can lead to missing resource data in FHIR search results.

This problem exists for:

  • HealthShare Unified Care Record 2020.1.0 b7015

This defect occurs due to an incorrect resource being deleted from the search index. Subsequent FHIR Resource requests against the FHIR Repository may return incomplete results due to that missing index. Any type of FHIR resource data can be lost, and depending on when the defect occurs, the same FHIR request could return different result sets.

00
0 0 54

InterSystems has corrected two defects that affect online backup of very large databases. Backups taken via external methods, such as snapshots or direct file copies, are not affected. These defects exist in all released versions of all InterSystems products.

20
0 0 93

InterSystems has corrected two defects that, in rare circumstances, can result in data integrity corruption after running global compaction, database compaction, or database defragmentation. InterSystems recommends avoiding these utilities until after applying the corrections listed below.

00
0 0 123

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

00
0 0 72
InterSystems Official
RB Omo · Mar 12, 2020
InterSystems COVID-19 Update

In light of the COVID-19 situation worldwide, InterSystems is working to ensure continuous support for our customers, promote the health and well-being of our employees, and protect the communities where we live and work. Please view our statement and frequently asked questions.

In addition, we have also established a special email address, COVID-19@InterSystems.com, should you have any questions or concerns.

As we have for 41 years, we stand by our commitment to customers and are prepared to support you during this challenging time.

Sincerely, 

John Paladino

Vice President, Client Services

60
0 0 178

InterSystems has corrected several critical defects that can result in data integrity issues. These defects were identified and corrected within a short time, so InterSystems has simplified the upgrade process by consolidating them into a single package. The effects of encountering these defects may not always be visible.

00
2 1 199

InterSystems has corrected a defect in applications that use Unicode character 223 (ß). This defect can result in incomplete query results, class compilation errors, and removal of custom SQL privileges.

This problem occurs on systems that are running or have previously run on:

  • Caché and Ensemble 2018.1.0, 2018.1.1, and 2018.1.2
  • HealthShare Health Connect (HSAP) 15.032 on Core versions 2018.1.0, 2018.1.1, and 2018.1.2
  • HealthShare Health Connect 2019.1
  • InterSystems IRIS data platform – all currently released versions
  • InterSystems IRIS for Health – all currently released versions

The defect is triggered by data and component names containing Unicode character 223 (ß). In the versions listed above, an uppercase conversion incorrectly maps that character to Unicode character 7838 (ẞ).  Applications perform this uppercase conversion using features such as $ZCONVERT and %SQLUPPER.

Problems can occur when accessing data or classes created or modified on a product with a different uppercase conversion than the one currently in use.

00
0 0 112

InterSystems has corrected a defect that could lead to invalid backups on Windows platforms. The defect causes upgrades to disable the EnableVSSBackup setting. By default, EnableVSSBackup is enabled (value set to 1) and the upgrade sets its value to 0. Windows VSS backups taken with this setting disabled may contain invalid CACHE.DAT files.

This problem is limited to Windows platforms on the following versions:

  • Caché and Ensemble 2018.1.0, 2018.1.1, and 2018.1.2
  • HealthShare Health Connect (HSAP) 15.032 on Core versions 2018.1.0, 2018.1.1, and 2018.1.2
  • HealthShare 2019.1 (Unified Care Record, Patient Index, Health Insight, Personal Community, and Provider Directory) on Core version 2018.1.2
  • HealthShare 2018.1 (Information Exchange, Patient Index, Health Insight, and Personal Community) on Core versions 2018.1.1 or 2018.1.0

The defect only occurs if you are upgrading to a version listed above. Once you have upgraded to an affected version, you must manually enable the setting; otherwise, it will be disabled on future upgrades, even when upgrading to versions containing the correction.

For customers using Windows VSS backups, InterSystems recommends enabling this setting on any 2018.1 instances of Caché or Ensemble. Once you have enabled the setting, future upgrades (including to affected versions) will preserve its value.

00
0 0 95