About

What we are trying to do

When an HL7 message fails, the error you get from the receiving system is usually one line long and not very helpful. We want to give you the next step: where exactly the problem is, which rule it breaks, and what a valid value would look like.

That is why the tools do more than say OK or error. They read HL7 v2 field by field, check FHIR R4 resources, convert HL7 v2 to FHIR and show every mapping row they used, and let you compare messages and load the rules of a specific receiver.

Why it exists

Most tools in this area are either paid, hard to install, or built around a single vendor. We wanted something you can open in a tab, use in the middle of an integration problem and close again, without creating an account.

Your messages usually contain patient data, so everything runs in your browser. Nothing you paste is sent to a server, and there is no analytics on its content.

What it is not

These tools are for testing and development. They do not certify conformance, they are not a medical device, and they should not be used for clinical decisions. A message that passes here can still be rejected by a receiving system that has its own rules.

hl7validator.com is independent and is not affiliated with or endorsed by HL7 International. HL7 and FHIR are registered trademarks of HL7 International.

Contact

Questions, a message that is checked wrongly, a rule that is missing or a translation that reads badly: write to hl7validator@gmail.com.

The tools

Validate HL7

check an HL7 v2 message against the standard and, optionally, a receiver profile

Validate FHIR

check a FHIR R4 resource or Bundle in JSON

HL7 to FHIR

convert an HL7 v2 message to a FHIR R4 Bundle

Reference

browse HL7 v2 versions and the HL7 v2 to FHIR maps