Alerts and episodes
What creates an alert, what creates an episode, and how the two differ in webhooks, FHIR and the Console's Record episodes switch.
An alert is one breach, and an episode is the clinical event that groups the breaches of one patient and one vital. Signals always records alerts; it records episodes only while the tenant setting episodicAlerts is on, which the Console shows as Record episodes.
| Alert | Episode | |
|---|---|---|
| Created by | A reading that breaches a trigger, or an empty reading, a note or a quiet patient | The first breaching reading of a patient's vital; the readings that follow join it |
| Closes when | A trigger resolves it, or someone acknowledges it | One of the close reasons applies, such as RECOVERED or TIMEOUT |
| Webhook events | alert.triggered, alert.refired, alert.resolved, alert.acknowledged and the empty, note and inactive events | episode.opened, episode.closed |
| FHIR resource | DetectedIssue | Flag |
Needs episodicAlerts | No | Yes |
When Record episodes is off
Signals records no episodes: you get DetectedIssues but no Flags, and episode feeds stay empty. Episode webhook events cannot be subscribed to, and the episode routes answer 403 FEATURE_DISABLED. See Alerts, episodes and annotations.
While it is off, Signals stops closing episodes too: the stale-episode check skips the tenant, so an episode that was open when you turned the switch off is not closed by TIMEOUT until you turn it back on.
The medical feed and the bells
The medical feed and the bells are Easycarehub's views of open episodes.
See also
Last updated on