HL7 Personal Health Record System Functional Model, Release 2
2.0.1 - Normative
HL7 Personal Health Record System Functional Model, Release 2
2.0.1 - Normative
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 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: Normative |
<Requirements xmlns="http://hl7.org/fhir">
<id value="PHRSFMR2-PH.3.5.6"/>
<meta>
<profile
value="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/FMFunction"/>
</meta>
<text>
<status value="extensions"/>
<div xmlns="http://www.w3.org/1999/xhtml">
<div id="description"><b>Description <a href="https://hl7.org/fhir/versions.html#std-process" title="Informative Content" class="informative-flag">I</a>:</b> In many care activities, recommendations are made for specific future activities. They are easy to let slip by and lose track of them. A thoughtful and documented reason for not following a particular recommendation should be captured to help manage liability risk. Some recommendations may be controversial and there are reasons not to follow them. It is useful to keep a list of recommendations as a separate check on future care to be managed with the help of the PHR Account Holder's provider.
Example(s):
- The radiologist recommends a repeat mammogram in six months rather than the usual twelve months.
- The Primary Care Provider recommends seeing a surgeon for occasional gallbladder attacks.
- A screening colonoscopy is recommended after age fifty.
- Annual screening or tests based on the PHR Account Holder's occupational risk factors.</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;">
PH.3.5.6#01
</td>
<td style="padding-left: 4px;">
SHALL
</td>
<td style="padding-left: 4px;" class="requirement">
The system SHALL provide the ability to capture recommendations from encounter and diagnostic studies in structured documents according to organizational policy and/or jurisdictional law (e.g., HIV results may need to be delayed from being sent directly to the PHR System, so that the provider has time to communicate with the patient directly).
Satisfied by:<ol>
<li><a href="https://www.hl7.org/fhir/communication.html">https://www.hl7.org/fhir/communication.html</a></li>
</ol>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
PH.3.5.6#02
</td>
<td style="padding-left: 4px;">
SHOULD
</td>
<td style="padding-left: 4px;" class="requirement">
The system SHOULD provide the ability to capture a recommendation, the identity of the recommending provider, the date of the recommendation, and the date suggested to perform the recommended action.
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
PH.3.5.6#03
</td>
<td style="padding-left: 4px;">
SHOULD
</td>
<td style="padding-left: 4px;" class="requirement">
The system SHOULD provide the ability to link a recommendation entry with the corresponding original document (e.g., a recommendation to lose ten pounds should be linked to a document that contains the PHR Account Holder's most recent BMI readings).
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
PH.3.5.6#04
</td>
<td style="padding-left: 4px;">
MAY
</td>
<td style="padding-left: 4px;" class="requirement">
The system MAY provide the ability to render a pending (or future) recommendation (e.g., so that a provider might be able to create a future-order or reminder, or to document the reason that the recommendation was dismissed).
</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/phrsfmr2/Requirements/PHRSFMR2-PH.3.5.6"/>
<version value="2.0.1"/>
<name value="PH_3_5_6_Manage_Recommendations"/>
<title value="PH.3.5.6 Manage Recommendations (Function)"/>
<status value="active"/>
<date value="2026-06-23T08:11:09+00:00"/>
<publisher value="EHR WG"/>
<contact>
<telecom>
<system value="url"/>
<value value="http://www.hl7.org/Special/committees/ehr"/>
</telecom>
</contact>
<description
value="Capture and track provider recommendations for future care."/>
<purpose
value="In many care activities, recommendations are made for specific future activities. They are easy to let slip by and lose track of them. A thoughtful and documented reason for not following a particular recommendation should be captured to help manage liability risk. Some recommendations may be controversial and there are reasons not to follow them. It is useful to keep a list of recommendations as a separate check on future care to be managed with the help of the PHR Account Holder's provider.
Example(s):
- The radiologist recommends a repeat mammogram in six months rather than the usual twelve months.
- The Primary Care Provider recommends seeing a surgeon for occasional gallbladder attacks.
- A screening colonoscopy is recommended after age fifty.
- Annual screening or tests based on the PHR Account Holder's occupational risk factors."/>
<statement>
<extension
url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
<valueBoolean value="true"/>
</extension>
<key value="PHRSFMR2-PH.3.5.6-01"/>
<label value="PH.3.5.6#01"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to capture recommendations from encounter and diagnostic studies in structured documents according to organizational policy and/or jurisdictional law (e.g., HIV results may need to be delayed from being sent directly to the PHR System, so that the provider has time to communicate with the patient directly)."/>
<satisfiedBy value="https://www.hl7.org/fhir/communication.html"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="PHRSFMR2-PH.3.5.6-02"/>
<label value="PH.3.5.6#02"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to capture a recommendation, the identity of the recommending provider, the date of the recommendation, and the date suggested to perform the recommended action."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="PHRSFMR2-PH.3.5.6-03"/>
<label value="PH.3.5.6#03"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to link a recommendation entry with the corresponding original document (e.g., a recommendation to lose ten pounds should be linked to a document that contains the PHR Account Holder's most recent BMI readings)."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="PHRSFMR2-PH.3.5.6-04"/>
<label value="PH.3.5.6#04"/>
<conformance value="MAY"/>
<conditionality value="false"/>
<requirement
value="The system MAY provide the ability to render a pending (or future) recommendation (e.g., so that a provider might be able to create a future-order or reminder, or to document the reason that the recommendation was dismissed)."/>
</statement>
</Requirements>
IG © 2023 EHR WG.
Package hl7.ehrs.uv.phrsfmr2#2.0.1 based on FHIR 5.0.0.
Generated
2026-06-23
Links: Table of Contents |
QA Report
| Version History |
|
Propose a change