Eligibility verification

Eligibility answers whether enrollment is active

The CMS Uniform Glossary defines terms such as enrollee, member, and coverage. Eligibility verification applies those ideas to a specific person, product, and date.

A portal may show active coverage today while an ABA assessment is scheduled next month. The future date still needs an effective-period check. Likewise, a claim from last month requires eligibility for its own service date rather than today's status.

Eligibility and benefit verification are different steps

Eligibility verification confirms enrollment. Benefit verification asks whether the product includes a defined ABA service and under which conditions. Network participation, authorization, referral, provider enrollment, cost sharing, and claim rules add more gates.

The HealthCare.gov glossary supplies general consumer definitions. It cannot decide the member's current ABA benefit or payer configuration. Keep every verification tied to the source, product, date, and question actually answered.

Record enough evidence to reproduce the check

A useful eligibility record includes:

• legal name and other payer-required identifiers
• payer, plan, product, group, and member ID
• subscriber relationship and relevant coverage order
• effective date, termination date, and status for the service date
• plan type and product-specific routing information
• portal, electronic response, representative, or written source
• transaction or reference number, check date, and staff owner
• limitations in the response and the next recheck trigger

Store only purpose-needed information with role-based access. Resolve mismatched names, birth dates, member IDs, plan codes, and dates before the record moves to benefit or authorization work.

Recheck at meaningful events

Eligibility can shift at a new plan year, month boundary, employer change, Medicaid renewal, household event, plan switch, premium event, or retroactive update. Practices often check before intake release, authorization submission, first service, and later service dates according to payer and financial policy.

A fixed cadence alone can miss a known change. Add event-based rechecks when the family reports new coverage, a payer returns an inactive status, a claim denies for eligibility, or a product identifier changes.

For recurring ABA schedules, connect the eligibility result to the exact dates currently released. A month-level response may be enough for one payer and incomplete for another. If coverage ends midmonth, place later appointments in a separate state and contact the family before representing those visits as covered. Preserve any transition, continuity, or retroactive eligibility question for the responsible payer specialist.

Give families a scoped answer

Explain the exact finding: “The portal showed this product active for September 12 when checked on September 8.” Then state the open questions, such as ABA benefit, network, authorization, deductible, and final adjudication.

The CMS health insurance terms guide helps families understand product and cost-sharing language. A plain-language estimate should identify assumptions and the date of each source.

A fictional eligibility worklist

Kira is a fictional intake coordinator reviewing 20 scheduled first appointments. Eighteen have a payer response covering the appointment date. One response covers only the prior month, and one member ID does not match the plan record.

Date-specific eligibility completeness is 18 of 20, or 90%. The two unresolved appointments stay in the denominator and move to a hold with owners and same-day follow-up. Among the 18 complete records, benefit and authorization work continues as separate tasks.

The measure reports evidence completeness. It supplies no estimate of attendance, coverage, claim acceptance, or payment.

Respond to conflicting sources carefully

When a payer portal, electronic response, member card, family report, and representative disagree, preserve each source and timestamp. Ask the payer to resolve the product and effective period in writing when possible. Avoid overwriting the prior response, since it may explain later claim processing.

Never ask the family to solve a payer data conflict alone. Tell them what the practice can verify, what information may be needed from the subscriber, and when the next update will arrive. Use an interpreter or accessible communication method when requested.

If a claim denies for eligibility, compare the service date, member identifiers, product, payer receipt, and retroactive changes before choosing a corrected claim, payer review, family update, or another authorized route.

Measure freshness and unresolved work

Useful measures include checks completed by target; records with service-date coverage; mismatches resolved; event-trigger rechecks completed; inactive results communicated; and oldest unresolved age.

Segment by payer, product, service month, verification route, and reason. Keep active enrollment, benefit confirmation, network status, authorization, scheduled care, claim adjudication, and payment in separate fields.

Give each verification an effective date, source, representative or transaction reference, product, network, and planned service range. Reverify after enrollment, employer, plan year, product, subscriber, other coverage, provider, or location changes. Expire old results rather than carrying a generic “active” flag into future scheduling or billing.