New-Patient Registration for Ophthalmology Practices

New-patient registration in ophthalmology is not a form. It is the point where four separate decisions get made about a visit that has not happened yet: how long the appointment needs to be, which provider can take it, whether the visit bills to a medical or a vision plan, and whether the patient can get home afterward. Get any of those wrong at registration and the error surfaces in the exam lane, when there is nothing left to do about it.

Most practices treat registration as data entry that happens after the appointment is booked. In ophthalmology the order runs the other way. A comprehensive new-patient exam with dilation is a longer visit than the template usually offers, the reason the patient is calling determines which subspecialist can see them, and the patient who drove themselves will be sitting in the lobby for two hours after their pupils are dilated. The front desk holds all of that in memory and applies it inconsistently, because it lives in nobody’s system.

What registration decides before anyone sees the patient

New-patient access is the constraint most practices are actually managing. An MGMA poll in 2026 found 46% of medical groups reported new-patient appointment wait times had stayed the same year to date, while 28% said waits were longer.

For an eye practice, a meaningful share of that wait is self-inflicted. The appointment gets booked into whatever slot the schedule offered, the registration work happens later or not at all, and the visit either runs long or gets rebooked. A rebooked new patient is a slot that produced nothing and a patient who now waits another six weeks.

Doing registration at the moment of booking changes what the schedule can hold. The reason for the visit, the insurance, the transportation, and the forms all resolve while the patient is still on the phone or still in the web form, which means the slot that gets held is the right length for the visit that will actually occur.

A generic slot is not a new-patient exam

The central mechanical problem is that scheduling templates speak in generic durations while ophthalmology visits do not.

A template carrying “Any 15” and “Any 30” slots will happily return one of them when a scheduler searches for availability. A new comprehensive exam with refraction and dilation is not a 15-minute visit, and a retina consult is not the same appointment type as a routine glaucoma follow-up even when both show as open on the same provider’s calendar. Which specific appointment types a generic slot is genuinely eligible for, per provider and per department, is the entire mapping problem, and in most practices it exists only in the head of whoever has worked the front desk longest.

Automating registration means writing that mapping down first. The practice defines which reasons map to which appointment types, which providers hold which types, and what each type actually needs for duration. After that the automation can take a caller’s stated reason, match it against the practice’s own mapping, and hold the correct athenaOne appointment type rather than the first open slot it finds.

The second rule that has to travel with it is lead time. New patients commonly cannot book inside three or four business days because the registration packet has to come back first, while established patients can book next business day. Those are two different rules on the same calendar, and a booking engine that does not know the difference will either block established patients unnecessarily or put a new patient in a chair with no completed history.

Dilation makes registration a transportation question

The detail that separates an eye practice from every other specialty is that the visit disables the patient for a few hours.

A dilated exam leaves most patients unable to drive comfortably afterward. Practices know this and tell patients to bring a driver, and the message routinely fails to land because it goes out with the confirmation text that nobody reads, or it never goes out at all because the visit was booked as a generic slot that carried no dilation flag. The result is a patient who declines dilation, which makes the exam less useful, or a patient who waits in the lobby until they feel safe to drive, which occupies a chair and a staff member’s attention.

Handled properly, this is a registration field, not a reminder. If the appointment type includes dilation, the automation asks about transportation at booking, records the answer, and follows up in the outbound confirmation with the specific instruction rather than a generic one. When a patient says they have no ride, that is not a scheduling failure to be solved by the AI. It goes to a person, because the options at that point are practice-specific: move the visit to a day someone can drive them, book without dilation and note why, or offer a time that fits a family member’s schedule.

The same pass confirms the other items an eye exam needs the patient to bring, including current glasses and the contact lens boxes if the visit involves a fitting.

Insurance is two questions in ophthalmology, not one

Eye care is one of the few specialties where the same patient carries two plans that both plausibly cover the visit, and the answer depends on why they are coming in.

A routine refraction for glasses generally runs through a vision plan. A visit for floaters, a diabetic eye exam, or a cataract evaluation is a medical visit and bills to the medical plan. Patients almost never know which is which, and they very often present the vision card because it is the one with a picture of an eye on it. Registering the wrong plan produces a denial weeks later and a patient who was told the wrong thing about their cost.

The registration automation should collect both plans when the patient has both, run the eligibility check against the plan the reason for visit points to, and record the other as secondary information rather than discarding it. Where the reason is ambiguous, the practice’s own mapping decides, and anything that mapping does not cover goes to a human rather than a guess.

Cataract work adds a further wrinkle worth knowing at registration. Medicare Part B may cover cataract surgery that implants a conventional intraocular lens, and the premium lens upgrades most practices offer are a separate patient-responsibility conversation. Capturing that a patient is coming in for a cataract evaluation, rather than a routine exam, is what lets the practice have that conversation on time instead of at checkout.

Where registration stops and the clinic starts

The boundary matters here because registration in ophthalmology sits close to something it must not become.

The automation collects the reason the patient gives in the patient’s own words, matches it to an appointment type using a mapping the practice’s clinicians wrote, verifies coverage, chases the forms, asks about transportation, and books. Every one of those is administrative work with a defined right answer.

What it does not do is decide how urgent the problem is on clinical grounds. A caller describing sudden vision loss or a curtain across their field of view is not a scheduling question, and the automation’s job is to follow the practice’s written escalation path and get a person on the line, not to assess what is happening. Practices define those trigger phrases in advance, clinicians own the list, and the automation applies it identically every time rather than depending on who picked up.

That consistency is the real argument for automating registration. The rules are the practice’s rules. They just stop depending on which of your staff answered the phone.

Key Takeaways

Do registration at booking, not after it. The reason for visit, the plan, the transportation, and the forms all determine what slot the patient should be holding.
Write down the mapping from reason to appointment type before automating anything. A generic “Any 15” slot is not a new comprehensive exam, and that mapping currently lives only in your front desk’s memory.
Carry two lead-time rules, not one. New patients need three to four business days for the packet to return; established patients can book next day.
Treat dilation transportation as a registration field, not a reminder. Ask at booking, record the answer, and route patients with no ride to a person.
Collect both the vision and the medical plan when a patient has both, then verify against the one the reason for visit points to. The wrong card at registration is a denial six weeks later.
Keep the escalation list in your clinicians’ hands. The automation should recognize the phrases they defined and get a person on the phone, never judge how urgent a symptom is.

New-patient registration is worth automating in ophthalmology for the same reason it is usually neglected: it is entirely rule-driven, it happens hundreds of times a week, and every rule in it was written by someone at your practice who is not always the person answering the phone. Handing it to an AI team working inside athenaOne does not change the rules. It just applies them the same way every time, and surfaces the exceptions while there is still time to fix them.

Sources