[0:00] Beautiful crisp
[0:02] late or early early summer day with what
[0:05] was like 60° outside. I'm not really
[0:08] sure what's happening. Anyhow, um so the
[0:12] previous meeting was December 19th of
[0:14] 2025. As for some of you who who's uh uh
[0:18] this is the first attendance to these
[0:20] meetings, we hold these meetings twice a
[0:21] year. uh once uh the second quarter of
[0:26] the year and then the second time is the
[0:28] fourth quarter of the year. Um so the
[0:30] last time we had this meeting was
[0:31] December. The next time we'll be having
[0:33] this meeting again will be December of
[0:35] 2026. So the minutes from the last
[0:38] minute from the last meeting were
[0:40] communicated. Um are there any
[0:42] questions, comments or concerns about
[0:44] those minutes um that we should be
[0:48] brought up today? Hey Mark, how are you?
[0:52] Good. How are you doing?
[0:53] » We're good. We just re uh just barely
[0:55] got started. So, yeah, I didn't miss
[0:57] much. So,
[0:59] » Okay. Seeing no uh questions, comments,
[1:01] or concerns on those, we'll move forward
[1:04] with um administrative updates. So to
[1:07] provide start with the SLDS grants um
[1:11] just a reminder that the operational
[1:13] considerations for the bridge grant uh
[1:16] is that it was moved from October of
[1:19] 2023 through September of 2027. That's
[1:22] the full duration of the grant period of
[1:25] time of performance and progress on that
[1:27] is that we there was uh some federal
[1:30] budget impacts um at the um federal
[1:35] education level. Um and so therefore
[1:38] we're behind uh on progress on that. We
[1:41] went from a team of 10 plus to just two
[1:44] individuals. Uh and unfortunately one of
[1:47] the individuals who one of those two
[1:49] individuals who was assisting us on the
[1:52] uh master person index algorithm
[1:54] component um had to leave the project.
[1:58] Um the third party vendor that we
[2:01] utilized to assist us in building out
[2:04] bridge was bought out by another third
[2:06] party vendor and unfortunately their
[2:08] contract conflicted with the new uh
[2:11] employee rules and regulations of the
[2:13] third party vendor. And so they had to
[2:16] leave the project and leave the company.
[2:18] So we were able to get a new resource
[2:21] through Burwood. Uh but unfortunately
[2:23] that resource uh had to obviously be
[2:25] onboarded to the project and on boarded
[2:27] into this very specific component of the
[2:30] project. Um so that took time and effort
[2:33] um and obviously uh development time as
[2:36] well. So as of June the delay in the
[2:39] progress is not an emergency. However,
[2:41] it is significant and material and we'll
[2:45] need to obviously um significantly hurry
[2:48] in the next months to um catch up and
[2:51] ailerate that uh deficit. So, uh but uh
[2:56] again, not an emergency at this time.
[2:58] So, and Jay will provide further update
[3:01] uh in his technology update on where
[3:02] we're at with Bridge um in the future.
[3:05] So,
[3:07] so that's where we're at with the
[3:09] development work for the bridge
[3:12] transactional system. Um, I'll provide
[3:15] now an update on the legal framework
[3:18] which is what is going to allow us to
[3:21] execute the operational goals of bridge
[3:25] um legally. So because of SP 195
[3:28] obviously the impact there was that we
[3:31] are allowed to undertake the operational
[3:33] activities that we defined under the
[3:35] bridge project. Um so generally speaking
[3:38] this will allow us to onboard
[3:40] participating state agencies. Um as
[3:43] we've previously stated bridge is is a
[3:46] voluntary
[3:47] um data system that we are going to be
[3:50] creating and building. Um it is not like
[3:53] the UDRC legacy system uh where the data
[3:55] partners are defined by code. Um bridge
[3:59] is is voluntary. So um we are in the
[4:03] process of rulem. Um so per 19 SP95 we
[4:08] had to create rulem uh rules or or
[4:10] verbiage or define the verbiage of the
[4:12] rulem uh for the SP 195 uh specifically
[4:17] uh related to the legal framework that
[4:20] we were going to create an institute for
[4:23] bridge. So the update there is that the
[4:25] draft administrative rules um that's
[4:28] completed uh we sent it out to our data
[4:32] partners for uh review. So that was uh
[4:36] all of you here um and we gave uh this
[4:39] group until July 15th to provide
[4:42] feedback um if uh if any. Um so we are
[4:47] we're waiting for that time to elapse.
[4:50] Um and then we will finalize the verbage
[4:53] by August 1st. Uh and then we will be
[4:56] seeking approval by the Yushi board on
[4:59] the September 2026
[5:02] uh board of higher education um board
[5:05] meeting. So after that um hopefully
[5:08] obviously it passes uh and they approve
[5:10] of it and then we will we will publish
[5:13] um the rule um as completed um at that
[5:17] point in time. So
[5:20] any questions, comments or concerns
[5:22] about that rule making process,
[5:24] the verbiage.
[5:30] Okay,
[5:35] moving along the administrative updates.
[5:37] Um I do have some really good news um
[5:40] about new forthcoming data to the UDRC
[5:43] legacy system. Um so and I the the
[5:48] latest news most up up to date on the
[5:50] home visiting program um here is that we
[5:53] actually did receive that today. Um so
[5:56] it's been signed and it's all completed.
[5:58] Uh so we'll be moving forward with
[6:00] coordinating with the department of
[6:01] health and human services in receiving
[6:02] that data uh in the coming weeks. Um so
[6:06] the home visiting program is a program
[6:08] that is supported by the department of
[6:10] health and human services. Um, Dakota,
[6:12] do you want maybe I I I've kind of
[6:14] provided here the a boilerplate
[6:16] definition of home visiting program, but
[6:18] maybe you probably do a more justice in
[6:21] in providing a a a definition for what
[6:23] the home visiting program is.
[6:25] » Yeah, sure thing. Um, so there home
[6:28] visiting is a very general term. So, the
[6:29] home visiting program that's specific to
[6:31] the office of early childhood over at
[6:32] DHS is the MCV funded um home visiting,
[6:35] which is the maternal infant early
[6:37] childhood home visiting grant uh through
[6:39] the feds under HERSA. Um and we are in
[6:42] almost every county in the state. We're
[6:44] missing just a couple. Um but those
[6:46] consist of the parents' teachers
[6:48] program, uh the family spirit program,
[6:50] the nurse family partnership program,
[6:52] and soon to be MESH maternal early
[6:54] childhood sustained home visiting, which
[6:56] is another nurse-based home visiting
[6:57] model. Um all of the models are focused
[6:59] on uh providing home visiting services
[7:01] to parents uh with children uh either
[7:04] prenatal or age 0 to 5 uh to support
[7:06] them on their parenting journey and make
[7:08] sure those kids are as ready for uh
[7:10] kindergarten and school and future
[7:12] school success as possible. Um and they
[7:14] do a lot of different screening work, a
[7:16] lots of connecting with different
[7:17] resources, but at the end of the day, um
[7:18] it is about supporting those parents to
[7:20] become uh the best parents they can
[7:22] possibly be for their children.
[7:25] » Great. Yeah. So, we're really excited.
[7:27] Um, so some of you may be aware that
[7:30] Department of Health and Human Services
[7:32] manages the EKID system or early
[7:33] education system. Um, this is this is
[7:37] part of a collaboration between us and
[7:40] Ekids in receiving more and more of the
[7:42] same data that they receive. Um, and
[7:45] Ekkids focuses on analytics, on
[7:48] reporting, and UDRC obviously focuses on
[7:51] research. Um, and so it's sort of
[7:53] synergistic the work that we're doing.
[7:55] uh whereas they're focused more on
[7:57] operations uh questions that the
[7:59] operations might have. We focus more on
[8:02] research uh policy questions that um the
[8:06] sort of early education world may have.
[8:09] So uh looking forward to obviously
[8:11] receiving that data in the in the coming
[8:13] weeks um and integrating into our system
[8:16] and obviously making it available for
[8:18] our own researchers as well as external
[8:20] researchers for for to conduct research
[8:22] in that realm. So
[8:25] moving along uh to other data sets that
[8:29] we will be receiving uh we are also in
[8:32] coordination with the department of
[8:32] health and human services in receiving
[8:34] the all pairs claims database. We're
[8:36] very very excited about this data set.
[8:39] It contains a data from health insurance
[8:42] carriers including Medicaid and third
[8:45] party administrators here in the state
[8:46] of Utah. Um this these data are very
[8:51] holistic uh and include anything
[8:53] everything from diagnosis and treatments
[8:56] to cost of care, location of care and so
[8:58] on. If I remember correctly, the table
[9:00] is 1,500 variables wide. Um so it's
[9:04] incredibly detailed as to the amount of
[9:07] information that is included uh in in
[9:10] there. Um where where are we with this
[9:13] one is that we are we have drafted an
[9:16] addendum to the masterou for department
[9:18] of health and human services and they're
[9:20] in the process right now of reviewing
[9:22] that and um hopefully signing it and
[9:25] then sending it back to us for
[9:26] signatures. So at that point in time. So
[9:30] um then the the last um data set that we
[9:35] are
[9:36] additionally coordinating with the HHS
[9:39] to receive is the hospital facilities
[9:40] database. Uh so this is similar to the
[9:43] all pairs claims database but from the
[9:45] hospital side of things. Um so it has um
[9:48] records for all licensed hospitals,
[9:50] emergency rooms and ambulatory surgery
[9:53] centers in Utah. Uh inatient records
[9:55] date from 1992 and other encounters from
[9:58] 1996.
[9:59] Um they represent all hospitalizations,
[10:02] emergency department visits and
[10:04] ambulatory surgeries and diagnosis
[10:06] procedures performed in Utah regardless
[10:08] of pair. Um so again similarly we are we
[10:13] have communicated to department health
[10:15] and human services an addendum to the
[10:16] master NYU they're reviewing um
[10:19] hopefully signing and then sending back
[10:21] to us for signatures. So super excited
[10:25] about receiving all of this new data
[10:27] here at the UDRC. the old pairs claims
[10:30] database will be a huge game changer for
[10:33] the for the sort of research questions
[10:36] we might be able to answer and a and ask
[10:39] as well. Um so an example might be we
[10:43] have ASQ data from uh from DHS as well.
[10:48] Uh we see a child receiving a screening.
[10:52] uh we might be able to see also that
[10:54] they subsequently received diagnosis um
[10:58] and then we will be able to uh link that
[11:01] into their K through2 uh performance and
[11:05] and be able to you know answer questions
[11:07] and ask questions that we had never been
[11:10] able to before in the past. So really
[11:13] excited about that. So any questions,
[11:16] comments or concerns about those data
[11:18] sets that are coming to the UDRC here in
[11:20] hopefully in uh in the next month or
[11:23] two. So
[11:26] okay,
[11:29] in addition to provide an update on some
[11:31] data that we're pursuing. So this is not
[11:34] a guarantee that these are we just
[11:36] wanted to communicate to this group
[11:37] about data that we are looking to um to
[11:42] receive uh and we're we're coordinating
[11:45] with the Department of Health and Human
[11:46] Services on this one as well. Um so
[11:48] we're we're looking to receive Head
[11:50] Start data. Again, this is part of
[11:53] receiving more of the same data that
[11:55] EKIDS receives um to support their their
[11:59] efforts and and also ours. Um so Grace
[12:03] uh Dakota uh has been really
[12:07] instrumental in connecting us with the
[12:09] Head Start um associations. Um and we've
[12:14] just at the very very beginning stages
[12:16] of this whole process of reaching out to
[12:19] them and asking if um we'd be a we'd be
[12:22] able to present to them um our our value
[12:25] proposition for receiving data into the
[12:27] into the UDRC system. Uh so this is very
[12:30] very early stages. They could just they
[12:31] could they could ultimately say no we're
[12:33] not interested and that would be
[12:34] perfectly fine but wanted to provide an
[12:36] update to this group that we are
[12:38] pursuing that data as well. So
[12:44] okay those are all the administrative
[12:46] updates I had. Um I'm going to pass it
[12:49] over to Jay now for the technology
[12:50] update.
[12:52] » Okay.
[12:55] » Hello everyone. Uh my update starts with
[12:58] uh UDRC legacy system uh which is the
[13:03] backbone of UDRC
[13:05] uh bridge. Uh so currently my team and I
[13:08] are maintaining and supporting the
[13:11] existing operational and research needs
[13:13] for legacy and any upgrades to the cloud
[13:17] architecture or any components within
[13:20] legacy system are being uh provided as
[13:23] and when needed. uh but uh with this I
[13:26] also wanted to provide an update on the
[13:28] legacy MPI. So the legacy MPI is uh
[13:32] something that we've worked on or
[13:34] created for the needs of legacy research
[13:39] uh purposes. uh it continues to support
[13:43] uh the existing matching process for
[13:45] legacy MPI but uh the data is
[13:49] deidentified in the legacy MPI and it
[13:53] but it is not designed for a high
[13:55] cadence transactional data transfer
[13:58] system. So we have had to re-engineer
[14:01] the MPI process for bridge which will be
[14:05] able to support a more uh faster
[14:08] matching for transactional data system,
[14:10] faster validation, quicker movement of
[14:13] data between projects of uh Google cloud
[14:17] platform and we will also be able to
[14:21] support for edge case individual
[14:23] matching in case of uh bridge uh data
[14:27] request. So we are trying to create a
[14:31] much faster system a transactional data
[14:34] system for bridge. But legacy MPI is
[14:37] going to provide us the foundational
[14:40] golden record data set which is going to
[14:43] be the authoritative uh person record
[14:46] and remains a critical foundation for
[14:50] identity resolution and person level
[14:52] data matching for bridge. So with this
[14:56] these are all the updates for UDRC uh
[14:59] legacy system. Uh Jeremia if we can go
[15:02] to the next slide. Uh now I will
[15:05] continue on the UDRC bridge updates. Uh
[15:09] UDRC bridge has several uh layers of
[15:12] development ongoing. Uh the first one is
[15:15] the foundation for all bridge operation
[15:18] which is the GCP environment. Uh over
[15:23] the last few months we have completed
[15:25] most of the deployments of uh design
[15:29] development and testing of the GCP
[15:32] environment for bridge and most of the
[15:35] core environment architecture including
[15:38] the application services uh networking
[15:42] uh identity access management and
[15:45] integration of the different layers
[15:48] within the GCP environments have been
[15:50] completed.
[15:51] uh I think overall we are tracking at
[15:53] around 79% completion according to our
[15:56] project forge document uh for the GCP
[16:00] environment uh of bridge and currently
[16:03] we have
[16:05] certain items open still uh in terms of
[16:08] GCP environment which includes the
[16:11] documentation of the final environment
[16:14] uh variables uh a final security
[16:17] completion and a close out UAT before uh
[16:21] it's ready for production from GCP
[16:24] environment. I will move on to the data
[16:26] services which is the backbone of all
[16:29] data ingestion, storage and data flows
[16:32] within into bridge and out of bridge
[16:34] system. Uh most of the data services uh
[16:38] have been completed uh when uh Borwood
[16:42] was completely on boarded with UDRC. Uh
[16:45] so we are tracking at around 85%
[16:47] completion with the project forge for
[16:50] data services and uh with the core
[16:53] design and development complete we are
[16:55] just awaiting uh some of the integration
[16:59] with the other layers of uh bridge
[17:01] applications. So uh some security
[17:04] implementation documentation and
[17:06] testings are remain open for the data
[17:09] services in terms of uh bridge
[17:11] development. Uh if you can go to the
[17:14] next slide Jerma uh this is the MPI
[17:18] services where most of the ma which has
[17:20] been a major area of focus for us over
[17:23] the last few months. Uh so we are
[17:26] designing and developing bridge as a
[17:29] request servicing workflow. So first
[17:32] when an identifying individual uh when a
[17:36] request comes into bridge uh we will be
[17:39] identifying whether that person exists
[17:41] in the golden record and if that person
[17:44] exists in the golden record then we will
[17:46] be validating the source data set from
[17:49] where uh the information has been
[17:51] retrieved into the golden record. If the
[17:54] source data set and the data partner are
[17:57] participating in bridge only then the
[17:59] request will be serviced for the end
[18:01] users otherwise they will be displayed a
[18:04] message that this data cannot be
[18:06] displayed currently as the partner data
[18:08] is not participating with bridge right
[18:10] now. So this is a overarching design for
[18:14] bridge which we are following in terms
[18:16] of uh supplying the data set for anyone
[18:19] who is who is requesting the data set.
[18:21] So with this in mind we have completed
[18:24] the core batch foundation work for uh
[18:28] the algorithm uh the CI/CD setup to test
[18:32] and implement the code as we are
[18:34] iteratively
[18:35] uh processing the data for all of the
[18:38] from all of the data partners and some
[18:41] of the pre-processing and bigquery setup
[18:43] has been completed. Uh major work uh
[18:47] also is going on with the linkage of
[18:49] individuals. So let's say an individual
[18:52] is coming with uh first name, last name
[18:55] and social security number from one data
[18:58] partner and slightly different uh
[19:01] information from another data partner.
[19:03] So we are trying to create uh we are
[19:06] trying to match these individuals or
[19:08] these edge cases so that our
[19:10] probabilistic and deterministic matching
[19:12] pipelines are are able to uh provide the
[19:17] provide the result set in a much faster
[19:20] process and uh with a much more much
[19:23] better confidence interval so that uh
[19:26] the data that we are supplying is the
[19:29] data that the user needs and with this
[19:32] we are also
[19:34] designing and developing a golden
[19:36] record. So golden record is going to be
[19:39] the spine of the bridge data system and
[19:42] also going to be uh supporting the
[19:45] legacy system in a deident for
[19:47] deidentified research data sets. uh
[19:50] while the bridge system will have a PII
[19:54] bearing information so that anyone
[19:56] requesting uh any information can be
[19:59] quickly matched against that and be able
[20:02] to request that service so that the user
[20:04] can receive their results.
[20:07] So uh that's all the updates for MBI
[20:10] services uh with the API and the AMS
[20:13] services which are interlin uh the API
[20:17] development is currently going on. We
[20:19] are currently going through the design
[20:22] uh phase and configuration of the API
[20:24] platform so that the API keys can be
[20:27] provided to the uh end users and we can
[20:30] set a revocation time or automatic
[20:33] revocation if uh the time has passed uh
[20:36] for which the end user was validated to
[20:40] to be receiving the data set for and
[20:43] with the AMS which is the security and
[20:45] governance layer to enable role based
[20:48] access for for data uh data
[20:51] administrators and also for data
[20:53] partners. Most of the development has
[20:56] completed uh some of the uh core uh
[21:00] administ core AMS services are already
[21:03] have already been through design
[21:05] development and testing. uh but uh there
[21:08] are some back-end functionality uh which
[21:11] are already running in UAT but we will
[21:14] still review them as the API services
[21:17] are developed and they are integrated
[21:20] into a one core component of the bridge
[21:22] system.
[21:24] Uh next slide please Jeremas.
[21:29] Uh so the last update for bridge is the
[21:32] UIUX which is the front end for uh
[21:35] bridge application. So that includes the
[21:38] dashboards for administrator, data
[21:40] partners and end users. Most of the
[21:42] development and testing for the UIUX
[21:45] portion of bridge uh was complete and we
[21:48] have provided the required feedback to
[21:51] our third party provider on uh admin
[21:55] dashboards, end users and data partner
[21:57] interfaces. I will be demoing a a a
[22:02] website on development platform uh on
[22:05] GCP right now after my presentation and
[22:08] there are certain remaining open items
[22:11] which we will be tackling as we move
[22:13] forward like some specific login request
[22:16] access data partner workbench uh and uh
[22:20] uh navigation sidebar etc. So overall uh
[22:25] we think around 78% of bridges uh
[22:28] technical infrastructure is now in place
[22:31] but the major area of focus going
[22:33] forward is going to be the MPI logic and
[22:36] validation
[22:37] deploying and integrating the API and
[22:40] the AMS services connecting all of these
[22:43] layers through middleware and finalizing
[22:46] the UI uh dashboards uh for UIT uh for
[22:50] UAT and uh production except acceptance.
[22:55] Uh Jeremas, do you mind if I uh took
[22:57] over the screen share for a minute to
[23:00] demo?
[23:13] Okay. So, this is the administrator
[23:17] uh dashboard. Are you guys able to see
[23:20] my screen?
[23:25] Yeah.
[23:26] » Okay. Uh so this is the administrator
[23:29] dashboard of uh the bridge uh system.
[23:33] You can see on the left pane we have the
[23:35] account management AMS uh messaging uh
[23:39] sorry matching as a service messaging
[23:41] and glossaryy.
[23:43] uh on the activity log page of the
[23:46] dashboard you can see these are all seed
[23:49] or uh sample data set that we have
[23:53] seeded into the current environment and
[23:56] if I go into one of these you'll be able
[23:58] to see how a request actually looks like
[24:02] so the administrator will be able to see
[24:05] who requested the data set what was the
[24:07] use case for which the data was
[24:09] requested the date when it was requested
[24:12] and the expiration date which we will be
[24:15] deciding based on the API key that was
[24:18] uh generated for the user. The total
[24:22] number of rows that this uh request is
[24:26] pulling and a sample number of rows for
[24:30] each of the tables from this uh from
[24:33] where this request is pulling the data
[24:34] set from. So these are all sample data
[24:37] sets. There's no PII information in
[24:39] these. And with this uh uh the
[24:43] administrator can go back to the
[24:45] dashboard look into other data set and
[24:49] there's also the account management
[24:51] where the administrator will be able to
[24:53] see how many users are currently active
[24:56] what are the roles assigned to each of
[24:58] these users their email address name etc
[25:02] and uh there I'll go into the AMS which
[25:06] is the
[25:09] authority manageer management system.
[25:11] Currently there are no master policies
[25:13] assigned but based on the creation ofus
[25:16] for bridge we will be assigning master
[25:18] policies and based on thoseus we will be
[25:22] creating the policies uh which will be
[25:25] guiding the rules for use cases and
[25:28] services and if any user is accessing
[25:32] trying to access a request the
[25:34] administrator will be see will be able
[25:36] to see their access request on uh this
[25:39] dash dashboard page. So you if you see
[25:42] one of these have been approved and one
[25:44] of them have been denied. I can still
[25:47] activate that on uh administrator side
[25:50] and only when the activation has
[25:53] completed only then the data flow will
[25:56] be working for the end user but whenever
[25:58] the administrator has closed this the
[26:01] data will not be flowing for the uh end
[26:05] user who is trying to access this. And
[26:07] this is how it will be working for the
[26:09] data partners as well. If they feel or
[26:12] see that some of the data that they are
[26:14] supplying is uh not uh is not ready for
[26:18] uh bridge, they can turn the data flow
[26:21] for their data sets only on the bridge
[26:24] platform and the data flow will be
[26:26] paused uh until it until the data
[26:29] partner turns it on. And uh moving on to
[26:33] some of the supporting instances of
[26:36] bridge like the uh support page where uh
[26:40] users can create support requests for uh
[26:43] any of the issues that they might be
[26:44] facing and glossery which will be
[26:47] showing um all the uh common questions
[26:51] related to uh the application so that
[26:54] the user can service their request or
[26:56] they can create a support request uh in
[26:58] case they are uh facing any issues.
[27:02] Uh so with that uh I conclude my update
[27:07] uh for the meeting. Any questions,
[27:10] comments or concerns.
[27:17] Okay. Uh back to you.
[27:21] » Thank you. Yeah.
[27:24] Uh one second.
[27:29] I think I'm back here now. I'm going to
[27:33] display.
[27:37] Sorry, one second.
[27:45] Okay.
[27:47] Okay. Um passing it over to the research
[27:50] update. Um over to Ari. Um do you want
[27:53] to start us off?
[27:55] » Yeah. Thank you, Jeremias. So, we have
[27:57] uh some research updates. I'm going to
[28:00] turn it over to the various researchers
[28:02] to talk about their projects and we'll
[28:04] start with Karen.
[28:07] » Uh thank you, Ari. So, the first one
[28:09] that I'm going to talk about is the
[28:11] education and wage outcomes for STEM
[28:14] students. and STEM students who um this
[28:17] research is defined as students who
[28:19] declare um their major as a STEM major
[28:23] um the first time that they declared a
[28:25] major and right now we're working on the
[28:29] data narrative and it is undergoing
[28:32] internal reviews and implementing
[28:34] feedback from internal reviews and um
[28:38] also for this one we'll be um trying to
[28:41] submit this one to an academic journal
[28:44] for publishing
[28:45] So um also we're working on editing down
[28:48] the UDRC version of this report to meet
[28:51] the requirements of um the journals that
[28:54] we will be submitting to. So hopefully
[28:56] we'll be able to update you on that next
[28:58] time we meet.
[29:00] Um and then the next one that I'm going
[29:02] to talk about is licensed employment. So
[29:05] this one is going to look at higher
[29:07] education to lensure and also the wage
[29:10] outcomes for um jobs that require
[29:13] licensing.
[29:15] Um so as of right now initial
[29:17] descriptive and modeling is completed
[29:20] and we will be meeting with our data
[29:23] partners in July sometime. So please be
[29:26] on the lookout for an invite. Um so that
[29:28] will be DWS
[29:30] um DOC and also Yushi. And finally, the
[29:35] last one I will talk about is a a series
[29:39] research on adult learners. So this one
[29:42] is going to look at the outcomes of
[29:44] returning adult learners. So that is
[29:47] defined as someone who left their
[29:49] post-secary education for 2 years or
[29:52] more and then later returned to Yushi.
[29:55] Um right now it is also undergoing
[29:57] internal review. Um so also the feedback
[30:01] from internal review is being
[30:03] implemented and then once that is done
[30:05] it will undergo other reviews as needed
[30:09] and I will turn the time over to Connor.
[30:14] All right. Thank you Karen.
[30:19] So I'm going to start off with uh RA23
[30:23] which is looking at the uh relationship
[30:26] between changing employers and wages. Uh
[30:30] common knowled or research has found
[30:32] that changing employers has found to
[30:34] have an increase in changing or increase
[30:37] in wages. So we wanted to look at this
[30:39] for our Yushi graduates. This is
[30:42] currently going under our internal
[30:44] review and then as the next steps go on
[30:48] I'll implement internal reviews and then
[30:50] it'll head out to the data partners for
[30:53] their thoughts and questions.
[30:55] Next slide please.
[30:58] Uh next project that I am working on is
[31:01] looking at children that participated in
[31:04] the ages and stages questionnaire and
[31:06] their early primary school outcomes. uh
[31:10] a lot of research has shown that ASQ has
[31:13] an adequate predictive value in
[31:15] predicting
[31:17] uh early childhood or early educational
[31:20] outcomes. So this is something that we
[31:23] were very keen on looking into. uh
[31:25] currently this is going under the
[31:28] internal review and again like the other
[31:30] one as the internal review goes on uh
[31:34] I'll implement the comments and then
[31:36] it'll head out to the data partners
[31:41] and then lastly uh this is uh a project
[31:45] from our our a series this one is
[31:48] looking at the states imp investigate
[31:52] state's impact on retaining out of state
[31:54] students
[31:55] from Yushi schools in Utah's workforce
[31:57] after graduating. This is currently uh
[32:00] undergoing internal review and it should
[32:02] be going to external review relatively
[32:05] soon.
[32:07] I believe I'm going to be handing it off
[32:09] to Alisia now.
[32:14] Thanks Connor. Um let's see. The first
[32:17] update I have is on engineering
[32:20] pathways. Um, and for this one, uh, it's
[32:25] currently in internal manager review,
[32:28] excuse me. Um, and I'll also be
[32:31] presenting this one at a conference in
[32:34] July. Um, and so, uh, once manager
[32:39] review is complete, uh, you guys should
[32:41] see that soon for external review. Next
[32:44] slide, please.
[32:47] Um and then for um RA27, this one is on
[32:51] high school math course taking patterns.
[32:54] Um currently that one's in data
[32:57] collection. Um we have initial partner
[32:59] meetings scheduled
[33:01] um as well with with some of you. Um and
[33:07] uh and so yeah, that is currently
[33:10] underway.
[33:12] Next slide, please.
[33:14] Uh and then finally um program outcomes.
[33:17] So this is an a series um that uh was
[33:24] related to some
[33:27] uh requests by the legislature and um
[33:32] OLAG um and has been split into two
[33:36] portions, but both of those portions um
[33:39] have are currently undergoing internal
[33:42] review. Um, and so you should see those
[33:46] uh partners should see those uh pretty
[33:48] soon as well. And I believe that's it
[33:52] for mine.
[33:55] » Great. Thank you, Karen, Connor, and
[33:57] Alicia. So, next, uh, I'll give a quick
[34:01] update on some data requests. So, we've
[34:03] completed a couple data requests. Um,
[34:05] one looks at um
[34:09] and of how um CTE uh is related to uh
[34:13] later outcomes for
[34:16] uh Native American indigenous um
[34:19] students. Uh this one was used as part
[34:22] of a dissertation
[34:24] um for a recently graduated
[34:27] uh PhD. Um and then we have our other
[34:32] one on the economic economic impacts of
[34:35] the University of Utah and uh UTU. Um so
[34:40] this one we've trans this is looking at
[34:42] how you know this is a contract worth
[34:46] with Chemcy Gardner um that Yushi has
[34:50] undertaken or that ChemC Gardener has
[34:52] undertaken for Yushi excuse me. Um and
[34:56] our part of this is fairly narrow. It's
[34:58] basically, you know, what students um
[35:00] are earning um and how kind of bringing
[35:03] in uh out of state students as well
[35:05] helps um with the local economy. Ongoing
[35:09] requests, we are now working on one uh
[35:11] from ASQ and early education outcomes.
[35:14] This sounds similar to uh Connor's
[35:16] research. It's fairly different actually
[35:19] despite
[35:21] you know ASQ and early education
[35:23] outcomes. Um and the next one uh we are
[35:27] in even earlier stages uh similar to the
[35:31] previous uh economic institutions.
[35:34] This one's going to be looking at the
[35:35] economic impacts of the system as a
[35:37] whole. Again, this one's ChemC Gardener
[35:40] or both these two ongoing requests are
[35:42] from ChemC Gardener. Just different
[35:44] researchers in there. Um not pictured,
[35:48] we also had our annual bagels and
[35:50] research. It went well. Um
[35:54] I I think our goal is to do that now
[35:57] every year. Um
[36:00] I know there are representatives from
[36:01] many of the organizations there this
[36:03] year. Uh we really appreciate having
[36:05] everyone there. Um
[36:08] I think everyone appreciates being able
[36:10] to share the research and hear, you
[36:12] know, and hear about it. Uh and it does
[36:14] help keep, you know, the UDRC data and
[36:16] research and then our partners um out in
[36:18] the community as well.
[36:21] So, and those are going to be my uh my
[36:25] updates for data requests and my team's
[36:28] updates for their research. Any
[36:30] questions for any of them or us before I
[36:32] turn it over?
[36:36] Okay. Uh thank you all. Jeremiah, back
[36:39] to you.
[36:40] » Great. Yeah. I'm gonna pass it over now
[36:42] to Britney for the user experience
[36:43] update. Britney,
[36:45] » Hi everyone. So for the UX updates
[36:48] today, I'm going to share our new UDRC
[36:50] website and I'll show a preview of our
[36:52] new P20 first credential dashboard. So
[36:55] we launched our redesigned um UDRC
[36:58] website early last month. So showing it
[37:00] today in case um any of you haven't had
[37:02] the chance to check it out. Um I'll also
[37:05] share a link in the chat
[37:07] so you can go directly there in the
[37:09] chat, but also share my screen and just
[37:11] walk through some of the the new
[37:13] features we have.
[37:20] Okay.
[37:23] Um, so you'll see that we have a new
[37:26] modern design and a new tagline. Smarter
[37:28] data stroker Utah. Uh, we also did a
[37:30] refresh of the UDRC logo. So it's still
[37:33] the same icon mark, but the font and
[37:35] placement of the UDRC name is updated.
[37:38] So you see here, this is our homepage.
[37:40] um some call to actions to view research
[37:43] or to request data and then three of our
[37:46] latest updates down here.
[37:51] » Sorry, just one second. Okay. Um some of
[37:54] our new features include our
[37:55] publications page. Um so you can look at
[37:59] our previous publications um through
[38:01] these different categories. Now if
[38:03] you're just interested in workforce and
[38:05] economy, you can click that and that
[38:06] will help narrow it down.
[38:11] And then uh we have our research agenda
[38:13] here. Um the current one will be posted
[38:17] um sometime tomorrow. Um you can also
[38:19] look at um the past research agendas. We
[38:23] have that archived all here. Um and then
[38:26] for request data um we separated these
[38:29] out into two um request types. So data
[38:32] set requests and analysis requests. We
[38:35] just noticed in the past there's been
[38:36] some confusion on that. So we decided to
[38:38] break it out. So for the data set
[38:40] request, this is what it looks like. Um
[38:42] it explains the different steps and then
[38:45] a button to start it.
[38:48] For the analysis request, it explains
[38:50] what that is here. Um including our data
[38:53] dictionary and then the request form to
[38:56] download right there.
[38:58] Um this is a new events area which shows
[39:01] um our previous recordings from bigles
[39:04] and research as well as this is where
[39:05] we'll we'll put our registration page um
[39:08] as well as past webinars.
[39:10] So you can see the bigles and research
[39:11] page looks like this. So we have three
[39:14] years worth there. Um and then here's
[39:16] some of our past webinars. So every time
[39:18] we release a new research product we do
[39:20] a webinar with it and we'll post the
[39:23] recording here.
[39:25] And then we have the resources page.
[39:27] These are just various documents um such
[39:29] as our governance document, our data
[39:31] dictionary as well as some other
[39:33] resources here.
[39:36] Uh under about us, um we broke this out
[39:39] into a few different subpages just to
[39:41] help um break out some of this
[39:44] information
[39:46] um about us. So we have this general
[39:47] about us and then we have our history
[39:49] explaining where how UDRC came about and
[39:52] where we are today.
[39:55] Um our team with some lovely pictures
[39:59] and then this is um newer where we have
[40:02] a data partners page where we put a
[40:04] little bit more explanation of what kind
[40:06] of data we are getting from each
[40:07] partner.
[40:09] So that's our website.
[40:14] Okay. So next um I'll show a preview of
[40:16] our upcoming dashboard on Utah's
[40:18] education to workforce pipeline which
[40:20] features first credentials and main
[40:21] milestone
[40:23] which I have here.
[40:30] Um, so first credential, if you haven't
[40:32] heard, this is a new statewide
[40:33] initiative. It ensures that that every
[40:35] high school student graduates with their
[40:37] first credential along with their
[40:39] diploma. So this dashboard looks at the
[40:42] different data highlights in K through
[40:44] 12 um post-secary and workforce data
[40:47] within the context of how they are
[40:49] supporting leading up to that first
[40:50] credential and also how that first
[40:52] credential helps support future college
[40:55] completion and workforce participation.
[40:57] So you'll see throughout this dashboard
[40:59] we pull metrics from various data
[41:02] sources um to help show those statewide
[41:04] trends and we try to do at least like a
[41:06] five-year look back on each one. some of
[41:09] them we didn't have enough data. Um
[41:10] maybe it's like three years back. Um but
[41:12] for the most part it's five years um at
[41:14] different um major points in the
[41:16] pipeline. Um but the overall purpose of
[41:18] this dashboard is to help determine um
[41:20] areas for improvement in early learning
[41:24] to help support first credentials um and
[41:26] also to monitor post-secondary um
[41:28] success and workforce alignment.
[41:31] So I'll just show um some of these pages
[41:34] um so you can get an idea.
[41:39] So for early foundations, we're looking
[41:41] at Aadian um reading levels K through
[41:44] three. Um looking back over time and
[41:46] seeing the difference here. So you'll
[41:48] notice on each page, we'll put the
[41:49] percentage point difference over the
[41:51] timeline that we're looking at. And then
[41:53] if someone wants to learn more about
[41:55] Aadian or this data, they can click
[41:57] here, learn more on the bottom right,
[41:59] and that will take them to the USB um
[42:01] data page about this.
[42:06] For the next one, high school readiness.
[42:09] Uh we pull data from NAPE. Here we're
[42:11] looking at fourth grade and eighth grade
[42:13] reading and math proficiency levels. Um
[42:17] we have overall comp comparisons as well
[42:19] as we could break it um through
[42:21] different Utah state, sorry, Utah
[42:23] student population groups.
[42:25] Uh we have a little write up here on the
[42:27] right about what it is and again a learn
[42:28] more button where it will take you
[42:30] directly to that NAPE data.
[42:35] Okay, first credentials. This is where
[42:36] we pulled a lot of like um new data that
[42:38] we haven't really shared before. So um
[42:41] here on the top left, these are the
[42:43] pathway indicators for first
[42:45] credentials. So for example, current
[42:46] enrollment is a pathway. Here we pulled
[42:49] participation rates over the past five
[42:50] years and showing the difference um over
[42:53] time. Here uh we have enrollments in CTE
[42:56] courses. Sorry, my internet's not
[42:58] working. Um but so different different
[43:01] filters. You can look at CTE courses.
[43:03] You can look at tech college completion
[43:05] rates, general ed certificate
[43:08] completions, as well as youth
[43:09] apprenticeships and looking at those um
[43:12] rates over time. We also include the
[43:14] high school cohort graduation rates over
[43:16] time by um different populations. So,
[43:19] this helps provide kind of like an
[43:21] overview baseline look of how we're
[43:23] doing with first credentials. And this
[43:25] is something we can look at each year um
[43:27] and see how how the participation is
[43:29] changing over time or the completion
[43:31] rates.
[43:34] The next one we have is um college
[43:37] success. So here we have um currently
[43:41] right here it's on the technical
[43:42] colleges um certificate completion um
[43:46] time to uh certificate rates. So you
[43:49] you'll see we have it broken down by
[43:50] each institution as well as the average
[43:52] um line for all of them. So looking at
[43:54] 100% of normal time, 150% and 200%.
[43:59] And then we also have see if this will
[44:02] reconnect
[44:03] uh our bachelor's cohort. So looking at
[44:06] it by each institution, four years after
[44:08] entry, six years and eight years and
[44:11] then we have our um percentage point
[44:13] difference over time here on the top
[44:14] left. We also included first year
[44:16] enrollments at Yushi of Utah High School
[44:18] graduates. um here on the left.
[44:25] Okay. Then finally, we have workforce
[44:26] alignment. This comes from Yushi's
[44:28] workforce outcomes dashboard. Here we
[44:31] pulled bachelor, associate, and
[44:33] certificate graduates.
[44:36] Um looking at um their employment,
[44:39] they're working in Utah um eight
[44:41] quarters after their graduation.
[44:44] And then we also um pulled their
[44:46] salaries. So you can see their change
[44:47] there from one year to five year after
[44:49] graduation.
[44:53] So uh so overall this dashboard it
[44:55] provides like a nice one-stop area to
[44:57] see these major indicators and how
[44:59] they're doing over time um in relation
[45:02] to first credential and uh so this is a
[45:04] preview so it's not final. So we're
[45:06] sending this out to our partners soon
[45:07] for their review and um thanks to way
[45:11] she did a lot of the heavy lifting on
[45:12] this project.
[45:14] So, I'm going to stop sharing. Were
[45:16] there any questions
[45:19] about any of those projects
[45:23] and thanks for your comment, Mark? Um,
[45:25] saying great website. Thank you.
[45:33] » Okay, no questions. I'll pass it back to
[45:34] Jeremas.
[45:36] » Great. Excuse me. Great.
[45:39] Um, I'll dispense of the the uh
[45:42] PowerPoint presentation since we only
[45:43] have two more slides. Um, the next
[45:46] section was going to be public comment.
[45:48] Um, I technically don't see any members
[45:52] of the public um on our meeting here.
[45:55] Um, everyone's either did a partner or a
[45:58] UDRC employee. So, um,
[46:02] I I don't think we're going to have any
[46:03] public comment today. So, um, then last
[46:06] slide is just to thank you as always.
[46:08] Thank you so much for your coordination
[46:10] and continued collaboration in this
[46:12] project that we call the UDRC. Uh we
[46:15] could not um do the work that we're
[46:17] doing without that component, your your
[46:20] side of the equation. So thank you so
[46:21] much as always and looking forward to
[46:24] meeting or meeting again in in in 6
[46:26] months time to provide another update.
[46:28] Uh hopefully we'll have a lot more to
[46:30] update on bridge uh next time uh and
[46:33] obviously all research and UX. So um if
[46:37] there are no further questions this time
[46:40] uh we'll adjourn the meeting. So have a
[46:42] wonderful day. Thank you.
[46:44] » Thank you. Bye.
[46:46] » Thanks everyone.