Developers · Records Agent Tools
Validate FHIR before an AI-assisted change leaves the workspace.
Give Claude Code or Codex local validation, project diagnostics, issue explanation, and CI-gate generation without making the model the authority.
Available now · v0.8.4 · MIT
Smallest useful example
Install the validation guardrail where the change is made.
The tool package gives a supported coding agent bounded FHIR diagnostics and validation skills before generated or edited resources move downstream.
Install for Claude Code
claude plugin marketplace add medvertical/records-agent-toolsclaude plugin install records@medverticalExpected contract
What comes back
Local project diagnostics and validator-backed findings that remain reviewable by the developer; the agent never becomes the release authority.
| Workspaces | Claude Code and Codex with their supported Records skills |
|---|---|
| Default boundary | Local project inspection and validation |
| Full validation | Requires an explicitly configured profile, terminology, invariant and reference runtime |
Built for one clear integration job
The surface stays small; Records carries the wider operational loop when you need it.
Local validation guardrail
Check generated resources and mapping changes through the local validator by default.
FHIR project diagnostics
Inspect project structure, packages, examples, and validation findings before proposing a fix.
Claude Code and Codex
Use the same bounded Records skills in either supported agent workspace, then turn the expectation into a repeatable CI gate.
Scope
The boundary
Know what this surface owns before you put it into a workflow.
What remains outside this surface
The agent tools validate and explain FHIR. Their local structural fallback is R4-only; full profile, terminology, invariant, and reference validation requires an explicitly configured runtime. They do not authorize clinical actions, decide whether data may be shared with a model, or replace human review.