Control Component Compliance
Audit reported completion of caller-defined integrated parasite-control components.
Description
A control programme checklist compares required components with reported completions.
A control programme checklist compares required components with reported completions. The completion percentage counts only required components.
The tool returns missingComponents (missing components); compliancePercent (compliance percent); complete (complete). Input measurements and model parameters are supplied by the caller; the tool computes the stated summary rather than acquiring those measurements.
When to use Control Component Compliance
Use Control Component Compliance when you already have requiredComponents, completedComponents and want missingComponents, compliancePercent, complete. This is useful for checking a supplied calculation, documenting a measurement convention, or comparing observations prepared on the same basis.
How to use Control Component Compliance and understand its results
- Enter requiredComponents, completedComponents using the field table below. Match the units, ordering and data boundaries described in the calculation.
- Run the tool after checking the stated bounds and matching paired observations or categories. A malformed request gives a tool error rather than a usable measurement.
- Read missingComponents, compliancePercent, complete. Use the calculation and interpretation below to distinguish amounts, ratios, signs and decision flags where applicable.
- Review the supplied parameters and assumptions before using the result in a report or comparing it with another observation.
| Input field | Meaning | Value type and bounds | Requirement |
|---|---|---|---|
| requiredComponents | Required components | list of string | Required |
| completedComponents | Completed components | list of string | Required |
Require a distinct nonempty required list, deduplicate completions, and list missing required components. Extra completed labels do not increase the percentage.
completion% = 100 × completedRequired/requiredCount; complete = missingCount = 0 The symbols refer to the supplied quantities or generated values described above; unit conversions and comparison boundaries follow the stated implementation.
{
"input": {
"requiredComponents": [
"nets",
"surveillance",
"treatment"
],
"completedComponents": [
"nets",
"treatment"
]
},
"output": {
"missingComponents": [
"surveillance"
],
"compliancePercent": 66.66666666666667,
"complete": false
}
}Limitations and assumptions
Labels are compared exactly. Checklist completion does not establish the effectiveness or quality of each intervention.
Numerical inputs must be finite. The tool checks its declared input shape and calculation constraints; those checks do not verify the quality, calibration or representativeness of the supplied observations.
Alternative or Complementary methods
Morbidity Register Summary: Deduplicate a morbidity register and tally unique patients by reported condition code. Therapeutic Geographic Coverage Gap: Compare person-level therapeutic coverage with area-level geographic coverage.
Methodological background: Monitoring drug coverage for preventive chemotherapy.1
References
-
Monitoring drug coverage for preventive chemotherapy — World Health Organization
Similar or alternative tools
- Morbidity Register Summary
Deduplicate a morbidity register and tally unique patients by reported condition code.
- Therapeutic Geographic Coverage Gap
Compare person-level therapeutic coverage with area-level geographic coverage.