search

cssat / sprout-issues

An issue-only repository for the Sprout data collection platform
https://sproutservices.org
2 stars 1 forks source link

Multiple staffing patterns exist in 72 hour organizations #173

Closed joemienko closed 3 years ago

joemienko commented 3 years ago

Definitions

72 hour visit organization - A family time organization, one per region, with contractual responsibilities to complete initial visits within 72 hours of DCYF receiving custody of a child.

72 hour visit coordinator - A family time user, within a 72 hour visit organization, with org admin and region admin privileges. This user can view referrals, accept referrals, assign referrals, and approve visit reports. (All orgs appear to plan on having this role)

72 hour visit supervisor - A family time user, within a 72 hour visit organization, with basic user privileges. This user can view referrals, and submit visit reports.

Regular visit supervisor - A family time user, within a family time organization, with basic user privileges. This user can view referrals, and submit visit reports.

User Story 1

As a 72 hour visit coordinator, I should be able to assign referrals to 72 hour visit supervisors or regular visit supervisors working in my same agency, so that I can choose staffing patterns which best meet the needs of my organization.

Planned Solution 1

Ensure Sprout permissions allow 72 hour visit coordinator to assign to 72 hour visit supervisor or regular visit supervisor in organizations that are contracted with the 72 hour organization.

User Story 2

As a 72 hour visit coordinator in a network administrator region, I should be able to assign 72 hour referrals from my 72 hour queue to any organization with which I have a contract.

Planned Solution 2

Ensure that the 72 hour organizations for network administrator regions have contracts with all potential providers who will be responsible for conducting 72 hour visits.

See also #172 See also #174 See also #175

Working Implementation Timeline

  1. Plan for code-completion 2-weeks after receipt of XML prototype, ideally week of July 12. Requirement to start work - XML prototype(s) with new reference values. (see #172)
  2. Plan for feature acceptance by July 16. Requirement to for acceptance testing - Test 72 hour referral push to Sprout UAT
  3. Plan for provider training during week of July 19. Requirement for training - Feature acceptance, feature deployment, and training referrals sent to usertest
joemienko commented 3 years ago

Due to some issues with the way Sprout enables access to key features for 72-hour referrals (e.g. access to the "Timeline"), 72 hour visit organizations will be required to either do 72-hour work from within their 72 hour visit organization or from their regular organization.

IOW - If a 72 hour visit organization wants to assign 72 hour referrals to their regular organization, they will have to do so with all of the 72 hour referrals. If they want to manage their 72 hour referrals from the 72 hour visit organization, they will have to do so with all of the 72 hour referrals.

Current plan is to encourage all organizations (aside from the NA) to manage all 72 hour referrals from within their 72 hour organization.

joemienko commented 3 years ago

Contracts implemented for the new orgs referenced in #174. The caveat on the contracting nuances above to be communicated at provider training.