Free cookie consent management tool by TermsFeed
Inefficiency Dissection

Academic Progress Monitoring

Summary: 

Preparing for Clinical Competency Committee (CCC) meetings is a manual data-gathering exercise that prevents the early and objective identification of struggling residents.

The Problem

Exposure gaps are discovered only at the end of the rotation, when it’s too late to fix them.

The Clinical Competency Committee (CCC) is the cornerstone of modern GME, yet its effectiveness is often crippled by the very data it needs to function. Before each meeting, program coordinators are sent on a digital scavenger hunt, manually pulling evaluation scores, case logs, procedure reports, and ITE scores from a half-dozen disconnected systems. This mountain of data is then compiled into massive PDF packets or binders. Committee members review raw, static data during the meeting, leaving limited time to assess patterns, progress, or emerging concerns across residents.

One experienced Program Director described the consequence:

“We spend the first 30 minutes of every CCC meeting just trying to find and assemble the data on a resident. The actual discussion about their trajectory is rushed. We’re making high-stakes decisions based on an incomplete, hastily assembled picture.”

A GME coordinator explained the operational burden:

“My job for two weeks before the CCC is ‘binder builder.’ I’m printing, downloading, and collating. I’m an evidence gatherer, not a program manager. By the end, I can’t even be sure we haven’t missed something critical.”

Under these conditions, the CCC operates as a retrospective review forum driven by fragmented inputs and subjective interpretation, limiting its ability to support timely, evidence-based academic progress monitoring.

How This Inefficiency Shows Up

Programs encounter the same operational patterns across CCC cycles: