The example below demonstrates the required data structure of one record per analyte per replicate per test condition per timepoint to accurately represent data from a stability study. The resulting structure would require 648 rows to illustrate the 12 analytes shown in the example study we received, done in triplicate under two test conditions at the number of timepoints in the example study.
For conciseness, we have abbreviated the examples below to demonstrate the concepts as follows:
First- we show all 12 analytes as a single replicate, at one time point and one test condition in order to illustrate the variables and terminology required to put together a stability study with assays done in replicate at different time points and varying test conditions, even though only one record per analyte is illustrated.
Second- We show ONE analyte (moisture) in triplicate, over a series of time points and two test conditions to give a sense of what the complete data would look like.
Hopefully users could combine the information shown in both examples to construct a complete dataset containing all the records for each analyte-replicate-test condition-time point group.
Tobacco domains
DI = TO for Tobacco Product Identifiers and Descriptors
SPDEVID = SPTOBID for Sponsor Tobacco Product Identifier
The example shown below is not an all inclusive comprehensive example. It is meant to be illustrative of the concepts.
Shelf life study has a protocol and provides the results of shelf life studies of Vapes products over time with different conditions and analytes. Generally there are many conditions with at least two with varying temperature, humidity, etc. The initial table shows the a number of the analytes and test conditions used in Shelf Life studies for Vapes products for one testing condition at one timepoint and one replicate.
Tobacco Product Testing (TT) is a Findings domain similar to the Laboratory Test Results domain.
PTCAS variable (in place of the LBLOINC variable) provides the accurate chemical name, structure for organic and inorganic substances.
Rows 1-12:
Shows several analytes (as noted in the PTTEST) in the E-Liquid substance for the condition noted in PTTSTCND which is E-Liquid Standard (Long Term) Condition.
Row 13:
Show microbials used in testing (aerobic plate count, mold, and yeast) using the PTTEST and PTTESTCD variable in the E-Liquid substance for the condition noted in PTTSTCND which is E-Liquid Standard (Long Term) Condition.
Row Captions Debug Message
Remember to keep number agreement between labels and captions.
A Shelf Life study dataset would shows analytes done in different test conditions with replicates over time points. In the interest of brevity for this example, only portions of the content using the TEST of Nicotine is shown in a sample of timepoints in two conditions with replicates. The weeks reflective of Week 1, Week 2, Week 3, etc. which would align with the PTTPTNUM of 2,3, etc. are not shown for visual viewing purposes. This is an example, this provides possible tests that might be used to demonstrate how to use the datasets and variables to show what was done for the shelf-life stability study. It shows what timepoint and what type of data follows. It is important to show different test conditions for each analyte. For aerosol a machine similutaion is use so mg/puff is valid.
Rows 1-9:
Show the PTTEST of Nicotine for E-Liquid Standard (Long Term) Condition which is shown in PTTSTCND. The sample of various timepoints that may be used in the testing for Nicotine is reflected in PTTPT. The PTTPTNUM shows the numerical version of the planned timepoint. The REPNUM shows the incidence number of a test that is repeated within a given timeframe for the same test.
Rows 10-19:
Show the PTTEST of Nicotine for E-Vapor Standard Aerosol Condition across the same timepoints. The PTGRPID is used to tie together a block of related records in a single domain.
Rows 20-27:
Show the PTTEST of Nicotine for E-Vapor Intense Aerosol Condition across the same timepoints. The PTGRPID is used to tie together a block of related records in a single domain.