How eligibility verification actually works

Most of the money a practice loses to coverage problems is lost before the patient sits down. The plan terminated last month, the patient switched employers, the visit needed an authorization nobody requested, or the card at the front desk belongs to a plan the practice is out of network with. None of that is visible on the claim. All of it is visible the day before, to anybody who looks.

Eligibility and benefits verification is the discipline of looking. It is unglamorous, repetitive, and almost entirely mechanical, which is exactly why it loses every competition for a front-desk person’s attention: it is important and never urgent, and the phone is always urgent.

A dedicated eligibility seat exists to remove it from that competition. The work is the same work; the difference is that it belongs to somebody whose day contains nothing else, running against tomorrow’s schedule while there is still time to act on what turns up.

What an eligibility and benefits check actually captures

A verification that records the word “active” and stops is not a verification. Active tells you the policy exists. It does not tell you what the plan will pay, what the patient owes, or whether the visit needs permission first.

A useful check captures, in the practice’s own fields and format:

• Payer, plan name and plan type, and the member and group identifiers as the payer holds them.
• Effective date and termination date, checked against the date of service rather than today.
• Network status for the rendering provider and the location, not just for the practice.
• Copay for the service type being scheduled, which is frequently not the copay printed on the card.
• Deductible: the amount, how much has been met, and when the plan year resets.
• Coinsurance and out-of-pocket maximum, and how much of it has been satisfied.
• Whether prior authorization is required for the planned service, and by whom.
• Visit or unit limits where the plan applies them, and how many have been used.
• Coordination of benefits: secondary and tertiary coverage, and which payer is primary.
• The reference number for the check, the source, and the date and time it was performed.

That last line matters more than it looks. A verification with no reference number and no timestamp cannot be used to argue anything later. A verification with both is evidence.

Where the check belongs in the week

Eligibility is a scheduling task that happens to produce billing information. Run it the day before the visit and it is worth a great deal: coverage problems reach the front desk while the patient can still be called, an authorization gap reaches whoever can request one, and the desk knows what to collect. Run it at check-in and it is worth much less, because nothing can be fixed with the patient standing at the counter. Run it after the claim has been submitted and it is worth almost nothing — it explains a denial rather than preventing one.

A workable rhythm for most practices looks like this:

1. Pull tomorrow’s schedule, plus any add-ons to today’s.
2. Run the batch check where the payer supports one, and the portal or phone where it does not.
3. Write the results into the practice management system in the agreed fields.
4. Separate the schedule into clean and exception.
5. Route each exception to the person who can act on it, with the reason stated in one line.
6. Re-check anything scheduled more than a week out, closer to the date.

The re-check is the step most often skipped and the one that catches terminations. A verification performed three weeks before a surgery describes coverage that may no longer exist on the day.

The exceptions are the product

It is tempting to measure this work by how many patients were verified. That number is easy to produce and tells nobody anything, because the clean accounts were never at risk. The output that matters is the short list: the eleven or twelve accounts on tomorrow’s schedule where something is wrong.

Common exceptions, and where each one has to go:

• Coverage terminated or not effective on the date of service. To the front desk, today, so the patient can be called before they travel.
• Different payer than the one on file. To whoever updates the record, before the claim is built against the wrong plan.
• Out of network for this provider or location. To the person who has the financial conversation, with the plan’s out-of-network position captured.
• Prior authorization required and not on file. To the authorization queue, with the payer’s requirement and the submission route recorded.
• Deductible not met and a large balance likely. To the front desk, as a number, so the collection conversation is prepared rather than improvised.
• Benefit limit reached. To the scheduler and the clinician, because the answer may be to move the visit rather than to bill it.

An exception that is found and not routed has cost the practice the labour of finding it and returned nothing. Deciding the routes in advance — in writing, by name — is most of what separates a queue that works from a queue that produces a report.

What to organize before assigning the queue

Decide the field list, and write it down

Which fields, in which screen, in which format. “Verify the patient” is not an instruction; it is a hope. A one-page field list is the difference between six people documenting six ways and a record the next person can read.

Decide the lead time by service type

A routine office visit and a scheduled procedure do not need the same lead time. Set the interval for each, and set a re-check point for anything booked far ahead.

Decide the exception routes

For each exception type: who is told, by what channel, and by when. Name the roles rather than the individuals, so the process survives somebody being on leave.

Decide what the seat may do, and what it must escalate

Updating a payer record, correcting a subscriber identifier, adding a secondary plan — some practices want that done, others want it flagged. Either is workable. What is not workable is leaving it unstated.

Arrange access properly

Practice management system, clearinghouse eligibility tool, and the payer portals the practice’s mix actually requires. Access should be granted under the practice’s own controls, with named accounts rather than shared logins, so every check is attributable to the person who made it.

How to tell whether it is working

The questions worth asking each week are not about volume:

• Was tomorrow’s schedule fully checked, every working day?
• What was found, and where did each exception go?
• How many exceptions were resolved before the date of service rather than after?
• Are coverage-related denials falling for the accounts that were checked?
• Which payers are consistently unreliable through the batch tool and need portal or phone verification instead?
• Are re-checks happening on anything booked more than a week out?

The fourth question is the honest one. Eligibility work addresses one family of denials and no others. If coverage denials are not moving for verified accounts, either the checks are not capturing enough detail, the exceptions are not being routed, or the denials have a different cause and the effort belongs somewhere else.

When a dedicated seat is the right answer

Verification is a good candidate for a dedicated offshore seat because it is scheduled work with a clear definition of done, it runs on systems rather than on relationships, and it can be performed in a fixed window every day without needing anybody in the building. It is a poor candidate for “whoever has a spare hour”, for the same reasons.

Questions worth answering before choosing a provider:

• Will the person work US business hours, so the exception list arrives while the office is open?
• Will they work inside your practice management system, or send you a spreadsheet to retype?
• Is it a dedicated full-time seat, or a shared pool that handles your checks between other clients?
• Who reviews the exception list at your end, and by when each day?
• What happens on a payer whose portal is down or whose batch response is unusable?
• How is a check evidenced — reference number, timestamp, source?

How Soft Home Global staffs this

Soft Home Global provides trained full-time back-office seats for US medical billing and revenue cycle work from Rawalpindi, Pakistan. Eligibility and benefits verification is one of them, published at $1,700 per seat per month, billed per seat with a one month minimum.

The seat works your hours, inside your system, against your schedule, using your field list and your exception routes. The practice keeps the decisions — what to verify, how far ahead, who is told what — and the seat performs the work every working day without it competing with a ringing phone.

Where an eligibility exception depends on another part of the cycle, it is routed rather than repeated: an authorization requirement goes to the authorization queue, a payer record correction goes to whoever owns the record. Soft Home Global staffs those adjacent seats too, which makes the handoff a queue rather than an email.

Start with tomorrow’s schedule

If you want to know whether this work is worth a seat, do not model it. Take one day’s schedule, verify every patient on it properly, and count what turns up. Whatever that count turns out to be, every account on it was going to become a denial, a write-off or an awkward conversation at the counter.

Then decide whether that list is worth producing every working day, and who should be producing it.