Clinical practice data from Australian eye clinics; Peer-reviewed clinical literature (Coroneo et al. 2024, Kokkinakis et al. 2023)
The device was evaluated through 4 years of continuous use in real-world clinical settings across more than 1,000 patients to support safety and performance claims.
Field testing in real world use; Observational / Real-world clinical use; Follow-up/Duration: >4 years
Ophthalmic patients; Sample Size: >1,000; Number of Sites: Multiple Australian eye clinics
Not applicable for this study
Safety (adverse events), performance of dynamic emissivity pattern capture
Indications for Use
TearView is an ophthalmic camera that is intended to be used by an eye care specialist in adult patients to take digital images of the eye and surrounding areas. TearView is a non-contact thermograph that captures and stores images of thermal (emissivity) pattern of the ocular surface including its tear film during blinking.
Device Story
TearView is a non-contact, passive thermal camera accessory for slit lamps; captures long-wave infrared (7.5-13µm) thermal radiation from the ocular surface and tear film during blinking. Device uses a 640x480 microbolometer array; records grey-scale video via touch-screen Windows-based software on a user-provided computer/tablet. Operated by eye care specialists in clinical settings; device attaches to slit lamp turret; slit lamp chin/headrest provides patient alignment. No light source; operates in dark; no direct patient contact. Output allows clinicians to visualize dynamic thermal emissivity patterns of the ocular surface; aids in assessment of tear film dysfunction. Benefits include high-resolution, non-invasive, real-time visualization of ocular surface thermal patterns without environmental control or specific patient blinking requirements.
Clinical Evidence
Bench testing confirmed compliance with ISO 15004-1:2020, IEC 60601-1:2005+A1:2012, and IEC 60601-1-2:2014. Real-world performance testing included over 1,000 patients across 4 years of continuous clinical use. Results published in peer-reviewed literature (Coroneo MT et al., 2024; Kokkinakis J et al., 2023) demonstrate the device safely captures dynamic emissivity patterns of the ocular surface and tear film.
Technological Characteristics
Long-wave infrared (7.5-13µm) thermograph; 640x480 pixel microbolometer array; 30 Hz frame rate; 28mK thermal sensitivity. Fixed focus lens system. Powered via USB-C (5V/5mA). Attaches to slit lamp turret. Software-based image acquisition and storage on external Windows PC/tablet. Complies with ISO 15004-1, IEC 60601-1, and IEC 60601-1-2.
Indications for Use
Indicated for adult patients requiring digital imaging of the eye and surrounding areas, specifically for capturing and storing thermal (emissivity) patterns of the ocular surface and tear film during blinking, for use by eye care specialists.
Regulatory Classification
Identification
An ophthalmic camera is an AC-powered device intended to take photographs of the eye and the surrounding area.
Special Controls
*Classification.* Class II (special controls). The device, when it is a photorefractor or a general-use ophthalmic camera, is exempt from the premarket notification procedures in subpart E of part 807 of this chapter subject to the limitations in § 886.9.
Predicate Devices
United Integrated Non-Contact Thermograph System Model IT-85 (K111771)
Submission Summary (Full Text)
{0}
**FDA** **U.S. FOOD & DRUG**
ADMINISTRATION
June 22, 2026
Beyond 700 Pty Ltd
Dr. Burkhardt Schuett
COO
8 Miller Street
Petersham, NSW 2049
Australia
Re: K253176
Trade/Device Name: TearView
Regulation Number: 21 CFR 886.1120
Regulation Name: Ophthalmic Camera
Regulatory Class: Class II
Product Code: HKI
Dated: May 9, 2026
Received: May 11, 2026
Dear Burkhardt Schuett:
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 (the 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. Although this letter refers to your product as a device, please be aware that some cleared products may instead be combination products. The 510(k) Premarket Notification Database available at https://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfpmn/pmn.cfm identifies combination product submissions. 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, FDA may publish further announcements concerning your device in the Federal Register.
Additional information about changes that may require a new premarket notification are provided in the FDA guidance documents entitled "Deciding When to Submit a 510(k) for a Change to an Existing Device"
U.S. Food & Drug Administration
10903 New Hampshire Avenue
Silver Spring, MD 20993
www.fda.gov
{1}
K253176 - Burkhardt Schuett
Page 2
(https://www.fda.gov/media/99812/download) and "Deciding When to Submit a 510(k) for a Software Change to an Existing Device" (https://www.fda.gov/media/99785/download).
Your device is also subject to, among other requirements, the Quality Management System Regulation (QMSR) (21 CFR Part 820), which includes, but is not limited to, ISO 13485 clause 7.3 (Design controls), ISO 13485 clause 8.3 (Nonconforming product), ISO 13485 clause 8.5.2 (Corrective action), and ISO 13485 clause 8.5.3 (Preventative action). Please note that regardless of whether a change requires premarket review, the QMSR requires device manufacturers to review and approve changes to device design and production (ISO 13485 clause 7.3 and ISO 13485 clause 7.5) and document changes and approvals in the Medical Device File (ISO 13485 clause 4.2.3).
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. 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 Part 803) for devices or postmarketing safety reporting (21 CFR Part 4, Subpart B) for combination products (see https://www.fda.gov/combination-products/guidance-regulatory-information/postmarketing-safety-reporting-combination-products); good manufacturing practice requirements as set forth in the Quality Management System Regulation (QMSR) (21 CFR Part 820) for devices or current good manufacturing practices (21 CFR Part 4, Subpart A) for combination products; and, if applicable, the electronic product radiation control provisions (Sections 531-542 of the Act); 21 CFR Parts 1000-1050.
All medical devices, including Class I and unclassified devices and combination product device constituent parts are required to be in compliance with the final Unique Device Identification System rule ("UDI Rule"). The UDI Rule requires, among other things, that a device bear a unique device identifier (UDI) on its label and package (21 CFR 801.20(a)) unless an exception or alternative applies (21 CFR 801.20(b)) and that the dates on the device label be formatted in accordance with 21 CFR 801.18. The UDI Rule (21 CFR 830.300(a) and 830.320(b)) also requires that certain information be submitted to the Global Unique Device Identification Database (GUDID) (21 CFR Part 830 Subpart E). For additional information on these requirements, please see the UDI System webpage at https://www.fda.gov/medical-devices/device-advice-comprehensive-regulatory-assistance/unique-device-identification-system-udi-system.
Also, please note the regulation entitled, "Misbranding by reference to premarket notification" (21 CFR 807.97). For questions regarding the reporting of adverse events under the MDR regulation (21 CFR Part 803), please go to https://www.fda.gov/medical-devices/medical-device-safety/medical-device-reporting-mdr-how-report-medical-device-problems.
{2}
K253176 - Burkhardt Schuett
Page 3
For comprehensive regulatory information about medical devices and radiation-emitting products, including information about labeling regulations, please see Device Advice (https://www.fda.gov/medical-devices/device-advice-comprehensive-regulatory-assistance) and CDRH Learn (https://www.fda.gov/training-and-continuing-education/cdrh-learn). Additionally, you may contact the Division of Industry and Consumer Education (DICE) to ask a question about a specific regulatory topic. See the DICE website (https://www.fda.gov/medical-devices/device-advice-comprehensive-regulatory-assistance/contact-us-division-industry-and-consumer-education-dice) for more information or contact DICE by email (DICE@fda.hhs.gov) or phone (1-800-638-2041 or 301-796-7100).
Sincerely,
Alexander Beylin Date: 2026.06.22
-S 14:27:17 -04'00'
for CAPT Bardley Cunningham, MSE, RAC
Acting Assistant Director
DHT1A: Division of Ophthalmic Devices
OHT1: Office of Ophthalmic, Anesthesia,
Respiratory, ENT, and Dental Devices
Office of Product Evaluation and Quality
Center for Devices and Radiological Health
Enclosure
{3}
DEPARTMENT OF HEALTH AND HUMAN SERVICES
Food and Drug Administration
Form Approved: OMB No. 0910-0120
Expiration Date: 06/30/2023
See PRA Statement below.
# Indications for Use
510(k) Number (if known)
K253176
Device Name
TearView
Indications for Use (Describe)
TearView is an ophthalmic camera that is intended to be used by an eye care specialist in adult patients to take digital images of the eye and surrounding areas.
TearView is a non-contact thermograph that captures and stores images of thermal (emissivity) pattern of the ocular surface including its tear film during blinking.
Type of Use (Select one or both, as applicable)
☑ Prescription Use (Part 21 CFR 801 Subpart D)
☐ Over-The-Counter Use (21 CFR 801 Subpart C)
CONTINUE ON A SEPARATE PAGE IF NEEDED.
This section applies only to requirements of the Paperwork Reduction Act of 1995.
*DO NOT SEND YOUR COMPLETED FORM TO THE PRA STAFF EMAIL ADDRESS BELOW.*
The burden time for this collection of information is estimated to average 79 hours per response, including the time to review instructions, search existing data sources, gather and maintain the data needed and complete and review the collection of information. Send comments regarding this burden estimate or any other aspect of this information collection, including suggestions for reducing this burden, to:
Department of Health and Human Services
Food and Drug Administration
Office of Chief Information Officer
Paperwork Reduction Act (PRA) Staff
PRAStaff@fda.hhs.gov
"An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a currently valid OMB number."
FORM FDA 3881 (6/20)
Page 1 of 1
PSC Publishing Services (301) 443-6740 EF
{4}
K253176
# 510(k) SUMMARY
| Preparation Date: | 5^{th} June 2026 |
| --- | --- |
| Applicant: | Beyond 700 Pty Ltd Unit 38 9 Hoyle Avenue Castle Hill, NSW, 2154 Australia |
| Contact Person: | Dr Burkhardt Schuett |
| Contact Phone | +61 (0) 432 175 797 |
| Device Trade Name: | TearView |
| Device Version: | Version 3 |
| Common Name: | Ophthalmic Imaging Device |
| Classification Name: | Camera, Ophthalmic, AC-powered |
| Device Classification: | Class II |
| Regulation: | 21 CFR 886.1120 |
| Predicate Device: | United Integrated Non-Contact Thermograph System Model IT-85 (**K111771**) |
| Product Code | HKI |
## 1. Device Description
The device TearView is a thermal camera designed to be used for eye conditions that a medical professional considers to have an affect on the thermal (emissivity) pattern of the eye during eye opening and blinking. As such, it is a thermal camera optimized to make recordings of thermal (emissivity) patterns coming off the open eye including its tear film in the blinking process. It is designed as an accessory to a slit lamp (that needs to be provided by the user). It is attached to the turret of a slit lamp via a provided arm. The slit lamp mechanism is used to focus the device on the eye of the patient whose head is supported in the chin / headrest of the slit lamp.
TearView is powered by a Windows computer/tablet (not part of the device) via an USB cable connection with a maximum theoretical output of 25mWatt (5V at 5mA). It also receives information from and sends information to the computer/tablet via the same cable connection. TearView is based on a 640×480 pixel array microbolometer with a fixed focus lens system and passively acquires and records the thermal radiation emitted from the ocular surface including its tear film and presents this as a grey-scale video. TearView uses its own touch-screen enabled Windows-based software, which needs to be installed on a computer/tablet (provided by the user) to run the device and to store the recordings for review. The thermal imaging is from a distance and completely passive, hence the device has no light source, can run in the dark, and never contacts the patient directly. Such recordings of unforced normal blinks of a subject take less than 30 seconds and can be taken at any temperature between 20-40°C with no other environmental control or specific blinking of the subject necessary.
1
{5}
K253176
## 2. Indications for Use
TearView is an ophthalmic camera that is intended to be used by an eye care specialist in adult patients to take digital images of the eye and surrounding areas.
TearView is a non-contact thermograph that captures and stores images of thermal (emissivity) pattern of the ocular surface including its tear film during blinking.
## 3. Substantial Equivalence
TearView is similar in principle function to the predicate thermographic camera (see Table 1), however TearView is an improvement on a number of technical parameters that define the effectiveness of this technology. TearView has higher spatial and temperature resolutions as well as a higher frame rate than the predicate device that was previously cleared under K111771. Overall, this is an improvement allowing better and clearer images of the thermal patterns coming from the eye, and as a difference to the Indications for Use statement of the predicate, it was included that the resulting emissivity pattern arise from the ocular surface including the tear film covering the eye as well. Furthermore, TearView is designed as an add-on to a slit lamp and needs an USB connection to an external computer for operation and power-supply rather than being a stand-alone device that is connected to the mains like the predicate. These features do not raise question regarding safety and effectiveness. TearView is not directly connected to the mains, runs on much lower voltage, and does not directly contact the patient.
Table 1: Similarities and differences between the proposed device TearView and the predicate device.
| | TearView | Predicate, UIS Non-Contact Thermograph System Model IT-85 | Comparison |
| --- | --- | --- | --- |
| 510(k) Number | K253176 | K111771 | |
| Regulation number | 21 CFR 886.1120 | 21 CFR 886.1120 | Identical |
| Product code | HKI | HKI | Identical |
| Indications for Use | TearView is an ophthalmic camera that is intended to be used by an eye care specialist in adult patients to take digital images of the eye and surrounding areas. TearView is a non-contact thermograph that captures and stores images of thermal (emissivity) patterns of the ocular surface including its tear film during blinking. | The UIS Non-contact Thermograph system is an ophthalmic imaging device that stores, archives, and manipulates digital images of ocular surface temperature measurements taken by a physician in adult patients. | Nearly identical. Both devices capture and store images of thermal emissivity patterns of the ocular surface. TearView and its software do not allow for manipulation of an image that was taken |
| Camera Type | Thermograph (Long wave infrared 7.5-13µm) | Thermograph (Long wave infrared 7.5-13µm) | Identical |
| Camera Resolution | 640x480 pixel | 320x240 pixel | Not Identical TearView has a higher spatial resolution than the predicate. |
2
{6}
K253176
| Camera frame rate | 30 Hz | 30 Hz | Identical |
| --- | --- | --- | --- |
| Camera sensor noise equivalent temperature (thermal sensitivity) | 28mK | 70mK | Not identical TearView has a higher thermal sensitivity than the predicate |
| Recorded media | Digital (external Window-computer or tablet) | Digital (Computer system part of this stand alone device) | Not identical TearView is operated from an external computer |
| Contact area with patient | none | Head (chin and forehead) | Not identical TearView is used with a third-party slit-lamp and is not in direct contact with the patient |
| Means for alignment | Fixed focus of the camera, for device alignment a slit-lamp mechanism and head rest of that slit lamp is used | Fixed focus of the camera, there are mechanism to move camera and built in head rest as part of this stand alone device | Similar TearView is designed as an add-on to a slit lamp and used the slit lamps function for alignment and focus |
| Working distance | 40mm | Not known | |
| Light Source | none | none | Identical |
| Power Source | USB-C, DC | AC-powered | Not identical |
#### 4. Bench Performance and Safety testing
TearView complies to the requirements applicable to ophthalmic instruments (ISO 15004-1: 2020) and the standard for basic and electrical safety (IEC 60601-1:2005 + A1:2012). It complies with the standard IEC 60601-1-2: 2014 Part 1+2, set for active devices with regard to electrostatic discharge immunity, radiated field immunity, magnetic field immunity, and unintended emission. The device has been bench tested for its ability to observe the thermal emissivity patterns of the ocular surface including its tear film across a range of ambient temperatures.
#### 5. Performance Testing
TearView has been field tested in real world use with more than 1,000 ophthalmic patients by 3rd party independent eye care specialists in continuous use for more than 4 years with no adverse events. Some of the resulting real world testing has been published (Coroneo MT et al. High-Resolution Ocular Surface Imaging: Real-Time Visualization of Tear Film Dysfunction. Cornea. 2024 May 30 and Kokkinakis J et al. Effects on the Human Tear Film of Applying Skin Lipids to the Ocular Surface. Cornea. 2023 Dec 1;42:1562-1571). In conclusion, it was shown that TearView enables the dynamic emissivity pattern of ocular surface including its tear film to be captured safely.
#### 6. Conclusion
The basic and underlying function of the ophthalmic camera TearView is the same as for the predicate. Due to its technical improvements compared to the predicate it allows more detailed thermographic imaging of the eye including its tear film during blinking.. Its use for more than 4 years in Australian eye clinics without any adverse events and the bench performance testing demonstrate that it is as safe and effective as the predicate. Taken together, TearView is therefore substantially equivalent to the predicate device.
3
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.