RTLS nurses will actually use mid-shift.
Find pumps, clear pathway bottlenecks, cut hunt-time — without a parallel dashboard that dies after go-live. Clinical UX and DPIA first; radios second.
Hunt-time is a clinical KPI
When nurses phone around for pumps and beds, care delays and overtime follow. Equipment RTLS only works if find-in-two-taps beats a beautiful map nobody opens at 03:00.
Par levels with biomedical, not just “utilisation heatmaps”, close the loop. See medical equipment locating and the hospitals guide.
Flow without wallpaper
Patient flow programmes stall when RTLS is a bed board instead of pathway timestamps (ED→ward→discharge). Exception queues need a coordinator with authority.
Hand hygiene likewise fails when dispense counts are divorced from care moments. We design for compliance coaching and audit views separately.
Privacy is a design input
Staff-adjacent and patient pathway data need a published purpose, retention and DPIA before the first tag. Works councils and legal are stakeholders — not afterthoughts.
We prefer anonymised counts where identity is not required for the clinical decision.
How we engage clinically
Walk the ward with charge nurses before the RF survey. Success criteria are hunt minutes, pathway dwell, and whether the night shift still uses the tool at week twelve.
Measure on the ward, not in IT
Success is hunt minutes, pathway dwell, and whether night shift still uses the tool at week twelve. Walk the ward with charge nurses before the RF survey. Par levels with biomedical close the loop that heatmaps alone never will.
Staff-adjacent and patient pathway data need purpose, retention and DPIA before the first tag. Prefer anonymised flow where identity is not required for the clinical decision. See DPO and medical equipment locating.
Vendor-neutral, gate-driven, no reseller margin. Worked examples on this site are composite patterns — we baseline your operation before we quote outcomes.
What we refuse to optimise for
League tables of nurses, surprise staff tracking without a published purpose, and dashboards that only IT opens. Clinical programmes fail when hunt-time is replaced by admin time. If a design adds taps without removing calls, we stop at the gate.
Frequently asked questions
Will this add work for nurses?
If it does, we failed. The bar is fewer calls and faster finds — measured on the ward, not in IT.
Do we need to track staff individually?
Only when the use case demands it (e.g. hand hygiene opportunities). Many programmes run on equipment and anonymised flow.
How does this sit with EHR / bed management?
As a feed into systems clinicians already trust — not a competing screen. Integration scope is explicit in the SOW.
What about infection control?
Pathway and equipment location can support IPC workflows; we design retention and access with IPC and DPO input.
Last updated: 13 September 2026