DSTU2 STU 3 Ballot
This page is part of the FHIR Specification (v1.0.2: DSTU 2). The current version which supercedes this version is

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

Operation-conceptmap-closure This is the narrative for the resource. See also the

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

Closure Table Maintenance Closure Table Maintenance

OPERATION: Closure Table Maintenance OPERATION: Closure Table Maintenance

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 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

URL: [base]/$closure URL: [base]/$closure

Parameters

Use Name Cardinality Type Binding Documentation
IN name 1..1 string

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

IN concept 0..* Coding

Concepts to add to the closure table Concepts to add to the closure table

IN version 0..1 id

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

OUT return 1..1 ConceptMap

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 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. © 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.