Release 5 Preview #3

This page is part of the FHIR Specification (v4.5.0: R5 Preview #3). 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-conceptmap-closure.json

Vocabulary Work GroupMaturity Level: N/AStandards Status: InformativeCompartments: Not linked to any defined compartments

Raw JSON (canonical form + also see JSON Format Specification)

Operation Definition

{
  "resourceType" : "OperationDefinition",
  "id" : "ConceptMap-closure",
  "text" : {
    "status" : "extensions",
    "div" : "<div>!-- Snipped for Brevity --></div>"
  },
  "extension" : [{
    "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm",
    "valueInteger" : 1
  },
  {
    "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
    "valueCode" : "trial-use"
  }],
  "url" : "http://hl7.org/fhir/OperationDefinition/ConceptMap-closure",
  "version" : "4.5.0",
  "name" : "Closure Table Maintenance",
  "status" : "draft",
  "kind" : "operation",
  "date" : "2020-08-20T17:41:31+10:00",
  "publisher" : "HL7 (FHIR Project)",
  "contact" : [{
    "telecom" : [{
      "system" : "url",
      "value" : "http://hl7.org/fhir"
    },
    {
      "system" : "email",
      "value" : "fhir@lists.hl7.org"
    }]
  }],
  "description" : "This operation provides support for ongoing maintenance of a client-side [transitive closure table](https://en.wikipedia.org/wiki/Transitive_closure#In_graph_theory) based on server-side terminological logic. For details of how this is used, see [Maintaining a Closure Table](terminology-service.html#closure)",
  "code" : "closure",
  "resource" : ["ConceptMap"],
  "system" : true,
  "type" : false,
  "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" : "string"
  },
  {
    "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 relationships that can be returned are equivalent, source-is-broader-than-target and source-is-narrower-than-target.",
    "type" : "ConceptMap"
  }]
}

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.