Records

Understand FHIR data. Verify the change.

Check conformance and data quality before your next FHIR release or data handover. Understand the findings, verify a correction and share a result your team can review.

Open public demo Plan your evaluation

Explore public test resources without an account. Evaluate your own workflow in a staged workspace.

Browse a delivery, explain the finding and verify its correction

Check conformance: Validate resources against the selected profiles, terminology, and project rules.
Measure data quality: Examine completeness, uniqueness, and reference integrity within an agreed dataset.
Verify the change: Investigate a finding, repeat the checks after a correction, and preserve the result.

Choose your decision

What do you need to know before FHIR moves forward?

Start with a release, an integration, or a research data delivery. Agree the checks and acceptance question, then compare results under a compatible validation basis.

Release & CI

Can this change move forward without a new FHIR regression?

Release Safety CI/CD Quality Gate

Change & comparison

What changed across runs, environments, or suppliers?

Drift Detection Multi-Server Comparison

Quality & evidence

Does this dataset meet the receiving team’s expectations?

Document Checks Research Data Quality Validation Reports

Automation

Can generated or transformed FHIR move downstream safely?

Agentic FHIR Workflows Claude Code guardrails

Technical foundation

Controlled by default. Verifiable by design.

Records keeps source data at its boundary and makes the validation engine independently inspectable.

Deployment and data boundaries

Validate beside your FHIR infrastructure.

Records runs beside your FHIR infrastructure, reads by default, and retains derived evidence instead of source payloads.

Hosted or customer-managed operation
No source payload retention
Read-only by default; operators control writes

Deployment options Trust and data handling

Open source · Apache-2.0

Verify the validator.

Inspect the open-source TypeScript engine, run it on your fixtures, and review the scope and limits of its archived reference comparisons.

Validate one FHIR fileShell

npx -p @records-fhir/validator \  records-fhir-validator ./patient.json

Review the evidence Source on GitHub

Start with one workflow

Try the demo. Then evaluate your next delivery.

Explore public test resources now, or plan a scoped evaluation of your own workflow: agreed checks, findings to review, and a repeat run after one correction.

Available now

Public Demo

Browse public FHIR test servers and inspect resources with live validation context. No account required.

Open public demo

Staged access

Records Workspace

Evaluate one FHIR delivery: conformance and quality checks, findings, and a repeat run after a correction. Workspace access is staged.

Plan your evaluation

Qualification

Enterprise

Qualify hosted production or customer-managed operation for regulated, procurement, and data-policy requirements.

Explore Enterprise