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.4.6.6"/>
<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.4.6.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 for the PHR Account Holder to manage participation in public health surveys from local, state and federal agencies.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>S.4.6.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 capture administrative information necessary to enroll in public health surveys.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>S.4.6.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 determine public health surveys that apply to the PHR Account Holder according to the PHR Account Holder's preferences and/or consents, organizational policy, and/or jurisdictional law.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>S.4.6.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 to capture PHR Account Holder responses to public health surveys.</p>
</div></span>
</td>
</tr>
</table>
</div>
</text>
<url value="http://hl7.org/ehrs/Requirements/PHRSFMR2-S.4.6.6"/>
<version value="0.1.0"/>
<name value="S_4_6_6_Enrollment_in_Public_Health_Surveys"/>
<title value="S.4.6.6 Enrollment in Public Health Surveys (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 Account Holder will have the ability to participate in public health surveys and store their responses to those surveys.
Example(s): The World Health Organization offers a survey to research the number of smokers who also have a specific related disease."/>
<statement>
<key value="PHRSFMR2-S.4.6.6-01"/>
<label value="S.4.6.6#01"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability for the PHR Account Holder to manage participation in public health surveys from local, state and federal agencies."/>
</statement>
<statement>
<key value="PHRSFMR2-S.4.6.6-02"/>
<label value="S.4.6.6#02"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to capture administrative information necessary to enroll in public health surveys."/>
</statement>
<statement>
<key value="PHRSFMR2-S.4.6.6-03"/>
<label value="S.4.6.6#03"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to determine public health surveys that apply to the PHR Account Holder according to the PHR Account Holder's preferences and/or consents, organizational policy, and/or jurisdictional law."/>
</statement>
<statement>
<key value="PHRSFMR2-S.4.6.6-04"/>
<label value="S.4.6.6#04"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to capture PHR Account Holder responses to public health surveys."/>
</statement>
</Requirements>