What is it about?
When someone has a stroke, doctors need to see exactly which parts of the brain are damaged by looking at brain scans. Currently, this requires medical experts to manually trace around the damaged areas on each scan, a process that takes hours and costs a lot of money. We have developed a new AI system using a large vision model (LVM), similar to the technology behind advanced image recognition systems, that can automatically identify these damaged areas without anyone having to trace them by hand. Instead of needing precise outlines, our LVM-based system only needs to know the underlying mechanism that caused the stroke (like irregular heartbeat causing clots or narrowed arteries in the neck). We trained this large-scale AI to recognize that different stroke mechanisms create distinct patterns of damage in specific brain locations. Our system works by combining two technologies: one that shows us what the AI is "looking at" in the brain scan, and another component that can accurately outline the damaged areas. This creates a direct link between why a stroke happened and where it damaged the brain.
Featured Image
Photo by Vitaly Gariev on Unsplash
Why is it important?
Stroke affects millions of people worldwide and is a major cause of death and disability. To provide the best treatment and predict recovery, doctors need to know exactly where the brain damage occurred. But having expert neurologists manually review every brain scan is not realistic. Our approach solves this problem by using information doctors already determine during diagnosis (the stroke mechanism—whether it is from heart problems, vessel blockages, or other sources) to automatically map the damage. This means hospitals can analyze brain scans from many more patients quickly and accurately, potentially improving treatment decisions and helping more stroke survivors recover better.
Read the Original
This page is a summary of: Zero-shot Stroke Lesion Segmentation via CAM-guided Prompting of MedSAM2, November 2025, ACM (Association for Computing Machinery),
DOI: 10.1145/3746252.3760872.
You can read the full text:
Contributors
The following have contributed to this page







