Frequently Asked Questions
Interfaces
Q: Given the ongoing problems with payment delays, incorrect validation logic, and data mismatches, what progress has been made on improving FCED?
A: To resolve current Foster Care Eligibility Determination (FCED) issues, development and testing should be completed ahead of Code Freeze, with clear identification of mandatory data fields, automated resubmission and error reporting for interface failures, and full end‑to‑end payment‑processing testing. Additional steps include producing daily reconciliation reports and establishing a process that allows payments for voluntary foster care placements when a petition is not yet sustained.
Q: What is the plan for system cutover, and how will downtime be minimized?
A: The plan for system cutover, as voted and approved by the Board of Directors on September 3, 2026, is to switch CWS/CMS to read‑only on Thursday at 5 p.m. This approach minimizes the amount of time counties operate in read‑only mode and helps reduce overall downtime. Because the cutover occurs shortly before Go‑Live, final validation and remediation are limited to one day prior, which reduces the time available for pre‑launch validation and issue resolution.
For full details, see the Important Update: CWS-CARES Go-Live Date Adjusted to December 7, 2026 communication on the CWDS website.
Q: I am a Binti county. How will my county’s existing RFA cases that still need action be handled as we move from the previous system to the new one?
A: Guidance explaining temporary procedures counties must follow for Resource Family Approvals (RFA), Resource Family Homes (RFH), and Emergency Placements when CWS‑CARES Version 1 (CARES V1) goes live was released August 31.
At CARES V1 Go-Live:
- All new RFA/RFH applications and Emergency Placements must be started and managed in CWS‑CARES.
- If an RFA/RFH application is approved in an external system after Go-Live, counties must re‑create and fully process the application in CWS‑CARES so the Resource Family Home can be created.
- Applications already in progress in external systems can continue there through approval.
- Historical information will remain in external systems until data is converted after Go-Live.
Q: Will the California Department of Education (CDE) interface replace Foster Focus?
A: No, the California Department of Education (CDE) and Foster Focus serve different purposes. The CDE interface available in CWS-CARES V1 will not replace Foster Focus. Foster Focus is expected to continue operating after CWS-CARES Go-Live. Additionally, the Sacramento County Office of Education is leading the work on updating Foster Focus to accept new CWS-CARES Version 1 data. The CDE Interface will provide updated school (resource) data elements within CWS-CARES, similar to what is currently in CWS/CMS. This information will not include child specific school or grade level information.
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: 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: When testing Foster Care Eligibility and Determination (FCED), will the CWS-CARES Service Desk be able to answer questions about CalSAWS?
A: The CWS-CARES Service Desk will be able to assist with some questions regarding CalSAWS, but any issues or defects related to CalSAWS will need to be forwarded to the CalSAWS team. The Project will coordinate with interface partners to streamline that process.
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.
Q: What is the Opeeka Interface?
A: The Opeeka Interface will have the Child and Adolescent Needs and Strengths Assessment (CANS) assessment highlighted as well as multiple other assessments available (separate from Structured Decision Making (SDM) which have the more change based assessments). This will mirror how the CANS assessment is currently done, pulling it into CWS-CARES using the Opeeka Interface (referring to the system look and feel).