{

"resourceType": "OperationDefinition",
"id": "ConceptMap-closure",
"text": {
  "status": "generated",
  "div": "<div><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>\n</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>\n</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>\n</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>\n</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 --&gt; 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>\n</div></td></tr></table></div>"
},
"url": "http://hl7.org/fhir/OperationDefinition/ConceptMap-closure",
"name": "Closure Table Maintenance",
"status": "draft",
"kind": "operation",
"publisher": "HL7 (FHIR Project)",
"contact": [
  {
    "telecom": [
      {
        "system": "other",
        "value": "http://hl7.org/fhir"
      },
      {
        "system": "email",
        "value": "fhir@lists.hl7.org"
      }
    ]
  }
],
"date": "2015-10-24T07:41:03+11:00",
"description": "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": "closure",
"system": true,
"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, narrower, wider, and unmatched",
    "type": "ConceptMap"
  }
]

}