Resource allocation in public sector programmes: does the value of a life differ between governmental departments?
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.
Bibliographic record
Abstract
BACKGROUND: The value of a life is regularly monetised by government departments for informing resource allocation. Guidance documents indicate how economic evaluation should be conducted, often specifying precise values for different impacts. However, we find different values of life and health are used in analyses by departments within the same government despite commonality in desired outcomes. This creates potential inconsistencies in considering trade-offs within a broader public sector spending budget. We provide evidence to better inform the political process and to raise important issues in assessing the value of public expenditure across different sectors. METHODS: Our document analysis identifies thresholds, explicitly or implicitly, as observed in government-related publications in the following public sectors: health, social care, transport, and environment. We include both demand-side and supply-side thresholds, understood as societies' and governments' willingness to pay for health gains. We look at key countries that introduced formal economic evaluation processes early on and have impacted other countries' policy development: Australia, Canada, Japan, New Zealand, the Netherlands, and the United Kingdom. We also present a framework to consider how governments allocate resources across different public services. RESULTS: Our analysis supports that identifying and describing the Value of a Life from disparate public sector activities in a manner that facilitates comparison is theoretically meaningful. The optimal allocation of resources across sectors depends on the relative position of benefits across different attributes, weighted by the social value that society puts on them. The value of a Quality-Adjusted Life Year is generally used as a demand-side threshold by Departments of transport and environment. It exceeds those used in health, often by a large enough proportion to be a multiple thereof. Decisions made across departments are generally based on an unspecified rationing rule. CONCLUSIONS: Comparing government expenditure across different public sector departments, in terms of the value of each department outcome, is not only possible but also desirable. It is essential for an optimal resource allocation to identify the relevant social attributes and to quantify the value of these attributes for each department.
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 imitationNot 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.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.011 | 0.002 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.000 |
| Bibliometrics | 0.000 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 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 it