Is your feature request related to a problem? Please describe.
Providers are warned that a referral is nearing the resolve date starting at two weeks prior to the end date or 180 days from the start date. However, once the resolve date passes, it is difficult to know exactly when the referral was resolved.
Describe the solution you'd like
Add the resolve date (either the end date or the 180 day count date) to the grey notification bar so that it reads "resolved on yyyy-mm-dd"
Describe alternatives you've considered
Train users to click in the referral and look for the end date?
Additional context
Add any other context or screenshots about the feature request here.
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.
joemienko
commented
4 years ago
Is your feature request related to a problem? Please describe. Providers are warned that a referral is nearing the resolve date starting at two weeks prior to the end date or 180 days from the start date. However, once the resolve date passes, it is difficult to know exactly when the referral was resolved.
Describe the solution you'd like Add the resolve date (either the end date or the 180 day count date) to the grey notification bar so that it reads "resolved on yyyy-mm-dd"
Describe alternatives you've considered Train users to click in the referral and look for the end date?
Additional context Add any other context or screenshots about the feature request here.
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.