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
Day, month, and year are expected in the death_date field.
Some source data may not have complete datestamp of the deceased persons death date. An approximation of that date should be used.
This issue was discussed thoroughly and ratified and could be documented as a Themis convention instead of in the CDM since it may not be applicable to all use cases and data sources.
Summary of answer
If the precise date include day or month is not known or not allowed, December is used as the default month, and the last day of the month the default day.
I could not find a directly related issue discussing the use of December and last day of month as defaults in the forums or issues. However it is in the CDM doc as stated and is in an issue/proposal supporting the change to death_datetime in CDM v6 Store death causes in condition_occurrence table CommonDataModel#210
The text was updated successfully, but these errors were encountered:
The death.death_date field has day resolution. Some source data may not have complete datestamp of the deceased persons death date. An approximation of that date should be used.
If the precise date include day or month is not known or not allowed, December is used as the default month, and the last day of the month the default day.
#Populating the month and/or year in death_date when this is not known or provided in source data
CDM or THEMIS convention?
THEMIS Issue - currently documented in the CDM webpage
https://ohdsi.github.io/CommonDataModel/cdm54.html#death
Table or Field level?
Field level
Is this a general convention?
No
Summary of issues
Summary of answer
Related links
Other comments/notes
The text was updated successfully, but these errors were encountered: