K Number
K113125
Date Cleared
2011-11-17

(24 days)

Product Code
Regulation Number
870.1025
Panel
CV
Reference & Predicate Devices
AI/MLSaMDIVD (In Vitro Diagnostic)TherapeuticDiagnosticis PCCP AuthorizedThirdpartyExpeditedreview
Intended Use

Indicated for use by health care professionals whenever there is a need for monitoring the physiological parameters of patients. Intended for monitoring and recording of, and to generate alarms for, multiple physiological parameters of adults and pediatrics in hospital environments and during transport inside hospitals.

Device Description

The name of this device is the IntelliVue MX40 Patient Monitor.

AI/ML Overview

This document outlines information found in the provided 510(k) summary for the Philips IntelliVue MX40 Patient Monitor. Please note that the available text primarily focuses on regulatory compliance and substantial equivalence to a predicate device, rather than a detailed comparative clinical study. Therefore, some of the requested information, particularly regarding specific performance metrics, sample sizes for test sets, and details of clinical studies, may not be explicitly present.

Acceptance Criteria and Reported Device Performance

Acceptance Criteria CategoryAcceptance CriteriaReported Device Performance
Overall PerformanceThe modified device is substantially equivalent to the previously cleared MX40 IntelliVue Patient Monitor (K103646), having the same Indications for Use, Intended Use, and technological characteristics as the legally marketed predicate device. Pass/Fail criteria were based on the specifications cleared for the predicate device."Test results showed substantial equivalence." "The results demonstrate that MX40 patient monitor meets all defined reliability requirements and performance claims." The device was cleared, indicating it met the acceptance criteria for substantial equivalence to its predicate.
System Level TestsNot explicitly detailed in the provided summary, but implied to be part of the predicate device's cleared specifications."Testing involved system level tests..."
Performance TestsNot explicitly detailed in the provided summary, but implied to be part of the predicate device's cleared specifications. These are likely to cover the physiological parameters it monitors (arrhythmia detection, ST segment monitoring, oximetry, etc.). Specific numerical performance metrics (e.g., accuracy, sensitivity, specificity for arrhythmia detection) are not provided in this summary."...performance tests, and safety testing from hazard analysis." This general statement indicates that performance was evaluated against established specifications, likely derived from the predicate device and relevant standards. Given the clearance, it implies satisfactory performance.
Safety Testing (Hazard Analysis)Not explicitly detailed in the provided summary, but implied to be part of the predicate device's cleared specifications."...and safety testing from hazard analysis." The device met the safety requirements.
Reliability RequirementsDefined reliability requirements, likely stemming from internal Philips standards and relevant voluntary standards (e.g., IEC 60601-1, ANSI/AAMI EC 13)."The results demonstrate that MX40 patient monitor meets all defined reliability requirements..."
Voluntary Standards ComplianceCompliance with applicable voluntary standards: IEC 60601-1:1998 + A1:1991 + A2:1995 (General Electrical Safety), IEC 60601-1-2:2001 + A1:2004 (EMC), ANSI/AAMI EC 13:2002 (Cardiac monitors, heart rate monitors and alarms), ISO EN 9919: 2005, IEC 60601-2-25:1993 + A1:1999, EC 53:1998 + A1:2008 (ECG Cables and leadwires), ISO 10993-1:2010 (Biocompatibility - for accessory lead wires).The document states, "The following voluntary standards were used where applicable for this product modification..." and implies compliance as part of the overall testing and clearance.

Study Information

  1. Sample size used for the test set and the data provenance:

    • Test Set Sample Size: The document does not specify a separate "test set" sample size in terms of patient data or clinical cases. The testing described is at a system, performance, and safety level, likely using engineering tests, simulations, and possibly limited human factor evaluations (though not explicitly stated as such). It is not a clinical study with a patient cohort. The evaluation is primarily based on demonstrating substantial equivalence to a predicate device and compliance with technical standards.
    • Data Provenance: Not applicable in the context of a clinical test set from patients. The testing involved internal verification and validation activities, which would use simulated data, test equipment, and engineering specifications.
  2. Number of experts used to establish the ground truth for the test set and the qualifications of those experts:

    • This information is not applicable as the document describes a technical verification and validation process against predefined specifications and standards, not a clinical study requiring expert-established ground truth from patient data. The "ground truth" here would be the technical specifications and performance characteristics of the predicate device, as well as the requirements of the cited voluntary standards.
  3. Adjudication method for the test set:

    • Not applicable. There was no clinical test set requiring adjudication in the context of this 510(k) summary. The "adjudication" in this context would be the pass/fail assessment against the established technical specifications and standards by the engineering and regulatory teams at Philips, and ultimately, by the FDA.
  4. If a multi-reader multi-case (MRMC) comparative effectiveness study was done, If so, what was the effect size of how much human readers improve with AI vs without AI assistance:

    • No. The document makes no mention of AI assistance or human readers. This is a 510(k) submission for a patient monitor, which is a standalone device providing physiological parameter monitoring. It is not an AI-powered diagnostic or assistive technology for human readers.
  5. If a standalone (i.e., algorithm only without human-in-the-loop performance) was done:

    • Yes, in essence. The "performance" being evaluated is that of the device itself (the monitor), which operates in a standalone capacity to measure and display physiological parameters and generate alarms. The verification and validation activities described (system level tests, performance tests, safety testing) assess the device's inherent function, without explicitly involving human-in-the-loop performance measurement or comparison in the context of a clinical study. The device is intended for use by healthcare professionals, but the performance testing described here is about the device's technical capabilities, not its impact on human action or diagnostic accuracy in a study context.
  6. The type of ground truth used (expert consensus, pathology, outcomes data, etc.):

    • The "ground truth" for this submission against the acceptance criteria is primarily based on:
      • Predicate Device Specifications: The established performance and reliability specifications of the previously cleared MX40 IntelliVue Patient Monitor (K103646).
      • Voluntary National and International Standards: Such as IEC 60601-1, ANSI/AAMI EC 13, ISO EN 9919, etc., which define acceptable performance limits and safety requirements for medical devices of this type.
      • Internal Engineering Specifications: Philips's own internal design and performance specifications for the updated device.
  7. The sample size for the training set:

    • Not applicable. There is no mention or indication of a "training set" in the context of this 510(k) summary. The device is an updated version of an existing patient monitor, implying its core algorithms and functions are established and validated-it is not a machine learning model that undergoes a training phase as described in AI/ML development.
  8. How the ground truth for the training set was established:

    • Not applicable, as there is no training set mentioned.

§ 870.1025 Arrhythmia detector and alarm (including ST-segment measurement and alarm).

(a)
Identification. The arrhythmia detector and alarm device monitors an electrocardiogram and is designed to produce a visible or audible signal or alarm when atrial or ventricular arrhythmia, such as premature contraction or ventricular fibrillation, occurs.(b)
Classification. Class II (special controls). The guidance document entitled “Class II Special Controls Guidance Document: Arrhythmia Detector and Alarm” will serve as the special control. See § 870.1 for the availability of this guidance document.