LLP Issue

[Jack]

Hello Folks,

I'm experimenting with Mirth and have come across a small issue with LLP. This has happened with the source configuration in ASCII and HEX modes. The log fragment from mirth.log is below. BTW the Mirth box is Windows and the sending unit is a Linux box with commercial PACS software that supports bi-directional HL7 messaging:

java.io.IOException: Message violates the minimal lower layer protocol: no start of message indicator received.

I ran tcpdump on the Linux server and found that the LLP is present as indicated in Mirth's default configuration. Also, I'm using the standard ASCII set with no values requiring escaping and segment termination using 0x0d. One additional item is I had this working last week, deleted that configuration and created one similar to it. Any ideas on that?

Thanks,
Jack

[chrisl]

Re: LLP Issue

If you are using 0x0d values in Mirth, make sure it is set to HEX. We understand that the wording is incorrect (and have fixed it in the current SVN pull), but the encoding relates to how to handle the LLP characters, not the actual message encoding.

This option is helpful in the situation where a vendor sends the ACTUAL string of: <0A> or <0B> in the message, rather than the correct ascii characters (new lines and carriage returns). You generally would want to leave the setting on HEX and use 0x0A, 0x0B, 0x0D, etc as the values Mirth should expect in the LLP. Mirth will see 0x** and actually look at the character table for the specific ascii character associated with the hexcode. In the case of 0x0A for example, Mirth will look for ascii character 10 in the incoming LLP stream.

Hope this helps. If not, please create a new issue (www.mirthproject.org/jira) and attach your channel definition file.

Thanks,
-Chris

[Jack]

Re: LLP Issue

Thanks, Chris. I&#039;ll let you know.

Jack

[Jack]

Re: LLP Issue

Hello Chris,

Thanks for the help. Problem is all gone.

Jack