Converting T to & in ADT message

Here is the code I am using:

regsub -all {\T\$} $xlateInVals {&} xlateOutVals

I need to change the T to and & in a result message.  

thanks

Barbi

Put this tps in the outbound otherwise the message will be truncated since “&” is the special character.

In my situation, I am getting & from HIS. when the engine takes the message, it will discard anything after the “&”. So I had to put a tps script to convert the “&” to T. Receiving systems are handling well.

Hope this helps.

reggie

Ariba,

I would not use an xltp type Tcl script. Rather I would use a TPS script and place it in the Outbound Tps (probably pre-write).

The script would replace all occurrences of T – but why stop there? Why not make allowances for all of the control characters as outlined in the HL/7 specification?

Jim Kosloskey

Ariba,

Well you could use the essence of the provided script (that is the regsub portion) However, all of the xltp type references (xlateOutVals for example) are not effective in a Tps type Tcl proc.

But yes place it in the Outbound Tps (I think pre-write).

Now please excuse me for getting on a soap box…

It is shameful that Cerner or any vendor which claims to be HL/7 compliant does not support use of the HL/7 specified escaping technique.

Personally I would try to shame the vendor into modifying their system to be compliant.

Of course that does not always work and so, luckily, we can make adaptations in Cloverleaf(R) to make up for the vendor’s shortcoming (I would remind them of those shortcomings every chance I get).

It is amazing to me how many vendors do not even know about this escaping technique much less support it.

I am off the soapbox now…

Jim Kosloskey

Its the HL7 committee’s fault for using & as a special character. I don’t know about you but I use this a common abbreviation for ‘and’ on a regular basis and have done for nearly 30 years since somebody introduced it to me:-)

Regards

Garry

Garry,

I respectfully disagree.

It really does not matter what characters you use for separators (you can define MSH-1 and 2) the possibility exists the characters could be used as data.

Knowing that, the committee wisely (in my opinion) provided for a mechanism to escape those characters.

It is the vendors who apparently are incapable of following a standard.

Jim Kosloskey

Ariba, which Cerner product are you using?  Millennium Open Engine supports standard escaped characters in most fields. The properties ENABLEESCAPES=”1″ (true) and ESCAPEDELIMITER=”” must be applied to the inbound comm server.  Use the OEN_PROC_VIEW utility to apply the properties. Millennium OE also supports variable HL7 message delimiters with the HL7DELIMS property, with default being

Sorry Jim,

My comment was tongue in cheek but it was amusing to read this as I’ve recently had the same problem with a couple of vendors.

Interestingly, one site insisted that we trap EVERY non-valid/escape character that could accidently be entered on the keyboard of the third party vendor’s system so I have a set of regsub’s for all HL7 control chars.

Regards

Garry

Garry,

My apologies for misinterpreting your post.

Jim Kosloskey