xlate string range help

This topic has 5 replies, 4 voices, and was last updated 18 years, 6 months ago by Nora Katz.

Creator

Topic
July 3, 2006 at 8:10 pm #48621
Nora Katz
Participant
I wanted to limit a OBR field to 29 characters, so I have the following xlate pre-proc

lassign $xlateInVals input

echo $input

set xlateOutVals [string range $input 0 28]

echo $xlateOutVals

But, if the input is Urine Macroscopic I get back Urine and if the input is C-Reactive Protein I get back C-Reactive in the Testing Tool. The echo lines look like the output I want.

The space in the name appear to be the problem. Is this just a problem with the testing tool or is my tcl incorrect?
Creator

Topic

Viewing 4 reply threads

Author

Replies
- July 3, 2006 at 8:53 pm #59186
  Jim Kosloskey
  Participant
  Nora,
  
  The arguments you receive when invoked by Xlate are lists (with the exception of xlateId).
  
  You need to treat them as such Including the argument(s) you return.
  
  Jim Kosloskey
  
  email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.
- July 4, 2006 at 2:41 pm #59187
  Max Drown (Infor)
  Keymaster
  When you echo a list, tcl will print out the whole list giving the impression that the WHOLE list is a single element of the list.
  
  Code: tcl>set tmp [list blah blah blah] tcl>echo $tmp blah blah blah tcl>echo [lindex $tmp 1] blah tcl>
  
  When you return values, you have to make sure that you return a string as a single element.
  
  Try something like this:
  
  Code: set newString [string range $input 0 28] set xlateOutVals [list “$newString”]
  
  -- Max Drown (Infor)
- July 5, 2006 at 12:29 pm #59188
  Michael Lacriola
  Participant
  Why use a xlate? Modify the variant for the OBR field to be 29 in length. Simple.
- July 5, 2006 at 12:41 pm #59189
  Jim Kosloskey
  Participant
  The variant might be a shared use variant and/or the field could be one of the fields used in multiple segments.
  
  Not all uses may want the length changed.
  
  Jim Kosloskey
  
  email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.
- July 5, 2006 at 5:04 pm #59190
  Nora Katz
  Participant
  Thank you all for the responses. Yes, we did consider changing the length of the field, but we have many interfaces, and as we build interfaces in the future, we did not want to limit all interfaces to this length limitation that only one receiving system needed at this time.
  
  Jim provided me with a reusable tcl proc that worked great!
  
  Thanks again.
Author

Replies

Viewing 4 reply threads

The forum ‘Cloverleaf’ is closed to new topics and replies.