-
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
Further Changes to Alri (if needed) #677
Open
tbhallett
wants to merge
228
commits into
master
Choose a base branch
from
ines/further-changes-to-alri
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…with treatment' analysis
…n classification due to clause age_exact_years <5
# Conflicts: # src/tlo/methods/hsi_generic_first_appts.py # tests/test_alri.py
# Conflicts: # src/tlo/methods/alri.py # tests/test_alri.py
# Conflicts: # src/tlo/methods/alri.py
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This builds on the changes in #676 and can be used to make any further changes following the review and work in July 2022.
Things discussed with @inesll, @timcolbourn and @tbhallett are:
Introduce parameter for the probability with which oxygen is indicated in the case of danger_signs
Introduce parameter that governs whether oxygen is provided to those with p.o. when O2 < 90%.
This is expected to show that there is a much greater impact of oxygen / pulse oximetry when....
I have been thinking that perhaps both of these could be accomplished by:
Changing the line in
treatment_failure
:needs_oxygen = SpO2_level == "<90%"
[I think this should probably change in any case, actually...?].Creating some more classification as follows:
danger_signs_pneumonia_oxygen_needed
anddanger_signs_pneumonia_oxygen_not_needed
Elaborating
_ultimate_treatment_indicated_for_patient
for indicate oxygen under each classification accordingly.Elaborating
get_imci_classification_based_on_symptoms
so that those withdanger_signs
among their symptoms get assigned todanger_signs_pneumonia_oxygen_needed
anddanger_signs_pneumonia_oxygen_not_needed
based on something (e.g. cyanosis symptom, or a flip of a coin, based on a parameter). [If a coin-flip would need to save theimci_classification_based_on_symptoms
as a property on the data fame so that it's fixed for the episode.]Elaborating
_get_imci_classification_by_SpO2_measure
so that those with Oxygen < 90 (and <92% when the parameter says so) get assigned todanger_signs_pneumonia_oxygen_needed
anddanger_signs_pneumonia_oxygen_not_needed
based on their actual measurement of SpO2.