[Robert Milfajt]

Per an earlier post by Rob, only 6.2 and 19.x are currently supported, so I’d stick to one of those if it were me.

Robert Milfajt
Northwestern Medicine
Chicago, IL

[Robert Milfajt]

And I’ll bet that time bomb is what gave you the two different results, i.e., working in testing tool, failing in practice.

Thanks for the info Jim, I thought CONTINUE was better, it’s good to get the confirmation.

Robert Milfajt
Northwestern Medicine
Chicago, IL

[Robert Milfajt]

Infrequently, but still it happens, a Cloverleaf process will grab a port defined in NetConfig for it’s own communication purposes.  If UNIX, lsof and netstat commands will be useful for you to figure this out.  It’s a simple matter of stopping that process, starting up your thread and starting the process back up, but in a lot of years, I’ve only seen this a handful of times, and mostly on test server.

Robert Milfajt
Northwestern Medicine
Chicago, IL

[Robert Milfajt]

Glad you got it to work.  I think the SEND might have thrown you off, I usually use CONTINUE in my Xlates to generate a second message.  I’m sure someone else on this board might have better insights on the differences between SEND and CONTINUE.

Robert Milfajt
Northwestern Medicine
Chicago, IL

[Robert Milfajt]

We document within the Notes of the thread here.  However, you could probably look at all the current production connections that you have and map them via port number to a netstat -an (AIX command, but should be similar in Windows) and look at the IPs that are connecting to each of your threads.  Of course the more threads you have, more tedious this is, and identify those IPs not within your organizational subnet(s).  After that, I’d document those that are coming from outside in the Notes section of the NetConfig.

Hope this helps,

Robert Milfajt
Northwestern Medicine
Chicago, IL

[Robert Milfajt]

Post your Xlate code here.  Sounds like a CONTINUE/SUPPRESS type of issue, and how you are duplicating in Xlate, but without the code, it’s hard to tell for sure.

Robert Milfajt
Northwestern Medicine
Chicago, IL

[Robert Milfajt]

Class of 1985?  What version of Cloverleaf were they running back then?  That even predates me and I’ve been around for over 20 years.

Robert Milfajt
Northwestern Medicine
Chicago, IL

[Robert Milfajt]

Wonder if this is related to your other post and if you need to actually be creating ACK via Xlate with all the stuff that goes around defining the XML.  If both are related, and you simply need to ACK receipt of messages for this vendor in XML, it might be quicker to write a TCL proc that hard codes the creation of the ACK message and pulls whatever information it needs (like MSH-10) from the source message.  This will mean breaking down XML in TCL, but with regular expressions, is probably doable.

Reach out to me in email and I might be able to get you going in a different direction.

Thanks,

Robert Milfajt
Northwestern Medicine
Chicago, IL

[Robert Milfajt]

What communication protocol is your vendor sending this message?  Are they asking for the ability to call a web service or use HTTP to post the message?  Or are they passing this message using proper HL7 MLLP protocol over TCP-IP sockets?  Do you need to send back an ACK?  If so, what format are they expecting ACK?  XML?  

The communication protocol and ACK format will drive the answer to your question.

Hope this helps,

Robert Milfajt
Northwestern Medicine
Chicago, IL

[Robert Milfajt]

It’s not about blame here.  It’s about finding answers, which you did indeed.

💡

Robert Milfajt
Northwestern Medicine
Chicago, IL

[Robert Milfajt]

I’m trying to recall, but if you pick length encoded (or do nothing because in 6.1 at least length encoded is the default), and the file is new line, you get the same error.

Robert Milfajt
Northwestern Medicine
Chicago, IL

[Robert Milfajt]

I agree with the commentary on not using SMAT due to disk space, but for another reasons as well.  For those device interfaces we have between various middleware vendors, iSirona, GE, iBus and Philips, we do not keep SMAT files for those for two reasons.  The obvious disk space issues, but the other reason is that most device data is only good in the moment and Epic keeps logs (which we keep for only 1 day).  If something failed from last week, chances are there are more recent results from yesterday or today which are more relevant.  However, if you have the disk space and are willing to use it, I see no reason why it’s a bad idea to store it.

Robert Milfajt
Northwestern Medicine
Chicago, IL

[Robert Milfajt]

We are, Alaris, and we do not use Cloverleaf.  In fact Epic recommends that these be point to point interfaces.

Robert Milfajt
Northwestern Medicine
Chicago, IL

[Robert Milfajt]

Reading through the dialogue, I wonder if comment lines are the right place for some of the commentary.  Similar to how Cloverleaf associates Notes with threads, it might be a good idea to have a Notes functionality for Xlates, routes, tables, etc.  In that way, one could be as verbose as necessary, especially for versioning type commentary.  Just a thought, or perhaps a wish, of mine.

Thanks,

Robert Milfajt
Northwestern Medicine
Chicago, IL

[Robert Milfajt]

What communication protocol is your thread using, and how is the RSP generated?  Is it done Cloverleaf, or do you have to pass the query message onto another system, which sends back your reply for Cloverleaf to pass back to querying system?

Robert Milfajt
Northwestern Medicine
Chicago, IL

[Author]

Replies