FHIR Release 3 (STU) 4

This page is part of the FHIR Specification (v3.0.2: (v4.0.1: R4 - Mixed Normative and STU 3). ) in it's permanent home (it will always be available at this URL). 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 R4 R3 R2

Operation-conceptmap-closure

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

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

Closure Table Maintenance

OPERATION: Closure Table Maintenance

The official URL for this operation definition is: 

http://hl7.org/fhir/OperationDefinition/ConceptMap-closure

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

URL: [base]/$closure

Parameters

Use Name 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 id 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 that can be returned are equal, specializes, subsumes and unmatched

 

 

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.