civictechdc/cfsa-referral

CFSA Referral Prototype

CFSA Referral Program

The DC Child and Family Services Agency (CFSA) is the public child welfare agency in the District of Columbia responsible for protecting child victims and those at risk of abuse and neglect and assisting their families.

There are 3 offices within CFSA: Community Partnerships, Child Protective Services (CPS), and Foster Care. This project focuses on client and case offerings within the Community Partnerships department. The referral program offerings are all voluntary, but have varying eligibility criteria that a client must meet.

The purpose of this project is to develop an app for case workers to use in the field to determine client eligibility and needs for certain CFSA voluntary programs including housing, educational, and substance abuse services. We aim to use the CFSA program eligibility criteria to build a data entry/decision tree app that would recommend the appropriate CFSA program.

Getting Started

This app was built with Create React App For testing framework please see Jest For more information on how the code works please reference the README found under the /app directory

• First, install node.js, then:

# Clone this repository
$ git clone https://github.com/codefordc/cfsa-referral.git

# Go into the repository
$ cd cfsa-referral/app

# Install dependencies
$ yarn install

# Run Tests
$ yarn test

# Run the app
$ yarn start

For additional documentation, visit our Google Docs project. To keep in touch, please join the #cfsa channel in the Code for DC Slack. Our Data Ambassadors are: Judy Yang, Michael Kalish, Aimee Barciauskas.

Prototype

Hosted on Invision, comments and mark-ups are welcome

https://invis.io/2AE4CENGY

9.23.17 Hackathon Activity

At the DC Health & Human Services Hackathon on September 23, 2017, the team consulted with the subject matter experts (Brittney and Tyanna) from CFSA. Our clients provided information on the problems and goals of the interactions that case workers have with clients in the field.

Together, we developed a decision tree of Yes/No questions that case workers should ask their clients in order to determine eligibility and best fit for CFSA's programs.

We focused on referrals for 6 CFSA programs with various focuses and eligibility criteria:

1. Mobile Stabilization Services (MSS)
2. Parent Education and Support (PESP)
3. Project Connect
4. Rapid Housing
5. Transitional Housing
6. Referral to Collaborative Agencies

Further details for each program is provided in the Google Docs project.

---

We created user flows and mockups using Balsamiq of the proposed app user interface and also worked on the decision tree app. The prototype was built using React and Javascript. The proposed app would function as follows:

• Search by client Name and DOB; Return results from FACES (CFSA system);
  • user selects relevant case or referral;
• Review case data populated from FACES;
  • Ability to update information including ward/address, income, family members/household;
• Answer key questions: Is there a crisis?
  • If Yes, referral to MSS
• If no, select the need:
  • Housing
    • Rapid or Transitional Housing
  • Parenting
    • PESP
  • Substance Abuse
    • Project Connect
• If none of the above, then referral to Collab
• When recommendations are returned, indicate if the family consents to the services.

Wishlist:

1. Data updated/edited during the interaction would be pushed back to FACES.
2. Flags for certain case data - history of participation/issues in programs, parent age <25 is ideal for PESP interventions.
3. Include enrollment capability into the programs from the app.

At the end of the hackathon, we presented our decision tree research, proposed mockup, and a prototype app. The next steps we documented in Github issues.

Volunteers who participated include: Laura, Kate, Ryan, Sam, Christine, Gabo, Terry, Catalina, Judy (DA), Michael (DA)

cfsa-referral's Issues

[Frontend] Update the favicon and title to be more DC themed

[Frontend] Search should be disabled when there has been no input

Create flags for the CFSA social worker.

When the FACES database is queried, the social worker should be signaled for certain historical information related to the case (young parent, etc.).

[Content] Create text to prompt social workers for each recommendation.

CFSA stakeholders would like to prompt social workers to pitch each recommended program and ask questions using motivational interviewing techniques to encourage program use. This is currently located in the google drive: https://docs.google.com/document/d/17e-RveFF5Az7GwV93Td7hy1G4m9iwIsRNgaV_BMnOWg/edit?usp=sharing

[Content] Create Spanish version

[Backend] Create fake profiles to populate "search by profile"

Profile data should include:

• Name
• Address/Ward
• Case Type
• Income
• Income sources
• Allegation (?)
• Social Worker Id
• Supervisor Id
• Case Id
• Referral Id
• Client Id
• Case Open Date
• Referral Date
• Primary Language

What's the status of the project?

Hey everyone,

I noticed this project back in October when I attended my first Code for DC meeting. I'm itching to get back into a Civic Tech project, and also do some React.

What's going on right now, and who should I get in contact with if I got any questions?

Best,
Geoffrey Yip

[Backend] Fake data should be populated after putting data in "search for profile page"

[Content] Verify Collaborative program referral rules

Figure out if handling of "collaborative" program logic is ok. At the moment there is no dependence on "ward" and assumes that any of the FrontYard, FrontPorch, and FrontDoor case states are valid case states for making a referral to the Collaborative program.

Update the decision tree based on CFSA input.

[Dev environment] Integrate Jest tests into build

Add jest suit for testing of the application

[Frontend] Each question should be its own route

Right now the url for all questions is /questions/923510, we should amend this by adding the question id to the url /questions/923510/1

First question should be "Is there a crisis"

• A "yes" answer should refer the user to MSS program
• A "no" answer should direct to the rest of the questions

[Dev environment] Just use yarn

Add instructions for using yarn. Remove references to npm.

[UX Design] Complete mockups of user flow

Complete mockups of user flow. Should probably be "mobile first" since case workers use tablets.

These have been started in this slide from the hackathon

[Backend] Call translations

[Frontend] Users should be able to see all answers so far

We don't really have a design for this :/

Save responses back into FACES

Once the social worker has completed the form, save the information back into the FACES database.

[Content] Review Questionnaire text to use inclusive language

Should the questionnaire use PARENT or CAREGIVER?

Connect to FACES.

FACES is the District of Columbia's state automated child welfare information system (SACWIS). We would like to allow CFSA social workers to pull this data to assist with recommendations and write new data there for long term outcome analysis.

Update/edit information pulled from FACES

When case activity is pulled, allow social worker to update/edit some information (income, ward, family members)

[Dev Environment] Add prettifier and linter

[Tech debt] Fix answer translation on final page

Final page "QualifiedPrograms"

Currently on master, questions and answers are not translated to their english counter parts:
https://github.com/codefordc/cfsa-referral/blob/master/app/src/QualifiedPrograms.js#L77-L78

https://github.com/codefordc/cfsa-referral/blob/abarciauskas-bgse_update-decision-tree/app/src/QualifiedPrograms.js#L78 fixes this but it's a brittle solution.

The acceptance criteria for this ticket is to come up with a less brittle solution to translating all answers to their english translation. This is complicated because we can't assume all answers will be true or false with the introduction of categorical answer types.

[UX Design] Visual design of interface

Mockup of what the layout, colors, buttons of the interface should be.

Some references, but just recommendations:

• http://rui.dc.gov/style-guide/
• https://standards.usa.gov/getting-started/ (design package)
• https://www.michiganbenefits.org/steps/introduce-yourself (similar data-entry type interface)

Refer to progress and mockups in #20

[Frontend] Implement UX design

See: https://projects.invisionapp.com/share/2AE4CENGY#/screens

I think max width of the content should be smaller, like 768px?

[Frontend] First page should "Login"

Implement login screen. Given this is a prototype, all non-empty login strings will be accepted.

Implement basic form as seen in the first screen below, no styling required:

[Dev Environment] Implement hot reloading of components and reducers

Reference:
https://github.com/BerndWessels/react-redux-rr4-wp2-rhl3/blob/master/src/root.client.js

[Backend Design] Pull profile information into qualified program decision logic

One of the questions for the Collaborative program is "Ward" and one of the questions for the housing programs is "Income". This information should be pulled from the profile information so the user doesn't have to answer the same question twice (or at all if this info is pulled from a database)

At the moment, profile information will be faked, so this information (Ward and Income) should just be pulled from the fake profiles.

This issue could be broken into 2: 1 for design and 1 for implementation if one person designs how this should work and implementation can be taken on later.

[Frontend] Page after login should be "Search for case"

Add a page with a search input.

Implement a basic version of the second screen:

Does not require styling.

[Dev environment] Tests for login page

Write tests for login page

[Frontend] There should be a back button when answer questions

Users should be able to navigate back to previous questions

[Frontend] Changing the language should cause the page to refresh

Additionally, the app should detect the browser language and load those translations

[Frontend] When no results are returned from search, there should be a helpful message and back button