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.6.1 PHR Account Holder Health Data Derived from Administrative and Financial Sources (Function) - XML Representation

Active as of 2024-01-31

Raw xml | Download

    <Requirements xmlns="http://hl7.org/fhir">
      <id value="PHRSFMR2-PH.6.1"/>
      <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.6.1#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 and maintain information related to financial data and the current balances from the PHR Account Holder’s health-related financial accounts.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>PH.6.1#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 a request for the correction (e.g., if the data is known to be incorrect) and/or annotation (e.g., if another opinion exists regarding the correctness of the data) of the administrative or financial data.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>PH.6.1#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 capture financial details and link those details to each clinical encounter or billable service (e.g., charges, allowed charges, or payments made by an insurance plan or by the PHR Account Holder).</p>
    </div></span>

                </td>
            </tr>

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

                    <span>PH.6.1#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 for the PHR Account Holder to render financial and administrative data and the data about those health-related accounts.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>PH.6.1#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 a notification to the PHR Account Holder of any changes to the financial data or health-related accounts.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>PH.6.1#06</span>

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

                    <span>SHALL</span>

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

                    <span><div><p>IF health data is derived from administrative and financial data, THEN the system SHALL provide the ability to capture data about, and a reference to, the source of the health data.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>PH.6.1#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 metadata about certain PHR Account Holder's health data that was derived from administrative and financial data, and link that metadata with the corresponding health data. For example, the fact that the PHR Account Holder broke a leg could be derived from an invoice from an insurance company that describes a procedure performed at the provider's site of a pin being inserted into a leg; the derived health data (the fact about the broken leg) needs to be associated with the financial data (the invoice) and with administrative data (the provider's site).</p>
    </div></span>

                </td>
            </tr>

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

                    <span>PH.6.1#08</span>

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

                    <span>SHALL</span>

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

                    <span><div><p>IF certain health data was derived from administrative and financial data, THEN the system SHALL provide the ability to render that health data to Authorized PHR Users, including metadata regarding the administrative and financial data from which that health data was derived.</p>
    </div></span>

                </td>
            </tr>

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

                    <span>PH.6.1#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 render information from interactions with the PHR Account Holder's insurance coverage systems (e.g., employer’s benefit system or the insurance company’s benefit information system).</p>
    </div></span>

                </td>
            </tr>

        </table>
    </div>
      </text>
      <url value="http://hl7.org/ehrs/Requirements/PHRSFMR2-PH.6.1"/>
      <version value="0.1.0"/>
      <name
            value="PH_6_1_PHR_Account_Holder_Health_Data_Derived_from_Administrative_and_Financial_Sources"/>
      <title
             value="PH.6.1 PHR Account Holder Health Data Derived from Administrative and Financial Sources (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="Tracking the personal costs of healthcare can be complex. Charges are typically discounted by the insurance plan to allowed charges. They will pay a portion of allowed charges with the PHR Account Holder being responsible for the rest. A given encounter such as a hospitalization will have multiple charges from several providers. Capturing the Explanation Of Benefits from the insurance plan can help monitor the expenses.

    Example(s): The system should capture charge information and payment data from the Explanation Of Benefits (EOB) and associate it with the encounter records stored in the PHR-S."/>
      <statement>
        <key value="PHRSFMR2-PH.6.1-01"/>
        <label value="PH.6.1#01"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to capture and maintain information related to financial data and the current balances from the PHR Account Holder’s health-related financial accounts."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-PH.6.1-02"/>
        <label value="PH.6.1#02"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to capture a request for the correction (e.g., if the data is known to be incorrect) and/or annotation (e.g., if another opinion exists regarding the correctness of the data) of the administrative or financial data."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-PH.6.1-03"/>
        <label value="PH.6.1#03"/>
        <conformance value="SHOULD"/>
        <conditionality value="false"/>
        <requirement
                     value="The system SHOULD provide the ability to capture financial details and link those details to each clinical encounter or billable service (e.g., charges, allowed charges, or payments made by an insurance plan or by the PHR Account Holder)."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-PH.6.1-04"/>
        <label value="PH.6.1#04"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY provide the ability for the PHR Account Holder to render financial and administrative data and the data about those health-related accounts."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-PH.6.1-05"/>
        <label value="PH.6.1#05"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY provide the ability to render a notification to the PHR Account Holder of any changes to the financial data or health-related accounts."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-PH.6.1-06"/>
        <label value="PH.6.1#06"/>
        <conformance value="SHALL"/>
        <conditionality value="true"/>
        <requirement
                     value="IF health data is derived from administrative and financial data, THEN the system SHALL provide the ability to capture data about, and a reference to, the source of the health data."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-PH.6.1-07"/>
        <label value="PH.6.1#07"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY provide the ability to capture metadata about certain PHR Account Holder's health data that was derived from administrative and financial data, and link that metadata with the corresponding health data. For example, the fact that the PHR Account Holder broke a leg could be derived from an invoice from an insurance company that describes a procedure performed at the provider's site of a pin being inserted into a leg; the derived health data (the fact about the broken leg) needs to be associated with the financial data (the invoice) and with administrative data (the provider's site)."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-PH.6.1-08"/>
        <label value="PH.6.1#08"/>
        <conformance value="SHALL"/>
        <conditionality value="true"/>
        <requirement
                     value="IF certain health data was derived from administrative and financial data, THEN the system SHALL provide the ability to render that health data to Authorized PHR Users, including metadata regarding the administrative and financial data from which that health data was derived."/>
      </statement>
      <statement>
        <key value="PHRSFMR2-PH.6.1-09"/>
        <label value="PH.6.1#09"/>
        <conformance value="MAY"/>
        <conditionality value="false"/>
        <requirement
                     value="The system MAY provide the ability to render information from interactions with the PHR Account Holder's insurance coverage systems (e.g., employer’s benefit system or the insurance company’s benefit information system)."/>
      </statement>
    </Requirements>