...
Scoping Details | |
---|---|
Responsible Person: | Christina Riley |
Other parties to review/input: | |
FYI: | |
Targeted release date: | date |
Jira Status: | ticket link |
The responsible person owns this feature from scoping to tracking development by Ona and providing clarifications if needed, to testing and sign off. Status
Status
# | Step | Status |
---|---|---|
1 | Responsible prepares rough business analysis/reqs doc | COMPLETE: Christina Riley |
2 | Get CHAI review | *Need several verifications from CHAI team |
3 | Get Akros/VW Review | FYI: Pierre Dane |
4 | Get Ona feedback | FYI: Craig Appl |
5 | Responsible - 1 iteration for feedback | |
6 | Ona sign off | |
7 | Ona tech spec scoping | |
8 | Ona LOE | |
9 | Ona scheduling |
Table of Contents |
---|
High Level Steps
...
We assume the following with this process:
We will create 1 plan for each index case classification that arrives- BIOPHICS is the first customer for this automated feature and we will tailor the workflow for this system. We will make it more generic in the future
- We will work within the constraints of Reveal 2 when generating tasks. For example, the IRS tasks are hardcoded in the Android client when a family is created, so we will not create them in the server if a family isn't registered at a structure.
Split into 3 - CR to be responsible for first & 2nd
...
- All plans described below are to be generated as drafts within the Planning Module and only made active by a human user - this has been covered under the NiFI Business Logic to be Developed section.
Note | ||
---|---|---|
| ||
NEW Assumptions for ReviewCraig Appl Annie Martin - the new assumptions below have been added based on recent conversations around missing scope pertaining to more than one FI plan being created when a case is linked to more than one foci (i.e. focus of infection and focus of residence), and when more than one index case is reported within the MIS for a given jurisdiction within a 20-day time period (i.e. how to deal with cases that would normally trigger an FI but an FI is already in progress). Automation for case-triggered FIs when the Focus of Infection and the Focus of Residence are the SAME If the BIOPHICS variables Focus_case_residence_classification_code and focus_Source_of_Infection_classification_code are the same, then the index case resides in the focus in which they acquired the malaria infection and only one plan needs to be generated and carried out in this focus (i.e. this is a local case). For the purposes of Thailand, local cases are defined as being from within the same focus (i.e. sub-village), as confirmed by Pedro. The assumptions for this type of scenario are in-line with the original assumptions described above. Automation for case-triggered FIs when the Focus of Infection and the Focus of Residence are NOT THE SAME **Section in progress** If the BIOPHICS variables Focus_case_residence_classification_id and Focus_Source_of_Infection_classification_id are NOT the same, then the index case resides in a focus other than the focus in which they acquired the malaria infection. This means that two plans need to be generated - one plan for each focus. By definition, the case classification will be considered local for the focus of infection and imported for the focus of residence. The case classification variable that is imported from BIOPHICS is classified in relation to the focus of diagnosis/residence. Christina Riley verifying that 'focus of residence' & 'focus of diagnosis' are considered the same in regard to the Thai Protocol & BIOPHICS classification. For the purposes of Thailand, local cases are defined as being from within the same focus (i.e. sub-village), as confirmed by Pedro.
Automation for case-triggered FIs when more than one index case is reported from the MIS in the same jurisdiction with an active plan (plans are active for 20 days from the 1st reported index case) **Section in progress**
|
Sample Index Case Classification Form from BIOPHICS
...