On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Addresses an unresponsive probe button caused by connection, contamination, control lock, workflow, cable, probe, or software conditions.
Step-by-Step Troubleshooting
1. Protect the Patient and Maintain Assessment Capability
Do not continue using an unreliable scan control during a patient examination. Use another verified scanner or an approved alternate scan control only if it is designed for clinical use.
Remove the probe from use if the button is physically damaged, sticking, cracked, or contaminated internally.
Expected outcome: Patient care continues without depending on an unreliable control.
2. Confirm the Button Failure
Verify whether the button:
- Does not move
- Moves but gives no response
- Works intermittently
- Requires unusual pressure
- Fails only at certain screens
- Fails when the cable is moved
Observe whether another approved scan control can start acquisition.
Expected outcome: The failure is confirmed as mechanical, intermittent, workflow-related, or isolated to the probe control.
3. Verify the Device Is Scan Ready
Confirm that the scanner is powered, logged in if required, on the correct patient or exam screen, and not displaying a prompt that must be completed.
Verify that scanning is not disabled by an active menu, dialog, access restriction, or incomplete patient entry.
Expected outcome: The scanner is in a state where the probe button should initiate a scan.
4. Inspect the Button Externally
Inspect around the button for dried gel, cleaning residue, adhesive, a torn membrane, impact damage, or material preventing normal travel.
Clean only by the approved external method. Do not pry, remove the button cover, or introduce fluid into the probe.
Expected outcome: The button moves freely and is externally clean. If cleaning restores response, proceed to final testing.
5. Inspect the Probe Cable and Connector
Check the cable, strain relief, connector, and accessible contacts for cuts, kinks, crushed areas, looseness, contamination, or movement-related intermittency.
Reseat the probe connection without forcing it. Route the cable so it is not under tension.
Expected outcome: The probe is securely connected and the button response is stable.
6. Compare With an Alternate Approved Scan Control
Use the scanner’s alternate approved scan-start control, when available. If the alternate control initiates and completes scans, the core scanner and acquisition path are likely operational.
Do not use unauthorized keyboard commands or service functions.
Expected outcome: Successful scanning from the alternate control isolates the issue to the probe button, cable, or probe assembly.
7. Compare With a Known-Good Probe
When the probe is detachable and an approved compatible probe is available, connect the known-good probe and test its scan button.
Keep the original probe clearly identified to prevent accidental clinical reuse.
Expected outcome: A working known-good probe confirms that the original probe assembly requires service. If neither button works, evaluate scanner software or interface conditions.
8. Restart the Scanner
Exit the patient workflow, shut down normally, restart the scanner, and return to the scan-ready screen. Do not enter restricted service menus or alter protected configuration.
Expected outcome: The button is recognized after restart. If the failure returns, the device or probe must be removed from service.
9. Perform Final Functional Verification
Initiate and complete multiple scans using the probe button. Confirm normal button travel, immediate command recognition, complete acquisition, and no response interruption when the cable is gently repositioned.
Expected outcome: The probe button operates reliably through repeated tests. Troubleshooting can stop and the device may return to service.
If the Problem Persists
External causes involving workflow state, contamination, cable routing, connector seating, alternate controls, and restart have been ruled out.
The remaining cause may involve the probe button mechanism, probe cable conductors, connector interface, scanner input circuitry, or software. Do not open the probe or attempt internal switch repair unless specifically authorized by approved service documentation and training.
The affected equipment 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
After repair, verify repeated button operation, scan completion, probe integrity, cleaning integrity, and all required return-to-service checks.
Knowing when to stop external troubleshooting is proper troubleshooting.
Clinical Use Tip
A button that works only intermittently is not reliable enough for patient assessment and should not remain in clinical use.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Clinical staff reported that pressing the probe scan button did not start bladder scan acquisition."
Cause
What was observed during troubleshooting.
Example:
"Clinical Engineering found dried ultrasound gel restricting normal movement of the probe button."
Resolution
What action was taken.
Example:
"Clinical Engineering cleaned the probe exterior using the approved method, verified normal button travel, and completed repeated successful test scans."
Helpful Details to Include (If Known)
- Whether the button moved normally
- Intermittent or complete failure
- Screen or workflow state
- Probe connector condition
- Cable movement effect
- Alternate scan control result
- Known-good probe result
- Cleaning performed
- Number of successful tests
- Final probe and device status
Final Thought
Keep the patient off unreliable equipment, confirm that the scanner is scan ready, inspect the button and cable externally, compare alternate controls, and verify repeated successful operation. Escalate probe or scanner faults without attempting unauthorized internal repair and document the consistent CCR event.
That is successful troubleshooting.