syngo.CT Brain Hemorrhage
Siemens Medical Solutions USA, Inc. • Radiology • 03/22/2024
Device Purpose
syngo.CT Brain Hemorrhage is an artificial intelligence-powered software designed to analyze non-contrast head CT scans to detect suspected intracranial and subarachnoid hemorrhages, providing notification-only output to assist radiologists in prioritizing their case worklists. The system employs an improved algorithmic model for enhanced sensitivity, particularly for smaller hemorrhages and newly included subarachnoid hemorrhage detection, and supports images from multiple CT scanner vendors.
Summary
syngo.CT Brain Hemorrhage is an image-processing software that utilizes an artificial intelligence algorithm to support qualified clinicians in analyzing and prioritizing non-contrast head CT images. It is designed to algorithmically identify findings suspicious of acute intracranial hemorrhage (ICH) and acute subarachnoid hemorrhage (SAH), facilitating a parallel workflow where suspected positive cases are flagged for prioritized review. The device provides case-level output to a CT scanner or PACS system for worklist management but does not alter the original medical image, mark specific locations, or remove cases from the reading queue, serving solely as an informational tool and not for standalone diagnostic use. This version of the software introduces an improved algorithm model for ICH triage, aiming for higher sensitivity with smaller hemorrhages, and extends its functionality to include SAH triage. It now supports DICOM conformant head CT reconstructions from various vendors, not just Siemens scanners, and offers expanded deployment compatibility with the syngo.via host system. Performance evaluation in a retrospective study of 900 cases showed a sensitivity of 95.0% and specificity of 93.1% for ICH triage, and 86.1% sensitivity with 85.2% specificity for SAH triage, both exceeding an 80% performance goal, with an average per-case processing time of approximately 13.34 seconds.
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 improved algorithm's higher sensitivity for smaller intracranial hemorrhages affect the false positive rate compared to the predicate device?; What specific architectural changes or training data differences enabled the extension of the algorithm to reliably triage subarachnoid hemorrhages?; What were the inclusion/exclusion criteria for the 900 cases in the retrospective study, particularly regarding image quality and scanner types (beyond Siemens)?; How does the device handle ambiguous cases or artifacts that might mimic hemorrhages, and what is the typical user response protocol for flagged cases?; What is the range of processing times observed, and how does it vary with case complexity or image characteristics?
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, 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.
• 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. 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