Patient insurance eligibility verification is the check that confirms a patient's coverage is active and that the plan will pay for the visit being booked. Denials still show up on the remit even when your team runs it on every scheduled patient, because what matters is when staff run the check. Most of the time it happens after booking, when plan details can't change the appointment anymore.

By the time the claim comes back, a lot of those denials have no corrected version to resubmit. The practice writes off the balance, and the patient gets a late request for new coverage or a new appointment date.

Where Patient Insurance Eligibility Verification Denials Actually Originate

Several points in the sequence produce these denials, and only one of them is the coverage check itself. A payer can deny a claim as CO-96 even when the policy is active. CO-96 is one of the Claim Adjustment Reason Codes payers put on the remittance advice to explain a rejection.

The 271 response confirms coverage and usually leaves the plan restrictions unresolved: visit caps, frequency limits, exclusions, and place-of-service differences. If the plan excludes the scheduled service, the claim is denied as a non-covered charge, and the patient learns about the cost too late to change their booking decision.

Referral and authorization requirements produce CO-170 or CO-197 even when coverage passes. The claim can come back as CO-170 for a missing referral or CO-197 for absent precertification. Staff then reopen the record, and the patient waits for a new date or approval.

Registration produces CO-22, which payers use when another insurer should have been billed first. When intake staff misses coordination of benefits, the payer returns that code weeks later. One intake question can catch a wrong or stale payer order before the claim goes to the wrong payer and before the patient gets bad cost information.

Coverage timing produces CO-27 when staff verify at booking and never run the check again before the visit. Coverage can change between scheduling and arrival for all kinds of reasons: a job loss, a plan switch, a premium lapse. The payer then applies CO-27 because coverage terminated before the date of service.

Every denial that lands after booking sends staff back to reopen the record, rebook the patient, or write off the balance, and each handoff costs more than the check that would have caught it upfront. Staff can see every one of these warnings before the remit arrives.

Each Denial Category Traces to One Step and One Owner

Mapping each denial back to the step that produced it also names the person who can stop it. Each category maps to one step, which is also the insurer-specific rule layer the Assort Health platform applies during scheduling before a slot gets locked in. Every signal lands with a specific person at a specific point in the booking sequence.

The map above names the warning. The sequence below assigns each one an owner and a deadline.

Run Verification in Six Steps, Each With an Owner and a Deadline

At each step below, a staff decision can produce a denial with a clear owner. A shared verification protocol records the owner, the deadline, the booking status, and the patient action. Those fields show where records stall, and they separate a failed payer match from a rule staff knowingly carried forward.

1. Start With Identity and Plan Capture at First Contact

The scheduler captures the patient's name, date of birth, member ID, group number, and plan without a mismatch. A mismatch here produces CO-31, the code payers use when they cannot identify the patient as a covered member.

A failed member match is the early signal, and the deadline is the first call. Fixing the record while the patient is still on the line saves everyone another round of asking for the same insurance information.

2. Confirm Coverage Against the Payer

Front-desk staff own the date-of-service coverage check, and billing owns any unresolved failed match. A wrong member ID, a payer switch, or an open-enrollment plan change can all lead to CO-27.

Before the encounter, staff need a resolution deadline and have to confirm the current card against the subscriber and payer records. Otherwise, billing gets the failed match after the visit, when the appointment can't change anymore.

3. Validate Plan-Specific Benefits and Visit Type

The verification team checks the benefit details behind CO-96: the deductible, the visit-type copay, visit limits, and exclusions. The scheduler then uses those details before confirming the slot.

When the plan imposes a visit interval or excludes the service, staff can offer an eligible date or give the patient accurate cost information before booking.

4. Check Referral and Prior Authorization Requirements

Schedulers own the booking decision when coverage passes, but the referral or authorization gate is still open. Early CO-170 or CO-197 risk shows up as a missing referral number, an expired authorization window, an unknown authorization indicator, or a pending approval.

While the appointment is still movable, staff can hold the slot, offer a later date, or route the record to the authorization queue.

5. Capture Secondary Coverage and Coordination of Benefits

The front desk owns the initial CO-22 signal when a second policy shows up at registration. Billing takes over the more complex coordination of benefits. Intake staff needs the second policy and the reason for the visit before setting the payer order. Getting that at registration keeps the claim from going to the wrong payer.

6. Run Verification Again Before the Visit

The verification or billing team owns the pre-visit batch, and the front desk confirms the result at check-in. A termination date before the appointment is the early CO-27 signal.

Every unresolved record needs an owner and a patient action: capture new insurance, provide a self-pay disclosure, change the appointment date, or clear the patient to arrive.

When the Check Runs Sets the Denial Rate

Verification results that land after booking create rework, because the appointment can no longer change. Staff hit this at coverage confirmation, again when plan-specific rules stay unresolved, and again when nobody runs the pre-visit check.

Late Verification Can't Change the Appointment

When staff gets a failed verification result after scheduling, the practice absorbs either the cost of changing the appointment or the denial. The patient also has less time to provide new insurance or pick a covered appointment.

Track the time from payer response to owner assignment, and split issues resolved before confirmation from those resolved afterward.

New Schedulers Cannot Hold Every Payer's Rules

A scheduler still months from proficiency cannot hold rules that diverge payer by payer. Every new hire restarts the training, and every missed rule sends another patient a call about a changed date or an unexpected cost.

Global periods show the size of that burden, because the same procedure carries different timing rules from one insurer to the next.

Pre-Visit Re-Verification Is the First Step Short-Staffed Teams Drop

When the front office is short-staffed, nobody has the hours to work tomorrow's schedule against the payer, so the batch re-verification is the step that gets dropped. Move the check into scheduling, and staff can keep a non-covered service off the schedule while the patient is still on the line. They use the 270/271 response to match the visit type to plan coverage and record the copay and deductible before confirming the slot.

Referral and authorization rules also need to resolve before confirmation. Because the eligibility response can return an unknown authorization indicator and no referral information, staff use the plan-type rule to confirm the slot or route the record for review.

Writing those decisions back to the EHR keeps staff from re-keying them, so patients don't repeat the same insurance details to another staff member. That handoff is one piece of the cash cycle. Healthcare workflow automation maps where the other intake-to-payment handoffs break down.

Assort Health Applies Insurer-Specific Rules Before Specialty-Care Booking

For specialty practices, insurer-specific referral and prior authorization requirements need to surface before booking. On the inbound call, Assort Health captures insurance information and verifies eligibility against the payer in real time. It then updates the EHR, so staff starts with a current record and the patient isn't getting a second call for the same information.

How NCRVA Enforces HMO Prior Authorization Before Booking

Insurer-specific precision also has to hold at scale. Northern California Retina Vitreous Associates needed to identify HMO patients and check prior authorization before confirming a slot, and it reports agents applying that check across more than 10,000 calls a month, inside the access workflow rather than as a separate downstream task.

 "Assort didn't just solve a staffing challenge, it accelerated our strategic roadmap. We were missing a third of our 10,000 monthly calls despite a strong front-office team. With Assort, we automated call handling, freed up staff capacity, and improved scheduling speed without hiring more people. It's allowed us to deliver faster, smarter care at scale."  

Aamer Hayat, Chief Administrative Officer, NCRVA

Move Patient Insurance Eligibility Verification to the Scheduling Call

For patient insurance eligibility verification, Assort Health's AI voice agents capture insurance information, verify eligibility in real time, and update the EHR during the call. Corrected eligibility details stay with the patient's record across touchpoints, so the practice does not place another call for the same information.

Accuracy on those rules holds after go-live because Assort Health tests the deployed agents continuously, scoring live calls against platform benchmarks and surfacing protocol misses before a denial pattern forms. For patient access leaders, the practical takeaway is that timing, not diligence, sets the eligibility denial rate. Post-booking results send staff back to reopen records and rebook patients, and every one of those handoffs costs the practice more than the check that would have prevented it.

Book a demo with Assort Health to watch a payer-specific referral and authorization check run before the slot gets confirmed on a live call.

FAQs About Patient Insurance Eligibility Verification

How Often Does Eligibility Verification Need to Run for Established Patients?

Coverage changes between encounters create avoidable denials, so established patients need verification at every visit. Medicaid status can change at any point in the year, because patients can apply and enroll in Medicaid any time rather than during an open enrollment window. Patients on recurring services need another check when a new benefit period starts. Every patient also needs a fresh check at the start of a plan year, when deductibles reset.

Which Eligibility Denials Cannot Be Recovered?

The ones with nothing to correct. A coding denial can be fixed and resubmitted, because the service happened and the claim described it wrong. A claim for a service the plan excludes, or for a policy that terminated before the date of service, has no corrected version to send: the coverage was not there on the day of the visit.

When Does Verification Need to Happen Before a Visit?

Run verification during scheduling, while coverage details can still change the appointment, and run it again before the visit. The second check catches coverage changes between booking and arrival.

How Do Specialty Practices Keep Payer-Specific Rules Out of Schedulers' Heads?

They move the rules into the system that books the appointment. The Assort Health platform applies plan-specific timing, referral, and authorization requirements while the appointment is being scheduled, so a new scheduler does not carry them in their head through a ramp period.