epic-fhir

epic-fhir is a skill for Claude Code, Codex from iblai/medical-healthcare-agents. It costs 45 tokens per session (690 once invoked), scanned A, original, MIT.

A connection to Epic, an electronic health-record system used by hospitals and clinics, through its standard FHIR interface. It can read patient records and, with the right permission, create draft notes or referral orders.

In plain words
What is it for?
Use it to retrieve diagnoses, medications, allergies, lab results, visit details, notes, care plans, discharge instructions, and referrals, or to prepare draft documentation and referral orders.
Why use it?
It gives an agent clinical context from an Epic-hosted chart without manual data transfer, while keeping clinician review for supported draft actions.

Skill for Claude CodeCodex

Which agent this was written for is unclear — built for openclaw. Also seen: built for openclaw.

Good fit Use it to retrieve diagnoses, medications, allergies, lab results, visit details, notes, care plans, discharge instructions, and referrals, or to prepare draft documentation and referral orders.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/iblai/medical-healthcare-agents/epic-fhir
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add iblai/medical-healthcare-agents --skill epic-fhir
Clone the repo
git clone --depth 1 https://github.com/iblai/medical-healthcare-agents

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for epic-fhir

README.md
[![agentmods](https://agentmods.dev/badge/skills/iblai/medical-healthcare-agents/epic-fhir/github.svg)](https://agentmods.dev/skills/iblai/medical-healthcare-agents/epic-fhir)
Your own site
<a href="https://agentmods.dev/skills/iblai/medical-healthcare-agents/epic-fhir"><img src="https://agentmods.dev/badge/skills/iblai/medical-healthcare-agents/epic-fhir/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for epic-fhir

Your own site · 80×15
<a href="https://agentmods.dev/skills/iblai/medical-healthcare-agents/epic-fhir"><img src="https://agentmods.dev/badge/skills/iblai/medical-healthcare-agents/epic-fhir.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 690 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00045 $0.00690
Opus 5 $0.00023 $0.00345
Sonnet 5 $0.00009 $0.00138
Haiku 4.5 $0.00005 $0.00069

Measured 12d ago against content hash cc00d0bc7c35, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

epic-fhir scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/epic-fhir/SKILL.md · 42 lines

How it starts

The opening of the file, as written. The whole thing — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Epic FHIR R4

What it is

Epic is the dominant EHR platform in US health systems. Its FHIR R4 API (via SMART on FHIR / backend service auth) exposes standardized clinical resources — Patient, Encounter, Condition, MedicationRequest, Observation, DocumentReference, ServiceRequest, and more. Agents use it to read encounter context, surface patient data, and (with write scopes) create draft notes or referral orders for clinician review.

When to use this skill

  • Retrieve active diagnoses, medications, allergies, or lab results for clinical decision support
  • Read encounter context (admit date, service type, attending provider) before routing a request
  • Fetch or draft clinical documentation (DocumentReference) via the In-Basket workflow
  • Create or check referral orders (ServiceRequest) during care coordination
  • Access care plan activities or discharge instructions (CarePlan) for patient education

Credentials

This skill authenticates using variables declared in the metadata above. Copy ~/.openclaw/.env.example to ~/.openclaw/.env and fill in real values. Required variables:

  • EPIC_FHIR_BASE_URL - FHIR R4 base endpoint (e.g., https://fhir.epicinstance.org/api/FHIR/R4)
  • EPIC_CLIENT_ID - OAuth 2.0 client ID registered in Epic App Orchard
  • EPIC_PRIVATE_KEY_PATH - path to RSA private key used for JWT client assertion (backend service auth)
  • EPIC_SCOPE - space-separated SMART scopes (e.g., system/Patient.read system/Observation.read)

Key operations

  • GET /Patient/{id} — demographics, MRN, language preference
  • GET /Encounter?patient={id} — encounter list with class, service type, status
  • GET /Condition?patient={id}&clinical-status=active — active problem list
  • GET /MedicationRequest?patient={id}&status=active — current medications
  • GET /Observation?patient={id}&category=laboratory — lab results with LOINC codes
  • GET /DocumentReference?patient={id}&type={LOINC} — clinical notes by type
  • POST /ServiceRequest — create referral order (write scope required)
  • POST /DocumentReference — submit draft note to In-Basket (write scope required)

Read the full file on GitHub · 42 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 42 lines · 45 tokens per session scan A cc00d0bc7c35

Subscribe to this mod's changes

epic-fhir is a skill published in the GitHub repository iblai/medical-healthcare-agents (10 stars, last pushed 3mo ago), licensed MIT. It adds 45 tokens to every session and 690 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

architecture-patterns

Implement proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design. Use this skill when designing clean architecture for a new microservice, when refactoring a monolith to use bounded contexts, when implementing hexagonal or onion architecture patterns, or…

wshobson/agents · 65 tokens

saga-orchestration

Implement saga patterns for distributed transactions and cross-aggregate workflows. Use this skill when implementing distributed transactions across microservices where 2PC is unavailable, designing compensating actions for failed order workflows that span inventory, payment, and shipping services, building…

wshobson/agents · 91 tokens

fastapi-templates

Create production-ready FastAPI projects with async patterns, dependency injection, and comprehensive error handling. Use when building new FastAPI applications or setting up backend API projects.

wshobson/agents · 37 tokens

api-design-principles

Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers. Use when designing new APIs, reviewing API specifications, or establishing API design standards.

wshobson/agents · 44 tokens

event-store-design

Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.

wshobson/agents · 33 tokens

error-handling-patterns

Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications. Use when implementing error handling, designing APIs, or improving application reliability.

wshobson/agents · 43 tokens