Get Mapping Coverage
Analyze mapping coverage between a source and target OMOP vocabulary - quantify how many concepts translate across SNOMED, ICD-10, LOINC, and RxNorm.
Overview
This endpoint analyzes mapping coverage between two vocabularies, providing domain-level breakdown and identifying unmapped concepts. Useful for understanding interoperability between vocabulary pairs.Query Parameters
Source vocabulary ID to analyze mappings from
Example:
Example:
SNOMEDTarget vocabulary ID to analyze mappings to
Example:
Example:
ICD10CMComma-separated domain IDs to filter the analysis
Example:
Example:
Condition,DrugSpecific vocabulary release version (e.g., “2025.1”)
Response
Indicates if the request was successful
Coverage analysis results
Response metadata and API information
Usage Examples
Basic Coverage Analysis
Analyze coverage from SNOMED to ICD-10-CM:TypeScript
Filter by Domain
Analyze coverage for specific domains only:TypeScript
Use Specific Vocabulary Version
Analyze coverage for a specific vocabulary release:TypeScript
Related Endpoints
- Get Concept Mappings - Mappings for specific concepts
- Get Mapping Quality - Quality metrics between vocabularies
- Map Concepts - Map concepts to a target vocabulary
Notes
- Both
source_vocabularyandtarget_vocabularyare required parameters - The
unmapped_conceptsarray contains a sample of up to 100 unmapped concepts - Coverage percentages are calculated based on valid, non-deprecated concepts
- Use
domain_idsto focus analysis on specific medical domains