Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Health Impact of Realistic Consumable Availability Scenarios #1367

Draft
wants to merge 54 commits into
base: master
Choose a base branch
from

Conversation

sakshimohan
Copy link
Collaborator

This PR estimates the health impact of increasing consumable availability to realistic levels. Realistic levels lie somewhere between default and all as predicted by the regression model or by assuming that all facilities perform as well as the facility at the nth percentile in terms of consumable availability.

Changes:

  1. Add scripts to prepare HHFA data and run regression analysis to determine factors associated with consumable availability
  2. Update ResourceFile_consumables_amatched.csv to include a crosswalk between names of consumables in the TLO model and that under HHFA
  3. Predict change in consumable availability under various scenarios
  4. Change healthsystem.py and consumables.py to accommodate specification of which consumable availability estimates to use
  5. Introduce a scenario which runs the model with a different set of availability estimates from the original estimates.

@sakshimohan sakshimohan self-assigned this May 22, 2024
sm2511 added 16 commits May 22, 2024 19:29
- some CMD and Reproductive health consumables were classified as "not relevant to regression analysis" and therefore assume not change to availability. This has been removed. We now assume that their availability changes in proportion to the average increase in the odds of availability across all consuamables.
- this equates the probability of availability to be equal to that of the 75th, 90th and 99th percentile facility (in terms of the mean vale of `available_prop` within the corresponding level; only availability of facilities in levels 1a and 1b are updated
- {'Facility_ID', 'month', 'item_code', 'available_prop'} only need to be a subset of all the columns because there may be additional scenario columns
- previously for each level of care, one best performing facility was chosen based on the average consumable availability across all item_codes; Now a different best performing facility is chosen for each level for each item_code, giving a greater improvement in available_prop
@sakshimohan
Copy link
Collaborator Author

Current consumable availability under various scenarios. All scenarios only affect levels 1a and 1b:

  1. Scenario 1: All items perform as well as consumables other than drugs/diagnostic tests
  2. Scenario 2: 1 + All items perform as well as consumables classified as 'Vital' in the Essential Medicines List
  3. Scenario 3: 2 + All facilities perform as well as those in which consumables stock is managed by pharmacists
  4. Scenario 4: 3 + Level 1a facilities perform as well as level 1b
  5. Scenario 5: 4 + All facilities perform as well as CHAM facilities
  6. Scenario 6: All facilities have the same probability of consumable availability as the 75th percentile best performing facility for each individual item
  7. Scenario 7: All facilities have the same probability of consumable availability as the 90th percentile best performing facility for each individual item
  8. Scenario 8: All facilities have the same probability of consumable availability as the 99th percentile best performing facility for each individual item

availability_by_level
availability_by_category

@sakshimohan
Copy link
Collaborator Author

Overall change in availability -
available_prop 0.49289695774871195
available_prop_scenario1 0.520910
available_prop_scenario2 0.523982
available_prop_scenario3 0.527928
available_prop_scenario4 0.529791
available_prop_scenario5 0.531345
available_prop_scenario6 0.513739
available_prop_scenario7 0.540825
available_prop_scenario8 0.575753

@tamuri tamuri added this to In progress in PR priorities Jun 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
PR priorities
In progress
Development

Successfully merging this pull request may close these issues.

None yet

1 participant