WEBVTT
00:00:00.479 --> 00:00:03.200
It's 9 p.m., my phone rings.
00:00:03.439 --> 00:00:05.360
Instinctively, I pick it up.
00:00:06.320 --> 00:00:14.080
The nurse practitioner from the ER starts asking me about a patient with right lower quadrant abdominal pain.
00:00:14.640 --> 00:00:16.239
There's only one problem.
00:00:16.480 --> 00:00:17.839
I'm not on call.
00:00:18.079 --> 00:00:19.839
I switched my call day with Dr.
00:00:20.000 --> 00:00:20.640
King.
00:00:20.960 --> 00:00:26.640
I don't know this patient, but even if I did, the on-call surgeon's job is to manage it.
00:00:26.879 --> 00:00:32.240
Ironically, I still answer because that's what we're trained to do: pick up the phone.
00:00:32.560 --> 00:00:35.280
But here's what no one tells you in residency.
00:00:35.520 --> 00:00:40.560
Being reachable and being available are not necessarily the same thing.
00:00:41.039 --> 00:00:47.759
One means your phone works, the other means you're the physician who's actually supposed to be taking this call.
00:00:48.960 --> 00:00:52.000
Too often in my career, I found out the hard way.
00:00:52.320 --> 00:00:56.159
Even this far into my practice, I still get roped in.
00:00:56.479 --> 00:01:04.159
The schedule can say one thing, and reality can say another, and the gap between them lands on whoever picks up that phone.
00:01:04.480 --> 00:01:07.760
Today, it just happened to be me.
00:01:08.719 --> 00:01:09.599
Welcome back.
00:01:09.760 --> 00:01:10.239
I'm Dr.
00:01:10.319 --> 00:01:15.040
Kevin Hallow, co-founder and chief medical officer of Clinician Corps.
00:01:15.280 --> 00:01:20.640
Today I want to talk to you about something we all know too well, the call schedule.
00:01:21.040 --> 00:01:32.799
But today I want to focus on the difference between a static schedule and a smart schedule, and why the former fuels burnout and the latter leaves it.
00:01:33.280 --> 00:01:45.280
Unfortunately, we've all been there and know too well that if you're fresh out of training, you are the most likely person in your group to get a misrouted call.
00:01:45.599 --> 00:01:48.319
It's not because anyone is targeting you.
00:01:49.040 --> 00:01:52.239
Maybe it's just because they want to give you a sympathy consult.
00:01:52.480 --> 00:02:04.640
But really, more likely, you're new to the rotation, you don't have the standing to question a schedule, and you've not built the workarounds that senior partners have developed over the years.
00:02:06.079 --> 00:02:11.759
Physician work weeks are running pretty close to 58 hours on average.
00:02:12.000 --> 00:02:16.879
And a meaningful chunk of that is pure administrative drag.
00:02:17.439 --> 00:02:22.240
A late night call for coverage that isn't yours is not just annoying.
00:02:22.400 --> 00:02:26.080
It's a withdrawal from an account that's already overdrawn.
00:02:26.240 --> 00:02:29.280
You're tired, but now you can't go back to sleep.
00:02:29.439 --> 00:02:32.560
It's an energy drain that just burns you out.
00:02:33.199 --> 00:02:38.400
When it happens to you, it's not a sign you are bad at managing call.
00:02:38.960 --> 00:02:49.360
If your group's routing runs off a static list, a swap that you made yesterday might not register until the call schedule coordinator processes it.
00:02:49.680 --> 00:02:51.360
Who knows when that might be?
00:02:51.599 --> 00:02:53.520
You did nothing wrong.
00:02:53.840 --> 00:02:58.080
The schedule was just behind reality, once again.
00:02:59.120 --> 00:03:02.560
A static scheduling system does not ask questions.
00:03:02.719 --> 00:03:06.080
It simply lists who the person is to contact.
00:03:06.240 --> 00:03:09.360
Whether that is right or wrong does not matter to that system.
00:03:09.759 --> 00:03:13.840
It's just a name on a calendar day that fills a checkbox.
00:03:14.159 --> 00:03:19.199
On the other hand, a schedule aware system asks questions.
00:03:19.360 --> 00:03:25.840
For example, who is actually on call right now for this coverage area at this moment?
00:03:26.639 --> 00:03:34.639
The difference between those two systems is the difference between another night of harassment and a good night's sleep.
00:03:35.599 --> 00:03:42.240
So ask your practice manager this today, not after it costs you another bad night.
00:03:42.879 --> 00:03:51.360
When I swap a call with a colleague, how fast does that change actually show up on our static call schedule?
00:03:51.680 --> 00:03:57.919
What happens if the person who is supposed to make that change is out of the office or not available?
00:03:58.159 --> 00:04:01.360
How do I know that the change has been made?
00:04:01.759 --> 00:04:14.400
If the answer is that the change is not automatic and instantaneous, then that just represents another phone call that will go to the wrong person at the wrong time.
00:04:14.719 --> 00:04:17.279
And that includes you.
00:04:18.480 --> 00:04:25.759
If you want to know the real energy drain of a static call schedule, try this exercise.
00:04:26.800 --> 00:04:42.959
First, go back and confirm all of your scheduled days on the call schedule, including those swaps that you've made, and see how long it takes you to jump through all of those hoops.
00:04:43.600 --> 00:04:55.360
Next, make a mental note of how much time it takes you to recheck and reconfirm the call schedule weekly, especially when you make a last-minute swap.
00:04:56.800 --> 00:05:01.920
Then think about how many times the wrong call went to you.
00:05:02.560 --> 00:05:10.160
Does your static call schedule scheduling system really work or is it hit and miss?
00:05:11.120 --> 00:05:16.560
How often does your static schedule get this call schedule wrong?
00:05:17.040 --> 00:05:20.639
Finally, add it all up and track the pattern.
00:05:21.439 --> 00:05:27.519
If you're catching coverage that isn't yours more than once, that's not noise.
00:05:28.000 --> 00:05:34.160
That's a signal worth naming out loud to your group and to your practice manager.
00:05:34.800 --> 00:05:43.839
The difference between reachable and available all depends upon a name, on a date, on a calendar.
00:05:44.160 --> 00:05:54.800
However, that difference also defines a very important boundary that marks an enjoyable practice from an unpleasant one.
00:05:55.360 --> 00:05:59.279
Enjoyable practices are sustainable for an entire career.
00:05:59.920 --> 00:06:06.399
Unpleasant practices just lead to more burnout and an early end of that career.
00:06:07.360 --> 00:06:10.959
Static scheduling systems do not ask questions.
00:06:11.199 --> 00:06:15.920
They just represent another box that was checked by someone.
00:06:16.720 --> 00:06:30.800
Take a moment and ask the people who run your schedule if the system knows who's actually on call, or just who's on call the last time someone remembered to update a list.
00:06:32.480 --> 00:06:36.879
The difference is way too important to ignore anymore.
00:06:38.079 --> 00:06:42.079
Okay, that's it for today's video podcast.
00:06:42.319 --> 00:06:54.480
Don't forget to check out our website, cliniciancore.com, to learn about on-call scheduled aware routing, as well as the many other features that Clinician Core provides.
00:06:54.800 --> 00:07:02.720
While you're there, sign up for our wait list to take part in our soft launch and our upcoming release.
00:07:03.279 --> 00:07:11.439
You can also follow us on LinkedIn, YouTube, Spotify, Instagram, Facebook, and Reddit.
00:07:11.759 --> 00:07:14.160
There's no excuse not to check out Clinici.
00:07:15.199 --> 00:07:15.839
I'm Dr.
00:07:15.920 --> 00:07:21.279
Kevin Hallow, co founder and chief medical officer of Clinician Core.
00:00:00.479 --> 00:00:03.200
It's 9 p.m., my phone rings.
00:00:03.439 --> 00:00:05.360
Instinctively, I pick it up.
00:00:06.320 --> 00:00:14.080
The nurse practitioner from the ER starts asking me about a patient with right lower quadrant abdominal pain.
00:00:14.640 --> 00:00:16.239
There's only one problem.
00:00:16.480 --> 00:00:17.839
I'm not on call.
00:00:18.079 --> 00:00:19.839
I switched my call day with Dr.
00:00:20.000 --> 00:00:20.640
King.
00:00:20.960 --> 00:00:26.640
I don't know this patient, but even if I did, the on-call surgeon's job is to manage it.
00:00:26.879 --> 00:00:32.240
Ironically, I still answer because that's what we're trained to do: pick up the phone.
00:00:32.560 --> 00:00:35.280
But here's what no one tells you in residency.
00:00:35.520 --> 00:00:40.560
Being reachable and being available are not necessarily the same thing.
00:00:41.039 --> 00:00:47.759
One means your phone works, the other means you're the physician who's actually supposed to be taking this call.
00:00:48.960 --> 00:00:52.000
Too often in my career, I found out the hard way.
00:00:52.320 --> 00:00:56.159
Even this far into my practice, I still get roped in.
00:00:56.479 --> 00:01:04.159
The schedule can say one thing, and reality can say another, and the gap between them lands on whoever picks up that phone.
00:01:04.480 --> 00:01:07.760
Today, it just happened to be me.
00:01:08.719 --> 00:01:09.599
Welcome back.
00:01:09.760 --> 00:01:10.239
I'm Dr.
00:01:10.319 --> 00:01:15.040
Kevin Hallow, co-founder and chief medical officer of Clinician Corps.
00:01:15.280 --> 00:01:20.640
Today I want to talk to you about something we all know too well, the call schedule.
00:01:21.040 --> 00:01:32.799
But today I want to focus on the difference between a static schedule and a smart schedule, and why the former fuels burnout and the latter leaves it.
00:01:33.280 --> 00:01:45.280
Unfortunately, we've all been there and know too well that if you're fresh out of training, you are the most likely person in your group to get a misrouted call.
00:01:45.599 --> 00:01:48.319
It's not because anyone is targeting you.
00:01:49.040 --> 00:01:52.239
Maybe it's just because they want to give you a sympathy consult.
00:01:52.480 --> 00:02:04.640
But really, more likely, you're new to the rotation, you don't have the standing to question a schedule, and you've not built the workarounds that senior partners have developed over the years.
00:02:06.079 --> 00:02:11.759
Physician work weeks are running pretty close to 58 hours on average.
00:02:12.000 --> 00:02:16.879
And a meaningful chunk of that is pure administrative drag.
00:02:17.439 --> 00:02:22.240
A late night call for coverage that isn't yours is not just annoying.
00:02:22.400 --> 00:02:26.080
It's a withdrawal from an account that's already overdrawn.
00:02:26.240 --> 00:02:29.280
You're tired, but now you can't go back to sleep.
00:02:29.439 --> 00:02:32.560
It's an energy drain that just burns you out.
00:02:33.199 --> 00:02:38.400
When it happens to you, it's not a sign you are bad at managing call.
00:02:38.960 --> 00:02:49.360
If your group's routing runs off a static list, a swap that you made yesterday might not register until the call schedule coordinator processes it.
00:02:49.680 --> 00:02:51.360
Who knows when that might be?
00:02:51.599 --> 00:02:53.520
You did nothing wrong.
00:02:53.840 --> 00:02:58.080
The schedule was just behind reality, once again.
00:02:59.120 --> 00:03:02.560
A static scheduling system does not ask questions.
00:03:02.719 --> 00:03:06.080
It simply lists who the person is to contact.
00:03:06.240 --> 00:03:09.360
Whether that is right or wrong does not matter to that system.
00:03:09.759 --> 00:03:13.840
It's just a name on a calendar day that fills a checkbox.
00:03:14.159 --> 00:03:19.199
On the other hand, a schedule aware system asks questions.
00:03:19.360 --> 00:03:25.840
For example, who is actually on call right now for this coverage area at this moment?
00:03:26.639 --> 00:03:34.639
The difference between those two systems is the difference between another night of harassment and a good night's sleep.
00:03:35.599 --> 00:03:42.240
So ask your practice manager this today, not after it costs you another bad night.
00:03:42.879 --> 00:03:51.360
When I swap a call with a colleague, how fast does that change actually show up on our static call schedule?
00:03:51.680 --> 00:03:57.919
What happens if the person who is supposed to make that change is out of the office or not available?
00:03:58.159 --> 00:04:01.360
How do I know that the change has been made?
00:04:01.759 --> 00:04:14.400
If the answer is that the change is not automatic and instantaneous, then that just represents another phone call that will go to the wrong person at the wrong time.
00:04:14.719 --> 00:04:17.279
And that includes you.
00:04:18.480 --> 00:04:25.759
If you want to know the real energy drain of a static call schedule, try this exercise.
00:04:26.800 --> 00:04:42.959
First, go back and confirm all of your scheduled days on the call schedule, including those swaps that you've made, and see how long it takes you to jump through all of those hoops.
00:04:43.600 --> 00:04:55.360
Next, make a mental note of how much time it takes you to recheck and reconfirm the call schedule weekly, especially when you make a last-minute swap.
00:04:56.800 --> 00:05:01.920
Then think about how many times the wrong call went to you.
00:05:02.560 --> 00:05:10.160
Does your static call schedule scheduling system really work or is it hit and miss?
00:05:11.120 --> 00:05:16.560
How often does your static schedule get this call schedule wrong?
00:05:17.040 --> 00:05:20.639
Finally, add it all up and track the pattern.
00:05:21.439 --> 00:05:27.519
If you're catching coverage that isn't yours more than once, that's not noise.
00:05:28.000 --> 00:05:34.160
That's a signal worth naming out loud to your group and to your practice manager.
00:05:34.800 --> 00:05:43.839
The difference between reachable and available all depends upon a name, on a date, on a calendar.
00:05:44.160 --> 00:05:54.800
However, that difference also defines a very important boundary that marks an enjoyable practice from an unpleasant one.
00:05:55.360 --> 00:05:59.279
Enjoyable practices are sustainable for an entire career.
00:05:59.920 --> 00:06:06.399
Unpleasant practices just lead to more burnout and an early end of that career.
00:06:07.360 --> 00:06:10.959
Static scheduling systems do not ask questions.
00:06:11.199 --> 00:06:15.920
They just represent another box that was checked by someone.
00:06:16.720 --> 00:06:30.800
Take a moment and ask the people who run your schedule if the system knows who's actually on call, or just who's on call the last time someone remembered to update a list.
00:06:32.480 --> 00:06:36.879
The difference is way too important to ignore anymore.
00:06:38.079 --> 00:06:42.079
Okay, that's it for today's video podcast.
00:06:42.319 --> 00:06:54.480
Don't forget to check out our website, cliniciancore.com, to learn about on-call scheduled aware routing, as well as the many other features that Clinician Core provides.
00:06:54.800 --> 00:07:02.720
While you're there, sign up for our wait list to take part in our soft launch and our upcoming release.
00:07:03.279 --> 00:07:11.439
You can also follow us on LinkedIn, YouTube, Spotify, Instagram, Facebook, and Reddit.
00:07:11.759 --> 00:07:14.160
There's no excuse not to check out Clinici.
00:07:15.199 --> 00:07:15.839
I'm Dr.
00:07:15.920 --> 00:07:21.279
Kevin Hallow, co founder and chief medical officer of Clinician Core.
