Release 4B

This page is part of the FHIR Specification (v4.3.0: R4B - STU). 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: R4B R4

Valueset-care-plan-activity-kind.xml

Vocabulary Work GroupMaturity Level: N/AStandards Status: Informative

Raw XML (canonical form + also see XML Format Specification)

Definition for Value SetCare Plan Activity Kind

<?xml version="1.0" encoding="UTF-8"?>

<ValueSet xmlns="http://hl7.org/fhir">
  <id value="care-plan-activity-kind"/> 
  <meta> 
    <lastUpdated value="2022-05-28T12:47:40.239+10:00"/> 
    <profile value="http://hl7.org/fhir/StructureDefinition/shareablevalueset"/> 
  </meta> 
  <text> 
    <status value="extensions"/> 
    <div xmlns="http://www.w3.org/1999/xhtml">
      <ul> 
        <li> Include these codes as defined in 
          <a href="codesystem-resource-types.html">
            <code> http://hl7.org/fhir/resource-types</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-resource-types.html#resource-types-Appointment">Appointment</a> 
              </td> 
              <td> Appointment</td> 
              <td> A booking of a healthcare event among patient(s), practitioner(s), related person(s) and/or
                 device(s) for a specific date/time. This may result in one or more Encounter(s).</td> 
            </tr> 
            <tr> 
              <td> 
                <a href="codesystem-resource-types.html#resource-types-CommunicationRequest">CommunicationRequest</a> 
              </td> 
              <td> CommunicationRequest</td> 
              <td> A request to convey information; e.g. the CDS system proposes that an alert be sent to
                 a responsible provider, the CDS system proposes that the public health agency be notified
                 about a reportable condition.</td> 
            </tr> 
            <tr> 
              <td> 
                <a href="codesystem-resource-types.html#resource-types-DeviceRequest">DeviceRequest</a> 
              </td> 
              <td> DeviceRequest</td> 
              <td> Represents a request for a patient to employ a medical device. The device may be an implantable
                 device, or an external assistive device, such as a walker.</td> 
            </tr> 
            <tr> 
              <td> 
                <a href="codesystem-resource-types.html#resource-types-MedicationRequest">MedicationRequest</a> 
              </td> 
              <td> MedicationRequest</td> 
              <td> An order or request for both supply of the medication and the instructions for administration
                 of the medication to a patient. The resource is called &quot;MedicationRequest&quot; rather
                 than &quot;MedicationPrescription&quot; or &quot;MedicationOrder&quot; to generalize the
                 use across inpatient and outpatient settings, including care plans, etc., and to harmonize
                 with workflow patterns.</td> 
            </tr> 
            <tr> 
              <td> 
                <a href="codesystem-resource-types.html#resource-types-NutritionOrder">NutritionOrder</a> 
              </td> 
              <td> NutritionOrder</td> 
              <td> A request to supply a diet, formula feeding (enteral) or oral nutritional supplement to
                 a patient/resident.</td> 
            </tr> 
            <tr> 
              <td> 
                <a href="codesystem-resource-types.html#resource-types-Task">Task</a> 
              </td> 
              <td> Task</td> 
              <td> A task to be performed.</td> 
            </tr> 
            <tr> 
              <td> 
                <a href="codesystem-resource-types.html#resource-types-ServiceRequest">ServiceRequest</a> 
              </td> 
              <td> ServiceRequest</td> 
              <td> A record of a request for service such as diagnostic investigations, treatments, or operations
                 to be performed.</td> 
            </tr> 
            <tr> 
              <td> 
                <a href="codesystem-resource-types.html#resource-types-VisionPrescription">VisionPrescription</a> 
              </td> 
              <td> VisionPrescription</td> 
              <td> An authorization for the provision of glasses and/or contact lenses to a patient.</td> 
            </tr> 
          </table> 
        </li> 
      </ul> 
    </div> 
  </text> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
    <valueCode value="pc"/> 
  </extension> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status">
    <valueCode value="trial-use"/> 
  </extension> 
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
    <valueInteger value="2"/> 
  </extension> 
  <url value="http://hl7.org/fhir/ValueSet/care-plan-activity-kind"/> 
  <identifier> 
    <system value="urn:ietf:rfc:3986"/> 
    <value value="urn:oid:2.16.840.1.113883.4.642.3.145"/> 
  </identifier> 
  <version value="4.3.0"/> 
  <name value="CarePlanActivityKind"/> 
  <title value="Care Plan Activity Kind"/> 
  <status value="draft"/> 
  <experimental value="false"/> 
  <publisher value="HL7 International - Patient Care WG"/> 
  <contact> 
    <telecom> 
      <system value="url"/> 
      <value value="http://www.hl7.org/Special/committees/patientcare/"/> 
    </telecom> 
  </contact> 
  <description value="Resource types defined as part of FHIR that can be represented as in-line definitions
   of a care plan activity."/> 
  <compose> 
    <include> 
      <system value="http://hl7.org/fhir/resource-types"/> 
      <concept> 
        <code value="Appointment"/> 
      </concept> 
      <concept> 
        <code value="CommunicationRequest"/> 
      </concept> 
      <concept> 
        <code value="DeviceRequest"/> 
      </concept> 
      <concept> 
        <code value="MedicationRequest"/> 
      </concept> 
      <concept> 
        <code value="NutritionOrder"/> 
      </concept> 
      <concept> 
        <code value="Task"/> 
      </concept> 
      <concept> 
        <code value="ServiceRequest"/> 
      </concept> 
      <concept> 
        <code value="VisionPrescription"/> 
      </concept> 
    </include> 
  </compose> 
</ValueSet> 

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.