Member

Member identifies the covered person

The CMS Uniform Glossary provides standard health-coverage terms and emphasizes that plan documents govern when definitions differ. In everyday payer operations, “member” or “enrollee” points to the individual enrolled under a plan or program.

The HealthCare.gov health-coverage definition describes a legal entitlement to payment or reimbursement under insurance, an employer plan, or a government program. The member record connects that coverage arrangement to the person and applicable dates.

Member and subscriber can be different people

The subscriber or policyholder is often the person who enrolls in the plan or holds the contract. A spouse or child may be a dependent member under that subscriber. In Medicaid, the member may have an individual case and assigned managed-care plan without a commercial policyholder structure.

For each person receiving ABA services, capture the member's own name, date of birth, member ID, product, and eligibility span. Keep the subscriber name, subscriber ID, and relationship in separate fields.

Coverage identity and legal authority are separate

A member can be a minor or an adult who has another person involved in care. A parent, caregiver, emergency contact, subscriber, and authorized representative may hold different rights. Coverage status alone does not establish who may consent to care, access records, receive protected information, file an appeal, or control communications.

Verify the governing authority for the action at hand. Store relationship labels, legal authority, privacy route, and payer representation separately. Offer communication and disability access to the member throughout intake, assessment, authorization, and service.

Match the member to the exact product and date

A usable coverage record includes:

• legal and preferred name plus date of birth
• member ID and any program-specific identifier
• subscriber, policyholder, or case relationship
• payer, administrator, product, network, and group
• eligibility start, termination, and renewal dates
• ABA benefit and age-specific rules
• provider network, referral, and authorization state
• cost-sharing and accumulator information
• claim, notice, grievance, and appeal channels
• source, verification date, reference number, and recheck trigger

The CMS health-insurance terms guide explains common concepts such as insured person, network provider, cost sharing, and the No Surprises Act. Plan documents and program rules supply the member-specific result.

A member card is a starting point

A card can provide member and group IDs, payer contacts, routing values, and plan labels. It may omit the complete product name, behavioral-health administrator, ABA benefit, service network, or current eligibility. Cards can also remain in a family's files after coverage ends.

Confirm information through the payer's approved source and record the service date being checked. When the portal, card, family report, and claim response disagree, preserve each item and seek written clarification.

A fictional member match

Samira's fictional family uploads two insurance cards during ABA intake. One belongs to the child under the current employer plan. The other is a parent's expired individual policy.

Staff review six matching fields across both cards: person, member ID, subscriber, product, group, and effective period. The current card matches all six. The expired card matches only the family surname.

Current-record matching is 6 of 6, or 100% for the child's card. That ratio measures identity and product evidence. It supplies no answer about ABA benefits, network, authorization, member cost, or claim payment.

Keep member communications understandable

Tell the family which person, product, and date were verified. Explain open items in plain language and use the requested channel, interpreter, large print, AAC, or other access support. Avoid sharing one family member's coverage details with another person unless the applicable authority and privacy route permit it.

Recheck after a new card, birthday, plan renewal, employment change, Medicaid redetermination, move, plan switch, eligibility denial, or payer rejection. Retain prior identities for older service dates and appeals.

Prevent duplicate and merged member records

Names, twins, suffixes, changed surnames, and reused family contact details can cause record-matching errors. Use the payer's required combination of identifiers and ask the family to confirm discrepancies. Keep preferred names and communication preferences alongside the legal values used for payer transactions.

When two records appear to represent one person, place a review hold before merging clinical, billing, or authorization data. Confirm the source record, plan, service dates, and responsible owner. A safe merge preserves the original identifiers and audit history. It also protects siblings from having each other's diagnoses, authorizations, or claims attached to the wrong chart.

Match the member identifier, name, date of birth, subscriber relationship, product, group, effective dates, and service date before discussing benefits. Separately verify consent, records access, representation, appeal, and financial authority. A caregiver, subscriber, emergency contact, and authorized representative may be different people.