Dependent

Dependent describes an enrollment relationship

HealthCare.gov defines dependent coverage as insurance coverage for family members of the policyholder, such as spouses, children, or partners. The exact eligible relationships, age rules, documentation, enrollment events, and continuation rights come from the governing plan and applicable law.

A dependent usually has coverage connected to a subscriber or policyholder. The dependent may have a distinct member ID, share part of the subscriber ID, or use another payer-specific format. Use the current card, portal, eligibility response, and plan source together.

Tax and insurance meanings can differ

HealthCare.gov's dependent glossary describes a tax-related meaning for Marketplace purposes. A tax dependent, insurance dependent, and household member can overlap, but they are not interchangeable in every plan or program.

Ask the payer which relationship code and supporting facts apply to the product. Avoid deciding coverage from a tax return, surname, address, custody label, or family role alone.

Keep dependent, member, and subscriber separate

The member is the person enrolled in the plan whose services are being checked. The subscriber or policyholder holds or anchors the coverage relationship under the product. The dependent is covered through an eligible relationship under that plan.

When the child receiving ABA is a dependent, the child's name, date of birth, member identifier, product, and coverage dates still matter. The subscriber's name, identifier, date of birth, group, and relationship belong in separate fields.

The patient, caregiver, emergency contact, financially responsible person, personal representative, and person authorized to consent may all be different. Dependent or subscriber status creates no universal authority to consent, access records, receive protected information, or control an appeal.

Verify the complete coverage identity

A benefit-verification record should capture:

• dependent member's legal name, date of birth, and member ID
• subscriber name, subscriber ID, and relationship
• payer, product, group, employer or sponsor when relevant
• effective and termination dates
• primary and secondary coverage order when applicable
• provider, location, network, service, code, and setting
• prior-authorization, referral, or order requirements
• source, representative or portal, reference number, and verification time

Match every field used in authorization and claims. A correct subscriber name cannot repair a wrong dependent member ID or expired product.

Coverage states remain separate

Eligibility shows that a person is enrolled under the source checked for a stated period. Benefits describe plan terms. Network status, clinical recommendation, prior authorization, claim acceptance, adjudication, and payment answer other questions.

The CMS Uniform Glossary explains that preauthorization is a plan decision about medical necessity and is not a promise that the plan will cover the cost. Confirm the actual policy and payer workflow.

A fictional dependent correction

Mira is a fictional child covered as a dependent under Sam's employer plan. Intake receives two cards. Staff compare seven fields: dependent name, dependent date of birth, member ID, subscriber, group, product, and effective period.

The older card matches Sam and the group but has an expired product and prior member ID. It matches 2 of 7 current fields. The newer card matches all seven, so identity completeness is 7 of 7.

Staff verify eligibility for Mira, then separately check ABA benefits, provider and location network status, authorization, and claim requirements. They retain both cards with received dates and mark the older one superseded. The newer card never becomes evidence of guaranteed payment.

Changes need a recheck

Dependent coverage may change after renewal, employment changes, marriage, divorce, adoption, age transitions, court action, loss of eligibility, or another enrollment event. The effective date and plan response matter more than assumptions about the event.

Reverify before an authorization request, first service, material plan change, and claim correction according to practice and payer rules. Ask for updated cards and written payer records when facts conflict.

Retain prior identifiers securely with their effective periods so older authorizations, claims, remittances, and appeals can still be matched accurately.

Explain the issue clearly to families

State which field conflicts, which source was checked, what is on hold, who owns the next action, and when the family will receive an update. Ask only for documents needed by the plan or authority.

Provide language and communication access. Avoid asking a family to resolve contradictory payer records alone. Keep timely filing, authorization, and appeal deadlines visible while corrections proceed.