Understanding why the gap exists and how to close it requires looking at IDSR not just as a technical framework but as a systems intervention. The framework itself is sound. The system conditions required for it to function are frequently absent.
What IDSR Is Designed to Do
The IDSR framework, first developed by WHO AFRO in 1998 and revised substantially in 2010 and 2019, provides a standardised approach to disease surveillance and response for district health systems across Africa. Its core design principle is integration: rather than parallel vertical surveillance systems for each disease, IDSR consolidates surveillance functions into a single, multi-disease system operating through existing health infrastructure.
The framework operates across three levels:
- Health facility level: Detection, recording, and reporting of cases meeting priority disease case definitions
- District (LGA) level: Aggregation of facility reports, analysis for outbreak signals, investigation of alerts, and coordination of immediate response
- National level: Aggregation of district data, epidemiological analysis, coordination of major outbreak response, and reporting to WHO under IHR obligations
IDSR designates approximately 50 priority diseases and conditions including cholera, meningitis, measles, yellow fever, and viral haemorrhagic fevers with standardised case definitions, reporting thresholds, and response protocols for each. The standardisation is what makes the framework work at scale: a suspected cholera case in Sokoto and a suspected cholera case in Imo State are detected and reported using the same criteria, enabling national-level pattern recognition.
The IDSR Reporting Chain
In functional form, the IDSR reporting chain works as follows:
- A health worker at a primary health care facility identifies a patient meeting the case definition for a priority disease.
- The case is recorded in the facility disease register and reported to the LGA Disease Surveillance and Notification Officer (DSNO) immediately for epidemic-prone diseases, within 24 hours for urgent conditions, and in the weekly facility report for routine diseases.
- The LGA DSNO aggregates facility reports, identifies any that meet the district-level alert threshold, and initiates an investigation if the threshold is crossed.
- The DSNO completes an investigation report using the standard case investigation form, collects specimens if indicated, and notifies the State Epidemiologist.
- The State Epidemiologist reviews investigation findings, coordinates laboratory specimen transport, and reports confirmed outbreaks to the national level.
- The national level receives state reports through DHIS2, generates national surveillance data, and reports to WHO under IHR obligations.
This chain is designed to move a suspected case from facility detection to national visibility in under 48 hours for epidemic-prone diseases. In practice, in the surveillance systems I have worked within across Nigeria, the median time from detection to national notification is considerably longer and the gap is not in the framework design. It is in the system conditions at each link in the chain.
Where the System Breaks Down
Link 1: Case Definition Application at Facility Level
The IDSR case definitions are technically correct. They are also written for epidemiologists, not for community health extension workers managing 60 patients a day in a facility with no laboratory access. When case definitions cannot be reliably applied at the point of first patient contact, cases are missed before they ever enter the reporting chain. This is the foundational failure from which all downstream gaps follow.
The fix requires translating case definitions into facility-level screening algorithms a maximum of three criteria that a health worker can apply in under 60 seconds. This is not a compromise of epidemiological rigour; it is a design adaptation that makes rigour achievable in operational conditions. See Outbreak Surveillance Mistakes for a detailed treatment of this failure mode.
Link 2: DSNO Capacity and Coverage
The LGA DSNO is the most critical node in the IDSR system and the most frequently under-resourced. In Nigeria's 774 LGAs, DSNO positions are filled inconsistently, turnover is high, and the combination of reporting responsibilities, investigation duties, and coordination functions frequently exceeds one person's capacity.
A DSNO who is responsible for 60 facilities, receives weekly reports from 40 of them, and is expected to investigate every alert threshold crossing while also producing weekly state reports is structurally set up to fail regardless of competence. The IDSR framework is designed for the position; the resource allocation must match the position's demands.
Link 3: Specimen Transport and Laboratory Turnaround
Laboratory confirmation is where the signal chain most frequently stalls. Specimens collected during investigation must reach a reference laboratory with the cold chain intact, be processed within a timeframe relevant to the response decision, and have results communicated back to the investigating team before investigation closure.
In practice, specimens frequently arrive at laboratories outside cold chain conditions, laboratory processing queues extend beyond the response window, and results are communicated by telephone rather than through the surveillance system creating a gap between the clinical and laboratory data that undermines the integrity of the case classification record. For strategies to manage this gap, see Real-Time Disease Surveillance in the Digital Era.
Link 4: Feedback to the Reporting Level
IDSR is designed as a bidirectional system: data flows up through the reporting chain, and feedback investigation findings, response recommendations, programme performance data flows back down. In practice, most IDSR implementations function as unidirectional reporting systems. Data flows up. Feedback rarely reaches facility level.
The consequence is predictable: facility health workers who never receive feedback on the cases they report have no mechanism to learn whether their case identification was accurate, whether the investigation confirmed their suspicion, or whether the programme they are contributing to is working. Over time, this erodes the sense of purpose that motivates careful reporting a surveillance motivation failure that is structural, not individual.
IDSR and IHR: The National Obligations Connection
The International Health Regulations (2005) require WHO member states to detect, assess, notify, and respond to public health events of potential international concern. IDSR is the primary operational framework through which African member states fulfil IHR notification obligations for event-based surveillance.
The connection matters for two reasons. First, it establishes that IDSR failures have international consequences gaps in national surveillance capacity become gaps in the global early warning system for emerging infectious diseases. Second, it provides a legal and normative framework that can be invoked to secure political and financial commitment for IDSR strengthening at national level.
IHR's Joint External Evaluation (JEE) and the Africa CDC's State Party Self-Assessment Annual Reporting (SPAR) tool both assess IHR core capacities, including surveillance and response. Countries with weak IDSR implementation consistently score poorly on these assessments producing evidence of the gap that can be used to mobilise resources and accountability.
Digital Tools and IDSR: Enabling and Complicating
Digital surveillance tools DHIS2, SORMAS, community surveillance applications have transformed the speed and granularity of IDSR-aligned surveillance where they are well-implemented. Case data that previously moved through the reporting chain by paper form and telephone can now reach national level in real time. Dashboards that previously required manual data compilation can now update automatically as facilities report.
But digital tools introduce dependencies that paper-based systems do not. A paper form works with no power and no network. A DHIS2-based system requires connectivity, device maintenance, user account management, and system administration all of which require resources and capacity that are not uniformly available across the 774 LGAs of Nigeria.
The design principle for IDSR-aligned digital surveillance is resilience: the system should function with digital tools where connectivity and capacity support them, and should fall back to paper-based reporting when digital conditions are not met without creating a gap in the surveillance chain. Parallel paper and digital systems are not duplicative; they are redundant by design.
For a detailed treatment of digital surveillance architecture, see DHIS2 Tracker Configuration for Outbreak Surveillance and Real-Time Disease Surveillance in the Digital Era.
Making IDSR Work: A Systems Strengthening Framework
IDSR strengthening that focuses on training and guidelines without addressing the system conditions that determine whether trained people can apply guidelines is incomplete. Effective IDSR strengthening operates on four levels simultaneously:
1. Detection Capacity at Facility Level
Field-adapted case definition tools. Community surveillance integration. Zero-reporting enforcement. Feedback mechanisms that connect facility health workers to the programme outcomes they contribute to.
2. Investigation Capacity at District Level
Adequate DSNO staffing relative to the number of facilities covered. Pre-positioned investigation kits. Standard investigation forms that can be completed offline. Clear escalation protocols with defined timelines.
3. Laboratory Integration
Cold chain infrastructure for specimen transport. Defined specimen-to-result turnaround time standards. Electronic result reporting that feeds back into the surveillance record. Clearly defined trigger points at which response begins without waiting for laboratory confirmation.
4. Data Use at Every Level
Dashboards designed around the decisions of each user group. Regular surveillance data review meetings with defined action protocols. Programme performance data timeliness, completeness, investigation rates measured and discussed alongside case counts. See DHIS2 Dashboard Best Practices for the design principles that make this work.
The Integrated Surveillance Dividend
The reason integration matters the reason IDSR was designed around integration rather than parallel disease-specific systems is efficiency and coherence. A health worker who understands the IDSR reporting system can report cholera, measles, and meningitis through the same process. A DSNO who manages one integrated surveillance system serves more diseases with less administrative burden than one who manages five parallel reporting lines.
And when multiple disease programmes share infrastructure the same reporting tools, the same health worker networks, the same laboratory systems, the same data management platforms investment in that infrastructure benefits every programme simultaneously. This is the integration dividend that justified the IDSR architecture in the first place.
Realising that dividend requires building the shared infrastructure first, and then populating it with disease-specific content not designing each disease programme independently and then trying to integrate them after the fact. The sequence matters as much as the design.