TLO output vs TLM data: patient mix#1862
Open
BinglingICL wants to merge 6 commits into
Open
Conversation
…lots, both mean and median
… not be on duty on any given day
This file contains hidden or 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
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.
Here we aim to compare patient mix output by TLO with TLM data, including four aspects:
(1) patient load per HCW. --> This is the fundamental step, making sure that TLO is capturing the patient volumes appropriately. We begin with subgroup comparison, then plan to build hierarchical model using the survey data to model district and level effects for a statistically sound validation for TLO model.
(2) patient care seeking persistence
(3) patient mix across age groups, wealth levels, health conditions, and facility types. District attribute may not be considered due to limited districts selected in TLM data.
(4) patient contact time.