The Costs of Scaling Up HIV Prevention for High Risk Groups: Lessons Learned from the Avahan Programme in India
Bibliographic record
Abstract
OBJECTIVE: The study objective is to measure, analyse costs of scaling up HIV prevention for high-risk groups in India, in order to assist the design of future HIV prevention programmes in South Asia and beyond. DESIGN: Prospective costing study. METHODS: This study is one of the most comprehensive studies of the costs of HIV prevention for high-risk groups to date in both its scope and size. HIV prevention included outreach, sexually transmitted infections (STI) services, condom provision, expertise enhancement, community mobilisation and enabling environment activities. Economic costs were collected from 138 non-government organisations (NGOs) in 64 districts, four state level lead implementing partners (SLPs), and the national programme level (Bill and Melinda Gates Foundation (BMGF)) office over four years using a top down costing approach, presented in US$ 2011. RESULTS: Mean total unit costs (2004-08) per person reached at least once a year and per monthly contact were US$ 235(56-1864) and US$ 82(12-969) respectively. 35% of the cost was incurred by NGOs, 30% at the state level SLP and 35% at the national programme level. The proportion of total costs by activity were 34% for expertise enhancement, 37% for programme management (including support and supervision), 22% for core HIV prevention activities (outreach and STI services) and 7% for community mobilisation and enabling environment activities. Total unit cost per person reached fell sharply as the programme expanded due to declining unit costs above the service level (from US$ 477 per person reached in 2004 to US$ 145 per person reached in 2008). At the service level also unit costs decreased slightly over time from US$ 68 to US$ 64 per person reached. CONCLUSIONS: Scaling up HIV prevention for high risk groups requires significant investment in expertise enhancement and programme administration. However, unit costs decreased with programme expansion in spite of an increase in the scope of activities.
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.003 | 0.013 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.001 |
| Bibliometrics | 0.001 | 0.002 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.003 | 0.002 |
| Open science | 0.002 | 0.002 |
| Research integrity | 0.001 | 0.002 |
| Insufficient payload (model declined to judge) | 0.002 | 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".