Records

Continuous FHIR validation for every release.

Records compares every FHIR run with an accepted validation basis, shows what changed, and takes teams from the gate signal to the affected resource and field—so the next release decision is clear and reviewable.

Open public demo Run locally

Records release investigation from the Production quality gate through run 14511 to the affected Observation and its validation result.

Compare each run: Hold every result against one accepted validation basis.
Explain the delta: Trace the gate signal to the affected resource, field, and constraint.
Decide with context: Keep the run inputs and result attached to the release decision.

Choose your decision

What do you need to know before FHIR moves forward?

Start with the decision. Records uses the same validation basis across release, comparison, handover, and automation paths.

Ship safely

Can this change move forward without a new FHIR regression?

Release safety CI/CD quality gate

Understand change

What changed across runs, environments, or suppliers?

Drift detection Multi-server comparison

Prove readiness

Can this result be handed over and defended?

Regulatory evidence Reporting readiness Research evidence

Automate safely

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

Continuous validation, not another clinical data store.

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; operators decide and act

Deployment options Trust and data handling

Open source · Apache-2.0

Verify the validator.

100.0% parity across 536 in-scope HL7 test-suite comparisons at a pinned public commit.

Validate one FHIR file

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

536/536

HL7 comparisons matched

Differences

Review the benchmark Source on GitHub

Public demo

From the server fleet to one profiled Patient.

Choose a public synthetic server, open its Patient resources, and inspect the profile and field context without creating an account.

Open the public demo

Records public demo flow from all available FHIR servers through a synthetic server overview and Patient list to the profiled Patient detail.

Choose the access path

Start with the boundary you can use today.

Public browsing is available now. Hosted workspaces are staged. Production and private operation begin with an enterprise boundary review.

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 saved runs, gates, and evidence in a staged workspace using a permitted test, synthetic, or de-identified server.

Request staged access

Qualification

Enterprise

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

Explore Enterprise

Continuous FHIR® validation for every release.

What Records does