Release 5

This page is part of the FHIR Specification (v5.0.0: R5 - STU). This is the current published version. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3 R2

Example OperationDefinition/ConceptMap-closure (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 closure operation as an OperationDefinition on ConceptMap. See the Operation documentation


URL: [base]/$closure

Parameters

UseNameScopeCardinalityTypeBindingDocumentation
INname1..1string

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

INconcept0..*Coding

Concepts to add to the closure table

INversion0..1string

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

OUTreturn1..1ConceptMap

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.