This page is part of the FHIR Specification (v1.1.0: STU 3 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
This is a frozen snapshot of the FHIR specification created for the purpose of balloting the GAO implementation Guide. It includes draft changes that may be part of the future DSTU 2.1 release but further change is expected. Readers should focus solely on the GAO implementation content, and FHIR DSTU 2 for other purposes.
This is the narrative for the resource. See also the XML or JSON format.
OPERATION: Closure Table Maintenance
This operation provides support for ongoing maintenance of a client-side 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 | 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, narrower, wider, 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.