Versions Compared

Old Version 5

changes.mady.by.user Jon Neville

Saved on

compared with

New Version 6

changes.mady.by.user Kathleen Mellars

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
  1. EM captures information about a variety of activities that can occur to or with tobacco product devices (e.g., malfunctions, calibrations, or parts replacement). It is an optional domain, to be used only if the sponsor has events that should be reported, or that they otherwise want to track. Records are specific to an individual device (SPTOBID). The entries may or may not be related to a study subject.
  2. USUBJID is Permissible in this domain, but should be populated if the device event is associated with a subject. See CDISC Notes for further explanation.
  3. If a malfunction or other event results in an adverse experience
    Jira
    showSummaryfalse
    serverIssue Tracker (JIRA)
    serverId85506ce4-3cb3-3d91-85ee-f633aaaf4a45
    keyTOBA-37
    for a subject, then that information should be recorded in the AE domain (see AE domain specification and assumptions for more information). The relationship between the AE and EM can be recorded on the CRF using EMSPID and/or EMAENO. EMAENO is a CDASH data capture variable that is not submitted in SDTM-based datasets, but is used to create a RELREC that links the event records.
  4. EMESTDTC is the date/time of the device event. EMEENDTC (end date/time) can be used, for example, if a malfunction occurs during a deployment and it is repaired later.
  5. If this domain is used to capture device malfunctions, and a controlled terminology coding dictionary is used to code the event, then any codes beyond the value shown in EMDECOD can be included as non-standard variables.