Path Parameters
The unique identifier of the concept to retrieve descendants for
Example:
Example:
73211009
(Diabetes mellitus)Query Parameters
Filter descendants to specific vocabulary
Example:
Example:
SNOMED
Maximum number of hierarchy levels to traverse downward (default: 10)
Range: 1-10. Values above 10 are capped at 10 by the server for performance reasons. Omitting this parameter defaults to the maximum of 10 levels.
Range: 1-10. Values above 10 are capped at 10 by the server for performance reasons. Omitting this parameter defaults to the maximum of 10 levels.
Relationship types to follow for hierarchy traversal. Accepts CSV string (comma-separated values) or array. Spaces must be URL-encoded (%20) in URLs. Individual entries are trimmed and matched case-insensitively.
Default:
Allowed values:
CSV Example:
Array Example:
Default:
Is a
Allowed values:
Is a
, Has part
, Subsumes
, Part of
, Has ingredient
, RxNorm has dose form
CSV Example:
Is%20a,Has%20part
(URL-encoded)Array Example:
["Is a", "Has part"]
Include hierarchical distance (level) for each descendant
Filter results by standard_concept flag. When true, restricts results to concepts with standard_concept=‘S’ (excludes classification ‘C’ and null values). When false, returns concepts regardless of standard_concept.
Include deprecated/invalid concepts in descendants. When false, excludes deprecated/invalid concepts; when true, includes them. This filter is applied after standard_only filtering.
Comma-separated list of domain IDs to filter descendants
Example:
Example:
Condition,Drug
Comma-separated list of concept class IDs to filter descendants
Example:
Example:
Clinical Finding,Procedure
Include synonym information for descendant concepts
Number of descendant concepts to return per page. Values over 1000 are automatically capped at 1000. Invalid values return HTTP 400. Results are ordered breadth-first by level, then concept_id ascending for deterministic pagination.
Page number for pagination (1-based). Uses deterministic ordering for stable pagination.
Response
The concept ID for which descendants were retrieved
Standard name of the source concept
Vocabulary containing the source concept
Array of descendant concepts in hierarchical order
Summary statistics about the descendant hierarchy
Response metadata and pagination information
Usage Examples
Note: Examples assume a preconfigured client with base URLhttps://api.omophub.com
and authentication headers. For direct usage:
Basic Descendant Retrieval
Get all descendants for a specific concept:Limited Hierarchy Depth
Retrieve descendants up to a specific number of levels:Domain-Specific Descendants
Filter descendants to specific medical domains:Detailed Descendant Information
Get descendants with synonyms and hierarchy levels:Concept Class Filtering
Find descendants of specific concept classes:Related Endpoints
- Get Concept Ancestors - Retrieve parent concepts
- Get Concept Hierarchy - Complete hierarchy view
- Get Concept Relationships - All concept relationships
- Search Concepts - Search within specific hierarchies
Notes
- Descendant traversal follows “Is a” relationships by default, but can include other relationship types
- Large hierarchies may contain thousands of descendants - use pagination and filtering appropriately
- Standard concepts are prioritized unless explicitly disabled
- Some medical concepts may have very deep hierarchies (6+ levels)
- Cross-vocabulary concepts may have descendants from multiple vocabularies
- Deprecated concepts are excluded from descendants unless specifically requested
- Synonym information adds significant detail but increases response size