1 00:00:02,240 --> 00:00:05,120 The most important health care decisions don't happen 2 00:00:05,120 --> 00:00:05,779 in isolation. 3 00:00:06,240 --> 00:00:08,179 They happen when leaders come together. 4 00:00:08,800 --> 00:00:11,519 Becker's sixteenth annual meeting brings together more than 5 00:00:11,519 --> 00:00:12,559 3,500 6 00:00:12,559 --> 00:00:15,525 hospital and health system executives this April in 7 00:00:15,525 --> 00:00:16,024 Chicago. 8 00:00:16,565 --> 00:00:18,664 With 800 speakers from Ascension, 9 00:00:18,964 --> 00:00:22,164 Cleveland Clinic, CommonSpirit and more, the conversations get 10 00:00:22,164 --> 00:00:24,964 real. Leaders will share how their scenario planning 11 00:00:24,964 --> 00:00:27,605 for policy shifts, breaking through value based care 12 00:00:27,605 --> 00:00:30,000 barriers, and building clinical teams that translate 13 00:00:37,359 --> 00:00:37,859 event 14 00:00:38,320 --> 00:00:38,820 details, 15 00:00:39,280 --> 00:00:41,759 visit beckershospitalreview.com 16 00:00:41,759 --> 00:00:43,520 and click on the events tab in the 17 00:00:43,520 --> 00:00:44,340 upper right. 18 00:00:46,375 --> 00:00:48,454 This is Laura Dirdo with the Becker's Healthcare 19 00:00:48,454 --> 00:00:48,954 podcast. 20 00:00:49,335 --> 00:00:51,094 I'm thrilled today to be joined by Myles 21 00:00:51,094 --> 00:00:53,494 Demarajan, who is the vice president of data 22 00:00:53,494 --> 00:00:55,975 and analytics at UC Irvine Health. Myles, a 23 00:00:55,975 --> 00:00:57,754 pleasure to have you on the podcast today. 24 00:00:59,310 --> 00:01:01,730 Same here, Laura. Thanks for inviting me. 25 00:01:02,670 --> 00:01:05,150 Absolutely. Now I'm looking forward to our conversation 26 00:01:05,150 --> 00:01:07,469 because I know UC Irvine Health has gone 27 00:01:07,469 --> 00:01:09,469 going through a big transformation right now, a 28 00:01:09,469 --> 00:01:12,375 lot happening, some expansion after your acquisition. So 29 00:01:12,534 --> 00:01:14,055 I'm looking forward to hearing a bit more 30 00:01:14,055 --> 00:01:16,055 about that. But first, can you introduce yourself 31 00:01:16,055 --> 00:01:17,495 and just talk a little bit more about 32 00:01:17,495 --> 00:01:18,555 UC Irvine Health? 33 00:01:19,174 --> 00:01:19,575 Sure. 34 00:01:20,135 --> 00:01:22,614 I'm Mile Duran. People call me Mile. The 35 00:01:22,614 --> 00:01:24,715 closest pronunciation is m I l e. 36 00:01:25,270 --> 00:01:27,270 So I'm vice president of data and analytics 37 00:01:27,270 --> 00:01:30,230 in USA Health. So I help USA Health 38 00:01:30,230 --> 00:01:33,430 in creating the data driven ecosystem so that 39 00:01:33,430 --> 00:01:34,890 we can take, 40 00:01:35,350 --> 00:01:35,850 authorization, 41 00:01:37,350 --> 00:01:39,609 decision based on data insights 42 00:01:39,984 --> 00:01:42,784 that we develop using the metrics and other 43 00:01:42,784 --> 00:01:43,284 parameters. 44 00:01:44,625 --> 00:01:47,444 You see, eighteen months for me. I'm relatively 45 00:01:47,584 --> 00:01:50,144 new, and I'm very excited to be here 46 00:01:50,144 --> 00:01:51,364 in UCI Health. 47 00:01:51,905 --> 00:01:54,510 It's one of the, you know, popular academic 48 00:01:54,510 --> 00:01:56,210 medical center in Southern California. 49 00:01:56,670 --> 00:01:57,650 So we are, 50 00:01:58,030 --> 00:01:58,530 close 51 00:01:59,310 --> 00:02:00,930 to 350 52 00:02:00,990 --> 00:02:01,490 beds, 53 00:02:01,870 --> 00:02:02,370 hospital. 54 00:02:02,909 --> 00:02:04,670 And recently, you know, in this, 55 00:02:05,069 --> 00:02:06,990 I would say couple of months, we transform 56 00:02:06,990 --> 00:02:07,969 ourselves from 57 00:02:08,474 --> 00:02:11,914 being single hospital to seven hospital system, integrating, 58 00:02:11,914 --> 00:02:15,115 you know, several tools, technology, processes, people, all 59 00:02:15,115 --> 00:02:17,275 of them together. And everything went live, you 60 00:02:17,275 --> 00:02:18,014 know, last, 61 00:02:18,634 --> 00:02:21,294 December, meaning just six weeks back. 62 00:02:23,340 --> 00:02:25,740 Good night. Wow. That's, incredible to hear. And 63 00:02:25,740 --> 00:02:27,180 I know, you know, so much, 64 00:02:27,580 --> 00:02:29,980 time and space happening. So, I guess, could 65 00:02:29,980 --> 00:02:31,099 you tell us a little bit more about 66 00:02:31,099 --> 00:02:32,780 some of the big trends you're watching currently? 67 00:02:32,780 --> 00:02:34,240 What's top of mind for you? 68 00:02:35,025 --> 00:02:37,025 Yeah. I mean, some of the trends that 69 00:02:37,025 --> 00:02:39,444 we are currently, you know, watching from, 70 00:02:40,145 --> 00:02:42,724 as a health care organization, you know, including, 71 00:02:43,504 --> 00:02:45,985 being a academic medical center also is, 72 00:02:46,784 --> 00:02:50,270 how AI, like anybody else, right, can enable 73 00:02:50,270 --> 00:02:51,810 some of the things that we do. 74 00:02:52,270 --> 00:02:53,010 As you may 75 00:02:53,550 --> 00:02:55,230 know, the health care, especially the provider side 76 00:02:55,230 --> 00:02:57,250 of the business, is a very low margin, 77 00:02:57,550 --> 00:02:59,889 and we are always in the financial pressure 78 00:03:00,030 --> 00:03:02,110 to make sure that how we can deliver 79 00:03:02,110 --> 00:03:05,094 patient care with the limited resources that are 80 00:03:05,094 --> 00:03:05,594 available, 81 00:03:06,215 --> 00:03:08,135 at the same time without any compromising the 82 00:03:08,135 --> 00:03:10,294 quality of the care that we do. So 83 00:03:10,294 --> 00:03:11,675 keeping those things in mind, 84 00:03:12,215 --> 00:03:14,534 how maximum we can leverage technology that are 85 00:03:14,534 --> 00:03:15,034 available. 86 00:03:15,575 --> 00:03:16,075 So 87 00:03:16,389 --> 00:03:19,030 currently, we are looking at all the tools 88 00:03:19,030 --> 00:03:21,049 technology available that we want to use 89 00:03:21,349 --> 00:03:22,330 with our recent, 90 00:03:23,509 --> 00:03:26,409 you know, opportunity to move from shared 91 00:03:26,709 --> 00:03:29,289 EPYC or EMR instance to our own instance, 92 00:03:29,694 --> 00:03:31,935 helped us a lot of, you know, positive 93 00:03:31,935 --> 00:03:33,474 way to get there. 94 00:03:33,935 --> 00:03:34,594 And also 95 00:03:35,055 --> 00:03:36,974 in parallel, we are also, you know, shifting 96 00:03:36,974 --> 00:03:38,594 ourselves moving from 97 00:03:38,974 --> 00:03:41,395 the typical AI pilot demos 98 00:03:41,909 --> 00:03:43,610 to how do we, you know, productionize 99 00:03:44,310 --> 00:03:45,689 those AI projects 100 00:03:46,229 --> 00:03:48,650 and, make sure that, you know, appropriate governance 101 00:03:48,709 --> 00:03:49,849 structure put in place 102 00:03:50,229 --> 00:03:50,729 and, 103 00:03:51,349 --> 00:03:55,245 enable our, you know, people across our organization 104 00:03:55,245 --> 00:03:57,844 from either its operations or the clinicians using, 105 00:03:57,844 --> 00:04:00,044 you know, some of the technology like Upbridge 106 00:04:00,044 --> 00:04:01,965 for the scribes, as well as the community 107 00:04:01,965 --> 00:04:02,864 cycle and research, 108 00:04:03,164 --> 00:04:03,664 community, 109 00:04:04,444 --> 00:04:06,465 to make sure that though they have 110 00:04:06,939 --> 00:04:09,360 the appropriate tool that they can use 111 00:04:09,739 --> 00:04:11,419 in a more effective way to do their 112 00:04:11,419 --> 00:04:12,239 day to day job. 113 00:04:12,699 --> 00:04:14,799 And, also, you know, from the 114 00:04:15,739 --> 00:04:17,039 health care data perspective, 115 00:04:17,660 --> 00:04:20,720 we also, you know, enable the technical framework 116 00:04:20,779 --> 00:04:22,079 in our new EMR. 117 00:04:22,454 --> 00:04:24,134 So what what it benefits is, you know, 118 00:04:24,134 --> 00:04:25,595 it it it also 119 00:04:25,975 --> 00:04:27,754 enabled us to leverage 120 00:04:28,214 --> 00:04:30,475 all the future functionality of the TEFCO framework 121 00:04:30,615 --> 00:04:31,975 so that we don't have to really, you 122 00:04:31,975 --> 00:04:33,595 know, dip it on a lot of HAEs 123 00:04:33,735 --> 00:04:34,875 to do certain functionality. 124 00:04:35,574 --> 00:04:37,354 We leverage the maximum 125 00:04:37,899 --> 00:04:40,240 opportunities to use a technical framework 126 00:04:40,540 --> 00:04:42,639 so it can, you know, also help us 127 00:04:43,100 --> 00:04:44,540 in cutting some of the costs related to 128 00:04:44,540 --> 00:04:45,600 the HIE technology. 129 00:04:46,779 --> 00:04:48,639 Additionally, we are also now investing, 130 00:04:49,339 --> 00:04:51,980 or looking for the opportunity to do the 131 00:04:51,980 --> 00:04:52,800 AI governance. 132 00:04:53,254 --> 00:04:55,175 In the AI governance, you know, the important 133 00:04:55,175 --> 00:04:56,774 part is to make sure that how do 134 00:04:56,774 --> 00:04:57,274 we 135 00:04:57,654 --> 00:04:59,894 manage those models in appropriate way? How do 136 00:04:59,894 --> 00:05:02,134 we have the right repository? How do we, 137 00:05:02,134 --> 00:05:04,154 you know, align with the regulatory, 138 00:05:04,935 --> 00:05:07,350 needs? And then also, obviously, the privacy and 139 00:05:07,350 --> 00:05:08,550 other concerns that we, 140 00:05:09,589 --> 00:05:11,110 have to make sure that those models are 141 00:05:11,110 --> 00:05:12,970 working appropriately to make it happen. 142 00:05:13,589 --> 00:05:15,509 So that's another, you know, important thing that 143 00:05:15,509 --> 00:05:17,289 we are investing as well as the 144 00:05:17,990 --> 00:05:20,649 the FHIR or the FHIR, the API maturity 145 00:05:20,789 --> 00:05:22,305 also helping us in 146 00:05:22,605 --> 00:05:23,665 helping solve the, 147 00:05:24,444 --> 00:05:26,545 analytics integration back into the application, 148 00:05:27,245 --> 00:05:29,084 which is, you know, previously I mean, we 149 00:05:29,084 --> 00:05:30,464 we used to have FHIR, 150 00:05:31,245 --> 00:05:33,084 APIs, but, again, it's not that much better. 151 00:05:33,084 --> 00:05:34,384 But now we have that opportunity 152 00:05:34,849 --> 00:05:37,110 to leverage that, more and more. 153 00:05:38,449 --> 00:05:38,930 And, 154 00:05:39,329 --> 00:05:41,189 in parallel, this is all, you know, mostly 155 00:05:41,250 --> 00:05:43,569 on the EMR side, you know, vendor dependence 156 00:05:43,569 --> 00:05:45,430 in certain things, including some of those, 157 00:05:46,129 --> 00:05:46,629 HIE 158 00:05:46,930 --> 00:05:48,370 stuff. But at the same time, we are 159 00:05:48,370 --> 00:05:49,509 also investing 160 00:05:50,144 --> 00:05:52,165 in modern analytics platform, 161 00:05:53,105 --> 00:05:54,084 which needs 162 00:05:54,545 --> 00:05:56,564 for our, you know, the administrative 163 00:05:57,425 --> 00:05:58,324 and other research, 164 00:05:59,024 --> 00:06:01,985 related needs. So this platform will help us 165 00:06:01,985 --> 00:06:05,285 to integrate data across, our multiple data domains, 166 00:06:06,250 --> 00:06:09,050 with the appropriate data governance structure. We also 167 00:06:09,050 --> 00:06:10,350 have an opportunity to, 168 00:06:11,050 --> 00:06:12,009 make sure that, 169 00:06:13,209 --> 00:06:15,629 the data is having all the trust 170 00:06:16,009 --> 00:06:17,470 in terms of, you know, making, 171 00:06:18,089 --> 00:06:21,615 the validation, data lineage, data metadata management, and 172 00:06:21,694 --> 00:06:22,194 other 173 00:06:22,574 --> 00:06:24,274 technology solution in the bottom, 174 00:06:24,654 --> 00:06:26,735 as well as collaborating always tightly with the 175 00:06:26,735 --> 00:06:29,474 business team to make sure that they understand, 176 00:06:30,814 --> 00:06:31,634 the the needs 177 00:06:32,095 --> 00:06:34,495 of definition of the each of the KPIs 178 00:06:34,495 --> 00:06:36,480 that they are talking about and making sure 179 00:06:36,480 --> 00:06:39,040 that those KPIs or the key performance indicators 180 00:06:39,040 --> 00:06:40,180 are defined appropriately. 181 00:06:40,720 --> 00:06:42,580 And then bringing all of them onboarded 182 00:06:43,279 --> 00:06:46,000 to understand these definitions are, you know, aligning 183 00:06:46,000 --> 00:06:47,699 with their specific needs 184 00:06:48,044 --> 00:06:50,125 and publish those information so that it there's 185 00:06:50,125 --> 00:06:51,185 there's a transparency 186 00:06:51,964 --> 00:06:54,444 in understanding and the documenting and using those, 187 00:06:55,084 --> 00:06:57,644 key performance syndicated. So why it is important? 188 00:06:57,644 --> 00:07:00,305 Once you have that particular process built 189 00:07:00,710 --> 00:07:03,050 with the tight partnership with the business, 190 00:07:03,430 --> 00:07:05,030 it will be very tough for us to, 191 00:07:05,030 --> 00:07:06,870 you know, say that, you know, this particular 192 00:07:06,870 --> 00:07:09,030 data is accurate. So the accuracy of the 193 00:07:09,030 --> 00:07:09,930 data, the trust, 194 00:07:10,470 --> 00:07:12,150 worthiness of the data is built with a 195 00:07:12,150 --> 00:07:14,595 partnership and then with the data governance structure. 196 00:07:14,834 --> 00:07:16,514 We are not there fully yet, but at 197 00:07:16,514 --> 00:07:19,235 the same time, we are kicking off, data 198 00:07:19,235 --> 00:07:23,254 governance process, collaborating again heavily with our business 199 00:07:23,314 --> 00:07:23,814 leaders, 200 00:07:24,595 --> 00:07:26,055 to make sure that we have 201 00:07:26,355 --> 00:07:27,714 each one of the step that we do 202 00:07:27,714 --> 00:07:29,475 in analytics and having that kind of a 203 00:07:29,475 --> 00:07:29,975 partnership. 204 00:07:30,435 --> 00:07:32,460 So those are the broader trends that currently 205 00:07:32,460 --> 00:07:33,520 we are, you know, 206 00:07:34,139 --> 00:07:36,639 watching and then making sure that those trends, 207 00:07:37,580 --> 00:07:40,480 are aligned with our needs as an organization. 208 00:07:40,779 --> 00:07:42,220 And then how do we, you know, bring 209 00:07:42,220 --> 00:07:44,814 in those, new tools, technology, other processes, you 210 00:07:44,814 --> 00:07:46,094 know, that tends can be even in the 211 00:07:46,094 --> 00:07:48,175 process, some of the specific process improvement that 212 00:07:48,175 --> 00:07:48,995 we can do, 213 00:07:49,615 --> 00:07:50,115 embedded, 214 00:07:50,735 --> 00:07:52,914 into our day to day, you know, workflow 215 00:07:53,055 --> 00:07:55,794 and, you know, our needs for our business. 216 00:07:58,660 --> 00:08:00,660 I love that. I think it's so helpful 217 00:08:00,660 --> 00:08:02,660 to understand that technology and exciting to see 218 00:08:02,660 --> 00:08:04,899 what's possible, but also, you know, the gravity 219 00:08:04,899 --> 00:08:06,500 of everything that you have to do in 220 00:08:06,500 --> 00:08:08,819 order to integrate the technology and the data 221 00:08:08,819 --> 00:08:10,259 and make sure the data is correct and 222 00:08:10,259 --> 00:08:12,975 accurate and then continues to, function in the 223 00:08:12,975 --> 00:08:14,814 way it's supposed to. I I think one 224 00:08:14,814 --> 00:08:16,254 of the things you talked about is the 225 00:08:16,254 --> 00:08:18,175 data governance process, which I know is so, 226 00:08:18,175 --> 00:08:20,574 so critical in being able to get the 227 00:08:20,574 --> 00:08:22,495 right outcomes that you need once you've got 228 00:08:22,495 --> 00:08:23,875 the technology in place. 229 00:08:24,254 --> 00:08:25,694 So can you talk a little bit more 230 00:08:25,694 --> 00:08:28,240 about the data governance process and how, you 231 00:08:28,240 --> 00:08:30,000 know, you set it up, who's involved, and 232 00:08:30,000 --> 00:08:32,399 what you've really learned about, making sure that 233 00:08:32,399 --> 00:08:34,000 this is done in a way that helps 234 00:08:34,000 --> 00:08:36,000 you move innovation forward, but also isn't putting 235 00:08:36,000 --> 00:08:36,740 you at risk? 236 00:08:37,440 --> 00:08:39,519 Yeah. I I think, I mean, those are 237 00:08:39,519 --> 00:08:41,475 the things that we are, watching now. So 238 00:08:41,475 --> 00:08:44,535 we we, the as our association, we established 239 00:08:44,595 --> 00:08:45,575 health data governance. 240 00:08:46,514 --> 00:08:49,315 But, again, we focused mainly on certain areas. 241 00:08:49,315 --> 00:08:51,315 And, again, we want to expand that across 242 00:08:51,315 --> 00:08:53,254 all the areas, you know, including administrative, 243 00:08:54,035 --> 00:08:55,654 key metrics and other things. 244 00:08:56,360 --> 00:08:58,519 So keeping that in mind, we are we 245 00:08:58,519 --> 00:09:00,220 are rejuvenating some of those, 246 00:09:00,600 --> 00:09:03,080 specific governance process across where we can bring 247 00:09:03,080 --> 00:09:03,820 in more, 248 00:09:04,519 --> 00:09:05,980 clinical clinical related, 249 00:09:06,360 --> 00:09:08,695 you know, the subject matter experts, including the 250 00:09:08,695 --> 00:09:09,595 leadership level. 251 00:09:10,054 --> 00:09:12,375 So we have one integrated, you know, set 252 00:09:12,375 --> 00:09:14,794 of processes across our organization as enterprise. 253 00:09:15,095 --> 00:09:17,095 Right? As a clinical medical center, as you 254 00:09:17,095 --> 00:09:20,054 may already know, when we have the the 255 00:09:20,054 --> 00:09:23,355 combination of, the medical system, the hospital side, 256 00:09:23,750 --> 00:09:25,990 the research, and then the school side. We 257 00:09:25,990 --> 00:09:28,809 always have different data needs for the organization. 258 00:09:29,269 --> 00:09:31,509 So we also need to carve out the 259 00:09:31,509 --> 00:09:33,909 appropriate data governance structure for that. So for 260 00:09:33,909 --> 00:09:35,830 example, in the hospital side, it can be 261 00:09:35,830 --> 00:09:37,049 a very specific 262 00:09:37,644 --> 00:09:39,964 set of data governance policy and procedure that 263 00:09:39,964 --> 00:09:42,845 we need to create versus in research, it 264 00:09:42,845 --> 00:09:45,404 may, you know, enable some of those policy 265 00:09:45,404 --> 00:09:47,804 procedures for their data needs, but also it 266 00:09:47,804 --> 00:09:49,024 has additional layer, 267 00:09:49,565 --> 00:09:52,044 for the privacy where we also need to 268 00:09:52,044 --> 00:09:52,799 go through the, 269 00:09:53,360 --> 00:09:55,299 IRB and other, compliance, 270 00:09:56,159 --> 00:09:57,919 layers to make sure that, you know, we 271 00:09:57,919 --> 00:10:00,159 have we are compliant with the privacy and 272 00:10:00,159 --> 00:10:02,639 then consent of the patient before we deliver 273 00:10:02,639 --> 00:10:05,279 any data. So those layers are always, you 274 00:10:05,279 --> 00:10:06,100 know, the additional, 275 00:10:07,039 --> 00:10:08,954 activity that we need to do. So keeping 276 00:10:08,954 --> 00:10:11,434 that in mind, at this point in time, 277 00:10:11,434 --> 00:10:12,574 we want to have 278 00:10:13,595 --> 00:10:17,434 create, these policies, procedures for hospital in a 279 00:10:17,434 --> 00:10:20,634 very broader sense, and then also trickle it 280 00:10:20,634 --> 00:10:23,454 down across our organization as appropriately. 281 00:10:23,850 --> 00:10:24,669 And also, Ruben, 282 00:10:25,129 --> 00:10:26,589 as academic medical center, 283 00:10:27,049 --> 00:10:29,230 we have several of our clinician also, 284 00:10:29,610 --> 00:10:30,190 you know, 285 00:10:31,209 --> 00:10:33,769 do, research. They are also PI for some 286 00:10:33,769 --> 00:10:35,690 of the research grants that they have. So 287 00:10:35,690 --> 00:10:37,850 we need to balance those activity and then 288 00:10:37,850 --> 00:10:38,909 make sure that those 289 00:10:39,404 --> 00:10:42,365 data is governed appropriately, not just in the 290 00:10:42,365 --> 00:10:44,684 EMR, but also outside the EMR. How we 291 00:10:44,684 --> 00:10:46,605 manage it? How do we secure it? How 292 00:10:46,605 --> 00:10:47,745 do we make sure that, 293 00:10:48,125 --> 00:10:50,125 what are the minimally needed data only is 294 00:10:50,125 --> 00:10:51,904 available for them at the same time, 295 00:10:52,279 --> 00:10:54,460 without, you know, stopping their research. 296 00:10:54,840 --> 00:10:56,759 What are the ways we can address their 297 00:10:56,759 --> 00:10:58,759 data needs? And whether it's a data defined 298 00:10:58,759 --> 00:11:00,940 dataset, we can give in a a broader 299 00:11:01,240 --> 00:11:03,879 sense. And also, we are also enabling some 300 00:11:03,879 --> 00:11:05,660 of the real world data, 301 00:11:06,360 --> 00:11:09,584 by partnership with our EMR vendor so that 302 00:11:09,584 --> 00:11:12,384 the researchers have an opportunity to go and, 303 00:11:12,584 --> 00:11:15,105 you know, get those access to a very 304 00:11:15,105 --> 00:11:17,284 large set. In this particular one, we have 305 00:11:17,345 --> 00:11:18,804 access to 300,000,000 306 00:11:18,865 --> 00:11:20,245 de identified data, 307 00:11:21,279 --> 00:11:22,340 across the globe, 308 00:11:22,800 --> 00:11:24,899 this data of patient across the globe, 309 00:11:25,519 --> 00:11:26,960 through our EMR. But that 310 00:11:27,759 --> 00:11:29,840 so this is this also enables that. Okay. 311 00:11:29,840 --> 00:11:31,200 Now it's a great now we have so 312 00:11:31,200 --> 00:11:33,200 much access to the data. Now, how do 313 00:11:33,200 --> 00:11:35,085 we make sure that this is safe? 314 00:11:35,565 --> 00:11:37,325 So that's where the data governance for. That 315 00:11:37,325 --> 00:11:39,965 specific real world data come into play. How 316 00:11:39,965 --> 00:11:41,085 do we make sure that, you know, the 317 00:11:41,085 --> 00:11:42,925 right people having access? How how do we 318 00:11:42,925 --> 00:11:44,304 make sure that they are trained, 319 00:11:44,764 --> 00:11:46,605 to use the data in appropriate way? So 320 00:11:46,605 --> 00:11:49,085 all these things are, you know, also driving 321 00:11:49,085 --> 00:11:50,304 us, to 322 00:11:50,720 --> 00:11:51,779 make the, 323 00:11:52,240 --> 00:11:55,220 you know, layers of data governance specific activity. 324 00:11:56,000 --> 00:11:57,139 But I, again, 325 00:11:57,519 --> 00:11:59,540 data governance is a very broad subject. 326 00:12:00,240 --> 00:12:01,840 It's very tough for us to, you know, 327 00:12:01,840 --> 00:12:04,100 start all the components of the data management, 328 00:12:04,399 --> 00:12:05,220 data governance, 329 00:12:05,884 --> 00:12:07,644 you know, aspects of it. So we need 330 00:12:07,644 --> 00:12:09,565 to focus on some of the critical ones, 331 00:12:09,565 --> 00:12:10,544 what would benefit, 332 00:12:11,404 --> 00:12:12,304 UCI Irvine, 333 00:12:12,605 --> 00:12:14,285 for next to, you know, three months, six 334 00:12:14,285 --> 00:12:17,004 months, one year, and then address all those 335 00:12:17,004 --> 00:12:19,230 specific component in that and then create the 336 00:12:19,230 --> 00:12:21,870 policy procedures and then processes for that and 337 00:12:21,870 --> 00:12:23,629 then execute that so that, you know, we 338 00:12:23,629 --> 00:12:25,789 don't boil the ocean. We address each one 339 00:12:25,789 --> 00:12:27,149 of these pieces and then move to the 340 00:12:27,149 --> 00:12:30,590 next one. So that's what currently I'm working 341 00:12:30,590 --> 00:12:31,870 on to make sure that, you know, what's 342 00:12:31,870 --> 00:12:34,154 our roadmap for data governance? What area we 343 00:12:34,154 --> 00:12:35,615 need to focus on data governance 344 00:12:35,995 --> 00:12:37,834 to make sure that we create a policy 345 00:12:37,834 --> 00:12:40,794 and procedures. So the user community as well 346 00:12:40,794 --> 00:12:43,834 as, including the technical, nontechnical, and then the 347 00:12:43,834 --> 00:12:44,334 users, 348 00:12:44,955 --> 00:12:45,855 they have a very 349 00:12:46,220 --> 00:12:47,440 transparent way to understand, 350 00:12:48,300 --> 00:12:50,700 you know, to get, to get the data, 351 00:12:50,700 --> 00:12:52,379 what I need to do. Simple. It could 352 00:12:52,379 --> 00:12:54,300 be right. How do I access data? What's 353 00:12:54,300 --> 00:12:56,139 the policy if my role is this x 354 00:12:56,139 --> 00:12:56,879 of z? 355 00:12:57,259 --> 00:12:58,860 How do we how do what kind of 356 00:12:58,860 --> 00:12:59,440 a data 357 00:12:59,740 --> 00:13:02,274 are currently available? Do we need to, you 358 00:13:02,274 --> 00:13:04,054 know, install the appropriate data 359 00:13:04,434 --> 00:13:05,254 catalog technology 360 00:13:05,794 --> 00:13:07,634 to make sure that they understand what is 361 00:13:07,634 --> 00:13:09,575 available before they ask for the new one? 362 00:13:10,034 --> 00:13:12,274 And then it could be what's the intake 363 00:13:12,274 --> 00:13:14,519 process and what's the priority for us to 364 00:13:14,759 --> 00:13:16,360 deliver data. If you have, you know, 15 365 00:13:16,360 --> 00:13:18,759 tickets when we have resource constrained and all 366 00:13:18,759 --> 00:13:20,600 the 15 has to be addressed this week, 367 00:13:20,600 --> 00:13:22,679 how do we prioritize that? So all these 368 00:13:22,679 --> 00:13:24,679 structures have to be put in place, policy 369 00:13:24,679 --> 00:13:27,160 and procedures, and and make it transparent, make 370 00:13:27,160 --> 00:13:29,264 it available for our user committee so that 371 00:13:29,585 --> 00:13:31,345 they know exactly where to go and look 372 00:13:31,345 --> 00:13:33,184 for what, and they they are very clearly 373 00:13:33,184 --> 00:13:33,684 understand, 374 00:13:34,545 --> 00:13:37,184 the policy and processes to get there. So 375 00:13:37,184 --> 00:13:38,884 that's in works for us 376 00:13:39,264 --> 00:13:40,085 at this time. 377 00:13:40,785 --> 00:13:42,545 Absolutely. Thank you so much for going through 378 00:13:42,545 --> 00:13:43,985 all of that. I know it's a lot, 379 00:13:44,399 --> 00:13:46,320 to to take on, but it's truly helpful 380 00:13:46,320 --> 00:13:48,639 to hear kind of those processes and the 381 00:13:48,639 --> 00:13:49,620 reasoning behind 382 00:13:50,000 --> 00:13:51,840 everything you put into place. And so, you 383 00:13:51,840 --> 00:13:53,440 know, as other health systems are trying to 384 00:13:53,440 --> 00:13:55,040 do something similar, they can, 385 00:13:55,840 --> 00:13:58,080 see that level of specificity. Now what are 386 00:13:58,080 --> 00:13:59,920 you most focused on and excited about right 387 00:13:59,920 --> 00:14:00,375 now? 388 00:14:01,815 --> 00:14:02,315 Well, 389 00:14:03,335 --> 00:14:05,674 so we are I'm very excited about, 390 00:14:07,575 --> 00:14:10,794 how do we evolve through the processes 391 00:14:11,495 --> 00:14:12,794 I mean, people and processes 392 00:14:13,735 --> 00:14:14,875 after our big, 393 00:14:16,200 --> 00:14:17,100 I would say, 394 00:14:17,480 --> 00:14:19,259 big initiative that we have done. 395 00:14:20,279 --> 00:14:23,100 So we acquired four new hospital, 396 00:14:24,440 --> 00:14:26,600 couple of years ago, and then we brought 397 00:14:26,600 --> 00:14:28,919 in all the hospital and integrated them from 398 00:14:28,919 --> 00:14:29,980 technology perspective, 399 00:14:31,000 --> 00:14:31,740 this December. 400 00:14:32,254 --> 00:14:34,914 And also we built a brand new hospital, 401 00:14:36,095 --> 00:14:37,875 investing 1,200,000,000, 402 00:14:38,414 --> 00:14:40,254 and then we integrated that in the same 403 00:14:40,254 --> 00:14:43,154 tools and technology. And then we also moved 404 00:14:43,615 --> 00:14:46,254 from our shared EMR instance to our own 405 00:14:46,254 --> 00:14:47,075 shared instance. 406 00:14:48,480 --> 00:14:50,340 And then now we have our, you know, 407 00:14:50,480 --> 00:14:51,300 feature race, 408 00:14:52,720 --> 00:14:54,740 feature enriched or feature futuristic 409 00:14:55,440 --> 00:14:57,779 EMR available for our clinicians and administrators. 410 00:14:58,320 --> 00:15:00,080 So all the three things happen, 411 00:15:01,245 --> 00:15:03,345 just six weeks back in December. 412 00:15:03,725 --> 00:15:05,425 So it was, you know, very, 413 00:15:06,125 --> 00:15:06,625 highly, 414 00:15:07,325 --> 00:15:08,684 what do you want to call it? As 415 00:15:08,684 --> 00:15:09,184 a, 416 00:15:10,125 --> 00:15:10,945 time consuming, 417 00:15:11,404 --> 00:15:11,904 complicated, 418 00:15:14,500 --> 00:15:17,399 tools, technology, processes, people, chain management, 419 00:15:17,860 --> 00:15:19,620 all of them put together in a very 420 00:15:19,620 --> 00:15:20,120 tight, 421 00:15:20,740 --> 00:15:21,559 you know, schedule. 422 00:15:22,019 --> 00:15:24,899 Right? And, I'm very proud that as a 423 00:15:24,899 --> 00:15:26,519 UCI, you know, coworker 424 00:15:27,325 --> 00:15:29,725 to make everything happen. And I I I 425 00:15:29,725 --> 00:15:32,044 saw people so much motivated in spite of, 426 00:15:32,044 --> 00:15:33,404 you know, they have to do their regular 427 00:15:33,404 --> 00:15:34,705 job of patient care, 428 00:15:35,245 --> 00:15:35,904 our research, 429 00:15:36,445 --> 00:15:38,524 our other administrative work. Along with that, you 430 00:15:38,524 --> 00:15:40,205 know, they have to participate in all these 431 00:15:40,205 --> 00:15:41,940 meetings to make sure that those things are, 432 00:15:42,860 --> 00:15:45,059 they are done. So now now that we 433 00:15:45,059 --> 00:15:46,740 are we have all these things in place, 434 00:15:46,740 --> 00:15:47,940 you know, which is, again, 435 00:15:48,659 --> 00:15:51,220 greatest achievement from my perspective. In my career, 436 00:15:51,220 --> 00:15:53,159 I would say, I haven't seen any organization 437 00:15:53,220 --> 00:15:55,784 taking all these three major initiative all at 438 00:15:55,784 --> 00:15:57,125 the same time. Right? 439 00:15:57,584 --> 00:15:59,345 So now my focus is, okay, now that 440 00:15:59,345 --> 00:16:00,725 we have all the things, 441 00:16:02,625 --> 00:16:03,985 as you may know, you know, obviously, we 442 00:16:03,985 --> 00:16:05,745 have the thin margin and then how do 443 00:16:05,745 --> 00:16:08,225 we, you know, make sure that with, available 444 00:16:08,225 --> 00:16:08,725 resources, 445 00:16:09,279 --> 00:16:10,720 how do we make sure that we have 446 00:16:10,720 --> 00:16:11,620 all the appropriate 447 00:16:12,080 --> 00:16:14,399 tools technology available for our users, you know, 448 00:16:14,399 --> 00:16:16,820 without any specific lag or, 449 00:16:17,840 --> 00:16:20,179 or delays. Right? The the minute when we, 450 00:16:20,720 --> 00:16:23,279 have any delays in enabling them this feature 451 00:16:23,279 --> 00:16:23,779 functionality, 452 00:16:24,125 --> 00:16:25,725 people may lose interest and then they may 453 00:16:25,725 --> 00:16:27,884 not even come back. So how do I, 454 00:16:27,884 --> 00:16:29,725 you know, look at my team and then 455 00:16:29,725 --> 00:16:32,204 reorganize my team within my team and then 456 00:16:32,204 --> 00:16:34,445 motivate my team members to look at the 457 00:16:34,445 --> 00:16:37,404 opportunity to enable some of the tools technology 458 00:16:37,404 --> 00:16:38,519 so that, you know, we have, 459 00:16:39,160 --> 00:16:41,160 opportunity for our user community to do the 460 00:16:41,160 --> 00:16:43,879 self-service. And so that's another self-service analytics is 461 00:16:43,879 --> 00:16:46,620 another important thing that, we are strongly creating 462 00:16:46,920 --> 00:16:48,139 so that some of the, 463 00:16:48,600 --> 00:16:51,399 regular reporting request comes in. All those things 464 00:16:51,399 --> 00:16:52,300 will be, you know, 465 00:16:52,725 --> 00:16:53,225 relatively 466 00:16:53,845 --> 00:16:55,764 reduced. So my team can focus more mainly 467 00:16:55,764 --> 00:16:58,245 on advanced analytics as well as how do 468 00:16:58,245 --> 00:16:59,945 we partnership with the business 469 00:17:00,325 --> 00:17:02,804 so that we become more of a business 470 00:17:02,804 --> 00:17:05,630 analytics consultant to them than as a typical 471 00:17:05,849 --> 00:17:07,769 report writer through the ticket. Right? How do 472 00:17:07,769 --> 00:17:09,450 we sit with them to tell that, okay. 473 00:17:09,450 --> 00:17:11,609 I understand all the data structure behind it. 474 00:17:11,609 --> 00:17:13,769 I understand all the tools technology behind it. 475 00:17:13,769 --> 00:17:15,529 And then I understand to a large extent, 476 00:17:15,529 --> 00:17:16,009 you know, 477 00:17:16,809 --> 00:17:19,150 what a specific type of request comes in. 478 00:17:19,644 --> 00:17:21,964 So how about you and the business and, 479 00:17:22,525 --> 00:17:23,904 the analytics team partner, 480 00:17:24,845 --> 00:17:26,924 and be as a consultant and then build 481 00:17:26,924 --> 00:17:28,785 the solution so that that improve their, 482 00:17:29,565 --> 00:17:31,244 day to day processes? And how do we 483 00:17:31,244 --> 00:17:33,164 optimize some of the processes that they they 484 00:17:33,164 --> 00:17:35,099 have? And what is what are the analytics 485 00:17:35,419 --> 00:17:37,660 needed for them to track, monitor, and improve 486 00:17:37,660 --> 00:17:39,579 it? So that's where we want to go. 487 00:17:39,579 --> 00:17:40,720 So that's my focus. 488 00:17:41,099 --> 00:17:43,259 And how do I need to train my 489 00:17:43,259 --> 00:17:43,759 team, 490 00:17:44,460 --> 00:17:47,039 in those function? Right? Improving their communication 491 00:17:47,744 --> 00:17:49,904 or, create some of the roles like the 492 00:17:49,904 --> 00:17:52,065 product management or the business analyst type of 493 00:17:52,065 --> 00:17:54,625 roles, as well as to make sure that 494 00:17:54,625 --> 00:17:55,765 we have all the 495 00:17:56,144 --> 00:17:57,765 training and other things available, 496 00:17:58,384 --> 00:18:00,144 so that it's not like, you know, every 497 00:18:00,144 --> 00:18:02,384 time when some certain things are needed to 498 00:18:02,384 --> 00:18:05,059 be done in self-service analytics, every time people 499 00:18:05,059 --> 00:18:06,420 ping us. Rather, you know, we have a 500 00:18:06,420 --> 00:18:09,460 regular scheduled training across our tools and different, 501 00:18:09,700 --> 00:18:10,200 technology. 502 00:18:10,660 --> 00:18:13,299 So we enable the user community to use 503 00:18:13,299 --> 00:18:14,440 self-service analytics. 504 00:18:14,900 --> 00:18:16,740 So keeping those things in mind, you know, 505 00:18:16,740 --> 00:18:19,275 all these transformation need to happen and need 506 00:18:19,275 --> 00:18:20,575 to happen pretty quickly, 507 00:18:21,194 --> 00:18:23,755 so that, you know, we don't lose interest 508 00:18:23,755 --> 00:18:24,654 from the users, 509 00:18:25,515 --> 00:18:27,914 of using our tools and technology or use 510 00:18:28,154 --> 00:18:29,054 lose their interest, 511 00:18:29,595 --> 00:18:31,194 in terms of, you know, waiting for our 512 00:18:31,194 --> 00:18:33,269 reports analytics for a long time. So that's 513 00:18:33,269 --> 00:18:35,109 our goal, you know, to make sure that 514 00:18:35,109 --> 00:18:37,350 we enable the sales service analytics so that 515 00:18:37,350 --> 00:18:38,890 they can do certain things themselves. 516 00:18:39,190 --> 00:18:41,130 And then, be a business partner, 517 00:18:41,509 --> 00:18:43,369 with them so that we can enable their, 518 00:18:43,910 --> 00:18:46,549 or enable and then improve their process and, 519 00:18:46,710 --> 00:18:49,424 you know, other operational improvement. And also, 520 00:18:50,125 --> 00:18:52,765 leverage our team skills in advanced analytics, data 521 00:18:52,765 --> 00:18:54,285 science. So we have one data scientist on 522 00:18:54,285 --> 00:18:56,545 our team. You know, how do we leverage, 523 00:18:57,085 --> 00:18:59,744 some of the data content and then improve 524 00:18:59,884 --> 00:19:02,384 those things using those data science, attributes. 525 00:19:02,924 --> 00:19:04,500 Right? So those are the things that I'm 526 00:19:04,579 --> 00:19:06,900 currently focused on and, make sure that, you 527 00:19:06,900 --> 00:19:08,619 know, these things are in place for next 528 00:19:08,740 --> 00:19:10,500 I have we have a road map for 529 00:19:10,500 --> 00:19:13,059 next six months to twelve months. And, also, 530 00:19:13,059 --> 00:19:14,660 we are building the road map for the 531 00:19:14,660 --> 00:19:15,160 following, 532 00:19:15,700 --> 00:19:18,044 twelve month six months to make sure that 533 00:19:18,044 --> 00:19:20,125 we have all the things queued up and 534 00:19:20,125 --> 00:19:22,605 then validate ourselves. You know, we interact for 535 00:19:22,605 --> 00:19:23,085 the, 536 00:19:24,365 --> 00:19:26,125 the the aim the the things that we 537 00:19:26,125 --> 00:19:28,524 are aiming for and also making sure that, 538 00:19:29,005 --> 00:19:30,384 our users are always, 539 00:19:31,190 --> 00:19:34,069 open for free feedback and then, communicating with 540 00:19:34,069 --> 00:19:36,230 them on a regular basis, partnering with them 541 00:19:36,230 --> 00:19:37,990 on a regular basis to make sure that 542 00:19:37,990 --> 00:19:39,509 we are on track, and they are on 543 00:19:39,509 --> 00:19:41,609 track on their expectation for the analytics. 544 00:19:44,325 --> 00:19:46,005 Absolutely. I think that makes a ton of 545 00:19:46,005 --> 00:19:48,164 sense. You know, it's it's really, helpful to 546 00:19:48,164 --> 00:19:50,164 understand the whole process and everything that has 547 00:19:50,164 --> 00:19:50,904 gone into, 548 00:19:51,444 --> 00:19:54,085 creating, you know, these types of processes and 549 00:19:54,085 --> 00:19:56,220 systems for the data and for the technology 550 00:19:56,220 --> 00:19:58,059 as you've been implementing it in the new, 551 00:19:58,380 --> 00:20:00,079 spaces, in the newly acquired 552 00:20:00,380 --> 00:20:02,619 hospitals as well. Now I'm curious. You said 553 00:20:02,619 --> 00:20:04,460 you have created that six month road map 554 00:20:04,460 --> 00:20:06,319 as well as the twelve month road map. 555 00:20:06,779 --> 00:20:08,619 You know, how do you I guess, what 556 00:20:08,859 --> 00:20:10,554 if everything goes into plan, what do things 557 00:20:10,554 --> 00:20:12,234 look like a year from now? And, you 558 00:20:12,234 --> 00:20:13,994 know, how do you know that the investments 559 00:20:13,994 --> 00:20:15,694 you're putting in are going to actually, 560 00:20:16,394 --> 00:20:18,315 make sense and have a return on the 561 00:20:18,315 --> 00:20:19,054 back end? 562 00:20:19,434 --> 00:20:21,454 Yeah. I know. That that's a awesome question. 563 00:20:22,315 --> 00:20:22,815 So 564 00:20:25,070 --> 00:20:27,470 so fast forward six months. So from six 565 00:20:27,470 --> 00:20:29,250 months from now, you know, 566 00:20:29,549 --> 00:20:30,289 we expect 567 00:20:33,309 --> 00:20:35,710 our our report analytics request through the tickets, 568 00:20:35,710 --> 00:20:37,869 the traditional, you know, reporting needs, you know, 569 00:20:37,869 --> 00:20:39,234 which is, you know, maybe a give me 570 00:20:39,234 --> 00:20:41,355 a patient list, you know, for this with 571 00:20:41,355 --> 00:20:44,075 with this, specific attributes. So those kind of 572 00:20:44,075 --> 00:20:46,075 tickets, we are expecting it to reduce anything 573 00:20:46,075 --> 00:20:47,694 between 20 to 30 percentage. 574 00:20:48,634 --> 00:20:50,394 So what that also means is it is 575 00:20:50,394 --> 00:20:51,835 releasing some of our, 576 00:20:52,315 --> 00:20:53,375 team's availability, 577 00:20:54,590 --> 00:20:58,369 for doing much more sophisticated more, sophisticated analytics, 578 00:20:58,750 --> 00:21:01,090 report they may need. Right? That's number one. 579 00:21:01,150 --> 00:21:02,849 Number two is I'm seeing 580 00:21:03,309 --> 00:21:04,049 my team 581 00:21:04,670 --> 00:21:05,730 transforming ourselves 582 00:21:06,190 --> 00:21:08,750 as a business consultants, meaning that they have 583 00:21:08,750 --> 00:21:10,964 rich knowledge of the data structure and then 584 00:21:10,964 --> 00:21:12,664 the data behind it. And also, 585 00:21:13,125 --> 00:21:15,845 the patents of analytic request comes from different 586 00:21:15,845 --> 00:21:18,085 departments. So we have a broader understanding, not 587 00:21:18,085 --> 00:21:19,625 just focus on one department, 588 00:21:19,924 --> 00:21:21,765 but a broader focus on, you know, several 589 00:21:21,765 --> 00:21:23,759 departments. As you may know in any of 590 00:21:23,759 --> 00:21:26,019 the conversation, there is one department is slightly 591 00:21:26,240 --> 00:21:27,539 better in certain operational 592 00:21:28,000 --> 00:21:29,839 maturity than the other departments. So we can, 593 00:21:29,839 --> 00:21:32,240 you know, compare and contrast and help our 594 00:21:32,240 --> 00:21:32,740 businesses, 595 00:21:33,359 --> 00:21:35,279 to do it better. We can say show 596 00:21:35,279 --> 00:21:37,345 that as a benchmark to show, hey, here 597 00:21:37,345 --> 00:21:39,184 are the things that the other team is 598 00:21:39,184 --> 00:21:41,024 doing. You know, how about you trying this? 599 00:21:41,024 --> 00:21:42,484 Right? So we have that visibility. 600 00:21:43,024 --> 00:21:45,105 And also, the third thing is some of 601 00:21:45,105 --> 00:21:47,284 the focus thing that we want to create, 602 00:21:48,544 --> 00:21:50,625 that we strongly believe that will help. Say, 603 00:21:50,625 --> 00:21:51,284 for example, 604 00:21:52,000 --> 00:21:53,839 one of the key thing that I'm getting 605 00:21:53,839 --> 00:21:54,339 consistently 606 00:21:54,640 --> 00:21:57,220 across all the business leader is the translation, 607 00:21:58,160 --> 00:21:59,460 layer type of role. 608 00:21:59,919 --> 00:22:02,320 So the business talks plain English, you know, 609 00:22:02,320 --> 00:22:04,079 you know, very simple English. Yeah. I want 610 00:22:04,079 --> 00:22:05,539 to know about x y z. 611 00:22:05,974 --> 00:22:07,894 And then my team talks, you know, pure 612 00:22:07,894 --> 00:22:09,914 table and data structure. Right? 613 00:22:10,215 --> 00:22:12,134 And there's a big gap between these two. 614 00:22:12,134 --> 00:22:13,815 So how do we, you know, with this 615 00:22:13,815 --> 00:22:15,595 particular transformation, how do 616 00:22:15,894 --> 00:22:18,875 we, you know, enable ourselves, learn ourselves 617 00:22:19,410 --> 00:22:22,450 the business related functions? And then how do 618 00:22:22,450 --> 00:22:24,210 we make sure that we work with the 619 00:22:24,210 --> 00:22:27,170 application team? And then various other, you know, 620 00:22:27,170 --> 00:22:27,670 groups 621 00:22:28,210 --> 00:22:28,950 to understand 622 00:22:29,330 --> 00:22:31,890 what's the mapping between the business plain English 623 00:22:31,890 --> 00:22:33,430 need and then the analytics, 624 00:22:34,049 --> 00:22:35,625 or the technology? And how do you break 625 00:22:35,625 --> 00:22:37,865 that particular gap with the specific roles like 626 00:22:37,865 --> 00:22:39,945 the business analyst or the product manager type 627 00:22:39,945 --> 00:22:42,345 of role, where this person can understand and 628 00:22:42,345 --> 00:22:45,464 translate this information into a technical information, even 629 00:22:45,464 --> 00:22:47,224 though it's a very traditional, you know, system 630 00:22:47,224 --> 00:22:49,644 analyst or, you know, business analyst previously discussed. 631 00:22:49,819 --> 00:22:51,579 But we want to make it as much 632 00:22:51,579 --> 00:22:53,839 more than that. It's not just translation alone, 633 00:22:54,220 --> 00:22:56,299 but also, you know, help them to give, 634 00:22:56,460 --> 00:22:58,460 you know, kind of a translation plus the 635 00:22:58,460 --> 00:22:59,599 consulting type of, 636 00:23:00,140 --> 00:23:01,599 skill set. They they 637 00:23:02,059 --> 00:23:03,740 will, you know, groom them into that level 638 00:23:03,740 --> 00:23:04,934 of sophistication. 639 00:23:05,315 --> 00:23:06,934 So it will help them to, 640 00:23:07,474 --> 00:23:09,394 enable some of these data products, which will 641 00:23:09,394 --> 00:23:11,075 have a lifecycle to say that, hey, here's 642 00:23:11,075 --> 00:23:13,095 what we are going to do this particular, 643 00:23:13,715 --> 00:23:15,715 set of dashboards or a set of metrics 644 00:23:15,715 --> 00:23:17,909 that we want to follow through. And then 645 00:23:17,909 --> 00:23:19,669 this will help you to improve your business 646 00:23:19,669 --> 00:23:21,750 by seven percentage rate. So that's a level 647 00:23:21,750 --> 00:23:23,769 of sophistication that we want to, 648 00:23:24,389 --> 00:23:26,869 do. And then that's the that's a kind 649 00:23:26,869 --> 00:23:28,730 of a one of the outcome I'm expecting, 650 00:23:29,029 --> 00:23:30,869 not within the six months, maybe the following, 651 00:23:30,869 --> 00:23:33,194 you know, six months and one year. That's 652 00:23:33,194 --> 00:23:35,115 where we want to grow into. And then 653 00:23:35,115 --> 00:23:36,174 we'll be able to, 654 00:23:37,194 --> 00:23:39,034 you know, figure that out with within the 655 00:23:39,034 --> 00:23:41,274 existing team itself. Right? We our team has 656 00:23:41,274 --> 00:23:41,755 very, 657 00:23:43,755 --> 00:23:44,974 kind of a very, 658 00:23:45,580 --> 00:23:47,920 you know, deep knowledge about business, 659 00:23:48,299 --> 00:23:50,720 but it's matter of connecting the point to 660 00:23:50,860 --> 00:23:53,340 make sure that we expose that, you know, 661 00:23:53,340 --> 00:23:54,559 skill sets outside 662 00:23:54,940 --> 00:23:57,660 and making the collaboration between our business so 663 00:23:57,660 --> 00:23:59,100 that and that will make and that will 664 00:23:59,100 --> 00:24:01,505 happen. Yeah. So so the thing is, 665 00:24:02,045 --> 00:24:04,305 one is through the metrics that we can 666 00:24:04,365 --> 00:24:06,285 track and monitor the number of tickets that 667 00:24:06,285 --> 00:24:08,845 we'll be able to, you know, see, the 668 00:24:08,845 --> 00:24:11,005 immediate impact of that road map. The number 669 00:24:11,005 --> 00:24:12,205 two is now how we are going to 670 00:24:12,205 --> 00:24:14,609 transform it. And then by transforming you know, 671 00:24:14,690 --> 00:24:15,589 creating this, 672 00:24:16,289 --> 00:24:19,349 business translation layer, that will help us to, 673 00:24:19,410 --> 00:24:21,809 you know, accelerate some of this business consulting 674 00:24:21,809 --> 00:24:22,369 type of, 675 00:24:22,849 --> 00:24:23,349 roles 676 00:24:23,650 --> 00:24:25,410 much more better. That's good for our, you 677 00:24:25,410 --> 00:24:27,410 know, businesses as well as it's good for 678 00:24:27,410 --> 00:24:28,069 the organization, 679 00:24:28,924 --> 00:24:30,125 so that we are, you know, much more 680 00:24:30,125 --> 00:24:31,664 generative on organization. 681 00:24:34,845 --> 00:24:37,325 Absolutely. No. That that's incredible to hear, and 682 00:24:37,325 --> 00:24:39,164 I I think, it it's really cool to 683 00:24:39,164 --> 00:24:42,045 understand everything that goes into bringing these products 684 00:24:42,045 --> 00:24:42,809 to life. And, 685 00:24:43,370 --> 00:24:45,450 I'm excited to to see how it goes 686 00:24:45,450 --> 00:24:46,890 over the next year. So we'll have to 687 00:24:46,890 --> 00:24:47,789 have another conversation, 688 00:24:48,250 --> 00:24:50,410 kind of in debriefing and seeing where it's 689 00:24:50,410 --> 00:24:51,070 all headed. 690 00:24:52,090 --> 00:24:54,430 I'm curious. Yeah. Happy to share. Perfect. 691 00:24:55,370 --> 00:24:57,210 Before we wrap up here, I wanted to 692 00:24:57,210 --> 00:24:58,664 ask, you know, you've got a ton of 693 00:24:58,664 --> 00:24:59,164 experience, 694 00:24:59,625 --> 00:25:01,304 you know, throughout your career. And so what 695 00:25:01,304 --> 00:25:03,544 advice would you give all evolving leaders, especially 696 00:25:03,544 --> 00:25:06,105 in the health IT and technology space that 697 00:25:06,105 --> 00:25:07,065 are looking to, 698 00:25:07,544 --> 00:25:09,625 build their careers today and in the current 699 00:25:09,625 --> 00:25:11,644 environment? What advice do you have for them? 700 00:25:12,380 --> 00:25:13,599 Yeah. I I think, 701 00:25:14,059 --> 00:25:16,099 over a period of time, what I learned 702 00:25:16,099 --> 00:25:16,380 is, 703 00:25:17,980 --> 00:25:18,799 as a technologist, 704 00:25:19,099 --> 00:25:20,480 specifically data analytics 705 00:25:20,859 --> 00:25:21,359 technologist, 706 00:25:24,380 --> 00:25:25,039 the importance 707 00:25:26,684 --> 00:25:27,184 for 708 00:25:27,644 --> 00:25:31,164 any of the data analytics technologies to to 709 00:25:31,164 --> 00:25:34,125 be successful is to have a very tight 710 00:25:34,125 --> 00:25:34,625 partnership 711 00:25:35,085 --> 00:25:37,265 with the business team. That's very, very important. 712 00:25:37,565 --> 00:25:39,184 I mean, compared I mean, relatively 713 00:25:39,644 --> 00:25:42,309 to any other IT or technology department. Again, 714 00:25:42,369 --> 00:25:44,369 in some of the organization, data analytics, you 715 00:25:44,369 --> 00:25:46,690 know, doesn't report to the IT, but, I'm 716 00:25:46,690 --> 00:25:48,769 talking about, you know, the organization where, we 717 00:25:48,769 --> 00:25:49,830 are part of the IT. 718 00:25:51,170 --> 00:25:51,830 The important 719 00:25:52,529 --> 00:25:53,970 thing that we need to keep in mind 720 00:25:53,970 --> 00:25:56,585 is, you know, we are much more closer 721 00:25:57,044 --> 00:25:59,525 to the business team because we are kind 722 00:25:59,525 --> 00:26:02,244 of in the gray area between the business 723 00:26:02,244 --> 00:26:03,544 and then the pure technology. 724 00:26:03,845 --> 00:26:06,164 So what that means is the closer we 725 00:26:06,164 --> 00:26:07,144 get to the business 726 00:26:07,684 --> 00:26:09,464 and, you know, leverage 727 00:26:09,779 --> 00:26:12,500 all of our technology knowledge along with the 728 00:26:12,500 --> 00:26:15,460 business challenges our business team is having and 729 00:26:15,460 --> 00:26:17,960 then build that partnership on a regular basis, 730 00:26:19,299 --> 00:26:20,759 and then deliver the value 731 00:26:21,140 --> 00:26:23,880 through that particular process. And also it is 732 00:26:24,744 --> 00:26:27,144 imperative for us to make sure that we 733 00:26:27,144 --> 00:26:28,845 have, on a regular basis, 734 00:26:29,625 --> 00:26:31,865 keep in touch with the leaders. Regular basis 735 00:26:31,865 --> 00:26:33,644 in a sense in a really regular basis, 736 00:26:33,704 --> 00:26:34,765 regular cadence, 737 00:26:35,544 --> 00:26:36,984 one on one with, you know, whether it's 738 00:26:36,984 --> 00:26:39,769 a c suite or the VPs or whatever 739 00:26:39,769 --> 00:26:40,170 different, 740 00:26:40,650 --> 00:26:42,750 you know, senior leadership role in your organization. 741 00:26:43,690 --> 00:26:44,509 Be with them 742 00:26:44,890 --> 00:26:45,390 every 743 00:26:45,769 --> 00:26:46,670 month minimum, 744 00:26:47,529 --> 00:26:48,910 to make sure that we understand 745 00:26:49,930 --> 00:26:50,750 their challenges 746 00:26:51,210 --> 00:26:51,710 today 747 00:26:52,250 --> 00:26:54,615 and how do we what are the opportunities 748 00:26:54,615 --> 00:26:57,195 we have to solve it through data. Right? 749 00:26:57,255 --> 00:26:57,894 So in, 750 00:26:59,575 --> 00:27:01,815 as as as we all know, health care 751 00:27:01,815 --> 00:27:04,775 is a very data intense business. Right? Everything 752 00:27:04,775 --> 00:27:05,515 is data. 753 00:27:05,815 --> 00:27:06,315 So 754 00:27:06,869 --> 00:27:08,789 and it's very, very rare that anybody's gonna 755 00:27:08,789 --> 00:27:10,230 tell them it's not a data problem or 756 00:27:10,230 --> 00:27:11,690 something. So it's kind of a, 757 00:27:12,230 --> 00:27:14,630 you know, it's it's it's obvious that as 758 00:27:14,630 --> 00:27:15,609 a data leader, 759 00:27:16,309 --> 00:27:18,150 you know, work with the business leaders, we 760 00:27:18,150 --> 00:27:18,944 have a tight 761 00:27:19,984 --> 00:27:22,144 relationship with them, and then be there to 762 00:27:22,144 --> 00:27:23,684 solve their challenges, 763 00:27:24,304 --> 00:27:27,184 in operations or in a strategical level. That's 764 00:27:27,184 --> 00:27:30,144 number one. Number two is within our team 765 00:27:30,144 --> 00:27:30,644 also, 766 00:27:31,105 --> 00:27:31,764 you know, 767 00:27:32,065 --> 00:27:33,284 keep them as a 768 00:27:33,849 --> 00:27:36,029 a very broader skill set. 769 00:27:36,490 --> 00:27:37,950 We don't want a specific 770 00:27:39,129 --> 00:27:42,409 tool operator type of skills, meaning we don't 771 00:27:42,409 --> 00:27:44,589 need you know, I'm I'm a informatica developer 772 00:27:44,649 --> 00:27:46,305 or I'm a, you know, x y z 773 00:27:46,625 --> 00:27:48,625 developer type of role. Rather, we need to 774 00:27:48,625 --> 00:27:50,565 look at it as a, you know, broader 775 00:27:50,865 --> 00:27:51,684 data analyst. 776 00:27:52,225 --> 00:27:55,025 This person should think through from the start, 777 00:27:55,025 --> 00:27:56,805 you know, how this data is created 778 00:27:57,265 --> 00:28:00,144 till the analytics is delivered. Right? We need 779 00:28:00,144 --> 00:28:00,725 to have 780 00:28:01,039 --> 00:28:02,819 team members that has the wide, 781 00:28:04,159 --> 00:28:06,240 aspect of the data, and then how do 782 00:28:06,240 --> 00:28:07,059 we, you know, 783 00:28:07,359 --> 00:28:09,220 get that particular skill set 784 00:28:09,519 --> 00:28:11,599 built, not as a, you know, train for 785 00:28:11,599 --> 00:28:13,679 a specific tool set or a specific tool 786 00:28:13,679 --> 00:28:15,585 alone. So have that kind of a broader 787 00:28:15,585 --> 00:28:18,464 overview. This also will motivate our team members 788 00:28:18,464 --> 00:28:19,125 to see 789 00:28:19,424 --> 00:28:20,945 if it here is what the business they 790 00:28:20,945 --> 00:28:23,345 had. And then with my data knowledge and 791 00:28:23,345 --> 00:28:25,045 then their business knowledge combined, 792 00:28:25,585 --> 00:28:28,065 we solve that particular business problem with data. 793 00:28:28,065 --> 00:28:30,519 So that gives them, you know, a good 794 00:28:30,519 --> 00:28:33,079 understanding of how the business stands as well 795 00:28:33,079 --> 00:28:34,539 as a good motivation of 796 00:28:35,000 --> 00:28:35,740 how they 797 00:28:36,359 --> 00:28:39,720 report a analytic solution solving business problem. K? 798 00:28:39,720 --> 00:28:42,539 So I I would encourage our leaders to, 799 00:28:43,240 --> 00:28:44,619 do that for our team, 800 00:28:45,055 --> 00:28:46,575 so that, you know, we have that kind 801 00:28:46,575 --> 00:28:47,795 of a motivated team. 802 00:28:48,974 --> 00:28:50,335 And then the last one I would say 803 00:28:50,335 --> 00:28:51,234 is, you know, 804 00:28:52,494 --> 00:28:54,335 the important thing for all of us is, 805 00:28:54,575 --> 00:28:56,815 the patient care or the, you know, research 806 00:28:56,815 --> 00:28:58,035 outcome and other things. 807 00:28:58,335 --> 00:28:58,835 So 808 00:28:59,559 --> 00:29:02,119 that should be our foundational thing. We are 809 00:29:02,119 --> 00:29:04,299 here to help enable our organization 810 00:29:04,839 --> 00:29:05,400 to do, 811 00:29:05,960 --> 00:29:08,059 you know, amazing patient care 812 00:29:08,680 --> 00:29:09,980 with high quality. 813 00:29:10,839 --> 00:29:11,980 So that's the foundation. 814 00:29:13,195 --> 00:29:15,994 So that should be the foundation for all 815 00:29:15,994 --> 00:29:18,335 the activities or the things that we do 816 00:29:18,394 --> 00:29:19,134 in the organization. 817 00:29:19,674 --> 00:29:21,674 So that's the foundation. So I I would 818 00:29:21,674 --> 00:29:22,894 also encourage, 819 00:29:23,914 --> 00:29:26,154 our leaders to think through that particular, you 820 00:29:26,154 --> 00:29:28,174 know, process before making any decision 821 00:29:28,750 --> 00:29:30,750 how possibly this is going to impact our 822 00:29:30,750 --> 00:29:31,250 patients, 823 00:29:32,029 --> 00:29:34,190 and how we are going to enable them 824 00:29:34,190 --> 00:29:35,470 in such a way that, 825 00:29:36,269 --> 00:29:37,869 you know, it it it will simplify some 826 00:29:37,869 --> 00:29:38,349 of their, 827 00:29:39,710 --> 00:29:41,535 activity that we need to interact with, 828 00:29:42,095 --> 00:29:44,414 whether it's, you know, our MyChart or any 829 00:29:44,414 --> 00:29:47,055 of our application or using our analytics. So 830 00:29:47,055 --> 00:29:48,734 how do we simplify in such a way 831 00:29:48,734 --> 00:29:50,815 that, you know, that will enable them and 832 00:29:50,815 --> 00:29:52,595 then keep them satisfied, 833 00:29:53,295 --> 00:29:53,955 and then, 834 00:29:54,730 --> 00:29:57,150 help that that'll help a lot from our, 835 00:29:57,690 --> 00:29:59,869 health care industry perspective too. 836 00:30:01,690 --> 00:30:04,009 Absolutely. That makes a ton of sense. Myel, 837 00:30:04,009 --> 00:30:05,210 thank you so much for joining us on 838 00:30:05,210 --> 00:30:07,450 the podcast today. This has been a really 839 00:30:07,450 --> 00:30:09,289 fun conversation. I I've learned a lot, and 840 00:30:09,289 --> 00:30:10,704 I look forward to connecting with you again 841 00:30:10,704 --> 00:30:13,105 soon. And then, you know, really continuing to 842 00:30:13,105 --> 00:30:15,365 to learn and have this conversation ongoing. 843 00:30:15,984 --> 00:30:18,384 Yeah. Thanks very much, for your thoughtful questions, 844 00:30:18,384 --> 00:30:20,164 Laura. Really appreciate that.