Clients, payers, EMR partners, IT leads, messaging and licensing across the whole deployment.
Bulk SMS with a message log, inbox, analytics and callbacks — the Africa's Talking dashboard, running on this deployment's messaging rail. Sends use the Messaging sandbox/live switch under Operating mode and the credentials configured further down this tab; nothing is stored in env vars.
Any column works — every cell that looks like a Ghana number is picked up. Duplicates are removed.
One shared Twilio/Africa's Talking/Hubtel account HNN can activate for a live test and deactivate again when done — used by any client below that hasn't set up its own. Whether this actually sends for real is controlled by the Messaging rail under Operating mode, not by anything on this card.
When a channel is on, the patient verification link sent at billing time (and on resend) also goes out by SMS and/or WhatsApp, with a short code the patient can text back instead of opening the link. Off by default for every client; unrelated to the payer-side verification gate under Payers.
Bring your own credentials — this client sends through its own provider account instead of the shared test account above (always wins over it when turned on). Off by default.
A group is a list of phone numbers a campaign can message as one batch.
New group — paste numbers one per line or comma-separated (any of 024…, 233…, +233… is fine).
Sends a real message to every contact in the group through this deployment's Messaging rail (see Operating mode for sandbox/live, and the shared test account under Messaging), skipping any number marked do-not-contact. This is the one button on this page that reaches real phones — there's a confirmation step before anything goes out.
Sign-ups from /register/ — whether from a campaign's "YES" reply or a direct visit. Approving here gives the applicant their own evaluation login: they get a text (and an email, if given) with a link to choose their password. It does not create a billing client; do that from the Clients tab once you're ready.
Settlement and Messaging switch independently — e.g. Messaging can go live while Settlement stays sandboxed, or vice versa. Once anything here is saved, it governs at runtime (no redeploy); the server's env vars only seed the very first default, before Master Control has ever saved anything.
Real bank transfers once live. Going live moves real money, so it requires typing LIVE to confirm; going back to sandbox never does.
—Real sends (and provider cost) once live — a plain toggle either direction, since this doesn't move money. While sandboxed, this is also what powers "simulate patient reply" on the billing screen.
—They sign in to the IT-lead console with the console key issued here. Scope is enforced server-side.
A commercial payer can carry a per-claim platform commission — separate from, and additional to, whatever expedited-settlement fee a hospital's own pricing already charges this same payer. Doesn't affect NNEST, price lists, targets or verification, which keep working regardless of edition.
This payer's own Stanbic marketplace username/password, used to authorise the A2A transfer to a provider. Stored encrypted; falls back to a legacy plaintext credential already on the payer record if nothing's saved here.
Set a volume an insurer/employer aims to process through HNN, and track settled value against it.
When on, this payer's claims can't be authorised until the patient has verified the bill via the link sent automatically at billing time.
Upload an insurer's approved prices (CSV or Excel-exported CSV). Columns: code, name, price and optionally unit, provider, category. A provider (tenant id or facility name) gives that facility its own price; blank = the payer's default.
When on, claims routed to this payer are repriced to its approved prices (facility-specific first, then default, else the billed price). The patient absorbs any gap between billed and approved.
A payer's product team builds Value-Based-Care programs, promotional campaigns, loyalty/discount programs, and configurable solutions (price comparison, claim expiry, settlement cycles… exposed to patients, hospitals or the payer team) here — no coding required. Every product starts as a draft, moves to sandbox to test against real observation data risk-free, then live once it's reviewed. Incentives, penalties and cashback only ever accrue as figures to review here — nothing disburses automatically yet. Clinical indicators (blood pressure, HbA1c, LDL, complications, follow-ups) come from an EMR/EHR partner's own feed — see the EMR/EHR partners tab for the API key a partner pushes them with.
Participating providers — the ecosystem this product reaches (hospitals, pharmacies, physio practices…). Leave none checked to include every provider with relevant data.
Metrics — pick the ones this program is scored on and weight each one (any positive numbers; they're normalised automatically, so 1/1/1 and 50/30/20 behave the same relative to each other).
Clinical targets used by the metrics above (defaults shown are standard primary-care benchmarks):
Provider incentive & penalty tiers — scored 0–100; a provider's bonus or penalty depends on where their own outcome score lands.
Every claim is scored by deterministic checks, a scorer trained on the payer's own decisions and Claude. Assist shows reviewers a recommendation; auto lets the AI approve on its own only while its measured accuracy on human-reviewed claims stays above the level you set in the product (and drops back to assist if it drifts). Raise the required accuracy, retrain, then promote.
Give the contribution URL to the savings partner (e.g. TrimesterSave) so deposits post to the plan; the secret is part of the URL. Hospitals enrol patients from the billing terminal; targets come from the obstetric pathways configured in the product.
Give these URLs to Africa's Talking (USSD) and ConfirmU. The secret is part of each URL, so treat them like passwords; rotating it invalidates the old ones.
Preview runs the scoring/reward engine and shows what it would pay out for a period — nothing is saved. Accrue runs the same engine and writes those figures to the ledger below it. Run each period once; accrual history shows what's already been recorded.
Accrual history
Each partner's API key (shown below as it does everywhere else — created once, then masked) is also what it uses to push clinical observations for the Product Lab: POST /api/v1/emr/observations with header x-api-key.
No EMR integration yet? A clinic can key a reading in by hand from its own terminal (POST /api/v1/clinical-observations, tenant key), and a patient can self-report once their phone is linked — the public /clinical/ page, or texting things like BP 130/85. Either path lands in the same observations feeding this tab.
The platform ships non-commercial and fee-free. Switch to licensed to require a paid licence per term. This is separate from per-transaction pricing (all set to zero).
Lets a qualifying claim clear without a human clicking approve on every one — an amount under a payer's own threshold, or a match on one of the structured rules below. Off here overrides every payer's own opt-in at once.
An expedited claim HNN hasn't been able to close (or whose patient verification stays disputed) falls back to standard processing through the payer's normal RX queue after this window.
Hubtel and MoMo are named choices from the call; HNN has no real payout credentials for either yet, so both always simulate (references prefixed STUB-) regardless of the live/sandbox switch above.
Settlement cycle (immediate / daily / biweekly) is the payer's own narrow-network setting — set from the payer's own Network API/portal (NNEST), not here.
Self-hosted LibreTranslate is the only translation engine; nothing else is called. If it is not configured or is down, every page and the developer chat keep working in the original language. Translations are cached, so the same text is only translated once. Twi, Hausa, Yoruba and Ga are usually not supported by LibreTranslate — those readers see the original text.
Rooms where developers write in their own language and everyone reads in theirs: /chat/. Members join with a room's invite code; each can also link a WhatsApp number to follow and reply from WhatsApp. (Per-person WhatsApp, not WhatsApp groups — provider APIs cannot post into groups.)
Upload a pharmacy's price list (CSV or Excel) so comparison works from day one. Quotes are shown as quoted and never mixed into real billed prices; as bills arrive, the comparison below shows both and how far each pharmacy's billing is from its quote. Columns: item (or drug/medicine), price, optionally code, unit, and pharmacy if one file covers several. Download template
Billed prices come from HNN's own real billing history at clients classified as a pharmacy (Clients tab); quoted prices come from the uploaded price lists above. Nothing is ever invented.