Medline BioCon 1100

Asset Type

Bladder Scanner

Manufacturer

Medline

Model

BioCon 1100

What This Guide Helps With

Troubleshooting failed data export, HL7 transmission, Wi-Fi transfer, or missing patient records caused by connectivity, configuration, destination, or network issues.

Step-by-Step Troubleshooting

1. Ensure Patient Safety First

Do not perform extended network or data-export troubleshooting while the BioCon 1100 is required for active patient assessment.

Complete the clinically necessary scan, preserve required results according to facility policy, and move troubleshooting to a controlled Clinical Engineering environment when possible.

Expected: Patient care is not delayed or dependent on unresolved data connectivity.

Why it matters: A data-export failure should not prevent clinicians from obtaining an alternate documented result or using another verified scanner when necessary.

If the immediate clinical concern is resolved, continue troubleshooting off-patient.

2. Confirm the Exact Failure Mode

Determine what “network/data export failure” means operationally.

Check whether the BioCon 1100:

• Cannot initiate a transfer
• Shows no available wireless connection
• Connects but does not transmit
• Fails only with HL7 output
• Transfers some records but not others
• Cannot reach the configured destination
• Appears to send data but no result arrives downstream
• Fails after a network, server, interface, or configuration change
• Displays a specific communication or export message

Document the exact screen behavior and any message shown.

Expected: The failure is narrowed to device connectivity, export initiation, or downstream receipt.

If the reported function now works normally, document the successful test and stop.

3. Verify the Device Is Otherwise Operating Normally

Confirm that the BioCon 1100:

• Powers on normally
• Completes startup without an unresolved fault
• Accepts normal user input
• Can perform or access a test record as appropriate
• Stores or displays expected record information
• Shows no unrelated system instability

Expected: The problem is isolated to communication or data export rather than a broader device failure.

If the unit freezes, reboots, loses records, or shows additional system faults, remove it from service and escalate for bench evaluation.

4. Check the Selected Export Method

Verify that the workflow being tested matches the facility’s actual implementation.

Determine whether the site uses:

• HL7 output
• Wi-Fi Direct transfer
• Another approved configured export workflow

Do not assume a general “network problem” when only one transfer method is failing.

Expected: Clinical Engineering identifies the exact interface path involved.

If the correct transfer method is selected and export succeeds, document the configuration finding and stop.

5. Check Visible Network or Wireless Status

Review the device interface for available connection indications.

Check for:

• Wireless connection status
• Unexpected disconnected state
• Missing expected destination
• Weak or unstable connectivity
• Communication warning
• Evidence that the device is connected to the wrong network or endpoint

Move the scanner to a location with known-good approved connectivity if appropriate.

Expected: The expected communication path is visibly available and stable.

If restoring the expected connection resolves export, verify with a controlled test and stop.

6. Rule Out a Location-Specific Network Problem

Test from a known-good area where the BioCon 1100 is expected to communicate.

Compare:

• Reported failure location
• Known-good coverage location
• Nearby functioning devices using the same approved infrastructure, when applicable

Do not alter hospital network settings simply to force connectivity.

Expected: Clinical Engineering determines whether the failure follows the scanner or remains tied to a specific location.

If export works in a known-good location, document the location dependency and escalate the infrastructure concern to the appropriate network team. Stop device troubleshooting.

7. Verify Date, Time, and Record Identification

Check that device date and time are reasonable and that the test record contains the expected identification information required by the facility workflow.

Look for:

• Incorrect date or time
• Incomplete patient identifiers
• Incorrectly selected record
• Missing required workflow information
• Duplicate or obviously invalid test data

Expected: The record being exported contains valid information suitable for the configured workflow.

If correcting permitted record or workflow information resolves the issue, verify successful receipt and stop.

8. Inspect External Accessories Used in the Workflow

If the local implementation uses any external approved accessory for identification or transfer, inspect it for:

• Loose connection
• Physical damage
• Contaminated connector
• Intermittent operation
• Failure isolated to one accessory

For example, if barcode-based identification is part of the workflow, confirm that the identification step completes correctly before assuming export failure.

Expected: External accessories are ruled out as the cause.

If a known-good approved accessory resolves the issue, replace the defective accessory, verify operation, and stop.

9. Compare With a Known-Good Device or Destination

When available, perform a controlled comparison.

Determine whether:

• Another BioCon 1100 can export through the same workflow
• The affected unit can export to an approved known-good destination
• The failure follows the scanner
• The failure remains with the network, interface, server, or destination

Expected: The problem boundary is narrowed without internal disassembly.

If multiple devices fail through the same destination, stop troubleshooting the individual scanner and escalate the shared infrastructure or interface issue.

10. Verify Approved Configuration Against Site Records

Using authorized Clinical Engineering, IT, or integration documentation, compare the affected scanner with the known-good site configuration.

Check only settings within your approved access level, such as applicable:

• Enabled export method
• Approved wireless configuration
• Destination information
• Interface configuration
• Facility-specific communication parameters

Do not guess values, copy settings blindly between devices, disable security controls, or make undocumented network changes.

Expected: The device configuration matches the approved production configuration.

If an authorized correction restores communication, complete a controlled export test, confirm downstream receipt, document the change, and stop.

11. Coordinate With IT or Interface Support

If the BioCon 1100 appears connected but data still does not arrive, involve the appropriate support team.

Ask them to verify, as applicable:

• Device communication is reaching the network
• The expected destination is available
• Required interface services are running
• HL7 messages are being received or rejected
• Recent network or interface changes occurred
• The destination is rejecting records because of configuration or formatting conditions

Provide:

• Device identity
• Asset number
• MAC or network identifier when authorized
• Exact failure time
• Test record time
• Error message
• Location
• Expected destination

Expected: The team determines whether the failure is on the device side or downstream.

If the downstream service or interface is corrected and export succeeds, verify receipt and stop.

12. Perform a Controlled Final Functional Test

After any correction, perform an approved end-to-end test.

Verify that:

• The device operates normally.
• A test record can be selected or generated according to facility procedure.
• Export initiates normally.
• No communication error appears.
• The record reaches the intended destination.
• The received record corresponds to the transmitted test.

Do not return the device to unrestricted clinical use based only on a connection icon.

Expected: End-to-end data transfer is confirmed.

If the complete workflow passes, return the device to service according to facility policy and document the result.

If the Problem Persists

If power, normal device operation, transfer method, visible connectivity, location, accessories, record information, approved configuration, destination availability, and downstream infrastructure have been checked, common external causes have been ruled out.

The fault may involve internal communication hardware, operating-system behavior, corrupted configuration, or another device-level condition requiring authorized evaluation.

The device should be:

• Removed from service
• Labeled Out of Service
• Sent for repair or controlled bench evaluation

Do not proceed into unsupported internal disassembly or undocumented software changes.

Knowing when to stop after external and infrastructure causes have been reasonably isolated is proper troubleshooting.

Clinical Use Tip

Do not let a network or data-export problem delay patient care. Obtain the bladder assessment safely, preserve required documentation through an approved alternate workflow, and troubleshoot connectivity off-patient whenever possible.

Work Order Documentation (CCR Method)

CCR = Complaint, Cause, Resolution

Complaint

What was reported by the clinical staff.

Example:
"Clinical staff reported that the Medline BioCon 1100 completed bladder scans but patient results were not transmitting to the configured destination."

Cause

What was observed during troubleshooting.

Example:
"BioCon 1100 operated normally, but testing showed the data-export failure was isolated to the configured communication path and persisted after basic connectivity checks."

Resolution

What action was taken.

Example:
"Verified device operation and external connections, reproduced the export failure, documented network behavior, removed the unit from service, and escalated for interface support and bench evaluation."

Helpful Details to Include (If Known)

• Exact export failure reproduced
• Exact message or screen behavior documented
• Device startup normal
• Local record available
• Export method identified
• Wireless status checked
• Known-good location tested
• Approved accessories checked
• Date and time verified
• Patient or test record identification checked
• Known-good device comparison performed
• Approved configuration reviewed
• IT/network team contacted
• Interface or destination status checked
• End-to-end receipt confirmed
• Final device status documented

Final Thought

Network and data-export failures require disciplined isolation between the scanner, wireless path, configuration, interface, and destination. Protect patient care first, verify external causes logically, escalate appropriately, and document exactly where the workflow failed or succeeded.

That is successful troubleshooting.