On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshooting failed bladder auto-detection caused by positioning, battery, probe contact, patient factors, setup, or device condition.
Step-by-Step Troubleshooting
Ensure Patient Safety First
Confirm the scanner is not being used in a situation where an inaccurate bladder volume could delay necessary clinical care.
If the patient’s condition requires urgent assessment, advise clinical staff to use an alternate verified bladder scanner or follow facility policy for further evaluation.
Expected outcome: Patient care is not delayed by troubleshooting.
Confirm the Reported Detection Problem
Ask clinical staff what they observed during scanning.
Common reports may include:
- Bladder not automatically detected
- Scanner unable to center or locate bladder
- Repeated low or inconsistent volume readings
- Scan completes but displays poor confidence or questionable results
- Device requires repeated rescans to produce a usable result
Expected outcome: The exact failure mode is understood before troubleshooting begins.
Check Battery Status and Power Condition
Verify the BBS Revolution has adequate battery charge and powers on normally.
Low battery or unstable power can affect scan completion, display response, and system performance.
Expected outcome: Device powers on normally and has enough charge to complete multiple scans.
If charging or power is the issue, place the unit on the correct charger or remove it from service if it will not charge properly.
Inspect the Probe and Scanner Housing
Examine the probe, cable, connector area, display, and scanner body for visible damage.
Look for:
- Cracked probe face
- Damaged cable jacket
- Loose or strained connector
- Fluid intrusion
- Impact damage
- Damaged screen or controls
Expected outcome: No physical damage is found that would affect scanning.
If damage is found, stop troubleshooting and remove the device from service.
Verify Probe Connection and Seating
Confirm the probe is fully connected and properly seated, if applicable to the configuration.
A loose or intermittent probe connection can cause poor image acquisition or failed automatic bladder detection.
Expected outcome: Probe connection is secure and the scanner recognizes the probe normally.
If reseating the probe restores normal detection, document the loose connection and stop.
Confirm Proper Scan Setup
Review the scanner setup with clinical staff.
Verify the correct patient type or scan mode is selected, if available, and confirm that the device is being used according to facility workflow.
Expected outcome: The scanner is not failing because of an incorrect mode, setup selection, or workflow error.
Check Coupling Gel Use
Confirm adequate ultrasound gel is being applied between the probe and the patient.
Insufficient gel or poor probe contact can prevent the scanner from obtaining a clear image for automatic bladder recognition.
Expected outcome: Gel coverage is adequate and probe contact is consistent.
If proper gel use restores automatic detection, stop and document the correction.
Check Probe Positioning Technique
Have qualified clinical staff confirm probe placement and scan angle.
Automatic bladder detection may fail if the probe is too high, too low, angled away from the bladder, or not centered over the expected bladder location.
Expected outcome: The scanner can identify the bladder when the probe is positioned correctly.
If repositioning resolves the issue, document user technique or positioning as the cause.
Consider Patient-Specific Factors
Confirm whether the issue occurs on one patient only or across multiple patients.
Patient factors that may affect detection include:
- Very low bladder volume
- Obesity or increased tissue depth
- Abdominal dressings
- Scarring
- Pregnancy
- Ascites
- Unusual anatomy
- Difficulty positioning the probe
Expected outcome: The issue is separated from patient-specific scanning limitations.
If the problem occurs only under difficult patient conditions, the device may be functioning normally.
Perform a Controlled Test Scan
Test the scanner using an approved training phantom, test fixture, or another facility-approved verification method if available.
Do not use an active patient for repeated equipment troubleshooting unless clinical staff confirm it is appropriate.
Expected outcome: The scanner detects the target consistently under controlled conditions.
If the scanner works during controlled testing, the problem is likely related to technique, setup, or patient-specific conditions.
Compare With Another Known-Good Scanner
If available, compare results using another verified bladder scanner under the same general conditions.
This helps determine whether the issue follows the device or is related to patient condition or technique.
Expected outcome: The suspect unit either performs similarly to the known-good unit or shows a repeatable failure.
If only the BBS Revolution fails to detect automatically, remove it from service.
Restart the Device
Power the scanner off, wait briefly, and power it back on.
A restart may clear a temporary software or sensor recognition issue.
Expected outcome: The scanner boots normally and automatic detection functions correctly.
If restart resolves the issue, document the reset and monitor for recurrence.
Check for Repeated or Intermittent Failure
Perform several test scans under safe, controlled conditions.
Watch for intermittent detection, freezing, delayed response, probe recognition errors, or inconsistent scan confidence.
Expected outcome: Automatic bladder detection is repeatable and stable.
If detection remains inconsistent, remove the scanner from service for bench evaluation.
If the Problem Persists
If the BBS Revolution still fails automatic bladder detection after battery status, probe condition, gel use, positioning, setup, patient factors, and controlled testing have been checked, common external causes have been ruled out.
The device should be:
- Removed from service
- Labeled Out of Service
- Sent for repair or bench evaluation
The likely issue may involve the probe, image acquisition system, software, internal electronics, or calibration-related performance. Clinical Engineering should stop before deep internal disassembly or unsupported repair attempts. Knowing when to stop is proper troubleshooting.
Clinical Use Tip
Do not troubleshoot repeated bladder detection failures on an active patient when results may affect care decisions. Have clinical staff move the patient to a backup device first by using another verified scanner or follow facility policy before continuing equipment evaluation. Therapy continuity and care decisions should not depend on a scanner with unresolved detection reliability concerns.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Clinical staff reported that the BD BBS Revolution bladder scanner would not automatically detect the bladder during patient scans."
Cause
What was observed during troubleshooting.
Example:
"Troubleshooting found the probe and power were normal, but the device repeatedly failed automatic detection during controlled test scans."
Resolution
What action was taken.
Example:
"Removed the bladder scanner from service, labeled it Out of Service, and sent it for bench evaluation/repair."
Helpful Details to Include (If Known)
- Alarm behavior or detection prompts observed
- Accessories swapped or compared, including charger, dock, or known-good scanner if available
- Power behavior, including battery charge level verified and charger or dock checked
- Environmental factors or patient-specific factors noted
- Indicator lights, display messages, scan confidence, or error messages observed
- Final device status documented
- Probe connection checked
- Probe face inspected
- Cable condition inspected
- Gel use confirmed
- Scan positioning reviewed with staff
- Controlled test scan performed
Final Thought
Automatic bladder detection problems should be approached logically and safely. Rule out power, probe condition, coupling gel, positioning, setup, and patient factors before suspecting internal failure. If the scanner cannot produce reliable detection, remove it from service and document the complaint, cause, and resolution clearly.
That is successful troubleshooting.