[Jodi Agosta2]

The issue in my case was a malformed tclproc for a filter to the thread. I am not sure why the log didn’t give me a tcl error. I deleted the filter and recreated it and everything was fine after that.

[Jodi Agosta2]

I found the problem. It was a malformed pre proc tcl filter.

[Jodi Agosta2]

Hi All,

I am getting this message on resend from two threads that originally worked in the past. I am trying to send to the thread that is dropping the messages. This is on v6.0.  At first I thought it was a filter issue but I took the filter out and still recieved this message when resending to that thread.

Any help would be appreciated.

Thanks,

Jodi

[Jodi Agosta2]

Max, Jim, Thomas,  

You guys are the greatest. Once I got the hang of it , it was amazingly easy to do.  Thanks for giving me such good advise. Very much appreciated.

Jodi

[Jodi Agosta2]

Thanks Thomas, will do.  I did finally get it to iterate but on the wrong value (%g1 instead of my $%s99) . I plan to play with it this afternoon.  I don’t know how I got away with not knowing this for so long. It looks pretty powerful, I just need to figure it out.

[Jodi Agosta2]

Right now I am trying to figure out why my add is not working. Mind you I have never done this before but it seems to be straight forward. Here is what I have

COPY {=Hospital Name}->{1(0).1(0).1(%s99).OBX.00573.[0]

MATH:ADD =1->{$%s99}

COPY {=Patient Name}->{1(0).1(0).1(%s99).OBX.00573.[0]

Keeps clobbering  the hospital name.

If I substitute a static address it looks fine.

btw I am on a windows machine running v5.4.

Thanks for the help.

[Jodi Agosta2]

Thanks Max,

Will do. The thread you gave me is giving me some great ideas on how to make this work.

Much appreciated!!

[Jodi Agosta2]

Hi Levy,

You are a life saver. My poor attempts were not even close. I still have to finish off the build but this will make it so much easier. I like your TCL idea. Thank you for helping me out of a tight spot.

Jodi

[Jodi Agosta2]

I am jus now becoming involved in this type of development. I would be interested.

[Jodi Agosta2]

Hi Debra,

That is great to hear. I was a little nervous about doing this. I am glad to hear that it has worked so well for you.

Thanks for sharing your experience.

[Jodi Agosta2]

Hi Charlie

Here is what I came up with using your suggestion:

set xlatetemp [lrange $xlateInVals 0 0]

set xlatetemp [format %06s [string trimleft $xlatetemp]]

set xlateOutVals $xlatetemp

See my mistake…I was bringing it in with a lrange and not a lindex…That was a two day exercise in making my hair even more gray than it already is.

Thank you for being there for me. You sparked me to rethink about where the problem was.

Jodi

[Jodi Agosta2]

We are also using cell phones for most of our departments. While it is not my area I do know that extensive testing was done around the other devices and we did not find any interference. Our policy does say to not use the phone within 3 feet of a life support device but this is more of a precaution verus us seeing actual interference.

[Jodi Agosta2]

Bryan, you have got me stumped. I set up a test. Flat file to HL7 2.1 DG1.1 field 506 (SI length 4) with that code and it worked perfectly. Are you in a position where you could do a reboot and clear memory? I don’t have a clue as to why that wouldn’t work even though we are on different versions.

Here was my setup for the test

copy   =3  -> 0(0).DG1.00506

with the code I gave you above in the pre tcl area.

[Jodi Agosta2]

Bryan,

Try this. It worked in my test env. I am on W2K v5.1r1. Make sure your receiving field has enough space.

set xlatetemp [string range $xlateInVals 0 3]

set xlateOutVals [format %04d $xlatetemp]

Let me know,

Jodi

[Jodi Agosta2]

Bryan,

This is probably going to be the dumbest idea you get today but if you get really desperate try this..split your grab and format. Get your data and put it in a temp value and then in another line of code format the temp field. You can echo the temp and then echo the format and see the difference….I know, shouldn’t make a difference… I am probably wasting your time.

Sorry,

Jodi

[Author]

Replies