Fhir Validator

Best FHIR Validators for IG Conformance Testing in 2026

Implementation guides are how FHIR becomes specific. Every serious FHIR program ends up writing or consuming an IG, and conformance testing against that IG is the discipline that separates a working integration from a hopeful one. A validator that handles IG conformance has to load the IG package, resolve cross-IG dependencies, and report errors against the IG's own profiles rather than against base FHIR. The four below are the validators that hold up to real IG conformance work in 2026. The complete guide to FHIR validators covers the broader frame.

For more reviews of this kind, FHIR tool comparisons and shortlists gather the rest of the relevant reads.

The Validators That Earn the IG Conformance Label

  1. HL7 Java Reference Validator. The official tool, kept current with the FHIR release train. Handles IG packages via the standard NPM mechanism and reports errors against the IG profiles cleanly. The baseline most teams start with.
  1. Firely Terminal. Commercial tool with strong IG authoring and conformance features. Suits teams writing their own IG, where the same tool authors profiles and validates conformant resources.
  1. HAPI FHIR Validator. The Java library used inside HAPI; loads IG packages well and integrates into Java-based pipelines. Production-grade for teams already on HAPI.
  1. Inferno Framework. The ONC-blessed conformance tool, particularly strong for US-centric IGs (US Core, USCDI). The right pick when the conformance check is part of an attestation or certification process.

What IG Conformance Adds on Top of Base Validation

A base-FHIR validation pass is necessary but not sufficient for IG conformance. The IG layer adds three things.

The first is profile resolution. An IG defines profiles that tighten base FHIR resources; the validator has to load these profile definitions and check the resource against them. The reference validator and HAPI both handle this through the standard IG package format.

The second is the cross-IG dependency graph. Most non-trivial IGs depend on other IGs (US Core depends on FHIR R4 base, mCODE depends on US Core, payer-specific IGs depend on US Core). The validator has to resolve this graph correctly or it produces phantom errors. The top 5 FHIR validators for US Core conformance review covers the US Core dependency specifically.

The third is the conformance-testing harness. An IG is usually accompanied by example resources that should pass validation; a serious IG validator runs these as part of its own self-test, so a broken IG load fails loudly rather than passing every resource silently.

How to Pilot for IG Conformance Specifically

The pilot is straightforward. Load the target IG (US Core, mCODE, Da Vinci PDex, whatever the program demands) into each candidate validator. Run the IG's own example resources through the validator. A validator that passes valid examples and fails intentionally broken ones is doing its job; one that disagrees with the IG's own examples is signaling a profile-resolution bug worth investigating before committing.

For the related REST-surface question of how the validator exposes the $validate operation, the top 5 FHIR validators for $validate REST operations review covers the integration shape that matters once the validator choice is settled. Conformance work is one area where the open-source reference tooling is genuinely the safest pick for most teams; the commercial options earn their cost only where IG authoring and validation share the same workflow.

Sources