A ConceptMap is a structured FHIR resource that explicitly defines a relationship between a concept in a source CodeSystem and one or more concepts in a target CodeSystem. It serves as a deterministic translation table, specifying whether the mapping is equivalent, broader, narrower, or unmatched, thereby enabling automated semantic translation between disparate clinical terminologies like SNOMED CT and ICD-10.
Glossary
ConceptMap
A FHIR resource that defines a mapping between concepts in one code system and concepts in another, enabling semantic translation and interoperability between different terminologies.
TERMINOLOGY MAPPING
What is ConceptMap?
A FHIR resource that defines a mapping between concepts in one code system and concepts in another, enabling semantic translation and interoperability between different terminologies.
Unlike a simple lookup table, a ConceptMap can handle complex dependsOn and product properties to manage context-dependent translations, such as those requiring patient age or gender for accurate mapping. This resource is critical for FHIR TerminologyService operations like $translate, allowing health information exchanges to normalize heterogeneous data into a unified standard like the OMOP Common Data Model without manual curation.
FHIR TERMINOLOGY SERVICE
Key Features of a ConceptMap
A ConceptMap is a critical FHIR resource that defines a semantic bridge between two distinct code systems, enabling automated translation and interoperability across heterogeneous healthcare data environments.
01
Semantic Translation Engine
Provides a structured, machine-processable mapping from a source code system to a target code system. Each mapping element specifies an equivalence relationship, such as equal, equivalent, wider, narrower, or unmatched. This allows a clinical decision support engine to automatically translate a local proprietary lab code into a standardized LOINC term for cross-institutional research without manual curation.
5+
Standard Equivalence Levels
02
Bidirectional Mapping Support
A single ConceptMap resource can define unidirectional or bidirectional translations. By specifying distinct source and target scopes using canonical URLs, the resource can map from a local code system to a standard terminology and back again. This is essential for displaying patient-friendly terms in a portal while storing precise clinical codes in the EHR backend.
03
Grouped Mapping Logic
Mappings are organized into logical groups that correspond to specific subsets of the source code system. Within each group, individual element entries define the precise translation rules. This structure supports complex, context-dependent mappings where a single source code may have multiple valid targets depending on the clinical context, such as mapping a general 'headache' code to specific SNOMED CT concepts for 'tension headache' or 'migraine' based on encounter type.
04
DependsOn and Product Chains
Supports complex mapping dependencies where a translation is only valid when additional properties are satisfied. The dependsOn property allows a mapping to require a specific value for a related attribute, such as a unit of measure or a specimen type. The product property defines the output of a mapping that generates multiple related codes, enabling sophisticated clinical data transformations.
05
Unmapped Code Handling
Explicitly defines how codes without a direct target are managed using the unmapped element. This prevents silent data loss during transformation by specifying a default fallback code or a fixed 'no mapping' indicator. This transparency is critical for maintaining data integrity in federated learning pipelines where incomplete translations could introduce systemic bias into a global model.
06
Terminology Service Integration
ConceptMap resources are invoked via the FHIR $translate operation on the Terminology Service API. A client submits a source code and system, and the server returns the corresponding target code and equivalence status. This RESTful interaction pattern allows real-time, on-demand translation within clinical workflows, CDS Hooks, and bulk data export pipelines without pre-loading entire terminologies.
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.
Enterprise searchRAGPermissions
Read more
Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.
AI agentsWorkflow automationGovernance
Read more
Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
AI integrationDecision supportModel routing
Read moreCONCEPTMAP CLARIFIED
Frequently Asked Questions
Essential questions about the FHIR ConceptMap resource, its role in semantic interoperability, and how it enables accurate translation between disparate clinical terminologies in federated healthcare environments.
A FHIR ConceptMap is a specialized resource that defines a structured mapping from a set of concepts in one CodeSystem (the source) to concepts in another CodeSystem (the target). It functions as a semantic translation layer, enabling interoperability between systems that use different clinical terminologies. The resource explicitly declares the equivalence relationship between each mapped pair—such as equivalent, wider, narrower, or unmatched—providing a deterministic, machine-readable rulebook for automated code translation. Unlike a simple lookup table, a ConceptMap can handle complex scenarios where a single source code maps to multiple target codes depending on context, or where no direct mapping exists. It is a cornerstone of terminology service operations, allowing a FHIR server to execute $translate operations that convert, for example, a local proprietary billing code into a standardized SNOMED CT or LOINC concept for cross-institutional analytics and federated learning.
About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
LinkedIn
Limited slotsGet a Free AI Consultation
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us