Agent skill

Scaffolding Smart On Fhir

by maziyarpanahi in maziyarpanahi/openmed

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…

Apache-2.0Auto-check passedResearch & Science

Install Scaffolding Smart On Fhir

skills CLI

$ npx skills add maziyarpanahi/openmed --skill scaffolding-smart-on-fhir -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install maziyarpanahi/openmed scaffolding-smart-on-fhir --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/maziyarpanahi/openmed.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/scaffolding-smart-on-fhir .claude/skills/scaffolding-smart-on-fhir && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "scaffolding-smart-on-fhir" agent skill from https://github.com/maziyarpanahi/openmed/tree/master/skills/scaffolding-smart-on-fhir into .claude/skills/scaffolding-smart-on-fhir/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scaffolding-smart-on-fhir", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/maziyarpanahi/openmed/tree/master/skills/scaffolding-smart-on-fhir

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add maziyarpanahi/openmed --skill scaffolding-smart-on-fhir -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install maziyarpanahi/openmed scaffolding-smart-on-fhir --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/maziyarpanahi/openmed.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/scaffolding-smart-on-fhir .agents/skills/scaffolding-smart-on-fhir && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "scaffolding-smart-on-fhir" agent skill from https://github.com/maziyarpanahi/openmed/tree/master/skills/scaffolding-smart-on-fhir into .agents/skills/scaffolding-smart-on-fhir/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scaffolding-smart-on-fhir", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add maziyarpanahi/openmed --skill scaffolding-smart-on-fhir -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install maziyarpanahi/openmed scaffolding-smart-on-fhir --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/maziyarpanahi/openmed.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/scaffolding-smart-on-fhir .cursor/skills/scaffolding-smart-on-fhir && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "scaffolding-smart-on-fhir" agent skill from https://github.com/maziyarpanahi/openmed/tree/master/skills/scaffolding-smart-on-fhir into .cursor/skills/scaffolding-smart-on-fhir/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scaffolding-smart-on-fhir", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/maziyarpanahi/openmed.git --path skills/scaffolding-smart-on-fhir

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add maziyarpanahi/openmed --skill scaffolding-smart-on-fhir -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install maziyarpanahi/openmed scaffolding-smart-on-fhir --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/maziyarpanahi/openmed.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/scaffolding-smart-on-fhir .gemini/skills/scaffolding-smart-on-fhir && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "scaffolding-smart-on-fhir" agent skill from https://github.com/maziyarpanahi/openmed/tree/master/skills/scaffolding-smart-on-fhir into .gemini/skills/scaffolding-smart-on-fhir/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scaffolding-smart-on-fhir", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install maziyarpanahi/openmed scaffolding-smart-on-fhir

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add maziyarpanahi/openmed --skill scaffolding-smart-on-fhir -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/maziyarpanahi/openmed.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/scaffolding-smart-on-fhir .github/skills/scaffolding-smart-on-fhir && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "scaffolding-smart-on-fhir" agent skill from https://github.com/maziyarpanahi/openmed/tree/master/skills/scaffolding-smart-on-fhir into .github/skills/scaffolding-smart-on-fhir/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scaffolding-smart-on-fhir", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add maziyarpanahi/openmed --skill scaffolding-smart-on-fhir -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install maziyarpanahi/openmed scaffolding-smart-on-fhir --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/maziyarpanahi/openmed.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/scaffolding-smart-on-fhir .opencode/skills/scaffolding-smart-on-fhir && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "scaffolding-smart-on-fhir" agent skill from https://github.com/maziyarpanahi/openmed/tree/master/skills/scaffolding-smart-on-fhir into .opencode/skills/scaffolding-smart-on-fhir/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scaffolding-smart-on-fhir", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: scaffolding-smart-on-fhir
GitHub stars: 5.5k
Token cost: ~1.9k tokens
SKILL.md length: 617 words
Files: 1
Skills in repo: 74
Repo updated: Oct 11, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

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…

The user wants to embed OpenMed inside an EHR
SKILL.md covers When to use, Two launch flows, Quick start: the launch sequence and Scopes you actually need, plus 4 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
Mentions SMART on FHIR

What it does

Scaffolding Smart On Fhir is an agent skill from maziyarpanahi/openmed. 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…

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Research & Science, covering Clinical and healthcare research, OAuth and OpenID Connect and Project scaffolding. The repository describes itself as: Local-first healthcare AI: clinical NER and HIPAA PII de-identification on hardware you control. 2,200+ medical models, 35 model-backed PII languages, and Python, MLX, Android… The licence is Apache-2.0.

When your agent uses it

The user wants to embed OpenMed inside an EHR
Mentions SMART on FHIR
Epic/Cerner app
Clinician-facing FHIR app

Example prompts

“/scaffolding-smart-on-fhir”

Requirements

Python 3

What it can do on your machine

Read from SKILL.md and the folder at commit 34d7b8c. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are python).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
- hl7.org
- datatracker.ietf.org
- fhir.epic.com
- fhir.cerner.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Scaffolding Smart On Fhir loads about 1.9k tokens when it runs. Until then it costs about 158 tokens; SKILL.md has 617 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~158
When it runs · the whole SKILL.md, loaded when a task matches: ~1.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from maziyarpanahi/openmed at commit 34d7b8c, republished under its Apache-2.0 licence (© maziyarpanahi). 617 words, ~1,893 tokens.

Download SKILL.mdSave it as .claude/skills/scaffolding-smart-on-fhir/SKILL.md (or your agent's skills folder).

name: scaffolding-smart-on-fhir
description: 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 adjacent.
license: Apache-2.0
metadata.project: OpenMed
metadata.category: fhir-interop
metadata.pairs: adjacent
metadata.version: 1.0

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 code flow with PKCE (required in v2), discovered via .well-known/smart-configuration.

Quick start: the launch sequence

1. EHR launch URL:
   GET https://app.example/launch?iss=https://ehr.example/fhir&launch=abc123

2. Discover endpoints:
   GET https://ehr.example/fhir/.well-known/smart-configuration
   -> { "authorization_endpoint": ".../authorize",
        "token_endpoint": ".../token",
        "code_challenge_methods_supported": ["S256"],
        "capabilities": ["launch-ehr","client-public","context-ehr-patient", ...] }

3. Redirect the browser to authorize (PKCE + the launch token):
   GET .../authorize?
       response_type=code&
       client_id=YOUR_CLIENT_ID&
       redirect_uri=https://app.example/callback&
       scope=launch openid fhirUser patient/DocumentReference.rs patient/Patient.r&
       state=RANDOM&
       aud=https://ehr.example/fhir&
       launch=abc123&
       code_challenge=BASE64URL(SHA256(verifier))&
       code_challenge_method=S256

4. Callback -> exchange code for token:
   POST .../token
       grant_type=authorization_code&code=...&redirect_uri=...&
       client_id=...&code_verifier=ORIGINAL_VERIFIER
   -> { "access_token": "...", "token_type": "Bearer", "expires_in": 3600,
        "scope": "patient/DocumentReference.rs ...",
        "patient": "Patient-123", "encounter": "Encounter-9",
        "id_token": "..." }

5. Call FHIR with the token:
   GET https://ehr.example/fhir/DocumentReference?patient=Patient-123&type=clinical-note
       Authorization: Bearer <access_token>

The token response carries the launch context (patient, sometimes encounter, and in v2 a fhirContext array). Use patient to scope every subsequent query.

Scopes you actually need

SMART v2 scopes are <level>/<Resource>.<permissions> where permissions are a subset of c r u d s (create/read/update/delete/search) — .rs = read + search. Request the minimum:

Scope	Why
`launch`	EHR launch context (omit for standalone; use `launch/patient`)
`openid fhirUser`	Identify the launching user
`patient/Patient.r`	The in-context patient demographics
`patient/DocumentReference.rs`	Read + search the patient's clinical notes
`patient/Condition.rs`	(optional) reconcile against existing problems
`offline_access`	(optional) refresh token for background work

Prefer patient/… (current-patient) over user/… (everything the user can see) to keep the blast radius small. Granular v2 scopes (.rs) are stricter than the v1 .read/.write forms — use them.

Where OpenMed runs

Notes arrive as DocumentReference → content.attachment (often base64 or a url to a Binary). Decode, then process locally:

python

import base64, openmed

note_b64 = document_reference["content"][0]["attachment"]["data"]
note = base64.b64decode(note_b64).decode("utf-8")

# De-identify on-device before anything else touches it
deid = openmed.deidentify(note, method="replace", policy="hipaa_safe_harbor")

# Clinical NER on the (de-identified or raw, per your IRB) text
entities = openmed.analyze_text(deid.text, model_name="disease_detection_superclinical")
# -> render highlights in the SMART app UI, or export FHIR (exporting-to-fhir)

OpenMed models run on-device after a one-time download — no note text is sent to a third party by OpenMed. Keep the access token and any PHI in memory only; do not log them.

Show full SKILL.md (252 more words)Show less

Hand-off to / from OpenMed

From the EHR to OpenMed: fetched DocumentReference notes → openmed.deidentify → openmed.analyze_text.
From OpenMed back to the EHR: built FHIR resources (exporting-to-fhir) → to_bundle (assembling-fhir-bundles) → write back with a write scope (e.g. patient/Condition.c) if your use case persists findings. Validate first (validating-us-core).
MCP option: if the app calls a local OpenMed MCP server, the tools are openmed_analyze_text and openmed_deidentify — same on-device guarantees.

Edge cases & gotchas

PKCE is mandatory in v2 and for public (browser) clients always. Generate a fresh code_verifier per launch; never reuse.
Validate state and aud. Reject the callback if state does not match; set aud to the FHIR base or the EHR will reject the authorize request.
Tokens are short-lived. Handle expires_in; use offline_access + refresh tokens only if you genuinely need background access, and store them securely (never client-side for confidential clients).
Scope down-grade is normal. The EHR may grant fewer scopes than requested; read the returned scope and degrade gracefully.
Don't persist PHI in the browser. Process in memory; if you must cache, cache the de-identified output only.
App registration is per-EHR. Epic (fhir.epic.com) and Cerner each have their own developer portals, client registration, and sandbox FHIR endpoints; test against the sandbox before go-live.
OpenMed stays local. The OAuth2 token authorizes FHIR calls to the EHR; it has nothing to do with OpenMed, which needs no network at inference time.

Standards & references

SMART App Launch v2: https://hl7.org/fhir/smart-app-launch/
Scopes & launch context: https://hl7.org/fhir/smart-app-launch/scopes-and-launch-context.html
.well-known/smart-configuration: https://hl7.org/fhir/smart-app-launch/conformance.html
OAuth2 PKCE (RFC 7636): https://datatracker.ietf.org/doc/html/rfc7636
Epic on FHIR: https://fhir.epic.com/
Oracle Health (Cerner) FHIR: https://fhir.cerner.com/

Files

Just SKILL.md in skills/scaffolding-smart-on-fhir of maziyarpanahi/openmed.

Open the folder on GitHubat commit 34d7b8c

Compare with similar skills

Scaffolding Smart On Fhir next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Scaffolding Smart On Fhir compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Scaffolding Smart On Fhir this skillmaziyarpanahi/openmed	5.5k	—	~1.9k	Automated safety check: Pass	Apache-2.0	today
Smart App Launchaehrc/pathling	137	—	~1.3k	Automated safety check: Pass	Apache-2.0	3 days ago
Clinical Trials Databasegoogle-deepmind/science-skills	3.2k	2 repos	~3.2k	Automated safety check: Pass	Apache-2.0	yesterday
CHARLS Paper Reproduction Guidexjtulyc/MedgeClaw	617	1 repos	~1.8k	Automated safety check: Pass	None	7 mo ago
Biomedical Analysis Dispatchxjtulyc/MedgeClaw	617	1 repos	~2k	Automated safety check: Pass	None	7 mo ago
Research Paperluwill/research-skills	862	—	~1.9k	Automated safety check: Pass	None	today

Similar skills

Smart App Launch
aehrc/pathling
Expert guidance for implementing SMART App Launch (HL7 FHIR specification for OAuth 2.0-based authorization).
137 GitHub stars~1.3k tokensUpdated 3 days ago
Backend & APIsAuto-check passed
Clinical Trials Database
google-deepmind/science-skills
Query ClinicalTrials.gov via APIv2. An agent skill from google-deepmind/science-skills.
3.2k GitHub starsUsed in 2 repos~3.2k tokens
Research & ScienceAuto-check passed
CHARLS Paper Reproduction Guide
xjtulyc/MedgeClaw
Guides an agent through reproducing papers built on the CHARLS health and retirement survey, from variable mapping to cognition, depression and isolation scores.
617 GitHub starsUsed in 1 repo~1.8k tokens
Research & ScienceAuto-check passed
Biomedical Analysis Dispatch
xjtulyc/MedgeClaw
Routes bioinformatics, drug discovery, clinical and multi-omics tasks from a chat interface to Claude Code sessions running K-Dense scientific skills, with a live dashboard per task.
617 GitHub starsUsed in 1 repo~2k tokens
Research & ScienceAuto-check passed
Research Paper
luwill/research-skills
A skill your agent uses when the user asks to write or draft an ORIGINAL RESEARCH ARTICLE — IMRaD paper, conference paper, short/workshop paper, 研究论文/期刊论文/会议论文 — reporting their own completed…
862 GitHub stars~1.9k tokensUpdated today
Research & ScienceAuto-check passed
Research Proposal
luwill/research-skills
A skill your agent uses when the user asks to write or draft a PhD / doctoral research proposal, research plan, 研究计划书, or 开题报告 — a forward-looking plan of background, gap, research questions…
862 GitHub stars~4.5k tokensUpdated today
Research & ScienceAuto-check: notes

Questions about Scaffolding Smart On Fhir

What does Scaffolding Smart On Fhir 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…. Scaffolding Smart On Fhir is an agent skill from maziyarpanahi/openmed. 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.

When should I use Scaffolding Smart On Fhir?

Scaffolding Smart On Fhir fits situations like: the user wants to embed OpenMed inside an EHR; mentions SMART on FHIR; epic/Cerner app; clinician-facing FHIR app.

How do I install Scaffolding Smart On Fhir in Claude Code?

Run `npx skills add maziyarpanahi/openmed --skill scaffolding-smart-on-fhir -a claude-code`. Or copy the skill folder (skills/scaffolding-smart-on-fhir in maziyarpanahi/openmed) into .claude/skills/scaffolding-smart-on-fhir in your project. Claude Code loads it when a task matches its description.

How do I install Scaffolding Smart On Fhir in Codex?

Run `npx skills add maziyarpanahi/openmed --skill scaffolding-smart-on-fhir -a codex`. Or copy the skill folder (skills/scaffolding-smart-on-fhir in maziyarpanahi/openmed) into .agents/skills/scaffolding-smart-on-fhir in your project. Codex loads it when a task matches its description.

Can I use Scaffolding Smart On Fhir in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add maziyarpanahi/openmed --skill scaffolding-smart-on-fhir -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/scaffolding-smart-on-fhir, .gemini/skills/scaffolding-smart-on-fhir, .github/skills/scaffolding-smart-on-fhir and .opencode/skills/scaffolding-smart-on-fhir in your project.

What does Scaffolding Smart On Fhir need to run?

SKILL.md names no scripts, command-line tools or credentials: Scaffolding Smart On Fhir is instructions for the agent only. Our summary lists: Python 3.

Does Scaffolding Smart On Fhir access the network?

SKILL.md names 4 domains. As links in the text: hl7.org, datatracker.ietf.org, fhir.epic.com and fhir.cerner.com. This is read from the text; nothing was executed.

Is Scaffolding Smart On Fhir safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Scaffolding Smart On Fhir use?

Scaffolding Smart On Fhir is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Scaffolding Smart On Fhir use?

About 1.9k tokens (SKILL.md is roughly 7.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Scaffolding Smart On Fhir?

Skills that share tags, products or a category with Scaffolding Smart On Fhir: Smart App Launch (aehrc/pathling, 137 stars), Clinical Trials Database (google-deepmind/science-skills, 3.2k stars), CHARLS Paper Reproduction Guide (xjtulyc/MedgeClaw, 617 stars) and Biomedical Analysis Dispatch (xjtulyc/MedgeClaw, 617 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Scaffolding Smart On Fhir?

maziyarpanahi (a GitHub user) maintains it in maziyarpanahi/openmed, which has 5,506 GitHub stars. The repository holds 74 skills in this directory. The repository was last updated on October 11, 2026.

Source: maziyarpanahi/openmed on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Scaffolding Smart On Fhir

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Scaffolding SMART on FHIR

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

Files

Compare with similar skills

Similar skills

More from maziyarpanahi/openmed

Related

Questions about Scaffolding Smart On Fhir