Reported Reactions

Devices › Pacemaker/icd/crt non-implanted components

Device brand name · External programmer

LATITUDE Programming System: medical device reports filed with FDA

1,323 reports name it, 2021–2026. Manufacturer given most often on reports: Boston Scientific. Product code OSR.

1,323
device reports naming the brand
0% of all MAUDE reports · about 241 a year
108
reports, 12 months to August 2026
173 in the 12 months before
98.6%
classified as malfunction
99.8% across the product code
0%
classified as death, as reported
0 reports · not verified by FDA

FDA's MAUDE database holds 1,323 reports that name the brand "LATITUDE Programming System" (external programmer), received between January 2021 and August 2026; the manufacturer given most often on reports is Boston Scientific. Spellings of one product vary from report to report.

108 reports arrived in the 12 months to August 2026, down 38% from 173 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.6%) and injury (1.4%); across all pacemaker/icd/crt non-implanted components reports (product code OSR) death is recorded in 0% and malfunction in 99.8%. Event type is the reporter's classification of the report, not a verified outcome.

The device problems coded most often are key or button unresponsive/not working (81.3%), defective device (52.8%) and application program problem (8.1%). The patient problems coded most often are asystole, syncope/fainting and bradycardia. 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

0203405Sep 2021: 0Oct 2021: 1Nov 2021: 1Dec 2021: 12022Jan 2022: 0Feb 2022: 2Mar 2022: 0Apr 2022: 6May 2022: 0Jun 2022: 12Jul 2022: 9Aug 2022: 5Sep 2022: 9Oct 2022: 16Nov 2022: 5Dec 2022: 102023Jan 2023: 6Feb 2023: 6Mar 2023: 1Apr 2023: 42May 2023: 405Jun 2023: 181Jul 2023: 24Aug 2023: 18Sep 2023: 35Oct 2023: 40Nov 2023: 30Dec 2023: 232024Jan 2024: 21Feb 2024: 12Mar 2024: 17Apr 2024: 24May 2024: 27Jun 2024: 18Jul 2024: 15Aug 2024: 16Sep 2024: 17Oct 2024: 17Nov 2024: 10Dec 2024: 182025Jan 2025: 7Feb 2025: 12Mar 2025: 16Apr 2025: 13May 2025: 15Jun 2025: 20Jul 2025: 26Aug 2025: 2Sep 2025: 4Oct 2025: 10Nov 2025: 9Dec 2025: 72026Jan 2026: 8Feb 2026: 6Mar 2026: 8Apr 2026: 5May 2026: 11Jun 2026: 12Jul 2026: 15Aug 2026: 13

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

04068112021: 720212022: 7420222023: 81120232024: 21220242025: 14120252026: 782026

Event type and report source

Event type, as classified on the report

Death0%0
Injury1.4%18
Malfunction98.6%1,305
Other0%0
Not given0%0

Who filed the report

Manufacturer report99.9%1,322
Voluntary report0%0
User facility report0%0
Distributor report0%0
Not given0.1%1

Grey bar: all 58,914 reports carrying product code OSR. Event type is the filer's classification and is not verified by FDA.

Device problems coded

Device problem (FDA code)ReportsShareShare across product code
Key or button unresponsive/not working1,07681.3%1.8%
Defective devicethe device was defective69852.8%1.3%
Application program problem1078.1%0.3%
Display or visual feedback problem695.2%3%
Nonstandard device302.3%0.1%
Interrogation problem262%0.1%
No display/image201.5%0%
Material integrity problema problem with the device material141.1%0%
Failure to power up120.9%0.1%
Pacing problem100.8%0.1%
Telemetry discrepancy90.7%0%
Date/time-related software problem70.5%0%
Connection problema connection problem60.5%0.1%
Device sensing problem60.5%0%
Computer operating system problem40.3%73.3%
Failure to charge20.2%0%
Noise, audible20.2%0%
Communication or transmission problemthe device could not communicate or transmit10.1%2.2%
Computer software problema software problem10.1%69.3%
Computer system security problem10.1%0%

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
Asystole131%
Syncope/fainting70.5%
Bradycardiaslow heart rate40.3%
Cardiac arrestthe heart stopped20.2%
Dizzinesslight-headedness or unsteadiness20.2%
Burn(s)a burn10.1%
Convulsion/seizure10.1%
Dyspneashortness of breath10.1%
Electric shockan electric shock10.1%
Falla fall10.1%
Head injurya head injury10.1%
Loss of consciousnesspassing out10.1%
Low blood pressure/ hypotension10.1%
Presyncope10.1%

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

In context

MeasureLATITUDE Programming SystemProduct code OSRAll MAUDE reports
Reports1,32358,91426,136,888
Share of that pool—2.2%0%
Classified as death, per 1,000 reports009
Classified as injury1.4%0.2%36.2%
Classified as malfunction98.6%99.8%62.3%
Filed by the manufacturer99.9%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 OSR

BrandReportsLatest 12 monthsClassified as death
CareLink SmartSync Common App iOS56,79955,6950%
CareLink SmartSync Base1,8642270%
Smart Monitor262320%
Smartview31750%
LATITUDE Communicator338600%
Patient Connector207830%
Communicator25900%
Carelink Encore36800%
SmartTouch6681320%
Autogen2,1922121%
Merlin Net / Hf Portal259340%
MyCareLink Patient Monitor893470.1%
Screwdriver396150%
Altrua 60971290.6%
Carelink Smartsync Platform Ios87010%

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 LATITUDE Programming System reports

How many FDA reports name LATITUDE Programming System?

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

What kinds of events are reported?

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

What device problems are coded?

key or button unresponsive/not working (81.3%), defective device (52.8%), application program problem (8.1%), display or visual feedback problem (5.2%) and nonstandard device (2.3%). These are FDA's device problem codes as entered on the report.

Who files these reports?

manufacturer reports (99.9%). Manufacturers and user facilities are required to report; voluntary reports come from health professionals and the public.

Do these reports show that LATITUDE Programming 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.