Release 4

Vocabulary Work Group Maturity Level: 3Trial Use Compartments: N/A

This operation provides support for ongoing maintenance of a client-side transitive closure table based on server-side terminological logic. For details of how this is used, see Maintaining a Closure Table.

The official URL for this operation definition is

Formal Definition (as a OperationDefinition).

URL: [base]/$closure

This is not an idempotent operation

In Parameters:
ИмяКардинальное множествоТипПривязкаПрофильДокументация

The name that defines the particular context for the subsumption based closure table


Concepts to add to the closure table


A request to resynchronise - request to send all new entries since the nominated version was sent by the server

Out Parameters:
ИмяКардинальное множествоТипПривязкаПрофильДокументация

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

Note: as this is the only out parameter, it is a resource, and it has the name 'return', the result of this operation is returned directly as a resource


POST [base]/$closure

  "resourceType" : "Parameters",
  "parameter" : [
      "name" : "name",
      "valueString" : "patient-problems"
      "name" : "concept",
      "valueCoding" : {
        "system" : "",
        "code" : "22298006",


HTTP/1.1 200 OK
[other headers]

  "resourceType": "ConceptMap",
  "identifier": "49088976-d54d-4d19-b868-3d4c18cebabb",
  "version": "8",
  "status": "active",
  "experimental": true,
  "date": "2012-06-13",
  "group": [
      "source": "",
      "target": "",
			"element" : {
				"code": "22298006",
				"target": [
						"code": "128599005",
						"equivalence": "subsumes"


For more information about operations, including how they are invoked, see Operations.