The release-quality layer for FHIR teams.

Records connects each validation run to its accepted basis, concrete findings, and reproducible decision evidence.

Explore public servers Run validation locally

Records Validation Runs with a selected Production run, accepted baseline, release policy, disposition, affected resources, and evaluation lanes.

The product spine

One run carries the complete decision context.

The run is not just a validator result. It keeps the measured scope, comparison basis, policy, findings, and downstream decision connected.

Basis: Source, scope, profiles, terminology, rules, and policy.
Result: Coverage, affected resources, evaluation lanes, and highest impact.
Decision: Accepted baseline, release correlation, disposition, and evidence.

Walk the complete release-quality loop

Investigation

Move from the signal to the exact field.

Aggregate counts show where to start. Records keeps the selected resource, profile, field path, and validation message visible together so the team can explain the delta without rebuilding context by hand.

Open the affected resource directly from the run.
Keep structural, terminology, profile, and rule findings in one context.

See the investigation flow

Evidence

Keep the result reproducible after the screen closes.

A status alone is not evidence. Records binds the result to the validator, source, timestamp, pinned packages, settings, and integrity metadata that produced it.

See the evidence workflow

Opened Records evidence report with validator, source, timestamp, pinned implementation guide packages, integrity hash, and run metadata.

How Records fits

One validation contract, with an explicit operating boundary.

Use the engine where work starts, then add shared run context without turning Records into the source system.

Integration surfaces

Different entry points, one validation contract.

Start in the surface closest to the workflow. Move into Records when a one-off result needs history, comparison, investigation, or evidence.

CLI

Local files and CI gates.

Engine

Embedded TypeScript runtime.

Agent tools

Claude Code or Codex local work.

MCP

Tenant-scoped run context.

Uses

Deterministic validator

Explicit release, packages, terminology, rules, and output

Produces

Local decision

Exit code, JSON, SARIF, or JUnit output.

Records context

Runs, baselines, comparisons, and evidence.

Operating boundary

Records measures beside the FHIR system.

The deployment decides what may cross the boundary. Records reads the permitted scope and keeps derived findings, comparison state, and evidence rather than source payloads.

FHIR source

Permitted server, environment, and resource scope.

Validation basis

FHIR release, packages, terminology, rules, and thresholds.

Read

Records core

Validate · compare · investigate · preserve

Derive

Decision signal

Threshold, delta, and concrete findings.

Evidence

Run basis, timestamps, integrity, and export.

Choose a developer surface

Choose where to go next.

The product overview stays short; each next question has its own page.

Inspect the product