FHIR Release 3 (STU)

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 of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3

Operation-codesystem-subsumes

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

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

Subsumption Testing

OPERATION: Subsumption Testing

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

UseNameCardinalityTypeBindingDocumentation
INcodeA0..1code

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

INcodeB0..1code

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

INsystem0..1uri

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

INversion0..1string

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

INcodingA0..1Coding

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

INcodingB0..1Coding

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

OUToutcome1..1code

The subsumption relationship between code/Coding "A" and code/Coding "B". There are 4 possible codes to be returned: equivalent, subsumes, subsumed-by, and not-subsumed. If the server is unable to determine the relationship between the codes/Codings, then it returns an error (i.e. an 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.