Case Study

Why retained surgical sponges remain a never-event problem

Two retained-sponge events in a single year is not a number a hospital files away quietly. For the 380-bed trauma center in this case study, it was the prompt to stop treating the manual count as sufficient on its own and to put an electronic backstop behind it. What follows is what they changed, what it cost, and what happened over the next 18 months — a working record rather than a sales pitch. Retained Surgical Items (RSI) — particularly sponges — are classified as never events by CMS yet still occur at a documented rate of 1 per 5,500 operations nationally. The customer is a 380-bed Level II trauma center with 14 ORs running ~9,800 cases/year. Our RFID surgical sponge tracking explainer covers the broader clinical case.

• Baseline: 2 RSS events in the 12 months pre-deployment; 1 required reoperation, settlement value $850K.
• Manual count compliance: 96.8% — but the 3.2% gap captures all RSS risk; standard practice is x-ray verification on miscount.
• Joint Commission survey 2024: 14 documentation findings related to surgical-count records (mostly missing initials, not actual count errors).
• Existing infrastructure: Epic OpTime, Stryker SurgiCount manual barcode-counter for 30% of cases (not enough adoption).
• Champion: VP Quality + Chief of Surgery — without exec sponsorship this kind of clinical-workflow change does not land.

9-month deployment across 16 surgical spaces

The vendor-of-record was Stryker, but tag supply moved to a custom RFID-tagged sponge pack co-packaged for the customer (Stryker SurgiCount-compatible). We helped the customer evaluate tag-supply economics and FDA UDI labeling. See our healthcare RFID FDA UDI compliance guide for the regulatory framework.

• Tag spec: chip-and-antenna assembly embedded in sterile gauze sponge, autoclave-survivable, FDA-cleared for in-vivo detection use.
• Reader: handheld wand at end of case + portal at every OR exit door (16 total) with audible/visual alert if tagged item exits unaccounted.
• Workflow change: surgical count protocol updated to require wand sweep before closure; ~90 seconds added to each case.
• Training: 100% of OR nurses + 100% of surgical techs across 6 weeks; pocket reference card for trauma cases.
• Capex: $410K all-in (readers, portals, integration with Epic OpTime, training); per-case consumable cost +$8.40 in tagged sponges.

18-month outcomes and risk-adjusted ROI

Quality outcomes were the headline; financial returns came largely from avoided malpractice exposure and reduced reoperation cost. The framework for hospital RFID ROI in patient-safety domains is in our hospital RFID patient-safety ROI methodology.

• RSS events: 2 in pre-deployment 12 months → 0 in 18 months post (statistically significant given the customer's case volume).
• Joint Commission findings: 14 → 2 in next survey cycle (87% reduction); both remaining findings were unrelated to surgical counts.
• Reoperation avoidance: minimum 1 reoperation prevented at ~$48K average direct cost; risk-adjusted malpractice exposure reduction modeled at ~$1.2M annualized.
• Workflow time: +90 seconds per case = +245 OR hours/year; offset by ~180 hours saved on x-ray verification of miscount events.
• Surgeon adoption: 94% of surgeons rated wand sweep "helpful" or "very helpful" in 6-month survey; 4% "neutral," 2% "hindrance" (mostly trauma cases under time pressure).

How does this case compare to published RSS data and competitor systems?

The customer's results are best read against the published industry baseline. STERIS's review of retained surgical items (Mayo Clinic Gawande/Studdert/Brennan studies and Pennsylvania Patient Safety Authority data, both cited in STERIS's 2023 RSI prevention writeup) sets the comparison. AORN's RSI guideline (2019) frames the regulatory expectation. Stryker SurgiCount, STERIS ORLocate and the legacy RF Surgical (now Stryker) systems are the FDA-cleared adjunct technologies most US hospitals weigh.

• Mayo Clinic baseline: a four-year Mayo study cited by STERIS placed RSI incidence at approximately 1 in every 5,500 surgical procedures, with ~1,500 cases per year estimated nationally. The customer's 2-event pre-baseline against ~9,800 cases/year sits at roughly 1 in 4,900 — slightly worse than the Mayo benchmark, which is what triggered the program.
• Pennsylvania Patient Safety Authority cost reference: STERIS cites a ~$166,000 average cost per RSI event including legal defence, indemnity and unreimbursed surgical care. The customer's avoided $48K direct reoperation cost is the conservative floor; full malpractice-modelled exposure ($1.2M annualised) aligns with PPSA-style total-cost framing.
• ECRI adoption baseline: STERIS quotes ECRI's estimate that only ~20% of US hospitals use any adjunct sponge-counting technology. ORLocate, Stryker SurgiCount and the legacy RF Surgical wand are the dominant FDA-cleared options; the customer chose a SurgiCount-compatible RFID extension to preserve their existing barcode workflow rather than replace it.
• STERIS ORLocate technical reference: STERIS publishes that the ORLocate locator wand reads tagged sponges up to 19 inches in vivo, while the HoveRead handheld counts at ~6 inches. The customer specified portal readers for door coverage at 16 OR exits in addition to the wand — defence-in-depth that single-vendor literature does not always emphasise.
• AORN guideline alignment: AORN's Guideline for Prevention of Retained Surgical Items (2019) recommends that adjunct technology supplement, not replace, the manual count, with closure deferred until the adjunct confirms the count. The customer documented this rule explicitly in their updated count protocol — auditors looked for that language and Joint Commission findings dropped accordingly.

What questions do prospective customers most often ask after reading this?

After publishing the headline metrics, the inbound questions are predictable. Each of the five below has come up in at least 6 of the last 10 hospital RFP conversations on RSS-prevention RFID.

• How does the wand integrate with our existing Stryker SurgiCount inventory? In this customer's setup, SurgiCount continued to handle non-tagged items (instruments, needles, raytec sponges purchased before the changeover); RFID-tagged sponges flow through both SurgiCount barcode counting and the RFID wand sweep, with redundant logging in Epic OpTime. Removing SurgiCount entirely was rejected because it would have re-trained a workflow already at 30% adoption.
• Could we deploy without the door portals? The wand alone covers in-vivo and waste-bin detection per STERIS ORLocate's published in-vivo range (~19 inches). The 16 door portals add 'sponge leaving the room' detection that catches sponges accidentally bagged with linen or trash before the closing count — which is where RSS reports to AORN and the Joint Commission Sentinel Event Alert most commonly originate.
• What about the trauma bays? Trauma cases (2 of the 16 spaces) are the highest RSS risk per AORN's commentary on emergent / unplanned procedures. The customer's protocol allows wand-only verification (skipping the closing manual count) for level-1 trauma where time precludes a structured count, with a mandatory wand sweep before drape removal — explicitly aligned with AORN's adjunct-technology language.
• How was FDA UDI handled for the tagged sponges? The tagged sponges are commercially supplied with FDA clearance for in-vivo detection (the underlying chemistry is the same as Stryker SurgiCount RF / ORLocate sponges). The hospital's documentation file cites the supplier 510(k) reference and applies the supplier's UDI on each sponge SKU — no in-house labelling work was needed beyond receiving inspection.
• What about the radio-opaque marker requirement? AORN guidelines retain the radio-opaque thread requirement on all surgical sponges so sponges remain x-ray detectable as a final-defence layer. The RFID-tagged sponges this customer adopted include the standard radio-opaque thread per AORN; RFID is the primary adjunct, x-ray verification remains the long-stop, manual count remains the foundation.

FAQ