On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshoots missing cycle documentation caused by printer supplies, connections, destination settings, network communication, record storage, or export-path problems.
Step-by-Step Troubleshooting
1. Protect the Patient and Preserve Reprocessing Documentation
Do not assume a scope is cleared for clinical use when required cycle documentation or traceability records are unavailable.
Preserve any available on-screen or local cycle information and follow facility policy for documenting affected reprocessing cycles.
Expected outcome: Clinical use and traceability decisions are not based on an unverified missing record.
2. Confirm What Is Actually Missing
Determine whether the problem involves:
- No local cycle record.
- Record exists locally but does not print.
- Printer output is blank or incomplete.
- Network export is missing.
- Tracking system did not receive the cycle.
- Only one cycle is missing versus all recent cycles.
Record the affected cycle, scope ID, date/time, and operator information when available.
Expected outcome: The failure is narrowed to record creation, printing, or external export.
3. Verify the Cycle Actually Completed and Was Stored
Using normal authorized controls, determine whether the affected cycle appears in local cycle history.
If the record exists locally, do not treat the problem as a missing-cycle-data failure; focus on printing or export.
If the record does not exist locally, preserve all available details and escalate appropriately.
Expected outcome: Local record availability is confirmed.
4. Inspect the Printer and Consumables
If a connected or integrated printer is involved, inspect:
- Paper supply.
- Correct paper loading.
- Cover or door closure.
- Paper path.
- Visible jams.
- Accessible printer connections.
- Printer power if externally powered.
Do not dismantle the printer mechanism.
Expected outcome: The printer is powered, loaded, connected, and free of obvious external obstruction.
5. Test Whether the Printer Responds
Use an authorized normal print function or another available record to determine whether the printer can produce output.
If another record prints normally, the problem may be isolated to the original cycle record.
If nothing prints, continue troubleshooting the printer or communication path.
Expected outcome: Printer functionality is distinguished from a specific missing record.
6. Inspect External Communication Connections
For networked record export, inspect accessible:
- Ethernet cables.
- Wall connections.
- External adapters.
- Patch connections.
- Network link indicators.
Reseat loose external connections if permitted.
Do not alter network parameters without authorization.
Expected outcome: The physical communication path is intact.
7. Determine Whether the Problem Is Local or Department-Wide
Check whether:
- Other ED-Flow units are exporting successfully.
- Other networked equipment in the same area is affected.
- The tracking or documentation server is available.
- IT or the application owner is aware of an outage.
A problem affecting multiple systems strongly suggests infrastructure or server-side involvement.
Expected outcome: The issue is isolated to the ED-Flow or identified as a broader system problem.
8. Verify Export Destination and Normal Configuration
Using authorized operator or technical configuration views, confirm that the intended printer or network export destination remains selected.
Compare with a known-good ED-Flow configuration if available.
Do not change undocumented network, security, or application settings.
Expected outcome: The unit is configured to send records to the intended destination.
9. Check Date and Time When Relevant
Verify that the displayed date and time are reasonable.
Incorrect timestamps can make successfully exported cycle records difficult to locate in downstream systems.
Do not make configuration changes outside authorized procedures.
Expected outcome: Records can be searched using an accurate cycle timestamp.
10. Attempt a Controlled Record and Export Test
After correcting any printer, cable, or configuration problem, run the appropriate approved test or use an authorized existing test record.
Verify:
- A record is generated.
- The record remains available locally.
- Printing works if required.
- Network export reaches the intended destination.
- The exported record corresponds to the correct cycle.
Expected outcome: Complete documentation is generated and reaches the required destination. Troubleshooting can stop after successful verification.
11. Preserve Missing-Record Information
If a specific cycle record cannot be recovered, document every available detail before further service work, including scope ID, cycle time, operator report, and displayed completion status.
Do not fabricate or manually reconstruct an official automated cycle record unless an approved facility process specifically allows it.
Expected outcome: Available evidence is preserved without creating misleading documentation.
12. Remove From Service When Required Records Cannot Be Reliably Produced
If required cycle documentation, printing, or export remains unreliable and the facility depends on that function for traceability, remove the ED-Flow from service until corrected.
Expected outcome: The reprocessor is not used when required documentation cannot be reliably maintained.
If the Problem Persists
Common external causes such as paper supply, printer loading, accessible cabling, destination selection, network connectivity, timestamp confusion, and local-versus-network record location have been ruled out.
Remaining causes may involve internal record storage, printer electronics, application configuration, network infrastructure, interface services, database communication, or another service-level condition.
The device should be:
- Removed from service when required documentation cannot be assured.
- Labeled Out of Service.
- Sent for repair or bench evaluation as appropriate.
- Evaluated using appropriate Getinge documentation and approved test equipment.
- Repaired or configured only by qualified personnel.
Coordinate with IT, cybersecurity, the tracking-system administrator, or Getinge when the failure is outside the reprocessor's external connections.
Verify local record creation and the complete required documentation path before returning the unit to service.
Knowing when to stop external troubleshooting and escalate is proper troubleshooting.
Clinical Use Tip
Verify the complete record path from the ED-Flow to the required traceability destination rather than assuming a locally completed cycle was successfully documented elsewhere.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"Sterile Processing reported that ED-Flow cycle records were visible locally but were no longer appearing in the networked tracking system."
Cause
What was observed during troubleshooting.
Example:
"Clinical Engineering found a loose Ethernet connection at the reprocessor with no stable network link."
Resolution
What action was taken.
Example:
"Reseated and secured the network connection, verified link restoration, completed a controlled record-export test, and confirmed the cycle record reached the tracking system."
Helpful Details to Include (If Known)
- Affected cycle date and time.
- Scope ID.
- Whether the record exists locally.
- Printer condition and paper status.
- Print-test result.
- Network link status.
- Cable and wall-port condition.
- Intended export destination.
- Whether other ED-Flow units are affected.
- Tracking-system availability.
- Date/time displayed by the reprocessor.
- Test export result.
- Results before and after correction.
- Final device status.
Final Thought
Protect traceability as part of patient safety, determine whether the failure is record creation, printing, or export, verify external causes before assuming internal failure, escalate appropriately, and document the final end-to-end verification.
That is successful troubleshooting.