During regular operation, brief network outages or network changes when clinicians move between locations should be imperceptible: Anesthesia Touch will cue changes until the connection resumes or a new connection takes its place. The application has an "Offline Mode," but this mode is typically used for planned offline periods of hours or days.

Normally, users do not need to take any extra steps if briefly disconnected from the server. 

Symptoms of Network Issues

However, consistent or persistent network issues can be disruptive. Anesthesia Touch could exhibit the following symptoms:

• Failure to save documentation to the server: charting in Anesthesia Touch is not visible for other users on other devices
• An "Unsaved Changes" count near the user name which only increases (this can increase to thousands of unsaved changes, which will be saved and uploaded when the device is able to connect to the server)
• Vitals are not populating the anesthesia record, and attempting to Import the Vitals (using "Others > Import Vitals") does not work
• Documents in cases or documentation in the IntraOp record isn't up to date when clinicians open it
• Remote View does not show vitals from ORs
• The Patient List does not update with new schedule information (or does not appear at all)
• Clinicians cannot login at all (e.g., they see an error that the server is unavailable)
• Anesthesia Touch or the host OS (iPadOS or Windows) shows a network error that prevents using the application

Troubleshooting

In the event any of the above occurs, try the following:

1. Check the network connection: if no wifi, wired, or cellular connection is available, the issue is not specific to Anesthesia Touch
2. Try using another device to determine if the issue is device-specific
3. On an affected device, turn off the active network connection, wait, and then turn the connection back on
4. Logout of Anesthesia Touch (if logged in) and log back in: this may reset Anesthesia Touch's network connection
5. Logout and power down the device and restart again to see if the issue is resolved
6. Re-install Anesthesia Touch on the device from the site's cloud server (uninstall the application and then install Anesthesia Touch again)
7. Update the host operating system (iPadOS or Windows) and ensure that a recent stable build of Anesthesia Touch is in use
8. Try using another network if feasible. This requires a network be available, can be configured on the device (e.g., it is not restricted by device management policies), and that using the network adheres to IT policies for personnel and devices.

Information for Reporting the Issue

If the issue is not resolvable, then it needs to be reported to support, possibly both the facility's IT and Plexus TG.

The following information is useful when reporting issues:

1. Device type(s) and network name(s)
2. Whether the issue is isolated or consistent, and what is affected
3. Symptoms (e.g., was a warning dialog seen or data not available)
4. Time and date of observed issue(s)
5. MRN of cases where the issue occurred, if the issue is intermittent
6. Troubleshooting steps taken to date and any results or changes