Reported Reactions

Devices › Compressor, cardiac, external

Device brand name · Cardiac resuscitator line-powered

AutoPulse Resuscitation System: medical device reports filed with FDA

232 reports name it, 2003–2026. Manufacturer given most often on reports: Zoll Circulation. Product code DRM.

232
device reports naming the brand
0% of all MAUDE reports · about 10 a year
22
reports, 12 months to August 2026
24 in the 12 months before
90.5%
classified as malfunction
95.8% across the product code
0.9%
classified as death, as reported
2 reports · not verified by FDA

FDA's MAUDE database holds 232 reports that name the brand "AutoPulse Resuscitation System" (cardiac resuscitator line-powered), received between February 2003 and August 2026; the manufacturer given most often on reports is Zoll Circulation. Spellings of one product vary from report to report.

22 reports arrived in the 12 months to August 2026, close to the 24 of 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 (90.5%), other (5.2%) and injury (3.4%); across all compressor, cardiac, external reports (product code DRM) death is recorded in 1.8% and malfunction in 95.8%. Event type is the reporter's classification of the report, not a verified outcome.

The device problems coded most often are visual prompts will not clear (38.4%), break (16.8%) and device displays incorrect message (11.2%). The patient problems coded most often are resuscitation, therapy/non-surgical treatment, additional and therapy/non-surgical treatment, aborted/stopped. 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

01223Sep 2021: 0Oct 2021: 0Nov 2021: 0Dec 2021: 02022Jan 2022: 0Feb 2022: 0Mar 2022: 0Apr 2022: 0May 2022: 0Jun 2022: 0Jul 2022: 0Aug 2022: 0Sep 2022: 0Oct 2022: 0Nov 2022: 0Dec 2022: 02023Jan 2023: 0Feb 2023: 0Mar 2023: 0Apr 2023: 0May 2023: 0Jun 2023: 0Jul 2023: 0Aug 2023: 0Sep 2023: 0Oct 2023: 22Nov 2023: 13Dec 2023: 232024Jan 2024: 0Feb 2024: 0Mar 2024: 0Apr 2024: 0May 2024: 0Jun 2024: 0Jul 2024: 6Aug 2024: 4Sep 2024: 1Oct 2024: 3Nov 2024: 3Dec 2024: 12025Jan 2025: 3Feb 2025: 2Mar 2025: 1Apr 2025: 1May 2025: 1Jun 2025: 1Jul 2025: 5Aug 2025: 2Sep 2025: 1Oct 2025: 2Nov 2025: 1Dec 2025: 12026Jan 2026: 1Feb 2026: 1Mar 2026: 3Apr 2026: 1May 2026: 2Jun 2026: 4Jul 2026: 2Aug 2026: 3

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

031622003: 6220032004: 362005: 320052006: 52008: 420082011: 52012: 320122023: 582024: 1820242025: 212026: 172026

Event type and report source

Event type, as classified on the report

Death0.9%2
Injury3.4%8
Malfunction90.5%210
Other5.2%12
Not given0%0

Who filed the report

Manufacturer report100%232
Voluntary report0%0
User facility report0%0
Distributor report0%0
Not given0%0

Grey bar: all 11,439 reports carrying product code DRM. Event type is the filer's classification and is not verified by FDA.

Device problems coded

Device problem (FDA code)ReportsShareShare across product code
Visual prompts will not clear8938.4%40.6%
Breakthe device broke3916.8%1.5%
Device displays incorrect message2611.2%21.6%
Device issuea problem with the device125.2%0.8%
Unexpected shutdown62.6%1.3%
Component(s), broken52.2%0.1%
Other (for use when an appropriate device code cannot be identified)52.2%0.1%
Replace41.7%0.1%
Computer software problema software problem31.3%0%
Display or visual feedback problem31.3%1.5%
Fitting problem31.3%0.4%
Noise31.3%0%
Failure to power up20.9%3.5%
Malfunction20.9%0.1%
Material separation20.9%0.1%
Complete loss of power10.4%0.1%
Detachment of device component10.4%0.1%
Device damaged prior to usethe device was damaged before use10.4%0%
Difficult to position10.4%0%
Display difficult to read10.4%0.8%

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)ReportsShare
Resuscitation208.6%
Therapy/non-surgical treatment, additional146%
Therapy/non-surgical treatment, aborted/stopped104.3%
Deaththe patient died; cause not stated by this term73%
Manual ventilation required62.6%
No patient involvement62.6%
Hospitalization required41.7%
Bone fracture(s)20.9%
Loss of pulse20.9%
Other (for use when an appropriate patient code cannot be identified)20.9%
Abrasion10.4%
Asphyxia10.4%
Asystole10.4%
Cardiac arrestthe heart stopped10.4%
Chest painchest pain10.4%

Patient problem codes are present mainly in reports filed since 2019 and are often blank.

In context

MeasureAutoPulse Resuscitation SystemProduct code DRMAll MAUDE reports
Reports23211,43926,136,888
Share of that pool—2%0%
Classified as death, per 1,000 reports9189
Classified as injury3.4%2.1%36.2%
Classified as malfunction90.5%95.8%62.3%
Filed by the manufacturer100%98.3%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 DRM

BrandReportsLatest 12 monthsClassified as death
Autopulse Resuscitation Model 1003,77900%
Autopulse Platform Resuscitation1,85900%
Autopulse Resuscitation System Model 1001,56802.8%
AutoPulseResuscitation System9533340%
Autopulse Nimh Battery80703.6%
AutoPulse Li-ion Battery1,415270.1%
Autopulse Lifeband24600.4%
Lucas 3 Chest Compression System2161855.1%
AutoPulse NXT Resuscitation System1921130%
LUCAS 3 CPR Chest Compression System1581581.3%
Lifeline4,8772,1170.4%
Zoll221014%

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 AutoPulse Resuscitation System reports

How many FDA reports name AutoPulse Resuscitation System?

232 medical device reports in the openFDA MAUDE release of 28 Sep 2026, covering reports received through August 2026; 22 in the latest 12 months.

What kinds of events are reported?

malfunction (90.5%), other (5.2%) and injury (3.4%). "Event type" is how the report was classified when filed: death, injury, malfunction or other.

What device problems are coded?

visual prompts will not clear (38.4%), break (16.8%), device displays incorrect message (11.2%), device issue (5.2%) and unexpected shutdown (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 AutoPulse Resuscitation 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.