K133892 · Optovue, Inc. · HLI · Mar 19, 2014 · Ophthalmic
Device Facts
Record ID
K133892
Device Name
IVUE 500
Applicant
Optovue, Inc.
Product Code
HLI · Ophthalmic
Decision Date
Mar 19, 2014
Decision
SESE
Submission Type
Traditional
Regulation
21 CFR 886.1570
Device Class
Class 2
Indications for Use
The iVue 500 with normative database is an optical coherence tomography system intended for in vivo imaging, axial cross-sectional, three-dimensional imaging and measurement of anterior and posterior ocular structures.
Device Story
iVue 500 is a compact, desktop optical coherence tomography (OCT) system for in vivo imaging of ocular structures. Device captures axial cross-sectional and three-dimensional images of retina, retinal nerve fiber layer, ganglion cell complex, optic disc, cornea, and anterior chamber. Operated by technicians in office settings via touchscreen or mouse interface. System utilizes software-assisted motorized alignment to position scanner head relative to patient's pupil and working distance. Output includes high-resolution tomographic images and quantitative measurements compared against a normative database. Clinicians use these outputs to aid in diagnosis, documentation, and management of ocular health and diseases. Redesign from predicate focuses on improved form factor and user interface for clinical workflow efficiency.
Clinical Evidence
Bench testing only. Testing verified design modifications, specifically the software-assisted motorized alignment system. Bench tests using two model eyes confirmed the device's ability to align the scanner head to the pupil and maintain working distance within ±1mm tolerance for both retina and cornea modes. No clinical data was required or presented.
Technological Characteristics
Non-invasive OCT system; micrometer-range resolution; desktop form factor; software-assisted motorized alignment; touchscreen/mouse interface; electrical safety and emissions compliant.
Indications for Use
Indicated for adult population to aid in diagnosis, documentation, and management of ocular health and diseases. Provides non-contact, high-resolution tomographic imaging and measurement of anterior and posterior ocular structures, including retina, retinal nerve fiber layer, ganglion cell complex (GCC), optic disc, cornea, and anterior chamber. Includes quantitative comparison of retinal nerve fiber layer, GCC, and optic disc measurements to a normative database.
Regulatory Classification
Identification
An ophthalmoscope is an AC-powered or battery-powered device containing illumination and viewing optics intended to examine the media (cornea, aqueous, lens, and vitreous) and the retina of the eye.
Special Controls
*Classification.* Class II (special controls). The device, when it is an AC-powered opthalmoscope, a battery-powered opthalmoscope, or a hand-held ophthalmoscope replacement battery, is exempt from the premarket notification procedures in subpart E of part 807 of this chapter subject to the limitations in § 886.9.
{0}------------------------------------------------
## 510(k) Summary Optovue iVue 500 K133892
MAR 1 9 2014
This 510(k) summary for the iVue 500 is submitted in accordance with the requirements of SMDA 1990 and 21 CFR 807.92
| Category | Comments |
|---------------------------------|---------------------------------------------------------------------------------------------------------|
| Sponsor: | Optovue, Inc.<br>2800 Bayview Pkwy<br>Fremont, CA 94538 |
| Correspondents: | Michael Sarrasin, Esq.,<br>VP, Regulatory Affairs and Quality Assurance<br>michael_sarrasin@optovue.com |
| Manufacturer: | Optovue, Inc.<br>2800 Bayview Parkway<br>Fremont, CA 94538 |
| Device Common Name: | Optical Coherence Tomography (OCT) System |
| Device Proprietary Name: | iVue 500 |
| Device Classification | CI II, HLI, 21 CFR §886.1570 |
| Predicate Device | IVue with NDB, K121739 |
| Predicate Device Manufacturer | Optovue, Inc. |
| Predicate Device Classification | CI II, HLI, 21 CFR §886.1570 |
Date Summary was Prepared: January 7, 2014
Device Description: The iVue 500 is a modification of its predicate device iVue with Normative Database (NDB) (K121739). The intended use, system performance, sub-assemblies, and key components of the iVue with NDB are all the same as the iVue with NDB. The intent of this redesign was to make the iVue a more compact desktop device, so it is more convenient to use and set-up in a lypical office. Additionally operation via touchscreen or mouse driven technology, makes it simpler for a technician to use.
- Intended Use: The iVue 500 with normative database is an optical coherence tomography system intended for in vivo imaging, axial crosssectional, three-dimensional imaging and measurement of anterior and posterior ocular structures.
- Indications for Use: The iVue 500 with normative database is a non-contact, high resolution tomographic imaging device. It is intended for in vivo imaging, axial cross-sectional and three-dimensional imaging and measurement of anterior and posterior ocular structures,
{1}------------------------------------------------
including retina, retinal nerve fiber layer, ganglion cell complex (GCC), optic disc, cornea, and anterior chamber of the eye. The iVuc 500 with normative database is a quantitative tool for the comparison of retinal nerve fiber layer, ganglion cell complex, and optic disc measurements to a database of known normal subjects. The iVuc 500 with normative database is indicated for use as a device to aid in the diagnosis, documentation, and management of ocular health and diseases in the adult population. (identical to predicate device)
- Technological Characteristics: The iVue 500 is a non-invasive device for imaging the cornea, anterior chamber, and retinal tissue structure with micrometer range resolution.
- Comparison to Predicate Device: The iVue 500 is a modification of its predicate device iVue with Normative Database (NDB) (K121739). The intended use, system performance, sub-assemblies, and key components of the iVue 500 with NDB are all the same as the iVue with NDB.
| Device | Predicate | Current |
|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|
| 510(k) Reference: | K121739 | K133892 |
| Intended Use: | The iVue with Normative<br>Database is an optical<br>coherence tomography<br>system intended for in vivo<br>imaging, axial cross-<br>sectional, three-<br>dimensional imaging and<br>measurement of anterior<br>and posterior ocular<br>structures. | Same |
| Device Description: | Optical Coherence<br>Tomography (OCT)<br>System | Same |
| Device Common Name: | Optical Coherence<br>Tomography (OCT)<br>System | Same |
| Device Classification: | Class II HLI<br>(21 CFR 886.1570) | Same |
| Manufacturer: | Optovue, Inc. | Same |
Summary of Testing: Testing was performed to verify design, and showed there were no new questions of safety or effectiveness with the subject device, This testing included electrical safety testing, electrical emissions testing, as well as bench. Bench testing demonstrated that the
{2}------------------------------------------------
iVue 500 is able to align to appropriate working distance on both left and right eyes within the predefined acceptance criteria.
The bench test of iVue 500 utilizing 2 model eyes provides evidence that the software assisted motorized iVue 500 is able to complete the initial alignment of moving the scanner head to working position and to align the scanner head with the pupil within ±1mm tolerance. These are the general requirements to align a scanner to be able to capture an OCT image. Also the iVue 500 is able to move scanner head between right and left eyes.
| Retina<br>Mode | Range | Average | Criteria | Results |
|---------------------|-----------------|---------|----------|---------|
| Working<br>distance | 20.3-22mm | 21.3 | +/- 1mm | Pass |
| centering | 0-.2mm | n/a | +/- 1mm | Pass |
| Pupil<br>distance | 66.1-<br>66.6mm | n/a | +/- 1mm | Pass |
| Cornea<br>Mode | Range | Average | Criteria | Results |
|---------------------|-----------------|---------|----------|---------|
| Working<br>distance | 16.4-<br>17.3mm | 16.7 | +/- 1mm | Pass |
| centering | 0-.1mm | n/a | +/- 1mm | Pass |
| Pupil<br>distance | 65.7-<br>66.8mm | n/a | +/- 1mm | Pass |
Conclusion:
As described in this 510(k) Summary, all necessary testing and analyses were completed on the iVue 500 to ensure that the device is substantially equivalent to the identified predicate device.
{3}------------------------------------------------
DEPARTMENT OF HEALTH & HUMAN SERVICES
Public Health Service
Food and Drug Administration 10903 New Hampshire Avenue Document Control Center - WO66-G609
Silver Spring, MD 2093-0002
March 19, 2014
Optovuc, Inc. % Mr. Michael Sarrasin, Esq. Vice President, Regulatory Affairs & Quality Assurance 2800 Bayview Drive Fremont, CA 94538
Rc: K133892
Trade/Device Name: iVue 500 Regulation Number: 21 CFR 886.1570 Regulation Name: Ophthalmoscope Regulatory Class: Class II Product Code: HILI Dated: February 19, 2014 Received: February 20, 2014
Dear Mr. Sarrasin:
We have reviewed your Section 510(k) premarket notification of intent to market the device referenced above and have determined the device is substantially equivalent (for the indications for use stated in the enclosure) to legally marketed predicate devices marketed in interstate commerce prior to May 28, 1976, the enactment date of the Medical Device Amendments, or to devices that have been reclassified in accordance with the provisions of the Federal Food, Drug, and Cosmetic Act (Act) that do not require approval of a premarket approval application (PMA). You may, therefore, market the device, subject to the general controls provisions of the Act. The general controls provisions of the Act include requirements for annual registration, listing of devices, good manufacturing practice, labeling, and prohibitions against misbranding and adulteration. Please note: CDRH does not evaluate information related to contract liability warranties. We remind you, however, that device labeling must be truthful and not misleading.
If your device is classified (see above) into either class II (Special Controls) or class III (PMA), it may be subject to additional controls. Existing major regulations affecting your device can be found in the Code of Federal Regulations, Title 21, Parts 800 to 898. In addition, F12A may publish further announcements concerning your device in the Eederal Register.
Please be advised that FDA 's issuance of a substantial equivalence determination does not mean that FDA has made a determination that your device complies with other requirements of the Act or any Federal statutes and regulations administered by other Federal agencies.
{4}------------------------------------------------
Page 2 - Mr. Michael Sarrasin, Esg.
You must comply with all the Act's requirements, including, but not limited to: Registration and listing (21 CFR Part 807); labeling (21 CFR Part 801); medical device reporting (reporting of medical device-related adverse events) (21 CFR 803); good manufacturing practice requirements as set forth in the quality systems (OS) regulation (21 CFR Part 820); and if applicable, the clectronic product radiation control provisions (Scctions 531-542 of the Act); 21 CFR 1000-1050.
If you desire specific advice for your device on our labeling regulation (21 CFR Part 801), please contact the Division of Small Manufacturers, International and Consumer Assistance at its tollfree number (800) 638-2041 or (301) 796-7100 or at its Internet address
http://www.lda.gov/MedicalDevices/ResourcesforYou/Industry/default.htm. Also, please note the regulation entitled, "Misbranding by reference to premarket notification" (21CFR Part 807,97). For questions regarding the reporting of adverse events under the MDR regulation (21 CFR Part 803), please go to
http://www.fda.gov/MedicalDevices/Safety/ReportalProblem/default.htm for the CDRH's Office of Surveillance and Biometrics/Division of Postmarket Surveillance.
You may obtain other general information on your responsibilities under the Act from the Division of Small Manufacturers, International and Consumer Assistance at its toll-free number (800) 638-2041 or (301) 796-7100 or at its Internet address
http://www.fda.gov/MedicalDevices/ResourcesforYou/Industry/default.htm.
Sincerely yours.
## Deborah L. Falls -S
for Malvina B. Eydelman, M.D. Director Division of Ophthalmic and Ear. Nose and Throat Devices Office of Device Evaluation Center for Devices and Radiological Health
Enclosure
{5}------------------------------------------------
#### DEPARTMENT OF HEALTH AND HUMAN SERVICES Food and Drug Administration
### Indications for Use
Form Approved: OMB No. 0910-0120 Expiration Date: December 31, 2013 See PRA Statement on last page.
#### 510(k) Number (if known)
K133892
Device Name
iVue 500
Indications for Use (Describe)
The iVue 500 with normative database is a non-contact, high resolution tomographic imaging device. It is intended for in vivo imaging, axial cross-sectional and three-diment of anterior and posterior and posterior ocular structures, including reinal nerve fiber layer, ganglion cell complex (GCC), optic disc, cornea, and anterior chamber of the eye. The iVue 500 with normalive database is a quantitative tool for the comparison of retinal nerve fiber layer, ganglion cell complex, and optic disc measurements to a database of known normal subjects. The iVue 500 with normative database is indicated for use as a device to aid in the diagnosis, documentation, and management of ocular health and diseases in the adult population.
Type of Use (Select one or both, as applicable)
[x] Prescription Use (Part 21 CFR 801 Subpart D)
] Over-The-Counter Use (21 CFR 801 Subpart C)
#### PLEASE DO NOT WRITE BELOW THIS LINE - CONTINUE ON A SEPARATE PAGE IF NEEDED.
FOR FOR FOR FOR FOR FOR FOR FOR FOR FOR FOR FOR FOR FOR FOR FOR FOR FOR FOR FOR Concurrence of Center for Devices and Radiological Health (CDRH) (Signature)
# Rahul K. Ram -S (Affiliate) 2014.03.13 15:02:55 -04'00'
FORM FDA 3881 (9/13)
Predicate graph will load when search results are available.
Embedding visualization will load when search results are available.
PDF viewer will load when search results are available.
Loading panels...
Select an item from Submissions
Click any panel, subpart, regulation, product code, or device to see details here.
Section Matches
Results will appear here.
Product Code Matches
Results will appear here.
Special Control Matches
Results will appear here.
Loading collections...
Loading
My Alerts
You will receive email notifications based on the filters and frequency you set for each alert.
Sort by:
Create Alert
Search Filters
Agent Token
Create a read-only bearer token for Claude, ChatGPT, or other agents that can call HTTP APIs.
Copy this now. It will not be shown again.
Connected apps
Apps you authorized through browser sign-in. Disconnecting revokes their access immediately.
Learn the FDA Browser
Two short videos show you everything — or skip straight to the written tutorial if you'd rather read. You can reopen this any time from the Tutorial button in the top bar.
Part 1 — Search, results, and everyday workflows 16 min
Part 2 — Embeddings: the galaxy map 3 min
1. Search: exact and fuzzy
Type a phrase like "coronary artery calcification" into the search box. You get two kinds of results. Exact results match the literal phrase — prefix searches work ("coronary artery calcificati") but suffix searches do not. Fuzzy results match on the meaning and intent of your phrase rather than the exact words, and are sorted by relevance score. Hover over the Exact or Fuzzy badge on any row to see exactly why it matched.
Use the checkboxes above the results to narrow: SaMD keeps only software-only devices, AI / ML keeps only devices with AI.
Exact vs. fuzzy search: what's the difference?
Exact matches on the literal phrase (prefix search works, suffix does not). Fuzzy matches on the meaning and intent of the phrase rather than the exact words. Hover over the badge on any row to see why it matched.
You search "coronary artery calcification" and want only software devices with AI. What two filters do you apply?
Narrow by SaMD (software-only devices), then narrow by AI/ML (devices with AI).
2. The results table
Scroll right in the results table. The intended use is extracted for you — no need to open the PDF. The device story gives a high-level snapshot of what the device does and how it's used. The AI Performance sub-table shows each output name, acceptance criteria, observed values, and development/test dataset descriptions — the same format Innolitics uses for regulatory strategy outputs, and the fastest high-level fingerprint of an AI device. It is AI-generated but has been very reliable in practice.
Where do you find a device's intended use without opening the PDF?
Scroll right in the search results table. The intended use column is extracted for you; no need to dig into the 510(k) summary PDF.
What does the AI Performance sub-table show, and why is it useful?
Output name, acceptance criteria, observed values, development dataset description, and test dataset description. It's the same format we use for regulatory strategy output and Fast 510(k) input, and the fastest high-level fingerprint of an AI device. AI-generated but reliable in practice.
3. Judging fuzzy relevance
Fuzzy results trail off in relevance as you scroll. Use three signals to decide how far down to go: the fuzzy badge explanations, the intended use column, and whether your target output (e.g., Cobb angle) still appears in the AI Performance sub-table. Once it stops appearing, you're past the relevant zone. A top hit with a low score (~0.4) and a stretched explanation is a hint the closest predicates are far away — the project may be headed for De Novo. Note the fuzzy search is a pattern match: it doesn't handle negation ("not") well, and hardware devices can appear — filter by SaMD/AI ML to cut them.
How do you judge how far down fuzzy search results to go?
Use the relevancy signals: the fuzzy badge explanations, the intended use column, and whether the target output (e.g., Cobb angle) still appears in the AI Performance sub-table. Once it stops appearing, results are trailing off in relevancy.
4. Device detail page: chat and citations
Click a device name to open its detail page: device facts on the left, a chat window on the right. Ask something like "Describe the training data". The answer carries little citation bubbles — click one to jump to the highlighted passage in the source PDF, so you can verify every AI answer against the document. There's also a Download PDF button for sharing.
How do you verify an AI chat answer on the device detail page?
Click the citation bubbles to jump to the relevant highlight in the source document.
Reading rule for every project: how many summaries do you read in full?
At least the three most relevant 510(k) or De Novo summaries, in full. After that, use targeted chat questions to confirm your memory quickly. The tool supports this professional habit — it doesn't replace it.
5. Side-by-side comparison
Select multiple rows in the results table (aim for under ~10), then open the PDF Viewer tab. Ask one question — it goes to all selected devices in parallel, each with citations. This is the fastest way to compare and contrast devices: training data, PCCP scope, how they handled adding new scanners, and so on.
What does the side-by-side PDF viewer mode do?
Select multiple devices, open the PDF viewer tab, and ask one question (e.g., "Describe the training data"). It queries all selected devices simultaneously with citations, so you can compare and contrast quickly.
6. Collections
With rows selected, go to the Collections tab and create a labeled collection (e.g., "Cobb Angle Project"). Reload that selection any time — before a client call, pull up the collection and ask questions across all of its devices at once.
How do you save a set of selected devices for later use?
Select the rows, go to the Collections tab, and create a labeled collection (e.g., "Cobb Angle Project"). You can reload the selection anytime and carry it into the PDF viewer and other tabs that support selections.
7. Product codes and the regulations tree
Click a product code in the results to jump to it in the regulations tree — identification text, sibling product codes, and devices you can open in a PDF viewer on the right. Click a regulation number to see its identification, special controls, and related product codes. You can also search by product code or regulation number at the top of the tree. Always read the special controls if any exist for your device — it broadens your search and sharpens pre-kickoff research.
What can you do from the regulations tree view?
Browse product codes and regulation numbers, read the identification text and special controls, browse sibling product codes, open device PDFs on the right, and search by product code or regulation number at the top of the tree.
8. Chart view
Click Show Chart and segment by regulation number (or product code) to see which regulations dominate your result set. Clicking a regulation takes you into the regulations tree. Great for spotting that most matches are, say, hardware laparoscopic devices — a cue to go back and filter.
How do you see which regulations dominate a search result set?
Click "Show Chart" and segment by Regulation Number. Clicking a regulation takes you to the regulations tree.
9. The predicate graph
Open the Predicates tab for a family-tree view of predicate relationships. Click a node to trace its parents and children; selections from search carry over pre-selected. Commonly predicated devices are worth reading — a lot of people predicated them for a reason. The visual lineage is also handy on client calls, e.g. to show how a predicate family evolved and justify why your predicate still holds.
In the predicate graph, why are commonly predicated devices worth reading?
A lot of people predicated them for a reason. Clicking a node traces parents and children, and selections from search carry over pre-selected.
10. Embeddings: the galaxy map
The Embeddings tab plots every matching document in a 2-D "galaxy map" where semantically similar devices cluster together. Hover or click clusters to explore, and let AI label the clusters for you. Embeddings beat product codes for grouping: two devices can carry different product codes (LLZ vs. QIH) yet do the same thing — the embedding captures the meaning of the intended use and device story. This is also exactly how retrieval-augmented generation (RAG) works under the hood, and it makes a great visual on client calls.
Try it yourself
Head to the search page and work through a few of these AI/ML fuzzy searches to build intuition: perivascular fat on CT · aortic valve calcification opportunistic screening on noncontrast CT · breast cancer prediction on digital pathology slides · autism detection · gestational age prediction · a hearing aid that can also detect a pulse · foundation model based analysis of ECG · large language models · penetration test. Watch how the relevance scores, intended use, and AI Performance tables tell you when results stop being meaningful.