A unified charting system that helps diabetes educators document visits, track goals, and submit to the EHR in one guided workflow, from prep to submission.
Before this system, one charting session took three separate tools that didn't talk to each other. Educators switched between them mid-appointment, took notes on paper, and finished documentation hours after the patient left.
In interviews with a diabetes educator and clinic collaborator, I mapped the charting workflow to find where educators lost the most time. Four barriers emerged, each a gap between what the tools provided and what educators needed at the point of care.
The cost: hours of educator time, records scattered across three systems, and clinic revenue quietly lost every day.
Sessions ran long, documentation piled up, and charting wrapped up at 7pm. That cut the capacity to see new patients and generate billable hours.
Labs in the EHR, prep notes in a binder, billing in a separate portal. Educators had no single place to see the full patient picture, so they juggled all three during appointments.
Without a guided flow, educators couldn't see where they were in the chart. That meant missed fields, incomplete records, and re-work, often discovered only at billing time.
Previous goals, educator notes, and patient history weren't surfaced at charting time, so every visit started from scratch. That undercut long-term diabetes education and made session-over-session tracking impossible.
"Charting in a diabetes clinic is repetitive and disconnected, and it eats the time educators should spend with patients. The design work came down to one question: which moment in the workflow actually needed help?"
Walk through the key screens: educator dashboard, guided session charting, AI summary generation, and EHR submission.
The calendar gives educators a real-time view of their schedule with A1C flags and patient risk levels. Clicking any patient row opens a slide-in drawer with demographics, labs, medications, goal history, flags, and prep notes.

The charting flow walks educators through every required field: numbered sections, completion checkmarks, and the ability to jump to any section without losing their place. The right panel toggles between Prep Notes and Medical History, so context is never more than a click away.

Medications can be reordered by priority with drag-and-drop. The Medical History panel closes automatically and the list moves to a fixed bottom strip, so source and target stay visible at the same time. No scrolling needed.

Goal setting surfaces the patient's previous goals alongside a field to add new ones. Progress bars track completion across all active patients and carry through to the next session automatically.

The summary collects the full chart into one reviewable view before EHR submission. Educators can edit any field inline, see flagged incomplete sections, and submit with one click.

Medicare reimburses clinics per completed patient session under code G0108 for individual DSME visits. The only way to get reimbursed is to submit a complete, signed chart. Incomplete documentation costs the clinic real revenue, not just the educator's evening.
25 minutes returned per patient session. Across a week of appointments, that's over 2 hours of patient care time given back.
With after-hours documentation gone, educators can see more patients per day and clinics can add billable sessions without hiring more staff.
A four-educator clinic clears ~$106,000 a year in new billable capacity, without hiring. On top of that, every chart that now closes the same day is a session that gets reimbursed instead of forfeited to an incomplete record. 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 DSME flow 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 | Diabetes charting + education | ✓ | ✓ | ✓ |
I visualized the entire workflow, before, during, and after each session, to pinpoint where friction built up and where design would have the most impact.
Quick layout explorations to test concepts and settle on a clear structure before the full prototype build.
Six iterations before the final design. Each version got me closer to what educators needed versus what I assumed they needed. The biggest pivots came from workflow constraints, not aesthetics.

The components were too big and the visual design felt outdated. If this is what educators see, there's no reason to switch from their existing tools. The design has to earn that switch.

We wanted to give educators a visual history of the patient over time. The idea made sense but the execution didn't. The layout was hard to read and the information wasn't presented in a useful way.

After scrapping the original timeline, we kept iterating on how to display patient history. The final version is filterable by date range, organized by category, and lives inside the medical history panel so educators can reference it without leaving the chart.
These scenarios don't show up in a happy-path wireframe, but they come up every week in a real clinic. Tools fail at the edges, not in the center.
When records can't be retrieved before a session, the system surfaces missing fields in the charting nav. Educators can flag incomplete data, continue without being blocked, and return to fill gaps later.
Partial saves appear as overdue tasks in the Dashboard. Each task card shows exactly which sections are missing, how many days late it is, and a "Resume →" button to jump back into the exact section needed.
Procedure and diagnosis codes are entered inline before the e-signature. The Submit button only activates when the chart is signed, preventing unsigned charts from being sent to the EHR accidentally.
The medication history strip shows last refill dates and a "Refill soon" badge for flagged medications. Educators see Acarbose is due for refill before the session ends, not after the patient has already left.
Rather than leaving this project as a Figma file, I partnered with Claude to build a fully interactive prototype in real code.
One question the wireframes couldn't answer kept coming back: what does it actually feel like to chart a patient in this tool? A static mockup couldn't show me how the AI pre-brief loads or how dragging a medication into the drop zone behaves in context.
So I built the prototype in code, using the same design system and the same patient data. It's fully clickable, not a Figma file wired up with hotspots.
Three AI integrations that reduce cognitive load at key moments, each tied directly to a pain point from the research.
Today's schedule with A1C flags, goal progress, and overdue-chart alerts. Click any patient for their full history.
In the Care Plan, AI reads the chart and suggests the two best-fit DSME goals with a one-line rationale. Click to apply.
The Summary drafts an EHR-ready narrative in five labeled sections. One click, review, accept.
Working closely with a clinic collaborator gave the project something most design projects don't have: a real workflow to improve, with real friction I could witness firsthand.
Building the prototype in code also revealed design decisions that Figma wireframes couldn't expose, particularly around the panel toggle behavior and the charting nav auto-advance.
If I could start over, I'd define the exact fields required for charting before designing a single screen. Getting deep into the information architecture revealed conflicts between what was required for billing and what was most useful for educators.
I'd also plan for usability testing earlier, specifically around the dashboard task management flow, which changed significantly after seeing how educators actually prioritize their day.
Integrating cleanly with existing EHR systems while staying flexible for different clinic workflows is the main technical challenge at scale. The current design assumes a relatively standardized EHR interface.
The next iteration would include deeper testing with real educators in live clinic environments, and a closer look at how the billing flow connects to existing revenue cycle management tools.