1 00:00:00,000 --> 00:00:05,920 Beautiful crisp 2 00:00:02,639 --> 00:00:08,400 late or early early summer day with what 3 00:00:05,920 --> 00:00:12,000 was like 60° outside. I'm not really 4 00:00:08,400 --> 00:00:14,080 sure what's happening. Anyhow, um so the 5 00:00:12,000 --> 00:00:18,560 previous meeting was December 19th of 6 00:00:14,080 --> 00:00:20,160 2025. As for some of you who who's uh uh 7 00:00:18,560 --> 00:00:21,840 this is the first attendance to these 8 00:00:20,160 --> 00:00:26,240 meetings, we hold these meetings twice a 9 00:00:21,840 --> 00:00:28,240 year. uh once uh the second quarter of 10 00:00:26,240 --> 00:00:30,560 the year and then the second time is the 11 00:00:28,240 --> 00:00:31,840 fourth quarter of the year. Um so the 12 00:00:30,560 --> 00:00:33,520 last time we had this meeting was 13 00:00:31,840 --> 00:00:35,280 December. The next time we'll be having 14 00:00:33,520 --> 00:00:38,800 this meeting again will be December of 15 00:00:35,280 --> 00:00:40,879 2026. So the minutes from the last 16 00:00:38,800 --> 00:00:42,960 minute from the last meeting were 17 00:00:40,879 --> 00:00:44,559 communicated. Um are there any 18 00:00:42,960 --> 00:00:48,320 questions, comments or concerns about 19 00:00:44,559 --> 00:00:52,079 those minutes um that we should be 20 00:00:48,320 --> 00:00:53,360 brought up today? Hey Mark, how are you? 21 00:00:52,079 --> 00:00:55,440 Good. How are you doing? 22 00:00:53,360 --> 00:00:57,199 » We're good. We just re uh just barely 23 00:00:55,440 --> 00:00:59,440 got started. So, yeah, I didn't miss 24 00:00:57,199 --> 00:01:01,920 much. So, 25 00:00:59,440 --> 00:01:04,239 » Okay. Seeing no uh questions, comments, 26 00:01:01,920 --> 00:01:07,680 or concerns on those, we'll move forward 27 00:01:04,239 --> 00:01:11,360 with um administrative updates. So to 28 00:01:07,680 --> 00:01:13,119 provide start with the SLDS grants um 29 00:01:11,360 --> 00:01:16,159 just a reminder that the operational 30 00:01:13,119 --> 00:01:19,520 considerations for the bridge grant uh 31 00:01:16,159 --> 00:01:22,479 is that it was moved from October of 32 00:01:19,520 --> 00:01:25,119 2023 through September of 2027. That's 33 00:01:22,479 --> 00:01:27,920 the full duration of the grant period of 34 00:01:25,119 --> 00:01:30,640 time of performance and progress on that 35 00:01:27,920 --> 00:01:35,360 is that we there was uh some federal 36 00:01:30,640 --> 00:01:38,799 budget impacts um at the um federal 37 00:01:35,360 --> 00:01:41,600 education level. Um and so therefore 38 00:01:38,799 --> 00:01:44,479 we're behind uh on progress on that. We 39 00:01:41,600 --> 00:01:47,119 went from a team of 10 plus to just two 40 00:01:44,479 --> 00:01:49,280 individuals. Uh and unfortunately one of 41 00:01:47,119 --> 00:01:52,720 the individuals who one of those two 42 00:01:49,280 --> 00:01:54,799 individuals who was assisting us on the 43 00:01:52,720 --> 00:01:58,399 uh master person index algorithm 44 00:01:54,799 --> 00:02:01,200 component um had to leave the project. 45 00:01:58,399 --> 00:02:04,079 Um the third party vendor that we 46 00:02:01,200 --> 00:02:06,320 utilized to assist us in building out 47 00:02:04,079 --> 00:02:08,720 bridge was bought out by another third 48 00:02:06,320 --> 00:02:11,440 party vendor and unfortunately their 49 00:02:08,720 --> 00:02:13,920 contract conflicted with the new uh 50 00:02:11,440 --> 00:02:16,640 employee rules and regulations of the 51 00:02:13,920 --> 00:02:18,560 third party vendor. And so they had to 52 00:02:16,640 --> 00:02:21,520 leave the project and leave the company. 53 00:02:18,560 --> 00:02:23,200 So we were able to get a new resource 54 00:02:21,520 --> 00:02:25,680 through Burwood. Uh but unfortunately 55 00:02:23,200 --> 00:02:27,920 that resource uh had to obviously be 56 00:02:25,680 --> 00:02:30,000 onboarded to the project and on boarded 57 00:02:27,920 --> 00:02:33,760 into this very specific component of the 58 00:02:30,000 --> 00:02:36,720 project. Um so that took time and effort 59 00:02:33,760 --> 00:02:39,680 um and obviously uh development time as 60 00:02:36,720 --> 00:02:41,840 well. So as of June the delay in the 61 00:02:39,680 --> 00:02:45,040 progress is not an emergency. However, 62 00:02:41,840 --> 00:02:48,800 it is significant and material and we'll 63 00:02:45,040 --> 00:02:51,360 need to obviously um significantly hurry 64 00:02:48,800 --> 00:02:56,080 in the next months to um catch up and 65 00:02:51,360 --> 00:02:58,080 ailerate that uh deficit. So, uh but uh 66 00:02:56,080 --> 00:03:01,200 again, not an emergency at this time. 67 00:02:58,080 --> 00:03:02,879 So, and Jay will provide further update 68 00:03:01,200 --> 00:03:05,599 uh in his technology update on where 69 00:03:02,879 --> 00:03:07,840 we're at with Bridge um in the future. 70 00:03:05,599 --> 00:03:09,920 So, 71 00:03:07,840 --> 00:03:12,720 so that's where we're at with the 72 00:03:09,920 --> 00:03:15,920 development work for the bridge 73 00:03:12,720 --> 00:03:18,319 transactional system. Um, I'll provide 74 00:03:15,920 --> 00:03:21,200 now an update on the legal framework 75 00:03:18,319 --> 00:03:25,040 which is what is going to allow us to 76 00:03:21,200 --> 00:03:28,640 execute the operational goals of bridge 77 00:03:25,040 --> 00:03:31,200 um legally. So because of SP 195 78 00:03:28,640 --> 00:03:33,599 obviously the impact there was that we 79 00:03:31,200 --> 00:03:35,440 are allowed to undertake the operational 80 00:03:33,599 --> 00:03:38,480 activities that we defined under the 81 00:03:35,440 --> 00:03:40,640 bridge project. Um so generally speaking 82 00:03:38,480 --> 00:03:43,200 this will allow us to onboard 83 00:03:40,640 --> 00:03:46,000 participating state agencies. Um as 84 00:03:43,200 --> 00:03:47,519 we've previously stated bridge is is a 85 00:03:46,000 --> 00:03:50,879 voluntary 86 00:03:47,519 --> 00:03:53,040 um data system that we are going to be 87 00:03:50,879 --> 00:03:55,840 creating and building. Um it is not like 88 00:03:53,040 --> 00:03:59,680 the UDRC legacy system uh where the data 89 00:03:55,840 --> 00:04:03,040 partners are defined by code. Um bridge 90 00:03:59,680 --> 00:04:08,080 is is voluntary. So um we are in the 91 00:04:03,040 --> 00:04:10,480 process of rulem. Um so per 19 SP95 we 92 00:04:08,080 --> 00:04:12,640 had to create rulem uh rules or or 93 00:04:10,480 --> 00:04:17,600 verbiage or define the verbiage of the 94 00:04:12,640 --> 00:04:20,560 rulem uh for the SP 195 uh specifically 95 00:04:17,600 --> 00:04:23,440 uh related to the legal framework that 96 00:04:20,560 --> 00:04:25,600 we were going to create an institute for 97 00:04:23,440 --> 00:04:28,800 bridge. So the update there is that the 98 00:04:25,600 --> 00:04:32,960 draft administrative rules um that's 99 00:04:28,800 --> 00:04:36,240 completed uh we sent it out to our data 100 00:04:32,960 --> 00:04:39,680 partners for uh review. So that was uh 101 00:04:36,240 --> 00:04:42,160 all of you here um and we gave uh this 102 00:04:39,680 --> 00:04:47,280 group until July 15th to provide 103 00:04:42,160 --> 00:04:50,960 feedback um if uh if any. Um so we are 104 00:04:47,280 --> 00:04:53,440 we're waiting for that time to elapse. 105 00:04:50,960 --> 00:04:56,800 Um and then we will finalize the verbage 106 00:04:53,440 --> 00:04:59,759 by August 1st. Uh and then we will be 107 00:04:56,800 --> 00:05:02,240 seeking approval by the Yushi board on 108 00:04:59,759 --> 00:05:05,040 the September 2026 109 00:05:02,240 --> 00:05:08,400 uh board of higher education um board 110 00:05:05,040 --> 00:05:10,960 meeting. So after that um hopefully 111 00:05:08,400 --> 00:05:13,840 obviously it passes uh and they approve 112 00:05:10,960 --> 00:05:17,600 of it and then we will we will publish 113 00:05:13,840 --> 00:05:20,080 um the rule um as completed um at that 114 00:05:17,600 --> 00:05:22,080 point in time. So 115 00:05:20,080 --> 00:05:24,960 any questions, comments or concerns 116 00:05:22,080 --> 00:05:28,199 about that rule making process, 117 00:05:24,960 --> 00:05:28,199 the verbiage. 118 00:05:30,720 --> 00:05:33,720 Okay, 119 00:05:35,120 --> 00:05:40,400 moving along the administrative updates. 120 00:05:37,600 --> 00:05:43,360 Um I do have some really good news um 121 00:05:40,400 --> 00:05:48,240 about new forthcoming data to the UDRC 122 00:05:43,360 --> 00:05:50,560 legacy system. Um so and I the the 123 00:05:48,240 --> 00:05:53,680 latest news most up up to date on the 124 00:05:50,560 --> 00:05:56,000 home visiting program um here is that we 125 00:05:53,680 --> 00:05:58,400 actually did receive that today. Um so 126 00:05:56,000 --> 00:06:00,080 it's been signed and it's all completed. 127 00:05:58,400 --> 00:06:01,120 Uh so we'll be moving forward with 128 00:06:00,080 --> 00:06:02,639 coordinating with the department of 129 00:06:01,120 --> 00:06:06,319 health and human services in receiving 130 00:06:02,639 --> 00:06:08,800 that data uh in the coming weeks. Um so 131 00:06:06,319 --> 00:06:10,000 the home visiting program is a program 132 00:06:08,800 --> 00:06:12,880 that is supported by the department of 133 00:06:10,000 --> 00:06:14,479 health and human services. Um, Dakota, 134 00:06:12,880 --> 00:06:16,800 do you want maybe I I I've kind of 135 00:06:14,479 --> 00:06:18,639 provided here the a boilerplate 136 00:06:16,800 --> 00:06:21,199 definition of home visiting program, but 137 00:06:18,639 --> 00:06:23,680 maybe you probably do a more justice in 138 00:06:21,199 --> 00:06:25,520 in providing a a a definition for what 139 00:06:23,680 --> 00:06:28,080 the home visiting program is. 140 00:06:25,520 --> 00:06:29,600 » Yeah, sure thing. Um, so there home 141 00:06:28,080 --> 00:06:31,120 visiting is a very general term. So, the 142 00:06:29,600 --> 00:06:32,479 home visiting program that's specific to 143 00:06:31,120 --> 00:06:35,759 the office of early childhood over at 144 00:06:32,479 --> 00:06:37,120 DHS is the MCV funded um home visiting, 145 00:06:35,759 --> 00:06:39,360 which is the maternal infant early 146 00:06:37,120 --> 00:06:42,960 childhood home visiting grant uh through 147 00:06:39,360 --> 00:06:44,880 the feds under HERSA. Um and we are in 148 00:06:42,960 --> 00:06:46,720 almost every county in the state. We're 149 00:06:44,880 --> 00:06:48,400 missing just a couple. Um but those 150 00:06:46,720 --> 00:06:50,800 consist of the parents' teachers 151 00:06:48,400 --> 00:06:52,479 program, uh the family spirit program, 152 00:06:50,800 --> 00:06:54,560 the nurse family partnership program, 153 00:06:52,479 --> 00:06:56,000 and soon to be MESH maternal early 154 00:06:54,560 --> 00:06:57,440 childhood sustained home visiting, which 155 00:06:56,000 --> 00:06:59,599 is another nurse-based home visiting 156 00:06:57,440 --> 00:07:01,680 model. Um all of the models are focused 157 00:06:59,599 --> 00:07:04,000 on uh providing home visiting services 158 00:07:01,680 --> 00:07:06,639 to parents uh with children uh either 159 00:07:04,000 --> 00:07:08,319 prenatal or age 0 to 5 uh to support 160 00:07:06,639 --> 00:07:10,479 them on their parenting journey and make 161 00:07:08,319 --> 00:07:12,080 sure those kids are as ready for uh 162 00:07:10,479 --> 00:07:14,400 kindergarten and school and future 163 00:07:12,080 --> 00:07:16,160 school success as possible. Um and they 164 00:07:14,400 --> 00:07:17,199 do a lot of different screening work, a 165 00:07:16,160 --> 00:07:18,960 lots of connecting with different 166 00:07:17,199 --> 00:07:20,960 resources, but at the end of the day, um 167 00:07:18,960 --> 00:07:22,639 it is about supporting those parents to 168 00:07:20,960 --> 00:07:25,440 become uh the best parents they can 169 00:07:22,639 --> 00:07:27,520 possibly be for their children. 170 00:07:25,440 --> 00:07:30,800 » Great. Yeah. So, we're really excited. 171 00:07:27,520 --> 00:07:32,080 Um, so some of you may be aware that 172 00:07:30,800 --> 00:07:33,919 Department of Health and Human Services 173 00:07:32,080 --> 00:07:37,840 manages the EKID system or early 174 00:07:33,919 --> 00:07:40,160 education system. Um, this is this is 175 00:07:37,840 --> 00:07:42,720 part of a collaboration between us and 176 00:07:40,160 --> 00:07:45,520 Ekids in receiving more and more of the 177 00:07:42,720 --> 00:07:48,000 same data that they receive. Um, and 178 00:07:45,520 --> 00:07:51,120 Ekkids focuses on analytics, on 179 00:07:48,000 --> 00:07:53,039 reporting, and UDRC obviously focuses on 180 00:07:51,120 --> 00:07:55,680 research. Um, and so it's sort of 181 00:07:53,039 --> 00:07:57,360 synergistic the work that we're doing. 182 00:07:55,680 --> 00:07:59,520 uh whereas they're focused more on 183 00:07:57,360 --> 00:08:02,479 operations uh questions that the 184 00:07:59,520 --> 00:08:06,400 operations might have. We focus more on 185 00:08:02,479 --> 00:08:09,360 research uh policy questions that um the 186 00:08:06,400 --> 00:08:11,680 sort of early education world may have. 187 00:08:09,360 --> 00:08:13,120 So uh looking forward to obviously 188 00:08:11,680 --> 00:08:16,160 receiving that data in the in the coming 189 00:08:13,120 --> 00:08:18,560 weeks um and integrating into our system 190 00:08:16,160 --> 00:08:20,400 and obviously making it available for 191 00:08:18,560 --> 00:08:22,800 our own researchers as well as external 192 00:08:20,400 --> 00:08:25,440 researchers for for to conduct research 193 00:08:22,800 --> 00:08:29,520 in that realm. So 194 00:08:25,440 --> 00:08:32,080 moving along uh to other data sets that 195 00:08:29,520 --> 00:08:32,880 we will be receiving uh we are also in 196 00:08:32,080 --> 00:08:34,320 coordination with the department of 197 00:08:32,880 --> 00:08:36,800 health and human services in receiving 198 00:08:34,320 --> 00:08:39,279 the all pairs claims database. We're 199 00:08:36,800 --> 00:08:42,240 very very excited about this data set. 200 00:08:39,279 --> 00:08:45,040 It contains a data from health insurance 201 00:08:42,240 --> 00:08:46,640 carriers including Medicaid and third 202 00:08:45,040 --> 00:08:51,040 party administrators here in the state 203 00:08:46,640 --> 00:08:53,200 of Utah. Um this these data are very 204 00:08:51,040 --> 00:08:56,160 holistic uh and include anything 205 00:08:53,200 --> 00:08:58,640 everything from diagnosis and treatments 206 00:08:56,160 --> 00:09:00,959 to cost of care, location of care and so 207 00:08:58,640 --> 00:09:04,640 on. If I remember correctly, the table 208 00:09:00,959 --> 00:09:07,279 is 1,500 variables wide. Um so it's 209 00:09:04,640 --> 00:09:10,480 incredibly detailed as to the amount of 210 00:09:07,279 --> 00:09:13,760 information that is included uh in in 211 00:09:10,480 --> 00:09:16,080 there. Um where where are we with this 212 00:09:13,760 --> 00:09:18,080 one is that we are we have drafted an 213 00:09:16,080 --> 00:09:20,320 addendum to the masterou for department 214 00:09:18,080 --> 00:09:22,000 of health and human services and they're 215 00:09:20,320 --> 00:09:25,760 in the process right now of reviewing 216 00:09:22,000 --> 00:09:26,959 that and um hopefully signing it and 217 00:09:25,760 --> 00:09:30,640 then sending it back to us for 218 00:09:26,959 --> 00:09:35,200 signatures. So at that point in time. So 219 00:09:30,640 --> 00:09:36,800 um then the the last um data set that we 220 00:09:35,200 --> 00:09:39,040 are 221 00:09:36,800 --> 00:09:40,880 additionally coordinating with the HHS 222 00:09:39,040 --> 00:09:43,360 to receive is the hospital facilities 223 00:09:40,880 --> 00:09:45,360 database. Uh so this is similar to the 224 00:09:43,360 --> 00:09:48,560 all pairs claims database but from the 225 00:09:45,360 --> 00:09:50,800 hospital side of things. Um so it has um 226 00:09:48,560 --> 00:09:53,200 records for all licensed hospitals, 227 00:09:50,800 --> 00:09:55,920 emergency rooms and ambulatory surgery 228 00:09:53,200 --> 00:09:58,160 centers in Utah. Uh inatient records 229 00:09:55,920 --> 00:09:59,680 date from 1992 and other encounters from 230 00:09:58,160 --> 00:10:02,880 1996. 231 00:09:59,680 --> 00:10:04,560 Um they represent all hospitalizations, 232 00:10:02,880 --> 00:10:06,320 emergency department visits and 233 00:10:04,560 --> 00:10:08,080 ambulatory surgeries and diagnosis 234 00:10:06,320 --> 00:10:13,200 procedures performed in Utah regardless 235 00:10:08,080 --> 00:10:15,200 of pair. Um so again similarly we are we 236 00:10:13,200 --> 00:10:16,560 have communicated to department health 237 00:10:15,200 --> 00:10:19,760 and human services an addendum to the 238 00:10:16,560 --> 00:10:21,920 master NYU they're reviewing um 239 00:10:19,760 --> 00:10:25,600 hopefully signing and then sending back 240 00:10:21,920 --> 00:10:27,600 to us for signatures. So super excited 241 00:10:25,600 --> 00:10:30,399 about receiving all of this new data 242 00:10:27,600 --> 00:10:33,760 here at the UDRC. the old pairs claims 243 00:10:30,399 --> 00:10:36,240 database will be a huge game changer for 244 00:10:33,760 --> 00:10:39,760 the for the sort of research questions 245 00:10:36,240 --> 00:10:43,279 we might be able to answer and a and ask 246 00:10:39,760 --> 00:10:48,000 as well. Um so an example might be we 247 00:10:43,279 --> 00:10:52,079 have ASQ data from uh from DHS as well. 248 00:10:48,000 --> 00:10:54,560 Uh we see a child receiving a screening. 249 00:10:52,079 --> 00:10:58,720 uh we might be able to see also that 250 00:10:54,560 --> 00:11:01,519 they subsequently received diagnosis um 251 00:10:58,720 --> 00:11:05,040 and then we will be able to uh link that 252 00:11:01,519 --> 00:11:07,680 into their K through2 uh performance and 253 00:11:05,040 --> 00:11:10,160 and be able to you know answer questions 254 00:11:07,680 --> 00:11:13,040 and ask questions that we had never been 255 00:11:10,160 --> 00:11:16,320 able to before in the past. So really 256 00:11:13,040 --> 00:11:18,000 excited about that. So any questions, 257 00:11:16,320 --> 00:11:20,640 comments or concerns about those data 258 00:11:18,000 --> 00:11:23,200 sets that are coming to the UDRC here in 259 00:11:20,640 --> 00:11:26,600 hopefully in uh in the next month or 260 00:11:23,200 --> 00:11:26,600 two. So 261 00:11:26,640 --> 00:11:31,360 okay, 262 00:11:29,040 --> 00:11:34,079 in addition to provide an update on some 263 00:11:31,360 --> 00:11:36,000 data that we're pursuing. So this is not 264 00:11:34,079 --> 00:11:37,839 a guarantee that these are we just 265 00:11:36,000 --> 00:11:42,399 wanted to communicate to this group 266 00:11:37,839 --> 00:11:45,200 about data that we are looking to um to 267 00:11:42,399 --> 00:11:46,320 receive uh and we're we're coordinating 268 00:11:45,200 --> 00:11:48,640 with the Department of Health and Human 269 00:11:46,320 --> 00:11:50,560 Services on this one as well. Um so 270 00:11:48,640 --> 00:11:53,040 we're we're looking to receive Head 271 00:11:50,560 --> 00:11:55,120 Start data. Again, this is part of 272 00:11:53,040 --> 00:11:59,360 receiving more of the same data that 273 00:11:55,120 --> 00:12:03,920 EKIDS receives um to support their their 274 00:11:59,360 --> 00:12:07,360 efforts and and also ours. Um so Grace 275 00:12:03,920 --> 00:12:09,920 uh Dakota uh has been really 276 00:12:07,360 --> 00:12:14,320 instrumental in connecting us with the 277 00:12:09,920 --> 00:12:16,320 Head Start um associations. Um and we've 278 00:12:14,320 --> 00:12:19,279 just at the very very beginning stages 279 00:12:16,320 --> 00:12:22,880 of this whole process of reaching out to 280 00:12:19,279 --> 00:12:25,839 them and asking if um we'd be a we'd be 281 00:12:22,880 --> 00:12:27,680 able to present to them um our our value 282 00:12:25,839 --> 00:12:30,160 proposition for receiving data into the 283 00:12:27,680 --> 00:12:31,920 into the UDRC system. Uh so this is very 284 00:12:30,160 --> 00:12:33,440 very early stages. They could just they 285 00:12:31,920 --> 00:12:34,800 could they could ultimately say no we're 286 00:12:33,440 --> 00:12:36,639 not interested and that would be 287 00:12:34,800 --> 00:12:38,399 perfectly fine but wanted to provide an 288 00:12:36,639 --> 00:12:43,079 update to this group that we are 289 00:12:38,399 --> 00:12:43,079 pursuing that data as well. So 290 00:12:44,800 --> 00:12:49,120 okay those are all the administrative 291 00:12:46,800 --> 00:12:50,880 updates I had. Um I'm going to pass it 292 00:12:49,120 --> 00:12:52,639 over to Jay now for the technology 293 00:12:50,880 --> 00:12:55,120 update. 294 00:12:52,639 --> 00:12:58,880 » Okay. 295 00:12:55,120 --> 00:13:03,040 » Hello everyone. Uh my update starts with 296 00:12:58,880 --> 00:13:05,440 uh UDRC legacy system uh which is the 297 00:13:03,040 --> 00:13:08,959 backbone of UDRC 298 00:13:05,440 --> 00:13:11,120 uh bridge. Uh so currently my team and I 299 00:13:08,959 --> 00:13:13,680 are maintaining and supporting the 300 00:13:11,120 --> 00:13:17,920 existing operational and research needs 301 00:13:13,680 --> 00:13:20,160 for legacy and any upgrades to the cloud 302 00:13:17,920 --> 00:13:23,360 architecture or any components within 303 00:13:20,160 --> 00:13:26,639 legacy system are being uh provided as 304 00:13:23,360 --> 00:13:28,399 and when needed. uh but uh with this I 305 00:13:26,639 --> 00:13:32,720 also wanted to provide an update on the 306 00:13:28,399 --> 00:13:34,720 legacy MPI. So the legacy MPI is uh 307 00:13:32,720 --> 00:13:39,040 something that we've worked on or 308 00:13:34,720 --> 00:13:43,040 created for the needs of legacy research 309 00:13:39,040 --> 00:13:45,120 uh purposes. uh it continues to support 310 00:13:43,040 --> 00:13:49,279 uh the existing matching process for 311 00:13:45,120 --> 00:13:53,120 legacy MPI but uh the data is 312 00:13:49,279 --> 00:13:55,519 deidentified in the legacy MPI and it 313 00:13:53,120 --> 00:13:58,079 but it is not designed for a high 314 00:13:55,519 --> 00:14:01,440 cadence transactional data transfer 315 00:13:58,079 --> 00:14:05,040 system. So we have had to re-engineer 316 00:14:01,440 --> 00:14:08,560 the MPI process for bridge which will be 317 00:14:05,040 --> 00:14:10,959 able to support a more uh faster 318 00:14:08,560 --> 00:14:13,839 matching for transactional data system, 319 00:14:10,959 --> 00:14:17,440 faster validation, quicker movement of 320 00:14:13,839 --> 00:14:21,040 data between projects of uh Google cloud 321 00:14:17,440 --> 00:14:23,440 platform and we will also be able to 322 00:14:21,040 --> 00:14:27,040 support for edge case individual 323 00:14:23,440 --> 00:14:31,279 matching in case of uh bridge uh data 324 00:14:27,040 --> 00:14:34,000 request. So we are trying to create a 325 00:14:31,279 --> 00:14:37,279 much faster system a transactional data 326 00:14:34,000 --> 00:14:40,399 system for bridge. But legacy MPI is 327 00:14:37,279 --> 00:14:43,120 going to provide us the foundational 328 00:14:40,399 --> 00:14:46,320 golden record data set which is going to 329 00:14:43,120 --> 00:14:50,079 be the authoritative uh person record 330 00:14:46,320 --> 00:14:52,399 and remains a critical foundation for 331 00:14:50,079 --> 00:14:56,240 identity resolution and person level 332 00:14:52,399 --> 00:14:59,519 data matching for bridge. So with this 333 00:14:56,240 --> 00:15:02,079 these are all the updates for UDRC uh 334 00:14:59,519 --> 00:15:05,839 legacy system. Uh Jeremia if we can go 335 00:15:02,079 --> 00:15:09,279 to the next slide. Uh now I will 336 00:15:05,839 --> 00:15:12,560 continue on the UDRC bridge updates. Uh 337 00:15:09,279 --> 00:15:15,680 UDRC bridge has several uh layers of 338 00:15:12,560 --> 00:15:18,560 development ongoing. Uh the first one is 339 00:15:15,680 --> 00:15:23,040 the foundation for all bridge operation 340 00:15:18,560 --> 00:15:25,600 which is the GCP environment. Uh over 341 00:15:23,040 --> 00:15:29,600 the last few months we have completed 342 00:15:25,600 --> 00:15:32,639 most of the deployments of uh design 343 00:15:29,600 --> 00:15:35,920 development and testing of the GCP 344 00:15:32,639 --> 00:15:38,560 environment for bridge and most of the 345 00:15:35,920 --> 00:15:42,959 core environment architecture including 346 00:15:38,560 --> 00:15:45,199 the application services uh networking 347 00:15:42,959 --> 00:15:48,079 uh identity access management and 348 00:15:45,199 --> 00:15:50,079 integration of the different layers 349 00:15:48,079 --> 00:15:51,360 within the GCP environments have been 350 00:15:50,079 --> 00:15:53,600 completed. 351 00:15:51,360 --> 00:15:56,560 uh I think overall we are tracking at 352 00:15:53,600 --> 00:16:00,240 around 79% completion according to our 353 00:15:56,560 --> 00:16:03,680 project forge document uh for the GCP 354 00:16:00,240 --> 00:16:05,600 environment uh of bridge and currently 355 00:16:03,680 --> 00:16:08,399 we have 356 00:16:05,600 --> 00:16:11,120 certain items open still uh in terms of 357 00:16:08,399 --> 00:16:14,560 GCP environment which includes the 358 00:16:11,120 --> 00:16:17,199 documentation of the final environment 359 00:16:14,560 --> 00:16:21,360 uh variables uh a final security 360 00:16:17,199 --> 00:16:24,560 completion and a close out UAT before uh 361 00:16:21,360 --> 00:16:26,560 it's ready for production from GCP 362 00:16:24,560 --> 00:16:29,440 environment. I will move on to the data 363 00:16:26,560 --> 00:16:32,240 services which is the backbone of all 364 00:16:29,440 --> 00:16:34,560 data ingestion, storage and data flows 365 00:16:32,240 --> 00:16:38,240 within into bridge and out of bridge 366 00:16:34,560 --> 00:16:42,240 system. Uh most of the data services uh 367 00:16:38,240 --> 00:16:45,279 have been completed uh when uh Borwood 368 00:16:42,240 --> 00:16:47,680 was completely on boarded with UDRC. Uh 369 00:16:45,279 --> 00:16:50,000 so we are tracking at around 85% 370 00:16:47,680 --> 00:16:53,519 completion with the project forge for 371 00:16:50,000 --> 00:16:55,920 data services and uh with the core 372 00:16:53,519 --> 00:16:59,440 design and development complete we are 373 00:16:55,920 --> 00:17:01,839 just awaiting uh some of the integration 374 00:16:59,440 --> 00:17:04,640 with the other layers of uh bridge 375 00:17:01,839 --> 00:17:06,720 applications. So uh some security 376 00:17:04,640 --> 00:17:09,919 implementation documentation and 377 00:17:06,720 --> 00:17:11,839 testings are remain open for the data 378 00:17:09,919 --> 00:17:14,240 services in terms of uh bridge 379 00:17:11,839 --> 00:17:18,079 development. Uh if you can go to the 380 00:17:14,240 --> 00:17:20,880 next slide Jerma uh this is the MPI 381 00:17:18,079 --> 00:17:23,360 services where most of the ma which has 382 00:17:20,880 --> 00:17:26,480 been a major area of focus for us over 383 00:17:23,360 --> 00:17:29,200 the last few months. Uh so we are 384 00:17:26,480 --> 00:17:32,799 designing and developing bridge as a 385 00:17:29,200 --> 00:17:36,240 request servicing workflow. So first 386 00:17:32,799 --> 00:17:39,360 when an identifying individual uh when a 387 00:17:36,240 --> 00:17:41,760 request comes into bridge uh we will be 388 00:17:39,360 --> 00:17:44,799 identifying whether that person exists 389 00:17:41,760 --> 00:17:46,960 in the golden record and if that person 390 00:17:44,799 --> 00:17:49,120 exists in the golden record then we will 391 00:17:46,960 --> 00:17:51,840 be validating the source data set from 392 00:17:49,120 --> 00:17:54,799 where uh the information has been 393 00:17:51,840 --> 00:17:57,200 retrieved into the golden record. If the 394 00:17:54,799 --> 00:17:59,840 source data set and the data partner are 395 00:17:57,200 --> 00:18:01,760 participating in bridge only then the 396 00:17:59,840 --> 00:18:04,480 request will be serviced for the end 397 00:18:01,760 --> 00:18:06,080 users otherwise they will be displayed a 398 00:18:04,480 --> 00:18:08,559 message that this data cannot be 399 00:18:06,080 --> 00:18:10,720 displayed currently as the partner data 400 00:18:08,559 --> 00:18:14,160 is not participating with bridge right 401 00:18:10,720 --> 00:18:16,320 now. So this is a overarching design for 402 00:18:14,160 --> 00:18:19,200 bridge which we are following in terms 403 00:18:16,320 --> 00:18:21,919 of uh supplying the data set for anyone 404 00:18:19,200 --> 00:18:24,960 who is who is requesting the data set. 405 00:18:21,919 --> 00:18:28,320 So with this in mind we have completed 406 00:18:24,960 --> 00:18:32,160 the core batch foundation work for uh 407 00:18:28,320 --> 00:18:34,160 the algorithm uh the CI/CD setup to test 408 00:18:32,160 --> 00:18:35,679 and implement the code as we are 409 00:18:34,160 --> 00:18:38,320 iteratively 410 00:18:35,679 --> 00:18:41,039 uh processing the data for all of the 411 00:18:38,320 --> 00:18:43,520 from all of the data partners and some 412 00:18:41,039 --> 00:18:47,039 of the pre-processing and bigquery setup 413 00:18:43,520 --> 00:18:49,919 has been completed. Uh major work uh 414 00:18:47,039 --> 00:18:52,559 also is going on with the linkage of 415 00:18:49,919 --> 00:18:55,760 individuals. So let's say an individual 416 00:18:52,559 --> 00:18:58,080 is coming with uh first name, last name 417 00:18:55,760 --> 00:19:01,120 and social security number from one data 418 00:18:58,080 --> 00:19:03,280 partner and slightly different uh 419 00:19:01,120 --> 00:19:06,160 information from another data partner. 420 00:19:03,280 --> 00:19:08,160 So we are trying to create uh we are 421 00:19:06,160 --> 00:19:10,559 trying to match these individuals or 422 00:19:08,160 --> 00:19:12,799 these edge cases so that our 423 00:19:10,559 --> 00:19:17,360 probabilistic and deterministic matching 424 00:19:12,799 --> 00:19:20,080 pipelines are are able to uh provide the 425 00:19:17,360 --> 00:19:23,760 provide the result set in a much faster 426 00:19:20,080 --> 00:19:26,400 process and uh with a much more much 427 00:19:23,760 --> 00:19:29,360 better confidence interval so that uh 428 00:19:26,400 --> 00:19:32,480 the data that we are supplying is the 429 00:19:29,360 --> 00:19:34,559 data that the user needs and with this 430 00:19:32,480 --> 00:19:36,559 we are also 431 00:19:34,559 --> 00:19:39,440 designing and developing a golden 432 00:19:36,559 --> 00:19:42,559 record. So golden record is going to be 433 00:19:39,440 --> 00:19:45,280 the spine of the bridge data system and 434 00:19:42,559 --> 00:19:47,760 also going to be uh supporting the 435 00:19:45,280 --> 00:19:50,720 legacy system in a deident for 436 00:19:47,760 --> 00:19:54,480 deidentified research data sets. uh 437 00:19:50,720 --> 00:19:56,720 while the bridge system will have a PII 438 00:19:54,480 --> 00:19:59,840 bearing information so that anyone 439 00:19:56,720 --> 00:20:02,160 requesting uh any information can be 440 00:19:59,840 --> 00:20:04,480 quickly matched against that and be able 441 00:20:02,160 --> 00:20:07,280 to request that service so that the user 442 00:20:04,480 --> 00:20:10,320 can receive their results. 443 00:20:07,280 --> 00:20:13,840 So uh that's all the updates for MBI 444 00:20:10,320 --> 00:20:17,280 services uh with the API and the AMS 445 00:20:13,840 --> 00:20:19,520 services which are interlin uh the API 446 00:20:17,280 --> 00:20:22,000 development is currently going on. We 447 00:20:19,520 --> 00:20:24,720 are currently going through the design 448 00:20:22,000 --> 00:20:27,520 uh phase and configuration of the API 449 00:20:24,720 --> 00:20:30,880 platform so that the API keys can be 450 00:20:27,520 --> 00:20:33,360 provided to the uh end users and we can 451 00:20:30,880 --> 00:20:36,960 set a revocation time or automatic 452 00:20:33,360 --> 00:20:40,080 revocation if uh the time has passed uh 453 00:20:36,960 --> 00:20:43,039 for which the end user was validated to 454 00:20:40,080 --> 00:20:45,440 to be receiving the data set for and 455 00:20:43,039 --> 00:20:48,640 with the AMS which is the security and 456 00:20:45,440 --> 00:20:51,919 governance layer to enable role based 457 00:20:48,640 --> 00:20:53,679 access for for data uh data 458 00:20:51,919 --> 00:20:56,159 administrators and also for data 459 00:20:53,679 --> 00:21:00,240 partners. Most of the development has 460 00:20:56,159 --> 00:21:03,520 completed uh some of the uh core uh 461 00:21:00,240 --> 00:21:05,360 administ core AMS services are already 462 00:21:03,520 --> 00:21:08,640 have already been through design 463 00:21:05,360 --> 00:21:11,520 development and testing. uh but uh there 464 00:21:08,640 --> 00:21:14,880 are some back-end functionality uh which 465 00:21:11,520 --> 00:21:17,520 are already running in UAT but we will 466 00:21:14,880 --> 00:21:20,000 still review them as the API services 467 00:21:17,520 --> 00:21:22,960 are developed and they are integrated 468 00:21:20,000 --> 00:21:24,559 into a one core component of the bridge 469 00:21:22,960 --> 00:21:28,760 system. 470 00:21:24,559 --> 00:21:28,760 Uh next slide please Jeremas. 471 00:21:29,440 --> 00:21:35,679 Uh so the last update for bridge is the 472 00:21:32,320 --> 00:21:38,000 UIUX which is the front end for uh 473 00:21:35,679 --> 00:21:40,080 bridge application. So that includes the 474 00:21:38,000 --> 00:21:42,720 dashboards for administrator, data 475 00:21:40,080 --> 00:21:45,679 partners and end users. Most of the 476 00:21:42,720 --> 00:21:48,960 development and testing for the UIUX 477 00:21:45,679 --> 00:21:51,919 portion of bridge uh was complete and we 478 00:21:48,960 --> 00:21:55,360 have provided the required feedback to 479 00:21:51,919 --> 00:21:57,760 our third party provider on uh admin 480 00:21:55,360 --> 00:22:02,159 dashboards, end users and data partner 481 00:21:57,760 --> 00:22:05,120 interfaces. I will be demoing a a a 482 00:22:02,159 --> 00:22:08,720 website on development platform uh on 483 00:22:05,120 --> 00:22:11,039 GCP right now after my presentation and 484 00:22:08,720 --> 00:22:13,520 there are certain remaining open items 485 00:22:11,039 --> 00:22:16,559 which we will be tackling as we move 486 00:22:13,520 --> 00:22:20,799 forward like some specific login request 487 00:22:16,559 --> 00:22:25,120 access data partner workbench uh and uh 488 00:22:20,799 --> 00:22:28,559 uh navigation sidebar etc. So overall uh 489 00:22:25,120 --> 00:22:31,039 we think around 78% of bridges uh 490 00:22:28,559 --> 00:22:33,200 technical infrastructure is now in place 491 00:22:31,039 --> 00:22:36,400 but the major area of focus going 492 00:22:33,200 --> 00:22:37,919 forward is going to be the MPI logic and 493 00:22:36,400 --> 00:22:40,400 validation 494 00:22:37,919 --> 00:22:43,840 deploying and integrating the API and 495 00:22:40,400 --> 00:22:46,480 the AMS services connecting all of these 496 00:22:43,840 --> 00:22:50,480 layers through middleware and finalizing 497 00:22:46,480 --> 00:22:55,200 the UI uh dashboards uh for UIT uh for 498 00:22:50,480 --> 00:22:57,760 UAT and uh production except acceptance. 499 00:22:55,200 --> 00:23:00,559 Uh Jeremas, do you mind if I uh took 500 00:22:57,760 --> 00:23:03,559 over the screen share for a minute to 501 00:23:00,559 --> 00:23:03,559 demo? 502 00:23:13,440 --> 00:23:20,480 Okay. So, this is the administrator 503 00:23:17,760 --> 00:23:23,720 uh dashboard. Are you guys able to see 504 00:23:20,480 --> 00:23:23,720 my screen? 505 00:23:25,120 --> 00:23:29,600 Yeah. 506 00:23:26,559 --> 00:23:33,280 » Okay. Uh so this is the administrator 507 00:23:29,600 --> 00:23:35,360 dashboard of uh the bridge uh system. 508 00:23:33,280 --> 00:23:39,120 You can see on the left pane we have the 509 00:23:35,360 --> 00:23:41,760 account management AMS uh messaging uh 510 00:23:39,120 --> 00:23:43,600 sorry matching as a service messaging 511 00:23:41,760 --> 00:23:46,640 and glossaryy. 512 00:23:43,600 --> 00:23:49,760 uh on the activity log page of the 513 00:23:46,640 --> 00:23:53,120 dashboard you can see these are all seed 514 00:23:49,760 --> 00:23:56,159 or uh sample data set that we have 515 00:23:53,120 --> 00:23:58,880 seeded into the current environment and 516 00:23:56,159 --> 00:24:02,240 if I go into one of these you'll be able 517 00:23:58,880 --> 00:24:05,120 to see how a request actually looks like 518 00:24:02,240 --> 00:24:07,360 so the administrator will be able to see 519 00:24:05,120 --> 00:24:09,200 who requested the data set what was the 520 00:24:07,360 --> 00:24:12,000 use case for which the data was 521 00:24:09,200 --> 00:24:15,679 requested the date when it was requested 522 00:24:12,000 --> 00:24:18,799 and the expiration date which we will be 523 00:24:15,679 --> 00:24:22,400 deciding based on the API key that was 524 00:24:18,799 --> 00:24:26,640 uh generated for the user. The total 525 00:24:22,400 --> 00:24:30,159 number of rows that this uh request is 526 00:24:26,640 --> 00:24:33,120 pulling and a sample number of rows for 527 00:24:30,159 --> 00:24:34,960 each of the tables from this uh from 528 00:24:33,120 --> 00:24:37,200 where this request is pulling the data 529 00:24:34,960 --> 00:24:39,440 set from. So these are all sample data 530 00:24:37,200 --> 00:24:43,120 sets. There's no PII information in 531 00:24:39,440 --> 00:24:45,360 these. And with this uh uh the 532 00:24:43,120 --> 00:24:49,039 administrator can go back to the 533 00:24:45,360 --> 00:24:51,120 dashboard look into other data set and 534 00:24:49,039 --> 00:24:53,279 there's also the account management 535 00:24:51,120 --> 00:24:56,559 where the administrator will be able to 536 00:24:53,279 --> 00:24:58,559 see how many users are currently active 537 00:24:56,559 --> 00:25:02,720 what are the roles assigned to each of 538 00:24:58,559 --> 00:25:06,880 these users their email address name etc 539 00:25:02,720 --> 00:25:09,200 and uh there I'll go into the AMS which 540 00:25:06,880 --> 00:25:11,039 is the 541 00:25:09,200 --> 00:25:13,039 authority manageer management system. 542 00:25:11,039 --> 00:25:16,559 Currently there are no master policies 543 00:25:13,039 --> 00:25:18,720 assigned but based on the creation ofus 544 00:25:16,559 --> 00:25:22,080 for bridge we will be assigning master 545 00:25:18,720 --> 00:25:25,120 policies and based on thoseus we will be 546 00:25:22,080 --> 00:25:28,159 creating the policies uh which will be 547 00:25:25,120 --> 00:25:32,400 guiding the rules for use cases and 548 00:25:28,159 --> 00:25:34,159 services and if any user is accessing 549 00:25:32,400 --> 00:25:36,400 trying to access a request the 550 00:25:34,159 --> 00:25:39,440 administrator will be see will be able 551 00:25:36,400 --> 00:25:42,000 to see their access request on uh this 552 00:25:39,440 --> 00:25:44,559 dash dashboard page. So you if you see 553 00:25:42,000 --> 00:25:47,200 one of these have been approved and one 554 00:25:44,559 --> 00:25:50,799 of them have been denied. I can still 555 00:25:47,200 --> 00:25:53,760 activate that on uh administrator side 556 00:25:50,799 --> 00:25:56,080 and only when the activation has 557 00:25:53,760 --> 00:25:58,960 completed only then the data flow will 558 00:25:56,080 --> 00:26:01,919 be working for the end user but whenever 559 00:25:58,960 --> 00:26:05,039 the administrator has closed this the 560 00:26:01,919 --> 00:26:07,279 data will not be flowing for the uh end 561 00:26:05,039 --> 00:26:09,440 user who is trying to access this. And 562 00:26:07,279 --> 00:26:12,159 this is how it will be working for the 563 00:26:09,440 --> 00:26:14,080 data partners as well. If they feel or 564 00:26:12,159 --> 00:26:18,720 see that some of the data that they are 565 00:26:14,080 --> 00:26:21,440 supplying is uh not uh is not ready for 566 00:26:18,720 --> 00:26:24,559 uh bridge, they can turn the data flow 567 00:26:21,440 --> 00:26:26,559 for their data sets only on the bridge 568 00:26:24,559 --> 00:26:29,760 platform and the data flow will be 569 00:26:26,559 --> 00:26:33,360 paused uh until it until the data 570 00:26:29,760 --> 00:26:36,400 partner turns it on. And uh moving on to 571 00:26:33,360 --> 00:26:40,000 some of the supporting instances of 572 00:26:36,400 --> 00:26:43,279 bridge like the uh support page where uh 573 00:26:40,000 --> 00:26:44,960 users can create support requests for uh 574 00:26:43,279 --> 00:26:47,440 any of the issues that they might be 575 00:26:44,960 --> 00:26:51,440 facing and glossery which will be 576 00:26:47,440 --> 00:26:54,480 showing um all the uh common questions 577 00:26:51,440 --> 00:26:56,480 related to uh the application so that 578 00:26:54,480 --> 00:26:58,880 the user can service their request or 579 00:26:56,480 --> 00:27:02,240 they can create a support request uh in 580 00:26:58,880 --> 00:27:07,360 case they are uh facing any issues. 581 00:27:02,240 --> 00:27:10,159 Uh so with that uh I conclude my update 582 00:27:07,360 --> 00:27:13,799 uh for the meeting. Any questions, 583 00:27:10,159 --> 00:27:13,799 comments or concerns. 584 00:27:17,760 --> 00:27:24,799 Okay. Uh back to you. 585 00:27:21,760 --> 00:27:28,760 » Thank you. Yeah. 586 00:27:24,799 --> 00:27:28,760 Uh one second. 587 00:27:29,520 --> 00:27:36,120 I think I'm back here now. I'm going to 588 00:27:33,120 --> 00:27:36,120 display. 589 00:27:37,200 --> 00:27:40,760 Sorry, one second. 590 00:27:45,279 --> 00:27:50,400 Okay. 591 00:27:47,440 --> 00:27:53,679 Okay. Um passing it over to the research 592 00:27:50,400 --> 00:27:55,039 update. Um over to Ari. Um do you want 593 00:27:53,679 --> 00:27:57,760 to start us off? 594 00:27:55,039 --> 00:28:00,159 » Yeah. Thank you, Jeremias. So, we have 595 00:27:57,760 --> 00:28:02,240 uh some research updates. I'm going to 596 00:28:00,159 --> 00:28:04,720 turn it over to the various researchers 597 00:28:02,240 --> 00:28:07,360 to talk about their projects and we'll 598 00:28:04,720 --> 00:28:09,760 start with Karen. 599 00:28:07,360 --> 00:28:11,919 » Uh thank you, Ari. So, the first one 600 00:28:09,760 --> 00:28:14,799 that I'm going to talk about is the 601 00:28:11,919 --> 00:28:17,279 education and wage outcomes for STEM 602 00:28:14,799 --> 00:28:19,520 students. and STEM students who um this 603 00:28:17,279 --> 00:28:23,919 research is defined as students who 604 00:28:19,520 --> 00:28:25,520 declare um their major as a STEM major 605 00:28:23,919 --> 00:28:29,279 um the first time that they declared a 606 00:28:25,520 --> 00:28:32,080 major and right now we're working on the 607 00:28:29,279 --> 00:28:34,159 data narrative and it is undergoing 608 00:28:32,080 --> 00:28:38,240 internal reviews and implementing 609 00:28:34,159 --> 00:28:41,360 feedback from internal reviews and um 610 00:28:38,240 --> 00:28:44,080 also for this one we'll be um trying to 611 00:28:41,360 --> 00:28:45,600 submit this one to an academic journal 612 00:28:44,080 --> 00:28:48,399 for publishing 613 00:28:45,600 --> 00:28:51,840 So um also we're working on editing down 614 00:28:48,399 --> 00:28:54,240 the UDRC version of this report to meet 615 00:28:51,840 --> 00:28:56,880 the requirements of um the journals that 616 00:28:54,240 --> 00:28:58,720 we will be submitting to. So hopefully 617 00:28:56,880 --> 00:29:00,720 we'll be able to update you on that next 618 00:28:58,720 --> 00:29:02,720 time we meet. 619 00:29:00,720 --> 00:29:05,360 Um and then the next one that I'm going 620 00:29:02,720 --> 00:29:07,440 to talk about is licensed employment. So 621 00:29:05,360 --> 00:29:10,240 this one is going to look at higher 622 00:29:07,440 --> 00:29:13,600 education to lensure and also the wage 623 00:29:10,240 --> 00:29:15,279 outcomes for um jobs that require 624 00:29:13,600 --> 00:29:17,600 licensing. 625 00:29:15,279 --> 00:29:20,799 Um so as of right now initial 626 00:29:17,600 --> 00:29:23,520 descriptive and modeling is completed 627 00:29:20,799 --> 00:29:26,159 and we will be meeting with our data 628 00:29:23,520 --> 00:29:28,640 partners in July sometime. So please be 629 00:29:26,159 --> 00:29:30,480 on the lookout for an invite. Um so that 630 00:29:28,640 --> 00:29:35,600 will be DWS 631 00:29:30,480 --> 00:29:39,200 um DOC and also Yushi. And finally, the 632 00:29:35,600 --> 00:29:42,320 last one I will talk about is a a series 633 00:29:39,200 --> 00:29:44,960 research on adult learners. So this one 634 00:29:42,320 --> 00:29:47,679 is going to look at the outcomes of 635 00:29:44,960 --> 00:29:49,919 returning adult learners. So that is 636 00:29:47,679 --> 00:29:52,799 defined as someone who left their 637 00:29:49,919 --> 00:29:55,279 post-secary education for 2 years or 638 00:29:52,799 --> 00:29:57,600 more and then later returned to Yushi. 639 00:29:55,279 --> 00:30:01,919 Um right now it is also undergoing 640 00:29:57,600 --> 00:30:03,440 internal review. Um so also the feedback 641 00:30:01,919 --> 00:30:05,760 from internal review is being 642 00:30:03,440 --> 00:30:09,200 implemented and then once that is done 643 00:30:05,760 --> 00:30:14,200 it will undergo other reviews as needed 644 00:30:09,200 --> 00:30:14,200 and I will turn the time over to Connor. 645 00:30:14,640 --> 00:30:18,600 All right. Thank you Karen. 646 00:30:19,840 --> 00:30:26,480 So I'm going to start off with uh RA23 647 00:30:23,120 --> 00:30:30,000 which is looking at the uh relationship 648 00:30:26,480 --> 00:30:32,399 between changing employers and wages. Uh 649 00:30:30,000 --> 00:30:34,399 common knowled or research has found 650 00:30:32,399 --> 00:30:37,279 that changing employers has found to 651 00:30:34,399 --> 00:30:39,760 have an increase in changing or increase 652 00:30:37,279 --> 00:30:42,640 in wages. So we wanted to look at this 653 00:30:39,760 --> 00:30:44,559 for our Yushi graduates. This is 654 00:30:42,640 --> 00:30:48,320 currently going under our internal 655 00:30:44,559 --> 00:30:50,880 review and then as the next steps go on 656 00:30:48,320 --> 00:30:53,120 I'll implement internal reviews and then 657 00:30:50,880 --> 00:30:55,520 it'll head out to the data partners for 658 00:30:53,120 --> 00:30:58,480 their thoughts and questions. 659 00:30:55,520 --> 00:31:01,679 Next slide please. 660 00:30:58,480 --> 00:31:04,640 Uh next project that I am working on is 661 00:31:01,679 --> 00:31:06,799 looking at children that participated in 662 00:31:04,640 --> 00:31:10,720 the ages and stages questionnaire and 663 00:31:06,799 --> 00:31:13,520 their early primary school outcomes. uh 664 00:31:10,720 --> 00:31:15,919 a lot of research has shown that ASQ has 665 00:31:13,520 --> 00:31:17,840 an adequate predictive value in 666 00:31:15,919 --> 00:31:20,559 predicting 667 00:31:17,840 --> 00:31:23,120 uh early childhood or early educational 668 00:31:20,559 --> 00:31:25,760 outcomes. So this is something that we 669 00:31:23,120 --> 00:31:28,159 were very keen on looking into. uh 670 00:31:25,760 --> 00:31:30,880 currently this is going under the 671 00:31:28,159 --> 00:31:34,240 internal review and again like the other 672 00:31:30,880 --> 00:31:36,640 one as the internal review goes on uh 673 00:31:34,240 --> 00:31:40,840 I'll implement the comments and then 674 00:31:36,640 --> 00:31:40,840 it'll head out to the data partners 675 00:31:41,039 --> 00:31:48,399 and then lastly uh this is uh a project 676 00:31:45,440 --> 00:31:52,000 from our our a series this one is 677 00:31:48,399 --> 00:31:54,159 looking at the states imp investigate 678 00:31:52,000 --> 00:31:55,360 state's impact on retaining out of state 679 00:31:54,159 --> 00:31:57,600 students 680 00:31:55,360 --> 00:32:00,559 from Yushi schools in Utah's workforce 681 00:31:57,600 --> 00:32:02,720 after graduating. This is currently uh 682 00:32:00,559 --> 00:32:05,360 undergoing internal review and it should 683 00:32:02,720 --> 00:32:07,600 be going to external review relatively 684 00:32:05,360 --> 00:32:09,519 soon. 685 00:32:07,600 --> 00:32:13,320 I believe I'm going to be handing it off 686 00:32:09,519 --> 00:32:13,320 to Alisia now. 687 00:32:14,240 --> 00:32:20,159 Thanks Connor. Um let's see. The first 688 00:32:17,919 --> 00:32:25,120 update I have is on engineering 689 00:32:20,159 --> 00:32:28,880 pathways. Um, and for this one, uh, it's 690 00:32:25,120 --> 00:32:31,679 currently in internal manager review, 691 00:32:28,880 --> 00:32:34,320 excuse me. Um, and I'll also be 692 00:32:31,679 --> 00:32:39,039 presenting this one at a conference in 693 00:32:34,320 --> 00:32:41,039 July. Um, and so, uh, once manager 694 00:32:39,039 --> 00:32:44,480 review is complete, uh, you guys should 695 00:32:41,039 --> 00:32:47,519 see that soon for external review. Next 696 00:32:44,480 --> 00:32:51,760 slide, please. 697 00:32:47,519 --> 00:32:54,720 Um and then for um RA27, this one is on 698 00:32:51,760 --> 00:32:57,200 high school math course taking patterns. 699 00:32:54,720 --> 00:32:59,519 Um currently that one's in data 700 00:32:57,200 --> 00:33:01,679 collection. Um we have initial partner 701 00:32:59,519 --> 00:33:07,519 meetings scheduled 702 00:33:01,679 --> 00:33:10,399 um as well with with some of you. Um and 703 00:33:07,519 --> 00:33:12,159 uh and so yeah, that is currently 704 00:33:10,399 --> 00:33:14,640 underway. 705 00:33:12,159 --> 00:33:17,679 Next slide, please. 706 00:33:14,640 --> 00:33:24,799 Uh and then finally um program outcomes. 707 00:33:17,679 --> 00:33:27,360 So this is an a series um that uh was 708 00:33:24,799 --> 00:33:32,960 related to some 709 00:33:27,360 --> 00:33:36,480 uh requests by the legislature and um 710 00:33:32,960 --> 00:33:39,919 OLAG um and has been split into two 711 00:33:36,480 --> 00:33:42,640 portions, but both of those portions um 712 00:33:39,919 --> 00:33:46,240 have are currently undergoing internal 713 00:33:42,640 --> 00:33:48,799 review. Um, and so you should see those 714 00:33:46,240 --> 00:33:52,559 uh partners should see those uh pretty 715 00:33:48,799 --> 00:33:55,440 soon as well. And I believe that's it 716 00:33:52,559 --> 00:33:57,200 for mine. 717 00:33:55,440 --> 00:34:01,120 » Great. Thank you, Karen, Connor, and 718 00:33:57,200 --> 00:34:03,600 Alicia. So, next, uh, I'll give a quick 719 00:34:01,120 --> 00:34:05,760 update on some data requests. So, we've 720 00:34:03,600 --> 00:34:09,280 completed a couple data requests. Um, 721 00:34:05,760 --> 00:34:13,599 one looks at um 722 00:34:09,280 --> 00:34:16,480 and of how um CTE uh is related to uh 723 00:34:13,599 --> 00:34:19,119 later outcomes for 724 00:34:16,480 --> 00:34:22,399 uh Native American indigenous um 725 00:34:19,119 --> 00:34:24,639 students. Uh this one was used as part 726 00:34:22,399 --> 00:34:27,919 of a dissertation 727 00:34:24,639 --> 00:34:32,879 um for a recently graduated 728 00:34:27,919 --> 00:34:35,280 uh PhD. Um and then we have our other 729 00:34:32,879 --> 00:34:40,000 one on the economic economic impacts of 730 00:34:35,280 --> 00:34:42,639 the University of Utah and uh UTU. Um so 731 00:34:40,000 --> 00:34:46,960 this one we've trans this is looking at 732 00:34:42,639 --> 00:34:50,399 how you know this is a contract worth 733 00:34:46,960 --> 00:34:52,159 with Chemcy Gardner um that Yushi has 734 00:34:50,399 --> 00:34:56,159 undertaken or that ChemC Gardener has 735 00:34:52,159 --> 00:34:58,320 undertaken for Yushi excuse me. Um and 736 00:34:56,159 --> 00:35:00,880 our part of this is fairly narrow. It's 737 00:34:58,320 --> 00:35:03,440 basically, you know, what students um 738 00:35:00,880 --> 00:35:05,680 are earning um and how kind of bringing 739 00:35:03,440 --> 00:35:09,359 in uh out of state students as well 740 00:35:05,680 --> 00:35:11,839 helps um with the local economy. Ongoing 741 00:35:09,359 --> 00:35:14,640 requests, we are now working on one uh 742 00:35:11,839 --> 00:35:16,880 from ASQ and early education outcomes. 743 00:35:14,640 --> 00:35:19,839 This sounds similar to uh Connor's 744 00:35:16,880 --> 00:35:21,359 research. It's fairly different actually 745 00:35:19,839 --> 00:35:23,200 despite 746 00:35:21,359 --> 00:35:27,520 you know ASQ and early education 747 00:35:23,200 --> 00:35:31,200 outcomes. Um and the next one uh we are 748 00:35:27,520 --> 00:35:34,880 in even earlier stages uh similar to the 749 00:35:31,200 --> 00:35:35,920 previous uh economic institutions. 750 00:35:34,880 --> 00:35:37,920 This one's going to be looking at the 751 00:35:35,920 --> 00:35:40,240 economic impacts of the system as a 752 00:35:37,920 --> 00:35:42,160 whole. Again, this one's ChemC Gardener 753 00:35:40,240 --> 00:35:44,400 or both these two ongoing requests are 754 00:35:42,160 --> 00:35:48,480 from ChemC Gardener. Just different 755 00:35:44,400 --> 00:35:50,400 researchers in there. Um not pictured, 756 00:35:48,480 --> 00:35:54,480 we also had our annual bagels and 757 00:35:50,400 --> 00:35:57,040 research. It went well. Um 758 00:35:54,480 --> 00:36:00,240 I I think our goal is to do that now 759 00:35:57,040 --> 00:36:01,760 every year. Um 760 00:36:00,240 --> 00:36:03,359 I know there are representatives from 761 00:36:01,760 --> 00:36:05,839 many of the organizations there this 762 00:36:03,359 --> 00:36:08,800 year. Uh we really appreciate having 763 00:36:05,839 --> 00:36:10,480 everyone there. Um 764 00:36:08,800 --> 00:36:12,240 I think everyone appreciates being able 765 00:36:10,480 --> 00:36:14,320 to share the research and hear, you 766 00:36:12,240 --> 00:36:16,640 know, and hear about it. Uh and it does 767 00:36:14,320 --> 00:36:18,960 help keep, you know, the UDRC data and 768 00:36:16,640 --> 00:36:21,040 research and then our partners um out in 769 00:36:18,960 --> 00:36:25,520 the community as well. 770 00:36:21,040 --> 00:36:28,079 So, and those are going to be my uh my 771 00:36:25,520 --> 00:36:30,240 updates for data requests and my team's 772 00:36:28,079 --> 00:36:32,880 updates for their research. Any 773 00:36:30,240 --> 00:36:36,200 questions for any of them or us before I 774 00:36:32,880 --> 00:36:36,200 turn it over? 775 00:36:36,640 --> 00:36:40,320 Okay. Uh thank you all. Jeremiah, back 776 00:36:39,520 --> 00:36:42,079 to you. 777 00:36:40,320 --> 00:36:43,440 » Great. Yeah. I'm gonna pass it over now 778 00:36:42,079 --> 00:36:45,440 to Britney for the user experience 779 00:36:43,440 --> 00:36:48,000 update. Britney, 780 00:36:45,440 --> 00:36:50,079 » Hi everyone. So for the UX updates 781 00:36:48,000 --> 00:36:52,560 today, I'm going to share our new UDRC 782 00:36:50,079 --> 00:36:55,760 website and I'll show a preview of our 783 00:36:52,560 --> 00:36:58,640 new P20 first credential dashboard. So 784 00:36:55,760 --> 00:37:00,720 we launched our redesigned um UDRC 785 00:36:58,640 --> 00:37:02,640 website early last month. So showing it 786 00:37:00,720 --> 00:37:05,280 today in case um any of you haven't had 787 00:37:02,640 --> 00:37:07,920 the chance to check it out. Um I'll also 788 00:37:05,280 --> 00:37:09,200 share a link in the chat 789 00:37:07,920 --> 00:37:11,440 so you can go directly there in the 790 00:37:09,200 --> 00:37:13,040 chat, but also share my screen and just 791 00:37:11,440 --> 00:37:16,760 walk through some of the the new 792 00:37:13,040 --> 00:37:16,760 features we have. 793 00:37:20,079 --> 00:37:23,079 Okay. 794 00:37:23,920 --> 00:37:28,160 Um, so you'll see that we have a new 795 00:37:26,000 --> 00:37:30,880 modern design and a new tagline. Smarter 796 00:37:28,160 --> 00:37:33,680 data stroker Utah. Uh, we also did a 797 00:37:30,880 --> 00:37:35,680 refresh of the UDRC logo. So it's still 798 00:37:33,680 --> 00:37:38,160 the same icon mark, but the font and 799 00:37:35,680 --> 00:37:40,880 placement of the UDRC name is updated. 800 00:37:38,160 --> 00:37:43,760 So you see here, this is our homepage. 801 00:37:40,880 --> 00:37:46,560 um some call to actions to view research 802 00:37:43,760 --> 00:37:50,520 or to request data and then three of our 803 00:37:46,560 --> 00:37:50,520 latest updates down here. 804 00:37:51,040 --> 00:37:55,680 » Sorry, just one second. Okay. Um some of 805 00:37:54,400 --> 00:37:59,119 our new features include our 806 00:37:55,680 --> 00:38:01,599 publications page. Um so you can look at 807 00:37:59,119 --> 00:38:03,119 our previous publications um through 808 00:38:01,599 --> 00:38:05,280 these different categories. Now if 809 00:38:03,119 --> 00:38:06,720 you're just interested in workforce and 810 00:38:05,280 --> 00:38:10,920 economy, you can click that and that 811 00:38:06,720 --> 00:38:10,920 will help narrow it down. 812 00:38:11,680 --> 00:38:17,440 And then uh we have our research agenda 813 00:38:13,839 --> 00:38:19,920 here. Um the current one will be posted 814 00:38:17,440 --> 00:38:23,440 um sometime tomorrow. Um you can also 815 00:38:19,920 --> 00:38:26,000 look at um the past research agendas. We 816 00:38:23,440 --> 00:38:29,440 have that archived all here. Um and then 817 00:38:26,000 --> 00:38:32,560 for request data um we separated these 818 00:38:29,440 --> 00:38:35,119 out into two um request types. So data 819 00:38:32,560 --> 00:38:36,560 set requests and analysis requests. We 820 00:38:35,119 --> 00:38:38,880 just noticed in the past there's been 821 00:38:36,560 --> 00:38:40,880 some confusion on that. So we decided to 822 00:38:38,880 --> 00:38:42,960 break it out. So for the data set 823 00:38:40,880 --> 00:38:45,119 request, this is what it looks like. Um 824 00:38:42,960 --> 00:38:48,400 it explains the different steps and then 825 00:38:45,119 --> 00:38:50,160 a button to start it. 826 00:38:48,400 --> 00:38:53,440 For the analysis request, it explains 827 00:38:50,160 --> 00:38:56,000 what that is here. Um including our data 828 00:38:53,440 --> 00:38:58,079 dictionary and then the request form to 829 00:38:56,000 --> 00:39:01,599 download right there. 830 00:38:58,079 --> 00:39:04,000 Um this is a new events area which shows 831 00:39:01,599 --> 00:39:05,599 um our previous recordings from bigles 832 00:39:04,000 --> 00:39:08,000 and research as well as this is where 833 00:39:05,599 --> 00:39:10,480 we'll we'll put our registration page um 834 00:39:08,000 --> 00:39:11,920 as well as past webinars. 835 00:39:10,480 --> 00:39:14,640 So you can see the bigles and research 836 00:39:11,920 --> 00:39:16,720 page looks like this. So we have three 837 00:39:14,640 --> 00:39:18,960 years worth there. Um and then here's 838 00:39:16,720 --> 00:39:20,880 some of our past webinars. So every time 839 00:39:18,960 --> 00:39:23,040 we release a new research product we do 840 00:39:20,880 --> 00:39:25,200 a webinar with it and we'll post the 841 00:39:23,040 --> 00:39:27,040 recording here. 842 00:39:25,200 --> 00:39:29,920 And then we have the resources page. 843 00:39:27,040 --> 00:39:31,520 These are just various documents um such 844 00:39:29,920 --> 00:39:33,359 as our governance document, our data 845 00:39:31,520 --> 00:39:36,720 dictionary as well as some other 846 00:39:33,359 --> 00:39:39,680 resources here. 847 00:39:36,720 --> 00:39:41,920 Uh under about us, um we broke this out 848 00:39:39,680 --> 00:39:44,000 into a few different subpages just to 849 00:39:41,920 --> 00:39:46,000 help um break out some of this 850 00:39:44,000 --> 00:39:47,599 information 851 00:39:46,000 --> 00:39:49,760 um about us. So we have this general 852 00:39:47,599 --> 00:39:52,320 about us and then we have our history 853 00:39:49,760 --> 00:39:55,440 explaining where how UDRC came about and 854 00:39:52,320 --> 00:39:59,920 where we are today. 855 00:39:55,440 --> 00:40:02,240 Um our team with some lovely pictures 856 00:39:59,920 --> 00:40:04,240 and then this is um newer where we have 857 00:40:02,240 --> 00:40:06,079 a data partners page where we put a 858 00:40:04,240 --> 00:40:07,599 little bit more explanation of what kind 859 00:40:06,079 --> 00:40:09,839 of data we are getting from each 860 00:40:07,599 --> 00:40:13,560 partner. 861 00:40:09,839 --> 00:40:13,560 So that's our website. 862 00:40:14,160 --> 00:40:18,320 Okay. So next um I'll show a preview of 863 00:40:16,160 --> 00:40:20,400 our upcoming dashboard on Utah's 864 00:40:18,320 --> 00:40:21,920 education to workforce pipeline which 865 00:40:20,400 --> 00:40:23,520 features first credentials and main 866 00:40:21,920 --> 00:40:27,160 milestone 867 00:40:23,520 --> 00:40:27,160 which I have here. 868 00:40:30,480 --> 00:40:33,599 Um, so first credential, if you haven't 869 00:40:32,320 --> 00:40:35,680 heard, this is a new statewide 870 00:40:33,599 --> 00:40:37,520 initiative. It ensures that that every 871 00:40:35,680 --> 00:40:39,680 high school student graduates with their 872 00:40:37,520 --> 00:40:42,400 first credential along with their 873 00:40:39,680 --> 00:40:44,640 diploma. So this dashboard looks at the 874 00:40:42,400 --> 00:40:47,920 different data highlights in K through 875 00:40:44,640 --> 00:40:49,599 12 um post-secary and workforce data 876 00:40:47,920 --> 00:40:50,960 within the context of how they are 877 00:40:49,599 --> 00:40:52,800 supporting leading up to that first 878 00:40:50,960 --> 00:40:55,119 credential and also how that first 879 00:40:52,800 --> 00:40:57,680 credential helps support future college 880 00:40:55,119 --> 00:40:59,280 completion and workforce participation. 881 00:40:57,680 --> 00:41:02,000 So you'll see throughout this dashboard 882 00:40:59,280 --> 00:41:04,400 we pull metrics from various data 883 00:41:02,000 --> 00:41:06,640 sources um to help show those statewide 884 00:41:04,400 --> 00:41:09,119 trends and we try to do at least like a 885 00:41:06,640 --> 00:41:10,720 five-year look back on each one. some of 886 00:41:09,119 --> 00:41:12,400 them we didn't have enough data. Um 887 00:41:10,720 --> 00:41:14,640 maybe it's like three years back. Um but 888 00:41:12,400 --> 00:41:16,240 for the most part it's five years um at 889 00:41:14,640 --> 00:41:18,240 different um major points in the 890 00:41:16,240 --> 00:41:20,880 pipeline. Um but the overall purpose of 891 00:41:18,240 --> 00:41:24,000 this dashboard is to help determine um 892 00:41:20,880 --> 00:41:26,640 areas for improvement in early learning 893 00:41:24,000 --> 00:41:28,880 to help support first credentials um and 894 00:41:26,640 --> 00:41:31,839 also to monitor post-secondary um 895 00:41:28,880 --> 00:41:34,560 success and workforce alignment. 896 00:41:31,839 --> 00:41:38,359 So I'll just show um some of these pages 897 00:41:34,560 --> 00:41:38,359 um so you can get an idea. 898 00:41:39,920 --> 00:41:44,319 So for early foundations, we're looking 899 00:41:41,760 --> 00:41:46,880 at Aadian um reading levels K through 900 00:41:44,319 --> 00:41:48,480 three. Um looking back over time and 901 00:41:46,880 --> 00:41:49,760 seeing the difference here. So you'll 902 00:41:48,480 --> 00:41:51,760 notice on each page, we'll put the 903 00:41:49,760 --> 00:41:53,920 percentage point difference over the 904 00:41:51,760 --> 00:41:55,599 timeline that we're looking at. And then 905 00:41:53,920 --> 00:41:57,599 if someone wants to learn more about 906 00:41:55,599 --> 00:41:59,200 Aadian or this data, they can click 907 00:41:57,599 --> 00:42:01,359 here, learn more on the bottom right, 908 00:41:59,200 --> 00:42:05,240 and that will take them to the USB um 909 00:42:01,359 --> 00:42:05,240 data page about this. 910 00:42:06,560 --> 00:42:11,680 For the next one, high school readiness. 911 00:42:09,440 --> 00:42:13,520 Uh we pull data from NAPE. Here we're 912 00:42:11,680 --> 00:42:17,040 looking at fourth grade and eighth grade 913 00:42:13,520 --> 00:42:19,440 reading and math proficiency levels. Um 914 00:42:17,040 --> 00:42:21,440 we have overall comp comparisons as well 915 00:42:19,440 --> 00:42:23,200 as we could break it um through 916 00:42:21,440 --> 00:42:25,680 different Utah state, sorry, Utah 917 00:42:23,200 --> 00:42:27,200 student population groups. 918 00:42:25,680 --> 00:42:28,880 Uh we have a little write up here on the 919 00:42:27,200 --> 00:42:30,160 right about what it is and again a learn 920 00:42:28,880 --> 00:42:34,200 more button where it will take you 921 00:42:30,160 --> 00:42:34,200 directly to that NAPE data. 922 00:42:35,119 --> 00:42:38,720 Okay, first credentials. This is where 923 00:42:36,720 --> 00:42:41,839 we pulled a lot of like um new data that 924 00:42:38,720 --> 00:42:43,599 we haven't really shared before. So um 925 00:42:41,839 --> 00:42:45,119 here on the top left, these are the 926 00:42:43,599 --> 00:42:46,800 pathway indicators for first 927 00:42:45,119 --> 00:42:49,040 credentials. So for example, current 928 00:42:46,800 --> 00:42:50,880 enrollment is a pathway. Here we pulled 929 00:42:49,040 --> 00:42:53,599 participation rates over the past five 930 00:42:50,880 --> 00:42:56,800 years and showing the difference um over 931 00:42:53,599 --> 00:42:58,880 time. Here uh we have enrollments in CTE 932 00:42:56,800 --> 00:43:01,520 courses. Sorry, my internet's not 933 00:42:58,880 --> 00:43:03,680 working. Um but so different different 934 00:43:01,520 --> 00:43:05,680 filters. You can look at CTE courses. 935 00:43:03,680 --> 00:43:08,160 You can look at tech college completion 936 00:43:05,680 --> 00:43:09,680 rates, general ed certificate 937 00:43:08,160 --> 00:43:12,319 completions, as well as youth 938 00:43:09,680 --> 00:43:14,319 apprenticeships and looking at those um 939 00:43:12,319 --> 00:43:16,400 rates over time. We also include the 940 00:43:14,319 --> 00:43:19,359 high school cohort graduation rates over 941 00:43:16,400 --> 00:43:21,040 time by um different populations. So, 942 00:43:19,359 --> 00:43:23,200 this helps provide kind of like an 943 00:43:21,040 --> 00:43:25,200 overview baseline look of how we're 944 00:43:23,200 --> 00:43:27,040 doing with first credentials. And this 945 00:43:25,200 --> 00:43:29,359 is something we can look at each year um 946 00:43:27,040 --> 00:43:31,200 and see how how the participation is 947 00:43:29,359 --> 00:43:34,200 changing over time or the completion 948 00:43:31,200 --> 00:43:34,200 rates. 949 00:43:34,720 --> 00:43:41,440 The next one we have is um college 950 00:43:37,440 --> 00:43:42,640 success. So here we have um currently 951 00:43:41,440 --> 00:43:46,560 right here it's on the technical 952 00:43:42,640 --> 00:43:49,520 colleges um certificate completion um 953 00:43:46,560 --> 00:43:50,800 time to uh certificate rates. So you 954 00:43:49,520 --> 00:43:52,800 you'll see we have it broken down by 955 00:43:50,800 --> 00:43:54,960 each institution as well as the average 956 00:43:52,800 --> 00:43:59,440 um line for all of them. So looking at 957 00:43:54,960 --> 00:44:02,000 100% of normal time, 150% and 200%. 958 00:43:59,440 --> 00:44:03,760 And then we also have see if this will 959 00:44:02,000 --> 00:44:06,160 reconnect 960 00:44:03,760 --> 00:44:08,800 uh our bachelor's cohort. So looking at 961 00:44:06,160 --> 00:44:11,040 it by each institution, four years after 962 00:44:08,800 --> 00:44:13,440 entry, six years and eight years and 963 00:44:11,040 --> 00:44:14,800 then we have our um percentage point 964 00:44:13,440 --> 00:44:16,800 difference over time here on the top 965 00:44:14,800 --> 00:44:18,960 left. We also included first year 966 00:44:16,800 --> 00:44:24,280 enrollments at Yushi of Utah High School 967 00:44:18,960 --> 00:44:24,280 graduates. um here on the left. 968 00:44:25,280 --> 00:44:28,960 Okay. Then finally, we have workforce 969 00:44:26,800 --> 00:44:31,760 alignment. This comes from Yushi's 970 00:44:28,960 --> 00:44:33,440 workforce outcomes dashboard. Here we 971 00:44:31,760 --> 00:44:36,079 pulled bachelor, associate, and 972 00:44:33,440 --> 00:44:39,599 certificate graduates. 973 00:44:36,079 --> 00:44:41,680 Um looking at um their employment, 974 00:44:39,599 --> 00:44:44,240 they're working in Utah um eight 975 00:44:41,680 --> 00:44:46,160 quarters after their graduation. 976 00:44:44,240 --> 00:44:47,839 And then we also um pulled their 977 00:44:46,160 --> 00:44:49,520 salaries. So you can see their change 978 00:44:47,839 --> 00:44:52,520 there from one year to five year after 979 00:44:49,520 --> 00:44:52,520 graduation. 980 00:44:53,520 --> 00:44:57,599 So uh so overall this dashboard it 981 00:44:55,520 --> 00:44:59,520 provides like a nice one-stop area to 982 00:44:57,599 --> 00:45:02,160 see these major indicators and how 983 00:44:59,520 --> 00:45:04,720 they're doing over time um in relation 984 00:45:02,160 --> 00:45:06,319 to first credential and uh so this is a 985 00:45:04,720 --> 00:45:07,680 preview so it's not final. So we're 986 00:45:06,319 --> 00:45:11,200 sending this out to our partners soon 987 00:45:07,680 --> 00:45:12,560 for their review and um thanks to way 988 00:45:11,200 --> 00:45:14,240 she did a lot of the heavy lifting on 989 00:45:12,560 --> 00:45:16,800 this project. 990 00:45:14,240 --> 00:45:19,599 So, I'm going to stop sharing. Were 991 00:45:16,800 --> 00:45:23,200 there any questions 992 00:45:19,599 --> 00:45:25,680 about any of those projects 993 00:45:23,200 --> 00:45:30,280 and thanks for your comment, Mark? Um, 994 00:45:25,680 --> 00:45:30,280 saying great website. Thank you. 995 00:45:33,040 --> 00:45:36,560 » Okay, no questions. I'll pass it back to 996 00:45:34,560 --> 00:45:39,599 Jeremas. 997 00:45:36,560 --> 00:45:42,000 » Great. Excuse me. Great. 998 00:45:39,599 --> 00:45:43,440 Um, I'll dispense of the the uh 999 00:45:42,000 --> 00:45:46,079 PowerPoint presentation since we only 1000 00:45:43,440 --> 00:45:48,800 have two more slides. Um, the next 1001 00:45:46,079 --> 00:45:52,000 section was going to be public comment. 1002 00:45:48,800 --> 00:45:55,520 Um, I technically don't see any members 1003 00:45:52,000 --> 00:45:58,240 of the public um on our meeting here. 1004 00:45:55,520 --> 00:46:02,319 Um, everyone's either did a partner or a 1005 00:45:58,240 --> 00:46:03,599 UDRC employee. So, um, 1006 00:46:02,319 --> 00:46:06,480 I I don't think we're going to have any 1007 00:46:03,599 --> 00:46:08,319 public comment today. So, um, then last 1008 00:46:06,480 --> 00:46:10,560 slide is just to thank you as always. 1009 00:46:08,319 --> 00:46:12,960 Thank you so much for your coordination 1010 00:46:10,560 --> 00:46:15,119 and continued collaboration in this 1011 00:46:12,960 --> 00:46:17,200 project that we call the UDRC. Uh we 1012 00:46:15,119 --> 00:46:20,000 could not um do the work that we're 1013 00:46:17,200 --> 00:46:21,520 doing without that component, your your 1014 00:46:20,000 --> 00:46:24,160 side of the equation. So thank you so 1015 00:46:21,520 --> 00:46:26,800 much as always and looking forward to 1016 00:46:24,160 --> 00:46:28,880 meeting or meeting again in in in 6 1017 00:46:26,800 --> 00:46:30,400 months time to provide another update. 1018 00:46:28,880 --> 00:46:33,359 Uh hopefully we'll have a lot more to 1019 00:46:30,400 --> 00:46:37,200 update on bridge uh next time uh and 1020 00:46:33,359 --> 00:46:40,000 obviously all research and UX. So um if 1021 00:46:37,200 --> 00:46:42,800 there are no further questions this time 1022 00:46:40,000 --> 00:46:44,400 uh we'll adjourn the meeting. So have a 1023 00:46:42,800 --> 00:46:46,160 wonderful day. Thank you. 1024 00:46:44,400 --> 00:46:49,480 » Thank you. Bye. 1025 00:46:46,160 --> 00:46:49,480 » Thanks everyone.