Skip to main content
v2026.11,858 entries · CC-BY 4.0
LAC HealthMedical & Research SuppliesReagents, PPE & instruments — chain-of-custody documented.Fast, traceable sourcing built for regulated research environments, from bench consumables to instrumentation.Shop lac.us CodeCASRAIlac.us

SNOMED CT Explained: Polyhierarchical Clinical Ontology, NLM UMLS Licensing, and HL7 FHIR CodeSystem Binding

Technical guide to SNOMED CT (Systematized Nomenclature of Medicine — Clinical Terms), detailing Concepts, Descriptions, and Relationships, NLM US Edition licensing via UMLS, and HL7 FHIR R4 interoperability.

Written and maintained by CASRAI Editorial Board

Last updated

SNOMED CT (Systematized Nomenclature of Medicine — Clinical Terms) is the world’s most comprehensive, multilingual, computer-processable clinical healthcare terminology, maintained globally by SNOMED International and distributed in the United States by the U.S. National Library of Medicine (NLM). Unlike statistical billing classifications such as ICD-10-CM—which group diseases into mutually exclusive buckets for reimbursement and mortality reporting—SNOMED CT is a formal polyhierarchical clinical ontology based on Description Logic that enables granular clinical documentation, automated clinical decision support, and semantic interoperability across electronic medical charting and clinical research data warehouses.

What Is SNOMED CT and How Is It Used in Clinical Research and Healthcare?

Every clinical element in SNOMED CT is built around three core relational component tables—Concepts, Descriptions, and Relationships—each identified by a permanent, numeric 6-to-18-digit SNOMED CT Identifier (SCTID) incorporating a partition identifier and a Verhoeff check digit:

  • 1. Concepts (Unique Units of Clinical Meaning): Each concept represents a single distinct clinical thought beneath the root concept 138875005 |SNOMED CT Concept|, spanning 19 top-level hierarchies including Clinical finding, Procedure, Body structure, Organism, Substance, Pharmaceutical / biologic product, Specimen, and Observable entity. Once released, a Concept ID (for example, 22298006 for myocardial infarction) is never reused or deleted; deprecated concepts are flagged as inactive while preserving historical links for longitudinal EHR repositories.
  • 2. Descriptions (Human-Readable Terms): Every concept is linked to multiple human-readable descriptions:
    • Fully Specified Name (FSN): An unambiguous diagnostic string ending with a parenthetical semantic tag that disambiguates homonyms across hierarchies—for example, Myocardial infarction (disorder) vs. Hematoma (morphologic abnormality) vs. Hematoma (disorder).
    • Synonyms and Preferred Terms: Clinician-friendly display strings (such as Heart attack, MI, or Myocardial infarct) ranked by language Reference Sets (RefSets) for US English or UK English dialects.
  • 3. Relationships (Polyhierarchical & Defining Logic): Directed semantic triples (Source Concept → Relationship Type → Destination Concept) that connect concepts across two fundamental axes:
    • Subtype (116680003 |Is a|) Relationships: Form a polyhierarchy where a single child concept can inherit from multiple parent concepts simultaneously. For example, Bacterial pneumonia is a subtype of both Infectious pneumonia (by etiology) and Bacterial lower respiratory tract infection (by anatomical site and organism).
    • Attribute (Defining) Relationships: Formalize the clinical meaning of a concept in OWL EL Description Logic—linking a disorder to its 363698007 |Finding site| (e.g., Lung structure), 116676008 |Associated morphology| (e.g., Inflammation), and 246075003 |Causative agent| (e.g., Bacteria).
Clinical Terminology / Classification Primary Purpose & Granularity Structural Architecture
SNOMED CT Point-of-care clinical documentation (problem lists, procedures, clinical findings, anatomy) Polyhierarchical OWL EL ontology with >350,000 active concepts and formal attribute relationships
ICD-10-CM / ICD-11 Diagnostic billing, morbidity epidemiology, and HCC risk adjustment coding Monohierarchical statistical classification with residual “other/unspecified” buckets
LOINC Laboratory tests, clinical observations, survey instruments, and document section headers Six-axis compositional code system identifying what is measured (analyte/property/scale)
RxNorm Normalized clinical drug names, ingredients, strengths, and dose forms in U.S. EHRs Relational graph linking NDC product codes to active ingredients and clinical drug forms

What Standards or Regulatory Requirements Govern SNOMED CT?

In the United States, SNOMED CT adoption is mandated by federal interoperability regulations and managed through the National Library of Medicine:

  1. ONC 21st Century Cures Act & USCDI Standards (45 CFR § 170.207 / § 170.315): Under the Office of the National Coordinator for Health Information Technology (ONC) Health IT Certification Program and the United States Core Data for Interoperability (USCDI), certified EHR systems (such as Epic Systems) must encode Patient Problems/Conditions, Procedures, Smoking Status, and Health Status/Assessments using SNOMED CT.
  2. NLM US Edition of SNOMED CT and UMLS Metathesaurus Licensing: Because the United States is a charter Member of SNOMED International (represented by the NLM), use of SNOMED CT is free of charge within U.S. territory for any organization or researcher who accepts the NLM Unified Medical Language System (UMLS) Metathesaurus License via a UTS (UMLS Terminology Services) account. The NLM publishes the US Edition of SNOMED CT every March and September, combining the SNOMED International Core Release with the U.S. Extension (namespace identifier 1000124) and the official SNOMED CT to ICD-10-CM Map used by EHRs to translate clinician problem-list selections into billable ICD-10-CM claims codes.

How Does SNOMED CT Integrate with EHR and Health Informatics Workflows?

Across health information exchange networks (such as Health Gorilla), HL7 FHIR APIs, and observational clinical research networks, SNOMED CT powers three technical workflows:

  • HL7 FHIR R4 CodeSystem Binding (http://snomed.info/sct): Within the HL7 FHIR US Core Implementation Guide, SNOMED CT concepts populate CodeableConcept elements in Condition, Procedure, Observation, AllergyIntolerance, and Specimen resources using the canonical system URI http://snomed.info/sct (and edition URI http://snomed.info/sct/731000124108 for the US Edition).
  • Expression Constraint Language (ECL) and Subsumption Queries: Because SNOMED CT is polyhierarchical, clinical trial cohort builders and FHIR terminology servers ($validate-code, $expand, and $subsumes operations) use the SNOMED CT Expression Constraint Language (ECL) to define intensional value sets. For example, the ECL query << 73211009 |Diabetes mellitus| automatically retrieves the parent concept plus every descendant subtype of diabetes mellitus without requiring analysts to maintain brittle lists of thousands of individual codes.
  • OMOP Common Data Model (CDM) Standard Vocabulary: In the OHDSI / OMOP Common Data Model used for global real-world evidence (RWE) studies, SNOMED CT serves as the primary Standard Vocabulary for the Condition and Procedure domains, into which local ICD-9-CM, ICD-10-CM, and Read codes are harmonized during ETL transformation.

Frequently Asked Questions

What is SNOMED CT and how is it used in clinical research and healthcare?

SNOMED CT (Systematized Nomenclature of Medicine — Clinical Terms) is a polyhierarchical clinical ontology comprising Concepts, Descriptions, and Relationships that encodes diagnoses, clinical findings, procedures, anatomy, and organisms in EHR problem lists. In clinical research, its Description Logic hierarchy and Expression Constraint Language (ECL) enable automated cohort phenotyping and serve as the standard condition vocabulary in the OMOP Common Data Model.

What standards or regulatory requirements govern SNOMED CT?

SNOMED CT is maintained internationally by SNOMED International and distributed in the United States by the National Library of Medicine (NLM) under the UMLS Metathesaurus License via the semi-annual US Edition (namespace 1000124). ONC certification rules (45 CFR § 170.207 and § 170.315) and the USCDI mandate SNOMED CT for problems, procedures, and clinical findings in certified EHR technology.

How does SNOMED CT integrate with EHR and health informatics workflows?

In EHRs and HL7 FHIR R4 APIs, SNOMED CT is bound to Condition, Procedure, and Observation resources using the canonical URI http://snomed.info/sct. Clinicians search interface synonyms at the point of care to record a SNOMED CT Concept ID, which the EHR automatically cross-walks via the NLM SNOMED CT to ICD-10-CM Map for downstream billing and quality reporting.

Follow CASRAI

Research-administration guidance, standards updates and independent tool reviews.

Ask CASRAI · free to try

Ask about SNOMED CT Explained: Polyhierarchical Clinical Ontology, NLM UMLS Licensing, and HL7 FHIR CodeSystem Binding

Ask your first 2 questions free below. Subscribers get 150 a day for $29 a month.

An AI assistant specialized in research administration. It cites the sources behind every answer, labels web answers and says when it can't answer.

Answers draw on CASRAI's guides and dictionary plus the federal and funder documents we index: Federal Register, Grants.gov, Regulations.gov and UKRI.

Works on this site and inside Claude, Cursor and the AI tools you already use.

Everything CASRAI publishes — this page, the dictionary, the guides and the news — stays free to read, with no account and no card.

Referenced across the research world

University of Cambridge logoColumbia University logoCrossref logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logoUniversity of Cambridge logoColumbia University logoCrossref logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logo
  • University of Cambridge logo
  • Columbia University logo
  • Crossref logo
  • University of Edinburgh logo
  • Harvard University logo
  • University of Oxford logo
  • Princeton University logo
  • Stanford School of Medicine logo
  • University College London logo
  • ORCID logo

View CASRAI adoption →