-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathindex.html
More file actions
794 lines (482 loc) · 34.9 KB
/
index.html
File metadata and controls
794 lines (482 loc) · 34.9 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
<!DOCTYPE html>
<html lang="" xml:lang="">
<head>
<title>Assessing coverage of Community-based Management of Acute Malnutrition</title>
<meta charset="utf-8" />
<meta name="author" content="" />
<script src="libs/header-attrs/header-attrs.js"></script>
<link rel="stylesheet" href="xaringan-themer.css" type="text/css" />
</head>
<body>
<textarea id="source">
class: center, middle, inverse, title-slide
.title[
# Assessing coverage of Community-based Management of Acute Malnutrition
]
.author[
###
]
---
class: inverse, center, middle
## Ernest Guevarra
### 1 March 2023
#### <svg aria-hidden="true" role="img" viewBox="0 0 512 512" style="height:1em;width:1em;vertical-align:-0.125em;margin-left:auto;margin-right:auto;font-size:inherit;fill:white;overflow:visible;position:relative;"><path d="M64 112c-8.8 0-16 7.2-16 16v22.1L220.5 291.7c20.7 17 50.4 17 71.1 0L464 150.1V128c0-8.8-7.2-16-16-16H64zM48 212.2V384c0 8.8 7.2 16 16 16H448c8.8 0 16-7.2 16-16V212.2L322 328.8c-38.4 31.5-93.7 31.5-132 0L48 212.2zM0 128C0 92.7 28.7 64 64 64H448c35.3 0 64 28.7 64 64V384c0 35.3-28.7 64-64 64H64c-35.3 0-64-28.7-64-64V128z"/></svg> [ernest@guevarra.io](mailto:ernest@guevarra.io) <svg aria-hidden="true" role="img" viewBox="0 0 512 512" style="height:1em;width:1em;vertical-align:-0.125em;margin-left:auto;margin-right:auto;font-size:inherit;fill:white;overflow:visible;position:relative;"><path d="M352 256c0 22.2-1.2 43.6-3.3 64H163.3c-2.2-20.4-3.3-41.8-3.3-64s1.2-43.6 3.3-64H348.7c2.2 20.4 3.3 41.8 3.3 64zm28.8-64H503.9c5.3 20.5 8.1 41.9 8.1 64s-2.8 43.5-8.1 64H380.8c2.1-20.6 3.2-42 3.2-64s-1.1-43.4-3.2-64zm112.6-32H376.7c-10-63.9-29.8-117.4-55.3-151.6c78.3 20.7 142 77.5 171.9 151.6zm-149.1 0H167.7c6.1-36.4 15.5-68.6 27-94.7c10.5-23.6 22.2-40.7 33.5-51.5C239.4 3.2 248.7 0 256 0s16.6 3.2 27.8 13.8c11.3 10.8 23 27.9 33.5 51.5c11.6 26 21 58.2 27 94.7zm-209 0H18.6C48.6 85.9 112.2 29.1 190.6 8.4C165.1 42.6 145.3 96.1 135.3 160zM8.1 192H131.2c-2.1 20.6-3.2 42-3.2 64s1.1 43.4 3.2 64H8.1C2.8 299.5 0 278.1 0 256s2.8-43.5 8.1-64zM194.7 446.6c-11.6-26-20.9-58.2-27-94.6H344.3c-6.1 36.4-15.5 68.6-27 94.6c-10.5 23.6-22.2 40.7-33.5 51.5C272.6 508.8 263.3 512 256 512s-16.6-3.2-27.8-13.8c-11.3-10.8-23-27.9-33.5-51.5zM135.3 352c10 63.9 29.8 117.4 55.3 151.6C112.2 482.9 48.6 426.1 18.6 352H135.3zm358.1 0c-30 74.1-93.6 130.9-171.9 151.6c25.5-34.2 45.2-87.7 55.3-151.6H493.4z"/></svg> [ernest.guevarra.io](https://ernest.guevarra.io) <svg aria-hidden="true" role="img" viewBox="0 0 448 512" style="height:1em;width:0.88em;vertical-align:-0.125em;margin-left:auto;margin-right:auto;font-size:inherit;fill:white;overflow:visible;position:relative;"><path d="M416 32H31.9C14.3 32 0 46.5 0 64.3v383.4C0 465.5 14.3 480 31.9 480H416c17.6 0 32-14.5 32-32.3V64.3c0-17.8-14.4-32.3-32-32.3zM135.4 416H69V202.2h66.5V416zm-33.2-243c-21.3 0-38.5-17.3-38.5-38.5S80.9 96 102.2 96c21.2 0 38.5 17.3 38.5 38.5 0 21.3-17.2 38.5-38.5 38.5zm282.1 243h-66.4V312c0-24.8-.5-56.7-34.5-56.7-34.6 0-39.9 27-39.9 54.9V416h-66.4V202.2h63.7v29.2h.9c8.9-16.8 30.6-34.5 62.9-34.5 67.2 0 79.7 44.3 79.7 101.9V416z"/></svg> [ernestguevarra](https://www.linkedin/in/ernestguevarra)
???
I am Ernest Guevarra, a medical doctor and a public health specialist with twenty years of professional experience working in twenty countries across Africa, South and South East Asia on community based programming in maternal and child health and nutrition. I have expertise in designing and conducting national health and nutrition surveys, spatial epidemiology, and programme evaluation.
I am currently a consulting research data scientist for modelling and analytics at EcoHealth Alliance producing analytics that inform policies related to the COVID-19 response in New York State.
I am founding member of Katilingban, a collective of public health and nutrition experts and practitioners leading its analytics and software development unit. I design, develop and maintain a set of open source software for implementation of health and nutrition spatial sampling surveys and nutrition analytics.
---
# Outline
* What is coverage?
* Why is coverage important?
* Measuring coverage
* Coverage challenges
???
In this lecture, I will first walk you through a conceptual framework of what coverage is and why it is important in relation to community-based management of acute malnutrition programmes. With this as foundation, I will then discuss how coverage of CMAM programmes has been measured in the early days, the limitations and weaknesses of these measures, and then detail the development and current use of more robust coverage assessment methods that addresses majority of the limitations and weaknesses of the previous methods. Finally, I will close by describing the set of challenges we face with regard to coverage of nutrition programmes in general and how the experience with development of concepts and methods for coverage assessment of CMAM programmes may offer solutions.
---
class: inverse, center, middle
# What is coverage?
---
class: center, middle
`$$\Large \text{coverage} ~ = ~ \frac{\text{No. in the programme}}{\text{No. who should be in programme}}$$`
???
Mathematically, we can represent a generic and general concept of coverage as follows.
Coverage is the proportion between those who are in a programme and those who should be in the programme.
What this mathematical model definition of coverage implies are:
* That there is a criteria or definition for those who should be in the programme; and,
* That the values for those in the programme and those who should be in the programme should be measured in order to give an estimate of coverage.
---
class: center, middle, inverse
# Coverage and CMAM
???
Now let us try to apply this mathematical concept of coverage to CMAM. /next slide
---
# Coverage estimators - old
`\(\Large \text{Point coverage} ~ = ~ \frac{C_{in}}{C_{in} ~ + ~ C_{out}}\)`
`\(\Large \text{Period coverage} ~ = ~ \frac{C_{in} ~ + ~ R_{in}}{C_{in} ~ + ~ C_{out} ~ + ~ R_{in}}\)`
where:
`\(C_{in} ~ = ~ \text{cases in the programme}\)`
`\(C_{out} ~ = ~ \text{cases not in the programme}\)`
`\(R_{in} ~ = ~ \text{recovering cases in the programme}\)`
???
The following estimators represent the the concept of coverage as it relates to CMAM.
Point coverage definition is a direct representation of the generic and general concept presented earlier in relation to CMAM. Here we now specifically call those who should be in the programme as cases and these cases have specific case definitions. For CMAM programmes, these will be case definitions of moderate acute malnutrition or MAM and severe acute malnutrition or SAM based on weight-for-height z-scores and/or MUAC.
Period coverage on the other hand adds the concept of recovering cases that are still in the programme. These cases are those that at some point earlier fulfilled the case definitions of MAM or SAM, have been identified by the programme and enrolled in the programme and are now still in the programme but by case definition are no longer MAM or SAM. These are previous cases that are most likely recovering and awaiting programme discharge.
---
# Characteristics of estimators
* **Point coverage** assesses the programme's case-finding capabilities
* **Period coverage** assesses the programme's case-finding capabilities and its ability to retain a case from admission to cure. Always equal to or higher than point coverage (never lower)
* Period coverage more closely approximates treatment coverage or effective coverage
???
Point coverage assesses the programme's case finding capabilities whilst period coverage assesses the programme's ability to find cases and its ability to retain a case from admission to cure.
Some important universal estimator characteristics to remember are:
* period coverage is always equal to or higher than point coverage; it can never be lower than point coverage; and,
* period coverage more closely approximates treatment coverage or effective coverage
---
# Bias and limitations of estimators
* Both estimators are unable to detect **cases who have died** and **recovering cases not in the programme**
* **Point coverage** can underestimate true coverage in settings where **case prevalence is low** and **majority of cases are in recovery**
* **Period coverage** can overestimate true coverage in settings where **length of stay** in programme is **prolonged**
???
It is important to understand also that these estimators have biases and limitations.
* both estimators are unable to account for cases who have died and cases who are recovering but are not in the programme;
* point coverage can underestimate true coverage in settings were case prevalence is low and majority of cases are in recovery; and,
* period coverage can overestimate true coverage in settings where length of stay in programme is prolonged.
---
# Which estimators to use?
* **Early days of CMAM:** reported both point and period coverage estimators
* **Recent past:** recommendation has been made to report *only one* of the coverage estimators with the choice of estimator to report to be based on programme features such as length of stay and MUAC at admission among others
???
In the early days of CMAM, both point and period coverage were reported. However, this has been met with confusion particularly in settings where the different between point and period coverage is large and reports tended to not explain the differentiation between the two estimators in relation to the programme context.
In the recent past, a general recommendation was made to report only one of the two estimators with the choice of which estimator to report based on programme features such as length of stay and MUAC at admission among others.
However, it has been noted that during this period, most programmes tended to report the coverage estimator that provided the higher estimate.
---
# Coverage estimators - updated
`\(\Large \text{Case-finding effectiveness} ~ = ~ \frac{C_{in}}{C_{in} ~ + ~ C_{out}}\)`
`\(\Large \text{Treatment coverage} ~ = ~ \frac{C_{in} ~ + ~ R_{in}}{C_{in} ~ + ~ C_{out} ~ + ~ R_{in} ~ + ~ R_{out}}\)`
where:
`\(C_{in} ~ = ~ \text{cases in the programme}\)`
`\(C_{out} ~ = ~ \text{cases not in the programme}\)`
`\(R_{in} ~ = ~ \text{recovering cases in the programme}\)`
`\(R_{out} ~ = ~ \text{recovering cases not in the programme}\)`
???
Current development work on the coverage assessment methods for CMAM have now led to an updating of these estimators as represented by these mathematical concepts.
These updates were aimed at addressing the known biases and limitations of the previous estimators and to provide a more practical way to resolve the issue of cherry-picking of indicators.
In the mathematical concepts shown in this slide, we note the following new elements:
* Terminology has been adapted to be more descriptive of what they actually measure. What we have previously called point coverage is now called case-finding effectiveness to aptly describe what the estimator measures.
* For period coverage, the concept of a recovering cases not in the programme has been introduced. This term addressed previous limitation that doesn't take into account this value.
* Given the inclusion of the recovering cases in the programme in the period coverage definition, this estimator has now been called treatment coverage as it now more robustly approximates this indicator.
---
# What estimators to use?
* We now recommend that *both* estimators be reported as they describe different aspects of the programme relevant to coverage.
* **Case-finding effectiveness** gives an idea of how good the programme is in case-finding – a key factor in coverage
* **Treatment coverage** provides an approximation of true coverage or effective coverage
???
With these changes, it is now recommended that both estimators be reported as they describe different aspects of the programme relevant to coverage:
* Case-finding effectiveness gives an idea of how good the programme is in case-finding which is a key factor in coverage; and,
* Treatment coverage provides an approximation of true coverage or effective coverage.
---
class: inverse, center, middle
# Why coverage?
???
Now that we have grounded ourselves on the definition of coverage in relation to CMAM, let us now discuss why coverage is important.
---
# Effective CMAM meets needs
* **Efficacy** of CMAM - cure rate in ideal and controlled settings - is near 100%
* **Effectiveness** of CMAM - cure rate in programme conditions - still room for improvement
* Effectiveness depends on:
1. Thorough case-finding and early treatment-seeking;
2. High-level of compliance; and,
3. Good retention from admission to cure.
???
The ultimate aim of CMAM is to meet the needs of wasted children who are at most risk of death. From the development of CMAM, we already know that the CMAM model of therapeutic care for wasted children is highly efficacious - close to 100% in ideal and controlled settings.
However, in actual programme conditions, CMAM effectiveness still leaves room for development.
Effectiveness depends on:
* thorough case-finding and early treatment seeking;
* high-level of compliance; and,
* good retention from admission to cure.
---
# High coverage CMAM meets needs
* **Coverage** of CMAM – the proportion of all children eligible to receive CMAM who actually receive it – contributes to effectiveness as well
* Coverage directly depends on:
1. Thorough case-finding and early treatment-seeking; and,
2. Good retention from admission to cure.
* It also indirectly depends on **compliance**.
???
The coverage of a CMAM programme contributes to effectiveness as well. To be able to reach high CMAM coverage, a programme requires:
* thorough case-finding and early treatment-seeking;
* good retention from admission to cure; and,
* indirectly, compliance.
---
background-color: #FFFFFF
.center[]
**Meeting needs require both high effectiveness and high coverage**
* Good coverage supports good effectiveness
* Good effectiveness supports good coverage
* Maximising coverage maximises effectiveness and met need
???
From this what we notice is that CMAM effectiveness depends on the very same things as CMAM coverage:
* Good coverage supports good effectiveness;
* Good effectiveness supports good coverage;
* Maximising coverage maximises effectiveness and met need
---
class: inverse, center, middle
`$$\LARGE \text{Met need} ~ = ~ \text{effectiveness} ~ \times ~ \text{coverage}$$`
???
This can be conceptualised mathematically as follows:
Met need = effectiveness X coverage
---
background-image: url(figures/coverage2.png)
background-size: contain
???
To illustrate this mathematical concept, here is a theoretical example.
The programme on the left-hand side is a high coverage programme with 80% of those in need having been recruited into the programme. It is also a highly effective programme with a cure rate of 90%. This programme meets the needs of 72% of those who have the needs.
On the other hand, the programme on the right-hand side has low coverage of 30% and a moderate level of effectiveness at 75%. This programme is assessed to be addressing only 23% of those with needs.
---
background-image: url(figures/coverage3.png)
background-size: contain
???
Another framework by which to conceptualise the importance of coverage is through Tanahashi's model of health service delivery coverage. Our various conceptions of coverage are hierarchical in nature with the more basic concept of availability being the most common and easily reported metric. This is usually proxied by geographic coverage indicators that indicate how many health care centres or facilities provide the specific service. This is considered a lower order coverage indicator or metric because it measures more of the coverage potential of a programme rather than its true or effective coverage. As one goes up Tanahashi's coverage ladder, various barriers and bottlenecks impact on this coverage potential whilst the metrics more and more approximate true or effective coverage.
The estimators we discussed a while ago would be considered contact coverage indicators, which are one rung below true or effective coverage indicators. But as we have noted above, combining the programmes effectiveness metric allows us to approximate true coverage.
---
class: inverse, center, middle
# Questions?
---
class: inverse, center, middle
# How to measure coverage?
???
I will now walk you through how CMAM coverage, as we have defined it, is measured.
---
# Indirect estimation of coverage
`$$\text{coverage} ~ = ~ \frac{\text{Total cases admitted in programme}}{\text{Estimated number of cases}}$$`
* **Numerator** is based on programme data
* **Denominator** is a caseload estimation based on total population in programme area and known prevalence estimate and known incidence
* Issues mainly stem from estimation of denominator
???
In the early days of therapeutic care for wasted children, coverage was usually estimated indirectly using the following formula shown in the slide.
The numerator value is taken from total admissions as per programme data while the denominator is based on a caseload estimation based on total population in the programme area and known prevalence and incidence of wasting
The main issue with indirect estimation stems from estimation of the denominator. It is not uncommon to find official reports that indicate coverage as being more than a 100% which illustrates the problem with the robustness of caseload estimation.
---
# Direct estimation of coverage
* Coverage estimation through a survey.
* Old approach: include coverage indicator in nutrition surveys that assess prevalence of undernutrition (SMART surveys)
* Issues with old approach: sample size
* Current approaches: surveys specifically assessing coverage
???
With this limitation in mind, others have tried to assess coverage through a survey and specifically, the approach was to piggyback coverage surveys onto nutrition surveys that assess prevalence of wasting (SMART surveys). The issue with this approach is sample size of children who quality for the case definition of MAM or SAM. Since the SMART surveys select samples of children under 5 regardless of their wasting status, it is not uncommon that only very few wasted children are identified and can be included in the sample for coverage estimation. Estimates were therefore lacking precision.
---
# History of methods development
* Coverage and its assessment was an integral component of the development process of CMAM (then called CTC)
* **Centric Systematic Area Sampling (CSAS)** was the first coverage assessment method developed
* However, **CSAS** was not as commonly used as it was deemed too costly and hard to implement
???
These issues were tackled alongside the development of the CMAM approach such that work was done to develop a specific survey method that would specific to therapeutic care of wasted children.
The first method developed as part of the development of the therapeutic care of wasted children is the Centric Systematic Area Sampling (CSAS) method. Majority of early and pre-cursor CMAM programmes were evaluated using CSAS.
However, CSAS was deemed too costly and hard to implement.
---
# History of methods development
* **SQUEAC** and **SLEAC** were then developed as quick and easy (hence less costly) methods to assess coverage
* **SQUEAC** and to some extent **SLEAC** now widely used and considered the standard, off-the-shelf methods
* With CMAM programmes getting scaled up to national scope, a wide area/large scale method such as **S3M** has been recently developed
???
The development then shifted to finding alternatives to CSAS that were rough and ready and cheap and easy to implement.
SQUEAC and SLEAC were then developed as quick and easy methods to assess coverage. SQUEAC and SLEAC are now widely used and considered the standard methods for assessing CMAM coverage.
Then recently, with CMAM programmes getting scaled up at national level, wide area methods such as the Simple Spatial Survey Method (S3M) has been developed to allow for large scale programme coverage assessment.
---
# CSAS: Design
* **CSAS** uses a two-stage sampling design
* The first stage is a **systematic spatial sample** of the entire service area to select the communities to survey.
* The second stage is an **active and adaptive case-finding method** that finds all or nearly all cases in the communities being surveyed.
???
CSAS uses a two-stage sampling design with the first stage being a systematic spatial sample of the entire service area to select the first stage samples. The second stage is an active and adaptive case-finding method that finds all or nearly all cases in the community being surveyed.
The active and adaptive case finding method is a method specifically designed for CMAM coverage. It is a snowball sampling approach. Key terms and descriptions used by the community to describe wasting is used as case-finding terms to find cases of wasted children. Once a case is found, they then become new informants to lead enumerators to find a case similar to the current case. This approach as used with SAM specifically has been found to have high specificity and sensitivity to detecting SAM cases. This case-finding method is used in all the coverage methods.
---
# CSAS: Results
* Overall coverage estimate
* Local coverage estimates which can be represented as a coverage map
* Ranked list of barriers
???
CSAS provides an overall coverage estimate, local coverage estimates which is reported as a coverage map, and a ranked list of coverage barriers
---
background-color: #FFFFFF
# CSAS: Results
.pull-left[
Coverage map produced by CSAS surveys
]
.pull-right[
Ranked list of barriers from a CSAS survey
]
???
Here we see the various outputs that CSAS provides. On the left-hand side, we see a coverage map produced by CSAS surveys. On the right-hand side, we see a Pareto chart of ranked list of barriers collected through a CSAS survey
---
# SQUEAC: Design
* **Semi-quantitative Evaluation of Access and Coverage** or **SQUEAC** is more an investigation than a survey
* **Stage 1:** Semi-quantitative investigation into factors affecting coverage using the **SQUEAC** toolkit, which is a set of simple and rapid tools and methods for collecting and analysing data related to coverage.
* **Stage 2:** Confirm areas of high and low coverage and other hypotheses relating to coverage identified in stage 1 through small studies, small surveys, and small-area surveys.
* **Stage 3:** Estimate overall coverage using Bayesian techniques. A likelihood survey is conducted as part of this stage. This two-stage sampling design is the same as with all other coverage survey methods.
* This stage is optional. Should be done if the reporting of an overall coverage estimate is a key information requirement in addition to the rich information on barriers and boosters to coverage already gained from stages 1 and 2.
???
Semi-quantitative evaluation of access and coverage or SQUEAC is a more local-focused method that is more an investigation than a survey.
Stage 1 involves a thorough quantitative and qualitative investigation of factors that impact on programme coverage. Stage 2 is usually a set of tests or small studies that aim to confirm or deny hypothesis of coverage developed from Stage 1. Stage 1 and stage 2 produce vast amounts of knowledge and understanding of the programme's coverage factors and informs programme managers of the what elements in the programme are supporting or blocking coverage.
Stage 3, an optional stage, is the step in which a prior belief of programme coverage generated from Stage 1 and Stage 2 is combined with the data from a likelihood survey using Bayesian calculations to come up with an overall estimate of programme coverage with useful precision.
This stage is recommended to be done only when an overall coverage estimate is required in addition to the already rich set of information provided by stage 1 and stage 2.
---
background-color: #FFFFFF
# SQUEAC: Results
.pull-left[
* Concept map of barriers and boosters to coverage
* Coverage map using small area surveys through a “risk mapping” approach
* Estimation of coverage proportion using Bayesian techniques
]
.pull-right[]
???
SQUEAC provides a concept map of barriers and boosters to programme coverage, a coverage map using small area surveys through a risk mapping approach, and an estimation of coverage proportion (if stage 3 is performed).
---
# SLEAC
* **Simplified Lot Quality Assurance Evaluation of Access and Coverage (SLEAC)** is a rapid low-resource survey method that classifies coverage at the service delivery unit (SDU) level.
* Identifies the category of coverage (e.g. **“low”**, **“moderate”** or **“high”**) achieved by the service delivery unit being assessed.
* Relatively small sample sizes (e.g. `\(n ~ \geq ~ 40\)`) are required in order to make an accurate and reliable classification.
* Can also estimate coverage over several service delivery units and is suited to wide-area use.
* Coverage is still classified for the individual service delivery units, then, data from individual service delivery units are combined and overall coverage for the wide area is estimated.
???
Simplified Lot Quality Assurance Sampling Evaluation of Access and Coverage or SLEAC classifies coverage achieved by the service in the service area as either a PASS or FAIL or as low, moderate or high. Relatively low sample sizes are required (n ≥ 40) are required in order to make a reliable classification.
If applied onto a wider area, coverage can be estimated by aggregating the SLEAC results in each service area surveyed to come up with an overall estimate for the combined area of smaller service areas.
---
# SLEAC: Design
* First stage systematic spatial sample similar to that used in CSAS. Only small sample sizes ( `\(n ~ \geq ~ 40\)` ) are required for each service delivery unit in which coverage is being classified.
* Second stage sample is an active and adaptive case-finding method as with the other coverage survey methods.
???
SLEAC uses a similar design as CSAS but with require fewer clusters as sample size requirement is much lower.
---
# SLEAC: Results
* Indicator classifications
* Can be used over wide areas to provide local indicators classifications with a map and a wide area estimate
* Ranked list of barriers
???
SLEAC provides coverage classification, a coverage map if applied over a wide area over multiple service areas and a ranked list of barriers /next slide
---
# SLEAC: Results
.pull-left[
Sierra Leone National Coverage Map produced by SLEAC
]
.pull-right[
Northern Nigeria coverage map produced by SLEAC
]
???
Here are examples outputs of coverage maps produced as an output of SLEAC surveys
---
# S3M
* **Simple spatial sampling method (S3M)** is a development of **CSAS** and uses a similar sampling design.
* The main difference is **S3M** uses a hexagonal grid (as compared to a square grid for **CSAS**).
* Hexagonal grids address the issue of unevenness of spatial sampling created by square grids particularly at scale
???
Simple spatial survey method or S3M is a development of CSAS and uses a similar sampling design. The main difference is that S3M uses a hexagonal grid (as compared to a square grid for CSAS). The hexagonal grid address the issue of spatial unevenness created by square grids particularly at scale.
---
# S3M: Results
.pull-left[
Coverage map of Wolayita Zone, Ethiopia produced by S3M
]
.pull-right[
Coverage map of Wollo Zone, Ethiopia produced by S3M
]
???
S3M provides the same set of results as CSAS but with coverage maps with much finer spatial resolution as shown in these examples.
---
# Coverage challenges
* Global CMAM coverage average is about 30%
* Coverage assessment fatigue (?)
* Same barriers and boosters are being identified
* Same low levels of coverage being achieved
* Better to act on what the current coverage assessments are saying about coverage to try to improve things before more coverage assessments are done
* Which barriers to focus on? Is there a **"magic bullet"**?
???
What now with coverage?
As of 4-5 years ago, global CMAM coverage is estimated to be around 30% based on results for programmes with which coverage assessments have been performed. It is likely that if all existing programmes are accounted for and assessed, this figure will even go lower.
Since then, the push for more coverage with CMAM has declined with lesser coverage surveys being performed compared to earlier and coverage was mainly being assessed within small programme areas despite continuous scaling up of CMAM in many countries.
There has been a general wait and see attitude from the key players and stakeholders of CMAM with a general sentiment being that there is an acceptance that current programming has poor coverage so better wait until the programmes get more mature and progress so that achievement in coverage can be shown. However, this thinking is inconsistent with what coverage assessment is mean to provide. The assessments should be seen as guide posts to facilitate the growing of the programme from early stage scale up with all its challenges and limitations and provide data and information on how to bring the programming to the next stage of improvement specifically on coverage. Without this, then programmes will be stabbing at the dark unaware of what their current coverage status is and how they can improve.
---
class: inverse, center, middle
# Questions?
---
class: inverse, center, middle
# Thank you!
This slide deck is available online at https://ernest.guevarra.io/coverageCMAM
A PDF copy of this slide deck is available to download from [here](https://github.com/ernestguevarra/coverageCMAM/raw/master/coverageCMAM.pdf)
This slide deck is also available as an R Markdown document from [here](https://github.com/ernestguevarra/coverageCMAM) which you can reproduce using R
</textarea>
<style data-target="print-only">@media screen {.remark-slide-container{display:block;}.remark-slide-scaler{box-shadow:none;}}</style>
<script src="https://remarkjs.com/downloads/remark-latest.min.js"></script>
<script>var slideshow = remark.create({
"highlightStyle": "github",
"highlightLines": true,
"countIncrementalSlides": false
});
if (window.HTMLWidgets) slideshow.on('afterShowSlide', function (slide) {
window.dispatchEvent(new Event('resize'));
});
(function(d) {
var s = d.createElement("style"), r = d.querySelector(".remark-slide-scaler");
if (!r) return;
s.type = "text/css"; s.innerHTML = "@page {size: " + r.style.width + " " + r.style.height +"; }";
d.head.appendChild(s);
})(document);
(function(d) {
var el = d.getElementsByClassName("remark-slides-area");
if (!el) return;
var slide, slides = slideshow.getSlides(), els = el[0].children;
for (var i = 1; i < slides.length; i++) {
slide = slides[i];
if (slide.properties.continued === "true" || slide.properties.count === "false") {
els[i - 1].className += ' has-continuation';
}
}
var s = d.createElement("style");
s.type = "text/css"; s.innerHTML = "@media print { .has-continuation { display: none; } }";
d.head.appendChild(s);
})(document);
// delete the temporary CSS (for displaying all slides initially) when the user
// starts to view slides
(function() {
var deleted = false;
slideshow.on('beforeShowSlide', function(slide) {
if (deleted) return;
var sheets = document.styleSheets, node;
for (var i = 0; i < sheets.length; i++) {
node = sheets[i].ownerNode;
if (node.dataset["target"] !== "print-only") continue;
node.parentNode.removeChild(node);
}
deleted = true;
});
})();
// add `data-at-shortcutkeys` attribute to <body> to resolve conflicts with JAWS
// screen reader (see PR #262)
(function(d) {
let res = {};
d.querySelectorAll('.remark-help-content table tr').forEach(tr => {
const t = tr.querySelector('td:nth-child(2)').innerText;
tr.querySelectorAll('td:first-child .key').forEach(key => {
const k = key.innerText;
if (/^[a-z]$/.test(k)) res[k] = t; // must be a single letter (key)
});
});
d.body.setAttribute('data-at-shortcutkeys', JSON.stringify(res));
})(document);
(function() {
"use strict"
// Replace <script> tags in slides area to make them executable
var scripts = document.querySelectorAll(
'.remark-slides-area .remark-slide-container script'
);
if (!scripts.length) return;
for (var i = 0; i < scripts.length; i++) {
var s = document.createElement('script');
var code = document.createTextNode(scripts[i].textContent);
s.appendChild(code);
var scriptAttrs = scripts[i].attributes;
for (var j = 0; j < scriptAttrs.length; j++) {
s.setAttribute(scriptAttrs[j].name, scriptAttrs[j].value);
}
scripts[i].parentElement.replaceChild(s, scripts[i]);
}
})();
(function() {
var links = document.getElementsByTagName('a');
for (var i = 0; i < links.length; i++) {
if (/^(https?:)?\/\//.test(links[i].getAttribute('href'))) {
links[i].target = '_blank';
}
}
})();
// adds .remark-code-has-line-highlighted class to <pre> parent elements
// of code chunks containing highlighted lines with class .remark-code-line-highlighted
(function(d) {
const hlines = d.querySelectorAll('.remark-code-line-highlighted');
const preParents = [];
const findPreParent = function(line, p = 0) {
if (p > 1) return null; // traverse up no further than grandparent
const el = line.parentElement;
return el.tagName === "PRE" ? el : findPreParent(el, ++p);
};
for (let line of hlines) {
let pre = findPreParent(line);
if (pre && !preParents.includes(pre)) preParents.push(pre);
}
preParents.forEach(p => p.classList.add("remark-code-has-line-highlighted"));
})(document);</script>
<script>
slideshow._releaseMath = function(el) {
var i, text, code, codes = el.getElementsByTagName('code');
for (i = 0; i < codes.length;) {
code = codes[i];
if (code.parentNode.tagName !== 'PRE' && code.childElementCount === 0) {
text = code.textContent;
if (/^\\\((.|\s)+\\\)$/.test(text) || /^\\\[(.|\s)+\\\]$/.test(text) ||
/^\$\$(.|\s)+\$\$$/.test(text) ||
/^\\begin\{([^}]+)\}(.|\s)+\\end\{[^}]+\}$/.test(text)) {
code.outerHTML = code.innerHTML; // remove <code></code>
continue;
}
}
i++;
}
};
slideshow._releaseMath(document);
</script>
<!-- dynamically load mathjax for compatibility with self-contained -->
<script>
(function () {
var script = document.createElement('script');
script.type = 'text/javascript';
script.src = 'https://mathjax.rstudio.com/latest/MathJax.js?config=TeX-MML-AM_CHTML';
if (location.protocol !== 'file:' && /^https?:/.test(script.src))
script.src = script.src.replace(/^https?:/, '');
document.getElementsByTagName('head')[0].appendChild(script);
})();
</script>
</body>
</html>