#Health Connect

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.

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

InterSystems has corrected a defect that can cause incomplete query results. This defect affects:

• InterSystems IRIS and InterSystems IRIS for Health 2019.1.0, 2019.1.1, 2019.2, 2019.3, 2019.4, 2020.1.0, 2020.2, and 2020.3
• HealthShare Health Connect 2019.1.0, 2019.1.1, 2020.1.0
• HealthShare Products 2019.2, 2020.1 and 2020.2

(In HealthShare and HealthShare Health Connect, this defect only affects Personal Community with 64,000 patient proxies and possibly customer-built custom queries.

How to implement transaction processing when using healthConnect to link external data for data operation

At present, the SNMP information provided in healthConnect can not meet the needs of users. How to extend the SNMP Library of the program

Built in multi model integration using InterSystems iris data platform

Solution of hospital information inquiry business

Integration of hospital information query business solutions using InterSystems IRIS data platform with built-in multiple models

### Summary:

With the gradual improvement of hospital information construction, there are more and more hospital subsystems, and more and more interfaces between systems. At the same time, the interface cost is increasing, and the management work is becoming more and more complex.

Is it possible to move data from i2b2 (https://community.i2b2.org) to IRIS (for example to Health Connect 2019) platform?

Does anybody have such experience?

In 2020 we implemented HealthConnect as our HL7 interface engine.  Having completed this, we are currently evaluating whether it would be beneficial to migrate our managed file transfers from our current MFT software, MOVEit to HealthConnect.  I am interested in hearing from any InterSystems customers who have previously used MOVEit and currently using HealthConnect for file transfer managment.  Any feedback would be appreciated.

Hi fellows,

I'm glad to share with you my new certification:

https://www.youracclaim.com/badges/3aa7dd58-9f94-417e-92de-2d62c6c477bb…

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

InterSystems has corrected a defect that may cause Windows Telnet processes that are secured using SSL/TLS to hang indefinitely; this may then cause an instance to become unresponsive. This defect is present only on Windows platforms.

This defect affects:

• Caché and Ensemble 2018.1.4
• HealthShare Health Connect (HSAP) 15.032 built on C/E 2018.1.4
• InterSystems IRIS and InterSystems IRIS for Health 2020.3

The problems caused by this defect can occur only when the instance is running Windows Telnet.

we are getting number of msgs from multiple facilities into our HIE solution, now which facilities is sending bad quality data and put some process around it to improve the msg quality

so where to start to generate this report, any guidance would be appreciated. 

My team is working on redesigning an Interoperability solution that currently runs on a HealthShare server that is part of a mirror. Most of the messages are delimited records processed using Complex Record Mapping. We were told to utilize cloud services available in AWS, use containers, autoscaling…

Once we figured out how to use Docker, we imported the Health Connect code in multiple containers with a shared Elastic File System with the directory structure we copied from the existing server.

Hi All,

  I know hundreds of people have done this but I'm looking for some DTL's as a start to do HL7 to FHIR, I appreciate everyone's HL7 is slightly different, but just some starter DTL's would be much appreciated?  Can anyone help?

  Regards

Hi 

Has anyone used Health Connect/Ensemble to receive results directly from POCT devices (Glucose monitors etc)?

I've been looking for information on the POCT01-A  protocol, and as far as I can tell it is a HL7v3 XML schema, I should be able to get results from these devices, though I expect I need a webserver endpoint. (though I can't find any reference in the Health Connect documentation)

Does anyone have any knowledge of this?

KR

Stephen

EDIT:  from the silence I'm wondering if this in normally handed off to specialist middleware?

Hi Developers and Interface Engineers!

I'd like to share with you how you can help your organization today obtain a better understanding of key message processing metrics (i.e. average message processing times, number of inbound messages, number of outbound messages, etc.)! Given the embedded IRIS database powering integration, you already have all the data you need -- you just need to put the data to use and present them in a user-friendly format!

Hello!

First of all, let me state that I am no senior InterSystems expert. 

In my organization, we have a HealthShare Health Connect setup where each namespace has one code database and one data database, which are both actively mirrored. We have two nodes in the mirror.

We had a controlled failover last night to make sure that the backup node works as intended, which it didn't. It turned out that we had only deployed code onto the primary node in several namespaces causing errors with missing classes after the failover.

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.

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:

• Caché and Ensemble 2018.1.4
• InterSystems IRIS and InterSystems IRIS for Health 2019.4, 2020.1, and 2020.2
• HealthShare Health Connect (HSAP) 15.032 built on Ensemble 2018.1.4
• HealthShare Health Connect 2020.1

No other InterSystems product versions are affected by this issue.  Specifically, earlier versions of Caché and Ensemble, Health Connect 2019.1 and 2019.1.

Hi all,

a HealthConnect customer of ours came across with a question to use an external service via REST and OpenID within one of his HealthConnect  (2020.1) productions. The overal idea is to send data to the external system after receiving a baerer token to use for the communication between HealthConnect and this system.

Since I´ve never done such thing before I have an idea to solve this task but looking for a best practise way to do so. Using the RESt-Api of the external system is not the question here.

Hello,

I am using a class based on %UnitTest.TestProduction to test Health Connect production.

I read in Class Reference IRIS for UNIX 2020.1:

Note: This class is not intended to be used in InterSystems IRIS instances.

Why should this not be used in IRIS? I have not seen any difference using this with HealthConnect 2017 or IRIS 2020.1

Hi Community,

The new video from Global Summit 2019 is already on InterSystems Developers YouTube:

⏯ InterSystems Health Connect: New and Next

In this article I'd like to share with you a phenomena that is best you avoid - something you should be aware of when designing your data model (or building your Business Processes) in Caché or in Ensemble (or older HealthShare Health Connect Ensemble-based versions).

Hi,

I have a HealthShare HealthConnect operation which uses the EnsLib.HTTP.OutboundAdapter. It is using a custom Operation class to send HTTP Post request. The request data that is sent to the operation and the response back from the operation is not  displayed on the visual trace. Is there anyway to display this data in the trace? 

Thank you for your help. 

Hi everyone,

Are there any tools to check the code coverage and to do a lint check for cache object script? Developers will be working with HealthConnect (IRIS based)

Thanks.

A releases are now published for the 2020.1 version of HealthShare Health Connect!

Kits and Container images are available via the WRC's WRC Software Distribution site.

The build number for these releases is 2020.1.0.215.0.

HealthShare Health Connect 2020.

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.

The 2019.4 versions of InterSystems IRIS, InterSystems IRIS for Health, and InterSystems IRIS Studio are now Generally Available!

These releases are available from the WRC Software Distribution site, with build number 2019.4.0.383.0.

InterSystems IRIS Data Platform 2019.4  has many new capabilities including:

• New Automatic Configuration Customization
• System security, performance, and efficiency enhancements including node tables
• ICM support for Tencent Cloud
• List Class available in the Native API for Java and .

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

Preview releases are now available for the 2020.1 version of HealthShare Health Connect!

Kits, Container images, and evaluation keys are available via the WRC's preview download site.

The build number for these releases is 2020.1.0.199.0.  (Note: first release was build 197, updated to 199 on 2/12/20)

HealthShare Health Connect 2020.

InterSystems has corrected a defect that can result in skipping a transaction rollback. This can only occur after activation or addition of a mirrored database on a primary mirror member.

This problem exists for:

• Caché and Ensemble 2018.1.3
• InterSystems IRIS data platform 2019.1.1, 2019.3, and 2019.4
• InterSystems IRIS for Health 2019.1.1, 2019.3, and 2019.4
• HealthShare Health Connect 2019.1.1

The conditions necessary for this defect to be triggered are quite specific. All of the following must apply:

• A database has been newly activated or added to a mirror on a primary mirror member.