Send Content-Free Notifications Across Channels
Veona sends a great many messages — appointment confirmations, result-ready nudges, staff invites, telehealth reminders, immunisation-due alerts. Every one of them goes through a single notification engine, and every one obeys one ironclad rule: no protected health information ever leaves the building in a notification. A message says “a result has been verified” or “your appointment is confirmed” — never the result value, never the diagnosis. The detail lives behind a secure login; the notification only points you to it. This page explains how that engine works and how an Administrator configures the channels it sends on.
Who / when: notifications touch all roles — staff are invited and reminded, patients are confirmed and nudged. The messages fire automatically as the clinical flows reach their milestones; an Administrator is the one who decides which channels are switched on and reviews what was sent.
The words you’ll need:
- Patient data — any clinical or identifying detail about a patient. The point of this whole design is that patient data never appears in a notification.
- Content-free — a message deliberately stripped of clinical content. It tells you that something happened and where to look, not what it says.
- Channel — the path a message travels: in-app banner, email, and (where configured) SMS. The same message can render to any channel.
- Template — the fixed, reviewed wording for each kind of event, so messages read consistently and the content-free rule is baked in, not left to whoever sends.
- Automatic (the engine) — when a clinical flow reaches a milestone — a result released, an appointment booked, a referral created, an immunisation falling due — the responsible module hands the event to the notification engine, which picks the right template and delivers it on the recipient’s enabled channels. No one presses “send”; it is part of the flow.
- Recipient — you receive a plain, safe message: for a patient, “Your appointment is confirmed” or “A result has been verified — sign in to view it”; for staff, a single-use invite link. To see the actual detail, you sign in to Veona or the patient portal — the message itself never contained it.
- Administrator — to choose which channels your facility sends on (in-app, email, SMS) and provide the connection details for each, open Admin → Channels. A channel that is switched off is simply skipped; the in-app message still appears.
- Administrator — to review the catalogue of message types and what has been sent, open Admin → Notifications. This is where you confirm a wave fired and see the engine’s activity, without ever exposing patient data in the log.
What happens next: because the engine is shared and the rule is universal, every module gets safe, consistent messaging for free — the lab can nudge an ordering clinician, the front desk can confirm a booking, HR can invite a new colleague, all without any of them having to think about what is safe to put in a message. Patients can tune which channels they hear from on their own preferences screen (see Set Notification Preferences and Channels), and the operational story of a whole batch going out is covered in Deliver an Audited Notification Wave.