ABOUT
This is not a technology company
that consulted some doctors.
SignalPath was built by a senior clinician after years running cardiac arrests, MET calls, trauma resuscitations, retrievals, and ICU emergencies.
The product exists because the documentation problem is real, the people writing the record at 3am are exhausted, and the current tools — paper, whiteboards, memory — are not enough.
01 — THE BOUNDARY
We record.
We don't recommend.
SignalPath captures, structures, and timestamps clinical events. It does not interpret them. It does not suggest treatments. It does not generate alerts or make clinical recommendations.
That boundary is deliberate and permanent.
Clinical decisions belong to clinicians. SignalPath's job is to make sure the record is accurate, complete, and defensible.
02 — THE DESIGN
Designed for the worst
moment of the day,
not the best one.
Every interface decision in SignalPath was made for one person — the tired, stressed, terrified clinician documenting at 3am.
PRINCIPLE 01
Large targets.
Hand tremor under stress. Gloved hands. No precision input available during resuscitation.
PRINCIPLE 02
Minimal cognitive load.
Working memory failure under cortisol. The scribe cannot also be a UI navigator.
PRINCIPLE 03
Clear hierarchy.
Visual search time costs seconds you don't have.
03 — THE ORIGIN
Why SignalPath exists.
The documentation problem in critical events has been ignored for too long. The most important records in clinical practice are reconstructed hours after the event, by the most junior person in the room, from incomplete notes.
That record then becomes the basis for clinical handover, audit, debrief, and — sometimes — coronial review.
SignalPath exists because that gap is unacceptable.