Fix flu triage when latest consent no longer allows injection#6740
Open
jhenderson wants to merge 1 commit intonextfrom
Open
Fix flu triage when latest consent no longer allows injection#6740jhenderson wants to merge 1 commit intonextfrom
jhenderson wants to merge 1 commit intonextfrom
Conversation
A flu patient could still be recorded as ready for injection after the same parent submitted a newer consent narrowing the route to nasal only. This happened when: - the parent first consented to nasal spray and injection - the patient was triaged as safe for injection only - the same parent later submitted a newer nasal-only consent The older safe-to-vaccinate triage was still treated as valid, so the patient remained due for injection and the record vaccination form was still shown. Update triage status generation so a safe-to-vaccinate triage only remains valid when the latest given consent still allows that vaccine method. If the latest consent no longer permits the triaged method, the patient returns to needs triage instead of due. Jira-Issue: MAV-2832
thomasleese
reviewed
May 5, 2026
Contributor
thomasleese
left a comment
thomasleese
left a comment
There was a problem hiding this comment.
With this approach the overall status changes to "Do not vaccinate" which makes sense (although I wonder if we would want the child to actually go back to "Needs triage"?), however, the triage object itself remains valid. I wonder if we need an approach where the triage itself becomes invalid (and therefore shows as such in the table of triage responses), which will then by virtue of being invalid reset the status of the child back to "Needs triage".
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A flu patient could still be recorded as ready for injection after the same parent submitted a newer consent narrowing the route to nasal only.
This happened when:
The older safe-to-vaccinate triage was still treated as valid, so the patient remained due for injection and the record vaccination form was still shown.
Update triage status generation so a safe-to-vaccinate triage only remains valid when the latest given consent still allows that vaccine method. If the latest consent no longer permits the triaged method, the patient returns to needs triage instead of due.
Jira Issue - MAV-2832