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.6.1 Outcome Measures and Analysis (Function)

Page standards status: Normative

Raw xml | Download

    <Requirements xmlns="http://hl7.org/fhir">
      <id value="EHRSFMR2-POP.6.1"/>
      <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>Many regions require regular reporting on the healthcare provided to individuals and populations. The system needs to provide the report-generating capability to easily create these reports or provide for the export of data to external report-generating software. The system may also provide the functionality to prompt for the collection of necessary information at the appropriate time in a patient encounter if such collection need can be properly defined in a workflow (e.g., requesting specific information for reporting of emergency services such as drug overdose, suspected abuse, communicable diseases, or for the collection of additional research data for a specific diagnosis).</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.6.1#01
                </td>
                <td style="padding-left: 4px;">
                SHOULD

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system SHOULD provide the ability to render data required to evaluate patient outcomes.</p>
    </div>

                </td>
            </tr>

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

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system SHOULD determine and render data by selection criteria (e.g., physician, facility, facility subsection, clinical research protocol number, or community) to evaluate patient, and/or population outcomes.</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                POP.6.1#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 capture and maintain outcome measures for a specific patient, and/or groups of patients with a specific diagnosis.</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                POP.6.1#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 and maintain measures to evaluate patient, and/or population outcomes to meet various regional requirements.</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                POP.6.1#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 capture and render unique patient and/or population outcome data defined to meet regional requirements.</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                POP.6.1#06
                </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 report formats for the export of patient, and/or population outcome data.</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                POP.6.1#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 and maintain notification phrases and prompts in the clinical care setting that would request information needed to comply with regional patient, and/or population outcome measurement requirements when specific triggers are met.</p>
    </div>

                </td>
            </tr>

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

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>The system SHOULD render patient, and/or population outcome data or query results to appropriate organizations (e.g., Quality Measurement organizations, Accreditation organizations) through a secure data service.</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                POP.6.1#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 tag patients who have been identified as exempt from being included on certain population-based reports (e.g., reports that would exclude the identity of a very important person (e.g., president of a country).</p>
    </div>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">
                POP.6.1#10
                </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: #f3e5ff;color: #7b1fa2;border: 1px solid #d1a3ff;">conditional</span>

                </td>
                <td style="padding-left: 4px;" class="requirement">
                    <div><p>IF the system provides the ability to tag patients who have been identified as exempt from being included on certain population-based reports, THEN the system SHALL provide the ability to manage-data-visibility for those patients.</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.6.1"/>
      <version value="2.1.1"/>
      <name value="POP_6_1_Outcome_Measures_and_Analysis"/>
      <title value="POP.6.1 Outcome Measures and Analysis (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="Support the capture and subsequent export or retrieval of data necessary for the reporting on patient outcome of care by population, facility, provider or community."/>
      <jurisdiction>
        <coding>
          <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
          <code value="001"/>
          <display value="World"/>
        </coding>
      </jurisdiction>
      <purpose
               value="Many regions require regular reporting on the healthcare provided to individuals and populations. The system needs to provide the report-generating capability to easily create these reports or provide for the export of data to external report-generating software. The system may also provide the functionality to prompt for the collection of necessary information at the appropriate time in a patient encounter if such collection need can be properly defined in a workflow (e.g., requesting specific information for reporting of emergency services such as drug overdose, suspected abuse, communicable diseases, or for the collection of additional research data for a specific diagnosis)."/>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-POP.6.1-01"/>
        <label value="POP.6.1#01"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to render data required to evaluate patient outcomes."/>
        <derivedFrom value="EHR-S_FM_R1.1 S.2.1.1#1"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-POP.6.1-02"/>
        <label value="POP.6.1#02"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD determine and render data by selection criteria (e.g., physician, facility, facility subsection, clinical research protocol number, or community) to evaluate patient, and/or population outcomes."/>
        <derivedFrom value="EHR-S_FM_R1.1 S.2.1.1#2"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-POP.6.1-03"/>
        <label value="POP.6.1#03"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to capture and maintain outcome measures for a specific patient, and/or groups of patients with a specific diagnosis."/>
        <derivedFrom value="EHR-S_FM_R1.1 S.2.1.1#3"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-POP.6.1-04"/>
        <label value="POP.6.1#04"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to capture and maintain measures to evaluate patient, and/or population outcomes to meet various regional requirements."/>
        <derivedFrom value="EHR-S_FM_R1.1 S.2.1.1#4"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-POP.6.1-05"/>
        <label value="POP.6.1#05"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to capture and render unique patient and/or population outcome data defined to meet regional requirements."/>
        <derivedFrom value="EHR-S_FM_R1.1 S.2.1.1#5"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-POP.6.1-06"/>
        <label value="POP.6.1#06"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to capture, maintain and render report formats for the export of patient, and/or population outcome data."/>
        <derivedFrom value="EHR-S_FM_R1.1 S.2.1.1#6"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-POP.6.1-07"/>
        <label value="POP.6.1#07"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to capture and maintain notification phrases and prompts in the clinical care setting that would request information needed to comply with regional patient, and/or population outcome measurement requirements when specific triggers are met."/>
        <derivedFrom value="EHR-S_FM_R1.1 S.2.1.1#7"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-POP.6.1-08"/>
        <label value="POP.6.1#08"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD render patient, and/or population outcome data or query results to appropriate organizations (e.g., Quality Measurement organizations, Accreditation organizations) through a secure data service."/>
        <derivedFrom value="EHR-S_FM_R1.1 S.2.1.1#8"/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-POP.6.1-09"/>
        <label value="POP.6.1#09"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL provide the ability to tag patients who have been identified as exempt from being included on certain population-based reports (e.g., reports that would exclude the identity of a very important person (e.g., president of a country)."/>
      </statement>
      <statement>
        <extension
                   url="http://hl7.org/ehrs/uv/ehrsfmr2/StructureDefinition/requirements-dependent">
          <valueBoolean value="false"/>
        </extension>
        <key value="EHRSFMR2-POP.6.1-10"/>
        <label value="POP.6.1#10"/>
        <conformance value="SHALL"/>
        <conditionality value="true"/>
        <requirement
                     value="IF the system provides the ability to tag patients who have been identified as exempt from being included on certain population-based reports, THEN the system SHALL provide the ability to manage-data-visibility for those patients."/>
      </statement>
    </Requirements>