On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Helps isolate loose connections, damaged cables, contaminated contacts, positioning, strain, and accessory-related causes of intermittent probe or docking communication.
Step-by-Step Troubleshooting
1. Protect Patient Care and Confirm the Complaint
Do not troubleshoot intermittent probe communication while staff are depending on the scanner for a patient assessment. Provide another verified bladder scanner when the intermittent condition could affect examination reliability.
Determine whether communication fails:
- Continuously
- Only when the cable is moved
- At a particular connector
- When placing or removing the device from a dock
- During scanning
- After transport
Expected outcome: The intermittent condition and circumstances that reproduce it are clearly identified.
2. Inspect the Probe and Cable Externally
Inspect the full accessible cable length and probe assembly for:
- Cuts
- Kinks
- Crushing
- Fraying
- Fluid intrusion
- Strain near cable exits
- Cracked housings
- Evidence of improper cleaning or impact
Do not continue using a damaged patient-contact probe or cable.
Expected outcome: The cable and probe show no unsafe physical damage. If damage is found, remove the affected equipment from service and replace or repair it through the approved process.
3. Inspect Accessible Connectors
Power down as appropriate before manipulating connections. Inspect accessible connector surfaces for:
- Bent or damaged contacts
- Debris
- Moisture
- Misalignment
- Loose fit
- Cracked connector shells
Do not force connectors.
Expected outcome: Connectors are clean, dry, undamaged, and seat normally. If reseating a loose external connection restores stable communication, proceed to final verification.
4. Reseat the Connection
Disconnect and reconnect the accessible probe or communication connection according to the normal approved connection method.
Ensure the connector is fully seated without excessive force.
Expected outcome: The probe or connected component is recognized consistently. If communication remains stable after repeated normal movement and use, the issue is resolved.
5. Perform a Gentle Movement Check
With the device off the patient and in a controlled test condition, gently move the cable near:
- Probe strain relief
- Connector strain relief
- Normal bends
- Docking interface
Do not sharply bend, twist, or stress the cable.
Expected outcome: Communication remains stable during normal cable movement. If communication drops with gentle movement, remove the device or affected accessory from service and escalate.
6. Inspect the Docking Interface
If the complaint involves docking, inspect accessible docking surfaces and contacts for contamination, damage, improper seating, or mechanical obstruction.
Confirm the device sits fully in the dock without rocking or requiring unusual pressure.
Expected outcome: Docking is secure and communication remains stable. If cleaning or proper seating corrects the problem, troubleshooting can stop after verification.
7. Use a Known-Good Compatible Accessory When Available
If facility resources permit, substitute a verified compatible probe, cable, dock, or applicable accessory to isolate the failure.
Do not interchange equipment unless compatibility is confirmed.
Expected outcome: A known-good component allows stable operation. If substitution identifies a faulty external accessory, replace that accessory and verify normal operation.
8. Perform Final Functional Verification
Complete a representative scan and confirm:
- Probe recognition remains stable
- Communication does not drop during normal positioning
- Cable movement within normal use does not interrupt operation
- Docking functions normally when applicable
- No new warnings or failures occur
Expected outcome: Stable operation is verified through a complete representative test. The device may be returned to service.
If the Problem Persists
External cable condition, connector seating, accessible contacts, docking alignment, and known-good substitutions have been evaluated. The remaining issue may involve an internal connector, interface circuitry, probe electronics, docking electronics, or another service-level communication fault.
The device should be:
- Removed from service
- Labeled Out of Service
- Sent for repair or bench evaluation
- Evaluated using appropriate Verathon documentation and approved test equipment
- Repaired or configured only by qualified personnel
Complete appropriate return-to-service functional testing before clinical use.
An intermittent connection that cannot be made reliably stable is a valid reason to stop troubleshooting and escalate.
Clinical Use Tip
Intermittent probe communication can undermine confidence in examination reliability; exchange the scanner before continuing patient assessment.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Nursing reported the Prime Plus intermittently lost probe communication when the scanner was moved."
Cause
What was observed during troubleshooting.
Example:
"Clinical Engineering found the external probe connector was not fully seated and communication dropped with normal cable movement."
Resolution
What action was taken.
Example:
"Clinical Engineering reseated the connector, verified stable recognition through repeated movement and representative scanning, and returned the unit to service."
Helpful Details to Include (If Known)
- When communication dropped
- Whether movement reproduced the issue
- Probe and cable physical condition
- Connector condition
- Docking interface condition
- Known-good accessory substitution
- Recognition status before and after reseating
- Representative scan result
- Final device status
Final Thought
Intermittent communication should be treated as a reliability problem, not ignored because the device occasionally works. Rule out external cables, connectors, and docking conditions first, verify stable operation, and escalate any unresolved intermittent fault with clear documentation.
That is successful troubleshooting.