The Prior Authorization That Wasn't Documented
A hospital's utilization review (UR) team discovers that for 14 Medicare Advantage inpatient stays over five months, the prior authorization was obtained by the attending physician's office but the authorization number was never entered into the registration system. Claims for all 14 were denied as unauthorized; the hospital appealed and won 11, lost 2, and 1 is pending. Combined denied charges are $412,000, with roughly $118,000 ultimately written off. The UR manager wants to add a hard-stop in the EHR that blocks admission without an auth number. The physician group objects, arguing that a hard stop will delay urgent admissions and that EMTALA requires them to accept and stabilize first. Separately, a compliance analyst notes that the hospital has been submitting some of these claims with a modifier indicating authorization was on file, and is unsure whether that was accurate in every case.
1. Evaluate the proposed EHR hard stop against the clinical and legal constraints described.
Read the worked answer
A hard stop on admission is the wrong control because it collides with a legal obligation that cannot be overridden by a billing workflow. EMTALA requires a medical screening examination and stabilizing treatment regardless of authorization status; an admission-blocking rule would either be bypassed routinely (making it useless) or would delay care (making it dangerous). Controls that force clinicians to choose between compliance and patient safety erode both.
Better design - decouple the clinical and financial workflows:
- Soft stop at registration with a time-bound exception path. Admission proceeds; the system flags 'auth pending' and opens a task for UR/registration with a defined window (e.g., 24 hours) to attach the number.
- Auth reconciliation worklist. Because the auth was obtained but not captured, the failure is a handoff problem, not an authorization problem. A daily reconciliation report matching scheduled/urgent admissions against payer auth records catches the gap before claim submission.
- Retrospective auth pathway. For cases where auth genuinely wasn't obtained, a documented UR process to request retro-authorization is far cheaper than appeal.
- Root-cause metric. Track 'auth obtained but not entered' separately from 'auth not obtained' - they have different fixes and the first is the dominant category here (11 of 14 appeals won).
2. The compliance analyst raises the modifier question. What should leadership do, and what is the governing principle?
Read the worked answer
Stop and investigate before submitting anything further. A modifier asserting authorization is on file, applied to claims where that may not be true, is a potential false claim - the intent question is irrelevant to the exposure. The governing principle is that billing representations must be accurate and supportable on audit; a modifier is an attestation, not a convenience field.
Concrete steps:
- Immediate hold on the affected modifier for the identified claim population pending review, with a documented decision by compliance, not by the UR or billing manager alone.
- Look-back. Identify every claim in the affected window where the modifier was applied and test whether auth documentation exists. Quantify overpayment.
- Voluntary disclosure analysis. If overpayments are identified, evaluate self-disclosure obligations under applicable payer contracts and federal program rules with counsel - do not wait for an audit to surface it.
- Root cause and control. The modifier was presumably added to prevent denials. That is precisely the kind of workaround that turns a revenue-cycle problem into a compliance problem. Replace it with a truthful status code and a reconciliation process.
- Culture signal. Leadership should explicitly thank the analyst and make clear that surfacing this is the desired behavior. A near-miss reported internally is a gift; the same issue found by a contractor is a settlement.