This page is part of the FHIR Specification (v0.0.82: DSTU 1). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3 R2

• Content
• Examples
• Formal Definitions
• Mappings
• Profiles

6.15 Resource ConceptMap - Content

A statement of relationships from one set of concepts to one or more other concept systems.

6.15.3 Resource Content

<ConceptMap xmlns="http://hl7.org/fhir"> 
 <!-- from Resource: extension, modifierExtension, language, text, and contained -->
 <identifier value="[string]"/><!-- 0..1 Logical id to reference this concept map § -->
 <version value="[string]"/><!-- 0..1 Logical id for this version of the concept map § -->
 <name value="[string]"/><!-- 1..1 Informal name for this concept map § -->
 <publisher value="[string]"/><!-- 0..1 Name of the publisher (Organization or individual) § -->
 <telecom><!-- 0..* Contact Contact information of the publisher § --></telecom>
 <description value="[string]"/><!-- 0..1 Human language description of the concept map § -->
 <copyright value="[string]"/><!-- 0..1 About the concept map or its content -->
 <status value="[code]"/><!-- 1..1 draft | active | retired § -->
 <experimental value="[boolean]"/><!-- 0..1 If for testing purposes, not real usage § -->
 <date value="[dateTime]"/><!-- 0..1 Date for given status § -->
 <source><!-- 1..1 Resource(ValueSet) Identifies the source value set which is being mapped § --></source>
 <target><!-- 1..1 Resource(ValueSet) Provides context to the mappings § --></target>
 <concept>  <!-- 0..* Mappings for a concept from the source valueset -->
  <system value="[uri]"/><!-- 1..1 System that defines the concept being mapped -->
  <code value="[code]"/><!-- 0..1 Identifies concept being mapped -->
  <dependsOn>  <!-- 0..* Other concepts required for this mapping (from context) -->
   <concept value="[uri]"/><!-- 1..1 Reference to element/field/valueset provides the context -->
   <system value="[uri]"/><!-- 1..1 System for a concept in the referenced concept -->
   <code value="[code]"/><!-- 1..1 Code for a concept in the referenced concept -->
  </dependsOn>
  <map>  <!-- 0..* A concept from the target value set that this concept maps to -->
   <system value="[uri]"/><!--  0..1 System of the target -->
   <code value="[code]"/><!-- 0..1 Code that identifies the target concept -->
   <equivalence value="[code]"/><!-- 1..1 equal | equivalent | wider | subsumes | narrower | specialises | inexact | unmatched | disjoint -->
   <comments value="[string]"/><!--  0..1 Description of status/issues in mapping -->
   <product><!-- 0..* Content as for ConceptMap.concept.dependsOn Other concepts that this mapping also produces --></product>
  </map>
 </concept>
</ConceptMap>

Alternate definitions: Schema/Schematron, Resource Profile

6.15.3.1 Terminology Bindings

6.15.3.2 Constraints

• Inv-1: On ConceptMap.concept.map: If the map is narrower, there SHALL be some comments (xpath on f:ConceptMap/f:concept/f:map: exists(f:comments) or ((f:equivalence/@value != 'narrower') and (f:equivalence/@value != 'inexact')))
• Inv-2: On ConceptMap.concept.map: If a code is provided, a system SHALL be provided (xpath on f:ConceptMap/f:concept/f:map: exists(f:system) or not(exists(f:code)))

6.15.4 Notes

• The value of the system and code element are the same as used by the Coding data type
• When a mapping equivalence is characterized as "narrower", some explanation of the scope difference SHALL be provided in the comments
• The concept map is a statement of mapping in a single direction. The existence of a matching mapping in the reverse direction cannot be assumed to exist automatically, but only through human review

6.15.5 Concept Translation

An application may offer to provide concept translation services for other applications. In this case, the standard way for an application to ask for concept translation is to perform a search on the value set with _query=translate:

  GET [service-url]/ConceptMap/?_query=translate&identity=:valueSet&system=:system&version=:version&code=:code&...

The identifier is the ValueSet.identifier of the value set used when the concept (system/code pair) was chosen. If an identifier is provided, the application performing the translation can locate a concept map for a matching value set; if no value set is identified, the application must look for a code equivalence assertion in a concept map where the value set the provides context matches the entire code system. The values for system, version, and code are those from the Coding data type. Version is optional, and code and system are mandatory. Alternatively, the parameter "coding" or "codeableconcept" can be used - the value of these parameters is a URL encoded XML or JSON representation of the two data types respectively.

The result of this query is an Operation Outcome with an extension http://hl7.org/fhir/Profile/general-extensions#translation, which is a codeableConcept that expresses the translation, if one could be found, or an error if one could not be found. The Operation Outcome may include warnings about how the translation was made.

6.15.6 Search Parameters

Search parameters for this resource. The standard parameters also apply. See Searching for more information about searching in REST, messaging, and services.