Map Concepts
Map medical concepts between OMOP vocabularies to find equivalent or related concepts across SNOMED, ICD-10, LOINC, RxNorm, and other terminologies.
Documentation Index
Fetch the complete documentation index at: https://docs.omophub.com/llms.txt
Use this file to discover all available pages before exploring further.
Overview
This endpoint maps medical concepts from source vocabularies to target vocabularies, finding equivalent or related concepts across different medical terminology systems. It’s essential for healthcare data integration, cross-system interoperability, and clinical data standardization.Request Body
Query Parameters
Specific vocabulary release version to use for mapping (e.g., “2025.1”, “2024.2”).
When not specified, uses the default/latest vocabulary version.
Response
Indicates if the request was successful
Error information (present only on error responses)
Contains the concept mapping results
Response metadata
Understanding OMOP Mapping Direction
Usage Examples
ICD-10 to SNOMED (most common use case)
Map ICD-10-CM diagnosis codes to SNOMED standard concepts:Cross-System Integration
Map multiple ICD-10 codes for EHR standardization:Drug Mapping
Map drug codes from NDC to RxNorm:Using OMOP Concept IDs
If you already have OMOP concept IDs (e.g., from a search result), usesource_concepts instead of source_codes:
The
source_concepts parameter expects OMOP concept IDs (internal database IDs), NOT vocabulary-specific codes.
If you have vocabulary codes (e.g., ICD-10 code “E11.9”), use the source_codes parameter instead,
or first look up the OMOP concept ID using /v1/concepts/by-code/{vocabulary}/{code}.Related Endpoints
- Batch Map Concepts - Batch mapping operations
- Get Concept Mappings - Get mappings for a specific concept
- Validate Mappings - Validate mapping accuracy