What a Positive BI Actually Sets in Motion.

The incubator reads positive. It's one small vial of spores that were supposed to be dead and aren't. And in that moment, the question stops being about one vial — it becomes about every tray that sterilizer has touched since the last time a test came back clean.

A biological indicator is the closest thing sterile processing has to a direct answer. It challenges the cycle with highly resistant bacterial spores; if the process worked, they're killed, and if they survive and grow, the process may not have done what it was supposed to. A positive BI is that second case — and it sets off a sequence that's bigger, and more record-dependent, than people outside the department tend to realize.

The First Move Is to Stop

A confirmed positive BI is treated as a real failure, not a fluke to be waved off. The immediate response, guided by AAMI ST79 and the sterilizer manufacturer's instructions, generally starts the same way: take the sterilizer out of service and don't run another load through it until it's been sorted out. This is the part that should never be improvised — it's a defined response, and the value of a guided flow here is that the technician isn't reconstructing the protocol from memory in a stressful moment.

The Recall Is the Real Event

Here's the part that catches people. A positive BI doesn't just condemn the load it was running in. Everything processed in that sterilizer back to the last negative BI is considered suspect and has to be treated as potentially non-sterile — located, retrieved, and quarantined.

Which means the size of the problem is set by something you decided days earlier: how often you test. Test every load, and the recall is that load. Test daily, and it's a day of loads. Test weekly, and it's every load that sterilizer ran for a week.

Now You Have to Find Them

Once the scope is set, the recall is only as good as your records. To retrieve every suspect item you have to answer, quickly and defensibly: what was in each of those loads, where did it go, and has any of it already been opened or used? Some sits on a sterile-storage shelf. Some is built into case carts. Some may already be in an OR. Some may already have been used on a patient — which pulls in infection prevention and risk management, and raises questions no one wants to be reconstructing after the fact.

This is the moment a department's record-keeping gets tested all at once. Not gradually, not at survey — right now, with the sterilizer down and the clock running.

Then Re-Qualify, Investigate, Document

With the recall underway, the rest of the sequence runs in parallel: investigate the likely cause (operator technique, load configuration, equipment, water or steam quality), and keep the sterilizer out of service until it's re-qualified — typically confirmed with negative BI results before it goes back into use, following ST79 and the manufacturer's guidance. Throughout, everything gets documented and the right people get notified. If suspect items reached patients, that documentation stops being a compliance formality and becomes the basis for a clinical decision.

Where the Decision Layer Earns Its Place

Two things make a positive BI survivable rather than chaotic. The first is a guided response, so the out-of-service, recall, and re-qualification steps are walked in order and documented as they go — not remembered under pressure. The second is records that already exist, captured contemporaneously, so the recall's scope is a query against known load contents instead of an archaeology dig through paper and memory.

You can't prevent every positive BI — that's rather the point of testing. What you can control is whether the day it happens, your department is executing a defined sequence against good records, or improvising one against shaky ones. Guide the decision. Capture the evidence. Defend the outcome — especially on the day the evidence is all anyone wants.