Device type · HKI
Camera, Ophthalmic, Ac-Powered
Last checked: Nov 19, 2026Source: openFDAMethods & limitations
Product code
HKI
Ophthalmic
Device class
Class II
FDA decisions since 2015
40
510(k), De Novo and PMA
Adverse event reports
0
Received Nov 1, 2025 to Nov 19, 2026
How FDA classifies it
- Device type
- Camera, Ophthalmic, Ac-Powered
- Product code
- HKI
- Device class
- Class II
- Review panel
- Ophthalmic
- Regulation
- 21 CFR 886.1120
- Specialty
- Ophthalmology
- FDA record
- Classification database entry for HKI
Latest FDA decisions
The 8 newest of 40 since 2015.
- TearView510(k)
K253176 · Decided Jun 22, 2026 · 269 days after receipt
Device type: Camera, Ophthalmic, Ac-Powered (HKI) · Ophthalmology
- Eyer 2510(k)
K251353 · Decided Jan 16, 2026 · 261 days after receipt
Device type: Camera, Ophthalmic, Ac-Powered (HKI) · Ophthalmology
- Fundus On Phone Non Mydriatic (FOP NM-10)Third-party review510(k)
Remidio Innovative Solutions Private Limited
K252120 · Decided Dec 12, 2025 · 158 days after receipt
Device type: Camera, Ophthalmic, Ac-Powered (HKI) · Ophthalmology
37 more FDA decisions with a free account
Reports received
0
Received Nov 1, 2025 to Nov 19, 2026
Malfunction reports
0
Injury reports
0
Death reports
0
Adverse event reports received per month
By the date FDA received each report, stacked by event type. The newest month is incomplete.
- Malfunction
- Injury
- Death
- Other
View as table
| Month | Malfunction | Injury | Death | Other |
|---|---|---|---|---|
| Dec 23 | 0 | 0 | 0 | 0 |
| Jan 24 | 0 | 0 | 0 | 0 |
| Feb 24 | 0 | 0 | 0 | 0 |
| Mar 24 | 0 | 0 | 0 | 0 |
| Apr 24 | 0 | 0 | 0 | 0 |
| May 24 | 0 | 0 | 0 | 0 |
| Jun 24 | 0 | 0 | 0 | 0 |
| Jul 24 | 0 | 0 | 0 | 0 |
| Aug 24 | 0 | 0 | 0 | 0 |
| Sep 24 | 0 | 0 | 0 | 0 |
| Oct 24 | 0 | 0 | 0 | 0 |
| Nov 24 | 0 | 0 | 0 | 0 |
| Dec 24 | 0 | 0 | 0 | 0 |
| Jan 25 | 0 | 0 | 0 | 0 |
| Feb 25 | 0 | 0 | 0 | 0 |
| Mar 25 | 0 | 0 | 0 | 0 |
| Apr 25 | 0 | 0 | 0 | 0 |
| May 25 | 0 | 0 | 0 | 0 |
| Jun 25 | 0 | 0 | 0 | 0 |
| Jul 25 | 1 | 0 | 0 | 0 |
| Aug 25 | 0 | 0 | 0 | 0 |
| Sep 25 | 0 | 0 | 0 | 0 |
| Oct 25 | 0 | 0 | 0 | 0 |
| Nov 25 | 0 | 0 | 0 | 0 |
| Dec 25 | 0 | 0 | 0 | 0 |
| Jan 26 | 0 | 0 | 0 | 0 |
| Feb 26 | 0 | 0 | 0 | 0 |
| Mar 26 | 0 | 0 | 0 | 0 |
| Apr 26 | 0 | 0 | 0 | 0 |
| May 26 | 0 | 0 | 0 | 0 |
| Jun 26 | 0 | 0 | 0 | 0 |
| Jul 26 | 0 | 0 | 0 | 0 |
| Aug 26 | 0 | 0 | 0 | 0 |
| Sep 26 | 0 | 0 | 0 | 0 |
| Oct 26 | 0 | 0 | 0 | 0 |
| Nov 26 | 0 | 0 | 0 | 0 |
Manufacturers named most often
Last 12 months. Bigger sellers get more reports. This is not a ranking of safety.
No manufacturers to rank.
Device problems as coded
Last 12 months. FDA's terms. A report can carry several.
No device problems coded.
Patient problems as coded
Last 12 months. FDA's terms. A report can carry several.
No patient problems coded.
Recent recalls
From FDA's recall database. FDA lists each recalled product separately, so one recall can appear several times. A recall is often a correction or a labeling change, not a removal from the market.
Z-0939-2019 · Started Dec 20, 2018 · Posted by FDA Feb 25, 2019
Reason given: Certain configurations of Merge Eye Station hardware may result in electrical output that exceeds the allowable limits for medical devices. Leakage current was found to exceed allowable limits in earth leakage current, touch current in a single fault condition (of open ground) and patient leakage current in a single...
Cause as FDA categorized it: Device Design
Z-0009-2018 · Started Jul 27, 2017
Reason given: FDA determined that a 510(k) is needed for the Vault Mapping software (also known as Lens Fitting).
Cause as FDA categorized it: Other
Z-1017-2017 · Started Dec 9, 2016
Reason given: This recall has been initiated due to an issue related to the potential accidental deletion of record(s) by an Eye Station user.
Cause as FDA categorized it: Software design
6 more recall records with a free account
For information only. Nothing on this page is investment, legal, tax or medical advice, and nothing here is an offer to sell or a solicitation of an offer to buy any security. The data comes from public government sources, which can be incomplete, delayed or wrong. Check the original record before relying on it.