Somewhere between residency and today, charting quietly annexed a chunk of your life. Not through any single change — a template tweak here, a payer requirement there, a new consent field, a portal message queue — until the average OD now spends a meaningful slice of every clinic day feeding the record instead of examining patients. The good news: charting time responds to deliberate attack. Here's the sequence that works, cheapest fixes first.
Start with template hygiene
Most optometry EHR templates were configured once, years ago, by whoever had time that week. Before spending a dollar on anything else, spend an afternoon on the templates themselves:
- Build visit-type defaults. Your normal comprehensive exam has a normal slit-lamp exam most of the time. Defaults that pre-populate normal findings — which you then edit by exception — beat building every note from blank.
- Kill the fields nobody reads. Every mandatory field that serves no clinical, legal, or billing purpose is a tax collected forty times a day.
- Standardize plan language. Your dry eye plan, your new-wearer contact lens plan, your diabetic-exam letter: write each once, well, and reuse. You're not being lazy; you're being consistent, which auditors prefer anyway.
Practices are routinely startled by how much time template work alone returns. It's the free tier of this problem.
Delegate the documentation that isn't yours
Look hard at what lands in the note before and after your part of the exam. Tech workups — acuities, IOP, history intake — should be documented by the tech, in the moment, not re-entered or verified keystroke-by-keystroke by you. Post-visit items — patient instructions, order entry, recall setting — can belong to support staff following your plan. Doctors habitually absorb documentation that was never theirs simply because the cursor was already blinking at them. Give it back.
Change when you chart, not just how
Batched charting — seeing patients all morning, documenting at lunch or at night — feels efficient and measurably isn't. Notes written hours later take longer per note (you're reconstructing, not recording) and are less accurate. The discipline of closing each note before the next patient, or at minimum before the next hour, is unglamorous and it works. If your schedule genuinely doesn't allow it, that's not a time-management failure — that's a signal your documentation load exceeds your documentation capacity, which is what the next section is for.
When the answer is a scribe
There's a point past which optimization can't close the gap: your medical volume is growing, notes carry coding weight, and every trick above still leaves you charting after close. That's the profile where a scribe — in-room or virtual — changes the equation rather than the margins, because it removes the doctor from the typing entirely. The economics and mechanics are covered in our scribe guides, but the short version: if you're spending an hour or more a day documenting, the math usually favors handing the keyboard to someone whose whole job is keeping pace with you.
Virtual scribes have made this accessible to practices that could never recruit a trained ophthalmic scribe locally — which, for smaller markets, is most of them.
What about AI documentation tools?
Worth watching, worth trialing, with one caution specific to eye care: ambient AI documents what it hears, and much of an eye exam is seen, not said. Doctors who try these tools in optometry report solid history sections and thin exam sections — fine for conversation-heavy visits, weaker where slit-lamp findings and imaging drive the note. Measure the after-correction time savings before committing. Our full AI-versus-human comparison goes deeper.
A realistic target
Practices that work this sequence — templates, delegation, timing, then scribe support where volume justifies it — commonly cut documentation time dramatically within a quarter, and the after-hours portion is usually first to go. Set your target there: zero routine charting outside clinic hours. It sounds ambitious the way "answered phones" sounds ambitious — right up until the structure exists to make it ordinary.
.png)
.png)
.png)
