Page Comparison

Problem Statement or Business Need

For documentation and history purposes, this section will outline the reasons for this change request.

Petitioned by the CCCCO (MIS) and the John Burton Foundation, citing new state legislation for current and former foster youth (AB12), the CCCApply Steering Committee has approved revisions to the Foster Youth question in the CCCApply standard application, including the Foster Youth Status data field values, data field logic (one or more related Foster Youth data fields), a new Integrity Flag (71), and corresponding changes to the Area B (Stay & Intent) residency logic.  

Overview

The Chancellor’s Office (representing the colleges) and JBF feel our current question is too complex because it’s trying to determine the status of three different things simultaneously:

• Whether a student was ever in foster care in any state

• Whether the student qualifies for priority registration

• Whether a student qualifies for an exception to residency status

There are a number of problems with the current question:

• The language is confusing which leads to incorrect responses.

• The language does not reflect the current foster care structure since the extension of foster care up to age 20 (for AB669) and up to 25 (AB194) and provides an incorrect explanation of the term ‘emancipated’ as used in the context of child welfare.

• The residency classification process does not coincide with the actual law in statute.

Proposed Solution

Problem Statements:

Note: These problems were submitted by Debbie Raucher at the John Burton Foundation. Several Steering members disagree with her anectdotal reasoning and research data. However, below are the primary factors contributing to the approved change specifications itemized herein. 

1. The current configuration of the question is complicated and confusing.

This results in some foster youth 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 does not fully agree with this anecdotal theory.  hey have no data to back up this claim - which Steering has requested.  We disagree that the initial question is confusing to the point that the student gives up trying to self-identify. However, we do agree that the question is too complicated overall.

2. The language does not reflect the current foster care structure and provides an incorrect explanation of the term ‘emancipated.’ 

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 until age 20. With this change the language in CCCApply was rendered obsolete, but it has not been updated. 

Steering Feedback - Steering takes issue with this statement as 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 and some of our logic will not change. Details will be specified below in the requirement changes.

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.

3. The residency classification language does not coincide with the actual law in statute.

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 doesn't completely agree with this statement and the solution below will include residency logic based on 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.

4.  The current Foster Youth Status field is trying to determine California residency in addition to foster youth status.

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.

Requirements Summary

The solution to the above issues requires several modifications, including

• Modifying the option choices in the Foster Youth Status field <foster_youth_status>
• Updating the hyperlinked Help “pop-up” language
• “Translating” the answer choices to match the current data field logic 
• Adding one additional flag option. No new fields are proposed.

Change Specifications

Example 2: Birthdate before RDD minus 20 yrs

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

Example 3: Birthdate after RDD minus 20 yrs

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

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 

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 "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 7: 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 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 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 would make them ineligible for AB669 Eligibility = No and flag 70 is not set in the DB.

Foster Youth Priority  

 (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 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.

• • 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 MIS  

(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

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.

Update Residency Area B Logic Based on New Foster Youth Status Data Specifications 

a) The new Foster Youth Status response options / values affect the Area B Residency Logic in the following ways:

i)  In 2013, the Area B residency logic was updated so that ALL USERS would pass through Step 4 of the logic regardless of the results of Steps 1 - 3. This  - regardless of Step 4 of the Area B logic is reRevise the "Evaluation Statement" in Step 4 of Area B Residency Logic from "Is the applicant a current or former Foster Youth, under age 20, and now residing in California?"  TO "Is the applicant a current or former Foster Youth,under age 20, and now residing in California?  

b) Revise the "Data Element & Logic" action FROM "ca_foster_youth = Yes"   TO   "foster_youth_status is NOT = 0 AND RDD* minus Birthdate < 20 years"

c) No change to the IF YES  and IF NO statements. 

NOTE to Developers:  If the student has a Foster Youth Status that is NOT "=0" and they are under 20 (19 years or younger) - they should be classified as CLASS B2 and set FLAG 70.  This is what the existing logic prescribes.  The only changes to Area B are:  1)We are extending the eligibility age from 19 or younger  to 20 years old or younger; and 2) 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. Per 1/25/2016 meeting with Debbie Raucher, John Burton Foundation, the age for AB669 (residency) is 19 years or younger / UNDER 20 (NOT 21) for all residency DOB calculations. All the rest of the changes (changes to the Foster Youth status values) is CORRECT.

The first three steps of the Area B logic do not change. 

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.

d) Report Center and Administrator Work - Ensure this new Integrity Flag 71 data field <integrity_fg_71> is added to the Database so the Administrator can pull it in to the available fields for Rules, and it's added to the Report Center for ad hoc reporting.  (Patty created JIRAs to add this flag to the Administrator for Rules CRTLCENTER-153  and Report Center REPORT-61  for the report additions).

e) Spec Change Only/No Development Work - Update the Integrity Flags Table in the Submission Calculation Service specifications for Flag 70, which is set if the applicant meets the criteria for Step 4 of the Area B residency logic.  Revise the flag language to update the age from "under 20 years of age" to "under 21 years of age"; and Replace flag logic notation from "ca_foster_youth = 1" TO "See Residency Area B Logic" 
 

Table B. Outline of Area B (Stay and Intent) Criteria in Residency Algorithm

Step

Evaluation Statement

Data Elements & Logic

if Yes

if No

1

Do out-of-state indicators support intent?

ca_outside_tax = 0 AND ca_outside_voted = 0 
AND ca_outside_college = 0 AND ca_outside_lawsuit = 0

Go to step 2

Class B0

(go to step 2)

2

Has the applicant lived in California for two years prior to RDD?

ca_res_2_years = 1

Go to step 5

Go to step 3

3

Has the applicant been resident in CA for over a year prior to RDD?

ca_date_current  ≠ null AND ca_date_current 
< RDD minus 1 year

Class B2

(flag 59);

go to step 5

Go to step 4

4

Is the applicant a current or former Foster Youth, 
under AGE 20, and now residing in California?

ca_foster_youth = Yes

foster_youth_status is NOT = 0 AND 
RDD* minus Birthdate < 20 years

Testing Examples:

NOTE: Applicant must be 19 or under (under 20 years of age) 
to be eligible for B2 status & Flag 70

Example 1 - foster_youth_status is not 0 and user is under 20 on RDD, then yes.

Example 2 - foster_youth_status is not 0 and user is 20 on RDD, then no.

Example 3 - foster_youth_status is not 0 and user is 20 or over on RDD, then no.

Example 4 - foster_youth_status is 0, then no.

NOTE: Developer to write unit tests for all scenarios.

Class B2;

go to step 5

(flag 70)

Class B0;

end

5

Has the applicant completed HS outside CA in last 2 yrs?

education: hs_state’ ≠ CA AND 
education: hs_comp_date ≥ RDD minus 2 years

Class B2

(flag 61);

go to step 6

Go to step 6

6

Is the applicant in military with non-CA home of record?

military_status = 2 AND 
( military_home_state ≠ CA OR military_legal_residence ≠ CA )

Class B2

flag 62);

go to step 7

Go to step 7

7

Is the applicant under the care and control of a guardian, 
under 19 and unmarried?

‘over19OrMarried’ = 0 AND 
‘guardianOrParentRelation’ = G

Class B2

(flag 58);

go to step 8

Go to step 8

8

Is the applicant’s current address outside ofCalifornia?

‘Mailing address – state’ ≠ CA

Class B2

(flag 01);

go to step 9

Go to step 9

9

Is the applicant’s permanent address outside ofCalifornia?

‘Permanent address – state’ ≠ CA

Class B2

(flag 02);

go to step 10

Go to step 10

10

Is the applicant under 19 as of RDD with last high school out-of-state?

RDD minus 19 years > personal_info: birthdate 
AND education: hs_state ≠ CA

Class B2

(flag 03);

go to step 11

Go to step 11

11

Was the applicant enrolled in an out-of-state college 
with a ‘To Date’ within the year previous to the term start date.

In any row of colleges_attended table:  If state ≠ CA 
AND to_date is greater than the term start date minus 1 year.

Class B2

(flag 04);

go to step 12

Go to step 12

12

Has Class B2 been set?

Class B2

Class B1

Spec Changes Update Data Specs - Summary

Foster Youth Status 

California Foster Youth

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

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

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

Integrity Flags Table (Flag 70)

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

Integrity Flags Table (Flag 71 - NEW)

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. Update Step 4 of the Residency Table B (Area B Logic) and corresponding Flowchart (if necessary) 

Update Data Specs & Other Documentation - Details

(Most of this is duplicate of what's already specified above; however, per Amanda and Patty meeting 12/29/15, a summary and detailed data spec updates will be added to these Change Request Requirements confluence pages, such as this. A good reference is the Gender Change Requirement confluence spec for how we'll be doing this in the future.)

Foster Youth Status data field <foster_youth_status>

1. See detailed specifications in Requirement #1 above.  Each detail in the specification is itemized and changes are shown inRED.
2. The spec below was taken from the combined Data Dictionary spec that is being worked on and prepped for release with March 2016 Update.
   

   Table 145: Foster Youth Status
   Data Element: residency: foster_youth_status
   Description: Indicates the Foster Youth status of the applicant based on their screen input.
   Format, Length: char 1
   Values: (See details in Requirement #1 above).  The new values are as follows:

0 = No

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.

3 = No Longer appears onscreen - this field is now obsolete (but will remain in the spec for archival reference).

4 = No Longer appears onscreen - this field is now obsolete (but will remain in the spec for archival reference).

5 = I exited the foster care system before my 18th birthday.

6 = I am not sure at what age I exited foster care.

Allows Null: No
Default: None
Usage:
Xap Field: fosterYouthStatus
Revision Log: ~~
Question Text: Have you ever been in court ordered foster care? (See additional text below)
Conditions: Always
Additional Text: If the applicant selects Yes to "Have you ever been in court-ordered foster care?" the conditional additional text appears with the response options:

When did you exit foster care?

• 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.
• I exited the foster care system before my 18th birthday.
• I am not sure at what age I exited foster care.

Response Options: (See Requirement #1 above). 

• 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.
• I exited the foster care system before my 18th birthday.
• I am not sure at what age I exited foster care.

Required fields: For the Yes/No question, if not selected, error message is “Please indicate if you have ever been in foster care.” When the Yes/No question = Yes, one of the options must be selected. If no option is selected, error message is “Please select one of the foster care options.”
Hover Help: "Please indicate whether or not you have ever been placed in court- ordered Foster Care." [Spanish: "Por favor indique, si o no ha estado alguna vez colocado en Cuidado Adoptivo ordenado por el tribunal."]
Pop-Up Help:  
(NOTES:  See Requirement #2 above for the new Pop-Up Help text boxes. Each of the four new help boxes are individually hyperlinked and each has it's own Pop-Up Help box (they are no longer combined into one Help box).  Ensure that the hyperlinks (underlined terms) are underlined in the spec. Some of the hyperlinks appear in the Response Options to the Foster Youth Status conditional question. 

Court-ordered Foster Care: You have been in foster care if you were removed from your biological family through an order by a court, which can include placement with foster parents, in a group home, or with relatives/extended family members. If you were living with relatives you must have been placed through the foster care system by an order of the court. Foster Care includes, but is not limited to, placement in out-of-home care under the supervision of the Juvenile Probation Department. As long as you were placed within the foster care system by order of a court, you were in foster care. Having a legal guardian does not necessarily mean that you have been in foster care. If you need assistance with determining whether you were in foster care, you can contact the California Foster Care Ombudsman’s office at (877) 846-1602 or fosteryouthhelp@dss.ca.gov. 

Revise data spec heading to: Foster Youth in California  (Question ONLY is obsolete). Note: Remove "Data field is used in Residency Algorithm)

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

Revise Description TO: Whether applicant is a current or former Foster Youth in California and under 20 years of age at RDD.

Remove this description entirely:  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 20 or does not .

Update the field values as shown below: 

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

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

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

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

     5. Integrity Flags Table (Flag 70)

     6. Integrity Flags Table (Flag 71 - NEW)

Add new Integrity Flag 71 to Integrity Flags Table

Add new integrity flag 71 data field to the Download Client User Guide (it's a downloadable field and used in reporting)

     7. Area B Logic (Step 4)

Update Step 4 of the Residency Table B (Area B Logic) and corresponding Flowchart (if necessary) 

Top

Changes to Data Download File

Changes to Logic

3)  Add New Integrity Flag 71 as Downloadable Data Field and in the Field Logic for Foster Youth Priority Field <foster_youth_priority> 

a.  Add new Integrity Flag 71 <integrity_fg_71> as a downloadable data field to the Submitted Applications database table.

b.  Add row to the Integrity Flag Table for new Integrity Flag 71 and define using the language shown below. 

c.  Add new Integrity Flag 71 to the field logic in the Foster Youth Priority data field <foster_youth_priority> based on the applicant's response to the new Foster Youth Status additional text responses and the applicant's data of birth, as follows:

After the NEW Foster Youth Status field has been set, trigger Flag 71 if the applicant's foster_youth_status field is =1, OR =2, OR =3, OR =4, OR =6) AND the applicant is UNDER 25 years of age (RDD minus Birthdate < 25 years),  This logic will be added to the Foster Youth Priority data field specifications (shown in RED below):

Notes about Integrity Flag 71:

• The purpose of this new integrity flag is to alert the college Admissions Office staff that the applicant is possibly eligible for Priority Registration based on their Foster Youth Status and their Date of Birth.  

• The logic that determines this eligibility and triggers the flag 71 is contained within the Foster Youth Priority data field <foster_youth_priority> only.

• This flag does not affect the residency logic.

• This flag has a corresponding database field for downloads <integrity_fg_71>
• This flag field is added to the CCC Administrator Rules area so that colleges can create a rule based on whether this flag was triggered or not.
• This flag field is added to the CCC Report Center database for reporting Standard Application data;
• This flag field is added to the Full Application Report and all Application Look-Up Reports in the Report Center.

Top

4)  Update Foster Youth-related Data Fields Based on the New Foster Youth Status Changes

The foster youth data fields that determine foster youth priority registration, MIS requirement, and California residency are based on the new Foster Youth Status data field specifications <foster_youth_status> response options / values. Specifications for each data field is outlined below.

NOTE:  Examples of Use Cases for each revised data field are displayed near the bottom of this change request document.

Foster Youth in California

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)

Foster Youth Priority  

 (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 Flag 71

Foster Youth MIS  

(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

Top

Update Residency Area B Logic Based on New Foster Youth Status Data Specifications  

a)  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. 

Changes to Data Download File

Changes to Logic

Top

Summary of CCCApply Standard Application Data Dictionary Changes

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

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

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

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)

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 

Top

Use Cases & User Stories (For Reference & Testing)

The following use cases are displayed for Admissions and/or IT in order to confirm that the data field changes  made with the new Foster Youth Status response options/values are accurate. These are for testing and reference use only.

Foster Youth in California: Use Cases

(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 Priority: Use Cases  

(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 MIS: Use Cases

(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.

Supporting Documentation 

Below is additional documentation (i.e., CCCCO legal opinions, residency and/or education code citations, legislation citations, supplemental information, etc.) to be referenced in support of this change request.