Generated Narrative: OperationDefinition ConceptMap-closure

Last updated: 2021-01-05 10:01:24+1100

URL: [base]/$closure

Parameters

UseNameScopeCardinalityTypeBindingDocumentation
INname1..1string

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

INconcept0..*Coding

Concepts to add to the closure table

INversion0..1string

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

OUTreturn1..1ConceptMap

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.

 <status value="active"/> <kind value="operation"/> <date value="2021-01-05T10:01:24+11:00"/> <publisher value="HL7 International / Terminology Infrastructure"/> <contact> <name value="HL7 International / Terminology Infrastructure"/> <telecom> <system value="url"/> <value value="http://www.hl7.org/Special/committees/Vocab"/> </telecom> </contact> <contact> <telecom> <system value="url"/> <value value="http://www.hl7.org/Special/committees/Vocab"/> </telecom> </contact> <description value="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)"/> <jurisdiction> <coding> <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/> <code value="001"/> <display value="World"/> </coding> </jurisdiction> <affectsState value="true"/> <code value="closure"/> <resource value="ConceptMap"/> <system value="true"/> <type value="false"/> <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="string"/> </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 relationships that can be returned are equivalent, source-is-broader-than-target and source-is-narrower-than-target."/> <type value="ConceptMap"/> </parameter> </OperationDefinition>