Extensions for Using Data Elements from FHIR STU3 in FHIR R4B
0.1.0 - STU International flag

Extensions for Using Data Elements from FHIR STU3 in FHIR R4B - Downloaded Version null See the Directory of published versions

: PlanDefinitionType - XML Representation

Page standards status: Trial-use Maturity Level: 2

Raw xml | Download


<CodeSystem xmlns="http://hl7.org/fhir">
  <id value="plan-definition-type"/>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: CodeSystem plan-definition-type</b></p><a name="plan-definition-type"> </a><a name="hcplan-definition-type"> </a><p>This case-sensitive code system <code>http://hl7.org/fhir/plan-definition-type</code> defines the following codes:</p><table class="codes"><tr><td style="white-space:nowrap"><b>Code</b></td><td><b>Display</b></td><td><b>Definition</b></td></tr><tr><td style="white-space:nowrap">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 style="white-space:nowrap">protocol<a name="plan-definition-type-protocol"> </a></td><td>Protocol</td><td>A set of activities that can be performed that have relationships in terms of order, pre-conditions, etc.</td></tr><tr><td style="white-space:nowrap">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 actions that should be taken whenever some condition is met in response to a particular event or events</td></tr></table></div>
  </text>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-ballot-status">
    <valueString value="Informative"/>
  </extension>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
    <valueInteger value="2"/>
  </extension>
  <extension url="http://hl7.org/fhir/StructureDefinition/package-source">
    <extension url="packageId">
      <valueId value="hl7.fhir.uv.xver-r3.r4b"/>
    </extension>
    <extension url="version">
      <valueString value="0.1.0"/>
    </extension>
    <extension url="uri">
      <valueUri
                value="http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r3.r4b"/>
    </extension>
  </extension>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
    <valueCode value="cds"/>
  </extension>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status">
    <valueCode value="trial-use">
      <extension
                 url="http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom">
        <valueCanonical
                        value="http://hl7.org/fhir/uv/xver/ImplementationGuide/hl7.fhir.uv.xver-r3.r4b"/>
      </extension>
    </valueCode>
  </extension>
  <url value="http://hl7.org/fhir/plan-definition-type"/>
  <version value="3.0.2"/>
  <name value="PlanDefinitionType"/>
  <status value="draft"/>
  <experimental value="false"/>
  <date value="2019-10-23T19:53:00-05:00"/>
  <publisher value="Clinical Decision Support"/>
  <contact>
    <name value="Clinical Decision Support"/>
    <telecom>
      <system value="url"/>
      <value value="http://www.hl7.org/Special/committees/dss"/>
    </telecom>
  </contact>
  <description value="The type of PlanDefinition"/>
  <jurisdiction>
    <coding>
      <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
      <code value="001"/>
      <display value="World"/>
    </coding>
  </jurisdiction>
  <caseSensitive value="true"/>
  <valueSet value="http://hl7.org/fhir/ValueSet/plan-definition-type|4.3.0"/>
  <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 performed 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 actions that should be taken whenever some condition is met in response to a particular event or events"/>
  </concept>
</CodeSystem>