Clovertech

Routing ORM’s

› Clovertech Forums › Read Only Archives › Cloverleaf › Cloverleaf › Routing ORM’s

  • Creator
    Topic
  • April 15, 2010 at 9:53 pm #51698
    Mark Perschbacher
    Participant

      We have a new ORM inbound interface that we are working on, and I need to figure out a way to have Cloverleaf read field 4 of each OBR; multiple OBR’s in a single ORM, and route based on that value.  There are three conditions I need to code.

      1.  Just a pathology order, single OBR with specific field 4 value- send to pathology thread.

      2.  Just a clinical order- send to clinical thread.

      3 Pathology and clinical orders mixed- send pathology order to pathology thread, and clinical orders to clinical thread

      About the only way I can think of doing this is to iterate over the OBR in an xlate, run them through a table that continues the pathology orders in one action, and then in another action, continues the clinical orders.  Anyone else got a more streamlined way to doing this?

    • Creator
      Topic
    Viewing 6 reply threads
    • Author
      Replies
      • April 15, 2010 at 10:40 pm #71340
        David Barr
        Participant

          Why not just write a custom trxid determination proc?

        • April 15, 2010 at 11:00 pm #71341
          Mark Perschbacher
          Participant

            David, thanks for replying.  I started in that direction.  The problem is that in an ORM with four OBR’s, three may need to get routed to the LIS, and one to the pathology system.  It seems like I would have to split the OBR’s apart and rebuild the message for each, rather than have CONTINUE AND SUPPRESS actions within an xlate.  At this point, I am open to suggestions.

          • April 15, 2010 at 11:30 pm #71342
            David Barr
            Participant

              Well, you could route all of the ORM’s to both systems, and use a tcl proc or xlate on each route to strip OBR’s for the other system and kill the message if there are no remaining OBR’s.

            • April 15, 2010 at 11:47 pm #71343
              Mark Perschbacher
              Participant

                kill_msg would certainly work for the pathology thread, that’s assuming it will read through iterations of a segment.  There are only seven pathology order codes.  I would have to modify it to run opposite for the LIS, kill any of the seven pathology codes, and let the others thru.

              • April 16, 2010 at 10:35 pm #71344
                Mark Perschbacher
                Participant

                  I tested kill_msg, and the version I have doesn’t iterate through multiple OBR’s.  It reads the first then stops.  Guess I’ll have to explore the xlate Continue Suppress option.

                • April 17, 2010 at 12:03 am #71345
                  David Barr
                  Participant

                    You could write a new tcl proc instead of using kill_msg.

                  • April 19, 2010 at 11:42 pm #71346
                    Mark Perschbacher
                    Participant

                      I’m still going to try the Continue Suppress actions in an xlate, but for the time being, I used trixid and Route Messages.  It sends a copy of the message into the pathology system for each clinical and multisystem order.  The pathology system deletes unused encounters anyway, so this should work.

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