Kairos ranks incoming genomic cases by urgency, drafts each report before a reviewer opens it, and routes every case to the right person. The clinical judgement stays where it belongs; what changes is the order of the work and how much of it is already done.
The queue is the problem
In genomic triage, the hard part is rarely the analysis. It is the order of the work. Cases arrive faster than they can be read, each one carrying a different degree of urgency, and the person who decides what to open next is usually the person least able to spare the time. Wait long enough and the sickest patient is somewhere in the middle of a list, indistinguishable from the rest.
Kairos was built around that ordering problem rather than around the science. The clinical judgement stays with the clinicians. What the system changes is what reaches them, in what order, and how much of the work is already done when it does.
What we built
- Ranking: every incoming case is scored for urgency and placed in a queue that reflects it.
- Drafting: each report is prepared in advance, so a reviewer edits rather than starts.
- Routing: a case goes to the reviewer whose expertise fits it, not to whoever is next.
- Review: nothing leaves the system without a person approving it.
The draft is the part that changes the day. A reviewer opening a prepared report spends their attention on judgement - what the evidence supports, what it does not - instead of on assembling the same structure again. The system holds the structure; the person holds the decision.
How it runs
Kairos runs under the client's own name, on their own infrastructure. Nothing in it carries ours, and no patient data leaves the system to train a model. That is the standard for everything we build, and in clinical work it is the condition of being allowed to build at all.
