EyeBOX
Oculogica, Inc. • Neurology • 07/31/2019
Device Purpose
The EyeBOX Model OCL 02 is an eye-tracking device intended as an adjunctive tool for diagnosing concussion (mTBI) in individuals aged 5 to 67 within one week of head injury. It operates by capturing high-frequency gaze data during a visual tracking task and employs a proprietary algorithm to analyze these movements, generating a 'BOX score' to aid in identifying ocular motor patterns potentially associated with concussion.
Summary
The EyeBOX, Model OCL 02, is an eye-tracking device designed as an aid in the diagnosis of concussion, also referred to as mild traumatic brain injury (mTBI). It is intended for use with patients aged 5 through 67 years within one week of a head injury, functioning as a supplementary tool to a standard neurological assessment. The system comprises a host PC with an integrated touchscreen, an eye-tracking camera, an LCD stimulus screen for presenting visual tasks, and a head-stabilizing rest (chin and forehead rest) for the patient. The core of its functionality lies in a data processing algorithm engineered to detect subtle changes in eye movements that may result from a concussion. During the assessment, which takes approximately 4 minutes, the patient follows a video that moves around the perimeter of the LCD monitor. A high-speed near-infrared (IR) camera records the patient's gaze positions 500 times per second. This collected data is then automatically post-processed to produce a 'BOX score.' A negative EyeBOX classification suggests eye movements consistent with the absence of concussion, while a positive classification indicates eye movements that could be present in individuals both with and without concussion. The Model OCL 02 is a tabletop version with WiFi capability, designed for seated patients only, and includes software changes for device licensing. Crucially, it retains the same eye-tracking camera, optical path, and the fundamental EyeBOX algorithm for data processing and BOX score generation as its predicate model.
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. What is the sensitivity and specificity of the EyeBOX (Model OCL 02) in differentiating between patients with and without concussion, particularly in the 5-67 age range specified?; How does the 'BOX score' quantitatively represent eye movement changes, and what specific kinematic parameters or patterns does the algorithm analyze?; Could the EyeBOX be adapted or validated for assessing concussion severity or tracking recovery progress over time, beyond the initial one-week post-injury window?; What impact, if any, do pre-existing ophthalmological conditions, medications affecting eye movement, or patient fatigue have on the accuracy of the EyeBOX assessment?; How does the performance of the EyeBOX compare to other objective concussion assessment tools (e.g., neuroimaging, other biomarkers) in terms of diagnostic accuracy and clinical workflow integration?
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, 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, SaaSBOM, 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