As a CANS-F user, I need clearer indications in the UI of the completion status of an assessment

[tinhart]

Is your feature request related to a problem? Please describe.
A problem, for many providers using the Sprout CANS-F application is that it isn't very clear what the status of an assessment is. Some revisions to the UI could help explain controls, indicate state of completion, and or provide more intuitive workflow for users.

Describe the solution you'd like
One or more of the following were shared with us by provider contacts at Haven and IFD:

• Help text, labels or other instructions in the interface could better explain what the controls mean, or do, and what the status of an assessment currently is. hey might also explain more about how the CANS-F app works (for example how auto save works or what clicking “Mark Complete” does/when to click it).

• A counter displaying the number of ratings left to complete or a % done could be helpful. But note that referrals don’t always go forward; a counter should not prohibit providers from only completing the exit portion of an assessment or prevent submitting an assessment.

• if the menu from Plans for Change that lists everything that has scored a 3 were similarly available in other tabs/screens used in an intervention (to avoid clicking back and forth to refer to or make sure they have covered other targeted areas), that would be helpful.

• The yellow timeout warning message is displayed too briefly (easy to miss and then get logged out). It if appeared for an extra 15-30 seconds that would help.

Describe alternatives you've considered
Trainings covering how to use Sprout CANS-F features and who can see/do what in it (if shared w/ everyone) and how to make sure an assessment is complete, what to do/where to put things etc. would be especially useful. Note that trainings were not advocated by Delton at DCYF (because of time involved to create them and due to potential changes/need for strategic planning, longer term).

Additional context
Approximately 34% of providers were below the ideal 75% submission rate for their assessments.

Prioritization Process

• Confirm the issue is a feature to which we want to devote resources.

• Write user story in as a (role) I want (something) so that (benefit) format.

• Label story Large, Uncertain, Small. If the story is too large, convert the story to a milestone/epic.

• Label story as an active backlog issue (i.e. an issue on which we will be actively working).

• Prioritize the story relative to other items in the active backlog.

• Review progress/priorities in weekly collaboration meeting.