ESP360° · CRC 2026 presentation site · Philadelphia · October 9–11, 2026Email · WhatsApp

60-second explanation

What is ESP360°?

Devices are good at recording numbers. ESP360° is about recording the human decision that sits beside those numbers.

The simplest example

Two people can have the same glucose reading, the same trend arrow and even the same insulin dose, while making that decision from very different human states. One may be rested, confident and following a familiar routine. The other may be exhausted, frightened after a recent low, and unsure whether the sensor is trustworthy.

Every glucose monitor in the world records the same thing for both. The curves are identical. The realities behind them are not.

The device can record the same action for both. ESP360° asks whether the decision context can also be represented as structured data.

What actually gets written down

At the moment of a dose — before the outcome is known — a structured record captures things a sensor cannot see. What was known and what was only assumed. How confident the person was, and in what. What they were afraid of. What competing interpretations they were holding at once. How much cognitive load they were carrying, how much sleep they had, who else was in the room. What they expected to happen next.

None of that is a diary entry. Each item is a defined field with defined values, so it can be counted, compared and audited the same way a glucose reading can.

Why it has to be captured in the moment

Ask someone a day later why they took the dose they took and you get a reconstruction, not a record. Memory rewrites reasoning once the outcome is known. A dose that worked becomes a good decision in retrospect; a dose that did not becomes a mistake. Capturing before the outcome is the whole method.

Common questions

Is this a mood tracker?

No. A mood tracker records how someone feels. This records the structure of a decision — what was known, what was uncertain, what was weighed — at a specific clinical moment.

Does it tell me what dose to take?

No, and it is not designed to. It makes no autonomous recommendations. It is a record, not an advisor.

Does it prove that stress or fatigue causes bad outcomes?

No. A single-subject record can show that a pattern is present and can be represented as data. It cannot establish cause, and nothing here claims to.

Is it scoring me as compliant or non-compliant?

No. The architecture was built partly because that framing is the problem. An override with a good reason behind it is information, not misbehaviour.

Who is it actually for?

In the near term, the people building diabetes technology and clinical AI — because their systems are learning from data with this layer missing. In the long term, patients and clinicians, who would gain a reviewable record of context rather than a compliance score.

What it does not claim. It does not prove causation, replace a clinician, score a person as compliant or non-compliant, or decide what dose anyone should take.

The outcome is part of the record. The reasoning that existed before the outcome should be part of the record too.