#Health Connect

1 Follower · 694 Posts

InterSystems HealthShare Health Connect is a healthcare integration engine that delivers high-volume transaction support, process management, and monitoring to support mission-critical applications. 

At the heart of Health Connect is a high-performance, multi-model data engine that seamlessly handles multiple forms of data at high speed. Health Connect easily scales from serving small clinics to handling the transaction volumes of the largest and most complex healthcare delivery systems in the world. Capabilities include:

  • Interoperability by design
  • Mirroring with fast failover recovery
  • Source control for HL7 schemas
  • Intuitive drag-and-drop HL7 schema editing
  • A flexible, adaptable security model and more
Question Hao Ma · May 24, 2021

I believe most of you have encounted this problem: a healthconnect/ensemble user get a slow response and ask measurement on how long it takes ensmeble to process this request, the ensemble 'activity data' gives no clue of the delay.

The reason is HealthConnect message measurement was based on ensemble message, which can’t give a correct answer on when ensmeble recevie the request and what time it send back response. when there is delay on inbound/outbound adpter, or csp gateway, there is no way to find out the delay from "activity data" . 

I am asked by a customer how to deal with this problem.

1
0 373
InterSystems Official Steven LeBlanc · Aug 21, 2020

I am pleased to announce the availability of InterSystems Container Registry. This provides a new distribution channel for customers to access container-based releases and previews. All Community Edition images are available in a public repository with no login required. All full released images (IRIS, IRIS for Health, Health Connect, System Alerting and Monitoring, InterSystems Cloud Manager) and utility images (such as arbiter, Web Gateway, and PasswordHash) require a login token, generated from your WRC account credentials.

14
7 2352
InterSystems Official Benjamin De Boe · Apr 21, 2021

Preview releases are now available for the 2021.1 version of InterSystems IRIS, IRIS for Health and HealthShare Health Connect.

As this is a preview release, we are eager to learn from your experiences with this new release ahead of its General Availability release next month. Please share your feedback through the Developer Community so we can build a better product together.

InterSystems IRIS Data Platform 2021.1 is an extended maintenance (EM) release. Many important new capabilities and enhancements have been added in continuous delivery (CD) releases since 2020.1, the previous EM release.

6
0 1013
Question Nigel Salm · Apr 22, 2021

NigelTSalm

Hi, I am loading zpm for the first time. I downloaded the %ZPM.Installer xml file and then tried to import it trough the Cache Studio. It threw up 4 errors Compilation started on 04/22/2021 23:41:53 with qualifiers 'cukb /checkuptodate=expandedonly' Compiling class %ZPM.Installer Compiling routine %ZPM.Installer.1 ERROR: %ZPM.Installer.cls(ExtractPackage+2) : MPP5610 : Referenced macro not defined: 'FileTempDir' TEXT: Set pFolder = ##class(%File).NormalizeDirectory($$$FileTempDir) ERROR: %ZPM.Installer.

3
0 733
Question Mark O'Reilly · Apr 1, 2021

Upgraded healthshare to health connect. The search box is not selecting the correct url 

i.e. selecting message loads 

http://penn-tietest:57772/csp/sys/EnsPortal.MessageViewer.zen?$NAMESPAC…

instead of this which when go through the menu it loads 

http://penn-tietest:57772/csp/healthshare/tie/EnsPortal.MessageViewer.z…

it actually loads from interopability view messages as 

http://penn-tietest:57772/csp/healthshare/tie/EnsPortal.MessageViewer.z…;

Please can someone advise 

1
0 219
InterSystems Official Jeff Fried · Mar 26, 2021

Three new sets of maintenance releases are now available: 

  • Caché  2018.1.5, Ensemble 2018.1.5, and HSAP 2018.1.5
  • InterSystems IRIS 2019.1.2, IRIS for Health 2019.1.2, and HealthShare Health Connect 2019.1.2
  • InterSystems IRIS 2020.1.1, IRIS for Health 2020.1.1, and HealthShare Health Connect 2020.1.1

Installation kits and containers can be downloaded from the WRC Software Distribution site.

These are maintenance releases with many updates across a wide variety of areas.

1
0 507
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

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

0
0 260
InterSystems Official Pete Greskoff · Feb 11, 2021

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.

0
0 301
Article Botai Zhang · Jan 25, 2021 4m read

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.

0
0 378
Question Allison Womack · Dec 15, 2020

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.

2
0 388
InterSystems Official Pete Greskoff · Dec 3, 2020

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.

0
0 238
Article Oliver Wilms · Nov 16, 2020 2m read

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.

0
0 348
Question Paul Hula · Nov 2, 2020

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

2
0 615
Question Stephen De Gabrielle · Oct 19, 2020

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?

2
0 327
Article Jin Kim · Mar 19, 2020 10m read

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!

3
1 878
Discussion Erik Svensson · Sep 18, 2020

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.

5
0 495
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.

0
0 272
InterSystems Official Pete Greskoff · Aug 27, 2020

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.

1
0 812
Question Sebastian Thiele · Sep 1, 2020

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.

4
0 638
Question Oliver Wilms · Jun 25, 2020

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

1
0 319
Article Tani Frankel · Jun 4, 2020 10m read

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).

2
0 510