October 15, 2020 – Multiple HealthShare Advisories

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

• Advisory: FHIR Medication asNeededBoolean Not Always Correct
• Advisory: Clinical Viewer and Management Portal Log Out Synchronization Issue
• Advisory: Failure to access linkage engine libraries in Patient Index
• Advisory: Failure to access linkage engine libraries in Provider Directory

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

October 15, 2020 – Advisory: FHIR Medication asNeededBoolean Not Always Correct
InterSystems has corrected an issue that occurs in certain cases with the dosageInstruction.asNeededBoolean property of MedicationRequest and MedicationStatment.

This problem exists for Customers who use one of the following versions:

• HealthShare Unified Care Record 2019.1, 2019.2, 2020.1

When transforming SDA to FHIR, if certain conditions are met, the dosageInstruction.asNeededBoolean property of MedicationRequest and MedicationStatment may be improperly set to 0. This occurs when the instructions for the medication is listed as "PRN”, but the Dosage Steps in SDA are not populated.

The correction for this defect is identified as IF-910 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).

If you have any questions regarding this advisory, please contact the Worldwide Response Center (WRC) at support@InterSystems.com or  +1.617.621.0700.

October 15, 2020 – Advisory: Clinical Viewer and Management Portal Log Out Synchronization Issue
InterSystems has identified an issue that occurs when a user has the Management Portal and the v2 Clinical Viewer open in different tabs of the same browser and tries to log out.

This problem exists for Customers who use one of the following versions:

• HealthShare Information Exchange 2018.1
• HealthShare Unified Care Record 2019.1, 2019.1.2, 2020.1
• HealthShare Clinical Viewer 2020.1

When a user has one tab with the Management Portal and one tab with the v2 Clinical Viewer open, logging out of the Clinical Viewer tab does not log the user out of the Management Portal. InterSystems is working on a correction, in the meantime customers are reminded that users should log out through the Management Portal and always validate their session has ended.

If you have any questions regarding this advisory, please contact the Worldwide Response Center (WRC) at support@InterSystems.com or  +1.617.621.0700.

October 15, 2020 – Advisory: Failure to access linkage engine libraries in Patient Index

InterSystems has corrected an issue that may occur in certain UNIX environments running Patient Index.

This problem exists for Customers who use one of the following versions:

• HealthShare Patient Index 15.032, 2018.1 2019.1, 2019.2, 2020.1 running on UNIX platforms

This issue is limited to UNIX platforms that fail to load the linkage engine libraries on initial start-up. The problem appears to be limited to systems that are running on underpowered environments, such as test systems.

Linkage evaluations and linkage rebuilds may receive errors attempting to access the linkage engine library. These errors show up in the error log, and users can query to see if these errors have occurred in their environment.

To resolve this issue customers are advised to stop and restart the installed instance.

The correction for this defect is identified as SOH723 and will be included in all future product releases. If you have any questions regarding this advisory, please contact the Worldwide Response Center (WRC) at support@InterSystems.com or  +1.617.621.0700.

October 15, 2020 – Advisory: Failure to Access Linkage Engine Libraries in Provider Directory

InterSystems has corrected an issue that may occur in certain UNIX environments running Provider Directory.

This problem exists for Customers who use one of the following versions:

• HealthShare Provider Directory 2019.1, 2020.1 running on UNIX platforms

This issue is limited to UNIX platforms that fail to load the linkage engine libraries on initial start-up. The problem appears to be limited to systems that are running on underpowered environments, such as test systems.

Linkage evaluations and linkage rebuilds may receive errors attempting to access the linkage engine library. These errors show up in the error log, and users can query to see if these errors have occurred in their environment.

To resolve this issue customers are advised to stop and restart the installed instance.

The correction for this defect is identified as SOH723 and will be included in all future product releases.   If you have any questions regarding this advisory, please contact the Worldwide Response Center (WRC) at support@InterSystems.com or  +1.617.621.0700