CPS.3.4 Support for Context-Sensitive Care Plans, Guidelines, Protocols (Function) - XML Representation - HL7 EHR-S FM R2.1.1 - Dental Health Functional Profile, Release 2 v2.0.0-ballot

HL7 EHR-S FM R2.1.1 - Dental Health Functional Profile, Release 2, published by HL7 International / Electronic Health Records. This guide is not an authorized publication; it is the continuous build for version 2.0.0-ballot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/dhfp-ig/ and changes regularly. See the Directory of published versions
: CPS.3.4 Support for Context-Sensitive Care Plans, Guidelines, Protocols (Function)

Page standards status: Informative
Maturity Level: 1
Raw xml | Download

<Requirements xmlns="http://hl7.org/fhir">
  <id value="DHFPR2-CPS.3.4"/>
  <meta>
    <profile
             value="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/FMFunction"/>
  </meta>
  <language value="en"/>
  <text>
    <status value="extensions"/>
    <div xml:lang="en" xmlns="http://www.w3.org/1999/xhtml" lang="en">
    
             
    
    
    <div id="description"><b>Description <a href="https://hl7.org/fhir/versions.html#std-process" title="Informative Content" class="informative-flag">I</a>:</b> <div><p>At the time of the clinical encounter (problem identification), recommendations for tests, treatments, medications, immunizations, referrals and evaluations are presented based on evaluation of patient-specific data such as age, gender, developmental stage, their health profile, and any site-specific considerations. These may be modified on the basis of new clinical data at subsequent encounters.</p>
</div></div>
    
    
    
    <div id="requirements"><b>Criteria <a href="https://hl7.org/fhir/versions.html#std-process" title="Normative Content" class="normative-flag">N</a>:</b></div>
    
    <table id="statements" class="grid dict">
        
        <tr>
            <td style="padding-left: 4px;">
            CPS.3.4#01
            </td>
            <td style="padding-left: 4px;">
            SHALL
            
                
            
            
            
                
                    <span style="border-radius: 999px;margin: 2px 2px;font-size: 10px;display: inline-block;padding: 3px 5px;letter-spacing: 0.5px;line-height: 1;white-space: nowrap;background-color: #e0f2ff;color: #0070c9;border: 1px solid #a3d9ff;">profiled</span>
                
            
            </td>
            <td style="padding-left: 4px;" class="requirement">
                <div><p>The system SHALL provide the ability to render care and treatment plans that are sensitive to the context of patient data and assessments. Dental treatment plan examples include pediatric vs. adult, ortho, and perio.</p>
</div>
                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
            CPS.3.4#02
            </td>
            <td style="padding-left: 4px;">
            SHOULD
            
                
            
            
            
                
            
            </td>
            <td style="padding-left: 4px;" class="requirement">
                <div><p>The system SHOULD provide the ability to capture and maintain the choice of action in response to care plan suggestions.</p>
</div>
                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
            CPS.3.4#03
            </td>
            <td style="padding-left: 4px;">
            SHOULD
            
                
            
            
            
                
            
            </td>
            <td style="padding-left: 4px;" class="requirement">
                <div><p>The system SHOULD determine and render alerts, notifications, and reports about variances from standard care plans, guidelines, protocols, and clinical pathways.</p>
</div>
                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
            CPS.3.4#04
            </td>
            <td style="padding-left: 4px;">
            SHALL
            
                
            
            
            
                
            
            </td>
            <td style="padding-left: 4px;" class="requirement">
                <div><p>The system SHALL conform to function <a href="Requirements-DHFPR2-CPS.3.1.html">CPS.3.1</a> (Support for Standard Assessments).</p>
</div>
                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
            CPS.3.4#05
            </td>
            <td style="padding-left: 4px;">
            SHALL
            
                
            
            
            
                
            
            </td>
            <td style="padding-left: 4px;" class="requirement">
                <div><p>The system SHALL conform to function <a href="Requirements-DHFPR2-CPS.3.2.html">CPS.3.2</a> (Support for Patient Context-Driven Assessments).</p>
</div>
                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
            CPS.3.4#06
            </td>
            <td style="padding-left: 4px;">
            SHALL
            
                
            
            
            
                
            
            </td>
            <td style="padding-left: 4px;" class="requirement">
                <div><p>The system SHALL conform to function <a href="Requirements-DHFPR2-CPS.3.3.html">CPS.3.3</a> (Support for Standard Care Plans, Guidelines, Protocols).</p>
</div>
                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
            CPS.3.4#07
            </td>
            <td style="padding-left: 4px;">
            SHOULD
            
                
            
            
            
                
            
            </td>
            <td style="padding-left: 4px;" class="requirement">
                <div><p>The system SHOULD provide the ability to capture, maintain, and render specialized medical treatment guidelines and protocols for unique physical, chemical, biological, and radiologic exposures.</p>
</div>
                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
            CPS.3.4#08
            </td>
            <td style="padding-left: 4px;">
            SHOULD
            
                
            
            
            
                
            
            </td>
            <td style="padding-left: 4px;" class="requirement">
                <div><p>The system SHOULD provide the ability to manage biometric data, such as age-specific, weight-specific or height-specific normative data, to identify, track and provide alerts, notifications and reports about variances, care plans, guidelines and protocols.</p>
</div>
                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
            CPS.3.4#09
            </td>
            <td style="padding-left: 4px;">
            SHALL
            
                
            
            
            
                
            
            </td>
            <td style="padding-left: 4px;" class="requirement">
                <div><p>The system SHALL provide the ability to capture, maintain and render care plan templates to be used as a basis for the creation of new plans of care and treatment.</p>
</div>
                
            </td>
        </tr>
        
        <tr>
            <td style="padding-left: 4px;">
            CPS.3.4#10
            </td>
            <td style="padding-left: 4px;">
            SHOULD
            
                
            
            
            
                
            
            </td>
            <td style="padding-left: 4px;" class="requirement">
                <div><p>The system SHOULD provide the ability to capture care plan templates from previously developed care plans.</p>
</div>
                
            </td>
        </tr>
        
    </table>
</div>
  </text>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status">
    <valueCode value="informative"/>
  </extension>
  <extension
             url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-change-info">
    <valueCode value="NC"/>
  </extension>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
    <valueCode value="ehr"/>
  </extension>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
    <valueInteger value="1">
      <extension
                 url="http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom">
        <valueCanonical
                        value="http://hl7.org/ehrs/us/dhfpr2/ImplementationGuide/hl7.ehrs.us.dhfpr2"/>
      </extension>
    </valueInteger>
  </extension>
  <url value="http://hl7.org/ehrs/us/dhfpr2/Requirements/DHFPR2-CPS.3.4"/>
  <version value="2.0.0-ballot"/>
  <name
        value="CPS_3_4_Support_for_Context_Sensitive_Care_Plans__Guidelines__Protocols"/>
  <title
         value="CPS.3.4 Support for Context-Sensitive Care Plans, Guidelines, Protocols (Function)"/>
  <status value="active"/>
  <date value="2025-12-19T08:44:27+00:00"/>
  <publisher value="HL7 International / Electronic Health Records"/>
  <contact>
    <telecom>
      <system value="url"/>
      <value value="http://www.hl7.org/Special/committees/ehr"/>
    </telecom>
  </contact>
  <description
               value="Identify and present the appropriate care plans, guidelines, protocols, and/or clinical pathways for the management of patient-specific conditions that are identified in a patient clinical encounter."/>
  <jurisdiction>
    <coding>
      <system value="urn:iso:std:iso:3166"/>
      <code value="US"/>
    </coding>
  </jurisdiction>
  <purpose
           value="At the time of the clinical encounter (problem identification), recommendations for tests, treatments, medications, immunizations, referrals and evaluations are presented based on evaluation of patient-specific data such as age, gender, developmental stage, their health profile, and any site-specific considerations. These may be modified on the basis of new clinical data at subsequent encounters."/>
  <derivedFrom
               value="http://hl7.org/ehrs/uv/ehrsfmr2/Requirements/EHRSFMR2-CPS.3.4"/>
  <statement>
    <extension
               url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <extension
               url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-change-info">
      <valueCode value="C"/>
    </extension>
    <key value="DHFPR2-CPS.3.4-01"/>
    <label value="CPS.3.4#01"/>
    <conformance value="SHALL"/>
    <conditionality value="false"/>
    <requirement
                 value="The system SHALL provide the ability to render care and treatment plans that are sensitive to the context of patient data and assessments. Dental treatment plan examples include pediatric vs. adult, ortho, and perio."/>
    <derivedFrom value="CPS.3.4#1"/>
  </statement>
  <statement>
    <extension
               url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <extension
               url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-change-info">
      <valueCode value="NC"/>
    </extension>
    <key value="DHFPR2-CPS.3.4-02"/>
    <label value="CPS.3.4#02"/>
    <conformance value="SHOULD"/>
    <conditionality value="false"/>
    <requirement
                 value="The system SHOULD provide the ability to capture and maintain the choice of action in response to care plan suggestions."/>
    <derivedFrom value="CPS.3.4#2"/>
  </statement>
  <statement>
    <extension
               url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <extension
               url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-change-info">
      <valueCode value="NC"/>
    </extension>
    <key value="DHFPR2-CPS.3.4-03"/>
    <label value="CPS.3.4#03"/>
    <conformance value="SHOULD"/>
    <conditionality value="false"/>
    <requirement
                 value="The system SHOULD determine and render alerts, notifications, and reports about variances from standard care plans, guidelines, protocols, and clinical pathways."/>
    <derivedFrom value="CPS.3.4#3"/>
  </statement>
  <statement>
    <extension
               url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <extension
               url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-change-info">
      <valueCode value="NC"/>
    </extension>
    <key value="DHFPR2-CPS.3.4-04"/>
    <label value="CPS.3.4#04"/>
    <conformance value="SHALL"/>
    <conditionality value="false"/>
    <requirement
                 value="The system SHALL conform to function [CPS.3.1](Requirements-DHFPR2-CPS.3.1.html) (Support for Standard Assessments)."/>
    <derivedFrom value="CPS.3.4#4"/>
  </statement>
  <statement>
    <extension
               url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <extension
               url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-change-info">
      <valueCode value="NC"/>
    </extension>
    <key value="DHFPR2-CPS.3.4-05"/>
    <label value="CPS.3.4#05"/>
    <conformance value="SHALL"/>
    <conditionality value="false"/>
    <requirement
                 value="The system SHALL conform to function [CPS.3.2](Requirements-DHFPR2-CPS.3.2.html) (Support for Patient Context-Driven Assessments)."/>
    <derivedFrom value="CPS.3.4#5"/>
  </statement>
  <statement>
    <extension
               url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <extension
               url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-change-info">
      <valueCode value="NC"/>
    </extension>
    <key value="DHFPR2-CPS.3.4-06"/>
    <label value="CPS.3.4#06"/>
    <conformance value="SHALL"/>
    <conditionality value="false"/>
    <requirement
                 value="The system SHALL conform to function [CPS.3.3](Requirements-DHFPR2-CPS.3.3.html) (Support for Standard Care Plans, Guidelines, Protocols)."/>
    <derivedFrom value="CPS.3.4#6"/>
  </statement>
  <statement>
    <extension
               url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <extension
               url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-change-info">
      <valueCode value="NC"/>
    </extension>
    <key value="DHFPR2-CPS.3.4-07"/>
    <label value="CPS.3.4#07"/>
    <conformance value="SHOULD"/>
    <conditionality value="false"/>
    <requirement
                 value="The system SHOULD provide the ability to capture, maintain, and render specialized medical treatment guidelines and protocols for unique physical, chemical, biological, and radiologic exposures."/>
    <derivedFrom value="CPS.3.4#7"/>
  </statement>
  <statement>
    <extension
               url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <extension
               url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-change-info">
      <valueCode value="NC"/>
    </extension>
    <key value="DHFPR2-CPS.3.4-08"/>
    <label value="CPS.3.4#08"/>
    <conformance value="SHOULD"/>
    <conditionality value="false"/>
    <requirement
                 value="The system SHOULD provide the ability to manage biometric data, such as age-specific, weight-specific or height-specific normative data, to identify, track and provide alerts, notifications and reports about variances, care plans, guidelines and protocols."/>
    <derivedFrom value="CPS.3.4#8"/>
  </statement>
  <statement>
    <extension
               url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <extension
               url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-change-info">
      <valueCode value="NC"/>
    </extension>
    <key value="DHFPR2-CPS.3.4-09"/>
    <label value="CPS.3.4#09"/>
    <conformance value="SHALL"/>
    <conditionality value="false"/>
    <requirement
                 value="The system SHALL provide the ability to capture, maintain and render care plan templates to be used as a basis for the creation of new plans of care and treatment."/>
    <derivedFrom value="CPS.3.4#9"/>
  </statement>
  <statement>
    <extension
               url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
      <valueBoolean value="false"/>
    </extension>
    <extension
               url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-change-info">
      <valueCode value="NC"/>
    </extension>
    <key value="DHFPR2-CPS.3.4-10"/>
    <label value="CPS.3.4#10"/>
    <conformance value="SHOULD"/>
    <conditionality value="false"/>
    <requirement
                 value="The system SHOULD provide the ability to capture care plan templates from previously developed care plans."/>
    <derivedFrom value="CPS.3.4#10"/>
  </statement>
</Requirements>