Stale BLE Asset Locations and Wayfinding Zones in a Hospital
A six-floor hospital has 140 Mist APs and 900 BLE asset tags on infusion pumps and wheelchairs. The requirements are to locate assets within 5 m, alert when a pump enters a restricted zone, and provide visitor wayfinding. Wi-Fi location is enabled for client devices, and BLE is used for the tags. After a floor-plan update, many tags appear stacked near the elevator core, and 15% of tags show last-seen timestamps older than 20 minutes. Projected tag battery life has fallen from three years to about 14 months. Some APs were recently replaced, and the hospital wants to use virtual beacons for wayfinding plus zones for restricted areas. The clinical team wants fresher asset locations and will not accept a location system that reports pumps in the wrong zone.
1. What would you check first to explain the stacked tags and stale last-seen times?
Read the worked answer
Start with the map and the BLE scan path, not the tags. A floor-plan update can change scale or AP placement, and if the scale or floor assignment is wrong, the location engine will project many tags toward a central feature such as the elevator core. Confirm that each AP is placed on the correct floor and that the map scale is accurate. Then confirm that BLE is enabled on every AP, especially the recently replaced models, and that the APs are not excluded from location scanning. Check tag firmware and battery state, and look for a subset of tags that share a missing AP or a floor with no BLE coverage. Compare last-seen times by floor and by AP to see whether the stale group follows infrastructure rather than tags. Only after those checks would you tune scan intervals or replace tags.
2. How should zones and virtual beacons be designed to meet the restricted-area and wayfinding requirements?
Read the worked answer
Define restricted zones as polygons on the correct floor plan and attach them to the floor, not as a radius around a single AP. Test the zone boundary with real tags and confirm that a pump crossing into the restricted area generates an alert with acceptable delay; if the zone is too tight or the scan interval is too slow, alerts will be late or missed. For wayfinding, use the AP BLE radios to transmit virtual beacons in a supported format, and place them so visitors receive a useful sequence rather than overlapping beacons from every AP. The wayfinding map and the asset-location map must use the same scale and floor reference. Keep the requirements separate: BLE tags provide asset location, virtual beacons provide visitor guidance, and Wi-Fi location serves Wi-Fi clients. Do not assume Wi-Fi location will locate BLE-only tags.
3. How would you address the battery-life drop without making location stale?
Read the worked answer
Battery life and location freshness are a tradeoff. If the tags were configured to scan or transmit more often to improve the 20-minute freshness target, the projected life will fall; the 14-month estimate is a signal to examine tag scan interval, transmit power, and whether motion-triggered reporting is available. First confirm the estimate is based on actual tag settings, not a default. If the clinical requirement allows it, reduce scan frequency for stationary assets and increase reporting only when movement is detected, which preserves freshness where it matters and saves battery elsewhere. Improve infrastructure coverage so tags can use lower transmit power, and eliminate tags that are repeatedly retried because they are at the edge of BLE coverage. Re-measure last-seen times after the change; if the 20-minute target still fails, the answer is better coverage or more frequent reporting, not simply longer battery life.