Frequently Asked Questions
Q: Which RM Directory Types will counties be responsible for maintaining, versus those maintained by Child Welfare Digital Services (CWDS), California Department of Social Services (CDSS), or Community Care Licensing (CCL)?
A: Counties will maintain records for service providers, law enforcement agencies, county superior courts, district attorney offices, county offices, and adoption agencies, with much of this information being converted from CWS/CMS. The California Department of Education (CDE) will maintain education provider records, the Department of Developmental Services (DDS) will maintain information for regional centers, and Community Care Licensing (CCL) will maintain records for licensed facilities such as FFAs, STRTPs, and TTHPs.
Q: Is the process for adding a New Agency in CWS-CARES the same as adding a New Office?
A: Yes, while the video demonstration shows the user selecting “Law Enforcement Agency” for the Organization Type, this is essentially demonstrating how a user would add a new office.
Q: Are there any plans for a visitation module in CWS-CARES?
A: Yes, visitation will be included in CWS-CARES. We are planning the ability to document data related to visits attended, cancelled, and rescheduled. We are also including the ability to document a visitation quality rating based upon the SDM definitions of visitation quality. Scheduling visits will not be part of CWS-CARES in this first version. However, we will include the ability to document and track efforts to schedule visitation.
Q: Will go/no-go decisions be made on a county-by-county basis or statewide using county-specific information?
A: Implementation Leads (ILs) will work with each county to complete readiness activities over the implementation period. Progress on readiness activities will be reported regularly to the state. Any overdue activities will be evaluated and may be raised as a risk. The state will use county-level readiness progress to inform a single statewide go/no-go decision.
Q: Can the project provide a list for each survey, indicating: what is the purpose/content of the survey and who is the target audience?
A: Advised that the project is large and they may receive correspondence from multiple project groups. We will do our best to inform ahead of time when we are aware of any surveys being distributed. - In addition, the project is tracking communications through the Strategic Communications group to help keep everyone informed. The CARES Compass published every other month will list all planned communications for the upcoming 2 months.
Q: In the screening module, can you indicate if the referral for abuse is evaluated out?
A: Yes, Evaluate Out is one of the Response Types in the Screening flow.
Q: Will Folio continue to use the Mother’s name for the referral (Screening Name), and then switch to the individual focus child’s name for the Case after the Investigation?
A: The current process is to use the Mother's name for the referral. In CWS-CARES, this is referred to as "Screening Name" and is populated based on county process. Following the Investigation the Case is based on the individual focus child.
Q: Will CWS-CARES automatically filter out bad data before it transfers it to CWS-CARES?
A: CWS-CARES will have data validation rules to identify incorrectly entered information. For example, emails have to follow a standard format. So it would not accept "name@" as a complete email and would give the user an error. Similar rules apply to other fields like SSN, phone number, etc.
Q: Will training for this count towards required training hours?
A: Yes, training will count towards the required 20 hours.
Q: What is the onboarding process for new users to access CWS-CARES? Will it be the same as was with CWS-CARES-Live?
A: After Go-Live County Admins will have permissions to add/update/inactivate users. The CWS-CARES Okta Team is currently working through an integration process to connect CWS-CARES Okta to the organization's security process. [Riverside has completed the integration process] For organizations that participate in integration their users will experience a single sign on experience that is managed on the organization side through their administrative processes.