AEYE-DS
AEYE Health, Inc. • Ophthalmic • 11/10/2022
Device Purpose
AEYE-DS is an artificial intelligence-based software device intended for use by healthcare providers to automatically screen for more than mild diabetic retinopathy (mtmDR) in diabetic adults using fundus images from a Topcon NW400 camera. Its methodology relies on AI analysis of retinal images, with clinical studies demonstrating high sensitivity and specificity, supporting its utility for detecting mtmDR.
Summary
The AEYE-DS is a retinal diagnostic software device utilizing artificial intelligence to automatically detect more than mild diabetic retinopathy (mtmDR) in adults diagnosed with diabetes who have not previously been diagnosed with the condition. The system operates with a Topcon NW400 fundus camera, where a local client module captures retinal images (either one or two per eye) and transmits them via a secure internet connection to a remote server. The server hosts service and analytics modules that process these images to identify disease features, returning a diagnostic result (mtmDR detected, not detected, or insufficient quality) to the client for healthcare provider review. The software architecture includes components for client interaction, service processing, analytics, reporting/archiving, and system security. A pivotal clinical study involving 531 subjects across 8 sites demonstrated the device's performance. When using one macula-centered image per eye, the AEYE-DS showed a sensitivity of 92.98% and specificity of 91.36% for mtmDR detection. With two images per eye (macula-centered and optic disc-centered), sensitivity was 94.74% and specificity was 88.64%. Imageability was high at over 99%, with most subjects not requiring pupil dilation. Precision studies showed high intra-operator, between-operator, and between-device reproducibility. A human factors validation study confirmed that novice operators found the device easy to use after initial training, successfully submitting images and obtaining diagnostic reports.
AI Regulatory Concerns
Powered by
Jev reads the full FDA letter and returns calibrated concern probabilities per regulatory category. These are AI estimates, not regulatory advice.
Keywords
Device Metadata
Relevant Clinical Questions
- Q1. How does the AEYE-DS algorithm specifically differentiate features of 'more than mild diabetic retinopathy' from milder forms or normal retinal presentations?; What was the rate of 'insufficient quality' images initially, and how did this change with the maximum of 6 image submission attempts by novice operators?; Given the slightly lower specificity with the 2-images-per-eye protocol (88.6%) compared to the 1-image-per-eye protocol (91.4%), what are the clinical considerations or trade-offs when deciding which protocol to use?; How does the performance of the AEYE-DS device vary with different demographic subgroups beyond those analyzed (e.g., specific comorbidities, duration of diabetes categories not tested)?; What are the specific cybersecurity measures implemented in the AEYE-DS system, particularly concerning the transfer and storage of patient fundus images on remote servers?
Risk Classification
ESL AnalysisFDA Class II via 510(k) pathway; IEC 62304 Class B (software safety classification); Authorized before §524B enforcement
Learn how Parasoft automates IEC 62304 compliance testing →Cybersecurity Evidence
Powered by SBOMator™Based on AI-generated device summaries, not the full FDA submission. Items not detected here may still be present in the complete submission package.
Supply Chain BOM Evidence
Based on the CycloneDX / OWASP ECMA-424 xBOM ecosystem. Detection is from the AI-generated summary.
Analysis:
• Analysis is based on the AI-generated device summary, not the full FDA submission package. Click "Analyze Full FDA PDF" below to scan the actual submission document.
• Evidence of ML-BOM, SaaSBOM, HBOM detected in AI-generated device summary.
• This device was authorized before §524B took effect. Cybersecurity evidence requirements were less prescriptive at the time.
• Postmarket cybersecurity monitoring plan not clearly documented in AI-generated device summary.
• Not detected in AI-generated device summary: SBOM, CBOM, VDR/VEX, OBOM. These may be present in the full FDA submission.
Preparing a similar submission?
ESL takes complete ownership of your software evidence work - SBOM & CVE remediation with SBOMator™, static analysis & unit testing with Parasoft, traceability, and full IEC 62304 lifecycle support.
Assess Your Readiness →Or contact ESL directly