Devices › Pump, infusion, insulin, to be used with invasive glucose sensor
Device brand name · Pump infusion insulin to be used with invasive glucose sensor
640g Insulin Pump Mmt-1712h: medical device reports filed with FDA
2,753 reports name it, 2017–2025. Manufacturer given most often on reports: Medtronic Puerto Rico Operations. Product code OYC.
- 2,753
- device reports naming the brand
- 0% of all MAUDE reports · about 300 a year
- 0
- reports, 12 months to August 2026
- 5 in the 12 months before
- 98.9%
- classified as malfunction
- 85.5% across the product code
- 0%
- classified as death, as reported
- 0 reports · not verified by FDA
FDA's MAUDE database holds 2,753 reports that name the brand "640g Insulin Pump Mmt-1712h" (pump infusion insulin to be used with invasive glucose sensor), received between May 2017 and July 2025; the manufacturer given most often on reports is Medtronic Puerto Rico Operations. Spellings of one product vary from report to report.
0 reports arrived in the 12 months to August 2026, against 5 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.9%) and injury (1.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 patient device interaction problem (21.4%), device displays incorrect message (21.4%) and break (16.9%). The patient problems coded most often are hyperglycemia, hypoglycemia and nausea. 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 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 |
|---|---|---|---|
| Patient device interaction problem | 590 | 21.4% | 7.9% |
| Device displays incorrect message | 588 | 21.4% | 24% |
| Breakthe device broke | 464 | 16.9% | 10.1% |
| Battery problema problem with the battery | 226 | 8.2% | 3.1% |
| Power problem | 200 | 7.3% | 4.9% |
| Material integrity problema problem with the device material | 162 | 5.9% | 2.7% |
| No display/image | 118 | 4.3% | 5% |
| Connection problema connection problem | 79 | 2.9% | 1.6% |
| Component missing | 75 | 2.7% | 0.5% |
| Circuit failure | 57 | 2.1% | 1% |
| Crackthe device cracked | 48 | 1.7% | 2.2% |
| Device difficult to program or calibrate | 45 | 1.6% | 2.8% |
| Device operates differently than expectedthe device behaved unexpectedly | 40 | 1.5% | 4.5% |
| Mechanical problema mechanical problem | 30 | 1.1% | 3.7% |
| Device alarm system | 29 | 1.1% | 2.4% |
| Loose or intermittent connection | 26 | 0.9% | 0.5% |
| Moisture or humidity problem | 26 | 0.9% | 1.7% |
| Loss of powerthe device lost power | 25 | 0.9% | 0.4% |
| Communication or transmission problemthe device could not communicate or transmit | 22 | 0.8% | 0.6% |
| Computer software problema software problem | 22 | 0.8% | 0.4% |
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 |
|---|---|---|
| Hyperglycemiahigh blood sugar | 85 | 3.1% |
| Hypoglycemialow blood sugar | 16 | 0.6% |
| Nauseafeeling sick | 4 | 0.1% |
| Vomitingbeing sick | 2 | 0.1% |
| Abdominal painstomach or belly pain | 1 | 0% |
| Appropriate clinical signs, symptoms and conditions term/code not available | 1 | 0% |
| Elevated ketones/ diabetic ketoacidosis | 1 | 0% |
Patient problem codes are present mainly in reports filed since 2019 and are often blank.
In context
| Measure | 640g Insulin Pump Mmt-1712h | Product code OYC | All MAUDE reports |
|---|---|---|---|
| Reports | 2,753 | 891,173 | 26,136,888 |
| Share of that pool | — | 0.3% | 0% |
| Classified as death, per 1,000 reports | 0 | 3 | 9 |
| Classified as injury | 1.1% | 14.2% | 36.2% |
| Classified as malfunction | 98.9% | 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 640g Insulin Pump Mmt-1712h reports
How many FDA reports name 640g Insulin Pump Mmt-1712h?
2,753 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.9%) and injury (1.1%). "Event type" is how the report was classified when filed: death, injury, malfunction or other.
What device problems are coded?
patient device interaction problem (21.4%), device displays incorrect message (21.4%), break (16.9%), battery problem (8.2%) and power problem (7.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 640g Insulin Pump Mmt-1712h 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.