Xlate not reading all of string ~ can’t believe I’m stumped.

[Nate Kruse]

As the title says, I can’t believe I’m stumped on this…

Description:  Inbound thread is reading in a FRL file into a tcl script.  The tcl script does some good stuff, and recreates the FRL data into a string variable.  The string is then passed to the xlate.  The xlate makes an A08 message out of the FRL data.  In the outbound thread Xlate Route Details, the tcl proc is the Pre Proc and the Xlate is listed in its Xlate spot.

Problem:  I’m passing the xlate several different patients in the string; however, it only reads the first row and creates one message.  In the FRL string, I’ve tried changing the end of row character from n to r to rn to ~.  It seems to me that the xlate is reading the first row, then hitting the end of row character and stopping.

It is probably something simple that I’m missing.  Any thoughts?

Thanks for any input.

Nate.

Topic

[Robert Milfajt]

If the end of row character is n (newline) that is probably your problem.  In fact the whole record may not be passed, if the inbound is a new line file.

If not, please give more specifics, i.e., sample data, to help better diagnose the problem.

Hope this helps,

Robert Milfajt
Northwestern Medicine
Chicago, IL

[Max Drown (Infor)]

In the HL7 world, a tilda (~) represents a repeating field.

ZSH|blah blah blah ~ foo foo foo|||||….

ZSH(0).01 –> blah blah blah

ZDH(1).01 –> foo foo foo

This may be causing your problem. Then again, it may not be. 🙂

-- Max Drown (Infor)

[Nate Kruse]

How about I ask that if you guys would build a string of different patients to pass to an xlate that builds HL7 messages, what ending character would you use to denote the end of a line?

[Max Drown (Infor)]

I would use a newline (n).

-- Max Drown (Infor)

[Chris Williams]

How about separating the names with white space and passing the patient names as a tcl list. Then you can use

Code:

for patient $patientList {
   (do stuff with $patient)
}

[John Hamilton]

Do you want each patient to have it’s own HL7 outbound message.

It is not clear to me as to what the ultimate goal is.

[Nate Kruse]

John Hamilton wrote:

Do you want each patient to have it’s own HL7 outbound message.

It is not clear to me as to what the ultimate goal is.

Correct, each patient (one per FRL line) would have it’s own HL7 message.  It is currently reading the first line of the FRL string and creating only one HL7 message.  I know all of the FRL string is being passed as I’ve written it to a file, but not sure why the xlate won’t iterate through the whole list.

Example of FRL string:

Nate      Test      123 Main St. …(n)

Beth      Test      PO Box 12 …(n)

Stan      Test      55 10th St. …(n)

My xlate output is just a HL7 message for Nate Test and no messages are created for Beth and Stan.

[John Hamilton]

In your Xlate ?

Do you iterate through  the names and use a contine  at the bottom to create each messages.

Can you post your inbound frl and your current translation ?

[Robert Milfajt]

John is right, we do not have enough information.  You may have set your inbound file definition up incorrectly too, so if you could add the snippet from NetConfig that contains the defnition of the inbound interface, along with what John asked, we should be able to see what is wrong.

Robert Milfajt
Northwestern Medicine
Chicago, IL

[Nate Kruse]

It has been a couple weeks since I was able to work on this, but it is figured out.  We had our Quovadx contact on site for some knowledge transfer and with his help we were able to get this working.  It was an issue of how I was passing the new values to the xlate.  I was trying to pass them all at one time rather than passing one row at a time (so to create one message for each line).  

Thanks for all of the input on this.  I appreciate your time.

[Author]

Replies