#HealthShare

Hi,

We currently have individual systems connecting to MESH, but would like to leverage the monitoring and managment facilities in HealthShare.

Has anyone integrated directly with MESH?

https://digital.nhs.uk/message-exchange-social-care-health/technical-inf...

Kind regards,

Stephen

Newbie question. So bear with me please.

We have a requirement to extract or build a file off of our local db to feed to HealthShare.

The requirement is for us to create the extract and send it to HealthShare the SDA format.

My initial thought is why would you do that when the SDA is native to HS. We could create a file in any format csv,tab etc let HS consume it, convert it to HL7 2.5.1 and then let HS do the work with the SDA.

However, the current direction is for us to query, get the data and map it to an xml file built off of the SDA.

I have a HL7 schema listed within Healthshare that is marked as 'Standard' however this doesn't appear to not a standard schema and more of a custom one created (there are very specific Z segments within it) that has somehow been marked as a standard. Is there a way to change it from a Standard to Custom? I realise that this cannot be completed within Healthshare but is there a way to change this within Studio?

Thanks

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.

I thought there used to be some code in the manuals to do this couldn't find it in my latest release manuals. In other words, turn prod data into test data.

I am designing the software architecture for an Ensemble/Healthshare production to be deployed on Amazon AWS EC2 servers (2 mirrored m4.large - 4 vCPUs / 16 GiB RAM running RedHat Linux 3.10.0-327.el7.x86_64 and Healthshare for RHEL 64-bit 2016.2.1). It's a rather CPU-intensive production involving massive XSLT 2.0 transformations (massive both in terms of size and volume). I was wondering if anyone has experience configuring Ensemble productions on EC2 servers. My question or concern has to do with the following statement in the Ensemble documentation:

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

Some highlights for Caché and Ensemble are:

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.

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.

Hoping someone can help.

I had posted a similar question outside this group a while ago "Errors requesting data from local Ensemble FHIR Repository" but haven't had the chance to follow up on it since. It was suggested I re-post inside this group.

I'm trying to request data from my local FHIR repository using a simple JavaScript client and am getting the following CORS errors . ( It is a standalone client not inside HealthShare without CSP etc. on my localhost ).

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.

For a HL7 production, How will I be able to use two different segment level transformation (sub transform) in the main transform.

For Ex:
Few mappings from source PID --> target ZAX segment (subtransform 1)
Few mappings from source PV1 --> target ZAX segment (subtransfrom 2),

In the main mappings, I have used subtransform 1 followed by subtransform 2. It doesn't seem working fine.

Any suggestions please. Thanks:)

How to Archive SDA from Post processor and save it in txt file at some location.

HI,

Has anyone implemented the NHS Care Connect profile in HealthShare and if so could you share the steps you took?

I am not looking to integrate it into the SDA model, Just looking having the classes within HealthShare and then applying a DTL to convert to HL7 2.x

I was hoping i could just down load the profiles from git hub and import into Studio but it appears I need the XSD to do this, which are not available.

Cheers,

Jason