Home / Platform / Notifications & Action Centre

Core platform

The right person hears about it. If they do not answer, the next one does.

A critical result at 02:00, a fridge out of range on a bank holiday, a device that has gone quiet: the problem is rarely that nobody was told. It is that the wrong person was told, nobody acknowledged it, and there was no second step. Catenix makes the rules explicit and the chain visible.

  • Rules per organisation, seeded with sensible defaults
  • One acknowledgement stops the chain for everyone
  • Escalation up the ladder on a timer
  • 20+ Action Centre signals with deep links

Notifications

Rules, acknowledgement, escalation, digest, one inbox.

Rules you can read

Per organisation: event type, filters (sites, devices, analytes, minimum severity), recipients (users, roles, extra emails, a webhook), channels (in-app, email, webhook), whether acknowledgement is required and how long the window is, quiet hours and duplicate suppression. A default set is seeded once and is yours to edit.

Acknowledged once, for everyone

Acknowledgement is per event with a note. One person acknowledging clears it for every recipient and stops the chain. Who acknowledged what, and when, is audited.

Escalation that gives up gracefully

If nobody acknowledges within the window, the rule's escalation steps run in order: next recipients, delays, optional email. When the chain is exhausted that is recorded once, and the noise stops.

Quiet hours and digests

Quiet-hour deliveries can be held or folded into a daily digest per user, grouped by category with critical first, emailed and available in-app.

One inbox

Notifications, digests, follow-up reminders assigned to you and older messages in one list with unread, acknowledgement, snooze, category and severity filters. The badge shows count, acknowledgements pending and criticals.

Nothing lost

Deliveries with no transport configured are stored as drafts, never dropped. Rule changes, emissions, escalations and acknowledgements are audited.

The Action Centre

What needs doing today, with a link to where it is done.

Every item carries a hint on what to do and a deep link that opens the right tab with the right filter. A missing table reads as unknown, never as a silent zero.
SignalSeverityOpens
Re-matched results awaiting downstream correctionCriticalResults, corrections queue
QC lockouts; QC failures without a root-cause reviewCriticalQC
Critical results not yet reviewedCriticalResults, critical filter
Certifications expired or expiringWarning / CriticalCompetency
Devices silentWarningDevice management, connectivity
EQA overdue; EQA due within 7 days; stale investigationsCritical / WarningEQA deadlines
CAPA overdue; non-conformance overdueWarningCAPA / Quality
SOP review due; SOP unsignedWarningDocument control
QC material expired or expiring within 14 daysCritical / WarningQC materials
Follow-ups due; unmatched results ageing; ambiguous matchesWarningFollow-ups / Results
Analyser service overdue; temperature excursions; in-use reagents expired; devices downWarning / CriticalDevice operations
Background jobs that gave up; scheduled reports whose last run failedWarningJobs and schedules

A clear boundary

Catenix is connectivity, workflow, record-keeping and data display. It does not interpret results, calculate clinical values, classify or flag results clinically, or provide clinical decision support. Statistics describe methods, processes and datasets, never a patient. Any reference range or note shown is customer-authored content Catenix displays.

Questions, answered

The questions teams ask first.

What events can trigger a notification?

Critical results, QC lockouts and failures, silent devices, expiring certifications, result matching corrections, temperature excursions and custom events raised by other modules, filtered by site, device, analyte and severity.

Who receives them, and how?

Recipients are users, roles resolved to the active users of your organisation, extra email addresses or a webhook. Channels are in-app, email and webhook. Quiet hours can hold a notification or fold it into the daily digest, and a duplicate-suppression window stops the same event nagging.

What does acknowledgement do?

Acknowledgement is per event: one person acknowledging clears it for every recipient and stops the escalation chain. Unacknowledged events walk through the rule's escalation steps on a timer, then record that the chain was exhausted and go quiet.

What is in the Action Centre?

A strip of signals with counts and deep links: re-matched results awaiting correction, QC lockouts and failures without review, critical results, expired and expiring certifications, silent devices, EQA overdue and due, overdue CAPAs and NCs, SOP reviews and unsigned SOPs, expired and expiring QC materials, follow-ups due, ageing unmatched and ambiguous results, device service overdue, temperature excursions, expired in-use reagents, devices down, dead background jobs and failed report schedules. A missing table reads as unknown, never as a silent zero.

Is anything sent to patients?

This page is about staff notifications. Patient communications are handled by reporting and the patient app, and are held while a critical result on the encounter is unacknowledged.

See an escalation chain run.

We will fire a critical-result event on a live tenant, let the window lapse, and watch it climb the ladder and stop on acknowledgement.