Transcript:
0:0:0.0 –> 0:0:5.960
Jordan Cooper
We are here today with Doctor Mark Weissman, the CIO and CMO of Title Health. Mark.
0:0:5.970 –> 0:0:7.110
Jordan Cooper
Thank you so much for joining us today.
0:0:7.680 –> 0:0:8.450
Mark Weisman
Hey, thanks, John.
0:0:8.460 –> 0:0:9.580
Mark Weisman
Appreciate you having me on.
0:0:10.70 –> 0:0:10.580
Jordan Cooper
Yeah.
0:0:10.590 –> 0:0:16.600
Jordan Cooper
So for those of you don’t know, uh, Title health is A2 hospital health system, based in Salisbury, MD.
0:0:16.610 –> 0:0:22.260
Jordan Cooper
Maryland on the Delmarva Peninsula, with about 360 beds and 800 providers.
0:0:22.890 –> 0:0:26.440
Jordan Cooper
So, Mark, what I’d like to do, you’re doing some interesting stuff there.
0:0:26.620 –> 0:0:33.780
Jordan Cooper
One of the things that we discussed earlier was how Title Health is using data to improve ambulatory operations.
0:0:33.790 –> 0:0:37.960
Jordan Cooper
Specifically, you mentioned that you’re creating scorecards for providers and executives.
0:0:38.120 –> 0:0:42.400
Jordan Cooper
You tell me more about why you did that, how you’re doing it with the outcomes of doing that have been.
0:0:43.420 –> 0:0:43.830
Mark Weisman
Sure.
0:0:43.840 –> 0:0:51.980
Mark Weisman
So there was a little bit of a shake up in the organization and my boss, who’s the Chief Operating Officer, got put in charge of the Medical Group.
0:0:52.370 –> 0:1:1.500
Mark Weisman
And so all of a sudden I had a very vested interest in making sure the Medical Group is successful and they have tremendous needs, particularly data needs.
0:1:1.730 –> 0:1:7.80
Mark Weisman
And they’re they’re very chaotic beasts, medical groups, they’re just always all of them.
0:1:7.290 –> 0:1:9.290
Mark Weisman
And I don’t think ours is any different than any others.
0:1:9.300 –> 0:1:22.770
Mark Weisman
They just, they’re constantly growing and building and adding providers and providers are coming and going, but they’re not always very data driven and that was something that the CEO and I wanted to fix.
0:1:22.780 –> 0:1:29.840
Mark Weisman
We wanted to make it better and so one of her struggles was trying to get provider engagement.
0:1:29.990 –> 0:1:47.50
Mark Weisman
And so she felt if we could put a scorecard together for the providers that they could see what is the the the number of visits they’re seeing their work RVU’s the the referral patterns, the work RV used of divided by the number of visits.
0:1:47.60 –> 0:1:54.280
Mark Weisman
Visits get an idea about how how well their how sick the patients are and so.
0:1:56.280 –> 0:2:0.30
Mark Weisman
He developed a scorecard and we started one at a time.
0:2:0.280 –> 0:2:4.950
Mark Weisman
The informatics team met with providers and we started with primary care.
0:2:4.960 –> 0:2:12.610
Mark Weisman
We haven’t gotten to all specialty yet, but with primary care, we’re rolling that out and it does take some hand holding it.
0:2:12.690 –> 0:2:13.800
Mark Weisman
There is some resistance.
0:2:13.810 –> 0:2:23.600
Mark Weisman
There is the typical denial, and then eventually you move through the stages of grief and you get to acceptance and they go, OK, they they they kind of dive into the data.
0:2:24.70 –> 0:2:25.720
Mark Weisman
They’ve also been very helpful.
0:2:25.790 –> 0:2:36.600
Mark Weisman
There’s a couple providers who will engage and then that’s a home run because they’re they want to get into the data and understand it, and then they’re going to help tell us, hey, did you know that your data is showing X?
0:2:36.690 –> 0:2:40.350
Mark Weisman
And and we really weren’t trying to show it that way and we would go and make changes.
0:2:41.250 –> 0:2:43.560
Jordan Cooper
What are some of the desired outcomes?
0:2:43.570 –> 0:2:45.360
Jordan Cooper
Specifically that X.
0:2:45.370 –> 0:2:50.710
Jordan Cooper
You know what’s an intervention and a result of that intervention because it’s nice to know, OK, this is my visit.
0:2:50.720 –> 0:2:55.940
Jordan Cooper
Count my relative value units, but what sort of are you the interventions?
0:2:55.950 –> 0:2:59.440
Jordan Cooper
How do you improve outcomes, improve reimbursement rates?
0:2:59.640 –> 0:3:4.490
Jordan Cooper
What actually was the desired end goal and how has that measured up in practice?
0:3:5.760 –> 0:3:6.250
Mark Weisman
Great question.
0:3:7.540 –> 0:3:18.740
Mark Weisman
The first desire was simply getting provider engagement and having them look at data and then asking questions like OK, well, what else can you get at?
0:3:18.750 –> 0:3:37.60
Mark Weisman
So we did start with operational metrics, but we’re now building the quality score card and so they know, OK, you could show me how many diabetics I have and what their last hemoglobin A1C is and how many have not had a hemoglobin A1C and now we can start to drive performance improvement through with doctors.
0:3:37.70 –> 0:3:38.590
Mark Weisman
You shine a spotlight on the problem.
0:3:38.600 –> 0:3:39.70
Mark Weisman
They’ll go.
0:3:39.80 –> 0:3:41.840
Mark Weisman
Oh, OK yeah, I’m different than my peers.
0:3:41.990 –> 0:3:43.50
Mark Weisman
They don’t like that.
0:3:43.130 –> 0:3:45.170
Mark Weisman
So I won’t be better than my peers.
0:3:45.180 –> 0:3:54.140
Mark Weisman
And so they they as a doctor myself, I can tell you we we respond to data when it’s put in front of us in a digestible easy format.
0:3:54.660 –> 0:4:8.760
Mark Weisman
And we we also found that we wanted providers to understand the the billing that we weren’t giving them any feedback about their work RVU’s or codes that were denied.
0:4:9.210 –> 0:4:11.60
Mark Weisman
They just were going about their day.
0:4:11.70 –> 0:4:15.450
Mark Weisman
They’d fill out some codes, they go off into the recycle land and we never hear about it.
0:4:16.10 –> 0:4:20.740
Mark Weisman
So we’re starting to show that with the with the providers, they feel like they’re part of the team.
0:4:21.120 –> 0:4:28.340
Mark Weisman
They’re engaging on the benefits of seeing data and then giving suggestions and asking good questions.
0:4:28.450 –> 0:4:29.280
Mark Weisman
That’s what we wanted.
0:4:29.290 –> 0:4:30.100
Mark Weisman
That was the main outcome.
0:4:30.610 –> 0:4:40.80
Jordan Cooper
So I love that you’re talking about data driven provider engagement and you actually have a piece of data I wanna share right now with our listening audience.
0:4:40.910 –> 0:4:42.360
Jordan Cooper
That is very interesting.
0:4:42.490 –> 0:4:53.400
Jordan Cooper
So everybody knows that every by every, every healthcare IT conference, everyone talked about provider burnout and alert fatigue in particular.
0:4:53.640 –> 0:5:8.360
Jordan Cooper
And I’m very interested in your efforts to tidal health to improve provider and staff efficiency by reducing alerts through a targeting efforts which has led to a best practice advisory acceptance rate of 40% which is very high.
0:5:8.520 –> 0:5:8.780
Jordan Cooper
Yeah.
0:5:9.660 –> 0:5:10.910
Jordan Cooper
How did you go about?
0:5:11.610 –> 0:5:29.170
Jordan Cooper
Uh, improving engagement, reducing the number of irrelevant alerts and you just mentioned, if we have these scorecards and we have the diabetics and these ones, you know you’re seeing 5 today who are diabetic and have not yet having anyone see, then there should be a BPA that fires.
0:5:29.180 –> 0:5:31.570
Jordan Cooper
It says for these guys you need to order that test.
0:5:31.720 –> 0:5:39.710
Jordan Cooper
You know, how did you develop a alerts in real time that have that providers have been responsive to it?
0:5:41.250 –> 0:5:47.140
Mark Weisman
Arrived in 2018 at this health system and they had gone live with epic about a year beforehand.
0:5:47.650 –> 0:5:51.600
Mark Weisman
And they took a lot of out of the box stuff and and turned it on.
0:5:51.610 –> 0:6:0.420
Mark Weisman
And some epic analysts might have said, yeah, you, you should have this alert and it wasn’t necessarily a quality driven initiative.
0:6:0.650 –> 0:6:1.260
Mark Weisman
It was.
0:6:1.270 –> 0:6:2.620
Mark Weisman
This sounds like a good idea.
0:6:2.630 –> 0:6:24.250
Mark Weisman
Bouncing around with some people and then it went and they we kind of sustained that for for a couple of years and the next thing you know, when you start looking at the reports and OK, we’re firing hundreds of thousands of alerts a month and we’re not getting 100 and hundreds of thousands of dollars of of of of value out of this, we’re not saving lives by hundreds of thousands.
0:6:24.260 –> 0:6:30.690
Mark Weisman
It’s it was a lot of noise and so we went through and started #1 just improving the targeting.
0:6:30.980 –> 0:6:36.470
Mark Weisman
The alert that’s meant to hit the doctor doesn’t need to hit the nurse, and the one that’s meant for the nurse doesn’t need to hit the doctor.
0:6:36.740 –> 0:6:41.880
Mark Weisman
So that’s just like basic clinical decision support 101, that was we we didn’t have that.
0:6:43.300 –> 0:6:57.340
Mark Weisman
We then challenged why we had many of these alerts and so do we really need a alert to hit the doctor to say, hey, the hemoglobin A1C hasn’t been drawn, can’t the medical assistant order that and tee it up for the doctor?
0:6:57.350 –> 0:6:58.410
Mark Weisman
The doctor just signs it.
0:6:58.420 –> 0:6:59.370
Mark Weisman
Absolutely.
0:6:59.660 –> 0:7:17.290
Mark Weisman
There were many things we found that it’s not the Doctor Who needs the alert and get people to work at top of license and we were very successful at reducing the number of alerts that are hitting the doctors and particularly with medication alerts on.
0:7:17.300 –> 0:7:26.550
Mark Weisman
This was a little controversial, so I’m seeing iOS and CIOs wouldn’t do this, but we let the doctors choose whether to turn on or off an alert.
0:7:27.60 –> 0:7:30.70
Mark Weisman
And very few actually turned them off.
0:7:30.140 –> 0:7:33.830
Mark Weisman
But they felt better knowing they had the ability to and that is.
0:7:40.0 –> 0:7:40.170
Jordan Cooper
Or.
0:7:33.840 –> 0:7:41.150
Mark Weisman
There are times where, due to their experience and their specialty and you’re training, but that’ll alert doesn’t add value to them.
0:7:41.160 –> 0:7:44.760
Mark Weisman
They know what they’re doing and they always use these two ticular drugs.
0:7:45.70 –> 0:7:53.180
Mark Weisman
I think as I always give the example of aspirin and Plavix and a heart patient and the cardiologist prescribing it, they use that every day.
0:7:53.370 –> 0:7:56.340
Mark Weisman
They don’t need an alert saying that that increases the risk of bleeding.
0:7:56.550 –> 0:7:57.210
Mark Weisman
They know that.
0:7:58.160 –> 0:8:5.140
Mark Weisman
So we got rid of those lower level medication interaction alerts or let the doctor say you know what, I got it.
0:8:5.190 –> 0:8:8.320
Mark Weisman
I can shut that one off myself and put the power in their hands.
0:8:8.330 –> 0:8:11.460
Mark Weisman
And they love that and power that led to two things.
0:8:11.470 –> 0:8:12.500
Mark Weisman
One is less alerts.
0:8:13.30 –> 0:8:20.840
Mark Weisman
The number 2 is our class scores the the the measurement of how well providers like their their EHR.
0:8:20.850 –> 0:8:27.800
Mark Weisman
We went from lowest, you know, the 18th percentile up to the 88th percentile over 18 months.
0:8:28.610 –> 0:8:38.460
Mark Weisman
And so a lot of that was giving the providers power and getting their engagements around IT initiatives and they responded.
0:8:40.220 –> 0:8:40.830
Jordan Cooper
Excellent.
0:8:40.840 –> 0:8:44.330
Jordan Cooper
I appreciate your story about provider engagement.
0:8:44.340 –> 0:8:49.910
Jordan Cooper
I love that we began with data driven scorecards and then and to enhance provider engagement.
0:8:49.920 –> 0:8:54.880
Jordan Cooper
And then you actually went out and you engaged providers and saw positive outcomes.
0:8:54.890 –> 0:8:58.650
Jordan Cooper
As a result, I’d like to transition to engaging patients.
0:9:0.120 –> 0:9:7.990
Jordan Cooper
You have improved the first call resolution rate and reduced call abandonment rate at your service desk.
0:9:8.80 –> 0:9:18.290
Jordan Cooper
So when patients call in you, they have a question they want something to be addressed and get it, allowing them to get through, improve satisfaction and engagement.
0:9:18.300 –> 0:9:20.670
Jordan Cooper
So we’ve already discussed provider engagement.
0:9:20.760 –> 0:9:22.650
Jordan Cooper
Let’s shift the story now to patient engagement.
0:9:32.430 –> 0:9:32.600
Jordan Cooper
Yeah.
0:9:24.270 –> 0:9:33.220
Mark Weisman
The scenario that you’re describing is typically around my chart issues where patients stuck and they’re calling our service because they don’t know how to get unstuck.
0:9:33.510 –> 0:9:36.910
Mark Weisman
And so in the service desk is busy.
0:9:36.920 –> 0:9:44.760
Mark Weisman
They’re getting lots of calls every day from all over the health system internal as well as from patients calling it, having problems with the patient portal.
0:9:45.200 –> 0:9:45.500
Jordan Cooper
Umm.
0:9:46.250 –> 0:9:47.720
Mark Weisman
We did a couple of things.
0:9:47.730 –> 0:9:54.370
Mark Weisman
Number one, we made it so that the the patient portal provided great information.
0:9:54.680 –> 0:9:55.890
Mark Weisman
Everything’s open, open book.
0:9:55.900 –> 0:9:56.290
Mark Weisman
Book.
0:9:56.520 –> 0:10:6.780
Mark Weisman
We did that before the law required, so our patients started to engage and get into the portal and use it because they’re adoption helps decrease the the problems they get in it.
0:10:6.790 –> 0:10:9.490
Mark Weisman
They start using this the first time users who tend to call and go.
0:10:9.500 –> 0:10:10.840
Mark Weisman
I don’t know what to do next.
0:10:11.980 –> 0:10:27.50
Mark Weisman
We did take some steps to help improve my chart adoption and utilization at the practice level and that helped, like if our service doesn’t answer the phones that that’s bad, that’s a problem.
0:10:27.340 –> 0:10:27.790
Jordan Cooper
Umm.
0:10:27.480 –> 0:10:35.270
Mark Weisman
And one of the things that we did was empowered them with knowledge to answer the questions and answer them quickly.
0:10:35.340 –> 0:10:44.70
Mark Weisman
So we built a knowledge base and now they’re bringing up that knowledge base in real time and able to answer patient questions as well as the internal questions.
0:10:44.80 –> 0:10:49.790
Mark Weisman
So they can they can move through quicker before our service desk was a bunch of ticket takers.
0:10:50.20 –> 0:10:50.680
Mark Weisman
That’s what they did.
0:10:50.690 –> 0:10:53.0
Mark Weisman
They would take a ticket and pass it to someone else.
0:10:53.800 –> 0:10:57.770
Mark Weisman
Well, that that didn’t really feel good to patients when they couldn’t get their problem solved.
0:10:57.780 –> 0:10:59.570
Mark Weisman
They wanted whatever they’re going in there to do.
0:10:59.580 –> 0:11:2.680
Mark Weisman
Maybe the schedule an appointment, so they wanted to do it.
0:11:2.690 –> 0:11:26.360
Mark Weisman
Now they want to do it when someone else got around to it, so being able to solve their problems, and now we’re we’re actually close to 65% first call resolution rate and you know we started somewhere around 5% for school resolution rate, so dramatically transforming our service desk gives our employees a better just feel for the for the organization as well as our patients.
0:11:27.390 –> 0:11:35.140
Jordan Cooper
So just really quickly before we move to another topic, you said you helped build the knowledge base among those at the service desk.
0:11:35.210 –> 0:11:39.480
Jordan Cooper
Do you have any concrete processes for how you were able to do that?
0:11:39.490 –> 0:11:44.80
Jordan Cooper
Was it just exposing a digital library or how did you build the knowledge base?
0:11:44.400 –> 0:11:46.720
Mark Weisman
We have to build the digital library right?
0:11:46.730 –> 0:11:52.290
Mark Weisman
Because what we did is we were looking at the calls that were coming in and try to getting a feel for, OK, what’s the number?
0:11:52.300 –> 0:11:59.890
Mark Weisman
1/2 top ten calls that are coming in, but we want it to be bigger than that and not just handle the top ten calls.
0:12:0.60 –> 0:12:12.890
Mark Weisman
So we started to get with the analysts and we asked them what do you think like, what are the common things that you think are being I’m being asked and they helped create the knowledge base.
0:12:13.60 –> 0:12:15.650
Mark Weisman
We made it an IT initiative.
0:12:20.310 –> 0:12:22.240
Jordan Cooper
That it’s.
0:12:15.720 –> 0:12:38.930
Mark Weisman
Everyone in IT rallied around this and everyone is committed to that first call resolution rate being over 50% is now we’re at 55% as a system goal and they they engaged, they felt ownership of that problem of they don’t know how to answer the questions and we we show this at our monthly meeting.
0:12:38.990 –> 0:12:40.350
Mark Weisman
We show it in our newsletters.
0:12:40.360 –> 0:12:41.710
Mark Weisman
It’s we talk about it.
0:12:41.720 –> 0:12:49.340
Mark Weisman
We put the data in front of the IT team and the managers when they see you starting to drop though OK, what are we missing?
0:12:49.350 –> 0:12:50.770
Mark Weisman
Let’s get back engaged.
0:12:51.100 –> 0:12:52.960
Mark Weisman
So the whole teams rallying around this.
0:12:53.300 –> 0:13:0.500
Jordan Cooper
And just in case any listeners are very interested in replicating this effort to build knowledge based on a drill in for one moment more.
0:13:2.840 –> 0:13:3.630
Jordan Cooper
What?
0:13:3.720 –> 0:13:13.790
Jordan Cooper
Like, how would you quantify the resources and timeline between the idea to build this digital library and it actually going live and being used in the in the service desk?
0:13:16.180 –> 0:13:21.950
Mark Weisman
So we’re just using plain old SharePoint right now, so nothing particularly fancy for storage of those knowledge base articles.
0:13:21.960 –> 0:13:34.60
Mark Weisman
We are excited to start adding a service management tool that will have a bot that will service it up to the to the technician as they’re talking to someone, but we’re not there yet.
0:13:35.930 –> 0:13:36.170
Jordan Cooper
OK.
0:13:34.70 –> 0:13:39.960
Mark Weisman
But but that the knowledge base probably took us six months to get to where we really felt sort of good about it.
0:13:39.970 –> 0:13:41.410
Mark Weisman
But it’s an ongoing process.
0:13:41.520 –> 0:13:41.800
Jordan Cooper
Right.
0:13:41.540 –> 0:13:53.250
Mark Weisman
So over the last two years, we continue to build that knowledge base #1 our technology changes and #2 the questions change from the consumers of our information.
0:13:53.260 –> 0:13:54.630
Mark Weisman
So we’re always updating.
0:13:55.310 –> 0:14:6.330
Jordan Cooper
So on the same topic of engaging patients and veering into the land of artificial intelligence, which is the hot topic of the day, I’d like to discuss the impact of bots talking to bots.
0:14:6.340 –> 0:14:18.380
Jordan Cooper
In particular, I’d like to know what happens when a patient’s personal bot starts talking to tidal health hospital scheduling by or where clinical quality control metrics come into the discussion when bots are talking to each other.
0:14:19.670 –> 0:14:26.100
Mark Weisman
This was a wonderful topic that we started to touch on at the Gartner conference with CIO’s and started a bat this around a little bit.
0:14:26.110 –> 0:14:28.70
Mark Weisman
It was fascinating to think.
0:14:28.130 –> 0:14:34.480
Mark Weisman
All right, pretty soon I’ll just tell Siri or Alexa or whatever it is, schedule my primary care appointment.
0:14:34.490 –> 0:14:37.360
Mark Weisman
It goes off and it will do that and it’ll talk.
0:14:37.430 –> 0:14:44.580
Mark Weisman
But we’re gonna have bots and the health system side that when patients call that they they’re talking to a box schedule their appointment.
0:14:44.910 –> 0:14:56.110
Mark Weisman
So what happens if bots are talking to bots so #1 the interface could be different, so do I need the big buttons that patients need to press for schedule now but don’t care?
0:14:56.120 –> 0:14:59.600
Mark Weisman
You know it, it just needs a good API and it can connect and execute.
0:14:59.610 –> 0:15:7.780
Mark Weisman
So it’s a different interface which I thought was fascinating, that we need to create that pathway, to make it easy for bots to schedule.
0:15:7.790 –> 0:15:9.640
Mark Weisman
We want people to schedule only come see us.
0:15:9.650 –> 0:15:10.460
Mark Weisman
That’s why we’re here.
0:15:10.740 –> 0:15:10.960
Jordan Cooper
Here.
0:15:11.140 –> 0:15:23.30
Mark Weisman
So we need to make it easy, and if we’re constantly changing where our buttons are and our website when the box are having a hard time understanding where to go, we’re putting paint into the system where we don’t want that pain.
0:15:23.40 –> 0:15:24.70
Mark Weisman
We wanna make it easy.
0:15:24.80 –> 0:15:28.70
Mark Weisman
We wanna make it more API based and not based on screen scraping.
0:15:28.420 –> 0:15:33.120
Mark Weisman
So where there’s that tendency of we move things around on the screen and now the bot gets confused.
0:15:34.20 –> 0:15:35.420
Mark Weisman
Umm the.
0:15:37.370 –> 0:15:42.800
Mark Weisman
The other interesting question that that we started to raise what happens when bots are talking to boxes?
0:15:42.970 –> 0:15:45.520
Mark Weisman
That quality piece is not there.
0:15:45.530 –> 0:15:47.220
Mark Weisman
No one’s talking about your clinical quality.
0:15:47.230 –> 0:15:54.300
Mark Weisman
No ones going to your website and looking at hey, you know, we do really well with gastric bypass surgery, you should come to us.
0:15:55.390 –> 0:15:58.870
Mark Weisman
That conversation is not happening when it’s boxed.
0:15:58.880 –> 0:16:5.360
Mark Weisman
Talking to bots, so as a doctor, as a CIO, as a CMIO, I’m trying to think about.
0:16:5.370 –> 0:16:23.780
Mark Weisman
No, I want patients to pick their provider based on good outcome metrics, which requires us to put those metrics publicly facing and we don’t do that as a here system across our country or lousy at that, try to figure out how good your surgeon is.
0:16:23.790 –> 0:16:34.110
Mark Weisman
Good luck if this information you cannot find easily, but we have to and we have to put it in there such that when someone asks a question, he scheduled me an appointment.
0:16:34.340 –> 0:16:35.830
Mark Weisman
That Siri’s gonna ask.
0:16:36.0 –> 0:16:45.190
Mark Weisman
Do you want the best doctor based on quality or number of Google Stars or something about quality, not just first available?
0:16:45.340 –> 0:16:47.150
Mark Weisman
Do you really want the first available doctor?
0:16:47.160 –> 0:16:47.470
Mark Weisman
Maybe.
0:16:47.480 –> 0:16:48.150
Mark Weisman
Maybe you do.
0:16:48.160 –> 0:16:50.430
Mark Weisman
Maybe that’s what awesome if someone got Open Access.
0:16:50.760 –> 0:16:56.530
Mark Weisman
Or maybe they’re really not the great doctor, and no one wants to see them, and that’s why they have lots of appointments available.
0:16:57.270 –> 0:17:6.290
Mark Weisman
So we we want a better experience for the patient when they arrive and box talking to bots creates a new dynamic that CIO have to think about.
0:17:7.90 –> 0:17:16.880
Jordan Cooper
I appreciate what you’ve done with bots talking to bots, certainly figuring out how AI fits in the healthcare arena is something that’s top of mind for many of our listeners.
0:17:17.170 –> 0:17:27.440
Jordan Cooper
We are approaching the end of this podcast episode and as I reflect on our conversation, I hear basically a theme that more transparency is good.
0:17:27.590 –> 0:17:32.560
Jordan Cooper
Exposed data on provider performance and on visits and referral patterns.
0:17:32.570 –> 0:17:36.930
Jordan Cooper
Provider metrics 2 providers and scorecards that leads to improved engagement.
0:17:37.410 –> 0:17:37.750
Jordan Cooper
Uh.
0:17:38.130 –> 0:18:10.930
Jordan Cooper
Go provide increased engagement and and knowledge and power about how billing codes are being affected by provider behavior and how best practice advisories can be managed in that improves provider engagement in the EHR and enable patients or even bots to get exactly the information they want as quickly as possible and as simply as possible in order to improve the experience is also something that I’ve I’ve I’ve heard you talk about.
0:18:10.940 –> 0:18:12.800
Jordan Cooper
So I’d like to open the floor to you now.
0:18:12.810 –> 0:18:23.400
Jordan Cooper
Are there any closing thoughts you’d like to add to our listeners about this theme of improving transparency and access to data at Title Health in order to improve engagement and outcomes?
0:18:24.750 –> 0:18:25.540
Mark Weisman
It’s not easy.
0:18:25.910 –> 0:18:30.610
Mark Weisman
All CIO’s know that finance might not want the providers to know their work.
0:18:30.620 –> 0:18:31.10
Mark Weisman
Our views.
0:18:31.20 –> 0:18:43.900
Mark Weisman
I can’t imagine why that, but that that battle it has to happen to say, look, we’re gonna get great outcomes from this trusted try a small pilot getting that data out of the silos.
0:18:43.910 –> 0:18:49.990
Mark Weisman
So if it lives in an Excel spreadsheet on some financial analyst desk, that’s not gonna be useful.
0:18:50.0 –> 0:18:57.820
Mark Weisman
So the CIO has great opportunity to bring the data together into a place where others can see it and digest it and use it.
0:18:58.140 –> 0:19:3.550
Mark Weisman
Those are things to see iOS and CMM iOS can take a very central role on and just get started.
0:19:3.640 –> 0:19:8.390
Mark Weisman
Just pick something and start to drive on it and just watch the magic start to happen.
0:19:8.440 –> 0:19:11.290
Mark Weisman
It is a long process.
0:19:11.300 –> 0:19:14.370
Mark Weisman
It would be wonderful to wave the magic wand, and I like that I’m a wave.
0:19:14.380 –> 0:19:15.70
Mark Weisman
The magic wand.
0:19:15.80 –> 0:19:15.650
Mark Weisman
Kind of person.
0:19:18.20 –> 0:19:18.230
Jordan Cooper
Yes.
0:19:15.660 –> 0:19:22.170
Mark Weisman
It just happens this takes a lot of effort, a lot of commitment and a lot of partnership.
0:19:25.610 –> 0:19:25.950
Jordan Cooper
1st.
0:19:22.260 –> 0:19:30.860
Mark Weisman
So as all CIO know, it’s about the relationships and you’re gonna be successful or unsuccessful with most of your initiatives based upon the relationships you’ve made.
0:19:32.60 –> 0:19:40.310
Jordan Cooper
For our listeners, this has been Doctor Mark Weisman, the CIO and CMIO of tidal health in the Delmarva Peninsula, based in Salisbury, MD.
0:19:40.540 –> 0:19:41.910
Jordan Cooper
Mark, thanks so much for joining us today.
0:19:42.630 –> 0:19:43.130
Mark Weisman
Thanks Jordan.