Device brand name · Aberrometer ophthalmic

ORA System with VerifEye Messaging: medical device reports filed with FDA

438 reports name it, 2016–2026. Manufacturer given most often on reports: Alcon Research - Irvine Technology Center. Product code NCF.

Read first · FDA's statement on these data

Adverse event reports submitted to FDA do not undergo extensive validation or verification. Therefore, a causal relationship cannot be established between product and reactions listed in a report. While a suspected relationship may exist, it is not medically validated and should not be the sole source of information for clinical decision making or other assumptions about the safety or efficacy of a product. Additionally, it is important to remember that adverse event reports represent a small percentage of total usage numbers of a product. Common products may have a higher number of adverse events due to the higher total number of people using the product. openFDA, FDA

FDA adds: "Although MDRs are a valuable source of information, this passive surveillance system has limitations, including the potential submission of incomplete, inaccurate, untimely, unverified, or biased data. In addition, the incidence or prevalence of an event cannot be determined from this reporting system alone due to potential under-reporting of events and lack of information about frequency of device use." And: "MDR data alone cannot be used to establish rates of events, evaluate a change in event rates over time or compare event rates between devices. The number of reports cannot be interpreted or used in isolation to reach conclusions about the existence, severity, or frequency of problems associated with devices."

Do not rely on openFDA to make decisions regarding medical care. While we make every effort to ensure that data is accurate, you should assume all results are unvalidated.

Not medical advice. This site counts what was reported to FDA. Questions about a medicine or device belong with a pharmacist or clinician.

438
device reports naming the brand: 0% of all MAUDE reports · about 43 a year; 26
reports, 12 months to August 2026: 26 in the 12 months before; 46.6%
classified as malfunction: 47.4% across the product code; 0%
classified as death, as reported: 0 reports · not verified by FDA

FDA's MAUDE database holds 438 reports that name the brand "ORA System with VerifEye Messaging" (aberrometer ophthalmic), received between June 2016 and August 2026; the manufacturer given most often on reports is Alcon Research - Irvine Technology Center. Spellings of one product vary from report to report.

26 reports arrived in the 12 months to August 2026, close to the 26 of the 12 months before. FDA releases MAUDE data monthly; reports can arrive months after an event, so the newest months grow in later releases. The event types recorded are injury (53.4%) and malfunction (46.6%); across all aberrometer, ophthalmic reports (product code NCF) death is recorded in 0% and malfunction in 47.4%. Event type is the reporter's classification of the report, not a verified outcome.

The device problems coded most often are incorrect measurement (18.7%), incorrect, inadequate or imprecise result or readings (14.8%) and loose or intermittent connection (13.9%). The patient problems coded most often are appropriate clinical signs, symptoms and conditions term/code not available, blurred vision and visual impairment. FDA states that "MDR data alone cannot be used to establish rates of events, evaluate a change in event rates over time or compare event rates between devices. The number of reports cannot be interpreted or used in isolation to reach conclusions about the existence, severity, or frequency of problems associated with devices." It adds that the reporting system "has limitations, including the potential submission of incomplete, inaccurate, untimely, unverified, or biased data."

Reports by month, five years

Reports by the month FDA received them. FDA releases MAUDE data monthly; reports can arrive months after an event, so the newest months grow in later releases.

By year received

Event type and report source

Event type, as classified on the report

Death0%0

Injury53.4%234

Malfunction46.6%204

Other0%0

Not given0%0

Who filed the report

Manufacturer report100%438

Voluntary report0%0

User facility report0%0

Distributor report0%0

Not given0%0

Grey bar: all 652 reports carrying product code NCF. Event type is the filer's classification and is not verified by FDA.

Device problems coded

Device problem (FDA code)	Reports	Share	Share across product code
Incorrect measurementthe device measured wrongly	82	18.7%	17.5%
Incorrect, inadequate or imprecise result or readings	65	14.8%	16.3%
Loose or intermittent connection	61	13.9%	12.1%
Device operates differently than expectedthe device behaved unexpectedly	27	6.2%	8.4%
Insufficient device problem information	23	5.3%	4.9%
Unexpected therapeutic results	10	2.3%	2.6%
Failure to align	6	1.4%	1.7%
Overcorrection	5	1.1%	0.8%
Patient-device incompatibilitythe device did not suit the patient	5	1.1%	0.6%
Therapeutic or diagnostic output failure	5	1.1%	0.8%
Improper device output	4	0.9%	0.6%
Improper or incorrect procedure or method	4	0.9%	1.8%
Power problem	4	0.9%	0.9%
Application program problem: power calculation error	3	0.7%	0.9%
Application program problem	2	0.5%	0.2%
Component missing	2	0.5%	0.5%
Detachment of device component	2	0.5%	0.3%
Device displays incorrect message	2	0.5%	0.8%
Device slipped	2	0.5%	0.5%
Output problem	2	0.5%	0.6%

FDA's device problem codes as entered on the report; one report can carry several. Generic codes such as "no apparent adverse event" are left out.

Patient problems coded

Patient problem (FDA code)	Reports	Share
Appropriate clinical signs, symptoms and conditions term/code not available	58	13.2%
Blurred vision	39	8.9%
Visual impairmentreduced vision	35	8%
Complaint, ill-defined	9	2.1%
Failure of implant	9	2.1%
No patient involvement	9	2.1%
Visual disturbances	8	1.8%
Therapeutic effects, unexpected	7	1.6%
Eye injury	5	1.1%
Dizzinesslight-headedness or unsteadiness	2	0.5%
Halo	2	0.5%
Vitrectomy	2	0.5%
Capsular bag tear	1	0.2%
Diplopia/double vision	1	0.2%
Discomfortdiscomfort	1	0.2%

Patient problem codes are present mainly in reports filed since 2019 and are often blank.

In context

Measure	ORA System with VerifEye Messaging	Product code NCF	All MAUDE reports
Reports	438	652	26,136,888
Share of that pool	—	67.2%	0%
Classified as death, per 1,000 reports	0	0	9
Classified as injury	53.4%	52.6%	36.2%
Classified as malfunction	46.6%	47.4%	62.3%
Filed by the manufacturer	100%	99.7%	94.9%

Shares are of reports, not of devices in use. FDA states that "MDR data alone cannot be used to establish rates of events, evaluate a change in event rates over time or compare event rates between devices. The number of reports cannot be interpreted or used in isolation to reach conclusions about the existence, severity, or frequency of problems associated with devices." It adds that the reporting system "has limitations, including the potential submission of incomplete, inaccurate, untimely, unverified, or biased data."

Questions about ORA System with VerifEye Messaging reports

How many FDA reports name ORA System with VerifEye Messaging?

438 medical device reports in the openFDA MAUDE release of 28 Sep 2026, covering reports received through August 2026; 26 in the latest 12 months.

What kinds of events are reported?

injury (53.4%) and malfunction (46.6%). "Event type" is how the report was classified when filed: death, injury, malfunction or other.

What device problems are coded?

incorrect measurement (18.7%), incorrect, inadequate or imprecise result or readings (14.8%), loose or intermittent connection (13.9%), device operates differently than expected (6.2%) and insufficient device problem information (5.3%). These are FDA's device problem codes as entered on the report.

Who files these reports?

manufacturer reports (100%). Manufacturers and user facilities are required to report; voluntary reports come from health professionals and the public.

Do these reports show that ORA System with VerifEye Messaging was at fault?

No. FDA states that "MDR data alone cannot be used to establish rates of events, evaluate a change in event rates over time or compare event rates between devices. The number of reports cannot be interpreted or used in isolation to reach conclusions about the existence, severity, or frequency of problems associated with devices." It adds that the reporting system "has limitations, including the potential submission of incomplete, inaccurate, untimely, unverified, or biased data." FDA adds that "a causal relationship cannot be established between product and reactions listed in a report."

How do I report a problem with a medical device?

Through FDA MedWatch (Form FDA 3500 for health professionals and consumers), or to the manufacturer. See the guide on how to report.

Where this comes from. Counts are built from the openFDA Device Adverse Event (MAUDE) bulk export released 28 Sep 2026, which holds reports FDA received through 31 Aug 2026. Brand, generic and manufacturer names are as written on the reports; product code names come from FDA's device classification. A report counts here when any device it lists carries this brand name after punctuation and capitalisation are normalised. No report narrative, lot number, patient detail or reporter identity is published. See the methodology and sources; FDA's record is authoritative, and corrections are handled within five working days.

Drug data (FAERS) through 30 Jun 2026; device data (MAUDE) through 31 Aug 2026. Not medical advice.