On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Use this guide when cycle documentation, printed records, data transfer, or an instrument-tracking interface is missing, incomplete, or unavailable.
Step-by-Step Troubleshooting
1. Protect Documentation and Processing Traceability
Determine whether department policy permits processing when electronic or printed cycle documentation is unavailable.
If traceability cannot be maintained by an approved alternate method, stop affected processing until documentation is restored.
Expected outcome: Required cycle records and instrument traceability are preserved.
2. Confirm What Function Failed
Determine whether the issue affects printing, electronic record storage, network transfer, barcode or tracking integration, or all documentation functions.
Confirm whether the cleaner itself still completes cycles normally.
Expected outcome: A documentation problem is separated from a cleaning-process problem.
3. Check Printer Supplies and Physical Condition
If a printer is involved, verify that paper or other normal consumables are present and correctly installed.
Inspect accessible covers, feed paths, and connectors for obvious obstruction or damage.
Expected outcome: The printer has required consumables and no simple mechanical obstruction.
4. Verify External Data Connections
Inspect accessible Ethernet, USB, serial, or other communication cables associated with the tracking interface.
Check for loose connectors, damaged latches, pinched cables, or recent equipment movement.
Expected outcome: Required data cables are securely connected and physically intact.
5. Check Link and Status Indicators
Observe any normal network or peripheral status indicators available without entering restricted settings.
A missing link indication may suggest a cable, wall jack, switch-port, or network problem.
Expected outcome: Expected communication indicators are present or the failure is narrowed to the infrastructure path.
6. Confirm Correct User-Accessible Configuration
Verify the intended destination, printer selection, or tracking workflow using only normal user-accessible settings.
Do not change IP addressing, protected interface mappings, or service-level configuration without authorization.
Expected outcome: The correct destination or workflow is selected.
7. Test the Peripheral Independently When Practical
Where possible, verify the printer, cable, wall port, scanner, or tracking workstation using a known-good comparison without altering the cleaner's protected configuration.
Expected outcome: The failure is isolated to the external peripheral, infrastructure, or cleaner interface.
8. Perform a Controlled Restart
If processing is not active, restart the cleaner and any external interface device through normal shutdown procedures.
Do not repeatedly cycle power during active data transfer.
Expected outcome: Communication and cycle-record functions recover. If they do, verify a new test record and stop troubleshooting.
9. Verify Record Creation
Run an appropriate test or review a newly completed cycle to verify that the cycle record is stored, printed, or transferred as intended.
Expected outcome: A complete record is produced and available at the intended destination.
10. Escalate Persistent Interface Failure
If the external cables, peripherals, and basic configuration are correct but the interface remains unavailable, escalate to the appropriate Clinical Engineering, IT, tracking-system, or manufacturer support team.
Expected outcome: The cleaner remains appropriately restricted if required documentation cannot be maintained.
If the Problem Persists
Printer supplies, cables, external peripherals, accessible configuration, and basic infrastructure have been checked. Remaining causes may involve the cleaner's communication hardware, software, internal storage, network configuration, interface engine, tracking-system configuration, or facility IT infrastructure.
The device should be:
- Removed from service when required documentation cannot otherwise be maintained
- Labeled Out of Service when continued use is not permitted
- Sent for repair or bench evaluation when the cleaner itself is suspected
- Evaluated using appropriate manufacturer documentation and approved test equipment
- Configured or repaired only by qualified personnel
Verify successful creation and transfer of a new cycle record before restoring normal documentation workflow.
Knowing when to stop external troubleshooting is proper troubleshooting.
Clinical Use Tip
A successful cleaning cycle and a successful tracking record are separate requirements; preserve approved manual documentation if the electronic interface fails.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Sterile Processing reported that completed CaviWave Pro cycles were no longer appearing in the instrument-tracking system."
Cause
What was observed during troubleshooting.
Example:
"Clinical Engineering found the external network cable disconnected from the cleaner after the unit had been moved."
Resolution
What action was taken.
Example:
"Reconnected the network cable, verified communication and successful transfer of a new cycle record, and returned the system to normal use."
Helpful Details to Include (If Known)
- Printer versus electronic-record failure
- Whether cycles otherwise complete normally
- Printer supply condition
- Cable type and condition
- Link or status indicators
- Wall jack or network port tested
- Tracking workstation status
- Recent equipment movement or network work
- Test-record result
- Final device status
Final Thought
Treat documentation failures methodically by separating the cleaner, peripheral, cable, network, and tracking-system portions of the path. Restore traceability before normal use when required, and document exactly where communication was restored.
That is successful troubleshooting.