Check It Before They Arrive: Eligibility Verification Moved to the Moment of Booking

A patient books an appointment on a Tuesday and is seen three weeks later. Six weeks after that, a remittance arrives showing the service fell outside their eligibility window. By then the patient has been treated, the clinician has been scheduled, the claim has been prepared, a biller has worked it, and someone now has to phone a person who thought they were covered. Every one of those costs was incurred after the moment the answer was cheapest to get.

This is the transformation we would run for that operation. It is presented as a concept, built on the same method we use in client engagements, so the before, the after, and the path between them are all visible.

Why is checking late so expensive?

Because eligibility is the only thing in the sequence that could have been known first. Everything else, the clinical work, the claim, the rework, is downstream of a fact that existed at booking and was not requested.

The CAQH Index 2025, published in February 2026 from more than 600 US provider organizations and health plans representing 63% of insured lives, identifies approximately $12.3 billion in annual savings available from fully adopting electronic eligibility and benefits verification, and estimates a manual provider eligibility call at $5 to $7. That is US data about a US payer mix, and it is quoted here to size the transaction class rather than to price an Ontario operation.

The transferable part is not the dollar figure, it is the shape. Eligibility verification is the single administrative transaction with the largest gap between what it costs to do early and what it costs to discover late, which is why it is the one worth moving.

Before and after: the booking

Drag the handle. The before is eligibility established by a bounced claim; the after is the check at the moment of booking.

The clinical work is unchanged and the patient conversation still belongs to a person. What changes is that the front desk knows, three weeks early, that there is something to talk about.

What we built

The concept above is the output of the same engagement steps we run in client work, and several are decisions a competent peer could argue with.

• We refused to let the system produce a patient-facing number. A coverage response is what a payer’s system reports at that moment, not an adjudication, and dressing it as a quoted price would convert an uncertain signal into a promise the practice would then own.
• We designed the ambiguous result to be as legible as the clean one, naming exactly what could not be established. A binary indicator that resolves to green under uncertainty gets ignored within a fortnight, and then the check has cost money and changed nothing. This is the decision most likely to be argued with, because three states are harder to design and harder to sell than two.
• We write the result back into the clinic’s own EMR rather than into a billing portal. A result the front desk cannot see at the desk does not exist, however correct it is.
• We confirm each client clinic’s own PHIPA agreement before running a check against its patients, because a billing company acting as agent for sixty clinics inherits sixty separate obligations rather than one.
• We wire evals from day one against the operation’s own historical remittances, scored on whether a check at booking would have predicted the eligibility rejections that actually occurred.

How it works

The clinic’s EMR stays where the front desk works. A booking triggers a coverage check against the payer. The result returns in three states, covered, not covered, or specifically ambiguous with the unresolved element named, and is written back into the EMR where the booking lives. A person decides what, if anything, to say to the patient. Nothing is quoted, and no patient-facing message is generated. Prevented rejections are tracked against the operation’s own historical rate for that payer, which is how the slice proves or disproves itself.

Because identifiers, coverage responses and booking data stay in Canadian infrastructure and processing runs with zero data retention, the design lines up with what PHIPA expects: a privacy impact assessment before deployment, an agreement naming the processor as an agent under section 17, and an audit log on every access. Each client clinic’s agreement is confirmed individually.

Why this pays back

The return is rework that never starts, plus a smaller number of the phone calls nobody wants to make. Break-even for the first slice is about two hundred and forty prevented eligibility rejections a month at the operation’s own loaded biller cost.

The limit worth saying plainly before anyone signs: this only pays where eligibility is genuinely variable. For a payer whose coverage is stable and near-universal, checking at booking produces a long series of confirmations of something everyone already assumed, at a real cost per check. The operation’s own rejection data will show which payers are worth checking, and the honest first step is to read that data rather than to buy a check for all of them. That may conclude that only one payer justifies this, which is a much smaller engagement than the one being discussed.