Skip to main content

Sensor Integration

Ward integrates with BLE wristbands for proximity verification, fall detection, elopement prevention, and real-time patient list ordering.

Sensor Types​

Sensor Hub​

The sensor hub is an on-premise Raspberry Pi 4 that:

  • Processes wristband data for fall detection and elopement alerts
  • Monitors wristband health (battery, tamper, connectivity)
  • Communicates securely with Ward's cloud

Each unit needs at least one hub.

Patient Wristbands​

BLE wristbands (Minew B7) worn by patients:

  • Enable proximity verification for observations
  • Support fall detection via built-in accelerometer
  • Enable elopement detection via fixed BLE receivers
  • Provide real-time distance for patient list ordering

Assign one wristband per patient.

Fixed BLE Receivers​

Minew MG4 BLE gateways that detect wristband signals and forward to the hub via HTTP:

  • Exit receivers (base deployment) — placed at unit exits, stairwells, and facility exits for elopement detection
  • Room doorway receivers (optional) — placed at patient room doorways to enable room-level geofencing and presence confirmation

Hardware Setup​

Installing the Hub​

  1. Connect hub to facility network (ethernet recommended, WiFi supported)
  2. Power on the hub
  3. Wait for the hub to boot (~60 seconds) — it will display a local web UI

Registering the Hub (Zero-Touch)​

  1. Open the hub's local web UI in a browser (http://ward-hub-{id}.local) — a QR code is displayed
  2. Open the Ward app on your phone
  3. Navigate to Settings > Devices > Add Device > Sensor Hub
  4. Scan the QR code — the app registers the hub and sends the API key automatically
  5. Hub confirms connection — green status on its web UI
  6. Select unit assignment in the Ward app

Registering the Hub (Manual Fallback)​

  1. Navigate to Settings > Devices
  2. Tap Add Device
  3. Select Sensor Hub
  4. Enter hub identifier
  5. Generate API key
  6. Copy the API key and enter it on the hub's local web UI

Registering Wristbands​

  1. In Settings > Devices, tap Add Device
  2. Select BLE Wristband
  3. Enter device identifier (MAC address or printed ID)
  4. Assign to unit

Assign wristbands to patients from the patient detail screen.

Installing BLE Receivers​

  1. Mount Minew MG4 at the boundary point (unit exit, stairwell, facility exit, or room doorway)
  2. Power and network connect the receiver
  3. In Settings > Devices, add the receiver
  4. Set boundary type (unit exit, stairwell, facility exit, or room doorway)
  5. If room doorway: select the room this receiver monitors
  6. Associate with the hub

Proximity Verification​

With a wristband assigned to a patient, the staff phone:

  1. Scans for nearby BLE wristbands
  2. Calculates distance from signal strength
  3. Auto-verifies proximity when within configured threshold
  4. Records distance with the observation

Staff see "Proximity Verified" with distance when documenting if the wristband is detected.

Patient List Ordering​

The patient list on the staff dashboard sorts by proximity — nearest patients appear first. This updates in real-time as staff move through the facility. Patients without wristbands appear below detected patients.

Fall Detection​

The hub processes accelerometer data from wristband BLE advertisements:

  • Detects rapid acceleration changes consistent with falls
  • Impact followed by stillness triggers a fall alert

When a fall is detected:

  1. Alert created immediately (Critical priority)
  2. Push notification sent to all unit staff
  3. Alert escalates if not acknowledged

Elopement Detection​

For patients with elopement risk and a configured geofence:

  1. Assign a wristband to the patient
  2. Configure geofence level (unit, floor, or campus — room level available when room doorway receivers are installed)
  3. Fixed BLE receivers detect the wristband at boundaries
  4. Hub evaluates whether detection constitutes a violation
  5. Alert triggers after debounce confirmation (~6-10 seconds)

Wristband Health​

The hub continuously monitors all registered wristbands:

  • Battery: Warning at 20%, critical at 10%
  • Connectivity: Alert if not seen for >1 hour
  • Tamper: Immediate alert if band is removed

Health indicators appear on patient cards and in the device management screen.

Device Management​

Device Management

Viewing Device Status​

Navigate to Settings > Devices to see:

  • All registered devices (hubs, wristbands, receivers)
  • Online/offline status
  • Battery level (wristbands)
  • Last seen timestamp
  • Hub software version and health metrics

Hub Fleet Management​

The device management screen provides fleet-level visibility for hubs:

  • Status: Online/offline, software version, uptime
  • Health: CPU, memory, disk usage, BLE radio status
  • Updates: Current version vs. latest available, update history
  • Diagnostics: Link to hub's local web UI for detailed troubleshooting

Hubs auto-update from Ward's CDN daily at 3 AM. Updates are verified by signature and roll back automatically if health checks fail within 5 minutes.

Device Health Alerts​

Ward alerts when devices have issues:

  • Wristband battery low or critical
  • Wristband tamper/removal detected
  • Wristband or hub offline
  • Hub degraded (high CPU, low disk, outdated version)

Troubleshooting​

Hub offline:

  • Check power connection
  • Verify network connectivity
  • Open the hub's local web UI (http://ward-hub-{id}.local) for diagnostics
  • Restart the hub if needed

Hub not updating:

  • Verify hub can reach Ward's CDN (outbound HTTPS)
  • Check update status on the hub's local web UI
  • Trigger a manual update from device management

Wristband not detecting:

  • Check battery level
  • Verify wristband is assigned to patient
  • Ensure staff phone has Bluetooth enabled

Proximity not verifying:

  • Confirm patient has a wristband assigned
  • Check that staff phone BLE scanning is active
  • Move closer to patient — RSSI accuracy improves at shorter range

API Access​

Sensor hubs communicate via the Sensor Ingest API.

For custom integrations, see the API documentation.