Value changing between Xlate and post Xlate Tcl script

[Barb Dozier]

We have an interface that changes a batch flat file into a file of HL7 messages.  In our Xlate we translate the flat file fields into the appropirate HL7 equivalents.  Part of this is to place the message count into the BTS 1 field.  We then have a post xlate proc that strips the other HL7 segments from before the BTS and FTS segments.  We see a value leave the xlate in the BTS 1 field via a post statement ‘echo’ however when the message gets to the post xlate tcl script it has a value of 0 in BTS 1.  What would be causing this value to change between the xlate and the script.

Thanks in advance for the assistance.

Barb Dozier

Topic

[Anonymous]

Barb…there could be a couple of reasons for this.  Can you attach some code so we can see what you are trying to do?

[Russ Ross]

I would be curious to try not stripping out the undesired segments so you simplify the number of steps and see if the BTS-1 field is still 0.

This will help determine if the post xlate proc that strips off undesired segments is causing the BTS-1 field to become 0.

I would suggest keep reducing the number of steps until you get the BTS-1 segment to be valued as desired.

Once you accomplish that then progress forward and start adding back one peice at a time the desired extra steps until you have them all working.

If it turns out you think your segment stripping proc is the problem I can provide you with one that is knonw to work and we have been using for years successfully.

Russ Ross
RussRoss318@gmail.com

[Barb Dozier]

Unfortunately the code from the time of the original post is gone.  We have made a variety of changes.  What we ended up doing as the value of BTS-1 at every step was 0 is to perform all formating of the BTS and FTS segments in the post route tcl script.  Things are looking good now.

Thanks, Barb

[Author]

Replies