Mirth Connect 4.0.1 Released!

Mirth Connect 4.0.1 is now available as an appliance update and on our GitHub page. Mirth Connect 4.0.1 is a patch release containing a bug fix which includes fixing a Jetty keystore regression that caused Connect servers using a PKCS12 keystore containing a wildcard certificate and/or a certificate with a SAN to throw an exception on startup. See the release notes for the list of fixes and updates.

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

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

Problem with ORU^R01 message

  • Filter
  • Time
  • Show
Clear All
new posts

  • Problem with ORU^R01 message

    I'm receiving an ORU^R01 message. When OBR segments are loaded with info (date,...) everything is ok, but when the OBR segment is empty like
    Mirth does not read the OBX segments that are attached to it.
    What can I do?

  • #2
    Re:Problem with ORU^R01 message

    I tried to populate it in the preprocessor script. But the empty OBR segment seems to be deleted from the message.
    Please help


    • #3
      Re:Problem with ORU^R01 message

      Use the non-strict parser, and you won't have any issues. Mirth does not selectively prune messages based on content. It turns what you give it into XML so you can easily work with it using e4x.
      Brendan Haverlock | Mirth Software Engineer | Mirth Corporation


      • #4
        Re:Problem with ORU^R01 message

        I don't want to turn off the strict parser as the message elements are accessed differently when it's not turned on.
        Could you please give me some hints how I put a dummy date into the empty OBR segment, so that this segment becomes visible?
        Thank you


        • #5
          Re:Problem with ORU^R01 message

          It's ok I found a solution. I read the message first into a channel without strict parser, and put a dummy date into the empty OBR segment. then redirect it to my actual channel