MSH-2 Encoding Characters FRL to XML

[Jordan Matos]

I have a process by which we take an HL7 message and put it through an HL7-HL7 xlate.

After this Xlate is done, a post-proc modifies MSH-2 to be “^~\&”.

Then this message goes to another thread an FRL-XML xlate.

The FRL is just one big field to hold the entire HL7 message.

Somehow, after it’s done with this Xlate, MSH-2 is “^~\&”.  Notice the extra “amp;”.

I’m a bit confused as to how this is happening.

 

Raw HL7 message –> HL7 to HL7 Xlate –> Post Proc –> FRL to XML Xlate (new thread)

 

Has anyone run into this?

Topic

[Jordan Matos]

The issue was that when xlating to XML, “&” gets escaped to “&”.

Therefore, it makes sense that if prior to the FRL-XML xlate, if I had “^~\&”, that it would once again escape the ampersand in that string.

[Author]

Replies