Satellite-Linked Rural Clinics and the Limits of Bandwidth
Three rural health clinics share a cloud electronic health record. The main clinic has 12 staff and two satellites have 3 each. All sites use a geostationary satellite link: 25 Mbps down, 4 Mbps up, 550 ms round-trip latency, and 80 ms jitter. VoIP calls drop when the nightly 2 GB backup runs. Patient record searches take 8–15 seconds, and staff report “spinning” on the EHR login screen. The main clinic has 30 devices on one flat network, including personal phones and a networked printer. There is no VLAN, no QoS, and no local cache. The backup starts at 23:00 and ends around 02:30. The clinic manager wants reliable calls and faster record access without doubling the satellite subscription.
1. Recommend a set of network changes that improve VoIP reliability and EHR response without doubling the satellite bandwidth. Explain the expected effect of each change.
Read the worked answer
First, apply QoS: classify VoIP as EF and give it strict priority, cap backup traffic, and put EHR interactive traffic above bulk transfer. VoIP needs low jitter and one-way delay well below 150 ms; the 550 ms round trip already consumes much of that budget, so queueing delay from a 2 GB backup must be removed. Second, separate traffic with VLANs - voice, clinical data, guest/personal devices, and management. This stops a personal phone or printer broadcast storm from affecting calls and lets QoS policies target the right traffic. Third, add a local EHR cache or store-and-forward proxy at the main clinic for read-heavy records, with cache invalidation on update. Fourth, reschedule or throttle the backup and enable compression/deduplication; a 2 GB nightly upload on a 4 Mbps uplink is about 67 minutes at full rate, so it is not inherently fatal, but it saturates the link and adds queueing. Together these changes reduce contention and repeated downloads; they do not fix the 550 ms latency, which is physical.
2. Explain why the EHR login “spins” even when the satellite link is not fully utilised. Refer to latency, round trips, and protocol behaviour.
Read the worked answer
A login is not one request; it is a sequence. The client may resolve DNS, open a TCP connection, negotiate TLS, send credentials, wait for an authentication response, then fetch user preferences and permissions. Each step can require one or more round trips. At 550 ms round-trip time, ten sequential round trips already cost 5.5 seconds before any large payload is transferred. If the EHR uses chatty APIs or does not reuse connections, the delay accumulates. The link can still show low utilisation because the bottleneck is propagation delay, not bandwidth. Jitter of 80 ms also causes retransmissions and timeouts. This is why “spinning” occurs without a full pipe: the system is waiting for replies, not downloading data. Caching credentials or session tokens locally and reducing round trips - for example, connection reuse, HTTP/2 multiplexing, or a local authentication proxy - helps more than adding bandwidth.
3. The manager proposes giving every staff member a personal phone on the clinic Wi-Fi. Assess the security and performance implications and recommend a policy.
Read the worked answer
Performance: 30 devices on one flat network already share the satellite link; adding personal phones increases broadcast traffic, DHCP load, and casual streaming, which competes with VoIP and EHR traffic. Security: personal phones are unmanaged, may lack updates, and can introduce malware or hotspot bridging. A flat network lets a compromised phone reach the printer and clinical devices. The policy should put personal devices on a separate guest VLAN with client isolation, no route to clinical subnets, and a bandwidth cap. Clinical devices should use WPA2-Enterprise or WPA3-Enterprise with individual credentials, not a shared pre-shared key. Staff who need mobile EHR access should use a managed device with screen lock, encryption, and remote wipe, or a published virtual desktop. The clinic should also disable unused switch ports and change default credentials on the printer. This preserves convenience while containing risk.