On this page
|
Legacy SHINES reference document. This page captures a Georgia DHS SHINES interface design as written (vendor spec, typically 2007–2025). It documents the system being replaced, not CRAIG behavior. CRAIG’s current implementation of the same data exchange lives under the craig-exchange API reference and in the design documents. Use this page only when mapping legacy integrations during CRAIG rollout. |
Interface* Detailed Design Document*
CAPS Referral - IES
Georgia Department of Human Services
Statewide Automated Child Welfare Information System
(SACWIS)
TBD
Version 1.[.line-through]0[.line-through]1
2/22/2023
[.line-through]# [.line-through] [.line-through] [.line-through]#Version 2.0
02/17/2024
Version 2.1
Table of Contents
General Design (Functional)
| Req. # | Validated Requirement |
|---|---|
CAPS - 1.1 |
The system shall allow the worker to send the following data fields to IES for a CAPS referral for children in Foster Care and CPS: o Referral Submitted Date o Source (SHIN) o Program (CC) o Type of Action o EMPI ID of child o Type of Service Requested o Special Needs (Y/N) o Reason Care Needed o Case Stage (Foster Care or CPS Custody) o Child’s Name - First Name - Middle Name - Last Name o Child Suffix o Gender o Race o Ethnicity o Date of Birth o Social Security Number (SSN) o Citizenship/Alien Status o Current Educational Status o CM Name o CM Suffix o CM Address o CM Telephone o CM Email o Supervisor Name o Supervisor Telephone o Supervisor Email o County Director Name o County Director Telephone o County Director Email o Caregiver Name o Caregiver Address o Caregiver Telephone o Pregnancy (Y or N) o Transaction ID |
CAPS - 1.2 |
The system shall send the provider rate sheet to IES |
CAPS - 1.3 |
The system shall send the birth certificate of the child to IES |
CAPS - 2.1 |
The system shall send the updated legal status of a child to IES |
CAPS - 3.1 |
The system shall send the updated placement address of a child in Foster Care to IES |
CAPS - 4.2 |
The system shall receive the CAPS eligibility type of a child from IES |
CR379-1.1 |
The system shall complete the required Reason Care Needed field for a CAPS Referral in the INV stage per the following logic: - Indicate 'Safety Resource' when there is an APRV Safety Resource - Indicate 'Case Plan/Safety Plan' when there is an APRV Safety Plan and no APRV Safety Resource - Otherwise, the field cannot be completed |
CR379-1.2 |
The system shall complete the required Reason Care Needed field for a CAPS Referral in the ONG stage per the following logic: - Indicate value 'Safety Resource' when there is an APRV Safety Resource - Indicate value 'Court Order' when there is an APRV Family Preservation Family Plan with Court Order indicated and there is no APRV Safety Resource - Indicate value 'Case Plan/Safety Plan' when there is an APRV Family Plan and no APRV Safety Resource - Indicate value 'Case Plan/Safety Plan' when there is no APRV Safety Resource or Family Plan - Otherwise, the field cannot be completed |
CR776365 CR CC CAPS |
The system shall be modified to display the Terminated or Denial Reason on the CAPS Update submodule. The statuses will be displayed under the Eligibility Status heading (we will not be adding an additional field) The date last updated (Dt_Last_Update) will be displayed as the date the termination or denial was received. These dates will be displayed under the Begin Date column (we will not be adding an additional field).. |
CR771654 - |
The backend system will be modified to accommodate new field coming from Gateway i.e Document Name for CAPS Certificate ,That will help to view the Cap certificates on front end |
Document Purpose
This document provides a detailed description of a Georgia SHINES outbound interface that sends case data to the Integrated Eligibility System to satisfy a CAPS (Childcare and Parent Services) Referral for a child.
Functional Description
The CAPS Referral Outbound Interface is used to provide information needed to complete a CAPS referral for children who are in Foster Care or Child Protective Services. The referrals for children in Foster Care will be an automated process generated by the system and referrals for children in CPS will be a manual process through a button located on Education Detail. This functionality will effect cases beginning on the date of release.
The following items must be met for a CAPS referral to be sent to IES for a child in foster care:
Child care setting of Head Start, Child Care, Informal Child Care, or Early Head Start (Education Type on Education Detail)
Child in DFCS Custody
Active Placement that is in COMP or APRV status
An uploaded Provider Rate Sheet to External Documentation
Lastly, the required information needed for the referral is captured in SHINES
The following items must be met for a CAPS referral to be manually sent to IES for a child in CPS:
Child NOT in DFCS Custody
Child care setting of Head Start, Child Care, Informal Child Care, or Early Head Start (Education Type on Education Detail)
An uploaded Provider Rate Sheet to External Documentation
Lastly, required information needed for the referral is captured in SHINES
Figure 1) SHINES à IES and IES à SHINES for CAPS Referral [Foster Care]
This flow chart depicts the outbound interface process from the Georgia SHINES system to the IES system as well as the inbound process from IES to SHINES for children in Foster Care:
Figure 2) SHINES à IES and IES à SHINES for CAPS Referral [CPS]
This flow chart depicts the outbound interface process from the Georgia SHINES system to the IES system as well as the inbound process from IES to SHINES for children in CPS:
Once an initial referral has been successfully sent from SHINES, an event will display on the Event List page indicating that a CAPS referral was sent. A CAPS Update submodule will also display under the child’s Person Detail page. When a CAPS Certificate of Eligibility is received from IES after the referral has been approved, information regarding eligibility will be displayed here. Please refer to the Person Detail Detailed Design for more information regarding this module. The terminated or denial Reason will be displayed when “DN” code is received and the status under the eligibility status will read “Denied” – with the termination or denial message following”. The date last updated (Dt_Last_Update) will be displayed as the date the termination or denial was received in the Begin date column.
After initial referrals, should the resource of the placement for the child change and the placement is in COMP or APRV status, an update with the new placement is sent to IES. Similarly, if the legal status of the child changes from in-DFCS Custody to Not in DFCS custody, an update with the new legal status is sent to IES.
Good cause referrals will not be handled any differently in SHINES. Any immediate responses from IES upon referral submission will not be tracked by SHINES.
Security Rules hold on how old is dictate how wanna dictate I want it to
| User Type | View | Add | Update | Delete | No Access |
|---|---|---|---|---|---|
Case Manager (Assigned) |
X |
X |
X |
||
Supervisor (Assigned) |
X |
X |
X |
Request/Response Elements
Below is a list of the CAPS data elements from SHINES that will be sent to IES.
| Data Element | SHINES Origin | Required for Initial Referral |
|---|---|---|
Application Received Date |
N/A |
Y |
Source |
N/A (Send value ‘SHIN’ to IES) |
Y |
Type of Action |
N/A (System generated) |
Y |
EMPI ID |
Person Identifiers on Person Detail |
Y |
Type of Service Request |
N/A (System generated) |
Y |
Case Stage |
Stage |
Y |
Program |
N/A (Send value ‘CC’ to IES) |
Y |
Child’s Name (First, Middle, Last) |
Person Detail |
Y (First and Last) |
Child Suffix |
Person Detail |
N |
Gender |
Person Detail |
Y YY |
Race |
Race/Ethnicity on Person Detail |
Y |
Ethnicity |
Race/Ethnicity on Person Detail |
Y |
Date of Birth |
Person Detail |
Y |
Social Security Number |
Person Identifiers on Person Detail |
N |
Citizenship/Alienage Status |
Citizenship and Identity of Person Detail |
Y |
Pregnancy Indicator |
Person Characteristics on Person Detail |
N |
Reason Care Needed |
N/A (System generated per the following logic): Child in DFCS Custody = ‘Child in DFCS Custody’ Child in CPS (INV or ONG) = INV with APRV Safety Resource = ‘Safety Resource’ INV with APRV Safety Plan with no APRV Safety Resource = ‘Case Plan/Safety Plan’ ONG with APRV Safety Resource = ‘Safety Resource’ ONG with APRV Family Preservation Family Plan with Court Order marked = ‘Court Order (CO)’ ONG with APRV Safety Plan and no APRV Safety Resource or Family Preservation Family Plan = ‘Case Plan/Safety Plan’ ONG with APRV Family Preservation Family Plan with no APRV Safety Resource or Safety Plan = ‘Case Plan/Safety Plan’ |
Y |
Special Needs (Y/N) |
Health Detail/Person Characteristics |
Y |
Caregiver Name |
Placement Information (FC) or Person Detail for (CPS) |
Y |
Caregiver Address |
Placement Information (FC) or Person Detail for (CPS) |
Y |
Caregiver Phone |
Placement Information (FC) or Person Detail for (CPS) |
Y |
Current Educational Setting |
Education Type – Ed Detail |
Y |
Name of Case Manager |
Staff Detail |
Y |
Office Location of Case Manager |
Staff Detail |
Y |
Email Address of Case Manager |
Staff Detail |
Y |
Telephone of Case Manager |
Staff Detail |
Y |
Supervisor Name |
Staff Detail |
Y Y Y |
Supervisor Phone S |
Staff Detail |
Y |
Supervisor Email |
Staff Detail |
Y |
County Director Name |
Staff Detail |
Y |
County Director Phone |
Staff Detail |
Y |
County Director Email |
Staff Detail |
Y |
Transaction ID |
N/A (Unique ID created by SHINES for transaction to IES) |
Y |
Legal Status |
Legal Status (sent on initial referral (Y/N) and when the status changes from in-DFCS custody to not in DFCS custody for Foster Care cases and from not in DFCS custody to in-DFCS custody for CPS cases after the initial referral) |
N/A |
Legal Status Date |
Not in DFCS Custody - Parental Custody Date from SHINES if Legal Status is N |
N/A |
Provider Address Line_1 |
Education Detail |
Y |
Provider Address Line_2 |
Education Detail |
Y |
Provider City |
Education Detail |
Y |
Provider State |
Education Detail |
Y |
Provider Zip |
Education Detail |
Y |
Provider County |
Education Detail |
Y |
Provider Primary Phone |
Education Detail |
Y |
A response will be received from GA Gateway through a batch that will provide the CAPS Certificate of Eligibility and the following data elements: Begin and end date of certificate, eligibility status and type. These data elements will display in the CAPS Update submodule on the Person Detail page The terminated or denial reason will be displayed when “DN” code is received and the status under the eligibility status will read Denied – with the termination or denial message following”. The date last updated (Dt_Last_Update) will be displayed as the date the termination or denial was received in the Begin date column.
CAPS Referral data will not be shared with any other downstream system except GA Gateway.
Codes Tables
| Field Label | Legal Status |
|---|---|
Codes Table Name (If applicable) |
CLEGSTAT |
Code |
Decode |
AFS |
Aftercare/Supervision |
CTD |
Committed To DJJ |
ILP |
ILP Aftercare |
NAF |
Not In DFCS Custody – Adoption Finalized |
NCT |
Not In DFCS Custody – Child Turned 18 (No ILP) |
NCD |
Not In DFCS Custody – Child Death |
NCO |
Not In DFCS Custody – Custody To Other |
NTT |
Not In DFCS Custody – Custody Transferred To Tribe |
NCE |
Not In DFCS Custody – Emancipated |
NGP |
Not In DFCS Custody – Guardianship |
NPC |
Not In DFCS Custody – Parental Custody |
NPR |
Not In DFCS Custody - Custody To Relative |
NOT |
Not In DFCS Custody – Out of State Child Adopted by Georgia Family |
PCT |
Permanent Court |
PVL |
Permanent Voluntary |
STE |
Short Term Emergency Care |
TCT |
Temporary Court |
TVL |
Temporary Voluntary |
NCS |
Not In DFCS Custody - Custody With Other State |
NDJ |
No Longer Committed to DJJ |
DJA |
DJJ Aftercare |
JCP |
Joint Commitment With DJJ - Permanent Court |
JCT |
Joint Commitment With DJJ - Temporary Court |
NCR |
Not In DFCS Custody - Runaway |
| Field Label | County |
|---|---|
Codes Table Name (If applicable) |
CCOUNT |
Code |
Decode |
001 |
Appling |
003 |
Atkinson |
005 |
Bacon |
007 |
Baker |
009 |
Baldwin |
011 |
Banks |
013 |
Barrow |
015 |
Bartow |
017 |
Ben Hill |
019 |
Berrien |
021 |
Bibb |
023 |
Bleckley |
025 |
Brantley |
027 |
Brooks |
029 |
Bryan |
031 |
Bulloch |
033 |
Burke |
035 |
Butts |
037 |
Calhoun |
039 |
Camden |
043 |
Candler |
045 |
Carroll |
047 |
Catoosa |
049 |
Charlton |
051 |
Chatham |
053 |
Chattahoochee |
055 |
Chattooga |
057 |
Cherokee |
059 |
Clarke |
061 |
Clay |
063 |
Clayton |
065 |
Clinch |
067 |
Cobb |
069 |
Coffee |
071 |
Colquitt |
073 |
Columbia |
075 |
Cook |
077 |
Coweta |
079 |
Crawford |
081 |
Crisp |
083 |
Dade |
085 |
Dawson |
087 |
Decatur |
089 |
Dekalb |
091 |
Dodge |
093 |
Dooly |
095 |
Dougherty |
097 |
Douglas |
099 |
Early |
101 |
Echols |
103 |
Effingham |
105 |
Elbert |
107 |
Emanuel |
109 |
Evans |
111 |
Fannin |
113 |
Fayette |
115 |
Floyd |
117 |
Forsyth |
119 |
Franklin |
121 |
Fulton |
123 |
Gilmer |
125 |
Glascock |
127 |
Glynn |
129 |
Gordon |
131 |
Grady |
133 |
Greene |
135 |
Gwinnett |
137 |
Habersham |
139 |
Hall |
141 |
Hancock |
143 |
Haralson |
145 |
Harris |
147 |
Hart |
149 |
Heard |
151 |
Henry |
153 |
Houston |
155 |
Irwin |
157 |
Jackson |
159 |
Jasper |
161 |
Jeff Davis |
163 |
Jefferson |
165 |
Jenkins |
167 |
Johnson |
169 |
Jones |
171 |
Lamar |
173 |
Lanier |
175 |
Laurens |
177 |
Lee |
179 |
Liberty |
181 |
Lincoln |
183 |
Long |
185 |
Lowndes |
187 |
Lumpkin |
189 |
McDuffie |
191 |
McIntosh |
193 |
Macon |
195 |
Madison |
197 |
Marion |
199 |
Meriwether |
201 |
Miller |
205 |
Mitchell |
207 |
Monroe |
209 |
Montgomery |
211 |
Morgan |
213 |
Murray |
215 |
Muscogee |
217 |
Newton |
219 |
Oconee |
221 |
Oglethorpe |
223 |
Paulding |
225 |
Peach |
227 |
Pickens |
229 |
Pierce |
231 |
Pike |
233 |
Polk |
235 |
Pulaski |
237 |
Putnam |
239 |
Quitman |
241 |
Rabun |
243 |
Randolph |
245 |
Richmond |
247 |
Rockdale |
249 |
Schley |
251 |
Screven |
253 |
Seminole |
255 |
Spalding |
257 |
Stephens |
259 |
Stewart |
261 |
Sumter |
263 |
Talbot |
265 |
Taliaferro |
267 |
Tattnall |
269 |
Taylor |
271 |
Telfair |
273 |
Terrell |
275 |
Thomas |
277 |
Tift |
279 |
Toombs |
281 |
Towns |
283 |
Treutlen |
285 |
Troup |
287 |
Turner |
289 |
Twiggs |
291 |
Union |
293 |
Upson |
295 |
Walker |
297 |
Walton |
299 |
Ware |
301 |
Warren |
303 |
Washington |
305 |
Wayne |
307 |
Webster |
309 |
Wheeler |
311 |
White |
313 |
Whitfield |
315 |
Wilcox |
317 |
Wilkes |
319 |
Wilkinson |
321 |
Worth |
999 |
Out of State |
XXX |
-None- |
| Field Label | Gender |
|---|---|
Codes Table Name (If applicable) |
CSEX |
Code |
Decode |
F |
Female |
M |
Male |
U |
Unknown |
| Field Label | Ethnicity |
|---|---|
Codes Table Name (If applicable) |
CINDETHN |
Code |
Decode |
HS |
Hispanic/Latino |
NH |
Not Hispanic/Latino |
UT |
Unable to Determine |
| Field Label | Race |
|---|---|
Codes Table Name (If applicable) |
CRACE |
Code |
Decode |
AA |
American Indian/Alaskan Native |
AN |
Asian |
BK |
Black/African American |
HP |
Native Hawaiian/Other Pacific Islander |
UD |
Unable to Determine |
WT |
White |
| Field Label | Suffix |
|---|---|
Codes Table Name (If applicable) |
CSUFFIX |
Code |
Decode |
2N |
Second |
3R |
Third |
4T |
Fourth |
5T |
Fifth |
JR |
Jr. |
SR |
Sr. |
MD |
M.D. |
PD |
PhD |
Design Requirements
| Validated Functional Requirement Number | Conceptual Design Requirement Number | Conceptual Design Requirement |
|---|---|---|
CAPS - 1.1 |
CAPS - 1.1.1 |
The system shall only send a CAPS referral to GA Gateway when the required data elements have been captured in SHINES |
CAPS - 1.1 |
CAPS - 1.1.2 |
The system shall automatically send the required data elements for a CAPS referral for children in Foster Care when the following items have been met: Uploaded Provider Rate Sheet Active Placement in COMP or APRV status Child care setting of Head Start, Child Care, Informal Child Care, Early Head Start |
CAPS - 1.1 |
CAPS - 1.1.3 |
The system shall send CAPS requested data fields to GA Gateway for all children ages 0-12 |
CAPS - 1.1 |
CAPS - 1.1.4 |
The system shall send CAPS requested data fields to GA Gateway for all children ages 13-18 with the following active diagnoses captured on Health Detail or Person Characteristics pages (Note: Look at an active diagnosis (Health Detail) first and then look at Person Characteristics): - Autism - Visually Impaired - Hearing Impaired - Any diagnosis or characteristic in the Child - Mental / Emotional / Behavioral section - Intellectual disability - Orthopedic impairment - Learning Disability - Speech Disability - Traumatic Brain Injury - Mobility Impaired |
CAPS - 1.1 |
CAPS - 1.1.5 |
The system shall require the value 'Y' to be sent to GA Gateway for Special Needs when a CAPS-eligible individual has any one of the following active diagnoses indicated on their Health Detail: - Autism - Visually Impaired - Hearing Impaired - Any diagnosis or characteristic in the Child - Mental / Emotional / Behavioral section - Intellectual disability - Orthopedic impairment - Learning Disability - Speech Disability - Traumatic Brain Injury - Mobility Impaired |
CAPS - 1.1 |
CAPS - 1.1.6 |
The system shall require the value 'N' to be sent to GA Gateway for Special Needs when a CAPS-eligible individual does not have any of the following active diagnoses indicated on their Health Detail: - Autism - Visually Impaired - Hearing Impaired - Any diagnosis or characteristic in the Child - Mental / Emotional / Behavioral section - Intellectual disability - Orthopedic impairment - Learning Disability - Speech Disability - Traumatic Brain Injury - Mobility Impaired |
CAPS - 1.1 |
CAPS - 1.1.7 |
The system shall always send the date the referral was submitted from SHINES to GA Gateway (format: MM-DD-YYYY) |
CAPS - 1.1 |
CAPS - 1.1.8 |
The system shall always send the value 'SHIN' as the Source for a CAPS referral from SHINES to GA Gateway |
CAPS - 1.1 |
CAPS - 1.1.9 |
The system shall always send the value 'CC' as the Program for a CAPS referral from SHINES to GA Gateway |
CAPS - 1.1 |
CAPS - 1.1.10 |
The system shall always send the value 'Child in DFCS Custody' to satisfy the Reason Care Needed field for an initial CAPS Referral for a child in Foster Care |
CAPS - 1.1 |
CAPS - 1.1.11 |
The system shall send the value 'Court Order' to satisfy the Reason Care Needed field for an initial CAPS Referral for a child in CPS if the Family Preservation Family Plan displays a Court Order |
CAPS - 1.1 |
CAPS - 1.1.12 |
The system shall send the value 'Safety Resource' to satisfy the Reason Care Needed field for an initial CAPS Referral for a child in CPS if the Family Preservation Family Plan displays a blank Court Order and an open, active safety resource is captured for the child |
CAPS - 1.1 |
CAPS - 1.1.13 |
The system shall send the value 'Case Plan/Safety Plan' to satisfy the Reason Care Needed field for an initial CAPS Referral for a child in CPS if the Family Preservation Family Plan displays a blank Court Order and a safety resource is not captured for the child |
CAPS - 1.1 |
CAPS - 1.1.14 |
The system shall require the Type of Action of 'New Application' for a CAPS-eligible individual to be sent from SHINES to GA Gateway when sending the initial CAPS referral |
CAPS - 1.1 |
CAPS - 1.1.15 |
The system shall require the Type of Action of 'Placement Change' for a CAPS-eligible individual to be sent from SHINES to GA Gateway when the resource of the placement has changed for the child (after initial referral) |
CAPS - 1.1 |
CAPS - 1.1.16 |
The system shall require the Type of Action of 'Provider Change' for a CAPS-eligible individual to be sent from SHINES to GA Gateway when a new Provider Rate Sheet is uploaded for the child and a provider has changed (after initial referral) |
CAPS - 1.1 |
CAPS - 1.1.17 |
The system shall require the Type of Action of 'Document Upload' for a CAPS-eligible individual to be sent from SHINES to GA Gateway when a new Provider Rate Sheet is uploaded for the child (after initial referral) |
CAPS - 1.1 |
CAPS - 1.1.18 |
The system shall require the Type of Action of 'Document Upload' for a CAPS-eligible individual to be sent from SHINES to GA Gateway when a Birth Certificate is uploaded for the child (after initial referral) |
CAPS - 1.1 |
CAPS - 1.1.19 |
The system shall require the Case Stage of 'Foster Care' for CAPS-eligible individuals in foster care to be sent from SHINES to GA Gateway |
CAPS - 1.1 |
CAPS - 1.1.20 |
The system shall require the Case Stage of 'CPS' for CAPS-eligible individuals in CPS to be sent from SHINES to GA Gateway |
CAPS - 1.1 |
CAPS - 1.1.21 |
The system shall send the type of service requested as 'CAPS' for children ages 0-12 or children ages 13-18 with special needs as detailed above for an initial CAPS referral to GA Gateway |
CAPS - 1.1 |
CAPS - 1.1.22 |
The system shall send the type of service requested as 'Early Head Start' for children under the age of 3 to GA Gateway, if available for an initial CAPS referral to GA Gateway |
CAPS - 1.1 |
CAPS - 1.1.23 |
The system shall send the type of service requested as 'Head Start' for children ages 3 - 4, if available for an initial CAPS referral to GA Gateway |
CAPS - 1.1 |
CAPS - 1.1.24 |
The system shall send the type of service requested as 'Pre-K' for all children age 4, if available for an initial CAPS referral to GA Gateway |
CAPS - 1.1 |
CAPS - 1.1.25 |
The system shall require the first name of a CAPS-eligible individual from the 'First:' field on SHINES Person Detail to be sent to GA Gateway for an initial CAPS referral |
CAPS - 1.1 |
CAPS - 1.1.26 |
The system shall send the middle name of a CAPS-eligible individual from the 'Middle:' field on SHINES Person Detail to GA Gateway, if available for an initial CAPS referral |
CAPS - 1.1 |
CAPS - 1.1.27 |
The system shall require the last name of a CAPS-eligible individual from the 'Last:' field on SHINES Person Detail to be sent to GA Gateway for an initial CAPS referral |
CAPS - 1.1 |
CAPS - 1.1.28 |
The system shall send the suffix of a CAPS-eligible individual from the 'Suffix:' field on SHINES Person Detail to GA Gateway, if available for an initial CAPS referral |
CAPS - 1.1 |
CAPS - 1.1.29 |
The system shall require the gender of a CAPS-eligible individual from the 'Gender:' field on SHINES Person Detail to be sent to GA Gateway for an initial CAPS referral |
CAPS - 1.1 |
CAPS - 1.1.30 |
The system shall require the race of a CAPS-eligible individual from value(s) indicated on the Race - Race/Ethnicity subsection on SHINES of Person Detail to be sent to GA Gateway for an initial CAPS referral |
CAPS - 1.1 |
CAPS - 1.1.31 |
The system shall require the ethnicity of a CAPS-eligible individual from value(s) indicated on the Ethnicity - Race/Ethnicity subsection on SHINES of Person Detail to be sent to GA Gateway for an initial CAPS referral |
CAPS - 1.1 |
CAPS - 1.1.32 |
The system shall require the date of birth of a CAPS-eligible individual from the 'DOB:' field on SHINES Person Detail to be sent to GA Gateway for an initial CAPS referral |
CAPS - 1.1 |
CAPS - 1.1.33 |
The system shall send the social security number of a CAPS-eligible individual from the Person Identifiers subsection on SHINES Person Detail to GA Gateway, if available for an initial CAPS referral |
CAPS - 1.1 |
CAPS - 1.1.34 |
The system shall require the citizenship/alienage status of a CAPS-eligible individual from the 'Citizenship/Alien Status:' field on SHINES Citizenship and Identity tab of Person Detail to be sent to GA Gateway for an initial CAPS referral |
CAPS - 1.1 |
CAPS - 1.1.35 |
The system shall always send the EMPI ID of a CAPS-eligible individual from the Person Identifiers subsection on SHINES Person Detail to be sent to GA Gateway for any type of CAPS action (initial, placement change, provider change, document upload) |
CAPS - 1.1 |
CAPS - 1.1.36 |
The system shall send the legal county of the CAPS-eligible individual from the 'Legal County' field on SHINES Legal Status to GA Gateway, if available for an initial CAPS referral for FCC cases (otherwise, the Case County will be sent for CPS cases) |
CAPS - 1.1 |
CAPS - 1.1.37 |
The system shall send the pregnancy indicator (Y or N) of a CAPS-eligible individual from the SHINES Child - Physical/Medical/Developmental section of Person Characteristics to GA Gateway, if available for an initial CAPS referral |
CAPS - 1.1 |
CAPS - 1.1.39 |
The system shall require the caregiver name of the current placement of the CAPS-eligible individual from facility field of SHINES Placement Information to be sent to GA Gateway for Foster Care Cases for an initial CAPS referral |
CAPS - 1.1 |
CAPS - 1.1.40 |
The system shall require the address (Street, City, State, Zip) of the caregiver/resource of the current placement of the CAPS-eligible individual from the Address/Phone Detail module of SHINES Placement Information to be sent to GA Gateway for Foster Care Cases for an initial CAPS referral |
CAPS - 1.1 |
CAPS - 1.1.41 |
The system shall require the telephone number of the current placement of the CAPS-eligible individual from the Address/Phone Detail module of SHINES Placement Information to be sent to GA Gateway for Foster Care Cases for an initial CAPS referral |
CAPS - 1.1 |
CAPS - 1.1.42 |
The system shall require send the primary caretaker name of the current placement of the CAPS-eligible individual from SHINES Person Detail of the Primary Caretaker to be sent to GA Gateway for CPS Cases for an initial CAPS referral |
CAPS - 1.1 |
CAPS - 1.1.43 |
The system shall require the address (Street, City, State, Zip) of the primary caretaker of the CAPS-eligible individual from the Address module of SHINES Person Detail to be sent to GA Gateway for CPS Cases for an initial CAPS referral |
CAPS - 1.1 |
CAPS - 1.1.44 |
The system shall require the telephone number of the primary caretaker of the CAPS-eligible individual from the Phone module of SHINES Person Detail to be sent to GA Gateway for CPS Cases for an initial CAPS referral |
CAPS - 1.1 |
CAPS - 1.1.45 |
The system shall require the first name of the case manager of a CAPS-eligible individual from the 'First:' field on SHINES Staff Detail to be sent to GA Gateway for an initial CAPS referral |
CAPS - 1.1 |
CAPS - 1.1.46 |
The system shall require the last name of the case manager of a CAPS-eligible individual from the 'Last:' field on SHINES Staff Detail to be sent to GA Gateway for an initial CAPS referral |
CAPS - 1.1 |
CAPS - 1.1.47 |
The system shall require the office location of the case manager of a CAPS-eligible individual from the 'Office Location' field on SHINES Staff Detail to be sent to GA Gateway for an initial CAPS referral |
CAPS - 1.1 |
CAPS - 1.1.48 |
The system shall require the telephone number of the case manager of a CAPS-eligible individual from the Number column from the Phone subsection of SHINES Staff Detail to be sent to GA Gateway for an initial CAPS referral |
CAPS - 1.1 |
CAPS - 1.1.49 |
The system shall require the email address of the case manager of a CAPS-eligible individual from the email address field on Address Detail of SHINES Staff Detail to be sent to GA Gateway for an initial CAPS referral |
CAPS - 1.1 |
CAPS - 1.1.50 |
The system shall require the first name of the supervisor (supervisor of the CM) of a CAPS-eligible individual from the 'First:' field on SHINES Staff Detail to be sent to GA Gateway for an initial CAPS referral |
CAPS - 1.1 |
CAPS - 1.1.51 |
The system shall require the last name of the supervisor of a CAPS-eligible individual from the 'Last:' field on SHINES Staff Detail to be sent to GA Gateway for an initial CAPS referral |
CAPS - 1.1 |
CAPS - 1.1.52 |
The system shall require the office location of the supervisor of a CAPS-eligible individual from the 'Office Location' field on SHINES Staff Detail to be sent to GA Gateway for an initial CAPS referral |
CAPS - 1.1 |
CAPS - 1.1.53 |
The system shall require the telephone number of the supervisor of a CAPS-eligible individual from the Number column from the Phone subsection of SHINES Staff Detail to be sent to GA Gateway for an initial CAPS referral |
CAPS - 1.1 |
CAPS - 1.1.54 |
The system shall require the email address of the supervisor of a CAPS-eligible individual from the email address field on Address Detail of SHINES Staff Detail to be sent to GA Gateway for an intial CAPS referral |
CAPS - 1.1 |
CAPS - 1.1.55 |
The system shall send the following values to GA Gateway if the supervisor role of the case manager of a CAPS-eligible individual is currently vacant for an initial CAPS referral: Name: Early Childhood Collaboration Unit Address L1: 2 Peachtree St NW Address L2: Suite 26.465 City, State, Zip: Atlanta, Georgia 30303 Telephone Number: 404-463-1575 Email: early.childhood@dhs.ga.gov |
CAPS - 1.1 |
CAPS - 1.1.55.1 |
The system shall send the following values to GA Gateway if the county director role of the legal county of the CAPS-eligible individual is currently vacant for an initial CAPS referral: Name: Early Childhood Collaboration Unit Address L1: 2 Peachtree St NW Address L2: Suite 26.465 City, State, Zip: Atlanta, Georgia 30303 Telephone Number: 404-463-1575 Email: early.childhood@dhs.ga.gov |
CAPS - 1.1 |
CAPS - 1.1.56 |
The system shall require the first name of the county director (of child’s legal county) of a CAPS-eligible individual from the 'First:' field on SHINES Staff Detail to be sent to GA Gateway for an initial CAPS referral |
CAPS - 1.1 |
CAPS - 1.1.57 |
The system shall require the last name of the county director of a CAPS-eligible individual from the 'Last:' field on SHINES Staff Detail to be sent to GA Gateway for an initial CAPS referral |
CAPS - 1.1 |
CAPS - 1.1.58 |
The system shall require the office location of the county director of a CAPS-eligible individual from the 'Office Location' field on SHINES Staff Detail to be sent to GA Gateway for an initial CAPS referral |
CAPS - 1.1 |
CAPS - 1.1.59 |
The system shall require the telephone number of the county director of a CAPS-eligible individual from the Number column from the Phone subsection of SHINES Staff Detail to be sent to GA Gateway for an initial CAPS referral |
CAPS - 1.1 |
CAPS - 1.1.60 |
The system shall require the email address of the county director of a CAPS-eligible individual from the email address field on Address Detail of SHINES Staff Detail to be sent to GA Gateway for an initial CAPS referral |
CAPS - 1.1 |
CAPS - 1.1.61 |
The system shall require the value 'In Head Start' to be sent to IES from SHINES when the CAPS-eligible child’s current education record indicates an education type of 'Head Start' (satisfies IES’s 'Placement' field) |
CAPS - 1.1 |
CAPS - 1.1.62 |
The system shall require the value 'In Early Head Start' to be sent to IES from SHINES when the CAPS-eligible child’s current education record indicates an education type of 'Early Head Start' (satisfies IES’s 'Placement' field) |
CAPS - 1.1 |
CAPS - 1.1.63 |
The system shall require the value 'In Informal Child Care' to be sent to IES from SHINES when the CAPS-eligible child’s current education record indicates an education type of 'Informal Child Care' (satisfies IES’s 'Placement' field) |
CAPS - 1.1 |
CAPS - 1.1.64 |
The system shall require the value 'In QR-Formal Child Care' to be sent to IES from SHINES when the CAPS-eligible child’s current education record indicates an education type of 'Child Care' (satisfies IES’s 'Placement' field) |
CAPS - 1.1 |
CAPS - 1.1.65 |
The system shall require a system-generated transaction ID to be sent to IES from SHINES when a CAPS referral is submitted (Transaction ID field) |
CAPS - 1.1 |
CAPS - 1.1.66 |
The system shall send the following values to GA Gateway if the Supervisor’s telephone number or email address is currently blank for an initial CAPS referral: Telephone Number: 404-463-1575 Email: early.childhood@dhs.ga.gov |
CAPS - 1.1 |
CAPS - 1.1.67 |
The system shall send the following values to GA Gateway if the County Director’s telephone number or email address is currently blank for an initial CAPS referral: Telephone Number: 404-463-1575 Email: early.childhood@dhs.ga.gov |
CAPS - 1.1 |
CAPS - 1.1.68 |
The system shall send the following values to GA Gateway if the Case Manager’s telephone number or email address is currently blank or invalid for an initial CAPS referral: Telephone Number: 404-463-1575 Email: early.childhood@dhs.ga.gov |
CAPS - 1.2 |
CAPS - 1.2.1 |
The system shall require the Provider Rate Sheet to be sent to GA Gateway for an initial CAPS referral |
CAPS - 1.2 |
CAPS - 1.2.2 |
The system shall send GA Gateway the Provider Rate Sheet every time it is uploaded to External Documentation for a CAPS-eligible individual along with a provider change after the initial referral |
CAPS - 1.2 |
CAPS - 1.2.4.1 |
The system shall require SHINES to send the Pre-K Referral uploaded to SHINES External Documentation to GA Gateway for CAPS-eligible child with school record indicating education type of Child Care and grade of Pre-K |
CAPS - 1.3 |
CAPS - 1.3.1 |
The system shall send the Birth Certificate of the child to GA Gateway once it has been uploaded to SHINES External Documentation for a CAPS-eligible individual |
CAPS - 2.1 |
CAPS - 2.1.1 |
The system shall send the legal status of the CAPS-eligible individual from SHINES Legal Status to be sent to GA Gateway when it has been updated/change (from in-DFCS Custody to Not in DFCS Custody for Foster Care cases send 'N' and from Not in DFCS Custody to in-DFCS Custody for CPS cases send 'Y') after the initial referral |
CAPS - 3.1 |
CAPS - 3.1.1 |
The system shall send the address (Street, City, State, Zip) of the caregiver/resource of the current placement of the CAPS-eligible individual from the Address/Phone Detail module of SHINES Placement Information to be sent to GA Gateway for Foster Care Cases when the resource has changed after the initial referral |
CAPS - 4.2 |
CAPS - 4.2.3 |
The system shall store the CAPS certificate of eligibility of a CAPS-eligible individual when it is received from GA Gateway (Note: Backend storage) |
CR379-1.1 |
CR379-1.1.1 |
The system shall send the value 'Safety Resource' to satisfy the Reason Care Needed field for an initial CAPS Referral for a child in the INV stage when there is an active, APRV safety resource |
CR379-1.1 |
CR379-1.1.2 |
The system shall send the value 'Case Plan/Safety Plan' to satisfy the Reason Care Needed field for an initial CAPS Referral for a child in the INV stage when there is an APRV Safety Plan and no APRV Safety Resource |
CR379-1.1 |
CR379-1.2.1 |
The system shall send the value 'Safety Resource' to satisfy the Reason Care Needed field for an initial CAPS Referral for a child in the ONG stage when there is an active, open, APRV safety resource |
CR379-1.1 |
CR379-1.2.2 |
The system shall send the value 'Court Order' to satisfy the Reason Care Needed field for an initial CAPS Referral for a child in the ONG stage if an APRV Family Preservation Family Plan has the Court Order checkbox marked |
CR379-1.1 |
CR379-1.2.3 |
The system shall send the value 'Case Plan/Safety Plan' to satisfy the Reason Care Needed field for an initial CAPS Referral for a child in the ONG stage when there is an APRV Safety Plan and no APRV Family Plan or APRV Safety Resource |
CR379-1.1 |
CR379-1.2.4 |
The system shall send the value 'Case Plan/Safety Plan' to satisfy the Reason Care Needed field for an initial CAPS Referral for a child in the ONG stage when there is an APRV Family Preservation Family Plan and no APRV Safety Plan or Active Safety Resource |
CR620909 |
CR620909 |
|
CR776365-BR-01.2 |
CR776365-BR-01.2 |
The system shall be modified to display the Terminated or Denial Reason on the CAPS Update submodule. The statuses will be displayed under the Eligibility Status heading (we will not be adding an additional field) The date last updated (Dt_Last_Update) will be displayed as the date the termination or denial was received. These dates will be displayed under the Begin Date column (we will not be adding an additional field). |
CR776365-BR-02 |
CR776365-BR-02 |
System should be modified so that Provider Change request must include the provider phone and address of the provider |
CR776365-BR-01.3 |
CR776365-BR-01.3 |
System should be modified If Legal Status changes from Y to N, Legal Status date will be sent by SHINES. In shine there is scenario where child is coming back in custody with same shine case and different stage in this case shine is sending subsequent on it instead of new initial referral, Shine will correct that to send it as new referrals (AFB) |
CR776365- BR-01.1 |
CR776365-BR-01.1 |
Gateway Client Id must take precedence over the Shines Id, the correct ID selected should override the Shines EMPI id and sent to Shines. Updated EMPI ID is sent back to SHINES and Merge request is sent by Gateway. Shine will get this New ID in Inbound table .Also through the EMPI alert service ,Where as per existing functionality Shine will end date the OLD EMPI id and keep New EMPI id with Start date from backend .New EMPI ID with start date will displays on Person Identifier section . |
CR 771654-BR-01 |
Add new column in IES Doc Inbound table to provide SHINES users the ability to view the CAPS Eligibility Certificates in the Georgia SHINES application. |
Technical Design
Technical Overview
The CAPS Referral Outbound Interface is used to provide information needed to complete a CAPS referral for children who are in Foster Care or Child Protective Services. The referrals for children in Foster Care will be an automated process generated by the system and referrals for children in CPS will be a manual process through a button located on Education Detail.
Web Service Exchange
Mapping files for the data flow between SHINES and Gateway via GTA
The following entries are made to the SHINES IES_CAPS_REF_OUTBOUND_ENC table based upon the scenarios listed.
| S.No | Scenario | Request Type | Interface Status | Mandatory Params |
|---|---|---|---|---|
1 |
Initial Application |
AFB |
NEW |
Please refer to section 1.7 Request/Response Elements for mandatory params |
2 |
Placement Change |
RMP |
NEW |
Please refer to section 1.7 Request/Response Elements for mandatory params |
3 |
Provider Change |
RMC |
Please refer to section 1.7 Request/Response Elements for mandatory params |
|
4 |
Legal Status Change |
RLC |
NEW |
Please refer to section 1.7 Request/Response Elements for mandatory params |
5 |
Document Upload (Birth Certificate/Pre-K Referral) |
DOU |
NEW |
Please refer to section 1.7 Request/Response Elements for mandatory params |
Technical Description
Based upon the above 5 scenarios the entries are made into the IES_CAPS_REF_OUTBOUND_ENC and/or IES_CAPS_REF_DOC_OUTBOUND as necessary.
The entries are sent to Gateway by batch executed by GTA every 15 mins.
As and when the Gateway process the referrals, they send back the Certificate Document Information and the referral Status to SHINES, via GTA which are then stored in the following INBOUND tables – IES_CAPS_REF_INBOUND_ENC, IES_CAPS_REF_CERT_INBOUND and IES_CAPS_REF_DOC_INBOUND. The triggers on these INBOUND tables will copy the data received from Gateway into corresponding SHINES tables which in-turn will be displayed in the application for end user to access.
Provider address will be mandatory on education details page to send any Caps referrals
Document Change Log
| Date | Author | Change Description |
|---|---|---|
02/17/2024 |
Rasika Jahagirdar |
Updated section 2.2,1.19,,1.0 |
6/13/2023 |
Rasika Jahagirdar |
Updated Section 2.12,2.3,1.2 |
3/20/2023 |
Rasika Jahagirdar |
Updated Section 2.2,1.7 |
2/23/2023 |
Janice Nelson |
Updated section 1.0,1.2,1.7,1.19 |
09/16/2021 |
Rasika Jahagirdar |
1.19 section to add New Requirement |
12/3/2019 |
Venkat Collooru |
Updated 2.0 Technical Design Sections |
6/6/2018 |
Christine Nguyen |
Updated section 1.2 (Functional Description) to specify placement updates (when resource changes) will invoke the interface when the placement is in COMP or APRV status. Added additional details specifying that the CAPS Update submodule on Person Detail will display on successful submission of a CAPS referral from SHINES as well as an event on the Event List page. |
5/9/2018 |
Christine Nguyen |
Confirmed with Felecia and clarified that a ‘Provider Change’ update requires a provider change and a provider rate sheet upload. Edited requirement 1.1.16 and 1.2.2 to clarify this. |
4/23/2018 |
Christine Nguyen |
Updated per CR 379 to update the system-generated logic for completing the Reason Care Needed field in a CAPS Referral to GA Gateway: Section 1.0 – functional requirements Section 1.7 – request/response elements – detailed the logic of determining this field based on stages and APRV documents within the stage Section 1.19 – design requirements |
3/15/2018 |
Christine Nguyen |
Updated req’t WIC – 1.1.36 to include that for CPS cases, the legal county field will pull the case county |
10/19/2017 |
Christine Nguyen |
Initial version created |
Note: A new row explaining document changes must be added to the Document Change Log for each revision. The Document Change Log must be maintained in reverse chronological order. The most recent changes are on the top of the list.