Table of Contents
Introduction
A patient walks into a Kentucky optometry practice with an active insurance card. The exam is completed, the visit looks routine, and the claim goes out. Nothing seems obviously wrong — until the payment comes back lower than expected, or the claim quietly lands in A/R and sits there.
The problem may not have started at the payer. By the time a claim reaches adjudication, several earlier decisions have already shaped whether it gets paid correctly, paid partially, or not paid at all — decisions made before the claim ever left the practice.
This article walks through where that kind of revenue leakage tends to hide in an optometry billing operation, what's specifically relevant for Kentucky practices in 2026, and how to start finding the gaps systematically.
What Revenue Leakage Looks Like in an Optometry Practice
Revenue leakage isn't always a denied claim. It can be a billable service that was never captured, a claim built with a classification or code that didn't match what actually happened, a payment that was never checked against what the contract or fee schedule expected, or an A/R balance that aged quietly while staff focused on new claims. Not every missed dollar should necessarily be billed — some represent services correctly left off a claim. The goal isn't billing everything possible; it's making sure the workflow isn't losing money it was actually owed.
The Medical vs. Vision Billing Divide
This is one of the most consistent sources of friction in optometry billing, and it deserves care rather than a shortcut. Medical eye care and routine vision care are governed by different coverage logic, different documentation expectations, and often different payers entirely.
| Area | Medical Billing | Vision Billing |
|---|---|---|
| Purpose | Diagnosis and treatment of eye-health conditions | Routine, refractive care |
| Coverage | Medical plan, subject to medical necessity | Vision plan benefit design |
| Documentation | Must support medical necessity and diagnosis | Standard exam documentation |
| Payer rules | Payer-specific medical policy applies | Plan-specific benefit rules apply |
| Common workflow risks | Necessity assumed but not documented | Refraction billed as if medically necessary |
Current Medicare guidance indicates that Original Medicare generally doesn't cover routine eye exams performed for eyeglasses or contact lenses. That's not the same as saying Medicare doesn't cover optometry — certain medically necessary ophthalmic services, and specific covered screenings, can be payable under applicable conditions. The distinction matters operationally: a visit that mixes a routine refraction with a medically necessary evaluation may need both classifications handled correctly on the same claim, or across separate payers entirely.
Kentucky Medicare Billing in 2026 — Why the MAC Matters
For Kentucky practices billing Original Medicare Part A and Part B fee-for-service claims, the applicable Medicare Administrative Contractor is CGS Administrators, LLC, under A/B MAC Jurisdiction 15 (J15), which also covers Ohio. That means J15's current local coverage determinations, billing and coding articles, and administrative requirements apply to Kentucky Medicare FFS claims specifically.
This doesn't mean every Kentucky optometrist follows CGS rules for every claim. Medicare Advantage plans administer their own coverage and claims rules, which may differ from Original Medicare FFS. Commercial medical and vision payers set their own requirements entirely, independent of CMS or CGS guidance. A Kentucky practice's actual payer mix usually spans several of these categories at once, which is exactly why knowing which rules apply to which claim matters more than treating “Kentucky” as a single rulebook.
Two Medicare-covered screening services worth knowing in this context: Medicare Part B covers glaucoma screening once every 12 months for patients meeting specific high-risk criteria (diabetes, family history of glaucoma, or certain demographic risk factors), and Medicare Part B helps cover an annual diabetic eye exam for beneficiaries with diabetes. Both are subject to the applicable frequency limits, eligibility criteria, and documentation expectations — they aren't automatic for every patient, and they should be billed and documented to reflect why the specific patient qualified.
8 Places Revenue Leakage Can Hide
| Potential Revenue Leak | What to Check | Why It Matters |
|---|---|---|
| Medical vs. vision classification | Visit reason and services against the correct billing path | Wrong path can mean denial or incorrect patient cost |
| Eligibility / benefit verification | Active coverage, medical and vision benefits separately | Active coverage isn't the same as a covered, payable service |
| Documentation mismatch | Note against what was actually billed | Unsupported services are a common denial driver |
| Diagnosis-to-service linkage | Diagnosis supports the medical necessity of the service | Weak linkage invites denial or downcoding |
| Coding / modifier errors | Codes and modifiers reflect the documented service | Mismatches can trigger denial or incorrect payment |
| Payer-specific edits | Current payer and NCCI-related requirements | Edits change and vary by payer |
| Payment posting / reconciliation | Paid amount against allowed/contracted amount | Underpayments often go unflagged without this step |
| Aging A/R / recurring denials | Claims by age bucket and denial pattern | Unworked claims and repeat issues compound over time |
Why a “Clean Claim” Can Still Become a Revenue Problem
A claim can be coded correctly, submitted on time, and still run into a payer rule the practice didn't anticipate — a frequency limitation already used for the year, a network-status issue, a benefit-design exclusion, or a medical-necessity standard the documentation didn't quite meet. Service performed doesn't automatically equal payment approved. Coverage limitations, documentation, network status, and claim edits all sit between the two.
Paid Doesn't Always Mean Correctly Reconciled
A payment landing in the bank doesn't close the loop by itself. Comparing what was billed against what was allowed, what was contractually adjusted, what was actually paid, and what moved to patient responsibility is how a practice catches underpayments and systematic payer issues — most go unnoticed without that comparison, not because anyone made an obvious mistake, but because nobody looked.
Denial, Downcoding, Non-Coverage, or Underpayment?
| Term | What It Means |
|---|---|
| Denial | The payer rejected the claim outright as submitted |
| Downcoding | The payer reimbursed at a lower code or level than billed |
| Non-coverage | The specific service isn't covered under the applicable plan or policy |
| Underpayment | Payment is lower than the applicable contract or fee schedule specifies |
| A/R delay | The claim is simply unresolved, not yet a denial or payment |
Calling every lower-than-expected payment a “denial” — or every denial an “underpayment” — can send the follow-up effort in the wrong direction before it even starts.
Kentucky Optometry Revenue Leakage Self-Check — 60 Seconds
| Self-Check | Done |
|---|---|
| We verify medical vs. vision benefits before billing | |
| Our team verifies active eligibility | |
| Our documentation supports the services reported | |
| We review current payer requirements | |
| We review relevant Medicare guidance where applicable | |
| Our coding workflow is reviewed for current CPT updates | |
| We monitor recurring denial categories | |
| We review downcoded claims | |
| We reconcile payments against expected reimbursement where applicable | |
| We monitor aging A/R | |
| We identify recurring root causes rather than correcting the same claim repeatedly | |
| We know which claims are delayed because of workflow issues |
This self-check is educational and does not determine coding accuracy or reimbursement eligibility.
Where Is Your Optometry Revenue Leak?
| Area | What to Check | Possible Warning Sign |
|---|---|---|
| Medical vs. Vision | How visit reason determines the billing path | Same workflow used for every visit regardless of reason |
| Eligibility | Active coverage checked separately for medical and vision | Coverage assumed from a prior visit |
| Documentation | Note supports the service billed | Templates don't capture medical necessity clearly |
| Coding | Codes and modifiers match documentation | Same codes used regardless of service complexity |
| Payer Rules | Current payer-specific requirements | Rules not reviewed since they were last updated |
| Denials | Root cause tracked, not just resubmission | Same denial reason recurring |
| Payment Posting | Paid amount reconciled against expected amount | Payments posted without a variance check |
| A/R | Aging buckets actively worked | Older claims deprioritized behind new ones |
Educational RCM self-assessment — not a coding determination, payer validation tool, or financial guarantee.
Denial → Root Cause → Prevention: The 5-Question Review
- Why did the payer reject or reduce the claim?
- Is it a coding issue, coverage issue, documentation issue, or administrative issue?
- Is this isolated or recurring?
- Can the issue be prevented upstream?
- Is the financial impact being tracked?
Denial Root-Cause Decision Tree
The point of the tree isn't to label every claim issue the same way. It's to work through the questions in order until the actual cause is identified — then decide whether the fix belongs upstream, in the claim itself, or in the follow-up process.
2026 Optometry Billing Workflow: What Should Be Reviewed?
We're not aware of a major optometry-specific CPT change for 2026 that would justify rewriting a practice's entire coding workflow — the more consistent 2026 story is a payer-policy and workflow-monitoring one: current Medicare guidance, current MAC requirements, current payer-specific edits, and whether the practice's own claim-building process has kept pace with any of it.
How Sirius Solutions Global Supports Optometry Billing
Sirius Solutions Global supports optometry practices across medical billing, revenue cycle management, claims management, denial management, A/R follow-up, payment posting, eligibility verification support, billing workflow review, and RCM reporting. For Kentucky practices, that includes tracking how J15/CGS guidance, Medicare Advantage variation, and commercial payer requirements intersect with a practice's actual medical-versus-vision billing workflow.
We don't promise guaranteed revenue recovery, zero denials, guaranteed collections, or guaranteed reimbursement improvement — no billing partner honestly can. What we focus on is helping practices see where a claim, a payment, or an aging balance may be telling a story worth a closer look.
FAQ
DISCLAIMER: Optometry coding, Medicare coverage, commercial payer policies, vision benefits, documentation requirements and reimbursement rules can vary by payer, service, diagnosis, provider status and individual circumstances. Policies and billing requirements can change. This article is provided for general educational purposes only and is not a substitute for current CPT, CMS, MAC or payer-specific coding, billing, legal or compliance guidance.
Conclusion
Revenue leakage is rarely one dramatic event. More often, it's a series of small workflow gaps — a classification assumption, a documentation shortcut, a payment nobody reconciled, a claim that aged quietly — that keep repeating until they add up.
Finding them starts with asking where, specifically, a claim could have gone sideways between the exam room and the bank account.