FHIR Release 3 (STU) CI-Build

This page is part of the FHIR Specification (v3.0.2: STU 3). The current version which supercedes this version is 5.0.0 . For a full list Continuous Integration Build of available versions, see FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions . Page versions: R5 R4B R4 R3

Operation-codesystem-subsumes

Example OperationDefinition/CodeSystem-subsumes (Narrative)

Maturity Level : N/A
Responsible Owner: Vocabulary Terminology Infrastructure Work Group Ballot Standards Status : Informative Compartments : Not linked to any No defined compartments

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

Note that this is the formal definition for the subsumes operation as an OperationDefinition on CodeSystem. See the Operation documentation

Subsumption Testing

OPERATION: Subsumption Testing Generated Narrative: OperationDefinition CodeSystem-subsumes The official URL for this operation definition is:

http://hl7.org/fhir/OperationDefinition/CodeSystem-subsumes Test the subsumption relationship between code/Coding A and code/Coding B given the semantics of subsumption in the underlying code system (see hierarchyMeaning)

URL: [base]/CodeSystem/$subsumes

URL: [base]/CodeSystem/[id]/$subsumes

Parameters

Use Name Scope Cardinality Type Binding Documentation
IN codeA 0..1 code

The "A" "A" code that is to be tested. If a code is provided, a system must be provided

IN codeB 0..1 code

The "B" "B" code that is to be tested. If a code is provided, a system must be provided

IN system type 0..1 uri

The code system in which subsumption testing is to be performed. This must be provided unless the operation is invoked on a code system instance

IN version type 0..1 string

The version of the code system, if one was provided in the source data

IN codingA 0..1 Coding

The "A" "A" Coding that is to be tested. The code system does not have to match the specified subsumption code system, but the relationships between the code systems must be well established

IN codingB 0..1 Coding

The "B" "B" Coding that is to be tested. The code system does not have to match the specified subsumption code system, but the relationships between the code systems must be well established

OUT outcome 1..1 code Concept Subsumption Outcome (Required)

The subsumption relationship between code/Coding "A" "A" and code/Coding "B". "B". There are 4 possible codes to be returned: equivalent, returned (equivalent, subsumes, subsumed-by, and not-subsumed. not-subsumed) as defined in the concept-subsumption-outcome value set. If the server is unable to determine the relationship between the codes/Codings, then it returns an error (i.e. response with an OperationOutcome) OperationOutcome.

 

 

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.