ISO/HL7 10781 - Electronic Health Record System Functional Model, Release 2.1
0.14.0 - CI Build
ISO/HL7 10781 - Electronic Health Record System Functional Model, Release 2.1
0.14.0 - CI Build
ISO/HL7 10781 - Electronic Health Record System Functional Model, Release 2.1 - Local Development build (v0.14.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
| Active as of 2024-06-01 |
<Requirements xmlns="http://hl7.org/fhir">
<id value="EHRSFMR2.1-POP.1.2"/>
<meta>
<profile value="http://hl7.org/ehrs/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>Evaluate and notify patient, and/or provider of those preventative services, tests, or behavioral actions that are due or overdue.</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>The system generates notifications to patients regarding activities that are due or overdue. Examples include but are not limited to time sensitive patient and provider notification of follow-up appointments, laboratory tests, immunizations or examinations. The notifications can be customized in terms of timing, repetitions and administration reports. For example, a PAP test reminder might be sent to the patient two months prior to the test being due, repeated at three month intervals, and then reported to the administrator or clinician when nine months overdue.</p>
</div></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>POP.1.2#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 capture, maintain, and render timely notifications to patients, and/or appropriate providers of preventative services, tests or behavioral actions that are due or overdue on an individual patient.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>POP.1.2#02</span>
</td>
<td style="padding-left: 4px;">
<span>SHOULD</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHOULD capture in the patient's record a history of preventative service and wellness related system notifications regarding that patient.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>POP.1.2#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 determine and present overdue preventative services.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>POP.1.2#04</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, maintain and render configuration parameters regarding patient notifications (e.g., number of repetitions of the notification, timing of the notification, escalation in priority).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>POP.1.2#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 provide the ability to update content of preventative service and wellness related notifications, guidelines, reminders and associated reference materials.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>POP.1.2#06</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 the guidelines, criteria or rules that trigger the preventative service and wellness related notifications.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>POP.1.2#07</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 manage the lifecycle of preventative service and wellness related notifications and reminders (e.g., mode of communication or timing of escalation from reminder to urgent alert).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>POP.1.2#08</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 and maintain the documentation of manual outreach activities (e.g., e-mail, letter or associated telephone conversation).</p>
</div></span>
</td>
</tr>
</table>
</div>
</text>
<url value="http://hl7.org/ehrs/Requirements/EHRSFMR2.1-POP.1.2"/>
<version value="0.14.0"/>
<name
value="POP_1_2_Present_Notifications_and_Reminders_for_Preventative_Services_and_Wellness"/>
<title
value="POP.1.2 Present Notifications and Reminders for Preventative Services and Wellness (Function)"/>
<status value="active"/>
<date value="2024-06-01T08:34:10+00:00"/>
<publisher value="EHR WG"/>
<contact>
<telecom>
<system value="url"/>
<value value="http://www.hl7.org/Special/committees/ehr"/>
</telecom>
</contact>
<description
value="Evaluate and notify patient, and/or provider of those preventative services, tests, or behavioral actions that are due or overdue."/>
<purpose
value="The system generates notifications to patients regarding activities that are due or overdue. Examples include but are not limited to time sensitive patient and provider notification of follow-up appointments, laboratory tests, immunizations or examinations. The notifications can be customized in terms of timing, repetitions and administration reports. For example, a PAP test reminder might be sent to the patient two months prior to the test being due, repeated at three month intervals, and then reported to the administrator or clinician when nine months overdue."/>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-POP.1.2-01"/>
<label value="POP.1.2#01"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL capture, maintain, and render timely notifications to patients, and/or appropriate providers of preventative services, tests or behavioral actions that are due or overdue on an individual patient."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.2.5.2#1"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-POP.1.2-02"/>
<label value="POP.1.2#02"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD capture in the patient's record a history of preventative service and wellness related system notifications regarding that patient."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.2.5.2#2"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-POP.1.2-03"/>
<label value="POP.1.2#03"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to determine and present overdue preventative services."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.2.5.2#3"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-POP.1.2-04"/>
<label value="POP.1.2#04"/>
<conformance value="MAY"/>
<conditionality value="false"/>
<requirement
value="The system MAY provide the ability to capture, maintain and render configuration parameters regarding patient notifications (e.g., number of repetitions of the notification, timing of the notification, escalation in priority)."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.2.5.2#5"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-POP.1.2-05"/>
<label value="POP.1.2#05"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to update content of preventative service and wellness related notifications, guidelines, reminders and associated reference materials."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.2.5.2#6"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-POP.1.2-06"/>
<label value="POP.1.2#06"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to manage the guidelines, criteria or rules that trigger the preventative service and wellness related notifications."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-POP.1.2-07"/>
<label value="POP.1.2#07"/>
<conformance value="MAY"/>
<conditionality value="false"/>
<requirement
value="The system MAY provide the ability to manage the lifecycle of preventative service and wellness related notifications and reminders (e.g., mode of communication or timing of escalation from reminder to urgent alert)."/>
<derivedFrom value="EHR-S_FM_R1.1 DC.2.5.2#7"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="EHRSFMR2.1-POP.1.2-08"/>
<label value="POP.1.2#08"/>
<conformance value="MAY"/>
<conditionality value="false"/>
<requirement
value="The system MAY provide the ability to capture and maintain the documentation of manual outreach activities (e.g., e-mail, letter or associated telephone conversation)."/>
</statement>
</Requirements>