Status

(DT comment: Christina Riley, I think this feature is straightforward enough to skip CHAI review step, but please indicate there are specific clarifications needed from CHAI, e.g., which fields should be editable vs. non-editable)

Notes

• Summary: Need editable and non-editable fields
• Relevant for both Bednet Distribution and Blood Screening forms
• Mosquito Breeding Site and Mosquito Collection Site forms, and PAOT forms can be re-completed numerous times and do not require this feature

Requirements

1. The user has the ability to click on any previously completed bednet distribution and blood screening tasks from the Family Tasks list view to view the previously entered information
2. Task edits for bednet distribution and blood screening can only be accessed through the Family Task List View
3. The user must select the 'COMPLETE' button of the given task on the Family List Task View to view the completed form.
4. The edit functionality will only be available by clicking the 'EDIT' button on the opened form.
5. Then the user has to hit the 'EDIT' button to edit those values and must then hit the 'SAVE' button for those values to be recorded and sent to the web and any other subscribing system.
6. Editable and non-editable fields will be identified in data dictionary for each form type (example below for bednet and blood screening)
7. Changes to the form will need to be reflected in reports and indicators
8. Changes to the form will need to be sent to any subscribing systems (Biophics or DHIS2)
   
9. If changes are made within the form while offline, only the most recent saved form will be synced with the web.
10. LIFECYCLE: The forms be locked from editing once the plan has been completed.

Examples

1. Bednet distribution
   1. FIELDS EDITABLE
      1. How many people live in this structure
      2. How many existing LLINS
      3. How many LLINS are <1 yr old
      4. How many LLINS are 1 to 2 yrs old
      5. How many LLINS are 1 to 2 yrs old
      6. How many LLINS are >3 yrs old
      7. How many existing LLIHNS
      8. How many LLIHNS are <1 yr old
      9. How many LLIHNS are 1 to 2 yrs old
      10. How many LLIHNS are 1 to 2 yrs old
      11. How many LLIHNS are >3 yrs old
      12. How many existing (conventional nets)
      13. How many normal nets dipped in last 6 months
      14. How many LLINS distributed
      15. How many LLIHNS distributed
      16. How many normal nets distributed
      17. How many normal nets redipped
      18. How many personal repellent units distributed
      19. Comment
   2. FIELDS NOT EDITABLE
      1. House has (N) total nets 
      2. Number of nets to be distributed
      3. Number of nets eligible to be redipped
2. Blood Screening (ALL FIELDS EDITABLE)

   1. Type of blood screening

   2. Has this person spent the night outside w/i the past two weeks
   3. Was this person tested
   4. Reason this person was not tested
   5. Type of test used
   6. Slide number
   7. Microscopy results
   8. RDT results
   9. Comments

Views

We anticipate the following views to be impacted on with the creation of this feature:

• Family View > Tasks list (DT comment: Craig Appl / Pierre Dane: does a list of all Reveal views already exist? Want to ensure we are using the same terminology to reference possible views)
  • Indicate under each task status in the Family List View that a task was edited (i.e. under 'COMPLETE' the user could see in smaller font 'Edited mm/dd')
• Add "Edit" button to top of bednet distribution form and blood screening form

Mock-ups

Complete Form View

Form Editing View

Edited Date View 

Software Requirements Specification

This section contains notes on what needs to be developed that were generated 23rd July to support estimating:

• Project activities:
  • Verify the data dictionary to ensure the editable fields are appropriate
  • We need to identify the underlying business logic when an edit form is completed compared to the first time that we need to 
  • We need to design the interactions (Roger's input is required)
  • We need to decide whether we should prepopulate the form or ask them to resubmit all together (this may mess up skip logic)
• Android client
  • We need to add a view to display and edit the form information
  • We need to update the form loading actions to ensure we can link these edited forms to tasks that were marked complete.
  • We need to update post save actions for edited forms
  • We need to update the form JSON in both languages to identify which forms should be edited.
• Web UI
  • We need to update the data warehouse tables to make previous versions available for querying
  • We need to update the ETL to ensure the information is mapped appropriately
  • We need to display the latest version of the form and possibly some indicator of the total number of versions submitted.

Justification

Thailand wants to be able to make corrections when mistakes are made during form completion, and add any additional information as necessary.

Dependencies

• Data dictionary update (DT comment: assuming may be easiest to define which fields should be editable vs. non-editable in the dictionary);
  • CR comment: yes - complete. fyi Craig Appl see data dictionary

Questions

Test Case