Practice Operations
Eligibility Checks When Coverage Changes Mid-Year
Health center patients lose and regain Medicaid between visits. What eligibility checks must catch when coverage changes mid-year, and who owns the exceptions.
Eligibility checks at a health center fail for a reason that has nothing to do with the check itself. The coverage was real when you verified it and gone by the time the patient arrived.
Most verification workflows assume coverage is a fact you establish once and carry forward. For a large share of health center patients it behaves more like a subscription that lapses without notice, changes plans mid-year, or reappears retroactively weeks after a visit has already been billed to the wrong payer.
Coverage moves, and the schedule does not know
The population a health center serves sits close to eligibility thresholds, which means small changes in income, household size, or paperwork produce changes in coverage.
A patient verified in March can be uninsured in June and re-enrolled in August. Nothing in the schedule reflects that. The appointment booked in April still shows the plan that was current when it was booked, and the front desk has no reason to look again unless someone tells them to.
The result is a specific and expensive pattern. The visit happens, the claim goes to a plan the patient no longer has, it denies, and the balance lands on a patient who could have been re-enrolled before the visit if anyone had checked. That is worse than a billing error. It is a patient who now believes the health center charged them for something they thought was covered.
Staff know this happens. What they lack is the hours to re-verify everything on a schedule that is already full, so re-verification becomes something done for the visits someone happened to worry about.
The scale of the churn is not a rounding error
This is worth quantifying, because leadership often treats coverage change as an edge case.
National Medicaid and CHIP enrollment reached a record high of 94 million enrollees in March 2023, when the pandemic-era continuous enrollment provision ended. The unwinding of that provision started on April 1, 2023, and by September 2024 national enrollment had dropped to 80 million. Enrollment stabilized briefly at the end of 2024 and began declining again in March 2025.
More change is scheduled rather than hypothetical. Work and reporting requirements for Medicaid expansion enrollees take effect in January 2027, or sooner at state option, and are expected to be the largest single source of further enrollment decline.
For a health center that is not a policy story. It is a forecast that says the share of patients whose coverage differs from what is on file will go up, not down, and that verification workflows built for a stable population will get less accurate every quarter they are left alone.
Re-check timing matters more than re-check thoroughness
The instinct when accuracy drops is to verify harder. The better move is to verify later.
A check run at booking answers a question about a date that has not arrived yet. For an appointment scheduled three weeks out, that answer has three weeks to go stale. The check that actually protects the visit is the one run close to it, and the one run again if the appointment moves.
The mechanics are ordinary. Read what is on the chart through GET /patients/{patientid}/insurances, compare it against the plan catalog through GET /insurancepackages so a plan change is recognized as a change rather than as an unfamiliar string, and run the check on a cadence tied to the appointment date instead of the booking date.
What this produces is a short, workable list rather than a full re-verification of the entire schedule. Most patients will come back unchanged. The ones who do not are the ones worth a phone call, and there are few enough of them that a person can actually make those calls.
The automation is doing lookup and comparison, which is the part that scales. It is not deciding what a coverage change means for a specific patient, which is the part that does not.
The complication: coverage that changed is not the same as coverage that ended
This distinction is where automated verification most often does damage, and it is worth being blunt about.
A patient can show as inactive because they were disenrolled. They can also show as inactive because their plan changed and the new one has not posted yet, because a renewal is processing, because the eligibility response is delayed at the state, or because a data entry error dropped a digit. Those look identical in a verification response and they call for completely different conversations.
Telling a patient they no longer have coverage when their renewal is simply in process is a serious error. It produces cancelled appointments, care that does not happen, and a patient who stops trusting what the health center tells them. Some of them do not come back.
So the rule is that the automation never delivers a coverage verdict to a patient. It flags the discrepancy, states what is on file, and asks a neutral question about whether anything has changed with their insurance. The answer to that question routes the work. A patient who says they are still enrolled goes to the eligibility team to reconcile. A patient who says they lost coverage goes to enrollment staff, who can start a re-application and, at a health center, apply the sliding-fee pathway in the meantime.
The appointment stays on the schedule through all of it. A coverage question is not a reason to cancel a visit at a health center, and an automation should never be configured to treat it as one.
Eligibility is already the largest phone task you have
The staffing math here usually settles the argument, because the work is already being done and it is being done on the phone.
In a March 10, 2026, MGMA Stat poll of practice leaders, eligibility and prior authorization together accounted for 45% of the most time-intensive phone tasks, ahead of scheduling at 31%, intake at 9%, and prescription refills at 6%. The poll had 294 applicable responses.
At a health center the eligibility share runs heavier, because a single patient can move between Medicaid, marketplace coverage, employer coverage, and uninsured with sliding-fee eligibility inside one year. Each transition generates its own calls, its own paperwork, and its own opportunity to bill the wrong payer.
The portion of that work that is genuinely repetitive is large: run the check, compare it to what is on file, note the difference, put it where somebody will see it. Moving that portion off the phone does not reduce the enrollment team. It gives the enrollment team back the hours they currently spend discovering problems, so they can spend them fixing problems instead.
The measure that tells you it is working
Verification rate is the metric everyone starts with and it saturates almost immediately. You can verify one hundred percent of appointments and still bill the wrong payer all year.
The number that matters is the share of visits whose coverage was confirmed within a short window before the appointment, rather than at any point in its history. That single change in definition usually reveals that a practice believing itself at ninety-something percent is actually much lower.
Two others are worth tracking. Denials attributable to eligibility, measured monthly, is the financial read and it should fall within a couple of billing cycles. And the count of patients routed to enrollment staff who were successfully re-enrolled before their visit is the one to show the board, because it is the number where revenue protection and the health center’s actual mission point in the same direction.
Key Takeaways
- Treat coverage as something that expires rather than something you establish. For a health center population, the plan on file is a snapshot with a short shelf life.
- Run the eligibility check close to the appointment date, not the booking date. A check run three weeks early has three weeks to go wrong.
- Re-run the check whenever an appointment moves. A rescheduled visit inherits the old verification and nothing flags it.
- Compare against the plan catalog so a plan change reads as a change rather than as an unrecognized value that gets ignored.
- Never let an automation tell a patient they lost coverage. Inactive can mean disenrolled, in renewal, delayed at the state, or mistyped, and those need different conversations.
- Route by the patient’s own answer: still enrolled goes to eligibility to reconcile, lost coverage goes to enrollment staff who can re-apply and open the sliding-fee pathway.
- Keep the appointment on the schedule while coverage is being sorted out. A coverage question is not a reason to cancel a visit at a health center.
- Measure coverage confirmed within a short window before the visit, not verification rate. The first number is honest and the second one saturates.
Coverage churn is usually filed as a billing problem because that is where the consequences show up, but it starts as an information problem on a specific date. The plan on file was accurate when someone typed it, and the visit is happening weeks later. The only thing standing between those two facts is whether anybody had time to look again. An AI team working inside athenaOne can look again as a matter of course. It re-reads coverage close to the appointment and after every reschedule, compares it against the plan catalog so changes are recognized, and produces a short exception list instead of a full re-verification. It asks the patient a neutral question rather than announcing a verdict, and hands every real coverage change to the enrollment staff who can still fix it before the visit.
Related reading
- verifying Medicaid eligibility before the visit
- sliding-fee conversations at the front desk
- prior authorization under Medicaid rules
Sources
Ready to See It in Action?
See how PGA rechecks coverage before the visit inside athenaOne and routes the exceptions to enrollment staff
Schedule a Demo →Written by Kevin Henrikson