StrokeGuard: A Multi-Agent Guided System for Prehospital Stroke Assessment
Organizations: Institute of Medical Robotics School of Biomedical Engineering Shanghai Jiao Tong University Shanghai, China
Abstract
Prehospital stroke assessment aims to accurately identify stroke symptoms and make rapid decisions through standardized procedures within an extremely narrow time window, thereby saving valuable time for subsequent treatment. In clinical practice, FAST-based scales are widely used for prehospital stroke assessment by issuing instructions that guide subjects to perform specific actions to screen facial, arm, and speech functions. However, in home and community settings, non-clinical users often encounter challenges such as inaccurate descriptions, incomplete symptom observation, and difficult operational procedures, which may lead to inaccurate or biased assessment results. To address these challenges, this paper presents StrokeGuard: a multi-agent guided system designed for prehospital stroke assessment that makes mobile FAST screening more standardized and executable. Specifically, to overcome the limitations of traditional single-agent systems in terms of procedural fault tolerance and user guidance capability, StrokeGuard adopts a dual-channel agent mechanism that separates formal assessment (i.e., facial palsy, arm weakness, speech impairment) from procedural support (e.g., step prompts, error correction, and real-time feedback). It guides the assessment process through multi-agent collaboration, dual-channel interaction, state-machine control, and stage-local fallback recovery mechanisms. Stage-specific scoring is delegated to constrained pretrained video assessment modules, while evidence source records are integrated with structured report generation. The user evaluation uses MATES-9, an exploratory scale for measuring user experience in multistep AI-guided tasks. In a simulated prehospital scenario, StrokeGuard improves the MATES-9 total score over a paper FAST-style form by 10.83 points, corresponding to a 23.8% relative increase.
Figures & tables
| Agent | Roles and output |
|---|---|
| Dual-channel decision agent | Routes input to assessment or support; outputs channel label, target role, and routing record. |
| Assessment agent | Guides current-stage capture; outputs media submission, text fallback request, completion, waiting, or failure event. |
| Support agent | Answers operational, explanatory, reassuring, and emergency-response questions; outputs support reply without state change. |
| Shared elicitation. \raisebox{-0.35ex}{\scriptsize1}⃝ System : Next, please record the face of the patient. Ask him to look at the camera and smile as widely as possible. The current stage is Face capture. \raisebox{-0.35ex}{\scriptsize2}⃝ User : I am a bit anxious. If one side of his mouth looks crooked when he smiles, is that very serious? How far should I hold the phone so that the video is clear? | ||
| Trajectory | Ablated open-ended agent | StrokeGuard |
| Dialogue after the shared prefix | \raisebox{-0.35ex}{\scriptsize3}⃝ Agent : One-sided mouth droop may indicate facial asymmetry and stroke risk. I will first record it as a Face abnormality. Next, please observe whether his arms are weak. \raisebox{-0.35ex}{\scriptsize4}⃝ User : Wait, he has not smiled yet. I was only asking what would happen if the mouth is crooked. \raisebox{-0.35ex}{\scriptsize5}⃝ Agent : Understood. Let us record the face video again. Please ask the patient to look at the camera and smile. \raisebox{-0.35ex}{\scriptsize6}⃝ User : Was he already marked as having facial droop? I am worried that the report is wrong. | \raisebox{-0.35ex}{\scriptsize3}⃝ Dual-channel decision agent : Routes the input to the support channel and creates no Face assessment event. \raisebox{-0.35ex}{\scriptsize4}⃝ Support agent : Keep the phone facing the face of the patient and make sure the whole face is visible. Obvious mouth asymmetry can be relevant, but the system will not record a result from a hypothetical question. \raisebox{-0.35ex}{\scriptsize5}⃝ Assessment agent : Please ask the patient to look at the camera and smile as widely as possible, then submit the face video. \raisebox{-0.35ex}{\scriptsize6}⃝ User : OK, I will ask him to smile and upload the face video now. \raisebox{-0.35ex}{\scriptsize7}⃝ Orchestrator : Receives the Face video and starts Face processing; Arm can begin only after Face is completed or locally downgraded. |
| Mechanism exposed | A help request is written as clinical evidence and causes premature stage progression. | The support interaction is answered without changing Face evidence or stage state. |
| Shared elicitation. \raisebox{-0.35ex}{\scriptsize1}⃝ System : Next, please first record the face of the patient. Ask him to look at the camera and smile as widely as possible. The current stage is Face. \raisebox{-0.35ex}{\scriptsize2}⃝ User : I just noticed that his left hand suddenly became weak, and the cup fell from his hand. I recorded that he could not lift his arm. Should I show you this first? | ||
| Trajectory | Ablated open-ended agent | StrokeGuard |
| Dialogue after the shared prefix | \raisebox{-0.35ex}{\scriptsize3}⃝ Agent : Left-hand weakness and dropping the cup suggest an upper-limb abnormality. You can upload the video, and I will record an Arm abnormality. Since we have already observed an arm problem, let us continue to check whether speech is clear. \raisebox{-0.35ex}{\scriptsize4}⃝ User : But did you not just ask me to record the face first? I have not recorded his face. \raisebox{-0.35ex}{\scriptsize5}⃝ Agent : OK, then let us add the face video. Please ask the patient to smile. \raisebox{-0.35ex}{\scriptsize6}⃝ User : Will that arm video be treated as the face video? How will the report record this? \raisebox{-0.35ex}{\scriptsize7}⃝ Agent : I will integrate this information. Please continue with the face video. | \raisebox{-0.35ex}{\scriptsize3}⃝ Dual-channel decision agent : Marks the left-hand weakness as stage-outside risk information and does not submit the arm video as current Face evidence. \raisebox{-0.35ex}{\scriptsize4}⃝ Support agent : Sudden left-hand weakness is important. Keep emergency help active and maintain scene safety. The current workflow still needs Face capture first; the arm video can be used in the Arm stage. \raisebox{-0.35ex}{\scriptsize5}⃝ Orchestrator : Rejects writing the arm video into the Face evidence slot and continues to request Face video. \raisebox{-0.35ex}{\scriptsize6}⃝ User : Understood. I will record his face first. \raisebox{-0.35ex}{\scriptsize7}⃝ Assessment agent and orchestrator : Accept the Face video, complete Face, and then enter Arm, where upper-limb video or Arm-stage text fallback can be accepted. |
| Mechanism exposed | Clinically important stage-outside evidence is allowed to replace the current stage, causing stage skipping and unclear media attribution. | Stage identity, task identity, and evidence-source checks preserve Face–Arm–Speech order and prevent wrong-stage writes. |
| Shared elicitation. \raisebox{-0.35ex}{\scriptsize1}⃝ System : Face and Arm have been recorded. Now ask the patient to repeat this sentence: The weather is good today, and I want to drink a glass of water. The current stage is Speech. \raisebox{-0.35ex}{\scriptsize2}⃝ User : His voice is very low. I keep failing to record it, and the upload keeps failing. Can I describe his condition directly? | ||
| Trajectory | Ablated open-ended agent | StrokeGuard |
| Dialogue after the shared prefix | \raisebox{-0.35ex}{\scriptsize3}⃝ Agent : Yes. Please describe his face, arms, and speech in text, and I will complete the assessment from your description. \raisebox{-0.35ex}{\scriptsize4}⃝ User : Were the face and arms not already recorded? Do I need to say everything again? \raisebox{-0.35ex}{\scriptsize5}⃝ Agent : To ensure completeness, please describe all findings again. \raisebox{-0.35ex}{\scriptsize6}⃝ User : I think his face is a bit crooked, his left arm is weak, and his speech is slurred. \raisebox{-0.35ex}{\scriptsize7}⃝ Agent : Facial abnormality, upper-limb abnormality, and speech abnormality have been recorded. Assessment complete. | \raisebox{-0.35ex}{\scriptsize3}⃝ Orchestrator : Binds the failure event to the Speech stage and does not roll back Face or Arm. \raisebox{-0.35ex}{\scriptsize4}⃝ Assessment agent : Please try recording again. Move closer to the patient, reduce background noise, and ask him to repeat the sentence once more. \raisebox{-0.35ex}{\scriptsize5}⃝ User : It still cannot record. Can I directly describe his speech? \raisebox{-0.35ex}{\scriptsize6}⃝ Assessment agent : Yes. Please describe only whether his speech is slurred, whether he has difficulty producing the sentence, or whether he seems unable to understand the instruction. Face and Arm do not need to be described again. \raisebox{-0.35ex}{\scriptsize7}⃝ User : His speech is slurred, and he cannot complete the sentence. \raisebox{-0.35ex}{\scriptsize8}⃝ Orchestrator and report module : Records Speech text fallback, preserves Face and Arm video results, and marks the Speech fallback reason in the report. |
| Mechanism exposed | A Speech failure spreads to the whole assessment and risks replacing completed video evidence with lower-priority text. | Recovery is bound to the current stage; Speech fallback cannot overwrite completed Face or Arm video evidence. |
| Item | Statement and construct |
|---|---|
| Q1 + | Complete all required task steps without additional researcher prompts; independent completion. |
| Q2 + | Clearly know the current task step; step orientation. |
| Q3 + | Clearly understand what the current step needs to collect or provide; input clarity. |
| Q4 R | Often unsure what to do next; next-step uncertainty. |
| Q5 R | Lose the original task position after help or explanation; support interruption. |
| Q6 R | Need to remember too much information at the same time; cognitive load. |
| Domain | Items | Source constructs |
|---|---|---|
| Task usability and guidance | Q1-Q2 | SUS reverse construct of technical-support dependence, task-completion ease, MAUQ information organization. |
| Information clarity | Q3-Q4r | MAUQ information organization, ASQ support information, PSSUQ/CSUQ information quality. |
| Support continuity | Q5r | CUQ/BUS dialogue continuity and error handling, Health-ITUES user control. |
| Low workload | Q6r-Q7r | NASA-TLX mental demand, physical demand, and effort. |
| Action support | Q8-Q9 | MAUQ/Health-ITUES usefulness, TAM perceived usefulness. |
Clinical Decision Support
Clinical Decision Support uses data, medical knowledge, and AI to help clinicians assess patients and choose tests, diagnoses, and treatments.
See all 242 papers