Page History
- EM captures information about a variety of activities (e.g., malfunctions, calibrations, parts replacement) that can occur to or with tobacco product devices. It is an optional domain, to be used only if the applicant 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. EM is not to be used for non-tobacco-product device events.
- USUBJID is Permissible in this domain, but should only be populated if the device event is associated with a subject's use of the product. See the CDISC Notes column in the specification for further explanation.
- If a malfunction or other event results in an adverse experience for a subject, then that information should be recorded in the AE domain (see Section 2.8.10.1, Adverse Events (AE), for more information). The relationship between AE and EM can be recorded on the CRF using EMSPID
and/or EMAENO. EMAENOJira showSummary false server Issue Tracker (JIRA) serverId 85506ce4-3cb3-3d91-85ee-f633aaaf4a45 key TOBA-557
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.Jira showSummary false server Issue Tracker (JIRA) serverId 85506ce4-3cb3-3d91-85ee-f633aaaf4a45 key TOBA-558 - EMSTDTC is the date/time of the device event. EMENDTC (end date/time)
can be used, for example, if a malfunction occurs during a deployment and it is repaired later.Jira showSummary false server Issue Tracker (JIRA) serverId 85506ce4-3cb3-3d91-85ee-f633aaaf4a45 key TOBA-99 - 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.
Overview
Content Tools