What AfyaMesh actually has
AfyaMesh is built in Bamenda and Yaounde, for Cameroon. This page is the measured state of it, recounted from the source code every time the checks run. It is published because a claim nobody can check is not worth making.
No patient has ever used AfyaMesh.Signing in needs a code sent by SMS, and the SMS sink refuses to run outside development, so there cannot be a patient until that is built. Nothing on this page describes a person. These are measurements of the software, recounted from the source on every run, and they are what there is to be honest about today.
Care pathways
Arya is an AI-powered triage assistant. Before any model is called, a deterministic danger-sign net runs on the text, in every language at once rather than only the one selected, because people here code-switch constantly.
Symptom-led, each running characterise, then associated, then danger.
Written out 42 times, because each rule exists in English, French and Cameroonian Pidgin, and all three are read on every turn rather than only the language the patient selected. People here code-switch constantly.
Children and the seriously ill do not use AfyaMesh. Their parents and carers do, and these are the signs they can report on another person's behalf: indrawing, grunting, blue lips, and the rest.
Each fixes what must be asked, what must never be said, and where it must escalate.
Health information
Written for a reader on a cheap handset paying for data by the megabyte. Every article names its source.
Each carries what it is, how it shows, what to do, and when to go now.
The reading surface behind the guidance.
children, infections, longterm, mind, symptoms, urgent, women.
None of it, yet. Every file says so in its own header and five review checklists are waiting. This number is here because it is the one a reader should see first.
What can be asked for
A priced, coded catalogue, so that a suggestion can end at something a person can actually obtain.
Including antenatal, delivery, postnatal and family planning.
Coded to LOINC, so a result means the same thing to the next clinician.
What has to be taken, and therefore where it can be taken.
Local codes tied to published ones, under a licence gate.
What holds it up
Checks that run on every push. They do not call a model and they do not touch the review database.
Each runs against a disposable database through the real endpoints.
Run against the shipping modules, with no build step in between.
The actual components, at phone and desktop widths.
Applied from empty and reversed again on every run.
The platform underneath
A check walks every route the application declares and requires each one to refuse an anonymous caller or to be named in a short public list with a reason.
For machines
The same figures, in the form that produced this page: metrics.json. It carries the commit it was counted at, so any number here can be traced back to the code that was measured.