This page is part of the FHIR Specification (v4.2.0: R5 Preview #1). 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
Vocabulary Work Group | Maturity Level: N/A | Standards Status: Informative | Compartments: Not linked to any defined compartments |
This is the narrative for the resource. See also the XML, JSON or Turtle format.
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 | 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, narrower and broader. |
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.