InterSystems Official Mike Morrissey · Mar 1, 2022

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

There are 22 alerts in the HealthShare HS2022-01 Alert communication.  The Alert Summary is in the table below, and the detail is contained in the attached document: HS2022-01-Communication

2
0 469
InterSystems Official Mike Morrissey · Mar 23, 2021

Dear HealthShare Customer:

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

0
0 222
InterSystems Official Mike Morrissey · Feb 11, 2021

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

0
0 239
InterSystems Official Mike Morrissey · Dec 22, 2020

Dear HealthShare Customer:

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

There are 3 alerts in the HealthShare HS2020-09 Alert communication.  The Alert Summary is in the table below, and the detail is contained in the document: HS2020-09-Communication

0
0 195
InterSystems Official Mike Morrissey · Oct 16, 2020

Dear HealthShare Customer:

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

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.

These alerts do not affect HealthShare Health Connect or HSAP customers

0
0 246
InterSystems Official Mike Morrissey · Oct 15, 2020

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

0
0 162
InterSystems Official Mike Morrissey · Sep 1, 2020

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

0
0 229
InterSystems Official Mike Morrissey · Jun 30, 2020

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

June 30, 2020 – Advisory: ODS Not Storing Observations When Terminology Translations Are Used

0
0 276
InterSystems Official Mike Morrissey · Jun 4, 2020

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.

0
0 183
InterSystems Official Mike Morrissey · Jun 3, 2020

Dear HealthShare Customer:

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

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

0
0 175
InterSystems Official Mike Morrissey · May 20, 2020

Dear HealthShare Customer:

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

There are 3 alerts in the HealthShare HS2020-05 Alert communication, including the previously posted "Alert: Possible Data Integrity Issues with Online Backup of Large Databases"  The Alert Summary is in the table below, and the detail is contained in the attached document: HS2020-05-Communication

0
0 268
InterSystems Official Mike Morrissey · May 12, 2020

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.

May 12, 2020 - Advisory: A manager from one facility could view users from another facility

0
0 234
InterSystems Official Mike Morrissey · Apr 2, 2020

Dear HealthShare Customer:

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

There are 3 alerts in the HealthShare HS2020-04 Alert communication, including the previously posted "Alert: Possible Data Integrity Issues after Adding Mirrored Database"  The Alert Summary is in the table below, and the detail is contained in the attached document: HS2020-04-Communication

0
0 205
InterSystems Official Mike Morrissey · Mar 25, 2020

Dear HealthShare Customer:

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

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.

0
0 170
InterSystems Official Mike Morrissey · Mar 23, 2020

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
0
0 375
Announcement Mike Morrissey · Mar 7, 2018

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.

0
0 706