Class I Defibrillator Recall Nine Days Before the Vendor Arrives
You are the HTM manager at a 300-bed hospital. On Monday at 08:00 the defibrillator vendor sends an urgent Medical Device Correction letter: a firmware defect can cause the device to enter a service mode and fail to charge after a specific sequence of battery removal and reinsertion. FDA has classified the action Class I. Your CMMS lists 38 defibrillators: 26 are the affected model, of which 4 are in the ED, 6 in ICU, 2 in the OR, 2 on code carts, 3 are vendor loaners currently in use, 2 are in the biomed shop, and 7 are in storage. The other 12 units are a different model. The correction requires a vendor field service engineer to load firmware, about 30 minutes per device, and the vendor's first available visit is in nine days. The hospital has no rental contract for defibrillators. At the last CMS survey the hospital was cited for preventive maintenance completion of 78%.
1. Describe your actions and documentation for the first 72 hours.
Read the worked answer
The correction letter is a controlled document, so the response has to be traceable from receipt to closure.
- Verify scope against serial numbers, not model names. Pull the affected serial range from the letter and match it to the CMMS and to a physical inventory. The CMMS is known to be incomplete, so physically confirm each of the 26 units, and specifically confirm the serials of the 3 loaners, which may belong to the vendor's pool and may or may not be in the affected range.
- Quarantine. Remove affected units from service, tag them, and move them to a locked area in biomed. Update equipment status in the CMMS so no one redeploys them, and physically check every code cart rather than trusting the asset list.
- Do not self-install firmware unless the vendor authorizes it in writing. Unauthorized modification can void the corrective action and the device's regulatory status.
- Notify: risk manager, CMO, nursing leadership for ED/ICU/OR, materials/contracts, and the recall coordinator. Complete and return the vendor's effectiveness check form and log the recall in the recall tracker.
- Assess for prior harm. Determine whether any affected unit failed to charge since the defect was introduced; if a device-related death or serious injury occurred, file a MedWatch user facility report within 10 working days and preserve the device and its logs.
- Communicate a one-page instruction to clinical staff: how to identify an affected unit, what to do if one is found, and who to call.
- Arrange coverage before the end of day one.
2. There is no spare fleet and the vendor cannot arrive for nine days. How do you maintain defibrillation coverage, and how do you decide whether any affected unit may remain in use?
Read the worked answer
First, count what is actually usable: 12 unaffected units plus any loaners confirmed outside the affected serial range. That is likely 12-15 devices for a 300-bed hospital with an ED, six ICUs, and an OR suite, which is short but not zero. I would allocate by acuity: ED resuscitation rooms first, then each ICU, then the OR, and place the remainder where response times are longest.
Coverage options in parallel: rent defibrillators from a regional vendor even without an existing contract (procurement can issue a short-term agreement), request mutual aid from sister facilities, and ask the manufacturer to accelerate the visit or ship field-replaceable units. Escalate the nine-day gap in writing to the CMO and CNO so the risk is owned at the executive level, not absorbed quietly by biomed.
The decision rule for any affected unit is the recall instruction itself. A Class I correction that says do not use means the device comes out of service; convenience does not override it. If leadership concludes that some affected units must remain available as a last resort, that decision must be documented as a formal, time-limited risk acceptance signed by the CMO and the safety officer, with explicit conditions: only units whose battery-removal sequence can be avoided, staff trained on the failure mode, an unaffected device brought to every resuscitation, and a defined end date.
The two units in the shop and the seven in storage stay quarantined until firmware is applied. Storage units are the easiest place for a missed device to reappear on a code cart, so they need physical tagging, not just a CMMS status change.
3. The 78% preventive maintenance completion finding and this recall are connected. How do you address the underlying system problem?
Read the worked answer
They are the same failure. A recall response depends entirely on knowing what you own and where it is; a PM program at 78% means roughly one in five devices is not being tracked on schedule, and the same gaps hide recalled units in storage closets or on loan.
Diagnosis first. Typical causes are equipment that never entered the CMMS at acceptance, PMs scheduled without protected staff time, no escalation when a PM is missed, and no reconciliation between the asset list and what is physically on the floors. I would sample the 22% of missed PMs and classify the reasons before writing a corrective action plan.
Then the fixes:
- Inventory reconciliation: a physical sweep with barcode or RFID tagging, including storage, loaners, and rental equipment, with an owner and a completion date.
- Acceptance process: no device enters service without an asset record, PM schedule, and recall enrollment.
- Protected PM time: scheduled blocks on the biomed calendar rather than PMs fitted around repairs, with a defined backlog threshold that triggers escalation.
- Weekly reporting of PM completion by department and device type to department leaders, and monthly to the Environment of Care committee.
- Alternative equipment maintenance where standards and manufacturer instructions allow, documented in policy, to make the workload realistic for 3.5 FTE.
- Internal audit: re-sample 30 records after 90 days to confirm the number is real and not a reporting artifact.
A recall plan is only as good as the inventory underneath it, so I would present these as one corrective action with one owner and one timeline.