Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
  1. PI 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. Records are specific to an individual device. 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 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.
  4. PIESTDTC is the date/time of the device event. PIEENDTC (end date/time) 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, and

...

  1. a controlled terminology

...

  1. coding dictionary is used to code the event, then any codes beyond the

...

  1. value shown in PITERM 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.