MétaCan
Menu
Back to cohort
Record W2116818131 · doi:10.1136/bmjqs-2014-003279

Fix and forget or fix and report: a qualitative study of tensions at the front line of incident reporting

2015· article· en· W2116818131 on OpenAlex
Tanya Hewitt, Samia Chreim

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.
fundA Canadian funder is recorded on the work.
aboutThe title or abstract carries a Canadian signal from the geographic lexicon.

Bibliographic record

VenueBMJ Quality & Safety · 2015
Typearticle
Languageen
FieldHealth Professions
TopicPatient Safety and Medication Errors
Canadian institutionsUniversity of Ottawa
FundersUniversity of Ottawa
KeywordsPatient safetyHarmThematic analysisHealth careForgettingMedicineQualitative researchSafety cultureNear missNursingMedical emergencyPsychologySocial psychologyManagementEngineeringSociologyForensic engineering

Abstract

fetched live from OpenAlex

INTRODUCTION: Practitioners frequently encounter safety problems that they themselves can resolve on the spot. We ask: when faced with such a problem, do practitioners fix it in the moment and forget about it, or do they fix it in the moment and report it? We consider factors underlying these two approaches. METHODS: We used a qualitative case study design employing in-depth interviews with 40 healthcare practitioners in a tertiary care hospital in Ontario, Canada. We conducted a thematic analysis, and compared the findings with the literature. RESULTS: 'Fixing and forgetting' was the main choice that most practitioners made in situations where they faced problems that they themselves could resolve. These situations included (A) handling near misses, which were seen as unworthy of reporting since they did not result in actual harm to the patient, (B) prioritising solving individual patients' safety problems, which were viewed as unique or one-time events and (C) encountering re-occurring safety problems, which were framed as inevitable, routine events. In only a few instances was 'fixing and reporting' mentioned as a way that the providers dealt with problems that they could resolve. CONCLUSIONS: We found that generally healthcare providers do not prioritise reporting if a safety problem is fixed. We argue that fixing and forgetting patient safety problems encountered may not serve patient safety as well as fixing and reporting. The latter approach aligns with recent calls for patient safety to be more preventive. We consider implications for practice.

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.021
metaresearch head score (Gemma)0.035
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMetaresearch
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Qualitative · Consensus signal: Qualitative
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.117
Threshold uncertainty score0.973

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0210.035
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.0000.000
Research integrity0.0000.000
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.454
GPT teacher head0.598
Teacher spread0.144 · 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