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.3.2 Manage PHR Conditions of Use (Function) - XML Representation

Active as of 2024-01-31

Raw xml | Download

    <Requirements xmlns="http://hl7.org/fhir">
      <id value="PHRSFMR2-S.3.2"/>
      <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.3.2#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 enter an indication of an agreement to the Conditions-of-Use when the PHR-S is initially used by the PHR Account Holder.</p>
    </div></span>

                </td>
            </tr>

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

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

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

                    <span>SHALL</span>

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

                    <span><div><p>The system SHALL render a notification to the PHR Account Holder that changes occurred to the Conditions-of-Use documents according to organizational policy and/or jurisdictional law.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>S.3.2#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 present changes that occurred to the Conditions-of-Use documents (e.g., the actual document, or an audit, or a summary, or an overview of the changes) according to organizational policy and/or jurisdictional law.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>S.3.2#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 render the Conditions-of-Use.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>S.3.2#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 provide the ability for the PHR Account Holder to render a notification to the PHR-S vendor and/or sponsor(s) as part of the process to seek redress regarding the vendor and/or sponsor‘s failure to meet performance expectations as specified in the Conditions-of-Use agreements (including reporting PHR-S errors, failures, abuse, fraud, or other issues).</p>
    </div></span>

                </td>
            </tr>

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

                    <span>S.3.2#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 a list of PHR-S administrators and personnel to receive, manage, and respond to emails and telephone calls regarding PHR-S errors, failures, abuse, fraud, or any other PHR Account Holder issues with the PHR-S Terms and Conditions-of-Use agreements.</p>
    </div></span>

                </td>
            </tr>

        </table>
    </div>
      </text>
      <url value="http://hl7.org/ehrs/Requirements/PHRSFMR2-S.3.2"/>
      <version value="0.1.0"/>
      <name value="S_3_2_Manage_PHR_Conditions_of_Use"/>
      <title value="S.3.2 Manage PHR Conditions of Use (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="The terms and conditions outline the sponsor requirements in using the application. The terms and conditions may include items such as copyright information, trademarks and intellectual property, third party links, indemnification, privacy, limitation of liability, term and termination and other miscellaneous provisions. The PHR Account Holder should be notified of the expectations of the sponsor and have the opportunity to agree to the requirements and any changes to the requirements.

    The Conditions of Use document also helps indemnify the PHR sponsor against certain misuse of the data. For example, a published article on diabetes may contain a copyright notice that forbids the storage of that article on a computer without first paying for the article. The Conditions of Use document would inform the PHR Account Holder that the sponsor does not support copyright infringement."/>
      <statement>
        <key value="PHRSFMR2-S.3.2-01"/>
        <label value="S.3.2#01"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability for the PHR Account Holder to enter an indication of an agreement to the Conditions-of-Use when the PHR-S is initially used by the PHR Account Holder."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-S.3.2-02"/>
        <label value="S.3.2#02"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL render a notification to the PHR Account Holder that changes occurred to the Conditions-of-Use documents according to organizational policy and/or jurisdictional law."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-S.3.2-03"/>
        <label value="S.3.2#03"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to present changes that occurred to the Conditions-of-Use documents (e.g., the actual document, or an audit, or a summary, or an overview of the changes) according to organizational policy and/or jurisdictional law."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-S.3.2-04"/>
        <label value="S.3.2#04"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to render the Conditions-of-Use."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-S.3.2-05"/>
        <label value="S.3.2#05"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL provide the ability for the PHR Account Holder to render a notification to the PHR-S vendor and/or sponsor(s) as part of the process to seek redress regarding the vendor and/or sponsor‘s failure to meet performance expectations as specified in the Conditions-of-Use agreements (including reporting PHR-S errors, failures, abuse, fraud, or other issues)."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-S.3.2-06"/>
        <label value="S.3.2#06"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to maintain a list of PHR-S administrators and personnel to receive, manage, and respond to emails and telephone calls regarding PHR-S errors, failures, abuse, fraud, or any other PHR Account Holder issues with the PHR-S Terms and Conditions-of-Use agreements."/>
      </statement>
    </Requirements>