META: Encounters completion stats

[anvmn]

For each type of encounter we want to know:

• For each of possible activities:
  1. How many activities in total were shown.
  2. How many activities from those shown were completed.

[anvmn]

High level design:

1. Each type of encounter will be added a field where it's completion data will be stored.
2. For each type of encounter, we'll have a dedicated script that will locate encounters that don't have completion data set, and will compute and set it.
3. The scripts will be executed once a day, during night time.
4. We'll add new front-end APP that will allow selection of desired report:
   • Encounter type
   • Scope (Global / HC)
   • Date range (?)
     5. App will forward request to back-end, where encounters matching the criteria will be loaded, and their completion metrics will be aggregated and send to front-end.
     6. App will process raw data and generate completion statistics.

[anvmn]

Notes:

• Encounters had new logic and activities added with time. Each new content type that was added requires additional check for launch date (date when new version that included that change was deployed).
• There are special scenarios where activities that are usually considered mandatory are skipped. For example COVID suspect diagnosis on CHW app will lead straight away to Next steps.