[Scott Smith]

I had already fixed, but after I posted code online.

[Scott Smith]

thanks guys.  I got it working now.  I moved suppress to beginning and moved continue to after second iterate.

[Scott Smith]

Moving the brackets fixed one error now I get:

rong # args: no script following “{[string equal $MSH8 “A08″] && [string equal $PV13” argument’

[Scott Smith]

I found them they are there, just after 2 echos I put in here is the entire statement:

if {[string equal $MSH8 “A08″]} && {[string equal $PV131 ” “]} {

                           set dispList

                        }

                        else {

                           set dispList

                       }

                     

                       if {[string equal $PV132 “B7E”]} {

                           set dispList

                       } else {

                           set dispList

 

                     

 

 echo $mh    

 echo $dispList

 }

[Scott Smith]

Actually I want to search a table with values from OBR 16 and OBR 28.  these values might not be the same.

[Scott Smith]

For some reason I had created xlate and varaint for 2.3.1 while the message was 2.2.  When I changed it to correct verison everything worked out.

[Scott Smith]

Mike,

I like those.  I was trying to use a already proc and modify it.  That looks much better.

And Bob thanks for the debugging help – I finally got it going.

[Scott Smith]

Bob,

It  must be one of those weeks.  I changed both “sets” to lappend and now I get the “bogus msgStrId…: error.  

Could it have something to with that I am killing the message by default and if it is found in table to continue the msg?

[Scott Smith]

Thanks Bob.

I fixed that error, now I getting

[0:TEST] ‘CONTINUE’ (returned by ‘tpsfilterdoccw_tbl ‘) does not match { }

[0:TEST] ‘message0’ (returned by ‘tpsfilterdoccw_tbl ‘) does not match { }

I don’t think I have seen this one before, do you know what it means?

[Scott Smith]

Thanks Mike.  worked like a charm.

[Scott Smith]

Jim,

Actually I doing thru TCL.  I thought I found a piece of code, but it is still pulling the whole field instead of data before first separator.  Here is what I have so far:

         # get the field separator from the hl7 message

           set fieldSeparator [crange $msg 3 3]

           # get the field from the hl7 message

           set OBRsegment [getHL7Segment $msg OBR]

           set drNumber [getHL7Field $OBRsegment 16 $fieldSeparator]

set obrFlds [split $OBRsegment $fieldSeparator]

            set obr16 [lindex $obrFlds 16]

echo $obr16

   set drNumber [crange $drNumber 0 3]

  set drNumberList $drNumber

echo drNum:<$drNumber>

Any help?

[Scott Smith]

That’s the idea I was looking for.

[Scott Smith]

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?

[Author]

Replies