# data[].attributes.body
I am drawn to (E) Seamless and equitable pathways and opportunities for youth to access mental health and wellness supports. and (F) Quality youth programs and services informed by and tailored to the needs of those they are intended to serve. The access and quality pieces have been framed as what the other indicators are in service of, so it feels important to hold those central. For (E) I would share that all collaboratives have changes to policy or practice to make services more accessible, with examples that include eliminating program fees, offering services in multiple languages, and tangible steps towards culturally responsive mental health spaces. For (F) I'd share that almost all collaboratives can name examples of making changes to services and programs that were directly in response to youth input and feedback. [EB]

# data[].attributes.body
Ash was excited about activities under (C) Codified commitment to youth mental health among organizational, philanthropic, and health system leaders. That is where she sees the work as being imbedded/becoming permanent. Here, I'd share that all collaboratives are engaged in conversations with funders to influence funders’ commitment/interest in investments in youth mental health and to date, over 20M has been secured by collaboratives partners through working together as a result of the grant. [EB]

# data[].attributes.body
Jessi was excited about activities under (B) Understanding, fluency, and normalization of mental health among community members and adults who interact with youth. She felt it was the leverage point for change and the heart and soul of what they are doing. Here, I'd elevate B3, where cumulatively 2815 youth-serving providers have been trained to recognize and/or screen for mental health concerns, and all five collaboratives are reporting data in this area.  [EB]

# data[].attributes.headline
A2. Number of institutionalized changes in organizational policy or practice to support communication, coordination, and data sharing (revised) - SDL

# data[].attributes.subject
A2. Number of institutionalized changes in organizational policy or practice to support communication, coordination, and data sharing (revised) - SDL

# data[].attributes.body
Lots of great examples of what feels huge in terms of building shared infrastructure!

LM: Two new processes shared by NAMI Peers and LifeMoves help to coordinate services and information sharing:  a shared spreadsheet to track client outreach, and a referrals system within the LifeMoves database. (IEIPHY)

The RWP developed a common referral form shared among partners.

WHYI partners added common survey questions to each agency's own youth evaluation survey to uniformly gather information across partners. (WHYI)

# data[].attributes.headline
B3. Number of youth-serving providers trained to recognize and/or screen for mental health concerns (2815, 1-1274, 5) - SH

# data[].attributes.subject
B3. Number of youth-serving providers trained to recognize and/or screen for mental health concerns (2815, 1-1274, 5) - SH

# data[].attributes.body
Overall - Big number! Spread across collabs (though about half are CalSAC). Tentacles.
Fave example - None of the examples really jump out at me. This one feels like the number is what's most interesting.

# data[].attributes.headline
E1. Number of changes to policy or practice to make services more accessible (e.g. language, cost, waitlist) (19, 2-12, 4) - SH

# data[].attributes.subject
E1. Number of changes to policy or practice to make services more accessible (e.g. language, cost, waitlist) (19, 2-12, 4) - SH

# data[].attributes.body
Overall - Went back and forth between E1 and E2, and could be swayed either way. I landed on E1 because of the broader implications of changes making services more accessible vs. changes facilitating an efficient referral system which may or may not lead youth to accessible services.
Fave example (OSTPDWN) - Program fees were eliminated at two sites.

# data[].attributes.headline
A2. Number of institutionalized changes in organizational policy or practice to support communication, coordination, and data sharing (143, 1-28, 5) - SH

# data[].attributes.subject
A2. Number of institutionalized changes in organizational policy or practice to support communication, coordination, and data sharing (143, 1-28, 5) - SH

# data[].attributes.body
-Overall - Institutionalized changes feel like the sticky bits that will lead to true systems change, it's heartening to see that all five collabs have data to report on this measure, and feels appropriate that this would be the case at this point in the initiative.
-Fave example (RWP) - The RWP developed a common referral form and shared among partners. Simple, but potentially impactful.

# data[].attributes.headline
F3. Changes to services/programs implemented in response to youth input (21, 1-12, 4) - SH

# data[].attributes.subject
F3. Changes to services/programs implemented in response to youth input (21, 1-12, 4) - SH

# data[].attributes.body
-Overall - May prefer this to F1, bc it is explicit that changes are youth informed. Though, number of changes is smaller and only 4 of the 5 collabs reported data on this.
-Fave example (allcove) - With the SCC allcove centers opening in June, several new procedures, hires, and design decisions were needed. All of the following were completed with youth input: intake and reg process, services and programs, staff hiring, design decisions, partner collaboration, community engagement, and evaluation.

# data[].attributes.headline
F1. Changes to policy or practice to make services more youth appropriate and appealing (37, 1-14, 5) - SH

# data[].attributes.subject
F1. Changes to policy or practice to make services more youth appropriate and appealing (37, 1-14, 5) - SH

# data[].attributes.body
-Overall - all collabs have made changes to policy or practice to be more youth informed, yay!
-Fave example (WHYI) - Youth revised FFY's group mentoring curriculum to make it more youth-centered and co-facilitated youth trainings to make them more culturally relevant (

# data[].attributes.body
Description of the systems change