Benefit verification

Verification separates several coverage questions

The HealthCare.gov benefits glossary says covered benefits and excluded services come from plan documents, while Medicaid and CHIP benefits come from state program rules. The manifest-provided CMS Uniform Glossary also warns that its educational definitions can differ from plan terms.

A useful verification keeps these states separate:

• Eligibility: whether the person appears enrolled in the named product for the relevant date.
• Benefit: whether current sources describe the proposed service as covered, excluded, or conditional.
• Network: whether the provider, group, location, and service configuration participate for that product and date.
• Prior authorization or referral: whether another approval or order is required before the service or claim.
• Cost sharing: the deductible, copayment, coinsurance, out-of-pocket status, and any benefit-specific rule reported by the source.
• Claim payment: the payer's later adjudication of the actual submitted service.

One “verified” checkbox cannot show which question was answered. Give each field its own value, evidence, timestamp, owner, and recheck trigger.

Verify the exact ABA configuration

Record:

1. member name, member ID, date of birth, and relationship to subscriber
2. payer, product, group, plan year, and coverage effective dates
3. requested service, code when applicable, provider type, setting, modality, and location
4. participating status for the individual, group, tax identity, and site as required
5. covered-benefit language, exclusions, age or diagnosis terms, and visit or unit limits
6. referral, order, assessment, prior-authorization, or treatment-plan requirement
7. deductible, amount met, copayment, coinsurance, out-of-pocket limit, and accumulators
8. coordination-of-benefits question and other coverage reported
9. source, portal result, representative, call reference, date, time, and limitations

Ask the payer to explain ambiguous terms in writing. Save the portal evidence or call note with the source version. A general provider directory, family insurance card, or prior payment supplies only part of the record.

Authorization and verification remain distinct

HealthCare.gov's preauthorization entry describes a plan decision about medical necessity and states that preauthorization does not promise cost coverage. A benefit verification may identify that authorization is required. It does not supply that authorization.

Likewise, authorization cannot freeze eligibility, network status, cost sharing, coding rules, or benefits through every future date. Recheck fields that can change before assessment, first service, a new plan year, a provider or location change, and claim release.

A qualified clinician decides clinical appropriateness and recommendation within scope. Benefits staff report payer evidence. The plan controls its own coverage and adjudication. Families receive a plain-language estimate with assumptions and a route for questions.

A fictional verification and estimate

Lena's family asks about a proposed in-network ABA assessment on October 6. A dated payer response reports active coverage, an ABA assessment benefit, prior authorization required, a $1,500 deductible with $900 met, and 20% coinsurance after the deductible. The practice separately confirms provider and location participation.

The remaining deductible is $1,500 − $900 = $600. If the allowed amount for the assessment claim were $120 and every other requirement cleared, the full $120 could be assigned to Lena's deductible. After the deductible is met, a later covered claim with a $120 allowed amount could assign $120 × 20% = $24 in coinsurance.

Those figures are conditional examples. The verification has no final allowed amount for an unsubmitted claim and cannot establish future accumulator balances. The family estimate names the assumed allowed amount, plan response date, deductible status, network configuration, authorization requirement, and exclusions from the estimate.

Recheck when a material fact changes

Useful triggers include a new calendar or plan year, coverage renewal, employer change, secondary insurance update, provider roster change, new site, service or code change, authorization expiration, and payer-policy revision. Also recheck after a portal response conflicts with a notice, contract, or call.

The CMS health-insurance terms guide distinguishes allowed amount, cost sharing, EOB, network status, and balance billing. Its examples help explain estimates while leaving the member's plan as the controlling source. The manifest-provided HealthCare.gov glossary index offers the same kind of educational orientation.

Measure completed verifications and open gaps

Suppose 25 requested verifications reach their due date in a week. Twenty-two contain every required source, product, service, network, benefit, cost-sharing, authorization, and timestamp field. Completeness is 22 of 25, or 88%.

Before first service, 20 of those 22 receive the required change-trigger recheck. Recheck completion is 20 of 22, or 90.9%. Keep the five incomplete or unrechecked records on hold with reason, owner, age, and escalation. Report source conflicts and payer corrections separately.