Forum Replies Created
-
AuthorReplies
-
Just developed this same xlate for a vendor. In my case, I had all of the associated procedures listed in AIS-3.1 for each applicable resource group. In my case, I was only interested in endoscopy cases, so the first iterate checks for “ENDO” in AIL-3.
I’ve attached the applicable xlate portions. Maybe this will help you with your code?
No specific reason – I used snippet from tcl code I found somewhere else..
Thanks, Dave, Jim and Marc. With your collaboration, I was able to get the tclproc working. 8)
I was testing this tclproc on a pair of new threads I had created for the purpose of trying to get this proc to work, but once I just added the proc to my working threads with translation I see progress. Now, the file is written out as defined in the protocol details, but the tcl renaming still isn’t getting done. When I check the logs, I see the following:
Code:[fset:wrte:ERR /0: to_talx:07/24/2013 16:23:59] ‘15424_072413_tstin.v5’ does not match ‘key value’
File successfully copied.
[cmd :cmd :INFO/0: batch_cmd:07/24/2013 16:23:59] Receiving a command
[cmd :cmd :INFO/0: batch_cmd:07/24/2013 16:23:59] Command client went away. Closing connection.
15424_072413_tstin.v5
[fset:wrte:ERR /0: to_talx:07/24/2013 16:24:21] ‘15424_072413_tstin.v5’ does not match ‘key value’15424_072413_tstin.v5 is the real filename I’m trying for, instead of the generic one I originally referenced in this thread. Does this have something to do with how I’m trying to set the key in
msgmetaset?Tried your suggestion, but it still didn’t work. Thanks, though 😀
Right – adding EVN as optional fixes the translation error. I was under the impression that a variant did not have requirements outside of what is defined in the format.
Thanks both for looking it over 😀
Nevermind — I’ve answered my question for myself. 😯
January 16, 2013 at 5:11 pm in reply to: Set format to concat multOBX segments into one segment #77796Just in case anyone uses this thread as a reference in the future, there’s several mistakes in the above that needed to be worked out.
The most substantial being that the inbound concat fields did not need to be split into a list, since they will come in as a list. Removed the “=+” from the xlate and the “[split $xlateInVals +]” from the tcl.
😳
January 16, 2013 at 1:25 pm in reply to: Set format to concat multOBX segments into one segment #77795Thank you! That worked nicely.
-
AuthorReplies