Chapter 24 — Key Takeaways

The argument, in one table

   WHERE AN ERROR IS CAUGHT              STAFF MINUTES

   Registration ......................... 0.5
   Scrubber ............................. 3
   Clearinghouse rejection .............. 12
   Denial, worked and followed up ....... 30-60, several touches
   After timely filing .................. — (no work to do)

Roughly 90 to 1 — and that is the GOOD outcome, because it assumes the denial was won.

The table is in MINUTES on purpose. Minutes are what a staffing decision is made in, and whatever your loaded labor rate is, the same number multiplies both sides.

An organization that will not fund thirty seconds is buying roughly ninety times as much back-office time instead — on a budget line not visibly connected to the decision.

The registration fields

The most expensive field is the one nobody thinks of as a field: "HAS ANYTHING CHANGED?"

A returning patient's record is complete — for a situation that no longer exists. New job, turned 65, divorce, aged off a parent's plan, employer changed carriers. None produces a warning. JANUARY is the month.

And one duty is not about billing at all: verify that the person is the person on the coverage. Medical identity theft contaminates the victim's record permanently. The reason is the chart, not the claim.

Eligibility — the 270/271

CAN tell you: active or not · plan and group · copay · deductible and remaining · coinsurance · other coverage on file · sometimes referral/authorization requirements.

CANNOT tell you:

• That coverage will still exist on the date of service — it is a snapshot
• A current deductible. The figure reflects claims the payer has PROCESSED → an estimate built on it asks the patient for too much
• Whether the service is medically necessary — Chapter 22's entire apparatus is absent
• Anything the payer chose not to populate

"Other coverage: none indicated" is a statement about the PAYER'S RECORDS. §24.7's questionnaire exists because those records are frequently wrong.

Verify three times: at scheduling (the only point the encounter can still be rearranged) · 48–72 hours before, in BATCH (early enough to act, late enough to still be true — the one that pays for itself) · day of service, in REAL TIME.

Ask of any response: as of what date? · what is it silent about? · what did the payer say versus what did my system display?

Referral vs. authorization vs. precertification

RECORD THE SCOPE, NOT JUST THE NUMBER.

number · date · issuer · CODES · DATE RANGE · UNITS · FACILITY · RENDERING PROVIDER

An authorization number recorded without its scope is a number, not a record — and the four underlined items are the four things that drifted in Chapter 22's Case Study 1.

When one practice orders and another performs, write down who obtains it — per payer, per service type. The party who knows the CODES is best placed; the party who does not get paid has the incentive; and whoever obtains it must pass on the SCOPE.

The MSPQ

Medicare is secondary when: group health through current employment (own or spouse's) · work-related injury → workers' compensation · accident → auto, no-fault, liability · black lung · VA-authorized · ESRD coordination period.

A 271 is not sufficient. Billing Medicare as primary when it is not is an OVERPAYMENT, and the sixty-day rule attaches on identification.

The MSPQ is a SEQUENCE of questions, not a form. Stopping at the first "yes" is right; skipping to the question you expected is not.

Asking for money

"Your copay for today is \$30.00. How would you like to take care of that?" States the amount as a fact. Asks about method, not permission.

NOT "Would you like to pay your copay today?" — which invites "no," and to which "no" is a complete and reasonable answer.

Makes it worse: asking within earshot of others · insisting when someone says they cannot · quoting a number you cannot stand behind.

May: collect · payment plans · financial assistance under a written policy · self-pay or prompt-pay discounts under a written policy. May NOT: ROUTINELY waive cost-sharing.

The word doing the work is "routinely." An individualized hardship determination under a written policy is a different thing — and the difference is a written policy and a record, which is the same answer this book gave about ABNs, about drug waste, and about queries.

Financial clearance

   ☐ Identity and demographics verified
   ☐ Coverage verified FOR THE DATE OF SERVICE
   ☐ Coordination of benefits resolved (MSPQ where applicable)
   ☐ Referral obtained, if required
   ☐ Authorization obtained AND ITS SCOPE RECORDED
   ☐ MEDICAL NECESSITY SCREENED  ◄ highest value, almost nobody does it
   ☐ Patient responsibility ESTIMATED
   ☐ Patient INFORMED
   ☐ Collection attempted or arrangement made

"Informed" is not "collected." A patient who cannot pay today has still been informed.

The estimate is built from the ALLOWED AMOUNT, not the charge, and it cannot know the deductible exactly, the codes that do not exist yet, or how the claim will adjudicate.

The sentence matters more than the number, and a good sentence names the specific thing that could move.

Measuring the front end

Clean claim rate · front-end denial rate (requires Chapter 29 §29.4's classification to compute at all) · eligibility verification rate for the date of service · authorization capture rate with scope · point-of-service collection rate.

And the sixth, which nobody has: of encounters that generated a front-end denial, what percentage had a completed clearance checklist? High → your checklist is missing an item. Low → it is not being completed. Different problems, different fixes.

The front end is measured by the back end's failures and staffed by the front end's budget.

The fix is not a new report — it is routing the existing one, weekly, with accounts attached, as feedback rather than discipline.

Key terms

patient access · registration · eligibility verification · 270/271 · coordination of benefits · prior authorization · referral · precertification · predetermination · medical necessity screening · point-of-service collection · financial clearance · MSPQ · clean claim rate · front-end denial rate · batch vs. real-time eligibility · medical identity theft

Monday morning

You should be able to:

• Say what a front-end error costs at each of five points, and the ratio.
• Read an address back instead of asking whether anything has changed.
• Run eligibility three times and know what each run catches.
• Tell a referral from an authorization in one sentence each.
• Record an authorization's scope, not its number.
• Ask for money about method.
• Build an estimate from the allowed amount and say the sentence that goes with it.
• Produce one front-end measure your organization does not currently have.

The Encounter — rewind to check-in.

What the front desk did right: verified eligibility for the date of service · asked whether anything had changed · correctly determined no referral required · correctly determined no authorization required for an established-patient visit · collected the \$30.00 copay.

Better than most practices manage — and the met deductible is what makes Chapter 2's arithmetic work.

What it missed: nothing on the schedule said a procedure might happen.

   COLLECTED AT CHECK-IN ........... $30.00
   ACTUAL PATIENT RESPONSIBILITY ... $47.58
                                     ────────
   BILLED AFTER THE FACT ........... $17.58   ► statement, day 70

Three cheap things: ask what the visit is for · screen the likely procedure for authorization (20610 did not require one — that is luck, not process) · frame the copay as a copay, so the day-70 statement is expected rather than a surprise.

The front desk did nothing wrong and the encounter still produced a surprise.

The front end's failures are usually not errors. They are questions nobody had written down.