Permitted export
A synthetic fixture, public documented format, or written-permission non-PHI export. No patient identifiers and no confidential files through the public site.
Partners
Make eye-surface records portable before the case gets lost.
Foveo is building a neutral record layer around specialty lens workflows. For scanner OEMs, practice software, design tools, and labs, the first conversation is not an API ask. It is a frame, quality, and provenance contract.
Integration Shape
What an integration actually requires.
Adapter interface
A parser must sniff the file, declare the coordinate frame, normalize units to millimeters, log transforms, and return a valid Eye Surface Record.
Conformance suite
Ten tests cover frame declaration, unit correctness, stable hashes, missing data, PHI blocking, typed refusal, and no network access during parse.
The Non-Negotiable Line
If the coordinate frame cannot be declared, the adapter stops.
Origin, x/y/z polarity, handedness, units, and laterality must be explicit. A guessed frame is not a convenience; it is a silent wrong-record generator. Foveo's adapter contract is built to halt rather than hide that uncertainty.
How To Start
A useful first conversation is small and technical.
- Review the public ESR v0.1 spec and conformance requirements.
- Tell Foveo what customers can actually export today and where that file goes next.
- Use one approved non-PHI fixture to test whether ESR captures the real workflow state.
- Decide whether a formal integration is worth scoping.