Efficacy of Personalized Repetitive Transcranial Magnetic Stimulation Protocol Based on Functional Reserve to Enhance Upper Limb Function in Subacute Stroke Patients
NCT: NCT06270238 · RECRUITING
Brief Summary
The objective of this study was to determine the effects of protocols of repetitive transcranial magnetic stimulation (rTMS) therapy based on the functional reserve of each hemiplegic stroke patient in subacute phase, compared to conventional low-frequency rTMS therapy on contralateral M1. Investigators hypothesized that the functional reserve of each hemiplegic stroke patient will be different, and therefore an appropriate simulating target for rTMS therapy is needed. In addition, this approach could be more effective compared to conventional protocols applied to stroke patients regardless of their severity, predicted mechanism of motor function recovery, or functional reserves.
Frequently Asked Questions
What is Efficacy of Personalized Repetitive Transcranial Magnetic Stimulation Protocol Based on Functional Reserve to Enhance Upper Limb Function in Subacute Stroke Patients?
Efficacy of Personalized Repetitive Transcranial Magnetic Stimulation Protocol Based on Functional Reserve to Enhance Upper Limb Function in Subacute Stroke Patients is a clinical trial registered under NCT06270238. Current status: RECRUITING.
What is the status of NCT06270238?
The current status of NCT06270238 (Efficacy of Personalized Repetitive Transcranial Magnetic Stimulation Protocol Based on Functional Reserve to Enhance Upper Limb Function in Subacute Stroke Patients) is: RECRUITING.
When did Efficacy of Personalized Repetitive Transcranial Magnetic Stimulation Protocol Based on Functional Reserve to Enhance Upper Limb Function in Subacute Stroke Patients start?
Efficacy of Personalized Repetitive Transcranial Magnetic Stimulation Protocol Based on Functional Reserve to Enhance Upper Limb Function in Subacute Stroke Patients started on 2024-02-13.
Official Source
View on ClinicalTrials.gov →Data sourced from ClinicalTrials.gov API. For the most current status, refer to the official record.