Agent skill

Mapping To Snomed

by maziyarpanahi in maziyarpanahi/openmed

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.

Apache-2.0Auto-check passedResearch & Science

Install Mapping To Snomed

skills CLI
$ npx skills add maziyarpanahi/openmed --skill mapping-to-snomed -a claude-code

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

GitHub CLI
$ gh skill install maziyarpanahi/openmed mapping-to-snomed --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/mapping-to-snomed .claude/skills/mapping-to-snomed && 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/

Facts

Skill name
mapping-to-snomed
GitHub stars
5.5k
Token cost
~2.1k tokens
SKILL.md length
650 words
Files
1
Skills in repo
74
Repo updated
First seen
Licence
Apache-2.0

At a glance

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.

  • Works in 7 steps: Extract spans with OpenMed (Disease,… → Pick a semantic constraint (ECL) from… → Search with ValueSet/$expand?filter=… → …
  • The user wants to code findings
  • SKILL.md covers When to use, Quick start (user-supplied…, Workflow and Hand-off from OpenMed, plus 2 more sections
  • Reaches snomed.info; needs FHIR_TX_TOKEN

What it does

Mapping To Snomed is an agent skill from maziyarpanahi/openmed. 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…

Its SKILL.md is about 2.1k 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 and Diagrams. 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 code findings
  • Body structures
  • Substances to SNOMED CT
  • Run an ECL query

Example prompts

  • “/mapping-to-snomed”

Requirements

  • Python 3
  • A credential in FHIR_TX_TOKEN

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Extract spans with OpenMed (Disease, Anatomy, Pharmaceutical models).
  2. Pick a semantic constraint (ECL) from the OpenMed label so you search the
  3. Search with ValueSet/$expand?filter= under that ECL.
  4. Rank & disambiguate by display match and confidence; prefer the most
  5. Validate with $validate-code; $lookup to capture the FSN and any
  6. Translate instead of searching when you already hold an ICD-10/local code
  7. Emit {system: "http://snomed.info/sct", code, display} — the SCTID plus

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

    Hosts in commands or code, which the agent is likely to contact:

    • snomed.info

    Also links to:

    • snomed.org
    • nlm.nih.gov
    • confluence.ihtsdotools.org
    • hl7.org
    • github.com
    • ontoserver.csiro.au

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • FHIR_TX_TOKEN

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Mapping To Snomed loads about 2.1k tokens when it runs. Until then it costs about 211 tokens; SKILL.md has 650 words of instructions outside code blocks.

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

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). 650 words, ~2,147 tokens.

Download SKILL.mdSave it as .claude/skills/mapping-to-snomed/SKILL.md (or your agent's skills folder).
name
mapping-to-snomed
description
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 OpenMed NER: consume Disease/Anatomy/Pharmaceutical entities from openmed.analyze_text and map each span out-of-process. SNOMED CT is license-restricted — it is NEVER bundled; the user calls their own affiliate-licensed server.
license
Apache-2.0
metadata.project
OpenMed
metadata.category
terminology-coding
metadata.pairs
after
metadata.version
1.0

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, or body sites.
  • You want to translate an existing code (ICD-10-CM, local code) to SNOMED CT via a ConceptMap/$translate.
  • You need subsumption/ECL queries ("is this a descendant of Diabetes mellitus?") for cohorting or decision support.

For billing codes use coding-icd10; for drugs normalizing-rxnorm; for labs mapping-loinc. SNOMED CT is the clinical-meaning layer.

Quick start (user-supplied FHIR terminology server)

Configuration is injected, never hardcoded. The operations are standard FHIR R4.

python
import os, requests

# Provided by the USER — their licensed server. Nothing bundled.
TX = os.environ["FHIR_TX_URL"]              # e.g. https://snowstorm.example.org/fhir
TOKEN = os.environ.get("FHIR_TX_TOKEN")     # if the server requires auth
SNOMED = "http://snomed.info/sct"
HDRS = {"Accept": "application/fhir+json"}
if TOKEN:
    HDRS["Authorization"] = f"Bearer {TOKEN}"

def lookup(code: str) -> dict:
    """$lookup: fully specified name + properties for an SCTID."""
    r = requests.get(f"{TX}/CodeSystem/$lookup",
                     params={"system": SNOMED, "code": code},
                     headers=HDRS, timeout=15)
    r.raise_for_status()
    return r.json()

def find_concepts(text: str, ecl: str = "<<404684003", count: int = 10):
    """Text search constrained by ECL (default: descendants of Clinical finding)."""
    vs = f"{SNOMED}?fhir_vs=ecl/{ecl}"
    r = requests.get(f"{TX}/ValueSet/$expand",
                     params={"url": vs, "filter": text, "count": count},
                     headers=HDRS, timeout=20)
    r.raise_for_status()
    return r.json().get("expansion", {}).get("contains", [])

def translate(code: str, source_system: str, conceptmap_url: str):
    """$translate an existing code to SNOMED CT via a ConceptMap."""
    r = requests.get(f"{TX}/ConceptMap/$translate",
                     params={"url": conceptmap_url, "system": source_system,
                             "code": code, "targetsystem": SNOMED},
                     headers=HDRS, timeout=20)
    r.raise_for_status()
    return r.json()

# ECL examples: 64572001=disease, 71388002=procedure, 123037004=body structure
print(find_concepts("type 2 diabetes", ecl="<<64572001"))

Workflow

  1. Extract spans with OpenMed (Disease, Anatomy, Pharmaceutical models).
  2. Pick a semantic constraint (ECL) from the OpenMed label so you search the right hierarchy: disorder span → <<64572001; anatomy span → <<123037004; substance/drug → <<105590001; procedure → <<71388002.
  3. Search with ValueSet/$expand?filter=<span> under that ECL.
  4. Rank & disambiguate by display match and confidence; prefer the most specific concept whose meaning is fully entailed by the text (do not over-code).
  5. Validate with $validate-code; $lookup to capture the FSN and any needed properties.
  6. Translate instead of searching when you already hold an ICD-10/local code and the user's server has the relevant ConceptMap.
  7. Emit {system: "http://snomed.info/sct", code, display} — the SCTID plus the OpenMed source offsets for traceability.

Hand-off from OpenMed

openmed.analyze_text(..., output_format="dict") returns entities, each a dict with text, label, confidence, start, end. Route each label to an ECL hierarchy and map out-of-process:

python
import openmed

note = "Assessment: type 2 diabetes mellitus with diabetic nephropathy."
result = openmed.analyze_text(
    note,
    model_name="disease_detection_superclinical",   # Disease category
    output_format="dict",
)

ECL_FOR_LABEL = {
    "DISEASE":   "<<64572001",     # | Disease |
    "CONDITION": "<<64572001",
    "PATHOLOGY": "<<64572001",
    "ANATOMY":   "<<123037004",    # | Body structure |
    "ORGAN":     "<<123037004",
}

for ent in result["entities"]:
    ecl = ECL_FOR_LABEL.get(ent["label"], "<<404684003")  # fallback: Clinical finding
    candidates = find_concepts(ent["text"], ecl=ecl, count=5)
    print(ent["text"], ent["start"], ent["end"], "->",
          [(c["code"], c["display"]) for c in candidates[:3]])

Carry OpenMed's start/end offsets next to each SCTID so every code is auditable back to its span. Persist codes and offsets only — never the raw note, and never a local copy of SNOMED content.

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

Edge cases & gotchas

  • Never bundle SNOMED CT. Do not vendor a release, embed an export, or cache descriptions to disk for reuse. If you find yourself shipping SNOMED data, stop — the design must call the user's licensed server live, out-of-process.
  • Affiliate licensing. Confirm the user holds (or their territory grants) a SNOMED International Affiliate License. In the US it is free via the NLM/UMLS; elsewhere it varies. Surface this requirement; do not assume entitlement.
  • Pre- vs post-coordination. Some clinical meanings need a post-coordinated expression (e.g. finding + body site + severity). Prefer a single pre-coordinated concept when one exists; only post-coordinate when your server and downstream systems support SNOMED CT expressions.
  • Edition/version drift. SCTIDs are stable but content differs across editions (International vs US vs UK) and monthly releases. Record the edition the server reports; do not mix codes across editions silently.
  • Negation/uncertainty stays in OpenMed. A span "no evidence of pneumonia" must not be coded as present pneumonia. Resolve assertion/negation with OpenMed's clinical-context layer before mapping.
  • Don't over-specify. Map to the concept actually supported by the text; inventing severity or laterality the note never stated is a coding error.
  • Local-first. OpenMed NER runs on-device; only de-identified concept strings reach the terminology server. No PHI over the wire.

Standards & references

© maziyarpanahi, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/mapping-to-snomed of maziyarpanahi/openmed.

Open the folder on GitHubat commit 34d7b8c

Compare with similar skills

Mapping To Snomed 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.

Mapping To Snomed compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Mapping To Snomed this skillmaziyarpanahi/openmed5.5k—~2.1kAutomated safety check: PassApache-2.0
Paper Analyzerzsyggg/paper-craft-skills1.3k—~1.9kAutomated safety check: PassNone
Paper To Codelingzhi227/agent-research-skills390—~793Automated safety check: PassNone
Research Planninglingzhi227/agent-research-skills390—~721Automated safety check: PassNone
New Diagrampedrohcgs/claude-code-my-workflow1.7k—~1.8kAutomated safety check: NotesMIT
Mat Defect Energy Dftlearningmatter-mit/AtomisticSkills176—~1.6kAutomated safety check: PassMIT

Similar skills

  • Paper Analyzer

    zsyggg/paper-craft-skills

    将学术论文转化为深度HTML长文。6轮强制工作流、代码仓库搜索、公式渲染、Mermaid图表. An agent skill from zsyggg/paper-craft-skills.

    1.3k GitHub stars~1.9k tokensUpdated 4 mo ago
    Research & ScienceAuto-check passed
  • Paper To Code

    lingzhi227/agent-research-skills

    Convert an ML research paper into a complete, runnable code repository.

    390 GitHub stars~793 tokensUpdated 7 mo ago
    Research & ScienceAuto-check passed
  • Research Planning

    lingzhi227/agent-research-skills

    Design research plans and paper architectures. An agent skill from lingzhi227/agent-research-skills.

    390 GitHub stars~721 tokensUpdated 7 mo ago
    Research & ScienceAuto-check passed
  • New Diagram

    pedrohcgs/claude-code-my-workflow

    Scaffold a new TikZ diagram from the snippet gallery with prevention rules pre-applied (explicit node dimensions, coordinate map, directional edge labels).

    1.7k GitHub stars~1.8k tokensUpdated 13 days ago
    Research & ScienceAuto-check: notes
  • Mat Defect Energy Dft

    learningmatter-mit/AtomisticSkills

    Calculate charged defect formation energies and transition level diagrams using pymatgen-analysis-defects and atomate2 VASP workflows.

    176 GitHub stars~1.6k tokensUpdated 3 days ago
    Research & ScienceAuto-check passed
  • Medical Research Gap To Study Planner

    aipoch/medical-research-skills

    Converts an audited medical research gap into a complete, structured, gap-traceable study design.

    1.9k GitHub stars~3.6k tokensUpdated 24 days ago
    Research & ScienceAuto-check passed

More from maziyarpanahi/openmed

All 74 skills in this repo
  • Checks OpenMed de-identified clinical text against the 18 HIPAA Safe Harbor identifier categories and reports gaps and residual re-identification risk.

    5.5k GitHub stars~1.7k tokensUpdated today
    Auto-check passed
  • OpenMed Model Card Writer

    maziyarpanahi/openmed

    Fills in a model card for an OpenMed clinical NER or de-identification model from its evaluation reports: intended use, metrics, subgroups and limitations.

    5.5k GitHub stars~1.8k tokensUpdated today
    Auto-check passed
  • Walks a data pipeline against the HIPAA Privacy and Security Rule checklist and produces a gap report before it processes patient data.

    5.5k GitHub stars~2k tokensUpdated today
    Auto-check passed
  • ICD-10 Coding Assistant

    maziyarpanahi/openmed

    Suggests candidate ICD-10-CM diagnosis and ICD-10-PCS procedure codes for clinical text extracted by OpenMed, with rationale for a certified coder to review.

    5.5k GitHub stars~2k tokensUpdated today
    Auto-check passed
  • OpenMed ETL to OMOP CDM

    maziyarpanahi/openmed

    Maps OpenMed-extracted, terminology-coded conditions, drugs and measurements into OMOP CDM v5.4 tables for OHDSI and ATLAS analytics.

    5.5k GitHub stars~1.9k tokensUpdated today
    Auto-check passed
  • Extracting SDOH and Z-Codes

    maziyarpanahi/openmed

    Finds social risks such as housing instability or food insecurity in clinical notes and proposes matching ICD-10-CM Z-codes for a coder to confirm.

    5.5k GitHub stars~1.9k tokensUpdated today
    Auto-check passed

Questions about Mapping To Snomed

What does Mapping To Snomed 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. Mapping To Snomed is an agent skill from maziyarpanahi/openmed. 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.

When should I use Mapping To Snomed?

Mapping To Snomed fits situations like: the user wants to code findings; body structures; substances to SNOMED CT; run an ECL query.

How do I install Mapping To Snomed in Claude Code?

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

How do I install Mapping To Snomed in Codex?

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

Can I use Mapping To Snomed 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 mapping-to-snomed -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/mapping-to-snomed, .gemini/skills/mapping-to-snomed, .github/skills/mapping-to-snomed and .opencode/skills/mapping-to-snomed in your project.

What does Mapping To Snomed need to run?

Going by SKILL.md and its folder, Mapping To Snomed needs credentials named FHIR_TX_TOKEN. Our summary lists: Python 3; A credential in FHIR_TX_TOKEN.

Does Mapping To Snomed access the network?

SKILL.md names 7 domains. In commands or code: snomed.info; the agent is likely to contact it when it follows the instructions. As links in the text: snomed.org, nlm.nih.gov, confluence.ihtsdotools.org, hl7.org, github.com and ontoserver.csiro.au. This is read from the text; nothing was executed.

Is Mapping To Snomed 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 Mapping To Snomed use?

Mapping To Snomed 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 Mapping To Snomed use?

About 2.1k tokens (SKILL.md is roughly 8.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 Mapping To Snomed?

Skills that share tags, products or a category with Mapping To Snomed: Paper Analyzer (zsyggg/paper-craft-skills, 1.3k stars), Paper To Code (lingzhi227/agent-research-skills, 390 stars), Research Planning (lingzhi227/agent-research-skills, 390 stars) and New Diagram (pedrohcgs/claude-code-my-workflow, 1.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Mapping To Snomed?

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.