Eligibility & Benefits Glossary

Start with exact identity and date

Coverage describes the benefits and protections available under a health plan or program, subject to its terms. A person's active enrollment does not establish that a particular ABA service, provider, setting, code, or date is covered.

HealthCare.gov defines health coverage broadly and maintains a public insurance glossary. Its definitions offer general orientation. The governing plan documents, payer or program records, contract, and applicable law control the case.

Record the member name and identifier, plan and product, group, relationship, coverage dates, verification timestamp, source, representative or portal reference, and exact questions asked. Preserve the response as dated evidence rather than a permanent fact.

Know when the benefit period resets

A benefit year is the period during which a plan organizes coverage and member cost-sharing rules. The HealthCare.gov benefit-year glossary says individual plans bought inside or outside the Marketplace use a January 1 through December 31 benefit year. Employer, government, and other plans may use different periods.

Store both coverage dates and the governing benefit period. A calendar-year assumption can misstate deductibles, visit limits, or authorization timing for a plan with another cycle. Recheck when the period changes, the product changes, the member adds coverage, or a payer reports a retroactive update.

Read accumulators as dated balances

An accumulator tracks progress toward a plan-defined amount or limit, such as a deductible, out-of-pocket maximum, or service quantity. The label needs a unit and scope. A dollar balance, visit count, hour count, and authorization-unit balance are separate measures.

Record the amount met, remaining amount, individual or family level, in-network or out-of-network scope, service category, benefit period, as-of date, and source. Claims still processing can change a balance. A quoted accumulator also does not prove that a future service will be covered or paid.

The CMS explanation-of-benefits guide explains how an EOB reports what was billed, what a plan paid, and what a person may owe. An EOB is a post-adjudication artifact. It can update financial evidence, while it does not replace pre-service benefit verification.

Separate authorization from benefits

HealthCare.gov's preauthorization glossary explains that preauthorization may be required before care and is not a promise that the plan will cover the cost. Eligibility, benefit coverage, medical-necessity review, network participation, prior authorization, and payment must remain separate states.

Before scheduling, identify which state the evidence supports. “Active” may refer only to enrollment. “Authorized” may apply to a defined service, dates, provider, setting, code, or quantity. “Covered” can still leave cost sharing and claim conditions unresolved.

Give the family a plain-language estimate with assumptions, known amounts, unresolved items, and a recheck trigger. Avoid presenting a portal screenshot or call reference as a guarantee.

Resolve other coverage in its own workflow

Third-party liability concerns another person, insurer, program, or entity that may be legally responsible for some or all of a claim. Medicaid's coordination-of-benefits and third-party-liability page describes Medicaid's payer-of-last-resort framework and state responsibilities within that program.

Record other coverage, effective dates, policyholder relationship, primary or secondary status, payer inquiry, coordination result, and unresolved discrepancies. A provider should not infer primacy from the card a family presents first. Follow current program and payer instructions, and route legal liability questions to qualified counsel.

Build rechecks around events

Recheck evidence when service dates cross a benefit period, an authorization expires, a member changes jobs or products, a newborn or dependent is added, other coverage appears, a payer changes its response, or a claim returns unexpected eligibility data.

Operations can collect and surface evidence. Payers and plans establish their own benefit states. Qualified clinicians make clinical recommendations. Families decide whether to proceed within the available information and applicable financial agreements.

When sources conflict, preserve both responses and pause the affected release. Ask the payer or program for written clarification through its defined route. Record who resolved the conflict, which source controlled, the effective date, and which scheduled services or estimates changed. A newer portal response may be fresher while still applying to another product, provider, or location. Recency alone does not settle scope.

A verification cohort example

A fictional practice locks 16 referrals whose two-business-day verification deadline passed. Thirteen have dated member, product, coverage, benefit-period, accumulator, network, authorization, and other-coverage findings, or 13/16, 81.3%. Ten of those 13 have every currently applicable scheduling gate cleared, or 10/13, 76.9%.

The practice reports three incomplete verifications and three completed reviews with open gates by age and reason. It does not call 10 of 13 the full cohort's coverage rate. The useful measures are review completeness and release readiness, not a promise that any later claim will pay.

Start or grow your ABA practice with Finni. Confirm current eligibility, benefits, payer coverage, security, implementation, and human-review controls during product diligence.