Medscape Medical NewsAll articles

Lunit INSIGHT CXR Triage

Lunit Inc. • Radiology • 11/10/2021

510(k)IEC 62304 Class B
FDA Summary PDF

Device Purpose

Lunit INSIGHT CXR Triage is an AI-powered software designed to analyze adult chest X-rays for suspected pleural effusion and pneumothorax, flagging critical cases within PACS/workstations to assist medical specialists in prioritizing their review workflow. The system utilizes a vendor-agnostic deep learning algorithm on DICOM images to detect these time-sensitive conditions, with its performance in identifying features suggestive of these findings validated through nonclinical and clinical studies demonstrating high ROC AUC, sensitivity, and specificity.

Summary

Lunit INSIGHT CXR Triage is a radiological computer-assisted software tool designed for triage and notification in adult chest X-ray analysis. It employs artificial intelligence algorithms to identify pre-specified critical findings, specifically pleural effusion and/or pneumothorax, on frontal chest X-ray images. The software integrates with existing Picture Archiving and Communication Systems (PACS) or workstations, flagging potentially critical images to enable prioritized review by appropriately trained medical specialists qualified to interpret chest radiographs; it does not alter the order of cases or remove them from the reading queue. It operates as a passive notification system, meaning it does not send proactive alerts, but rather groups suspicious exams for potential earlier review within the standard care workflow, and is explicitly not intended for standalone clinical decision-making or directing attention to specific image portions beyond indicating the presence of the target findings. The device processes de-identified DICOM chest radiographs, utilizing a vendor-agnostic artificial intelligence algorithm to analyze each image for features suggestive of pleural effusion or pneumothorax, providing a case-level output ('flag' or blank) to the PACS/workstation. It can identify multiple critical findings per radiograph, and users can selectively enable notifications for each condition. When deployed with imaging equipment, analysis occurs automatically post-acquisition; an on-device notification also informs technologists (15 minutes post-interpretation by the specialist) which cases were prioritized by the AI, without providing diagnostic data. Nonclinical validation on 1,385 images yielded ROC AUCs of 0.9864 for pleural effusion (94.29% sensitivity, 95.72% specificity) and 0.9973 for pneumothorax (96.08% sensitivity, 99.14% specificity). Clinical studies using 1,708 images from NIH and Indian datasets demonstrated ROC AUCs of 0.9686 for pleural effusion (89.86% sensitivity, 93.48% specificity) and 0.9630 for pneumothorax (88.92% sensitivity, 90.51% specificity), with an average analysis and notification time of approximately 20-21 seconds per finding.

AI Regulatory Concerns

Powered byJev by TypeSafe AI

Jev reads the full FDA letter and returns calibrated concern probabilities per regulatory category. These are AI estimates, not regulatory advice.

Keywords

Artificial IntelligenceChest X-rayPleural EffusionPneumothoraxTriagePrioritizationRadiological SoftwareDICOMROC AUCPACS

Device Metadata

Submission Number
K211733
Company
Lunit Inc.
Panel
Radiology
Product Code
N/A
Data Type
Images
Clinical Function
Assessment
AI Function
Analysis
AI Subclass
triage

Relevant Clinical Questions

  • Q1. How does the algorithm's performance vary with the severity or subtlety of pleural effusion and pneumothorax (e.g., small vs. large findings)?; What were the specific demographic characteristics (age, sex, comorbidities) and image quality parameters of the NIH and India datasets used in the clinical validation, and how might these affect generalizability?; How does the system handle images with multiple concurrent critical and non-critical pathologies, and does the presence of other findings impact the accuracy for pleural effusion or pneumothorax detection?; What is the defined threshold for the 'flag' notification, and can users adjust this threshold based on their clinical setting's tolerance for false positives versus false negatives?; Considering the 15-minute delay for technologist notification *after* specialist interpretation, what is the intended actionable outcome or utility of this specific notification for the technologist?

Risk Classification

ESL Analysis
FDA Device ClassII

FDA 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.

Cyber Score10/100
SBOM Evidence⚠ Not mentioned in summary
Cyber Risk Assessment⚠ Not mentioned in summary
Postmarket Plan⚠ Not mentioned in summary
§524B ApplicableNo

Supply Chain BOM Evidence

Based on the CycloneDX / OWASP ECMA-424 xBOM ecosystem. Detection is from the AI-generated summary.

SBOMSoftware Bill of Materials
- Not detected
ML-BOMMachine Learning Bill of Materials(deep learning, algorithm, dataset)
✓ Detected
SaaSBOMSoftware-as-a-Service Bill of Materials
- Not detected
HBOMHardware Bill of Materials(on-device)
✓ Detected
CBOMCryptography Bill of Materials
- Not detected
VDR/VEXVulnerability Disclosure Report / Vulnerability Exploitability eXchange
- Not detected
OBOMOperations Bill of Materials
- Not detected

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.

• Postmarket cybersecurity monitoring plan not clearly documented in AI-generated device summary.

• 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
Lunit INSIGHT CXR Triage - Lunit Inc. | ESL FDA AI Device Intelligence