ClariCT.AI
ClariPi Inc. • Radiology • 07/27/2021
Device Purpose
ClariCT.AI is a software device engineered to enhance the quality of DICOM-formatted Computed Tomography (CT) images by reducing noise, particularly in low-radiation dose acquisitions across various anatomical studies. It employs pre-trained deep learning models for its denoising capabilities and features an AI Marketplace Integration module to facilitate deployment and interoperability with existing hospital PACS and IT infrastructure via a virtualized Linux environment.
Summary
ClariCT.AI is a software device designed for the networking, communication, processing, and enhancement of Computed Tomography (CT) images presented in DICOM format. Its primary purpose is to improve CT image quality, particularly by reducing noise in images acquired with lower radiation doses. The software can be applied to CT scans of various anatomical regions, including the head, chest, heart, and abdomen, and aims to enhance the diagnostic utility of low-dose images, including those processed with Filtered Back Projection or Iterative Reconstruction techniques. The core technology behind ClariCT.AI's image enhancement capabilities involves the use of pre-trained deep learning models for noise reduction. This version of the software introduces an "AI Marketplace Integration module," which facilitates its installation and operation within AI Marketplace systems. This module allows ClariCT.AI to be hosted via third-party AI marketplaces, enabling central integration with Picture Archiving and Communication Systems (PACS) and existing IT infrastructure through Docker images in a virtualized Linux environment. Non-clinical performance evaluations have demonstrated the software's compliance with recognized standards for medical device software, cybersecurity, and interoperability.
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 performance of ClariCT.AI's deep learning-based noise reduction compare quantitatively to traditional iterative reconstruction algorithms across different anatomical regions and CT scanner models, particularly at very low radiation doses?; What is the typical processing time added to the clinical workflow when ClariCT.AI is integrated via the AI Marketplace module, and how does this impact radiologist efficiency and image turnaround time?; What specific pre-trained deep learning models are utilized by ClariCT.AI, and what were the characteristics (e.g., diversity, size, annotation quality) of the dataset used for their training to ensure robust generalizability?; How does the AI Marketplace Integration module ensure data security, patient privacy, and system integrity when CT images are processed via a third-party platform, especially concerning the Dockerized Linux environment?; Are there any known limitations or image artifact types where ClariCT.AI's denoising process might inadvertently obscure subtle pathological findings or introduce new, misleading artifacts?
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.
• Postmarket cybersecurity monitoring plan not clearly documented in AI-generated device summary.
• 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