Frequently Asked Questions
Q: How will CWS-CARES get the Aid Codes for the cases?
A: Aid Codes information comes directly from CalSAWS.
Q: Will you be able to see if a child has Medi-Cal, Medi-Cal Fee for Service or Managed Care Medi-Cal, and what health provider they have?
A: Medi-Cal is not being tracked in CARES V1, and CARES V2 scope is not yet available.
Q: Will user role configuration be specific to a position or function?
A: Role configuration will be specific to a function. This work will be performed by organizations as part of an activity called role mapping in which security profiles for CWS-CARES will be provided to your organization (through your IC) and your implementation team will have the opportunity to assign profiles based on job responsibilities.
Q: Will current feedback items be compared to feedback that was given during previous Extended User Scenario Testing (EUST) periods?
A: Yes, the EUST 3 feedback items have been compared against the feedback submitted during the first two EUST cycles as the Product Team reviewed each item. As part of our analysis, we reviewed the product backlog all three periods to identify recurring themes, confirm whether previously reported issues had been addressed, and assign appropriate determination type for each feedback item. We understand that some items may still appear during Production Simulation. In many cases, these items are already scheduled for updates in upcoming releases, are in progress, or require further validation to ensure the solution meets user expectations. Production Simulation is intended to provide counties with another opportunity to confirm whether previously reported items have been resolved and to surface anything that still needs attention. Our goal is to ensure counties feel heard and that feedback from all EUST cycles is thoroughly considered as we prepare for rollout.
Q: Were users contacted for the Extended User Scenario Testing (EUST) 3 items that were categorized as "can't replicate?"
A: Users were contacted to request the additional information needed to accurately triage and prioritize the issue. If no response was received, the item remained categorized as 'Unable to Replicate' because the project team could not reproduce the issue without further details.
Q: Why were some users invited to provide Extended User Scenario Testing (EUST) 3 feedback and not invited to Production Simulation?
A: Participation in the current phase of Production Simulation was based on whether users participated in EUST 3. Our goal for this phase was to start with users who are already familiar with the system’s navigation and processes, so they can help validate updates and identify any remaining issues efficiently. Additional phases of Production Simulation will expand participation to a wider tester group, allowing more users to provide feedback as we progress.
Q: How are you planning to consolidate Production Simulation feedback with existing Extended User Scenario Testing (EUST) feedback?
A: All feedback from Production Simulation and EUSTs follows the same process and is reviewed by the same team. All feedback is evaluated collectively alongside all other feedback received.
Q: Can counties build flexibility into Binti contracts in case of any unexpected issues with CWS-CARES V1 go-live?
A: Yes, in All County Letter 18-47 CDSS encourages counties to work with their contract and procurement offices to incorporate language into any vendor contracts for external systems that may allow for flexibility to modify and/or terminate contracts as appropriate as the statewide functionality is developed and fully implemented in CWS-CARES.
Q: What kind of testing activities are recommended for organizations to complete in Production Simulation for external systems? Should testing vary based on fully in scope or partially in scope systems?
A: Organizations should use Production Simulation and recorded demonstrations to test real workflows in CWS-CARES V1 using converted data as it becomes available.
For fully in-scope systems, we recommend organizations validate their required workflows can be completed from start to finish in CWS-CARES V1 without relying on the external system.
For partially in scope systems, organizations are encouraged to use a mix of common daily tasks, workflows, and county-specific processes to identify the boundary between CWSCARES V1 and the external system. The organization will then know which steps occur in CWS-CARES, and which steps remain outside CWS-CARES. Thus, validating functionality that is partially in-scope.
The ESCU recommendations for validation tools and activities in Production Simulation are available in the February 2026 External Systems Monthly Meeting Materials within the External Systems Portal.
Q: Which CWS-CARES Version 1 (CARES V1) activities will be completed within California Statewide Automated Welfare System (CalSAWS)?
A: The Foster Care Eligibility Determination (FCED) is an interface that will electronically transmit key case and placement data between CWS-CARES Version 1 (CARES V1) and California Statewide Automated Welfare System (CalSAWS) in near real-time. This includes the transmission of determination results back to CWS-CARES V1 and the sharing of documents, forms, and notices between CalSAWS and CWS-CARES users.
For information related to the CalSAWS activities completed in CWS-CARES, please refer to the Process Information Session for Placement and Eligibility which provides a walkthrough of the CWS-CARES Version 1 (CARES V1) To-Be Process Map and Change Impacts.