querying-terminology-service

npx skills add maziyarpanahi/openmed --skill querying-terminology-service --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

# Querying a Terminology Service OpenMed deliberately **bundles no restricted vocabulary** — no SNOMED CT, RxNorm, LOINC, ICD-10, UMLS. So when an OpenMed entity span needs a *validated* code (the grounding step `exporting-to-fhir` references), you call a **FHIR terminology server** the user already operates, with their own license. This skill is the thin client the coding skills lean on. ## When to use Use it whenever a span must become a *coded* `CodeableConcept`, when you need to confirm a code is valid in a system, expand a ValueSet for a picklist, look up a display, or map between vocabularies. Triggers: "terminology server", "$validate-code", "$expand", "ValueSet", "ECL", "is this a valid SNOMED/LOINC/ RxNorm code", "translate ICD-10 to SNOMED". It sits between OpenMed NER and `exporting-to-fhir`. ## Bring your own server The four operations are standard FHIR; point the client at whichever server the user is licensed for: - **Ontoserver** (CSIRO) — production SNOMED CT/LOINC, full ECL. - **HAPI FHIR** terminology module — self-hosted. - **tx.fhir.org** — HL7 public server (open content only; **not** for licensed SNOMED/full LOINC, and not for PHI). OpenMed never ships or prox

curl -s -X POST 'https://tx.example/fhir/CodeSystem/$validate-code' \
Expand "disorders of the lung" via an implicit SNOMED ECL value set
curl -s -X POST 'https://tx.example/fhir/ValueSet/$expand' \
Display + properties for a LOINC code
POST [tx]/CodeSystem/$lookup  { url=http://loinc.org, code=4548-4 }
Map an ICD-10-CM code to SNOMED via a ConceptMap
POST [tx]/ConceptMap/$translate {