fhir-r6-guardrails

Enforce PHI redaction and immutable audits for FHIR access over MCP.

27|9|Updated Mar 31, 2025
One-click install
npx skills add https://github.com/aks129/HealthClawGuardrails --skill fhir-r6-guardrails
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fhir-r6-guardrails
Source: https://github.com/aks129/HealthClawGuardrails/tree/main/skills/fhir-r6-guardrails
Command: npx skills add https://github.com/aks129/HealthClawGuardrails --skill fhir-r6-guardrails

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

HealthClaw Guardrails provides PHI redaction, immutable audit trails, and access control when AI agents access FHIR data via MCP, preventing leakage of patient data and enabling compliant usage.

Core Features & Use Cases

  • Read/write through MCP with automatic PHI redaction
  • Two-phase write with propose/commit and step-up authorization
  • Evaluating R6 Permission resources for access control
  • Auditing agent access with an immutable trail
  • Supports FHIR R4 US Core v9 and FHIR R6 ballot3

Quick Start

Run HealthClaw guardrails in your MCP-enabled environment and verify PHI redaction and audit trails.

Frequently Asked Questions about fhir-r6-guardrails

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I redact PHI when AI agents access FHIR data over MCP?

PHI redaction for FHIR data over MCP is handled automatically during read, search, and write operations. The guardrails intercept agent requests, evaluate R6 permissions, and strip protected health information before returning responses.

How does two-phase write with propose and commit work for FHIR resources?

Two-phase write for FHIR resources separates proposal from commitment using step-up authorization. The propose phase validates permissions and tenant isolation, while the commit phase finalizes the write only after additional authorization checks pass.

Does this support both FHIR R4 US Core v9 and R6 ballot3?

Both FHIR R4 US Core v9 and FHIR R6 ballot3 are supported for reading, searching, and writing. The guardrails evaluate R6 Permission resources and enforce tenant isolation across both FHIR versions.

How do I enforce immutable audit trails for AI agent access to FHIR?

Immutable audit trails for FHIR access are enforced automatically by logging every agent interaction through MCP. The guardrails record read, search, and write events with PHI redaction status and permission evaluation results.

What is step-up authorization for FHIR writes via MCP?

Step-up authorization for FHIR writes requires elevated permission validation during the two-phase propose and commit workflow. It prevents unauthorized agent writes by demanding additional access verification before final commitment.

Can I evaluate R6 Permission resources to control tenant isolation in FHIR?

R6 Permission resources are evaluated directly to enforce tenant isolation and access control for FHIR data. The guardrails interpret these resources during MCP requests to ensure compliant multi-tenant agent access.