Retained Surgical Item Prevention: Counts, Adjunct Technology, and the Cases Where a Correct Count Still Fails

A retained surgical item (RSI) — also called a retained foreign object (RFO) or unintentionally retained foreign object (URFO) — is any sponge, instrument, needle, or other surgical material left inside a patient after a procedure closes. It is one of the smallest-volume categories of surgical harm and one of the most consequential: it sits on the National Quality Forum’s Serious Reportable Events list (the formal source of what the industry calls a “never event”), it is a CMS Hospital-Acquired Condition that affects payment for the resulting care, and The Joint Commission treats a confirmed RSI as a reviewable sentinel event requiring a comprehensive systematic analysis. For an infection preventionist, patient-safety officer, quality director, or risk manager, RSI prevention is not primarily a surgical-technique question — it is a systems question about count protocol design, escalation when a count fails to reconcile, and where adjunct technology fits around (not instead of) the count. This page covers all three, plus the specific clinical scenarios in which a correctly performed count still misses a retained item.

Page checked August 2026. The count-protocol structure and risk-factor findings below reflect well-established, widely-published perioperative and patient-safety nursing literature — principally AORN’s Guideline for Prevention of Unintentionally Retained Surgical Items and the peer-reviewed case-control literature on RSI risk factors — rather than a fresh direct fetch of AORN’s current guideline text; aorn.org’s guideline pages returned 404s to automated retrieval when checked for this page. Confirm current wording, any facility-specific variation, and the exact current edition of the AORN guideline against your own perioperative services policy and your AORN Guidelines for Perioperative Practice subscription before treating any specific step below as verbatim current guideline language.

Why RSI Is Classified the Way It Is

Three separate classification systems apply to a retained surgical item, and a program’s response depends on getting the distinction right:

• NQF Serious Reportable Event (“never event”). Retention of a foreign object in a patient after a surgical or other invasive procedure is one of the National Quality Forum’s Serious Reportable Events — the formal list behind the term “never event.” Classification as an SRE is what drives most states’ mandatory-reporting requirements and a hospital’s own root-cause-analysis obligation.
• CMS Hospital-Acquired Condition. “Foreign Object Retained After Surgery” has been on CMS’s Hospital-Acquired Condition list since the original 2008 IPPS policy. When an RSI is coded as not present on admission for an inpatient stay, CMS pays the claim as though the complicating condition were not present — the hospital does not receive the additional payment the higher-severity coding would otherwise generate. This is a distinct mechanism from the Hospital-Acquired Condition Reduction Program’s payment penalty, which is based on a hospital’s PSI-90 composite score rather than any single event — see CASRAI’s guide to the Present on Admission (POA) indicator for how the coding decision drives which mechanism applies.
• Joint Commission reviewable sentinel event. An RSI that reaches a patient and results in death, permanent harm, or severe temporary harm meets The Joint Commission’s own sentinel event definition, triggering the same comprehensive systematic analysis and corrective action plan obligations covered in CASRAI’s sentinel event guide — including, for accredited hospitals, the reporting and response timeline described there.

These three classifications overlap on the same event but are administered by three different bodies (NQF, CMS, The Joint Commission) with three different consequences — public/state reporting, reimbursement, and accreditation review, respectively. A single retained-item event can trigger all three simultaneously, which is exactly why RSI prevention sits at the intersection of clinical risk management and regulatory operations rather than being purely a perioperative nursing concern.

The Counting Protocol

The baseline defense against RSI is a manual count of sponges, sharps, and instruments performed at defined points in the case, following AORN’s Guideline for Prevention of Unintentionally Retained Surgical Items. The standard count points are:

1. Before the procedure begins — the baseline count, establishing what’s on the field before the first incision.
2. Before closure of a cavity within a cavity — for example, before closing the uterus during a cesarean delivery, or before closing any secondary cavity opened during the case, since items left there become inaccessible to a later wound check once the outer layer closes.
3. Before wound closure begins — the count that has to reconcile before the surgeon starts closing.
4. At skin closure — the final count.
5. At the time of permanent relief of either the scrub person or the circulating nurse — a relief count, independent of where the case is in its own timeline, whenever either counting role changes hands.

Counts are performed audibly and visibly by two people — typically the scrub person and the circulating nurse — counting concurrently rather than one person counting alone and reporting a number. That two-person, concurrent-count structure is what makes a count a genuine independent check rather than a single point of failure repeating itself at five points in the case.

When a Count Doesn’t Reconcile

An incorrect count is not itself the failure — it is the protocol working as designed by catching a discrepancy before closure is complete. What has to happen next, in order, is what the count-discrepancy protocol actually governs:

1. Stop and recount. Both counters independently recount the category that didn’t reconcile before assuming an item is genuinely missing.
2. Search the field, then the room. A methodical search of the surgical field and wound, followed by the immediate surroundings — the floor, linens, trash and sharps containers, and any specimen sent from the field — in a defined sequence, not an ad hoc look-around.
3. Notify the surgeon and the rest of the team at the point the discrepancy is confirmed, not after the search concludes, so the surgeon can extend the wound exploration before closure proceeds further.
4. Obtain intraoperative imaging before the patient leaves the OR if the item still isn’t accounted for. This is the backstop step: a radiographic (or, for some items, other imaging) study read before the patient is transferred out of the operating room, specifically to rule out a retained item the physical search didn’t find. Delaying this until recovery or after discharge defeats its purpose — the entire value of “before the patient leaves the OR” is that a confirmed retained item can still be removed in the same operative encounter.
5. Document the discrepancy, the search, the imaging result, and the resolution in the operative record regardless of outcome — an incorrect count that resolved correctly is still a near-miss worth capturing for your program’s surveillance, not just the confirmed RSI cases.

A facility’s count-discrepancy policy should name who has authority to proceed with closure over an unresolved discrepancy (in practice, this should be close to “no one, without imaging”) and should require the imaging read to be documented before the patient leaves the room, not deferred to the formal radiology report reaching the chart later.

Adjunct Technology: Radiofrequency and Barcode Systems

AORN’s guideline frames radiofrequency (RF) detection and bar-code or data-matrix sponge-counting systems as adjuncts to the manual count, not replacements for it. The two families work differently:

• Radiofrequency (RF) detection. Sponges are manufactured with an embedded RF tag. Before closure, a wand or mat is passed over (or the patient is scanned across) the surgical field and, for some systems, the whole body, to detect any tagged sponge still present regardless of whether the manual count reconciled. This catches the specific failure mode where a sponge is miscounted (not just misplaced) — the count says correct, and the RF scan disagrees.
• Bar-code / data-matrix counting. Each sponge carries a unique scannable code. Sponges are scanned onto the field and scanned off as they’re removed, with the system maintaining a running electronic count independent of (and cross-checked against) the manual tally. This adds documentation rigor and catches simple counting-arithmetic errors, but — unlike RF detection — it does not independently confirm a sponge’s physical absence from the patient the way a body scan does.

Both technology families are commonly deployed for sponges specifically; instruments and sharps still rely primarily on the manual count and, when a discrepancy occurs, imaging. Adopting either technology is a supplement to the five-point manual count above, not a justification for skipping or abbreviating it — the count-discrepancy protocol in the previous section still applies in full when the technology itself flags a discrepancy the manual count missed.

Why RSI Still Happens Despite a Correct Count

The finding most relevant to program design is that a meaningful share of confirmed retained-item cases occur despite the manual count being reported as correct at every count point. That is not a description of counting technique failing in the moment — it is a description of specific case circumstances under which a normally reliable process becomes unreliable. The scenarios most consistently associated with RSI in the peer-reviewed case-control literature on this question are:

• Emergency surgery. Compressed timelines, less predictable staffing, and higher case acuity all work against the disciplined, unhurried execution the counting protocol assumes.
• Unplanned change in the procedure. When the operative plan changes mid-case — an additional procedure, an extended exploration, a different approach than the one the team prepared for — the baseline count established at the start of the case no longer matches what’s actually needed, and additional items introduced mid-case are the ones most likely to fall outside a count point.
• Higher patient body mass index. A larger surgical cavity and greater soft-tissue depth make a sponge or small instrument harder to locate on physical exploration and harder to resolve on imaging, compounding both steps of the count-discrepancy pathway above.

Two further factors are widely recognized in perioperative safety literature as compounding these three, though the evidence base for them is broader and less specific to a single landmark study: multiple surgical teams or specialties operating in the same case (each with its own instruments and sponges on the field), and a scrub or circulating staff change during a long or high-blood-loss procedure — which is precisely why the counting protocol requires an independent relief count rather than treating a shift change as covered by the case’s other count points.

The case-control literature establishing emergency surgery, unplanned procedure change, and elevated BMI as independent risk factors for RSI is well-established and widely cited in perioperative and patient-safety curricula; this page states the finding qualitatively rather than citing specific effect sizes, since that specific figure was not re-verified against a fresh primary source within this session (see the sourcing note above) and a precise multiplier is exactly the kind of number that should not be stated without direct verification.

Building This Into Your Program

For a patient-safety or quality program, the practical implication of the section above is that count-correct cases are not automatically low-risk cases. A program built only around “did the count reconcile” misses the population of cases where it reconciled and an item was still retained. A more complete approach:

• Flag high-risk case types prospectively — emergency add-ons, cases with a documented intraoperative change in plan, and patients above your facility’s defined BMI threshold — for mandatory adjunct-technology use where available, rather than leaving adjunct use to individual surgeon or team preference.
• Route every count discrepancy, resolved or not, through the same near-miss capture your program already uses for other close calls, so PDSA-style improvement work (see CASRAI’s PDSA cycle guide) has real denominator data, not just the numerator of confirmed events.
• Treat a confirmed RSI as a sentinel event requiring root cause analysis, using a structured technique-selection approach (see CASRAI’s guide to choosing an RCA technique) rather than an incident-specific ad hoc review, and route the analysis through your PSO where your facility participates in one, for the work-product privilege protections covered in CASRAI’s PSO reporting and privilege guide.
• Review the case, not just the individual, using your program’s just culture framework (see CASRAI’s just culture algorithm guide) — the risk-factor pattern above is a systems finding, and a review process that defaults to blaming the counting staff for a count that was, in fact, performed correctly will miss the actual lever available to your program.
• Confirm relief counts are actually independent — a shift or staff change mid-case is exactly the kind of transition where CASRAI’s SBAR handoff discipline for clinical information should extend to the count itself, not just to clinical status.

Frequently Asked Questions

What counts as a retained surgical item?

Any sponge, instrument, needle, or other surgical material unintentionally left inside a patient after a surgical or other invasive procedure closes. It is also referred to as a retained foreign object (RFO) or unintentionally retained foreign object (URFO) in the literature and in some facility policies.

Is a retained surgical item always a reportable never event?

Retention of a foreign object after a surgical or invasive procedure is on the National Quality Forum’s Serious Reportable Events list, which is the formal source of the “never event” designation, and most state mandatory-reporting frameworks that use the NQF/SRE list as their basis treat it accordingly. Confirm the exact reporting trigger and timeline against your own state’s mandatory-reporting statute, since implementation details vary by state.

Does a correct final count rule out a retained item?

No. A meaningful share of confirmed RSI cases occur despite every manual count being reported as correct, which is why AORN frames radiofrequency and bar-code adjunct technologies as a supplement to the manual count rather than treating a reconciled count alone as sufficient assurance, particularly in the high-risk case types covered above.

Do radiofrequency or barcode systems replace the manual count?

No. Both technology families are adjuncts under AORN’s guideline. The manual, two-person concurrent count at all five standard count points remains the baseline requirement regardless of whether adjunct technology is also in use.

What should happen if a count doesn’t reconcile before closure?

A recount, followed by a methodical search of the field and room, followed by intraoperative imaging before the patient leaves the operating room if the item is still unaccounted for, with the discrepancy, search, and outcome all documented regardless of whether the item is ultimately found.

Does a retained surgical item affect hospital reimbursement?

Yes. “Foreign Object Retained After Surgery” is a CMS Hospital-Acquired Condition; when coded as not present on admission, CMS pays the claim as though the higher-severity complication were not present, separate from any effect on the hospital’s broader HAC Reduction Program score.