Status
# | Step | Status |
---|---|---|
1 | Responsible prepares rough business analysis/reqs doc | |
2 | Get CHAI review | |
3 | Get Akros Review | |
4 | Get Ona feedback | |
5 | Responsible - 1 iteration for feedback | |
6 | Ona sign off | |
7 | Ona tech spec scoping | |
8 | Ona LOE | |
9 | Ona scheduling |
Requirements
- The Thailand BVBD requires that all data captured in Reveal be available for ETL into their Malaria Informations System (Biophics)
- These data include all form fields and as much metadata as possible
- The requirement is for the following forms to be available in the Biophics holding database (db_mhealth)
- Household Registration with Head of Household (HoH) details and HoH created as a Household Member as well, as per Reveal
- Household Members (including HoH as mentioned above)
- Blood screening (linked to household member)
- Index Case Confirmation (linked to household member)
- Bednet distribution (linked to household)
- Indoor Residual Spraying (linked to household)
- Mosquito Collection (linked to focus area/operational area)
- Larval Dip (linked to focus area)
- (Near future) Potential Area of Transmission (linked to focus area/operational area)
- Field testing is planned for 23rd August
- Pilot in 3 provinces is scheduled for September, dependant on successful field testing
- It is more important to be able to see that a form has saved to the holding tables that to have every data exactly mirrored. The process can be tweaked to ensure that all fields are captured correctly, but the main priority is for CHAI and the BVBD to be able to see some data from each form saved on the mobile device showing up in Biophics within a few minutes. Each record should be correctly linked to other relevant records (e.g. a household member should always have a household record, a blood screening should always have a household member).
- Ideally, the holding tables should enforce referential integrity, but this can be relaxed if it will cause race conditions and insert failures
- Every record should have a timestamp for when it was created in Reveal, and when it was created in the holding tables
- Every record should include the name of the Reveal user who captured the data
- Every record should be linked to a plan and focus area
- There may be focus areas in Reveal that do not exist in Biophics - this is expected and should be dealt with (holding tables should include both the Reveal location id (not null) as well as the Biophics focus area id (nullable)
Screenshots
Notes
Questions
Test Case
# | Step | Pass / Fail | Comment |
---|---|---|---|
1 | |||
2 | |||
3 | |||
4 | |||
5 | |||
6 | |||
7 | |||
8 | |||
Additional tester comments: |