Search Filters

Search Results

Found 1 results

510(k) Data Aggregation

    K Number
    K181343
    Date Cleared
    2018-06-12

    (22 days)

    Product Code
    Regulation Number
    892.1200
    Reference & Predicate Devices
    Predicate For
    N/A
    AI/MLSaMDIVD (In Vitro Diagnostic)TherapeuticDiagnosticis PCCP AuthorizedThirdpartyExpeditedreview
    Intended Use

    HeartSee Software for cardiac position tomography (PET) is indicated for determining regional and global absolute rest and stress myocardial perfusion in co'min/g, Coronary Flow Reserve and their combination into the Coronary Flow Capacity (CFC) Map in patients with suspected or known coronary artery disease (CAD) in order to assist clinical interpretation of PET perfusion images by quantification of their severity.

    HeartSee is intended for use by trained professionals, such as nuclear technicians, nuclear cardiology physicians, or cardiologists with appropriate training and certification. The climician remains ultimately responsible for the final assessment and diagnosis based on standard practices, clinical judgment and interpretation of PET images or quantitative data.

    Device Description

    HeartSee is a software tool for cardiac positron emission tomography (PET) for determining regional and global absolute rest and stress myocardial perfusion in cc/min/q. Coronary Flow Reserve and their combination into the Coronary Flow Capacity (CFC) Map for facilitating the interpretation of PET perfusion images in patients with suspected of known coronary artery disease. HeartSee is intended for use by trained professionals, such as nuclear technicians, nuclear medicine or nuclear cardiology physicians, or cardiologists with appropriate training and certification.

    HeartSee contains two fundamental components. First, the software imports cardiac PET images in DICOM format from PET scanners with DICOM output. These images are reoriented to cardiac axes to produce standard tomographic and topographic displays of relative uptake. Second, the software quantifies absolute rest and stress myocardial perfusion per unit tissue (cc/min/gm), Coronary Flow Reserve (CFR) as the stress/rest perfusion ratio and the Coronary Flow Capacity combining CFR and stress perfusion, all on a pixel basis for regional and global values. Archiving output data is supported for clinical diagnostics, quality control and research.

    AI/ML Overview

    The provided text does not contain detailed acceptance criteria and the results of a study proving the device meets these criteria. The document is a 510(k) summary for the HeartSee Cardiac P.E.T. Processing Software (K181343).

    Here's what can be extracted based on the prompt's requirements:

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

    The document states: "The verification and validation testing of the predicate device verification is deemed to be sufficient for the proposed device as the devices are identical with the exception of branding." This indicates that no new performance data or acceptance criteria specific to K181343 are presented because its performance is considered identical to its predicate (K171303). Therefore, a table for K181343's performance against specific acceptance criteria is not provided in this document.

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

    Not provided for K181343. Since no new testing was performed for K181343, this information would pertain to the predicate device (K171303) and is not detailed here.

    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)

    Not provided for K181343. This information would relate to the testing of the predicate device (K171303) and is not detailed here.

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

    Not provided for K181343. This information would relate to the testing of the predicate device (K171303) and is not detailed here.

    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

    The document states: "No clinical testing was performed in support of this 510(k) premarket notification." Therefore, no MRMC comparative effectiveness study was done for this specific submission (K181343).

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

    The document states: "No clinical testing was performed in support of this 510(k) premarket notification." Therefore, no standalone algorithm performance study was done for this specific submission (K181343).

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

    Not provided for K181343. This information would relate to the testing of the predicate device (K171303) and is not detailed here.

    8. The sample size for the training set

    Not provided for K181343. This information would relate to the development and training of the algorithm for the predicate device (K171303) and is not detailed here.

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

    Not provided for K181343. This information would relate to the development and training of the algorithm for the predicate device (K171303) and is not detailed here.

    Summary of the Study that Proves the Device Meets Acceptance Criteria:

    The document explicitly states: "The proposed device and K171303 are software tools using identical standard, industrial computing hardware and applications. The code in the proposed software package is identical to K171303." And further: "The verification and validation testing of the predicate device verification is deemed to be sufficient for the proposed device as the devices are identical with the exception of branding."

    This means that no new study was performed for K181343 to demonstrate its performance against acceptance criteria. The device is considered substantially equivalent to a previously cleared predicate device (K171303) because it is essentially the same software, differing only in branding. Therefore, the prior testing and validation of the predicate device (K171303) is the "study" referenced, and its acceptance criteria and performance data are considered applicable to K181343 by extension. The details of that predicate study are not present in this document.

    Ask a Question

    Ask a specific question about this device

    Page 1 of 1