On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshoots nonresponsive bolus or PCA handsets caused by connection problems, damaged accessories, incorrect configuration, lockout state, or device-side recognition failure.
Step-by-Step Troubleshooting
1. Protect the Patient and Maintain Therapy
If the handset controls patient-requested dosing or another clinically important function, ensure the patient has a safe alternate method for pain or therapy management while troubleshooting occurs.
Do not leave a patient dependent on a known-unresponsive bolus control.
Expected outcome: Patient care continues safely without reliance on the defective control.
2. Confirm the Exact Complaint
Determine whether the handset:
- Never responds
- Responds intermittently
- Is physically damaged
- Produces no pump indication when pressed
- Works only in certain positions
- Is believed to be blocked by lockout or programming
Expected outcome: The failure is distinguished from normal programmed dose restrictions.
3. Verify the Therapy Configuration
Confirm through authorized clinical workflow that the pump is actually configured for the function expected from the handset.
Do not change therapy settings just to make the handset respond.
Expected outcome: The connected control is appropriate for the currently configured therapy. If the function is intentionally unavailable due to configuration, troubleshooting can stop after clarification and documentation.
4. Check for Normal Lockout Behavior
Determine whether the reported nonresponse is occurring during a programmed lockout or other expected restriction.
The pump's clinical indication should be interpreted according to approved use procedures.
Expected outcome: Normal lockout behavior is not mistaken for accessory failure. If the device and handset are functioning as programmed, troubleshooting can stop.
5. Inspect the Handset
Examine the external accessory for:
- Cracked housing
- Stuck button
- Damaged cable
- Bent connector
- Contamination
- Fluid intrusion
- Strain near the cable ends
Remove visibly damaged accessories from service.
Expected outcome: The handset is physically intact or identified as defective. If replacement of a damaged handset resolves the issue, troubleshooting can stop.
6. Verify the Connection
Disconnect and securely reconnect the handset using approved procedures.
Inspect the pump's external connector for debris, damage, or looseness.
Expected outcome: The handset is fully connected and recognized. If reseating the connection restores reliable operation, troubleshooting can stop.
7. Test for Position-Dependent Intermittency
With the pump off the patient, gently observe whether ordinary cable movement causes the accessory to connect or disconnect intermittently.
Do not aggressively flex or stress the cable.
Expected outcome: The handset remains reliable during normal movement. If movement reproduces the failure, replace the accessory or escalate a suspected connector problem.
8. Substitute a Known-Good Compatible Handset
Use a known-good approved handset when available.
This determines whether the problem follows the accessory or remains with the pump.
Expected outcome: A known-good handset functions normally. If so, the original handset is the likely cause and troubleshooting can stop.
9. Perform Final Functional Verification
Using an approved non-patient test setup and authorized configuration, verify that handset activation is detected appropriately and that the pump responds according to its programmed state.
Also confirm relevant alarm, display, and control functions.
Expected outcome: The accessory and pump respond reliably during controlled testing. If all required checks pass, troubleshooting can stop.
10. Escalate Persistent Nonresponse
If a known-good compatible handset is not recognized or does not function with correct configuration, remove the pump from service when the handset function is required.
Do not repair the internal connector or alter protected configuration without approved service procedures.
Expected outcome: The device is routed for service-level evaluation.
If the Problem Persists
Accessory damage, connection problems, configuration, and normal lockout behavior have been ruled out. Remaining causes may involve the pump's accessory interface, connector assembly, software, configuration, or internal electronics.
The device should be:
- Removed from service when the affected function is required
- Labeled Out of Service
- Sent for repair or bench evaluation
- Evaluated using appropriate manufacturer documentation and approved test equipment
- Repaired or configured only by qualified personnel
Complete applicable handset, alarm, and pump functional testing before clinical use.
Knowing when to stop external troubleshooting and escalate is proper troubleshooting.
Clinical Use Tip
For PCA or similar patient-controlled therapy, provide the patient an alternate safe clinical pathway before testing or exchanging a nonresponsive handset.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Nursing reported the PCA bolus handset connected to the Sapphire did not respond when pressed."
Cause
What was observed during troubleshooting.
Example:
"Clinical Engineering found the handset cable damaged near the connector and intermittently open during movement."
Resolution
What action was taken.
Example:
"Replaced the handset with a known-good approved accessory and verified consistent bolus-input recognition during functional testing."
Helpful Details to Include (If Known)
- Therapy mode in use
- Whether lockout was active
- Handset condition
- Cable and connector condition
- Pump-side connector condition
- Intermittent behavior with movement
- Known-good handset result
- Pump response when button pressed
- Functional-test result
- Final device status
Final Thought
A nonresponsive handset may represent normal lockout behavior, accessory damage, or a pump interface fault. Confirm configuration and the external accessory first, and do not return unreliable patient-control hardware to service.
That is successful troubleshooting.