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-PH.2.5.8"/>
<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>Manage the PHR Account Holder's Family Health History.</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 family history traditionally imparts the PHR Account Holder with certain risks and probabilities of illnesses that have a familial component. The major illnesses and cause of death of primary family members should be captured and displayed. For some illnesses of the PHR Account Holder a negative family history is also pertinent such as for cancer.</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>PH.2.5.8#01</span>
</td>
<td style="padding-left: 4px;">
<i>dependent</i>
<span>SHALL</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHALL provide the ability to manage family history according to organizational policy and/or jurisdictional law.</p>
</div></span>
Satisfied by:<ol>
<li><a href="https://www.hl7.org/fhir/familymemberhistory.html">https://www.hl7.org/fhir/familymemberhistory.html</a></li>
</ol>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>PH.2.5.8#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 capture, maintain, and transmit a request-for-correction to family history that was captured from an external source. Note: There could be multiple types of errors, both unintentional and intentional; the errors could also reside in multiple storage locations (primary, secondary, and intermediary); the errors could also reside in current records or in archived records; there could also be multiple sources (author, custodian-of-record, transcriptionist).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>PH.2.5.8#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 for the PHR Account Holder to annotate the family history with text comments (e.g., "Great-grandmother Alice was lost at sea” and that "Uncle Robert disagrees with the cause-of-death attributed to great-grandmother Alice".)</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>PH.2.5.8#04</span>
</td>
<td style="padding-left: 4px;">
<span>SHALL</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHALL provide the ability to enter missing information regarding the family history.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>PH.2.5.8#05</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 family history entries with the PHR Accounts of other family members according to user preference and/or consent, user role, organizational policy, and/or jurisdictional law.</p>
</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-PH.2.5.8"/>
<version value="2.0.1-ballot"/>
<name value="PH_2_5_8_Maintain_Family_History"/>
<title value="PH.2.5.8 Maintain Family History (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="Manage the PHR Account Holder's Family Health History."/>
<purpose
value="The family history traditionally imparts the PHR Account Holder with certain risks and probabilities of illnesses that have a familial component. The major illnesses and cause of death of primary family members should be captured and displayed. For some illnesses of the PHR Account Holder a negative family history is also pertinent such as for cancer."/>
<statement>
<extension
url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
<valueBoolean value="true"/>
</extension>
<key value="PHRSFMR2-PH.2.5.8-01"/>
<label value="PH.2.5.8#01"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to manage family history according to organizational policy and/or jurisdictional law."/>
<satisfiedBy value="https://www.hl7.org/fhir/familymemberhistory.html"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="PHRSFMR2-PH.2.5.8-02"/>
<label value="PH.2.5.8#02"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to capture, maintain, and transmit a request-for-correction to family history that was captured from an external source. Note: There could be multiple types of errors, both unintentional and intentional; the errors could also reside in multiple storage locations (primary, secondary, and intermediary); the errors could also reside in current records or in archived records; there could also be multiple sources (author, custodian-of-record, transcriptionist)."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="PHRSFMR2-PH.2.5.8-03"/>
<label value="PH.2.5.8#03"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability for the PHR Account Holder to annotate the family history with text comments (e.g., "Great-grandmother Alice was lost at sea” and that "Uncle Robert disagrees with the cause-of-death attributed to great-grandmother Alice".)"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="PHRSFMR2-PH.2.5.8-04"/>
<label value="PH.2.5.8#04"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability to enter missing information regarding the family history."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
<valueBoolean value="true"/>
</extension>
<key value="PHRSFMR2-PH.2.5.8-05"/>
<label value="PH.2.5.8#05"/>
<conformance value="MAY"/>
<conditionality value="false"/>
<requirement
value="The system MAY provide the ability to exchange family history entries with the PHR Accounts of other family members according to user preference and/or consent, user role, organizational policy, and/or jurisdictional law."/>
</statement>
</Requirements>