Scanner-Neutral Workflow

A clean path toward importer research without real scanner uploads.

Foveo is not tied to one scanner or topographer in the public prototype. The near-term work is defining a neutral internal schema and testing it with synthetic fixtures.

Current inputsSynthetic fixtures
Future focusNeutral schema
Public limitNo real exports

Review Point

Why neutral matters

Specialty lens work can involve different measurement systems, exports, and lab handoff expectations. A neutral software layer can make those differences easier to reason about, but only after data policy and advisor review are in place.

Review Point

Current research lane

The public scanner sandbox validates synthetic fixture shapes that resemble common export concerns without using private vendor files or patient scans.

Review Point

Safe collaboration request

Foveo can discuss export expectations and workflow gaps with labs or clinicians, but the public site asks collaborators not to send patient data or proprietary files.

Fast Answers

Does Foveo import real scanner files today?
No. Public scanner work uses synthetic fixtures only.
Why not build directly around one scanner?
A neutral model keeps the software flexible and reduces early dependence on one vendor format.
Can a lab discuss its workflow?
Yes, as non-confidential process feedback with no patient records, prescriptions, scans, or proprietary methods.

Search Context

Useful phrases for this page

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

Start Clean

Review the artifact, 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]