Doctora automatically extracts contact lens data from your exam narration and syncs it to your EHR. This article covers what gets captured, how to review it, and how to get the best results.
AI extraction from exam narration
When you narrate a contact lens fitting or evaluation during an encounter, Doctora's dedicated contact lens AI worker listens for relevant details and extracts them into structured data. This runs as a separate processing stage from the main EHR extraction, using a specialized model tuned for contact lens documentation.
The system distinguishes between current lenses (what the patient wore into the exam) and trial lenses (diagnostic or trial lenses dispensed during the visit). Each lens entry captures per-eye parameters for both OD and OS independently, so mixed-brand or asymmetric prescriptions are fully supported.
What fields are captured
For each contact lens service, Doctora extracts:
- Brand name -- matched against your practice's inventory (see below)
- Per-eye parameters (OD and OS independently): base curve, diameter, sphere, cylinder, axis, and add power
- Visual acuity with contacts -- distance VA achieved while wearing that specific lens, reported as Snellen fractions for OD, OS, and OU
- Fit assessment -- whether the fit is acceptable, plus per-eye lens rotation, movement, and over-refraction (sphere/cylinder/axis)
- Dispensed status -- whether the lens was given to the patient
- Comments -- any additional notes, including patient quotes about comfort or vision
Doctora also automatically generates refractive diagnosis ICD-10 codes (myopia, hyperopia, astigmatism) based on the extracted contact lens prescription powers. These appear alongside your other diagnoses without any extra work.
Contact lens inventory sync
For practices using RevolutionEHR, Doctora syncs your contact lens product inventory directly from the EHR. This happens automatically through the Chrome extension and stores your full product catalog--including product specifications like available base curves, diameters, sphere ranges, and step sizes for each product.
This inventory sync serves two purposes:
-
Brand matching -- When the AI extracts a brand name from your narration, it fuzzy-matches against your actual inventory. This ensures the brand name, product ID, and location product ID are correct for your EHR, even if you say the name slightly differently than it appears in the system.
-
Parameter auto-fill -- If a lens has only one available base curve or diameter, Doctora fills it in automatically. For lenses with a range of options, inventory data constrains the valid values shown in the editor dropdowns.
The inventory is filtered to remove duplicate pack-size variants (e.g., if you stock both 30-pack and 90-pack of the same lens, only one entry is used for matching, preferring the 90-pack).
CrystalPM also supports contact lens data sync, mapping current and trial lens parameters (up to three trial slots) through its field-based encounter format.
Reviewing contact lens data in the editor
The Doctora editor displays contact lens services in a dedicated section. Each lens entry shows as an expandable card labeled either "Current" or "Trial." From the editor you can:
- Add or remove lens entries
- Toggle a lens between current and trial
- Search and select products from your synced inventory
- Edit all per-eye parameters using dropdowns constrained by the product's valid ranges
- Review and adjust visual acuity, fit assessment, and over-refraction values
- Mark whether a lens was dispensed
The editor sorts lenses so the current lens always appears first, followed by trials.
EHR sync
When you sync an encounter, contact lens data is written back to your EHR as part of the normal sync process. In RevolutionEHR, this is handled by a dedicated ContactLensProcessor that writes three distinct record types:
- Current contact lens -- the lens the patient was wearing
- Trial lenses -- any diagnostic or trial lenses evaluated during the visit
- Fit evaluation -- over-refraction, rotation, movement, and assessment notes
Each is written to the appropriate section of the RevolutionEHR encounter via its API.
Tips for best contact lens extraction
- Say the brand name clearly. The AI matches what you say against your inventory, so using the product name as it appears in your EHR gives the best results. Saying "Acuvue Oasys" works; mumbling a partial name may not match.
- Specify per-eye parameters. State powers, base curve, and diameter for each eye separately, especially if they differ. "Right eye minus 3.00, left eye minus 2.75" is clearer than "about minus 3 both eyes."
- Distinguish current from trial. Say "the patient came in wearing..." for current lenses, and "I placed a trial lens..." or "I'm fitting them in..." for trials.
- State contact lens VA explicitly. If you check acuity with the contacts on, say so: "With contacts, 20/25 right, 20/20 left." The AI will not copy best-corrected or manifest VA into the contact lens section--it only uses VA that you explicitly associate with the contact lens.
- Mention over-refraction when performed. "Over-refraction OD plano, OS minus 0.50" gets captured; if you skip it, those fields stay empty.
- Note dispensing. If you hand the patient trial lenses to take home, say "dispensed" so the record reflects it.