tblLTFU - Death and drop-out


All submitted participants should figure in the table. Participants who are NOT lost to follow and who have died, should be noted as DROP_Y=0

Holds data on death and drop-out

Core Fields

Note: Fields marked bold form the unique identifier for a record of the table.
Field name
Format
Description
PATIENT
character (or numeric if possible)
Code to identify patient (Cohort Patient ID)
DROP_Y

numeric:

  • 0 = No
  • 1 = Yes
Has the patient dropped out?
DROP_D
yyyy-mm-dd
If patient has dropped out, date of last visit
DROP_D_A
character: see coding of date precision
optional precision annotation for date of last visit
DROP_RS
numeric. see coding table for valid codings.
Reason for drop
DEATH_Y

numeric:

  • 0 = No
  • 1 = Yes
Has the patient died?
DEATH_D
yyyy-mm-dd
Date of Death
DEATH_D_A
character: see coding of date precision
optional precision annotation for date of death
SUD_DEATH_Y

numeric:

  • 0 = No
  • 1 = Yes
  • 9 = Unknown
Sudden Death?
EXP_DEATH_Y

numeric:

  • 0 = No
  • 1 = Yes
  • 9 = Unknown
Expected Death?
AUTOP_Y

numeric:

  • 0 = No
  • 1 = Yes
  • 9 = Unknown
Was an autopsy Performed?
DEATH_R1
character. see coding table for valid codings.
Cause of death
DEATH_RC1

character with codes:

  • I = Immediate cause
  • U = Underlying cause/condition
  • C = Contributing cause
  • N = Not available
Coding of causal relation of the code given in DEATH_R1 to the death
DEATH_R2
character. see coding table for valid codings.
Cause of death
DEATH_RC2

character with codes:

  • I = Immediate cause
  • U = Underlying cause/condition
  • C = Contributing cause
  • N = Not available
Coding of causal relation of the code given in DEATH_R2 to the death
DEATH_R3
character. see coding table for valid codings.
Cause of death
DEATH_RC3

character with codes:

  • I = Immediate cause
  • U = Underlying cause/condition
  • C = Contributing cause
  • N = Not available
Coding of causal relation of the code given in DEATH_R3 to the death
DEATH_SOURCE
character
Source of information for coding of death (e.g. CoDe within own cohort, CoDe from D:A:D, CoDe from ART-CC, etc.)
MOTHERDEATH_Y

numeric:

  • 0 = No
  • 1 = Yes
  • 9 = Unknown
Hast the patient's biological mother died?
MOTHERDEATH_D
yyyy-mm-dd
Date of death of the patient's biological mother
MOTHERDEATH_D_A
character: see coding of date precision
optional precision annotation for date of death of patient's mother
FATHERDEATH_Y

numeric:

  • 0 = No
  • 1 = Yes
  • 9 = Unknown
Hast the patient's biological father died?
FATHERDEATH_D
yyyy-mm-dd
Date of death of the patient's biological father
FATHERDEATH_D_A
character: see coding of date precision
optional precision annotation for date of death of patient's father

List of DEATH_R# and DEATH_RC# should be continued for as many reasons that are recorded.

The DEATH_RC# fields should enable cohorts to transfer data in accordance with the ​Coding of Death project (CoDe). You are welcome to contact the CoDe group for electronic sample forms for detailed collection of data used for the CoDe review process.

CoDe defines 1 immediate, 2 contributing and 1 underlying cause of death.

Additional Fields

Field name
Format
Description
ICD10_1
character
Cause of death as ICD-10 if available
ICD10_2
character
Cause of death as ICD-10 if available
ICD10_31
character
Cause of death as ICD-10 if available
ICD9_1?
character
Cause of death as ICD-9 if available
ICD9_2
character
Cause of death as ICD-9 if available
ICD9_31
character
Cause of death as ICD-9 if available
DEATH_OT
character
Reason for death – other - description
L_ALIVE_D
yyyy-mm-dd
Last date known to be alive
L_ALIVE_D_A
character: see coding of date precision
optional precision annotation for last date of Information / lknown to be alive

1: List of ICD10_# and ICD9_#inplace of or together with DEATH_R# and together DEATH_RC# and should be continued for as many reasons that are recorded.

CoDe defines 1 immediate, 2 contributing and 1 underlying cause of death.

QA Checks


TableCrosstableError CodeDescriptionStudy specificHICDEP?
AllTablesCrossTableATC001any date in database after DEATH_D in tblLTFU Yes
AllTablesCrossTableATC002any date in database after DROP_D in tblLTFU Yes
AllTablesCrossTableATC003any date in database before BIRTH_D in tblBAS Yes
AllTablesCrossTableATC004any date in database in the future Yes
AllTablesCrossTableATC005patients submitted previously who have been missed out Yes
AllTablesCrossTableATC006Any fields not coded as coding lists on table definition Yes
tblLTFUWithinTableLFW001DROP_Y and DEATH_Y both non-null Yes
tblLTFUWithinTableLFW002DEATH_Y and DROP_RS both non-null Yes
tblLTFUWithinTableLFW003Any of DEATH_Rx or DEATH_RCx non-null but DEATH_Y=0 Yes
tblLTFUWithinTableLFW004R2/RC2 non-null but R1/RC1 null Yes
tblLTFUWithinTableLFW005R3/RC3 non-null but R2/RC2 null Yes
tblLTFUWithinTableLFW006Duplicate patients Yes
tblLTFUWithinTableLFW007Missing DROP_Y Yes
tblLTFUWithinTableLFW008Missing DROP_D if DROP_Y=1 Yes
tblLTFUWithinTableLFW009Missing DROP_RS if DROP_Y=1 Yes
tblLTFUWithinTableLFW010Missing DEATH_Y Yes
tblLTFUWithinTableLFW011Missing DEATH_D if DEATH_Y=1 Yes
tblLTFUWithinTableLFW012DEATH_D non null but DEATH_Y=0 Yes
tblLTFUCrossTableLFC001Patient not found in tblBAS Yes
tblLTFUCrossTableLFC002patient in tblBAS hasn't got a record in tblLTFU Yes
tblLTFUCrossTableLFC003tblBAS has AIDS=0 but DEATHRx =8.1 Yes