Tele-Neurology: Trends in Stroke Management and Brain Health
Virtual care is changing how stroke patients and those with complex brain and nervous system disorders are being treated and managed. This blog examines the adoption of tele-stroke programs and other tele-neurology use cases that are helping healthcare providers improve patient access and outcomes.
The important role that telemedicine plays in supporting acute care intervention through programs like tele-stroke is well documented. The research is clear: “Alerting neurologists via telemedicine that a patient with suspected acute stroke is en route to the hospital significantly enhances the speed at which thrombolysis is administered and increases the number of patients who receive timelier, potentially lifesaving treatment.”
Case in Point: In research exploring the impact of tele-neurology pre-notification during stroke cases, 50.4% of patients whose care team received a tele-neurology pre-notification received treatment within 30 minutes of arrival versus 18.9% of patients in the no pre-notification group.
High-acuity patient threats such as strokes demand rapid response and intervention to prevent severe brain damage and disability. Here are just a few examples of the ways leading healthcare organizations are improving patient care through tele-stroke programs:
Mayo Clinic has expanded its TeleStroke Network services across multiple states, ensuring that stroke expertise is just a video call away. The program has dramatically increased the timely use of thrombolytic therapies in rural hospitals. Learn more about Mayo Clinic’s tele-stroke network services.
Bringing tele-stroke into their digital-first approach, Kaiser Permanente’s integrated tele-stroke service offers immediate stroke assessments, reducing the time to treatment. Their model showcases a significant reduction in door-to-needle times and improved patient outcomes. Discover more about Kaiser Permanente’s integrated tele-stroke approach.
Cleveland Clinic developed a robust statewide tele-stroke network that serves patients across Ohio, ensuring rapid diagnosis and treatment. The network has been crucial in streamlining stroke care protocols and enhancing the accessibility of specialist consultations. Read more about Cleveland Clinic’s tele-stroke network.
Increasingly, providers are amplifying efforts around tele-neurology to extend the benefits of the virtual care model to patients who are recovering from strokes or other traumatic brain injuries. These patients often require closer monitoring and more frequent interventions due to memory impairment.
Telehealth programs like Virtual Patient Observation support around-the-clock care for these high-acuity patient populations, helping to reinforce patient safety and support. Virtual visits are also ideal for fielding follow-up care visits and symptom management for many neurological conditions.
And the field is ripe for further innovation. The incorporation of technologies like eye-tracking and computer vision into virtual care will unlock new possibilities in the field of remote clinical diagnostics for neurodegenerative conditions such as Alzheimer’s, autism, and Parkinson’s, where problems in the brain can often be detected in eye function.
The evolution of virtual care in neurology marks a pivotal shift in how strokes, brain injuries, and neurological disorders are treated and managed. Advances in technology have enabled widespread adoption of tele-stroke services, making specialist care immediately accessible, even in remote locations. As we continue to innovate, the potential to further decrease response times and improve outcomes through tele-neurology looks increasingly promising.
When Time is Brain, TeleStroke Changes Lives
More than 25 years ago, neurologist Camilo R. Gomez, M.D., coined the phrase “Time is Brain” to describe the urgency of timely treatment for stroke survivors. It is estimated that we lose 1.9 million brain cells a minute when a stroke blocks blood flow to the brain, so every moment of delayed treatment increases the risk of death and/or long-term disability.
Yet most stroke patients do not receive timely treatment, according to the American Stroke Association. Many put off going to the emergency room, and when they do show up their hospital is unlikely to have a neurologist on call — particularly if they live in a rural area. That’s why the American Heart Association and the American Stroke Association strongly advocate for the expanded use of telestroke programs.
What Is Telestroke?
Telestroke is the use of interactive videoconferencing technologies to make stroke specialists available, anytime day or night, to remotely diagnose and treat stroke patients in collaboration with on-site emergency room physicians and other medical professionals.
About 87 percent of strokes are ischemic strokes, which happen when a clot blocks a vessel supplying blood to the brain. Less common are hemorrhagic strokes, which occur when a blood vessel ruptures and bleeds into the brain. The goal in treating a hemorrhagic stroke is to control the bleeding and pressure on the brain, usually with drugs and/or surgery. The goal in treating the more common ischemic stroke is to dissolve or remove the blood clot.
The single most promising treatment for ischemic strokes is a fast-acting, clot-dissolving blood thinner known as tissue Plasminogen Activator or tPA, which was approved by the FDA in 1996. But though we know that tPA can reverse stroke symptoms and significantly improve patient outcomes, it is used in only an estimated 3 to 6 percent of stroke patients.
Why? Because it works best if administered intravenously within an hour of the onset of symptoms. The sooner the treatment, the more likely a patient will survive with minimal or even zero disability. After three to four-and-a-half hours (the timing varies for individual patients and requires assessment by a neurologist), the risk of serious side effects — mainly bleeding in the brain — outweighs any potential benefits.
Telemedicine for Strokes: A Success Story
A 2016 American Heart Association/American Stroke Association review of the literature on telemedicine and stroke outcomes described telestroke as “one of the most successful applications of telemedicine.” Early studies found that the risk of serious complications increased significantly when tPA was administered by inexperienced doctors. Subsequent studies found that telestroke networks led to better adherence to protocols for administering the drug and better outcomes for patients.
With telestroke, a neurologist can immediately interview and virtually examine the patient, read their CT scan, evaluate blood tests, and determine both the type of stroke and the safest and most effective possible treatment. Without being able to see the patient and the CT scan for themselves, even an experienced neurologist — during a phone consultation, for instance — can easily misdiagnose a stroke.
“Stroke mimics,” for instance, are medical conditions that present with similar symptoms. The most common are seizures, but they can include migraines, brain tumors, and even low sodium or low blood sugar. Misdiagnosing a patient and treating stroke mimics or hemorrhagic strokes with tPA can put a patient at extreme risk.
Using telemedicine for strokes, neurologists can supervise timely treatment with intravenous tPA and minimize the attendant risks. And they can screen patients who might benefit from other interventions, including endovascular therapy — in which a catheter is used to remove the clot from the vessel inside the brain — and oversee their transfer to a stroke center for that procedure and further evaluation and treatment.
Telestroke Saves Patients and Money
For at least two decades, stroke experts have been advocating for telestroke to promote timely care and save lives. Telestroke has been shown to increase the use of tPA in hospitals, and it allows hospitals to treat patients with tPA on site rather than transferring them to the nearest stroke center where they are likely to arrive after the narrow window of time during which the drug can be safely and effectively administered. Telestroke has also been shown to be highly cost effective for hospitals and society at large because timely treatment allows patients to be discharged sooner and reduces the need for rehabilitative care.
Telestroke technology has come a long way since Drs. Steven R. Levine and Mark Gorman coined the term in 1999 to describe their proposal that rural emergency rooms use bedside video cameras to connect to urban stroke specialists.
Today, using the most sophisticated audio-video conferencing and digital image sharing technology now available, telestroke platforms help emergency room doctors fulfill that 1999 dream — transcending time and space to bring neurological expertise to their patients’ bedsides at the moment they need it.
Learn how Caregility can change how you delivery stroke care with a customized telestroke program.
Cookie Consent
We use cookies to improve your experience on our site. By using our site, you consent to cookies.
Cookie Preferences
Manage your cookie preferences below:
Essential cookies enable basic functions and are necessary for the proper function of the website.
Name
Description
Duration
Geolocation Config
This cookie is used to store the consent settings based on the visitor's location.
60 days
Cookie Preferences
This cookie is used to store the user's cookie consent preferences.
60 days
CloudFlare provides web performance and security solutions, enhancing site speed and protecting against threats.
These cookies are for internal use which allows Cloudflare to identify production issues on clients.
session
cf_chl_rc_m
These cookies are for internal use which allows Cloudflare to identify production issues on clients.
session
__cfruid
Used by the content network, Cloudflare, to identify trusted web traffic.
session
__cf_bm
Cloudflare's bot products identify and mitigate automated traffic to protect your site from bad bots. Cloudflare places the __cf_bm cookie on End User devices that access Customer sites that are protected by Bot Management or Bot Fight Mode. The __cf_bm cookie is necessary for the proper functioning of these bot solutions.
session
__cflb
When enabling session affinity with Cloudflare Load Balancer, Cloudflare sets a __cflb cookie with a unique value on the first response to the requesting client. Cloudflare routes future requests to the same origin, optimizing network resource usage. In the event of a failover, Cloudflare sets a new __cflb cookie to direct future requests to the failover pool.
session
_cfuvid
The _cfuvid cookie is only set when a site uses this option in a Rate Limiting Rule, and is only used to allow the Cloudflare WAF to distinguish individual users who share the same IP address.
session
cf_clearance
Whether a CAPTCHA or Javascript challenge has been solved.
session
__cfseq
Sequence rules uses cookies to track the order of requests a user has made and the time between requests and makes them available via Cloudflare Rules. This allows you to write rules that match valid or invalid sequences. The specific cookies used to validate sequences are called sequence cookies.
session
cf_ob_info
The cf_ob_info cookie provides information on: The HTTP Status Code returned by the origin web server. The Ray ID of the original failed request. The data center serving the traffic
session
cf_use_ob
The cf_use_ob cookie informs Cloudflare to fetch the requested resource from the Always Online cache on the designated port. Applicable values are: 0, 80, and 443. The cf_ob_info and cf_use_ob cookies are persistent cookies that expire after 30 seconds.
session
__cfwaitingroom
The __cfwaitingroom cookie is only used to track visitors that access a waiting room enabled host and path combination for a zone. Visitors using a browser that does not accept cookies cannot visit the host and path combination while the waiting room is active.
session
cf_chl_rc_i
These cookies are for internal use which allows Cloudflare to identify production issues on clients.
session
Statistics cookies collect information anonymously. This information helps us understand how visitors use our website.
Google Analytics is a powerful tool that tracks and analyzes website traffic for informed marketing decisions.
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
__utma
ID used to identify users and sessions
2 years after last activity
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
__utmv
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.
18 months
_ga
ID used to identify users
2 years
_gali
Used by Google Analytics to determine which links on a page are being clicked
30 seconds
_ga_
ID used to identify users
2 years
_gid
ID used to identify users for 24 hours after last activity
24 hours
_gat
Used to monitor number of Google Analytics server requests when using Google Tag Manager
1 minute
Google Tag Manager simplifies the management of marketing tags on your website without code changes.
Name
Description
Duration
td
Registers statistical data on users' behaviour on the website. Used for internal analytics by the website operator.
session
cookiePreferences
Registers cookie preferences of a user
2 years
Hotjar is a powerful analytics tool that helps you understand user behavior through heatmaps and session recordings.
Name
Description
Duration
_hjCachedUserAttributes
This cookie stores User Attributes which are sent through the Hotjar Identify API, whenever the user is not in the sample. These attributes will only be saved if the user interacts with a Hotjar Feedback tool.
session
_hjIncludedInSessionSample
This cookie is set to let Hotjar know whether that visitor is included in the data sampling defined by your site's daily session limit
30 minutes
_hjSession_
A cookie that holds the current session data. This ensues that subsequent requests within the session window will be attributed to the same Hotjar session.
30 minutes
_hjSessionUser_
Hotjar cookie that is set when a user first lands on a page with the Hotjar script. It is used to persist the Hotjar User ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID.
365 days
_hjSessionTooLarge
Causes Hotjar to stop collecting data if a session becomes too large. This is determined automatically by a signal from the WebSocket server if the session size exceeds the limit.
session
_hjSessionRejected
If present, this cookie will be set to 1 for the duration of a user’s session, if Hotjar rejected the session from connecting to our WebSocket due to server overload. This cookie is only applied in extremely rare situations to prevent severe performance issues.
session
_hjSessionResumed
A cookie that is set when a session/recording is reconnected to Hotjar servers after a break in connection.
session
hjViewportId
This cookie stores user viewport details such as size and dimensions.
Session
_hjSessionStorageTest
This cookie checks if the Hotjar Tracking Code can use Session Storage. If it can, a value of 1 is set.
Session
_hjTLDTest
When the Hotjar script executes we try to determine the most generic cookie path we should use, instead of the page hostname. This is done so that cookies can be shared across subdomains (where applicable). To determine this, we try to store the _hjTLDTest cookie for different URL substring alternatives until it fails. After this check, the cookie is removed.
session
_hjCookieTest
This cookie checks to see if the Hotjar Tracking Code can use cookies. If it can, a value of 1 is set.
Session
_hjUserAttributesHash
User Attributes sent through the Hotjar Identify API are cached for the duration of the session in order to know when an attribute has changed and needs to be updated.
session
_hjIncludedInPageviewSample
This cookie is set to let Hotjar know whether that visitor is included in the data sampling defined by your site's page view limit.
30 minutes
_hjLocalStorageTest
This cookie is used to check if the Hotjar Tracking Script can use local storage. If it can, a value of 1 is set in this cookie. The data stored in_hjLocalStorageTest has no expiration time, but it is deleted immediately after creating it so the expected storage time is under 100ms.
-
_hjHasCachedUserAttributes
This cookie sets when a user first lands on a page. Persists the Hotjar User ID which is unique to that site. Hotjar does not track users across different sites. Ensures data from subsequent visits to the same site are attributed to the same user ID.
365 days
_hjid
Hotjar cookie. This cookie is set when the customer first lands on a page with the Hotjar script. It is used to persist the random user ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID.
365 days
hj_visitor
hotjar uses cookies to enhance the user’s experience on our website, for example to complete forms, navigating the site, and identify returning users and offer related content. Users can control the use of cookies at the individual browser level.
Session
_hjIncludedInSample
Hotjar cookie. This session cookie is set to let Hotjar know whether that visitor is included in the sample which is used to generate funnels.
365 days
_hjClosedSurveyInvites
Hotjar cookie. This cookie is set once a visitor interacts with a Survey invitation modal popup. It is used to ensure that the same invite does not re-appear if it has already been shown.
365 days
_hjDonePolls
Hotjar cookie. This cookie is set once a visitor completes a poll using the Feedback Poll widget. It is used to ensure that the same poll does not re-appear if it has already been filled in.
365 days
_hjMinimizedPolls
Hotjar cookie. This cookie is set once a visitor minimizes a Feedback Poll widget. It is used to ensure that the widget stays minimizes when the visitor navigates through your site.
365 days
_hjDoneTestersWidgets
Hotjar cookie. This cookie is set once a visitor submits their information in the Recruit User Testers widget. It is used to ensure that the same form does not re-appear if it has already been filled in.
365 days
_hjMinimizedTestersWidgets
Hotjar cookie. This cookie is set once a visitor minimizes a Recruit User Testers widget. It is used to ensure that the widget stays minimizes when the visitor navigates through your site.
365 days
_hjShownFeedbackMessage
This cookie is set when a visitor minimizes or completes Incoming Feedback. This is done so that the Incoming Feedback will load as minimized immediately if they navigate to another page where it is set to show.
365 days
_hjFirstSeen
The cookie is set so Hotjar can track the beginning of the user's journey for a total session count. It does not contain any identifiable information.
30 minutes
_hjAbsoluteSessionInProgress
The cookie is set so Hotjar can track the beginning of the user's journey for a total session count. It does not contain any identifiable information.
30 minutes
_hjptid
This cookie is set for logged in users of Hotjar, who have Admin Team Member permissions. It is used during pricing experiments to show the Admin consistent pricing across the site.
session
Vimeo is a video hosting platform for high-quality content, ideal for creators and businesses to showcase their work.
Collects analytical tracking information about videos and enables the player to function properly.
2 years
sd_identity
Collects analytical tracking information about videos and enables the player to function properly.
2 years
continuous_play_v3
Used to keep track of whether continuous play is on or not for a user
2 years
Player
This first party cookie created by Vimeo is used to remember user’s player mode preferences.
1 minute
vuid
This first party cookie created by Vimeo is used to assign a Vimeo Analytics unique id.
1 minute
Marketing cookies are used to follow visitors to websites. The intention is to show ads that are relevant and engaging to the individual user.
Name
Description
Duration
hubspotutk
Hubspot
1 day
__hstc
Hubspot
6 months
__hstc
Hubspot
1 day
__hssrc
Hubspot
1 day
__hssc
Hubspot
1 day
HubSpot is an all-in-one marketing, sales, and customer service platform that streamlines business growth.
Name
Description
Duration
hs-messages-hide-welcome-message
This cookie is used to prevent the chat widget welcome message from appearing again for one day after it is dismissed.
1 day
hubspotapi-prefs
This is used with the hubspotapi cookie to remember whether the user checked the 'remember me' box (controls the expiration of the main cookie's authentication).
1 Year
hubspotapi
This cookie allows the user to access the app with the correct permissions.
7 days
__hs_opt_out
This cookie is used by the opt-in privacy policy to remember not to ask the visitor to accept cookies again.
13 months
hubspotapi-csrf
This is used for CSRF prevention - preventing third party websites from accessing your data. Expires after a year.
1 year
__hs_do_not_track
This cookie can be set to prevent the tracking code from sending any information to HubSpot.
13 months
__hs_cookie_cat_pref
This cookie is used to record the categories a visitor consented to.
6 months
__hs_initial_opt_in
This cookie is used to prevent the banner from always displaying when visitors are browsing in strict mode.
7 days
__hs_gpc_banner_dismiss
This cookie is used when the Global Privacy Control banner is dismissed.
180 days
hs_ab_test
This cookie is used to consistently serve visitors the same version of an A/B test page they’ve seen before.
session
__hs_notify_banner_dismiss
This cookie is used when the website uses a Notify consent banner type.
180 days
hs-messages-is-open
This cookie is used to determine and save whether the chat widget is open for future visits.
30 minutes
__hsmem
This cookie is set when visitors log in to a HubSpot-hosted site.
1 year
hs-membership-csrf
This cookie is used to ensure that content membership logins cannot be forged.
session
hs_langswitcher_choice
This cookie is used to save the visitor's selected language choice when viewing pages in multiple languages.
2 years
__hstc
The main cookie for tracking visitors.
13 months
hubspotutk
This cookie keeps track of a visitor's identity. It is passed to HubSpot on form submission and used when deduplicating contacts.
13 months
__hssc
This cookie keeps track of sessions.
30 minutes
__hssrc
Whenever HubSpot changes the session cookie, this cookie is also set to determine if the visitor has restarted their browser.
session
messagesUtk
This cookie is used to recognize visitors who chat with you via the chatflows tool. If the visitor leaves your site before they're added as a contact, they will have this cookie associated with their browser.
13 months
LinkedIn Insight is a web analytics service that tracks and reports website traffic.