Frequently Asked Questions
Process Information Session (PIS)
Q: Will the non-Foster Care locations (aka placements) be sent to CalSAWS? If a child is removed from the placement location and sent on an extended visit, we would want the Foster Care placement to discontinue in CalSAWS, but we wouldn't want the non-Foster Care location to populate to CalSAWS because we aren't issuing payment.
A: No, the only placement information required to support Foster Care Eligibility Determination will be transmitted to CalSAWS. Non-Foster Care placement information that is not needed for eligibility or payment purposes will not be sent. More specifically, if a child is moved to an Alternative Care placement, that information will be sent to CalSAWS. If the child is absent from their existing placement, such as for an Extended Visit, that information will not go to CalSAWS. As a note, the CWS-CARES Worker can send Bed Hold information to CalSAWS subject to their county business processes.
Q: Los Angeles assigns "Library" to the case on the assignment page, so the case will populate under that specific month, and we know that Redetermination is due that specific month. Will we continue to do this process in CWS-CARES?
A: Counties will continue to manage assignments based on their local business processes. Los Angeles County's current process can continue if it aligns with its CWS-CARES implementation and business needs. Additionally, CalSAWS will inform CWS-CARES of what the Redetermination Due date is, and CWS-CARES supervisors can pull a report of cases each month of redeterminations coming due for their unit that can be used.
Q: Is there a way to remind users to request forms? For example, the SOC 161 form must be filled out every six months. Can a reminder be set for the worker to remind them to request/send this form?
A: No, CWS-CARES Version 1 (CARES V1) does not include reminder functionality for requesting or sending eligibility forms such as the SOC 161. However, CWS-CARES Version 1 (CARES V1) does have the functionality to create a report of Foster Care Redeterminations that are coming due. Counties can also use the Tasks feature to remind workers to generate certain forms at certain times. These features and functionalities alongside county business processes can be leveraged to send reminders to staff.
Q: Do Requests for Information (RFIs) have a built-in escalation process, or do they sit for however long it takes to get the requested information?
No, CWS-CARES Version 1 does not include an automated escalation process for Requests for Information (RFIs). Counties should continue following their existing business processes for monitoring and responding to RFIs.
Why are there separate fields for Current Child Address and Placement Address in the Mandatory Child Eligibility Request Information section of the Eligibility Record? Wouldn't these addresses always be the same if the Eligibility Record is generated when a placement is made?
A: Yes, the Product Team is looking at having just one address, but this change will not be made in CWS-CARES Version 1 (CARES V1).
Q: In our county, the CalSAWS Eligibility Worker collects and enters income. If a worker enters income in CalSAWS, will that populate the income in CWS-CARES?
A: Yes, property or income information entered in CalSAWS for the focus child will transmit over to CWS-CARES. Property or income for other members of the Home of Removal will not be sent from CalSAWS to CWS-CARES in Version 1.
Q: In the Kin-GAP process map, the CWS-CARES user sends over a change in program before they discontinue the Foster Care case. Do we know what happens in CalSAWS when the "change of program" is received?
A: To process the change in program information, CWS-CARES will send information through the Foster Care Eligibility Record to inform CalSAWS about closing the case. CWS-CARES will also send a new Case Link request for a newly opened Kin-GAP Eligibility Record to initiate CalSAWS opening a Kin-GAP case.
Q: Will users in CalSAWS and CWS-CARES have to keep both systems up-to-date manually?
A: No, information supported by the Foster Care Eligibility Determination (FCED) interface will be transmitted automatically between CWS-CARES and CalSAWS. Information that is not included in the interface will continue to require existing county business processes.
Q: If the same form is created in CWS-CARES and CalSAWS, will both systems have duplicates?
A: No, CWS-CARES will generate forms that support CWS-CARES business processes. Forms generated in CWS-CARES will not also be generated by CalSAWS as part of the interface.
Q: Not all data is shared bi-directionally via Foster Care Eligibility Determination (FCED) from CalSAWS to CWS-CARES. How will workers know what can be transmitted via FCED versus what needs to be manually shared via e-mail or other processes?
A: The Project is working on developing a document and business process guidance that identifies what information and data elements is exchanged between CWS-CARES and CalSAWS. Any information not supported by the interface must continue to be shared through existing county processes. Additionally, the July 2026 FCED Newsletter can be referenced to see which APIs have a unidirectional flow of information between CWS-CARES and CalSAWS.