Aidoc
Clinical AI platform for radiology and enterprise imaging workflows.
Last updated: June 5, 2026
Back to directoryFDA-cleared autonomous AI diagnostic screening system for more-than-mild diabetic retinopathy in eligible adults with diabetes.
Clinics that want same-visit diabetic retinopathy screening with supported cameras, trained image capture, EHR reporting, and defined referral routing.
Compare within workflow: Medical imaging and radiology · comparison shortlist · source index
Product-specific review. These product-specific signals summarize what the cited sources imply before treating AEYE-DS as safe for a local clinical, operational, or research workflow.
| Regulatory / FDA | Match deployment to the current AEYE-DS 510(k), camera, indication, contraindications, trained-user workflow, eligible adult diabetes population, and local diagnostic-screening rules. |
|---|---|
| Privacy | Review retinal-image capture, identifiers, EHR ordering and result return, de-identified model-improvement use, U.S. hosting, retention by provider agreement, access controls, and BAA or data-processing terms. |
| Evidence | Validate local performance against the clinic's camera, operator skill, image-quality rate, patient demographics, disease prevalence, follow-up capacity, and expectations for non-diabetic eye disease. |
| Workflow | Best governed as a protocolized care-gap closure workflow with eligibility checks, trained capture, report review, referral routing, billing review, and quality monitoring. |
AEYE Health describes AEYE-DS as an FDA-cleared autonomous diabetic-retinopathy screening system for one non-mydriatic image per eye using supported Topcon NW400 and Optomed Aurora cameras; FDA records list AEYE-DS K221183 and K240058, and AEYE privacy materials describe retinal-image, exam-identifier, MRN, and diagnostic-result processing.
Not for: Comprehensive eye exams, glaucoma or other ocular-disease screening, use outside eligible adult diabetes populations, or workflows without referral capacity.
Use these links to confirm current claims, terms, regulatory status, pricing, and deployment requirements.