Current Build
Vocabulary Work Group Maturity Level: 3Normative Compartments: N/A

Normative Candidate Note: This page is candidate normative content for R4 in the Conformance Package. Once normative, it will lose it's Maturity Level, and breaking changes will no longer be made.

Translate a code from one value set to another, based on the existing value set and concept maps resources, and/or other additional knowledge available to the server.

One (and only one) of the in parameters (code, coding, codeableConcept) must be provided, to identify the code that is to be translated.

The operation returns a set of parameters including a 'result' for whether there is an acceptable match, and a list of possible matches. Note that the list of matches may include notes of codes for which mapping is specifically excluded, so implementers have to check the match.equivalence for each match

The official URL for this operation definition is

Formal Definition (as a OperationDefinition).

URL: [base]/ConceptMap/$translate

URL: [base]/ConceptMap/[id]/$translate

This is an idempotent operation

In Parameters:

A canonical url for a concept map. The server must know the concept map (e.g. it is defined explicitly in the server's concept maps, or it is defined implicitly by some code system known to the server.


The concept map is provided directly as part of the request. Servers may choose not to accept concept maps in this fashion.


The identifier that is used to identify a specific version of the concept map to be used for the translation. This is an arbitrary value managed by the concept map author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available.


The code that is to be translated. If a code is provided, a system must be provided


The system for the code that is to be translated


The version of the system, if one was provided in the source data


Identifies the value set used when the concept (system/code pair) was chosen. May be a logical id, or an absolute or relative location. The source value set is an optional parameter because in some cases, the client cannot know what the source value set is. However, without a source value set, the server may be unable to safely identify an applicable concept map, and would return an error. For this reason, a source value set SHOULD always be provided. Note that servers may be able to identify an appropriate concept map without a source value set if there is a full mapping for the entire code system in the concept map, or by manual intervention


A coding to translate


A full codeableConcept to validate. The server can translate any of the coding values (e.g. existing translations) as it chooses


Identifies the value set in which a translation is sought. May be a logical id, or an absolute or relative location. If there's no target specified, the server should return all known translations, along with their source


identifies a target code system in which a mapping is sought. This parameter is an alternative to the target parameter - only one is required. Searching for any translation to a target code system irrespective of the context (e.g. target valueset) may lead to unsafe results, and it is at the discretion of the server to decide when to support this operation


Another element that may help produce the correct mapping


The element for this dependency


The value for this dependency


if this is true, then the operation should return all the codes that might be mapped to this code. This parameter reverses the meaning of the source and target parameters

Out Parameters:

True if the concept could be translated successfully. The value can only be true if at least one returned match has an equivalence which is not unmatched or disjoint


Error details, for display to a human. If this is provided when result = true, the message carries hints and warnings (e.g. a note that the matches could be improved by providing additional detail)


A concept in the target value set with an equivalence. Note that there may be multiple matches of equal or differing equivalence, and the matches may include equivalence values that mean that there is no match


A code indicating the equivalence of the translation, using values from ConceptMapEquivalence


The translation outcome. Note that this would never have userSelected = true, since the process of translations implies that the user is not selecting the code (and only the client could know differently)


Another element that is the product of this mapping


The element for this product


The value for this product


The canonical URI for the concept map from which this mapping comes from


GET [base]/ConceptMap/$translate?system=


HTTP/1.1 200 OK
[other headers]

  "resourceType": "Parameters",
  "parameter": [
      "name": "result",
      "valueBoolean": true
      "name": "match",
      "part": [
          "name": "equivalence",
          "valueCode": "equivalent"
          "name": "concept",
          "valueCoding": {
            "system": "",
            "code": "active",
            "userSelected": false


For more information about operations, including how they are invoked, see Operations.