DEATH
Table Description
The death domain contains the clinical event for how and when a Person
dies. A person can have up to one record if the source system contains
evidence about the Death, such as: Condition in an administrative
claim, status of enrollment into a health plan, or explicit record in
EHR data.
CDM Field
|
User Guide
|
ETL Conventions
|
Datatype
|
Required
|
Primary Key
|
Foreign Key
|
FK Table
|
FK Domain
|
person_id
|
|
|
integer
|
Yes
|
No
|
Yes
|
PERSON
|
|
death_date
|
The date the person was deceased.
|
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.
|
date
|
Yes
|
No
|
No
|
|
|
death_datetime
|
|
If not available set time to midnight (00:00:00)
|
datetime
|
No
|
No
|
No
|
|
|
death_type_concept_id
|
This is the provenance of the death record, i.e., where it came
from. It is possible that an administrative claims database would
source death information from a government file so do not assume
the Death Type is the same as the Visit Type, etc.
|
Use the type concept that be reflects the source of the death
record. Accepted
Concepts. A more detailed explanation of each Type
Concept can be found on the vocabulary
wiki.
|
integer
|
No
|
No
|
Yes
|
CONCEPT
|
Type Concept
|
cause_concept_id
|
This is the Standard Concept representing the Person’s cause of
death, if available.
|
There is no specified domain for this concept, just choose the
Standard Concept Id that best represents the person’s cause of
death.
|
integer
|
No
|
No
|
Yes
|
CONCEPT
|
|
cause_source_value
|
|
If available, put the source code representing the cause of death
here.
|
varchar(50)
|
No
|
No
|
No
|
|
|
cause_source_concept_id
|
|
If the cause of death was coded using a Vocabulary present in the
OMOP Vocabularies put the CONCEPT_ID representing the cause of
death here.
|
integer
|
No
|
No
|
Yes
|
CONCEPT
|
|