Chest-CAD
Imagen Technologies, Inc • Radiology • 07/20/2021
Device Purpose
Chest-CAD is an artificial intelligence-driven software that analyzes adult chest radiographs using deep learning algorithms to identify and categorize suspicious regions of interest across eight distinct classes, serving as a concurrent reading aid for physicians. Its purpose is to enhance diagnostic accuracy in chest X-ray interpretation by improving clinician sensitivity and specificity in detecting potential abnormalities.
Summary
Chest-CAD is a computer-assisted detection (CADe) software designed to aid physicians in the interpretation of adult chest radiographs. It utilizes deep learning algorithms for computer vision to analyze digital X-ray images and identify suspicious regions of interest (ROIs), which are then automatically categorized into one of eight predefined classes: Cardiac, Mediastinum/Hila, Lungs, Pleura, Bones, Soft Tissues, Hardware, or Other; the software generates a DICOM Presentation State overlay with bounding boxes and category information for concurrent review in a PACS viewer. Standalone performance assessment on 20,000 chest radiograph cases demonstrated high overall sensitivity (0.908), specificity (0.887), and an Area Under the Curve (AUC) of the Receiver Operating Characteristic (ROC) curve of 0.976, with category-specific AUCs ranging from 0.921 (Mediastinum/Hila) to 0.994 (Hardware). A subsequent multi-reader, multi-case (MRMC) retrospective clinical study involving 24 readers and 238 cases further evaluated the software's impact, showing that reader accuracy, measured by case-level aggregate AUC, significantly improved when using Chest-CAD (Aided AUC: 0.894) compared to unaided interpretation (Unaided AUC: 0.836), with corresponding increases in reader sensitivity from 0.757 to 0.856 and specificity from 0.843 to 0.870.
AI Regulatory Concerns
Powered by
Jev reads the full FDA letter and returns calibrated concern probabilities per regulatory category. These are AI estimates, not regulatory advice.
Keywords
Device Metadata
Relevant Clinical Questions
- Q1. How does the Chest-CAD software's performance, particularly its sensitivity and specificity for the "Mediastinum/Hila" and "Bones" categories (which had lower individual metrics), compare to human expert consensus in real-world, prospective clinical settings beyond the retrospective study?; What is the variability in Chest-CAD's performance across different X-ray equipment vendors, imaging protocols, and patient demographic subgroups (e.g., age, BMI, presence of multiple comorbidities)?; Could the categorization of "Other" ROIs be further refined or sub-categorized in future iterations to provide more specific guidance to clinicians, and what types of findings typically fall into this category?; What is the average impact on a physician's interpretation time per case when using Chest-CAD as a concurrent reading aid compared to unaided reads, and how does this affect overall workflow efficiency?; Beyond bounding boxes and category labels, are there plans to incorporate additional quantitative information or visual cues (e.g., heatmaps, probability scores for specific pathologies within a category) to further assist in the characterization of detected ROIs?
Risk Classification
ESL AnalysisFDA Class II via 510(k) pathway; IEC 62304 Class B (software safety classification); Authorized before §524B enforcement
Learn how Parasoft automates IEC 62304 compliance testing →Cybersecurity Evidence
Powered by SBOMator™Based on AI-generated device summaries, not the full FDA submission. Items not detected here may still be present in the complete submission package.
Supply Chain BOM Evidence
Based on the CycloneDX / OWASP ECMA-424 xBOM ecosystem. Detection is from the AI-generated summary.
Analysis:
• Analysis is based on the AI-generated device summary, not the full FDA submission package. Click "Analyze Full FDA PDF" below to scan the actual submission document.
• Evidence of ML-BOM, HBOM detected in AI-generated device summary.
• This device was authorized before §524B took effect. Cybersecurity evidence requirements were less prescriptive at the time.
• Not detected in AI-generated device summary: SBOM, SaaSBOM, CBOM, VDR/VEX, OBOM. These may be present in the full FDA submission.
Preparing a similar submission?
ESL takes complete ownership of your software evidence work - SBOM & CVE remediation with SBOMator™, static analysis & unit testing with Parasoft, traceability, and full IEC 62304 lifecycle support.
Assess Your Readiness →Or contact ESL directly