Artifacts
Every conformance resource and example this implementation guide defines — 151 artifacts. Filter by kind, or type to search names and descriptions.
ICR Administrative Coverage
ProfileAdministrative coverage: doses/treatments delivered ÷ planning denominator, computed from tallies. Carries denominator provenance and is permanently marked source=administrative.
ICR Adverse Event
ProfileAn adverse event following a campaign intervention — vaccine (AEFI) or MDA drug (pharmacovigilance) alike. The suspected product/event is referenced via suspectEntity; causality uses the WHO/CIOMS classification; seriousness/severity carry the minor-vs-serious distinction the field forms collect. Carries the required campaign-vs-routine record origin. Intervention-neutral so it serves both the immunization and MDA arms (working doc §17.2 C1).
ICR Campaign
ProfileA specific campaign execution — the keystone resource. Begins life as a microplan (intent=plan) and evolves into the execution record as Tasks complete and coverage accumulates. Rounds are sibling ICRCampaigns under an umbrella campaign via partOf (working doc §7.2, §6.3).
ICR Campaign Activity
ProfileA discrete work type within a campaign — 'administer albendazole to children 5–14', 'distribute ITNs to households' — instantiated as ICRCampaignTask resources (working doc §7.3).
ICR Campaign Protocol
ProfileThe reusable, version-controlled template for a campaign type — what a measles SIA *is* (products, age bands, activity sequence, coverage goals), instantiated by every execution in every country (working doc §7.1).
ICR Campaign Task
ProfileThe assignable, trackable operational unit of work — one Task per site-session (Type A, focus = the site Location) or per household (Type B, focus = the household Group). Tasks may be pre-planned from the microplan or field-registered on discovery (the required task-origin code records which). Whether Tasks are assigned at village or household level is a configuration choice (working doc §7.4).
ICR Care Team
ProfileThe campaign delivery team — the vaccinators/CDDs who do the work and the supervisor who oversees them and typically files the report. Referenced from ICRCampaign.careTeam (the roster) and Task.owner/Task.performer (the team that worked a Task); the supervisor surfaces again as the MeasureReport.reporter on rolled-up coverage and often owns the supervisory-area Location via the oversees-area extension. With workload-target it carries the microplan workload assigned to the team (working doc §5.5, §17.3).
ICR Consent (Person-Data Governance)
ProfileRecords the permission governing collection, storage, and cross-border sharing of a registered individual's (or a household's) campaign data. A v1 starting point: ICR holds named people (ICRPatient, §6.4), so a privacy/sharing permission and its scope are first-class. The grantor is typically the head of household or caregiver; the subject is the ICRPatient the data is about.
ICR Delivery Unit (Household / Community)
ProfileThe actual Group of people a campaign Task acts on — a household (Type B house-to-house), a community (Type C MDA), or a school cohort (school-based delivery), distinguished by the required group-kind code. The validated Group + Location pattern, generalized: the Group is who, the Location (group-location extension) is where it lives or is based — the dwelling for a household, the settlement or community point for a community, the school for a school cohort — with the Location carrying the Overture GERS ID for stable cross-campaign identity. Type A's delivery unit is a site, which is a Location, not a Group (working doc §3.2, §7.5, §9.1).
ICR Immunization Event
ProfileA vaccination delivery event: CVX-coded, with lot accountability and the required campaign-vs-routine record origin.
ICR Location
ProfileThe most-customized ICR resource: nested administrative hierarchy (6+ levels in campaign countries), operational geography linkable-but-distinct from admin units, GeoJSON boundaries, and multi-system geospatial identity — Overture Maps GERS IDs (building / place / division) as the preferred cross-campaign join key, with P-codes and national codes as coequal aliases (working doc §7.7, §9).
ICR Medication Administration
ProfileAn MDA treatment event: ATC-coded preventive chemotherapy with directly-observed consumption, dosage derived from a dose-pole height Observation, and the required record origin.
ICR Patient (Registered Individual)
ProfileAn individual person registered in a campaign — a household or community member, and the subject of every person-level delivery event. Person registration is a mainline capture mode in community-and-household campaigns, not an exception. Base R4 Patient aligned to WHO IMMZ.Patient (required gender/birthDate; MS name/phone/address), with a sliced cross-campaign identifier (national ID preferred, registry-assigned ID as fallback) so the same person is rejoinable across rounds. A person need not belong to any Group: they may be a household member, a community member, or simply the patient/subject of a standalone event. The caregiver is a RelatedPerson (WHO IMMZ.Caregiver), not an ICRPatient (working doc §6.4).
ICR Supervision Report
ProfileA STRUCTURED supervision-visit / QA record (ESPEN Forms 5 health-facility and 6 CDD-observation): a QuestionnaireResponse against the icr-mda-supervision-checklist Questionnaire, so each checklist answer (supplies present, DOC observed, height-chart used correctly, stock concordance, population informed, channels used…) links to a defined, coded question. Subject is the supervised area/community; author is the supervising ICRCareTeam. Replaces the v0.19 lightweight text-component Observation (working doc §17.3).
ICR Supply Delivery
ProfileA commodity distribution event — ITNs, IRS consumables, vitamin A capsules — GS1 GTIN-coded where applicable, with the required record origin.
ICR Survey Coverage
ProfileIndependently-measured coverage — post-campaign cluster survey, LQAS, or RCM — with method, sample design, and date. A separately-sourced, first-class measure of the same quantity as administrative coverage: the two routinely diverge (Cuamba, Mozambique: ~99% admin vs ~76% survey) and must never be collapsed.
ICR Target Population
ProfileA target-population denominator: a conceptual cohort (actual=false) with a count, eligibility characteristics, and — critically — source and date provenance. Multiple competing estimates per geography are retained; exactly one is flagged as the planning denominator (working doc §7.6, §4.2).
Campaign Round
ExtensionRound number of this campaign execution. Each round is its own CarePlan instantiating the same protocol, linked to an umbrella campaign via CarePlan.partOf (working doc §6.3).
Coverage Source
ExtensionThe measurement lineage of this coverage report: administrative vs survey/LQAS/RCM. The two lineages routinely diverge (Cuamba: ~99% admin vs ~76% survey) and must never be merged (working doc §4.1).
Coverage Unit
ExtensionWhat the coverage figure counts: people, or implementation units (villages/areas = geographic coverage). Absent ⇒ people (espen-v3 / §17.2 B1).
Delivery Strategy
ExtensionHow this activity/site/task reaches its target population. First-class and coded because a single campaign routinely mixes strategies, and the strategy governs which data elements exist (working doc §3).
Denominator Source
ExtensionThe method/source behind this population estimate (census, microcensus, WorldPop, GRID3…). Reuse is only safe with provenance (working doc §2.3, §4.2).
Denominator Type
ExtensionWhether the denominator is the TOTAL population or the AT-RISK/eligible subset — programme vs epidemiological coverage in NTD MDA. On a coverage MeasureReport it qualifies the figure; on an ICRTargetPopulation it labels the estimate (espen-v3 / §17.2 B1).
Directly Observed Consumption
ExtensionWhether the community drug distributor physically observed the individual swallow the medication (MDA DOC protocol).
Dose-pole Band
ExtensionThe measured dose-pole height band that determined the tablet count for a PC-NTD treatment — makes the height-band → dose logic machine-readable rather than buried in dosage.text. Bands are drug-specific; coded extensibly (espen-v3 minor-issue).
Eligible Persons Absent
ExtensionNumber of eligible persons absent at the visit(s) — feeds same-day mop-up lists. Program-neutral counterpart of eligible-present.
Eligible Persons Present
ExtensionNumber of eligible persons — per the campaign protocol's target definition — present at the visit(s). Program-neutral by design: children under 5 for polio, household members for ITN registration, the eligible age band for MDA or vitamin A.
Estimate Confidence
ExtensionFree-text or coded confidence qualifier on a population estimate.
Estimate Date
ExtensionWhen this population estimate was made. Denominators decay fast (1–3 years); a stale denominator silently reused produces confident, wrong coverage.
Exclusion Reason
ExtensionWhy a present, age-eligible person was clinically excluded from the intervention this round (under dose-pole height/age, pregnant, breastfeeding, acutely ill). Distinct from missed (not reached) and noncompliance (declined): the person was there and age-eligible but contraindicated. MDA treatment forms tally these per drug (espen.md rec 2 / §17.4).
Finger Marked
ExtensionWhether the child was finger-marked — the in-field 'already covered' flag of house-to-house campaigns.
Group Location
ExtensionThe physical Location of a delivery-unit Group — the validated Ona pattern: Group (who) + Location (where). For a household the Location is the dwelling (carrying the GERS building ID); for a community it is the settlement or community point; for a school cohort it is the school. This is the group's RESIDENCE/BASE, not its service point: where service actually happened is Task.location and the delivery event's own location — a household served at a village distribution center keeps its dwelling here unchanged (working doc §7.5, §9.1).
Houses Visited
ExtensionNumber of houses visited — aggregate output of a house-to-house task.
Is Planning Denominator
ExtensionTrue when this estimate is the one flagged as the campaign's planning denominator among competing estimates for the same geography.
Location Boundary (GeoJSON)
ExtensionBoundary geometry for a Location — district polygons, settlement areas, catchment zones — as a GeoJSON attachment. R4 extension mirroring the R5 standard boundary extension; alignment path is working doc §10 question 6.
Missed Reason
ExtensionWhy eligible person(s) were missed at this visit. House-to-house campaigns produce this natively (working doc §3.1).
Noncompliance Reason
ExtensionWhy the household/caregiver declined — drives social mobilization and mop-up targeting.
Overlays Admin Unit
ExtensionLinks an operational-geography Location (supervisory area, operational area) to the administrative unit(s) it overlays. Operational ≠ administrative geography: partOf can only express one hierarchy, so this extension is what makes operational areas linkable-but-distinct rather than just distinct (working doc §9, identity principle 3).
Oversees Area
ExtensionThe supervisory/operational-area Location(s) a CareTeam's supervisor covers — ties the team to operational geography (working doc §5.5, §6.3).
Planning Denominator
ExtensionThe target-population Group flagged as this campaign's planning denominator. Multiple competing estimates may exist per geography; exactly one is the planning denominator (working doc §4.2).
Prior-dose Status (Zero-dose)
ExtensionThe person's prior-dose status for this antigen at the time of the campaign contact: zero-dose (never received before), previously-received, or no-recall. The per-event carrier of the polio SIA tally's never/previously/no-recall split; aggregates to the dose-history coverage stratifier and feeds zero-dose reach / dropout measures. Distinct from Immunization.protocolApplied.doseNumber, which counts this series' doses, not prior status of the antigen (forms-v1 / jul3-form-analysis §Aggregate #1).
Real-time vs Reconciled
ExtensionData lineage of this record: the real-time operational stream or the post-campaign reconciled stream. One structure serves both; consumers filter by lineage — dashboards read realtime, JAP exports read reconciled (working doc §4.3). Default semantics: ABSENT MEANS REALTIME — live-stream records may omit the flag, but reconciled records must carry it, and coverage MeasureReports always carry it (1..1 on both coverage profiles).
Record Origin
ExtensionWhether this delivery event was recorded during a campaign or a routine facility visit. REQUIRED on all ICR delivery-event profiles — without it, SIA doses contaminate routine coverage analytics (working doc §4.4). Also valid on AdverseEvent so a campaign-context AEFI/side-effect stays separable from routine pharmacovigilance (v0.19.0).
Revisit Outcome
ExtensionOutcome of a follow-up revisit to a previously-missed household/person (already-vaccinated | vaccinated-on-revisit | still-missing) — the 'outcome of the revisit' of the missed-children recording forms. Set on the person-targeted follow-up Task (Task.for = Patient, Task.focus = the originating Task that missed them) (forms-v1 / jul3-form-analysis §Aggregate #4).
Sample Design
ExtensionSample design / method detail of an independently-measured coverage estimate — e.g. 'WHO 30×10 cluster survey, district-representative', LQAS lot definition, RCM site-selection note. Survey coverage without its design is uninterpretable (working doc §4.1).
Serious-Event Criteria
ExtensionWhy an adverse event is serious — the WHO/CIOMS criterion/criteria behind AdverseEvent.seriousness = serious (death, life-threatening, hospitalization, disability, congenital anomaly, other medically important) (espen-v4 / §17.2 C1).
Settlement / Special-population Type
ExtensionThe settlement or special-population classification of a place (urban / rural / slum / refugee-IDP / nomad-pastoralist / security-compromised / hard-to-reach / cross-border / immigrant) — the recurring 'type of settlement' axis on the polio SIA monitoring/tally forms. A vulnerability/equity attribute of a Location that drives hard-to-reach-area targeting and equity disaggregation (forms-v1 / jul3-form-analysis §Aggregate #5).
Social Mobilization
ExtensionDemand-generation for a campaign/round: whether the population was informed beforehand and the channels used (ESPEN supervision Form 5). The demand axis of §17.3 (espen-v4).
Stock Accountability
ExtensionVial/commodity accountability and wastage on a supply event — received / used / remaining / not-usable (expired/damaged) / returned, plus physical-vs-theoretical concordance and (vaccines) the VVM stage. Reusable for vaccines, drugs and ITNs; the ESPEN supervision Form 5 stock block (espen-v4 / §17.2 C2).
Target Geography
ExtensionThe geography (admin unit or operational area) this campaign targets.
Task Origin
ExtensionWhether this Task was generated in advance from the microplan or registered in the field on discovery. REQUIRED on ICRCampaignTask — field-registered counts per area measure how incomplete the microplan's enumeration was, feeding the next round's denominators (working doc §10 q1).
Workload Target
ExtensionThe microplan workload assigned to a CareTeam — the area(s) it covers and the expected volume (population / households / days). With oversees-area, makes the CareTeam the typed team-area-workload unit of the microplan (the ICRCampaign with intent=plan is the microplan itself) (espen-v4 / §17.3).
ICR Adverse Event Causality
Value SetWHO/CIOMS causality categories. Binding: extensible on ICRAdverseEvent causality assessment.
ICR Adverse Event Seriousness
Value SetSerious vs non-serious. Binding: extensible on ICRAdverseEvent.seriousness — uses the HL7 adverse-event-seriousness code system.
ICR Campaign Type
Value SetCampaign types by delivery model. Binding: required on ICRCampaignProtocol.type and ICRCampaign.category.
ICR Communication Channel
Value SetSocial-mobilization channels. Binding: extensible on the social-mobilization extension's channel.
ICR Coverage Source
Value SetAll coverage measurement lineages.
ICR Coverage Stratifier
Value SetStandard coverage disaggregation axes. Binding: extensible on the Measure/MeasureReport stratifier code (espen-v3 / §17.2 B1).
ICR Coverage Unit
Value SetPeople vs implementation-units (geographic coverage). Binding: required on the coverage-unit extension.
ICR Data Lineage
Value SetReal-time vs reconciled lineage. Binding: required on the realtime-vs-reconciled extension.
ICR Delivery Strategy
Value SetDelivery strategies. Binding: required on the delivery-strategy extension.
ICR Denominator Source
Value SetSources of population denominators. Binding: extensible.
ICR Denominator Type
Value SetTotal-population vs at-risk/eligible denominator. Binding: required on the denominator-type extension.
ICR Dose History / Zero-dose Status
Value SetPrior-dose status (zero-dose / previously-received / no-recall). Binding: required on the prior-dose-status extension; also the value space of the dose-history coverage stratifier (forms-v1).
ICR Exclusion Reason
Value SetReasons a present, age-eligible person was clinically excluded from treatment (under-height/age, pregnant, breastfeeding, acutely ill). Binding: extensible — countries may add local codes.
ICR Group Kind
Value SetDelivery-unit Group kinds (household / community). Binding: required on ICRDeliveryUnit.code.
ICR Independent Coverage Source
Value SetIndependently-measured coverage lineages only (survey / LQAS / RCM) — the ICRSurveyCoverage binding.
ICR Location Type
Value SetCampaign-relevant location types, including operational geography. Binding: extensible on ICRLocation.type — countries may add local types.
ICR MDA Medication
Value SetWHO ATC-coded preventive-chemotherapy medications. Binding: extensible — local formulary codes map back via ConceptMap. Includes the full ATC system; typical PC-NTD codes are albendazole P02CA03, ivermectin P02CA01, praziquantel P02BA01, azithromycin J01FA10, diethylcarbamazine P02CB02. Restricting to a PC-NTD subtree is deferred until country formularies are reviewed.
ICR Missed Reason
Value SetReasons an eligible person/household was missed. Binding: extensible — countries may add local codes.
ICR Noncompliance Reason
Value SetReasons for refusal/noncompliance. Binding: extensible — countries may add local codes.
ICR Record Origin
Value SetCampaign vs routine record origin. Binding: required on the record-origin extension.
ICR Revisit Outcome
Value SetOutcome of a follow-up revisit (already-vaccinated / vaccinated-on-revisit / still-missing). Binding: extensible on the revisit-outcome extension (forms-v1).
ICR Serious-Event Criteria
Value SetWHO/CIOMS serious-event criteria. Binding: extensible on the serious-criteria extension.
ICR Settlement / Special-population Type
Value SetSettlement / special-population classification of a Location. Binding: extensible on the settlement-type extension — countries add local codes (forms-v1).
ICR Supplied Item
Value SetCoded products distributed via ICRSupplyDelivery. Binding: extensible. Drug commodities (MDA receipts/distribution) use WHO ATC; physical commodities (ITNs, IRS consumables, vitamin A) use GS1 GTIN where a local binding exists, otherwise text. Added v0.18.0 (espen.md rec 3) so a drug receipt → administration → reconciliation share one ATC code.
ICR Task Origin
Value SetPre-planned vs field-registered task origin. Binding: required on the task-origin extension.
ICR Team Role
Value SetCampaign CareTeam member roles. Binding: extensible on ICRCareTeam.participant.role.
ICR Adverse Event Causality
Code SystemWHO/CIOMS causality classification of an adverse event following an intervention — intervention-neutral: covers AEFI (immunization) and MDA drug pharmacovigilance alike. Top-level WHO categories; immunization implementations may use WHO IMMZ.AdverseEvent's finer A1–A4 subtypes (espen-v3 / §17.2 C1).
ICR Campaign Type
Code SystemThe type of public health campaign, grouped by delivery model rather than disease (working doc §3).
ICR Communication Channel
Code SystemSocial-mobilization / demand-generation channels used to inform the population ahead of and during a campaign (ESPEN supervision Form 5). Bound extensible (espen-v4 / §17.3).
ICR Coverage Source
Code SystemThe measurement lineage of a coverage figure. Administrative and independently-measured coverage are separately-sourced, first-class measures of the same conceptual quantity and must never be collapsed (working doc §4.1).
ICR Coverage Stratifier
Code SystemThe standard disaggregation axes a coverage MeasureReport stratifies by (and a Measure declares). Formalises the v0.18.0 stratified-tally pattern into a named contract (espen-v3 / §17.2 B1).
ICR Coverage Unit
Code SystemWhat is being counted in a coverage figure: people, or implementation units. Implementation-unit coverage is geographic coverage — villages/areas treated ÷ total (ESPEN supervision Form 5; espen-v3 / §17.2 B1).
ICR Data Lineage
Code SystemWhether a record belongs to the real-time operational stream or the post-campaign reconciled stream. One structure serves both; consumers filter by lineage (working doc §4.3).
ICR Delivery Strategy
Code SystemHow a campaign activity reaches its target population. A first-class, coded attribute of every campaign activity, site, and task — campaigns routinely mix strategies, and the available data elements change with the strategy (working doc §3).
ICR Denominator Source
Code SystemThe method/source behind a target-population estimate. Every estimate carries its source and date — the denominator is the dominant source of error in campaign analytics (working doc §4.2).
ICR Denominator Type
Code SystemWhether a coverage figure (or a target-population estimate) is measured against the TOTAL population or the AT-RISK/eligible subset — the difference between programme coverage and epidemiological coverage in NTD MDA (espen-v3 / §17.2 B1).
ICR Dose History / Zero-dose Status
Code SystemA person's prior-dose status for the campaign antigen, at the time of a campaign contact — the polio SIA tally's core split (never received / previously received / no recall) and the zero-dose vs not-zero-dose axis. Carried per event by the prior-dose-status extension and aggregated as the dose-history coverage stratifier; feeds zero-dose reach and the proposed dropout/fully-immunized measures (forms-v1 / jul3-form-analysis §Aggregate #1).
ICR Exclusion Reason
Code SystemWhy a PRESENT, age-eligible person was not treated because they are clinically ineligible/contraindicated for the intervention this round — as opposed to being MISSED (not reached, ICRMissedReasonCS) or DECLINING (ICRNoncomplianceReasonCS). The MDA case (ESPEN treatment Form 3): under the dose-pole minimum, pregnant, breastfeeding, acutely ill. Added v0.18.0 (espen.md rec 2 / §17.4 NTD specifics).
ICR Group Characteristic
Code SystemCharacteristic codes for ICR Group profiles — currently the geographic-scope characteristic that links a target-population estimate to its Location, making estimates computably joinable to the location hierarchy (working doc §7.6).
ICR Group Kind
Code SystemThe kind of delivery-unit Group a campaign Task acts on. Households (Type B house-to-house) and communities (Type C MDA) share the same Group + Location pattern; this code distinguishes them (working doc §3.2, §7.5).
ICR Location Type
Code SystemCampaign-relevant location types, including operational geography (supervisory and operational areas) as linkable-but-distinct from the administrative hierarchy (working doc §9).
ICR Missed Reason
Code SystemWhy an eligible person or household was not reached during a campaign visit.
ICR Noncompliance Reason
Code SystemWhy a household or caregiver declined the intervention — drives social-mobilization targeting and mop-up planning.
ICR Record Origin
Code SystemWhether a delivery event originated in a campaign or a routine facility visit. Required on every ICR delivery event so SIA doses never contaminate routine coverage analytics, and routine history observed during campaigns stays analyzable (working doc §4.4).
ICR Revisit Outcome
Code SystemThe outcome of a follow-up visit to a household/person previously missed — the 'outcome of the revisit' block of the missed-children recording forms. Carried on the follow-up Task via the revisit-outcome extension (forms-v1 / jul3-form-analysis §Aggregate #4).
ICR Serious-Event Criteria
Code SystemWHO/CIOMS criteria that make an adverse event SERIOUS — the reason behind AdverseEvent.seriousness = serious. Intervention-neutral (AEFI and MDA pharmacovigilance) (espen-v4 / §17.2 C1).
ICR Settlement / Special-population Type
Code SystemThe settlement or special-population classification of a place — the recurring 'type of settlement' axis on the polio SIA monitoring/tally forms (urban / rural / slum / refugee-IDP / nomad-pastoralist / security-compromised / hard-to-reach / cross-border / immigrant). A vulnerability/equity attribute of a Location, carried by the settlement-type extension; drives hard-to-reach-area (HTRA) targeting and equity disaggregation (forms-v1 / jul3-form-analysis §Aggregate #5). Bound extensible — countries add local codes.
ICR Task Origin
Code SystemWhether a campaign Task was generated in advance from the microplan or registered in the field on discovery. Field-registered counts per area measure how incomplete the microplan's enumeration was — input to the next round's denominators (working doc §10 q1).
ICR Team Role
Code SystemRole of a member within a campaign CareTeam — the front-line delivery and supervision roles (working doc §5.5). Bound extensible: countries add local roles. Supervisor *level* (national/regional/district/partner/health-facility, ESPEN Forms 5/6) is carried by managingOrganization or the overseen area, not multiplied into roles.
ICR ↔ WHO IMMZ AEFI Causality
Concept MapMaps ICRAdverseEventCausalityCS (WHO/CIOMS A/B/C/D) to the WHO SMART Immunizations AEFI causality categories. Provisional — target codes to be confirmed against the published IMMZ IG (§18.3).
ICR Campaign Readiness Checklist
QuestionnaireStructured pre-campaign readiness/preparedness validation at operational level (UNICEF Preparedness Validation form), grouped: microplan, cold chain & logistics, social mobilization, trainings. Representative items, not the full instrument; countries extend (forms-v1).
ICR MDA Supervision Checklist
QuestionnaireStructured supervision checklist for community-directed MDA (ESPEN Forms 5 & 6), grouped: supplies, CDD observation, stock & wastage, social mobilization.
ICR Administrative Coverage Measure
MeasureDoses/treatments delivered ÷ planning denominator, from tallies. Disaggregable by sex, age band, delivery strategy and geography.
ICR Campaign Readiness Measure
MeasurePre-campaign readiness: operational units (wards/facilities) validated ready ÷ total targeted, from the readiness checklist (coverage-unit = implementation-units). Turns the UNICEF Preparedness Validation form into a roll-up readiness measure, stratified by readiness domain (microplan | cold-chain | social-mobilization | trainings). Placeholder CQL pending executable logic (forms-v1 / jul3-form-analysis §Aggregate #2).
ICR Geographic Coverage Measure
MeasureImplementation-unit coverage: settlements/areas treated ÷ total targeted (coverage-unit = implementation-units). The ESPEN supervision-form 'villages treated / total' figure, with non-treatment reasons as a stratifier.
ICR MDA Treatment Coverage Measure
MeasurePC-NTD treatment coverage: persons treated ÷ at-risk/eligible population, disaggregated by sex, age band and treatment disposition (treated vs not-treated reason). The Measure behind the ESPEN treatment-form tally.
ICR Survey Coverage Measure
MeasureIndependently-measured coverage (cluster survey / LQAS / RCM). A separately-sourced measure of the same quantity as administrative coverage; the two routinely diverge and must never be merged.
ICR Zero-dose Coverage Measure
MeasureZero-dose children reached in the round ÷ children reached, disaggregated by prior-dose status (dose-history). Turns the polio SIA tally's never/previously/no-recall split into a first-class measure of how many zero-dose children a campaign reaches — the equity signal behind zero-dose reduction. Placeholder CQL pending executable logic (forms-v1 / jul3-form-analysis §Aggregate #1).