Critical Care Suite
GE Medical Systems, LLC. • Radiology • 08/12/2019
Device Purpose
Critical Care Suite is an AI-powered software designed to expedite the identification of pneumothorax by analyzing adult frontal chest X-ray images and flagging potential cases for prioritized radiologist review in PACS. Its methodology relies on a sequence of algorithms for image quality assessment and pneumothorax classification, aiming to improve triage efficiency without impacting standard image processing times.
Summary
Critical Care Suite is a software module employing AI-based image analysis algorithms to detect pneumothorax in adult frontal chest X-ray images. Its purpose is to aid in case prioritization or triage by flagging images with suspected critical findings directly in the PACS/workstation for expedited review by a radiologist. The system first uses Quality Care Suite algorithms for an automated check to confirm image compatibility and adequate lung field coverage, potentially notifying technologists of atypical positioning on compatible X-ray systems. Following this, the PTX Classifier algorithm determines the presence of pneumothorax. The device is intended for notification only and does not replace full patient evaluation or a qualified physician's diagnosis. The system's performance was evaluated using a dataset of 804 frontal chest X-rays, demonstrating an Area Under the Curve (AUC) of 0.96, a specificity of 93.5%, and a sensitivity of 84.3%. It showed high sensitivity for large pneumothoraces (96.3%) and moderate sensitivity for small pneumothoraces (75%). When deployed on Digital Projection Radiographic Systems, it can provide an on-device notification to technologists 15 minutes after exam closure regarding cases prioritized in PACS, though this notification is contextual and not for clinical action. Internal testing indicated that integrating Critical Care Suite does not statistically impact the timing of image acquisition, processing, annotation, and transfer to PACS, with images arriving at PACS with the prioritization flag already incorporated.
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. What is the specific architecture of the AI algorithms (Quality Care Suite and PTX Classifier) used for image analysis and pneumothorax detection?; How does the system's performance (sensitivity, specificity, AUC) vary with different patient demographics (e.g., age, sex, co-morbidities) not explicitly detailed in the clinical evaluation?; What are the criteria for defining 'atypical lung field positioning' by the Quality Care Suite algorithms, and how does this pre-screening impact the overall workflow and false positive/negative rates of the PTX classifier?; How was the 'ground truth' for pneumothorax presence and size established by the 3 independent US-board certified radiologists in the clinical evaluation, and what was the inter-rater variability?; What is the real-world impact on radiologist turnaround time and patient outcomes when Critical Care Suite is integrated into a busy clinical workflow, beyond the immediate flagging in PACS?
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