-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deaths investigation - Create activity after death flag #862
Labels
Comments
Jennit07
added
On hold
Waiting for something / someone outside of our control
Mar23-update
labels
Jan 8, 2024
Jennit07
added
Priority: High
and removed
On hold
Waiting for something / someone outside of our control
labels
Jan 24, 2024
Confirmed at the SLF information session that this would be useful for analysts to have. I've changed the tag on this to high priority and removed the on hold label |
Please refer to the "Investigation into activity after death" report for detailed information about the issues found and methodology proposed for creating the activity after death flag. |
SwiftySalmon
added a commit
that referenced
this issue
May 27, 2024
Related to #862 WIP - Added function for get_all_slf_deaths_lookup_path which combines all financial years' extract. - Added function for add_activity_after_death_flag Following identification of activity recorded after death due to data quality or admin issues, an investigation into sources of death data available for SLFs was undertaken. This guided the addition of a new variable to flag records where activity occurred after the death of date. Further details about the issues and methodology can be found in the accompanying "Investigation into activity after death" report.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add a flag to episode and individual files that will flag if activity is after the death date.
There is sometimes activity recorded after death and this is due to various data quality or admin issues. The idea here is to add a flag so that analysts can decide for themselves if they want to remove these cases
The text was updated successfully, but these errors were encountered: