MétaCan
Menu
Back to cohort
Record W1977960312 · doi:10.12927/hcq.2012.22842

Medication Reconciliation in the Hospital: What, Why, Where, When, Who and How?

2012· review· en· W1977960312 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.

Bibliographic record

VenueHealthcare Quarterly · 2012
Typereview
Languageen
FieldMedicine
TopicPharmaceutical Practices and Patient Outcomes
Canadian institutionsUniversity of TorontoUniversity Health Network
Fundersnot available
KeywordsHarmObligationProcess (computing)Health careTask (project management)Patient safetyMedication ReconciliationMedicinePsychologyNursingMedical emergencyComputer sciencePolitical scienceSocial psychologyLaw

Abstract

fetched live from OpenAlex

Medication reconciliation arose as the solution to the well-documented patient safety problem of unintentionally introducing changes in patients' medication regimens due to incomplete or inaccurate medication information at transitions in care. Unfortunately, medication reconciliation has often been misperceived as a superficial administrative accounting task with a "pre-occupation with completing forms," resulting in the implementation of ineffective processes. In this article, the authors briefly review the evidence supporting medication reconciliation but focus more on key practical questions regarding the elements of an effective medication reconciliation process: what it should consist of, where and when it should occur, who should carry it out and how hospitals should implement it. The authors take the why of medication reconciliation to consist not just of the professional obligation to avoid causing harm, but also of a rational self-interest on the part of healthcare leaders. The authors argue that, rather than wasting time implementing a nominal reconciliation process, we should invest time and energy in a more robust and effective strategy, and they address specific practical questions that arise in such an effort.

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.001
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Review · Consensus signal: Review
Teacher disagreement score0.982
Threshold uncertainty score0.853

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.001
Open science0.0000.000
Research integrity0.0000.001
Insufficient payload (model declined to judge)0.0000.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.205
GPT teacher head0.447
Teacher spread0.242 · 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