#HealthShare

Hi. What notifications are available, if any, when any part of an SDA has been modified (inserted, updated, deleted, etc...)?

Thanks in advance.

Hey all! I'd like to collect some feedback regarding searching for messages using the Message Viewer. I'd like to find out what things regarding the Message Viewer you all in the community have found difficult/confusing/poorly documented. This can of course include things that you don’t know how to do yet, but would like to learn about.

Prompted by this post about accessing a global at its original location after you have changed a mapping, here's a tip about one specific dropdown in Portal that's sometimes useful.

Hello everyone,

Currently we have 2 Windows servers in a clustered environment. Is there a setting in HealthShare for a TCP/IP Operation to use the virtual IP address when initiating the connection, rather than the host IP address?

Thanks in advance!

I'm a beginner for hs2014

I try to write text file in ASCII format (encode CP874) from HS2014 (run on RHEL)

I try to use

o file:"WNSK\CP874\"
o file:"RSK\CP874\"
o file:"WNSK\THAW\
o file:"WNS"

but output file still in UTF-8 encoding

please advise me

Thk.

I only recently noticed the presence of a local database named CACHE alongside the more familiar CACHESYS, CACHELIB, CACHETEMP and CACHEAUDIT.

A bit of digging through the documentation archive led me to conclude that the CACHE database arrived in 2010.2, where the release notes say:

Hi all,

I was wondering if InterSystems offers any message profiling capabilities. What I mean by "message profiling" is essentially stats or metrics gathered from a collection of data submissions of a particular type. For instance, average number of segments <XYZ> in a specific HL7 V2 message type. Or the number of sections found in a HL7 V3 CDA documents.

Curious if there is anything like this provided "out-of-box".

Thanks!

James

Prior to 2017.1, whenever I created a new namespace using Portal on Ensemble or HealthShare it was automatically configured to host productions. This used to irritate me, because sometimes I'm setting up a namespace (for example, to host our Deltanji tool) that doesn't need the extra Ensemble baggage.

If you deal with multiple instances of Caché / Ensemble / HealthShare and sometimes have to work at the Terminal command prompt, did you know that you can easily add extra information to that prompt which may help prevent you running a command on the wrong instance?

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

Some notes for Caché and Ensemble, including highlights, are:

In this posting I want to raise the profile of a feature that arrived in 2009.1 but is perhaps not very well known.

It is sometimes useful to make certain packages, globals or routines available to all of your namespaces. Of course you can add the necessary mappings whenever you create a new namespace, but here's a simpler way.

Hi,

We have a mixture of legacy and new systems, and are grappling with the issue of moving documents between systems.

At the moment we are mostly using file drops and encoding metadata in filenames, but a new supplier (letter transcription) is going to provide a Hl7v2 feed sending MDM^T02 messages with PDF's of letters base64 encoded in the message itself.

We are thinking of asking all our suppliers to go with MDM (or ORU) for sending documents.

I'm interested in the pros and cons of the options; and if there are options I haven't thought of.

Our client is a test out of 2016.1 (Build 656U) Healthshare that wants to do a one way SSL connection to our Java 1.7/Tomcat 8.0 server. We have yet to come up with a secure cipher set that Healthshare and Java agree on for the handshake. So far we've had to use these ciphers identified which are not recommended (though it does do a handshake properly).

Hello. New to the forum and was hoping I could get some expert help here. I have one data set that is using CHD Logic to combine Procedure and Diagnosis codes to define Sensitive data and flag the record for additional protected filtering. The files coming in define what is flagged and the Clinical Info Rule and Clinical Info Type are tied to the flag in the file which identifies it as a additional protected record.