2nd DSTU Draft For Comment

This page is part of the FHIR Specification (v0.4.0: DSTU 2 Draft). 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

Operation-conceptmap-translate

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

Concept Translation

OPERATION: Concept Translation

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 outcome is an operationOutcome with hints, warnings, or errors, or the translated code in an extension

URL: [base]/ConceptMap/$Concept Translation

URL: [base]/ConceptMap/[id]/$Concept Translation

Parameters

UseNameCardinalityTypeDocumentation
INcode0..1code

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

INsystem0..1uri

The system for the code that is to be translated

INversion0..1string

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

INvalueSet0..1uri

Identifies the value set used when the concept (system/code pair) was chosen. May be a logical id, or an absolute or relative location

INcoding0..1Coding

A coding to translate

INcodeableConcept0..1CodeableConcept

A full codeableConcept to validate. The server can translate any of the coding values as it chooses

INtarget1..1uri

Identifies the value set in which a translation is sought. May be a logical id, or an absolute or relative location

OUTresult1..1boolean

True if the concept could be translated

OUTmessage0..1string

Error details, if result = false. If this is provided when result = true, the message carries hints and wanrings

OUToutcome0..1Coding

The translation outcome

 

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.