8.3 Fatigue, Workload, and Communication Scenarios

8.3 Fatigue, Workload, and Communication Scenarios

Scenario questions in this domain hand you a stressed human and a clinical deadline. Read for six things: role, task, governing rule, the cue (the pressure), the safest action, and the output. The pressure is bait; the rule is the answer.

Fatigue and workload

Fatigue produces slips (doing the right step wrong) and lapses (forgetting a step). Lone night-shift work, mandatory overtime, and back-to-back shifts are the classic exam setups. Controls the exam rewards:

• Task rotation between physically and cognitively different tasks.
• Scheduled breaks and adequate rest between shifts (not energy drinks or "powering through").
• A non-punitive culture where a fatigued tech can say "I need a check" or "I am behind" without penalty.
• Escalation, not shortcuts, when volume exceeds safe capacity.

The wrong answers always offer a way to make the work faster (fewer brush passes, skipping the rinse, shortening manual cleaning). Manual cleaning removes the bioburden that shields microbes from HLD, so cutting it is the single most dangerous shortcut.

Communication and handoffs

Reprocessing is a relay, and the baton is the scope's status. A structured handoff (an SBAR-style note — Situation, Background, Assessment, Recommendation) should convey:

A scope whose reprocessing status is unknown, interrupted, or undocumented is treated as dirty and reprocessed again. "Probably done" is never an acceptable handoff.

Delayed reprocessing and the time clock

Workload pressure also shows up as delay. If a scope cannot be reprocessed promptly after use, dried bioburden becomes far harder to remove and biofilm can begin to form. The IFU defines a maximum delay before special pre-cleaning or extended soaking is required; when that window is exceeded, the scope needs the manufacturer's delayed-reprocessing protocol, not the normal one. A stem describing a scope left soiled overnight is testing whether you recognize that the standard process is no longer adequate. The human-factors answer is to follow the delayed protocol and document the delay, never to run the routine cycle and hope.

Worked scenario

Night shift, one tech, three colonoscopes behind, a 0600 case posted. The tempting answer is to reduce brushing or shorten manual cleaning to catch up. The correct answer is to notify the charge nurse or manager that volume exceeds safe single-staff capacity, follow every validated step on each scope, and let scheduling absorb the delay. Patient safety outranks the case start time, and the department, not the lone technician, owns the staffing problem. Escalation is the action; a shortcut is the trap.

Interruptions and divided attention

Manual cleaning interrupted by a phone call, a co-worker's question, or a competing task is a documented error source because the technician loses their place and may skip or repeat a step. The exam-correct design controls include a dedicated, low-traffic decontamination area, clear separation of clean and dirty workflow, visual "do not interrupt" signals during critical steps, and restarting the step that was interrupted at a critical point rather than guessing where you left off. Multitasking is not a virtue here; single-tasking through the validated sequence is.

Common traps

• Choosing the answer that protects throughput or the surgeon's schedule over the answer that protects the patient.
• Treating a handoff gap as a documentation nuisance instead of a contamination risk; an undocumented scope status defaults to "dirty."
• Assuming an aborted or interrupted AER cycle can simply be resumed — it requires full reprocessing restarting from manual cleaning.
• Believing a soiled scope can wait indefinitely; once the IFU delay window passes, the delayed-reprocessing protocol applies and the delay must be recorded.

Reading the cue when the label is hidden

Scenario items rarely announce "this is a human-factors question." They read like ordinary clinical situations. The cue is the pressure embedded in the stem: a posted case start, a lone technician, a phone ringing, an end-of-shift rush, a manager asking to speed up. When you spot that pressure, switch into human-factors mode and ask whether the tempting answer trades a validated step for time. Practice naming the lever each time — is the stem really about fatigue, workload, communication, competency, ergonomics, or culture? Mislabeling the lever leads you to the wrong family of distractors.

Speaking up is part of the job

The exam frames the technician as an active safety participant, not a passive task-doer. If a scope's status is uncertain, if a colleague looks fatigued, if a connector seems wrong, or if a manager pressures the team to cut corners, the competent reprocessor raises it through the chain — charge tech, manager, infection prevention, risk management. "Stop the line" authority is a legitimate human-factors control: any team member may halt a process they believe is unsafe.

Answers that involve quietly complying, staying silent, or working around the problem are nearly always wrong on the CER exam, because silence is how latent failures reach patients.