Release 5 R6 Ballot (3rd Draft)
This page is part of the FHIR Specification (v5.0.0: R5 - STU ). This is the current published version in it's permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3 R2

Publish-box (todo)

Example OperationDefinition/ConceptMap-closure (Narrative)

Terminology Infrastructure Work Group Maturity Level : N/A Standards Status : Informative Compartments : 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 closure operation as an OperationDefinition on ConceptMap. See the Operation documentation

Generated Narrative: OperationDefinition ConceptMap-closure

URL: [base]/$closure

Parameters

Use Name Scope Cardinality Type Binding Documentation
IN name 1..1 string

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

IN concept 0..* Coding

Concepts to add to the closure table

IN version 0..1 string

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

OUT return 1..1 ConceptMap

A list of new entries (code / system --> code/system) that the client should add to its closure table. The only kind of entry mapping relationships that can be returned are equivalent, source-is-broader-than-target and source-is-narrower-than-target.

 

 

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.