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

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

Response Fields

boolean
Whether the lookup succeeded.
object
Matching concept record.
integer
OMOP concept identifier.
string
Primary concept name.
string
Matched source code.
string
Matched vocabulary.
string
OMOP domain.
string
Concept class.
string | null
S, C, or null.
string
Validity start date.
string
Validity end date.
string | null
Invalidity marker, or null.
boolean
Derived validity flag.
boolean
Whether this is a standard concept.
boolean
Whether this is a classification concept.
array
Synonym names, present when include_synonyms=true.
object
Parent and child relationships, present when include_relationships=true.
object
Request metadata.
string
Request correlation ID.
string
Response timestamp.
string
Vocabulary release used.

Query Parameters

string
Specific vocabulary release to use (e.g., “2025.2”). Uses latest if not specified.
boolean
default:"false"
Include concept synonyms in the response
boolean
default:"false"
Include concept relationships and mappings
boolean
default:"false"
Include concept hierarchy information
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.