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.2.2 Manage Health Insurance Plan Benefit Information (Function) - XML Representation

Active as of 2024-01-31

Raw xml | Download

    <Requirements xmlns="http://hl7.org/fhir">
      <id value="PHRSFMR2-S.2.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.2.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 to capture selected insurance benefit information that is pertinent to the PHR Account Holder's needs.</p>
    </div></span>

                    Satisfied by:<ol>

                        <li><a href="https://www.hl7.org/fhir/insuranceplan.html">https://www.hl7.org/fhir/insuranceplan.html</a></li>

                    </ol>

                </td>
            </tr>

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

                    <span>S.2.2#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 maintain the selected health insurance benefit information.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>S.2.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 for the PHR Account Holder to capture and render updates made to selected insurance plan benefit information that is pertinent to the PHR Account Holder's needs. For example, the PHR Account Holder might receive information regarding changes in deductible amounts, categories of coverage (e.g., new medicines or new therapies being covered), terms-of-coverage (e.g., changes in co-pay amounts), prior authorization requirements, and updates to the list of health care providers that are within the insurance carrier's network (including specific facilities and providers).</p>
    </div></span>

                </td>
            </tr>

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

                    <span>S.2.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 manage health insurance benefit information from multiple payer sources.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>S.2.2#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 link to the health insurance benefit PHR-S as the source for multiple categories of account distributions which may be related to the varied financial implications of funds usage in accounts (such as Consumer-Directed Health Plans).</p>
    </div></span>

                </td>
            </tr>

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

                    <span>S.2.2#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 manage multiple categories of account distributions which may be related to the varied financial implications of funds usage in accounts (such as Consumer-Directed Health Plans).</p>
    </div></span>

                </td>
            </tr>

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

                    <span>S.2.2#07</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 capture preauthorization requirements for medications and health services specific to the PHR Account Holder’s policies.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>S.2.2#08</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 capture, store, and render referral requirements. Note: Referral requirements are those requirements that must be met by a healthcare provider as specified by the healthcare payer or a care-coordinating entity. A care-coordinating entity consists of a group of healthcare professionals who have formally agreed to manage the healthcare of a patient.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>S.2.2#09</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 capture and present an indication that an insurance coverage / benefit / deductible-amount / co-pay amount has changed (e.g., by receiving a notice from an insurance providers of the existence of a new benefit, an expired benefit, or a changed benefit.)</p>
    </div></span>

                </td>
            </tr>

        </table>
    </div>
      </text>
      <url value="http://hl7.org/ehrs/Requirements/PHRSFMR2-S.2.2"/>
      <version value="0.1.0"/>
      <name value="S_2_2_Manage_Health_Insurance_Plan_Benefit_Information"/>
      <title
             value="S.2.2 Manage Health Insurance Plan Benefit Information (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="Robust management features allow the PHR Account Holder to actively maintain their health insurance benefits information for selected benefits related to PHR Account Holder coverage needs. Over an extended period of time, with the likelihood of multiple insurance providers, it may be important for there to be information management capability for the varied payer sources, varied levels of benefit information, and varied levels of coverage including allowed coverages, exclusions, and limitations on specific coverages. Information management capabilities may include analytics regarding the PHR Account Holder's desired care such as: the selection of the most appropriate insurance plan for the current disease or injury; or the amount of deductibles that can be expected under varying insurance plans. Out-of-date or non-current insurance plan and benefit information can be used to compare different benefit packages, costs, and/or expenses over time resulting in a better understanding of health care as it pertains to health insurance coverage."/>
      <statement>
        <key value="PHRSFMR2-S.2.2-01"/>
        <label value="S.2.2#01"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to capture selected insurance benefit information that is pertinent to the PHR Account Holder's needs."/>
        <satisfiedBy value="https://www.hl7.org/fhir/insuranceplan.html"/>
      </statement>
      <statement>
        <key value="PHRSFMR2-S.2.2-02"/>
        <label value="S.2.2#02"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to maintain the selected health insurance benefit information."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-S.2.2-03"/>
        <label value="S.2.2#03"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability for the PHR Account Holder to capture and render updates made to selected insurance plan benefit information that is pertinent to the PHR Account Holder's needs. For example, the PHR Account Holder might receive information regarding changes in deductible amounts, categories of coverage (e.g., new medicines or new therapies being covered), terms-of-coverage (e.g., changes in co-pay amounts), prior authorization requirements, and updates to the list of health care providers that are within the insurance carrier's network (including specific facilities and providers)."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-S.2.2-04"/>
        <label value="S.2.2#04"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to manage health insurance benefit information from multiple payer sources."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-S.2.2-05"/>
        <label value="S.2.2#05"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY provide the ability to link to the health insurance benefit PHR-S as the source for multiple categories of account distributions which may be related to the varied financial implications of funds usage in accounts (such as Consumer-Directed Health Plans)."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-S.2.2-06"/>
        <label value="S.2.2#06"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY provide the ability to manage multiple categories of account distributions which may be related to the varied financial implications of funds usage in accounts (such as Consumer-Directed Health Plans)."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-S.2.2-07"/>
        <label value="S.2.2#07"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY provide the ability to capture preauthorization requirements for medications and health services specific to the PHR Account Holder’s policies."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-S.2.2-08"/>
        <label value="S.2.2#08"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY provide the ability to capture, store, and render referral requirements. Note: Referral requirements are those requirements that must be met by a healthcare provider as specified by the healthcare payer or a care-coordinating entity. A care-coordinating entity consists of a group of healthcare professionals who have formally agreed to manage the healthcare of a patient."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-S.2.2-09"/>
        <label value="S.2.2#09"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY provide the ability to capture and present an indication that an insurance coverage / benefit / deductible-amount / co-pay amount has changed (e.g., by receiving a notice from an insurance providers of the existence of a new benefit, an expired benefit, or a changed benefit.)"/>
      </statement>
    </Requirements>