1 00:00:00,000 --> 00:00:02,159 Hi, everyone. This is Lucas Voss with Becker's 2 00:00:02,159 --> 00:00:03,919 Healthcare. Thanks so much for tuning in to 3 00:00:03,919 --> 00:00:06,240 the Becker's Healthcare podcast series. It's great to 4 00:00:06,240 --> 00:00:08,980 have you. Today, we're talking about how independent 5 00:00:09,039 --> 00:00:10,580 providers can turn insight 6 00:00:11,439 --> 00:00:13,679 into action. I'm so excited to be joined 7 00:00:13,679 --> 00:00:15,875 by Megan Zukruski. She's the vice president of 8 00:00:15,875 --> 00:00:17,675 product strategy at Veradigm. Megan, it's so great 9 00:00:17,675 --> 00:00:18,994 to have you. Thanks for being here. Thank 10 00:00:18,994 --> 00:00:20,994 you. I'm excited to be here. Yes. It's 11 00:00:20,994 --> 00:00:22,114 great to have you. I do wanna start 12 00:00:22,114 --> 00:00:23,795 off with introductions for those that might not 13 00:00:23,795 --> 00:00:25,394 know you yet. If you could just talk 14 00:00:25,394 --> 00:00:27,314 a little bit about who you are, your 15 00:00:27,314 --> 00:00:29,074 role in health care, and your job at 16 00:00:29,074 --> 00:00:32,189 Veradigm. Yeah. I work in platform strategy at 17 00:00:32,189 --> 00:00:32,689 Veradigm 18 00:00:33,070 --> 00:00:35,869 in a really unique position between payers and 19 00:00:35,869 --> 00:00:36,369 providers. 20 00:00:36,829 --> 00:00:38,509 So what I focus on today is making 21 00:00:38,509 --> 00:00:40,829 sure we have a collaborative platform that can 22 00:00:40,829 --> 00:00:43,755 help our independent provider network succeed and also 23 00:00:43,755 --> 00:00:45,914 help our payer clients get the things that 24 00:00:45,914 --> 00:00:48,414 they need back from those independent providers. 25 00:00:48,954 --> 00:00:50,954 It's been a really exciting time as the 26 00:00:50,954 --> 00:00:53,835 market really comes together and as both sides 27 00:00:53,835 --> 00:00:55,675 are really trying to problem solve and make 28 00:00:55,675 --> 00:00:57,869 sure that each is armed with the information 29 00:00:57,869 --> 00:00:59,649 they need about the patients that they have, 30 00:01:00,109 --> 00:01:02,210 combined. So it's just been a great, interesting 31 00:01:02,429 --> 00:01:04,590 area of health care to really dive into 32 00:01:04,590 --> 00:01:06,750 and and problem solve in. Yeah. We'll talk 33 00:01:06,750 --> 00:01:08,430 about some of the collaborative nature of this 34 00:01:08,430 --> 00:01:09,629 here in a little bit, which is so 35 00:01:09,629 --> 00:01:11,524 key as you've just mentioned. I do wanna 36 00:01:11,524 --> 00:01:12,325 talk about, 37 00:01:12,724 --> 00:01:14,564 perspective gap closure a little bit. I know 38 00:01:14,564 --> 00:01:15,625 it's fairly specific, 39 00:01:16,164 --> 00:01:18,084 but when we talk about perspective gap closure 40 00:01:18,084 --> 00:01:19,784 in today's value based care environment, 41 00:01:20,405 --> 00:01:22,424 can you explain what that means 42 00:01:22,804 --> 00:01:25,890 and then why it's becoming such an important 43 00:01:26,109 --> 00:01:27,010 lever specifically 44 00:01:28,189 --> 00:01:29,730 for independent providers? 45 00:01:30,350 --> 00:01:31,890 Yeah. For a long time, 46 00:01:32,350 --> 00:01:35,310 the delay of data transfer between payers and 47 00:01:35,310 --> 00:01:35,810 providers 48 00:01:36,430 --> 00:01:38,850 left payers operating very retrospectively. 49 00:01:39,230 --> 00:01:42,084 Right? So they're reviewing claims data that's six 50 00:01:42,084 --> 00:01:43,844 months or a year old and then trying 51 00:01:43,844 --> 00:01:46,164 to course correct after the fact, get that 52 00:01:46,164 --> 00:01:48,884 information back to providers maybe months or even 53 00:01:48,884 --> 00:01:50,805 a year after they've actually seen the patient 54 00:01:50,805 --> 00:01:52,884 face to face. So when we talk about 55 00:01:52,884 --> 00:01:54,024 prospective strategies, 56 00:01:54,409 --> 00:01:56,969 we're really looking to arm providers with the 57 00:01:56,969 --> 00:01:59,930 information they need that payers might know about. 58 00:01:59,930 --> 00:02:02,090 Right? Because payers have a good three sixty 59 00:02:02,090 --> 00:02:03,870 view of patients from a claims perspective. 60 00:02:04,490 --> 00:02:06,890 But we're talking about arming providers with that 61 00:02:06,890 --> 00:02:09,050 information while the patient's face to face with 62 00:02:09,050 --> 00:02:10,030 them in the room. 63 00:02:10,465 --> 00:02:12,704 We know that regulatory is really cracking down 64 00:02:12,704 --> 00:02:14,544 on things like this as well. We wanna 65 00:02:14,544 --> 00:02:16,164 make sure that the provider is 66 00:02:16,625 --> 00:02:18,465 armed with the right information at the right 67 00:02:18,465 --> 00:02:20,305 time in the right place, that they're capturing 68 00:02:20,305 --> 00:02:21,685 the right things in the record, 69 00:02:22,224 --> 00:02:24,305 and that needs to happen real time before 70 00:02:24,305 --> 00:02:25,989 the claim is submitted. So when we're talking 71 00:02:25,989 --> 00:02:26,729 about prospective, 72 00:02:27,269 --> 00:02:29,590 it's really making sure that the provider can 73 00:02:29,590 --> 00:02:32,169 act on the information that they have 74 00:02:32,469 --> 00:02:35,269 before the claim is submitted. And that way, 75 00:02:35,269 --> 00:02:37,030 we can make sure that, you know, gaps 76 00:02:37,030 --> 00:02:39,155 are closed and the patient is getting the 77 00:02:39,155 --> 00:02:40,694 best, most accurate depiction, 78 00:02:41,155 --> 00:02:42,534 captured into the EHR. 79 00:02:43,474 --> 00:02:45,895 Obviously, the goal is to make this happen. 80 00:02:46,995 --> 00:02:49,715 What are the barriers that you're still seeing 81 00:02:49,715 --> 00:02:52,534 that organizations are facing for making this happen? 82 00:02:53,189 --> 00:02:55,129 I think for a long time, we focused 83 00:02:55,270 --> 00:02:58,789 on really large health systems and really large 84 00:02:58,789 --> 00:02:59,289 payers 85 00:02:59,750 --> 00:03:02,229 sharing data amongst each other with a lot 86 00:03:02,229 --> 00:03:03,769 of money and a lot of tech. 87 00:03:04,150 --> 00:03:05,509 And I think when we get out into 88 00:03:05,509 --> 00:03:08,025 the independent and rural space, it's just a 89 00:03:08,025 --> 00:03:09,324 totally different ballgame. 90 00:03:09,625 --> 00:03:12,905 You're talking about providers that are potentially off 91 00:03:12,905 --> 00:03:14,125 the grid from an interoperability 92 00:03:14,425 --> 00:03:14,925 perspective. 93 00:03:15,465 --> 00:03:18,364 They may not have things like ADT interfacing 94 00:03:18,504 --> 00:03:21,030 where they know whether their patient's been admitted 95 00:03:21,030 --> 00:03:21,849 to the hospital. 96 00:03:22,229 --> 00:03:24,469 They could be using paper for labs still. 97 00:03:24,469 --> 00:03:27,030 I mean, just the the technical disparity that 98 00:03:27,030 --> 00:03:28,949 we see in the independent space can be 99 00:03:28,949 --> 00:03:29,769 really significant, 100 00:03:30,069 --> 00:03:31,590 and that can be a barrier. That can 101 00:03:31,590 --> 00:03:33,209 be a barrier for the 102 00:03:33,564 --> 00:03:35,645 data that they have access to for decision 103 00:03:35,645 --> 00:03:36,145 making. 104 00:03:36,604 --> 00:03:38,604 And we wanna make sure that those independent 105 00:03:38,604 --> 00:03:41,264 providers are really armed with the best information. 106 00:03:41,324 --> 00:03:43,104 So I think data and interoperability 107 00:03:43,405 --> 00:03:44,944 has been a consistent barrier. 108 00:03:45,245 --> 00:03:46,705 I think the second thing, 109 00:03:47,349 --> 00:03:50,310 is probably just admin burden and just less 110 00:03:50,310 --> 00:03:50,810 hands. 111 00:03:51,750 --> 00:03:54,069 Providers that work under the umbrella of a 112 00:03:54,069 --> 00:03:56,709 large health system tend to have teams that 113 00:03:56,709 --> 00:03:59,590 are dedicated to things like gap closure and 114 00:03:59,590 --> 00:04:02,185 risk adjustment and quality initiatives. But when you 115 00:04:02,185 --> 00:04:04,425 talk about an independent provider, it's just a 116 00:04:04,425 --> 00:04:05,485 totally different, 117 00:04:05,865 --> 00:04:09,224 framework. So they're running shorter, with hands. They're 118 00:04:09,224 --> 00:04:10,925 running shorter from a tech perspective, 119 00:04:11,224 --> 00:04:12,585 and it feels like the odds are kinda 120 00:04:12,585 --> 00:04:14,264 stacked against them. So when we are trying 121 00:04:14,264 --> 00:04:16,105 to problem solve in that environment, we need 122 00:04:16,105 --> 00:04:18,220 to make sure that we are creating tech 123 00:04:18,220 --> 00:04:20,779 solutions that can help alleviate that admin burden 124 00:04:20,779 --> 00:04:22,779 and not expect an entire team to help 125 00:04:22,779 --> 00:04:24,000 carry some of that lift. 126 00:04:24,379 --> 00:04:26,240 So I think that's another area. 127 00:04:26,939 --> 00:04:27,839 And then finally, 128 00:04:28,379 --> 00:04:29,600 attribution confusion. 129 00:04:30,164 --> 00:04:32,644 So providers that are independent don't wanna have 130 00:04:32,644 --> 00:04:34,644 to think about, hey. Is this a patient 131 00:04:34,644 --> 00:04:36,564 for payer x and this one's a patient 132 00:04:36,564 --> 00:04:37,224 for payer, 133 00:04:37,764 --> 00:04:39,764 y? And and I have different workflows for 134 00:04:39,764 --> 00:04:41,925 each payer. So I think when we're running 135 00:04:41,925 --> 00:04:44,410 short from a just not as many hands 136 00:04:44,410 --> 00:04:46,410 to help support and we're we have technical 137 00:04:46,410 --> 00:04:48,490 barriers, on top of that, we wanna make 138 00:04:48,490 --> 00:04:50,430 sure that workflows are 139 00:04:50,730 --> 00:04:52,970 agnostic to the payer behind the scenes. So 140 00:04:52,970 --> 00:04:55,129 we wanna make sure that the provider is 141 00:04:55,129 --> 00:04:57,550 armed with a strategy that allows them 142 00:04:57,944 --> 00:05:00,504 to address gaps in care and make sure 143 00:05:00,504 --> 00:05:02,824 that everything's well captured on a patient, but 144 00:05:02,824 --> 00:05:05,404 decouple that from specific payer programs. 145 00:05:05,784 --> 00:05:07,064 And I think that makes it a lot 146 00:05:07,064 --> 00:05:09,625 easier for independent providers to navigate all of 147 00:05:09,625 --> 00:05:11,064 the things that they need to do for 148 00:05:11,064 --> 00:05:12,125 better patient outcomes. 149 00:05:12,504 --> 00:05:15,279 If we can help create workflows that are 150 00:05:15,279 --> 00:05:17,919 payer agnostic and similar, that really drives behavior 151 00:05:17,919 --> 00:05:20,160 change and stickiness for the provider. So the 152 00:05:20,160 --> 00:05:21,759 behavior change is really crucial, and we talk 153 00:05:21,759 --> 00:05:24,000 a lot about, okay. There's data available. We 154 00:05:24,000 --> 00:05:25,759 know that there's a ton of data available 155 00:05:25,759 --> 00:05:28,419 in health care. The harder part is 156 00:05:28,795 --> 00:05:31,035 using that data to then drive action, which 157 00:05:31,035 --> 00:05:31,935 is so crucial. 158 00:05:32,634 --> 00:05:34,555 What does it take to embed gap closure 159 00:05:34,555 --> 00:05:37,375 capabilities directly into those provider workflows 160 00:05:37,675 --> 00:05:38,175 natively, 161 00:05:38,955 --> 00:05:40,895 and how does that shift then 162 00:05:41,275 --> 00:05:42,654 engagement and outcomes? 163 00:05:43,540 --> 00:05:46,259 It's great because many EHR vendors have started 164 00:05:46,259 --> 00:05:47,000 to recognize 165 00:05:47,300 --> 00:05:50,740 this need for a consolidated workflows to support 166 00:05:50,740 --> 00:05:51,240 payer 167 00:05:51,699 --> 00:05:52,439 gap closure. 168 00:05:52,819 --> 00:05:54,580 So Veradigm is one of them, but there 169 00:05:54,580 --> 00:05:56,600 are other EHRs, Epic, Athena, 170 00:05:57,455 --> 00:05:57,955 eClinicalWorks. 171 00:05:58,574 --> 00:06:01,694 They've all created workflows that are designed to 172 00:06:01,694 --> 00:06:04,595 corral payer content through one common workflow. 173 00:06:05,375 --> 00:06:07,055 I think of this sort of like when 174 00:06:07,055 --> 00:06:10,115 labs started becoming very commonly ordered in EHRs, 175 00:06:10,459 --> 00:06:12,379 we had a lab module that would allow, 176 00:06:12,379 --> 00:06:15,100 you know, the provider to choose a specific 177 00:06:15,100 --> 00:06:16,699 lab test. But behind the scenes, it would 178 00:06:16,699 --> 00:06:19,259 do the thinking of which lab that the 179 00:06:19,259 --> 00:06:21,500 procedure actually needed to be completed by, and 180 00:06:21,500 --> 00:06:23,600 it would do that thinking for the provider. 181 00:06:23,794 --> 00:06:26,435 We're looking to mirror that same concept when 182 00:06:26,435 --> 00:06:28,274 it comes to payer gap closure. We wanna 183 00:06:28,274 --> 00:06:30,915 be able to surface payer insights to providers 184 00:06:30,915 --> 00:06:32,595 at the point of care, but through a 185 00:06:32,595 --> 00:06:34,915 common channel, through a common workflow. And I 186 00:06:34,915 --> 00:06:36,915 think when we think about how does the 187 00:06:36,915 --> 00:06:39,550 EHR natively start to inject information, 188 00:06:40,089 --> 00:06:42,889 it becomes strengthened if we have more volume 189 00:06:42,889 --> 00:06:44,910 and more stickiness because of the repetition. 190 00:06:45,370 --> 00:06:48,430 So if we're stripping down the nuances 191 00:06:48,730 --> 00:06:51,129 between plans and saying, hey. We're gonna ask 192 00:06:51,129 --> 00:06:52,569 you to send all of your gaps to 193 00:06:52,569 --> 00:06:54,954 this standard format. And when we surface them, 194 00:06:54,954 --> 00:06:56,475 it's gonna be the same every time for 195 00:06:56,475 --> 00:06:58,175 the provider. It's gonna be the same workflow. 196 00:06:58,235 --> 00:06:59,935 It's gonna be surfacing the similar 197 00:07:00,314 --> 00:07:01,834 concepts so that we can start to drive 198 00:07:01,834 --> 00:07:03,294 that behavior change and stickiness. 199 00:07:03,675 --> 00:07:06,074 So I think that's, that's something that is 200 00:07:06,074 --> 00:07:08,474 really important is it's that it's a common 201 00:07:08,474 --> 00:07:10,860 workflow. And it also needs to feel intuitive 202 00:07:10,860 --> 00:07:13,360 to the workflows that the provider has already, 203 00:07:13,660 --> 00:07:15,180 you know, is already used to from a 204 00:07:15,180 --> 00:07:16,079 charting perspective. 205 00:07:16,620 --> 00:07:18,959 So we're looking at ways to meaningfully 206 00:07:19,899 --> 00:07:23,180 surface insights to the provider during their normal 207 00:07:23,180 --> 00:07:25,475 day to day, charting on a patient 208 00:07:25,775 --> 00:07:26,675 without causing, 209 00:07:27,215 --> 00:07:29,055 extra abrasion because they need to log in 210 00:07:29,055 --> 00:07:32,574 to multiple systems or other portals. We wanna 211 00:07:32,574 --> 00:07:34,735 try to bring all that information right into 212 00:07:34,735 --> 00:07:37,455 the normal workflow and then remind providers in 213 00:07:37,455 --> 00:07:39,580 areas that feel natural to them. So if 214 00:07:39,580 --> 00:07:41,740 they're ordering a test, making sure that we 215 00:07:41,740 --> 00:07:45,180 could, for example, trigger a prior authorization within 216 00:07:45,180 --> 00:07:46,160 the orders workflow. 217 00:07:46,460 --> 00:07:48,460 So it's things that when we're talking about 218 00:07:48,460 --> 00:07:49,819 native, we need to make sure that it's 219 00:07:49,819 --> 00:07:51,660 something that we have enough volume to drive 220 00:07:51,660 --> 00:07:54,055 that stickiness and behavior change, but also that 221 00:07:54,055 --> 00:07:56,214 we're thinking ahead as to how the provider 222 00:07:56,214 --> 00:07:57,514 actually uses the system. 223 00:07:57,895 --> 00:07:59,335 And that's what I think gives the EHR 224 00:07:59,335 --> 00:08:00,235 vendor a unique, 225 00:08:00,694 --> 00:08:03,175 perspective on this because we've designed how the 226 00:08:03,175 --> 00:08:04,805 provider is charting on the patient, and then 227 00:08:04,805 --> 00:08:04,884 we can also complement those existing workflows with 228 00:08:04,884 --> 00:08:06,154 additional intelligence, from payer partners. And 229 00:08:11,870 --> 00:08:13,790 outcomes that you're looking for? Is there any 230 00:08:13,790 --> 00:08:16,350 measurable outcomes that you're looking to see, any 231 00:08:16,350 --> 00:08:19,069 examples that you've seen actually make a difference 232 00:08:19,069 --> 00:08:19,970 for health systems? 233 00:08:20,485 --> 00:08:22,805 Yeah. I mean, so far, you know, it's 234 00:08:22,805 --> 00:08:25,125 it's been very exciting in this space because 235 00:08:25,125 --> 00:08:26,185 we work with 236 00:08:26,725 --> 00:08:28,985 thousands of independent provider practices 237 00:08:29,685 --> 00:08:30,085 that, 238 00:08:30,485 --> 00:08:33,205 have significant patient panels that, like I said, 239 00:08:33,205 --> 00:08:35,090 they might be off the grid and not 240 00:08:35,090 --> 00:08:37,490 used to receiving this information inside of this 241 00:08:37,490 --> 00:08:37,990 EHR. 242 00:08:38,370 --> 00:08:40,210 And now that we've sort of opened those 243 00:08:40,210 --> 00:08:41,509 pipes and we allow, 244 00:08:41,810 --> 00:08:43,730 payer content to get to the point of 245 00:08:43,730 --> 00:08:45,590 care, we have impacted, 246 00:08:46,129 --> 00:08:47,509 since the program's inception, 247 00:08:48,184 --> 00:08:51,065 over 2,000,000 patients in, you know, independent and 248 00:08:51,065 --> 00:08:51,964 rural settings 249 00:08:52,264 --> 00:08:55,964 that potentially may have gone, without preventative screenings 250 00:08:56,345 --> 00:08:57,384 or gaps, 251 00:08:57,705 --> 00:08:59,245 been been addressed because, 252 00:08:59,879 --> 00:09:01,480 you know, historically, these things could have been 253 00:09:01,480 --> 00:09:03,799 living in manual processes or portals that were 254 00:09:03,799 --> 00:09:05,960 never getting logged into. So I think from 255 00:09:05,960 --> 00:09:09,500 a, a volume perspective, we're we're upwards of, 256 00:09:09,559 --> 00:09:12,059 like I said, over 2,000,000 patients impacted, 257 00:09:12,894 --> 00:09:15,534 nearly 3,000,000 actual gaps that have been surfaced 258 00:09:15,534 --> 00:09:18,174 to providers. And we're also tracking things like 259 00:09:18,174 --> 00:09:20,975 program efficacy and making sure that providers are 260 00:09:20,975 --> 00:09:23,375 actually looking at the information, they're interacting with 261 00:09:23,375 --> 00:09:23,955 the information. 262 00:09:24,414 --> 00:09:26,570 So we're able to track whether a provider 263 00:09:26,629 --> 00:09:28,870 accepts the condition is present or rejects that 264 00:09:28,870 --> 00:09:31,289 the condition is present, which gives us meaningful 265 00:09:31,350 --> 00:09:33,909 insight and feedback back to payers to tell 266 00:09:33,909 --> 00:09:35,750 them, you know, hey. This is working. This 267 00:09:35,750 --> 00:09:37,909 isn't working. These are the practices that might 268 00:09:37,909 --> 00:09:39,289 need a little bit more help. 269 00:09:39,884 --> 00:09:41,884 So we can kinda track how they're using 270 00:09:41,884 --> 00:09:43,884 the system and also just what types of 271 00:09:43,884 --> 00:09:45,884 gaps are being surfaced for them. So I 272 00:09:45,884 --> 00:09:46,685 think it's pretty, 273 00:09:47,165 --> 00:09:49,105 it's pretty exciting. And so far, 274 00:09:49,725 --> 00:09:51,404 we feel like we're really making an impact 275 00:09:51,404 --> 00:09:53,085 in the area of the industry that's been, 276 00:09:53,085 --> 00:09:54,305 you know, often overlooked. 277 00:09:54,730 --> 00:09:56,649 The gap number speaks for itself, I feel 278 00:09:56,649 --> 00:09:57,629 like. Yeah. 279 00:09:58,330 --> 00:10:00,649 How is this going to evolve looking ahead? 280 00:10:00,649 --> 00:10:02,730 Right? What are you expecting this to look 281 00:10:02,730 --> 00:10:04,490 like, say, you know, five, ten years down 282 00:10:04,490 --> 00:10:06,330 the road, and specifically when we're looking at 283 00:10:06,330 --> 00:10:09,134 independent providers? Right? What do they need to 284 00:10:09,134 --> 00:10:09,875 prioritize right 285 00:10:10,575 --> 00:10:11,075 now? 286 00:10:11,615 --> 00:10:14,835 I think for independent providers, getting connected to, 287 00:10:15,774 --> 00:10:18,654 the information superhighway and being able to exchange 288 00:10:18,654 --> 00:10:20,815 data through things like TEFCA is really important. 289 00:10:20,815 --> 00:10:23,370 So I think interoperability or the ability to 290 00:10:23,370 --> 00:10:25,129 move data from point a to point b 291 00:10:25,129 --> 00:10:26,509 inside of the healthcare ecosystem, 292 00:10:27,129 --> 00:10:28,570 for me, is top of mind. I think 293 00:10:28,570 --> 00:10:30,009 that's the most important thing. We need to 294 00:10:30,009 --> 00:10:31,070 make sure that providers 295 00:10:31,610 --> 00:10:33,629 not only can receive data externally, 296 00:10:33,945 --> 00:10:35,625 but that the data that they hold within 297 00:10:35,625 --> 00:10:37,304 their walls can make it to the acute 298 00:10:37,304 --> 00:10:39,225 care setting and to the local hospital if 299 00:10:39,225 --> 00:10:42,044 a patient was, unexpectedly admitted for an emergency. 300 00:10:42,504 --> 00:10:45,004 Those types of things really tackle the duplication 301 00:10:45,144 --> 00:10:47,159 and waste that we see in the health 302 00:10:47,159 --> 00:10:49,879 care system and eventually tackle affordability and all 303 00:10:49,879 --> 00:10:51,179 the things that are really dragging. 304 00:10:51,559 --> 00:10:53,320 So I think that's an area that's really 305 00:10:53,320 --> 00:10:55,480 interesting. I think top of mind for me 306 00:10:55,480 --> 00:10:58,839 for strength in the future is interoperability and 307 00:10:58,839 --> 00:11:00,860 making sure that providers can be connected, 308 00:11:01,164 --> 00:11:03,004 not just data out, but also data back 309 00:11:03,004 --> 00:11:04,924 meaningfully to the point of care. And I 310 00:11:04,924 --> 00:11:07,424 think, you know, payers provide a unique perspective 311 00:11:07,485 --> 00:11:09,565 on that because they also have a tremendous 312 00:11:09,565 --> 00:11:12,684 amount of data that can meaningfully impact physician 313 00:11:12,845 --> 00:11:14,970 clinical decision making at the point of care. 314 00:11:14,970 --> 00:11:17,149 So if we can create those rails and 315 00:11:17,449 --> 00:11:20,429 allow data to seamlessly move through the ecosystem, 316 00:11:20,889 --> 00:11:22,809 I think it can help to give significant 317 00:11:22,809 --> 00:11:23,789 lift and impact 318 00:11:24,169 --> 00:11:26,089 to patient outcomes and making sure that we 319 00:11:26,089 --> 00:11:27,689 are really driving down costs and some of 320 00:11:27,689 --> 00:11:29,894 the other things that are creating waste and 321 00:11:29,894 --> 00:11:31,034 drag on the system. 322 00:11:31,495 --> 00:11:32,934 Megan, so great to have you. Thanks again 323 00:11:32,934 --> 00:11:35,334 for your time and insights today. So excited 324 00:11:35,334 --> 00:11:36,615 to have you. We also want to thank 325 00:11:36,615 --> 00:11:38,615 our podcast sponsor, Veradigm. You can tune in 326 00:11:38,615 --> 00:11:40,615 to more podcasts from Becker's Healthcare visiting our 327 00:11:40,615 --> 00:11:44,075 podcast page at beckershospitalreview.com.