A ward-scale system that takes every monitored patient's temperature continuously, keeps the record itself, and tells the nurse station the moment a reading crosses its threshold. The ward is watched around the clock, without anyone walking it to find out what changed.
What the ward sees, what nurses do differently, and what it saves.
Instead of one number per patient, every monitored bed sits on one screen — the live reading, the trend behind it, and whether a threshold has been crossed. Staff can see at a glance who is stable, who is climbing and who needs someone now. The console at the nurse station is where alerts land and where sensors are assigned to patients, and it is meant to be learned in one sitting rather than handed to a technician.
Nurses stop walking a fixed schedule of manual checks and start responding when the system flags something. That does not take clinical judgment out of the ward. It changes when judgment gets used — at the moment the data says a patient needs attention, rather than at a pre-set time regardless of what is happening in the bed.
The return is nursing time no longer spent on routine rounds, and earlier warning of deterioration that would otherwise wait for the next scheduled check. At Longhua Central Hospital, monitoring 183 patients this way saved approximately 91 staff hours. Every ward differs in size, staffing and patient acuity, so we would rather work the numbers against your own rounding schedule during a pilot than quote you an industry average.
The patient only ever sees the sensor. The rest runs out of sight.
Each patient wears a 2g sensor under the arm — hypoallergenic patch, no wires, nothing for the patient to operate.
Ceiling- or wall-mounted gateways collect readings from every sensor in range. No hospital IT integration required to start.
Readings stream to the cloud dashboard: live ward map, trend curves, threshold alerts and full history for every patient.
The station screen shows every monitored patient at a glance, and raises audible alerts the moment any temperature crosses its threshold.
Every ward already takes temperatures. The question is what that costs, and what gets missed.
| Manual temperature rounds | Continuous monitoring | |
|---|---|---|
| How often a reading is taken | △ Every few hours, on the round schedule | ✓ Every few seconds, with nobody in the room |
| A spike between two checks | ✗ Happens and passes unseen | ✓ On the station screen as it starts |
| The record | △ Written by hand, transcribed later | ✓ Logged automatically and exportable |
| At night | ✗ Patients woken to be measured | ✓ Patients sleep through it |
| Who is watching | △ Whoever is walking the round | ✓ One screen, every monitored bed at once |
| Where staff time goes | ✗ A fixed round, whatever is happening | ✓ The bed an alert points at |
What each stage asks of your team, and what we bring to it.
You map the ward and where the beds sit. We go through it with you and agree where the gateways go so no bed is out of range — usually settled in a day.
Sensors assigned to patients via the nurse console; readings flow to the dashboard immediately.
Nurses learn the console in a single session: assign sensor, set thresholds, respond to alerts.
Additional wards replicate the pilot configuration. Central dashboard views span departments.
Share your bed count and use case, and our team will come back with a recommended configuration and volume pricing.
P20 wearable sensors, Bluetooth gateways to relay readings, a cloud dashboard showing every monitored bed, and a nurse station console for assigning sensors and responding to alerts.
The dashboard is designed to scale from a single pilot ward to multiple departments — the architecture doesn't change with scale, only the number of gateways and sensors deployed.
A pilot ward can typically go live within days of the site survey. Exact timing depends on ward layout and how quickly staff onboarding is scheduled.
Not as a prerequisite — the system runs as a standalone dashboard and console. Export interfaces are available via our SDK for hospitals that want to feed data into existing clinical systems, but this isn't required to start monitoring.
Yes, this is the recommended approach. A pilot ward validates the workflow before scaling, and additional wards typically replicate the same configuration once it's proven.
The console is designed to be learned in a single onboarding session covering sensor assignment, threshold setting and alert response — most hospitals train staff on the pilot ward directly rather than through separate classroom training.
This depends on your ward's current manual rounding frequency and staffing model; the shift is generally from scheduled walking rounds to responding to system-flagged events. We recommend evaluating this against your specific ward's baseline during a pilot.
