"I've been on call."
I hear this from International Medical Graduates (IMGs) every single match cycle. It's supposed to be the ultimate trump card. The assumption is simple: if you survived overnight call, you must have been doing hands-on procedures, specifically bedside ultrasound.
Here is the myth, precisely defined: Call equals clinical volume, which equals ultrasound exposure, which equals procedural competency.
It's a dangerous leap in logic.
The reality? Call experiences vary wildly by site, staffing models, supervision levels, and institutional documentation. "Call" is not a standardized metric. A night shift at a Level 1 trauma center where you are the primary sonographer looks nothing like a night shift at a community hospital where the radiology tech does the scanning and you just sign the chart.
When you tell a Program Director (PD) you were on call, you are giving them a proxy for presence, not a proxy for competence. In this article, we are going to tear down this assumption. I'll show you what PDs actually count, why clinical experience signals must be explicit rather than implied, and how to stop relying on vague time-based claims to prove you can do the job.
Let's clarify what call typically covers. You are triaging new admissions, answering floor calls, managing overnight clinical changes, and fielding consults. You are putting out fires. That does not automatically translate to bedside imaging opportunities.
Clinical exposure is incredibly heterogeneous. Without measurable endpoints, like the actual number of exams you performed, you cannot assume competency. I've reviewed hundreds of applications where an applicant claims extensive call experience, only to admit during the interview that they never once held the probe.
Here are the most common failure modes I see when applicants conflate call with ultrasound training:
- Shadowing without performing: You followed the senior resident or attending, watched them scan, and nodded. You didn't acquire the images.
- Workflow bottlenecks: The patient was too unstable, or the ER was too crowded, limiting your window to actually set up the machine and scan.
- Credentialing restrictions: Some hospitals strictly limit who can perform and bill for point-of-care ultrasound (POCUS), relegating residents to an observer role.
Supervision also complicates the narrative. "On call with supervision" sounds great on paper. But in practice, it might just mean you squeezed the gel bottle while the attending manipulated the transducer. If your supervision meant you were physically in the room but not physically driving the probe, your hands-on skill acquisition is near zero. Time on call guarantees you were in the building. It doesn't guarantee you were doing the work.
Program Directors are not in the business of rewarding hours. They are risk-managing.
When a PD looks at your application, their mental model is focused on one question: Can this person do the job on day 1, or at least by day 30, without killing someone or slowing down the team? Vague claims about being on call don't answer that question. Structured signals do.
For ultrasound and procedural skills, PDs look for specific proof points. They want to know the exact number of studies you performed. They want to see the complexity mix. Did you do 50 FAST exams, or did you do 20 FASTs, 15 cardiac echoes, and 15 vascular duplex scans? Most importantly, they need to know if you actually acquired the images yourself, or if you just interpreted clips someone else handed you.
Then comes the documentation layer. PDs trust logs, supervising faculty attestations, and chartable outcomes. A letter that says, "Dr. X performed and interpreted 150 POCUS scans under my direct supervision," is worth its weight in gold. A letter that says, "Dr. X was a dedicated member of the night call team," is practically useless for proving procedural competence.
This brings us to the credibility layer. Specificity correlates directly with trust. When you give me exact numbers, study types, and supervision levels, I believe you. When you give me generic, time-based statements like "I was on call for ultrasounds," it signals ambiguity. And in the Match, ambiguity is a death sentence. PDs will simply move on to the applicant who gave them hard data.
Let's confront a massive misconception head-on: there is no universal "call hours to ultrasound skills" conversion factor. You cannot divide your call hours by some magic number to arrive at your procedural competency.
Look at the data visualization above. Panel A (the blue bars) shows on-call presence. It's all over the place. You might work 60 hours one week and 120 the next. But look at Panel B (the orange bars), the actual hands-on studies performed. The variation is much narrower, and more importantly, it doesn't map cleanly to the hours worked. In Scenario B, the resident worked 110 hours but only performed 8 scans. In Scenario C, they worked 60 hours and performed 15.
Presence is a terrible predictor of performance.
Yes, applicant-driven data has limitations. Case mix varies. Supervision varies. But an action-based approach is infinitely more predictive than time-on-call. When you translate this into your application strategy, the directive is clear: stop tracking your hours. Start tracking your actions. Document what you personally performed, categorize it by study type, and note your level of supervision. That is the data PDs actually care about.
So, how do you fix this on your ERAS application? You change your vocabulary.
First, adopt the action language PDs actually understand. Delete "on call for ultrasounds" from your personal statement and work experiences. Replace it with: "Performed and interpreted 120 POCUS studies (40 cardiac, 50 FAST, 30 vascular) with attending supervision." That single sentence does more work than a whole paragraph about your grueling night shifts.
Next, fix your letter strategy. When you ask an attending for a Letter of Recommendation, explicitly ask them to detail your role and independence. Give them the exact phrasing you need. Tell them to distinguish between "acquired images independently," "performed with hands-on guidance," or "observed at bedside." If the letter just says you "helped at bedside," it's a wasted opportunity.
For your resume and ERAS work experiences, include a dedicated "Ultrasound/Point-of-Care (POCUS) Log" section. Break it down by date ranges and study types. Make it incredibly easy for the PD to see your volume at a glance.
Finally, what if you lack volume? Don't bluff. I can spot a bluff from a mile away, and so can the PDs interviewing you. If your call experience didn't yield high ultrasound numbers, own it. Instead, show targeted learning. Highlight your simulation hours, your supervised practice on models, and your competency checkoffs. Transparency builds trust; bluffing destroys it.
Key Takeaways
- "On call" is presence, not proof. PDs rely on action-based evidence, what you performed, how many you did, and your level of supervision, rather than implied exposure from simply being in the hospital.
- Replace vague duty statements with measurable data. Use role-specific ultrasound and POCUS counts. Ensure your letters of recommendation explicitly distinguish between acquiring images yourself, observing, or just interpreting provided clips.
