Sign in
Taking people in United StatesNo phase

Long-term reliability of Medtronic heart rhythm devices in heart patients

Tracks how long Medtronic heart devices keep working in people with arrhythmia.

Key facts

Who runs it
Medtronic
Where
Akron, Albuquerque, Allentown, Anchorage, Atlanta, Aurora, Austin, Bakersfield, Baltimore, Baton Rouge, Bethesda, Bethlehem, Birmingham, Boston, Bradenton, Burlington, Centennial, Chandler, Charlottesville, Chula Vista, Cincinnati, Clearwater, Cleveland, Clinton, Colorado Springs, Columbia, Columbus, Coon Rapids, Dallas, Danville, Denver, Durham, Eatontown, Edgewood, Erie, Evansville, Falls Church, Fort Worth, Germantown, Hartford, Hattiesburg, Hollywood, Houston, Huntington, Hyattsville, Indianapolis, Jacksonville, Jonesboro, Kansas City, La Jolla, Lakewood, Lancaster, Lansing, Little Rock, Los Angeles, Louisville, Madison, Manhasset, Marietta, Marlton, Marquette, Milwaukee, Minneapolis, Morristown, Mount Kisco, Nashville, New Brunswick, New Haven, New York, Ocean City, Oklahoma City, Olympia, Omaha, Palm Springs, Panama City, Philadelphia, Pittsburgh, Plano, Port Jefferson, Portland, Poughkeepsie, Raleigh, Rancho Mirage, Redwood City, Ridgewood, Robbinsdale, Rochester, Safety Harbor, Saint Cloud, Saint Paul, Salinas, Salisbury, San Diego, Sarasota, Shreveport, Silver Spring, Spokane, St Louis, Stanford, Takoma Park, Tampa, The Woodlands, Toledo, Torrance, Tyler, Utica, Van Nuys, Ventura, Washington D.C., West Des Moines, Wilkes-Barre, and Ypsilanti, United StatesSee the 112 sitesAlso in 34 other countries, 224 sites
Trial code
Registry title
Product Performance Report: Evaluate Long-term Reliability & Performance of Medtronic Marketed Cardiac Therapy Products
Status
Recruiting
People taking part
20,000 people, planned
Started
Jan 1983
Expected to end
Dec 2040
Type of study
Observational
Treatments tested
  • Device
Record updated
4 November 2026

Who can take part

AI summary

From the trial's eligibility criteria. Machine-read from the registry text on this page, so it can be wrong. The registry text below and the trial team decide who can take part.

The trial is looking for people who are about to get, or just got, a Medtronic heart rhythm device (pacing, sensing or defibrillation). It follows how long the devices keep working.

Sex
All sexes can join.
Earlier treatment
People must be due to get, or have had within the last 30 days, at least one Medtronic market-released device for pacing, sensing or defibrillation. Or they took part in a qualifying study (IDE) of such a device with complete implant and follow-up data.

Main reasons for not taking part

  • People who cannot be reached for follow-up now or later
  • People with exclusion criteria required by local law (EMEA only)
  • People implanted at a non-participating center when implant data and current status cannot be confirmed within 30 days after implant
  • People with a Medtronic device whose set enrollment limit for that product has been exceeded

The registry criteria, word for word

Show all 8 criteriaShow less

Who can take part

  • Subject or appropriate legal guardians provide written informed consent and/or authorization for access to and use of health information as required by an institution's IRB/MEC/REB; AND one of the following must also apply:
  • Subject is indicated for implant or within 30 days post-implant of at least one Medtronic market-released product used for a pacing, sensing or defibrillation application
  • Subjects who participated in a qualifying study (IDE) of a Medtronic market-released product with complete implant and follow-up data and subject or appropriate legal guardian authorizes release of subject study data

Who cannot take part

  • Subjects receiving an implant of a Medtronic device at a non-participating center and the implant data and current status cannot be confirmed within 30 days after implant
  • Subjects who are, or will be inaccessible for follow-up
  • Subjects with exclusion criteria required by local law (EMEA only)
  • Subjects implanted with a Medtronic device whose predetermined enrollment limit for that specific product has been exceeded

Other criteria

  • Subjects who meet the following inclusion criteria and do not meet any of the following exclusion criteria are eligible for enrollment

Where in United States

Also in 34 other countries, 224 sites

  • Akron, OhioHospital not named in the registryContact: Medtronic CRM Clinical TrialsNo longer taking part
  • Albuquerque, New MexicoHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Allentown, PennsylvaniaHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Anchorage, AlaskaHospital not named in the registryContact: Medtronic CRM Clinical TrialsNo longer taking part
  • Atlanta, GeorgiaHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Aurora, ColoradoHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Austin, TexasHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Bakersfield, CaliforniaHospital not named in the registryContact: Medtronic CRM Clinical TrialsNo longer taking part
  • Baltimore, MarylandHospital not named in the registryContact: Medtronic CRM Clinical TrialsNo longer taking part
  • Baton Rouge, LouisianaHospital not named in the registryContact: Medtronic CRM Clinical TrialsNo longer taking part
  • Bethesda, MarylandHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Bethlehem, PennsylvaniaHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Birmingham, AlabamaHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Boston, MassachusettsHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Bradenton, FloridaHospital not named in the registryContact: Medtronic CRM Clinical TrialsNo longer taking part
  • Burlington, MassachusettsHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Centennial, ColoradoHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Chandler, ArizonaHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Charlottesville, VirginiaHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Chula Vista, CaliforniaHospital not named in the registryContact: Medtronic CRM Clinical TrialsNo longer taking part
  • Cincinnati, OhioHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Clearwater, FloridaHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Cleveland, OhioHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Clinton, MarylandHospital not named in the registryContact: Medtronic CRM Clinical TrialsNo longer taking part
  • Colorado Springs, ColoradoHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Columbia, MarylandHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Columbus, OhioHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Coon Rapids, MinnesotaHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Dallas, TexasHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Danville, PennsylvaniaHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Denver, ColoradoHospital not named in the registryContact: Medtronic CRM Clinical TrialsNo longer taking part
  • Durham, North CarolinaHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Eatontown, New JerseyHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Edgewood, KentuckyHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Erie, PennsylvaniaHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Evansville, IndianaHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Falls Church, VirginiaHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Fort Worth, TexasHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Germantown, TennesseeHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Hartford, ConnecticutHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Hattiesburg, MississippiHospital not named in the registryContact: Medtronic CRM Clinical TrialsNo longer taking part
  • Hollywood, FloridaHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Houston, TexasHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Huntington, New YorkHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Hyattsville, MarylandHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Indianapolis, IndianaHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Jacksonville, FloridaHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Jonesboro, ArkansasHospital not named in the registryContact: Medtronic CRM Clinical TrialsNo longer taking part
  • Kansas City, KansasHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • La Jolla, CaliforniaHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Lakewood, ColoradoHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Lancaster, PennsylvaniaHospital not named in the registryContact: Medtronic CRM Clinical TrialsNo longer taking part
  • Lansing, MichiganHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Little Rock, ArkansasHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Los Angeles, CaliforniaHospital not named in the registryContact: Medtronic CRM Clinical TrialsNo longer taking part
  • Louisville, KentuckyHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Madison, WisconsinHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Manhasset, New YorkHospital not named in the registryContact: Medtronic CRM Clinical TrialsNo longer taking part
  • Marietta, GeorgiaHospital not named in the registryContact: Medtronic CRM Clinical TrialsNo longer taking part
  • Marlton, New JerseyHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Marquette, MichiganHospital not named in the registryContact: Medtronic CRM Clinical TrialsNo longer taking part
  • Milwaukee, WisconsinHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Minneapolis, MichiganHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Morristown, New JerseyHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Mount Kisco, New YorkHospital not named in the registryContact: Medtronic CRM Clinical TrialsNo longer taking part
  • Nashville, TennesseeHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • New Brunswick, New JerseyHospital not named in the registryContact: Medtronic CRM Clinical TrialsNo longer taking part
  • New Haven, ConnecticutHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • New YorkHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Ocean City, New JerseyHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Oklahoma City, OklahomaHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Olympia, WashingtonHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Omaha, NebraskaHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Palm Springs, CaliforniaHospital not named in the registryContact: Medtronic CRM Clinical TrialsNo longer taking part
  • Panama City, FloridaHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Philadelphia, PennsylvaniaHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Pittsburgh, PennsylvaniaHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Plano, TexasHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Port Jefferson, New YorkHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Portland, OregonHospital not named in the registryContact: Medtronic CRM Clinical TrialsNo longer taking part
  • Poughkeepsie, New YorkHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Raleigh, North CarolinaHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Rancho Mirage, CaliforniaHospital not named in the registryContact: Medtronic CRM Clinical TrialsNo longer taking part
  • Redwood City, CaliforniaHospital not named in the registryContact: Medtronic CRM Clinical TrialsNo longer taking part
  • Ridgewood, New JerseyHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Robbinsdale, MinnesotaHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Rochester, MinnesotaHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Safety Harbor, FloridaHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Saint Cloud, MinnesotaHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Saint Paul, MinnesotaHospital not named in the registryContact: Medtronic CRM Clinical TrialsNo longer taking part
  • Salinas, CaliforniaHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Salisbury, North CarolinaHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • San Diego, CaliforniaHospital not named in the registryContact: Medtronic CRM Clinical TrialsNo longer taking part
  • Sarasota, FloridaHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Shreveport, LouisianaHospital not named in the registryContact: Medtronic CRM Clinical TrialsNo longer taking part
  • Silver Spring, MarylandHospital not named in the registryContact: Medtronic CRM Clinical TrialsNo longer taking part
  • Spokane, WashingtonHospital not named in the registryContact: Medtronic CRM Clinical TrialsNo longer taking part
  • St Louis, MissouriHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Stanford, CaliforniaHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Takoma Park, MarylandHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Tampa, FloridaHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • The Woodlands, TexasHospital not named in the registryContact: Medtronic CRM Clinical TrialsNo longer taking part
  • Toledo, OhioHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Torrance, CaliforniaHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Tyler, TexasHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Utica, New YorkHospital not named in the registryContact: Medtronic CRM Clinical TrialsNo longer taking part
  • Van Nuys, CaliforniaHospital not named in the registryContact: Medtronic CRM Clinical TrialsNo longer taking part
  • Ventura, CaliforniaHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Washington D.C., District of ColumbiaHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • West Des Moines, IowaHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Wilkes-Barre, PennsylvaniaHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people
  • Ypsilanti, MichiganHospital not named in the registryContact: Medtronic CRM Clinical TrialsTaking people

About the trial

What the trial wants to find out

The main purpose of the Product Performance Report (formerly referred to as System Longevity Study) is to evaluate long-term performance of Medtronic market-released cardiac rhythm products by analyzing product survival probabilities.

Treatments tested

  • Device

Questions to ask the study team

  1. How often do I need to come in, and for how long each time?
  2. Are travel costs paid?
  3. Can I keep my own doctor?
  4. What happens if I want to stop?

Contact the study team: see the registry record → Contacts and Locations

Print a page for my doctor

Data and sources

Registry record
Listed on ClinicalTrials.gov.How to verify a trial in the registry
Official title
Medtronic CRDM Product Performance Report
Plain-language title
Long-term reliability of Medtronic heart rhythm devices in heart patientsGenerated from the registry record. The registry title is the official one.
AI summary
From the trial's eligibility criteria. Read by machine on 12 November 2026.
Record updated
4 November 2026