Wireless Infusion Pumps Dropping Off the Network
A hospital deployed 120 wirelessly connected infusion pumps for dose-error-reduction software and drug-library updates. Within a month, biomedical engineering logs show 8–12% of pumps failing to receive library updates, and intermittent 'off network' status. The pumps roam between units on mobile poles. IT reports the wireless network is 'fine' based on access-point uptime. Nursing occasionally bypasses the pump's drug library when it appears outdated. The pharmacy updates the library monthly. There is no documented process for verifying that a library update reached every pump. A recent event involved a pump running an old library version during a high-alert medication infusion.
1. Why is 'access-point uptime' an inadequate measure of pump connectivity, and what would you measure instead?
Read the worked answer
Access-point uptime measures infrastructure availability, not client experience. Pumps are mobile clients that roam, and connectivity failures are often client-side or RF-environmental.
Better metrics:
- Per-device association success rate and time-to-reconnect after roaming.
- Library version compliance rate - percentage of pumps on the current library, by unit.
- Update delivery latency - time from pharmacy release to confirmed receipt per pump.
- Drop-event counts correlated with physical location (dead zones, elevator banks, shielding).
- RF survey data in patient-care areas, not just at access points.
Reasoning: a pump can be 'off network' while every access point is up, so uptime cannot detect the failure that matters - a pump running an outdated library.
2. Nursing bypasses the drug library when it looks outdated. How do you address this as a system problem rather than a training problem?
Read the worked answer
A bypass is a rational response to an unreliable system; fix the system first.
- Make library status visible and trustworthy: display the current library version and last-update time on the pump so staff can tell whether it is current.
- Close the verification loop: build a process that confirms each pump received the update, with a compliance report by unit, and a defined action for pumps that miss it.
- Reduce the need to bypass: if a pump is genuinely outdated, provide a clear escalation path (swap the pump, notify pharmacy/BME) rather than leaving the clinician to choose between an old library and no library.
- Analyze bypass events as quality data - track rate and reasons, and feed back to the pharmacy/BME loop.
Training alone will not fix a workflow where the correct action is unclear or unavailable.
3. Design the verification process for monthly library updates.
Read the worked answer
A closed-loop process:
- Release - pharmacy publishes the library with a version identifier and effective date.
- Distribution - push to all pumps; log target and confirmed receipt per device.
- Verification - automated report of pumps on the new version vs. the prior version; flag any pump not confirmed within a defined window (e.g., 72 hours).
- Exception handling - for unconfirmed pumps, locate, connect, or swap; document resolution.
- Sign-off - BME and pharmacy jointly confirm 100% compliance or documented exceptions before the update is considered complete.
- Audit - periodic spot checks and a monthly compliance metric reported to the safety committee.
This converts an invisible failure into a measurable, auditable one.