Lessons Learned in 2024: Insights & Strategies from Virtual Nursing Go-Lives
On-Demand Webinar
Lessons Learned in 2024: Insights & Strategies from Virtual Nursing Go-Lives
In this on-demand webinar, we take a candid, behind-the-scenes look at virtual nursing in 2024, as our team shares real-life experiences from over a dozen health system rollouts. In this engaging, roundtable-style conversation, our clinical experts discuss innovative implementations, unexpected challenges, and key successes that shaped 2024’s virtual nursing go-lives.
Key Takeaways:
Identify innovative applications of virtual nursing that enhanced patient care and streamlined workflows in 2024.
Understand critical success factors and common pitfalls in virtual nursing implementations, with practical troubleshooting examples.
Recognize key benefits health systems realized with virtual nursing, from improved patient engagement to increased clinical efficiency.
Get expert advice on planning and executing a virtual nursing program, including effective preparation and post-implementation strategies.
Hybrid Care Innovation at UMass Memorial Health
Digital innovation is a cornerstone of UMass Memorial Health’s strategy, garnering the health system impressive accolades including HIMSS Stage 7 certification for EMR adoption, CHIME’s Most Wired Level 8 certification, and Epic Gold Stars Level 10 status.
Dave Smith, Senior Director of Digital Innovation for UMass Memorial Health, attributes his organization’s competitive edge to a physician-led leadership team that truly embraces digital transformation. UMass Memorial has been delivering hybrid care for the better part of 20 years through its flagship eICU and tele-stroke programs. The throes of the pandemic and ensuing challenges related to patient safety, capacity management, patient flow, and staffing shortages reignited interest in hybrid care innovation, leading the health system to pursue additional programs like hospital at home, remote observation, and remote patient monitoring (RPM) in recent years.
In the enlightening session “Hybrid Care Innovation: The ROI of Bedside Virtual Care at Scale,” part of Becker’s Healthcare’s 2024 Digital Health and Telehealth Virtual Event, Smith sat down with Caregility President and COO Mike Brandofino to share compelling insights into the transformative hybrid care initiatives his organization is pursuing, how his team approaches ROI, and what it takes to scale new hybrid care models.
Hybrid Care’s Return on Value
UMass Memorial’s Hospital-at-Home program is a great example of how health systems are bringing resources to bear to improve outcomes, efficiency, and the experience for patients and clinicians. Patients receive twice-daily visits at home, supported by EMS partners working in collaboration with UMass doctors and nurses. They also have immediate access to virtual nursing support. The health system employs a four-to-one ratio for field nurses and a 30-to-one ratio for virtual nurses.
By bringing acute care to the patient’s home, the team has been able to expand capacity. “In our first year of operation, we saved over 3,000 bed days at our busiest hospitals,” shared Smith.
“With our eICU program, we monitor 150 critical care beds around the clock with intensivists on any given shift and the aid of a pharmacist at night,” Smith said. Since its inception in 2006, UMass’s eICU program has seen a 27% reduction in patient mortality and fewer patient complications, reducing care costs.
“For programs like tele-stroke and tele-psych, the ROI is really about improving access,” Smith continued. “But also, community hospitals see the ROI because they don’t have to hire and retain a full-time specialist. Instead, they buy professional services from a tertiary health system like UMass Memorial.”
The health system’s remote video monitoring (RVM) program has shown the strongest direct labor-cost ROI by enabling a single care team member to support six patients instead of conventional one-on-one observation ratios. “To take advantage of the full 12-patient panel, we assign each observation tech six primary patients and six backup patients for a total of 12,” Smith shared. “For every remote observation tech, we save $300,000 a year in direct labor costs.”
The health system is also leveraging AI solutions for radiology, ophthalmology, and ambient dictation to save providers valuable time. “I don’t think AI is going to replace doctors anytime soon, but I do think the ones who embrace it will probably surpass the ones who don’t,” noted Smith.
Scaling Hybrid Care Innovation
Smith sees digital health innovation as “the cost of doing business for healthcare systems that want to innovate and remain competitive.”
“We're in the process of building a new 72-bed inpatient facility that will open about a year from now and every bed will be wired with Caregility technology. We'll use the technology for a variety of use cases like virtual rounding, remote observation, specialty consults, patient/family communication, and even tele-ICU level care. And the funny thing is, it was an easy sell to hospital leadership because they understand the importance of hybrid care and balancing staffing demands. I just think hybrid care is the new standard.”
Dave Smith
Senior Director of Digital Innovation, UMass Memorial Health
Smith champions platforms that can be leveraged across the enterprise over point solutions. “To do anything at scale, it cannot exist in silos and pockets that are scattered throughout the organization,” he shared. “A good example is our commitment to building a digital medicine hub. We’re taking most of our virtual services and putting them under one roof. By doing so, not only will it be a showcase for our health system of the future, but we’re expecting to find operational synergies by having these virtual care teams collaborate in the same physical space. So, teams like eICU, transfer center, RVM, RPM, interpreter services, and virtual nursing will all be working alongside each other.”
“We’re also investing in a new digital innovation team to support rapid scalability. Digital health and especially AI is evolving so quickly that we need to operate at a faster pace to keep up. I’ll be leading a new multidisciplinary team to focus on emerging technologies that support our system initiatives and foster collaboration with our care teams. The whole idea is to identify opportunities, experiment with proofs of concept, fail fast, if necessary, iterate, and then deliver a solution or look at alternatives.”
“People are embracing technology in ways never thought possible and it’s making hybrid care models not only plausible but also practical.”
Hybrid Care Innovation: The ROI of Remote Bedside Engagement
On-Demand Webinar
Hybrid Care Innovation: The ROI of Remote Bedside Engagement
In this on-demand webinar, hosted by Becker’s Healthcare as part of their 2024 Digital Health + Telehealth Virtual Event, David Smith, Senior Director of Digital Innovation at UMass Memorial Health System, and Mike Brandofino, President and COO of Caregility, discuss the strategic advantages of extending virtual care to every patient room, best practices for navigating change management in the shift to hybrid care models, and how to create an integrated digital health infrastructure built for long-term success.
Topics Include:
Hybrid care models UMass has implemented to elevate the standard of care for patients and staff
How to cost-justify your programs and key hard and soft ROI factors
What it takes to scale virtual care to every patient bedside
Advice for other health systems pursuing similar innovation
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.