EFAI ChestSuite XR Pleural Effusion Assessment System
Ever Fortune.AI Co., Ltd. • Radiology • 09/08/2022
Device Purpose
The EFAI ChestSuite XR Pleural Effusion Assessment System is an artificial intelligence-powered software designed to analyze adult PA chest X-rays for suspected pleural effusion, providing passive notifications to PACS/workstations to aid in worklist prioritization. Its deep learning methodology involves image preprocessing and AI inference, demonstrating high sensitivity and specificity in clinical tests for identifying potential pleural effusion cases to assist radiological triage.
Summary
The EFAI ChestSuite XR Pleural Effusion Assessment System is a software workflow tool designed to assist clinicians in prioritizing adult chest X-ray cases suspected of pleural effusion. It utilizes a deep learning artificial intelligence algorithm to automatically analyze PA-view chest radiographs. The system operates through a four-stage process: data transfer, image preprocessing (including normalization and filtering based on DICOM tags), AI inference for pleural effusion detection, and post-processing of results into a JSON message. This message is then sent to a PACS/workstation, providing a passive notification to aid radiologists in triaging their worklists without highlighting specific image areas or replacing clinical judgment. Performance validation of the EFAI ChestSuite XR system involved both nonclinical and clinical testing. An internal validation using 1454 retrospective images from Taiwan demonstrated an AUC of 0.9517, sensitivity of 0.9013, and specificity of 0.8869. A subsequent standalone clinical test on a diverse dataset of 600 chest X-rays (from US and OUS institutions, multiple scanner manufacturers) compared the system to a predicate device. In this clinical test, using a reference standard established by three board-certified radiologists, the EFAI system achieved a sensitivity of 0.9510, specificity of 0.9745, and an AUC of 0.9712 for pleural effusion detection. The average processing time was 19.6 seconds, and consistent performance was observed across various clinical subgroups, including different patient demographics and imaging characteristics.
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 algorithm's performance vary with the subtlety or volume of pleural effusion, and are there defined thresholds for detection?; What were the specific image normalization techniques used in the preprocessing stage, and how sensitive is the AI to variations in image quality or acquisition protocols beyond those tested?; The clinical test included various confounding factors; could the performance metrics be further stratified to show the impact of each specific comorbidity (e.g., atelectasis, pneumonia) on the algorithm's accuracy for pleural effusion detection?; Given the system generates a passive notification, what is the anticipated real-world impact on radiologist reading times and diagnostic accuracy for pleural effusion when integrated into a busy clinical workflow?; How was the "ground truth" for pleural effusion established in the nonclinical dataset, and what was the inter-rater reliability among the three board-certified radiologists in both the nonclinical and clinical studies?
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 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, HBOM, 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