Engineering
Event-driven monitoring at clinical scale
Why we treat a vital sign as an event with a lifecycle, not a row in a table.
A vital sign is not a number. It is a measurement with a timestamp, a source, a confidence and a clinical context. Treating it as a row makes it easy to store and hard to reason about. Treating it as an event makes the workflow possible.
Our monitoring layer gives each signal a lifecycle: received, normalized, evaluated, surfaced and resolved. The care team sees the current state, while the record keeps the history. The same event can trigger a notification, a documentation task or nothing at all.
The design constraint is not throughput alone. It is legibility under pressure. Every state change has an owner and an audit trail, so a clinician can answer the question that matters most: why is this in front of me now?