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

• Narrative Content
• XML
• JSON
• TTL

: PlanDefinitionType - XML Representation

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>This code system http://terminology.hl7.org/CodeSystem/plan-definition-type 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">clinical-protocol
            
            
                  <a name="plan-definition-type-clinical-protocol"> </a>
          
          
                </td>
          
          
                <td>Clinical Protocol</td>
          
          
                <td>Defines a desired/typical sequence of clinical activities including preconditions, triggers and temporal relationships.</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>
        
        
              <tr>
          
          
                <td style="white-space:nowrap">workflow-definition
            
            
                  <a name="plan-definition-type-workflow-definition"> </a>
          
          
                </td>
          
          
                <td>Workflow Definition</td>
          
          
                <td>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.</td>
        
        
              </tr>
      
      
            </table>
    
    
          </div>
  </text>
  <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="3"/>
  </extension>
  <extension url="http://hl7.org/fhir/StructureDefinition/package-source">
    <extension url="packageId">
      <valueId value="hl7.fhir.uv.xver-r4b.r5"/>
    </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-r4b.r5"/>
    </extension>
  </extension>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
    <valueCode value="cds"/>
  </extension>
  <url value="http://terminology.hl7.org/CodeSystem/plan-definition-type"/>
  <version value="4.3.0"/>
  <name value="PlanDefinitionType"/>
  <title value="PlanDefinitionType"/>
  <status value="draft"/>
  <experimental value="false"/>
  <date value="2020-12-27T23:55:11-06: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|5.0.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="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>