Skip to content

Conversation

thomasleese
Copy link
Contributor

The session of a vaccination record is used to determine the location where the vaccination took place. When recording an "already had" vaccination, we don't know where the vaccination took place so it doesn't make sense to store a location

@tvararu tvararu temporarily deployed to mavis-pr-3592 May 23, 2025 16:37 Inactive
@thomasleese thomasleese added the operations Improving live support label May 28, 2025
@thomasleese thomasleese force-pushed the dont-store-session-on-already-had branch from 9c0e098 to 1c148f5 Compare June 4, 2025 10:55
The session of a vaccination record is used to determine the location
where the vaccination took place. When recording an "already had"
vaccination, we don't know where the vaccination took place so it
doesn't make sense to store a location
@thomasleese thomasleese force-pushed the dont-store-session-on-already-had branch from 1c148f5 to 48c8390 Compare June 7, 2025 06:28
Copy link

sonarqubecloud bot commented Jun 7, 2025

@thomasleese
Copy link
Contributor Author

#3551 is a better alternative to this, we'll continue to associate the records with the session they were recorded in, but their location will be nil.

@thomasleese thomasleese closed this Jun 8, 2025
@thomasleese thomasleese deleted the dont-store-session-on-already-had branch June 8, 2025 06:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
operations Improving live support
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants