FHIR standardized health data. MCP standardized how AI connects to tools. HealthClaw standardizes the security, privacy, and clinical safety guardrails in between.
Every other health tool shows you data. HealthClaw shows you the trail. One FHIR operation, one MCP tool, one review surface. Built on the dead-simple primitive every PHR is missing: current state + append-only evidence.
GET /$compiled-truthReturns a FHIR Parameters bundle: the redacted current resource, its curation state, quality score, and the full Provenance timeline — newest first. Nothing hidden.
fhir_compiled_truthAgents call this before making resource-specific claims. Responses carry _meta.ui.resourceUri — an embeddable review surface. No more chat-text walls of fine print.
A focused page renders exactly when the agent needs it: current data left, evidence right, approve / re-evaluate bottom. Zero install. No app-nobody-opens.
Inspired by the compiled-truth + append-only-evidence pattern. Backed by R6 Provenance. Patient-first by construction.
When an AI agent accesses clinical data through HealthClaw, each request is validated, redacted, authorized, and recorded before anything touches the FHIR server.
Applied on every read path: direct reads, search results, upstream proxy responses, and context envelopes. Agents work with safe, de-identified data by default.
Whether you're building an AI health agent, managing your own health data, or evaluating compliance infrastructure — HealthClaw meets you where you are.
The healthclaw-marketplace hosts two plugins that ship as auto-discoverable Claude Code skills. Add the marketplace once, install either plugin, and Claude invokes the right skill whenever your prompt matches its triggers — no manual tool wiring.
Marketplace manifest: .claude-plugin/marketplace.json · Skills authored against Anthropic's Skill Authoring Guide
Curatr evaluates FHIR resources against live public terminology services, explains issues in plain language, and lets you approve fixes with full provenance tracking.
Every approved fix creates a linked Provenance resource
recording patient intent, field changes, and agent attribution — recorded in the immutable audit trail. No black-box corrections.
HealthClaw works with any FHIR server. The guardrails are the product, not the data layer.
| HealthClaw | AWS HealthLake | Medplum MCP | Raw FHIR | |
|---|---|---|---|---|
| Any FHIR server | ✓ | ✗ | ✗ | — |
| PHI redaction on reads | ✓ | ✗ | ✗ | ✗ |
| Immutable audit trail | ✓ | Separate | Partial | ✗ |
| Step-up auth for writes | ✓ | Separate | Built-in | ✗ |
| Human-in-the-loop | ✓ | ✗ | ✗ | ✗ |
| R6 Permission $evaluate | ✓ | ✗ | ✗ | ✗ |
| Setup time | 10 sec | 30+ min | 15+ min | Varies |
No accounts. No API keys. No cloud setup. Clone, install, run.
# Install + run in 10 seconds uv sync STEP_UP_SECRET=your-secret python main.py # Or with Docker docker-compose up -d --build # Connect to your FHIR server FHIR_UPSTREAM_URL=https://hapi.fhir.org/baseR4 python main.py
The current health data system was built around institutions, not patients. What happens when we flip that?
Read on Substack →A walkthrough of building an AI health agent using OpenClaw skills and HealthClaw Guardrails with real health data.
Read on Substack →A short email when we ship a new MCP tool, redaction rule, or upstream-server integration. No marketing — just what's actually changed in the repo.
updates@healthclaw.io. One-click unsubscribe in every email.