One doctor. The reach of several.
BwinoCare is two systems in one. A data platform that assembles a complete, governed patient record out of everything your institutions already run — and an intelligence layer on top of it that extends how much one clinician can safely carry. Neither works without the other, and that is the whole point.
Every system you already run, reconciled into one patient. Held here. Owned by you.
Intelligence grounded in that record, putting what the clinician needs in front of them at the moment they decide.
Register your institution, or join as a pharmacy, a patient, or a doctor already invited to a practice. Or just ask us a question.
The patient arrives in pieces
The data is not missing.
It is scattered.
A patient's history exists. It is just not in one place. Part of it is in a paper register at the clinic they first attended. Part is in an EMR at the district hospital. A lab result sits in a system that talks to neither. The pharmacy has a dispensing record nobody upstream can see. The national reporting stack holds an aggregate row that describes a population, not a person.
So nobody has the patient. Everybody has a fragment. Tests get repeated because the earlier result is unreachable. Interactions get missed because the dispensing history lives somewhere else. A history restarts from zero because someone changed district. And the clinician in the room makes the call on whatever fraction happens to be in front of them.
There is a second cost, quieter than the first. Data this scattered cannot be governed either. You cannot secure what you cannot see, you cannot prove who accessed what, and you cannot put it to work — for the patient, for the institution, or for the country. A fragmented record is not just incomplete. It is unusable and unprotectable at the same time.
The provider is outnumbered — and under-equipped
You cannot train
your way out
of this.
Africa is producing more health workers than it ever has — 5.72 million in 2024, up from 4.3 million in 2018, with over 325,000 new graduates a year. The region still holds only 46% of the workforce it needs, and nearly a million of those trained workers are unemployed because systems cannot absorb them. At the current rate the gap is still 5.85 million people in 2030.
Now the part that matters more. Scarcity is not the only constraint. WHO finds that health workers in the region diagnose correctly in about 62% of cases, and treat appropriately in 40% of those. So even if the missing five million clinicians appeared tomorrow, you would have five million more people deciding from partial records.
Presence is not the same as capacity. The question is not only how many providers exist. It is how far each one can safely reach — and that is decided by what they can see when they decide.
Sources — WHO Regional Office for Africa, State of the Health Workforce in Africa 2026 · World Bank, physicians per 1,000 people (2022)
These are the same problem
The provider is under-equipped because the record is in pieces. Those are not two problems that happen to co-occur in African healthcare. They are one problem seen from two ends, and it means the fix for scarcity runs through the fix for fragmentation.
That order is not a preference. It is a safety requirement. An intelligence layer built on fragmented, unverified, unrepresentative data does not fail quietly — it fails confidently, and in clinical work confidence is the dangerous failure mode, not the harmless one. A system that recommends from half a record recommends wrongly with the same certainty it recommends rightly, and a clinician has no way to tell which one they are looking at.
So BwinoCare is built in the only order that works. Assemble and govern the record first. Put intelligence on top of it second. Everything on this page after this line follows from that sequence.
The record
One patient. Every system you already run.
BwinoCare reconciles the sources above into a single, continuous, versioned record per patient — and it does it without asking any institution to abandon the system it already has. Hospitals, clinics, medical centres, pharmacies and laboratories each join with roles and permissions built for how they actually operate, not a single clinic template stretched over all five. Institution registration is verified against official licensing, so the directory a patient searches is one they can trust.
-
Continuous history
A patient stays one entity across every institution that treats them, so the record does not restart when they change clinic, district or system.
-
Reconciled, not just collected
Different identifiers, spellings, units and decades resolved into something a clinician can act on in the room, with gaps marked as gaps rather than silently filled. Imports run as reviewable jobs with a downloadable report of every row that did not map, and re-importing the same file does not duplicate anyone.
-
Joins by standard
The systems already in place connect through the standards they already speak, so adoption is an integration rather than a migration. A read-only FHIR R4 API with SMART on FHIR authorization keeps your records reachable by other systems — including whatever you move to after us.
-
Resident, owned and scoped
The record stays in-region and belongs to the institution that produced it. Access is scoped to the care relationship: a doctor opens a chart only where a confirmed or completed encounter with that patient exists, and every open is written to the audit log along with every change.
-
Reaches the point of care
Delivered as a Progressive Web App that installs like a native app and keeps records you have already opened readable when the connection drops. In a country with 109 mobile subscriptions per 100 people and 17.1% internet penetration, a record that needs a live connection is a record that is absent exactly where it is needed most. To be exact: reading works offline; booking and prescribing need the connection back.
Source — World Bank, mobile cellular subscriptions and individuals using the internet, Zambia (2024)
The reach
Raise the ceiling on what one provider can safely carry.
With a whole record underneath it, intelligence stops guessing and starts carrying weight. Not by replacing the clinician — by making sure they are not deciding half-blind, and by taking the work that never needed a human in the first place.
-
The whole patient, surfaced Live
What is already in the record that this clinician has not seen: the earlier result, the other prescription, the pattern across three visits to three different facilities. The chart, the timeline, the complaint history and the response to each medication period, in the order they actually happened.
-
Interaction, allergy and dose checks Live
Run against the real dispensing history rather than what the patient remembers. Every drafted prescription is checked for recorded allergies, interactions and duplicates, and the dose comes from the Zambia National Formulary rather than from what a model remembers.
-
Evidence in context Live
The Zambia Standard Treatment Guidelines and STI guidelines are the local ground truth; product labels, trials, adverse-event reports and traditional-medicine monographs sit behind them, each carrying its own jurisdiction. An option the Zambian guidelines do not carry is labelled as such rather than merged in, and when the corpus has nothing the system says so instead of filling the gap.
-
Referral and network consult routing Live
Referrals inside your institution, and de-identified case discussions with consenting specialists outside it — so a hard case can reach the scarce expert without the patient travelling, and without their identity leaving your walls.
-
Caseload risk stratification In build
Which patients in a caseload are drifting toward crisis, ranked before they present as an emergency. Cohort analysis and trends over your own population ship today; the ranking on top of them does not yet.
-
Population signal In build
An emerging outbreak or a drug-supply failure surfaced while there is still time to act on it.
Every suggestion shows its working: what in the record produced it, and what evidence sits behind it. A clinician who cannot interrogate a recommendation cannot be accountable for it — and accountability stays with the clinician, by design. Nothing is written to a record without a clinician approving it first.
BwinoCare's AI features assist clinical judgement. They do not replace it. BwinoCare is not a diagnostic device and makes no claim of clinical validation.
What that looks like on a Tuesday
The two layers are not abstractions. This is what they turn into.
- Appointments & discovery
- Map-based doctor search, online booking, automated multi-channel reminders that cut missed visits without staff effort.
- Telemedicine
- A clinician at one facility sees patients who cannot travel in — the most direct form of extending a limited pool.
- E-prescriptions
- QR-secured and time-limited, checked against the record for interactions, routed straight to pharmacy fulfilment. An expired script stops working rather than quietly being honoured.
- Pharmacy & lab loop
- Dispensing and results flow back into the same record, so the next clinician inherits them instead of rediscovering them. Stock moves as it is dispensed, with low-stock and expiring-soon items flagged.
- Billing & claims
- Consultation invoicing and insurance-claims tracking generated from the clinical record, not reconciled against it afterwards.
- Institution analytics
- Performance and financial reporting drawn from the same spine as the clinical view.
Who it's for
Four kinds of user, four hubs, one record between them. Every routine action sits on the dashboard of the person who actually does it.
Run the whole institution
Doctors, appointments and patient records across departments. Inter-specialty referrals between your teams, a platform-wide clinical protocol library, consultation invoicing, and analytics over your own population.
See patients, not paperwork
Publish your availability, then work from one screen: the chart, the notes, the diagnosis and the prescription. Dose guidance and the treatment guidelines are in the same place.
Dispense against a real record
Scan a digital prescription, check it, dispense it. Inventory moves as you dispense, with low-stock and expiring-soon items flagged on your dashboard.
Carry your own history
Find a doctor, book an appointment, join a video consultation, and keep your medical history, prescriptions and documents in one place instead of a folder you have to remember to bring.
Security, audit and getting your data out
Security you can check
Three layers, not one: the role decides what kind of view you reach, object permissions decide which institution or pharmacy you are attached to, and the encounter gate decides whether you may open this patient's chart at all. Multi-factor authentication is available on every staff account, and the most sensitive clinical fields — patient identifiers, consultation notes, diagnoses and prescriptions — are encrypted at rest.
Audit trail
Every change to a patient record, diagnosis, prescription or clinical note is logged with the user who made it — as is every chart opened and every sign-in.
Ours to hold.
Africa carries roughly a quarter of the world's disease burden and supplies under 2% of the genomic data global medicine is built on. Of the 20,825 clinical trials that opened worldwide in 2023, 819 — about 4% — were hosted here. Medicine tested on populations that are not ours arrives as an approximation, and we are the ones who absorb the error.
This is not a separate argument from the two above. It is the same one at continental scale: intelligence is only as good as the record beneath it, and the record the world treats as universal barely contains us. That does not close by shipping more African health data abroad to be processed. It closes when the record is built here, held here, and governed here. BwinoCare is a Zambian platform. Your institution's data belongs to your institution, stays in-region, and is readable by the systems built to serve the people described in it.
Sources — IQVIA clinical trial starts, 2023 · genomic representation, peer-reviewed literature 2022–2026
At national scale
Joining, not replacing
A platform that only unifies the institutions inside it recreates fragmentation one tier up. BwinoCare is built to join the systems a country already runs rather than replace them, so adoption makes the national picture more complete instead of adding another silo to it.
The claims work grows with the scheme
Zambia's compulsory National Health Insurance Scheme is expanding the pool of insured patients. As more institutions become NHIMA-accredited providers, the scheduling, billing and claims-adjacent record-keeping they must do grows with it — and that record-keeping is exactly what a complete, governed record makes tractable.
Healthcare first.
BwinoCare is built by MKN Technologies, a Zambian data infrastructure company. The spine underneath it — one governed record, reconciled from the systems that already exist and kept under African ownership, with intelligence built on top of it — is being pointed at real estate next, with education, agriculture, finance and logistics behind it. Fragmentation is not a healthcare problem that happens to affect other sectors. It is the same problem wearing different clothes.
Pricing depends on your size, not your patients
We charge for practitioner seats and staff accounts, never for the number of patients you treat. Tell us how many clinicians you have and what you are running today, and we'll quote it — fifteen minutes on a call gets you a straighter answer than a pricing table would.
Or reach us directly — Stephankalaba@gmail.com · +260 764 738 169 · +260 776 514 959
Questions we get asked
The four that come up on almost every call. Anything else, the contact form above reaches a person.
Can we migrate our existing data?
Yes. Import FHIR R4 bundles, HL7 v2 batches, or CSV — including CSV exports from systems like OpenMRS. Each import runs as a reviewable job with a downloadable error report for the rows that don't map, and re-importing the same file doesn't duplicate anyone.
Do we need reliable internet?
Not constantly. BwinoCare installs as an app, and pages and records you have already opened stay readable when the connection drops — which covers the consultation that starts while the line is down. Writing a new booking or prescription does need the connection back.
Is our data separate from other institutions'?
Yes. Every clinical query is scoped to your own doctors, the assistant can only retrieve your institution's records, and the FHIR API filters by the caller's institution on every request. The one deliberate exception is the clinical protocol library, which is shared platform-wide — we say so rather than implying it is yours alone.
Can we get our data out again?
Yes. A read-only FHIR R4 API with SMART on FHIR authorization covers patients, conditions, observations, medication requests, encounters, practitioners and organizations, so your records stay reachable by other systems — including whatever you move to after us.
See it on your
own workflow.
Thirty minutes, your institution's actual appointment and prescription flow, and an honest answer about whether this fits. If it doesn't, we'll tell you.
Register in minutes • Import your existing records • Email support included