A Cluster-based, Spatial-sampling Method for Assessing Household Healthcare Utilization Patterns in Resource-limited Settings
Bibliographic record
Abstract
BACKGROUND: Implementation of population-based surveys is resource intensive and logistically demanding, especially in areas with rapidly changing demographics and incomplete or no enumeration of the underlying population and their residences. To remove the need for pre-enumeration and to simplify field logistics for the population healthcare utilization survey used for the Surveillance for Enteric Fever in Asia Project in Nepal, we incorporated a geographic information system-based geosurvey and field mapping system into a single-stage cluster sampling approach. METHODS: A survey was administered to ascertain healthcare-seeking behavior in individuals with recent suspected enteric fever. Catchment areas were based on residential addresses of enteric fever patients using study facilities; clusters were randomly selected from digitally created grids using available satellite images and all households within clusters were offered enrollment. A tablet-compatible geosurvey and mapping system that allowed for data-syncing and use in areas without cellular data was created using the ArcGIS suite of software. RESULTS: Between January 2017 and November 2018, we surveyed 25 521 households in Nepal (16 769 in urban Kathmandu and 8752 in periurban Kavrepalanchok), representing 84 202 individuals. Overall, the survey participation rate was 90.9%, with geographic heterogeneity in participation rates within each catchment area. Areas with higher average household wealth had lower participation rates. CONCLUSION: A geographic information system-based geosurvey and field mapping system allowed creation of a virtual household map at the same time as survey administration, enabling a single-stage cluster sampling method to assess healthcare utilization in Nepal for the Surveillance for Enteric Fever in Asia Project . This system removed the need for pre-enumeration of households in sampling areas, simplified logistics and could be replicated in future community surveys.
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.027 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.006 | 0.007 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.002 | 0.002 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.004 | 0.001 |
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".