Devices › Orthopedic stereotaxic instrument
Device brand name · Orthopedic stereotaxic instrument
Real Intelligence Cori: medical device reports filed with FDA
983 reports name it, 2020–2026. Manufacturer given most often on reports: Blue Belt Technologies. Product code OLO.
- 983
- device reports naming the brand
- 0% of all MAUDE reports · about 166 a year
- 97
- reports, 12 months to August 2026
- 130 in the 12 months before
- 80.4%
- classified as malfunction
- 81.6% across the product code
- 0%
- classified as death, as reported
- 0 reports · not verified by FDA
FDA's MAUDE database holds 983 reports that name the brand "Real Intelligence Cori" (orthopedic stereotaxic instrument), received between August 2020 and August 2026; the manufacturer given most often on reports is Blue Belt Technologies. Spellings of one product vary from report to report.
97 reports arrived in the 12 months to August 2026, down 25% from 130 in 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 malfunction (80.4%) and injury (19.6%); across all orthopedic stereotaxic instrument reports (product code OLO) death is recorded in 0.1% and malfunction in 81.6%. Event type is the reporter's classification of the report, not a verified outcome.
The device problems coded most often are application program problem: parameter calculation error (40.4%), unintended application program shut down (37.2%) and connection problem (5.4%). The patient problems coded most often are laceration(s), no patient involvement and loss of range of motion. 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
Who filed the report
Grey bar: all 20,634 reports carrying product code OLO. 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 |
|---|---|---|---|
| Application program problem: parameter calculation error | 397 | 40.4% | 2.9% |
| Unintended application program shut down | 366 | 37.2% | 2.4% |
| Connection problema connection problem | 53 | 5.4% | 2.4% |
| Application program freezes or fails to launch | 51 | 5.2% | 0.5% |
| Application program problem | 29 | 3% | 0.9% |
| Computer operating system problem | 25 | 2.5% | 0.3% |
| Computer software problema software problem | 19 | 1.9% | 2.7% |
| Failure to power up | 9 | 0.9% | 0.2% |
| Defective alarm | 8 | 0.8% | 0% |
| Problem with software installation | 7 | 0.7% | 0% |
| Erratic or intermittent display | 6 | 0.6% | 0.1% |
| Intermittent continuity | 6 | 0.6% | 0.4% |
| Imprecision | 5 | 0.5% | 3.4% |
| Intermittent communication failure | 4 | 0.4% | 0.3% |
| Communication or transmission problemthe device could not communicate or transmit | 3 | 0.3% | 0.5% |
| Data problem | 3 | 0.3% | 0.1% |
| Defective devicethe device was defective | 3 | 0.3% | 0.2% |
| Display or visual feedback problem | 3 | 0.3% | 0.6% |
| Insufficient device problem information | 3 | 0.3% | 4.4% |
| Failure to calibrate | 2 | 0.2% | 0.7% |
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 |
|---|---|---|
| Laceration(s) | 35 | 3.6% |
| No patient involvement | 12 | 1.2% |
| Loss of range of motion | 8 | 0.8% |
| Fibrosis | 5 | 0.5% |
| Muscle/tendon damage | 4 | 0.4% |
| Perforation | 4 | 0.4% |
| Arthralgiajoint pain | 3 | 0.3% |
| Bone notching | 3 | 0.3% |
| Deformity/ disfigurement | 2 | 0.2% |
| Fluid discharge | 2 | 0.2% |
| Medical device site infectioninfection at the device site | 2 | 0.2% |
| Painpain, site not specified | 2 | 0.2% |
| Physical asymmetry | 2 | 0.2% |
| Wound dehiscencea wound reopened | 2 | 0.2% |
| Cellulitisa skin infection | 1 | 0.1% |
Patient problem codes are present mainly in reports filed since 2019 and are often blank.
In context
| Measure | Real Intelligence Cori | Product code OLO | All MAUDE reports |
|---|---|---|---|
| Reports | 983 | 20,634 | 26,136,888 |
| Share of that pool | — | 4.8% | 0% |
| Classified as death, per 1,000 reports | 0 | 1 | 9 |
| Classified as injury | 19.6% | 18.2% | 36.2% |
| Classified as malfunction | 80.4% | 81.6% | 62.3% |
| Filed by the manufacturer | 99.9% | 99.1% | 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."
Other brands with product code OLO
| Brand | Reports | Latest 12 months | Classified as death |
|---|---|---|---|
| Mazor X System | 1,009 | 238 | 0.6% |
| 3 0 Rio Robotic Arm - Mics | 847 | 2 | 0% |
| Handpiece MICS | 812 | 183 | 0% |
| Reamer Handle Offset | 758 | 345 | 0% |
| Velys Saw Interface Right | 611 | 124 | 0% |
| Velys Saw Interface Left | 597 | 125 | 0% |
| Excelsius Gps | 597 | 128 | 0.3% |
| Real Intelligence Robotic Drill | 585 | 81 | 0% |
| Navio Handpiece | 489 | 0 | 0% |
| NavLock | 464 | 90 | 0% |
| Velys Satellite Station | 353 | 94 | 0% |
| Navio Surgical System Us | 334 | 0 | 0% |
| Mako Robotic Arm 3 1 | 317 | 65 | 0% |
| Velys Saw Handpiece | 269 | 82 | 0% |
| Velys | 257 | 257 | 0% |
Ordered by report count for navigation only. 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 also states that "common products may have a higher number of adverse events due to the higher total number of people using the product."
Questions about Real Intelligence Cori reports
How many FDA reports name Real Intelligence Cori?
983 medical device reports in the openFDA MAUDE release of 28 Sep 2026, covering reports received through August 2026; 97 in the latest 12 months.
What kinds of events are reported?
malfunction (80.4%) and injury (19.6%). "Event type" is how the report was classified when filed: death, injury, malfunction or other.
What device problems are coded?
application program problem: parameter calculation error (40.4%), unintended application program shut down (37.2%), connection problem (5.4%), application program freezes or fails to launch (5.2%) and application program problem (3%). These are FDA's device problem codes as entered on the report.
Who files these reports?
manufacturer reports (99.9%) and voluntary reports (0.1%). Manufacturers and user facilities are required to report; voluntary reports come from health professionals and the public.
Do these reports show that Real Intelligence Cori 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.