Frequently Asked Questions
Data
Q: Will CWS/CMS data overwrite Binti data?
A: Yes. CWS/CMS is the system of record. If a field already exists in CWS/CMS, Binti data will not override it.
Q: When a data refresh occurs, will the most recent CWS/CMS data be loaded into CWS-CARES, or will the environment reset to the data originally loaded for Production Simulation?
A: The Project plans one or two refreshes only, when needed, recognizing counties' preference to minimize refreshes. When a full data refresh occurs, the most recent updates from all legacy systems will be converted and applied to the environment, giving counties another opportunity to validate the most recent data.
Q: Will Binti documents be converted?
A: Yes. Binti documents, often referred to as unstructured data, are planned to be migrated into CWS-CARES.
Q: If workers are mid-function in CWS/CMS when it changes to read-only and data transfers to CWS-CARES, will in-progress items default to pending or be treated as finalized?
A: The Conversion team has developed and implemented transformation logic that allows users to continue "in-flight" cases, referrals, or other units of work (such as items pending approval) from CWS/CMS into CWS-CARES. Production Simulation is a good opportunity to test these in-progress workflows.
Q: Will all existing documents in CWS/CMS be migrated to CWS-CARES, and how will that migration be accomplished given the multiple document areas in CWS-CARES?
A: Yes. All existing documents in the legacy system will be available in CWS-CARES as part of the data conversion process.
Q: Can California Immunization Registry (CAIRS) immunization reports be uploaded into CWS-CARES rather than hand-entered?
A: For immunizations to appear in the Health and Education Passport (HEP), they must be entered into CWS-CARES. A CAIRS immunization report can be uploaded into the document section of CWS-CARES, but it will not generate as part of the HEP. CAIRS will not be included in CWS-CARES V1, though the Project is considering integrating the functionality in future development.
Q: Once county data is loaded into Production Simulation, will there be an environment available with mock data that counties can use when sharing screens with each other without data showing?
A: The Project is finalizing the plan to make the Training environment available and will share more details in a formal communication once they become available.
Q: When will the legacy data layer be available?
A: The Legacy Data Layer is available in CWS-CARES environments. Documentation is included in the CWS-CARES Data Dictionary and SqlDBM. County Developers have access to this in CARES102 (CountyDev) and this feature will be included in the Production Simulation environment once this is made available to the counties.
Q: When was the Family Finding module added?
A: The Binti Family Finding module was part of the original scope for Binti data conversion, it was not added later on.
Q: Will reports continue to be available in SafeMeasures as an ancillary application, be migrated into CWS‑CARES, or be embedded within the CWS-CARES system in some way?
A: Legacy SafeMeasures will continue to exist separately from CWS-CARES SafeMeasures. The legacy application will update as usual until we no longer receive CWS/CMS data. At that point, legacy SafeMeasures will stop updating and will be available with historical data. Legacy SafeMeasures will be maintained until CWS/CMS is decommissioned and we are told to decommission legacy SafeMeasures. This could happen six months after CWS-CARES implementation, but no hard date has been set. CWS-CARES SafeMeasures will not be integrated or embedded in CWS-CARES for V1. The new SafeMeasures will be a standalone application like it is currently but with a new URL and login page. Staff will be able to access both legacy SafeMeasures and CWS-CARES SafeMeasures sites.