MétaCan
Menu
Back to cohort

Resources and the Rule of Rescue<sup>1</sup>

2007· article· en· W2122233165 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.

aboutThe title or abstract carries a Canadian signal from the geographic lexicon.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueJournal of Applied Philosophy · 2007
Typearticle
Languageen
FieldHealth Professions
TopicEthics in medical practice
Canadian institutionsnot available
Fundersnot available
KeywordsPrima facieObligationContext (archaeology)Resource (disambiguation)Moral obligationLaw and economicsResource allocationBusinessEconomicsLawComputer sciencePolitical science

Abstract

fetched live from OpenAlex

abstract The central issue that I consider in this paper is the use of the so‐called ‘Rule of Rescue’ in the context of resource allocation. This ‘Rule’ has played an important role in resource allocation decisions in various parts of the world. It was invoked in Ontario to overturn a decision not to fund treatment for Gaucher's Disease and it has also been used to justify resource decisions in Israel concerning the same condition. In the paper I consider the nature of the Rule of Rescue and its moral justification. The latter involves consideration of the distinction between agent‐relative and agent‐neutral obligations. If the Rule of Rescue is to be justified, it is plausible to think that it will be in the context of agent‐relative obligations. Two problems with this suggestion are considered: the role of identifiability in the Rule of Rescue and the extent to which policy makers in a health care system can be taken to have such obligations. It is argued that in both cases these problems can be overcome and hence that there is a prima facie obligation to follow the Rule of Rescue.

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.003
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesResearch integrity
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: Theoretical or conceptual
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.554
Threshold uncertainty score0.997

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0210.003
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0010.001
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.005
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.054
GPT teacher head0.407
Teacher spread0.353 · 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