You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Do we want to incorporate some kind of documentation or citations around our choice for values and groups used in the application?
Below is an older version of this issue, more focused on which groups to include.
This question is intended to facilitate the discussion around what (pre-defined) risk groups should be included in Tabby2 as targetable for increased screening coverage in the "Custom Interventions."
Additionally, we have previously stated that we'd like to include sorting into categories close to the following:
Elevated LTBI Prevalence
Elevated TB Exposure
Elevated LTBI to Active TB Progression
It looks to me like the CDC TTT risk groups are only sorted into the last two categories, so we should discuss how to divide the risk groups into these three categories or if there are any changes we should make to the categories.
Do we want to incorporate some kind of documentation or citations around our choice for values and groups used in the application?
Below is an older version of this issue, more focused on which groups to include.
This question is intended to facilitate the discussion around what (pre-defined) risk groups should be included in Tabby2 as targetable for increased screening coverage in the "Custom Interventions."
Additionally, we have previously stated that we'd like to include sorting into categories close to the following:
It looks to me like the CDC TTT risk groups are only sorted into the last two categories, so we should discuss how to divide the risk groups into these three categories or if there are any changes we should make to the categories.
The CDC Targeted Tuberculosis Testing website provides the following classification of Persons at Risk of Developing TB Disease:
Additional categories that we've previously said we should include are:
The text was updated successfully, but these errors were encountered: