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

## : PH.1.3 Manage PHR Account Holder and Family Preferences (Function) - XML Representation

Active as of 2024-01-31

Raw xml | Download

    <Requirements xmlns="http://hl7.org/fhir">
      <id value="PHRSFMR2-PH.1.3"/>
      <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.1.3#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 to capture, maintain, and render the PHR Account Holder's preferences (e.g., language, religion, ethnicity, spiritual practices, or cultural practices) according to organizational policy and/or jurisdictional law.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>PH.1.3#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, maintain, and render family preferences (such as preferred language, religion, spiritual practices and culture) for example, to support clinical decision making activities.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>PH.1.3#03</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 to capture, maintain, and/or render PHR Account Holder and family preferences as they pertain to current treatment plans according to user preference and/or consents, organizational policy, and/or jurisdictional law.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>PH.1.3#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 update care guidelines and options based on documented PHR Account Holder and family preferences, including clinical guidelines and treatment options (e.g., treatment for individuals who refuse blood transfusions).</p>
    </div></span>

                </td>
            </tr>

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

                    <span>PH.1.3#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 present care guidelines and options relating to documented PHR Account Holder and family preferences, including clinical guidelines and treatment options.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>PH.1.3#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 integrate PHR Account Holder preferences with appropriate health education materials (e.g., dietary advice based on dietary preference).</p>
    </div></span>

                </td>
            </tr>

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

                    <span>PH.1.3#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 integrate documentation of PHR Account Holder preferences, such as living wills, specific consents or releases, and other Advance Directives.</p>
    </div></span>

                </td>
            </tr>

        </table>
    </div>
      </text>
      <url value="http://hl7.org/ehrs/Requirements/PHRSFMR2-PH.1.3"/>
      <version value="0.1.0"/>
      <name value="PH_1_3_Manage_PHR_Account_Holder_and_Family_Preferences"/>
      <title
             value="PH.1.3 Manage PHR Account Holder and Family Preferences (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 hold certain religious or philosophical views that impact how they wish to be treated or how they might respond to treatment choices. These preferences should be captured, prominently displayed, and made available during the care process. For example, a person may hold certain preferences regarding eating certain foods (e.g., avoidance of meats; preference for vegetables); taking certain therapeutic serums derived from animals; use of a pig-valve for valve replacement; use of human or animal tissues (e.g., skin tissue or bone).

    Example(s): A religiously-based proscription of blood transfusion is a commonly encountered example of a PHR Account Holder preference."/>
      <statement>
        <key value="PHRSFMR2-PH.1.3-01"/>
        <label value="PH.1.3#01"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL provide the ability to capture, maintain, and render the PHR Account Holder's preferences (e.g., language, religion, ethnicity, spiritual practices, or cultural practices) according to organizational policy and/or jurisdictional law."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-PH.1.3-02"/>
        <label value="PH.1.3#02"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to capture, maintain, and render family preferences (such as preferred language, religion, spiritual practices and culture) for example, to support clinical decision making activities."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-PH.1.3-03"/>
        <label value="PH.1.3#03"/>
        <conformance value="SHALL"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHALL provide the ability to capture, maintain, and/or render PHR Account Holder and family preferences as they pertain to current treatment plans according to user preference and/or consents, organizational policy, and/or jurisdictional law."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-PH.1.3-04"/>
        <label value="PH.1.3#04"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to update care guidelines and options based on documented PHR Account Holder and family preferences, including clinical guidelines and treatment options (e.g., treatment for individuals who refuse blood transfusions)."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-PH.1.3-05"/>
        <label value="PH.1.3#05"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY provide the ability to present care guidelines and options relating to documented PHR Account Holder and family preferences, including clinical guidelines and treatment options."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-PH.1.3-06"/>
        <label value="PH.1.3#06"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to integrate PHR Account Holder preferences with appropriate health education materials (e.g., dietary advice based on dietary preference)."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-PH.1.3-07"/>
        <label value="PH.1.3#07"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to integrate documentation of PHR Account Holder preferences, such as living wills, specific consents or releases, and other Advance Directives."/>
      </statement>
    </Requirements>