Product tour
Alerts and codes
From a code button or a critical result to acknowledgement, escalation and audit.
Diagram: the critical-result path. Timers are example values that the specification marks as open.
Diagram: the imminent-threat path. Who counts as the two people is an open owner decision.
What exists Pilot
- 22 editable default code templates per facility, with a “confirm local meaning” notice.
- Colour plus pattern plus plain text, so alerts never rely on colour alone.
- Propose-then-approve by a different person for catalog and policy edits, versioned.
- Drill mode and silent mode; Do Not Disturb never silences the highest-priority alerts.
- Routine pings are rate limited; emergency alerts are exempt.
- Drills with timings, delivery and acknowledgement reports, and a stale-alert watch.
- A setting for how an imminent-threat alert may be cancelled (any two eligible people, or two different role classes). The owner’s default is still pending.
Limits
- Alerts reach connected terminals only: no pager, SMS or overhead paging Designed.
- The on-site hub keeps alerts running when the internet is down; late alerts are flagged when they arrive after reconnect.
- Touch screens get 48 px buttons; with a mouse the minimum is 36 px.
- Code meanings are typical usage; each hospital confirms its own. None is claimed universal.
Common questions
Can an alert be cancelled by one person?
Not the imminent-threat alert. A first eligible role starts the cancel and a different eligible person must confirm within a time window. The pairing rule is an open decision.
Does it page phones?
No. SMS, pager and overhead paging are not built.
See alerts and codes on synthetic data
A short walkthrough. No patient information needed.