Methinks CTA Stroke
K251590Methinks Software S.L. · cleared 2025-08-20 · product code QAS · Radiology
Premarket evidence — what FDA accepted
Device typesamd
source quote (p.5)
“Methinks CTA Stroke is a software-only device which is intended to be used by trained physicians involved in the management of Acute Stroke (AS) patients at emergency settings or other departments across the stroke care pyramid model.”
AlgorithmArtificial intelligence/Neural Network
source quote (p.4)
“Methinks CTA Stroke uses an artificial intelligence algorithm to analyze images for findings suggestive of a pre-specified clinical condition and to notify an appropriate medical specialist of these findings in parallel to standard of care image interpretation.”
Adaptive (vs locked)FDA source did not state this
PCCPFDA source did not state this
Cybersecurity addressedYes
source quote (p.8)
“Cybersecurity has been integrated into the design and development of the Methinks CTA Stroke device in accordance with FDA's cybersecurity guidance and Section 524B of the FD&C Act. The device underwent rigorous non-clinical testing under clinically relevant conditions. Design verification and validation per 21 CFR Part 820.30 confirmed that all design requirements and specifications were met. Methinks employed a risk-based cybersecurity strategy that includes secure design principles, threat modeling, vulnerability assessment, third-party penetration testing and a Software Bill of Materials (SBOM). Key security controls such as authentication, authorization, secure update mechanisms, and system logging have been implemented. Cybersecurity was addressed as part of the software verification process. Controls including authentication, authorization, cryptography, code, data and execution integrity, confidentiality, monitoring, resiliency and recovery, software updates, patch management, and coordinated vulnerability disclosure are in place to ensure ongoing safety, effectiveness and resilience against cybersecurity threats throughout the device lifecycle.”
Validation studies (1)
Retrospective clinical
n=336 cases
endpoints: evaluate the software's performance in identifying CTA images containing Large Vessel Occlusion (LVO) findings
Reported performance (3 observations)
sensitivity98.2CI 93.6% - 99.8%
source quote (p.8)
“LVO was observed at Sensitivity: 98.2% (95% CI: 93.6% - 99.8%)”
specificity91.6CI 87.2% - 94.9%
source quote (p.8)
“and Specificity: 91.6% (95% CI: 87.2% - 94.9%).”
time_to_resultas written: “Time to notification of CTA-LVO (minutes)”3.3CI 3.23 - 3.36
source quote (p.9)
“Time to notification of CTA-LVO (minutes) Mean 3.30 95% CI Lower 3.23 95% CI Upper 3.36”
Each value carries its own analysis unit and task — never compare or pool across devices. Source: 510(k) summary PDF.
Predicate network
Postmarket — what happened after clearance
0
recalls in product code, 24mo
0
MAUDE reports in code, 12mo
—
vs code's own 3-yr baseline
0
drift signals on this device
Recall and MAUDE counts are product-code-level (reports aren't reliably attributable to one device). Signals are descriptive observables with sources — never a judgment that the device is unsafe or drifting. Snapshot 2026-07-08.
Reimbursement — how devices like this got paid
Not yet tracked — no payment pathway indexed for this clearance (the reimbursement corpus is a growing seed set).