On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshooting PadScan HD printing, export, saved scan, storage, or report transfer issues caused by setup, media, cables, or workflow.
Step-by-Step Troubleshooting
Ensure Patient Safety First
Do not troubleshoot printing, export, or data storage while delaying patient care.
Action:
- Confirm the bladder scan result has been reviewed or documented by clinical staff before clearing, exporting, or restarting the device.
- If the scanner is needed for active patient care, provide another bladder scanner if available.
- Do not delete stored patient records unless approved by site policy.
Expected outcome: Patient care and scan documentation are protected before troubleshooting begins.
Why it matters: Printer or export issues are usually not life-threatening, but lost scan records can create documentation and care continuity problems.
Verify the Reported Issue
Confirm exactly what function is failing.
Action:
- Check whether the issue involves:
- Internal or external printer not printing
- Blank or incomplete printout
- Export to USB not working
- Saved scans not appearing
- Storage full message
- Report cannot be transferred
- Patient data not saving
- Date/time or patient information missing from reports
Expected outcome: The failure mode is clearly identified before parts or settings are blamed.
If the issue is only a workflow misunderstanding and the scanner prints, saves, or exports normally after proper steps are followed, document the correction and stop.
Check Device Power and Startup Status
Confirm the PadScan HD scanner is fully powered and operating normally.
Action:
- Verify the scanner powers on without startup errors.
- Confirm the battery is adequately charged or connect the scanner to approved power if applicable.
- Restart the unit if the display or menu is frozen.
- Check whether the scanner responds normally to touchscreen or button inputs.
Expected outcome: The scanner is stable enough to access stored data, print menus, and export functions.
If a restart restores normal printer, export, or storage function, document the restart and successful test, then stop.
Confirm the Scan Was Actually Saved
Verify that the missing report or export file exists on the scanner.
Action:
- Review the stored records, history, or patient list on the device.
- Confirm the scan was completed and saved before the user attempted to print or export.
- Check whether the user exited the exam before saving the result.
- Confirm the correct patient, date, or exam record is being selected.
Expected outcome: The record is either found in storage or confirmed not to have been saved.
If the scan was not saved, this is a workflow/documentation issue rather than a hardware failure. Notify the department and document the finding.
Check Available Storage
Look for signs that the scanner memory is full or near capacity.
Action:
- Check for storage full, memory full, database full, or save failure messages.
- Review whether older records are preventing new scans from saving.
- Follow facility policy before deleting or archiving patient records.
- If records need to be removed, confirm clinical documentation retention requirements first.
Expected outcome: The scanner has enough available memory to save new scan records.
If clearing approved old records restores saving function, perform a test scan/save if appropriate, document the result, and stop.
Verify Printer Paper or Label Media
If the printer is not printing or prints blank, check the simple media issues first.
Action:
- Confirm printer paper is installed.
- Confirm the paper roll is loaded in the correct direction if thermal paper is used.
- Check for jammed, torn, or incorrectly seated paper.
- Confirm the printer cover is fully closed.
- Inspect for debris around the paper path without disassembling the printer.
Expected outcome: The printer has correct media installed and feeds normally.
If reloading the paper restores printing, print a test record, document the correction, and stop.
Check Printer Connection and Power
If the PadScan HD uses an external printer, verify the printer is connected and powered.
Action:
- Confirm the printer power cord or battery is connected.
- Check the printer power indicator.
- Reseat the printer cable or USB connection.
- Try a known-good cable if available.
- Confirm the printer is connected to the correct port.
- Verify the printer is not offline, paused, or showing an error light.
Expected outcome: The printer is powered, connected, and ready to receive print jobs.
If a loose cable or offline printer caused the issue, correct it, print a test report, document the result, and stop.
Check Printer Selection or Output Setting
Confirm the scanner is set to the correct print or output method.
Action:
- Review the printer/export settings available to Clinical Engineering.
- Confirm the selected printer or report format matches the connected printer or export method.
- Check whether the device is set to print automatically or only after manual selection.
- Confirm the correct report type is selected.
Expected outcome: The scanner is sending the report to the intended output path.
If correcting the output setting restores printing or exporting, document the setting change and stop.
Test Printing With a Known Stored Record
Use a non-active or approved test record if available.
Action:
- Select a stored record that is safe to print under facility policy.
- Attempt to print the report.
- Observe whether the scanner displays an error, sends the job, freezes, or does nothing.
- Note whether paper feeds, partially prints, or remains idle.
Expected outcome: The printer behavior confirms whether the problem is scanner-side, printer-side, or media-related.
If a test print succeeds, the reported issue may have been record-specific, workflow-related, or intermittent.
Check USB Export Media
If export to USB is failing, inspect the USB device first.
Action:
- Confirm the USB drive is fully inserted.
- Try a known-good USB drive approved by the facility.
- Avoid using encrypted, damaged, unsupported, or very large USB drives unless the device supports them.
- Check whether the USB drive is full or write-protected.
- Confirm the scanner recognizes the USB device before exporting.
Expected outcome: The scanner detects usable USB media and can attempt export.
If changing to a known-good USB drive restores export, document the failed media and successful export test, then stop.
Check File Format and Destination
Confirm the user is expecting the correct export output.
Action:
- Verify whether the scanner exports reports as images, PDFs, data files, or another supported format.
- Confirm the exported file is being checked on the correct USB folder or destination.
- Check whether the export completed but the user looked in the wrong location.
- Confirm the report contains the expected patient or exam information.
Expected outcome: The export function and file location are understood.
If the file exported successfully but was misidentified or saved in a different folder, document the workflow correction and stop.
Check Date, Time, and Patient Information
Incorrect date/time or patient identifiers can make stored records appear missing.
Action:
- Verify the scanner date and time are correct.
- Confirm patient information was entered or selected properly before the scan was saved.
- Check whether the record is filed under a different patient ID, generic patient entry, or incorrect date.
- Correct date/time settings only if permitted by facility procedure.
Expected outcome: Records can be located and exported using accurate identifying information.
If records were saved under incorrect information, notify the department and document the finding.
Check Network or Computer Export Path if Used
If the PadScan HD is configured for network, PC, or database transfer, verify the external connection.
Action:
- Confirm the network cable or Wi-Fi connection is active, if applicable.
- Check whether other devices on the same network are functioning.
- Verify the destination computer, shared folder, or receiving software is powered on and available.
- Confirm no recent IT changes affected IP address, permissions, firewall rules, or shared folder access.
- Escalate to IT if the scanner appears functional but the network destination is unavailable.
Expected outcome: The scanner has a valid path to the intended export or storage destination.
If restoring the network or destination system resolves the issue, document the external cause and stop.
Review Error Messages or Indicator Lights
Record any specific messages before resetting or escalating.
Action:
- Document any displayed messages such as:
- Printer error
- Paper empty
- Storage full
- Export failed
- USB not detected
- Save failed
- Transfer failed
- Database error
Expected outcome: The work order includes useful details for repair, vendor support, or IT escalation.
Perform a Controlled Restart and Retest
If no obvious external cause is found, restart the scanner and retest the affected function.
Action:
- Power down the scanner normally.
- Wait briefly before restarting.
- Confirm the scanner boots without errors.
- Attempt one controlled test of the affected function: print, save, export, or transfer.
- Do not repeatedly power cycle if the device freezes, loses data, or shows storage/database errors.
Expected outcome: Temporary software or communication faults clear after restart.
If the issue resolves after restart and retest passes, document the restart and final status.
If the Problem Persists
If the PadScan HD still cannot print, export, save, or store records after power, media, cables, settings, storage, USB devices, and external connections have been checked, the likely cause may be internal printer hardware, storage/database corruption, software failure, communication board failure, or configuration fault.
The device should be:
- Removed from service if scan documentation cannot be reliably saved or retrieved
- Labeled Out of Service
- Sent for bench evaluation, IT review, or vendor repair depending on the failure type
Knowing when to stop is proper troubleshooting. Do not perform deep internal disassembly, board-level repair, or unauthorized database manipulation during normal Clinical Engineering response.
Clinical Use Tip
Do not troubleshoot data storage or export problems by deleting records from an active clinical device without confirming documentation requirements. If the scanner is needed for patient care, move staff to another available bladder scanner first, then troubleshoot the affected unit safely.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Clinical staff reported that the Caresono PadScan HD would not export saved bladder scan reports to USB."
Cause
What was observed during troubleshooting.
Example:
"Troubleshooting found the scanner recognized a known-good USB drive, but the original USB drive was not detected and appeared to be the cause of the export failure."
Resolution
What action was taken.
Example:
"Replaced the USB drive with approved known-good media, successfully exported a stored test report, and returned the scanner to service."
Helpful Details to Include (If Known)
- Whether the issue involved printing, USB export, network transfer, or saved records
- Exact error message displayed
- Whether printer paper was checked or replaced
- Whether printer cover was open or paper was jammed
- Whether an external printer was powered and connected
- Whether a known-good USB drive was tested
- Whether storage full or database errors were present
- Whether date/time and patient record lookup were verified
- Whether network or destination computer issues were suspected
- Whether the scanner restarted normally
- Final device status: returned to service, sent to IT, or removed for repair
Final Thought
PadScan HD printer, export, and storage issues should be approached logically: protect patient documentation first, check the simple external causes, verify media and connection paths, then escalate when data reliability cannot be confirmed. Good CCR documentation helps separate user workflow, IT, accessory, and device repair issues.
That is successful troubleshooting.