& getting converted to ^ in translation

[Anna Flores]

Good Afternoon Everyone!

where to begin…

how do i maintain the integrity of “garbage in, garbage out”?

Let me try to explain with an example

1 of many examples…given HL7 standard delimiters…I have a system that is sending & in PID.5 HL7 v2.3 (XPN data type). During translation to PID.5 HL7 v2.2 (PN data type), the & is getting converted to ^. I’m assuming that the engine is trying to correct the formatting of the field to reflect the data type definition.

Can someone explain why the engine is doing this?

How can I prevent this…or can I?

We are on QDX V5.2 Rev 2 on AIX 5.2.0.0

Your input is greatly appreciated…

Anna M Flores

Lead Programmer/Analyst

Memorial Hermann

Houston, TX

713-448-6259

Topic

[Dorian DiNardo]

Hi Anna,

I think you can change your field on your outbound HL7 variant to XPN. Otherwise I would write a post proc to substitute the ^ for an & in PID.5.

Good luck,

Dorian

[Anna Flores]

Thanks Dorian. I instead changed the XPN to PN since I did not have the option in 2.2 to change the PN to XPN. I still get the & changed to a ^.

The real fix is for my sending sysem to not send & as text in the HL7 fields. They are exploring feasible options.

However, I would really like to know if someone has an explanation for what Cloverleaf translator is doing and why.

THANKS!

The weekend is upon us…hope everyone has a good one!

Anna M Flores

[Author]

Replies