Omni-channel alerts
How Ovok runs your rule on each Signals alert event and tells the people it names by push and email.
Signals sends alert events. Omni-channel alerts in Ovok tells the people your rule names, over the channels it names.
Who does what
| Signals | Ovok | |
|---|---|---|
| Sends the alert events | Yes, as it always does, to your webhooks and to Ovok | No |
| Holds your rule | No | Yes, with the project |
| Runs the rule on each event | No | Yes |
| Finds the people the rule names | No: it never holds names or addresses | Yes, from the project's FHIR records |
| Sends the email or push | No | Yes, through your email provider and push provider |
| Stores the alert | Yes | No: only a short-lived marker per send, so a retry never tells anyone twice |
Omni-channel alerts is part of Ovok. It does not change what Signals sends. To deliver alerts over a channel of your own, take Signals' alert webhooks directly.
How an event reaches people
- Signals sends an alert event, for example
alert.triggered, to the project's Ovok subscription. - Ovok runs your rule on the event. The rule answers who to tell and over which channels.
- Ovok resolves each recipient group the rule names (
practitioner,caregiver,relatedPerson,sharedWith) to people in the patient's project, and tells each of them over each channel the rule names. - A person with no email address, or no registered device, is skipped for that channel. If a provider fails, Ovok answers so that Signals retries, and only the sends that failed go out again.
A rule that fails tells nobody of that event, and the failure is logged.
Recipients
| Recipient | Who | From |
|---|---|---|
practitioner | The patient's general practitioners, and the practitioners they share their record with | Patient.generalPractitioner, and accepted record shares |
caregiver | The patient's care team | Members of active CareTeam resources whose subject is the patient |
relatedPerson | Family members and emergency contacts | RelatedPerson resources of the patient not marked inactive |
sharedWith | The people the patient shares their readings with | Accepted shares with carers and with other patients |
Email goes to the first email address in the person's telecom. Push goes to the devices the person registered after signing in.
What a message says
The email carries the patient's name, when the alert fired, the event and a link to it. Practitioners get ALERT_NOTIFICATION, everyone else PATIENT_ALERT_NOTIFICATION; map both in Email templates. No reading or value is ever included. A push shows no patient name or value on the lock screen, and its data is { type: 'ovok.alert', alertId, patientId, event }.
Turn it on
The project needs a Signals tenant of its own. Switch on OMNICHANNEL_ALERTS_ENABLED, which subscribes Ovok to the tenant's alert events. Then save a rule and map the email templates. The guide walks through it.
Related
Last updated on