Skip to main content

Overview

Retrieve concept information using the vocabulary-specific code instead of the universal concept ID. This is useful when working with source data that contains original codes.

Path Parameters

vocabulary_id
string
required
The vocabulary identifier (e.g., “SNOMED”, “ICD10CM”, “LOINC”)
concept_code
string
required
The vocabulary-specific code (e.g., “59621000” for SNOMED, “I10” for ICD10CM)

Response Fields

Query Parameters

vocab_release
string
Specific vocabulary release to use (e.g., “2025.2”). Uses latest if not specified.
include_synonyms
boolean
default:"false"
Include concept synonyms in the response
include_relationships
boolean
default:"false"
Include concept relationships and mappings
include_hierarchy
boolean
default:"false"
Include concept hierarchy information
include_invalid
boolean
default:"true"
Include concepts with invalid_reason set (deprecated/updated concepts). Set to false to only return valid concepts.

Common Use Cases

1. Source Data Processing

Convert source system codes to standardized concepts during ETL processes.

2. Legacy System Integration

Map existing codes from legacy healthcare systems.

3. Claims Processing

Look up diagnosis and procedure codes from insurance claims.

4. Clinical Documentation

Validate codes entered by healthcare providers.