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 tasks from the Family Tasks list view to view the previously entered information
2. Then the user has to hit an "Edit" button to edit those values
3. Q: Can the task be edited if navigated to through the map view as well, for those structures that only have one task type available, or through a link on a task Card?
4. Q:  What will the call to action on the card or family list view be?
5. The edit functionality will only be available by clicking a button on the task/form
6. Then the user has to hit an "Edit" button to edit those values
7. Editable and non-editable fields will be identified in data dictionary for each form type (example below for bednet and blood screening)
8. Changes to the form will need to be reflected in reports and indicators
9. Changes to the form will need to be sent to any subscribing systems (Biophics or DHIS2)
10. LIFECYCLE: Should the forms be locked for editing at any point? once the plan has been completed? After a certain amount of time?

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)
  • QUESTION/RECOMMENDATION: Do we want to 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

Add Form view

With edit button

                              Display edited date

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

• QUESTION/RECOMMENDATION: Do we want to 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')

Test Case