On this page
Asset Type
Manufacturer
Advanced Sterilization Products (ASP)
Model
What This Guide Helps With
Troubleshoot network or tracking integration loss caused by cabling, switch connectivity, configuration, infrastructure, or interface-system problems without altering protected settings.
Step-by-Step Troubleshooting
1. Protect Sterile Processing Traceability
Determine whether loss of network or tracking integration affects load release, documentation, or instrument traceability.
Use the facility-approved manual or alternate workflow when necessary.
Expected outcome: Sterilization records and instrument traceability are maintained despite the connectivity outage.
2. Confirm the Scope of the Failure
Determine whether:
- Only one STERRAD 100NX is affected
- Multiple sterile-processing devices are affected
- The sterilizer shows offline status
- The instrument tracking system is unavailable globally
- Cycle data is generated locally but not transmitted
- Connectivity is intermittent
Expected outcome: The issue is narrowed to the sterilizer, local network path, or enterprise application.
3. Verify Local Sterilizer Operation
Confirm the sterilizer itself powers normally, completes cycles, and creates local cycle records.
A network problem should not be assumed to be a sterilizer process failure.
Expected outcome: The sterilization process and local record generation are either confirmed normal or identified as a separate issue.
4. Inspect the Network Cable and Port
Inspect the external Ethernet cable for damage, loose seating, broken latch tabs, sharp bends, or strain.
Verify both ends are connected to the intended ports.
Expected outcome: The physical network connection is secure and undamaged.
If reseating a loose cable restores connectivity and data flow, troubleshooting can stop after verification.
5. Check Link Indicators When Available
Observe normal external network link/activity indications on the device or network connection if visible.
Compare with a known-working nearby device when useful.
Expected outcome: A physical Ethernet link is present.
No link with a known-good cable suggests a port, jack, switch, or device-interface problem requiring further isolation.
6. Test With a Known-Good Network Path When Authorized
If local IT/Clinical Engineering procedures allow, compare the cable, wall jack, or switch path with a known-working connection without changing protected network configuration.
Avoid moving the sterilizer onto an arbitrary network or VLAN.
Expected outcome: The problem is isolated to the device-side connection or facility network infrastructure.
7. Verify Observed Network Configuration
Review, but do not arbitrarily change, approved network settings such as device address information or server destination values if these are accessible within authorized technical scope.
Compare them with documented approved values.
Expected outcome: The observed configuration matches the known approved configuration.
If it does not, escalate before making changes unless Clinical Engineering is specifically authorized to restore the documented configuration.
8. Check the Instrument Tracking System
Determine whether the receiving tracking application, server, interface engine, or related hospital system is operational.
Ask IT or the application owner whether there is an active outage or maintenance event.
Expected outcome: The upstream receiving system is confirmed available or an infrastructure outage is identified.
9. Verify End-to-End Data Flow
After correcting an external network issue, verify that a new test or approved cycle record reaches the intended destination and is associated correctly.
Do not consider link restoration alone sufficient if the clinical requirement is actual data transfer.
Expected outcome: New cycle data successfully traverses the complete path from sterilizer to the intended tracking system.
If verified, troubleshooting can stop.
10. Escalate Persistent Connectivity Failure
If cabling, local link, approved configuration, and receiving-system availability have been checked, escalate to the appropriate ASP, Clinical Engineering, IT networking, cybersecurity, or integration support team.
Expected outcome: The unresolved issue is routed to the team responsible for the failing layer rather than addressed through unauthorized configuration changes.
If the Problem Persists
Common external causes have been ruled out.
Possible remaining categories include:
- Device network-interface failure
- Switch-port or VLAN issue
- Firewall or routing problem
- Addressing or configuration error
- Integration server failure
- Instrument tracking application problem
- Interface or software service fault
The sterilizer should be removed from service if required traceability cannot be maintained through an approved backup workflow. Otherwise, its continued clinical use should follow facility policy while connectivity is repaired.
Any configuration changes should be performed only by authorized personnel using approved documentation.
Verify full end-to-end data transfer after correction.
Knowing whether the problem belongs to Clinical Engineering, IT, the application owner, or ASP is proper troubleshooting.
Clinical Use Tip
A network link light does not prove successful integration; confirm the cycle record actually reaches the intended tracking or documentation system.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Sterile Processing reported that completed STERRAD 100NX cycle records were no longer appearing in the instrument tracking system."
Cause
What was observed during troubleshooting.
Example:
"Clinical Engineering found the sterilizer was functioning normally but the external Ethernet cable was loose and the network link was down."
Resolution
What action was taken.
Example:
"The network cable was reseated, link was restored, and a new verification record successfully transferred to the instrument tracking system."
Helpful Details to Include (If Known)
- Local cycle operation
- Local record availability
- Network link status
- Cable condition
- Wall jack or switch port tested
- Known-good cable result
- Approved network configuration observed
- Tracking-system availability
- IT outage information
- End-to-end transfer result
- Final device status
Final Thought
Integration failures should be isolated layer by layer: sterilizer operation, physical network connection, network configuration, infrastructure, and receiving application. Avoid unauthorized network changes, confirm the complete data path after correction, and preserve traceability throughout the outage.
That is successful troubleshooting.