Problem Statement
Petitioned by MIS administrators, 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.
Additonal Problem Statements
Note: These problems were submitted by Debbie Raucher of the John Burton Foundation. These problems were considered by the Steering Committee, though not all members agreed with all of them, citing anectdotal reasoning and lack of research data. However, below are contributing factors to the approved change specifications itemized herein.
Click to expand the Additional Problem Statements below:
Expand | ||
---|---|---|
| ||
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. |
Expand | ||
---|---|---|
|
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. |
Expand | ||
---|---|---|
| ||
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. |
Expand | ||
---|---|---|
|
|
| |
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. |
Proposed Solution
Requirements SummaryThe solution to the above issues requires several modifications, including
Modifyingmodifying the option
choiceschoices in the Foster Youth Status field <foster_youth_status>
Updating; updating the hyperlinked Help “pop-up” language
“Translating”; translating” the answer choices to match the current data field
logic Addinglogic; and adding one new additional integrity flag and data field <integrity_fg_71>
.to the application. The Area B residency logic is also modified to use the Foster Youth Status field <foster_youth_status> instead of the <ca_foster_youth> field.
Requirements Summary
# | Change Requirements SummaryDescription |
---|---|
1 | Revise the Foster Youth Status data field specifications < residency: foster_youth_status> with new conditional question and additional text, updated validation, and new Foster Youth Status response options / values to better align with AB12 and MIS reporting requirements. The current question prompt text "Have you ever been in court-ordered foster care?" does not change, but the Foster Youth Status response options/values DO CHANGE to align to the new conditional questioni/additional text responses that appear if the applicant answers "Yes" to the question. This change requirement requires colleges to update their download file to capture the new responses/values. See Changes to Download File section. |
2 | Revise Replace the existing Help pop-up Help box that appears is hyperlinked in the Foster Youth question and replace with two new Help pop-up Help terms which appear as hyperlinks in the Foster Youth question and conditional question response options. These will be boxes : 1) hyperlinked under "court-ordered foster care" in the onscreen question, with a definition for "court-ordered foster care"; and 2) a second box that contains three new definitions which are hyperlinked in the conditional question response options. The three definitions are for: "exit foster care", "exited the foster care system before my 18th birthday", and "not sure". These are documented in the CCCApply Data Dictionary v1v.0 (2016) .1 under Foster Youth Status field "additional text" responses. |
3 | Update the other foster youth data field specs as needed due to the new Foster Youth Status response options/values and other change specifications. These fields are: Foster Youth Priority <foster_youth_priority>, Foster Youth in California <ca_foster_youth>, and Foster Youth MIS <foster_youth_mis>. Each field has minor changes and have been documented inside and outside the application and Data Dictionary. |
4 | Add new Integrity Flag 71 and data field <integrity_fg_71> to the database and Standard Application download file, and add the flag to the Integrity Flags Table and data field logic. This new flag will identify users who may be eligibile for Priority Registration based on their foster youth status and their date of birth (AB194). If yes - the student is possibly eligible for AB194, theThe new flag data field is also added to the Rules database in the Administrator and the Report Center. |
5 | Revise Step 4 of Area B Residency logic to identify Foster Youth residency eligibility. |
Change Specifications
1)
UpdateUpdate the Foster Youth Status Question and Data Field Specifications
<residency:foster_youth_status>a)
UpdateUpdate the Foster Youth Status question
, condition,and add new conditional question and additional question text,
that appears if the
applicantsapplicant says, "Yes", to the Foster Youth Status question: "Have you ever been
inin court-ordered foster care?"
These. The changes are shown in red in the
tabletable below.
Foster Youth Status Question Changes
Element | Changes | Specification |
Question Text: |
| Change from: Have you ever been in court ordered Foster Care? Change to: "Have you ever been in court-ordered foster care?" |
Conditions: | No Change to conditions | This question will Always appear to applicants |
Additional Text: |
| Change the existing Foster Youth question "Additional Text" from the (see strike-through text below) to the new Additional Text in RED below.
New Conditional Question (Additional Text) When did you exit foster care?
Database Values
|
Requirement 1: Screenshot
1) New Foster Youth Status Additional Text - if the user selects "Yes" to the Foster Youth Status question, "Have you ever been in court-ordered foster care"?
Anchor | ||||
---|---|---|---|---|
|
a) Revise the former Foster Youth Status response options / data values to the new response options/data values as shown in Table A below. These new response values appear onscreen as corresponding RADIAL BUTTONS if the user selects YES to the question, "Have you ever been in court-ordered foster care?"
Former Foster Youth Status Field Responses/ Values
What changes
NEW Foster Youth Status Field Response Options / Values
If the response to the question,
“Have you ever been in
court-ordered foster care?” is NO
Nothing
NOTE: Former response options/data values #4 and #5 are no longer used in the Foster Youth Status field.
The new Foster Youth Status response options/data values are:
1 = I am currently in foster care (including extended foster care after age 18).
2 =
I was previously in foster care in California but aged-out or emancipated from the systemoption which appears onscreen.
New Onscreen Response Option / Value:
I aged out/emancipated from foster care or exited voluntarily on or after my 18th birthday.
5 = I exited the foster care system before my 18th birthday.
6 = I am not sure at what age I exited foster care.
Database Values
- Value 1 should be associated to this additional text - "I am currently in foster care (including extended foster care after age 18)."
- Value 2 should be associated to this additional text - "I aged out/emancipated from foster care or exited voluntarily on or after my 18th birthday.
responses; revise how these now defunct values
are used in the in existing field and residency algorithm logic. This response option will not be displayed; no longer used.
Value: 3 = I am currently in a foster care system outside of California.
Remove Response Option: No Longer displays onscreen as a Foster Youth Status response option.
NOTE: In the download file, it will display 3 = N/A.
and aged-out or emancipated from the system
responses;
- "
- Value 5 should be associated to this additional text - "I exited the foster care system before my 18th birthday."
- Value 6 should be associated to this additional text - "I am not sure at what age I exited foster care."
Table A: Changes to Foster Youth Status Responses / Values | |||||
Former Foster Youth Status Field Responses/ Values | What changes | NEW Foster Youth Status Field Response Options / Values | |||
0 = No If the response to the question, “Have you ever been in court-ordered foster care?” is NO | Nothing | 0 = No | |||
1 = I am currently in foster care in California | Revise the language of this response / value | New Onscreen Response Option / Value: 1 = I am currently in foster care (including extended foster care after age 18) | |||
2 = I was previously in foster care in California but aged-out or emancipated from the system | Revise the language of this value/response option which appears onscreen. | New Onscreen Response Option / Value: 2 = I aged out/emancipated from foster care or exited voluntarily on or after my 18th birthday. | |||
3 = I am currently in a foster care system outside of California | Remove this response / value from onscreen responses; revise how these now defunct values are used in the in existing field and residency algorithm logic. This response option will not be displayed; no longer used. |
Remove Response Option: No Longer displays onscreen as a Foster Youth Status response option. NOTE: In the download file, it will display 4 3 = N/A. | 5 |||
4 = I was previously in a foster care | but did NOT age out or emancipatesystem outside of California and aged-out or emancipated from the system | Revise the language of Remove this value/ | response option which appears onscreen.ADD NEW VALUE #6 and add | option from onscreen responses; revise how these now defunct values are used in the in existing field and residency algorithm logic. This response option will not be displayed; no longer used. |
Remove Response Option: No Longer displays onscreen as a Foster Youth Status response option. NOTE: In the download file, it will display 4 = N/A. |
5 = I was previously in foster care but did NOT age out or emancipate from the system | Revise the language of this value/response option which appears onscreen. | New Onscreen Response Option / Value: 5 = I exited the foster care system before my 18th birthday. | |||
ADD NEW VALUE #6 and add new onscreen response option as shown. | NEW Onscreen Response Option: 6 = I am not sure at what age I exited foster care. |
Anchor | ||||
---|---|---|---|---|
|
Replace existing Help pop-up box with two new Help pop-up boxes and four new definitions/hyperlinks
a) Replace the existing Help pop-up
Helpbox and foster youth terms/definitions with
fourtwo new Help pop-up
Helpboxes, based on the new terms being defined in the
newFoster Youth Status question, and the additional text response options, which appear if the student answers "yes" to the onscreen question.
The
fourtwo new
hyperlink Pop-UpHelp
text boxes as detailed below (i - iv). Ensure these new terms/sentences are underlined and hyperlinked (where indicated) to individualpop-up
Help boxes as defined below. (Note: Use Title case for these terms since they are titles in the pop-up Help box titles):i)
boxes and corresponding hyperlinks are:
1) 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.
ii) Aged Out/Emancipated:
. A single definition for "court-ordered foster care" appears when the hyperlink for "court-ordered foster care" is selected in the onscreen question; and 2) a second Help pop-up box, containing definitions for three new terms (see below) appear if the user clicks on any of the following hyperlinks that appear in the additional text conditional question response options: a) "When did you exit foster care?"; b) "Aged Out/Emancipated"; c) "Exited the foster care system before my 18th birthday"; and d) "Not sure".
Click to expand the definitions that appear in two new Help pop-up boxes, below:
Expand | ||
---|---|---|
| ||
(This link appears in the foster youth question "Have you ever been in court-ordered foster care?" ) |
Expand | ||
---|---|---|
| ||
(This link contains three definitions, shown below:) Aged Out/Emancipated: (This link appears in foster youth status response value = 2) |
or fosteryouthhelp@dss.ca.gov. |
|
Anchor | ||||
---|---|---|---|---|
|
Add new downloadable data field for Integrity Flag 71
as a NEW Downloadable Data Field & Use in the Field Logic& use in the field logic for Foster Youth Priority
a. Add new Integrity Flag 71 <integrity_fg_71> as a new downloadable data field to the Submitted Applications database table.
b. Add row to the Integrity Flag Table for new Integrity Flag 71 and define the description using the language shown below.
71 | Applicant is a current or former foster youth and is under the age of 25. Applicant is possibly eligible for Priority Registration per AB12. | (foster_youth_status=1 OR =2 OR =3 OR =4 OR =6 ) AND (RDD* minus Birthdate < 25 years) |
c. Add new Integrity Flag 71 to the field logic in the the Foster Youth Priority data data field <foster_youth_priority> based on the applicant's response to the new Foster Youth Status additional text responses and the applicant's date 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):
Foster Youth Priority
|
Notes about Integrity Flag 71: Anchor Flag-71 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
Anchor | ||||
---|---|---|---|---|
|
data fields based on the
Newnew Foster Youth Status
Changeschanges
The foster youth data fields that determine foster youth priority registration, MIS requirement, and California residency are based on the 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.
Anchor foster_youth_priority foster_youth_priority
Updates to: Foster Youth in California
foster_youth_priority | |
foster_youth_priority |
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)
Anchor foster_youth_priority foster_youth_priority
Updates to: Foster Youth Priority
foster_youth_priority | |
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
Updates to: 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
Anchor | ||||
---|---|---|---|---|
|
based on
Newnew Foster Youth Status
Data Specificationsdata specifications
a) Revise 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.
Anchor Table-B Table-B
Table B. Outline of Area B (Stay and Intent) Criteria in Residency Algorithm
Table-B | |
Table-B |
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 | 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, | NEW LOGIC: foster_youth_status is NOT = 0 AND RDD* minus Birthdate < 20 years | Use Case Examples:Class B2; go to step 5 (flag 70) | Class B0; end |
NOTE: Steps 5 through 11 are not dsplayed. | ||||
Class B2; go to step 5 (flag 70) | Class B0; end | |||
NOTE: Steps 5 through 11 are not dsplayed. | ||||
12 | Has Class B2 been set? |
| Class B2 | Class B1 |
cb) 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. Replace flag logic notation from "ca_foster_youth = 1" TO "See Residency Area B Logic"
Revise Integrity Flag 70 as follows:
70 | Applicant is a current or former Foster Youth in California and under 20 years of age | See Residency Area B Logic |
Anchor | ||||
---|---|---|---|---|
|
Top This approved change request resulted in one new data field, which happens to be an Integrity Flag (71).
New Downloadable Data Field: Integrity Flag 71 <integrity_fg_71>
Actions Required by College:
- See below for information on updating to the latest Download Client Jar File.
- Modify your existing Standard Application Download Format XML file to include the new Integrity Flag 71.
Note |
---|
Update Your Download Client Jar File Step 1: To implement the 2016 Annual Update changes in your downloads, you must first update to the latest version of the Download Client jar file. Information and instructions can be found in the CCCApply Download Client User Guide v.2016.1. Step 2: Modify your existing Download Format XML file to include new data fields being released in the 2016 Annual Update. NOTE: We recommend you test these changes in the PILOT environment before the Production release. Reference the CCCApply Download Client User Guide v.2016.1 for details. **If you have been experiencing any issues with your downloads since the March 31 release, please see Download Client Solutions for March 2016 for troubleshooting information. |
Anchor | ||||
---|---|---|---|---|
|
This approved change request resulted in some changes to the Foster Youth Status data field response options/data values.
- Foster Youth Status field <fy_status> has NEW RESPONSE VALUES .
- The data field name <fy_status> DID NOT CHANGE. It still appears in your download file, exactly as it has been.
- The existing Integrity Flag 70 is still a field in your download file. The language for that flag has not changed.
- A new Integrity Flag 71 has been added to the download file and triggers in the Foster Youth Priority field (see above).
What does your college need to do due to this change?
- Review your business processes, procedures, and forms to identify if any changes need to be made due to the new Foster Youth Status field responses / values.
- Review your Student Information System (SIS) fields and reports to identify if any changes need to be made due to these new Foster Youth Status field responses / values.
PLEASE UPDATE YOUR REPORTS AND MAPPED VALUES in your Student Information System. - Review the new CCCApply Data Dictionary v.2016.1 for any other details relative to these Foster Youth field, flag, and logic changes as needed.
- Inform your college Admissions & Records staff about the new and revised Foster Youth Status responses / values.
Anchor | ||||
---|---|---|---|---|
|
Due to the changes made to the Foster Youth Status field response options/data values <foster_youth_status>, changes had to be made to the Area B Residency Logic. The logic in Area B still leads to the same result, however now the logic is based on the "foster_youth_status" AND the applicant's age based on the RDD, not the "ca_foster_youth" field. The reason for this is because the "ca_foster_youth" field had built-in age calculation, where as "foster_youth_status" field does not. So, the only change made to the Area B logic is the field used and a concise age calculation based on the user's age against the RDD ("RDD minus Birthdate < 20 years").
There is no action required by the college relative to this residency change
- Step 4 of Area B residency logic has been revised with new data field and an age calculation
- The outcome of Step 4 of Area B residency logic is the same and the same Flag 70 is triggered when applicable
- There are no other changes to Area B residency logic: Steps 1 - 3 and Steps 5 - 10 did not change
Expand | ||
---|---|---|
| ||
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".
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. |
Anchor | ||||
---|---|---|---|---|
|
Due to the changes made to the Foster Youth Status field response options/data values <foster_youth_status>, corresponding changes had to be made to the field logic within the Foster Youth Priority, Foster Youth MIS, and California Foster Youth data fields. The logic within these fields lead to the same results, however the foster youth status data values used to reach these results have changed.
There is no action required by the college relative to these changes.
Expand | ||
---|---|---|
| ||
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) |
Expand | ||
---|---|---|
| ||
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 |
Expand | ||
---|---|---|
| ||
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 |
Anchor | ||||
---|---|---|---|---|
|
Expand | ||
---|---|---|
|
| |
Foster Youth Status Data Field <foster_youth_status>
California Foster Youth Data Field <ca_foster_youth>
Foster Youth Priority Data Field <fy_priority>
Foster Youth MIS Data Field <fy_MIS>
Integrity Flags Table (Flag 70)
Integrity Flags Table (Flag 71 - NEW Download Data Field)
|
Area B Logic (Step 4)
|
Top
Expand | ||
---|---|---|
| ||
New Download Data Field: Integrity Flag 71
|
Anchor | ||||
---|---|---|---|---|
|
The following use cases are displayed for Admissions and/or IT in order to confirm that the data field changes made made with the new Foster Youth Status response options/values are accurate. These are for testing and reference use only.
Expand | ||
---|---|---|
|
| |
(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
|
|
Example 2: Birthdate before RDD minus 20 yrs RDD = 2015-01-04
Example 3: Birthdate after RDD minus 20 yrs RDD = 2015-01-04
|
|
Example 4: User Chose No Radio Button RDD = 2015-01-04
Example 5: User chose value 5 "I exited the foster care system before my 18th birthday." RDD = 2015-01-04 |
04
|
|
|
Example 6: User chose value 6 I am not sure at what age I exited foster care. RDD = 2015-01-04
|
|
|
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.
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.
|
Expand | ||
---|---|---|
|
(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
Example 2: Birthdate before RDD minus 25 yrs
Example 3: Birthdate after RDD minus 25 yrs
Example 4: User Chose No Radio Button RDD = 2015-01-04
|
|
Example 5: User chose value 5 "I exited the foster care system before my 18th birthday."
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.
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.
|
Expand | ||
---|---|---|
| ||
(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,
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.
|
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.
Description | File or Link |
---|---|
AB12 Fact Sheet | AB12FactSheet.pdf |
Download Client User Guide | CCCApply Download Client User Guide v.2016.1 |