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

6.25.11 Resource ConceptMap - Operations

This resource has 2 operations associated with it. For more information about operations, including how they are invoked, see Operations.

6.25.11.1 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

Formal Definition (as a OperationDefinition).

URL: [base]/ConceptMap/$translate

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

In Parameters:
NameCardinalityTypeProfileDocumentation
code0..1code

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

system0..1uri

The system for the code that is to be translated

version0..1string

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

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

coding0..1Coding

A coding to translate

codeableConcept0..1CodeableConcept

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

target1..1uri

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

Out Parameters:
NameCardinalityTypeProfileDocumentation
result1..1boolean

True if the concept could be translated

message0..1string

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

outcome0..1Coding

The translation outcome

6.25.11.2 Closure Table Maintenance

This operation provides support for ongoing maintenance of a client-side closure table based on server-side terminological logic. For details of how this is used, see Maintaining a Closure Table

Formal Definition (as a OperationDefinition).

URL: [base]/$closure

In Parameters:
NameCardinalityTypeProfileDocumentation
name1..1string

The name that defines the particular context for the subsumption based closure table

concept0..*Coding

Concepts to add to the closure table

version0..1id

A request to resynchronise - request to send all new entries since the nominated version was sent by the server

Out Parameters:
NameCardinalityTypeProfileDocumentation
return1..1ConceptMap

A list of new entries (code / system --> code/system) that the client should add to it's closure table. The only kind of entry mapping equivalences that can be returned are equal, narrower, wider, and unmatched

Note: as this the only out parameter, it is a resource, and it has the name 'return', the result of this operation is returned directly as a resource