Eight Occlusion-Alarm Complaints in 45 Days: Reportable or Not?
Over 45 days, a 340-bed hospital receives eight internal reports involving the same model of large-volume infusion pump: the pump continues infusing after a downstream occlusion, with no occlusion alarm, and the line is later found to have a kink or closed clamp. One case involved a vasopressor: the delay was discovered roughly four hours later, the patient became hypotensive and was transferred to the ICU for additional support. A second involved a delayed chemotherapy infusion with no lasting harm; the remainder were caught during routine checks. Bench testing by biomedical engineering reproduces the failure on three of the eight pumps with a calibrated occlusion tester, at pressures well above the manufacturer's alarm threshold. All eight pumps are from the same software version, and the hospital switched giving-set suppliers about two months ago. The clinical engineering director must decide what to report, to whom, and on what timeline, while the vendor's local representative is asking that nothing be filed until their investigation concludes.
1. Determine what is reportable, to whom, and by when, and explain how the reporting clock is defined.
Read the worked answer
Framework. As a device user facility, the hospital has obligations under 21 CFR Part 803 (Medical Device Reporting).
The vasopressor event. A delay in vasopressor delivery producing hypotension that required ICU-level intervention is a plausible serious injury - a life-threatening condition, or one requiring intervention to prevent permanent impairment. Under Part 803 a user facility must report device-related serious injuries to the manufacturer within 10 working days of becoming aware. Deaths must be reported to both FDA and the manufacturer within 10 working days. If the manufacturer is unknown, the serious injury goes to FDA as well.
The other seven. Each needs individual assessment against the serious-injury definition. The chemotherapy delay without lasting harm probably does not meet it; the near-misses are malfunctions. Malfunctions that would be likely to cause or contribute to a death or serious injury are primarily manufacturer-reportable, but the hospital should still file a voluntary MedWatch report for the cluster, because the pattern is exactly the signal the reporting system exists to detect.
The clock. "Aware" means when the information first reached hospital personnel - typically the first internal report or the moment biomedical engineering reproduced the fault - not when the committee meets or when the investigation closes. Working days exclude weekends and holidays; counting from a monthly safety meeting is a common and serious error.
The vendor's request. A representative has no authority to suspend a statutory reporting obligation. Note the request in the file, state that the hospital will meet its own obligations, and keep the vendor informed. Do not wait for the vendor's investigation to conclude.
2. Design the internal investigation and its documentation, including the possibilities that would change your reporting decision.
Read the worked answer
Preserve first. Quarantine the implicated pumps and, critically, the giving sets and fluid containers from the events. Do not return devices to the vendor before documenting serial numbers, software version, drug-library version, event date and time, alarm and event logs, and photographs.
Bench work. Repeat the occlusion testing with a calibrated pressure/flow analyzer using the manufacturer's specified method and set. Record the pressure at which the alarm actually fires versus the specified threshold, and the time to alarm. Test both the failed pumps and a sample of pumps that have not failed, so you know whether this is an all-units behavior or a subset.
The confounder that matters most. The giving-set supplier changed about two months ago, and the failures began in that window. Set composition, compliance, and dead-space volume directly affect the pressure the pump's sensor sees and the time required to build occlusive pressure. Test the implicated pumps with both the old and the new sets. If the failure only reproduces with the new sets, the root cause may be a consumable/device interaction - which changes what is reported, what the corrective action is (a set restriction, a labeling change, a software threshold change), and who is responsible.
Also check software version against any vendor field notices, drug-library configuration that could suppress alarms, and whether users might be silencing alarms in a way that mimics the failure. Interview reporters about what they saw, without leading them.
How the decision changes. If the fault reproduces on the bench independently of the giving set, this is a device malfunction with a demonstrated harm mechanism - report and expect a manufacturer correction. If it is set-dependent, report it to both the pump and the set manufacturer, because the hazard is real either way but the responsible party and the fix differ. In neither case does the internal cluster stay internal.
3. The manufacturer later issues an urgent field correction for this software version. Describe the hospital's obligations and the judgement points in responding, and distinguish this from the hospital's own restriction.
Read the worked answer
What a field correction/removal is. When a manufacturer initiates a correction or removal to address a violation or a risk to health, FDA classifies it - Class I where there is a reasonable probability of serious adverse health consequences or death, Class II for temporary or reversible harm, Class III for unlikely harm. The classification drives urgency, not the wording of the vendor's letter.
Hospital obligations:
- Route the notice to a designated recall coordinator, not to whoever happens to open the mail.
- Reconcile the affected serial numbers or lots against the CMMS inventory, plus rentals, loaners, and units in storage or out on trial elsewhere in the system.
- Quarantine affected units or apply the correction, and verify the correction on each device rather than trusting the label.
- Return the acknowledgment even if no affected product is on hand - "none on hand" is a required answer, not a non-response.
- Document completion dates and retain records for the required period, and report completion status internally to risk management and clinical leadership.
Judgement points:
- A recall does not automatically close the hospital's own event file; the MDR report, the internal investigation, and the recall response must stay mutually consistent.
- Do not stand down interim clinical safeguards - independent double-checks on high-alert infusions - until the correction is verified across the fleet, not merely announced.
- The hospital's own earlier restriction (for example, prohibiting a particular giving set with these pumps) is a separate, self-imposed control with its own authority and its own removal criteria; it does not substitute for executing the manufacturer's correction, and the correction does not automatically lift the local restriction.
- Transparency: communicate the sequence of events, findings, and actions to risk management and the medical staff, and support any patient disclosure that risk management and treating clinicians determine is required.