Impact of vessel tortuosity and radiological thrombus characteristics on the choice of first-line thrombectomy strategy: Results from the ESCAPE-NA1 trial
Bibliographic record
Abstract
INTRODUCTION: Despite improvements in device technology, only one-third of stroke patients undergoing endovascular thrombectomy (EVT) achieve first-pass effect (FPE). We investigated the effect of arterial tortuosity and thrombus characteristics on the relationship between first-line EVT strategy and angiographic outcomes. PATIENTS AND METHODS: Patients with thin-slice baseline CT-angiography from the ESCAPE-NA1 trial (Efficacy and safety of nerinetide for the treatment of acute ischemic stroke) were included. Tortuosity was estimated using the tortuosity index extracted from catheter pathway, and radiological thrombus characteristics were length, non-contrast density, perviousness and hyperdense artery sign. We assessed the association of first-line EVT strategy (stent-retriever [SR] versus contact aspiration [CA] versus combined SR+CA) with FPE (eTICI score 2c/3 after one pass), final eTICI 2b/3, number of passes and procedure duration using multivariable regression. Interaction of tortuosity and thrombus characteristics with first-line technique were assessed using interaction terms. RESULTS: Among 520 included patients, SR as a first-line modality was used in 165 (31.7%) patients, CA in 132 (25.4%), and combined SR+CA in 223 (42.9%). FPE was observed in 166 patients (31.9%). First-line strategy was not associated with FPE. Tortuosity had a significant effect on FPE only in the CA group (aOR = 0.90 [95% CI 0.83-0.98]) compared with stent-retrievers and combined first-line approach (p interaction = 0.03). There was an interaction between thrombus length and first-line strategy for number of passes (p interaction = 0.04). Longer thrombi were associated with higher number of passes only in the CA group (acOR 1.03 [95% CI 1.00-1.06]). CONCLUSION: Our study suggests that vessel tortuosity and longer thrombi may negatively affect the performance of first-line contact aspiration catheters in acute stroke patients undergoing EVT.
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.003 | 0.005 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.002 | 0.002 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.000 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.002 | 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".