Contact Lens Fitting CPT Codes: How to Choose the Right Code

- Remove the current class from the content27_link item as Webflows native current state will automatically be applied.
- To add interactions which automatically expand and collapse sections in the table of contents select the content27_h-trigger element, add an element trigger and select Mouse click (tap)
- For the 1st click select the custom animation Content 27 table of contents [Expand] and for the 2nd click select the custom animation Content 27 table of contents [Collapse].
- In the Trigger Settings, deselect all checkboxes other than Desktop and above. This disables the interaction on tablet and below to prevent bugs when scrolling.
Two contact lens visits can look nearly identical on the schedule and still require different coding. The difference may be the clinical purpose, aphakia status, lens design, laterality, whether the service is therapeutic rather than refractive, or which benefit pathway applies.
Start with the service performed, not the code number. Clinical purpose, lens or service type, aphakia, laterality, and provider role determine the coding path; benefits and payer rules come afterward. CPT and payer guidance can change, so current authorized coding references and payer contracts should be checked before billing.
How do you choose the right contact lens fitting code?
Use the same sequence for each encounter so the code follows the current clinical service rather than a scheduling label, prior code, or default template.
1. Identify the clinical purpose
Start with why the contact lens service is being performed: routine refractive correction, aphakia, ocular-surface disease, keratoconus, or another specialty indication. Disease-management services may move the encounter outside the familiar 92310 family. Do not let the patient's previous code or the scheduling label make the decision for you.
2. Identify the lens or service type
Next, identify whether the service involves a corneal lens, corneoscleral or scleral design, or a therapeutic or bandage lens. The lens label alone is not enough. A large-diameter lens used for keratoconus and a therapeutic lens used for ocular-surface disease may require different coding logic because the clinical purpose is different.
3. Confirm aphakia and laterality
Aphakia materially changes the coding path. CPT 92310 is written for a non-aphakic corneal fitting service involving both eyes, while 92311 and 92312 separate aphakic corneal fitting by one eye versus both eyes. When a non-aphakic corneal fitting is performed for only one eye, verify the current CPT instructions and payer-specific modifier handling before billing rather than assuming the bilateral code can be submitted unchanged.
4. Confirm who performed the fitting
Provider role can change the code family. The 92314-92317 family addresses contact lens prescription and fitting performed by an independent technician under medical supervision and direction. Routine technician assistance in an optometry practice does not, by itself, move a service into that family. Confirm who actually performed the fitting service and verify the current CPT requirements before charge capture.
5. Separate fitting from lens supply
The fitting service and the physical contact lens are different billing concepts. A professional fitting code describes the fitting and prescribing service. HCPCS V-codes may describe the lens or material. The supply may be included in the fitting charge or reported separately depending on the coding and payer rules, so do not assume separate reporting automatically means separate reimbursement.
6. Verify the benefit and payer pathway
After the clinical coding path is clear, determine whether the service is expected under a routine vision benefit, medical benefit, Medicare or Medicaid, or patient responsibility. Verify the benefit and payer pathway, including authorization, frequency, bundling, and specialty-lens rules when they apply. A high-cost lens order is a poor time to discover that the practice and patient were operating under different assumptions.
7. Match the documentation to the claim
Before billing, the record should make the clinical indication, service performed, lens type, laterality when relevant, who performed the fitting, and follow-up plan easy to trace. The code should emerge from the current encounter. If staff have to search old notes or infer the reason for the fitting from the order, the process is already creating downstream risk.
Decision flow: Which contact lens fitting code applies?
Clinical purpose → lens/service type → aphakia + laterality → provider role → fitting vs. supply → benefit verification → documentation
Use the sequence to narrow the coding path before relying on a code table.
Contact lens fitting CPT codes at a glance
The descriptions below are paraphrased rather than copied from official CPT language. Exact code meaning, laterality, modifiers, and payer handling should be confirmed against the current authorized code set and payer guidance.
92310 vs. 92311 vs. 92312: the aphakia and laterality decision
For this coding path, start with aphakia. If the patient is not aphakic and the service is a corneal fitting/prescribing service, 92310 is the relevant both-eyes path. When aphakia applies, laterality separates 92311 from 92312: 92311 is the one-eye aphakia path, while 92312 is the both-eyes aphakia path.
Do not default to 92310 because it is the practice's familiar fitting code. The current service and documentation should support the code selected. When only one non-aphakic eye is fit, confirm the current reduced-service or other payer-specific reporting instructions before submitting the claim.
When might 92313, 92071, or 92072 be the better fit?
92313 and corneoscleral or scleral fitting
92313 belongs to the corneoscleral fitting pathway and is commonly used in specialty-lens workflows involving corneoscleral or scleral designs. The word "scleral" in the chart or order is not enough by itself to settle the coding decision. The service performed and clinical indication still matter, especially when the encounter is disease-specific rather than a general specialty-lens fitting.
Unlike 92310, the 92313 descriptor does not explicitly state one eye or both eyes. Do not assume its bilateral reporting follows the 92310 structure. Verify the payer's current instructions for laterality, modifiers, and units when one or both eyes are fit.
92071 and therapeutic contact lens use
92071 applies to fitting a contact lens for treatment of ocular-surface disease, not simply a refractive fitting performed with an unusual lens. Keep the documentation centered on the therapeutic purpose and service provided, and verify payer-specific laterality and material-billing rules.
92072 and initial keratoconus fitting
92072 is specific to the initial fitting work for management of keratoconus. "Initial" should not be interpreted simply as the patient's first contact-lens visit at your practice or as a code to carry forward for every subsequent lens encounter. The initial-fitting work includes the clinical and diagnostic work used to establish the lens parameters for the keratoconic cornea, and the lens design may be corneal, scleral, hybrid, or another appropriate design.
When a later visit is routine monitoring, adaptation, or follow-up rather than a new fitting, another evaluation pathway may apply. If the existing lens no longer meets the patient's needs and a genuinely new fitting is performed with the full initial-fitting work repeated, current coding guidance may again support the initial-fitting path. Verify the current CPT reference and payer policy rather than assuming either outcome.
The fitting service and the contact lens are separate billing concepts
The professional fitting service and the physical lens are separate billing concepts. The clinician may perform the fitting while another workflow handles lens fulfillment, and those activities may involve different codes and benefit rules.
Treat the fitting code and any HCPCS V-code or material line as separate questions that must still agree with the same encounter. Depending on the code set and payer, lens supply may be included in the fitting charge or reported separately; separate reporting does not guarantee separate payment. For deeper material-code guidance, see RevolutionEHR's Optical Billing V-Codes guide rather than turning this article into a second V-code explainer.
Before the claim: verify the benefit, documentation, and patient responsibility
A technically correct fitting code is only one part of a clean claim. Before the service moves downstream, confirm that the expected benefit pathway, documentation, material billing, and patient communication agree.
Contact lens fitting pre-claim check
- Yes / No: Clinical indication is documented and supports the fitting code selected.
- Yes / No: The expected benefit pathway has been verified as far as the payer allows.
- Yes / No: Authorization, frequency, or bundling rules have been checked when applicable.
- Yes / No: The fitting code reflects the current service rather than a prior visit or template default.
- Yes / No: Lens material or supply coding has been considered separately from the professional fitting service.
- Yes / No: Aphakia, laterality, and who performed the fitting have been confirmed where they affect the code family or reporting method.
- Yes / No: The patient has been told what is verified, what remains uncertain, and what responsibility is currently estimated.
Payer and contract rules vary. Verification reduces avoidable surprises; it does not guarantee coverage or payment.
How connected optometry workflows can reduce contact-lens billing rework
The highest-risk point is often the handoff from clinical care to charge capture, claim review, patient responsibility, and lens fulfillment. When each team works from a different version of the encounter, even a correct code can create rework.
RevolutionEHR brings documentation, billing, claims, and optical workflows into one connected optometry platform. Its contact-lens integrations can also reduce duplicate entry between exam and lens-ordering workflows by carrying patient and prescription information forward. The value is not that software chooses the fitting code; it helps the practice preserve a coding decision that was already made from the current clinical service.
Software should carry a defined human decision forward, not replace the coding judgment that starts with the current clinical service.
Start with the clinical service, then protect the handoff
Choose the fitting code from the current clinical service, then make sure the documentation, benefit pathway, material billing, and claim tell the same story. Connected technology can help preserve that decision downstream, but the coding logic still starts with the encounter itself. See how RevolutionEHR can help keep contact lens documentation, ordering, billing, and claims connected from the exam through final reimbursement by requesting a demo today.