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
| Active as of 2024-01-31 |
<Requirements xmlns="http://hl7.org/fhir">
<id value="PHRSFMR2-S.2.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>S.2.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 health insurance benefit information.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>S.2.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 render health insurance benefit information.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>S.2.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 manage multiple payer sources of health insurance benefits information.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>S.2.1#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 capture insurance type (e.g., medical or dental).</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>S.2.1#05</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 insurer(s) contact information.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>S.2.1#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 for a PHR Account Holder to determine and present estimated PHR Account Holder responsibility and insurance covered costs for an healthcare-related event.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>S.2.1#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 for a PHR Account Holder to determine and present final PHR Account Holder responsibility and insurance determination for an event.</p>
</div></span>
</td>
</tr>
<tr>
<td style="padding-left: 4px;">
<span>S.2.1#08</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 store, determine, and present (i.e., track) multiple categories of account distributions related to the varied financial implications of funds usage in Consumer-Directed Health Plan (CDHP) accounts according to the PHR Account Holder's authorization, organizational policy, and/or jurisdictional law.</p>
</div></span>
</td>
</tr>
</table>
</div>
</text>
<url value="http://hl7.org/ehrs/Requirements/PHRSFMR2-S.2.1"/>
<version value="0.1.0"/>
<name
value="S_2_1_Capture_and_Read_Health_Insurance_Account_and_Benefit_Information"/>
<title
value="S.2.1 Capture and Read Health Insurance Account and 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="PHR Account Holders may want to centralize administrative information related to the insurance accounts that he/she participate in. Administrative information such as group, group number, policy number, member identification number, effective and termination dates, probationary periods, pre-existing condition constraints, prior authorization or referral requirements and others are important data for provider offices for billing purposes. Current and prior insurance coverage information is important for correct billing and payment. Detail of multiple coverages allows for coordination of benefits information to be easily provided.
The ability to capture information of separate riders such as extra major medical coverage or cancer specific coverages in addition to routine benefit plans assists the PHR Account Holder in better knowledge and utilization of the financial resources available for payments. The system should allow the PHR Account Holder to display patient responsibility and benefit plan covered costs – both estimated and final – for a given event (e.g., test, procedure, surgery, or provider appointment).
In newer plan types such as Consumer Directed Health Plans (CDHP), this information will help the PHR Account Holder determine the financial implications of his/her treatment options, alternative treatment options and provide information that may be needed by the provider."/>
<statement>
<key value="PHRSFMR2-S.2.1-01"/>
<label value="S.2.1#01"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to capture health insurance benefit information."/>
</statement>
<statement>
<key value="PHRSFMR2-S.2.1-02"/>
<label value="S.2.1#02"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to render health insurance benefit information."/>
</statement>
<statement>
<key value="PHRSFMR2-S.2.1-03"/>
<label value="S.2.1#03"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to manage multiple payer sources of health insurance benefits information."/>
</statement>
<statement>
<key value="PHRSFMR2-S.2.1-04"/>
<label value="S.2.1#04"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD capture insurance type (e.g., medical or dental)."/>
</statement>
<statement>
<key value="PHRSFMR2-S.2.1-05"/>
<label value="S.2.1#05"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to capture insurer(s) contact information."/>
</statement>
<statement>
<key value="PHRSFMR2-S.2.1-06"/>
<label value="S.2.1#06"/>
<conformance value="MAY"/>
<conditionality value="false"/>
<requirement
value="The system MAY provide the ability for a PHR Account Holder to determine and present estimated PHR Account Holder responsibility and insurance covered costs for an healthcare-related event."/>
</statement>
<statement>
<key value="PHRSFMR2-S.2.1-07"/>
<label value="S.2.1#07"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability for a PHR Account Holder to determine and present final PHR Account Holder responsibility and insurance determination for an event."/>
</statement>
<statement>
<key value="PHRSFMR2-S.2.1-08"/>
<label value="S.2.1#08"/>
<conformance value="SHOULD"/>
<conditionality value="false"/>
<requirement
value="The system SHOULD provide the ability to store, determine, and present (i.e., track) multiple categories of account distributions related to the varied financial implications of funds usage in Consumer-Directed Health Plan (CDHP) accounts according to the PHR Account Holder's authorization, organizational policy, and/or jurisdictional law."/>
</statement>
</Requirements>