Prior Authorizations in Ophthalmology: Injections, Surgery, and Imaging

Prior authorization is a burden everywhere in medicine, but ophthalmology's version has a distinguishing feature: it recurs by design. The retina patient on anti-VEGF therapy doesn't need one authorization — they need one per treatment cycle, indefinitely. Add surgical approvals, advanced imaging, and specialty medications, and a mid-sized practice runs an authorization operation whether it admits it or not. The only question is whether that operation has structure and an owner, or runs on sticky notes and heroics.

Where the volume comes from

Anti-VEGF injections dominate. Payers manage these expensive agents aggressively: step-therapy requirements that dictate which drug comes first, authorizations that expire after a set number of doses or months, and re-authorization demands supported by documented response to treatment. A retina practice's auth pipeline is effectively a subscription-renewal business run against deadlines with clinical consequences.

Surgery comes second: cataract procedures for some payers, and more consistently the adjacent categories — premium diagnostics, certain lens implant scenarios, oculoplastics procedures where medical necessity documentation (visual field impact, photographs) decides the outcome.

Imaging and diagnostics round it out, payer-dependent: OCT frequency limits, fundus photography rules, and the quiet trap of frequency denials — services that needed no authorization but exceeded an unpublished per-year count.

The pipeline that works

Practices that handle auth volume without treatment delays run it as a literal pipeline with stages and dates:

• Intake: every auth-requiring event enters the tracker the day it's ordered — injection scheduled, surgery booked, imaging planned — with payer, procedure, and needed-by date.
• Submission: auths go out within a day of intake, with the documentation each payer wants attached the first time. The chart note that supports medical necessity — where scribe quality quietly becomes revenue protection — is the payload.
• Tracking: every pending auth has a status and a next-action date. Silence from a payer is not a status; it's a follow-up call scheduled three business days out.
• Expiration watch: the tracker flags auths expiring within thirty days for patients with continuing treatment — the single most valuable alert in retina, where an expired auth discovered on injection day means a rescheduled patient and a disrupted treatment interval.
• Denial lane: denied auths route immediately to peer-to-peer scheduling or appeal, with the clinical rationale packaged for the doctor. Speed matters; so does not letting these sit.

The ownership question

Everything above fails without a named owner, and the owner's defining requirement is uninterrupted follow-through — auth work is phone queues, portal checks, and documentation assembly, all of it hostile to the interrupted rhythm of a clinical front office. This is why dedicated auth specialists, increasingly remote, have become standard in high-volume ophthalmology: a trained virtual team member who owns the tracker end to end, submits same-day, works the follow-up queue every morning, and escalates only the exceptions. Practices that make this move typically measure the change in two places — auth turnaround time and treatment-delay incidents — and both tend to move within the first sixty days.

The clinical stakes deserve the last word. An authorization delayed is not paperwork delayed; it's an injection interval stretched, a surgery postponed, a disease given schedule slack it doesn't deserve. Practices that treat auth operations as revenue administration get modest returns. The ones that treat it as treatment logistics — with the urgency that framing implies — protect both the schedule and the patients on it.