#Health Connect

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.1  has many new capabilities including:

• Healthcare Interoperability
  
  • FHIR R4 Support
  • HL7 Productivity Tools
• API Management
  
  • InterSystems API Manager
  • Open API/Swagger Specification-First REST Development
• New Look in the Management Portal
• SQL Enhancements
  
  • Universal Query Cache
• Interoperability Production Enhancements

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 .Net
• Container and Cloud Deployment improvements
• SQL enhancements

Int

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

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

• Advisory: Gap in medications display if generic names not included
• Advisory: Updated the Clinical Viewer so that silent encounters do not display
• Advisory: Corrected gap in custom lab charts not displaying all results in Clinical Viewer
• Advisory: Residual Locks on Late Update
• Advisory: Incorrect HealthShare Mirror Upgrade Documentation could lead to Data Integrity issues

If you have any questions regarding these advisor

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  has many new capabilities including:

• Healthcare Interoperability
  
  • FHIR R4 Support
  • HL7 Productivity Tools
• API Management
  
  • InterSystems API Manager
  • Open API/Swagger Specification-First REST Development
• New Look in the Management Portal
• SQL E

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 memb

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 sur

hi,

Product: 

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

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

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

In InterSystems IRIS and IRIS for Health, shadowing code is included, but it should not be used; InterSystems recommends using mirroring, which

I would like to control multiple 'services' in Ensemble.

I would like the ability to switch them off and on.

My plan is to achieve this in a Cache class using ObjectScript.

Is this possible?

Any tips, starting points would be gratefully received.

Many thanks.,

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.

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. It will help you determine your level

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.  A full set of kits is available from

Hi there

I've noticed extreme slowness using the portal in my Healthconnect dev enviroment lately.

Any page in the Portal takes a lot of time Loading.

Any ideas of what it could be?

Kind Regards,

Joao

Looking at the DTL, we can pretty much understand what the provided mapping from FHIR to SDA3.

But, is there any Intersystems document, where the mapping To/From FHIR is documented, at least FHIR to SDA3 ?

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. This name will become the namespace that contains the class definitions for the production

So the name I give it will

I'm a beginner using HealthConnect.  Trying to bring in a CCD and transform it to a HL7 messages.  Is there any documentation on how to accomplish this?  thanks!

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.

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.

Can health Connect create a file in a directory, than add data  (HL7 messages) to it?

1. Purpose

This is a 10-minute simple step-by-step guide on how to quickly set up various flavors of HealthShare docker containers from scratch on a Win10 laptop. 

For example, we can build a couple of  HealthShare "global edition vs UK Edition" demos as shown below.  

There are a couple of frequently asked questions from HealthShare colleagues and partners:

• "I am no Docker guy, but is there a quick way to build various flavors of HealthShare containers simply for demo/PoC/dev/training or troubleshooting purpose?"
• "I just can't make "Docker for Windows" work on my Win10 laptop - how did

Preview kits are now published via the WRC's preview download site for:

• InterSystems IRIS 2019.1.1
• InterSystems IRIS for Health 2019.1.1
• HealthShare Health Connect 2019.1.1

The build number for these releases is 2019.1.1.608.0.

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

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

• Support for the InterSystems API Manager,
• In-place conversion from Caché and Ensemble to InterSystems IRIS
• X12 element validation.

This release

Currently we are using Health Share 2015.2.2, and looking to upgrade to the latest version in the next month.

From what I understand we have to upgrade to 2017 or 2018 prior to going to 2019.1 since 2019.1 is on the IRIS platform.

In trying to outline my steps in the upgrade process I came up with a question.

• Can a Full System Backup from 2015.2.2 be restored into 2019.1?
• Do I have to restore the 2015.2.2 back up into 2017 or 2018, then do the 2019.1 conversion?

Has anyone had experience with this? or should I open a ticket with WRC?

Thanks

Scott Roth

The Ohio State University Wexn

I am trying to work through our upgrading steps from 2015.2.2 to Health Connect 2019.1. Is there a place online I can access previous versions of Health Connect documentation? I am specifically looking for Health Connect 2018.1.2 documentation so I can understand the upgrade process on AIX.

Thanks

Scott Roth

Hello All.

In need of some help.

We are currently migrating Interfaces from JCAPS to HealthConnect 19.1 and have done a lot of work on our Dev server.  I am looking to copy/export this work over to the Test server and have managed to export the production and Rules, HL7 custom Schemas etc.  The only thing left now are the Data Transformations but so far I can only find ways of copying the transformations over individually.  Is there some way to copy all of the transformations we have produced in our namespace to another server in one go?  

Thanks