mapping-to-snomed
Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL query, translate via a ConceptMap, or resolve a span to a concept id with FHIR $lookup/$translate/$validate-code. Trigger keywords: SNOMED CT, SNOMED concept id, ECL, ConceptMap, $translate, $lookup, Ontoserver, Snowstorm, SCTID, post-coordination, terminology server. Pairs after Ope
npx skills add maziyarpanahi/openmed --skill mapping-to-snomed --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.
# Mapping OpenMed spans to SNOMED CT Ground clinical concept spans that OpenMed extracts — disorders, findings, procedures, body structures, substances — to **SNOMED CT**, the comprehensive clinical reference terminology. The atom is the **SCTID** (a SNOMED CT concept identifier), organized into a description-logic hierarchy you can query with **ECL** (Expression Constraint Language). > **Hard licensing boundary — read first.** SNOMED CT is **license-restricted**. > OpenMed and this skill **never bundle, ship, cache, or redistribute** any > SNOMED CT content. All mapping happens **out-of-process against a terminology > server the user supplies and is licensed for** — their own **Ontoserver**, > **Snowstorm**, the NLM's **UTS/UMLS** FHIR endpoint, or a national release > server. SNOMED International requires an Affiliate License (free in member > territories like the US via the NLM; check your country). Your code receives a > **base URL + credentials from the user**; it must work with *any* compliant > FHIR terminology server and store nothing but the returned codes. ## When to use - You need rich, hierarchy-aware clinical codes (more granular than ICD-10) for problems, procedures,
- When to use
- Quick start (user-supplied FHIR terminology server)
- Workflow
- Hand-off from OpenMed
- Edge cases & gotchas
- Standards & references
What does the mapping-to-snomed skill do?
Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL query, translate via a ConceptMap, or resolve a span to a concept id with FHIR $lookup/$translate/$validate-code. Trigger keywords: SNOMED CT, SNOMED concept id, ECL, ConceptMap, $translate, $lookup, Ontoserver, Snowstorm, SCTID, post-coordination, terminology server. Pairs after Ope
How do I install it?
Run `npx skills add maziyarpanahi/openmed --skill mapping-to-snomed --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.