Release 5 Draft Ballot

This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions


Vocabulary Work GroupMaturity Level: N/AStandards Status: InformativeCompartments: Not linked to any defined compartments

This is the narrative for the resource. See also the XML, JSON or Turtle format.


OPERATION: translate

The official URL for this operation definition is:

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 (i.e. 'not-related-to'), so implementers have to check the target.relationship for each match.

URL: [base]/ConceptMap/$translate

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



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


Limits the scope of the $translate operation to source codes ( that are members of this value set.


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


Limits the scope of the $translate operation to target codes ( that are members of this value set.


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 true, then the operation should return all the codes that are mapped to the 'code'/'coding'/'codeableConcept' input parameter. In this case:

The input code or coding(s) must belong to the target{{Scope}} ValueSet (rather than the source{{Scope}} ValueSet)

Any provided dependency parameters are matched against (rather than


True if the concept could be translated successfully. The value can only be true if at least one returned match has a relationship other than 'not-related-to'.


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 a relationship. Note that there may be multiple matches of equal or differing relationships, and the matches may include the 'not-related-to' relationship value which means that there is no translation


A code indicating the relationship (e.g., equivalent) of the translation, using values from ConceptMapRelationship


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


An element that this mapping depends on


The element for this product


The value for this product


The canonical reference to the concept map from which this mapping comes from



Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.