Point-of-care community drug checking technologies: an insider look at the scientific principles and practical considerations
Bibliographic record
Abstract
Drug checking is increasingly being explored outside of festivals and events to be an ongoing service within communities, frequently integrated within responses to illicit drug overdose. The choice of instrumentation is a common question, and the demands on these chemical analytical instruments can be challenging as illicit substances may be more complex and include highly potent ingredients at trace levels. The answer remains nuanced as the instruments themselves are not directly comparable nor are the local demands on the service, meaning implementation factors heavily influence the assessment and effectiveness of instruments. In this perspective, we provide a technical but accessible introduction to the background of a few common drug checking methods aimed at current and potential drug checking service providers. We discuss the following tools that have been used as part of the Vancouver Island Drug Checking Project in Victoria, Canada: immunoassay test strips, attenuated total reflection IR-absorption spectroscopy, Raman spectroscopy from powder samples, surface-enhanced Raman scattering in a solution of colloidal gold nanoparticles, and gas chromatography-mass spectrometry. Using four different drug mixtures received and tested at the service, we illustrate the strengths, limitations, and capabilities of such instruments, and expose the scientific theory to give further insight into their analytical results. Each case study provides a walk-through-style analysis for a practical comparison between data from several different instruments acquired on the same sample. Ideally, a single instrument would be able to achieve all of the objectives of drug checking. However, there is no clear instrument that ticks every box; low cost, portable, rapid, easy-to-use and provides highly sensitive identification and accurate quantification. Multi-instrument approaches to drug checking may be required to effectively respond to increasingly complex and highly potent substances demanding trace level detection and the potential for quantification.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.040 | 0.035 |
| Meta-epidemiology (narrow) | 0.002 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.004 | 0.002 |
| Science and technology studies | 0.004 | 0.012 |
| Scholarly communication | 0.016 | 0.016 |
| Open science | 0.005 | 0.006 |
| Research integrity | 0.009 | 0.008 |
| Insufficient payload (model declined to judge) | 0.005 | 0.002 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".