MétaCan
Menu
Back to cohort
Record W3143109072 · doi:10.1002/prs.12250

Hierarchy of controls in Contra Costa Health Services (<scp>CCHS</scp>) incident investigations

2021· article· en· W3143109072 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.
fundA Canadian funder is recorded on the work.

Bibliographic record

VenueProcess Safety Progress · 2021
Typearticle
Languageen
FieldDecision Sciences
TopicRisk and Safety Analysis
Canadian institutionsDalhousie University
FundersNatural Sciences and Engineering Research Council of Canada
KeywordsIncident reportProtocol (science)HierarchyWork (physics)Operations managementIncident managementSAFEREngineeringProcess managementComputer scienceEngineering managementComputer securityMedicinePolitical science

Abstract

fetched live from OpenAlex

Abstract Industrial safety ordinance (ISO), implemented in Contra Costa County in 1998, and in the city of Richmond in 2000, expands on the California accidental release program (CalARP) and requires the consideration of inherently safer design (ISD). Identifying ISD‐based corrective actions as part of incident investigations is an opportunity to consider ISD within the existing process safety management framework. The objectives of this work were to analyze corrective actions from ISO incident investigation reports with respect to the hierarchy of controls, to identify additional ISD‐based corrective actions for an incident using the ISD bow tie protocol, and to develop additional ISD example‐based guidance. Thirty incidents from 2001 to 2018 were analyzed, and 227 recommended corrective actions were documented and categorized according to the hierarchy of controls. An incident at the Tesoro Golden Eagle Refinery on September 15, 2004 was analyzed, and five additional ISD‐based corrective actions were identified. This work suggests that using the ISD bow tie protocol and example‐based guidance, in addition to ISD checklists and guidewords in incident investigations could help identify more ISD‐based corrective actions.

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.002
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: Observational
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.282
Threshold uncertainty score0.993

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0040.002
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0010.004
Science and technology studies0.0000.000
Scholarly communication0.0000.001
Open science0.0010.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.038
GPT teacher head0.371
Teacher spread0.333 · 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