#Health Connect

Is there any good documentation/tutorials on creating gateways in both directions between FHIR and Hl7v2 (for Health Connect)?

the scenarios I'm most interested in

1. Client application sends a FHIR demographic query to Health Connect - and the interface has to convert this to Hl7v2 QBP^Q11 message to the PAS.

2. Health connect sends a PDF document (from a file or HL7v2 interface) to an EPR over FHIR.

Thanks

Stephen

UPDATE

We are using Health Connect  15.03 - Cache for Windows (x86-64) 2017.2.1 (Build 801U) Wed Dec 6 2017 09:07:51 EST [HealthShare Modules:Core:15.03.9901 + Linkage Engine:15.03.

Hello,

I'm wondering what the path is to learning healthshare & ensemble?   I've looked on the learning page and its minimally helpful.   I've found that as a long time mumps programmer that new jobs are requiring this.  I've just been using mumps to assist with epic emr.   Everything I'm seeing is either VistA or Healthshare.  Does someone know where do I go to learn these apps?  Seems like a catch 22.  You need to know these prior to getting a job but you can't get a job where you can learn them.    Frustrating.

Is there any out of the box capability in Ensmeble to remove an FHS segment from a batch file? We have a client that is creating a batch of HL7 messages and they insert an FHS but there is no trailing FTS.

We are hoping to avoid custom COS code to handle this scenario.

InterSystems is pleased to announce the availability of HealthShare Health Connect v15.032 on 2017.2.2

The platforms for this maintenance release are the same as for HealthShare Health Connect v15.03 on 2017.2.1.

• Full details can be found in this supported platforms document.

This release is based on core technology version 2017.2.2.865.0.18321 with the following HealthShare module:

• Core: 15.032.9685

The version number of the HealthShare Health Connect kits for this release is 2017.2.2HS.9685.0

I am working in Ensemble (Health Connect) and doing an HL7 translation

I have what I hope is a simple coding question (but for the life of me, I am struggling).  I have a requirement where I need to extract the last 5 characters of a variable length string.  The return value should be those last 5 characters.  For example - String = CE325ACCT98765 where the return value of the function needs to be 98765.  I am just drawing a blank.

thank you,

Gigi

InterSystems is pleased to announce the availability of these maintenance releases

·Caché and Ensemble 2017.1.3

·HealthShare Health Connect v15.03 for 2017.1.3

For Caché and Ensemble

·Oracle Solaris 10, 11 for SPARC-64 and Oracle Solaris 10, 11 for x86-64 platforms are now approved for release.  They were not available for earlier 2017.1 releases.

·The full list of corrections can be found in the release notes

·The version number of the kits is 2017.1.3.317.0

HealthShare Health Connect v15.03 on core technology 2017.1.3.317.

Effective immediately InterSystems will no longer support Health Connect on Solaris. Previously released products starting with 2017.1 will also no longer offer this combination. This is in line with InterSystems HealthShare, which is not available on this platform.

We do not use the out of the box web server (57772) for HealthConnect, we run a stand alone instance of Apache with https enabled. Now when I go to Tools > Templates > Web Form Wizard,  I get an error Navigation Cancelled. I get a similar error when I try Tools > Add Ons > Add On.

Any ideas?

Hi-

I have searched through documentation, etc and see many mentions of using Ensemble / Health Connect along with the Java Gateway to interface with JMS Queues, but see no specific documentation on how to do this.

Does anyone have any information, or a concise example of using the Java Gateway to allow Ensemble / Health Connect to be able to place messages and retrieve messages from a JMS Queue?

Thanks

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

·Caché and Ensemble 2017.2.1

·HealthShare Health Connect v15.03 for 2017.2.1

Caché and Ensemble 2017.2.1 details:

·Platforms are the same as for 2017.2.0, with the addition of:

oOracle Solaris 10, 11 for SPARC-64

oOracle Solaris 10, 11 for x86-64

·The version number of the kits for these releases is 2017.2.1.801.0

·The full list of corrections can be found in the release notes

HealthShare Health Connect v15.03 on core technology 2017.2.1.801.

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

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

Caché and Ensemble 2016.2.3 are available on the same platforms as 2016.2.2

The full list of corrections can be found in the release notes.

• The version number of these releases is 2016.2.3.903.0
• For complete platform details, please refer to the 2016.2 Supported Platforms document.

HealthShare Health Connect v15.021 for core technology 2016.2.3.903.0 contains the following HealthShare module:

• Core: 15.021.

Hi-

Please excuse my rather limited knowledge of HL7.

In Ensemble, I have a HL7 message that contains several Z segments.  I have created a custom schema to represent the new Z segments along with the new DocType Structure and Message Structure

How does Ensemble/Health Connect know which custom schema to use?  I believe it has to be indicated in the MSH segment somewhere, but not sure where exactly that would be.   Is the version simply updated with the new schema name or is there some other field?

TIA

Ken

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?