Latest / The MaineHealth Podcast / WTKE: From Data to Decisions -- Launching MaineHealth’s Enterprise Intelligence Team
Transcript
- 0:09Hello, and welcome to Working Together with Kelly Elkins. I'm your host,
- 0:13Kelly Elkins, your Chief Operating Officer for MaineHealth.
- 0:16In this podcast series, I will be joined each episode by guests who are participating
- 0:21on teams focused on how we can support and enhance how we work together across MaineHealth
- 0:26so that we can achieve our vision of working together so that our communities
- 0:30are the healthiest in America.
- 0:32In particular, we will highlight work we are doing in further development of
- 0:36our operating model for Maine Health and how we are creating structure and processes
- 0:40that make it easier for you to do your work.
- 0:43Today's episode is titled, From Data to Decisions, Launching MaineHealth's
- 0:48Enterprise Intelligence Team.
- 0:50At MaineHealth, we talk often about creating a more connected,
- 0:53coordinated, and sustainable health system.
- 0:56Whether we're improving access, advancing quality, reducing the total cost of
- 1:00care, or supporting our care teams, One thing has become increasingly clear
- 1:05The decisions we make are only as good as the information we have available to us,
- 1:10That's why I'm excited today to talk about the launch of MaineHealth's Enterprise Intelligence Team.
- 1:15This effort is about much more than data dashboards or reports.
- 1:19It's about creating a shared source of truth across our system and providing
- 1:23timely and actionable intelligence and helping leaders and frontline teams make
- 1:28better decisions every day.
- 1:30Today, we'll discuss why this team is being launched, what problems it's designed
- 1:34to solve, and how it will support care teams and leaders across the system,
- 1:39and what success will look like in the years ahead.
- 1:42To join me in the conversation today is my guest, Ali Russo,
- 1:45Vice President, Analytics for MaineHealth. Welcome to the podcast,
- 1:49Ali! Thank you, Kelly.
- 1:50All right, Ali. So, as we launch into the conversation, we've intentionally
- 1:56started using the term enterprise intelligence rather than simply analytics.
- 2:03What is the difference and why does that distinction matter?
- 2:07Analytics is really the information itself, right?
- 2:12Whereas enterprise intelligence is the ability to use that information and expand
- 2:18it across the organization so that we can make decisions and we can use the
- 2:23information to do things with it.
- 2:26Yeah, because I think that is, for us, when we talk about a differentiator,
- 2:30it's how do we move beyond just the reports, the figures we see.
- 2:36On the paper or on the screen, and really translate that more into intelligent
- 2:41insights, to your point.
- 2:43Exactly. So, and there's a big difference between a report and analytics, too.
- 2:49Well, maybe talk about that. What's the difference? So reports are that flat
- 2:53piece of reporting the news, being able to say, oh, and this trend went up,
- 2:58whereas analytics is being able to convey that why behind it.
- 3:02And it's a really important piece to understand the business enough to be able
- 3:06to explain what that why is to the stakeholders who are getting that information. Very good.
- 3:13So we're talking about enterprise intelligence. I opened with how we're really
- 3:17going to build a new team or a new way to do this.
- 3:21But maybe before we dig into that, let's step back a moment and say,
- 3:26you know, what challenges are we trying to solve for today that really led us
- 3:31to create this team and this direction?
- 3:35So there were a number of different challenges that I encountered hearing about
- 3:39when I started speaking to a lot of the different stakeholders across the organization.
- 3:44Between many different teams doing similar types of activities,
- 3:49nobody talking to each other within the teams,
- 3:52very much having duplicative reports that were pulling information from different
- 3:57places, so they were coming out with different answers,
- 4:01different definitions for the same exact words, so length of stay.
- 4:04Having a different definition depending on who you spoke with,
- 4:07as well as basically people were saying that they weren't getting the information that they needed.
- 4:16They may be getting reports, they may be getting a lot of different reports
- 4:19or a lot of different sound bites, but they weren't getting the critical information
- 4:25that they needed to run their business or their line or their service line,
- 4:29or to be able to convey that information and convert it into decisions.
- 4:36And, you know, I also want to maybe pull a little bit on the thread when you talked about.
- 4:41Teams, different people. Part of this is not just about creating the outcome,
- 4:47right? That intelligent analytics, those insights, and reducing that duplication.
- 4:54But it's also in how we're going to do it. And a big piece of that is bringing
- 4:59together a team that kind of has existed all over the place,
- 5:05right? And pulling that together.
- 5:07Talk a little bit about the team itself and kind of where we are today and what the future state is.
- 5:14So today we have a number of different teams that are doing analytics across the organization.
- 5:19And this particular team is going to encompass an enterprise intelligence hub,
- 5:23which is really going to set the standards.
- 5:26It's going to be the organization that really sets forth the governance for
- 5:31how we do things, as well as handle a number of the different analytics and
- 5:35analyses to disseminate this information so that the enterprise can make decisions.
- 5:40There will also be some spokes, which will remain where they live today,
- 5:45such as quality, finance, research, strategy, and business planning, as well as HR.
- 5:53And those spokes, though, are going to be much more integrated into the hub
- 5:57so that there will be a lot more communication, a lot more ability that they
- 6:03see what's going on in the hub, and the hub sees what's going on in the spokes.
- 6:07And that will also help to reduce a lot of the friction that we've heard of
- 6:12today, as well as a lot of the duplication and or different metrics being used
- 6:17and different data sets being used. Yeah.
- 6:20So when we have this team together, when we have both the hub team,
- 6:25kind of the enterprise intelligence team working with these other,
- 6:29pieces of the organization, what really are the benefits that our frontline
- 6:35and our leaders can expect from this work?
- 6:38And, well, I guess let me ask it a different, an assumption or something I know,
- 6:43which is this isn't just to support the executive team, right?
- 6:48It's really to support everyone. But what are the benefits?
- 6:51What can our care team members expect when this is fully in place?
- 6:56So I'm going to say glibly, one definition for length of stay.
- 7:01But also clear definitions for everything, right?
- 7:04Very, very clear and specific single sources of truth.
- 7:10Yeah. The ability for a better intake and triage process so that people don't
- 7:15feel like things kind of go into a black hole for as long as they might.
- 7:19Much more efficient group of individuals who hopefully will understand,
- 7:24really understand what the business is asking for, as opposed to constantly
- 7:29going back and saying, oh, is this right?
- 7:31Oh, no, okay, and taking it back. So, really being able to get a group of individuals
- 7:36who can listen to what the needs are, interpret what that information is,
- 7:41and then create not just the report.
- 7:44But the full analysis with an executive summary and an interpretation and a
- 7:50lot of the why behind everything to then transfer back to the individuals and
- 7:56the stakeholders who need it so that they can then,
- 7:59continue care, improve care, and do the things that they need to do.
- 8:03That's awesome. So you mentioned a little bit, which I think plays into my next
- 8:08question, which is around what are the capabilities needed or that this team
- 8:14will bring to the table and you've listed a few, but.
- 8:18What capabilities really will make up this team? Obviously, there's human resources.
- 8:24I'm sure there's some tech resources. So what are the capabilities that are
- 8:29going to be needed to make this successful?
- 8:31Looking at the vertical of the analytics themselves, I am a big believer that it's business first.
- 8:37The individuals on those teams are a business function. They're not a technical function.
- 8:42And largely, they're going to have to understand the business of what we do.
- 8:48So, for the healthcare side of things, understanding the ambulatory workflows,
- 8:53understanding what does access mean within the facility realm,
- 8:57understanding what is a DRG and how does that play into things.
- 9:02We're going to have a cross-domain group. So, being able to interpret value-based
- 9:06reimbursements and be able to incorporate that knowledge into the results and
- 9:10the analyses around them. Are they working? Are they not working?
- 9:15What are the ones that we should be in versus not? So really being able to not
- 9:21just craft a report, but hear what the problems are, ask what the individual
- 9:26and the stakeholders are trying to achieve,
- 9:28and then be able to put together the information that the stakeholders need
- 9:34to execute on what they're trying to achieve.
- 9:37I have to imagine another capability that...
- 9:40Is the ability or capability of having a lot of information and data,
- 9:48perhaps in a location that's easy for this high-powered team to access. Yes.
- 9:54So we are embarking on the data hub.
- 10:00Which we are already kind of well down the path of everything.
- 10:04It is going to be an AWS cloud environment where we're going to have all of
- 10:10our information up there. It's all going to be aggregated.
- 10:12We're going to have all of our systems
- 10:14all up there in its native form and ability, and we will connect it,
- 10:19behind the scenes and then put tools on top of it that have chatbots and things
- 10:24like that to allow people to interrogate the information that they're getting.
- 10:29Nice, nice. So some folks, I've heard it called many things.
- 10:34We're calling it a data hub. Some people you may have heard reference data houses,
- 10:39data lakes, lake houses.
- 10:41I've heard it all. So, you know, I know a lot of people, rightfully so,
- 10:45are aware of the fact that a lot of our data is sensitive information with patient identifiers, etc.
- 10:54Maybe just briefly, you know, this cloud and all of our data, I'm sure will be secure.
- 11:00But will everyone have access to any data they want? or how will we ensure that
- 11:07the right folks get access to the right level of data?
- 11:11So we're going to have role-based access. Okay, great. And many of the things
- 11:14that we're putting into place are data set access itself. So there might be
- 11:19certain data sets that are only accessible to certain individuals.
- 11:23What we're calling row level. So if you think of an Excel spreadsheet,
- 11:26right, there might be certain rows, maybe in our EPIC data, we might not be
- 11:31able to see our other employee conditions and things like that.
- 11:34So we might be pulling those out. We will have access at that level.
- 11:38And then thinking again as an Excel spreadsheet, columns, maybe you have social
- 11:42security numbers in there and the only people who can see that are HR.
- 11:45That would be a role-based access of security. Yeah.
- 11:48Excellent. Excellent. And I appreciate that our care team is so conscious of
- 11:54the security of our information.
- 11:57So the team's going to have these capabilities.
- 12:00They're going to be business oriented first, really supporting and enhancing
- 12:06no matter what the role is to folks to have better access to information,
- 12:10to make better decisions, best decisions, best decisions.
- 12:14I think to really use the information in the best possible way might require
- 12:21an element of literacy or education.
- 12:24So how are we thinking about that in this work?
- 12:28That's a great question. We actually have one of the roles is going to be a
- 12:31data literacy specialist.
- 12:34And that person is going to be able to help to craft the tools and tips and
- 12:40trainings for the care team members to be able to utilize the technology and
- 12:45the other things that we are going to be priding.
- 12:48Awesome. Okay, so we're going to educate folks.
- 12:51We're going to give them lots of tools, tricks. We're going to enhance technology.
- 12:55We've got this team of experts that'll be there to help make all their dreams
- 13:00come true with the analytics and intelligence information that's needed.
- 13:05If we could fast forward five years from now, from your perspective,
- 13:10what does success look like?
- 13:12Success looks like nobody having to ask and say that they don't have the information they need.
- 13:18But really and truly, it is a team, a care team, who can utilize the information
- 13:25that we are giving to them, that we have provided access to through self-service as well.
- 13:32And they have at their fingertips what they need to do their jobs,
- 13:38to make decisions, and to achieve what they need to achieve as well.
- 13:42That sounds amazing. I can't wait for that day. Now, that's five years from now.
- 13:48We're really just launching, you know, in a big way, as you said,
- 13:51some of the data hub stuff's underway, the team formation's starting to occur.
- 13:56What are some of the most important milestones, say, in the first 12 months
- 14:01of this effort that are going to be important?
- 14:03So big milestones are going to be having the footprint of the data hub up and
- 14:07running with at least 30 data sets and most of our critical data sets,
- 14:11so Epic, Info, Strata, et cetera, in that data hub.
- 14:15Connect it with a layer on top of it that allows the business users to be able
- 14:20to access the information through their own language.
- 14:23So not calling it a PAT underscore ID, but a patient identifier or something like that.
- 14:28As well as having all of the tooling in place so that people have it,
- 14:34are using it both internally for the analytics team to set things up,
- 14:39as well as externally for some of the analytics
- 14:41individuals to use from the front end.
- 14:44And then also having the team having a new intake triage method,
- 14:48having a lot of that together, having our governance in place in full scale
- 14:52so that everybody is able to know what are the different definitions of all
- 14:56the metrics that we're using. Yeah.
- 14:58Well, that sounds like a lot. How confident are you that we can achieve all
- 15:03of that in the next 12 months?
- 15:05So I, day 83, I think, and we have all of the software procured for the data hub.
- 15:13We have our infrastructure or it was kind of funny. I was talking to Adrian (Moran)
- 15:17earlier. He called it our quote unquote hardware set up for our infrastructure,
- 15:23even though it's up in the cloud.
- 15:25I'm fairly confident we're going to have what we need to have done because we
- 15:28are pushing ahead as fast as we can with quality.
- 15:32Yeah. But also in a very thoughtful and specific way to do this. Awesome.
- 15:38Well, it's definitely something that I hear about a lot. I've heard about a
- 15:43lot since I arrived at MaineHealth, you know, some years ago.
- 15:48And I'm just so excited that we have your leadership kind of guiding us and
- 15:53really taking us in this big next step to really democratize the data and information
- 16:01we have so that everyone has.
- 16:03The right level of access but can actually use it to help inform their work
- 16:08or how they make decisions and ultimately how we best care for our patients.
- 16:12So thank you so much for your leadership. Thanks for talking it through with
- 16:17the audience today and look forward to what comes next on this journey.
- 16:21Well, thank you for having me.
- 16:23Well, I hope that you found this episode informative and provides a deeper insight
- 16:27into one of our major areas of focus as we continue to enhance how we work together as MaineHealth
- 16:33to achieve our vision of working together so that our communities are the healthiest in America.
- 16:39If you have ideas for topics for
- 16:42future podcasts, please email those to workingtogether@mainhealth.org.
- 16:47Thank you and have a blessed day.