Version 1 (modified by trac, 6 years ago) (diff)

copy from version 1.50

tblOVERLAP - Cross-cohort identification

holds information on the patient's participation in other cohorts

Core fields

Note: Fields marked bold form the unique identifier for a record of the table.

Field name




character (or numeric if possible)

Code to identify patient (Cohort Patient ID)



Code/name of the cohort



Unique patient identifier in other cohorts



Name of the cohort

Patients of an "original"-cohort who also participate in a "super"-cohort should be analysed within the "original"-cohort only. To suppress these patients from the datasets of the "super"-cohorts the identifier used in the "super"-cohort is needed. It is suggested that "original"-cohorts report id's from the "super"-cohorts, since the "super"-cohorts might not even know the other ID’s. Often this information is only available at centre level.

A record should be present for each cohort that the patient is participating in (apart from it's own "original"-cohort).

QA Checks

Table Crosstable Error Code Description Study specific HICDEP?
AllTablesCrossTableATC001any date in database after DEATH_D in tblLTFUYES
AllTablesCrossTableATC002any date in database after DROP_D in tblLTFUYES
AllTablesCrossTableATC003any date in database before BIRTH_D in tblBASYES
AllTablesCrossTableATC004any date in database in the futureYES
AllTablesCrossTableATC005patients submitted previously who have been missed outYES
AllTablesCrossTableATC006Any fields not coded as coding lists on table definitionYES
tblOVERLAPWithinTableOW001Invalid other cohortYES
tblOVERLAPCrossTableOC001PATIENT not found in tblBAS for that cohortYES
tblOVERLAPCrossTableOC002PAT_OTH not found in tblBAS for that overlapping cohortYES