#Health Connect

InterSystems is pleased to announce the availability of these maintenance releases:

• Caché and Ensemble 2017.1.2
• HealthShare Health Connect v15.03 for 2017.1.2

Caché and Ensemble are available on the same platforms as 2017.1.1

• The full list of corrections can be found in the release notes
• The version number of the kits for these releases is 2017.1.2.217.0
• Oracle Solaris 10, 11 for SPARC-64 and Oracle Solaris 10, 11 for x86-64 are not yet approved for release.  They are expected to be included in the next maintenance release.

HealthShare Health Connect v15.03 on core technology 2017.1.2.

InterSystems is pleased to announce the release of Caché, Ensemble, and HealthShare Health Connect v15.03

Some highlights for Caché and Ensemble are:

• Parallel dejournaling to improve throughput of mirroring and journal restore
• New iFind and iKnow features like co-occurrence search, performance improvements, and more
• SQL enhancements in Query Auditing, optional ANSI SQL operator precedence, and Frozen Plan Evaluation, along with several query optimization improvements
• Ensemble updates include DICOM enhancements, XML performance, and XSLT2 activities in BPL.

Hi

Reading through the installation guide I found a fairly stern warning in the robustness checklist not to use the inbuilt apache web server.

>Use a robust web server. Do not use the limited Apache server installed with
>Ensemble. It is provided as a convenience for use on development systems and
> is not a fully capable web server.

We only have a few users, the Interface team (3), an integration consultant(1) and an interface monitoring/development vendor.

Do we need a 'robust web server' for using HealthShare Health Connect Integration engine?

1. Scope and Objective:

Recently we supported a few NHS cases that required TIE (Trust Integration Engine) integration with the PKB service.   Hence this article is meant to be a 10-minute quick guide to describe a demo solution (simple configurations and end-2-end implementation steps) for Health Connect (Ensemble) Integration with PKB (Patient-Knows-Best) service.

The product I'm using is HealthConnect ( this installation HSAP-2017.1.1.111.0.17521-hscore15.03-b8382-win_x64.exe). Do I have access to the Information Exchange Clinical Viewer ? Is there a way to install this and connect it up to my HealthShare FHIR repository?

HealthShare HealthConnect and Information Exchange version 15.03 support import transformations from C-CDA 2.1 to SDA. You can find these transforms in your installation's csp/xslt/SDA3 directory. For general information about import transforms, see "CDA Documents and XSL Transforms in HealthShare" in Overview of Health Connect.

Among the enhancements to import functionality added in connection with C-CDA 2.1 support is the ability to preprocess your C-CDA input files prior to the transformation done for import.

A sophisticated alerting solution lets you solve problems quickly and proactively.  Watch the recorded webinar: Proactive Alerting: Advanced Approaches for Alerting Solutions webinar presented by Michael Brady, InterSystems Technical Trainer, to learn how to make the most out of your alerting solution. 

Hi, Community!

A sophisticated alerting solution lets you solve problems quickly and proactively. So, check the new video:

Proactive Alerting: Advanced Approaches for Alerting Solutions

I am pleased to announce the Maintenance Release of HealthShare Health Connect v15.021 on data platforms 2016.1.4

This contains the HealthShare module Core: 15.021.8253

The version number for this kit is 2016.1.4HS.8253.0

The platform list is the same as for HealthShare Health Connect v15.02 for 2016.1.3. You can get details from the Supported Platforms document.

InterSystems is pleased to announce the availability of the following maintenance releases:

• Caché and Ensemble 2017.1.1
• HealthShare Health Connect v15.021 on core technology 2017.1.1

Caché and Ensemble are available on the same platforms as 2017.1.0, except as noted below

• The full list of corrections can be found in the release notes.
• The version number of the kits for these releases is 2017.1.1.111.0
• Oracle Solaris 10, 11 for SPARC-64 and Oracle Solaris 10, 11 for x86-64 are not yet approved.

HealthShare HealthConnect v15.021 on core technology 2017.1.1.111.

Hi -

When upgrading a Health Connect deployment from 2014 to 2016 do I HAVE to recompile? or is the "just upgrading" enough?

I want Healthconnect to be the middle man between my client and my respository vendor. I've setup

HS.IHE.XDSb.RepositoryServices > HS.IHE.XDSb.Respository.Process>HS.IHE.XDSb.DocumentSource.Operations

Is this the correct approach?