Tracking an IOP Spike

A spike is a meaningful jump in your eye pressure. When one happens, ODyn gives you a guided workflow to respond and — just as important — to capture what caused it, so the correlation engine can learn from the event.

This guide covers flagging a spike, applying drops or monitoring, re-measuring, identifying the cause, and resolving.

Flag a spike

1. Log an IOP reading that's above your normal range. 2. When ODyn asks whether the reading looks elevated, choose to track it as a spike.

What to expect: a spike banner appears and guides the rest. You can also start a track manually if you suspect a spike the first reading didn't catch.

Apply drops — or monitor without them

1. If you take drops for a spike, choose Log drops applied and record them. A re-measure timer starts automatically. 2. If you're not using drops this time, choose Monitor without drops — ODyn keeps tracking and opens the trigger box, without a drop timer.

Re-measure

1. Take three quick re-measures a few minutes apart — the timer prompts each one. 2. Then re-measure about every 30 minutes until you're back to baseline. 3. Can't measure right now? Skip a re-measure or end reminders — neither closes the spike.

What to expect: this captures how fast and how far your pressure moves, which matters as much as the peak.

Identify what caused it

1. In the Identify what caused this spike box, add suspects. 2. For packaged items, scan them; for anything else, add a non-packaged item. 3. Mark a confirmed cause if you already know it.

What to expect: your suspects link to this spike so ODyn can correlate them. You don't have to finish in the moment — you can return to the event from your history and add more later.

Resolve

1. When your pressure returns to baseline, choose Mark resolved. 2. Add any final notes.

What to expect: the spike becomes a permanent record in your history — the curve, the suspects, and the analysis — that you can revisit anytime.