Announcement

Collapse
No announcement yet.

Problem with ORU^R01 message

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

  • Bleupomme
    replied
    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

    Leave a comment:


  • Bleupomme
    replied
    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

    Leave a comment:


  • brendanh
    replied
    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.

    Leave a comment:


  • Bleupomme
    replied
    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

    Leave a comment:


  • Bleupomme
    started a topic Problem with ORU^R01 message

    Problem with ORU^R01 message

    Hi,
    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
    OBR||||||||
    Mirth does not read the OBX segments that are attached to it.
    What can I do?
Working...
X