StrokeViewer Perfusion
NICo-Lab B.V. • Radiology • 12/14/2023
Device Purpose
StrokeViewer Perfusion is an image processing software application that analyzes CT perfusion scans to provide quantitative hemodynamic parameters, such as CBF, CBV, MTT, and TMax, for adult patients suspected of ischemic stroke. It functions by processing DICOM CTP images to generate parametric maps and volume calculations of affected brain tissue, offering supplementary data for clinicians.
Summary
StrokeViewer Perfusion is an image processing software application designed to assist in the assessment of adult patients with suspected ischemic stroke by analyzing CT perfusion (CTP) scans of the brain. The software processes DICOM-compliant imaging data to provide quantitative perfusion information, generating parametric maps such as Cerebral Blood Flow (CBF), Cerebral Blood Volume (CBV), Mean Transit Time (MTT), and Residue function time-to-peak (TMax). It also calculates the volume of affected tissue based on Tmax and CBF abnormalities. Intended for use by medical imaging professionals like neurologists and radiologists, the output serves as additional data to complement standard image interpretation and clinical information, and is not meant as a standalone diagnostic tool. Contraindications include inadequate contrast bolus, excessive patient motion leading to artifacts, and the presence of hemorrhage. The software operates on standard "off-the-shelf" computers or virtual platforms and is packaged as a Docker container. Results, including parametric maps and DICOM reports, are exported and can be viewed on compatible DICOM viewers. The device's efficacy was supported by non-clinical performance testing, which included software validation (unit, end-to-end, and reproducibility testing) and algorithm performance assessment using simulated datasets (Kudo digital phantom) based on tracer kinetic theory. This testing demonstrated that the device met its performance goals and acceptance criteria. Risk management was conducted according to ISO 14971:2019, and the software adhered to recognized consensus standards for medical device software and DICOM compatibility.
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 on the Kudo digital phantom translate to real-world clinical scenarios with varying image quality and patient presentations?; What are the specific thresholds used for Tmax and CBF abnormalities in the volume calculations, and how were these thresholds validated?; Are there any known limitations or specific patient conditions (e.g., severe motion artifacts, pre-existing lesions) where StrokeViewer Perfusion's accuracy might be compromised?; How does the processing time of StrokeViewer Perfusion compare to other perfusion analysis tools, and how does this impact its integration into time-sensitive stroke care protocols?; What future developments are planned for StrokeViewer Perfusion, particularly regarding the potential inclusion of MR perfusion data analysis or AI-driven predictive analytics?
Risk Classification
ESL AnalysisFDA Class II via 510(k) pathway; IEC 62304 Class B (software safety classification); Post-§524B but no clear network capability detected
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.
• SBOM not mentioned in AI-generated device summary. Under §524B (effective Oct 2023), cyber devices must provide a SBOM.
• Cybersecurity risk assessment not referenced in AI-generated device summary. FDA cybersecurity guidance (2023) expects this for cyber devices.
• 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