MétaCan
Menu
Back to cohort
Record W2522936975 · doi:10.9778/cmajo.20150070

Introducing pharmacogenetic testing with clinical decision support into primary care: a feasibility study

2016· article· en· W2522936975 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.
venuePublished in a venue whose home country is Canada.

Bibliographic record

VenueCMAJ Open · 2016
Typearticle
Languageen
FieldPharmacology, Toxicology and Pharmaceutics
TopicPharmacogenetics and Drug Metabolism
Canadian institutionsUniversity of British Columbia
Fundersnot available
KeywordsClinical decision support systemMedicineGenotypingDecision support systemPharmacyPharmacogeneticsPharmacistPersonalized medicineClinical pharmacyFamily medicineGenotypeBioinformaticsData miningGenetics

Abstract

fetched live from OpenAlex

BACKGROUND: Inappropriate prescribing increases patient illness and death owing to adverse drug events. The inclusion of genetic information into primary care medication practices is one solution. Our aim was to assess the ability to obtain and genotype saliva samples and to determine the levels of use of a decision support tool that creates medication options adjusted for patient characteristics, drug-drug interactions and pharmacogenetics. METHODS: We conducted a cohort study in 6 primary care settings (5 family practices and 1 pharmacy), enrolling 191 adults with at least 1 of 10 common diseases. Saliva samples were obtained in the physician's office or pharmacy and sent to our laboratory, where DNA was extracted and genotyped and reports were generated. The reports were sent directly to the family physician/pharmacist and linked to an evidence-based prescribing decision support system. The primary outcome was ability to obtain and genotype samples. The secondary outcomes were yield and purity of DNA samples, ability to link results to decision support software and use of the decision support software. RESULTS: Genotyping resulted in linking of 189 patients (99%) with pharmacogenetic reports to the decision support program. A total of 96.8% of samples had at least 1 actionable genotype for medications included in the decision support system. The medication support system was used by the physicians and pharmacists 236 times over 3 months. INTERPRETATION: ClinicalTrials.gov, NCT02383290.

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.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.004
metaresearch head score (Gemma)0.001
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow), Insufficient payload (model declined to judge)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.538
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0040.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0000.000
Science and technology studies0.0010.000
Scholarly communication0.0000.000
Open science0.0020.001
Research integrity0.0000.001
Insufficient payload (model declined to judge)0.0010.000

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.

Opus teacher head0.212
GPT teacher head0.510
Teacher spread0.298 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it