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.
Operation Definition
<OperationDefinition xmlns="http://hl7.org/fhir"> <id value="ConceptMap-closure"/> <text> <status value="generated"/> <div xmlns="http://www.w3.org/1999/xhtml"> <h2>Closure Table Maintenance</h2> <p>OPERATION: Closure Table Maintenance</p> <div> <p>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 <a href="terminology-service.html#closure">Maintaining a Closure Table</a> </p> </div> <p>URL: [base]/$closure</p> <p>Parameters</p> <table class="grid"> <tr> <td> <b>Use</b> </td> <td> <b>Name</b> </td> <td> <b>Cardinality</b> </td> <td> <b>Type</b> </td> <td> <b>Binding</b> </td> <td> <b>Documentation</b> </td> </tr> <tr> <td>IN</td> <td>name</td> <td>1..1</td> <td>string</td> <td/> <td> <div> <p>The name that defines the particular context for the subsumption based closure table</p> </div> </td> </tr> <tr> <td>IN</td> <td>concept</td> <td>0..*</td> <td>Coding</td> <td/> <td> <div> <p>Concepts to add to the closure table</p> </div> </td> </tr> <tr> <td>IN</td> <td>version</td> <td>0..1</td> <td>id</td> <td/> <td> <div> <p>A request to resynchronise - request to send all new entries since the nominated version was sent by the server</p> </div> </td> </tr> <tr> <td>OUT</td> <td>return</td> <td>1..1</td> <td>ConceptMap</td> <td/> <td> <div> <p>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</p> </div> </td> </tr> </table> </div> </text> <url value="http://hl7.org/fhir/OperationDefinition/ConceptMap-closure"/> <name value="Closure Table Maintenance"/> <status value="draft"/> <kind value="operation"/> <publisher value="HL7 (FHIR Project)"/> <contact> <telecom> <system value="other"/> <value value="http://hl7.org/fhir"/> </telecom> <telecom> <system value="email"/> <value value="fhir@lists.hl7.org"/> </telecom> </contact> <date value="2015-12-03T09:57:31+11:00"/> <description value="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](terminology-service.html#closure)"/> <code value="closure"/> <system value="true"/> <instance value="false"/> <parameter> <name value="name"/> <use value="in"/> <min value="1"/> <max value="1"/> <documentation value="The name that defines the particular context for the subsumption based closure table"/> <type value="string"/> </parameter> <parameter> <name value="concept"/> <use value="in"/> <min value="0"/> <max value="*"/> <documentation value="Concepts to add to the closure table"/> <type value="Coding"/> </parameter> <parameter> <name value="version"/> <use value="in"/> <min value="0"/> <max value="1"/> <documentation value="A request to resynchronise - request to send all new entries since the nominated version was sent by the server"/> <type value="id"/> </parameter> <parameter> <name value="return"/> <use value="out"/> <min value="1"/> <max value="1"/> <documentation value="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"/> <type value="ConceptMap"/> </parameter> </OperationDefinition>
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.