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. For a site that only needs paging, see Paging Link.
- Display feeds for corridor and staff-base displays over MQTT, including isolation status, alongside each Edge Node's own board.
- 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.
- Role-based access and an audit log — ward, administrator and read-only roles; every change recorded.
New installation or legacy head end
In a new Southerly installation the Enterprise Gateway is the head end for Edge Nodes and call points. Over a legacy system it connects to the existing controller's data feed through a Ward Gateway board, 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.
The Assistant
Staff talk to the Enterprise Gateway in plain language. Ask it to page a ward and it works out who should get the message, drafts it with the location and priority filled in, and waits for a tap on Send. Ask what happened on a ward and it answers from the live records. It runs on Claude, inside the gateway, with the same role-based permissions as the person asking — a ward login can page and check status; configuration needs an administrator.
Where it runs
On a small on-premises appliance on the hospital LAN — no cloud, no internet dependency, no licence server that can switch the ward off. The web application is reached from any browser on the network; nothing is installed on staff devices.
Specifications
| Role | Software head end / supervisor for Southerly Nurse Call; read-only data gateway over legacy controllers |
|---|---|
| Modes | New installation over Edge Nodes · legacy read-only over an existing controller (via Ward Gateway WG-01) |
| Runs on | On-premises Southerly appliance on the ward LAN; Ethernet; optional 4G for remote sites |
| Integrations | Olinqua, Ascom (TAP/IXO); MQTT displays; BACnet/IP (read-only objects); CSV/PDF reports |
| Access | Web application, role-based access, audit log |
| Version | Enterprise Gateway 1.11 |
| Standard | Designed to AS 3811:2026 |
| Status | Live at hospital sites |