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

HL7 Electronic Health Record System Functional Model, Release 2.1.1, published by HL7 International / Electronic Health Records. This guide is not an authorized publication; it is the continuous build for version 2.1.1 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/ehrsfm-ig/ and changes regularly. See the Directory of published versions

## : POP.9 Support Consistent Healthcare Management of Patient Groups or Populations (Function)

Page standards status: Normative

Raw xml | Download

    <Requirements xmlns="http://hl7.org/fhir">
      <id value="EHRSFMR2-POP.9"/>
      <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>Populations or groups of patients that share diagnoses (such as diabetes or hypertension), problems, functional limitations, treatment, medication, and demographic characteristics such as race, ethnicity, religion, socio-economic status that may impact care are identified for the clinician. The clinician is advised and assisted with management of these patients to optimize the clinician's ability to provide appropriate care. For example, a clinician is alerted to information regarding racial, cultural, religious, socio-economic, living situation and functional limitations of the patient that are required to provide appropriate care. Among other examples are notification of the patients' eligibility for a particular test, therapy, or follow-up; availability of supportive resources in the community; or results from audits of compliance of these populations with disease management protocols. The system may also Include the ability to identify groups of patients based on clinical observations or laboratory test results and assist in initiating a follow-up or recall for selected patients.</p>
    <p>The system may also provide the ability to create and render configurable reports for specific populations/or topics of interest, e.g. chronic conditions, suicidal risk, or post traumatic stress syndrome, or traumatic brain injury.</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;">
                POP.9#01
                </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-EHRSFMR2-CPS.3.4.html">CPS.3.4</a> (Support for Context-Sensitive Care Plans, Guidelines, Protocols).</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                POP.9#02
                </td>
                <td style="padding-left: 4px;">
                SHALL

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system SHALL provide the ability to analyze and tag patients who are eligible for healthcare management protocols based on criteria identified within the protocol.</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                POP.9#03
                </td>
                <td style="padding-left: 4px;">
                SHOULD

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system SHOULD provide the ability to analyze and tag (for inclusion or exclusion) a patient from an existing healthcare management protocol group.</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                POP.9#04
                </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 the reason for inclusion or exclusion from a protocol or protocol group.</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                POP.9#05
                </td>
                <td style="padding-left: 4px;">
                SHOULD

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system SHOULD provide the ability to audit compliance of selected populations and groups that are the subjects of healthcare management protocols.</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                POP.9#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-EHRSFMR2-CPS.9.4.html">CPS.9.4</a> (Standard Report Generation).</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                POP.9#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 determine and present groups of patients based on similar attributes, as can be found in clinical observations or laboratory test results.</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                POP.9#08
                </td>
                <td style="padding-left: 4px;">
                SHALL

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system SHALL capture, maintain, and render the information necessary for patient follow-ups or recalls.</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                POP.9#09
                </td>
                <td style="padding-left: 4px;">
                SHALL

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system SHALL capture, maintain, and render protocols and guidelines for follow-ups or recalls.</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                POP.9#10
                </td>
                <td style="padding-left: 4px;">
                SHOULD

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system SHOULD determine and present notifications to initiate follow-ups or recalls based on protocols and guidelines.</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                POP.9#11
                </td>
                <td style="padding-left: 4px;">
                SHOULD

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system SHOULD capture research protocol deviation information, including any verbatim text of protocol deviation.</p>
    </div>

                </td>
            </tr>

        </table>
    </div>
      </text>
      <extension
                 url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status">
        <valueCode value="normative"/>
      </extension>
      <extension
                 url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
        <valueCode value="ehr"/>
      </extension>
      <url value="http://hl7.org/ehrs/uv/ehrsfmr2/Requirements/EHRSFMR2-POP.9"/>
      <version value="2.1.1"/>
      <name
            value="POP_9_Support_Consistent_Healthcare_Management_of_Patient_Groups_or_Populations"/>
      <title
             value="POP.9 Support Consistent Healthcare Management of Patient Groups or Populations (Function)"/>
      <status value="active"/>
      <date value="2025-12-13T09:06:06+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="Provide the ability to identify and consistently manage healthcare over time and across populations or groups of patients that share diagnoses, problems, functional limitations, treatment, medications, and demographic characteristics that may impact care ( e.g., population management, disease management, wellness management or care management)."/>
      <jurisdiction>
        <coding>
          <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
          <code value="001"/>
          <display value="World"/>
        </coding>
      </jurisdiction>
      <purpose
               value="Populations or groups of patients that share diagnoses (such as diabetes or hypertension), problems, functional limitations, treatment, medication, and demographic characteristics such as race, ethnicity, religion, socio-economic status that may impact care are identified for the clinician. The clinician is advised and assisted with management of these patients to optimize the clinician's ability to provide appropriate care. For example, a clinician is alerted to information regarding racial, cultural, religious, socio-economic, living situation and functional limitations of the patient that are required to provide appropriate care. Among other examples are notification of the patients' eligibility for a particular test, therapy, or follow-up; availability of supportive resources in the community; or results from audits of compliance of these populations with disease management protocols. The system may also Include the ability to identify groups of patients based on clinical observations or laboratory test results and assist in initiating a follow-up or recall for selected patients.

    The system may also provide the ability to create and render configurable reports for specific populations/or topics of interest, e.g. chronic conditions, suicidal risk, or post traumatic stress syndrome, or traumatic brain injury."/>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-POP.9-01"/>
        <label value="POP.9#01"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL 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.2.2#1"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-POP.9-02"/>
        <label value="POP.9#02"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL provide the ability to analyze and tag patients who are eligible for healthcare management protocols based on criteria identified within the protocol."/>
        <derivedFrom value="EHR-S_FM_R1.1 DC.2.2.2#2"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-POP.9-03"/>
        <label value="POP.9#03"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to analyze and tag (for inclusion or exclusion) a patient from an existing healthcare management protocol group."/>
        <derivedFrom value="EHR-S_FM_R1.1 DC.2.2.2#3"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-POP.9-04"/>
        <label value="POP.9#04"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to capture, maintain and render the reason for inclusion or exclusion from a protocol or protocol group."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-POP.9-05"/>
        <label value="POP.9#05"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to audit compliance of selected populations and groups that are the subjects of healthcare management protocols."/>
        <derivedFrom value="EHR-S_FM_R1.1 DC.2.2.2#4"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-POP.9-06"/>
        <label value="POP.9#06"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL conform to function [CPS.9.4](Requirements-EHRSFMR2-CPS.9.4.html) (Standard Report Generation)."/>
        <derivedFrom value="EHR-S_FM_R1.1 DC.2.2.2#5"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-POP.9-07"/>
        <label value="POP.9#07"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to determine and present groups of patients based on similar attributes, as can be found in clinical observations or laboratory test results."/>
        <derivedFrom value="EHR-S_FM_R1.1 DC.2.2.2#7"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-POP.9-08"/>
        <label value="POP.9#08"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL capture, maintain, and render the information necessary for patient follow-ups or recalls."/>
        <derivedFrom value="EHR-S_FM_R1.1 DC.2.2.2#8"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-POP.9-09"/>
        <label value="POP.9#09"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL capture, maintain, and render protocols and guidelines for follow-ups or recalls."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-POP.9-10"/>
        <label value="POP.9#10"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD determine and present notifications to initiate follow-ups or recalls based on protocols and guidelines."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-POP.9-11"/>
        <label value="POP.9#11"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD capture research protocol deviation information, including any verbatim text of protocol deviation."/>
      </statement>
    </Requirements>