- This topic has 4 replies, 3 voices, and was last updated 15 years, 11 months ago by .
-
Topic
-
I’ve run into this before, and just have never drug it to ground. HL7, CL 5.2, TrxID
Say I have an ORM^O01. That has a sub-field delimiter (sfd) smack in the middle of the mix. The sfd is defined in MSH[2.0], and legally can be many characters.
If you set TrxID determination to HL7, you use a syntax in your route like “ORM_O01”. My assumption is that Cloverleaf is helpfully keeping me from cutting my fingers on that pesky sfd.
In developing my own TrxID procs, I’ve tried several methods to get the same effective output, but I’ve never been able to get there.
I’ve tried: (sfd is in $sfd)
Code:regsub -all {$sfd} $trxId {_} trxId
(with escaping and quoting)
Code:string map {$sfd _} $trxId
(with escaping and quoting)
Every time before, after failing miserably and considering the option of
, I’ve always just put in the ORM^O01 to my route, knowing that one day running with scissors will be my undoing.Hara-kiriCan anybody give me a clue as to how this SHOULD be done?
Thanks!!!!
- The forum ‘Cloverleaf’ is closed to new topics and replies.