Traci McCarty, LISW-S, Clinical Director at The Village Network, a multi-discipline behavioral health organization in Ohio.
The COVID-19 crisis has demanded that we shift our practice in many ways, and staff have responded differently to those demands. I have found it helpful to remember that it is skill, not will, getting in the way for some staff, and to practice Plan B when problems arise.
Two weeks ago, upon order from Ohio’s Governor to shelter in place, our agency, like many, started the transition to telehealth; providing clinical services to youth and families remotely through use of technology. This process required our clinicians to learn how to use a new software application quickly and then immediately shift to the role of “teacher” to their clients.
Within a 5-day period, clinicians were trained in the new software application, state regulations, and best clinical practices to support the change to telehealth.
Simultaneously, these same clinicians were adjusting to working from home while also navigating through their own fears about community spread, home-schooling, and limited access to practical necessities like toilet paper. Many clinicians wondered whether they could be successful counseling clients by phone or laptop when they typically depend on using sensory regulating tools and relational-based interventions to capture and maintain children’s attention. It seemed that the conditions of telehealth appointments would make it likely that challenges and challenging behaviors would arise. The transition to telehealth meant that each clinician’s own emotional regulation and cognitive flexibility skills were being put to the test.
I noticed that one clinician in particular had not signed on to any of the required telehealth webinars or to the new software application. Zero clients were on the clinician’s schedule for telehealth.
Now, prior to our recent focus on implementing the Collaborative Problem Solving approach into our agency’s supervision philosophy, my response to this clinician would likely have been very “Plan A.” I might have assumed that this staff member was simply being uncooperative; avoiding the transition to telehealth to avoid having to put in extra work. My response might have included performance-based tracking forms and corrective actions.
However, since we have implemented Collaborative Problem Solving into both our clinical model and into our supervisory practices, we hold tightly to the philosophy that it is skill, not will getting in the way when our youth or our staff aren’t meeting expectations. I turned to Plan B to find out what was getting in the way of this clinician delivering services via telehealth to clients.
I started the Plan B conversation neutrally. “I noticed that you haven’t attended the telehealth webinars or started transitioning your clients to telehealth. What’s going on?”
In rapid fire, the clinician immediately expressed several concerns that were getting in the way of being able to transition to telehealth. First, they felt anxiety around using any new technology, and they were not able to find the necessary software application on the desktop. The clinician also cited doubts that elementary-school aged clients, most of whose families had limited financial resources, would be able to engage via telehealth, due to lack of access to WiFi, computers, and mobile phones; even the libraries where many clients and parents typically accessed internet are closed due to state orders. Finally, the clinician was very concerned that telehealth sessions would not be clinically useful, and that they would instead result in the clinician staring at carpet and ceiling fans via webcam. (Any aunt, uncle, or grandparent who has tried to face-time with a 6-year-old can probably relate to this!)
Wow, I thought. That’s a lot. And every one of those concerns was valid. In asking for this staff member’s perspective, I learned something new that would likely help me be a more effective leader in the confusing wake of COVID-19. I surmised that other clinicians were likely experiencing the same challenges. I made a mental note to follow up with others.
The calming effect of the first ingredient created the safety for the second ingredient: I expressed two concerns. First, our agency wanted to avoid contributing to a community spread of the virus. Second, continued contact with clients could be helpful to maintain the clinical relationship, to check for worries or other mental health needs related to the virus, and to keep an eye out for critical needs or the need for crisis intervention.
With both sets of concerns on the table, the clinician and I brainstormed several solutions. Some of the solutions were quick and easy. As it turned out, there was a technology glitch that impacted the software application from displaying on the clinician’s desktop. We solved it with just one email to the IT department. Once the clinician could actually see the software application, the novelty of the application became much less intimidating.
The clinician identified several other flexible strategies to provide consistent services during this time. One idea was using a hybrid model of phone calls and the web application, depending on the client’s level of access to the internet. In addition, the clinician requested permission to still provide face-to-face sessions when truly in the best interest of the client, utilizing all physical distance protocols and personal protective equipment. Finally, the clinician suggested that it would be helpful to have a plan for accessing technology support or a supervisor for quick troubleshooting if (and when) technology failed.
All of the solutions posed by the clinician were reasonable and do-able, and they met both of our concerns. In fact, the flexible options for using hybrid methods to connect, and the reminders of how to access supervisors and tech support were rolled out to every clinician to assure that no client was left behind in our shift to telehealth.
Cookie | Duration | Description |
---|---|---|
__cf_bm | 1 hour | This cookie, set by Cloudflare, is used to support Cloudflare Bot Management. |
__hssc | 1 hour | HubSpot sets this cookie to keep track of sessions and to determine if HubSpot should increment the session number and timestamps in the __hstc cookie. |
__hssrc | session | This cookie is set by Hubspot whenever it changes the session cookie. The __hssrc cookie set to 1 indicates that the user has restarted the browser, and if the cookie does not exist, it is assumed to be a new session. |
cookielawinfo-checkbox-advertisement | 1 year | Set by the GDPR Cookie Consent plugin, this cookie records the user consent for the cookies in the "Advertisement" category. |
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
CookieLawInfoConsent | 1 year | CookieYes sets this cookie to record the default button state of the corresponding category and the status of CCPA. It works only in coordination with the primary cookie. |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
Cookie | Duration | Description |
---|---|---|
li_gc | 6 months | Linkedin set this cookie for storing visitor's consent regarding using cookies for non-essential purposes. |
lidc | 1 day | LinkedIn sets the lidc cookie to facilitate data center selection. |
UserMatchHistory | 1 month | LinkedIn sets this cookie for LinkedIn Ads ID syncing. |
Cookie | Duration | Description |
---|---|---|
__hstc | 6 months | Hubspot set this main cookie for tracking visitors. It contains the domain, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session). |
_ga | 1 year 1 month 4 days | Google Analytics sets this cookie to calculate visitor, session and campaign data and track site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognise unique visitors. |
_ga_* | 1 year 1 month 4 days | Google Analytics sets this cookie to store and count page views. |
_gat_gtag_UA_* | 1 minute | Google Analytics sets this cookie to store a unique user ID. |
_gid | 1 day | Google Analytics sets this cookie to store information on how visitors use a website while also creating an analytics report of the website's performance. Some of the collected data includes the number of visitors, their source, and the pages they visit anonymously. |
AnalyticsSyncHistory | 1 month | Linkedin set this cookie to store information about the time a sync took place with the lms_analytics cookie. |
CONSENT | 2 years | YouTube sets this cookie via embedded YouTube videos and registers anonymous statistical data. |
hubspotutk | 6 months | HubSpot sets this cookie to keep track of the visitors to the website. This cookie is passed to HubSpot on form submission and used when deduplicating contacts. |
vuid | 1 year 1 month 4 days | Vimeo installs this cookie to collect tracking information by setting a unique ID to embed videos on the website. |
Cookie | Duration | Description |
---|---|---|
bcookie | 1 year | LinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser IDs. |
bscookie | 1 year | LinkedIn sets this cookie to store performed actions on the website. |
li_sugr | 3 months | LinkedIn sets this cookie to collect user behaviour data to optimise the website and make advertisements on the website more relevant. |
NID | 6 months | Google sets the cookie for advertising purposes; to limit the number of times the user sees an ad, to unwanted mute ads, and to measure the effectiveness of ads. |
test_cookie | 15 minutes | doubleclick.net sets this cookie to determine if the user's browser supports cookies. |
VISITOR_INFO1_LIVE | 6 months | YouTube sets this cookie to measure bandwidth, determining whether the user gets the new or old player interface. |
YSC | session | Youtube sets this cookie to track the views of embedded videos on Youtube pages. |
yt-remote-connected-devices | never | YouTube sets this cookie to store the user's video preferences using embedded YouTube videos. |
yt-remote-device-id | never | YouTube sets this cookie to store the user's video preferences using embedded YouTube videos. |
yt.innertube::nextId | never | YouTube sets this cookie to register a unique ID to store data on what videos from YouTube the user has seen. |
yt.innertube::requests | never | YouTube sets this cookie to register a unique ID to store data on what videos from YouTube the user has seen. |
Cookie | Duration | Description |
---|---|---|
__Secure-YEC | 1 year 1 month | Description is currently not available. |
_cfuvid | session | Description is currently not available. |
_pk_id.d014234b-506e-4c9f-8f74-9ecfcde5874f.838e | 1 hour | Description is currently not available. |
_pk_ses.d014234b-506e-4c9f-8f74-9ecfcde5874f.838e | 1 hour | Description is currently not available. |
cf_clearance | 1 year | Description is currently not available. |
ppms_privacy_d014234b-506e-4c9f-8f74-9ecfcde5874f | 1 year | Description is currently not available. |
VISITOR_PRIVACY_METADATA | 6 months | Description is currently not available. |