Clovertech

Segments out of order warning with Static, Raw Routing

› Clovertech Forums › Read Only Archives › Cloverleaf › Cloverleaf › Segments out of order warning with Static, Raw Routing

  • Creator
    Topic
  • January 31, 2013 at 10:24 pm #53501
    Donna Bailey
    Participant

      Has anyone had this happen?  I have a static, raw route of an ORM….but I am getting segments out of order errors in the log.  My Inbound defines it as an HL7 message, but I’ve also tried FRL.  Can’t get the errors to go away!

      Any help is sure appreciated!

      Thanks,

      Donna

      Donna Bailey
      Tele: 315-729-3805
      dbailey@microstar.health
      Micro Star Inc.

    • Creator
      Topic
    Viewing 6 reply threads
    • Author
      Replies
      • February 1, 2013 at 3:08 pm #77871
        Max Drown (Infor)
        Keymaster

          Donna, my guess is that something else is amiss, possible something simple. Such as not bouncing the process after changing the route from xlate to raw or another pair of threads in the same process.

          -- Max Drown (Infor)

        • February 1, 2013 at 5:09 pm #77872
          Donna Bailey
          Participant

            This interface was in test….and doing the same thing when I moved it to live….Never had an xlate associated to it.  Been bounced numerous times????  Weird huh???

            Donna

            Donna Bailey
            Tele: 315-729-3805
            dbailey@microstar.health
            Micro Star Inc.

          • February 1, 2013 at 5:16 pm #77873
            Max Drown (Infor)
            Keymaster

              Are there other threads in the same process?

              -- Max Drown (Infor)

            • February 1, 2013 at 7:14 pm #77874
              Robert Milfajt
              Participant

                Whenever I see these, it’s because the format is bad on some Xlate.  Never seen on a static raw route before.  Do you have any other routes this may be coming from for within that process??

                Robert Milfajt
                Northwestern Medicine
                Chicago, IL

              • February 1, 2013 at 8:08 pm #77875
                Donna Bailey
                Participant

                  There are other threads in the process, but it’s specifically saying fr_mac_ord…I tuned the logging up on the thread and it’s showing up when the messages are received from that thread.

                  The other weird part is, all the segments I am getting the error on, are in the outbound message…..

                  I’m sure it’s something silly….I just can’t find it….

                  Donna

                  Donna Bailey
                  Tele: 315-729-3805
                  dbailey@microstar.health
                  Micro Star Inc.

                • February 1, 2013 at 10:07 pm #77876
                  Michael Hertel
                  Participant

                    Check your check_ack proc. Defined in Outbound tab>Inbound Replies>TPS Inbound Reply

                    It may use a VARIANT to parse the ACK message. These are user arguments for us.

                    Perhaps you could post a snippet of your error log?

                  • February 5, 2013 at 9:07 pm #77877
                    Donna Bailey
                    Participant

                      It wasn’t the check_ack proc, but thank you for pointing me in that direction…it was the Raw HL7 proc….it had arguments with the reference to HL7 message.  I changed that to the cloverleaf standard HL7Raw_ack proc and it fixed the problem.

                      Thanks to all for your responses!

                      Donna

                      Donna Bailey
                      Tele: 315-729-3805
                      dbailey@microstar.health
                      Micro Star Inc.

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