Healthcare
Clinics and hospitals
A companion sits in the same chair for days. Instead of asking for a new code every morning, give them guest Wi-Fi that remembers the device and stays clear of the medical device network.
- Device remembered 7 days
- VLAN away from medical net
- No health data stored
- Consent logged on portal
A waiting relative, a sensitive network
A hospital guest is not an overnight visitor. A companion stays in the same room for three days, five days. A new code on their phone every morning wears them down; walking to reception to say the internet dropped again wears your staff down.
The same building runs bedside monitors, imaging equipment and the patient record system. Guest traffic must never touch that network. The phone of the person sitting beside the bed cannot share a network segment with a medical device.
And the setting is sensitive. Guest Wi-Fi has no need to know who the patient is or which ward they are in. What the record-keeping duty requires is an access record, not health data.
Law 5651 for healthcare providers
A hospital or clinic that opens internet access to visitors falls under the Law 5651 definition of a mass-use provider. The law expects that provider to keep internal IP allocation records, protect their integrity with a timestamp and retain them for 2 years. These records show which device received which internal IP and when; they have nothing to do with a diagnosis.
Whether records for the physician and staff network are also required depends on how your organisation is structured; get legal advice on this point. The box can add the staff SSID to the same record chain or watch the guest network only; the choice is yours.
This page is not legal advice; confirm your obligations with your legal adviser.
Setting up in a hospital
- 1
The box sits behind your existing modem and switch, at the point where the guest VLAN reaches the internet; the modem stays, and no extra licence is needed on the access points.
- 2
The medical device network, the patient record system and the staff network stay on separate VLANs; the guest SSID leaves the building only through the box.
- 3
Client isolation is switched on at the access points, so two visitors in the waiting room cannot see each other's devices.
- 4
TVs, kiosks and queue displays in waiting areas connect through a MAC exemption and never see the portal.
- 5
The portal carries your logo, your privacy notice and an explicit consent checkbox; the record chain starts on installation day.
Login for companions
Sign-in method
- SMS code
- Remembered device
- Coupon
The companion logs in with an SMS code on day one; thanks to device memory, the same phone reconnects for 7 days without asking for a code again. For long admissions, or relatives who cannot receive SMS, reception hands out a coupon. Our recommended 'long stay' template: 15/5 Mbps, 24-hour session, 3 devices, 5 GB per day. A guest whose phone uses a randomised MAC address may be asked for a code again; that is the phone's setting, not the box's.
Ready-made plan templates
Speed, session and device count are set per plan on the box, independent of the access point brand. The values below are our own lab recommendations and can be changed in the panel.
- Recommended for this sector
Extended stay
Hotels, serviced apartments, dormitories, hospitals, residential complexes
- Speed (down / up)
- 15 / 5 Mbps
- Session
- 24 hours
- Idle timeout
- 30 min
- Devices
- 3
- Daily quota
- 5 GB
- Remembered device
- 7 days
No new code every day; in dormitories the remembered window can span the whole term.
Standard
Cafés, restaurants, shops, bakeries, salons, gyms
- Speed (down / up)
- 10 / 5 Mbps
- Session
- 2 hours
- Idle timeout
- 15 min
- Devices
- 2
- Daily quota
- 1 GB
- Remembered device
- Off
Keeps tables turning; a guest who wants more gets a coupon from the till.
Conference
Events, fairs, waiting lounges, cinemas, bank branches
- Speed (down / up)
- 5 / 2 Mbps
- Session
- 4 hours
- Idle timeout
- 10 min
- Devices
- 1
- Daily quota
- 500 MB
- Remembered device
- Off
Low speed and one device for many simultaneous users; capacity 250 concurrent devices.
Staff-guest
Offices, factories, office towers, logistics, tutoring centres
- Speed (down / up)
- 20 / 10 Mbps
- Session
- 10 hours
- Idle timeout
- 30 min
- Devices
- 3
- Daily quota
- None
- Remembered device
- 30 days
Registered users or coupon groups; separate groups for suppliers and subcontractors.
What is recorded
- Verification detail: phone number stored encrypted and shown masked in the panel, or the coupon code
- Device MAC address
- Assigned internal IP and NAT details where applicable
- Session start and end times
- Explicit consent given on the portal
What is not recorded
- The patient's name, ward, diagnosis or any health data
- Websites visited and URLs
- Message content and call details
- Location data
Example scenario
Example scenario: a multi-storey private hospital
- Problem
- Companions come down to reception every morning asking for a new password. IT is uneasy that guest traffic shares a switch with imaging equipment. Nobody is sure what to show if an audit asks for records.
- Solution
- The guest SSID was moved to its own VLAN with its exit through the box. The 'long stay' template was applied with a 24-hour session and 7-day device memory. Waiting room TVs went onto the MAC exemption list. The hospital's privacy notice and consent checkbox were added to the portal.
- Outcome
- A companion receives one code for the whole admission. The medical device network sees no guest traffic. Daily records are chained and timestamped, and can be exported from the panel as a ZIP whenever needed.
An illustrative example; no real business is named.
Frequently asked
Does a companion have to receive an SMS every day?
No. With device memory on, the same phone reconnects without a code for as long as you set (we suggest 7 days). The session renews itself every 24 hours. If the phone uses a randomised MAC address it may appear as a new device and be asked for a code again.
Does patient data end up on the box?
No. The box keeps access records only: verification detail, MAC, internal IP and session times. Who the patient is, which ward they are in or what the hospital information system says are things the box never sees. Websites visited are not recorded either.
Can the guest network reach medical devices?
During setup the guest SSID is placed on its own VLAN and the box acts as the firewall for that VLAN; no path is opened to the medical device network. Client isolation at the access points also keeps guests from seeing each other. The box does not replace a corporate UTM; your existing security layers stay in place.
Do physician and staff connections need to be recorded too?
That depends on your organisation's structure and your legal adviser's view. Technically both routes are open: pass the staff SSID through the box and add it to the same chain, or watch the guest network only. Staff can use registered-user login with device memory of up to 30 days.
How does a foreign patient's relative connect?
SMS codes go to foreign numbers too; if you wish, international numbers are routed to a separate provider. If you prefer not to use SMS, reception prints a coupon that stays valid for the length of the admission. Coupon logins are written to the same record chain.
A 20-minute demo for your own venue
Let's work out your device count and sign-in method together.
Request a demo