CME Needs Better Inputs Before Better Formats
Earlier coverage of learning design and its implications for CME providers.
ACCME modeling of universal design and root-cause needs assessment both show how early infrastructure choices reduce later friction for learners and teams.
ACCME modeled full accessibility through live captions, accurate medical transcripts, alt text, WCAG keyboard operability, and advance accommodation workflows at its own events. Treating these as default design choices rather than retrofit fixes reduces last-minute costs and builds learner trust; a parallel signal from CME writers shows how root-cause analysis can sharpen needs assessments beyond surface gaps.
ACCME used its own platform this week to model accessibility as universal design rather than a legal minimum. The discussion covered live captions, accurate transcripts for medical language, alt text, advance accommodation notices, WCAG-style keyboard operability, and cross-functional help from ed-tech teams and librarians in a Coffee with Graham episode on accessibility in healthcare and continuing education.
The important provider signal is not that every activity needs a bespoke accommodation plan. It is that many accessibility decisions can be standardized before registration opens: captioning expectations, transcript review, slide and PDF checks, accessibility statements, faculty guidance, and a clear path for learners to request support.
The caveat matters: this is ACCME and educator modeling, not a broad independent clinician demand signal captured this week. Still, it is portable across specialties. CME teams should ask whether accessibility is owned only by event operations at the end of production, or whether it is a requirement in the activity brief, platform QA, faculty instructions, and budget from the beginning.
The second signal came from the planning side of CME. A Write Medicine episode argued that root-cause analysis can strengthen needs assessments by asking what is underneath a visible performance gap: scheduling delays, communication failures, patchy follow-up, siloed curricula, weak team processes, or other conditions that a literature scan alone may not expose. The episode names fishbone diagrams, 5 Whys, and Pareto analysis as tools for moving from surface description to targeted intervention design in root-cause analysis for needs assessments.
This is also provider-owned educational content, not independent clinician corroboration. But the point fits a longer CME design problem we have covered before: better formats do not compensate for weak inputs, as noted in an earlier brief on why CME needs better inputs before better formats.
For CME teams, the implication is concrete. If the stated gap is “diagnostic delay,” the next step should not automatically be another disease-state update. The planning question is: why is the delay happening, and which cause is education actually positioned to change?
The week’s useful lesson is not that CME needs another layer of process. It is that some late-stage fixes are only late-stage because teams have not made them default work. Accessibility and root-cause analysis both ask the same operational question: what should be built into the design system so learners, faculty, and outcomes teams are not forced to compensate later?
ACCME podcast details practical tactics (live captions, accurate medical-jargon transcripts, alt text, advance notices, WCAG keyboard operability) plus partnerships with ed-tech and librarians; stresses distinction between legal minimum and full accessibility.
Open sourceWrite Medicine podcast outlines how root-cause tools (fishbone, 5 Whys, Pareto) reveal scheduling delays, silos, or curricular gaps that traditional gap analysis misses, enabling precisely targeted interventions.
Open sourceEarlier coverage of learning design and its implications for CME providers.
Earlier coverage of learning design and its implications for CME providers.
Earlier coverage of outcomes planning and its implications for CME providers.
ChatCME surfaces the questions clinicians actually ask — so you can build activities that close real knowledge gaps.
Request a demo