Integrated Campaign Registry (ICR) Implementation Guideunicef.fhir.icr · v0.1.0 · FHIR 4.0.1
Draft — this implementation guide is a working snapshot (v0.1.0) and its content may change without notice.

Home

Official URL: https://fhir.icr.unicef.org/ImplementationGuide/unicef.fhir.icr Version: 0.1.0
Draft as of 2026-07-03 Computable Name: ICR

Integrated Campaign Registry (ICR) Implementation Guide

Public health campaigns — measles–rubella SIAs, polio rounds, NTD mass drug administration, malaria ITN/IRS, vitamin A supplementation — repeatedly target the same communities and the same beneficiaries, yet each program re-maps the same villages, re-registers the same households, and re-estimates the same denominators every round. The ICR inverts this: each campaign becomes a contributor to a cumulative, reusable corpus of public health intelligence, so that data collection cost compounds across programs and over time.

This Implementation Guide is the "DNA" of that registry. It defines how campaign semantics — protocols, microplans, denominators, households, delivery events, coverage — are expressed in HL7 FHIR R4, so that interchangeable open-source components (data collection, transformation, FHIR store, data quality, geospatial microplanning, analytics) can share one model.

The architecture in one paragraph

FHIR has no native Campaign resource, so the IG profiles existing resources — the same community-validated approach used for households (Group + Location). CarePlan is the keystone: ICRCampaignProtocol (PlanDefinition) is the reusable campaign protocol; ICRCampaign (CarePlan) is a specific execution that begins as a microplan and evolves into the execution record; ICRCampaignTask (Task) is the operational unit — one per site-session or per household — carrying the coded delivery strategy and house-to-house data elements natively; delivery events hang off Task.output as ICRImmunizationEvent, ICRMedicationAdministration, or ICRSupplyDelivery, each permanently flagged campaign vs routine (record-origin). ICRDeliveryUnit (Group — a household or a community, the generalized Group + Location pattern) and ICRTargetPopulation (Group) carry people and denominators — every estimate with source, date provenance, and a computable geographic scope — and ICRLocation carries the administrative hierarchy and geospatial identity, with Overture Maps GERS IDs as the cross-campaign join key alongside P-codes and national codes. Administrative and survey coverage are separate, never-merged lineages (ICRAdministrativeCoverage, ICRSurveyCoverage).

Status

This is the v0.1 draft produced in Phase 1 of the ICR project (UNICEF; Ona prime, Crosscut partner). It encodes the design rationale of the ICR working design document (ICR FHIR Implementation Guide — Campaign Data Model & Structure); see Background for the design decisions and open questions. It will be revised against real campaign datasets (data conformance testing) and FHIR community review (chat.fhir.org, working-group calls, Connectathons) before pilot use.

Planned for subsequent drafts: SQL-on-FHIR ViewDefinition resources (the portable analytics layer), ConceptMap scaffolds for country code localization, Consent guidance, and Measure definitions aligned to WHO JAP / ICG / ESPEN reporting minimums.