How can I validate a message containing custom components? One of our
partners sends HL7 messages with custom components that depart from the
HL7 standard. The default validator catches this violation of the
standard and spewes out the exception. Could I configure the validator
so it skips the field with the violation? Or could I re-write the
specific field so that it conforms to the HL7 standard?
I would like to keep the validation feature on before parsing these
messages. Until, I find a way to skip over this "custom" field, we are
halting the processing of these messages. Nevertheless, we would like
to have a means to overcome this issue.
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Hl7api-devel mailing list
Hl7api-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hl7api-devel
