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.

Scanner-Neutral Workflow

A clean path toward scanner-neutral workflow without real scanner uploads.

Foveo is not tied to one scanner or topographer in the public demo. 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 workflow review are in place.

Avoids assuming one scanner is the entire market.
Keeps geometry handling separated from vendor-specific details.
Lets test fixtures cover missing points, noise, and coverage differences.
Protects the codebase from proprietary implementation shortcuts.

Review Point

Current workflow lane

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

Schema-first elevation grids.
Coverage and unit validation.
Dirty-scan fixture planning.
No authenticated portal scraping.

Working Proof

Synthetic source fixtures now generate real review artifacts.

Foveo can normalize synthetic Eaglet-style, Pentacam-style, and Medmont-style fixtures into one internal elevation grid, then produce the same artifact family used by the console.

Neutral Foveo grid from synthetic source records.
Design spec with source and normalization warnings.
Cross-section image, STL artifact, and replayable eye file.
Deterministic reorder proof for the generated fixture STL.

Review Point

Safe workflow 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.

Discuss field names and workflow needs at a high level.
Use public documentation where available.
Keep real data out until policies exist.
Document unknowns separately from implementation decisions.

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 workflow lane. They are not medical, fitting, dispensing, manufacturing, privacy, or regulatory claims.

scanner neutral workflow
topography workflow planning
eye scanner export schema
synthetic scanner fixtures
corneal topography importer
ophthalmic data workflow

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]