Product Features
Read about CWS-CARES functionality and new features. Expand your understanding of the new system, how it will work, and what the impact will be for end users.
The CWS-CARES Public Library is a searchable repository of project information. The articles published here may also be located in the CARES Explorer Newsletters. If you have any questions, please contact CWDS Communications.
Or browse articles by category:
Read about CWS-CARES functionality and new features. Expand your understanding of the new system, how it will work, and what the impact will be for end users.
Learn more about Service Areas (the core functions and capabilities of CWS-CARES related to child welfare activities and practices) and Milestones (significant stages in development).
Meet the people behind CWS-CARES and learn more about how different teams work together to shape the final product.
Dive deeper into the data and interfaces that will be needed for CWS-CARES.
We are pleased to share that the JNET interface for CWS-CARES is now completed ahead of schedule!
JNET is used to track children, youth, and young adults involved in the juvenile justice system, whether as probation wards or child welfare dependents.
The JNET interface is currently in use with CWS/CMS. The interface is being kept in place for CARES V1 at the request of San Bernardino County. The functionality in CARES V1 will be identical to the existing functionality in CWS/CMS. The interface will update the courts system with current assignments in CWS-CARES that applies to San Bernardino only.
Originally published in the CWS-CARES Explorer.
There are three Milestones that focus on reporting:
Federal Reports extends and consolidates metric development completed in previous milestones to generate required Federal Extracts (e.g., National Child Abuse and Neglect Data System (NCANDS), Adoption and Foster Care Analysis and Reporting System (AFCARS), Indian Child Welfare Act (ICWA), National Youth in Transition Database (NYTD)) and deliver interactive dashboard views of Federal Statewide Indicators and other required Federal reports, including those required to draw down Family First Prevention Services Act (FFPSA) funds. CWS-CARES dashboards will support pulling multiple populations as appropriate, including entry cohorts, exit cohorts, attribute- defined cohorts and point-in-time snapshots.
State Reports) extends and consolidates metric development completed in previous milestones to deliver interactive thematic dashboard views of both State and Federal metrics. Thematic dashboards organize process, practice (fidelity) and outcome metrics by theme, such as Prevention, Safety and Permanency.
In addition to the planned reports that will be available when CARES V1 goes live (federal and state requirements, key outcomes, and practice measures), CARES will provide data consumers with the ability to develop their own reports using Tableau. They will have access to all appropriate CARES data in close to real time, translated into the categories and terminology that are meaningful to child welfare practitioners and researchers. This will include the kinds of historical needed to perform longitudinal studies.
Originally published in the CWS-CARES Explorer.
The Indian Child Welfare Act (ICWA) is a federal law enacted in 1978 to protect the best interests of Native American children and promote the stability and security of Native American tribes and families. The ICWA establishes minimum Federal standards for the removal of Indian children, delineates the roles of State and Tribal governments in child welfare cases, establishes placement preferences for placement with family and Tribal members, and institutes protections for parents regarding the termination of parental rights. In California, ICWA provides guidance to counties, regarding the handling of child abuse and neglect and adoption cases involving Indian children and sets minimum standards for these cases, to support Indian children and families, and ensure children remain connected to their family, Tribe, and culture.
Among protections for Indian children, ICWA requires caseworkers to make several considerations when handling an ICWA case, including:
Providing active efforts to the family;
Identifying a placement that fits under the ICWA preferences provisions;
Notifying the child’s tribe and the child’s parents of the child custody proceeding; and
Working actively to involve the child’ tribe and the child’s parents in the proceedings.
ICWA ensures that tribes as sovereign nations, have a strong voice in child custody proceedings involving Indian children. Tribes have exclusive jurisdiction over cases when the child resides on the reservation, or when the child is a ward of the tribe. Tribes have concurrent jurisdiction for an ICWA case, when the child is living or domiciled off the reservation, or the Tribal court declines to take the case. In California when the county and Tribe have concurrent jurisdiction, ICWA establishes a presumption that the county must transfer jurisdiction to the Tribe, upon request.
Originally published in the CWS-CARES Explorer.The California Department of Social Services (CDSS) is the project sponsor and participates in various areas of the CARES project. Subject matter experts from Accounting, Fiscal, Legal and Program provide input and policy guidance on development activities.
The Child Welfare System Branch (CWSB) is responsible for representing the CDSS at Child Welfare Digital Services (CWDS). The branch chief wears multiple hats including sitting on the CWDS Executive Leadership Team. Five of the staff are Service Managers and work directly with the Product Delivery Team to develop functionality to support case management, external stakeholder coordination, financial management, resource family approval, resource management, reporting and metrics. Staff research child welfare regulation, statute, and county letter guidance to ensure CARES supports current child welfare policy and practice to comply with the Comprehensive Child Welfare Information System (CCWIS) requirements.
The team works directly with multiple tribes to identify how CARES will support users in meeting the Indian Child Welfare Act requirements. Working directly with counties, the team identifies external or ancillary systems to ensure business operations will not be impacted when CARES goes live. The team also provides fiscal oversight to the CARES project and conducts biennial data quality reviews as required by CCWIS. In the current CWS/CMS system, addresses are not validated when they are entered. This can cause problems if there are errors, or if the address does not exist.
In CARES V1, users will enter the address, search, and then select the correct one from a validated list. The goal of validating addresses as they are entered is to eliminate errors and duplicates, and to ensure that addresses exist. Address data will come from a tool called Smarty Streets.

Originally published in the CWS-CARES Explorer.
The Data Conversion Team has been working to convert data from CWS/CMS to CWS-CARES. To accurately capture the questions and needs of our counties, the Data Conversion Team has a process that they repeat every Data Conversion Cycle with new and existing groups for Practice and Data Validation (depending on service areas).
First, they schedule a kickoff meeting to provide a general overview of the data conversion process so that the counties know what to expect. For Practice Validation, the workgroup meets regularly to discuss the source to target mapping (STTM) and transformation logic for the original field in the legacy system and the new field in CARES V1. For Data Validation, office hours are scheduled to answer questions and walk through issues reported by the county testers.
The Data Conversion team tracks and addresses issues brought up by the counties, and revises STTM and/or transformation logic as needed. When functionality questions come up, the team also creates clarification requests and follows up with the Product team. All the responses and updates to issues raised are accessible real-time via Microsoft Teams.
We want to thank counties for their continued support in this critical process of validating data conversion!
Originally published in the CWS-CARES Explorer.The CWS-CARES project team has been working hard to enhance document generation and management in an effort called Content Management.
The three parts of Content Management for CARES V1 include: Document Generation (i.e., create documents) by Adobe Experience Manager (AEM), Document Management (i.e., access, collaborate and route documents) by DocuEdge, and eSignature by AdobeSign.
The CARES V1 system will:
Generate documents using the specific templates tailored by State, County, Organization, and Tribe
Organize, access, collaborate and pass along documents and forms for review
Easily route documents for eSignatures for both internal and external signers
Contain security features to keep sensitive data safe
Help create an accessible and inclusive online experience