Wearable guideWearable setup

NexRing

DueCare • PPG/ECG

Continuous remote monitoring wearable for heart rate, SpO₂ trends, sleep, readiness, and telemetry.

Transport

Bluetooth

Launch

Direct page

Mode

Continuous

Before you begin

Check these first so setup goes smoothly.

Ensure the ring is charged and worn on the correct finger.

Enable Bluetooth and keep the phone close during pairing.

Use the real normalized session path already implemented for scan, connect, and metric flow.

Confirm persistence wiring is aligned with your existing vitals contracts.

Recommended order for first-time or repeat setup.

Open the NexRing page and start a scan.

Select the discovered device and connect.

Allow the session bootstrap to complete, including battery and device info requests.

Monitor normalized metrics and confirm telemetry is updating.

Persist supported values through the clean metric persister path.

What to check when the workflow does not behave as expected.

If pairing succeeds but metrics are sparse, inspect bootstrap commands and notification handling.

If data flows but persistence is missing, wire the session onMetric output into the vitals contract cleanly.

If a ring connects under web transport but misses advanced features, compare with native plugin behavior.

If duplicate metrics appear, inspect bounded history and persistence dedupe rules.

Use these rules to keep the workflow reliable and clinically sensible.

Treat wearable readings as trend-supporting data, not a sole clinical decision engine.

Confirm abnormal values with dedicated spot-check workflows where needed.

Keep persistence normalized and clearly sourced as wearable telemetry.

Operational guidance based on how these integrations are actually shaped in the app.

NexRing is best positioned as CRM/RPM rather than a one-off spot-check device.

Keep wearable persistence thin and clean instead of contaminating Health Monitor logic.

Use the dedicated device page for real monitoring and `/iomt` for quick access only.