Skip to content

Validate FHIR profiles, terminology and conformance.

Inspect conformance issues across profiles, required fields, references and terminology with results that are easier to act on.

VALIDATION · RESOURCE → RULES → RESULTS

VALIDATION WORKFLOWS

Find FHIR profile and terminology issues in context.

Instead of a wall of errors, organize findings around the rules, locations and resource context that produced them.

PROFILE VALIDATION

Check resources against selected FHIR profiles.

Surface missing elements, cardinality issues and structural mismatches with the affected path kept in view.

Open Care-Compliance Validator
Patient
Cardinality ✓Required fields ✓References !

TERMINOLOGY + REFERENCES

Review coding and reference issues in context.

Make terminology and relationship problems easier to locate so implementation teams can resolve them faster.

Request validation documentation
code718-7
→
systemLOINC
→
Matched

PROFILE & TERMINOLOGY CHECKS

Check resources against profiles and terminology.

Review profile and terminology findings by severity, location and affected resource.

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

02
Issue reporting

Return actionable locations

03
Pipeline ready

Use in repeatable workflows

Request API documentation

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 Validator
Does 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 quality
What 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 references

WHAT'S NEXT

Understand what is inside your FHIR data.

Move from validation results into readable resource views, relationships and nested structure.

Explore Visualization