Bibliographic record
Abstract
INTRODUCTION: A drug screen is a frequent investigation in the emergency department. The purpose of ordering this test is to determine whether the patient's condition is due to a drug. The purpose of this review is to address the question - do you really need that emergency drug screen? BACKGROUND: A screening test is an investigation performed upon a defined population to identify subclinical disease. A diagnostic test confirms a specific disease in a particular patient who is at risk of that condition because of the medical history or physical examination. Diagnostic tests have optimal performance characteristics that differ from those of screening tests. Therefore, an optimal screening test cannot be an optimal diagnostic test. LITERATURE REVIEW: The relevant literature was identified through electronic search augmented by subsequent search of reference lists of the primarily identified publications. Articles not dealing with emergency qualitative urine drug screening of emergency department patients were not considered. RESULTS: There were seven retrospective case series describing 1,405 patients, one prospective case series of 196 patients, and one randomized trial of 117 patients. There were three retrospective case series describing 694 children. For patients presenting with psychiatric symptoms, there were two retrospective case series totaling 557 patients and one randomized trial of 392. There were three retrospective case series in 3,509 multiple trauma patients. There was no significant impact upon the management of these patients in the emergency department. CONCLUSION: The emergency drug screen is unlikely to impact significantly upon the management of the patient in the emergency department.
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.001 | 0.005 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.002 | 0.001 |
| Bibliometrics | 0.002 | 0.003 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.002 |
| Open science | 0.001 | 0.000 |
| Research integrity | 0.001 | 0.001 |
| 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".