This post is part of the HealthShare HS2022-01 Alert communications process.  The same information is also distributed:

• By Email
• On the Product Alerts & Advisories page
• On the WRC Distribution Page InterSystems Documents

There are 22 alerts in the HealthShare HS2022-01 Alert communication.

Dear HealthShare Customer:

This post is part of the HealthShare HS2021-03 Alert communications process.

February 11, 2021 – Advisory: Incomplete Query Results with ‘ORDER BY <row ID field> DESC’ – HealthShare

InterSystems has corrected a defect that can cause incomplete query results.  This defect affects the platforms underlying HealthShare and HealthShare Health Connect:

• InterSystems IRIS and InterSystems IRIS for Health 2019.1.0, 2019.1.1, and 2020.1.0

See Alert: Incomplete Query Results with ‘ORDER BY <row ID field> DESC’ for further detail

Customers using HealthShare Personal Community should evaluate the number of proxy relationships they have established or removed.

Dear HealthShare Customer:

This post is part of the HealthShare HS2020-09 Alert communications process.  The same information is also distributed:

• By Email
• On the Product Alerts & Advisories page
• On the WRC Distribution Page InterSystems Documents

There are 3 alerts in the HealthShare HS2020-09 Alert communication.

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

Dear HealthShare Customer:

This post is part of the HealthShare HS2020-08 Alert communications process.  The same information is also distributed:

• By Email
• On the Product Alerts & Advisories page
• On the WRC Distribution Page InterSystems Documents

There are 2 alerts in the HealthShare HS2020-08 Alert communication, and outlined in the Alert Summary table below.  The detail is contained in the attached document: HealthShare HS2020-08.

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

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

September 1, 2020 – Advisory: Consent API allows for the creation of consent policies for non-existing MPI IDs

InterSystems has corrected a defect when using the Consent API, where it is possible to associate a consent policy with an MPI ID that does not yet exist.

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

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.

This defect only affects FHIR resources at the HealthShare ODS.

Dear HealthShare Customer:

This post is part of the HealthShare HS2020-06 Alert communications process.  The same information is also distributed:

• By Email
• On the Product Alerts & Advisories page
• On the WRC Distribution Page InterSystems Documents

There are 2 Health Insight alerts in the HealthShare HS2020-06 Alert communication.

Dear HealthShare Customer:

This post is part of the HealthShare HS2020-05 Alert communications process.

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

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

• Advisory: A manager from one facility could view users from another facility
• Advisory: Significant Performance Issues with ListEncounterRelationships()
• Advisory: The Lab Results Table in Clinical Viewer does not display "IM" results.

HealthShare 2020.1 is now Generally Available!

The 2020.

Dear HealthShare Customer:

This post is part of the HealthShare HS2020-04 Alert communications process.

Dear HealthShare Customer:

This post is part of the HealthShare HS2020-03 Alert communications process.  The same information is also distributed:

• By Email
• On the Product Alerts & Advisories page
• On the WRC Distribution Page InterSystems Documents

There are 7 alerts in the HealthShare HS2020-03 Alert communication, including the previously posted "March 25, 2020 Alert: Possible Data Integrity Issues after Compaction or Defragmentation."  The summary is in the table below, and the detail is contained in the attached document: HealthShare HS2020-03.

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

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

We are pleased to announce the availability of HealthShare 2019.1.

The InterSystems FHIR® Sandbox is a virtual testing environment that combines HealthShare technology with synthetic patient data and open source and commercial SMART on FHIR apps, to allow users to play with FHIR functionality.

The sandbox is designed to enable developers and innovators to connect and test their own DSTU2 apps to multi-source health records hosted by the latest version of HealthShare.   Share your experience with others or ask questions here in the FHIR Implementers Group. 

Click here to access the InterSystems FHIR® Sandbox.