OVISTA isn't tied to one piece of hardware, and it isn't built to be a black box. Here's how the platform is put together, at a conceptual level.
OVISTA is designed to work with a range of eye-tracking hardware — today's clinical-grade trackers, and future ones — rather than being built around a single vendor. That matters for a screening tool meant to sit in ordinary primary care settings: it shouldn't force a clinic into one supplier, one price point, or one generation of equipment.
The tasks OVISTA measures are sensitive to milliseconds. So the session itself runs locally, on-device, rather than depending on a live connection to a remote server to time each trial — timing precision and patient responsiveness shouldn't be at the mercy of network conditions. It's also a simpler, more private way to handle a clinical session by default.
A clinician doesn't need a spreadsheet of gaze coordinates. They need a clear, structured report: the risk band, the metrics behind it, and enough context to decide on next steps. That's the actual output OVISTA is built to produce.
The same five-minute session produces two very different views — deliberately. One is designed to keep a patient calm and focused. The other is designed to give a clinician a fast, structured read.
A single moving target on a plain, low-contrast background. No instructions, no numbers, no clutter — nothing to distract from the task itself.
A session list, the risk-band result, and the metrics behind it — laid out for a fast clinical read, not a data-science review.
The platform is one piece. The screening protocol and clinician workflow are the other.