Search Filters

Search Results

Found 1 results

510(k) Data Aggregation

    K Number
    K070643
    Manufacturer
    Date Cleared
    2007-11-02

    (239 days)

    Product Code
    Regulation Number
    876.5860
    Reference & Predicate Devices
    N/A
    Why did this record match?
    Device Name :

    PHOENIX HEMODIALYSIS DELIVERY SYSTEM, VERSION 3.35

    AI/MLSaMDIVD (In Vitro Diagnostic)TherapeuticDiagnosticis PCCP AuthorizedThirdpartyExpeditedreview
    Intended Use

    The Phoenix® Hemodialysis delivery system is intended to be used to provide high flux and low flux hemodialysis, hemofiltration and ultrafiltration on patients weighing 15 Kilograms or more. The Phoenix system is to be used with either high or low permeability dialyzers. The device is intended to be used by trained operators when prescribed by a physician, in a chronic care dialysis facility or acute care unit.

    Device Description

    Phoenix® is a self-contained, microprocessor-controlled device that provides hemodialysis and ultrafiltration-only therapies. The system consists of the Hemodialysis Machine in use with a blood tubing set designed for the machine, a dialyzer, a heparin-filled syringe, a BiCart® column (sodium bicarbonate powder), and other appropriate dialysate concentrates. The machine has many built-in features which are intended to enhance the ease of providing patient dialysis treatments. Phoenix® has a modular structure.

    AI/ML Overview

    The provided text describes a 510(k) submission for the Phoenix® Hemodialysis Delivery System 3.35. This document focuses on demonstrating substantial equivalence to a predicate device and includes information about nonclinical testing.

    Here's an analysis to extract the requested information:

    1. A table of acceptance criteria and the reported device performance

    The document uses the predicate device (Phoenix® Hemodialysis Delivery System Version 3.00) as a benchmark for acceptance criteria and performance. The performance metrics for the modified device (Version 3.35) are compared directly against those of the predicate. The "Accuracy" values for the modified device represent the reported device performance.

    ParameterAcceptance Criteria (Predicate V3.00)Reported Device Performance (Modified Device V3.35)
    Anticoagulation (Heparin Pump)Range: 0.5 - 10 ml/hr
    Accuracy: ± 5% or ± 0.2 ml/hRange: 0/0.5 - 10 ml/hr
    Accuracy: ± 5% or ± 0.2 ml/h
    Blood Flow RateRange: 10 - 500 ml/min
    Accuracy: ± 10%Range: 10 - 580 ml/min
    Accuracy: ± 10% if pressure before the pump is not lower (more negative) than – 150 mmHg
    Fluid Removal Rate from PatientRange: 0 - 4 Kg/h
    Accuracy: ± 2.5 % of actual value or ± 50 ml/h, whichever is greaterRange: 0 - 4 Kg/h
    Dialysate flow rate at 350 ml/min: Accuracy (on total Weight removed): ±(2% UF rate + 35 g/hr)
    Dialysate flow rate at 500 ml/min: Accuracy (on total Weight removed): ±(2% UF rate + 50 g/hr)
    Dialysate flow rate at 800 ml/min: Accuracy (on total Weight removed): ±(2% UF rate + 80 g/hr)
    Dialysate Flow RateRange: 350 - 1000 ml/min
    Accuracy: ± 5%Range: 350 - 800 ml/min
    Accuracy: ± 5%
    Transmembrane PressureRange: -200 to +500 mmHgRange: -100 to +450 mmHg
    Ultrafiltration RateRange: 0 - 4 Kg/h
    Accuracy: ± 2.5 % of actual value or ± 50 ml/h, whichever is greaterRange: 0 - 4 Kg/h
    Accuracy: ± 2 % of actual value.
    Dialysate TemperatureRange: 34 - 40 °CRange: 34 - 39.5 °C
    Dialysate ConductivityRange: 13-17 mS/cmRange: 13-17 mS/cm
    Arterial PressureRange: -400 to +150 mmHgRange: -400 to +150 mmHg
    Venous PressureRange: 100 to +450 mmHgRange: 0 to +450 mmHg

    2. Sample size used for the test set and the data provenance (e.g. country of origin of the data, retrospective or prospective)

    The document mentions "component level hardware testing," "static and dynamic software testing (e.g., unit testing, code inspections, testing targeted to the changes implemented in software version 3.35, regression testing)," and "human factors evaluations." However, it does not specify sample sizes for these tests, nor the country of origin or whether the data was retrospective or prospective. The information points to internally conducted engineering and software verification and validation activities.

    3. Number of experts used to establish the ground truth for the test set and the qualifications of those experts (e.g. radiologist with 10 years of experience)

    The document states that testing was performed by "internal and external independent personnel with the appropriate skills" for the nonclinical testing and human factors evaluations. However, it does not specify the number of experts, their qualifications, or their role in establishing a ground truth for a test set. The context is about engineering and system performance validation, not clinical image interpretation or diagnosis.

    4. Adjudication method (e.g. 2+1, 3+1, none) for the test set

    The document does not describe any adjudication method for a test set. This type of method is typically associated with studies involving human interpretation (e.g., radiology reads) where discrepancies need resolution. The testing described is primarily technical performance validation.

    5. 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 MRMC comparative effectiveness study was done or mentioned. This submission is for a medical device (hemodialysis system), not an AI-powered diagnostic tool, and therefore, the concept of "human readers improving with AI assistance" is not applicable to the context of this device.

    6. If a standalone (i.e. algorithm only without human-in-the-loop performance) was done

    This refers to the performance of the device itself (the "algorithm only" in this context refers to the device's automated functions). The entire nonclinical testing section, which evaluated parameters like flow rates, accuracies, and pressures, represents standalone performance testing of the Phoenix® System 3.35. The tables directly report these standalone performance metrics.

    7. The type of ground truth used (expert consensus, pathology, outcomes data, etc)

    For the nonclinical testing, the "ground truth" would be established by controlled engineering measurements against known standards and specifications. For example, a calibrated flow meter would provide the "ground truth" for blood flow rate accuracy, or a calibrated pressure sensor for pressure measurements. These are physical and electrical measurements, not expert consensus, pathology, or outcomes data in the clinical sense.

    8. The sample size for the training set

    The document does not mention a training set sample size. This is not an AI/machine learning device that typically requires a large training dataset. The development and testing revolve around hardware and software engineering principles.

    9. How the ground truth for the training set was established

    Since there is no mention of a training set, there is no information on how its "ground truth" was established.

    Ask a Question

    Ask a specific question about this device

    Page 1 of 1