Clinical software built in South Africa, for the consult
Our mission is simple: the note, the script and the codes should be finished when the consult is — without the doctor giving up control of a single word.
The paperwork should not outlive the consult
A consultation’s note, script, certificate and codes are drafting work. Machines should draft; doctors should decide.
Safety is enforced, not suggested
A review reminder is not a safety system. Sign-off must be able to refuse — and overrides must leave a trace.
South African practice deserves SA-first software
MIT ICD-10 coding, Medicine Price Registry prescribing, HPCSA record-keeping rules, POPIA, and recordings kept in Cape Town — not an American template with the currency changed.
Why we built it
I grew up around the small practices in Mahikeng, and the thing I kept noticing was what happened after the last patient left. The doctor would sit down to a second shift. Notes to write up, a script to redo properly, a sick note for someone still waiting at reception, codes to look up for the medical aid. The patients were done. The work was not.
Most of what those practices had to work with was not built for South Africa. It was built somewhere else and sold here, so it did not know our medical aid rules, our codes, or what a script legally has to say. Some practices ran three or four systems that could not talk to each other, and the doctor became the person carrying information between them.
So we did not start with the note. The note was never the slow part on its own. Writing it is where the paperwork begins. The script, the sick note, the referral, the codes, that is where the evening goes. A system that hands you a beautiful note and leaves you to type the script by hand has done half the job. Here the documents come out of the same recording, in the form that is actually valid in this country, so the work finishes when the consultation finishes.
There are three things we will not trade away. The doctor signs, never the software, and everything the system writes stays a draft until a qualified person agrees with it. Patient information is somebody’s private life, not data we get to be casual with. And we do not claim what we have not built. If it is not real yet, this website does not say it is.
I am Ndzalamansuku Nkuna. I build software in Pretoria, and NissiHealth is the one I have put myself into. What I want a doctor to feel reading this is simple. Somebody here understood the actual day, and built for it.
NissiHealth is built by WeMakeSites (Pty) Ltd, a South African software company. One product, built close to the practices that use it.
One system, from waiting room to signed record
Built in the open, with the first practices
The ten beta South African languages are improving toward the same standard as the English medical lane. Lab result delivery is next on the roadmap after lab request forms. And the order of everything else is set by founding practices — what they ask for is what gets built next.
Be one of the founding practices
NissiHealth is new. We don’t have testimonials or case studies to show you yet — and we won’t invent them. What the first practices get instead:
Hands-on onboarding
We set up your practice with you and stay close through the first real consults, until the workflow fits the way you work.
A direct line to the builder
Questions and issues go straight to the person who writes the code — not a ticket queue.
A say in the roadmap
What founding practices ask for is what gets built next.