Digital eye-file concepts, synthetic topography-style fixtures, STL previews, design specs, warning records, cross-sections, and replay hashes.
Legal Boundaries
Clear product limits for the public Foveo demo.
Foveo Labs is building specialty lens workflow software. The public website and console demonstrate synthetic, non-clinical software artifacts only. This page is not legal advice, medical advice, regulatory clearance, privacy certification, or a freedom-to-operate opinion.
Public Demo
What Foveo can show today.
Non-confidential discussions with doctors, technicians, labs, universities, scanner groups, and software partners about what the workflow should include.
Architecture for approved exports, clinic-owned files, or formal integrations. The public site does not ingest real scanner exports.
Authenticated notes, file records, case status, tracking references, and audit history are product direction for a private system, not public upload features today.
No Clinical Claims
What Foveo does not claim.
- No diagnosis, treatment, medical advice, prescription decision, clinical fit approval, dispensing, or wearable lens release.
- No claim that synthetic results predict real patient outcomes.
- No claim that any file is ready for fabrication, patient use, FDA review, HIPAA compliance, or commercial manufacturing.
- No request for patients, doctors, labs, or universities to upload patient scans, prescriptions, medical records, or protected health information through the public site.
Data Boundary
No patient data on the public site.
Public forms are for general, non-confidential workflow context only. A real clinic workflow involving patient data would require authentication, role-based access, privacy review, retention policy, security controls, contracts, and any required healthcare privacy analysis before accepting protected health information.
IP Boundary
Build interoperability without copying competitors.
Foveo may review public documentation, support user-provided exports, and pursue formal partner integrations. It should not scrape private software, bypass access controls, clone proprietary workflows, copy patented methods, or claim partner integrations without permission.
Before Real Use
What must happen before clinical, patient, or manufacturing workflows.
Terms, consent model, privacy policy, data retention, contracts, access controls, and healthcare privacy analysis.
Qualified review of whether any software function is regulated, non-device software, clinical decision support, or another category.
Patent landscape, license boundaries, Waterloo or other university commercialization paths, and do-not-copy implementation rules.
Formal verification, test cases, audit logs, security controls, data provenance, lab requirements, and documented failure modes.
Public References
Why the boundaries matter.
FDA pages on device software functions and clinical decision support software are relevant to software-claim discipline. HHS HIPAA Privacy Rule and de-identification pages are relevant before any real patient data strategy. These references are not a substitute for professional review.