Case Study

Building an EMR System for Pediatric Ophthalmology, One Physician Workflow at a Time

A 9-month UX lead engagement translating physician requirements into a doctor-friendly Electronic Medical Record system, years before the PhD and defense contracting.

User Experience Lead, Excel Eye Center August 2011 to April 2012 Independent pediatric ophthalmology practice HealthcareUX Research
9
Months from research to full clinical rollout
1
Physician-designed EMR shipped and adopted

Situation

A pediatric ophthalmology practice was still running patient records the old way: paper charts, disconnected notes, appointments packed with kids who don't sit still. They needed a real Electronic Medical Record system built around how a pediatric ophthalmologist actually works an exam room. A generic EMR template retrofitted onto their specialty wasn't going to cut it.

What I Built

  • Led user research directly with physicians and clinical staff, translating exam-room workflows and documentation habits into requirements an off-the-shelf EMR vendor would never have captured.
  • Designed and prototyped a doctor-friendly Electronic Medical Record system, built around the specific pace and structure of a pediatric ophthalmology exam rather than a general practice.
  • Collaborated with medical staff and IT teams on compliance and usability together, so the system met recordkeeping requirements without slowing physicians down during patient visits.
  • Deployed the system into full clinical use, research to a rollout the practice actually adopted. No prototype stalling after the pitch.
Exam-room observation Physician requirements EMR prototype and compliance review Full clinical rollout 9 MONTHS, RESEARCH TO ADOPTED CLINICAL SYSTEM
The interface had to disappear into an existing exam-room workflow, not the other way around.

The Hardest Problem

Physicians don't tolerate friction during patient visits, especially in pediatrics, where the appointment window is short and the patient is rarely cooperative. The interface had to disappear into the physician's existing workflow. Asking them to adapt to the software's model of a medical record was never going to work. Getting that right meant designing from direct observation of exam-room behavior. A requirements document written by someone who'd never sat in the room wouldn't have gotten it right.

Outcome

The practice moved off paper and fragmented notes onto a system physicians actually used, built around their real workflow, not a generic template. It was an early, small-scale proof of an approach I kept using later: watch how the work actually happens before designing the system meant to support it.

Skills Demonstrated

Healthcare UX research, physician-centered interface design, compliance-aware system design, clinical workflow analysis, prototype-to-deployment delivery.

Evaluating me for a role

See the rest of the track record

More case studies spanning 16+ years of AI and technical leadership.

View full work →
Need this built or governed

Let's talk about your problem

AI strategy, LLM agent architecture, and governance frameworks that hold up under scrutiny.

Get in touch →