Medical & Healthcare
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 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.
- Publisher / source
- maziyarpanahi/openmed (found on GitHub top repositories)
- Upstream record
- maziyarpanahi/openmed
- Version
- Version 1
- Published
- Publication review
- Approved for publication
- Content fingerprint
b8833f982a7952028bfc56516fda2990493bc3e8226317ec5ce88ececa2b2e6f