Diabetes educators were switching between paper forms, PowerPoint, and the EHR during every class. I redesigned the workflow into one system that helped them teach, track patient progress, and complete documentation without leaving the session.
A single session ran across three disconnected tools. Patient data entered on paper had to be manually re-entered into the EHR. Nothing transferred automatically.
I interviewed diabetes educators and program managers to understand how group classes actually run. Four constraints came up in every conversation.
One educator teaches. A second handles documentation. Even with two staff, there still isn't enough time to do both well.
Patients don't always complete pre-class questionnaires. Many arrive unprepared, so educators spend 10-15 minutes per session helping them catch up, cutting into teaching time.
Current documentation methods are too slow for a live class. Educators need quick-select inputs, not text fields. Printed materials are still the norm, and they go missing or stale.
Attendance is tracked manually, which is slow and error-prone. There's nothing tracking patient progress, engagement, or outcomes across sessions.
"The hard part was never adding features. It was building a form someone could actually fill out while teaching ten people at once."
Four screens that keep everything in one place: the class dashboard, in-session charting with medical history, auto-filled forms, and the pre-class checklist.
The dashboard brings upcoming classes, patient progress, and lesson materials into one system. Educators stay in it for the full session.

Educators chart each patient with the full medical history and medication list visible the whole time, right beside the form.

Past session responses pre-fill the form and sit next to each question. Educators confirm what changed instead of re-entering everything.

Before class starts, educators confirm session details, work through the checklist, and see which patients completed their pre-class forms.

Medicare reimburses clinics per patient per group session under code G0109. The faster a clinic runs a session, the more cohorts it can schedule. This tool directly supports that math.
10 extra minutes of teaching per session. Across 3 cohorts/week, that's 30 minutes of patient care time returned every week.
Freeing a second educator means clinics can run parallel cohorts instead of dedicating two staff to one class.
Projected impact based on interview findings. Not yet validated in live sessions.
Running three cohorts at full capacity is ~$1,824 a week, and none of it requires a second hire. Projected from interview findings, not yet validated in a live clinic.
I looked at the software a diabetes educator actually touches, from the ADA's own documentation platform to the enterprise EHRs. Each solves a slice. The gap is a guided workflow built for teaching a class that also submits to the EHR and drafts the documentation.
| Tool | What it is | Guided DSME flow | EHR submission | AI documentation |
|---|---|---|---|---|
| Chronicle Diabetes (ADA) | DSMES documentation | ✓ | ✗ | ✗ |
| Epic | Enterprise EHR | Configurable | ✓ | ✓ |
| Oracle Health (Cerner) | Enterprise EHR | Configurable | ✓ | ✓ |
| Glooko | Diabetes data platform | ✗ | ✓ | Analytics only |
| Cecelia Health | Virtual diabetes clinic | ✓ | ✓ | ✗ |
| Welldoc (BlueStar) | Digital therapeutic | ✗ | ✓ | Patient-side |
| My design | Group lesson charting + education | ✓ | ✓ | ✓ |
I mapped the full session from pre-class to submission. Seeing every step in one place made it easier to spot where time was leaking and where the design could actually help.
Seven iterations before I landed on the final design. Each one closed the gap between what I assumed and what the research showed.
Early sketches
Wireframe iterations
My first pass was a digital copy of what educators described to me. I designed what I heard, not what would actually work better.
A lot of EHR systems use vertical list navigation, so I tried that next. But the form still leaned on typing, the exact problem research had flagged.
Replaced most text inputs with toggles and selectors. Added previous session answers inline so educators see changes right away. The snapshot panel keeps patient context in view without leaving the charting screen.
These are the edge cases I designed for, pulled from interviews and conversations with our engineers.
The Add/Drop button lets educators update the roster mid-session without navigating away. A no-show is marked directly on the patient card, keeping the cohort count accurate for billing.
The pre-session checklist shows form completion at the cohort level before class starts. Educators see who submitted and who didn't before opening a single chart.
Each EHR submission costs money, so the system is designed around getting it right the first time. The billing readiness screen flags every incomplete field before the educator hits submit.
This was the core constraint the whole system was built around. Every interaction needed to work for one person teaching and charting at once, with no second staff member to offload to.
Static mockups only show part of the story. I built an interactive prototype so reviewers could experience the full group lesson workflow instead of imagining it from screenshots.
Built from my Figma designs using Claude Code and React.
I explored where AI could reduce cognitive load without adding extra steps. Each idea came from a real moment in the educator workflow.
One panel: who to watch today, last session's unmet goals, and who hasn't submitted their pre-class form.
As the educator charts, it flags whether last session's goals were met and suggests activity, nutrition, and monitoring next steps.
The close screen shows a live G0109 readiness score and one-click fixes for any missing field.
This one pushed me to design for constraints I hadn't hit before. A few things I'd take with me.
I tried to solve for every clinic's workflow at once. The research kept pointing me back to the same core constraints, and a simpler system was the right call.
Start simpler. Test with real educators sooner. The final design ended up leaner than the fourth iteration.
EHR integration has to flex to different clinic setups, and that's the hardest part to get right. Next is testing in live sessions to see where the workflow holds and where it breaks.