healthOS
Contact us

Solutions

Aged Care Home Care Disability Acute & Hospital Wellness & Monitoring

Modules

Intake & CRM Services Care Admin Care Delivery Data & Insights Research

Features

Government Services AI Handover Voice Dictation Pathways Deterioration Engine Notifications Telephony Bulk Integration Forms & Documents Security

More

How it works

Notifications that follow your org chart.

The right person hears about it the moment it happens. One embedded notification engine for the entire platform. Routes by organisational hierarchy, role and occupant, not by bolted-on email rules. In-app and email. Real-time WebSocket delivery. No separate notification product to procure or maintain.

Contact us

See it in motion.

A short, narrated explainer. Captions included.

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) and email, configurable per event type. Urgent events reach the in-basket and email.
Clinical event types
Task assignment, co-sign requests, critical results, medication updates, 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 updates. Filter, mark read, action or dismiss. Real-time unread count.

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 Work Queue showing clinical tasks and notifications with priorities, sources, owners and due dates across care teams

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 and when
System Tenant Facility

No separate product. No integration tax.

Most care platforms bolt on a third-party notification service, a separate SMS gateway, a separate email service, a custom WebSocket layer for real-time. Each requires separate configuration, separate user mapping, separate failure monitoring. HealthOS owns the routing, templating, deduplication and audit itself, and drives the delivery channels from one place.

  • In-app: WebSocket push with real-time unread count (with a polling fallback)
  • Email: integrated transactional email (Postmark, or Microsoft 365 via Graph) with templated HTML emails
  • SMS: available where configured (used today for family messaging)
  • 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 stored; per-category muting of non-urgent notifications is planned

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 updates) 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.

Contact us Back to home