All,
What if the Cloverleaf engine checks if the field has sub-components first? I agree that the issue is in the sender’s side but some times is hard to convince the vendor to fix it for free (some times the app team has no idea on how to fix it)
But, what if the Cloverleaf parser checks that field in the HL7 variance before interpreting the & as a separator?
If the HL7 field is defined as containg sub-components, then the & should be interpreted as a separator by the xlate, but if it is defined as text, then it should be interpreted as another character.
Will something like that work for everybody? Is this doable by Quovadx?
Best regards,
Carlos
