Ophthalmology billing
Specialty
Two benefit systems, one patient, and a routing decision made at the front desk.
Scope of work
Where ophthalmology revenue actually breaks
These are the failure points we look for first, in this discipline specifically.
Medical plan or vision plan
Routing is the first decision in nearly every claim and it is made before the exam begins. Route a medical complaint to the vision plan and it is underpaid; route a refractive visit to the medical plan and it is denied.
E/M codes versus ophthalmological service codes
Two code families can describe the same encounter with different documentation requirements and different payer preferences. Choosing by habit rather than by documentation leaves money on the table or invites audit.
Diagnostic testing frequency limits
Imaging and visual field testing are frequency-edited by diagnosis. Testing that is clinically reasonable can still be denied when the interval or the supporting diagnosis is not aligned.
Intravitreal injections and drug units
The drug and the administration are billed separately, with unit counts, wastage documentation and payer-specific product preferences. Unit errors on high-cost drugs are the single most expensive mistake in the specialty.
Bilateral procedures and eye modifiers
Right, left, bilateral and staged-procedure modifiers determine whether the second eye is paid, reduced or rejected as a duplicate.
Cataract episodes and post-operative periods
Surgery carries a global period during which unrelated care must be separately identified, while premium-lens patient responsibility runs alongside the covered claim.
Interactive model
How we run ophthalmology revenue cycle
The operating model is consistent; the controls inside it are specialty-specific.
Routing decides the claim
Pick the reason the patient booked. The benefit the visit should be routed to is decided before the exam begins. Illustrative interaction, not payer policy.
Medical plan
Route here
Vision plan
Not this visit
Medical plan
Not this visit
Vision plan
Route here
Medical plan
Route here
Vision plan
Not this visit
Medical plan
Route here
Vision plan
Not this visit
Medical plan
Not this visit
Vision plan
Route here
Materials and fitting sit with the vision plan.
Illustrative model. Pure Billing verifies both benefits where a patient carries each.
Interactive model
How we run ophthalmology revenue cycle
The operating model is consistent; the controls inside it are specialty-specific.
01
Benefit routing at scheduling
Chief complaint and coverage are checked together so each visit is routed to the medical or vision benefit before arrival, with the reason recorded.
02
Dual eligibility verification
Where a patient carries both, we verify both — including which plan covers refraction, testing and materials — so the front desk is not guessing.
03
Testing and injection charge review
Frequency edits, diagnosis linkage, drug units and wastage documentation are reviewed before submission on every testing and injection claim.
04
Eye-modifier and global-period control
Laterality, staged procedures and post-operative visits are checked against the surgical episode record rather than the encounter alone.
05
Routing-error feedback loop
Monthly reporting separates denials caused by benefit routing from clinical documentation issues, and the routing rules are updated with the front desk.
Relevant services
What we typically run for this specialty
Coding & Charge Posting
Coding and charge posting handled with specialty context, so documentation,
Prior Authorization
Authorization requests initiated, tracked and documented so procedures are not
Eligibility Verification
Coverage, benefits and patient responsibility checked before the visit,
How this specialty is staffed
Ophthalmology accounts are run by a named team that works this discipline daily — charge entry and coding review, payer-specific scrubbing, denial root-cause follow-up and AR recovery, all inside your existing EHR and practice management system.
Get an Ophthalmology Revenue Health Check
A structured review of your ophthalmology denials, AR ageing and front-end workflow — with findings specific to this discipline.
