510(k) Report

510(k) · Cleared

Cleared

Enguard Remote Patient Monitor

K020632510(k) SpecialCleared Mar 15, 200216-day reviewClass II21 CFR 870.1025

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

Mennen Medical, Ltd. · QYX Outpatient Cardiac Telemetry

Cleared on Mar 15, 2002 as substantially equivalent to K001120 (Mennen Medical, Ltd., 2001) after a 16-day review. Its family tree reaches back 1 generation to 2001.

Decided
Mar 15, 2002
Review
16 days
Class
Class II
Product code
QYX
Recalls
None
Predicates
1

Its longest line of descent runs back 1 generation to K001120 (2001). No later device cites it as a predicate yet.

K001120 · Envoy Patient Monitor · Mennen Medical, Ltd. · 2001200020022004
K001120 · Envoy Patient Monitor · Mennen Medical, Ltd. · 20010
  1. Root · 1 generation backK001120 Envoy Patient MonitorMennen Medical, Ltd. · 2001
  2. This deviceK020632 Enguard Remote Patient MonitorMennen Medical, Ltd. · 2002
View FIG. 1 as a table

Line of descent and top descendants

GenerationNumberDeviceApplicantDecidedRecalls
−1K001120Envoy Patient MonitorMennen Medical, Ltd.2001—
0 (this device)K020632Enguard Remote Patient MonitorMennen Medical, Ltd.2002—
FIG. 1 — Lineage of K020632, 2001–2002Source: 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 QYX? 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 QYX device

  1. #1 K250793 RhythmStar System (SL)score 14.8 · 13 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
*K001120Envoy Patient Monitor
Summary page 6
…Medical electrical equipment, Part 2, (1994) Requirements for safety of electrocardiograph monitoring equipment. Predicate Device MENNEN MEDICAL ENVOY PATIENT MONITOR (K001120). Device Description: Envoy Patient Monitor The Envoy is a multiparameter physiological patient monitor, capable of monitoring:…
Mennen Medical, Ltd.2001—

Also cleared against K001120: 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?

  • Its one ancestor has no recall.
  • 3 other devices also cite its predicate K001120.

How does its category compare?

All QYX devices

QYX Outpatient Cardiac Telemetry: FDA decisions, review times, recalls and adverse event reports over 20 years.

FDA decisions per year · QYX

1in 2025

2007: 12009: 12010: 12011: 22012: 12014: 22016: 12017: 32024: 32025: 12026 (partial year): 1
2007high 3 (2017) · low 0 (2008)2026

2026 to Oct 25, outlined.

Median 510(k) review, days · QYX

244in 2024

2017: 169 days median2024: 244 days median
2007high 244 (2024) · low 169 (2017)2026

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

Recalls per year · QYX

No recall names QYX since 2007.

Adverse event reports per year · QYX

107in 2025

2023: 742024: 4002025: 107
2007high 400 (2024) · low 0 (2007)2025

MAUDE reports naming product code QYX, 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
20071—00
20080—00
20091—00
20101—00
20112—00
20121—00
20130—00
20142—00
20150—00
20161—00
2017316900
20180—00
20190—00
20200—00
20210—00
20220—00
20230—074
202432440400
20251—0107
20261—0—

What is it indicated for?

Enguard is intended for use as a remote patient multiparameter monitoring system. The Enguard can monitor ECG/heart rate, two invasive blood pressure channels, two temperature channels, pulse oximetry, respiration, non-invasive blood pressure and EtCO2. This effectively allows the Enguard to monitor & wide-range of adult, pediatric and neonatal patient conditions, in many different areas of the hospital. Functions include display of multiparameter…

Read the full statement (117 words)

Enguard is intended for use as a remote patient multiparameter monitoring system.

The Enguard can monitor ECG/heart rate, two invasive blood pressure channels, two temperature channels, pulse oximetry, respiration, non-invasive blood pressure and EtCO2. This effectively allows the Enguard to monitor & wide-range of adult, pediatric and neonatal patient conditions, in many different areas of the hospital.

Functions include display of multiparameter waveforms, vital signs, alarm & status messages.

The Mennen Medical Enguard is intended for sale as a system for remote monitoring and recording patient information or any in-hospital application requiring remote patient monitoring.

The following are examples of intended clinical applications:

Critical Care Patients

Cardiac Step-down/Telemetry Units

Emergency Departments

Intra-operative (Anesthesia) Monitoring

Post Anesthesia Care

Indications for use read by OCR from a scanned FDA summary, so letters may be misread. Check the PDF before quoting it.

Cite this page

510(k) Report. “K020632: Enguard Remote Patient Monitor.” Lineage record from FDA 510(k) data and the FDA summary. Updated Nov 3, 2026. Accessed Nov 6, 2026. https://510kreport.com/device/K020632

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