Cardea SOLO M300-5Recalls & reported problems
Cardiac Insight, Inc. · Cardea SOLO Wearable Sensor (M300) · Class 2
Data updated Oct 16, 2026 from official FDA records · Editorial policy
- Adverse event reports
- 1
- Deaths reported
- 0
- Injuries reported
- 1
- Recalls naming it
- 0
Summary
The FDA's MAUDE database contains 1 adverse event report that list this exact device (DI 10857553006112), received between Dec 14, 2023 and Dec 14, 2023 — classified as 1 injury.
The most frequently reported specific device problem is “Patient Device Interaction Problem” (1 report).
Reports come from manufacturers, hospitals and patients and are not verified by the FDA. A report does not prove the device caused the event, and counts can't be used to compare devices or estimate failure rates. What reports can and can't tell you · How this data works · Data updated Oct 16, 2026.
Reports received per month
Most reported problems
Device problems
- Adverse Event Without Identified Device or Use Problem1
- Patient Device Interaction Problem1
Patient problems
- Erythema1
- Hypersensitivity/Allergic reaction1
- Skin Inflammation/ Irritation1
Recent adverse event reports
The 1 most recent of 1 reports, in the reporter's own words as published by the FDA.
InjuryDec 14, 2023Adverse Event Without Identified Device or Use Problem; Patient Device Interaction Problem; Adverse Event Without Identified Device or Use Problem; Patient Device Interaction Problem
PATIENT EXPERIENCED SEVERE RASH AND BLISTERING OF HER SKIN DURING WEAR OF THE M300 (SENSOR). THE PATIENT STARTED EXPERIENCING SOME ITCHING, BURNING AND DISCOMFORT AFTER WEARING THE PATCH FOR 1-2 DAYS. DUE TO DISCOMFORT, THE PATIENT REMOVED THE SENSOR AFTER WEARING IT FOR 4 DAYS AND 21 HOURS (B)(6) 2023). STAFF SAID SHE CAME TO THE CLINIC HOLDING A WET COMPRESS ON THE WOUND AND REQUESTED TO SPEAK WITH THE MEDICAL STAFF. SHE DESCRIBED THAT SHE HAD SOME DISCOMFORT AND REMOVED THE SENSOR EARLY DUE TO CONCERNS, WHEN SHE REMOVED THE PATCH THAT'S WHEN HER SKIN SHOWED THE BLISTERING AND THE RASH. PHYSICIAN INITIALLY SUGGESTED AT-HOME REMEDIES AND CARE. HOWEVER, AFTER A WEEK, THE AREA WASN'T HEALLING SO HE PROVIDED THE PATIENT WITH A TOPICAL STEROID CREAM AND IS MONITORING HER HEALING PROCESS. IT WAS REPORTED (B)(6) 2023 THE PATIENT DID WELL WITH THE TOPICAL STEROID CREAM. ALTHOUGH TEMPERATURES WERE ABOVE NORMAL DURING THE WEAR PERIOD, PATIENT REPORTED TO HAVE SPENT MOST OF THE WEAR PERIOD TIME INDOORS AND WAS NOT WORKING IN THE SUN OR DOING MANY OUTDOOR ACTIVITIES.
Patient problems: Erythema; Hypersensitivity/Allergic reaction; Skin Inflammation/ Irritation
MAUDE report 18332737 ↗
Other Computer, Diagnostic, Programmable devices
- ZIO AT Patch A100A100XIrhythm Technologies, Inc. · Computer, Diagnostic, Programmable1 recall14 deaths629 reports
- CARTO 3 FG540000Biosense Webster (Israel) Ltd. · Computer, diagnostic, programmable1 death437 reports
- Sensis 10764561Siemens Healthcare GmbH · COMPUTER, DIAGNOSTIC, PROGRAMMABLE5 recalls8 reports
- Sensis Vibe Hemo 11007641Siemens Healthcare GmbH · COMPUTER, DIAGNOSTIC, PROGRAMMABLE4 recalls1 death22 reports
- Sensis Vibe Combo 11007642Siemens Healthcare GmbH · COMPUTER, DIAGNOSTIC, PROGRAMMABLE4 recalls1 death6 reports
- Change Healthcare Cardiology Hemo 15.1Change Healthcare Canada Company · Computer, Diagnostic, Programmable4 recalls1 report
- Change Healthcare Cardiology Hemo 15.0.1Change Healthcare Canada Company · Computer, Diagnostic, Programmable3 recalls1 death1 report
- Change Healthcare Cardiology Hemo 14.3.2Change Healthcare Canada Company · Computer, Diagnostic, Programmable3 recalls0 reports
Sources and updates
- Device record: FDA GUDID, file dated Oct 13, 2026 · View this device in AccessGUDID ↗
- Adverse event reports: FDA MAUDE, file dated Oct 14, 2026 · each report above links to its original FDA record
- Recalls: FDA Medical Device Recalls, file dated Oct 16, 2026
- Page last rebuilt: Oct 16, 2026. Data downloaded through openFDA, which notes it is not validated for clinical or regulatory use.
How reports and recalls are matched · Editorial policy · Report an error on this page