Support
Everything on this page runs in your browser. The message is not uploaded, and the page makes no request of any kind carrying your data.
This is not a conformance validator, and a clean result is not a clean bill of health. It checks three things: the encoding characters against what the header declares, the format of every field the dictionary types as a date or a timestamp, and the segment orderings that hold for every message type. It does not check whether the message carries the segments and fields its own type requires, or how many of each, or whether any coded value exists in the receiving system - so a message that passes here can still be rejected for the first field a receiver looks at. Everything it does not look at is listed with every result.
To see how the whole message was read, field by field, use the HL7 v2 Parser.
This list does not change with the result. It is what the tool never looks at, and it travels beside a clean result on purpose.
Which fields failed which check, and what kind of thing is wrong with each. No values are included - not a date, an identifier, a name or a code - so this can be pasted into a ticket or an email without editing it first.