Hazard Flagging as a Risk Mitigation Strategy for Violence against Paramedics
Bibliographic record
Abstract
Paramedics are increasingly being subjected to violence, creating the potential for significant physical and psychological harm. Where a patient has a history of violent behavior, hazard flags - applied either to the individual, their residential address, or phone number - can alert paramedics to the possibility of violence, potentially reducing the risk of injury. Leveraging a novel violence reporting process embedded in the electronic patient care record, we reviewed violence reports filed over a thirteen-month period since its inception in February 2021to assess the effectiveness of hazard flagging as a potential risk mitigation strategy. Upon reviewing a report, paramedic-supervisors can generate a hazard flag if recurrent violent behavior from the patient is anticipated. In all, 502 violence reports were filed, for which paramedic-supervisors generated hazard flags in 20% of cases (n=99). In general, cases were not flagged either because the incident occurred at a location not amenable to flagging, or because the supervisors felt that a hazard flag was not warranted based on the details in the report. Hazard flagging was associated with an increased risk of violence during subsequent paramedic attendance (Odds Ratio [OR] 6.21, p
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.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.010 | 0.037 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.001 |
| Bibliometrics | 0.002 | 0.001 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.001 | 0.002 |
| Open science | 0.001 | 0.002 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.003 | 0.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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".