OneHealth Hub

A multilingual digital One Health surveillance research prototype for Nigeria.

It demonstrates one pathway end to end: a community observation reaches a surveillance workflow from a basic phone, is placed on a map alongside human, animal and environmental events, and comes back to the same community as a risk communication message in that zone's language.

Research prototype — not a production national surveillance system. The USSD and SORMAS pathways are demonstrated architectures. There is no live Africa's Talking subscription and no live SORMAS connection behind this deployment.

Community / field
  USSD (Africa's Talking-compatible endpoint) · offline field form
        │
        ▼
Surveillance
  Human + Animal + Environmental + Zoonotic
        │
        ▼
Situational awareness
  GIS · severity · trends
        │
        ▼
Response
  RCCE → geopolitical zone → local language → community

lib/taxonomy.ts is the single place that decides what a record is called and what kind of record it is. Two categories, kept strictly apart:

• Disease event — a named diagnosis or hazard from the canonical vocabulary (Brucellosis, Lassa Fever, Avian Influenza (H5N1), …). One spelling per disease, everywhere: map, cards, filters, alerts, exports.
• Community-reported signal — a symptom or sign observed and reported, such as Abortion/miscarriage or Diarrhea/vomiting. A signal is not a diagnosis and is never counted as one. It carries a sector and a location and waits for field verification.

Historical rows are normalised on read, so past spellings stay usable without rewriting the operational database. data/migrations/001 applies the same normalisation at rest.

Locations are always written as State → LGA/Town, e.g. Jigawa → Doko. lib/geo.ts canonicalises free-text state names and owns the single state → geopolitical zone mapping used by the dashboard, the USSD handler and the field form.

English remains available for every zone as the general/default language. data/seed/rcce_demo_alerts.sql seeds one demonstration alert per pathway.

A reporter's phone number is never published.

• The USSD handler writes the phone number only to ussd_reports, the audit log a field officer needs for follow-up. It is not written to outbreaks, which the public dashboard reads.
• Community reports are attributed as Community reporter · CR-XXXXXX — a reference derived from the record's own ID, resolvable by an authorised officer, not reversible to a phone number by a visitor.
• SORMAS exports carry the reporter reference, never the number.
• data/migrations/002 puts row level security on ussd_reports so the audit log is not readable through the public anon key.

Run both migrations before treating any deployment as safe to share.

npm install
npm run dev

Environment (.env.local):

NEXT_PUBLIC_SUPABASE_URL=
NEXT_PUBLIC_SUPABASE_ANON_KEY=
SUPABASE_SERVICE_ROLE_KEY=

Point an Africa's Talking USSD channel at POST /api/ussd to exercise the reporting flow against a real handset.

Next.js (App Router) · TypeScript · Supabase · Leaflet · Recharts · Tailwind.

© 2026 Jibrin Abi Precious. Research prototype — shared for academic evaluation. See /about.