MétaCan
Menu
Back to cohort
Record W2131227505 · doi:10.1002/asi.20228

Information behavior in the context of improving patient safety

2005· article· en· W2131227505 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.
aboutThe title or abstract carries a Canadian signal from the geographic lexicon.

Bibliographic record

VenueJournal of the American Society for Information Science and Technology · 2005
Typearticle
Languageen
FieldHealth Professions
TopicOccupational Health and Safety Research
Canadian institutionsUniversity of Toronto
Fundersnot available
KeywordsPatient safetyChampionKnowledge managementContext (archaeology)Health careNursingCoping (psychology)PsychologyMedicineComputer science

Abstract

fetched live from OpenAlex

Abstract Although it is assumed that information about patient safety and adverse events will be used for improvement and organizational learning, we know little about how this actually happens in patient care settings. This study examines how organizational and professional practices and beliefs related to patient safety influence (1) how health care providers and managers make sense of patient safety risks and adverse events, and (2) the flow and use of information for making improvements. The research is based on an ethnographic case study of a medical unit in a large tertiary care hospital in Canada. The study found that front‐line staff are task driven, coping with heavy workloads that limit their attention to and recognition of potential information needs and knowledge gaps. However, a surrogate in an information‐related role—an “information/change agent”—may intervene successfully with staff and engage in preventive maintenance and repair of routines. The article discusses four key functions of the information/change agent (i.e., boundary spanner, information seeker, knowledge translator, and change champion) in the context of situated practice and learning. All four functions are important for facilitating changes to practice, routines, and the work environment to improve patient safety.

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.003
metaresearch head score (Gemma)0.001
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Other design · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.954
Threshold uncertainty score0.508

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0030.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.002
Science and technology studies0.0010.001
Scholarly communication0.0000.002
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.031
GPT teacher head0.409
Teacher spread0.377 · 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