STU3 Candidate

This page is part of the FHIR Specification (v1.8.0: STU 3 Draft). 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 R3

Codesystem-plan-definition-type.xml

Raw XML (canonical form)

Definition for Code System PlanDefinitionType

<CodeSystem xmlns="http://hl7.org/fhir">
  <id value="plan-definition-type"/>
  <meta>
    <lastUpdated value="2016-12-06T12:22:34.981+11:00"/>
  </meta>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml">
      <h2>PlanDefinitionType</h2>
      <div>
        <p>The type of PlanDefinition</p>

      </div>
      <p>This code system http://hl7.org/fhir/plan-definition-type 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>order-set
            <a name="plan-definition-type-order-set"> </a>
          </td>
          <td>Order Set</td>
          <td>A pre-defined and approved group of orders related to a particular clinical condition
             (e.g. hypertension treatment and monitoring) or stage of care (e.g. hospital admission
             to Coronary Care Unit). An order set is used as a checklist for the clinician when managing
             a patient with a specific condition. It is a structured collection of orders relevant
             to that condition and presented to the clinician in a computerized provider order entry
             (CPOE) system</td>
        </tr>
        <tr>
          <td>protocol
            <a name="plan-definition-type-protocol"> </a>
          </td>
          <td>Protocol</td>
          <td>A set of activities that can be peformed that have relationships in terms of order, pre-conditions
             etc</td>
        </tr>
        <tr>
          <td>eca-rule
            <a name="plan-definition-type-eca-rule"> </a>
          </td>
          <td>ECA Rule</td>
          <td>A decision support rule of the form [on Event] if Condition then Action. It is intended
             to be a shareable, computable definition of a actions that should be taken whenever some
             condition is met in response to a particular event or events</td>
        </tr>
      </table>
    </div>
  </text>
  <url value="http://hl7.org/fhir/plan-definition-type"/>
  <identifier>
    <system value="urn:ietf:rfc:3986"/>
    <value value="urn:oid:2.16.840.1.113883.4.642.1.987"/>
  </identifier>
  <version value="1.8.0"/>
  <name value="PlanDefinitionType"/>
  <status value="draft"/>
  <experimental value="false"/>
  <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>
  <date value="2016-12-06T12:22:34+11:00"/>
  <description value="The type of PlanDefinition"/>
  <caseSensitive value="true"/>
  <valueSet value="http://hl7.org/fhir/ValueSet/plan-definition-type"/>
  <content value="complete"/>
  <concept>
    <code value="order-set"/>
    <display value="Order Set"/>
    <definition value="A pre-defined and approved group of orders related to a particular clinical condition
     (e.g. hypertension treatment and monitoring) or stage of care (e.g. hospital admission
     to Coronary Care Unit). An order set is used as a checklist for the clinician when managing
     a patient with a specific condition. It is a structured collection of orders relevant
     to that condition and presented to the clinician in a computerized provider order entry
     (CPOE) system"/>
  </concept>
  <concept>
    <code value="protocol"/>
    <display value="Protocol"/>
    <definition value="A set of activities that can be peformed that have relationships in terms of order, pre-conditions
     etc"/>
  </concept>
  <concept>
    <code value="eca-rule"/>
    <display value="ECA Rule"/>
    <definition value="A decision support rule of the form [on Event] if Condition then Action. It is intended
     to be a shareable, computable definition of a actions that should be taken whenever some
     condition is met in response to a particular event or events"/>
  </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.