Settings
OMNICHANNEL_ALERTS_ENABLED
Turns on Omni-channel alerts, so Ovok runs your rule on each Signals alert event and tells the people it names.
Turns on Omni-channel alerts. Ovok runs your rule on each alert event Signals sends and tells the people it names, by push and email.
| Type | Boolean setting |
| Change with | PUT /v1/project/settings/OMNICHANNEL_ALERTS_ENABLED |
| Who can change it | Project admin |
| When unset | Off |
| Needs | A Signals tenant of the project's own |
| When off | Ovok tells nobody. Signals still sends its alert events to your own webhooks. |
curl -X PUT 'https://api.sandbox.ovok.com/v1/project/settings/OMNICHANNEL_ALERTS_ENABLED' \
--header "Authorization: Bearer ${OVOK_TOKEN}" \
--header 'Content-Type: application/json' \
--data '{"enabled": true}'What turning it on does
Ovok subscribes to the tenant's alert events. Turning it off removes the subscription.
The setting does not write a rule. Until you save one, nobody is told.
Gotchas
- No rule, no messages. Check
GET /v1/omnichannel-alerts/rulesafter turning it on. - Map the email templates.
ALERT_NOTIFICATIONandPATIENT_ALERT_NOTIFICATIONgo out through your email templates. - Shared Signals tenants are not supported. The project needs a tenant of its own.
Related
Last updated on
PATIENT_SHARING_ENABLED
Let patients share chosen readings with another patient or a carer, how to turn it on, and why it is not in the project settings record.
PATIENT_BILLING_ENABLED
Turns on patient billing and insurance, so a project can store patients' insurance, plans, billing accounts and invoices through /v1/patient-billing.