#HL7

Folks

1) What's the correct way to check for an existence of a segment?  So far I have been doing this by checking to see if a required field is non-null, and this seems to work but is a bit clumsy. In this case, it’s an X12 message being checked in an IF action in BPL:

              request.GetValueAt("NTE(1):Description")'=""

Or in a DTL, to see if a Z segment exists:

              source.{ZEF:Counter}=1

2) I have a case where I need to change from an external date format (YYYYMMDD) to internal (+$H) for a DTL to create a new object (and then persist it later).

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

noob here..(moving from JCAPS to Ensemble)

We are wondering where is the best place to tie the schema category for an incoming HL7 message? Should we do this within the service (via the message schema category setting) or receive everything and validate in the process (DTL) level?

We want to capture everything that will be sent to that HL7 listener service and then decide what to do with bad messages at the process layer.

Does anyone have any recommendation regarding this? Appreciate your input and decision thought process.

Thank You,

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. 

This is the options I have so far;

1. file drops -

Hi

I need to process a very large Batch file which contains HL7 charges which we pull using FTP. I need to loop through the file and do some checks and then split the large Batch file in to individual messages. These individual messages then gets process through a different module to create a output batch of different format

Performing LUT table maintenance through Portal impacted Business Service HL7 message processing for one of our inbound feeds causing a message to fail.  We are on Healthshare 2014.1.3.  Is this a known issue, or is there a right way to modify table?

Hi all,

We have a big problem with spanish accent and special characters using Data Transformation (HL7 Messages).

We have some DT to transform HL7 messages to other type (OUL^R22 To OML^O21) so it copys the PID segment to the new one, but if in the PatienName field has any special character, the transformation stops and it not continues with the transformation.

This is the message
 

MSH|^~\&|B11111111|000000000C|LAB|TSFLAB|20170117163714||OUL^R22|ID1||2.5||||||UTF-8 
PID|1|1234567890134567890|00000000R||MUÑOZ LÓPEZ^JUAN^||19900101000000||||&||
OBR|1|23145687456894561321|23141211||||||
ORC|RS||4385025

For testing purposes, I would like to create an EnsLib.HL7.Message from either a %String or a file on disk and pass it into a function in a unit test (outside of an Ensemble context). EnsLib.HL7.Parser appears to do the necessary parsing, but it also sends the message via Ensemble service rather than returning it as a value. Is there a way to leverage the parsing outside of a Ensemble service? Alternatively, is there another way to create an EnsLib.HL7.Message?

I have a project to convert a JSON message with two patient identifiers into an HL7 ADT^A31.  Is there any documentation or training that you would think is appropriate?

Currently using Ensemble 2014.1.5 on AIX

Hopefully somebody can help with this :

Using healthshare - Ensemble::: I have an HL7 message (ORU^R01) where I have an RTF file embeded into an OBX segment as what appears to be plain text.

example below :

How would I  extract this file out and create an email and attach this RTF file as an attachment?

I have a standard text file that is coming out of a system new line delimited. Each document will have the same field structure each time.

ID: xxxxxxxxx
Name: xxxx,xxxx   Age: xx   Sex: x

OSU Wexner Medical Center Harding Hospital
Treatment at  7/14/2016   10:39:34 AM

% Energy Set                                    50 %
Charge Delivered                             255.4 mC
Current                                       0.91 A
Stimulus Duration                              7.0 Sec
Frequency                                       40 Hz
Pulse Width

My SOAP Operation is returning an error "ERROR ErrBusinessDispatchNameNotRegistered: Business dispatch name 'PKB_SOAP_Sender' is not registered to run"

How to I resolve this?

I have an amazing tool called 7edit for editing and sending HL7 v2 messages.  I've searched hours for a similar tool for HL7v3 without luck.  They're all web based, crappy, broken links, etc.

Learn to successfully design your HL7 production.

I see the TS and DT data types in the default 2.3 schema:

<DataType name='TS' description='time stamp'>
    <DataSubType piece='1' description='time of an event' datatype='ST'/>
    <DataSubType piece='2' description='degree of precision' datatype='ST'/>
</DataType>

<DataType name='DT' description='Date (2.8.13)'>
    <DataSubType piece='1' description='Date (2.8.13)'/>
</DataType>

but it doesn't appear that it would actually validate the format.Is this possible?We had an instance recently where a customer was sending a timestamp with a missing digit (20160503120 for example).

We are interfacing through Ensemble with an application that does not like diacritic signs in text. I have been searching for a way to strip these signs from the HL7 messages that get send to that application. 
The problem in short is we have an incoming HL7 message with e.g. é (or ë, á etc), this goes into Ensemble. In the outgoing message the é should be replaced with an e. 

I have tried solving this issue with the use of a new subtable, which does the conversion as é->e / ë->e etc. This works with (file)streams and also with ZConvert: Write $Zconvert("ë","O","BASCII")outputs "e", where

I'm trying to read PID-3 and route the message based on if a certain prefix existed, but I keep getting Property Does Not Exist.

I've tried

HL7.(PID:PatientIDInternalID()) Contains "COS"

HL7.(PID:PatientIDInternalID(1)) Contains "COS"

HL7.{PID:PatientIDInternalID()} Contains "COS"

HL7.{PID:PatientIDInternalID(1)} Contains "COS"

This is a 2.3 MDM message. Thanks!

Framing refers to the characters that mark the start and end of an HL7 message (or other types of framed messages).  Most HL7 services and operations have a Framing setting that allows the user to define this framing.  The most common choices are available as defaults, but with the AsciiMM/NN setting, components can be configured to recognize any framing characters.

The most common framing error is ErrEndBlock.  Other typical errors include a warning saying "Discarding received non-HL7 data", a warning saying "Returning unused unexpected n-char segment", and "Discarding leftover input ''".

These

Given the following data type:

<DataType name='TN' description='telephone number'>
    <DataSubType piece='1' description='telephone number'/>
</DataType>

What is the point in setting a SegmentSubStructure's datatype to "TN" instead of "ST"?

We have an incoming ADT adapter and the ACK MODE is set to IMMEDIATE.  This is what the docs say: 

An inbound ACK shows up as a square in the visual trace.  These do not.  How can I view them?

Did some searching online with no luck.  In Studio, is it possible to add comments to .HL7 schema files?  For instance

<!-- This is a comment -->
//or maybe this is
<MessageStructure name='ACK' definition='MSH~MSA~[~ERR~]'/>

We want to isolate the storage of our CCDAs from our HL7 V2 data, but keep them under the same namespace. From my understanding, I should create a new database then store those classes related to CCDAs in that database. Is this the correct approach?

I'm doing some Schema changes.  I used our existing standard schema as a base, which was already based on 2.3.  So let's call our existing one Custom.MHC.Schema (based on 2.3).  I created Custom.MHC.Schema.Advanced (based on Custom.MHC.Schema) and copied down one of the code tables then made a change to it.

When I ran a message through, the code table change didn't show up.  I noticed in the message viewer that the DocType is still Custom.MHC.Schema:ADT_A01 but the DocType Category is Custom.MHC.Schema.Advanced.

I have changed the HL7 Service Message Schema Category setting and I also tried

I have a tool I absolutely love for HL7 v2 analysis and manipulation. It's called 7edit.  I'm wondering if there is anything similar for HL7v3/CDA/CCD.  I know it is considerably more complex, but I still have hope.

So far the best resource I've found is http://www.cdapro.com/.  I'd love to hear anyone else's tips for tools or resources.

Hi,

IHAC who is trying to connect Ensemble to Quadramed for HL7 messaging, however, it seems that in order to do this, the following is required:

"we open a passive connection to Quadramed and then listen for a connection request from Quadramed, once this is established we then send messages"

Has anyone done this before?  Is this possible with the standard HL7 components?

Thanks,

Steve.

Hi everyone!

I have imported a schema (HL7 v2.5 XML schema) using the "Ensemble > Interoperate > XML" and I have built a Web Service that receives a string with an XML document that follows the schema. I have used EnsLib.EDI.XML.Document as follows to consume the string and produce the XML vDoc:

Presenter: Matt Spielman
Task: Use the FHIR standard with HealthShare-based solutions
Approach: Provide an overview of how HealthShare will support the evolving FHIR

The next major release of HealthShare will be the first version to support the emerging HL7 FHIR standard. This presentation will discuss InterSystems’ involvement with the FHIR standard, detail the new FHIR functionality, and review our long term plans for FHIR in the HealthShare platform.

Content related to this session, including slides, video and additional learning content can be found here. Please note that this content is available only to HealthShare customers and attendees of the Global Summit. On the learning web site you will be prompted for your Global Summit credentials to access this content.

What is the recommended approach to handle the following scenario: Large number of HL7 messages are serviced via Ensemble.Those messages are then transformed and routed to an Operation which calls a web service which does a number of different activities.If will do address normalization, location geo coding, MPI lookup and resolution, and insert into a SQL Server database to stage for an analytics product.Unfortunately all of this work takes time and the first thing that happens in the web service is a lock taken out on the Patien in SQL Server.

This post is intended to share how we have implemented HL7 v.2.x in XML format in several Ensemble projects.

We have added to our local InterSystems Iberia GitHub repository a package which uses an approach that takes advantage of EnsLib.HL7.Message class.

More information here:

https://github.com/intersystems-ib/Ensemble-HL7-XML

I have had a few questions about the number of HL7 messages Ensemble can handle lately, so i thought i would draw people's attention to the benchmark report

https://community.intersystems.com/documentation/ensemble-and-healthshare-hl7v2-message-throughput-0

It describes the throughput of HL7 messages with realistic messages and routing.

Dave