This page is part of the FHIR Specification (v4.2.0: R5 Preview #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
Vocabulary Work Group | Maturity Level: N/A | Standards Status: Informative |
Raw XML (canonical form + also see XML Format Specification)
Definition for Code System ConceptSubsumptionOutcome
<?xml version="1.0" encoding="UTF-8"?> <CodeSystem xmlns="http://hl7.org/fhir"> <id value="concept-subsumption-outcome"/> <meta> <lastUpdated value="2019-12-31T21:03:40.621+11:00"/> </meta> <text> <status value="generated"/> <div xmlns="http://www.w3.org/1999/xhtml"> <h2> ConceptSubsumptionOutcome</h2> <div> <p> 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).</p> </div> <p> This code system http://hl7.org/fhir/concept-subsumption-outcome defines the following codes:</p> <table class="codes"> <tr> <td style="white-space:nowrap"> <b> Code</b> </td> <td> <b> Display</b> </td> <td> <b> Definition</b> </td> </tr> <tr> <td style="white-space:nowrap">equivalent <a name="concept-subsumption-outcome-equivalent"> </a> </td> <td> Equivalent</td> <td> The two concepts are equivalent (have the same properties).</td> </tr> <tr> <td style="white-space:nowrap">subsumes <a name="concept-subsumption-outcome-subsumes"> </a> </td> <td> Subsumes</td> <td> Coding/code "A" subsumes Coding/code "B" (e.g. B has all the properties A has, and some of it's own).</td> </tr> <tr> <td style="white-space:nowrap">subsumed-by <a name="concept-subsumption-outcome-subsumed-by"> </a> </td> <td> Subsumed-By</td> <td> Coding/code "A" is subsumed by Coding/code "B" (e.g. A has all the properties B has, and some of it's own).</td> </tr> <tr> <td style="white-space:nowrap">not-subsumed <a name="concept-subsumption-outcome-not-subsumed"> </a> </td> <td> Not-Subsumed</td> <td> Coding/code "A" and Coding/code "B" are disjoint (e.g. each has propeties that the other doesn't have).</td> </tr> </table> </div> </text> <url value="http://hl7.org/fhir/concept-subsumption-outcome"/> <identifier> <system value="urn:ietf:rfc:3986"/> <value value="urn:oid:2.16.840.1.113883.4.642.1.1239"/> </identifier> <version value="4.2.0"/> <name value="ConceptSubsumptionOutcome"/> <title value="ConceptSubsumptionOutcome"/> <status value="draft"/> <experimental value="false"/> <date value="2019-12-31T21:03:40+11:00"/> <publisher value="HL7 (FHIR Project)"/> <contact> <telecom> <system value="url"/> <value value="http://hl7.org/fhir"/> </telecom> <telecom> <system value="email"/> <value value="fhir@lists.hl7.org"/> </telecom> </contact> <description value="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)."/> <caseSensitive value="true"/> <valueSet value="http://hl7.org/fhir/ValueSet/concept-subsumption-outcome"/> <content value="complete"/> <concept> <code value="equivalent"/> <display value="Equivalent"/> <definition value="The two concepts are equivalent (have the same properties)."/> </concept> <concept> <code value="subsumes"/> <display value="Subsumes"/> <definition value="Coding/code "A" subsumes Coding/code "B" (e.g. B has all the properties A has, and some of it's own)."/> </concept> <concept> <code value="subsumed-by"/> <display value="Subsumed-By"/> <definition value="Coding/code "A" is subsumed by Coding/code "B" (e.g. A has all the properties B has, and some of it's own)."/> </concept> <concept> <code value="not-subsumed"/> <display value="Not-Subsumed"/> <definition value="Coding/code "A" and Coding/code "B" are disjoint (e.g. each has propeties that the other doesn't have)."/> </concept> </CodeSystem>
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.