Digital Eye File

A reusable case record for cleaner specialty lens review.

Foveo uses the term digital eye file for a versioned software record that can hold eye geometry, design parameters, warning records, review notes, artifact hashes, and replay metadata so clinic and lab teams can discuss the same case record.

PurposeReview and repeatability
Current dataSynthetic fixtures only
ArtifactsJSON, STL, PNG, hash

Review Point

What the file contains

The public demo treats the eye file as a structured workflow record. It is designed to keep generated artifacts inspectable, reproducible, and easier to hand off between a clinic and lab review team.

Review Point

Why it matters

A repeatable record can reduce ambiguity when a clinic, doctor, fitter, or lab reviews the same software artifact. The current public implementation uses synthetic data and is not a patient record system.

Review Point

Boundary

The public digital eye file does not store real patient data, prescriptions, protected health information, real scanner exports, or wearable lens approvals.

Fast Answers

Is a Foveo digital eye file a medical record?
No. In the public demo it is a synthetic software artifact record for workflow review.
Can the file regenerate the same software artifact?
The demo demonstrates deterministic replay concepts by recording parameters and hashes for synthetic cases.
Does Foveo accept patient scans today?
No. The public workflow uses synthetic fixtures only.

Search Context

Useful phrases for this page

These terms describe the public software workflow lane. They are not medical, fitting, dispensing, manufacturing, privacy, or regulatory claims.

Start Clean

Review the workflow, not a patient case.

Send only non-confidential collaboration context. Do not send patient records, prescriptions, scans, protected health information, real lens orders, or proprietary methods.

Open the console [email protected]