Error Database: Out Of Order Message

Clovertech Forums Read Only Archives Cloverleaf Cloverleaf Error Database: Out Of Order Message

  • Creator
    Topic
  • #49006
    Gordon Wilkinson
    Participant

      I am getting the Error message below.  I have checked the HL7 2.2 format and the order is correct and is ordered the same as what is comming out of STAR.  Why would I still get this error message?

      [msg :RecP:WARN/0:     t4_xlate] [0.0.632375013] The # 4 segment encountered ‘NK1’ is out of order for message type ‘ADT_A05’.  Segment ignored.

      01/09/2007 19:14:53

      [msg :RecP:WARN/0:     t4_xlate] [0.0.632375013] The # 5 segment encountered ‘NK1’ is out of order for message type ‘ADT_A05’.  Segment ignored.

      01/09/2007 19:14:53

      [msg :RecP:WARN/0:     t4_xlate] [0.0.632375013] The # 6 segment encountered ‘PV1’ is out of order for message type ‘ADT_A05’.  Segment ignored.

      01/09/2007 19:14:53

      [msg :RecP:WARN/0:     t4_xlate] [0.0.632375013] The # 7 segment encountered ‘PV2’ is out of order for message type ‘ADT_A05’.  Segment ignored.

      01/09/2007 19:14:53

      [msg :RecP:WARN/0:     t4_xlate] [0.0.632375013] The # 8 segment encountered ‘AL1’ is out of order for message type ‘ADT_A05’.  Segment ignored.

      01/09/2007 19:14:53

      [msg :RecP:WARN/0:     t4_xlate] [0.0.632375013] The # 9 segment encountered ‘DG1’ is out of order for message type ‘ADT_A05’.  Segment ignored.

      01/09/2007 19:14:53

      [msg :RecP:WARN/0:     t4_xlate] [0.0.632375013] The # 10 segment encountered ‘DG1’ is out of order for message type ‘ADT_A05’.  Segment ignored.

      01/09/2007 19:14:53

      [msg :RecP:WARN/0:     t4_xlate] [0.0.632375013] The # 11 segment encountered ‘PR1’ is not defined for message type ‘ADT_A05’.  Segment ignored.

      01/09/2007 19:14:53

      [msg :RecP:WARN/0:     t4_xlate] [0.0.632375013] The # 12 segment encountered ‘GT1’ is out of order for message type ‘ADT_A05’.  Segment ignored.

      01/09/2007 19:14:53

      [msg :RecP:WARN/0:     t4_xlate] [0.0.632375013] The # 13 segment encountered ‘IN1’ is out of order for message type ‘ADT_A05’.  Segment ignored.

      01/09/2007 19:14:53

      [msg :RecP:WARN/0:     t4_xlate] [0.0.632375013] The # 14 segment encountered ‘IN2’ is out of order for message type ‘ADT_A05’.  Segment ignored.

      01/09/2007 19:14:53

      [msg :RecP:WARN/0:     t4_xlate] [0.0.632375013] The # 15 segment encountered ‘ACC’ is out of order for message type ‘ADT_A05’.  Segment ignored.

      01/09/2007 19:14:53

      [msg :RecP:WARN/0:     t4_xlate] [0.0.632375013] The # 16 segment encountered ‘ZPI’ is out of order for message type ‘ADT_A05’.  Segment ignored.

      01/09/2007 19:14:53

      [msg :RecP:WARN/0:     t4_xlate] [0.0.632375013] The # 17 segment encountered ‘ZPV’ is out of order for message type ‘ADT_A05’.  Segment ignored.

      01/09/2007 19:14:53

      [msg :RecP:WARN/0:     t4_xlate] [0.0.632375013] The # 18 segment encountered ‘ZPR’ is out of order for message type ‘ADT_A05’.  Segment ignored.

      01/09/2007 19:14:53

      [msg :RecP:WARN/0:     t4_xlate] [0.0.632375013] The # 19 segment encountered ‘ZIN’ is out of order for message type ‘ADT_A05’.  Segment ignored.

      Engine idle — 01/09/2007 19:17:17

    Viewing 2 reply threads
    • Author
      Replies
      • #60449
        Daniel Lee
        Participant

          Something about the varient has to be different then the message that the engine is receiving.  Sometime it will give you an out of order error if there’s an extra segment in the message that isn’t in the varriant.

        • #60450
          Ed Mastascusa
          Participant

            Since you have Z segments displayed in your error messages your xlt would need a variant in order to define the Z-segments.  

            If there is a variant involved then the usual cause of the message is that variant definition isn’t matching the segments you are actually receiving in the A05, as an earlier post suggested.  

            In the GUI, “file/recofigure” will show the variants in use in the translation. You would then need to check how the ADT_A05 message type is defined within your variant.

            BTW, The message is actually a warning and won’t affect your translate as long as you don’t need any data from the ignored segments.

          • #60451
            Alice Kazin
            Participant

              Sometimes it’s the variant used in a tcl proc that is giving this error not just the Xlate.

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