Path Parameters
The domain identifier to retrieve hierarchy for
Example:
Example:
Condition
, Drug
, Procedure
Query Parameters
Filter hierarchy to specific vocabularies within the domain
Example:
Example:
SNOMED,ICD10CM
Start hierarchy from a specific root concept (instead of domain roots)
Example:
Example:
404684003
(Clinical finding)Maximum hierarchy depth to traverse
Range:
Range:
1-10
Minimum number of children required to include a concept in hierarchy
Include count of descendant concepts for each node
Include concepts with no children (leaf nodes)
Only include standard concepts in hierarchy
Only include active (non-deprecated) concepts
Response format for hierarchy data
Options:
Options:
nested
- Hierarchical parent-child objects with nested structure preservedflat
- Flattened array of hierarchy_paths (each entry is a root→leaf path with depth implied by path length)tree
- One or more root-based trees (may include multiple disconnected root nodes) suitable for tree rendering
Sort hierarchy nodes by specified criteria
Options:
Options:
concept_name
, concept_id
, direct_children_count
Sort order for hierarchy nodes
Options:
Options:
asc
, desc
Response
Information about the domain being analyzed
The hierarchical structure of the domain
Statistical summary of the domain hierarchy
Suggestions for UI navigation and display
Response metadata and processing information
Usage Examples
Basic Domain Hierarchy
Get the hierarchical structure of a domain:Limited Depth Hierarchy
Get hierarchy with limited depth for performance:SNOMED-Only Hierarchy
Get hierarchy for specific vocabulary:Flat Path Format
Get hierarchy as flat paths instead of nested structure:Specific Root Analysis
Start hierarchy from a specific concept:Related Endpoints
- Get Domains - Available domains
- Get Domain Concepts - All concepts in domain
- Get Concept Ancestors - Specific concept ancestry
- Get Concept Descendants - Specific concept children
Notes
- Domain hierarchies can be very large - use depth limits and thresholds appropriately
- Standard concepts provide more reliable hierarchical structures
- Some domains have multiple disconnected root nodes when using tree format
- Navigation hints help build intuitive user interfaces
- Orphaned concepts exist in the domain but lack hierarchical relationships
- Vocabulary-specific hierarchies may have different organizational principles
- Branch statistics help identify significant sub-domains for focused analysis
- Truncation may occur for very large hierarchies to maintain performance