Faculty AI Fluency Is Falling Behind Trainees, and CME Is Not Ready

Key Takeaways

• The strongest public signal this week was not demand for more AI content; it was concern about uneven AI fluency between trainees and faculty.
• CME providers should treat AI education as a role-based curriculum problem, not a webinar topic.
• Ethics, safety checks, escalation habits, and protected learning time are becoming core design requirements for clinician AI education.

Clinician discussion this week put a sharper point on a practical AI education problem: trainees may be moving faster than the faculty expected to supervise them. The signal is strongest in oncology and medical education settings, but the provider implication is broader: AI learning pathways need to be tiered by role, responsibility, and workflow exposure.

The gap is no longer just about awareness

One radiation oncologist reflecting on AIMed25 framed the asymmetry plainly: “Many students & residents now are more fluent in AI tools than their faculties” (source). That is a different problem from low AI awareness. It means some learners may be experimenting in real clinical or pre-clinical workflows while their supervisors are still trying to understand the tools, risks, and boundaries.

A second thread made the faculty-side problem concrete: “We do not know what these tools actually do, how they make decisions, or how we can check their safety and limits” (source). The requested fix was not another overview of generative AI. It was structured training, protected time, and closer work between clinicians, data scientists, and educators.

For CME providers, the lesson is to stop treating AI education as a single audience. Trainees need foundations, interpretation, responsibility, and leadership competencies. Faculty need enough fluency to coach, challenge, supervise, and escalate safely. A conference reflection from the same week also emphasized trust, regulatory compliance, model reliability, and clinician-data scientist learning as part of the AI conversation (source).

That connects directly to a pattern we saw in an earlier brief on simulation faculty needing shared AI governance rules, not more tool demos. The next step is curriculum architecture: separate tracks for faculty upskilling and trainee development, joined by shared language around ethics, hallucination risk, safety checks, and when to seek help. The operating question for CME teams is simple: are you teaching a tool, or are you teaching a supervised clinical behavior?

What CME Providers Should Do Now

• Build separate AI learning paths for faculty and trainees rather than sending both groups through the same introductory content.
• Include explicit modules on safety checks, limits of model outputs, ethics, and escalation—not only prompt technique or tool comparison.
• Use 30- and 90-day follow-up to test whether learners are changing verification habits, supervision conversations, or workflow decisions.

If this continues

The risk is not that every clinician will adopt AI at the same pace. They will not. The risk is that CME programs keep offering flat, one-size-fits-all AI education while clinical teams develop uneven fluency inside the same learning environment. If this pattern holds, the providers with an advantage will be the ones that can map AI education to role, stage, and responsibility. Faculty development and trainee education should not be separate silos, but they should not be identical courses either.