Profile validation
Check resources against the FHIR profiles you expect.
Surface missing elements, cardinality issues and structural mismatches with the affected path kept in view.
Patient
Cardinality ✓Required fields ✓References !
Hgear Validation
Validate FHIR profiles, terminology and conformance.
Inspect conformance issues across profiles, required fields, references and terminology, with results organized so they are easy to act on.
Profile conformanceRequired fields & cardinalityTerminology bindingsReference integrity
Validation tools
Find FHIR profile and terminology issues in context.
Instead of a wall of errors, findings are organized around the rules, locations and resource context that produced them.
Terminology + references
Review coding and reference issues in context.
Locate terminology and relationship problems quickly so implementation teams can resolve them before data moves on.
code718-7
→systemLOINC
→Matched
How it works
From a resource to findings you can act on.
Validation runs the same way in the browser and through the API, so results are consistent from development to production.
Choose the profile or implementation guide
Validate against base FHIR or a specific profile such as a US Core resource, depending on what the receiving system requires.
Run structural and cardinality checks
Required elements, must-support flags, data types and cardinality are checked against the selected profile.
Check codes and references
Coded values are checked against their bound value sets, and references are checked for targets that exist and match the expected type.
Resolve findings by severity and path
Each finding carries its severity, element path and resource, so teams can fix root causes rather than symptoms.
Profile & terminology checks
Every finding comes with its severity, element and reason.
Findings are grouped by severity, element path and affected resource, so the next step is always clear.
- Errors, warnings and information separated by severity
- The exact element path for every finding
- Terminology and reference issues shown alongside structural ones
SeverityElementFinding
errorPatient.identifierRequired element is missing
warningPatient.genderCode not in bound value set
warningObservation.subjectReference target not found
infoPatient.telecomMust-support element absent
Why validate before you integrate.
A FHIR resource can be well-formed JSON and still fail the profile a receiving system expects: a required identifier is missing, a code comes from the wrong system, a reference points to a resource that does not exist. Those problems are cheap to fix during development and expensive once data is flowing between organizations, so validation belongs early in the workflow, not at the end.
Hgear validates resources against base FHIR or a chosen profile, checks terminology bindings and reference integrity, and organizes findings by severity, element path and resource. The same checks run in the Care Compliance Validator and through the REST API, which means the rules your team tested interactively are the rules your pipeline enforces.
Workflow integration
Put validation inside the workflow.
Use the same validation logic during development, testing and repeatable API-driven processing.
01
Profile checks
Validate expected structure and terminology
02
Issue reporting
Return findings with severity and element path
03
Pipeline ready
Gate data before it moves downstream
Common questions
FHIR Validation FAQ
What does FHIR validation check?
FHIR validation checks a resource against the rules used by a workflow: its structure, required elements, cardinality, selected profiles and terminology constraints. Review findings by severity and resource path. The checks available depend on the selected validator, FHIR version, profiles and terminology configuration.
Explore the Care Compliance ValidatorDoes valid FHIR mean the data is complete and accurate?
No. Conformance to a profile does not establish that every clinical fact is correct or that the data is sufficient for a particular use. Review completeness and consistency as separate quality dimensions, and compare results with source data and downstream requirements.
Understand healthcare data qualityWhat information is needed to investigate a validation error?
Use a synthetic or de-identified example and record the FHIR version, selected profile, affected resource path, severity and validation message. Inspect referenced resources and any codes involved, correct the source or mapping as appropriate, then validate the updated output again.
Inspect FHIR resources and referencesWhat's next
Understand what is inside your FHIR data.
Move from validation results into readable resource views, relationships and nested structure.