FHIR CI-Build

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

Example OperationDefinition/ConceptMap-translate (Narrative)

Terminology Infrastructure Work GroupMaturity Level: N/AStandards Status: InformativeCompartments: No defined compartments

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

Note that this is the formal definition for the translate operation as an OperationDefinition on ConceptMap. See the Operation documentation


Generated Narrative: OperationDefinition ConceptMap-translate

URL: [base]/ConceptMap/$translate

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

Parameters

UseNameScopeCardinalityTypeBindingDocumentation
IN url type 0..1 uri

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.

IN conceptMap type 0..1 ConceptMap

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

IN conceptMapVersion type 0..1 string

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.

IN sourceCode 0..1 code

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

IN system 0..1 uri

The system for the code that is to be translated

IN version 0..1 string

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

IN sourceScope 0..1 uri

Limits the scope of the $translate operation to source codes (ConceptMap.group.element.code) that are members of this value set.

IN sourceCoding 0..1 Coding

A coding to translate

IN sourceCodeableConcept 0..1 CodeableConcept

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

IN targetCode 0..1 code

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

IN targetCoding 0..1 Coding

A target coding to translate to

IN targetCodeableConcept 0..1 CodeableConcept

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

IN targetScope 0..1 uri

Limits the scope of the $translate operation to target codes (ConceptMap.group.element.target.code) that are members of this value set.

IN targetSystem 0..1 uri

identifies a target code system in which a mapping is sought. This parameter is an alternative to the targetScope 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

IN dependency 0..*

Data from another attribute that may help produce the correct mapping

IN dependency.attribute 0..1 uri

The attribute for this dependency

IN dependency.value 0..1 code | Coding | string | boolean | Quantity

The data value for this dependency

OUT result 1..1 boolean

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'.

OUT message 0..1 string

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)

OUT match 0..*

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

OUT match.relationship 0..1 code

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

OUT match.concept 0..1 Coding

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)

OUT match.property 0..*

A property of this mapping (may be used to supply for example, mapping priority, provenance, presentation hints, flag as experimental, and additional documentation)

OUT match.property.uri 1..1 uri

The uri that identifies the property

OUT match.property.value 1..1 Coding | string | integer | boolean | dateTime | decimal | code

The value of the property

OUT match.product 0..*

A data value to go in an attribute that is the product of this mapping

OUT match.product.attribute 1..1 uri

The attribute for this product

OUT match.product.value 1..1 code | Coding | string | boolean | Quantity

The value for this product

OUT match.dependsOn 0..*

An data value in an additional attribute that this mapping depends on

OUT match.dependsOn.attribute 1..1 uri

The attribute for this product

OUT match.dependsOn.value 1..1 code | Coding | string | integer | boolean | dateTime | decimal | uri | id

The value for this product

OUT match.originMap 0..1 uri

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.