Digital eye-file history
Preserve source metadata, design specs, warning records, review notes, artifacts, and replay hashes in one case trail.
Current Scope
Foveo starts with the record, not the clinical claim.
The first product focus is the digital eye-file layer: source context, artifact review, warning history, packet handoff, and replayable case memory for specialty lens teams.
Product Focus
One commercial surface first: the case record.
Artifact packet
Show the STL, JSON spec, cross-section, warnings, and handoff state without asking teams to chase loose files.
Continuity proof
Regenerate or compare synthetic artifacts from the saved record so follow-up discussions start from the same version.
Boundary
The design engine is a synthetic demonstration today.
Foveo does not currently diagnose, prescribe, fit, dispense, manufacture, approve, or fabricate wearable contact lenses. The public demo uses synthetic data only.
- No patient data or protected health information.
- No real scanner exports through the public site.
- No clinical validation, regulatory clearance, or freedom-to-operate claim.
- No wearable-lens printing with desktop resin equipment.
Partner Review
What Foveo wants to learn next.
Where does the record break?
Which remake, lab message, scan, note, or follow-up detail disappears between visits?
What should the packet contain?
Which files, warnings, geometry summaries, and status fields make a case easier to review?
What is safe to evaluate?
Which synthetic or approved non-PHI fixtures would make this workflow useful before any clinical path?