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-S.2.4"/>
<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>S.2.4#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 for the authorized PHR Account Holder to render ad hoc reports of the PHR.</p>
</div></span>
Satisfied by:<ol>
<li><a href="https://www.hl7.org/fhir/measure.html">https://www.hl7.org/fhir/measure.html</a></li>
</ol>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>S.2.4#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 for the authorized PHR Account Holder to render customized reports of summarized information based on sort and filter controls for date or data range, problem, or other clinical data element or categories (e.g., medications or providers).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>S.2.4#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 maintain ad hoc reports for future retrieval and use.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>S.2.4#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 to maintain summarized information through customized reports based on prioritization of chronology, problem or other pertinent information of importance to the authorized PHR Account Holder.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>S.2.4#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 data visibility for PHR Account Holder Proxies using confidentiality-related preferences that were previously established by the PHR Account Holder for all ad hoc reporting capabilities.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>S.2.4#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 render consolidated reports across family members (e.g., children).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>S.2.4#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 conform to TI.1.1 (Entity Authorization).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>S.2.4#08</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.2 (Auditable Records).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>S.2.4#09</span>
</td>
<td style="padding-left: 4px;">
<span>MAY</span>
</td>
<td style="padding-left: 4px;" class="requirement">
<span><div><p>The system (or an external application using data from the PHR-S) MAY provide the ability to capture and maintain parameters for ad hoc reports.</p>
</div></span>
</td>
</tr>
</table>
</div>
</text>
<url value="http://hl7.org/ehrs/Requirements/PHRSFMR2-S.2.4"/>
<version value="0.1.0"/>
<name value="S_2_4_Manage_Ad_Hoc_Reporting"/>
<title value="S.2.4 Manage Ad Hoc Reporting (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="PHR Account Holders may request ad hoc, non-standard reports. The purpose is not for PHR interchange but rather for PHR Account Holder’s analysis of his/her health related financial and administrative data, and for sharing (if desired)."/>
<statement>
<key value="PHRSFMR2-S.2.4-01"/>
<label value="S.2.4#01"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability for the authorized PHR Account Holder to render ad hoc reports of the PHR."/>
<satisfiedBy value="https://www.hl7.org/fhir/measure.html"/>
</statement>
<statement>
<key value="PHRSFMR2-S.2.4-02"/>
<label value="S.2.4#02"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability for the authorized PHR Account Holder to render customized reports of summarized information based on sort and filter controls for date or data range, problem, or other clinical data element or categories (e.g., medications or providers)."/>
</statement>
<statement>
<key value="PHRSFMR2-S.2.4-03"/>
<label value="S.2.4#03"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to maintain ad hoc reports for future retrieval and use."/>
</statement>
<statement>
<key value="PHRSFMR2-S.2.4-04"/>
<label value="S.2.4#04"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to maintain summarized information through customized reports based on prioritization of chronology, problem or other pertinent information of importance to the authorized PHR Account Holder."/>
</statement>
<statement>
<key value="PHRSFMR2-S.2.4-05"/>
<label value="S.2.4#05"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL manage data visibility for PHR Account Holder Proxies using confidentiality-related preferences that were previously established by the PHR Account Holder for all ad hoc reporting capabilities."/>
</statement>
<statement>
<key value="PHRSFMR2-S.2.4-06"/>
<label value="S.2.4#06"/>
<conformance value="MAY"/>
<conditionality value="false"/>
<requirement
value="The system MAY provide the ability to render consolidated reports across family members (e.g., children)."/>
</statement>
<statement>
<key value="PHRSFMR2-S.2.4-07"/>
<label value="S.2.4#07"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD conform to TI.1.1 (Entity Authorization)."/>
</statement>
<statement>
<key value="PHRSFMR2-S.2.4-08"/>
<label value="S.2.4#08"/>
<conformance value="SHALL"/>
<conditionality value="false"/>
<requirement
value="The system SHALL conform to TI.2 (Auditable Records)."/>
</statement>
<statement>
<key value="PHRSFMR2-S.2.4-09"/>
<label value="S.2.4#09"/>
<conformance value="MAY"/>
<conditionality value="false"/>
<requirement
value="The system (or an external application using data from the PHR-S) MAY provide the ability to capture and maintain parameters for ad hoc reports."/>
</statement>
</Requirements>