Get Mappings for a Concept
Find how a concept maps to other vocabularies:Filter by Target Vocabulary
Include Invalid Mappings
Use Specific Vocabulary Version
Map Multiple Concepts
Map a batch of concept IDs to a target vocabulary:Map Using Vocabulary Codes
Map concepts directly using vocabulary codes instead of OMOP concept IDs:Use
sourceCodes when you have vocabulary-specific codes (e.g. SNOMED codes from your source system).
Use sourceConcepts when you already have OMOP concept IDs.
You cannot use both in the same request - the SDK enforces this at the type level via a discriminated union and re-validates at runtime so JS callers also get a structured missing_required_field error rather than a wire 400.Map with Specific Mapping Type
Filter mappings by type:Vocabulary Release Pinning
vocabRelease is sent as a query-string parameter, not in the JSON body - matches the Python SDK convention:
Procedure-Domain Vocabulary Priority
For Procedure-domain sources, the API applies a fallback vocabulary priority whentargetVocabulary is left to “best fit” semantics:
Common Use Case: SNOMED → ICD-10
Option 1: Direct mapping using vocabulary codes (recommended)Idempotency
POST endpoints (mappings.map) only retry on transient failures when an Idempotency-Key is provided: