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

## : S.4.5 Manage PHR Account Holder Reminder Information Updates (Function) - XML Representation

Active as of 2024-01-31

Raw xml | Download

    <Requirements xmlns="http://hl7.org/fhir">
      <id value="PHRSFMR2-S.4.5"/>
      <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.5#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 automatically receive inbound communications from external sources (e.g., from Cancer Registries or Immunization Registries) to facilitate updating of the PHR Account Holder's reminder-related information.</p>
    </div></span>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">

                    <span>S.4.5#02</span>

                </td>
                <td style="padding-left: 4px;">

                    <span>SHOULD</span>

                </td>
                <td style="padding-left: 4px;" class="requirement">

                    <span><div><p>IF the system has received an inbound communication from an external source (e.g., from Cancer Registry or Immunization Registry) regarding reminder-related information, THEN the system SHOULD provide the ability for the PHR Account Holder to transmit an acknowledgement of that inbound communication.</p>
    </div></span>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">

                    <span>S.4.5#03</span>

                </td>
                <td style="padding-left: 4px;">

                    <span>SHOULD</span>

                </td>
                <td style="padding-left: 4px;" class="requirement">

                    <span><div><p>IF the system has received inbound communications from external sources (e.g., from Cancer Registries or Immunization Registries) regarding reminder-related information, THEN the system SHOULD provide the ability for the PHR Account Holder to maintain that reminder-related information (e.g., by reviewing, editing, storing, harmonizing, updating, or deleting the information).</p>
    </div></span>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">

                    <span>S.4.5#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 manage reminders automatically for PHR Account Holders meeting specific criteria (e.g., age, gender, or diagnosis). For example, the PHR Account Holder is a male and does not need to view reminders about annual mammograms; or the PHR Account Holder is diabetic and desires to receive and store reminders about foot examinations that will help assess circulatory health.</p>
    </div></span>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">

                    <span>S.4.5#05</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 reminders automatically to the PHR Account Holder (e.g., via email or voice message).</p>
    </div></span>

                </td>
            </tr>

            <tr>
                <td style="padding-left: 4px;">

                    <span>S.4.5#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 log reminder activity (e.g., by logging the fact the PHR-S transmitted a reminder message to the PHR Account Holder's email or mobile phone regarding an upcoming appointment).</p>
    </div></span>

                </td>
            </tr>

        </table>
    </div>
      </text>
      <url value="http://hl7.org/ehrs/Requirements/PHRSFMR2-S.4.5"/>
      <version value="0.1.0"/>
      <name value="S_4_5_Manage_PHR_Account_Holder_Reminder_Information_Updates"/>
      <title
             value="S.4.5 Manage PHR Account Holder Reminder Information Updates (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="Information from outside groups, such as immunization groups or public health organizations, may periodically have and send updates of value to PHR Account Holders. The system should be capable of generating reminders based on the recommendations of these organizations. Reminders could be provided to PHR Account Holders by a number of means, including alerts or system generated email. A record of such reminders may become part of a PHR Account Holder’s record.

    Example(s): Reminders could include a recommended immunization, prophylactic guidelines for treating Mitral Valve Prolapse disorder, or PHR Account Holder self-testing for disease."/>
      <statement>
        <key value="PHRSFMR2-S.4.5-01"/>
        <label value="S.4.5#01"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to automatically receive inbound communications from external sources (e.g., from Cancer Registries or Immunization Registries) to facilitate updating of the PHR Account Holder's reminder-related information."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-S.4.5-02"/>
        <label value="S.4.5#02"/>
        <conformance value="SHOULD"/>
        <conditionality value="true"/>
        <requirement
                     value="IF the system has received an inbound communication from an external source (e.g., from Cancer Registry or Immunization Registry) regarding reminder-related information, THEN the system SHOULD provide the ability for the PHR Account Holder to transmit an acknowledgement of that inbound communication."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-S.4.5-03"/>
        <label value="S.4.5#03"/>
        <conformance value="SHOULD"/>
        <conditionality value="true"/>
        <requirement
                     value="IF the system has received inbound communications from external sources (e.g., from Cancer Registries or Immunization Registries) regarding reminder-related information, THEN the system SHOULD provide the ability for the PHR Account Holder to maintain that reminder-related information (e.g., by reviewing, editing, storing, harmonizing, updating, or deleting the information)."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-S.4.5-04"/>
        <label value="S.4.5#04"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY provide the ability to manage reminders automatically for PHR Account Holders meeting specific criteria (e.g., age, gender, or diagnosis). For example, the PHR Account Holder is a male and does not need to view reminders about annual mammograms; or the PHR Account Holder is diabetic and desires to receive and store reminders about foot examinations that will help assess circulatory health."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-S.4.5-05"/>
        <label value="S.4.5#05"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY provide the ability to render reminders automatically to the PHR Account Holder (e.g., via email or voice message)."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-S.4.5-06"/>
        <label value="S.4.5#06"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD log reminder activity (e.g., by logging the fact the PHR-S transmitted a reminder message to the PHR Account Holder's email or mobile phone regarding an upcoming appointment)."/>
      </statement>
    </Requirements>