Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

In tobacco studies, subjects may report events (problems) or malfunctions with the device used to deliver the tobacco product, Often the true cause of the issue cannot be determined until a cause analysis is performed. The applicant decides when tobacco product device events and malfunctions are collected. If malfunction or product event results in an adverse event, then that information should be recorded in the AE domain using the appropriate device-related variables (e.g., AEACNDEV, AERLDEV).

The Tobacco Product Events and Malfunctions (EM)) domain is based on the Events General Observation class and is used to represent device issues and/or events. 

There is more than one approach to identifying tobacco product devices involved with these events/incidents. The method chosen will depend upon the granularity at which the applicant needs to track the tobacco product devices and will affect how the data are modeled. A tobacco product device can be identified as a single unit or its components can be separately identified. The level of granularity an applicant chooses will be influenced by whether the components will be replaced and/or tracked, and how tobacco product device/adverse event relationships and actions taken will be assessed.

Example

This is an example of a study where the applicant collected issues and events associated with the operation of the electronic cigarette product and any adverse events that a subject experienced as a result of the product issue or event.   

Include Page
CDASH Example.Tobacco Product Events or Malfunctions
CDASH Example.Tobacco Product Events or Malfunctions

Include Page
SDTM Example.Tobacco Product Events and Malfunctions
SDTM Example.Tobacco Product Events and Malfunctions

Pagenav