InferRead CT Stroke.AI
Infervision Medical Technology Co., Ltd. • Radiology • 08/12/2021
Device Purpose
InferRead CT Stroke.AI is a software application utilizing a deep learning algorithm to analyze non-enhanced head CT images for the suspected presence of intracranial hemorrhage. Its purpose is to assist radiologists in workflow triage by visually marking potentially positive cases on a worklist, thereby facilitating earlier review and prioritization within the standard care pathway.
Summary
InferRead CT Stroke.AI is a radiological computer-assisted triage and notification software designed for the analysis of non-enhanced head CT images. The system operates on an Ubuntu OS and can be deployed as an onsite server, utilizing a deep learning algorithm to process DICOM series. It consists of four main modules: NeoViewer, Docking Toolbox, RePACS, and DLServer. The Docking Toolbox receives and inspects DICOM series; those meeting requirements are processed for intracranial hemorrhage (ICH) detection on a first-in-first-out basis. When a potential hemorrhage is detected, the system marks the case on a worklist, prompting users for preemptive triage and prioritization, without altering the original medical image or removing cases from the standard queue. The device is intended to assist hospital networks and trained radiologists by flagging suspected positive ICH findings to improve workflow triage. It operates in parallel with the standard of care, providing a worklist with marked cases. A retrospective clinical study involving 369 non-contrast brain CT scans demonstrated the software's performance: it achieved a sensitivity of 0.916 and a specificity of 0.922 for ICH detection against a ground truth established by neuroradiologists. The area under the receiver operating characteristic curve (AUC) was 0.962. Furthermore, the InferRead time-to-notification was significantly shorter (mean 1.07 minutes) compared to the standard of care time-to-open-exam (mean 75.4 minutes), indicating its potential to expedite 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 performance (sensitivity and specificity) of the InferRead CT Stroke.AI deep learning algorithm vary with different severities or types of intracranial hemorrhage (e.g., subarachnoid, intraparenchymal)?; What is the computational time required for the algorithm to process a typical non-enhanced head CT series, and how does this scale with increasing patient volume?; What were the characteristics of the false positive and false negative cases in the performance study, and what steps are being taken to address these?; How does the 'marking cases in the worklist' notification method impact radiologist workflow and cognitive load compared to other notification systems, such as pop-ups used by predicate devices?; Are there plans to expand the algorithm's capabilities to detect other acute neurological conditions visible on non-enhanced head CT scans beyond intracranial hemorrhage?
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 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, 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