Frequently Asked Questions
Data
Q: What forms can the two systems CalSAWS and CWS-CARES share?
A: CalSAWS and CWS-CARES can share documents. From CWS-CARES, an Eligibility Resource can upload any document to the Eligibility Record, so long as they're following county business practices, and it will be shared with CalSAWS. Forms that can be shared between CalSAWS and CWS-CARES includes all the regular forms related to Foster Care, ARC, Kin-GAP, AAP and foster care-related Medi-Cal. It also includes forms like birth certificates, affidavits, etc, as well as county forms.
Additionally, there are documents from CWS-CARES and the Focus Child's person record that are automatically pulled from the Eligibility Record such as birth certificates, court orders, regional center rate letters, placement agreements, etc. From CalSAWS, case-level documents are shared to CWS-CARES. If documents such as these mentioned are uploaded to the Eligibility Record in CWS-CARES or to the Case in CalSAWS, they will be shared in that way with the other system.
Q: What is the process to deactivate a user? Can it be done by the user themselves, or another party at the CBO, or can it only be done by a Child Welfare staff member with a CWS-CARES administrator login? What permissions does a CWS-CARES worker need to be able to add individuals to the provider portal? Will reports on logins/utilization by individuals be available, so counties can monitor users?
A: Regarding deactivation of a user in CWS-CARES, the CBO Portal Administrator will control activation and deactivation for their organization. To add and remove users, A CBO Portal Administrator permission their specific organization is required. The Project did not build native reports on data aspects such as logins and utilization by individual in CWS-CARES V1, but the data will exist within each organization’s portal and for the county Prevention Services Supervisor. County Prevention Services Supervisors will be able to monitor this data in CWS-CARES and could possibly have their own county Super Users build their own reports.
Q: What is the long-term solution for the Azure Object ID requirement?
A: The Object ID is a mandatory attribute and will be needed until we build an automated way to sync. The system also supports another flow, called Just in Time (JIT), for obtaining the object ID automatically during SSO, if the following conditions are true:
- This is a new user and does not exist in the CWS-CARES system
- The user is already added to Azure security group on the county (integrated county) side
- County administrator requests the user to login to CWS-CARES
Q: Will the Production Simulation (CARES 100) data refresh wipe any permissions CARES100 users might have changed or is it just the case data that's being wiped out and refreshed?
A: All data and permissions will be overwritten during the data refresh.
Q: What information will be available on the public Resource Family Approval (RFA) portal?
A: The Resource Family Approval (RFA) portal will be used for prospective and current Resource Families to either submit an application, upload documents to their current CWS-CARES worker, including but not limited to training certificates, required placement documentation and forms, such as the RFA 01, RFA 01B, RFA 7, RFA 11, etc. The portal will also be a place for the approved families to see what placements they have and any scheduled or completed home visits. Production Simulation has a window where counties will be able to test the RFA Portal from both perspectives: One from the CWS-CARES worker or the prospective of a current family utilizing the portal. If counties want to work with families using Production Simulation, the Project is not limiting who can use the portal. It is not production, so whatever is done there will need to be completed in the current business process.
Q: We may be able to use narrative fields but cannot collect data in CWS-CARES, does this mean we can enter it but not in a reportable way? And we haven’t received guidance as to whether or not there will be direction by Go-Live so we don’t know if we should spend time determining our own plan.
A: At this time, we are not able to collect additional SOGIE data in CWS-CARES. In the future, additional guidance will be provided by CDSS Program Policy that will outline how to document. Additionally, CWS-CARES cannot issue guidance on any workarounds outside of the two allowable data fields required; future guidance on this will also have to come from CDSS Policy.
Q: What updates can you share regarding progress on improving the reporting functionality?
A: The Project is currently assessing options to support counties and evaluating improvements to the reporting experience aligned with post‑CWS-CARES Version 1 (CARES V1) priorities and capacity.
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: Given the issues with unreliable search and record‑management functions, including duplicate results and limitations with merge/unmerge, what progress has been made to address these problems?
A: The unmerge workflow is currently under development. This work was previously dependent on onboarding the new Service Desk vendor; however, due to contracting timelines, the Project has moved forward with development of the technical components of the unmerge workflow.
Technical testing will be completed, and the timing will be confirmed. Once the new Service Desk vendor begins onboarding in early October, the Project will work with the vendor to validate the end-to-end unmerge ticketing process, including routing, assignment, notifications, and the ability to support the targeted 48-hour SLA.
The Project deployed additional enhancements and refinements to the Civica Search tool in the Production Simulation environment at the end of August 2026, including enhancements to the “AND/OR” search criteria. The Project continues to refine search functionality based on testing results and county feedback.
Q: Will there be improvements to the search functionality, and what enhancements can users expect?
A: The following Search enhancements were deployed to Production Simulation (Prod Sim, or CARES100) on August 29, 2026:
- The Person and RM (Resource Management) Directory Search now use the “And” operator instead of “Or,” resulting in more precise and narrowed search results.
- In Person Search, the “Sex at Birth” and “Approximate Age” criteria are now fully functional. Phonetic search for first and last names has also been enabled to make it easier to locate the intended individual. Previously reported performance issues, where searches took up to 2 minutes to return results, have been resolved.
- In RM Directory Search, multi-select capability for placement category types is now available.