Page History

PI
1. EM captures information about a variety of activities
that can occur to or with tobacco product devices
2. (e.g., malfunctions, calibrations,
or
3. parts replacement) that can occur to or with tobacco product devices. It is an optional domain, to be used only if the
sponsor
4. 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.
5. Events represented in the EM domain will be consistent with scientific and regulatory requirements. It is the applicant's responsibility to define an event and the appropriate collection period for events. This definition may vary based on product characterization and reporting of product safety. In consultation with regulatory authorities, applicants may extend or limit the scope of event collection. 
6. 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.
7. 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 AE domain specification and assumptions for more information). The relationship between the AE and PI can be recorded on the CRF using PISPID and/or PIAENO. PIAENO 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.
8. . See Section 2.8.10.1, Adverse Events (AE) for more information on how to represent subject adverse experiences. See also Section 2.8.5.2, Relating Subject Records and Datasets for more information on how to relate the records between EM and AE.
9. EMSTDTC
PIESTDTC
10. is the date/time of the device event.
PIEENDTC
11. EMENDTC (end date/time)
can
12.  can be used, for example, if a malfunction occurs during a deployment and it is repaired later.

Steal from DE assumptions below:

9. PIEENDTC can be used, for example, if a malfunction occurs during a deployment and it is repaired.

...

1. If this domain is used to capture device malfunctions

...

1. and a controlled terminology coding dictionary is used to code the event, then any codes beyond the

...

1. value shown in EMDECOD can be included as

...

11. Note that in some of the examples that follow, variables that would be blank may have been dropped to conserve space. This does not mean that the variables cannot be used in the illustrated use case, merely that in the particular example they were not populated.

...

1. non-standard variables.