Health . Access . Everyday

The health graph for Cameroon.

One platform connecting pharmacies, doctors, patients, and the family abroad who pays for their care. Every need becomes one care episode that travels across the apps, verifies itself, and settles in a single ledger.

Open the working demo Clickable end to end. Mock data, simulated payments, real flows.

Getting the right medicine is a scavenger hunt

The pieces exist. Pharmacies, doctors, mobile money, a diaspora that wants to help. None of them are connected.

1 in 4

essential-medicine requests in Douala go unfilled at the first pharmacy

Stock is invisible across the street, let alone across the city. Patients walk from counter to counter while a pharmacy two sectors away has the box.

No rail

connects a prescription to the pharmacy that fills it

Paper scripts are copied, photographed, and re-keyed. There is no way to tell a real prescriber from a forged one at the point of sale.

$4B+

in yearly diaspora remittances, none of it buying medicine directly

A daughter in Paris sends cash and hopes. She cannot pay a Douala pharmacy, see the order, or know it was delivered.

One episode, moving across every actor

A patient consults a doctor. The doctor issues a signed, self-verifying e-prescription. It routes to the nearest pharmacy with stock. A sponsor abroad pays. Delivery is tracked. Ops sees the whole thing as one timeline. No re-keying, no verification bottleneck.

Consult

Doctor

e-Prescription

Self-verifying

Routed

Nearest pharmacy

Paid

Sponsor abroad

Delivered

Tracked

Ops sees all five as one audit trail, updated live as each actor acts.

The care episode

One object: a patient need enters once and routes through consult, prescription, order, payment, and delivery. Every actor sees the same episode in their own app.

Self-verifying prescriptions

An e-prescription issued inside the graph by an NODC-verified doctor needs no review. It flows straight into fulfilment. Uploaded external scripts route to a fast ops queue.

One split-payout ledger

A single collection settles to whichever nodes delivered value: the pharmacy in XAF, the doctor their consult fee, the platform its margin. The payer is decoupled from the patient.

Live inventory and demand

Every search and every stockout in a catchment is captured. Pharmacies see the slice for their area; the network sees all of it.

This prototype

The graph is already whole. The demo proves it end to end.

  • Sign in as a pharmacy, doctor, patient, sponsor, or ops
  • A doctor issues an e-prescription and it appears in the pharmacy console live
  • A Paris sponsor pays by international card; the pharmacy is paid in XAF
  • 90 days of generated operating history: orders, inventory, garde rotation, demand
  • Bilingual, mobile-first, installable as a patient PWA
  • Every integration is a mock adapter with the real interface, behind one flag

Why it compounds

01

The demand dataset

Every unmet request, by drug, by sector, by hour. It tells a distributor what to import and a pharmacy what to stock. It is the most defensible asset in the stack and it only exists once the network runs.

02

The verified-provider graph

Pharmacies, doctors, labs, and hospitals as verified nodes reconciled against national registries. New actor types are a role flag and a subdomain, never a rebuild.

03

The settlement layer

Mobile money, domestic card, and international card in; split payouts out. Once money moves through it, switching cost is real for every party.

Douala first, then the region

The activation ladder is deliberate. Win one dense cluster, prove the unit economics, then repeat. Cross-border settlement is built in from day one, so expansion is configuration.

Now

One Douala sector cluster

Akwa, Bonanjo, Bonapriso and neighbours. Pharmacies first, then doctors on the same graph.

12 months

Douala city-wide

Full garde coverage, lab and hospital rungs activated, the demand dataset sold back to distributors.

Beyond

Yaounde, then CEMAC

The same graph, region by region. Cross-border settlement is already the model, not a migration.

The ask

A build budget takes this from a clickable prototype to a live network in one Douala sector cluster: real pharmacy onboarding, the payment adapters wired to Flutterwave, a courier integration, and the ops team to run garde coverage. The commercial question is answered here. The remaining question is execution.

Product

Harden the adapters, ship the doctor and lab rungs, real auth and roles.

Supply

Onboard the first cohort of pharmacies and verified prescribers by sector.

Operations

Garde desk, delivery partner, and the demand dataset as a B2B product.

Walk the demo