Frequently Asked Questions
Implementation
Q: Which Extended User Scenario Testing (EUST) iteration will counties see Opeeka/IP-Child and Adolescent Needs and Strengths (CANS) in?
A: The Integrated Practice Child and Adolescent Needs and Strengths (IP-CANS) functionality, delivered through Opeeka, will be available in End User Scenario Testing (EUST) 3.
Q: Will CWS-CARES include an indicator to identify that a service provider is no longer active or viable?
A: At this time, an “Inactive/Active” indicator is not confirmed for CWS-CARES. Users can refer to the report date to see when the provider record was created to confirm whether they are a current provider.
Q: Is anything customizable in the Child and Family Team (CFT) documentation section, such as adding a section for the Child and Adolescent Needs and Strengths (CANS) discussion?
A: Yes, in the CFT documentation section the meeting topics are customizable and have various options that can be selected, including “Other Topic”. There is also a section for meeting notes with a character limit of 5K.
Q: Where is the connection between the Child and Family Team (CFT) function and generating a Child and Adolescent Needs and Strengths (CANS) assessment?
A: The connection between CFT function and generating a CANS must be determined through CDSS Policy guidance and training.
Q: Where will the Child and Family Team (CFT) Action Plan be located in CWS-CARES?
A: The Child and Family Team (CFT) Action Plan is located in the CFT Summary and Action Items section.
Q: The "wraparound" indicator is currently a special project code in CWS/CMS. What code or field will indicate wraparound services in CWS-CARES?
A: In CWS-CARES, wraparound services are captured as a service type within the "Case Management Services" category. A dedicated checkbox is also available to indicate wraparound services, consistent with how this information was captured in CWS/CMS.
Q: Will CDSS staff who are not currently fingerprinted need to be fingerprinted in order to handle case-specific CWS-CARES data?
A: All CDSS users who access case- or client-level information in CWS-CARES are required to be fingerprinted. State fiscal workers will have access to case- and client-level data through CWS-CARES financial management reports and will also need to be fingerprinted if they have not already been. In short: staff who have already been fingerprinted need take no further action; staff who have not been fingerprinted and will be given access will need to complete fingerprinting.
Q: Will CDSS or the Project provide updated confidentiality forms for CWS-CARES? The current forms reflect CWS/CMS.
A: Yes. The Project will provide updated confidentiality forms (such as the End User ID Application Form) for CWS-CARES. Once the CWS-CARES V1 permission sets are complete, the Project will release the official form.
Q: Can dedicated counties access CWS CARES V1 from both county and state computers, including county devices connected through VPN?
A: To access the live (steady-state) CWS-CARES system, dedicated county users are expected to use their dedicated county machines (supported by CWDS), similar to how they access CWS/CMS. County machines that are on the county network and not CWDS-supported are, by design, not allowed access to the steady-state CWS-CARES production system. Users with special requirements, similar to those in CWS/CMS, may be assigned as Citrix users based on specific business needs.
Q: For users who are new to CWS-CARES and never used CWS/CMS, are there additional processes they need to follow to get access?
A: There are no additional processes to follow. The county's CWS-CARES Administrator is responsible for adding new users to CWS-CARES. This includes current staff who never used CWS/CMS as well as new staff hired after CWS-CARES goes live. Current staff who are already active in CWS/CMS and have not been deactivated will automatically convert into CWS-CARES at Go-Live.