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.
npx skills add iblai/medical-healthcare-agents --skill cerner-fhirgit clone --depth 1 https://github.com/iblai/medical-healthcare-agentsWrote 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.
[](https://agentmods.dev/skills/iblai/medical-healthcare-agents/cerner-fhir)<a href="https://agentmods.dev/skills/iblai/medical-healthcare-agents/cerner-fhir"><img src="https://agentmods.dev/badge/skills/iblai/medical-healthcare-agents/cerner-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.
<a href="https://agentmods.dev/skills/iblai/medical-healthcare-agents/cerner-fhir"><img src="https://agentmods.dev/badge/skills/iblai/medical-healthcare-agents/cerner-fhir.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00042 | $0.00705 |
| Opus 5 | $0.00021 | $0.00352 |
| Sonnet 5 | $0.00008 | $0.00141 |
| Haiku 4.5 | $0.00004 | $0.00071 |
Grade A, and why
cerner-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.
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.
Cerner Millennium FHIR R4
What it is
Cerner Millennium (now Oracle Health) is the second-largest EHR platform in US health systems. Its FHIR R4 API exposes the same standard resource types as Epic (Patient, Encounter, Condition, MedicationRequest, Observation, DocumentReference, Procedure) via SMART on FHIR backend service auth. Agents use it as the Cerner-deployment equivalent of the Epic FHIR skill, providing the same clinical context to downstream workflows.
When to use this skill
- Read active diagnoses, medications, and allergy lists from a Cerner-hosted chart
- Retrieve encounter context (class, service, attending NPI) for routing and documentation
- Fetch clinical notes or discharge summaries (DocumentReference) for coding or CDI workflows
- Access procedure records and lab observations for quality measurement
- Create draft documentation or orders in the Cerner PowerChart note workflow (write scope)
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:
CERNER_FHIR_BASE_URL- FHIR R4 base endpoint (e.g.,https://fhir-ehr.cerner.com/r4/{tenant-id})CERNER_CLIENT_ID- OAuth 2.0 client ID from Cerner code consoleCERNER_CLIENT_SECRET- OAuth 2.0 client secret (system app auth)CERNER_TENANT_ID- health system tenant identifier issued during registration
Key operations
GET /Patient/{id}— demographics, MRN, preferred languageGET /Encounter?patient={id}— encounter list with class, status, periodGET /Condition?patient={id}— problem list with ICD-10/SNOMED codesGET /MedicationRequest?patient={id}&status=active— active medication listGET /Observation?patient={id}&category=laboratory— lab results with LOINCGET /DocumentReference?patient={id}— clinical notes and reportsGET /Procedure?patient={id}— completed and planned proceduresPOST /DocumentReference— write draft note to Cerner workflow (write scope required)
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.
- 12d ago First seen · 42 lines · 42 tokens per session scan A 7334f0b31233
cerner-fhir is a skill published in the GitHub repository iblai/medical-healthcare-agents (10 stars, last pushed 3mo ago), licensed MIT. It adds 42 tokens to every session and 705 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.
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…
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…
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.
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.
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.
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.