Claude CoWork for Optometrists

What is Claude CoWork?

Claude CoWork is the practice of using Claude as a dedicated, context-aware assistant that plugs directly into your optometry workflow. Instead of starting from scratch every time you open a chat window, you configure Claude with your practice context, documentation preferences, and clinical style so it consistently produces output that is useful from the first draft.

Claude-native prompts. The prompts in this guide use Claude's native XML tag structure (<context>, <instructions>, <format>, <avoid>) for more precise, consistent output. These tags help Claude parse your intent with less ambiguity. They work in ChatGPT too, but are optimized for Claude.

Optometrists manage a unique documentation load that spans clinical care and administrative overhead. Exam notes that must capture detailed findings across multiple systems, insurance narratives that justify medical necessity for everything from specialty lenses to cataract referrals, patient education handouts that translate complex diagnoses into actionable guidance, and referral letters that clearly communicate your clinical reasoning to ophthalmologists and other specialists. These tasks are essential but repetitive, and they are exactly where Claude adds the most value.

This guide shows you how to configure Claude for optometry-specific work, the five workflows that will reclaim the most time in your day, and the privacy guardrails that are non-negotiable in a clinical setting.

Install the Optometrist Plugin

This guide works on three Claude surfaces. The plugin is the fastest path on two of them. Pick whichever you use:

If you're on Cowork (desktop or mobile app)

Claude Cowork is Anthropic's agentic workspace — Claude completes work autonomously and returns finished deliverables. The Optometrist plugin packages the workflows below as native skills and slash commands.

Open the Cowork plugin directory in your desktop app.
Filter by Cowork, search for "Optometrist", and click Install.
The plugin's slash commands and ambient skills are now available in any Cowork task.

If you don't see the plugin in the directory yet, install via custom marketplace: paste https://github.com/alexclowe/awesome-claude-cowork-plugins in your Cowork plugin settings.

If you're on Claude Code (CLI)

Install from your terminal:

claude plugin add alexclowe/awesome-claude-cowork-plugins/optometrist

The plugin's slash commands and skills load on next session.

If you're on Claude.ai (web chat only)

Plugins aren't directly installable on the web chat surface. You have two options:

Use the prompts in this guide directly in a Claude Project (covered in the next section). Same outputs, more typing.
Upload the plugin's skills as a zip via Settings → Features → Custom Skills (Pro/Max/Team/Enterprise plans). Higher friction; only worth it if you want the auto-activating skills, not the slash commands.

What the plugin gives you (any surface)

Slash command	What it does
`/exam-note`	Draft comprehensive eye exam documentation with findings, refraction, and assessment/plan
`/referral-letter`	Create specialist referral letters to ophthalmologists with clinical findings and consultation requests
`/patient-education`	Generate vision care education materials and post-visit instructions for patients
`/insurance-narrative`	Write medical necessity letters for vision procedures with clinical justification

Auto-activating skills (no command needed — Claude applies them when relevant):

Clinical Optometry — Comprehensive eye examination, ocular disease documentation, contact lens fitting, and refractive assessment
Patient Communication — Vision care education, treatment option explanation, compliance counseling, and post-visit instructions

The plugin works standalone for one-off tasks. Pair it with the surface-specific setup below for persistent context across every task — that combination is the full Claude CoWork setup.

Setting Up Claude for Optometry Work

Surface note: The Project setup below is for claude.ai web users. Cowork users have their own task-context mechanism (set context once when starting a Cowork task). Claude Code users get the plugin's ambient skills automatically — no Project setup needed. The workflows themselves are surface-agnostic — paste the prompts wherever you're working. Step 1: Create an Optometry Project. In Claude, go to Projects and create one called "Optometry Practice" or similar. This is your persistent workspace with context that carries across conversations.

Step 2: Set your custom instructions. In the Project settings, add:

You are my optometry documentation assistant. Here is my context:

<practice-profile>
- Role: [OD / Associate OD / Practice Owner / Residency-trained OD]
- Specialty focus: [General / Ocular disease / Pediatric / Contact lens / Low vision / Neuro-optometry]
- State: [Your State]
- EHR system: [RevolutionEHR, Crystal PM, EyeMD EMR, Compulink, etc.]
- Common payers: [List your top 3-5 insurance companies and vision plans]
- Documentation style: [Problem-oriented, SOAP format, assessment-plan focused]
</practice-profile>

<rules>
- Exam notes should follow AOA documentation guidelines
- Always include pertinent positives and negatives for documented diagnoses
- Insurance narratives should emphasize medical necessity using ICD-10 specificity
- Patient education materials should use plain language at an 8th-grade reading level
- Never generate content for a specific identifiable patient — all scenarios must use de-identified information
- Remind me to verify all clinical details before finalizing documentation
</rules>

Step 3: Upload your templates. Add your preferred exam note template, referral letter format, any payer-specific medical necessity criteria you reference frequently, and your standard patient handout format.

Step 4: Always work inside this Project. Every new conversation inherits your context automatically.

Your Top 5 Workflows with Claude

1. Comprehensive Exam Notes

Documenting detailed eye exams with multiple findings across anterior segment, posterior segment, and functional testing is time-intensive. Claude drafts structured notes from your clinical shorthand.

<task>Draft a comprehensive optometric exam note from these findings (de-identified patient).</task>

<context>
- 62-year-old female, annual medical eye exam
- CC: Blurry near vision worsening over past 6 months, occasional dry eye symptoms
- Entering VA: OD 20/25, OS 20/30, OU 20/25
- Refraction: OD -1.75 -0.50 x 180, OS -2.25 -0.75 x 175, Add +2.25
- BCVA: OD 20/20, OS 20/20
- IOP: OD 16, OS 17 (Goldmann)
- Pupils: PERRLA, no APD
- SLE: Grade 2 nuclear sclerosis OU, 1+ meibomian gland dysfunction OU, TBUT 6 sec OU
- DFE: C/D 0.3 round OU, mild RPE mottling macular OU, flat and attached retina 360 OU
- OCT: Normal RNFL OU, mild drusen noted macular OS
</context>

<instructions>
Format as a structured medical exam note. Include assessment with ICD-10 codes and a detailed plan. Flag the early macular changes and dry eye for monitoring.
</instructions>

<avoid>Patient identifiers, definitive diagnoses beyond what the findings support.</avoid>

Before Claude: 10-15 minutes per comprehensive exam note. After Claude: 3 minutes to input findings, 3 minutes to review and finalize.

2. Insurance Narratives for Medical Necessity

When vision plans deny coverage or medical claims need justification, a precise narrative makes the difference. Claude structures the clinical argument from your findings.

<task>Draft a medical necessity narrative for cataract surgery referral.</task>

<context>
- 71-year-old male, retired, active lifestyle (golf, driving)
- BCVA with current Rx: OD 20/40, OS 20/50
- Glare testing: Significant reduction OU, particularly OS
- Diagnosis: Age-related nuclear cataract OU, worse OS (H25.13)
- Functional impact: Difficulty driving at night, cannot read scorecards on golf course, reports near-misses while driving due to glare
- Conservative measures tried: Updated refraction, anti-glare coating, recommended sunglasses — symptoms persist
- Referring to: Dr. [Ophthalmologist] for cataract evaluation OS, with plan for OD to follow
</context>

<instructions>
- Emphasize functional impairment and failed conservative treatment
- Use medical necessity language consistent with Medicare LCD for cataract surgery
- Include Snellen acuity, glare testing results, and functional limitations
- Format as a narrative suitable for inclusion in a referral packet
</instructions>

<avoid>Guaranteeing surgical outcomes, overstating findings beyond documented evidence.</avoid>

Before Claude: 15-20 minutes crafting the narrative from scratch. After Claude: 3 minutes to input clinical data, 4 minutes to review and customize.

3. Patient Education Handouts

Patients retain more when they leave with something written in language they understand. Claude generates condition-specific handouts tailored to your practice.

<task>Create a patient education handout about dry eye disease.</task>

<context>
- Target audience: Patients newly diagnosed with evaporative dry eye / meibomian gland dysfunction
- Reading level: 8th grade, no clinical jargon
- Practice offers: In-office treatments (LipiFlow, IPL), warm compress kits, and preservative-free artificial tears
</context>

<instructions>
Include:
- What dry eye is (brief, simple explanation)
- Why meibomian glands matter (one paragraph)
- At-home care steps (warm compresses, lid hygiene, omega-3s, hydration)
- When to use artificial tears and which type to look for
- What in-office treatments are available and when they are recommended
- When to call the office (worsening symptoms, pain, vision changes)

Keep it to one page. Use short paragraphs and bullet points.
</instructions>

<avoid>Brand names for medications, guarantees about treatment outcomes, language that could be construed as medical advice for undiagnosed conditions.</avoid>

Before Claude: 30-45 minutes to write and format a handout from scratch. After Claude: 5 minutes to generate, 5 minutes to customize for your practice.

4. Referral Letters to Ophthalmology

Clear, concise referral letters strengthen your relationship with specialists and ensure continuity of care for your patients.

<task>Draft a referral letter to a retinal specialist for a de-identified patient.</task>

<context>
- 58-year-old female with Type 2 diabetes, diagnosed 12 years ago, HbA1c 8.2%
- Annual diabetic eye exam findings:
  - BCVA: OD 20/20, OS 20/25
  - DFE: OD — scattered dot-blot hemorrhages, 2 cotton wool spots, no NV; OS — dot-blot hemorrhages, microaneurysms, clinically significant macular edema suspected
  - OCT macula: OD — normal foveal contour; OS — central subfield thickness 340 microns with intraretinal fluid
- Assessment: Severe NPDR OD, severe NPDR with DME OS
- Urgency: Within 1-2 weeks
</context>

<instructions>
- Format as a professional referral letter
- Include all relevant findings and OCT data
- Clearly state the reason for referral and urgency
- Keep it under 300 words
- End with your availability for co-management
</instructions>

<avoid>Treatment recommendations that are outside optometric scope for this case, patient identifiers.</avoid>

Before Claude: 12-15 minutes composing a detailed referral letter. After Claude: 3 minutes to input findings, 3 minutes to review and send.

5. Follow-Up and Recall Communications

Proactive patient communication improves outcomes and retention. Claude drafts follow-up messages for various clinical scenarios.

<task>Draft a follow-up communication template for patients with glaucoma suspect findings.</task>

<context>
- Scenario: Patients with elevated IOP, suspicious optic nerve appearance, or borderline OCT findings who need to return in 3-6 months for repeat testing
- Communication type: Letter or secure message template
- Goal: Explain why follow-up matters without causing unnecessary alarm
</context>

<instructions>
Include:
- A brief explanation of what "glaucoma suspect" means in plain language
- Why the follow-up visit is important (tracking changes over time)
- What tests to expect at the next visit (OCT, visual field, IOP)
- A clear call to action to schedule the appointment
- Reassurance that early monitoring is a proactive, positive step

Tone should be warm, professional, and reassuring — not alarming.
</instructions>

<avoid>Diagnosing glaucoma, making prognosis statements, using technical terms without explanation.</avoid>

Before Claude: 20-30 minutes writing and refining a template. After Claude: 5 minutes to generate, 5 minutes to adjust tone and practice details.

Prompt Engineering Tips for Optometrists

1. Include both eyes separately. Claude writes better exam documentation when you provide OD and OS findings individually rather than lumping them together. Asymmetric findings are clinically significant and should be documented that way.

2. Specify the payer for insurance narratives. Medicare, VSP, EyeMed, and commercial medical plans all have different medical necessity standards. Telling Claude which payer the narrative is for produces more targeted language.

3. Always state the ICD-10 code. Including the specific diagnosis code in your prompt helps Claude use the right clinical terminology and specificity level in documentation.

4. Set the audience for patient materials. Add "plain language, 8th-grade reading level, no clinical jargon" every time you generate patient-facing content. Your patients will be more compliant when they understand their condition.

5. Ask Claude to flag documentation gaps. Paste a completed exam note and ask: "Review this note for documentation completeness, medical necessity support, and any gaps an auditor might flag." This catch-and-fix workflow prevents downstream problems.

6. Use Claude for coding verification. Describe a clinical scenario and ask Claude to suggest the most specific ICD-10 code with laterality. Then verify it against your coding reference. This is a fast way to catch under-coding.

Privacy & Compliance

HIPAA compliance is mandatory. Never enter real patient names, dates of birth, medical record numbers, or any identifying information into Claude. This is a hard rule, no exceptions.

De-identify all clinical scenarios. When using Claude for documentation support, change or omit identifying details. Use "62-year-old female, annual exam" instead of any real patient information. Adjust ages by a few years, omit exact dates, and never include facility-specific chart numbers.

Claude drafts, you finalize. Every note, letter, and handout that Claude produces is a draft. Your clinical review, verification, and signature are what make it a valid medical document. You are the clinician of record, not Claude.

Verify clinical accuracy. Claude does not have access to the slit lamp, OCT, or the patient sitting in your chair. Always verify that generated documentation accurately reflects your actual clinical findings. Do not accept AI-generated clinical impressions without independent confirmation.

Medical necessity documentation standards. Insurance narratives and referral letters must meet payer-specific documentation requirements. Claude can structure the argument, but the clinical facts and their accuracy are your responsibility.

Check your employer's AI policy. Many practice groups and health systems have specific policies about using AI tools with clinical information. Review these before integrating Claude into your workflow, even with de-identified data.

Going Further

Ready to take your optometry practice further with AI? Explore these resources:

Browse our full library of optometry AI resources and prompt packs for additional templates
Run the AI readiness audit for optometrists to see where AI fits in your practice
Check out AI tools designed for eye care professionals to streamline documentation and patient engagement