Medline BioCon 1100

Touchscreen Unresponsive / Software Freeze

On this page

Asset Type

Bladder Scanner

Manufacturer

Medline

Model

BioCon 1100

What This Guide Helps With

Troubleshooting a frozen, delayed, or unresponsive touchscreen caused by contamination, power instability, software lockup, connected accessories, or persistent console failure.

Step-by-Step Troubleshooting

1. Ensure Patient Safety First

Do not troubleshoot an unresponsive BioCon 1100 while it is being relied upon for an active patient assessment.

If bladder-volume information is clinically time-sensitive, provide another verified bladder scanner or appropriate alternate assessment method before continuing.

Expected: Patient care is not delayed by an unreliable scanner.

Why it matters: A frozen interface can prevent reliable patient selection, scanning, review, or documentation of bladder-volume measurements.

If patient care has been transferred appropriately, continue troubleshooting in a controlled Clinical Engineering setting.

2. Confirm the Exact Failure Behavior

Power on the BioCon 1100 and determine whether the problem is:

Document any displayed message, abnormal indicator, or repeatable trigger.

Expected: The failure is clearly defined and can be distinguished from a blank display, startup failure, or isolated touch-area defect.

If the unit operates normally and the complaint cannot be reproduced, continue through inspection and functional verification before return to service.

3. Inspect the Touchscreen Surface

Examine the display for:

Clean the touchscreen only with an approved method compatible with the device and facility policy. Allow the surface to dry fully before retesting.

Do not flood the display edges with liquid.

Expected: The screen is clean, dry, intact, and responds normally.

If cleaning resolves the issue, verify repeated touch operation and stop troubleshooting.

4. Rule Out Gloves or Touch-Input Conditions

Test the touchscreen under controlled conditions using normal approved interaction.

Determine whether the complaint occurs:

Expected: Touch response is consistent across normal operating conditions.

If the problem is limited to contamination or an external interaction condition, correct the condition, verify operation, and stop troubleshooting.

5. Check for a Localized Touchscreen Failure

With the unit safely removed from patient use, test multiple selectable areas of the interface.

Look for:

Do not repeatedly enter or change clinical settings solely for testing.

Expected: Touch input is recognized consistently across the usable interface.

If the same region repeatedly fails while other regions respond normally, suspect a touchscreen or console hardware problem and proceed toward escalation.

6. Check External Power Condition

Inspect the external power path for:

Test the receptacle using your facility-approved method when external power is suspect.

Do not use a visibly damaged power adapter or cord.

Expected: External power remains stable with no intermittent connection or abnormal physical condition.

If restoring a secure power connection resolves the freeze, verify repeated operation and stop troubleshooting.

7. Compare External-Power and Battery Operation

After confirming adequate charge status, determine whether the freeze occurs:

Avoid prolonged testing on a depleted or questionable battery.

Expected: The touchscreen and software remain stable under available normal power modes.

Why it matters: A repeatable difference between power modes can help separate general software instability from a power-related condition.

If the issue follows one power condition, document the pattern and evaluate the associated external power or battery complaint separately.

8. Check Connected External Accessories

If accessories are attached, inspect externally accessible connections and determine whether the freeze correlates with a particular accessory or connection.

Examples may include configured peripheral or data-entry accessories used with the system.

Look for:

When clinically safe and consistent with approved configuration, retest without a suspect nonessential external accessory.

Expected: The console remains responsive without an externally induced connection problem.

If removing a suspect accessory eliminates the freeze, verify the accessory separately and stop using the suspect component until evaluated.

9. Perform a Controlled Restart

If the interface remains frozen and normal shutdown is available, perform a normal shutdown and restart.

If normal shutdown cannot be completed because the interface is locked, follow the approved operator or service procedure for powering down the unit. Do not improvise an undocumented reset sequence.

After shutdown:

Expected: The unit boots normally and the touchscreen responds consistently.

If the restart resolves the issue, continue testing before return to service because a recurring software freeze still requires evaluation.

10. Observe Startup and Self-Diagnostic Behavior

During restart, watch for:

Record exact wording and behavior rather than documenting only “software issue.”

Expected: Startup completes without abnormal alerts and the unit reaches a responsive operating screen.

If a hardware, maintenance, or persistent system indication appears, stop routine troubleshooting and escalate for service evaluation.

11. Test for a Repeatable Trigger

If the unit initially works after restart, determine whether the freeze returns during a specific normal workflow, such as:

Do not create unnecessary patient records or alter protected configuration solely to stress-test the unit.

Expected: Normal operating workflows can be repeated without freezing.

If one action consistently triggers the failure, document the exact sequence and escalate with that reproducible information.

12. Verify Basic Functional Stability

Before considering return to service, perform a controlled functional check appropriate to Clinical Engineering practice and facility procedure.

Verify:

Use an approved test method, phantom, or facility verification process where required.

Expected: The device remains stable and responsive through repeated functional checks.

If the freeze returns at any point, remove the unit from service and escalate.

If the Problem Persists

If the BioCon 1100 remains frozen, develops recurring software lockups, has persistent touchscreen dead zones, repeatedly reboots, or displays unresolved hardware or maintenance indications after external causes are ruled out, the problem is likely internal to the console, touchscreen interface, software environment, power subsystem, or related electronics.

The device should be:

Do not proceed into unapproved internal disassembly, touchscreen replacement, board-level repair, or undocumented software modification.

Knowing when to stop is proper troubleshooting. A bladder scanner that intermittently freezes cannot be considered reliable simply because one restart temporarily restores operation.

Clinical Use Tip

Do not troubleshoot an intermittent touchscreen or software freeze while the scanner is being relied upon for patient assessment. Move care to another verified device first, then reproduce the issue under controlled conditions.

Work Order Documentation (CCR Method)

CCR = Complaint, Cause, Resolution

Complaint

What was reported by the clinical staff.

Example:
"Clinical staff reported the BioCon 1100 touchscreen became unresponsive during operation and the displayed interface would no longer accept selections."

Cause

What was observed during troubleshooting.

Example:
"Found the console repeatedly froze during normal touchscreen navigation despite a clean display, stable power, and removal of suspect external accessory connections."

Resolution

What action was taken.

Example:
"Removed the BioCon 1100 from service, labeled it Out of Service, documented the repeatable freeze sequence, and routed the unit for bench evaluation and repair."

Helpful Details to Include (If Known)

Final Thought

Start with patient safety, define whether the problem is touch input or a full software freeze, then rule out contamination, power, and external connections before escalation. Recurring lockups require appropriate removal from service and clear CCR documentation rather than repeated temporary resets.

That is successful troubleshooting.

Related Guides

Was this guide helpful?

Don't see a guide you need?

Suggest a Guide