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).
The two concepts are equivalent (have the same properties).
0‑L
subsumes
Subsumes
ConceptSubsumptionOutcome
2019-11-01T09:29:23
Preferred: Subsumes
Coding/code "A" subsumes Coding/code "B" (e.g. B has all the properties A has, and some of it's own).
0‑L
subsumed-by
Subsumed-By
ConceptSubsumptionOutcome
2019-11-01T09:29:23
Preferred: Subsumed-By
Coding/code "A" is subsumed by Coding/code "B" (e.g. A has all the properties B has, and some of it's own).
0‑L
not-subsumed
Not-Subsumed
ConceptSubsumptionOutcome
2019-11-01T09:29:23
Preferred: Not-Subsumed
Coding/code "A" and Coding/code "B" are disjoint (e.g. each has propeties that the other doesn't have).
Legenda: Type L=leaf, S=specializable, A=abstract, D=deprecated. NullFlavor OTH (other) suggests text in originalText. HL7 V3: NullFlavors to appear in @nullFlavor attribute instead of @code.