When network loading issues prevent Phreesia from loading forms at check-in, which approach is recommended?

• A. Reboot the server and forget it
• B. Contact
• C. Verify network status, test device connectivity, switch to offline cache if available, and queue form submissions for later
• D. Ignore the issue and continue check-in

Answer: (C)

When loading issues block forms at check-in, a practical, patient-flow–preserving approach is to triage the problem helps you confirm what’s happening and keep the process moving. First, check the network status to see if the clinic’s connection is down or if there’s an outage affecting the path to Phreesia. Then test the device’s connectivity to ensure the device itself isn’t offline or experiencing local network issues. If the system supports it, switch to offline cache so forms can be stored locally and completed without an active connection. Finally, queue form submissions so they can be submitted automatically or in a batch later when connectivity is restored. This combination minimizes data loss, avoids interrupting the check-in flow, and ensures forms eventually reach the system.

Why other approaches aren’t as good: rebooting the server might create downtime without addressing the root cause, and simply contacting support without taking immediate triage steps wastes time. Ignoring the issue or continuing check-in without a plan risks incomplete records and a messy patient experience.