Clovertech

Segment Out Of Order Error

› Clovertech Forums › Read Only Archives › Cloverleaf › Cloverleaf › Segment Out Of Order Error

  • Creator
    Topic
  • September 18, 2017 at 4:25 pm #55498
    Rodney Howell
    Participant

      Need a little help in resolving out of order error.

      My inbound variant is (Epic 2.5.1) RDE_O11 and I

      Sr. Integration Analyst
      Houston Methodist

    • Creator
      Topic
    Viewing 2 reply threads
    • Author
      Replies
      • September 18, 2017 at 7:29 pm #85558
        Keith McLeod
        Participant

          What happens when you use the HL7 Testing tool with the Inbound variant selected?  Do you get the same error?  Can you show the variant configuration in the terms:

          Variant Definition of the selected message.(Seen on right hand side of Variant Message definition)

          Identify which segment is out of order.  Should tell from the HL7 Test.

          Look for required segments in the variant that you possibly don’t have in the message.

          Possibly a WebEx might help.  Let me know.

        • September 18, 2017 at 8:09 pm #85559
          Rodney Howell
          Participant

            Thanks for responding Keith,

            Jim Kosloskey was kind enough to take time out of his day to help resolve the issue.

            Issue:

            In the 2.5.1 HL7 standard variant RDE_O11 TQ1 is a required field. The messages I tested with and failed did not have a TQ1 segment. The testing tool indicated that the segments after RXE: RXR, RXC, OBX and ZRX were out of order instead of presenting TQ1 >< as an empty segment. TQ1 being an empty segment would have made it obvious as to the issue.

            RXE>TQ1>RXR>RXC>OBX>ZRX

            Thanks Jim

            Sr. Integration Analyst
            Houston Methodist

          • September 18, 2017 at 8:13 pm #85560
            Paul Bishop
            Participant

              yes, the outbound variant can generate this error as well.  It usually happens when you have a required segment that didn’t get populated in the translate so it doesn’t exist.  example if the outbound variant is defined as:

              MSH

              PID

              PV1

              ORC

              and your outbound message is created without the PV1, you will get the error.  Either force something in a field in the PV1 or make the PV1 optional on your outbound varian.

              Paul Bishop
              Carle Foundation Hospital
              Urbana, IL

          • Author
            Replies
          Viewing 2 reply threads
          • The forum ‘Cloverleaf’ is closed to new topics and replies.