Clovertech

kill_msg

› Clovertech Forums › Read Only Archives › Cloverleaf › Cloverleaf › kill_msg

  • Creator
    Topic
  • February 25, 2008 at 5:16 pm #49853
    Mark Perschbacher
    Participant

      I am trying to set up kill_msg to block all ORU messages with the OBR-25 value of P from going out,  here is the argumnent I have

      {PASSCOND ~F} {SEGNAME OBR} {FIELDNUM 25} {SUBFIELDNUM 0}, but it doesn’t seem to be working.  I have the proc applied to the inbound thread, Route Prop., Xlate Route Prop., Pre Proc.   Any ideas?

    • Creator
      Topic
    Viewing 6 reply threads
    • Author
      Replies
      • February 25, 2008 at 6:56 pm #63876
        John Hamilton
        Participant

          I know a dozen or so procedures you pass things to like you are showning.

          Without knowing the script and paramaters it expects it is hard to solve this one.

          Aside from that I almost always do this at the pre-xlate upoc.

          So I hope that helps.

        • February 25, 2008 at 7:02 pm #63877
          Levy Lazarre
          Participant

            Mark,

            The “~” after PASSCOND indicates a negation. So, if you want to let only final results go through, you should write:

            {PASSCOND F}

            If you want to block all preliminary results and let anything else go through, you should write:

            {PASSCOND ~P}

            I hope this helps.

            Levy

          • February 25, 2008 at 7:48 pm #63878
            Mark Perschbacher
            Participant

              Levy, the negation issue was it, thanks for your assistance

            • February 25, 2008 at 8:07 pm #63879
              Mark Perschbacher
              Participant

                Well, I just realised that I need to iterate through the OBR’s.  I am guessing that kill_msg is designed to evaluate a unique, rather than repeating segment.  Can anyone verify this?

              • February 25, 2008 at 8:19 pm #63880
                Levy Lazarre
                Participant

                  Yes. I believe that this is correct. If you want to evaluate another condition, you would have to stack another instance of kill_msg with the new condition. Rather than doing this however, it may be better to write a single script that will take care of both conditions.

                  In your particular case, I am not sure why you need to iterate through all the OBR segments. Generally, results are either P or F. Do you expect a combination of P and F in a single HL7 message?

                • February 25, 2008 at 9:47 pm #63881
                  Mark Perschbacher
                  Participant

                    This particular ORU interface is configured on our host to send out cumulative results.  In other words, if there are three results, an ORU goes out when the first one is released, its OBR has an F in field 25, the last two would have a P.

                  • February 28, 2008 at 8:27 pm #63882
                    Alan James
                    Participant

                      This proc asks for arguments at the segment level, not the message level.  Are we sure it won’t work with repeating segments?  If it finds the condition in any segment, as defined in the arguments, it will kill the whole message, however…

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