HL7 Terminology (THO)
3.1.5 - Continuous Process Integration ( ci build ) World

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

: x_ActOrderableOrBillable - XML Representation

Active as of 2014-03-26

Raw xml | Download



<ValueSet xmlns="http://hl7.org/fhir">
  <id value="v3-xActOrderableOrBillable"/>
  <language value="en"/>
  <text>
    <status value="extensions"/>
    <div xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"><p>This value set includes codes based on the following rules:</p><ul><li>Include these codes as defined in <a href="CodeSystem-v3-ActClass.html"><code>http://terminology.hl7.org/CodeSystem/v3-ActClass</code></a><table class="none"><tr><td style="white-space:nowrap"><b>Code</b></td><td><b>Display</b></td><td><b>Definition</b></td></tr><tr><td><a href="CodeSystem-v3-ActClass.html#v3-ActClass-ACCM">ACCM</a></td><td>accommodation</td><td>An accommodation is a service provided for a Person or other LivingSubject in which a place is provided for the subject to reside for a period of time. Commonly used to track the provision of ward, private and semi-private accommodations for a patient.</td></tr><tr><td><a href="CodeSystem-v3-ActClass.html#v3-ActClass-ENC">ENC</a></td><td>encounter</td><td>An interaction between a patient and healthcare participant(s) for the purpose of providing patient service(s) or assessing the health status of a patient. For example, outpatient visit to multiple departments, home health support (including physical therapy), inpatient hospital stay, emergency room visit, field visit (e.g., traffic accident), office visit, occupational therapy, telephone call.</td></tr><tr><td><a href="CodeSystem-v3-ActClass.html#v3-ActClass-PCPR">PCPR</a></td><td>care provision</td><td>An **Act** that of taking on whole or partial responsibility for, or attention to, safety and well-being of a subject of care.<br/><br/>*Discussion:* A **care provision** event may exist without any other care actions taking place. For example, when a patient is assigned to the care of a particular health professional.<br/><br/>In **request** (RQO) mood **care provision** communicates a referral, which is a request:<br/><br/> *  from one party (linked as a **participant** of type **author** (AUT)),<br/> *  to another party (linked as a **participant** of type **performer** (PRF),<br/> *  to take responsibility for a scope specified by the code attribute,<br/> *  for an entity (linked as a **participant** of type **subject** (SBJ)).<br/><br/>The scope of the care for which responsibility is taken is identified by *code* attribute.<br/><br/>In **event** (EVN) mood **care provision** indicates the effective time interval of a specified scope of responsibility by a **performer** (PRF) or set of **performers** (PRF) for a **subject** (SBJ).<br/><br/>*Examples:*<br/><br/>1.  Referral from GP to a specialist.<br/>2.  Assignment of a patient or group of patients to the case list of a health professional.<br/>3.  Assignment of inpatients to the care of particular nurses for a working shift.</td></tr><tr><td><a href="CodeSystem-v3-ActClass.html#v3-ActClass-SBADM">SBADM</a></td><td>substance administration</td><td>The act of introducing or otherwise applying a substance to the subject.<br/><br/>*Discussion:* The effect of the substance is typically established on a biochemical basis, however, that is not a requirement. For example, radiotherapy can largely be described in the same way, especially if it is a systemic therapy such as radio-iodine. This class also includes the application of chemical treatments to an area.<br/><br/>*Examples:* Chemotherapy protocol; Drug prescription; Vaccination record</td></tr><tr><td><a href="CodeSystem-v3-ActClass.html#v3-ActClass-TRNS">TRNS</a></td><td>transportation</td><td>Transportation is the moving of a payload (people or material) from a location of origin to a destination location. Thus, any transport service has the three target instances of type payload, origin, and destination, besides the targets that are generally used for any service (i.e., performer, device, etc.)</td></tr></table></li><li>Import all the codes that are contained in <a href="ValueSet-v3-ActClassObservation.html">http://terminology.hl7.org/ValueSet/v3-ActClassObservation</a></li><li>Import all the codes that are contained in <a href="ValueSet-v3-ActClassProcedure.html">http://terminology.hl7.org/ValueSet/v3-ActClassProcedure</a></li></ul></div>
  </text>
  <url value="http://terminology.hl7.org/ValueSet/v3-xActOrderableOrBillable"/>
  <identifier>
    <system value="urn:ietf:rfc:3986"/>
    <value value="urn:oid:2.16.840.1.113883.1.11.19822"/>
  </identifier>
  <version value="2.0.0"/>
  <name value="XActOrderableOrBillable"/>
  <title value="x_ActOrderableOrBillable"/>
  <status value="active"/>
  <date value="2014-03-26"/>
  <compose>
    <include>
      <system value="http://terminology.hl7.org/CodeSystem/v3-ActClass"/>
      <concept>
        <code value="ACCM"/>
      </concept>
      <concept>
        <code value="ENC"/>
      </concept>
      <concept>
        <code value="PCPR"/>
      </concept>
      <concept>
        <code value="SBADM"/>
      </concept>
      <concept>
        <code value="TRNS"/>
      </concept>
    </include>
    <include>
      <valueSet
                value="http://terminology.hl7.org/ValueSet/v3-ActClassObservation"/>
    </include>
    <include>
      <valueSet value="http://terminology.hl7.org/ValueSet/v3-ActClassProcedure"/>
    </include>
  </compose>
</ValueSet>