Annalise Enterprise CXR Triage Pneumothorax
Annalise-AI • Radiology • 02/24/2022
Device Purpose
Annalise Enterprise CXR Triage Pneumothorax is an AI-driven software employing a deep learning convolutional neural network to identify pneumothorax and tension pneumothorax on adult chest X-rays, aiming to improve clinical workflow through worklist prioritization. The system is designed as an assistive tool for trained clinicians, demonstrating high accuracy with an AUC of 0.979 for pneumothorax and efficient triage capabilities.
Summary
Annalise Enterprise CXR Triage Pneumothorax is a software tool designed to assist clinicians in the medical care environment by analyzing adult chest X-ray (CXR) images for features suggestive of pneumothorax and tension pneumothorax. It utilizes an artificial intelligence algorithm, specifically a convolutional neural network developed using deep learning techniques trained on over 1,500,000 CXR images from diverse sources. The device integrates with Picture Archiving and Communication Systems (PACS) or Radiology Information Systems (RIS) to make case-level outputs available, enabling worklist prioritization or triage. It is intended for use by trained clinicians qualified to interpret CXRs and is not meant for standalone diagnostic decisions, to rule out these conditions, or to identify anomalies other than pneumothorax and tension pneumothorax; it also does not decrease a study's existing priority. The device's performance was evaluated through standalone accuracy and triage effectiveness assessments. In a retrospective study using 949 unique patient CXR cases (413 positive for pneumothorax, including 123 tension pneumothorax), the AI algorithm demonstrated an Area Under the Curve (AUC) of 0.979 for pneumothorax and 0.988 for tension pneumothorax. At its default 'balanced' operating point, it achieved 93.9% sensitivity and 92.2% specificity for pneumothorax, and 94.3% sensitivity and 95.8% specificity for tension pneumothorax. Additional operating points optimizing for sensitivity or specificity also met performance requirements. A triage effectiveness study on 621 positive cases showed an average triage turn-around time of 20.57 seconds, supporting its utility in expediting the review of critical cases.
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 subtle or atypical presentations of pneumothorax versus classic presentations?; What were the specific characteristics of the 123 tension pneumothorax cases within the test dataset, and did performance differ for this critical subset compared to simple pneumothorax?; Given the training data was sourced from three continents, how was dataset shift or variability in imaging protocols across these sources managed during model development and validation?; What is the expected impact on radiologist workload and time-to-diagnosis in a real-world clinical setting beyond the reported bench study triage turn-around time?; How does the device differentiate between true pneumothorax and mimics, such as skin folds or bullous lung disease, and what was the false positive rate for such mimics in the test set?
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, SaaSBOM, OBOM 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, HBOM, CBOM, VDR/VEX. 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