Active patients
—
on your roster
In Red zone now
—
needs review today
Declining trend
—
vs prior sessions
Avg time in Green
—
across roster readings
Needs attention
ranked: Red zone first, then declining trend, then Yellowcomputed client-side from /api/provider/patients/{id}/analytics — see handoff notes for a proposed /api/provider/alertsLoading…
GET /api/provider/patients
| Patient | Diagnosis | Latest | Zone | Trend | Sessions | Last session | |
|---|---|---|---|---|---|---|---|
| Loading… | |||||||
Pick a patient from the roster to see their detail view.
FEV1 % — session history
Clinic sessions
Red zone band
Log in-clinic session
manual entry — no device link neededPOST /api/provider/patients/{id}/sessionsEnter FEV1 to preview the zone
Clinical timeline
derived from logged sessionsRecent sessions
Household context
ℹ️
Not linked to a household
Provider-added patient records link to a household only via the device QR flow (see Devices & households).
Current zone mix — whole roster
aggregated from each patient's session historyLoading…
Roster by diagnosis
Loading…
Average FEV1% by diagnosis
Needs the most attention
lowest latest FEV1%Loading…
Devices assigned to you
1 device = 1 household = 1 provider, strictlyalveoASHA doesn't yet expose a "list my devices" endpoint for providers — device/household visibility currently comes through each patient's own portal. Use "Link household" to accept a QR/token code a patient shares with you; once linked you'll see their readings via their household.
How linking works
for the design handoff
A provider sees a household's data through the device, not a direct patient link. The patient generates a QR token in their portal (GET /api/household/provider-link); on the web the provider pastes that token here instead of scanning. Transfers to another provider always require a reason and are audited (PUT /api/device/{serial}/transfer-provider).