This page is part of the FHIR Specification (v1.6.0:
STU
3 Ballot 4). The current version which supercedes this version is
5.0.0
.
For
a
full
list
of
available
versions,
see
the
Directory
of
published
versions
. For a full list of available versions, see the
Directory of published versions
.
Page
versions:
. Page versions:
R5
R4B
R4
R3
R2
Raw JSON
(
canonical
form
canonical form
)
Operation
Definition
)
Operation Definition
{
"resourceType": "OperationDefinition",
"id": "ConceptMap-closure",
"text": {
"status": "generated",
"div": "<div>!-- Snipped for Brevity --></div>"
},
"url": "http://hl7.org/fhir/OperationDefinition/ConceptMap-closure",
"name": "Closure Table Maintenance",
"status": "draft",
"kind": "operation",
"date": "2016-08-11T17:02:54+10:00",
"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",
"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, specializes, subsumes and unmatched",
"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.
©
HL7.org
2011+.
FHIR
DSTU2
(v1.0.2-7202)
generated
on
Sat,
Oct
24,
2015
07:43+1100.
Links:
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.