On this page
Asset Type
Manufacturer
Model
What This Guide Helps With
Troubleshoots connectivity, data-transfer, and approved update failures caused by cabling, network infrastructure, removable media, configuration, permissions, or compatibility.
Step-by-Step Troubleshooting
1. Protect Clinical Operation Before Troubleshooting Connectivity
Do not interrupt active anesthesia delivery to troubleshoot a nonessential network, export, or software-update problem. Perform troubleshooting with the machine out of patient use whenever changes, restarts, or cable manipulation may be required.
Expected outcome: Connectivity troubleshooting does not interfere with patient care or critical anesthesia functions.
2. Confirm the Exact Failure
Determine whether the issue involves network connectivity, central-system communication, data export, removable media, or an approved software-update process. Record the exact displayed message and when the failure occurs.
Expected outcome: The problem is narrowed to a specific communication or software workflow.
3. Verify Physical Network Connections
Inspect accessible network cables and connectors for loose seating, damaged latches, pin damage, or obvious cable defects. Confirm the cable is connected to the intended wall jack or network connection.
Expected outcome: The physical network path is securely connected and visibly intact.
4. Check the External Network Path
When permitted, verify the wall jack, switch path, or network connection using an approved known-good device, cable, or infrastructure test method. Coordinate with hospital IT when the network connection is managed by them.
Expected outcome: The network infrastructure is confirmed operational or an external infrastructure problem is identified.
5. Verify Approved Network Configuration
Review visible and authorized network settings such as addressing or connection status without changing established configuration unless the correct values are documented and the change is authorized.
Expected outcome: The Flow-c configuration matches the intended hospital network design, or a configuration discrepancy is identified for authorized correction.
6. Check Data-Export Media and Connections
For data-export problems, verify approved removable media or external connections are properly inserted, recognized, compatible with the approved workflow, and not visibly damaged. Test a known-good approved medium when appropriate.
Expected outcome: The export problem is isolated from damaged, incompatible, or improperly connected external media.
7. Verify Software-Update Preconditions
For an approved software update, confirm the update package, machine identification, required power condition, approved media or network path, and authorization are appropriate before proceeding. Do not install unofficial files or repeatedly retry a failed update.
Expected outcome: The update is attempted only under documented and authorized conditions.
8. Verify Communication After Correction
After correcting a cable, infrastructure, media, or authorized configuration issue, verify that the intended connection or export completes and that the receiving system recognizes the expected data where applicable.
Expected outcome: Communication or data transfer operates correctly end to end.
9. Complete Final Functional Verification
If a software update or restart occurred, complete required post-update checks and verify normal startup, ventilation, alarms, controls, and network-related functions before return to service.
Expected outcome: The Flow-c operates normally and the affected communication or software function is restored without compromising clinical operation.
If the Problem Persists
If cables, wall connections, infrastructure, approved network settings, removable media, permissions, and update prerequisites have been ruled out, the problem may involve an internal network interface, software corruption, compatibility issue, server-side configuration, cybersecurity restriction, or other service-level condition.
Remove the machine from network-dependent service as appropriate and, when clinical functionality or software integrity is uncertain, remove it completely from service and label it Out of Service. Coordinate further evaluation with qualified Clinical Engineering, hospital IT, cybersecurity personnel, and the manufacturer as appropriate.
Use current manufacturer documentation and approved service tools for software recovery or configuration. Do not bypass security controls, install unapproved software, or modify undocumented settings.
Following repair, configuration, or update, complete the appropriate communication checks and full return-to-service functional testing. Recognizing an infrastructure or software boundary and escalating appropriately is proper troubleshooting.
Clinical Use Tip
Verify the entire communication path—including the Flow-c, cable, network infrastructure, and receiving system—before assuming the anesthesia machine itself has failed.
Work Order Documentation (CCR Method)
CCR = Complaint, Cause, Resolution
Complaint
What was reported by the clinical staff.
Example:
"OR staff reported the Getinge Flow-c could not communicate with the hospital network after the machine was moved to another room."
Cause
What was observed during troubleshooting.
Example:
"Clinical Engineering found the network cable connected to a wall port that was not active for the required device network."
Resolution
What action was taken.
Example:
"Clinical Engineering coordinated connection to the correct active network port, verified communication with the receiving system, and confirmed normal machine operation."
Helpful Details to Include (If Known)
- Exact network, export, or update message
- Function that failed
- Network cable condition
- Wall jack or port tested
- Connection or link status
- Authorized network settings observed
- Receiving system involved
- Approved removable media tested
- Recent room move or network change
- Software/update version information when relevant
- IT or manufacturer involvement
- Results before and after correction
- Final functional-test result
- Final device status
Final Thought
Connectivity and software problems should be isolated methodically from cable and infrastructure through configuration and receiving systems before the machine is blamed. Protect clinical operation, avoid unauthorized changes, escalate service-level failures, and document end-to-end verification.
That is successful troubleshooting.