You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The use of Xpert consumable (item_code 187) is currently logged as 0 across all scenarios generated by job_id htm_and_hss_runs-2025-01-16T135243Z comparing horizontal versus vertical investments.
The tb module seems to request the use of Xpert correctly because it is logged as Not_Available under tlo.methods.healthsystem.summary, and the quantity not available correctly increases under TB scale up scenarios.
Xpert is delivered at level 2 facilities, with an average consumable availability recorded at 31%. The availability is 0% at level 1b facilities. The healthsystems.py module takes the average availability across levels 1b and level 2 (by district and month), so this is likely to bring the average availability down for the merged level 1b and 2 facilities used in the simulation, but not down to 0. So it's not clear what's happening here.
Additionally, there are major challenges with the disaggregated estimates of availability by month. For all districts, for 7 months, the availability recorded is close to 0 as per LMIS data. This is probably an artefact of OpenLMIS errors and needs to be corrected. See attached the availability at level 2 facilities by District (rows) and month (columns).
The text was updated successfully, but these errors were encountered:
The use of
Xpert
consumable (item_code 187
) is currently logged as 0 across all scenarios generated by job_idhtm_and_hss_runs-2025-01-16T135243Z
comparing horizontal versus vertical investments.The
tb
module seems to request the use ofXpert
correctly because it is logged asNot_Available
undertlo.methods.healthsystem.summary
, and the quantity not available correctly increases under TB scale up scenarios.Xpert is delivered at level 2 facilities, with an average consumable availability recorded at 31%. The availability is 0% at level 1b facilities. The
healthsystems.py
module takes the average availability across levels 1b and level 2 (by district and month), so this is likely to bring the average availability down for the merged level 1b and 2 facilities used in the simulation, but not down to 0. So it's not clear what's happening here.Additionally, there are major challenges with the disaggregated estimates of availability by month. For all districts, for 7 months, the availability recorded is close to 0 as per LMIS data. This is probably an artefact of OpenLMIS errors and needs to be corrected. See attached the availability at level 2 facilities by District (rows) and month (columns).
The text was updated successfully, but these errors were encountered: