Frequently Asked Questions

Data

Q: Can social work staff or supervisors be included in the attendance of the Data Conversion Workgroup meeting or is the focus more specific to the actual technical conversion of the data?

A: The purpose of the Data Conversion Workgroup is to validate the data mapping and not the CARES application. It is best to have people that understand the underlying data and fields, who can best validate that the intended data is properly related to the appropriate object model in CARES. This is best suited for people who have some type of experience with data models, xTools, databases, or Entity-Relationship-Diagrams.

Q: Can you provide information on county data transfers, housing data in from Child Welfare Services-California Automated Response and Engagement System (CWS-CARES) in house, and how counties will receive our data in monthly extracts?

A: Yes, data extracts will be available. The project is currently working on designing and implementing secure mechanisms to provide data extracts to organizations. Details will be provided via CWS-CARES Analytics Transition Workgroup in the coming weeks.

Q: How will data be improved in Child Welfare Services-California Automated Response and Engagement System (CWS-CARES)?

A: CWS-CARES is being designed through guidance from the Comprehensive Child Welfare Information System (CCWIS) requirements as set by the Administration on Children Youth and Families (ACYF). These regulatory requirements will ensure that data collected will be:

  • Complete, Timely, and Accurate
  • Consistently & Uniformly Collected
  • Exchanged & Maintained Confidentially
  • Implemented & Maintained through Automated Functions
  • Supportive of Child Welfare Policies, Goals & Practices
The California CCWIS Data Quality Plan includes the Data Quality Improvement (DQI) framework that defines processes and tools intended to meet the above data collection objectives and for continual monitoring and improvement through transparent communications. Built-in processes that can contribute to improved data quality that will be a part of CWS-CARES:
  • Data will be validated at collection (I.e., data entry)
  • Data in CWS-CARES will be continually measured through data profiling and data quality assessments. CWS-CARES data stewards will work closely with the data governance and data quality teams in determining the criticality of any data violations and the effectiveness of the remediations.
  • Using automated data exchanges in a standardized format with various external sources to provide supporting data, in turn, reducing manual entry with the goal of preventing data inconsistencies and inaccuracy.
  • Improved data analysis tools that can assist in trends, projections, and identifying gaps in providing child welfare services.
  • Providing master data management (MDM) to provide a single source of truth throughout CWS-CARES thereby avoiding duplicates, redundancy, and inaccuracy.
All of this will result in creating CWS-CARES as a decision support system and an evidence-based system that will streamline workflows to alleviate current pain points and improve data to keep workers spending time with children and families and contribute to better safety, permanency, and well-being outcomes.

Q: Is the Organization (Org) Data Conversion Workgroup Subject Matter Expert (SME) more of a technical position, policy position, or can it be filled by a Children and Family Services Supervisor or Child Welfare Social Worker?

A:  It is recommended the participating Organization’s Subject Matter Experts (SME’s):

  • Understand data in the legacy system Child Welfare Services/Case Management System (CWS/CMS)
  • Understand how the data is inter-related in CWS/CMS
  • Understand data transformation rules.
  • Understand data quality concepts.
  • Are familiar with database and related concepts, i.e., entities, attributes, data types, relationships, mandatory fields, and list of values (LOVs)
  • Are familiar with the current CWS/CMS business model (i.e., Referrals, Allegations, Delivered Services, Cases)
  • Have knowledge of County policies and/or County desk procedures that direct specific data entry for a program or interim solution that may have used data fields for data other than their original intent. Sometimes counties have very specific data they want to capture.
  • Have knowledge of County business practices (possibly by program) that will help identify the intentional or unintentional use of a field. For example:
    • Storing the Corporate Identification Number (CIN) number in a different data field (before the CIN number was added to CWS/CMS)
    • Storing a CalWORKs number in a data field intended for something else.
    • Storing American Academy of Pediatrics (AAP) and/or Kinship Guardianship Assistance (Kin-GAP) program information in CWS/CMS data fields designated for other programs/placements
    • Are familiar with any County unique dropdowns/screens/fields.
    • Understand use or misuse of a field to record data that was not the original intent of the data element.
Please email CWDS Implementation if you have additional questions.

Q: What position, skills, or requirements are expected for Data Stewards?

A: Data Stewards include staff from the County Welfare Directors Association of California (CWDA), County Child Welfare Departments, County Juvenile Probation Departments, Title IV-E Tribes, and California Department of Social Services (CDSS). CARES Data Stewards will be responsible for reviewing artifacts provided by the Conversion team and working with the CWDS Data Team on Data Quality management and cleanup. Data Stewards will participate in and be responsible for:

  • Data Quality
  • Data Clean-up
  • Data Practice Validation activities
  • Ongoing Data Stewardship during Conversion and post CWS-CARES Go-Live.

Q: Can counties get guidance for validating converted data?

A: Yes, there are certain activities that counties should practice when validating converted data. As guidance, counties should practice the following:

  • Identify knowledgeable staff
  • Validate accuracy and completeness
  • Run county-specific test scenarios
  • Provide structured feedback