Personal Health Record System Functional Model, Release 2
0.1.0 - CI Build
Personal Health Record System Functional Model, Release 2 - Local Development build (v0.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
| Active as of 2024-01-31 |
<Requirements xmlns="http://hl7.org/fhir">
<id value="PHRSFMR2-PH.3.1.1"/>
<meta>
<profile value="http://hl7.org/ehrs/StructureDefinition/FMFunction"/>
</meta>
<text>
<status value="extensions"/>
<div xmlns="http://www.w3.org/1999/xhtml">
<table id="statements" class="grid dict">
<tr>
<td style="padding-left: 4px;">
<span>PH.3.1.1#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 provide the ability for the PHR Account Holder to capture self-generated health observations (e.g., symptoms, vital signs, physical observations, direct-to-consumer laboratory studies, home health devices, (e.g., a blood sugar measurement device or a telemetric cardiac measurement device)).</p>
</div></span>
Satisfied by:<ol>
<li><a href="https://www.hl7.org/fhir/composition.html">https://www.hl7.org/fhir/composition.html</a></li>
</ol>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>PH.3.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 capture the PHR Account Holder's self-measured and externally-sourced vital signs (e.g., blood pressure, temperature, heart rate, respiratory rate, and severity of pain) according to organizational policy and/or jurisdictional law.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>PH.3.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 capture other self-reported clinical measures (e.g., peak expiratory flow rate, size of lesions, or oxygen saturation) as discrete elements of structured or unstructured data.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>PH.3.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 capture the PHR Account Holder's self-reported mental health status according to organizational policy (e.g., using certain privacy and security protections). For example, the PHR Account Holder might note that the medication that has been prescribed by his physician is causing feelings of anger and depression (and suicidal ideation). If the PHR Account Holder shares that information with a healthcare organization, that organization might note that the PHR Account Holder's self-reported mental health status must be masked for members of the care team who do not have explicit permissions to view that data (i.e., only authorized health care provider(s)). The vendor organization that hosts the PHR system software might have a policy that states that that the PHR Account Holder's self-reported mental health status will not be exported without explicit consents and/or authorizations by the PHR Account Holder.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>PH.3.1.1#05</span>
</td>
<td style="padding-left: 4px;">
<span>SHOULD</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>IF the system provides the ability to capture the PHR Account Holder's self-reported mental health status, THEN the system SHOULD provide the ability to capture corresponding consents and/or authorizations regarding the transmission of the PHR Account Holder's self-reported mental health status information according to organizational policy and/or jurisdictional law.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>PH.3.1.1#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 maintain educational information that can be used by the PHR Account Holder to understand his or her condition(s).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>PH.3.1.1#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 to maintain educational information that can be used by the PHR Account Holder to understand and choose from various self-care options.</p>
</div></span>
</td>
</tr>
</table>
</div>
</text>
<url value="http://hl7.org/ehrs/Requirements/PHRSFMR2-PH.3.1.1"/>
<version value="0.1.0"/>
<name value="PH_3_1_1_Manage_Personal_Observations_and_Care"/>
<title value="PH.3.1.1 Manage Personal Observations and Care (Function)"/>
<status value="active"/>
<date value="2024-01-31T14:45:34+00:00"/>
<publisher value="EHR WG"/>
<contact>
<telecom>
<system value="url"/>
<value value="http://www.hl7.org/Special/committees/ehr"/>
</telecom>
</contact>
<description
value="A PHR system can help a PHR Account Holder capture and maintain self-generated health observational information. That observational information can appear in structured and unstructured formats and/or as several media types. of observational methods could include structured or unstructured text documents, audio files from telephone devices, calendar entries, text messages, scanned or digital images (including photographs), and personal drawings.
Example(s): The system SHALL capture Account Holder's self-reported health observations such as symptoms, vital signs and other physical conditions."/>
<statement>
<key value="PHRSFMR2-PH.3.1.1-01"/>
<label value="PH.3.1.1#01"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL provide the ability for the PHR Account Holder to capture self-generated health observations (e.g., symptoms, vital signs, physical observations, direct-to-consumer laboratory studies, home health devices, (e.g., a blood sugar measurement device or a telemetric cardiac measurement device))."/>
<satisfiedBy value="https://www.hl7.org/fhir/composition.html"/>
</statement>
<statement>
<key value="PHRSFMR2-PH.3.1.1-02"/>
<label value="PH.3.1.1#02"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to capture the PHR Account Holder's self-measured and externally-sourced vital signs (e.g., blood pressure, temperature, heart rate, respiratory rate, and severity of pain) according to organizational policy and/or jurisdictional law."/>
</statement>
<statement>
<key value="PHRSFMR2-PH.3.1.1-03"/>
<label value="PH.3.1.1#03"/>
<conformance value="MAY"/>
<conditionality value="false"/>
<requirement
value="The system MAY capture other self-reported clinical measures (e.g., peak expiratory flow rate, size of lesions, or oxygen saturation) as discrete elements of structured or unstructured data."/>
</statement>
<statement>
<key value="PHRSFMR2-PH.3.1.1-04"/>
<label value="PH.3.1.1#04"/>
<conformance value="MAY"/>
<conditionality value="false"/>
<requirement
value="The system MAY provide the ability to capture the PHR Account Holder's self-reported mental health status according to organizational policy (e.g., using certain privacy and security protections). For example, the PHR Account Holder might note that the medication that has been prescribed by his physician is causing feelings of anger and depression (and suicidal ideation). If the PHR Account Holder shares that information with a healthcare organization, that organization might note that the PHR Account Holder's self-reported mental health status must be masked for members of the care team who do not have explicit permissions to view that data (i.e., only authorized health care provider(s)). The vendor organization that hosts the PHR system software might have a policy that states that that the PHR Account Holder's self-reported mental health status will not be exported without explicit consents and/or authorizations by the PHR Account Holder."/>
</statement>
<statement>
<key value="PHRSFMR2-PH.3.1.1-05"/>
<label value="PH.3.1.1#05"/>
<conformance value="SHOULD"/>
<conditionality value="true"/>
<requirement
value="IF the system provides the ability to capture the PHR Account Holder's self-reported mental health status, THEN the system SHOULD provide the ability to capture corresponding consents and/or authorizations regarding the transmission of the PHR Account Holder's self-reported mental health status information according to organizational policy and/or jurisdictional law."/>
</statement>
<statement>
<key value="PHRSFMR2-PH.3.1.1-06"/>
<label value="PH.3.1.1#06"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to maintain educational information that can be used by the PHR Account Holder to understand his or her condition(s)."/>
</statement>
<statement>
<key value="PHRSFMR2-PH.3.1.1-07"/>
<label value="PH.3.1.1#07"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to maintain educational information that can be used by the PHR Account Holder to understand and choose from various self-care options."/>
</statement>
</Requirements>