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.3.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">
<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>Allow the PHR Account Holder to manage the import to and export of data from a PHR-S.</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>A PHR Account Holder needs to prescribe how data is exchanged with other systems including how data is imported to the PHR-S, and the parameters for data export (e.g., who, when, or the extent of data). Some import and export functions may be one-time events; other exchanges, for example, may occur at regular intervals (such as via a subscription service). The PHR Account Holder should be able to determine the information or data that he/she will accept into the PHR. The system should record the acknowledgement or refusal of data sent to the Account Holder’s PHR-S. Use of exported data should be constrained according its intended and permitted purpose of use (e.g., as described in the PHR-S manufacturer's Terms of Service and Terms of Use agreements).</p>
<p>Example(s): The PHR Account Holder may desire to inform her General Practitioner that the PHR Account Holder has received a proposed dietary regimen from a Registered Dietitian / Nutrition specialist. The PHR Account Holder may also desire to send a copy of the proposed nutrition care plan to the General Practitioner.</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>S.3.6#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 exchange PHR Account Holder data content with another PHR system.</p>
</div></span>
Satisfied by:<ol>
<li><a href="https://hl7.org/fhir/uv/bulkdata/">https://hl7.org/fhir/uv/bulkdata/</a></li>
</ol>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>S.3.6#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 exchange PHR Account Holder data content with other systems.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>S.3.6#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 exchange PHR Account Holder data content with other systems.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>S.3.6#04</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 determine entities from which data may be imported into the PHR-S.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>S.3.6#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 for the PHR Account Holder to determine entities to which data may be exported from the PHR-S.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>S.3.6#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 for the PHR Account Holder to exchange information with an entity on a one-time basis.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>S.3.6#07</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 exchange information with an entity on a recurring basis.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>S.3.6#08</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 incoming information.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>S.3.6#09</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 render a notification (i.e., an acknowledgment) of the receipt or the refusal to receive information that was sent from another system.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>S.3.6#10</span>
</td>
<td style="padding-left: 4px;">
<span>SHALL</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system SHALL conform to TI.1.5 (Non-Repudiation) to promote provenance regarding professionally-sourced clinical information.</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-S.3.6"/>
<version value="2.0.1-ballot"/>
<name value="S_3_6_Manage_PHR_Data_Import_and_Export"/>
<title value="S.3.6 Manage PHR Data Import and Export (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="Allow the PHR Account Holder to manage the import to and export of data from a PHR-S."/>
<purpose
value="A PHR Account Holder needs to prescribe how data is exchanged with other systems including how data is imported to the PHR-S, and the parameters for data export (e.g., who, when, or the extent of data). Some import and export functions may be one-time events; other exchanges, for example, may occur at regular intervals (such as via a subscription service). The PHR Account Holder should be able to determine the information or data that he/she will accept into the PHR. The system should record the acknowledgement or refusal of data sent to the Account Holder’s PHR-S. Use of exported data should be constrained according its intended and permitted purpose of use (e.g., as described in the PHR-S manufacturer's Terms of Service and Terms of Use agreements).
Example(s): The PHR Account Holder may desire to inform her General Practitioner that the PHR Account Holder has received a proposed dietary regimen from a Registered Dietitian / Nutrition specialist. The PHR Account Holder may also desire to send a copy of the proposed nutrition care plan to the General Practitioner."/>
<statement>
<extension
url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="PHRSFMR2-S.3.6-01"/>
<label value="S.3.6#01"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to exchange PHR Account Holder data content with another PHR system."/>
<satisfiedBy value="https://hl7.org/fhir/uv/bulkdata/"/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="PHRSFMR2-S.3.6-02"/>
<label value="S.3.6#02"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to exchange PHR Account Holder data content with other systems."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="PHRSFMR2-S.3.6-03"/>
<label value="S.3.6#03"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to exchange PHR Account Holder data content with other systems."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="PHRSFMR2-S.3.6-04"/>
<label value="S.3.6#04"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability for the PHR Account Holder to determine entities from which data may be imported into the PHR-S."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="PHRSFMR2-S.3.6-05"/>
<label value="S.3.6#05"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability for the PHR Account Holder to determine entities to which data may be exported from the PHR-S."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="PHRSFMR2-S.3.6-06"/>
<label value="S.3.6#06"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability for the PHR Account Holder to exchange information with an entity on a one-time basis."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="PHRSFMR2-S.3.6-07"/>
<label value="S.3.6#07"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability for the PHR Account Holder to exchange information with an entity on a recurring basis."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="PHRSFMR2-S.3.6-08"/>
<label value="S.3.6#08"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability for the PHR Account Holder to annotate incoming information."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="PHRSFMR2-S.3.6-09"/>
<label value="S.3.6#09"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability for the PHR Account Holder to render a notification (i.e., an acknowledgment) of the receipt or the refusal to receive information that was sent from another system."/>
</statement>
<statement>
<extension
url="http://hl7.org/ehrs/uv/phrsfmr2/StructureDefinition/requirements-dependent">
<valueBoolean value="false"/>
</extension>
<key value="PHRSFMR2-S.3.6-10"/>
<label value="S.3.6#10"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL conform to TI.1.5 (Non-Repudiation) to promote provenance regarding professionally-sourced clinical information."/>
</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