Update Foster Youth Data Fields & Logic Per State Legislation AB12

This results in some foster youth applicants checking ‘no’ to the foster youth question because they cannot decipher which of the five sub-responses they should choose. When this occurs, these students may miss out on essential benefits available to foster youth that will help them stay in school. In addition, these students are then missing from data collection efforts that are used to inform equity planning and ensure that an adequate level of support is being provided to students with experience in foster care.

Steering Feedback - Steering requested research data to support this theory/reason; however, data was unavailable. Nevertheless, Steering did agree that the question is a bit complicated overall.

Prior to the extension of foster care in 2012, youth emancipated from the foster care system at the age of 18. In 2012 the availability of foster care was extended up to age 20. With this change the language in CCCApply was rendered obsolete, but it had not been updated.  Debbie Raucher at the John Burton Foundation also stated that in addition, the definition of ‘emancipated’ used in CCCApply is incorrect. In the context of foster care this does not refer to “emancipated minors” but rather is synonymous with the concept of ‘aging out’ on or after one’s 18th birthday.

Steering Feedback - Steering notes that the residency requirements for foster youth are different than the legislature that extends benefits beyond age 18. Our logic changes will reflect what we need for residency and some of our logic will not change. Details will be specified below in the Change Specifications section.

The statute provides that a student who currently resides in California and is 18 years of age or under at the time of enrollment, who is currently a dependent through California’s child welfare system, or aged out after age 18 may be entitled to resident classification until he or she has resided in the state the minimum time necessary to become a resident. This is designed to allow a youth who is a dependent through California’s child welfare system (i.e. California retained jurisdiction over the case) who does not otherwise qualify for residency because the youth was placed out of state, or because the biological parents reside out of state, to attend college as a California resident.

Steering Feedback - Again, Steering approves the solution below to the residency logic that complies with the California residency requirements and MIS reporting. They are less concerned with incorporating any logic or changes for priority registration. The flag 71 is being introduced to identify this determination.

The current question asks about whether the youth was in foster care ‘in California’ which is an ambiguous question. It will be interpreted by most as whether the youth resided in California as opposed to a jurisdictional determination of which state had responsibility for the case. To determine which state had jurisdiction over a student’s foster care case is complicated and is not realistic to determine through CCCApply. As these students must be flagged for a follow up residency determination regardless of which foster care subcategory they select, it is unnecessary to include this level of detail in the CCCApply question.  

Steering Feedback - Steering agrees with this problem and our solution is designed to simplify the question, responses and logic all around.

Revise the "Data Element & Logic" action in Step 4 of the Area B residency logic from "ca_foster_youth = Yes"  TO: "foster_youth_status is NOT = 0 AND RDD* minus Birthdate < 20 years".  

• There are no changes made to the Evaluation Statement and no changes to the IF YES  and IF NO statements.  
• Instead of using the Foster Youth in California field plus the date of birth, the logic was changed to using the new Foster Youth Status AND the date of birth,extending the scope of potential eligibility to ANY applicant that has a Foster Youth Status that is NOT "=0" and under 20 years of age (19 years or younger). 
• If YES, then Class B2 and FLAG 70 is set.  
• If NO, then set B0  and end the logic there. This is what the existing logic prescribes.  The only change to Area B is the logic is now based on the Foster Youth Status field plus the applicant's DOB, instead of the <ca_foster_youth> field only. This is outlined in the Area B table below. 

NOTE:  The first three steps of Area B logic do not change. See the changes to Step 4 in the Table B below. If the logic takes the student to Step 4 - the revisions described above will either classify the student as B2/Flag 70, or they will be classified as B0 and the logic will end there. 

See Table B Residency Table for details.

This field logic is used in the Area B residency algorithm. Changes to field logic are shown in red below.

Data Element: residency: ca_foster_youth

Description: Determines if an applicant who may not otherwise qualify as a resident should be flagged (flag 70) as potentially qualifying for CA residency based on foster care status. A “1” value indicates the applicant may be a current foster youth or a youth who was in foster care at age 18 and was under 20 years of age at RDD. A "0" value indicates that the applicant is either over age 19 (20 or over), or has indicated they were never in foster care.

Values: The calculation for how to set this field based on the foster_youth_status field. This field is used in the Residency Algorithm.

AB669 Eligibility = Yes  IF (foster_youth_status=1 OR =2 OR = 6) AND (RDD* minus Birthdate < 20 years)

AB669 Eligibility = No IF  (foster_youth_status=0 OR =3 OR =4 OR =5) OR (RDD* minus Birthdate is ≥ to 20 years)

This field is NOT used the Area B residency algorithm. The changes below pertain to field logic only. Changes to values & logic appear in RED below.

Data Element: foster_youth_priority

Description: Calculated result for AB194 (priority registration) eligibility. Eligibility is defined as being a current foster youth or former foster youth who was in foster care as of the applicant’s 18th birthday and under age 25.

Values: AFTER the foster_youth_status field has been set, set the value of foster_youth_priority as follows:

AB194 Eligibility = No  IF (foster_youth_status=0 OR =5) OR (RDD* minus Birthdate ≥ 25 years)

AB194 Eligibility = Yes  IF (foster_youth_status=1 OR =2 OR =3 OR =4 OR =6 ) AND (RDD* minus Birthdate < 25 years) THEN Set new Flag 71

This field is NOT used the Area B residency algorithm. The changes below pertain to field logic only. Changes to values & logic appear in RED below.

Data Element: foster_youth_mis

Description: Derived field based on foster_youth_status. Any foster youth option THAT IS NOT  = 0,  sets the value to “yes.” (In other words, foster youth status = 1, =2, =3, =4, =5, =6 , equals YES).  NOTE:  Even though = 3 and =4 are no longer used, we can keep them in the logic for assurance that in case the values should appear, they will be considered eligible.)

Values: AFTER the foster_youth_status field has been set, set the value of foster_youth_mis as follows:

1 MIS SG03 = 1 foster_youth_status=1 OR =2 OR =3 OR =4 OR =5 OR =6 

0 MIS SG03 = 0 foster_youth_status=0

Foster Youth Status Data Field <foster_youth_status> 

1. 1. Change capitalization in onscreen question text (change Foster Care to foster care)
   2. Revise Additional Text
   3. Revise/Remove-Retire/Add new data values/response options
   4. Replace existing Pop-Up Help Text boxes with four new Pop-Up Help Text boxes
      
      

California Foster Youth Data Field <ca_foster_youth>

1. 1. Revise data spec heading - remove note about question being obsolete
   2. Edit the New Combined DD - strike-through all specs related to the Form Specification (see below)
   3. Keep the specs related to the data element and logic within the data field only (no strike-through)
   4. Revise field logic using the new Foster Youth Status values/response options
       

Foster Youth Priority Data Field <fy_priority>

1. 1. Revise field logic using the new Foster Youth Status values/response options
   2. Add logic for setting Integrity Flag 71 within field
       

Foster Youth MIS Data Field <fy_MIS>

1. 1. Revise field logic using new Foster Youth Status values/response options
       

Integrity Flags Table (Flag 70)

1. 1. Update Integrity Flag 70 language and logic reference in the Integrity Flags Table 
       

Integrity Flags Table (Flag 71 - NEW Download Data Field)

1. 1. Add new Integrity Flag 71 to Integrity Flags Table
   2. Add new integrity flag 71 data field to the Download Client User Guide (it's a downloadable field and used in reporting)
       

Area B Logic (Step 4)

1. 1. Update Step 4 of the Residency Table B (Area B Logic) and corresponding Flowchart 

New Download Data Field: Integrity Flag 71

1. 1. Add new download field <int_fg_71> to Standard Application Data Fields table
   2. Add new download field <int_fg_71> to the Rules area of the CCCApply Administrator for rules
   3. Add new download field <int_fg_71> to the Submitted Applications data source in the CCC Report Center for reporting 

(Foster Youth Status <foster_youth_status> response options/values & logic changes appear in RED below.)

Data Element: residency: ca_foster_youth

Description: Determines if an applicant who may not otherwise qualify as a resident should be flagged (flag 70) as potentially qualifying for CA residency based on foster care status. A “1” value indicates the applicant may be a current foster youth or a youth who was in foster care at age 18 and was under 20 years of age at RDD. A "0" value indicates that the applicant is either over age 19 (20 or over), or has indicated they were never in foster care.

Values: The calculation for how to set this field based on the foster_youth_status field. This field is used in the Residency Algorithm.

AB669 Eligibility = Yes  IF (foster_youth_status=1 OR =2 OR = 6) AND (RDD* minus Birthdate < 20 years)

AB669 Eligibility = No IF  (foster_youth_status=0 OR =3 OR =4 OR =5) OR (RDD* minus Birthdate is ≥ to 20 years)
 

Example 1: Birthdate on the day of RDD minus 20 yrs

RDD = 2015-01-04
Birthday (RDD-20yrs) = 1995-01-04

• • If this user clicks the radio button for "1 = I am currently in foster care (including extended foster care after age 18).", or "2 = I aged out/emancipated from foster care or exited voluntarily on or after my 18th birthday," or "6 = I am not sure at what age I exited foster care." and RDD is 1/4/2015 then NO, the user is NOT eligible for AB669.

Example 2: Birthdate before RDD minus 20 yrs

RDD = 2015-01-04
Birthday (RDD-20yrs) = 1995-01-02

• • If this user clicks the radio button for "1 = I am currently in foster care (including extended foster care after age 18).", or "2 = I aged out/emancipated from foster care or exited voluntarily on or after my 18th birthday," or "6 = I am not sure at what age I exited foster care." and RDD is 1/4/2015 then NO, the user is NOT eligible for AB669.

Example 3: Birthdate after RDD minus 20 yrs

RDD = 2015-01-04
Birthday (RDD-20yrs) = 1995-01-05

• • If this user clicks the radio button for "1 = "I am currently in foster care (including extended foster care after age 18).", "2 = I aged out/emancipated from foster care or exited voluntarily on or after my 18th birthday," or "6 = "I am not sure at what age I exited foster care." and RDD is 1/4/2015 then YES, the user is eligible for AB669.
    
    

Example 4: User Chose No Radio Button

RDD = 2015-01-04
Birthday = 1999-01-04

• • If this user clicks the No radio button for "Have you ever been in court-ordered foster care?" then NO, the user is NOT eligible for AB669.
     

Example 5: User chose value 5 "I exited the foster care system before my 18th birthday." 

RDD = 2015-01-04
Birthday = 1999-01-04 

• • If this user clicks the radio button for "5 = I exited the foster care system before my 18th birthday." and RDD is 1/4/2015 then NO, the user is NOT eligible for AB669.
    
    

Example 6: User chose value 6 I am not sure at what age I exited foster care. 

(Foster Youth Status response options/values & logic changes appear in RED below.)

Data Element: foster_youth_priority

Description: Calculated result for AB194 (priority registration) eligibility. Eligibility is defined as being a current foster youth or former foster youth who was in foster care as of the applicant’s 18th birthday and under age 25.

Values: AFTER the foster_youth_status field has been set, set the value of foster_youth_priority as follows:

AB194 Eligibility = No  IF (foster_youth_status=0 OR =5) OR (RDD* minus Birthdate ≥ 25 years)

AB194 Eligibility = Yes  IF (foster_youth_status=1 OR =2 OR =3 OR =4 OR =6 ) AND (RDD* minus Birthdate < 25 years) THEN Set Flag 71

Example 1 Birthdate on the day of RDD minus 25 yrs

RDD = 2015-01-04
Birthday (RDD-25yrs) = 1990-01-04

• • If this user clicks the radio button for "I am currently in foster care (including extended foster care after age 18).", I aged out/emancipated from foster care or exited voluntarily on or after my 18th birthday," or "I am not sure at what age I exited foster care." then NO, the user is NOT eligible for AB194.

Example 2: Birthdate before RDD minus 25 yrs
RDD = 2015-01-04
Birthday (RDD-25yrs) = 1990-01-02

• • If a user clicks the radio button for "I am currently in foster care (including extended foster care after age 18).", I aged out/emancipated from foster care or exited voluntarily on or after my 18th birthday," or "I am not sure at what age I exited foster care." and RDD is 1/4/2015 then NO, the user is NOT eligible for AB194.

Example 3: Birthdate after RDD minus 25 yrs
RDD = 2015-01-04
Birthday (RDD-25yrs) = 1990-01-05

• • If a user clicks the radio button for "I am currently in foster care (including extended foster care after age 18).", I aged out/emancipated from foster care or exited voluntarily on or after my 18th birthday," or "I am not sure at what age I exited foster care." and RDD is 1/4/2015 then YES, the user is eligible for AB194 and the system needs to set Flag 71 in the DB.

Example 4: User Chose No Radio Button

RDD = 2015-01-04
Birthday (RDD-25yrs) = 1990-01-04

• • If this user clicks on the No radio button for Have you ever been in court ordered Foster Care? then NO, the user is NOT eligible for AB194.

Example 5: User chose value 5 "I exited the foster care system before my 18th birthday."
RDD = 2015-01-04
Birthday = 1999-01-04

• • If this user clicks the radio button for value 5 "I exited the foster care system before my 18th birthday." then NO, the user is NOT eligible for AB194.

Example 6: User chose value 6 I am not sure at what age I exited foster care.
RDD = 2015-01-04
Birthday = 1999-01-04

• • If this user clicks the radio button for value 6 " I am not sure at what age I exited foster care." and RDD is 1/4/2015 then YES, the user is eligible for AB194 and the system needs to set Flag 71 in the DB.

Example 7: Edge Case 1 - User who is less than 25 chose disabled foster youth statuses 3 , "I am currently in Foster Care in a system outside California" or 4, I was previously in Foster Care in a system outside California, and aged out or emancipated from the system prior to code push.

• • Before the changes are pushed to the CI environment, the QA team will need to set up a scenario where a user chose value 3 or 4 and then hit save. After the new code gets pushed to CI, the user will be forced to choose a new available option since values 3 and 4 are no longer available.

Example 8: Edge Case 2 - User who is less than 25 chose disabled foster youth statuses 3 , "I am currently in Foster Care in a system outside California" or 4, I was previously in Foster Care in a system outside California, and aged out or emancipated from the system after they already validated the page.

• Before the changes are pushed to the CI environment, the QA team will need to set up another scenario where a user starts an Apply application, fills out the Residency page and selected either option 3 or 4 for the Have you ever been in Court Ordered Foster Care?  The user will need to navigate through the application until they reach the review page. The user will then need to Log out. After the new code gets pushed to CI, the user will need to resume the application. The user should start on the review page (be sure to NOT go back to the page where you select that foster youth status) and then submit the application.  The expected results is the system will store the original chosen 3 or 4 value AND that their AB194 Eligibility = Yes and flag 71 should be set in the DB.

(Foster Youth Status response options/values & logic changes appear in RED below.)

Data Element: foster_youth_mis

Description: Derived field based on foster_youth_status. Any foster youth option THAT IS NOT  = 0,  sets the value to “yes.” (In other words, foster youth status = 1, =2, =3, =4, =5, =6 , equals YES).  NOTE:  Even though = 3 and =4 are no longer used, we can keep them in the logic for assurance that in case the values should appear, they will be considered eligible.)

Values: AFTER the foster_youth_status field has been set, set the value of foster_youth_mis as follows:

1 MIS SG03 = 1 foster_youth_status=1 OR =2 OR =3 OR =4 OR =5 OR =6 

0 MIS SG03 = 0 foster_youth_status=0

Example 1 - User chose 0, so foster_youth_mis is set to false in the DB

Example 2 - User chose either 1,2,5,6, so foster_youth_mis is set to true in the DB

Example 3 - Edge case 1: User chose disabled foster youth statuses 3 , "I am currently in Foster Care in a system outside California" or 4, I was previously in Foster Care in a system outside California, and aged out or emancipated from the system prior to code push, 

• • Before the changes are pushed to the CI environment, the QA team will need to set up a scenario where a user chose value 3 or 4 and then hit save. After the new code gets pushed to CI, the foster_youth_mis would be set to true in the DB.

Example 4 - Edge Case 2 - User chose disabled foster youth statuses 3 , "I am currently in Foster Care in a system outside California" or 4, I was previously in Foster Care in a system outside California, and aged out or emancipated from the system after they already validated the page. 

• • The user will need to navigate through the application until they reach the review page. The user will then need to Log out. After the new code gets pushed to CI, the user will need to resume the application. The user should start on the review page (be sure to NOT go back to the page where you select that foster youth status) and then submit the application.  The expected results is foster_youth_mis would be set to true in the DB.