Skip to content

Make "Follow-up requested" a sub-status of "Has a refusal"#6658

Open
murugapl wants to merge 3 commits intonextfrom
has-refusal-follow-up-requested
Open

Make "Follow-up requested" a sub-status of "Has a refusal"#6658
murugapl wants to merge 3 commits intonextfrom
has-refusal-follow-up-requested

Conversation

@murugapl
Copy link
Copy Markdown
Contributor

A parent who requests follow-up has actively declined the standard consent route, making it semantically closer to a refusal than an unanswered consent request. This moves needs_consent_follow_up_requested to has_refusal_follow_up_requested, so these patients appear under "Has a refusal" rather than "Needs consent".

Jira Issue - MAV-6744

Screenshots

Screenshot 2026-04-21 at 14 35 13

…requested

A parent can only request a follow-up discussion through a consent refusal. Hence, it makes sense for "follow-up requested" to be a substatus of "has a refusal" rather than "needs consent". This commit modifies the code to use has_a_refusal as the parent status. We retain needs_consent_follow_up_requested for now, and can remove it in a future commit when all patients have had their status updated appropriately.
With the post-deploy task all patients with needs_consent_follow_up_requested should be updated to has_a_refusal_follow_up_requested. This means we can hide the checkbox under needs consent till we remove the status altogether in a follow-up PR.
@murugapl murugapl added this to the v8.3.0 milestone Apr 21, 2026
@murugapl murugapl requested a review from a team as a code owner April 21, 2026 14:39
@murugapl murugapl added the feature New functionality label Apr 21, 2026
Comment thread db/data/20260421100000_update_follow_up_requested_programme_status.rb Outdated
The parent status should now be "Has a refusal" not "Needs consent"
@murugapl murugapl force-pushed the has-refusal-follow-up-requested branch from b5671ac to 3c37a44 Compare April 21, 2026 14:59
@murugapl murugapl modified the milestones: v8.3.0, v8.5.0 Apr 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

feature New functionality

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants