A taxonomy is a controlled vocabulary arranged in a strict hierarchical structure, where each concept inherits meaning from its broader parent term. Unlike flat lists, this tree-like organization enforces a single, unambiguous path from a general category down to a specific instance, making it a foundational tool for entity categorization and faceted search in information architecture.
Glossary
Taxonomy

What is a Taxonomy?
A taxonomy is a hierarchical classification scheme that organizes concepts into parent-child relationships, providing a simple but powerful structure for navigation and entity categorization within a knowledge organization system.
In the context of knowledge graphs, a taxonomy often serves as the lightweight schema backbone, defining the 'is-a' relationships between entity types. While less expressive than a full ontology, its simplicity enables high-performance navigation and consistent document tagging, directly supporting concept normalization and automated classification pipelines.
Core Characteristics of a Taxonomy
A taxonomy is a hierarchical classification scheme that organizes concepts into parent-child relationships. It provides a simple but powerful structure for navigation and entity categorization within a knowledge organization system.
Hierarchical Structure
A taxonomy organizes concepts into a strict tree-like hierarchy where each node has a single parent, creating clear is-a relationships. This structure enables intuitive drill-down navigation from broad categories to specific instances.
- Root node: The most general category at the top
- Child nodes: Increasingly specific subcategories
- Leaf nodes: The most granular, specific terms
- Depth: The number of levels from root to leaf
Example: Medical Devices > Cardiovascular Devices > Stents > Drug-Eluting Coronary Stents
Inheritance of Properties
In a taxonomy, child nodes inherit the characteristics of their parent nodes. This property inheritance is a fundamental reasoning mechanism that allows systems to infer that a specific instance possesses all the attributes of its broader category.
- A Drug-Eluting Coronary Stent inherits all properties of a Stent
- A Stent inherits all properties of a Cardiovascular Device
- This enables downward inference without explicit assertion
This inheritance logic is distinct from an ontology, which can define more complex, non-hierarchical relationships.
Single Inheritance Model
Unlike ontologies or knowledge graphs, a strict taxonomy enforces single inheritance—each child concept can have only one parent. This constraint ensures a clean, unambiguous tree structure that is easy to navigate and maintain.
- Monohierarchy: One concept, one parent location
- No polyhierarchy: A concept cannot belong to multiple branches
- Simplifies classification decisions for human curators
- Reduces ambiguity in browsing and search interfaces
For domains requiring multi-parent relationships, an ontology or polyhierarchical taxonomy is more appropriate.
Controlled Vocabulary Foundation
A taxonomy serves as a controlled vocabulary, establishing a set of authorized, preferred terms for a domain. This eliminates synonym confusion and ensures consistent tagging across an organization.
- Preferred terms: The single authorized label for a concept
- Non-preferred terms: Synonyms mapped to the preferred term (see references)
- Scope notes: Definitions that clarify when a term should be used
- Term disambiguation: Distinguishing homonyms with different meanings
This control is critical for accurate document classification, content tagging, and faceted search.
Taxonomy vs. Ontology
While both are knowledge organization systems, a taxonomy is a simpler, hierarchical subset of an ontology. Understanding the distinction is crucial for selecting the right tool for a given use case.
| Feature | Taxonomy | Ontology |
|---|---|---|
| Structure | Tree hierarchy | Directed graph |
| Relationships | Parent-child (is-a) | Rich, custom semantic relations |
| Inheritance | Single | Multiple |
| Reasoning | Basic inheritance | Complex logical inference |
| Complexity | Low | High |
A taxonomy is ideal for navigation and classification, while an ontology excels at complex querying and inference.
Use Cases in Healthcare
Taxonomies are foundational to organizing clinical information for interoperability and analytics. They provide the backbone for coding systems and content management in electronic health records.
- ICD-10-CM: A hierarchical taxonomy of disease and procedure codes for billing
- MedDRA: A taxonomy of medical terminology for adverse event reporting in pharmacovigilance
- EHR Problem Lists: Organizing patient diagnoses into a navigable hierarchy
- Clinical Content Portals: Structuring guidelines and reference materials for point-of-care access
- Quality Measure Grouping: Categorizing clinical quality measures for reporting programs
Frequently Asked Questions
Clear, technical answers to the most common questions about hierarchical classification schemes and their role in organizing clinical knowledge.
A taxonomy is a hierarchical classification scheme that organizes concepts into strict parent-child relationships based on a single, unambiguous principle of division. Each child node inherits all the properties of its parent, creating a tree structure where every entity belongs to exactly one branch. This is fundamentally different from an ontology, which models a domain using a rich network of semantic relationships—including equivalence, restriction, and disjointness axioms—allowing an entity to have multiple parent classes and complex property constraints. In clinical informatics, a taxonomy like ICD-10-CM classifies diseases into mutually exclusive categories for billing, while an ontology like SNOMED CT defines polyhierarchical is-a relationships and defining attributes to support clinical reasoning. The key distinction is that taxonomies are simple, rigid trees optimized for navigation and categorization, whereas ontologies are expressive, graph-based models designed for inference and semantic interoperability.
Taxonomy Examples in Healthcare
A taxonomy is a hierarchical classification scheme that organizes concepts into parent-child relationships. In healthcare, taxonomies provide a foundational structure for navigating medical knowledge, enabling consistent entity categorization and semantic interoperability across clinical systems.
ICD-10-CM Disease Classification
The International Classification of Diseases, 10th Revision, Clinical Modification is a hierarchical taxonomy maintained by the WHO and adapted by CMS for US healthcare. It organizes diseases into 21 chapters based on etiology and body system.
- Chapter-level: Neoplasms (C00-D49), Circulatory System (I00-I99)
- Block-level: Malignant neoplasms of digestive organs (C15-C26)
- Category-level: Malignant neoplasm of stomach (C16)
- Subcategory-level: Malignant neoplasm of cardia (C16.0)
This strict is-a hierarchy enables consistent billing, epidemiological tracking, and cohort identification across EHR systems.
RxNorm Drug Taxonomy
RxNorm, maintained by the National Library of Medicine, provides a normalized naming taxonomy for clinical drugs. It organizes medications into a multi-level hierarchy that links brand names, generics, and ingredient-level concepts.
- Ingredient: Atorvastatin
- Clinical Drug Component: Atorvastatin 20 MG
- Brand Name: Lipitor
- Clinical Drug: Atorvastatin 20 MG Oral Tablet [Lipitor]
This taxonomic structure enables medication reconciliation across disparate EHR systems by mapping local formularies to a single canonical hierarchy.
LOINC Laboratory Test Hierarchy
Logical Observation Identifiers Names and Codes (LOINC) provides a taxonomic framework for laboratory and clinical observations. It organizes tests into a six-axis hierarchy rather than a simple tree, using semantically typed components.
- Component: Glucose
- Property: Mass Concentration
- Timing: Point in Time
- System: Serum/Plasma
- Scale: Quantitative
- Method: Enzymatic
This multi-axial taxonomy enables precise semantic mapping of lab results across different hospital information systems and reference laboratories.
SNOMED CT Hierarchical Relationships
SNOMED CT employs a polyhierarchical taxonomy where a single concept can have multiple parent relationships through its |is a| attribute. This distinguishes it from strict tree-based taxonomies.
- Concept: Viral pneumonia (SNOMED ID: 75570004)
- Parent 1: Infective pneumonia (by etiology)
- Parent 2: Viral respiratory infection (by pathogen type)
- Parent 3: Lung disease (by anatomical site)
This multi-parent taxonomy enables powerful subsumption reasoning—a query for 'lung disease' will retrieve viral pneumonia regardless of which hierarchical path the query engine traverses.
MedDRA Adverse Event Hierarchy
The Medical Dictionary for Regulatory Activities (MedDRA) provides a five-level taxonomic hierarchy for adverse event reporting in pharmacovigilance. Each level aggregates terms with increasing granularity.
- System Organ Class (SOC): Cardiac disorders (highest level)
- High-Level Group Term (HLGT): Coronary artery disorders
- High-Level Term (HLT): Ischaemic coronary artery disorders
- Preferred Term (PT): Myocardial infarction
- Lowest Level Term (LLT): Heart attack (lowest, most granular)
This taxonomy is mandatory for FDA and EMA regulatory submissions, ensuring consistent safety signal detection across global clinical trials.
CPT Procedural Taxonomy
The Current Procedural Terminology (CPT) taxonomy, maintained by the AMA, classifies medical procedures and services into three categories with a strict numeric hierarchy.
- Category I: Standard procedures (e.g., 99213 - Office visit, established patient)
- Category II: Performance measurement tracking codes
- Category III: Emerging technologies and procedures
Within Category I, codes are organized by anatomical system and procedure type:
- Surgery codes: 10004-69990
- Radiology codes: 70010-79999
- Pathology codes: 80047-89398
This taxonomy is the primary billing lexicon for US healthcare reimbursement, directly linking clinical documentation to revenue cycle management.
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Taxonomy vs. Ontology vs. Folksonomy
A structural comparison of three distinct approaches to organizing and classifying information, from rigid hierarchies to emergent social tagging.
| Feature | Taxonomy | Ontology | Folksonomy |
|---|---|---|---|
Core Structure | Hierarchical tree (parent-child) | Semantic graph with axioms | Flat, non-hierarchical tag cloud |
Relationship Types | Broader/Narrower (single inheritance) | Rich, domain-specific properties (e.g., treats, causes, located_in) | None; associative co-occurrence only |
Formality Level | Controlled vocabulary | Formal logic constraints (OWL, RDFS) | Uncontrolled, emergent vocabulary |
Primary Author | Domain experts and taxonomists | Ontology engineers and domain specialists | End users and community members |
Reasoning Capability | |||
Disambiguation | Implied by hierarchical context | Explicit via unique URIs and axioms | None; polysemy and synonymy are common |
Typical Use Case | Website navigation, file systems, biological classification | Clinical decision support, knowledge graph schemas, semantic interoperability | Social bookmarking (e.g., Flickr, Delicious), content discovery |
Change Management | Top-down, controlled revision cycles | Formal versioning and deprecation protocols | Bottom-up, organic, and continuous |
Related Terms
A taxonomy is a foundational knowledge organization system. Explore the related concepts that define how taxonomies are structured, queried, and integrated into broader semantic architectures.
Concept Normalization
The task of mapping diverse textual mentions of a concept to a single canonical identifier in a standardized vocabulary. In a clinical taxonomy, this resolves synonymy by linking 'heart attack,' 'myocardial infarction,' and 'MI' to the same concept ID. This process is critical for consistent data aggregation and ensures that a taxonomy's hierarchical structure is populated with clean, unambiguous entities.
Entity Resolution
The computational process of identifying and merging disparate records that refer to the same real-world entity. Before populating a taxonomy, entity resolution deduplicates source data by determining that 'John Smith' in one database and 'J. Smith' in another are the same patient. This ensures the taxonomy is built on a foundation of clean, non-redundant master data.
Graph Traversal
The algorithmic process of visiting nodes in a graph by following edges according to specific rules. In a taxonomy stored as a graph, traversal algorithms like breadth-first search efficiently retrieve all descendants of a parent concept. This is fundamental to executing queries that require navigating the hierarchical tree structure to aggregate data at different levels of granularity.
Semantic Layer
A business abstraction that maps complex underlying data sources into a unified, business-friendly terminology. A taxonomy often serves as the core navigational structure of a semantic layer, allowing non-technical users to query data using familiar hierarchical categories without understanding the physical table schemas or join logic of the underlying data warehouse.

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us