“We verify every patient’s insurance before they come in.” Every front desk says it, and it is true.
The check runs. It runs the day before every visit, automatically, and it comes back with a flag that says approved. Then medical claim denials arrive for coverage anyway, and the office cannot see how both things can be true.
They are both true. An eligibility check, meaning a question sent to the insurer asking whether this patient has coverage, comes back with a flag. The flag answers that question and no other. A policy exists. Whether the policy pays for this visit, at this practice, on this date, for this service, is four more questions, and the flag was never asked any of them.
Here is the map. A patient is booked. The night before, the system asks the insurer about the patient’s coverage and stores the answer. The desk sees the flag. The visit happens. The claim goes out and is paid or refused. The flag sits at the second step, and the whole front door of the money path depends on someone reading past it.
What the flag actually says
Approved means the insurer found a policy for this person that was active on the day the check ran. The message ends there.
It is useful. A patient with no policy at all gets caught, and that is a visit that would have produced a claim to nobody. But a patient with a policy is most patients, so the flag says approved on most visits, including the ones the insurer is about to refuse.
The answer the practice needed is in the response behind the flag. Every eligibility response carries the plan name, the coverage dates, the services covered, and what the patient owes. The flag is a summary of one line of it. The other lines are where the denials, the insurer’s refusals to pay, come from.
The four things approved does not tell you
The plan. One insurer sells dozens of plans, and a practice is in network with some of them, meaning under contract at an agreed rate. The flag reads approved for a policy under a plan the practice has never billed. The claim goes out and comes back out of network. Nothing on the flag was wrong.
The date. The check ran the day before the visit, or a week before, or when the card was first scanned. Coverage that ends on the last day of the month is active on the twenty-eighth and gone on the first. Nothing happens the day a card expires, and a flag from last week reads approved on a visit the insurer will not pay.
The service. A policy can be active and still exclude the visit being scheduled. A plan that does not cover a particular assessment, a limit on the number of visits, a service that needs authorization, the insurer’s advance permission, before it will pay. The flag says the policy is active. The refusal says the service was not covered under it.
The switch. A patient changed jobs, changed plans, or moved to a spouse’s coverage in January and never mentioned it. The card on file is the old one. The check ran against the old policy, found it active for a few more weeks, and said approved. The claim went to an insurer that no longer covered the patient.
None of these is a billing error. Each is a question the practice could have answered before the visit, from the response it already had.
Why the response never gets read
Because reading it is a person’s job and the flag is a machine’s.
The check runs automatically. The flag appears automatically. The response behind it sits in the system, one screen deeper, in a format built for a biller. The desk has forty patients tomorrow and a flag that says approved next to each one. Opening forty responses and reading four lines in each is an hour nobody has, so the flag becomes the answer.
At practices we have worked with, the eligibility check reads approved on most of the visits the insurers later refuse for coverage. The check was running on every patient. The response was never opened. The plan on it was, on visit after visit, not one the practice billed.
Denials get created upstream, meaning early in the chain, and this is where those refusals get created. The billing team inherits a refusal it could not have prevented and a denial rate it gets blamed for.
The check that works
The check that works reads the response instead of the flag, and it does it without a person.
The plan on the response is matched against the list of plans the practice bills. A plan not on the list is flagged, in words, the afternoon before the visit.
The coverage dates on the response are compared to the visit date, not the check date. A visit outside the dates is flagged. The service being scheduled is compared to what the response says is covered and what needs authorization. A gap is flagged.
And the patient’s share on the response, the copay and deductible and coinsurance, is put on the check-in screen so the desk can ask for it.
That is four comparisons per patient. A machine does them in a second for the whole schedule. A person does them for the first six patients and stops.
The result is a short list every afternoon, in words the desk can act on. Not approved. This plan is not one we bill. Coverage ends before the visit. This service needs authorization and none is on file. The patient owes this much at check-in.
What to do with the list
Call the patient before the visit. The whole action is that call, and it is only possible because the list exists a day early.
A plan the practice is not in becomes a conversation about cost, or a referral, or a rescheduled visit under the right coverage, before the chair is spent on it.
A coverage gap becomes a question to the patient about a new card. A service without authorization becomes a request to the insurer with time to get an answer. An insurer that does not pay the claim is a problem for the billing team. An insurer that was never going to pay is a problem for the desk, the day before, when it can still be fixed.
Real situations, and what the flag hid
At one practice we worked with, the denial review started with the billing team and ended at the front desk. A large share of the refusals were for coverage. Every one had a flag that said approved behind it. The plan on the response was one the practice did not bill, and the desk had never been shown the plan, only the flag.
At another, coverage denials clustered at the start of each month, because the check ran days before the visits it covered. The check ran on the twenty-fifth for the whole following week. Patients whose coverage ended on the thirty-first read approved and were refused four days later.
At a third, one type of service kept coming back refused, and the eligibility response had said all along that it needed authorization. The eligibility response for those patients said, on a line nobody opened, that the service needed authorization. None had been requested. The billing team had been appealing a refusal the desk could have prevented with one call.
What this means for you
If your denials include coverage refusals and your desk checks eligibility on every patient, the flag is being read and the response is not. Pull tomorrow’s schedule, open the eligibility response for each patient, and compare the plan on it to the plans you bill.
The number of mismatches is a denial count for a week that has not happened yet, and every one of them is a phone call today.
Grab 30 minutes with us. Prep nothing. You will see how many of next week’s approved patients are booked under a plan you do not bill.
Questions people ask
What does an approved eligibility check actually mean?
That the insurer found an active policy for the patient on the day the check ran. It does not say the plan is one the practice is in, that coverage is active on the visit date, that the service is covered, or that the patient has not switched plans.
Why do coverage denials happen when eligibility was verified?
Because the flag was read and the response was not. The plan, the coverage dates, the covered services, and the authorization requirement are all in the response. The flag summarizes one line of it.
How should a medical practice verify insurance eligibility?
Read the response, not the flag, and do it automatically the afternoon before the visit. Match the plan against the plans the practice bills, the coverage dates against the visit date, the service against what is covered, and put the patient’s share on the check-in screen.
When should eligibility be checked?
Close enough to the visit that the coverage dates on the response cover the visit date. A check run a week early reads approved on coverage that ends before the patient arrives. The afternoon before is the working standard.
What should the front desk do with an eligibility problem?
Call the patient before the visit. A plan the practice is not in becomes a cost conversation or a reschedule. A coverage gap becomes a question about a new card. A missing authorization becomes a request with time to get an answer.