Conversation
…emphero/nurses_scenario
…emphero/nurses_scenario
| self.initial_population_size = 200 | ||
| self._scenarios = self._get_scenarios() | ||
| self.number_of_draws = len(self._scenarios) | ||
| self.number_of_draws = 2 |
There was a problem hiding this comment.
Line 29 is repeating line 28, so line 29 can be dropped, I think.
| { | ||
| "HealthSystem": { | ||
| 'ResourceFile_HR_scaling_by_level_and_officer_type': "default", | ||
| 'mode_appt_constraints_postSwitch': 2, |
There was a problem hiding this comment.
All scenarios use Mode 2 since 2025; so line 61 is enough.
There was a problem hiding this comment.
This applies to all scenarios.
| self._default_of_all_scenarios(), | ||
| { | ||
| "HealthSystem": { | ||
| 'ResourceFile_HR_scaling_by_level_and_officer_type': "default", |
There was a problem hiding this comment.
I think it is not here is implement the change of nursing cadre capabilities. It should be in the class ConstantRescalingHRCapabilities in the health system module to read the updated capabilities, and then schedule the expansion event every year from a start year to an end year (normally the simulation end) in the health system module.
There was a problem hiding this comment.
This applies to all scenarios.
There was a problem hiding this comment.
If I understand you correctly, you want use to change the expansion every year. Aren't we just supposed to change yearly_HR_scaling_mode for that? Or are you suggesting that we have to re-write class ConstantRescalingHRCapabilities for yearly scaling?
There was a problem hiding this comment.
Hi Wati, we are supposed to change year_HR_scaling_by_level_and_officer_type parameter here, such as set it to be 2025, so that the event of ConstantRescalingHRCapabilities will be scheduled on the first day in the year of 2025, meaning the expansion will happen on that day and the scaled up staff capabilities will remain onwards till the end of simulation
My comment above meant that 'ResourceFile_HR_scaling_by_level_and_officer_type' is not a health system module parameter, so we cannot modify it. Instead, we should modify 'HR_scaling_by_level_and_officer_type_mode' parameter, such as set it to be "default" or "custom" (the csv file that store the values of scaling up factors).
There was a problem hiding this comment.
The parameter name of yearly_HR_scaling_mode is quite similar and can be misleading, but it is related to a default historial HRH growth from 2020 to 2024, which is not relevant to our nursing expansion from 2025 here.
| "HealthSystem": { | ||
| 'ResourceFile_HR_scaling_by_level_and_officer_type': "default", | ||
| 'mode_appt_constraints_postSwitch': 2, | ||
| "use_funded_or_actual_staffing": "actual", |
There was a problem hiding this comment.
This parameter is to be untouched I think. All HRH capabilities change will be implemented by changing the values in the csv files in ResourceFile_HR_scaling_by_level_and_officer_type folder.
There was a problem hiding this comment.
This applies to all scenarios.
There was a problem hiding this comment.
I think we did this. You will notice that we changed the csv value files in the ResourceFile_HR_scaling_by_level_and_officer_type folder for scenarios Improved Staffing Doubled Establishment, Worse Case. These are associated with csv files custom_doubling.csv and custom_worse.csv respectively. Is this what you mean? Or do you mean we should delete all lines where we set ResourceFile_HR_scaling_by_level_and_officer_type?
There was a problem hiding this comment.
Hi Pemphero, here I meant to not modifying use_funded_or_actual_staffing parameter in this script, which is not necessary. So all relevant lines on this should be dropped.
It is good that we have already the csv files to modify the nursing staffing. To implement such changes, we just need to modify the HR_scaling_by_level_and_officer_type_mode as mentioned in my response to Wati.
There was a problem hiding this comment.
If we remove use_funded_or_actual_staffing , how best are we going to represent the scenarios where in the baseline scenario we are using the actual (filled positions) and in the improved scenario, we are using the funded_plus (staff establishment)?
There was a problem hiding this comment.
Hi Pemphero, sorry for my possible misunderstanding, but may I confirm: in your improved scenario, you will only have the nursing cadre to achieve the establishment level? Considering that all other cadres remain as current levels across all scenarios.
If so, you do not need to modify use_funded_or_actual_staffing here but to calculate the corresponding scale-up factor and store it in the csv file in the ResourceFile_HR_scaling_by_level_and_officer_type folder, and then modify the HR_scaling_by_level_and_officer_type_mode parameter.
It would be good that we have a clear diagram for all nursing expansion scenarios, specifying the expansion time/period along the simulation timeline. And we could have further discussions on this if anything unclear. (I am attaching one example from my work, which is yearly expansion from 2025 to 2034; not a one-time scaling-up at the beginning of 2025 though.)

There was a problem hiding this comment.
Hi Bingling and Pemphero,
The attached document contains the scenarios for this study. Of course, its not final.
For Improved Staffing scenario or scaling factor, I went through Tara's paper. Was thinking we could use a linear establishment filling for the scaling factor as seen below. The only challenge would be that we need to find number of filled nursing posts in the baseline year (N0) and approved nursing establishment (E) as seen below. It would also be easy to get a formula for the worst case from this. This is something we would try to find.
Improved Staffing (Nurses Only): Establishment Filling
Let:
N0= number of filled nursing posts in the baseline year (maybe 2024)E= approved nursing establishmentT= target year (2030)y= current simulation year, where y ∈ {2025, 2026, …, 2030}
We assume linear filling of vacant nursing posts:
N_y = N0 + ((E - N0) / (T - 2024)) * (y - 2024)
The nurse scaling factor applied in year y is:
SF_y = N_y / N0
| } | ||
| ), | ||
|
|
||
| "Improved Staffing": |
There was a problem hiding this comment.
Is this scenario to scale up all cadres to meet the establishment level? If so, we need to calculate the correspondeing scaling up factors to be saved in a csv file in the folder ResourceFile_HR_scaling_by_level_and_officer_type.
There was a problem hiding this comment.
It seems to me that this scenario consists of two parts: one is to expand nurse cadre, and the other is to expand other cadres. I think these two parts may need to be explicitly separated in the scenario definitions. By which I mean, the main variable in the problem is to change the nursing capabilities, and basing on that, consider what capability levels of other cadres are to be specified across the scenarios.
There was a problem hiding this comment.
In our previous discussions, we decided to keep all other cadres constant and use historical growth (i.e., Only nurses change. Other cadres remain constant)
| "HealthSystem": { | ||
| 'ResourceFile_HR_scaling_by_level_and_officer_type': "default", | ||
| 'mode_appt_constraints_postSwitch': 2, | ||
| "use_funded_or_actual_staffing": "funded_plus", |
There was a problem hiding this comment.
So in this scenario, if you want to scale up the nursing staff to the establishment level in the year of 2025: we do not use "use_funded_or_actual_staffing": "funded_plus", which will not work; instead, we create a csv file to store the scale-up factor (e.g. established nursing count/2024 nursing count) that will enable such expansion and set HR_scaling_by_level_and_officer_type_mode to the csv file name.
There was a problem hiding this comment.
This applies to the next scenario where you want to increase nursing count to doubling establishment.
…emphero/nurses_scenario
|
Hi @BinglingICL and @tbhallett, |
Analyses for nurse shortages. Issue #1747