8.2 Competency, Training, and Error-Prevention Workflows

8.2 Competency, Training, and Error-Prevention Workflows

This section converts human factors into the workflows the CER exam actually scores: building competency, training to the instructions for use (IFU), and selecting the strongest error-prevention control.

Competency lifecycle

Competency is demonstrated, observed ability — not a class attended or a quiz passed. The standards (AAMI ST91, the device IFU, and accreditation bodies such as The Joint Commission) expect a defined cadence:

Documentation is not optional. Surveyors ask to see dated competency records with the evaluator's signature and the specific task assessed (e.g., "manual cleaning of a duodenoscope, including elevator recess").

Training to the IFU

Reprocessing is IFU-driven: the scope IFU, the AER IFU, the detergent IFU, and the HLD IFU must all be reconciled. Where they conflict, follow the most stringent compatible instruction and contact the manufacturers. Training that teaches a generic "one way to clean a scope" is a trap — a duodenoscope with an elevator, a colonoscope, and a bronchoscope each have model-specific brushing and flushing steps.

Error-prevention hierarchy (high-yield)

The exam favors controls that design the error out of the system over controls that depend on a tired human remembering:

1. Forcing functions / engineering controls — strongest. Example: an AER that will not start a cycle unless connectors are attached and a leak test passes.
2. Standardization — checklists, standard work, identical setups across rooms.
3. Redundancy — a second technician verifies high-risk steps; borescope inspection backs up visual checks.
4. Reminders / education / vigilance — weakest, because they rely on attention that fatigue erodes.

What competency assessment actually includes

The exam expects competency to be verified by direct observation against a written checklist, not by a multiple-choice quiz alone. A complete competency record names the specific task and device, the date, the evaluator, and the outcome. For a high-risk device the evaluator watches the whole sequence: leak test, manual cleaning with the correct brush sizes, brushing of every port and the elevator recess, flushing of all channels with the correct connectors, the rinse, AER loading, drying, and documentation. Partial observation is a trap answer; you cannot verify what you did not watch.

Re-education after an error is also a competency event and must be documented the same way.

Orientation versus continuing competency

New personnel work under direct supervision until initial competency is verified, then move to independent reprocessing. Continuing competency keeps that skill current through the annual cycle and the change-driven triggers. The exam likes to test the difference: a tech who passed orientation two years ago but was never reassessed when the department adopted a new AER is not competent on that AER, regardless of seniority. Experience is not a substitute for documented, current competency.

Worked example

A department wants to stop scopes from skipping the leak test. A poster reminding staff (a reminder) is the weakest fix because it relies on a tired person noticing it. Re-training (education) is stronger but still depends on memory. Building the leak test into a mandatory, signed checklist step (standardization) is stronger still because it makes the omission visible. Best of all is an AER or tracking-system workflow that physically blocks the next step until the leak test is logged — a forcing function that makes the unsafe path impossible. When a stem offers several of these, choose the highest one available.

Common traps

• Calling annual competency "enough" while ignoring the change-driven trigger when a new AER, scope model, or chemical arrives.
• Ranking "more training" as the best fix when a forcing function or standardization is available in the options.
• Confusing prospective tools (checklist, failure mode and effects analysis) with retrospective tools (root cause analysis performed after an event has occurred).
• Treating verbal attestation as documentation; if the competency, in-service, or corrective action is not recorded with a date and signature, a surveyor will treat it as never having happened.

In-service education and the learning loop

Beyond formal competency, departments run in-service education whenever a recall, an outbreak report, a new device, or an audit finding surfaces. A strong human-factors program closes the loop: an error or near miss feeds back into training, the training is verified by competency, and the competency is documented. The exam may describe a recurring error and ask for the best long-term fix; the answer is usually a system change (process redesign plus targeted re-education and competency verification), not a one-time memo. A memo informs; a verified competency proves the skill was rebuilt.

Standardized work across shifts and rooms

Variation between technicians is itself a human-factors hazard. If three techs each clean a colonoscope slightly differently, the process is not validated — only the IFU sequence is. Standardized work means every room is set up the same way, the same brushes and connectors are stocked in the same place, and the checklist is identical regardless of who is on shift. This reduces the cognitive load on a tired or new technician and makes deviations easy to spot.

On the exam, an answer that reduces variability and follows the IFU exactly outranks one that relies on an experienced tech's personal method, no matter how skilled that individual is.

For each scenario, list the trigger, the authority (the device IFU and AAMI ST91), the evidence (the signed record), and the action before you commit to an answer.