Platform / Rule builder
NO CODE REQUIRED

Building a rule

Clinical leads and safety officers write these, not engineers. Pick a trigger, a condition, who gets asked and what runs: the graph and the readable rule are generated together.

Trigger
Who is asked
Action
TRIGGER
Irregular heart rhythm
CONDITION
4 consecutive beats outside the rhythm envelope, no motion artefact
APPROVAL GATE
On-call nurse: Confirm · 20 s · escalate on expiry
ACTION
Page the responder
WHEN ecg.rhythm.irregular_beats >= 4 AND 4 consecutive beats outside the rhythm envelope, no motion artefact ASK on-call nurse // Confirm · 20 s · escalate on expiry THEN page on-call · attach 30 s signal window
BEFORE IT REACHES ANYONE

Test against last week

Run a draft rule over recorded signal from your own fleet and see the proposals it would have raised, before a single person is interrupted by it.

Staged rollout

Ship to one ward, one shift or one squad. Compare override rates against the control group, then widen, or roll back in a click.

Versioned and signed

Every change records the editor, the diff and the approver who released it. The ledger points at the exact version that fired.

Start with one ward, one shift, or one squad

A pilot runs four to sixteen weeks depending on deployment model. You bring the population and the responders. We bring devices, gateways and the first set of rules, and we measure override rate and time-to-answer from day one.

Request a pilotSee how it works