-
Notifications
You must be signed in to change notification settings - Fork 7
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
equipment: integration into modules #1124
Conversation
901419c
to
dbe3043
Compare
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
358f787
to
48b8d6f
Compare
This comment was marked as resolved.
This comment was marked as resolved.
ed64e6a
to
ebe0b6a
Compare
This comment was marked as resolved.
This comment was marked as resolved.
48b8d6f
to
c486fea
Compare
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
c2a84de
to
3ba42c7
Compare
This comment was marked as outdated.
This comment was marked as outdated.
76b9bd6
to
f1aa86c
Compare
…oscope, PSA test added manually
Hi @sakshimohan, because we haven't updated the generate_consumables_item_codes_and_packages script yet, as we planned to do when we find time to do so (see issue #1274), and since you've now added the consumables using this script, it overwrote back the changes done manually, which we don't want to happen. I did revert the changes in the @joehcollins, could you now add these as consumables whenever you wanted to add those? |
…ration_in_modules # Conflicts: # resources/healthsystem/consumables/ResourceFile_Consumables_availability_small.csv # resources/healthsystem/infrastructure_and_equipment/ResourceFile_Equipment.csv # src/scripts/healthsystem/equipment/equipment_catalogue.py # src/tlo/methods/alri.py # src/tlo/methods/breast_cancer.py # src/tlo/methods/care_of_women_during_pregnancy.py # src/tlo/methods/contraception.py # src/tlo/methods/healthsystem.py # src/tlo/methods/labour.py # src/tlo/methods/newborn_outcomes.py
|
Hi @joehcollins @EvaJanouskova, naive question about how this PR deals with module parameters which already embed assumptions about equipment availability. To give a concrete example: the probability that a woman receives blood pressure measurement during an ANC appt is based on observed data, and hence already includes assumptions about equipment availability. If we wanted to self-consistently capture the effect of equipment availability, this probability should therefore increase (and if so, by how much?) if equipment is established as being present for the appt. Is this (or a similar logic) already included in the PR? |
Hi @marghe-molaro - at present equipment availability wont effect individual interventions within a HSI but rather will determine if an entire HSI will run (only if the module has determined such a piece of equipment exists that would prevent the entire appointment from running). I dont believe availability will be probabilistic for each HSI either, it either is or isnt available in a binary sense. I get what you mean for certain in-module parameters that i have in the ANC module. Previously ive tried to adjust these so that they account for the average consumable availability for a given intervention to lead to intervention coverage from the observed data - if that makes sense. |
Thanks for the clarification @joehcollins,
|
@marghe-molaro - i suppose with your BP check example that assumes the probability represents the total probability of intervention delivery. In my modules it often represents the probability the intervention will be delivered because the HCW knows they should deliver the intervention i.e. clinical competence. So p(intervention_delivered) = p(consumables) * p(competence) |
Agree we should maybe think more on this model wide though... |
Agreed, only reason I brought up ANC is that I knew at least of this specific example and was wondering if you were already addressing this. As you say this is likely affecting a lot more modules, so @EvaJanouskova would be good to think about how to ensure this is consistently addressed. |
# Conflicts: # src/tlo/methods/healthsystem.py # src/tlo/methods/hsi_generic_first_appts.py
We're continuing the work on this in #1341 |
Within this PR, used equipment is integrated for each HSI event that requires some (only non-general/specific equipment to that event, so no chairs etc).
How:
__init__
, eg:if some equipment essential for the HSI event to run:
... (some asserts and setups)
If equipment checks enabled, and any of the items not available, the HSI event will not run.
if no equipment is essential for the HSI event to run:
... (some asserts and setups)
By doing that, you are showing that you've thought through the equipment for the particular event.
apply
function, add the equipment (including the essential equipment as it is not added automatically):Think thoroughly about whether the equipment is used only when consumables are available or if any other conditions are satisfied.
Sources where to look up equipment needed for the HSI events:
Use only item names or pkg names included in the
ResourceFile_Equipment.csv
located inresources/healthsystem/infrastructure_and_equipment/
. If the item you need to add is not present in the RF, it should be added there first.The original source of the items contained in the
ResourceFile_Equipment.csv
, is the HSSP III Equipment Costing (SEL Costing Sheet). You can find additional information there, including department and ward/room where the item is used.(note: If you can't find the exact item name, taken from
ResourceFile_Equipment.csv
, in the original SEL Costing Sheet, you can also try searching for one of the alternative names. If I've adjusted the item name, I've included the original name as an alternative name, including original names with a typo.)If you are not sure which equipment should be used with your HSI events, following sources may be helpful:
Module equipment integration assignees
TLO modules with HSI events & module leaders
TODO