Frequently Asked Questions
Stakeholder Briefing
Q: How will duplicate persons be identified and merged in CWS-CARES?
A: Users with the Merge permission can search for persons using Person Search and select duplicate persons from the search results to merge them.
Q: When is the Production Simulation Phase II User List due to the project with the revised user permissions for the bulk upload?
A: Information on this is currently being planned out by the Project, details on it will be released via a formal communication once it is available.
Q: In CWS/CMS, users often have to exit Word documents and restart to generate a Health and Education Passport (HEP) or form. Is this resolved in CWS-CARES?
A: The Health and Education Passport (HEP) in CWS-CARES is generated as a PDF.
Q: Will the California Immunization Registry (CAIRS) be linked to CWS-CARES so immunizations can be downloaded into the Health and Education Passport (HEP)?
A: The California Immunization Registry (CAIRS) is under consideration for future inclusion in CWS-CARES functionality.
Q: Is a .gov email address required to subscribe to the Weekly Digest?
A: No. A .gov email address is not required to receive the Weekly Digest. It is freely available to anyone and can be subscribed to using the CWS-CARES Weekly Digest Subscription Form.
Q: Will a Virtual Private Network (VPN) be necessary to access CWS-CARES?
A: CWS-CARES will be accessible via supported devices connected to the county network. Connectivity may be through a hard-wired or wireless network connection, or over the internet via a VPN connection as implemented by the county. Users must be authenticated by the county's identity and access management system.
Q: Is there spell check in CWS-CARES?
A: Yes. CWS-CARES includes spell check: a red underline appears beneath words that may be misspelled, and users can right-click to see suggested corrections.
Q: Were any feedback items recategorized to the proper CWS-CARES area?
A: Yes. During the review process, the CWS‑CARES Product Team recategorizes feedback items on the back end as needed. If an item was submitted under an incorrect area, it was reassigned to the appropriate CWS‑CARES functional area during triage and prioritization, so the results are not skewed by the category originally selected by the user.
Q: What is the plan for the next phase of feedback collected during user testing?
A: There will be another opportunity for counties to provide feedback prior to rollout. The next phase of feedback will occur during Production Simulation, where users will be able to validate system functionality, confirm updates made from EUST 3 findings, and submit any additional feedback that was not captured previously. Details on the Production Simulation schedule and feedback process will be shared in advance so counties can plan accordingly. Regarding the volume of EUST 3 feedback, the team reviewed and triaged all items using a consistent methodology to ensure each item received a determination. We understand that some users were not able to submit all their feedback during EUST 3, and Production Simulation is designed to provide that additional opportunity. Our goal is to ensure feedback is gathered comprehensively before rollout, support system readiness and a smooth transition for users.
Q: What is the plan to implement the feedback provided during Extended User Scenario Testing (EUST), considering the upcoming code freeze on July 30, 2026, and what will be the impact on training material, considering training materials are due in June 2026?
A: Feedback will be implemented based on priority and severity, guided by the determination type assigned to each item. Items identified as high‑priority or critical will be addressed before code freeze whenever possible.