Release 4B 5

This page is part of the FHIR Specification (v4.3.0: R4B (v5.0.0: R5 - STU ). The This is the current published version which supercedes in it's permanent home (it will always be available at this version is 5.0.0 . URL). For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R5 R4B R4 R3 R2

Operation-conceptmap-closure

Example OperationDefinition/ConceptMap-closure (Narrative)

Vocabulary Terminology Infrastructure Work Group Maturity Level : N/A Standards Status : Informative Compartments : Not linked to any No defined compartments

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

Closure OPERATION: Closure The official URL for

Note that this operation is the formal definition is: http://hl7.org/fhir/OperationDefinition/ConceptMap-closure This operation provides support for ongoing maintenance of a client-side transitive the closure table based operation as an OperationDefinition on server-side terminological logic. For details of how this is used, see Maintaining a Closure Table ConceptMap. See the Operation documentation

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 equivalences relationships that can be returned are equal, specializes, subsumes equivalent, source-is-broader-than-target and unmatched 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.