Authorization Approved at the Wrong Site of Service
Dr. Okafor orders an MRI of the lumbar spine without and with contrast (CPT 70553) for a 62-year-old with progressive radiculopathy and a history of prostate cancer. The payer portal shows a prior authorization approved for 1 unit of 70553 at place of service 22 (outpatient hospital), effective 03/01 through 03/31. The hospital scanner fails, so on 03/28 the patient is scanned at the freestanding imaging center the group owns (POS 11). The claim bills 70553 with POS 11 and is denied CO-197 (precertification absent). The charge is $1,340. The payer contract requires authorization for advanced imaging at every site of service and states that services rendered outside an approved authorization are not reimbursable. The patient's deductible is met; coinsurance is 20%. The practice has no signed advance beneficiary notice on file.
1. Is this a billing error or a genuine authorization failure, and who should absorb the $1,340?
Read the worked answer
Both, but the weight falls on the practice.
- An authorization is not a yes/no flag; it is a data set: CPT, units, place of service, rendering provider, and effective dates. The practice held a valid number, but the service was delivered outside the approved scope because the POS changed.
- Under the contract language quoted, a service performed outside the approved authorization "is not reimbursable." That allocates the loss to the provider, not the payer.
- The patient is the wrong target. The practice caused the mismatch, no ABN was signed, and the service was medically necessary and covered in principle. Attempting to collect $1,340 from the patient would likely violate the contract's balance-billing terms and create a complaint risk.
- Therefore: pursue retro-authorization/appeal, and if that fails, take the write-off and treat it as a process defect cost, not a patient-balance decision.
2. What actions should be taken in the first 45 days, in priority order, and what documentation supports each?
Read the worked answer
- Confirm the denial reason in writing and pull the exact contract clause on site-of-service authorization. Do not assume the portal note is the whole story.
- Request a retro-authorization or an authorization modification to POS 11 for the 03/28 date of service. Attach: the original auth number and date, the radiologist's report, the order and clinical note showing progressive radiculopathy plus the oncologic history, and a short statement documenting the hospital scanner outage on 03/28 (site contingency).
- File a first-level appeal inside the contractual window. The argument is not "we had an auth" (the payer will point at POS). The argument is: auth existed, medical necessity was met, the site change was an unplanned equipment failure, and the service was performed by an in-network provider at an in-network site. Include the auth record showing § the service and dates.
- Place the patient balance on hold and suppress statements until the payer issues a final determination.
- If the second level also fails, adjust the $1,340 off with a documented reason code and no patient billing.
- Log the root cause in the denial-tracking log so it counts toward the pattern review, not just this claim.
3. The manager wants 'a checklist so this never happens again.' What is the single failure point and what control actually addresses it?
Read the worked answer
Failure point: the authorization was treated as a one-time approval rather than a record that must match the claim line by line. Nothing in the workflow re-verified the auth when the schedule changed.
Controls that address the real risk:
- Make place of service a required field on the auth tracker alongside CPT, units, and date range. If POS is blank, the auth is not considered complete.
- Build a 48-hour pre-service worklist for high-cost modalities (MRI, CT, PET, sleep studies, infusions). Any schedule change or relocation auto-triggers re-verification.
- Give scheduling staff a hard rule: if the approved site is unavailable, either move the patient to another approved POS-22 facility or reschedule - do not substitute a different site and backfill the paperwork.
- Add a claim-scrub rule comparing the POS on the claim to the POS on the stored auth; route mismatches to a human queue before submission.
- Monthly audit: sample 10% of auth-required claims and score POS, units, and date-range match.