Device type · DRG
Transmitters And Receivers, Physiological Signal, Radiofrequency
Last checked: Nov 19, 2026Source: openFDAMethods & limitations
Product code
DRG
Cardiovascular
Device class
Class II
FDA decisions since 2015
48
510(k), De Novo and PMA
Adverse event reports
76
Received Nov 1, 2025 to Nov 19, 2026
How FDA classifies it
- Device type
- Transmitters And Receivers, Physiological Signal, Radiofrequency
- Product code
- DRG
- Device class
- Class II
- Review panel
- Cardiovascular
- Regulation
- 21 CFR 870.2910
- Specialty
- Cardiology
- FDA record
- Classification database entry for DRG
Latest FDA decisions
The 8 newest of 48 since 2015.
K261569 · Decided Jul 9, 2026 · 58 days after receipt
Device type: Transmitters And Receivers, Physiological Signal, Radiofrequency (DRG) · Cardiology
K252984 · Decided Jan 22, 2026 · 126 days after receipt
Device type: Transmitters And Receivers, Physiological Signal, Radiofrequency (DRG) · Cardiology
- EasyTeleMed (2.0.2)510(k)
K252440 · Decided Oct 2, 2025 · 59 days after receipt
Device type: Transmitters And Receivers, Physiological Signal, Radiofrequency (DRG) · Cardiology
K250259 · Decided Jun 4, 2025 · 127 days after receipt
Device type: Transmitters And Receivers, Physiological Signal, Radiofrequency (DRG) · Cardiology
- iBSM510(k)
Iorbit Digital Technologies Private Limited
K243837 · Decided May 16, 2025 · 154 days after receipt
Device type: Transmitters And Receivers, Physiological Signal, Radiofrequency (DRG) · Cardiology
K242018 · Decided Nov 12, 2024 · 125 days after receipt
Device type: Transmitters And Receivers, Physiological Signal, Radiofrequency (DRG) · Cardiology
- BioButton System510(k)
K241101 · Decided Sep 26, 2024 · 157 days after receipt
Device type: Transmitters And Receivers, Physiological Signal, Radiofrequency (DRG) · Cardiology
- ANNE Chest510(k)
K240251 · Decided Jun 3, 2024 · 125 days after receipt
Device type: Transmitters And Receivers, Physiological Signal, Radiofrequency (DRG) · Cardiology
Reports received
76
Received Nov 1, 2025 to Nov 19, 2026
Malfunction reports
74
97% of reports
Injury reports
2
2.6% of reports
Death reports
0
0.0% of reports
Adverse event reports received per month
By the date FDA received each report, stacked by event type. The newest month is incomplete.
- Malfunction
- Injury
- Death
- Other
View as table
| Month | Malfunction | Injury | Death | Other |
|---|---|---|---|---|
| Dec 23 | 4 | 0 | 0 | 0 |
| Jan 24 | 6 | 0 | 0 | 0 |
| Feb 24 | 3 | 0 | 0 | 0 |
| Mar 24 | 3 | 0 | 0 | 0 |
| Apr 24 | 0 | 0 | 2 | 0 |
| May 24 | 1 | 0 | 0 | 0 |
| Jun 24 | 1 | 0 | 0 | 0 |
| Jul 24 | 1 | 0 | 0 | 0 |
| Aug 24 | 1 | 0 | 0 | 0 |
| Sep 24 | 0 | 0 | 0 | 0 |
| Oct 24 | 1 | 0 | 0 | 0 |
| Nov 24 | 2 | 0 | 0 | 0 |
| Dec 24 | 5 | 0 | 0 | 0 |
| Jan 25 | 0 | 0 | 0 | 0 |
| Feb 25 | 2 | 0 | 0 | 0 |
| Mar 25 | 3 | 0 | 0 | 0 |
| Apr 25 | 2 | 0 | 0 | 0 |
| May 25 | 1 | 0 | 0 | 0 |
| Jun 25 | 1 | 0 | 0 | 0 |
| Jul 25 | 5 | 1 | 0 | 0 |
| Aug 25 | 11 | 0 | 0 | 0 |
| Sep 25 | 7 | 1 | 0 | 0 |
| Oct 25 | 8 | 0 | 0 | 0 |
| Nov 25 | 4 | 1 | 0 | 0 |
| Dec 25 | 6 | 0 | 0 | 0 |
| Jan 26 | 7 | 0 | 0 | 0 |
| Feb 26 | 6 | 0 | 0 | 0 |
| Mar 26 | 9 | 0 | 0 | 0 |
| Apr 26 | 7 | 0 | 0 | 0 |
| May 26 | 4 | 0 | 0 | 0 |
| Jun 26 | 3 | 0 | 0 | 0 |
| Jul 26 | 6 | 1 | 0 | 0 |
| Aug 26 | 12 | 0 | 0 | 0 |
| Sep 26 | 6 | 0 | 0 | 0 |
| Oct 26 | 4 | 0 | 0 | 0 |
| Nov 26 | 0 | 0 | 0 | 0 |
Manufacturers named most often
Last 12 months. Bigger sellers get more reports. This is not a ranking of safety.
Device problems as coded
Last 12 months. FDA's terms. A report can carry several.
- Communication or Transmission Problem60
- Unable to Obtain Readings19
- Intermittent Communication Failure14
- Output Problem8
- Data Problem3
- Incorrect Measurement2
- Incorrect, Inadequate or Imprecise Result or Readings2
- Patient Data Problem2
- Wireless Communication Problem2
- Application Program Problem1
Patient problems as coded
Last 12 months. FDA's terms. A report can carry several.
- No Clinical Signs, Symptoms or Conditions73
- Arrhythmia1
- Burn(s)1
- High Blood Pressure/ Hypertension1
- Insufficient Information1
- Itching Sensation1
- Sleep Dysfunction1
- Urticaria1
Recent recalls
From FDA's recall database. FDA lists each recalled product separately, so one recall can appear several times. A recall is often a correction or a labeling change, not a removal from the market.
Z-3013-2026 · Started Jul 20, 2026 · Posted by FDA Aug 25, 2026
Reason given: A communication anomoly may result in incorrect electrocardiogram waveforms of a patient and an inaccurate beats-per-minute calculation.
Cause as FDA categorized it: Software design
Z-2616-2024 · Started Jul 19, 2024 · Posted by FDA Aug 14, 2024
Reason given: Software anomaly causing the skin temperature measurement accuracy to be slightly out of specification.
Cause as FDA categorized it: Device Design
- WMTS Telemetry Receiver, Multiple Patient Receiver, Model Number/ UDI: ORG 9100A/ 00841983102554 ORG 9110A/ 00841983102561 ORG 9700A/No UDIOpen, Classified
Z-1162-2021 · Started Jan 8, 2021
Reason given: Incorrect Date Stamp or No Data Transfer on Telemetry Receiver and Transmitter.
Cause as FDA categorized it: Software design
Z-2537-2020 · Started May 21, 2020 · Posted by FDA Jul 10, 2020
Reason given: A healthcare provider (HCP) noticed a patient had a lowered historic SpO2 reading that the software should have triggered a notification to the care team, but no notification was found. A software defect was encountered causing the lack of notification. The defect could result in exposing a patient to potential...
Cause as FDA categorized it: Software Design Change
Z-3132-2017 · Started May 15, 2017
Reason given: The device history record (DHR) was missing its test documentation for final HIPOT (high potential) electrical testing.
Cause as FDA categorized it: Unknown/Undetermined by firm
Z-1708-2017 · Started Mar 2, 2017
Reason given: eCareCoordinator (eCC) is intended for use in data aggregation, patient interaction facilitation, storage and clinical information management with independent physiological devices and ancillary systems that are connected either directly or through networks. The software is intended to provide patient information from...
Cause as FDA categorized it: Software Manufacturing/Software Deployment
Z-1557-2016 · Started Mar 10, 2016
Reason given: The adherence check generates a software error. Two issues occur as a result of the software error: 1) No adherence flag is generated for that day; 2) No task is generated for the date 14 days later. An error message is generated and forwarded to operations. Subsequently, for days in which no task was generated,...
Cause as FDA categorized it: Under Investigation by firm
Z-1652-2013 · Started Feb 24, 2012 · Posted by FDA Jul 2, 2013
Reason given: Braemar has recently became aware of a battery related incident that occurred with EWT battery packs that are used in a Braemer ER920W wireless event monitor and Fusion device. The event did not result in any patient related injury or present any clinical impact.
Cause as FDA categorized it: Material/Component Contamination
Showing the 8 newest of 12 recall records in FDA's data.
For information only. Nothing on this page is investment, legal, tax or medical advice, and nothing here is an offer to sell or a solicitation of an offer to buy any security. The data comes from public government sources, which can be incomplete, delayed or wrong. Check the original record before relying on it.