Six steps, one engine.
A closer look at the six steps that turn a plain-language description into something useful in care.
Most people arrive at care having already told their story several times, in several places, and lost something in each retelling. The first version is the fullest one. Eiralis is built around keeping it.
The engine runs in one pass. A person describes what is happening in their own words. What comes back is a structured account of that description, organized so a clinician can read it quickly and so the person can carry it into the next conversation without starting over.
The six steps
- 01
Listen
Take in what the person said, in their own language, with the context that surrounds it.
- 02
Structure
Turn the description into structured medical context: signs, duration, history, concerns.
- 03
Reason
Apply clinical reasoning to surface what is likely, what is uncertain, and what matters to act on.
- 04
Verify
Check against safety guardrails, red-flag criteria, and intended-use boundaries. Escalate when the situation calls for it.
- 05
Route
Return the assessment to the person and, when they choose, into a clinic, hospital, or provider workflow.
- 06
Learn
Close the loop. Outcomes, feedback, and supervision sharpen the system over time.
What comes out of it
The output is an assessment: a written summary of what was described, what context surrounds it, what the system judged to be uncertain, and what would reasonably come next. It is meant to be read by a person, and it is meant to travel. Nothing in it is a diagnosis, and nothing in it instructs a clinician what to do.
Structured assessment
Not a diagnosis
Red-flag awareness
Human review where the situation calls for it
Guided intake
Not a replacement for a clinician
Auditable by design
Every step logged and reviewable
Where the boundaries are
Step four is the one that matters most. Before anything is returned, the assessment is checked against red-flag criteria and intended-use boundaries. Situations that fall outside what the system should handle on its own are escalated rather than answered, and uncertainty is reported as uncertainty rather than smoothed over.
Eiralis is not for emergencies. In an emergency, contact local emergency services.
The reasoning is recorded at every step, which means an assessment can be reviewed after the fact rather than taken on trust. That is a requirement of the design, not a feature added to it.