It doesn’t work because those without direct access to your data will create queries without the knowledge you put death into the future. This is especially troublesome if you have a high percentage of dead Persons lacking a death date in your database. In the following hypothetical study, you will add a lot of false data and skew your results heavily by using 2099.
- A Person who was diagnosed with X in 2015 and is now dead (per your source data) will have a longevity of 84 years from date of diagnosis. Not good. They died between 2015 and the date of your data pull.
For your use case, which is specific to the All of Us project, then I suggest
And make it apparent in your ETL specifications and in your end user documentation. The date of death would be the date the data was recorded or date of data pull.
Or lobby hard for the death flag