- This topic has 5 replies, 5 voices, and was last updated 15 years, 2 months ago by .
(I’ve had no luck at all using the search function in this forum to find any posts with strings like “0B” or “1C”, even though I know those strings exist in posts here, so maybe that’s why I get nothing when searching for “04”. If anyone can point me to previous posts that address this topic, if there are any, that would be appreciated.)
We are a site with Eclipsys, and therefore we have their interface engine, eLink, in addition to our Cloverleaf engine. In the config parameters for some of the eLink standard tcp/ip clients that we have connecting to Cloverleaf, by default a “SendShutDown” option is enabled, and what this seems to do is cause a couple messages to be transmitted when the client is manually stopped from the monitor console.
The first message has a “datagram tag” (excuse me if I’m not using the correct terminology here) of “DATA ” in the first 10 characters, followed by the message content which is hex “0B 04 1C 0D”. This is basically the hex character “04” surrounded by the HL7 mllp envelope.
The second message is just a datagram tag of “CLOSE “, with no message content.
The effect of receiving the first of these two messages in Cloverleaf by an inbound thread using the mlp_tcp.pdl is that the envelope characters are stripped off, leaving just the hex “04”, and this is treated like it is an actual message and causes a NAK to be sent back because the expected HL7 message (is only 1 byte long and) doesn’t begin with “MSH”.
So I guess my question is: if the “04” represents some sort of “shutdown” signal, is this part of a known protocol that the mlp_tcp.pdl simply doesn’t support, or is eLink doing something non-standard and proprietary to Eclipsys?
I’m looking at just disabling the SendShutDown from the eLink side, but wondered if maybe I wasn’t using the correct protocol driver from the Cloverleaf side.
- The forum ‘Cloverleaf’ is closed to new topics and replies.