Clovertech

Route messages based doctor

› Clovertech Forums › Read Only Archives › Cloverleaf › Cloverleaf › Route messages based doctor

  • Creator
    Topic
  • October 1, 2008 at 6:59 pm #50336
    Scott Smith
    Participant

      I need to take ORU messages and route to at least 3 different threads based on doctor.  I think I can use a lookup table with the dr number being on the left side.  I am not going to be able to add any fields to the message, so what do I do with the returned value of dr number?

      Any examples would be great as I am on a time crunch with this one.

      Also, where would be the best place put this proc?  I need to have route determined on my inbound thread before sending the message.  These messages are being sent raw, so there is no xlate(s).

      Any help would be great

      Scott Smith

    • Creator
      Topic
    Viewing 4 reply threads
    • Author
      Replies
      • October 1, 2008 at 7:10 pm #65688
        Dennis Pfeifer
        Participant

          Even though you are routing raw, you can still put in a proc in the route.

          Send the message to all three destinations, then kill it on two of them.

          You could use the same proc on all three, and have a parameter on each route indicating the ID to keep …

          Dennis

        • October 1, 2008 at 7:17 pm #65689
          Scott Smith
          Participant

            So Dennis,

            Could I put the dr ID on the left and KILL, CONTINUE. etc on the right and use that value to match on each route.  Then I would put the proc in each route, right?

          • October 1, 2008 at 7:38 pm #65690
            Dennis Pfeifer
            Participant

              That’s an option…

              You could use one table instead of three (sounds like you intend to use three) ..

              Input would be Dr. number. output would be destination interface ‘id’ ..

              then put the ID as a parameter to the tcl proc.

              If the ID returned by the table look up does not match the ID in the parameter, then kill the message..

              You would use a different ID on each route…

              Dennis

            • October 1, 2008 at 7:43 pm #65691
              Scott Smith
              Participant

                That’s the idea I was looking for.

              • October 2, 2008 at 1:28 pm #65692
                Alan James
                Participant

                  Build three threads.  Use the kill_msg.tcl proc (attached) on each thread, varying the arguments to filter your ORU transactions accordingly.  I

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