TRV-2026-2017Version 1 · Certified
Reason for this version
Certified into the record
Canonical text (the exact bytes fingerprinted)
TRUVACE RECORD VERSION record: TRV-2026-2017 version: 1 kind: certified reason: Certified into the record timestamp: 2026-10-20T10:43:36.692092Z status: published lens: g_space sector: health headline: Impact of RapidAI® Implementation on Workflow Metrics and Access to Reperfusion Therapies in Acute Ischemic Stroke: A 10-Year Retrospective Analysis dek: Background and Purpose: Artificial intelligence‑assisted perfusion imaging can support selection and coordination in acute ischemic stroke (AIS). This study assessed institutional changes in access to reperfusion therapies and workflow metrics before and after RapidAI® implementation. Methods: We retrospectively analyzed consecutive AIS admissions (July 2014–October 2024) at a single comprehensive stroke center, comparing pre‑implementation and post‑implementation periods (RapidAI® introduced June 2018). Primary… gain_title: After a single stroke center adopted AI perfusion imaging, adjusted analysis showed fewer rescue decompressive craniectomies and about 2.3 fewer hospital days per patient, though this is an association. problem_title: (none) trace_subject: (none) gain_reading: After a single stroke center adopted AI perfusion imaging, adjusted analysis showed fewer rescue decompressive craniectomies and about 2.3 fewer hospital days per patient, though this is an association. gain_evidence: Rescue decompressive craniectomy was lower in the post period | hospital length of stay was reduced (adjusted B −2.33 days problem_reading: (none) problem_evidence: (none) quick_read: Researchers reviewed 2,144 consecutive acute ischemic stroke admissions at one comprehensive stroke center between July 2014 and October 2024. They compared the years before and after the center introduced RapidAI in June 2018, an AI-assisted perfusion imaging tool. Adjusted results showed lower rescue decompressive craniectomy and shorter hospital stays after implementation. The study design cannot show that the software caused these changes, and the authors urge caution because of low software use and possible background trends. limitation: The authors note that low software utilization and possible secular trends mean the findings should be interpreted cautiously; this single-center before-and-after design shows coincidence rather than causation. tag: Evidence-backed gain key_points: The analysis covered 2,144 stroke patients treated at one comprehensive stroke center from July 2014 to October 2024. | Adjusted odds of rescue decompressive craniectomy were lower after implementation (OR 0.15; 95% CI 0.03–0.82). | Hospital stay fell by an adjusted 2.33 days (95% CI −3.62 to −1.03). | Intravenous thrombolysis and mechanical thrombectomy use did not differ significantly between periods. rundown: The study compared pre- and post-implementation periods, with RapidAI introduced in June 2018. Primary outcomes were use of intravenous thrombolysis and mechanical thrombectomy, discharge mRS 0–1, and decompressive craniectomy. Neither thrombolysis (adjusted OR 0.93) nor thrombectomy (adjusted OR 2.73, with a wide interval of 0.70–10.61) showed a significant change. Door-to-needle time was also not significantly different. Functional outcomes, including discharge mRS 0–1 and ordinal mRS at discharge and 90 days, showed no significant adjusted differences. Sensitivity analyses using multiple imputation gave consistent results. sources: - peer_reviewed | Cerebrovascular Diseases | https://doi.org/10.1159/ced/accag042 | 2026-10-19 prev: 0000000000000000000000000000000000000000000000000000000000000000
- sha256
- 25a1f3fae76471527c36a049d2720acc1ea83eb727ecb618ef988106ba0b913d
- previous
- 0000000000000000000000000000000000000000000000000000000000000000
Verify this record
How to verify without trusting this page
Fetch the canonical text of any version from /api/record/TRV-2026-2017 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.
ace