scaffolding-smart-on-fhir
Scaffold a SMART-on-FHIR app (SMART App Launch v2 — EHR launch and standalone launch, OAuth2 PKCE, scopes, token handling, fhirContext) so an OpenMed-powered tool can run inside Epic or Cerner/Oracle Health. Covers the .well-known/smart-configuration discovery, authorize/token sequence, scopes like patient/DocumentReference.rs and launch/patient, and fetching clinical notes the app then de-identifies and runs NER on locally with OpenMed. Use when the user wants to embed OpenMed inside an EHR, mentions SMART on FHIR, OAuth2 launch, scopes, Epic/Cerner app, or clinician-facing FHIR app. Pairs ad
Profile →npx skills add maziyarpanahi/openmed --skill scaffolding-smart-on-fhir --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Scaffolding SMART on FHIR To put an OpenMed-powered tool *inside* a clinician's EHR (Epic, Cerner/Oracle Health), you build a **SMART on FHIR** app: a web app the EHR launches with an OAuth2 flow, granting scoped, time-limited access to the patient's FHIR data. The app fetches the clinical notes, then runs OpenMed **on-device** (de-id + NER) — so PHI is processed locally and only de-identified output, if anything, leaves the browser/host. ## When to use Reach for this when the deliverable is a clinician-facing app embedded in an EHR, or a standalone app authorizing against an EHR's FHIR endpoint. Triggers: "SMART on FHIR", "EHR launch", "OAuth2 scopes", "Epic/Cerner app", "embed OpenMed in the chart". For pulling notes at *cohort* scale (no UI), use `exporting-bulk-fhir` instead. ## Two launch flows - **EHR launch** — clinician clicks your app in the chart. The EHR opens your `launch_uri?iss=<fhir-base>&launch=<opaque>`; you complete OAuth2 and inherit the current patient/encounter context. - **Standalone launch** — user opens your app directly; it discovers the FHIR server and runs OAuth2, and the user/EHR picks the patient. Both use **SMART App Launch v2**: OAuth2 authorization
- When to use
- Two launch flows
- Quick start: the launch sequence
- Scopes you actually need
- Where OpenMed runs
- Hand-off to / from OpenMed
- Edge cases & gotchas
- Standards & references
What does the scaffolding-smart-on-fhir skill do?
Scaffold a SMART-on-FHIR app (SMART App Launch v2 — EHR launch and standalone launch, OAuth2 PKCE, scopes, token handling, fhirContext) so an OpenMed-powered tool can run inside Epic or Cerner/Oracle Health. Covers the .well-known/smart-configuration discovery, authorize/token sequence, scopes like patient/DocumentReference.rs and launch/patient, and fetching clinical notes the app then de-identifies and runs NER on locally with OpenMed. Use when the user wants to embed OpenMed inside an EHR, mentions SMART on FHIR, OAuth2 launch, scopes, Epic/Cerner app, or clinician-facing FHIR app. Pairs ad
How do I install it?
Run `npx skills add maziyarpanahi/openmed --skill scaffolding-smart-on-fhir --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From maziyarpanahi/openmed, a repository with 4,851 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.