This page is part of the FHIR Specification (v3.2.0: R4 Ballot 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 | Ballot Status: Informative | Compartments: Not linked to any defined compartments |
Operation Definition
{ "resourceType": "OperationDefinition", "id": "ConceptMap-closure", "text": { "status": "generated", "div": "<div>!-- Snipped for Brevity --></div>" }, "url": "http://hl7.org/fhir/OperationDefinition/ConceptMap-closure", "name": "Closure Table Maintenance", "status": "draft", "kind": "operation", "date": "2017-12-20T15:52:34+11:00", "publisher": "HL7 (FHIR Project)", "contact": [ { "telecom": [ { "system": "url", "value": "http://hl7.org/fhir" }, { "system": "email", "value": "fhir@lists.hl7.org" } ] } ], "description": "This operation provides support for ongoing maintenance of a client-side [transitive closure table](https://en.wikipedia.org/wiki/Transitive_closure#In_graph_theory) based on server-side terminological logic. For details of how this is used, see [Maintaining a Closure Table](terminology-service.html#closure)", "code": "closure", "resource": [ "ConceptMap" ], "system": true, "type": false, "instance": false, "parameter": [ { "name": "name", "use": "in", "min": 1, "max": "1", "documentation": "The name that defines the particular context for the subsumption based closure table", "type": "string" }, { "name": "concept", "use": "in", "min": 0, "max": "*", "documentation": "Concepts to add to the closure table", "type": "Coding" }, { "name": "version", "use": "in", "min": 0, "max": "1", "documentation": "A request to resynchronise - request to send all new entries since the nominated version was sent by the server", "type": "id" }, { "name": "return", "use": "out", "min": 1, "max": "1", "documentation": "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", "type": "ConceptMap" } ] }
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.