-
Notifications
You must be signed in to change notification settings - Fork 8
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
How to populate death_date when source does not provide #100
Comments
Hi @assimilateDave I opened this as a Themis issue so I could comment. The note about the removal of the death table in v6.0 relates to multiple causes of death and not necessarily what to do when death date is not provided in the data. Anything in v6.0 by definition will not be retained in the v5 series as many of them were breaking changes. Have you found a suggestion for how to populate death_date if it is not given in the source? |
Suggestions for "writing" an estimated death date include:
|
Thanks @assimilateDave for working on this one! I would suggest we not include the fictitious future date as this has implications for the observation period and is almost the same as having a null. There would be no way to use such a date. Similarly, the flag option was brought up in the past but the OMOP CDM specifically typically doesn't include flags but instead relies on the records themselves to indicate that something happened to the person. In this way the dates are critical because wthout a date there is no way to temporally associate the death with any other events. In this case I would use the first and fourth bullets you have as the methods for answering this question |
I am unable to edit the original document content and would like to replace the "Summary of answer" with the following:
|
Thanks @assimilateDave ! I updated it, I opened the issue so I guess it didn't give you edit rights |
Issue # and locationForum discussion Issue summaryIn order to insert a record in the death table, the death_date must be populated. However, some data sources only contain a death flag. In this case, what should the ETL do when there is not a date at the source, but there is a flag indicating the person is deceased? Convention typeTable CDM tableDeath CDM fieldNA Links to issue discussionProvenance of dataAll The ratified conventionIf your source data do not have a method to properly identify a realistic death_date, then do not create a record in the Death table. If you think you have a robust method to do the imputation, and you checked that against the data where you do have the death date, you use it. One method of imputation uses the date of the last Patient-Provider interaction. Date of ratification/publishedJanuary 29, 2022 Downstream implicationsNo Link to DQD checkRelated conventions/further informationNA #Tags |
When the person's death_date is not provided but the patient is deceased
CDM or THEMIS convention?
Themis convention as it is not applicable to all and the CDM covers incomplete death_date and death_datetime data.
https://ohdsi.github.io/CommonDataModel/cdm54.html#death
Is this a general convention?
No
Summary of issues
Summary of answer
Recording the last known Provider-Person interaction based on other clinical entries. https://forums.ohdsi.org/t/what-to-do-with-null-death-dates-in-omop/4241/19
The most obvious recommendation is to not use the death_date if your ETL source data does not have a method to properly insert death_date with the accuracy expected. Not a fix, but the best recommendation I can find. https://forums.ohdsi.org/t/what-to-do-with-null-death-dates-in-omop/4241/41
Related links
https://forums.ohdsi.org/t/what-to-do-with-null-death-dates-in-omop/4241
OHDSI/CommonDataModel#210
https://ohdsi.github.io/CommonDataModel/cdm54.html#death
Other comments/notes
The text was updated successfully, but these errors were encountered: