Devices › Pump, infusion, insulin, to be used with invasive glucose sensor
Device brand name · Oyc
Animas Vibe System: medical device reports filed with FDA
3,135 reports name it, 2015–2019. Manufacturer given most often on reports: Dexcom. Product code OYC.
- 3,135
- device reports naming the brand
- 0% of all MAUDE reports · about 275 a year
- 0
- reports, 12 months to August 2026
- 0 in the 12 months before
- 98.1%
- classified as malfunction
- 85.5% across the product code
- 0.1%
- classified as death, as reported
- 2 reports · not verified by FDA
FDA's MAUDE database holds 3,135 reports that name the brand "Animas Vibe System" (oyc), received between February 2015 and July 2019; the manufacturer given most often on reports is Dexcom. Spellings of one product vary from report to report.
0 reports arrived in the 12 months to August 2026, and none 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 (98.1%), injury (1.8%) and death (0.1%); across all pump, infusion, insulin, to be used with invasive glucose sensor reports (product code OYC) death is recorded in 0.3% and malfunction in 85.5%. Event type is the reporter's classification of the report, not a verified outcome.
The device problems coded most often are device operates differently than expected (46.4%), wireless communication problem (24%) and device displays incorrect message (12.6%). The patient problems coded most often are foreign body in patient, itching sensation and erythema. 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
No report naming Animas Vibe System was received in the five years to August 2026; the latest was received in July 2019.
By year received
Event type and report source
Event type, as classified on the report
Who filed the report
Grey bar: all 891,173 reports carrying product code OYC. 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 |
|---|---|---|---|
| Device operates differently than expectedthe device behaved unexpectedly | 1,454 | 46.4% | 4.5% |
| Wireless communication problema wireless connection problem | 753 | 24% | 1.3% |
| Device displays incorrect message | 394 | 12.6% | 24% |
| Imprecision | 234 | 7.5% | 0.4% |
| Detachment of device component | 83 | 2.6% | 0.4% |
| Component missing | 65 | 2.1% | 0.5% |
| Incorrect or inadequate test results | 20 | 0.6% | 0.1% |
| Communication or transmission problemthe device could not communicate or transmit | 19 | 0.6% | 0.6% |
| Detachment of device or device componentpart of the device came off | 14 | 0.4% | 0.6% |
| Breakthe device broke | 13 | 0.4% | 10.1% |
| No device output | 12 | 0.4% | 0% |
| Incorrect, inadequate or imprecise result or readings | 10 | 0.3% | 0.1% |
| Improper or incorrect procedure or method | 8 | 0.3% | 0.7% |
| Data problem | 7 | 0.2% | 0.2% |
| Alarm not visible | 6 | 0.2% | 0% |
| Invalid sensing | 5 | 0.2% | 0.1% |
| Device sensing problem | 4 | 0.1% | 0.3% |
| Fracturea broken bone | 4 | 0.1% | 0.2% |
| False reading from device non-compliance | 2 | 0.1% | 0% |
| Unable to obtain readings | 2 | 0.1% | 0.1% |
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 |
|---|---|---|
| Foreign body in patientpart of a device left in the patient | 19 | 0.6% |
| Itching sensation | 17 | 0.5% |
| Erythemaskin redness | 16 | 0.5% |
| Rashskin rash | 15 | 0.5% |
| Hypoglycemialow blood sugar | 13 | 0.4% |
| Loss of consciousnesspassing out | 9 | 0.3% |
| Skin inflammation | 6 | 0.2% |
| Confusion/ disorientation | 5 | 0.2% |
| Hyperglycemiahigh blood sugar | 5 | 0.2% |
| Burn(s)a burn | 4 | 0.1% |
| Purulent discharge | 4 | 0.1% |
| Vomitingbeing sick | 4 | 0.1% |
| Blurred vision | 3 | 0.1% |
| Cognitive changes | 3 | 0.1% |
| Dehydrationdehydration | 3 | 0.1% |
Patient problem codes are present mainly in reports filed since 2019 and are often blank.
In context
| Measure | Animas Vibe System | Product code OYC | All MAUDE reports |
|---|---|---|---|
| Reports | 3,135 | 891,173 | 26,136,888 |
| Share of that pool | — | 0.4% | 0% |
| Classified as death, per 1,000 reports | 1 | 3 | 9 |
| Classified as injury | 1.8% | 14.2% | 36.2% |
| Classified as malfunction | 98.1% | 85.5% | 62.3% |
| Filed by the manufacturer | 100% | 100% | 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 OYC
| Brand | Reports | Latest 12 months | Classified as death |
|---|---|---|---|
| Paradigm Real-Time Revel Insulin Infusion Pump | 178,691 | 0 | 0.6% |
| Paradigm Real-Time Insulin Infusion Pump | 126,282 | 0 | 0.3% |
| 640G Insulin Pump MMT-1712K | 119,547 | 1,598 | 0.1% |
| 640G Insulin Pump MMT-1711K | 76,609 | 151 | 0.1% |
| Animas Vibe | 88,703 | 0 | 0% |
| T Slim G5 System | 49,783 | 0 | 0% |
| t:slim G4 system | 39,215 | 20 | 0% |
| Pump Mmt-1712kl 640g V4 10 Bk Sf Mg | 21,531 | 952 | 0% |
| 640g Insulin Pump | 16,911 | 0 | 0% |
| Paradigm REAL-Time REVEL Insulin Infusion Pump MMT-723LNAS | 12,936 | 41 | 0.8% |
| t:slim X2 Insulin Pump | 31,159 | 86 | 0% |
| Pump Mmt-1711kl 640g V4 10 Bk Sf Mm | 11,157 | 168 | 0% |
| Paradigm REAL-Time Insulin Infusion Pump MMT-754WWS | 10,465 | 661 | 0% |
| Paradigm Real-Time Revel Insulin Infusion Pump Mmt-723nas | 8,540 | 49 | 0.8% |
| 640g Insulin Pump Mmt-1712b | 5,629 | 1 | 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 Animas Vibe System reports
How many FDA reports name Animas Vibe System?
3,135 medical device reports in the openFDA MAUDE release of 28 Sep 2026, covering reports received through August 2026; 0 in the latest 12 months.
What kinds of events are reported?
malfunction (98.1%), injury (1.8%) and death (0.1%). "Event type" is how the report was classified when filed: death, injury, malfunction or other.
What device problems are coded?
device operates differently than expected (46.4%), wireless communication problem (24%), device displays incorrect message (12.6%), imprecision (7.5%) and detachment of device component (2.6%). 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 Animas Vibe System 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.