tblCEP - Clinical Events and Procedures


holds type and date of clinical events and procedures including serious non-AIDS conditions. Former known as tblAE (adverse event).

Core Fields

Note: Fields marked bold form the unique identifier for a record of the table.
Field name
Format
Description
EVENT_ID
numeric
Unique Event Identifier (foreign key to the different event tables)
PATIENT
character (or numeric if possible)
Code to identify patient (Cohort Patient ID)
CEP_D
yyyy-mm-dd
date of event
CEP_ID
character. see coding table for valid codings.
identifies type of event
CEP_SPEC
character. see coding table for valid codings.
further specification
CEP_V
numeric. See coding table for interpretation.
Depending on CEP_ID and CEP_SPEC: value of given event
SRCDOC_Y

numeric:

  • 1 = Yes
  • 0 = No
whether the source documentation is available
SRCDOC_D
yyyy-mm-dd
date for source documentation verification
VERIFY_Y

numeric:

  • 1 = Yes
  • 0 = No
Has the monitor verified the source documentation?
VERIFY_D
yyyy-mm-dd
date for monitor verification
APPROV_Y

numeric:

  • 1 = Yes
  • 0 = No
final verification/approval
APPROV_D
yyyy-mm-dd
final verification date
APPROV_S
character
signature for final verification

Additional Fields

Field name
Format
Description
CEP_Y

numeric:

  • 1 = Yes
  • 0 = No
  • 9 = Unknown
has the patient had an event?
CEP_NAME
character
full name of the event
CEP_DESCRIP
character
full description of the event
CEP_R_Y

numeric:

  • 0 = not related
  • 1 = definitive
  • 2 = remote/unlikely
  • 3 = possible
  • 4 = probable
relation to treatment

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