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

Tomography appointment is happening at level 2 rather than level 3 #1499

Open
BinglingICL opened this issue Oct 29, 2024 · 1 comment
Open

Comments

@BinglingICL
Copy link
Collaborator

Scenario run results shows that Tomography appointment is happening at level 2 rather than at level 3. As defined by ResourceFile_Appt_Time_Table.csv, this appointment should happen and only happen at level 3/central hospitals.

Initial search shows that Tomography is only used by RTI module; but not yet know the cause of this inconsistent place of level.

@mnjowe
Copy link
Collaborator

mnjowe commented Jan 28, 2025

Hi @BinglingICL . I think this code has to be changed to

if  'Tomography' in list(self.EXPECTED_APPT_FOOTPRINT.keys()):
            self.ACCEPTED_FACILITY_LEVEL = '3'
            self.add_equipment({'Computed Tomography (CT machine)', 'CT scanner accessories'})

self.add_equipment(self.healthcare_system.equipment.from_pkg_names('X-ray'))

I think with the current implementation, this condition will never run since the first block will always be true i.e. DiagRadio will always be in the list(self.EXPECTED_APPT_FOOTPRINT.keys()). This is according to how the expected footprint is being initialised here but also the fact that this function is just adding another key/appointment Tomography to the existing footprint if there are any injuries requiring tomography appointment and overwriting DiagRadio if any injuries requiring its appointment

I think the above is the reason you're having tomography appointment happening at facility level 2. It is because this block is not running hence no change of facility level

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants