CME Still Designs for Teaching Instead of Retention

Key Takeaways

• ACCME leadership put a sharper spotlight on the gap between instruction that feels successful in the room and learning that clinicians can recall later.
• Retrieval practice, spacing, prior-knowledge activation, and reflection need to be built into planning templates, not added as optional engagement features.
• Simulation-based education offers a model for turning learner-identified workflow frictions into documented system improvements through reporting and follow-up.

ACCME leadership is reframing CME design around what learners retain and transfer rather than what instructors deliver in a single session. The evidence base is narrow and education-led, but the implication is concrete: CME teams must treat retrieval practice, spacing, and follow-through as required design elements.

Design for what clinicians can recall later

On an ACCME-hosted episode of Coffee with Graham, Graham McMahon and Nidhi Sachdeva distinguished immediate performance from real learning and named spaced recall, prior-knowledge connections, deliberate practice, varied scenarios, and reflection as the mechanics that move knowledge toward use (source).

That matters because many CME workflows still center the live session or enduring module. This extends an earlier brief on one-week recall: the question is no longer whether recall fades, but where in the activity plan the provider deliberately prompts retrieval, reapplication, and reflection after a delay.

For CME teams, the planning handoff must change. A needs assessment should specify what prior knowledge the activity will activate, when recall will be prompted, how the concept will be tested in a different context, and what reflection will ask the learner to notice.

Simulation can become a reporting system

A second education-led signal came from the STORK simulation team’s discussion on Simulcast. Their in-situ courses documented equipment, drug-pump, and workflow frictions, then used structured reports and follow-up advocacy to achieve resolution (source).

One line captures the shift: “And this paper describes how 45% of the issues that were identified through these courses were actually resolved at the follow-up.” The caveat is important: this is a simulation-community podcast and a paediatric resuscitation example, not broad clinician consensus. Still, it shows a concrete outcome pathway.

The lesson is not that every activity must become a QI program. It is that some formats generate operational data providers often let disappear. If a debrief surfaces a missing tool or repeated workaround, the design should decide in advance whether that information will be captured and who owns follow-up.

What CME Providers Should Do Now

• Audit one upcoming activity for three required elements: delayed recall, changed-context application, and learner reflection on the process.
• Add a planning-template prompt that asks faculty to name the prior knowledge learners need to connect with the new material.
• For simulation or team-based activities, decide before launch whether debriefed system frictions will become a structured report and who owns follow-up.

What CME teams should reconsider

The quiet-week signal is simple: CME cannot keep treating the activity boundary as the learning boundary. If the goal is retention, the design has to include time. If the goal is transfer, the design has to include changed context. If the goal is system improvement, the design has to include a reporting and follow-up loop.