You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
The text was updated successfully, but these errors were encountered: