Skip to content

CardioMEMS™ CM3100Recalls & reported problems

Cardiomems, Inc. · Hospital System · Class 3 · Implant

Data updated Oct 16, 2026 from official FDA records · Editorial policy

1 open recall names this device. See the recall details and contact the manufacturer or your healthcare provider.

Quick summary

This CardioMEMS hospital system reads pressure data from an implanted heart sensor. Most of its 452 reports describe software problems, such as readings from a patient being filed under another patient, and the reports list 2 injuries, no deaths and 450 malfunctions. There is 1 open recall, from February 2023, over sensors that may give inaccurate readings at higher elevations. Reports fell to 112 in the most recent year from 329 in the year before.

AI-generated from the FDA records on this page and checked automatically against the numbers below. Read the details before relying on it.

Adverse event reports
419
Deaths reported
0
Injuries reported
2
Recalls naming it
1

Summary

The FDA's MAUDE database contains 419 adverse event reports that list this exact device (DI 05415067034724), received between Mar 8, 2023 and Mar 25, 2026 — classified as 2 injuries, 417 malfunctions.

The most frequently reported specific device problem is “Application Program Problem” (370 reports).

1 FDA recall record name this device's identifier, 1 still open.

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

Nov 2023: 0 reportsDec 2023: 1 reportsJan 2024: 0 reportsFeb 2024: 2 reportsMar 2024: 0 reportsApr 2024: 0 reportsMay 2024: 0 reportsJun 2024: 0 reportsJul 2024: 1 reportsAug 2024: 0 reportsSep 2024: 2 reportsOct 2024: 1 reportsNov 2024: 14 reportsDec 2024: 2 reportsJan 2025: 2 reportsFeb 2025: 68 reportsMar 2025: 3 reportsApr 2025: 159 reportsMay 2025: 12 reportsJun 2025: 50 reportsJul 2025: 6 reportsAug 2025: 4 reportsSep 2025: 6 reportsOct 2025: 3 reportsNov 2025: 7 reportsDec 2025: 9 reportsJan 2026: 28 reportsFeb 2026: 24 reportsMar 2026: 11 reportsApr 2026: 0 reportsMay 2026: 0 reportsJun 2026: 0 reportsJul 2026: 0 reportsAug 2026: 0 reportsSep 2026: 0 reportsOct 2026: 0 reports202420252026159
Last 36 months. The most recent month may be incomplete.

Recalls naming this device

  1. Feb 7, 2023Open, Classified

    Select CardioMEMS PA Sensors (Model CM2000) operate outside of the intended frequency range at higher elevations when readings are taken over approximately 2,000 ft. (610 meters) above sea level; operation outside of the intended radiofrequency has the potential to result in inaccurate readings or sensor signal acquisition difficulties.

    Z-1225-2023 · Root cause: Device Design · Recall details · FDA record ↗

Most reported problems

Device problems

  • Application Program Problem370
  • Material Frayed23
  • Wireless Communication Problem14
  • Failure to Read Input Signal7
  • Electromagnetic Interference5
  • Break2
  • Loose or Intermittent Connection2
  • Communication or Transmission Problem1

Patient problems

  • No Clinical Signs, Symptoms or Conditions418
  • Dyspnea1
  • Hypervolemia1
  • Unspecified Kidney or Urinary Problem1

Recent adverse event reports

The 25 most recent of 419 reports, in the reporter's own words as published by the FDA.

  • MalfunctionMar 25, 2026Break; Loose or Intermittent Connection; Noise, Audible

    THIS REPORT IS TO ADVISE OF AN EVENT OBSERVED DURING ANALYSIS CONFIRMING EXPOSED WIRES ON THE INTERNAL CABLE CONNECTING THE WAND PORT TO THE TELEMETRY PRINTED CIRCUIT BOARD (PCB). THE HOSPITAL ELECTRONIC UNIT WAS REPLACED AND THERE WERE NO PATIENTS INVOLVED.

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 24687416 ↗
  • MalfunctionMar 19, 2026Application Program Problem

    ABBOTT R&D INTERNAL TESTING AND CODE REVIEW IDENTIFIED AN ISSUE WHERE THE READINGS FROM ONE CM3100 SYSTEM SESSION FOR ONE PATIENT (PATIENT A) WERE INCORRECTLY REPORTED UNDER A DIFFERENT PATIENT (PATIENT B). NO PATIENT INJURY WAS REPORTED. THE ISSUE IS CURRENTLY UNDER INVESTIGATION. MDR-(B)(4) WAS CREATED FOR THE SECOND PATIENT (PATIENT B).

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 24643072 ↗
  • MalfunctionMar 19, 2026Application Program Problem

    ABBOTT R&D INTERNAL TESTING AND CODE REVIEW IDENTIFIED AN ISSUE WHERE THE READINGS FROM ONE CM3100 SYSTEM SESSION FOR ONE PATIENT (PATIENT A) WERE INCORRECTLY REPORTED UNDER A DIFFERENT PATIENT (PATIENT B). NO PATIENT INJURY WAS REPORTED. THE ISSUE IS CURRENTLY UNDER INVESTIGATION. (B)(4) WAS CREATED FOR THE SECOND PATIENT (PATIENT A).

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 24643057 ↗
  • MalfunctionMar 12, 2026Application Program Problem

    ABBOTT R&D INTERNAL TESTING AND CODE REVIEW IDENTIFIED AN ISSUE WHERE THE READINGS FROM ONE CM3100 SYSTEM SESSION FOR ONE PATIENT (PATIENT A) WERE INCORRECTLY REPORTED UNDER A DIFFERENT PATIENT (PATIENT B). NO PATIENT INJURY WAS REPORTED. THE ISSUE IS CURRENTLY UNDER INVESTIGATION. MDR (B)(4) WAS CREATED FOR THE SECOND PATIENT (PATIENT B).

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 24581432 ↗
  • MalfunctionMar 9, 2026Application Program Problem

    ABBOTT R&D INTERNAL TESTING AND CODE REVIEW IDENTIFIED AN ISSUE WHERE THE READINGS FROM ONE CM3100 SYSTEM SESSION FOR ONE PATIENT (PATIENT A) WERE INCORRECTLY REPORTED UNDER A DIFFERENT PATIENT (PATIENT B). NO PATIENT INJURY WAS REPORTED. THE ISSUE IS CURRENTLY UNDER INVESTIGATION. MDR-2026-08395 WAS CREATED FOR THE SECOND PATIENT (PATIENT A).

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 24546491 ↗
  • MalfunctionMar 9, 2026Application Program Problem

    ABBOTT R&D INTERNAL TESTING AND CODE REVIEW IDENTIFIED AN ISSUE WHERE THE READINGS FROM ONE CM3100 SYSTEM SESSION FOR ONE PATIENT (PATIENT A) WERE INCORRECTLY REPORTED UNDER A DIFFERENT PATIENT (PATIENT B). NO PATIENT INJURY WAS REPORTED. THE ISSUE IS CURRENTLY UNDER INVESTIGATION. (B)(4) WAS CREATED FOR THE SECOND PATIENT (PATIENT B).

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 24544178 ↗
  • MalfunctionMar 9, 2026Application Program Problem

    ABBOTT R&D INTERNAL TESTING AND CODE REVIEW IDENTIFIED AN ISSUE WHERE THE READINGS FROM ONE CM3100 SYSTEM SESSION FOR ONE PATIENT (PATIENT A) WERE INCORRECTLY REPORTED UNDER A DIFFERENT PATIENT (PATIENT B). NO PATIENT INJURY WAS REPORTED. THE ISSUE IS CURRENTLY UNDER INVESTIGATION. (B)(4) WAS CREATED FOR THE SECOND PATIENT (PATIENT A).

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 24544164 ↗
  • MalfunctionMar 9, 2026Application Program Problem

    ABBOTT R&D INTERNAL TESTING AND CODE REVIEW IDENTIFIED AN ISSUE WHERE THE READINGS FROM ONE CM3100 SYSTEM SESSION FOR ONE PATIENT (PATIENT A) WERE INCORRECTLY REPORTED UNDER A DIFFERENT PATIENT (PATIENT B). NO PATIENT INJURY WAS REPORTED. THE ISSUE IS CURRENTLY UNDER INVESTIGATION. MDR (B)(4) WAS CREATED FOR THE SECOND PATIENT (PATIENT B).

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 24544114 ↗
  • MalfunctionMar 9, 2026Application Program Problem

    ABBOTT R&D INTERNAL TESTING AND CODE REVIEW IDENTIFIED AN ISSUE WHERE THE READINGS FROM ONE CM3100 SYSTEM SESSION FOR ONE PATIENT (PATIENT A) WERE INCORRECTLY REPORTED UNDER A DIFFERENT PATIENT (PATIENT B). NO PATIENT INJURY WAS REPORTED. THE ISSUE IS CURRENTLY UNDER INVESTIGATION. (B)(4) WAS CREATED FOR THE SECOND PATIENT (PATIENT A).

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 24543953 ↗
  • MalfunctionMar 5, 2026Application Program Problem

    ABBOTT R&D INTERNAL TESTING AND CODE REVIEW IDENTIFIED AN ISSUE WHERE THE READINGS FROM ONE CM3100 SYSTEM SESSION FOR ONE PATIENT (PATIENT (B)(6) WERE INCORRECTLY REPORTED UNDER A DIFFERENT PATIENT (PATIENT (B)(6). NO PATIENT INJURY WAS REPORTED. THE ISSUE IS CURRENTLY UNDER INVESTIGATION. MDR: (B)(4) WAS CREATED FOR THE SECOND PATIENT (PATIENT (B)(6).

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 24518648 ↗
  • MalfunctionMar 5, 2026Application Program Problem

    ABBOTT R&D INTERNAL TESTING AND CODE REVIEW IDENTIFIED AN ISSUE WHERE THE READINGS FROM ONE CM3100 SYSTEM SESSION FOR ONE PATIENT (PATIENT A) WERE INCORRECTLY REPORTED UNDER A DIFFERENT PATIENT (PATIENT B). NO PATIENT INJURY WAS REPORTED. THE ISSUE IS CURRENTLY UNDER INVESTIGATION. MDR-2026-08379 WAS CREATED FOR THE SECOND PATIENT (PATIENT A).

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 24518632 ↗
  • MalfunctionFeb 24, 2026Application Program Problem

    THE DEVICE IS INCLUDED IN THE FA-Q125-HF-1 CM3100 DUPLICATED PATIENT PROFILE IN HF CLOUD INITIATED ON (B)(6) 2025. ABBOTT R&D INTERNAL TESTING AND CODE REVIEW IDENTIFIED AN ISSUE WHERE THE READINGS FROM ONE CM3100 SYSTEM SESSION FOR ONE PATIENT (B)(6) WERE INCORRECTLY REPORTED UNDER A DIFFERENT PATIENT (PATIENT B). NO PATIENT INJURY WAS REPORTED. THE ISSUE IS CURRENTLY UNDER INVESTIGATION. (B)(4) WAS CREATED FOR THE SECOND PATIENT (B)(6).

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 24435663 ↗
  • MalfunctionFeb 24, 2026Application Program Problem

    THE DEVICE IS INCLUDED IN THE FA-Q125-HF-1 CM3100 DUPLICATED PATIENT PROFILE IN HF CLOUD INITIATED ON 30JAN2025. ABBOTT R&D INTERNAL TESTING AND CODE REVIEW IDENTIFIED AN ISSUE WHERE THE READINGS FROM ONE CM3100 SYSTEM SESSION FOR ONE PATIENT (PATIENT A) WERE INCORRECTLY REPORTED UNDER A DIFFERENT PATIENT (PATIENT B). NO PATIENT INJURY WAS REPORTED. THE ISSUE IS CURRENTLY UNDER INVESTIGATION. MDR-(B)(4) WAS CREATED FOR THE SECOND PATIENT (PATIENT [X]).

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 24435589 ↗
  • MalfunctionFeb 23, 2026Application Program Problem

    ABBOTT R&D INTERNAL TESTING AND CODE REVIEW IDENTIFIED AN ISSUE WHERE THE READINGS FROM ONE CM3100 SYSTEM SESSION FOR ONE PATIENT (PATIENT A) WERE INCORRECTLY REPORTED UNDER A DIFFERENT PATIENT (PATIENT B). NO PATIENT INJURY WAS REPORTED. THE ISSUE IS CURRENTLY UNDER INVESTIGATION. (B)(4) WAS CREATED FOR THE SECOND PATIENT (PATIENT B).

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 24421970 ↗
  • MalfunctionFeb 23, 2026Application Program Problem

    ABBOTT R&D INTERNAL TESTING AND CODE REVIEW IDENTIFIED AN ISSUE WHERE THE READINGS FROM ONE CM3100 SYSTEM SESSION FOR ONE PATIENT (PATIENT A) WERE INCORRECTLY REPORTED UNDER A DIFFERENT PATIENT (PATIENT B). NO PATIENT INJURY WAS REPORTED. THE ISSUE IS CURRENTLY UNDER INVESTIGATION. (B)(4) WAS CREATED FOR THE SECOND PATIENT (PATIENT A).

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 24421943 ↗
  • MalfunctionFeb 19, 2026Application Program Problem

    ABBOTT R&D INTERNAL TESTING AND CODE REVIEW IDENTIFIED AN ISSUE WHERE THE READINGS FROM ONE CM3100 SYSTEM SESSION FOR ONE PATIENT (PATIENT A) WERE INCORRECTLY REPORTED UNDER A DIFFERENT PATIENT (PATIENT B). NO PATIENT INJURY WAS REPORTED. THE ISSUE IS CURRENTLY UNDER INVESTIGATION. MDR-2026-05546 WAS CREATED FOR THE SECOND PATIENT (PATIENT B).

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 24387807 ↗
  • MalfunctionFeb 19, 2026Application Program Problem

    ABBOTT R&D INTERNAL TESTING AND CODE REVIEW IDENTIFIED AN ISSUE WHERE THE READINGS FROM ONE CM3100 SYSTEM SESSION FOR ONE PATIENT (PATIENT: (B)(6) WERE INCORRECTLY REPORTED UNDER A DIFFERENT PATIENT (PATIENT: (B)(6)). NO PATIENT INJURY WAS REPORTED. THE ISSUE IS CURRENTLY UNDER INVESTIGATION. MDR: (B)(4) WAS CREATED FOR THE SECOND PATIENT (PATIENT: (B)(6).

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 24387790 ↗
  • MalfunctionFeb 19, 2026Application Program Problem

    ABBOTT R&D INTERNAL TESTING AND CODE REVIEW IDENTIFIED AN ISSUE WHERE THE READINGS FROM ONE CM3100 SYSTEM SESSION FOR ONE PATIENT (PATIENT A) WERE INCORRECTLY REPORTED UNDER A DIFFERENT PATIENT (PATIENT B). NO PATIENT INJURY WAS REPORTED. THE ISSUE IS CURRENTLY UNDER INVESTIGATION. MDR-(B)(4) WAS CREATED FOR THE SECOND PATIENT (PATIENT B).

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 24387785 ↗
  • MalfunctionFeb 19, 2026Application Program Problem

    ABBOTT R&D INTERNAL TESTING AND CODE REVIEW IDENTIFIED AN ISSUE WHERE THE READINGS FROM ONE CM3100 SYSTEM SESSION FOR ONE PATIENT (PATIENT A) WERE INCORRECTLY REPORTED UNDER A DIFFERENT PATIENT (PATIENT B). NO PATIENT INJURY WAS REPORTED. THE ISSUE IS CURRENTLY UNDER INVESTIGATION. MDR-2026-06016 WAS CREATED FOR THE SECOND PATIENT (PATIENT A).

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 24387761 ↗
  • MalfunctionFeb 19, 2026Application Program Problem

    ABBOTT R&D INTERNAL TESTING AND CODE REVIEW IDENTIFIED AN ISSUE WHERE THE READINGS FROM ONE CM3100 SYSTEM SESSION FOR ONE PATIENT (PATIENT A) WERE INCORRECTLY REPORTED UNDER A DIFFERENT PATIENT (PATIENT B). NO PATIENT INJURY WAS REPORTED. THE ISSUE IS CURRENTLY UNDER INVESTIGATION. MDR-(B)(4) WAS CREATED FOR THE SECOND PATIENT (PATIENT B).

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 24387744 ↗
  • MalfunctionFeb 19, 2026Application Program Problem

    ABBOTT R&D INTERNAL TESTING AND CODE REVIEW IDENTIFIED AN ISSUE WHERE THE READINGS FROM ONE CM3100 SYSTEM SESSION FOR ONE PATIENT (PATIENT A) WERE INCORRECTLY REPORTED UNDER A DIFFERENT PATIENT (PATIENT B). NO PATIENT INJURY WAS REPORTED. THE ISSUE IS CURRENTLY UNDER INVESTIGATION. MDR-2026-06019 WAS CREATED FOR THE SECOND PATIENT (PATIENT A).

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 24387734 ↗
  • MalfunctionFeb 13, 2026Application Program Problem

    ABBOTT R&D INTERNAL TESTING AND CODE REVIEW IDENTIFIED AN ISSUE WHERE THE READINGS FROM ONE CM3100 SYSTEM SESSION FOR ONE PATIENT (PATIENT A) WERE INCORRECTLY REPORTED UNDER A DIFFERENT PATIENT (PATIENT B). NO PATIENT INJURY WAS REPORTED. THE ISSUE IS CURRENTLY UNDER INVESTIGATION. (B)(4) WAS CREATED FOR THE SECOND PATIENT (PATIENT B).

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 24337262 ↗
  • MalfunctionFeb 13, 2026Application Program Problem

    ABBOTT R&D INTERNAL TESTING AND CODE REVIEW IDENTIFIED AN ISSUE WHERE THE READINGS FROM ONE CM3100 SYSTEM SESSION FOR ONE PATIENT (PATIENT A) WERE INCORRECTLY REPORTED UNDER A DIFFERENT PATIENT (PATIENT B). NO PATIENT INJURY WAS REPORTED. THE ISSUE IS CURRENTLY UNDER INVESTIGATION. (B)(4) WAS CREATED FOR THE SECOND PATIENT (PATIENT A).

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 24337230 ↗
  • MalfunctionFeb 13, 2026Application Program Problem

    ABBOTT R&D INTERNAL TESTING AND CODE REVIEW IDENTIFIED AN ISSUE WHERE THE READINGS FROM ONE CM3100 SYSTEM SESSION FOR ONE PATIENT (PATIENT A) WERE INCORRECTLY REPORTED UNDER A DIFFERENT PATIENT (PATIENT B). NO PATIENT INJURY WAS REPORTED. THE ISSUE IS CURRENTLY UNDER INVESTIGATION. (B)(4) WAS CREATED FOR THE SECOND PATIENT (PATIENT B).

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 24337203 ↗
  • MalfunctionFeb 13, 2026Application Program Problem

    ABBOTT R&D INTERNAL TESTING AND CODE REVIEW IDENTIFIED AN ISSUE WHERE THE READINGS FROM ONE CM3100 SYSTEM SESSION FOR ONE PATIENT (PATIENT A) WERE INCORRECTLY REPORTED UNDER A DIFFERENT PATIENT (PATIENT B). NO PATIENT INJURY WAS REPORTED. THE ISSUE IS CURRENTLY UNDER INVESTIGATION. MDR-(B)(4) WAS CREATED FOR THE SECOND PATIENT (PATIENT A).

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 24337195 ↗

Other System, hemodynamic, implantable devices

All System, hemodynamic, implantable devices →

Sources and updates

How reports and recalls are matched · Editorial policy · Report an error on this page