Announcement

Collapse

Mirth Connect 4.3.0 Released!

Mirth Connect 4.3.0 is now available as an appliance update and on our GitHub page.

This is a major release containing new features like adding new functionality to the Mirth Connect Setup Wizard, adding the ability for resource and channel-specific classloaders to load child-first or parent-first, and added a default implementation of the getObjectsForSwaggerExamples() method in the ServicePlugin class. This release also contains enhancements for the Mirth Connect Administrator Launcher, the Mirth Connect Docker images, and several bug fixes and security improvements.

Download | See What's New | Upgrade Guide | Release Notes

For discussion on this release, see this thread.
See more
See less

LLP Listener - HL7 message received in two parts

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • LLP Listener - HL7 message received in two parts

    I have the attached channel with an LLP Listener & a FileWriter. It works fine for smaller messages. But the larger HL7 messages are arriving in TWO parts; just chopped halfway ramdomly. So most cases the second part of the message is erroring out as it is not a complete message. Smaller sized messages do arrive fine. (by large messages I do not mean huge files, just 3kb ASCII files - multiple lab tests in one order)

    Please help me out. RequisitionsChannel.xml (23277 bytes)

  • #2
    Re:LLP Listener - HL7 message received in two parts

    I am still stuck with this issue. Can someone please help?

    bikashpanda wrote:
    I have the attached channel with an LLP Listener & a FileWriter. It works fine for smaller messages. But the larger HL7 messages are arriving in TWO parts; just chopped halfway ramdomly. So most cases the second part of the message is erroring out as it is not a complete message. Smaller sized messages do arrive fine. (by large messages I do not mean huge files, just 3kb ASCII files - multiple lab tests in one order)

    Please help me out. RequisitionsChannel.xml (23277 bytes)

    Comment


    • #3
      Re:LLP Listener - HL7 message received in two parts

      I imported your channel into a Mirth ver 1.6. Since the channel was created in a ver 1.5, the process suggested that some of the channel properties may not be the same. I let it automatically convert the properties.

      After a couple of minor changes to make things work on my box, I sent some 1k sized ORM-1 messages to the channel source port. The messages flowed through, were transformed and filed in the appropriate folder.

      I padded one of the messages with a total of 41 NTE segments so the file size would be 3k. I sent it a couple of times and it flowed through properly.

      As stated in the beginning, I am not running the same version Mirth you are testing with and this difference may be the cure...or, as the dialog box indicated when the channel was imported, our channel properties may have ended up different.

      I'll take a look at the channel file you attached and what the resulting channel configuration looks like and post what I find, if anything.

      Patrick

      Comment


      • #4
        Re:LLP Listener - HL7 message received in two parts

        This issue is one I believe I fixed in 1.6.0. The defaults in LLP listener (with the strict LLP validation) should not split messages anymore. Please try 1.6 and let me know if it works for you. Also, you should generally use strict llp validation unless you have problems with it.

        Jacob

        Post edited by: jacobb, at: 08/24/2007 11:36
        Jacob Brauer
        Director, Software Development
        NextGen Healthcare

        sigpic

        Comment

        Working...
        X