510(k) Report

510(k) · Cleared

Cleared

CloudHRV™ System (100-01-001)

K241217510(k) TraditionalCleared Jan 16, 2025260-day reviewClass II21 CFR 870.2340

Data to Oct 25, 2026 (FDA decisions) Oct 12, 2026 (recalls) Sep 30, 2026 (MAUDE) refreshed weekly, last Nov 3, 2026

Inmedix, Inc. · DPS Electrocardiograph

Cleared on Jan 16, 2025 as substantially equivalent to K071168 (Dyansys, Inc., 2007) after a 260-day review. Its family tree reaches back 4 generations to 1995.

Decided
Jan 16, 2025
Review
260 days
Class
Class II
Product code
DPS
Recalls
None
Predicates
1

Its longest line of descent runs back 4 generations to K950779 (1995). 10 ancestors in all, the oldest K820885 (1982). No later device cites it as a predicate yet.

Other ancestors, by year cleared 1999: 1 other ancestor1998: 1 other ancestor1997: 1 other ancestor1982: 1 other ancestor1994: 1 other ancestor1993: 1 other ancestorK950779 · Heart Rate Variability Software Option · Spacelabs, Inc. · 1995K972991 · Monitor One NDX · Qmed, Inc. · 1998K991831 · BMT Anscore Health Management System, Model 1.1 · Boston Medical Technologies, Inc. · 1999K071168 · The Portable Ansiscope · Dyansys, Inc. · 200719801990200020102020
Other ancestors, by generation 2 generations back: 2 other ancestors3 generations back: 2 other ancestors4 generations back: 2 other ancestors K071168 · The Portable Ansiscope · Dyansys, Inc. · 2007K991831 · BMT Anscore Health Management System, Model 1.1 · Boston Medical Technologies, Inc. · 1999K972991 · Monitor One NDX · Qmed, Inc. · 1998K950779 · Heart Rate Variability Software Option · Spacelabs, Inc. · 19950
  1. Root · 4 generations backK950779 Heart Rate Variability Software OptionSpacelabs, Inc. · 1995
  2. 3 generations backK972991 Monitor One NDXQmed, Inc. · 1998
  3. 2 generations backK991831 BMT Anscore Health Management System, Model 1.1Boston Medical Technologies, Inc. · 1999
  4. 1 generation backK071168 The Portable AnsiscopeDyansys, Inc. · 2007
  5. This deviceK241217 CloudHRV™ System (100-01-001)Inmedix, Inc. · 2025
View FIG. 1 as a table

Line of descent and top descendants

GenerationNumberDeviceApplicantDecidedRecalls
−4K950779Heart Rate Variability Software OptionSpacelabs, Inc.1995—
−3K972991Monitor One NDXQmed, Inc.1998—
−2K991831BMT Anscore Health Management System, Model 1.1Boston Medical Technologies, Inc.1999—
−1K071168The Portable AnsiscopeDyansys, Inc.2007—
0 (this device)K241217CloudHRV™ System (100-01-001)Inmedix, Inc.2025—

Other ancestors by year cleared

Year clearedDevicesWith a Class I recall
198210
199310
199410
199710
199810
199910
FIG. 1 — Lineage of K241217, 1995–2025Source: FDA 510(k) summaries, read by 510(k) Report · How lineage is built

Get the monthly Device Review Tracker

Notable FDA decisions, review times and new Class I recalls. See an issue.

Sources: FDA 510(k) database (decision fields), the FDA summary (predicates and indications), FDA recall and enforcement reports, and MAUDE; processed by 510(k) Report. Verify on FDA.gov · Methodology and accuracy.

Planning a device in DPS? A 510(k) Report weighs predicate choices, recall history and review times for a new device like this one.

Top candidate predicates for a new DPS device

  1. #1 K212112 Cardiologs Holter Platformscore 18.6 · 5 generations · no Class I recall
  2. #2 Held for the reportin the report
  3. #3 Held for the reportin the report
Get a 510(k) Report

What was it cleared against? (1)

Devices the submitter claimed this one is substantially equivalent to (*), and reference devices cited for a specific test or feature (†), as written in the FDA summary.

TypeNumberDeviceApplicantDecidedRecalls
*K071168The Portable Ansiscope
Summary page 5
…m Classification Name(s): Electrocardiograph Product Code/ Regulation: DPS / 870.2340 Classification: 2 Predicate Device: ANSiscope™ ECG Monitoring System (K071168) Subject Device Description The Inmedix® CloudHRV™ System acquires approximately 5 minutes of 3-lead electrocardiographic (ECG) d…
Dyansys, Inc.2007—

Also cleared against K071168: 3 other devices →

What descends from it?

No later submission names this one as a predicate yet.

Has anything in its family been recalled? (0 Class I)

No FDA recall names this device.

No ancestor or descendant has a Class I recall.

What does this lineage say?

  • The line of descent spans 30 years and passes through 5 companies; a new generation was cleared every 8.2 years on median.
  • None of the 10 ancestors has a recall.
  • 3 other devices also cite its predicate K071168.

How does its category compare?

All DPS devices

DPS Electrocardiograph: FDA decisions, review times, recalls and adverse event reports over 20 years. 2025, this device’s year, is highlighted.

FDA decisions per year · DPS

6in 2025

2007: 112008: 132009: 142010: 112011: 222012: 122013: 102014: 112015: 82016: 112017: 92018: 142019: 32020: 62021: 52022: 62023: 102024: 82025: 62026 (partial year): 6
2007high 22 (2011) · low 3 (2019)2026

2026 to Oct 25, outlined.

Median 510(k) review, days · DPS

163in 2025

2007: 87 days median2008: 31 days median2009: 84 days median2010: 104 days median2011: 154 days median2012: 117 days median2013: 134 days median2014: 253 days median2015: 178 days median2016: 229 days median2017: 177 days median2018: 221 days median2019: 178 days median2020: 224 days median2021: 135 days median2022: 244 days median2023: 236 days median2024: 260 days median2025: 163 days median2026 (partial year): 258 days median
2007high 260 (2024) · low 31 (2008)2026

Receipt to decision; years with fewer than 3 clearances left blank.

Recalls per year · DPS

3in 2025

2007: 22009: 12010: 22011: 12019: 92020: 22021: 12022: 12023: 32024: 4, 1 Class I2025: 32026 (partial year): 4
2007high 9 (2019) · low 0 (2008)2026

Class I (1 since 2007) Class II/III not classified

Adverse event reports per year · DPS

55in 2025

2007: 92008: 172009: 142010: 212011: 1212012: 562013: 152014: 152015: 302016: 122017: 152018: 192019: 272020: 592021: 242022: 592023: 542024: 642025: 55
2007high 121 (2011) · low 9 (2007)2025

MAUDE reports naming product code DPS, not matched to any one device; reports are not rates.

View these four charts as a table
YearDecisionsMedian 510(k) review, daysRecalls (Class I)MAUDE reports
2007118729
20081331017
20091484114
201011104221
2011221541121
201212117056
201310134015
201411253015
20158178030
201611229012
20179177015
201814221019
20193178927
20206224259
20215135124
20226244159
202310236354
202482604 (1)64
20256163355
202662584—

What is it indicated for?

The Inmedix® CloudHRV™ System is intended to acquire, display, and record electrocardiographic (ECG) information to measure heart rate variability (HRV) in adult patients (age 22 or above) with normal sinus rhythm and resting heart rate within 40 – 110 bpm. These measurements are not intended for any specific clinical diagnosis. The clinical significance of HRV must be determined by the physician. Assessment is indicated for patients in a healthcare…

Read the full statement (135 words)

The Inmedix® CloudHRV™ System is intended to acquire, display, and record electrocardiographic (ECG) information to measure heart rate variability (HRV) in adult patients (age 22 or above) with normal sinus rhythm and resting heart rate within 40 – 110 bpm. These measurements are not intended for any specific clinical diagnosis. The clinical significance of HRV must be determined by the physician.

Assessment is indicated for patients in a healthcare facility including a physician office or a hospital outpatient clinic where the patient is able to remain supine and still. The CloudHRV™ System is not indicated for use in a surgical suite or during transport.

Normal sinus rhythm is determined by the physician. The ECG is not intended to be used to diagnose or monitor cardiovascular conditions. The device does not provide assessments of cardiovascular abnormalities/arrhythmias.

Indications for use as stated in the FDA summary.

Cite this page

510(k) Report. “K241217: CloudHRV™ System (100-01-001).” Lineage record from FDA 510(k) data and the FDA summary. Updated Nov 3, 2026. Accessed Nov 6, 2026. https://510kreport.com/device/K241217

Report an extraction error

Tell us what is wrong; we check it against the FDA summary.

Are you the manufacturer?

Send a correction or an update to this page, for example a newer model or a public statement about a recall.

Record history
  • FDA decision record loaded May 2, 2026
  • Summary read Oct 13, 2026 (extraction version 9eaa42aa01ed)
  • Lineage and recalls computed Nov 3, 2026
  • Page last updated Nov 3, 2026