healthOS
Book a demo

Solutions

Aged Care Home Care Disability Acute & Hospital

Modules

Intake Services Admin Delivery Insights Research Waitlist

Features

Government Services Clinical Coding AI Handover Wellness & Monitoring Care Pathways Deterioration Engine Notifications Bulk Integration Forms & Documents Security

More

How it works
Platform

Notifications that follow your org chart.

One embedded notification engine for the entire platform. Routes by organisational hierarchy, role and occupant — not by bolted-on email rules. In-app, email and SMS. Real-time WebSocket delivery. No separate notification product to procure or maintain.

Book a demo
Capabilities

Embedded in the platform. Not bolted on.

Role-based routing

Notifications route to roles — registered nurse, nurse unit manager, allied health, GP — not to named individuals. When staff change, routing follows automatically.

Org hierarchy scope

Rules resolve at facility, tenant then system scope — most specific wins. A single site can override routing without affecting the rest of the organisation.

Multi-channel delivery

In-app (real-time WebSocket), email, and SMS — configurable per event type. Urgent events fan out to multiple channels simultaneously.

Clinical event types

Task assignment, co-sign requests, critical results, medication alerts, deterioration warnings, coding queries — every clinical event has a notification type wired in.

Admin-configurable

Organisation admins override routing rules per site or per event type without code changes. System defaults remain as fallback — tenants tune on top.

Unified in-basket

Every notification type surfaces in one in-basket — tasks, alerts, co-sign requests, medication warnings. Filter, mark read, action or dismiss. Real-time unread count.

Operations

One notification engine. Every clinical event. Every role.

Routing rules follow your org chart. When staff rotate, notifications route to whoever occupies the role — no manual updates.

HealthOS — Notification Routing Admin ORGANISATION HIERARCHY Sunrise Health Group Tenant-level rules (3) Sunrise Aged Care — North 3 facility overrides Roles: RN, NUM, EN, AH, GP Sunrise Aged Care — South 1 facility override Roles: RN, NUM, EN, AH Sunrise Home Care Using tenant defaults Roles: RN, Coordinator SCOPE PRECEDENCE 1. Facility (most specific) 2. Tenant 3. System default Routing Rules — Sunrise Aged Care North 3 facility overrides + 3 tenant defaults + 3 system defaults shown Event Type Roles Channels Priority Scope deterioration_urgent RN, NUM, AH, GP In-app Email Urgent Facility deterioration_concern RN, NUM In-app Email High Facility deterioration_watch NUM In-app Low Tenant critical_result RN, NUM, Ordering clinician In-app Email Urgent Tenant task_assignment Assigned user In-app Normal System medication_alert Prescribing clinician In-app Email High System In-Basket 4 Sarah K. (RN) — 4 unread Critical: Systolic 152 Margaret T. | 2 min ago View → Co-sign required Harold M. progress note Review → Task: Med reconciliation Dorothy K. | Due today Open task → Coding query Episode #4821 | Coder Respond → How a notification flows Clinical Event deterioration_urgent Resolve Scope Facility > Tenant > System Resolve Roles RN + NUM + AH + GP Find Occupants Who holds the role today? Fan-out In-app + Email + SMS Delivered Real-time WS Key: Staff rotate → routing follows the role, not the person. No manual notification rule updates when rosters change. user_notifications | notification_routing_rules | WebSocket | Email (SendGrid / SES) | SMS Indicative wireframe — HealthOS Notification Engine (routing admin + in-basket)

Roles and occupants, not named recipients

Traditional notification systems route to named users. When staff rotate — agency nurses, weekend handover, leave cover — notifications go to the wrong person or nobody at all. HealthOS routes to the role and resolves who occupies that role at delivery time.

  • Routing rules target role codes: registered_nurse, nurse_unit_manager, allied_health, general_practitioner
  • Occupant resolution happens at delivery time — not when the rule was created
  • Roster changes, leave cover and agency staff: zero notification configuration changes required
  • Explicit user targeting still available for edge cases (e.g. named GP for a specific person)
  • Recipient deduplication — if one user holds multiple roles, they receive one notification, not three

Scope precedence — facility overrides tenant overrides system

A multi-site organisation needs different notification behaviour per site. The ICU wants urgent deterioration alerts to SMS + email + in-app. The community wing only needs in-app. System defaults cover everything else. No code changes — just admin configuration.

  • System defaults seeded at deployment — sensible baseline for every organisation
  • Tenant-level rules override system defaults across all sites
  • Facility-level rules override tenant rules for that specific site only
  • First match wins — the most specific scope takes precedence
  • Admin portal UI shows effective rules per site with scope attribution
  • Audit trail on every rule change — who modified, when, previous values
System Tenant Facility

No separate product. No integration tax.

Most care platforms bolt on a third-party notification service — Twilio for SMS, SendGrid for email, a custom WebSocket layer for real-time. Each requires separate configuration, separate user mapping, separate failure monitoring. HealthOS embeds all three channels in the platform itself.

  • In-app: WebSocket push with real-time unread count update — no polling
  • Email: integrated email service (SendGrid or SES) with templated HTML emails
  • SMS: direct integration where configured — no third-party notification middleware
  • One configuration surface for all channels — the admin routing rules page
  • Delivery failures logged per-channel for audit — no silent notification loss
  • User notification preferences respected: staff can mute non-urgent categories

Connected across the platform

Deterioration Engine

Nine detection rules feed urgent notifications via this routing engine.

Care Delivery

Clinical events (co-sign, critical results, medication alerts) trigger notifications.

Admin

Organisation admins configure routing rules per site and event type.

See notification routing in action.

A 45-minute walkthrough showing how clinical events resolve to the right person at the right site in real time.

Book a demo Back to home