ClariPulmo
ClariPi Inc. • Radiology • 04/06/2022
Device Purpose
ClariPulmo is an image analysis software that utilizes deep learning for automated lung segmentation and quantifies low and high-attenuation areas in thoracic CT images using Hounsfield unit thresholds to support physician diagnosis. It enhances CT image quantification through optional U-Net based denoising and kernel normalization functions, particularly for low-dose or sharp kernel images.
Summary
ClariPulmo is a non-invasive, standalone software application designed to support physicians in the quantification of lung CT images for examining pulmonary tissues and abnormalities. Its core functionality involves automated segmentation of the lungs using a pre-trained deep learning model. Following segmentation, the software quantifies low-attenuation areas (LAA) and high-attenuation areas (HAA) within the lungs by counting voxels based on user-predefined Hounsfield unit (HU) thresholds. The analysis results, including color overlay images of the segmented lungs, tables, and charts, are provided in summary reports to aid in diagnosis and documentation, although it is explicitly not intended for diagnosing pneumonia or COVID-19. The software incorporates optional advanced features to improve image quality and quantification accuracy, particularly for challenging CT datasets. These include an AI-based kernel normalization function, built on U-Net architecture, which translates images from sharp to smooth kernels, and an AI-based denoising function, also using U-Net architecture, to reduce noise in low-dose CT (LDCT) images. Performance testing demonstrated excellent agreement of its HAA analysis (PCC: 0.980–0.983) and LAA analysis (PCC: 0.99) with expert-established segmentations. The AI-based lung segmentation also showed high accuracy (PCC: 0.977–0.992; DICE coefficients: 0.98–0.99) across various patient datasets, CT scanners, reconstruction kernels, and low-dose conditions when compared to expert radiologist segmentations.
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 specific features or architectural modifications of the U-Net are employed for the denoising and kernel normalization tasks, and how were these models trained and validated?; How does the performance of the automated lung segmentation algorithm vary across different types of interstitial lung diseases or in the presence of extensive pleural abnormalities?; What is the range of user-predefined Hounsfield unit thresholds typically used for LAA and HAA analysis, and how does the software guide users in selecting appropriate thresholds?; Can the ClariPulmo software integrate with existing PACS systems, and what is the typical workflow for a radiologist using this tool in a clinical setting?; Beyond PCC and DICE coefficients, what other validation metrics were used to assess the accuracy and robustness of the LAA, HAA, and lung segmentation features, particularly concerning inter-scanner variability?
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.
• Postmarket cybersecurity monitoring plan not clearly documented in AI-generated device summary.
• 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