HL7 Personal Health Record System Functional Model, Release 2
2.0.1-ballot - Normative Ballot
HL7 Personal Health Record System Functional Model, Release 2
2.0.1-ballot - Normative Ballot
HL7 Personal Health Record System Functional Model, Release 2, published by EHR WG. This guide is not an authorized publication; it is the continuous build for version 2.0.1-ballot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/phrsfm-ig/ and changes regularly. See the Directory of published versions
| Page standards status: Informative |
<Requirements xmlns="http://hl7.org/fhir">
<id value="PHRSFMR2-S.1.1"/>
<meta>
<profile
value="http://hl7.org/ehrs/uv/phrsfmr2/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>Support a PHR Account Holder in seeking providers who may meet their healthcare requirements.</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>In seeking healthcare, the system should support the PHR Account Holder being able to obtain a list(s) of providers by geographic area and/or within a dental or medical plan panel. Further, the PHR Account Holder should be able to sort providers by attributes including, but not limited to:</p>
<ul>
<li>specialty;</li>
<li>office hours;</li>
<li>telehealth-oriented encounters;</li>
<li>sex;</li>
<li>language;</li>
<li>methods of information selection;</li>
<li>methods of information sharing;</li>
<li>and (possible) payment information.</li>
</ul>
<p>The PHR Account Holder should be able to maintain, or provide access to, current provider information. A PHR Account Holder may desire to research (because of a planned household relocation to another geographic area) a diagnosis requiring highly specialized care by healthcare providers and or healthcare facilities that are in limited availability. The system should be flexible on alternative sources of information allowing the PHR Account Holder to review providers who might best meet the individual’s needs.</p>
<p>Consider also, that if various types of providers, care-team members, or social-affinity groups might be involved with the PHR Account Holder's health, then various methods of information selection, information sharing, and (possible) payment information might also need to be accommodated within the PHR system.</p>
<p>As a result, the PHR system ought to support a rich, extended set of caregivers such as:</p>
<ul>
<li>Social Networking Groups that are oriented towards health maintenance and recovery, wellness, and health goals;</li>
<li>Personal Health Support Groups (e.g., weight, drugs, behavioral health, mental health, or diabetes support)</li>
<li>Exercise and Physical Training specialists</li>
<li>School Nurses</li>
<li>Nutritionists/Dietitians</li>
<li>Care managers (e.g., in-home therapists, or discharge planners)</li>
<li>Community health worker (either professional or volunteer) (e.g., neighbors, public health workers, health representatives, health screeners, or non-traditional healthcare workers)</li>
<li>A mobile health clinic provider
Note: Some of these extended caregivers might offer PHR data entry services on behalf of the PHR Account Holder.</li>
</ul>
</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>S.1.1#01</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 link to multiple sources of healthcare provider and healthcare system information.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>S.1.1#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 provide the ability to render information based on one or more provider attributes.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>S.1.1#03</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 information regarding available health benefit plan provider panel(s) based on one or more attributes.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>S.1.1#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 present insurance information regarding a selected provider versus a health plan provider panel (in order to help the PHR Account Holder choose between an in-network versus an out-of-network provider). For example, the PHR Account Holder may desire to compare prices of certain specialists, compare the credentials of the specialists, identify the level of experience, research comments regarding the provider's quality of service, or evaluate the provider's caseload panel.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>S.1.1#05</span>
</td>
<td style="padding-left: 4px;">
<span>SHALL</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHALL manage the provider’s contact/business information.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>S.1.1#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 capture provider participation in payer networks.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>S.1.1#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 capture provider participation in payer benefit plan products.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>S.1.1#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 a healthcare provider privilege status at a healthcare facility.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>S.1.1#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 analyze a healthcare provider's credential information (e.g., to verify the accuracy of the stated credential).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>S.1.1#10</span>
</td>
<td style="padding-left: 4px;">
<i>dependent</i>
<span>MAY</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system MAY provide the ability to transmit a request to subscribe to a (health-oriented) Social Networking Group, a Health Support Group, or a health research organization according to user-preference, organizational policy, and/or jurisdictional law.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>S.1.1#11</span>
</td>
<td style="padding-left: 4px;">
<i>dependent</i>
<span>MAY</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system MAY provide the ability to manage personal health information in the health-coaching (including fitness training and/or exercise management) environment according to user-preference, organizational policy, and/or jurisdictional law (e.g., a health-coach might need to know the PHR Account Holder's health goals, physical limitations, natural human language, pregnancy status, age, and weight).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>S.1.1#12</span>
</td>
<td style="padding-left: 4px;">
<i>dependent</i>
<span>MAY</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system MAY provide the ability to exchange selected personal health information with a school health information system according to user-preference, organizational policy, and/or jurisdictional law (e.g., a parent might use the PHR system to share their child's diabetes information, diet order (e.g., feeding instructions, timing, or schedule) meal plan, or allergy restriction with the school nurse and with the child's pediatrician in keeping with Family Educational Rights and Privacy legislative requirements).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>S.1.1#13</span>
</td>
<td style="padding-left: 4px;">
<i>dependent</i>
<span>MAY</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system MAY provide the ability to exchange selected personal health information with a community health worker according to user-preference, organizational policy, and/or jurisdictional law (e.g., a parent might use the PHR system to share their children's demographic information with a disaster relief worker after a flood; a PHR Account Holder Proxy might use the PHR system to share information about their elderly parent's health status with a community health worker who is analyzing community risk for potentially unhealthful airborne exposures).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>S.1.1#14</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 for the PHR Account Holder to exchange selected health information with virtual encounter groups. Examples of virtual encounter groups include:</p>
<ul>
<li>telehealth-oriented encounters with providers;</li>
<li>Social Networking Groups that are oriented towards health maintenance and recovery, wellness, and health goals;</li>
<li>Support Groups (e.g., weight, drugs, behavioral health, mental health, or diabetes support); or</li>
<li>Care Managers (e.g., a care-manager who offers virtual assessments or reviews, or who provides discharge planning services, or who serves as a PHR information management or data-curation concierge).</li>
</ul>
</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/phrsfmr2/Requirements/PHRSFMR2-S.1.1"/>
<version value="2.0.1-ballot"/>
<name value="S_1_1_Manage_Selection_of_Providers"/>
<title value="S.1.1 Manage Selection of Providers (Function)"/>
<status value="active"/>
<date value="2025-08-29T14:03:44+00:00"/>
<publisher value="EHR WG"/>
<contact>
<telecom>
<system value="url"/>
<value value="http://www.hl7.org/Special/committees/ehr"/>
</telecom>
</contact>
<description
value="Support a PHR Account Holder in seeking providers who may meet their healthcare requirements."/>
<purpose
value="In seeking healthcare, the system should support the PHR Account Holder being able to obtain a list(s) of providers by geographic area and/or within a dental or medical plan panel. Further, the PHR Account Holder should be able to sort providers by attributes including, but not limited to:
- specialty;
- office hours;
- telehealth-oriented encounters;
- sex;
- language;
- methods of information selection;
- methods of information sharing;
- and (possible) payment information.
The PHR Account Holder should be able to maintain, or provide access to, current provider information. A PHR Account Holder may desire to research (because of a planned household relocation to another geographic area) a diagnosis requiring highly specialized care by healthcare providers and or healthcare facilities that are in limited availability. The system should be flexible on alternative sources of information allowing the PHR Account Holder to review providers who might best meet the individual’s needs.
Consider also, that if various types of providers, care-team members, or social-affinity groups might be involved with the PHR Account Holder's health, then various methods of information selection, information sharing, and (possible) payment information might also need to be accommodated within the PHR system.
As a result, the PHR system ought to support a rich, extended set of caregivers such as:
- Social Networking Groups that are oriented towards health maintenance and recovery, wellness, and health goals;
- Personal Health Support Groups (e.g., weight, drugs, behavioral health, mental health, or diabetes support)
- Exercise and Physical Training specialists
- School Nurses
- Nutritionists/Dietitians
- Care managers (e.g., in-home therapists, or discharge planners)
- Community health worker (either professional or volunteer) (e.g., neighbors, public health workers, health representatives, health screeners, or non-traditional healthcare workers)
- A mobile health clinic provider
Note: Some of these extended caregivers might offer PHR data entry services on behalf of the PHR Account Holder."/>
<statement>
<extension
url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="PHRSFMR2-S.1.1-01"/>
<label value="S.1.1#01"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to link to multiple sources of healthcare provider and healthcare system information."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="PHRSFMR2-S.1.1-02"/>
<label value="S.1.1#02"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to render information based on one or more provider attributes."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="PHRSFMR2-S.1.1-03"/>
<label value="S.1.1#03"/>
<conformance value="MAY"/>
<conditionality value="false"/>
<requirement
value="The system MAY provide the ability to render information regarding available health benefit plan provider panel(s) based on one or more attributes."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="PHRSFMR2-S.1.1-04"/>
<label value="S.1.1#04"/>
<conformance value="MAY"/>
<conditionality value="false"/>
<requirement
value="The system MAY provide the ability to present insurance information regarding a selected provider versus a health plan provider panel (in order to help the PHR Account Holder choose between an in-network versus an out-of-network provider). For example, the PHR Account Holder may desire to compare prices of certain specialists, compare the credentials of the specialists, identify the level of experience, research comments regarding the provider's quality of service, or evaluate the provider's caseload panel."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="PHRSFMR2-S.1.1-05"/>
<label value="S.1.1#05"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL manage the provider’s contact/business information."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="PHRSFMR2-S.1.1-06"/>
<label value="S.1.1#06"/>
<conformance value="MAY"/>
<conditionality value="false"/>
<requirement
value="The system MAY provide the ability to capture provider participation in payer networks."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="PHRSFMR2-S.1.1-07"/>
<label value="S.1.1#07"/>
<conformance value="MAY"/>
<conditionality value="false"/>
<requirement
value="The system MAY provide the ability to capture provider participation in payer benefit plan products."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="PHRSFMR2-S.1.1-08"/>
<label value="S.1.1#08"/>
<conformance value="MAY"/>
<conditionality value="false"/>
<requirement
value="The system MAY provide the ability to capture a healthcare provider privilege status at a healthcare facility."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="PHRSFMR2-S.1.1-09"/>
<label value="S.1.1#09"/>
<conformance value="MAY"/>
<conditionality value="false"/>
<requirement
value="The system MAY provide the ability to analyze a healthcare provider's credential information (e.g., to verify the accuracy of the stated credential)."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
<valueBoolean value="true"/>
</extension>
<key value="PHRSFMR2-S.1.1-10"/>
<label value="S.1.1#10"/>
<conformance value="MAY"/>
<conditionality value="false"/>
<requirement
value="The system MAY provide the ability to transmit a request to subscribe to a (health-oriented) Social Networking Group, a Health Support Group, or a health research organization according to user-preference, organizational policy, and/or jurisdictional law."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
<valueBoolean value="true"/>
</extension>
<key value="PHRSFMR2-S.1.1-11"/>
<label value="S.1.1#11"/>
<conformance value="MAY"/>
<conditionality value="false"/>
<requirement
value="The system MAY provide the ability to manage personal health information in the health-coaching (including fitness training and/or exercise management) environment according to user-preference, organizational policy, and/or jurisdictional law (e.g., a health-coach might need to know the PHR Account Holder's health goals, physical limitations, natural human language, pregnancy status, age, and weight)."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
<valueBoolean value="true"/>
</extension>
<key value="PHRSFMR2-S.1.1-12"/>
<label value="S.1.1#12"/>
<conformance value="MAY"/>
<conditionality value="false"/>
<requirement
value="The system MAY provide the ability to exchange selected personal health information with a school health information system according to user-preference, organizational policy, and/or jurisdictional law (e.g., a parent might use the PHR system to share their child's diabetes information, diet order (e.g., feeding instructions, timing, or schedule) meal plan, or allergy restriction with the school nurse and with the child's pediatrician in keeping with Family Educational Rights and Privacy legislative requirements)."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
<valueBoolean value="true"/>
</extension>
<key value="PHRSFMR2-S.1.1-13"/>
<label value="S.1.1#13"/>
<conformance value="MAY"/>
<conditionality value="false"/>
<requirement
value="The system MAY provide the ability to exchange selected personal health information with a community health worker according to user-preference, organizational policy, and/or jurisdictional law (e.g., a parent might use the PHR system to share their children's demographic information with a disaster relief worker after a flood; a PHR Account Holder Proxy might use the PHR system to share information about their elderly parent's health status with a community health worker who is analyzing community risk for potentially unhealthful airborne exposures)."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="PHRSFMR2-S.1.1-14"/>
<label value="S.1.1#14"/>
<conformance value="MAY"/>
<conditionality value="false"/>
<requirement
value="The system MAY provide the ability for the PHR Account Holder to exchange selected health information with virtual encounter groups. Examples of virtual encounter groups include:
- telehealth-oriented encounters with providers;
- Social Networking Groups that are oriented towards health maintenance and recovery, wellness, and health goals;
- Support Groups (e.g., weight, drugs, behavioral health, mental health, or diabetes support); or
- Care Managers (e.g., a care-manager who offers virtual assessments or reviews, or who provides discharge planning services, or who serves as a PHR information management or data-curation concierge)."/>
</statement>
</Requirements>
IG © 2023 EHR WG. Package hl7.ehrs.uv.phrsfmr2#2.0.1-ballot based on FHIR 5.0.0. Generated 2025-08-29
Links: Table of Contents |
QA Report
| Version History |
|
Propose a change