Release 4B Snapshot #1

This page is part of the FHIR Specification (v4.3.0-snapshot1: Release 4B Snapshot #1). 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

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

This is the narrative for the resource. See also the XML, JSON or Turtle format.


closure

OPERATION: closure

The official URL for this operation definition is:

http://hl7.org/fhir/OperationDefinition/ConceptMap-closure

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

URL: [base]/$closure

Parameters

UseNameCardinalityTypeBindingDocumentation
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 equivalences that can be returned are equal, specializes, subsumes and unmatched


 

 

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.