HL7 Terminology (THO)
6.1.0 - Continuous Process Integration (ci build) International flag

HL7 Terminology (THO), published by HL7 International - Vocabulary Work Group. This guide is not an authorized publication; it is the continuous build for version 6.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/UTG/ and changes regularly. See the Directory of published versions

: v2CS-relationshipType - XML Representation

Active as of 2019-12-01

Raw xml | Download


<CodeSystem xmlns="http://hl7.org/fhir">
  <id value="v2-0948"/>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: CodeSystem v2-0948</b></p><a name="v2-0948"> </a><a name="hcv2-0948"> </a><a name="v2-0948-en-US"> </a><p><b>Properties</b></p><p><b>This code system defines the following properties for its concepts</b></p><table class="grid"><tr><td><b>Name</b></td><td><b>Code</b></td><td><b>URI</b></td><td><b>Type</b></td><td><b>Description</b></td></tr><tr><td>status</td><td>status</td><td>http://terminology.hl7.org/CodeSystem/utg-concept-properties#status</td><td>code</td><td>Status of the concept</td></tr><tr><td>deprecated</td><td>deprecated</td><td>http://terminology.hl7.org/CodeSystem/utg-concept-properties#v2-table-deprecated</td><td>code</td><td>Version of HL7 in which the code was deprecated</td></tr><tr><td>V2 Concept Comment</td><td>v2-concComment</td><td>http://terminology.hl7.org/CodeSystem/utg-concept-properties#v2-concComment</td><td>string</td><td>V2 Concept Comment</td></tr></table><p><b>Concepts</b></p><p>This case-sensitive code system <code>http://terminology.hl7.org/CodeSystem/v2-0948</code> defines the following codes in a Is-A hierarchy:</p><table class="codes"><tr><td style="white-space:nowrap"><b>Code</b></td><td><b>Display</b></td><td><b>Definition</b></td><td><b>V2 Concept Comment</b></td></tr><tr><td style="white-space:nowrap">CAUS<a name="v2-0948-CAUS"> </a></td><td>Causes/caused</td><td>Source universal service identifier causes/caused the outcome(s) on the target</td><td>Example: a procedure caused  complication(s)</td></tr><tr><td style="white-space:nowrap">COMP<a name="v2-0948-COMP"> </a></td><td>Component of</td><td>Target universal service identifier is a component of source universal identifier</td><td>Example: one care plan activity (target) is a component of another care plan activity (source)</td></tr><tr><td style="white-space:nowrap">CONCR<a name="v2-0948-CONCR"> </a></td><td>Concurrently</td><td>Source and target universal service identifier should start concurrently</td><td>Example: two care plan activities should start concurrently</td></tr><tr><td style="white-space:nowrap">EVID<a name="v2-0948-EVID"> </a></td><td>Evidence</td><td>Source universal service identifier provides evidence for target universal service identifier</td><td>Example: observation result provides evidence for certain care plan activity or treatment action</td></tr><tr><td style="white-space:nowrap">INTF<a name="v2-0948-INTF"> </a></td><td>Interferes / interfered</td><td>Source universal service identifier interferes / interfered with fulfilment of target universal service identifier</td><td>Example: patient financial or physical constraints interferes / interfered with fulfilment of goal</td></tr><tr><td style="white-space:nowrap">LIMIT<a name="v2-0948-LIMIT"> </a></td><td>Limits/limited</td><td>Source universal service identifier limits/limited the fulfillment of target universal service identifier</td><td>Example: patient condition limits the extend that planned treatment can be implemented</td></tr><tr><td style="white-space:nowrap">SUCCD<a name="v2-0948-SUCCD"> </a></td><td>Succeeds</td><td>Target universal service identifier should succeed (starts after end of) source universal service identifier</td><td>Example: one care plan activity (target) should start after completion of another (source)</td></tr><tr><td style="white-space:nowrap">SVTGT<a name="v2-0948-SVTGT"> </a></td><td>Service target</td><td>Target universal service identifier is the object of the service identified by the source universal service identifier</td><td>Example: An order requests clarification or interpretation of a previous clinical laboratory test result</td></tr><tr><td style="white-space:nowrap">TRIG<a name="v2-0948-TRIG"> </a></td><td>Triggers/triggered</td><td>Source universal service identifier triggers action of target universal service identifier</td><td>Example: a bleeding complication triggers the review and change in anti-coagulant dosage</td></tr></table></div>
  </text>
  <url value="http://terminology.hl7.org/CodeSystem/v2-0948"/>
  <identifier>
    <system value="urn:ietf:rfc:3986"/>
    <value value="urn:oid:2.16.840.1.113883.18.448"/>
  </identifier>
  <version value="2.0.0"/>
  <name value="V2CSRelationshipType"/>
  <title value="v2CS-relationshipType"/>
  <status value="active"/>
  <experimental value="false"/>
  <date value="2019-12-01"/>
  <publisher value="Health Level Seven International"/>
  <contact>
    <telecom>
      <system value="url"/>
      <value value="http://hl7.org"/>
    </telecom>
    <telecom>
      <system value="email"/>
      <value value="hq@HL7.org"/>
    </telecom>
  </contact>
  <description
               value="HL7-defined code system of concepts that identify the type of relationship identified by Relationship Instance Identifier (REL-3) that is established between the Source Information Instance (REL-4)  and the Target Information Instance (REL-5)."/>
  <purpose
           value="Underlying Master Code System for V2 table 0948 (Relationship Type)"/>
  <copyright
             value="This material derives from the HL7 Terminology (THO). THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html"/>
  <caseSensitive value="true"/>
  <valueSet value="http://terminology.hl7.org/ValueSet/v2-0948"/>
  <hierarchyMeaning value="is-a"/>
  <compositional value="false"/>
  <versionNeeded value="false"/>
  <content value="complete"/>
  <property>
    <code value="status"/>
    <uri
         value="http://terminology.hl7.org/CodeSystem/utg-concept-properties#status"/>
    <description value="Status of the concept"/>
    <type value="code"/>
  </property>
  <property>
    <code value="deprecated"/>
    <uri
         value="http://terminology.hl7.org/CodeSystem/utg-concept-properties#v2-table-deprecated"/>
    <description value="Version of HL7 in which the code was deprecated"/>
    <type value="code"/>
  </property>
  <property>
    <code value="v2-concComment"/>
    <uri
         value="http://terminology.hl7.org/CodeSystem/utg-concept-properties#v2-concComment"/>
    <description value="V2 Concept Comment"/>
    <type value="string"/>
  </property>
  <concept id="6760">
    <code value="CAUS"/>
    <display value="Causes/caused"/>
    <definition
                value="Source universal service identifier causes/caused the outcome(s) on the target"/>
    <property>
      <code value="v2-concComment"/>
      <valueString value="Example: a procedure caused  complication(s)"/>
    </property>
    <property>
      <code value="status"/>
      <valueCode value="N"/>
    </property>
  </concept>
  <concept id="6761">
    <code value="COMP"/>
    <display value="Component of"/>
    <definition
                value="Target universal service identifier is a component of source universal identifier"/>
    <property>
      <code value="v2-concComment"/>
      <valueString
                   value="Example: one care plan activity (target) is a component of another care plan activity (source)"/>
    </property>
    <property>
      <code value="status"/>
      <valueCode value="N"/>
    </property>
  </concept>
  <concept id="6762">
    <code value="CONCR"/>
    <display value="Concurrently"/>
    <definition
                value="Source and target universal service identifier should start concurrently"/>
    <property>
      <code value="v2-concComment"/>
      <valueString
                   value="Example: two care plan activities should start concurrently"/>
    </property>
    <property>
      <code value="status"/>
      <valueCode value="N"/>
    </property>
  </concept>
  <concept id="6763">
    <code value="EVID"/>
    <display value="Evidence"/>
    <definition
                value="Source universal service identifier provides evidence for target universal service identifier"/>
    <property>
      <code value="v2-concComment"/>
      <valueString
                   value="Example: observation result provides evidence for certain care plan activity or treatment action"/>
    </property>
    <property>
      <code value="status"/>
      <valueCode value="N"/>
    </property>
  </concept>
  <concept id="6764">
    <code value="INTF"/>
    <display value="Interferes / interfered"/>
    <definition
                value="Source universal service identifier interferes / interfered with fulfilment of target universal service identifier"/>
    <property>
      <code value="v2-concComment"/>
      <valueString
                   value="Example: patient financial or physical constraints interferes / interfered with fulfilment of goal"/>
    </property>
    <property>
      <code value="status"/>
      <valueCode value="N"/>
    </property>
  </concept>
  <concept id="6765">
    <code value="LIMIT"/>
    <display value="Limits/limited"/>
    <definition
                value="Source universal service identifier limits/limited the fulfillment of target universal service identifier"/>
    <property>
      <code value="v2-concComment"/>
      <valueString
                   value="Example: patient condition limits the extend that planned treatment can be implemented"/>
    </property>
    <property>
      <code value="status"/>
      <valueCode value="N"/>
    </property>
  </concept>
  <concept id="6766">
    <code value="SUCCD"/>
    <display value="Succeeds"/>
    <definition
                value="Target universal service identifier should succeed (starts after end of) source universal service identifier"/>
    <property>
      <code value="v2-concComment"/>
      <valueString
                   value="Example: one care plan activity (target) should start after completion of another (source)"/>
    </property>
    <property>
      <code value="status"/>
      <valueCode value="N"/>
    </property>
  </concept>
  <concept id="6767">
    <code value="SVTGT"/>
    <display value="Service target"/>
    <definition
                value="Target universal service identifier is the object of the service identified by the source universal service identifier"/>
    <property>
      <code value="v2-concComment"/>
      <valueString
                   value="Example: An order requests clarification or interpretation of a previous clinical laboratory test result"/>
    </property>
    <property>
      <code value="status"/>
      <valueCode value="N"/>
    </property>
  </concept>
  <concept id="6768">
    <code value="TRIG"/>
    <display value="Triggers/triggered"/>
    <definition
                value="Source universal service identifier triggers action of target universal service identifier"/>
    <property>
      <code value="v2-concComment"/>
      <valueString
                   value="Example: a bleeding complication triggers the review and change in anti-coagulant dosage"/>
    </property>
    <property>
      <code value="status"/>
      <valueCode value="N"/>
    </property>
  </concept>
</CodeSystem>