FHIR 5.0.0 © HL7.org  |  FHIRsmith 0.8.5  |  Server Home  |  TX Home  |  Capability Statement  |  Terminology Capabilities  |  Operations  |  Problems  |   

TX: CodeSystem plan-definition-type

<?xml version="1.0" encoding="UTF-8"?>
<CodeSystem xmlns="http://hl7.org/fhir">
  <id value="plan-definition-type"/>
  <meta>
    <lastUpdated value="2024-04-24T00:00:00+00:00"/>
  </meta>
  <language value="en"/>
  <text>
    <status value="generated"/>
    <div value="&lt;div xmlns=&quot;http://www.w3.org/1999/xhtml&quot; xml:lang=&quot;en&quot; lang=&quot;en&quot;&gt;&lt;p class=&quot;res-header-id&quot;&gt;&lt;b&gt;Generated Narrative: CodeSystem plan-definition-type&lt;/b&gt;&lt;/p&gt;&lt;a name=&quot;plan-definition-type&quot;&gt; &lt;/a&gt;&lt;a name=&quot;hcplan-definition-type&quot;&gt; &lt;/a&gt;&lt;div style=&quot;display: inline-block; background-color: #d9e0e7; padding: 6px; margin: 4px; border: 1px solid #8da1b4; border-radius: 5px; line-height: 60%&quot;&gt;&lt;p style=&quot;margin-bottom: 0px&quot;&gt;Last updated: 2024-04-24 00:00:00+0000; Language: en&lt;/p&gt;&lt;/div&gt;&lt;p&gt;This case-sensitive code system &lt;code&gt;http://terminology.hl7.org/CodeSystem/plan-definition-type&lt;/code&gt; defines the following codes:&lt;/p&gt;&lt;table class=&quot;codes&quot;&gt;&lt;tr&gt;&lt;td style=&quot;white-space:nowrap&quot;&gt;&lt;b&gt;Code&lt;/b&gt;&lt;/td&gt;&lt;td&gt;&lt;b&gt;Display&lt;/b&gt;&lt;/td&gt;&lt;td&gt;&lt;b&gt;Definition&lt;/b&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td style=&quot;white-space:nowrap&quot;&gt;order-set&lt;a name=&quot;plan-definition-type-order-set&quot;&gt; &lt;/a&gt;&lt;/td&gt;&lt;td&gt;Order Set&lt;/td&gt;&lt;td&gt;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.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td style=&quot;white-space:nowrap&quot;&gt;protocol&lt;a name=&quot;plan-definition-type-protocol&quot;&gt; &lt;/a&gt;&lt;/td&gt;&lt;td&gt;Protocol&lt;/td&gt;&lt;td&gt;Defines a desired/typical sequence of activities including preconditions, triggers and temporal relationships.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td style=&quot;white-space:nowrap&quot;&gt;clinical-protocol&lt;a name=&quot;plan-definition-type-clinical-protocol&quot;&gt; &lt;/a&gt;&lt;/td&gt;&lt;td&gt;Clinical Protocol&lt;/td&gt;&lt;td&gt;Defines a desired/typical sequence of clinical activities including preconditions, triggers and temporal relationships.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td style=&quot;white-space:nowrap&quot;&gt;eca-rule&lt;a name=&quot;plan-definition-type-eca-rule&quot;&gt; &lt;/a&gt;&lt;/td&gt;&lt;td&gt;ECA Rule&lt;/td&gt;&lt;td&gt;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.&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td style=&quot;white-space:nowrap&quot;&gt;workflow-definition&lt;a name=&quot;plan-definition-type-workflow-definition&quot;&gt; &lt;/a&gt;&lt;/td&gt;&lt;td&gt;Workflow Definition&lt;/td&gt;&lt;td&gt;Defines the steps for a group of one or more systems in an event flow process along with the step constraints, sequence, pre-conditions and decision points to complete a particular objective.&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;&lt;/div&gt;"/>
  </text>
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
    <valueCode value="cds"/>
  </extension>
  <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
    <valueInteger value="2"/>
  </extension>
  <url value="http://terminology.hl7.org/CodeSystem/plan-definition-type"/>
  <identifier>
    <system value="urn:ietf:rfc:3986"/>
    <value value="urn:oid:2.16.840.1.113883.4.642.1.1245"/>
  </identifier>
  <version value="2.0.0"/>
  <name value="PlanDefinitionType"/>
  <title value="PlanDefinitionType"/>
  <status value="active"/>
  <experimental value="false"/>
  <date value="2024-04-24T00:00:00+00:00"/>
  <publisher value="Health Level Seven International"/>
  <contact>
    <telecom>
      <system value="url"/>
      <value value="http://hl7.org"/>
    </telecom>
    <telecom>
      <system value="email"/>
      <value value="hq@HL7.org"/>
    </telecom>
  </contact>
  <description value="The type of PlanDefinition."/>
  <copyright value="This material derives from the HL7 Terminology (THO). THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license"/>
  <caseSensitive value="true"/>
  <valueSet value="http://terminology.hl7.org/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="Defines a desired/typical sequence of activities including preconditions, triggers and temporal relationships."/>
  </concept>
  <concept>
    <code value="clinical-protocol"/>
    <display value="Clinical Protocol"/>
    <definition value="Defines a desired/typical sequence of clinical activities including preconditions, triggers and temporal relationships."/>
  </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>
  <concept>
    <code value="workflow-definition"/>
    <display value="Workflow Definition"/>
    <definition value="Defines the steps for a group of one or more systems in an event flow process along with the step constraints, sequence, pre-conditions and decision points to complete a particular objective."/>
  </concept>
</CodeSystem>