Lab Result Data Analysis
There are some anomalies with the LeafData reporting for Lab Results for cannabis in Washington State. Here we will highlight some of the assertions made by the LCB and some observations from the data. This has been previously discussed [/blog/2020/124-lab-result-restrictions](Lab Result Data Restrictions)
- All Products must have a Lab Result, according to Washington State law.
- The technology platform enforces this.
- Material can be sold with proper lab results.
- Material can be sold with un-tracked WAATTESTED type results.
- No New ATTESTED materials should appear (since July 2019)
Preparing the Sample Data
The data we are using is from the public records of Washington. Data sample is Inventory Lots at retail-type licenses from 2019-10-01 though 2020-04-05, 4670789 rows.
There were 212702 (4.55%) that were missing lab result information. There are 1327978 (28.43%) of what we labled AT4, that is ATTESTED materials that are part of this massive set of ATTESTED that occurred in July 2019. There are 252383 (5.40%) of what we've labeled AT5, that is ATTESTED materials that have been created after July 2019 (LCB asserts this should not exist). There are 2877726 (61.61%) records that are proper lab results.
Before July 2019
Missing: 86676 (5.1%); AT4: 183772 (10%); AT5: 48870 (2.8%); LR1: 1380958 (81%)
Normal error rate for missing, a larger portion of AT4 type lab results. These are simply lab results being back-ported onto materials that existed during the July 2019 migration.
Usage of AT5 Type Lab Results
Here's what the usage of AT5 type Lab Results look like over time.
The time stamp is taken from when the lot was marked as created_at.
https://data.openthc.org/lab/attested
What we can see from this data is that once the AT4 option was introduced it's been in heavy usage.
Assertion: No New Attested
Assertion was made by LCB that after July 2019 no new WAATTESTE values would appear. There are 252383 records, using WAATTESTE values that are not found in the lab_result table, like all the AT4s are. This is un-expected and creates a situation where the system is unable to report on testing.