HL7 Electronic Health Record System Functional Model, Release 2.1.1
2.1.1-ballot - Normative Ballot

Publication Build: This will be filled in by the publication tooling

## : CPS.3.10 Support for Identification of Potential Problems and Trends (Function) - XML Representation

Page standards status: Informative

Raw xml | Download

    <Requirements xmlns="http://hl7.org/fhir">
      <id value="EHRSFMR2-CPS.3.10"/>
      <meta>
        <profile
                 value="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/FMFunction"/>
      </meta>
      <text>
        <status value="extensions"/>
        <div xmlns="http://www.w3.org/1999/xhtml">
        <span id="description"><b>Statement <a href="https://hl7.org/fhir/versions.html#std-process" title="Normative Content" class="normative-flag">N</a>:</b> <div><p>Identify conditions of clinical interest, identify trends that may lead to significant problems, and provide prompts for clinical decision support.</p>
    </div></span>

        <span id="purpose"><b>Description <a href="https://hl7.org/fhir/versions.html#std-process" title="Informative Content" class="informative-flag">I</a>:</b> <div><p>Providing the health care provider with a prompt, notification or alert for identified specific concerns of clinical interest is a cornerstone of Clinical Decision Support. When personal health information is collected directly during a patient visit, input by the patient, or acquired from an external source (laboratory results), it is important to be able to identify and tag potential problems and trends that may be condition- or patient-specific (given the individual's personal health profile), or changes warranting further assessment.
    Example:
    Examples include: Behavioral risk factors such as tobacco/alcohol use, social history, significant trends (laboratory results, weight); a decrease in creatinine clearance for a patient on Metformin; an abnormal increase in INR for a patient on warfarin; an increase in suicidal ideation; presence of methamphetamines; or absence of therapeutic levels of antidepressants.</p>
    </div></span>

        <span id="actors"><b>Actors:</b><br/> ehr</span>

        <span id="requirements"><b>Criteria <a href="https://hl7.org/fhir/versions.html#std-process" title="Normative Content" class="normative-flag">N</a>:</b></span>

        <table id="statements" class="grid dict">

            <tr>
                <td style="padding-left: 4px;">

                    <span>CPS.3.10#01</span>

                </td>
                <td style="padding-left: 4px;">

                    <span>SHALL</span>

                </td>
                <td style="padding-left: 4px;" class="requirement">

                    <span><div><p>The system SHALL conform to function <a href="Requirements-EHRSFMR2-CP.3.1.html">CP.3.1</a> (Conduct Assessments) and provide the ability to access standard assessment data in the patient record.</p>
    </div></span>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">

                    <span>CPS.3.10#02</span>

                </td>
                <td style="padding-left: 4px;">

                    <i>dependent</i>

                    <span>SHOULD</span>

                </td>
                <td style="padding-left: 4px;" class="requirement">

                    <span><div><p>The system SHOULD provide the ability to present health standards and practices according to scope of practice at the time of the encounter.</p>
    </div></span>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">

                    <span>CPS.3.10#03</span>

                </td>
                <td style="padding-left: 4px;">

                    <span>SHOULD</span>

                </td>
                <td style="padding-left: 4px;" class="requirement">

                    <span><div><p>The system SHOULD provide the ability to analyze patient context-driven assessments and additional health information against best practices in order to identify patient-specific growth or development patterns, health trends and potential health problems.</p>
    </div></span>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">

                    <span>CPS.3.10#04</span>

                </td>
                <td style="padding-left: 4px;">

                    <span>SHOULD</span>

                </td>
                <td style="padding-left: 4px;" class="requirement">

                    <span><div><p>The system SHOULD provide the ability to manage rules for defining trends.</p>
    </div></span>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">

                    <span>CPS.3.10#05</span>

                </td>
                <td style="padding-left: 4px;">

                    <span>SHOULD</span>

                </td>
                <td style="padding-left: 4px;" class="requirement">

                    <span><div><p>The system SHOULD present the provider with trends based on patient contextual health information.</p>
    </div></span>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">

                    <span>CPS.3.10#06</span>

                </td>
                <td style="padding-left: 4px;">

                    <span>MAY</span>

                </td>
                <td style="padding-left: 4px;" class="requirement">

                    <span><div><p>The system MAY provide the ability to transmit trends and related rules to external systems (e.g., PHR systems).</p>
    </div></span>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">

                    <span>CPS.3.10#07</span>

                </td>
                <td style="padding-left: 4px;">

                    <span>SHOULD</span>

                </td>
                <td style="padding-left: 4px;" class="requirement">

                    <span><div><p>The system SHOULD provide the ability to render laboratory data in numerical (tabular or spreadsheet) form over time to enable trend analysis.</p>
    </div></span>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">

                    <span>CPS.3.10#08</span>

                </td>
                <td style="padding-left: 4px;">

                    <span>SHOULD</span>

                </td>
                <td style="padding-left: 4px;" class="requirement">

                    <span><div><p>The system SHOULD provide the ability to render laboratory data in graphical form over time to enable trend analysis.</p>
    </div></span>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">

                    <span>CPS.3.10#09</span>

                </td>
                <td style="padding-left: 4px;">

                    <span>MAY</span>

                </td>
                <td style="padding-left: 4px;" class="requirement">

                    <span><div><p>The system MAY provide the ability to integrate the laboratory result trends with items from the Problem List and other items such as vital signs.</p>
    </div></span>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">

                    <span>CPS.3.10#10</span>

                </td>
                <td style="padding-left: 4px;">

                    <span>MAY</span>

                </td>
                <td style="padding-left: 4px;" class="requirement">

                    <span><div><p>The system MAY provide the ability to render prescription timelines (i.e., events related to a prescription from order to administration) in graphic form over time to enable trend analysis.</p>
    </div></span>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">

                    <span>CPS.3.10#11</span>

                </td>
                <td style="padding-left: 4px;">

                    <span>SHOULD</span>

                </td>
                <td style="padding-left: 4px;" class="requirement">

                    <span><div><p>The system SHOULD present the provider with information that may prompt an order for additional assessments, testing or adjunctive treatment.</p>
    </div></span>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">

                    <span>CPS.3.10#12</span>

                </td>
                <td style="padding-left: 4px;">

                    <span>SHOULD</span>

                </td>
                <td style="padding-left: 4px;" class="requirement">

                    <span><div><p>The system SHOULD conform to function <a href="Requirements-EHRSFMR2-CPS.3.8.html">CPS.3.8</a> (Manage Documentation of Clinician Response to Decision Support Prompts).</p>
    </div></span>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">

                    <span>CPS.3.10#13</span>

                </td>
                <td style="padding-left: 4px;">

                    <span>MAY</span>

                </td>
                <td style="padding-left: 4px;" class="requirement">

                    <span><div><p>The system MAY provide the ability to integrate or link health information contained in the patient record with appropriate patient education materials.</p>
    </div></span>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">

                    <span>CPS.3.10#14</span>

                </td>
                <td style="padding-left: 4px;">

                    <span>SHOULD</span>

                </td>
                <td style="padding-left: 4px;" class="requirement">

                    <span><div><p>The system SHOULD conform to function <a href="Requirements-EHRSFMR2-CPS.3.4.html">CPS.3.4</a> (Support for Context-Sensitive Care Plans, Guidelines, Protocols).</p>
    </div></span>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">

                    <span>CPS.3.10#15</span>

                </td>
                <td style="padding-left: 4px;">

                    <span>MAY</span>

                </td>
                <td style="padding-left: 4px;" class="requirement">

                    <span><div><p>The system MAY provide the ability to tag an individual patient's conditions of clinical interest.</p>
    </div></span>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">

                    <span>CPS.3.10#16</span>

                </td>
                <td style="padding-left: 4px;">

                    <span>MAY</span>

                </td>
                <td style="padding-left: 4px;" class="requirement">

                    <span><div><p>The system MAY provide the ability to maintain and render the list of individual patient's conditions of clinical interest that have been tagged.</p>
    </div></span>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">

                    <span>CPS.3.10#17</span>

                </td>
                <td style="padding-left: 4px;">

                    <span>MAY</span>

                </td>
                <td style="padding-left: 4px;" class="requirement">

                    <span><div><p>The system MAY provide the ability to capture a set of notifications for conditions of clinical interest that have been tagged, and capture configuration parameters regarding the rendering of that set of notifications.</p>
    </div></span>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">

                    <span>CPS.3.10#18</span>

                </td>
                <td style="padding-left: 4px;">

                    <span>MAY</span>

                </td>
                <td style="padding-left: 4px;" class="requirement">

                    <span><div><p>The system MAY provide the ability to render details on the patient's conditions of clinical interest that have been tagged.</p>
    </div></span>

                </td>
            </tr>

        </table>
    </div>
      </text>
      <extension
                 url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
        <valueCode value="ehr"/>
      </extension>
      <url
           value="http://hl7.org/ehrs/uv/ehrsfmr2/Requirements/EHRSFMR2-CPS.3.10"/>
      <version value="2.1.1-ballot"/>
      <name
            value="CPS_3_10_Support_for_Identification_of_Potential_Problems_and_Trends"/>
      <title
             value="CPS.3.10 Support for Identification of Potential Problems and Trends (Function)"/>
      <status value="active"/>
      <date value="2025-04-04T11:04:36+11: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 conditions of clinical interest, identify trends that may lead to significant problems, and provide prompts for clinical decision support."/>
      <jurisdiction>
        <coding>
          <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
          <code value="001"/>
          <display value="World"/>
        </coding>
      </jurisdiction>
      <purpose
               value="Providing the health care provider with a prompt, notification or alert for identified specific concerns of clinical interest is a cornerstone of Clinical Decision Support. When personal health information is collected directly during a patient visit, input by the patient, or acquired from an external source (laboratory results), it is important to be able to identify and tag potential problems and trends that may be condition- or patient-specific (given the individual's personal health profile), or changes warranting further assessment.
    Example:
    Examples include: Behavioral risk factors such as tobacco/alcohol use, social history, significant trends (laboratory results, weight); a decrease in creatinine clearance for a patient on Metformin; an abnormal increase in INR for a patient on warfarin; an increase in suicidal ideation; presence of methamphetamines; or absence of therapeutic levels of antidepressants."/>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.3.10-01"/>
        <label value="CPS.3.10#01"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL conform to function [CP.3.1](Requirements-EHRSFMR2-CP.3.1.html) (Conduct Assessments) and provide the ability to access standard assessment data in the patient record."/>
        <derivedFrom value="EHR-S_FM_R1.1 DC.2.1.3#1"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="true"/>
        </extension>
        <key value="EHRSFMR2-CPS.3.10-02"/>
        <label value="CPS.3.10#02"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to present health standards and practices according to scope of practice at the time of the encounter."/>
        <derivedFrom value="EHR-S_FM_R1.1 DC.2.1.3#2"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.3.10-03"/>
        <label value="CPS.3.10#03"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to analyze patient context-driven assessments and additional health information against best practices in order to identify patient-specific growth or development patterns, health trends and potential health problems."/>
        <derivedFrom value="EHR-S_FM_R1.1 DC.2.1.3#3"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.3.10-04"/>
        <label value="CPS.3.10#04"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to manage rules for defining trends."/>
        <derivedFrom value="EHR-S_FM_R1.1 DC.2.1.3#4"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.3.10-05"/>
        <label value="CPS.3.10#05"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD present the provider with trends based on patient contextual health information."/>
        <derivedFrom value="EHR-S_FM_R1.1 DC.2.1.3#5"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.3.10-06"/>
        <label value="CPS.3.10#06"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY provide the ability to transmit trends and related rules to external systems (e.g., PHR systems)."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.3.10-07"/>
        <label value="CPS.3.10#07"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to render laboratory data in numerical (tabular or spreadsheet) form over time to enable trend analysis."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.3.10-08"/>
        <label value="CPS.3.10#08"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to render laboratory data in graphical form over time to enable trend analysis."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.3.10-09"/>
        <label value="CPS.3.10#09"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY provide the ability to integrate the laboratory result trends with items from the Problem List and other items such as vital signs."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.3.10-10"/>
        <label value="CPS.3.10#10"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY provide the ability to render prescription timelines (i.e., events related to a prescription from order to administration) in graphic form over time to enable trend analysis."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.3.10-11"/>
        <label value="CPS.3.10#11"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD present the provider with information that may prompt an order for additional assessments, testing or adjunctive treatment."/>
        <derivedFrom value="EHR-S_FM_R1.1 DC.2.1.3#6"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.3.10-12"/>
        <label value="CPS.3.10#12"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD conform to function [CPS.3.8](Requirements-EHRSFMR2-CPS.3.8.html) (Manage Documentation of Clinician Response to Decision Support Prompts)."/>
        <derivedFrom value="EHR-S_FM_R1.1 DC.2.1.3#7"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.3.10-13"/>
        <label value="CPS.3.10#13"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY provide the ability to integrate or link health information contained in the patient record with appropriate patient education materials."/>
        <derivedFrom value="EHR-S_FM_R1.1 DC.2.1.3#8"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.3.10-14"/>
        <label value="CPS.3.10#14"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD conform to function [CPS.3.4](Requirements-EHRSFMR2-CPS.3.4.html) (Support for Context-Sensitive Care Plans, Guidelines, Protocols)."/>
        <derivedFrom value="EHR-S_FM_R1.1 DC.2.1.3#9"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.3.10-15"/>
        <label value="CPS.3.10#15"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY provide the ability to tag an individual patient's conditions of clinical interest."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.3.10-16"/>
        <label value="CPS.3.10#16"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY provide the ability to maintain and render the list of individual patient's conditions of clinical interest that have been tagged."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.3.10-17"/>
        <label value="CPS.3.10#17"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY provide the ability to capture a set of notifications for conditions of clinical interest that have been tagged, and capture configuration parameters regarding the rendering of that set of notifications."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-CPS.3.10-18"/>
        <label value="CPS.3.10#18"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY provide the ability to render details on the patient's conditions of clinical interest that have been tagged."/>
      </statement>
    </Requirements>