Skip to content
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

Document date fields that are known to contain bad dates #1672

Open
rebkwok opened this issue Oct 20, 2023 · 0 comments
Open

Document date fields that are known to contain bad dates #1672

rebkwok opened this issue Oct 20, 2023 · 0 comments
Milestone

Comments

@rebkwok
Copy link
Contributor

rebkwok commented Oct 20, 2023

Several date fields in TPP can contain either ceiling dates (which we're mostly replacing with nulls), or impossible dates. In some cases these look like they may represent a default value (1900-01-01 or 1901-01-01). In other cases, they are somewhat random "bad" dates, that are clearly impossible and are probably data entry errors. We should consider documenting these to ensure users are aware that they may need to use boundary dates to exclude bad data.

See #1523 for details.

Applies to fields in tables:
APCS
CPNS
EC
ISARIC_New
OPA
WL_ClockStops
WL_Diagnostics
WL_OpenPathways
Appointment
Consultation
MedicationIssue
RegistrationHistory
VaccinationDate

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

2 participants