Search Filters

Search Results

Found 2 results

510(k) Data Aggregation

    K Number
    K242809
    Date Cleared
    2024-10-17

    (30 days)

    Product Code
    Regulation Number
    868.1890
    Reference & Predicate Devices
    Why did this record match?
    Device Name :

    Ascent Cardiorespiratory Diagnostic Software

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

    Ascent Cardiorespiratory Diagnostic Software is intended to be used for measurements, data collection and analysis of lung function (PFT) parameters, and cardiopulmonary testing (CPET) parameters, aiding in the diagnosis of related conditions.

    All the measurements are performed via a mouthpiece or a mask.

    The results of the test can be viewed on-line with the help of a computer screen and can be printed after the test. The test results can be saved for further referral or report generation purposes.

    For use of the Bronchial Challenge option, the medical director of the laboratory, physician, or person appropriately trained to treat acute bronchoconstriction, including appropriate use of resuscitation equipment, must be close enough to respond quickly to an emergency.

    The product can be utilized for patients from 4 years old and older as long as they can cooperate in the performance -- no special limit to patient's sex or height.

    Measurements will be performed under the direction of a physician in a hospital environment, physician's office or similar settings.

    Device Description

    Ascent™ Cardiorespiratory Diagnostic Software ("Ascent") is a stand-alone software application which can be used with several hardware devices in the Medical Graphics Corporation product line.

    The core purpose of the software for measurement, data collection and analysis of testing in patients who may be suffering from pulmonary illnesses like chronic obstructive pulmonary disease (COPD), asthma, exercise intolerance, heart failure and/or cardiorespiratory concerns where diagnosis and prognosis needs to be determined.

    In conjunction with diagnostic hardware, Ascent is used to collect data pertaining to the patient's degree of obstruction, lung volumes, and diffusing capacity. It is also used to present the collected lung diagnostic information so that it can be checked for quality and interpreted by a qualified physician, often a pulmonologist or cardiologist.

    All the measurements are performed via a mouthpiece or a face mask.

    AI/ML Overview

    The provided text is a 510(k) summary from the FDA, which outlines the substantial equivalence determination for a medical device. This type of document focuses on comparing a new device to existing legally marketed predicate devices rather than providing detailed acceptance criteria and the results of a specific clinical study with granular performance metrics. As such, the document does not contain the specific information needed to fulfill all aspects of your request, particularly regarding detailed performance metrics, sample sizes for test sets (beyond general validation statements), expert qualifications, ground truth establishment methods for test sets, MRMC studies, or training set details.

    However, I can extract the information that is present and highlight what is missing based on your request.

    Missing Information:

    • Detailed Acceptance Criteria Table with Specific Performance Metrics: The document states that the software was "extensively validated per medical device software standards and guidance" and that "Testing results support that Ascent fulfills its intended use/indications for use." It also mentions "Performance tests included FEV1, MVV, FRC, SVC, DLCO, VA, TGV, VO2, VCO2, and VE." However, it does not provide specific quantitative acceptance criteria (e.g., "FEV1 must be within X% of ground truth") or the reported performance for these metrics.
    • Sample Size for Test Set and Data Provenance: The document does not specify the sample size for the test data used for performance validation, nor does it detail the provenance (country, retrospective/prospective) of this data.
    • Number of Experts and Qualifications for Ground Truth: The document does not describe how ground truth for the test set was established, including the number or specific qualifications of experts involved.
    • Adjudication Method for Test Set: No information is provided regarding adjudication methods (e.g., 2+1, 3+1).
    • Multi-Reader Multi-Case (MRMC) Comparative Effectiveness Study: The document does not indicate that an MRMC study was performed or provide any effect size for human reader improvement with AI assistance.
    • Standalone Performance (Algorithm Only): While the document states "Ascent Cardiorespiratory Diagnostic Software is a stand-alone software application," it describes validation as "Performance validation testing was done with the subject software device and recommended hardware devices working together." It does not provide specific performance metrics for the algorithm only without human interaction in a diagnostic capacity beyond its intended function of measuring, collecting, and analyzing parameters. The software aids diagnosis, implying human interpretation.
    • Type of Ground Truth Used (for Test Set): The document implicitly refers to "performance tests" for various physiological parameters (FEV1, DLCO, etc.), suggesting comparison to a reference standard for these measurements. However, it does not explicitly state the nature of this "ground truth" (e.g., expert consensus, pathology, outcome data) beyond reference to ATS/ERS guidelines for standardization.
    • Sample Size for Training Set: No information on training data or its size is provided. This is typical for a 510(k) for software that calculates and analyzes data from hardware, rather than an AI/ML model that learns from large datasets.
    • How Ground Truth for Training Set was Established: Not applicable as training data details are not provided.

    Information that can be extracted from the document:

    The provided document is a 510(k) summary for the "Ascent Cardiorespiratory Diagnostic Software" (K242809). It details the device's substantial equivalence to predicate devices, focusing on its intended use, technological characteristics, and conformity to relevant standards and guidelines.

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

    As noted above, specific quantitative acceptance criteria and reported performance metrics are NOT provided in this document. The document generally states that "Ascent Cardiorespiratory Diagnostic Software was extensively validated per medical device software standards and guidance. Testing results support that Ascent fulfills its intended use/indications for use..."

    It mentions that "Performance tests included FEV1, MVV, FRC, SVC, DLCO, VA, TGV, VO2, VCO2, and VE." However, no numerical results or thresholds are given. The validation was done referencing the following guidelines/standards for "acceptability and repeatability":

    • ATS/ ERS Standardisation of Spirometry (2019)
    • ERS/ ATS Standardisation of the Measurements of Lung Volumes (2023)
    • 2017 ERS/ ATS Standards for Single-Breath Carbon Monoxide Uptake in the Lung
    • ERS Technical Standard on Bronchial Challenge Testing (2017)
    • 2017 ATS Guidelines for a Standardized PF Report
    • ATS/ ACCP Statement on Cardiopulmonary Exercise Testing (2003)

    Summary of available information for a table format (conceptual, as specific numerical data is missing):

    Performance MeasureAcceptance Criteria (Stated as conforming to standards)Reported Device Performance (General Statement)
    FEV1Conforms to ATS/ERS Standardisation of Spirometry (2019) requirements for acceptability and repeatability.Testing results support intended use.
    MVVConforms to ATS/ERS Standardisation of Spirometry (2019) requirements for acceptability and repeatability.Testing results support intended use.
    FRCConforms to ERS/ATS Standardisation of the Measurements of Lung Volumes (2023) requirements for acceptability and repeatability.Testing results support intended use.
    SVCConforms to ATS/ERS Standardisation of Spirometry (2019) requirements for acceptability and repeatability.Testing results support intended use.
    DLCOConforms to 2017 ERS/ATS Standards for Single-Breath Carbon Monoxide Uptake in the Lung for acceptability and repeatability.Testing results support intended use.
    VAConforms to 2017 ERS/ATS Standards for Single-Breath Carbon Monoxide Uptake in the Lung for acceptability and repeatability.Testing results support intended use.
    TGVConforms to ERS/ATS Standardisation of the Measurements of Lung Volumes (2023) requirements for acceptability and repeatability.Testing results support intended use.
    VO2Conforms to ATS/ACCP Statement on Cardiopulmonary Exercise Testing (2003) guidelines.Testing results support intended use.
    VCO2Conforms to ATS/ACCP Statement on Cardiopulmonary Exercise Testing (2003) guidelines.Testing results support intended use.
    VEConforms to ATS/ACCP Statement on Cardiopulmonary Exercise Testing (2003) guidelines.Testing results support intended use.
    CybersecurityAddressed as per FDA Guidance - Cybersecurity in Medical Devices.Not specified explicitly beyond "addressed."
    Risk ManagementConforms to ISO 14971.Not specified explicitly.
    Software Life CycleConforms to IEC 62304.Not specified explicitly.

    2. Sample sized used for the test set and the data provenance:

    • Sample Size: Not specified. The document only states "Software validation testing involved system level tests, performance tests and safety testing based on hazard analysis. Performance validation testing was done with the subject software device and recommended hardware devices working together."
    • Data Provenance: Not specified (e.g., country of origin, retrospective or prospective).

    3. Number of experts used to establish the ground truth for the test set and the qualifications of those experts:

    • This information is not provided in the document.

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

    • This information is not provided in the document.

    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 study is mentioned or implied. The software is described as
      "aiding in the diagnosis of related conditions" and presenting "diagnostic information so that it can be checked for quality and interpreted by a qualified physician." This device is a "Predictive Pulmonary-Function Value Calculator" and performs measurements and analysis, but it is not described as an AI system assisting human readers in image interpretation or diagnosis in a comparative effectiveness study context.

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

    • The device is indeed described as a "stand-alone software application." However, the performance validation was done "with the subject software device and recommended hardware devices working together." Its output (measurements and analysis) is intended to be "displayed to the user" and "interpreted by a qualified physician."
    • The document does not provide performance metrics for the algorithm only in a way that suggests a diagnostic output without human interpretation or hardware interaction. It's a software that processes data from hardware to provide measurements and analysis, not, for example, a diagnostic image analysis AI.

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

    • The document implies that the ground truth for the performance tests (FEV1, DLCO, etc.) would be established by the standardized measurement techniques defined by governing bodies like ATS/ERS/ACCP. These typically involve comparing the device's calculated values against accepted reference methods for deriving those physiological parameters, often involving highly calibrated equipment and expert technicians following strict protocols. However, the exact nature of this "ground truth" (e.g., what gold standard was used for comparison) is not explicitly detailed beyond referencing the standards themselves.

    8. The sample size for the training set:

    • This information is not provided in the document. This type of device (a calculator/analyzer) is typically engineered based on established physiological formulas and algorithms, rather than being "trained" on large datasets in the way a deep learning AI model would be.

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

    • Not applicable, as training set details are not provided and the device functions as a calculator based on established science, not a machine learning model that learns from a labeled training set.
    Ask a Question

    Ask a specific question about this device

    K Number
    K181912
    Date Cleared
    2019-04-12

    (269 days)

    Product Code
    Regulation Number
    868.1890
    Reference & Predicate Devices
    Why did this record match?
    Device Name :

    Ascent Cardiorespiratory Diagnostic Software

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

    Ascent Cardiorespiratory Diagnostic Software is intended to be used for measurements, data collection and analysis of lung function (PFT) parameters, aiding in the diagnosis of related conditions. All the measurements are performed via a mouthpiece or a mask. The test can be viewed on-line with the help of a computer screen and can be printed after the test results can be saved for further referral or report generation purposes.

    For use of the Bronchial Challenge option, the medical director of the laboratory, physician, or person appropriately trained to treat acute bronchoconstriction, including appropriate use of resuscitation equipment, must be close enough to respond quickly to an emergency.

    The product can be utilized for patients from 4 years old and older as long as they can cooperate in the performance -- no special limit to patient's sex or height.

    Measurements will be performed under the direction of a physician in a hospital environment, physician's office or similar settings.

    Device Description

    In conjunction with pulmonary diagnostic hardware, Ascent software, a Windows desktop application developed using Microsoft's NET Framework, is used to collect data pertaining to the patient's degree of obstruction, lung volumes, and diffusing capacity. It is also used to present the collected lung diagnostic information so that it can be checked for quality and interpreted by a qualified physician, usually a pulmonologist.

    The core purpose of the software is to facilitate pulmonary function testing in patients who may be suffering from pulmonary illnesses like Chronic Obstructive Pulmonary Disease and asthma. The software will interact with connected Medical Graphics Corporation diagnostic devices to perform the desired pulmonary function tests on the patient by a professional pulmonary function technologist. The application will display both actual and derived test variables to the user after a test is performed for purposes of data review.

    AI/ML Overview

    Here's a breakdown of the acceptance criteria and study information for the Ascent Cardiorespiratory Diagnostic Software, based on the provided document:

    1. Table of Acceptance Criteria and Reported Device Performance:

    The document doesn't explicitly list "acceptance criteria" in a typical quantitative pass/fail format within a table. Instead, it describes general validation and performance testing. However, we can infer the performance objectives and how they were met.

    Acceptance Criteria (Inferred from Validation)Reported Device Performance
    Software Functionality and Safety (General)Fulfills intended use/indications of use.
    Compliant with medical device software standards & guidanceValidated per ISO 14971 and IEC 62304.
    Performance of key pulmonary function parameters within acceptable limitsPhysiologic performance validation testing conducted for FVC, MVV, FRC, SVC, DLCO, VA, and TGV. Results support intended use.
    System-level tests, performance tests, and safety testing based on hazard analysis.Validation testing conducted, including system-level, performance, and safety tests.

    2. Sample Size for the Test Set and Data Provenance:

    • Sample Size for Test Set: 38 test sessions.
    • Data Provenance: The subjects for these test sessions were "from seven to sixty-three years old." The document does not specify the country of origin of the data or whether it was retrospective or prospective.

    3. Number of Experts Used to Establish Ground Truth for the Test Set and Qualifications:

    The document does not specify the number of experts or their qualifications used to establish ground truth for the test set. It mentions that the software presents data to a "qualified physician, usually a pulmonologist, for diagnostic interpretation," but this refers to the intended use, not the ground truth establishment for the validation study itself.

    4. Adjudication Method for the Test Set:

    The document does not describe any specific adjudication method (e.g., 2+1, 3+1). The "physiologic performance validation testing" implies direct measurement comparison rather than expert consensus on interpretive tasks.

    5. If a Multi-Reader Multi-Case (MRMC) Comparative Effectiveness Study Was Done:

    No, an MRMC comparative effectiveness study was not explicitly mentioned or described as being performed. The study focused on the performance of the software and integrated hardware, not on the impact of the software on human reader performance.

    6. If a Standalone (i.e., algorithm only without human-in-the-loop performance) Was Done:

    Yes, the "physiologic performance validation testing" and "software validation testing" described seem to represent a standalone assessment of the device's ability to measure and process pulmonary function parameters. The device's core function is data collection and analysis, which occurs without direct human interpretation assistance during the measurement phase. The overall intention is for a "qualified physician" to interpret the results generated by the algorithm.

    7. The Type of Ground Truth Used:

    The document doesn't explicitly state "ground truth" in the context of reference standards. However, the nature of the device (pulmonary function software) implies that the ground truth for "physiologic performance validation testing" would be the physical measurements obtained from the connected hardware devices for various pulmonary function parameters (e.g., airflow, volume, gas concentrations). The accuracy of these measurements would be compared against expected values or highly accurate reference standards, though these specific reference standards are not detailed in the provided text.

    8. The Sample Size for the Training Set:

    The document does not mention any training set sample size or details about a training set. This is likely because the device, as described, is not an AI/machine learning model that typically requires a discrete training phase with labeled data. It appears to be a software system for data acquisition, processing, and display based on established physiological algorithms and hardware interaction.

    9. How the Ground Truth for the Training Set Was Established:

    As no training set is discussed, there is no information on how its ground truth might have been established.

    Ask a Question

    Ask a specific question about this device

    Page 1 of 1