When a new hire joins a clinic and sits down with an EHR for the first time, the person training them is almost always a senior MA or nurse who learned the system through years of trial and error, not through any structured curriculum. The complaints users describe — 'it takes some time to learn how to navigate,' 'finding functions is not user-friendly, making it time-consuming to learn' — translate directly into training sessions that are long, inconsistent, and dependent on whoever happens to be available that day. When that senior staff member leaves, the institutional knowledge of how to navigate the system walks out with them.
EHR vendors do offer training, but it covers the full system for all roles — a general orientation that maps to no one's actual daily workflow. It's designed to satisfy implementation contracts, not to get an MA productive in their first week. The gap is role-specific, workflow-specific, practice-specific training that teaches exactly what a rooming MA at a family medicine practice actually clicks through in a given day — not a tour of every module in the system.
The reason this gap is structural is that building role-specific training requires understanding clinical workflows at a granular level, which EHR vendors don't have because their employees aren't clinicians doing the work. A training company that embeds in practices, records actual navigation sequences, and builds short-form video walkthroughs tied to specific EHR versions and roles is doing something the vendor genuinely cannot — not because of capability, but because of organizational distance from the actual work.
This is a business and not a one-time project because EHRs push updates that move menus, rename functions, and add steps — which breaks every training video on a rolling basis. Practices also have ongoing staff turnover in clinical support roles, which means onboarding training is never a one-time purchase. Staffing agencies that place clinical staff across many practices have an even stronger incentive: they need their placed staff to get productive faster, regardless of which EHR the clinic runs.
What to build
Build a subscription library of short-form, role-specific EHR navigation walkthroughs — organized by EHR product, version, and job function (rooming MA, front desk, billing) — with a practice admin dashboard that tracks which staff have completed which modules and flags when a module needs updating after an EHR version change.
Where to start
Sign a single mid-size clinical staffing agency as the first customer — they place staff into practices running several different EHRs and are paying for onboarding time right now with no structured curriculum; one agency gives you enough volume to fund building the first three EHR-specific libraries.
The hard part
EHR vendors update their interfaces on unpredictable schedules, and keeping the video library current across multiple EHR products requires a systematic process for detecting UI changes — without it, the library goes stale and the product's credibility collapses.
How it makes money
Annual subscription per agency or per practice group, tiered by number of staff seats with a per-module update fee when EHR version changes require a library refresh.
See the evidence. The complaints behind this idea, the products they came from, and similar ideas in EHR.
More ideas in EHR