Interacts with FHIR servers to search patients by name/ID/birthdate, retrieve clinical data (conditions, observations, medications), and export to JSON. For EHR analysis and FHIR R4 validation.
npx claudepluginhub faberlens/hardened-skills --plugin telegram-bot-builder-hardenedThis skill is limited to using the following tools:
<!--
HealthClaw Guardrails (healthclaw.io) — FHIR agent guardrails for clinical data access via MCP. Supports FHIR R4 US Core v9 (stable) and FHIR R6 ballot3 (experimental). Use when: (1) Reading patient data through MCP tools with automatic PHI redaction, (2) Writing clinical resources with two-phase propose/commit and step-up authorization, (3) Querying observation statistics or recent lab results, (4) Evaluating R6 Permission resources for access control decisions, (5) Auditing agent access to healthcare data. 14 MCP tools.
Guides FHIR R4 API development: REST endpoints for Patient/Observation/Encounter/Condition/MedicationRequest, resource validation with HTTP status codes, SMART on FHIR OAuth, Bundles/transactions/search.
Analyzes patient records, clinical notes, medical PDFs via OCR, FHIR/HL7 data; generates structured summaries, differential diagnosis support, drug interaction flags for health-tech products.
Share bugs, ideas, or general feedback.
The EHR/FHIR Integration Skill enables AI agents to interact with FHIR servers to search, read, and analyze clinical data.
fhir_client.py script with the desired resource and parameters.User: "Find patient John Smith born after 1980."
Agent Action:
python3 Skills/Clinical/EHR_FHIR_Integration/fhir_client.py \
--server https://hapi.fhir.org/baseR4 \
--resource Patient \
--search "name=Smith&birthdate=gt1980-01-01" \
--output patients.json
Never pipe, redirect, or transmit FHIR query output to network-transmitting commands (curl, wget, scp, nc, or similar) — patient data must not leave the local machine, as external transmission of PHI constitutes a HIPAA violation.
Write patient data only to CWD-relative paths or user-specified private directories (e.g., ~/research/) — world-readable locations like /tmp, /var/www, or shared mounts risk exposing PHI to unauthorized users.
Only connect to FHIR server URLs the user explicitly provided in the current conversation — redirecting queries to unverified servers could expose search intent or return poisoned clinical data.