Flow Diversion for Intracranial Aneurysms With Incorporated Branch: A Subanalysis From the SEASE International Registry
Bibliographic record
Abstract
Background The presence of an incorporated branch as well as its anatomical relationship to the intracranial aneurysms (IAs) and the parent artery may affect the occlusion outcome following flow diversion. This study evaluated the safety and effectiveness of the cobalt‐chromium Surpass Evolve (Stryker), a 64‐wire flow diversion device for the treatment of IAs with incorporated branches. Methods This subanalysis uses data from the SEASE (Safety and Effectiveness Assessment of Surpass Evolve) registry to retrieve data related to IAs with incorporated branches. Those IAs were classified by a core lab into 4 categories based on their anatomical relationship to the parent artery and branch: (A) sidewall anatomic, (B) sidewall hemodynamic, (C) neck branch, and (D) dome branch. We compared the outcomes based on their incorporated branch's relation to the dome (A–C versus D). Results This study included 67 patients and IAs. Most IAs were in the posterior communicating artery (46.3%), with a median size of 4.35 mm. Age, sex, comorbidities, baseline functional‐status, and IA features were similar between the 2 groups. Among those, 53 (79.1%) had branches emerging from the dome, and 14 (20.9%) had branches originating from other locations (A = 7, B = 2, and C = 5). At a median imaging follow‐up of 10.5 months, complete occlusion was lower in IAs with a branch from the sac compared with those with the neck (60.8% versus 92.9%; P = 0.026), with an overall occlusion of 67.7%. Thromboembolic and hemorrhagic complications, as well as retreatment, were reported in 1.6% and 3.1% of cases, respectively, with no significant differences between groups. Conclusion Our analysis underscores the influence of branch origin on occlusion rates, with the neck‐originating branch demonstrating higher occlusion rates. These insights emphasize the role of anatomical considerations in treatment strategies, follow‐up timelines, and designing future clinical trials. Further studies are warranted to explore these variations across different flow diversion technologies.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.002 | 0.004 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.002 |
| Bibliometrics | 0.002 | 0.002 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.000 | 0.001 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.001 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".