Dry Eye Billing in 2026: CPT Codes, Documentation & Revenue Leakage for Optometry Practices
A dry-eye test is run, the result lands in the chart, and the claim goes out the door looking clean. A few weeks later the remittance comes back and the payer treated the service differently than the practice expected — paid at a reduced rate, bundled into another line, or denied outright. The front desk re-checks the CPT code. The code was right.
The code was only one part of the problem.
Dry-eye billing in 2026 is not a story about which CPT code pays the most. It's a story about whether the service that was actually performed is documented, coded, submitted and adjudicated the way the applicable payer rules require. That chain — not the code alone — is what this guide is built around.
Why Dry-Eye Billing Is More Than Picking a CPT Code
A CPT code on a claim is not the end of the billing process. It is the beginning of the payer's review.
Once a claim is submitted, the payer checks the code against the diagnosis, the documentation on file (if audited), the patient's benefit design, and its own coverage policy for that specific test or procedure. The sequence that actually determines payment looks like this:
Service performed → Documentation → Medical necessity → Code selection → Payer policy → Claim construction → Adjudication → Payment or denial → A/R → Revenue impact.
Skipping or weakening any one link — vague documentation, an unverified payer policy, a missed modifier — can turn a correctly coded, medically appropriate service into a denial or an underpayment. The revenue opportunity in dry-eye billing is not about choosing the highest-paying code. It is about making sure the service actually performed is documented, coded, submitted and reimbursed according to the rules that apply to that specific payer and that specific patient.
Dry-Eye CPT Codes to Review in 2026
Current CMS practitioner utilization data shows optometry providers reporting 68761, 83516 and 83861 in connection with dry-eye care. That data reflects actual usage patterns — it is not a guarantee that every payer covers every one of these codes for every patient. Each code has its own documentation expectations and its own coverage variability.
CPT 68761: Punctal Occlusion
CPT 68761 (closure of the lacrimal punctum, by plug) is reported per punctum, not per eye — a frequent source of unit errors. Most Medicare Administrative Contractors expect lid-specific modifiers (E1–E4) or RT/LT, and the code carries a global period that affects whether related follow-up visits are separately billable. Documentation should tie the procedure to a specific dry-eye diagnosis, prior conservative treatment where applicable, and the punctum(s) treated. Payers generally bundle the plug material into the procedure payment, though HCPCS supply coding conventions vary by payer and should be verified rather than assumed. A procedure should be performed because it is clinically indicated — not selected because reimbursement may exist.
CPT 83861: Tear Osmolarity / Microfluidic Analysis
CPT 83861 reports microfluidic tear osmolarity testing, billed once per eye when both eyes are tested. Coverage is genuinely split across payers: some current 2026 commercial medical policies list osmolarity testing as potentially reimbursable when ordered to help diagnose or stage dry eye based on a comprehensive eye exam, while applying different — sometimes stricter — criteria to other dry-eye lab tests billed alongside it. A payer's willingness to reimburse 83861 does not extend automatically to every other dry-eye test ordered on the same visit.
CPT 83516: Immunoassay-Based Testing
CPT 83516 is a generic laboratory descriptor — immunoassay for an analyte other than an infectious-agent antibody or antigen — used across many specialties, not a dry-eye-specific code. In eye care it has historically been reported for point-of-care MMP-9 inflammatory marker testing. Several current payer medical policies treat MMP-9/immunoassay testing more restrictively than osmolarity testing, and some Medicare contractors have previously found insufficient evidence that such testing changes treatment outcomes. The device used, the documentation supporting it, and the specific payer's current policy all need to be checked — never assume the code is dry-eye-exclusive or automatically payable.
Are your dry-eye services moving cleanly from clinical documentation to the claim? ➜ Review Your Billing Workflow |
Documentation: The Part of the Claim the Payer Can't See From the CPT Alone
A CPT code tells the payer what was billed. It does not tell the payer why. The chart is what supports that. A well-supported dry-eye claim typically reflects:
• The reason for the evaluation and the patient's reported symptoms
• Objective clinical findings supporting a dry-eye diagnosis
• The specific diagnosis, including laterality where applicable
• Clinical rationale connecting the findings to the test or procedure performed
• The test or procedure performed and its result
• The treatment decision made based on that result
• Follow-up or monitoring plans where relevant
These are general documentation principles reflected in payer and CMS coverage guidance — not a substitute for the specific requirements of the payer a claim is being submitted to.
Medical Insurance vs. Vision Benefits: A Dry-Eye Billing Trap
Practices that handle both medical eye care and routine vision benefits often see dry-eye claims fall into the wrong bucket. Benefit design — not the diagnosis alone — determines which coverage applies.
| Medical Billing | Vision Benefit Billing |
Primary purpose | Diagnosing and treating a medical condition | Routine refractive/vision correction care |
Coverage basis | Medical necessity, diagnosis-driven | Plan-defined routine benefit, often diagnosis-independent |
Typical payer | Medical carrier / Medicare Part B | Vision plan (e.g., routine exam riders) |
Documentation focus | Symptoms, findings, clinical rationale | Refraction and routine exam findings |
Dry-eye fit | Appropriate when evaluation/testing addresses a diagnosed condition | Generally not appropriate for diagnostic dry-eye testing or procedures |
Not every dry-eye encounter belongs under medical insurance — but diagnostic testing and procedural treatment for a diagnosed condition generally does not belong under a routine vision benefit either. The plan's benefit language and the payer's rules decide this, not a default assumption.
Where Dry-Eye Revenue Leakage Can Hide
None of the items below guarantee lost revenue on their own. Each represents a point where a practice's workflow can be worth a closer look.
# | Potential Leak Point |
1 | A test or procedure is performed but not captured on the claim |
2 | Documentation does not clearly support the billed service |
3 | Diagnosis lacks the specificity the payer or coding guidance expects |
4 | Laterality or unit count does not match what was performed |
5 | Payer-specific coverage was not verified before the service or claim |
6 | Medical vs. vision benefit confusion routes the claim incorrectly |
7 | Missing or incorrect modifier affects claim construction |
8 | A recurring denial pattern is resubmitted without finding the root cause |
9 | Payment is posted without reconciling it against the expected allowed amount |
10 | Aging A/R on dry-eye claims is not actively worked |
The 60-Second Dry-Eye Billing Health Check
Educational RCM self-assessment — not a coding determination or payer-coverage decision. Check each item that currently reflects your practice's workflow.
☐ We verify the service actually performed before it's billed
☐ Documentation supports the reported service
☐ The dry-eye diagnosis is specific and supported by findings
☐ Laterality is captured correctly where applicable
☐ Units billed are reviewed against what was performed
☐ Applicable payer coverage is checked before or at claim submission
☐ Medicare NCCI / MUE rules are reviewed where applicable
☐ Commercial payer policies are not assumed to mirror Medicare
☐ Denials are categorized by root cause, not just resubmitted
☐ Payment variances are reviewed against expected allowed amounts
☐ Aging A/R on dry-eye claims is monitored
☐ Our team periodically reviews recurring billing patterns
Scoring Guide
• 0–4 checked: Several workflow controls may need attention.
• 5–8 checked: Your process has useful controls, but gaps may remain.
• 9–12 checked: You have a stronger dry-eye billing monitoring foundation.
Several unchecked boxes above? That may be a workflow signal worth investigating. ➜ Talk to Sirius Solutions Global |
Code → Document → Coverage → Payment
Checkpoint | Question to Ask |
CODE | Was the service coded correctly for what was actually performed? |
DOCUMENT | Does the chart support the service that was billed? |
COVERAGE | Does the applicable payer cover it under their current policy? |
PAYMENT | Did the payer adjudicate the claim as expected? |
If any checkpoint answer is no: investigate before resubmitting. Resubmitting without identifying which checkpoint failed tends to reproduce the same denial.
When a Dry-Eye Claim Denies, Don't Just Resubmit It
The Dry-Eye Denial Root-Cause Test asks six questions before a claim goes back out:
• Was the service covered under the applicable payer policy?
• Was the diagnosis supported by documentation?
• Was the procedure or test coded correctly?
• Did documentation support the claim as submitted?
• Was the payer policy version current at time of service?
• Was the issue isolated to one claim, or is it recurring?
These questions also help a team tell the difference between distinct outcomes that are often lumped together: a denial, a non-covered service, a downcoding, a payment variance, and an A/R delay. Each has a different fix.
Paid Does Not Always Mean Correctly Reconciled
"Paid claim" and "finished claim" are not the same thing. A claim moves through several more steps after adjudication:
Billed → Allowed → Contractual Adjustment → Paid → Posted → Reconciled → A/R Closed
A payment that looks lower than expected is not automatically an underpayment — it may reflect a correct contractual adjustment. But without reconciling the posted payment against the expected allowed amount, a practice cannot tell the difference. That reconciliation step is where real variances (and real revenue) get identified.
2026 NCCI and Payer Policy: What Billing Teams Should Recheck
CMS updates its National Correct Coding Initiative Procedure-to-Procedure edits and Medically Unlikely Edits on a quarterly cycle — new versions took effect across 2026 with each quarter replacing the prior one, alongside routine additions, deletions and revisions. Because these files change quarterly, an edit or unit limit that applied last quarter may not apply today, and a billing team should always check the currently effective NCCI file rather than rely on a saved reference from a prior quarter.
Commercial payer medical policies for dry-eye testing also change independently of Medicare and of each other. Current 2026 policy language from national payers shows real variation: some cover tear osmolarity testing under defined clinical criteria while applying separate, more restrictive criteria to MMP-9 or other immunoassay testing for the same patient population. Treating one payer's dry-eye testing policy as representative of all payers is a documented source of avoidable denials.
When Should an Optometry Practice Review Its Dry-Eye Billing Workflow?
A few recurring signals are worth treating as prompts for a closer look, rather than one-off noise:
• Recurring denials tied to the same code or diagnosis pattern
• Unexplained changes in payment amounts for the same service
• Growing aging A/R specific to dry-eye claims
• Services documented in the chart that don't appear in billing data
• Inconsistent outcomes across payers for comparable claims
• Frequent claim corrections or resubmissions for the same service type
What a Specialty-Specific Optometry RCM Partner Should Actually Do
Generic medical billing workflows don't always account for the specific friction points in optometry — medical vs. vision benefit routing, dry-eye-specific testing policies, punctal procedure modifiers, and ophthalmic coding conventions. A workflow built for optometry should:
☐ Understand medical vs. vision benefit workflows
☐ Apply optometry-specific coding knowledge
☐ Track dry-eye claims through the full lifecycle
☐ Review denials by root cause, not just resubmit
☐ Monitor A/R actively, not just at month-end
☐ Review payment variance against expected allowed amounts
☐ Stay current on payer-policy changes, including quarterly NCCI updates
☐ Provide reporting that's actually meaningful to practice leadership
Conclusion
The goal is not to bill more codes. The goal is to make sure the right services, documentation, coding, coverage and payment all line up.
At Sirius Solutions Global, our team works with behavioral health and medical practices — including optometry — to connect that chain from clinical documentation through to reconciled payment, so revenue cycle issues get identified before they turn into recurring denials or aging A/R.
Frequently Asked Questions
What CPT codes are commonly reviewed for dry-eye billing?
Current CMS practitioner data shows optometry providers reporting CPT 68761 (punctal occlusion), 83861 (tear osmolarity testing) and 83516 (generic immunoassay, often used for MMP-9 testing) in connection with dry-eye care — though coverage for each varies by payer.
What is CPT 68761?
CPT 68761 reports closure of the lacrimal punctum by plug, billed per punctum treated, with lid-specific or laterality modifiers typically required.
What is CPT 83861 used for in dry-eye testing?
CPT 83861 reports microfluidic tear osmolarity analysis, used to help assess dry-eye severity, billed once per eye tested.
What is CPT 83516 used for?
CPT 83516 is a generic immunoassay code, not dry-eye-exclusive, that has been used in eye care for point-of-care inflammatory marker (e.g., MMP-9) testing when supported by the specific device and payer policy.
Does Medicare cover dry-eye testing?
Coverage depends on the specific test, the Medicare Administrative Contractor's current local coverage policy, and documented medical necessity — it is not uniform across all dry-eye tests or all jurisdictions.
Can dry-eye services be billed to medical insurance?
Diagnostic testing and procedural treatment for a diagnosed dry-eye condition are generally medical services, but final routing depends on the patient's specific benefit design and the payer's rules.
Why are dry-eye claims denied?
Common reasons include documentation that doesn't clearly support the billed service, diagnosis specificity issues, unverified payer coverage, modifier or unit errors, and payer policies that differ from what the practice assumed.
How can optometry practices find dry-eye revenue leakage?
By regularly reviewing documentation-to-claim alignment, payer-specific coverage rules, denial root causes, payment reconciliation, and aging A/R — the ten-point leakage framework above is a starting structure, not a complete audit.
Disclaimer
Optometry coding, dry-eye coverage, Medicare requirements, commercial payer policies, documentation standards and reimbursement rules can vary by service, provider, payer and individual circumstances. Policies and coding guidance may 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. |
