The dashboard view. Keyset-paged: pass nextCursor back as cursor.
By default this is one row per breach, filtered by tenant, patient and subscriber attachment only — NOT project-scoped, so do not build a per-facility view on it.
?episodes=true answers with episodes instead: one row per clinical event, which opens on the first breaching reading, absorbs the rest, and closes on recovery, on going stale, or by hand. That grain REQUIRES project and is the one a facility-facing feed wants. It defaults to every medical code except out-of-bed (103214-3), whose evaluation and records live in ovok.
Filters belong to one grain or the other: algorithmId to alerts, and codes, since and acknowledged to episodes. Sending one to the wrong grain is a 400, not a filter that silently did nothing. status reads ACTIVE/RESOLVED for alerts and OPEN/CLOSED for episodes.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
A filter was sent to the wrong grain, or episodes=true arrived without project.
Missing, malformed or unrecognised Basic credentials.
Authenticated, but the client's role does not permit this, or it is not attached to the patient.
episodicAlerts is not enabled for this tenant, and episodes were requested.