How Often Will Medicare Pay for Visual Fields and OCT in Glaucoma, and Why Do Frequency Denials Keep Happening?

What Actually Stops Glaucoma Frequency Denials Before They Post

The goal is a schedule where every glaucoma test is either within the payer’s frequency allowance or backed by progression documentation that justifies it, so the denial never posts in the first place. Here is what does that, move by move.

1. Run a Pre-Test Frequency Check Against Payer Policy

The denial is a timing problem, so the fix happens before the test, not after. Before a glaucoma visual field or optic-nerve OCT is performed, check the patient’s payer policy and their prior test dates: is this within the allowed frequency for their disease stage, or is it the second test in a window the plan caps at one for a stable eye? A quick pre-test check turns a routine template into a policy-aware one, so the test that would have been denied gets either the documentation it needs or a date that fits the allowance.

2. Prompt the Physician to Document Progression When the Cadence Is Higher

Payers pay for more frequent testing when the record shows it is warranted, so the fix is to make sure the record does. When a patient genuinely needs a field or an OCT more often than the stable-disease allowance, the physician gets a prompt to document the progression, the pressure change, the field defect, the reason a tighter cadence is medically necessary, in the note that supports the claim. The higher-frequency test is payable when the documentation justifies it; the denials come from running the cadence without ever writing down why.

3. Track Denials by Test Code and Payer, Not in Aggregate

A frequency denial hides in a healthy-looking denial rate because it is one code, one payer, a few patients at a time. The fix is to track denials by the specific test code and the specific plan, so a pattern, a particular Medicare Advantage plan denying the second field of the year for stable patients, surfaces in weeks instead of the two quarters it usually takes for someone to notice. What you track by line item, you catch early; what you watch only in aggregate, you find out about at the yield report.

4. Appeal the Denials That Were Actually Justified

Not every frequency denial is correct. When the higher cadence was clinically warranted and the progression was documented, the denial is appealable, and the record proves it. The fix works both sides: prevent the denials that were genuinely outside policy by fixing the cadence, and appeal the ones that were justified by attaching the progression documentation the payer’s automated screen never read. That split is what recovers the revenue you earned without wasting appeals on tests that never should have been scheduled that often.

5. Hand Frequency Denial Prevention to a Dedicated Team

Practices that stop bleeding revenue to frequency denials do it by handing the whole loop to a dedicated team: specialists who run the pre-test check, prompt the documentation, track denials by code and payer, and appeal the justified ones, live in 1 to 2 weeks. The physicians go back to seeing patients, a trained backup covers every gap, and frequency denials stop being the quiet erosion nobody was watching. Below is what it sounds like when nobody owns this yet, in providers’ own words.

Why This Keeps Happening

If the test was appropriate, why does it still get denied? Because Medicare pays glaucoma diagnostics on a frequency calendar, and the scheduling template runs on a clinical one, and the two rarely check each other. For stable disease, Medicare and its Advantage plans generally allow a visual field and a scanning optic-nerve OCT roughly once a year, with more frequent testing payable when higher-risk or progressing disease is documented; the exact caps live in each region’s Local Coverage Determination and each plan’s policy, so treat the specific numbers as payer-dependent. When a template books every stable patient on a fixed six-month cadence without checking that policy, the extra test lands outside the allowance and the payer denies it. It is a timing-and-documentation mismatch, not a clinical one.

The reason it runs for quarters is that a frequency denial is nearly invisible. It does not stop the clinic, it does not generate an angry call, and it does not move an aggregate denial rate that looks healthy, because it is one test code, one payer, a handful of patients a month. Ophthalmology coding guidance is consistent that these frequency edits are among the easiest denials to miss precisely because they hide inside an otherwise clean report. Catching them requires tracking by line item, which is exactly what a dedicated AI denial management workflow is built to surface.

And the cost is a slow erosion rather than a shock. Each denied field or OCT is a small number, but run it across a full glaucoma panel tested on a fixed cadence, and it compounds into a meaningful hit to the yield over a couple of quarters. Worse, some of those denials were genuinely justified, the patient was progressing, and the practice simply never appealed with the documentation that would have paid them. The revenue lost to the denials that should have been prevented is real, and the revenue left on the table from the ones that should have been appealed is on top of it.

Most groups have already tried the obvious fixes before they talk to anyone. Each one fails the same way: the work lands back on the practice. The pattern, in one table:

The Solution

So what does “someone whose whole job it is” actually look like before a glaucoma test? The specialist checks the patient’s payer policy and prior test dates before the field or the OCT is run, so a test that would deny for a stable eye is caught while there is still time to fix it, either by documenting the progression that makes it payable or by moving it to a date inside the allowance. That single pre-test step turns a template that outruns the payer into one that respects the frequency rule, which is exactly what dedicated revenue cycle management is built to protect.

Then comes the two-sided part. When a higher cadence is genuinely warranted, the specialist prompts the physician to document the progression in the note that supports the claim, so the payable test is actually paid. And when a justified test still denies on an automated frequency screen, they appeal it with the progression record attached, recovering the revenue the payer’s screen never read. Meanwhile they track every frequency denial by test code and payer, so a plan quietly denying the second field of the year surfaces in weeks, not two quarters.

Behind all of it, AI drafts the first pass and a credentialed human verifies. The workflow reads the payer frequency policy, checks the prior test dates, and flags the ones at risk; a person confirms the clinical picture, prompts the documentation, and owns the appeal. Every security control that protects the chart data moving through that process is documented and auditable, and the whole approach is described on our HIPAA and security page, because moving clinical documentation through a denial workflow is only safe when the controls are real.

Who Actually Does This Work

Fair question: why would an outsourced team catch these frequency denials better than your own staff? Because reading payer frequency policy and checking it against test dates is their entire day, not the thing they squeeze between roomings. The people working your denials are credentialed medical professionals: overseas-trained physicians, US-licensed nurses and pharmacists, and PharmDs, all trained in US ophthalmology coding and denial workflows. They know how a Local Coverage Determination reads, how a stable-disease frequency cap differs from a progression allowance, and how to write an appeal that attaches the record the payer’s automated screen skipped. That is not a generalist task handed to whoever is free; it is a specialty.

We are not a call center. We are a clinical operations partner, a healthcare BPO built on dedicated virtual staff: 500+ credentialed professionals, 24/7 coverage, and the AI-first-pass plus human-verify workflow you just read about behind every one of them. A typical practice is live in 1 to 2 weeks, at up to 70% below the cost of hiring locally, and no one on our side goes out without a trained backup already inside your workflow, so a frequency-denial pattern never runs for two quarters because the one person who watches it is on vacation.

And the security piece your compliance officer will ask about: we are audited to SOC 2 Type II with zero exceptions and certified for ISO/IEC 27001:2022, HIPAA, and GDPR, with zero breaches in eight years. Every workstation runs inside a secure enclave on US-based servers, with screen captures and downloads blocked by policy, so PHI never sits on someone’s home laptop. Every client account carries a $5M E&O and cyber liability policy and a BAA signed before any work starts; the full detail lives in our HIPAA and security posture.

Put the routine and the people together, and a specific list of things simply stops happening.

How We Permanently Fix the Process

A person alone is not the fix, and neither is a smarter template alone. The fix is a documented frequency workflow: which payers cap which glaucoma test at what frequency for which disease stage, the pre-test check that runs before every field and OCT, the documentation prompt for a warranted higher cadence, and the appeal path for a justified denial, all written down and worked the same way every time. Before we run a single check for a new practice, we chart your frequency denials by test code and payer so we can see exactly where the template and the policy are colliding, and we build the workflow against that, not a generic edit list.

From there the workflow becomes a living playbook rather than tribal knowledge in one coder’s head. It records each payer’s frequency policy and how it changes, the disease-stage triggers for a higher cadence, how progression should be documented to support the claim, and the exact appeal packet for a denied but justified test. It is written down, kept current as payers revise their Local Coverage Determinations, and owned by the team. When your specialist is out, a trained backup works the same playbook the same way, so the frequency check never lapses because one person is gone.

That is the difference between reworking this quarter’s denials and fixing the process for good, and it is what a dedicated denial management partner actually buys you. A coder leaving used to mean the frequency edits stopped getting caught and the yield started eroding again. Under this model the pre-test check keeps running, the playbook stays, the backup steps in, and frequency denials stop being the quiet drain nobody was watching.

The Whole Thing in Four Sentences

Medicare and its Advantage plans generally pay for a glaucoma visual field and an optic-nerve OCT about once a year for stable disease and more often only when progression is documented, so frequency denials keep happening because scheduling templates book testing on a fixed cadence that ignores the payer’s frequency policy. Booking on a fixed calendar, watching only the aggregate denial rate, or running higher-frequency tests without documenting progression all fail the same way. The fix is a pre-test frequency check against payer policy, a progression-documentation prompt, denial tracking by code and payer, and appeals on the justified ones. An eye-care group runs exactly this model with us today, names withheld, no patient data shown.

If you want to check us out before talking to anyone: our security posture is independently auditable, we are an MGMA 2026 Corporate Member, and 800+ providers run back office work with us.

Ready to stop losing tests to frequency denials? Try us risk free: two weeks, your real glaucoma denial pattern, a dedicated specialist running the pre-test checks and working the appeals, and if it does not earn the handoff, you walk away. From here down is the sales part, and it is short: here is exactly what it costs.

Written By

Dan Nandan

Founder and CEO, Staffingly, Inc. · Piscataway, NJ

Dan Nandan has spent 25+ years in IT consulting and healthcare BPO, was among the first in the US to build an RPO/BPO delivery network in India, and has been featured in Computerworld. He runs the operations and the dedicated virtual teams behind the workflows on this page; the team-voice answers above come from the remote specialists who work them every day.

Connect on LinkedIn

Where the Claims on This Page Come From