3. Understanding visits to distinct set of providers

3.1 Currently Active

Providers who are currently notifying, even if not regularly.

## Error in fix.by(by.x, x): 'by' must specify a uniquely valid column

3.2 Recently stopped notifying (<=4 months ago)

These are providers who have recently stopped notifying (a maximum of until 4 months ago)

## Error in fix.by(by.x, x): 'by' must specify a uniquely valid column

3.3 Stopped notifying >=5 months ago

These are providers who have notified for a minimum period of 5 months.

## Error in fix.by(by.x, x): 'by' must specify a uniquely valid column

3.4 Not Notifying yet

## Error in fix.by(by.x, x): 'by' must specify a uniquely valid column

3.5 Not Notifying

## Error in fix.by(by.x, x): 'by' must specify a uniquely valid column

4. Provider Engagement & Field Efforts Combined: Month-Wise

Here, we look at the different type of providers (based on notifying behavior), along with the field efforts made to engage them.
We define below some of the terms used in the graph which might not be self-explanatory:

  1. new: who just joined
  2. last month notified: who have not notified in the current month + last 2 months (and hence we will not have any left ones for Jul 2021 and NA)
  3. regular: who are active at least 66%-70% of the months since they joined. 66% if duration is equal to or less than 3 months
  4. irregular: the ones who are not regular

How to read this graph:

  1. the 1st bar gives us number of providers in the category
  2. the 2nd bar gives us %share of notifications given by this group. Remember that not all of the providers would be notifying from that group in that current month
  3. the 3rd & fourth bar give us %cbnaat & %fdc given by the corresponding providers
  4. the 5th bar gives us the share of visits made last month to this category

Mar 2021

## Error in ans[ypos] <- rep(yes, length.out = len)[ypos]: replacement has length zero

NA

## Error in ans[ypos] <- rep(yes, length.out = len)[ypos]: replacement has length zero

May 2021

## Error in ans[ypos] <- rep(yes, length.out = len)[ypos]: replacement has length zero

5. The “what if” of providers leaving

Here, for each month providers stop notifying, we see what is the impact they are having on notifications & service usage. A high net impact means we need to scale up our efforts to sustain engagement.

## Error in ans[ypos] <- rep(yes, length.out = len)[ypos]: replacement has length zero

6. Field Officers; Detailed

From here on, we will look specifically at individual field officer efforts to drive engagement.

6.1 Visits made; Summary

While it is tempting to look at, the total visits made by each field officer may not the best criteria for monitoring in all situations. Here, we look at the average visits made by each field officer in a month to get a broader sense of their work schedules.

6.2 Total Visits made each month

Here, we see if field officers are increasing or decreasing their visits made, month on month

6.3 Days Active (monthly)

Here, we see if field officers are increasing or decreasing their visits made, month on month 

## Error in `combine_vars()`:
## ! Faceting variables must have at least one value.

6.4 Daily Visits (monthly)

Here, we see if field officers are increasing or decreasing their visits made, month on month 

## Error in `combine_vars()`:
## ! Faceting variables must have at least one value.

6.5 Unique Times a doctor is visited

## Error in `combine_vars()`:
## ! Faceting variables must have at least one value.

7. New Engagements

*Omitted for this version

8. Lost Providers

8.1 Lost Providers

Here, we see the number of providers assigned to these field officers who have stopped notifying, but are still being visited.

8.2 Data for providers who have stopped notifying


8. Detailed Visit data, for last 6 months, summarized