What it does
- Live calls and faults across every ward, with the time each was raised, attended and cleared.
- Response-time reporting by ward, shift and call type; repeat-caller and fault histories; CSV and PDF export.
- Clinical messaging to Olinqua and Ascom over TAP with heartbeat supervision — calls land on DECT and smartphones.
- Display feeds for corridor and staff-base displays over MQTT, including isolation status.
- Room sensing — radar/thermal fall and presence sensors raised as calls.
- Uptime Report — monthly availability per site for gateway, link and controller-feed layers.
- BACnet feed — read-only objects for EBI and other BMS platforms, opt-in.
New installation or legacy head end
In a new Southerly installation the Ward Gateway is the head end for Edge Nodes and call points. Over a legacy system it connects to the existing controller's data feed, read-only, and does the same job — which is how a hospital gets reporting and messaging on day one and migrates rooms afterwards. How migration works →
Remote and 4G sites
Small sites connect over 4G with the gateway dialling out to a supervised peer; the link is monitored and appears in the Uptime Report alongside the controller feed, so a dropped link is distinguished from a dropped call system.
Specifications
| Role | Head end / supervisor for Southerly Nurse Call; read-only data gateway over legacy controllers |
|---|---|
| Hardware | WG-01 Rev B industrial controller board (in production); DIN rail; supervised 12–24 V DC |
| Interfaces | Ethernet; RS-485; legacy controller data feed (read-only); optional 4G |
| Integrations | Olinqua, Ascom (TAP/IXO); MQTT displays; BACnet/IP (read-only objects); CSV/PDF reports |
| Software | Southerly Gateway 1.11 — web application, role-based access, audit log |
| Standard | Designed to AS 3811:2026 |
| Status | Live at hospital sites |