On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshoots missing cycle documentation, printer problems, or export failures caused by supplies, connections, destination availability, configuration, or communication issues.
Step-by-Step Troubleshooting
1. Protect Documentation Integrity and Confirm the Failure
Determine whether:
- The printer produces no output
- Print is blank or incomplete
- The cycle record is missing
- Stored cycle data cannot be retrieved
- Export to an external system fails
Do not recreate or alter processing records in a way that could misrepresent cycle completion.
Expected outcome: The documentation failure is clearly identified while preserving record integrity.
2. Verify the Cycle Completed Normally
Confirm the underlying washer cycle completed successfully and the issue is limited to documentation or data transfer.
Expected outcome: The washer's processing function is separated from the record-output problem. If the cycle itself failed, troubleshoot the cycle failure instead.
3. Check Printer Supplies and Physical Condition
For an attached printer, inspect:
- Paper supply
- Paper loading
- Cover closure
- Visible jams
- External damage
- Printer power or indicators
Use only the approved consumable type.
Expected outcome: Printer supplies and physical setup are correct. If replacing or properly loading consumables restores printing, verify a test record and stop.
4. Inspect External Cables and Connections
Check accessible printer, network, serial, USB, or other applicable external data connections for:
- Loose plugs
- Damaged connectors
- Disconnected cables
- Strain or pinching
Expected outcome: External communication connections are secure and undamaged.
5. Verify the Intended Output Destination
Confirm the printer, export destination, or connected documentation system is available and not offline.
For networked systems, coordinate with IT when the destination server, network port, interface, or application may be unavailable.
Expected outcome: The external destination is reachable and available. If restoring an external system corrects the failure, verify successful transfer and stop.
6. Confirm Authorized Configuration
Verify visible user-accessible output settings are appropriate. Do not alter protected configuration, network parameters, or service settings without authorization.
Expected outcome: Approved output configuration appears correct.
7. Test With a New Completed Cycle
Run an approved test cycle if required and confirm a new cycle record is generated, printed, stored, or exported successfully.
Expected outcome: Complete documentation is produced and associated with the correct test cycle. Troubleshooting can stop.
8. Verify Historical Data Carefully
If historical cycle records are involved, avoid deleting, overwriting, or modifying existing records during troubleshooting.
Expected outcome: Existing records remain preserved while current functionality is tested.
9. Escalate Persistent Documentation Failures
If supplies, external connections, destination availability, and authorized settings are correct but records remain unavailable, stop external troubleshooting.
Expected outcome: The documentation subsystem is referred for qualified service or IT evaluation.
If the Problem Persists
The remaining issue may involve internal printer hardware, data storage, software, network configuration, interface services, communication hardware, or another service-level problem.
The washer should be evaluated based on the facility's documentation requirements. When the missing record prevents compliant processing documentation, the washer should be:
- Removed from service
- Labeled Out of Service
- Sent for repair or service evaluation
- Evaluated using appropriate STERIS documentation and approved test equipment
- Repaired or configured only by qualified personnel
After repair, verify that complete cycle records are correctly produced, stored, and transferred as required. Knowing when to stop external troubleshooting is proper troubleshooting.
Clinical Use Tip
Do not assume a successfully completed wash cycle automatically satisfies facility documentation requirements when the required cycle record is missing.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Sterile Processing reported the Reliance 444 completed cycles but no printed cycle record was produced."
Cause
What was observed during troubleshooting.
Example:
"Clinical Engineering found the printer paper roll empty with no additional printer fault present."
Resolution
What action was taken.
Example:
"Approved printer paper was installed, and a subsequent test cycle produced a complete and legible cycle record."
Helpful Details to Include (If Known)
- Whether print, storage, or export failed
- Cycle completion status
- Paper or consumable condition
- Printer indicators
- Cable condition
- Destination system status
- Network or interface involvement
- Exact error or message
- Test record result
- Final device status
Final Thought
Separate the washing process from its documentation path, then check supplies, cables, destinations, and authorized settings before escalating software or internal communication concerns. Preserve records and verify a complete cycle record before closing the work order.
That is successful troubleshooting.