Significance
30 measured / 30 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 30 events
Connected Situation / Through 2026-10-24
Nigeria Ebola Case and Regional Public-Health Response
- stories
- 53
- events
- 30
- entities
- 150
- connections
- 53
Evidence so far on 2026-10-24 UTC · updated 2026-10-24 21:26 UTC · analysis as of 2026-10-23 21:28 UTCSign in for the live Situation ↗
Narrative
As-of analysis
Situation at a glance
On 20 October, the Federal Government of Nigeria activated an Ebola response after confirming an imported case. The 22 October headline “Nigeria identifies first Ebola patient as diplomat’s wife who holidayed in Uganda” identifies the patient as a diplomat’s wife and links her reported travel to Uganda. On 21 October, the Nigeria Centre for Disease Control reported the patient’s multi-organ failure in Abuja, and Uganda’s Ministry of Health reinforced screening at Entebbe. The Nigerian Senate directed the federal government to screen travelers for Ebola; the 22 October story “Nigeria's Senate orders Ebola screening at all entry points, seeks emergency funds” also describes its funding request. A 22 October story, “Nigeria and Uganda coordinate efforts to contain Ebola outbreak risk,” reports cross-border coordination, while “Africa CDC calls crisis meeting as Ebola outbreak spreads” describes a regional meeting. [Evidence: event:cameoplus_26aa49914653ba89, story:d64470faffcc, event:cameoplus_a589b62f13b6d3ef, entity:e_704567e430cea20e, event:cameoplus_19514886398d86fe, event:cameoplus_707034ee561d0716, story:a8bee78c3361, connection:0, story:66f64e43a5f3]
Footnotes[9][1][11][16][10][8][4][20][5]Assessment
The central established facts are Nigeria’s imported Ebola case and actions by its federal government, the Nigeria Centre for Disease Control, and the Senate, alongside Uganda’s Entebbe screening. The patient’s Uganda travel link and the reported Nigeria–Uganda coordination make the cross-border dimension material, but they do not establish where the infection originated. The case coverage includes a headline attributing a DR Congo-strain match to health officials and another saying Nigeria had not confirmed to WHO that the patient traveled to DR Congo; “Bundibugyo Ebola outbreak spreads amid displacement and vaccine shortages” supplies separate outbreak context, not proof that Bundibugyo caused the Nigerian case. [Evidence: event:cameoplus_26aa49914653ba89, event:cameoplus_a589b62f13b6d3ef, event:cameoplus_707034ee561d0716, event:cameoplus_19514886398d86fe, story:d64470faffcc, connection:0, story:865b51328a99, connection:7]
Footnotes[9][11][8][10][1][20][7][21]Explanation originally captured 2026-10-23 · Evidence through 2026-10-24 UTC · Source edition sed_4dec184b9e3981847e4bd553f0b4ee2a
What informs this explanation
- Complete retained Story and Event membership
- Daily reporting and coded-occurrence time steps
- Event taxonomies, metrics, units, and denominators
- Canonical Entities and recorded actor/target bindings
- Typed reporting, membership, and incident edges
- Changes against the preceding retained edition
- Permitted macro, public-record, and asset facts only when they were retained with an explicit source and observation date
Quantitative
Evidence in numbers
- Scope
A 5-day Situation represented by 30 coded Events carried across 53 member Stories.
- Coded activity
The coded activity is led by HE04 · Public Health Policy Action (12) and HE01 · Disease Outbreak (8).
- Prominent subjects
Nigeria Centre for Disease Control, Africa Centres for Disease Control and Prevention, and Government of Bayelsa State are prominent in the retained actor and relationship evidence.
- Entity coverage
150 canonical Entities are linked to this edition.
Metric coverage. 30 coded Events · 30 CAMEO+ · 0 conflict. The four dimensions describe the CAMEO+ subset; conflict Events do not carry these scores.
Magnitude2.4
min 1max 5
Systemic importance0.19
min 0.08max 0.3
Propagation potential0.28
min 0max 0.37
Market sensitivity0.07
min 0.05max 0.5
Dot = mean · shaded span = observed range · position uses each metric’s defined scale.
All 7 scores, distributions & definitions
How the coder scored the full retained Event set
30 coded events — 30 CAMEO+ (7 political)
- Significance · 300.26min 0.18max 0.38
- Magnitude · 302.4min 1max 5
- Systemic · 300.19min 0.08max 0.3
- Propagation · 300.28min 0max 0.37
- Market · 300.07min 0.05max 0.5
- Goldstein · 7-0min -5max 4
- Confidence · 300.73min 0.32max 0.96
Quad class over those 7 events · Verbal Cooperation 4 · Verbal Conflict 3. No conflict-family event here, so nothing carries a fatality count — a missing column, not a toll of zero. 23 sit outside POLITICAL, where Goldstein and quad class are undefined.
Magnitude
30 measured / 30 eligible · 0 missing · 0 not applicable
score (0 to 10) · Event-level distribution, not a Situation risk score.
across all 30 events — every one of them CAMEO+
Systemic
30 measured / 30 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 30 events — every one of them CAMEO+
Propagation
30 measured / 30 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 30 events — every one of them CAMEO+
Market
30 measured / 30 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 30 events — every one of them CAMEO+
Goldstein
7 measured / 7 eligible · 0 missing · 23 not applicable
score (-10 to 10) · Event-level distribution, not a Situation risk score.
across the 7 of 30 events Goldstein is defined on — CAMEO+ POLITICAL and the conflict family; the other nine CAMEO+ domains have no Goldstein semantics
Confidence
30 measured / 30 eligible · 0 missing · 0 not applicable
score (0 to 1) · Event-level distribution, not a Situation risk score.
across all 30 events
This retained edition, independent of graph and page limits. Different dimensions, not a blended risk score; reported tolls may overlap.
Day by day5 reporting days · click a day to open or close it
2026-10-24from the recordslatest
Kenya Ministry of Health accounts for 135 Ebola contacts
15 Stories and 4 coded Events (-9 / -3 against the day before). Widest coverage: Kenya reports second Ebola death, a close relative of the first patient (25 articles). Recorded acting: Government of Bayelsa State.
- 15-9
- Stories · vs day before
- 4-3
- Events · vs day before
- 88
- articles
The lay of the land
Situation timeline
Threads
All 5 daysarticlesstoriesevents
10-2010-2110-2210-2310-24
Loading Situation timeline…
What kind of event · 11 coded types
over 30 coded events on this edition
- Health23
- HE04 · Public Health Policy Action12
- HE01 · Disease Outbreak8
- HE03 · Vaccine or Treatment Milestone2
- HE05 · Health System Crisis1
- Political7
- 01 · Make Public Statement1
- 0242 · Policy Change1
- 032 · Intent for Diplomatic Cooperation1
Countries · where it happened
Countries · who is acting
Salient structure
What holds this Situation together
Selected from the complete retained edition
Key threads
- core
AnalystNigeria’s imported case and response
The imported-case identification, the Nigeria CDC patient update, and federal mobilization form the Nigerian case-and-response strand.
- development
AnalystSenate screening and quarantine policy
The Senate’s screening direction and its reported request for emergency funds make the policy strand distinct from the clinical update.
- development
AnalystCross-border and regional measures
Coverage places the Nigerian case alongside Uganda screening, reported Nigeria–Uganda coordination, and South Africa’s travel-history and port-of-entry measures.
- development
Key actors
- NC
Key Events
contextAnalystNigeria activates response after confirming imported Ebola case
On 20 October, the Federal Government of Nigeria activated a response after confirming an imported Ebola case.
On 20 October, the Federal Government of Nigeria activated a response after confirming an imported Ebola case.
Footnotes[9]contextAnalystNigeria CDC reports Ebola patient’s multi-organ failure in Abuja
On 21 October, the Nigeria Centre for Disease Control reported the patient’s multi-organ failure in Abuja.
On 21 October, the Nigeria Centre for Disease Control reported the patient’s multi-organ failure in Abuja.
Footnotes[11]contextAnalystUganda Ministry of Health reinforces Ebola screening at Entebbe
On 21 October, Uganda’s Ministry of Health reinforced Ebola screening at Entebbe.
On 21 October, Uganda’s Ministry of Health reinforced Ebola screening at Entebbe.
Footnotes[10]
contextAnalystNigerian Senate directs federal government to screen travelers for Ebola
On 21 October, the Nigerian Senate directed the federal government to screen travelers for Ebola.
On 21 October, the Nigerian Senate directed the federal government to screen travelers for Ebola.
Footnotes[8]contextAnalystBenin activates Ebola pre-alert and strengthens border surveillance
On 20 October, Benin’s Ministry of Health activated an Ebola pre-alert and strengthened border surveillance.
On 20 October, Benin’s Ministry of Health activated an Ebola pre-alert and strengthened border surveillance.
Footnotes[13]
Notable connections
Evidenced relationships involving significant participants beyond the central cast.
The Nigeria Centre for Disease Control is identified as the actor in the Abuja patient update. · recorded participationAnalystNigeria Centre for Disease Control → Nigeria CDC reports Ebola patient’s multi-organ failure in Abuja
The Entity’s supporting-event entry identifies it as actor in this Event.
The case-identification Story supports the Event describing Nigeria’s response after confirmation of an imported case. · reporting linkAnalystNigeria activates response after confirming imported Ebola case → Nigeria identifies first Ebola patient as diplomat’s wife who holidayed in Uganda
The Event lists the case-identification Story as supporting coverage.
The Senate screening Story supports the Event describing the Senate’s direction to the federal government. · reporting linkAnalystNigerian Senate directs federal government to screen travelers for Ebola → Nigeria's Senate orders Ebola screening at all entry points, seeks emergency funds
The Event lists the Senate screening Story as supporting coverage.
A supplied same-day Story link connects the Nigerian case coverage with South Africa’s travel-history advice. · reporting linkAnalystNigeria identifies first Ebola patient as diplomat’s wife who holidayed in Uganda → South Africa urges travelers to disclose travel history amid Ebola outbreak
The link connects the Stories; it does not establish South Africa’s participation in the Nigerian case.
Africa Centres for Disease Control and Prevention is mentioned in the crisis-meeting Story, without a supplied Event-参与p · reporting linkAnalystAfrica Centres for Disease Control and Prevention → Africa CDC calls crisis meeting as Ebola outbreak spreads
The Entity’s supporting Stories include the crisis-meeting headline, but its Entity entry has no supporting Event.
How a Situation is put together53 Stories · 30 Events · 53 membership connections · 479 graph edges
A retained time step
This edition freezes the complete served membership and analysis available through its UTC cutoff. Later repairs or identity changes do not rewrite what this edition showed.
Stories, Events, and cast
Stories are reporting clusters. Events are coded occurrences within that reporting. The cast contains 150 canonical people and organizations linked to the retained evidence.
Typed connections
Story-to-Event edges identify supporting reporting. Entity-to-Event edges identify recorded actor or target participation. Mentions and analytical roles stay visibly distinct from recorded participation.
Core, precursor, and continuation labels organize the reading. They do not by themselves establish causation. Collapsed graph groups and paginated evidence change presentation only; counts use the complete retained edition.