ID

35000

Beskrivning

OMOP Common Data Model (CDM) Death As of OMOP CDM v6.0, the DEATH table has been deprecated in favor of storing the cause of death in the CONDITION_OCCURRENCE table, any observations relating to death stored in the OBSERVATION table, and a singular death date will be chosen and stored in the PERSON table. The 'Death' domain contains the clinical events surrounding how and when a Person dies. A Person can have information in the source system containing evidence about the Death, such as: Condition Code in the Header or Detail information of claims, Status of enrollment into a health plan, Explicit record in EHR data. The Observational Medical Outcomes Partnership (OMOP) was a public-private partnership established to inform the appropriate use of observational healthcare databases for studying the effects of medical products. © 2014 Observational Health Data Sciences and Informatics This work is based on work by the Observational Medical Outcomes Partnership (OMOP) and used under license from the FNIH at http://omop.fnih.org/publiclicense. Version updated on 06.02.2019, from https://github.com/OHDSI/CommonDataModel/wiki/DEATH. Living patients should not have a value in PERSON.DEATH_DATETIME, nor should they have any records relating to death either in the CONDITION_OCCURRENCE or OBSERVATION tables. Only one death date per individual can be used. If a patient has clinical activity (e.g. prescriptions filled, labs performed, etc) more than 60+ days after death you may want to drop the death record as it may have been falsely reported. If multiple records of death exist on multiple days you may select the death that you deem most reliable (e.g. death at discharge) or select the latest death date (THEMIS issue #6). If multiple death records occur, the date and the person have to be the same, but the cause can be different. Can be reported by different sources as well (THEMIS issue #5).If PERSON.DEATH_DATETIME cannot be precisely determined from the data, the best approximation should be used. Any cause of death should be stored in the CONDITION_OCCURRENCE table, using the CONDITION_TYPE vocabulary with the DEATH_TYPE concept class. All observations relating to death should be stored in the OBSERVATION table, including the concept 4306655. The DEATH_DATETIME in the PERSON table should not be used as the way to find all deaths: select * from PERSON where death_datetime is not null should not be the practice. Rather, deaths should be found through the OBSERVATION table and the PERSON table is only used to determine which death date should be used in analysis.

Länk

http://omop.fnih.org/publiclicense

Nyckelord

  1. 2017-01-04 2017-01-04 -
  2. 2019-02-07 2019-02-07 -
  3. 2019-02-28 2019-02-28 -
Rättsinnehavare

Observational Medical Outcomes Partnership (OMOP)

Uppladdad den

7 februari 2019

DOI

För en begäran logga in.

Licens

Creative Commons BY-NC 3.0

Modellkommentarer :

Här kan du kommentera modellen. Med hjälp av pratbubblor i Item-grupperna och Item kan du lägga in specifika kommentarer.

Itemgroup-kommentar för :

Item-kommentar för :

Du måste vara inloggad för att kunna ladda ner formulär. Var vänlig logga in eller registrera dig utan kostnad.

OMOP Common Data Model (CDM) Death

OMOP Common Data Model (CDM) Death

Death
Beskrivning

Death

Alias
UMLS CUI-1
C0011065
UMLS CUI-2
C1955348
Person ID
Beskrivning

A foreign key identifier to the deceased person. The demographic details of that person are stored in the person table.

Datatyp

integer

Alias
UMLS CUI [1]
C2348585
Death date
Beskrivning

The date the person was deceased. If the precise date including 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.

Datatyp

date

Alias
UMLS CUI [1,1]
C0011008
UMLS CUI [1,2]
C0011065
Death type concept ID
Beskrivning

A foreign key referring to the predefined concept identifier in the Standardized Vocabularies reflecting how the death was represented in the source data.

Datatyp

integer

Alias
UMLS CUI [1,1]
C0011065
UMLS CUI [1,2]
C0332307
UMLS CUI [1,3]
C0178566
UMLS CUI [1,4]
C1300638
Cause concept ID
Beskrivning

A foreign key referring to a standard concept identifier in the Standardized Vocabularies for conditions.

Datatyp

integer

Alias
UMLS CUI [1,1]
C0007465
UMLS CUI [1,2]
C0178566
UMLS CUI [1,3]
C1300638
Cause source value
Beskrivning

The source code for the cause of death as it appears in the source data. This code is mapped to a standard concept in the Standardized Vocabularies and the original code is, stored here for reference.

Datatyp

text

Alias
UMLS CUI [1,1]
C0007465
UMLS CUI [1,2]
C0449416
UMLS CUI [1,3]
C1522609
Cause source concept ID
Beskrivning

A foreign key to the concept that refers to the code used in the source. Note, this variable name is abbreviated to ensure it will be allowable across database platforms.

Datatyp

integer

Alias
UMLS CUI [1,1]
C0007465
UMLS CUI [1,2]
C0449416
UMLS CUI [1,3]
C0178566
UMLS CUI [1,4]
C1300638

Similar models

OMOP Common Data Model (CDM) Death

Name
Typ
Description | Question | Decode (Coded Value)
Datatyp
Alias
Item Group
Death
C0011065 (UMLS CUI-1)
C1955348 (UMLS CUI-2)
Person ID
Item
Person ID
integer
C2348585 (UMLS CUI [1])
Death date
Item
Death date
date
C0011008 (UMLS CUI [1,1])
C0011065 (UMLS CUI [1,2])
Death type concept ID
Item
Death type concept ID
integer
C0011065 (UMLS CUI [1,1])
C0332307 (UMLS CUI [1,2])
C0178566 (UMLS CUI [1,3])
C1300638 (UMLS CUI [1,4])
Cause concept ID
Item
Cause concept ID
integer
C0007465 (UMLS CUI [1,1])
C0178566 (UMLS CUI [1,2])
C1300638 (UMLS CUI [1,3])
Cause source value
Item
Cause source value
text
C0007465 (UMLS CUI [1,1])
C0449416 (UMLS CUI [1,2])
C1522609 (UMLS CUI [1,3])
Cause source concept ID
Item
Cause source concept ID
integer
C0007465 (UMLS CUI [1,1])
C0449416 (UMLS CUI [1,2])
C0178566 (UMLS CUI [1,3])
C1300638 (UMLS CUI [1,4])

Använd detta formulär för feedback, frågor och förslag på förbättringar.

Fält markerade med * är obligatoriska.

Do you need help on how to use the search function? Please watch the corresponding tutorial video for more details and learn how to use the search function most efficiently.

Watch Tutorial