This page is part of the FHIR Specification (v0.0.82: DSTU 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
Operation Definition
<OperationDefinition xmlns="http://hl7.org/fhir"> <id value="ConceptMap-closure"/> <text> <status value="generated"/> <div xmlns="http://www.w3.org/1999/xhtml"><!-- Snipped for brevity --></div> </text> <url value="http://hl7.org/fhir/OperationDefinition/ConceptMap-closure"/> <name value="Closure Table Maintenance"/> <publisher value="HL7 (FHIR Project)"/> <contact> <telecom> <system value="url"/> <value value="http://hl7.org/fhir"/> </telecom> <telecom> <system value="email"/> <value value="fhir@lists.hl7.org"/> </telecom> </contact> <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)"/> <status value="draft"/> <date value="2015-03-27T00:13:00+11:00"/> <kind value="operation"/> <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.