Insurance Eligibility Verification Checklist for Clinics

January creates the obvious pile. Plans reset, cards change, and tomorrow’s schedule still looks exactly like December’s. The quieter version happens every week: one transposed member ID, one expired referral, one payer response saved with no date.

Eligibility verification works better as an exception queue than as a green check beside every appointment. Capture the evidence once. Put uncertain cases in view. Give each one an owner before the patient reaches the desk.

Start with a verification workboard

INSURANCE ELIGIBILITY WORKBOARD

Patient and appointment ID: ______________________________
Date and planned service category: _______________________

Member name and ID checked against source: ______________
Date of birth and relationship to subscriber: ___________
Payer and plan: __________________________________________

Inquiry source and reference: ____________________________
Inquiry date and time: ___________________________________
Coverage dates returned: _________________________________
Coverage status for planned date: ________________________

Relevant benefit details returned: _______________________
Network information returned: ____________________________
Referral requirement: ____________________________________
Prior-authorization signal: ______________________________
Coordination-of-benefits question: _______________________

Status: Clear / Needs patient input / Needs payer review /
        Referral or authorization work / Escalated
Owner: __________________________ Due: ____________________
Evidence location: ________________________________________
Patient communication: ___________________________________

The workboard records what came back. It does not promise what the payer will do with a future claim.

Know what the transaction answers

CMS describes HETS as a system that accepts HIPAA-compliant 270 eligibility requests and returns 271 responses for Medicare. CMS’s 270/271 companion guidance identifies the 270 as the inquiry and the 271 as the response.

Commercial payer portals and clearinghouses may expose the same transaction family through different screens. Save the response or reference permitted by policy, along with the date, planned date of service, and user. A copied sentence in an appointment note is weak evidence because it loses the source and timing.

Verify identity before interpreting benefits

Many failures begin before coverage. Compare the patient-entered details, card, registration record, and payer response under the practice’s identity procedure.

Check:

• spelling and approved identifiers;
• member and group numbers;
• subscriber name and relationship;
• payer and product name;
• old card versus current card;
• effective and termination dates;
• whether another plan may be primary.

Do not merge two patients because their names resemble each other. Do not replace an old insurance record without preserving which claims or appointments used it.

Read the response for the scheduled work

“Active” is not a complete answer. The response must be read against the date and planned service category.

Look for returned information on network, copay, deductible, coinsurance, limits, referral requirements, or authorization signals that matter to the appointment. The exact response varies. When the data is absent or unclear, say that. Do not manufacture a zero balance or a covered-service promise.

The patient-facing sentence should be careful: the practice verified the information shown by the named source at a named time. Eligibility and benefits are not a guarantee of payment. Final responsibility depends on the claim and applicable plan rules.

Work exceptions by type

One red queue is noisy. Split it.

Exception	Next owner	Evidence needed
Member not found	Registration or patient contact	Card, identifiers, payer confirmation
Inactive for planned date	Patient contact and billing review	Coverage dates and alternate plan
Network unclear	Contract or payer-review owner	Plan, provider, location, payer response
Referral required	Referral desk	Referring provider, order or referral, validity
Authorization signal	Authorization team	Planned service, payer rule, submission status
Other coverage indicated	Coordination-of-benefits owner	Primary and secondary plan facts
Response unavailable	Supervisor or downtime lane	Attempt log and approved fallback

Do not use a generic “insurance issue” task. It hides the work and makes aging useless.

Test five cases before trusting automation

Use synthetic accounts and payer training environments where available.

1. Active coverage, no returned exception. Confirm that the evidence is stored and the result expires under policy.
2. Coverage terminates the day before the appointment. Confirm that the workflow compares the date instead of trusting the word “active.”
3. Member ID is wrong by one digit. Confirm that the system does not silently attach a different person.
4. Response indicates a referral or authorization issue. Confirm a task reaches the correct owner with the source attached.
5. Payer endpoint is unavailable. Confirm the appointment does not become “verified” because the check failed open.

Then change the appointment date. The prior response should remain in history, while the new date receives a fresh decision under policy.

Keep eligibility, estimates, and collections apart

Eligibility checks coverage and returned benefits. It does not replace the practice’s good-faith-estimate duties for applicable uninsured or self-pay patients, its price-estimate workflow, or payer-specific authorization work. CMS keeps provider No Surprises Act resources in a separate body of guidance for a reason.

Likewise, a coverage problem should not become a collection note before the balance exists. Preserve the sequence: verify, communicate uncertainty, perform approved referral or authorization work, submit the claim if appropriate, receive adjudication, correct errors, and only then manage a patient balance.

Measure the queue, not a vanity percentage

Track clear results, exceptions, age, resolved-before-visit counts, rescheduled cases, payer downtime, and rework caused by bad identifiers. Sample results back to the source response.

A 99 percent “verified” rate is meaningless if staff mark unavailable responses as clear. The useful measure is how many exceptions reached the correct owner soon enough to act, without an invented benefit quote.

Product boundary

Patient Square can support practice workflows within the current product scope. This article does not claim automated payer eligibility, benefit interpretation, prior-authorization submission, guaranteed estimates, claim adjudication, or payment collection.

Check the current US plan scope before buying around any workflow. Ask the vendor to demonstrate the exact transaction source, evidence record, exception queue, permissions, failure behavior, and handoff to staff.