The Short Version
Having both CMAs and nurses able to perform EKGs, phlebotomy, and injections is good for coverage. It's also exactly the setup that produces the classic diffusion of responsibility problem: when two people can both do a task, it's statistically more likely to sit undone than when only one person can do it, because each person has a reasonable excuse to assume the other has it covered.
The fix isn't picking one role to own everything, that defeats the coverage benefit. It's making individual tasks visible enough that "someone else probably has it" stops being a safe assumption.
Why Overlap Creates Delay, Not Speed
On paper, having two roles capable of the same task should mean things move faster, whoever's free grabs it. In practice, it often means the opposite. If a phlebotomy order comes in and both the CMA and the nurse are mid-task with other patients, neither one necessarily knows the order exists until they happen to check, and each assumes if it were urgent, the other would have flagged it.
This isn't a competence issue. Both roles are fully capable of doing the work. It's a coordination issue: overlap without visibility means responsibility for any given task is genuinely unclear in the moment, not just theoretically shared.
What Makes This Specific to CMA and Nurse Overlap
Unlike, say, front desk versus clinical tasks, which have a natural boundary, procedure tasks like EKGs, phlebotomy, injections, and vaccine administration sit squarely inside both role's normal scope. There's no obvious tiebreaker for who should do a given one, and forcing an artificial split, "CMAs always do phlebotomy, nurses always do injections", throws away the flexibility that having both roles capable was supposed to provide in the first place.
The overlap is a feature when it comes to covering absences or busy stretches. It's a liability when it comes to individual tasks quietly waiting on an assumption that isn't true.
What a Working Assignment System Looks Like
Every procedure task is visible to both roles at once, not routed to a specific person by default. The point isn't to eliminate the overlap, it's to make sure both people looking at the day's work see the same list.
Claiming a task is explicit, not implied. Whoever picks up the EKG order marks it as theirs, so the next person glancing at the list sees it's in progress and moves on, instead of either duplicating the work or, just as commonly, also assuming it's covered and neither of them doing it.
Nothing sits unclaimed past a reasonable window. If a task has been sitting fifteen or twenty minutes with no claim, that's worth surfacing, not silently waiting on whoever happens to glance at it next.
Coverage gaps get handled by the same system, not a separate conversation. If the CMA is out for the day, the nurse doesn't need a new process, just a clear view that everything on the list is now theirs by default until someone else is available.
The list reflects urgency, not just a flat queue. A same-day EKG for a symptomatic patient needs to stand out from a routine annual labs draw, so whoever's picking up the next task naturally grabs the more urgent one first.
Where This Actually Falls Apart
The failure here rarely looks like refusal or carelessness. It looks like two competent people, both busy, both reasonably assuming the other has something covered, and a twenty-minute delay turning into an hour because neither one had visibility into what the other was actually working on.
This is the same underlying pattern as other clinic breakdowns: real capability, real willingness to do the work, undermined by a lack of shared visibility into what's actually been claimed and what's still sitting open.
This is where Tabflows fits into procedure task assignment. Every EKG, phlebotomy order, or injection shows up as a task both the CMA and nurse can see, claimed explicitly the moment someone picks it up, so the rest of the team knows at a glance what's covered and what's still open. The flexibility of overlapping roles stays intact. What goes away is the ambiguity that made overlap risky in the first place.
A Simple Rule to Start With
If a procedure task has been unclaimed for more than a few minutes during a normal shift, it should be visible enough that it gets picked up without anyone having to specifically go looking for it. That single standard closes most of the gap that overlap alone tends to create.
FAQs
Who should perform EKGs, phlebotomy, and injections in a small clinic?
Both CMAs and nurses can typically perform these procedures, which is efficient for coverage but creates ambiguity about who's actually doing a specific task in the moment. A shared task list with clear claiming, rather than an assumed default, resolves this without requiring a rigid role split.
Why do tasks get delayed when two roles can both do them?
Because each person can reasonably assume the other one has it. Without an explicit claim or assignment, a task sitting between two overlapping roles is more likely to be delayed than one assigned to a single role, since neither person feels solely responsible.
Should a clinic assign fixed roles for procedures like phlebotomy and injections?
Rigid role splits usually create coverage gaps when someone is out or the schedule gets busy. A better approach is keeping the overlap for flexibility, but making every individual task visible and claimable, so coverage stays flexible without any specific task falling into a gap.
How do you prevent duplicate work when two people can do the same task?
Whoever picks up a task claims it visibly, so a second person checking the same list sees it's already in progress and moves to the next thing instead of duplicating the work or, just as often, both assuming the other has it and neither doing it.