Is your feature request related to a problem? Please describe.
FamLink side considered adding a Telehealth checkbox, but ultimately did not. DCYF/Amber wants to know if we can add it to the Sprout UI for CANS-F instead so they have a means of tracking the prevalence of Telehealth use once it is an option, statewide, on 10/1/24.
Describe the solution you'd like
A control (drop down, buttons or check boxes) added to CANS-F in order to indicate that Telehealth was the means of service delivery for some, all, or none of the service provided.
Describe alternatives you've considered
See above for some history on alternatives or options considered.
Additional context
Notes from 6/18/24 discussion in weekly mtg: "They are talking about doing that in FamLink on the referral form, so this is a broader request (for maintenance). If not it may change the conversation. Sarah: if it is something that will be added to FamLink, Amber could certainly put in a request that we add something on the Sprout side, but remember there is no connection between Sprout and FamLink on the CANS side. So if Amber wants to track it in the data set that we have for CANS data in Sprout, we would need to add it in Sprout (a button). We could still add the button in Sprout even if it won't be in FamLink, we just would need to figure out where to put it in the UI of Sprout. Amber: thinks we should wait to hear back on the FamLink decision and then refer back to this. Amber wants to know if she could compare the data if we first put it in Sprout only (for provider to indicate the interaction was via Telehealth) and if DCYF workers were indicating it in FamLink with the addition of the button there, later on. Sarah: either way, if it is part of the FamLink referral or not, it sounds like it needs to be there either way in Sprout. Maybe on CSSAT side we could add this to our backlog to investigate what adding such a button would entail. We can just email Amber with our findings if that is OK. Justin will take this into a separate notes section and Amber will let us know."
8/23/24: Need to confirm where in CANS-F the control will be placed, what type of control (drop down currently favored), terminology to use within the control and how/whether to make it required. Amber getting feedback from Kamaile and will make decisions after discussion 8/27-9/3. See email from Justin on 8/23 and or mtg recording from 8/22. Also, Amber is planning to communicate the forthcoming Telehealth control at a statewide mtg. with providers on 9/11/24. Training for the new control may not be needed if the design is intuitive and or supported with appropriate help text/prompts for users.
Prioritization Process
[ X] Confirm the issue is a feature to which we want to devote resources.
[ X] Write user story in as a (role) I want (something) so that (benefit) format.
[ X] Label story Large, Uncertain, Small. If the story is too large, convert the story to a milestone/epic. SMALL
[ X] Label story as an active backlog issue (i.e. an issue on which we will be actively working).
[ X] Prioritize the story relative to other items in the active backlog.
[ ] Review progress/priorities in weekly collaboration meeting.
Is your feature request related to a problem? Please describe. FamLink side considered adding a Telehealth checkbox, but ultimately did not. DCYF/Amber wants to know if we can add it to the Sprout UI for CANS-F instead so they have a means of tracking the prevalence of Telehealth use once it is an option, statewide, on 10/1/24.
Describe the solution you'd like A control (drop down, buttons or check boxes) added to CANS-F in order to indicate that Telehealth was the means of service delivery for some, all, or none of the service provided.
Describe alternatives you've considered See above for some history on alternatives or options considered.
Additional context Notes from 6/18/24 discussion in weekly mtg: "They are talking about doing that in FamLink on the referral form, so this is a broader request (for maintenance). If not it may change the conversation. Sarah: if it is something that will be added to FamLink, Amber could certainly put in a request that we add something on the Sprout side, but remember there is no connection between Sprout and FamLink on the CANS side. So if Amber wants to track it in the data set that we have for CANS data in Sprout, we would need to add it in Sprout (a button). We could still add the button in Sprout even if it won't be in FamLink, we just would need to figure out where to put it in the UI of Sprout. Amber: thinks we should wait to hear back on the FamLink decision and then refer back to this. Amber wants to know if she could compare the data if we first put it in Sprout only (for provider to indicate the interaction was via Telehealth) and if DCYF workers were indicating it in FamLink with the addition of the button there, later on. Sarah: either way, if it is part of the FamLink referral or not, it sounds like it needs to be there either way in Sprout. Maybe on CSSAT side we could add this to our backlog to investigate what adding such a button would entail. We can just email Amber with our findings if that is OK. Justin will take this into a separate notes section and Amber will let us know."
8/23/24: Need to confirm where in CANS-F the control will be placed, what type of control (drop down currently favored), terminology to use within the control and how/whether to make it required. Amber getting feedback from Kamaile and will make decisions after discussion 8/27-9/3. See email from Justin on 8/23 and or mtg recording from 8/22. Also, Amber is planning to communicate the forthcoming Telehealth control at a statewide mtg. with providers on 9/11/24. Training for the new control may not be needed if the design is intuitive and or supported with appropriate help text/prompts for users.
Prioritization Process
[ X] Confirm the issue is a feature to which we want to devote resources.
[ X] Write user story in
as a (role) I want (something) so that (benefit)format.[ X] Label story Large, Uncertain, Small. If the story is too large, convert the story to a milestone/epic. SMALL
[ X] Label story as an active backlog issue (i.e. an issue on which we will be actively working).
[ X] Prioritize the story relative to other items in the active backlog.
[ ] Review progress/priorities in weekly collaboration meeting.