STU 3 Candidate

This page is part of the FHIR Specification (v1.4.0: STU 3 Ballot 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

Codesystem-encounter-class.xml

Raw XML (canonical form)

Definition for Code System EncounterClass

<CodeSystem xmlns="http://hl7.org/fhir">
  <id value="encounter-class"/>
  <meta>
    <lastUpdated value="2016-03-31T08:01:25.570+11:00"/>
  </meta>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml">
      <h2>EncounterClass</h2>
      <p>Classification of the encounter</p>
      <p>This code system http://hl7.org/fhir/encounter-class defines the following codes:</p>
      <table class="codes">
        <tr>
          <td>
            <b>Code</b>
          </td>
          <td>
            <b>Display</b>
          </td>
          <td>
            <b>Definition</b>
          </td>
        </tr>
        <tr>
          <td>inpatient
            <a name="inpatient"> </a>
          </td>
          <td>Inpatient</td>
          <td>An encounter during which the patient is hospitalized and stays overnight.</td>
        </tr>
        <tr>
          <td>outpatient
            <a name="outpatient"> </a>
          </td>
          <td>Outpatient</td>
          <td>An encounter during which the patient is not hospitalized overnight.</td>
        </tr>
        <tr>
          <td>ambulatory
            <a name="ambulatory"> </a>
          </td>
          <td>Ambulatory</td>
          <td>An encounter where the patient visits the practitioner in his/her office, e.g. a G.P.
             visit.</td>
        </tr>
        <tr>
          <td>emergency
            <a name="emergency"> </a>
          </td>
          <td>Emergency</td>
          <td>An encounter in the Emergency Care Department.</td>
        </tr>
        <tr>
          <td>home
            <a name="home"> </a>
          </td>
          <td>Home</td>
          <td>An encounter where the practitioner visits the patient at his/her home.</td>
        </tr>
        <tr>
          <td>field
            <a name="field"> </a>
          </td>
          <td>Field</td>
          <td>An encounter taking place outside the regular environment for giving care.</td>
        </tr>
        <tr>
          <td>daytime
            <a name="daytime"> </a>
          </td>
          <td>Daytime</td>
          <td>An encounter where the patient needs more prolonged treatment or investigations than outpatients,
             but who do not need to stay in the hospital overnight.</td>
        </tr>
        <tr>
          <td>virtual
            <a name="virtual"> </a>
          </td>
          <td>Virtual</td>
          <td>An encounter that takes place where the patient and practitioner do not physically meet
             but use electronic means for contact.</td>
        </tr>
        <tr>
          <td>other
            <a name="other"> </a>
          </td>
          <td>Other</td>
          <td>Any other encounter type that is not described by one of the other values. Where this
             is used it is expected that an implementer will include an extension value to define what
             the actual other type is.</td>
        </tr>
      </table>
    </div>
  </text>
  <extension url="http://hl7.org/fhir/StructureDefinition/valueset-oid">
    <valueUri value="urn:oid:2.16.840.1.113883.4.642.1.138"/>
  </extension>
  <url value="http://hl7.org/fhir/encounter-class"/>
  <version value="1.4.0"/>
  <name value="EncounterClass"/>
  <status value="draft"/>
  <experimental value="false"/>
  <publisher value="HL7 (FHIR Project)"/>
  <contact>
    <telecom>
      <system value="other"/>
      <value value="http://hl7.org/fhir"/>
    </telecom>
    <telecom>
      <system value="email"/>
      <value value="fhir@lists.hl7.org"/>
    </telecom>
  </contact>
  <date value="2016-03-31T08:01:25+11:00"/>
  <description value="Classification of the encounter"/>
  <caseSensitive value="true"/>
  <valueSet value="http://hl7.org/fhir/ValueSet/encounter-class"/>
  <content value="complete"/>
  <concept>
    <code value="inpatient"/>
    <display value="Inpatient"/>
    <definition value="An encounter during which the patient is hospitalized and stays overnight."/>
  </concept>
  <concept>
    <code value="outpatient"/>
    <display value="Outpatient"/>
    <definition value="An encounter during which the patient is not hospitalized overnight."/>
  </concept>
  <concept>
    <code value="ambulatory"/>
    <display value="Ambulatory"/>
    <definition value="An encounter where the patient visits the practitioner in his/her office, e.g. a G.P.
     visit."/>
  </concept>
  <concept>
    <code value="emergency"/>
    <display value="Emergency"/>
    <definition value="An encounter in the Emergency Care Department."/>
  </concept>
  <concept>
    <code value="home"/>
    <display value="Home"/>
    <definition value="An encounter where the practitioner visits the patient at his/her home."/>
  </concept>
  <concept>
    <code value="field"/>
    <display value="Field"/>
    <definition value="An encounter taking place outside the regular environment for giving care."/>
  </concept>
  <concept>
    <code value="daytime"/>
    <display value="Daytime"/>
    <definition value="An encounter where the patient needs more prolonged treatment or investigations than outpatients,
     but who do not need to stay in the hospital overnight."/>
  </concept>
  <concept>
    <code value="virtual"/>
    <display value="Virtual"/>
    <definition value="An encounter that takes place where the patient and practitioner do not physically meet
     but use electronic means for contact."/>
  </concept>
  <concept>
    <code value="other"/>
    <display value="Other"/>
    <definition value="Any other encounter type that is not described by one of the other values. Where this
     is used it is expected that an implementer will include an extension value to define what
     the actual other type is."/>
  </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.