#Health Connect

1 Follower · 672 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
InterSystems staff + admins Hide everywhere
Hidden post for admin
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 480
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 265
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 803
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 622
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 317
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 502
Question Mary George · May 7, 2020

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. 

7
0 891
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 185
InterSystems Official Jeff Fried · Dec 10, 2019

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 .
5
0 586
InterSystems Official Jeff Fried · Jan 29, 2020

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.

1
0 322
InterSystems Official Pete Greskoff · Feb 11, 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.
0
0 289
Announcement Kate Lindsay · Feb 3, 2020

Dear Developer Community, 

Would you like to earn a free certification exam voucher?

The Certification Team of InterSystems Learning Services has designed exam objectives and now needs input from our implementation community for the following proposed certification exam:

HealthShare Unified Care Record Technical Specialist

If you have completed at least one UCR/Information exchange (version 15.x or higher) implementation, assisting or supporting in a technical role, ObjectScript proficiency, and Health Connect interfacing experience, you can help us by filling out our Job Task Analysis survey.

0
0 276
Question Yakov Berger · Jan 21, 2020

hi,

Product: 



IRIS for Windows (x86-64) 2019.1.1 (Build 612U) Mon Oct 28 2019 11:29:24 EDT [HealthConnect:1.1.2]



 

i am using a TCP Inbound  Adapter with call interval set to 5.

To my understanding this means that the adapter check to see if there any connections to the port every 5 seconds.

But i am getting error  "No Connection made on port 12123 within interval 5"

The sending application connections to the port happen at no specific interval, what are the recommended setting for call interval?.

 

Thanks

1
0 626
Question Gunwant Kapade · Dec 26, 2019

Hello All,

I am working on Files where I have to compare contents of two files and display result. e.g Suppose file1 contains data in Name and Roll form and file2 contains data in name and class form, so it should compare name from file1 and file2 and display those matching data(Name,Roll,class).

I have piece of idea about file system so any help would be appreciated. Thanks in advance.

Regards, Gunwant

1
0 392
InterSystems Official RB Omo · Nov 25, 2019

InterSystems has corrected a defect that can cause shadowing to fail with an access violation. In rare cases, the defect can cause memory corruption, leading to unpredictable behavior. 

Note: The defect does not affect mirroring.

This defect affects:

  • InterSystems IRIS 2019.1.1 and 2019.3
  • IRIS for Health 2019.1.1 and 2019.3
  • HealthShare Health Connect 2019.1.1
  • HealthShare Health Connect (HSAP) 15.032 on 2018.1.3
  • Caché and Ensemble 2018.1.
0
0 426
Question Cedric Daniels · Nov 13, 2019

does Health Connect have an out of box setting to send some type of "Keep Alive" packet?  This is for a TCP connection.  I have a vendor that will disconnect from the engine if there is a 2 hour idle time.  would like to send something across every hour (if its idle) to prevent the disconnection.   I'm assuming this may be something custom that needs to be created, but thought I asked the community first.

1
0 664
InterSystems Official Pete Greskoff · Nov 4, 2019

InterSystems has corrected several critical defects that can result in data integrity issues. These defects were identified and corrected within a short time, so InterSystems has simplified the upgrade process by consolidating them into a single package. The effects of encountering these defects may not always be visible. These defects affect InterSystems IRIS, IRIS for Health, Health Connect, Caché, Ensemble, and HealthShare products. All of these defects relate to the application of journal data.

InterSystems recommends that you review this document.

1
2 503
InterSystems Official Jeff Fried · Nov 4, 2019

The 2019.1.1 version of HealthShare Health Connect 2019.1.1 is now Generally Available!

 

This release includes maintenance updates in a number of areas, as described in the online documentation here.

It also includes two new features, described in the online documentation here:

  • Support for InterSystems API Manager
  • X12 Element Validation in Interoperability Productions
  • In-Place Conversion from Ensemble - based Health Connect (version 15.03) to Intersystems IRIS - based Health Connect

 

The build number for these releases is 2019.1.1.612.0.

0
0 333
Question Stephen De Gabrielle · Oct 10, 2019

Hi, 

What is a Foundation Production and what does it do?

We are currently on HealthShare Health Connect  15.03 and we are starting the process of moving to HealthShare Health Connect 2019.1.

The 2019.1 Installation Guide is pretty clear that it is essential, but I'm having trouble working out exactly what it does?

Leading on from this is what should I call it?

From the installation guide: 

5. For Local Name, enter the name that will identify the Foundation production.

12
0 1119
InterSystems Official Pete Greskoff · Sep 19, 2019

InterSystems has corrected a defect in applications that use Unicode character 223 (ß). This defect can result in incomplete query results, class compilation errors, and removal of custom SQL privileges.

This problem occurs on systems that are running or have previously run on:

  • Caché and Ensemble 2018.1.0, 2018.1.1, and 2018.1.2
  • HealthShare Health Connect (HSAP) 15.032 on Core versions 2018.1.0, 2018.1.1, and 2018.1.2
  • HealthShare Health Connect 2019.1
  • InterSystems IRIS data platform – all currently released versions
  • InterSystems IRIS for Health – all currently released versions

The defect is triggered by data and component names containing Unicode character 223 (ß). In the versions listed above, an uppercase conversion incorrectly maps that character to Unicode character 7838 (ẞ).  Applications perform this uppercase conversion using features such as $ZCONVERT and %SQLUPPER.

Problems can occur when accessing data or classes created or modified on a product with a different uppercase conversion than the one currently in use.

0
0 294
InterSystems Official Pete Greskoff · Sep 19, 2019

InterSystems has corrected a defect that could lead to invalid backups on Windows platforms. The defect causes upgrades to disable the EnableVSSBackup setting. By default, EnableVSSBackup is enabled (value set to 1) and the upgrade sets its value to 0. Windows VSS backups taken with this setting disabled may contain invalid CACHE.DAT files.

This problem is limited to Windows platforms on the following versions:

  • Caché and Ensemble 2018.1.0, 2018.1.1, and 2018.1.2
  • HealthShare Health Connect (HSAP) 15.032 on Core versions 2018.1.0, 2018.1.1, and 2018.1.2
  • HealthShare 2019.1 (Unified Care Record, Patient Index, Health Insight, Personal Community, and Provider Directory) on Core version 2018.1.2
  • HealthShare 2018.1 (Information Exchange, Patient Index, Health Insight, and Personal Community) on Core versions 2018.1.1 or 2018.1.0

The defect only occurs if you are upgrading to a version listed above. Once you have upgraded to an affected version, you must manually enable the setting; otherwise, it will be disabled on future upgrades, even when upgrading to versions containing the correction.

For customers using Windows VSS backups, InterSystems recommends enabling this setting on any 2018.1 instances of Caché or Ensemble. Once you have enabled the setting, future upgrades (including to affected versions) will preserve its value.

0
0 266