Sahabat is the Indonesian word for companion — the friend who stays. We put AI in the middle of it, because that is where it belongs: inside the relationship, helping the person doing the work. Not in front of them, replacing it.
It is also the whole product decision. Every layer we build assists a human who keeps the final say — a kader, a midwife, a doctor, a coder. None of them are being automated away.
There are competent products at almost every layer of Indonesian healthcare — clinic EMRs, AI scribes, consumer telehealth apps, casemix consultancies. Every one of them is a point solution, and not one of them hands the next layer a record. That is the honest gap, and it is the whole thesis: SahAIbat runs the same system of record from the village health post to the hospital claim, which means each layer arrives at the next already knowing the patient.
Screening, growth tracking and referral at the Posyandu (village health post), aligned to the ILP primary-care standard.
Paper registers. No commercial vendor finds this layer economic.
A single-layer competitor can add a second layer. What they cannot do is reconstruct the years of longitudinal, consented history that only exists because the platform was already in the field at the layer below.
Digitising a register satisfies a regulation. It does not tell anyone whether a child is wasting or whether an outbreak has started. Underneath every interface we ship, a real model is running — which is why one measurement that costs a kader thirty seconds can end up as a district's early-warning signal without a single person re-entering it.
A kader weighs and measures a child at the Posyandu. Thirty seconds, on a phone that may have no signal all day.
WHO growth standards run on the handset — weight-for-age, height-for-age, weight-for-height — returned as Z-scores before the family stands up.
A WAZ of −2.7 is not a number a kader should have to interpret. It comes back as SAM, with the referral already written.
The midwife and the Puskesmas receive the case with the measurements attached — not a phone call describing them from memory.
The same record updates village prevalence, district SAM rate, immunisation coverage and Posyandu performance ranking. Nobody re-types anything into a monthly report.
When communicable disease reports cross mean + 1.5 SD of that district's own history, the epidemic curve raises an SKDR-compatible alert on its own.
WHO WAZ, HAZ and WHZ computed offline on the handset — classified, and referred, from the same screen.
Danger signs, ANC 10T completeness, weight velocity and immunisation gaps come back as graded risk, not raw rows.
Alert thresholds computed as mean + 1.5 SD of a district's own history — not a national constant that fits nowhere.
Labs, imaging and ECGs read together; eGFR and FIB-4 computed; the ICD-10 code held against the patient's own results.
The plan, the reminders and the language shift with each household's own history — not one template broadcast to everybody.
Posyandu ranking, nutrition status by WAZ band, immunisation coverage, stunting prevalence month by month and a live epidemic curve — generated from records a kader created that morning, with no reporting cycle in between.
The same consented records feed Indonesia's own clinical model. We are fine-tuning MedGemma on Indonesian clinical language — how a kader records a danger sign, how a midwife documents ANC 10T, how a doctor writes an assessment in Bahasa Indonesia, how a coder justifies a severity level under BPJS. Extraction runs today on our own GPU in Jakarta; nothing a doctor corrects leaves the country.
An app that satisfies a mandate can be rebuilt in a quarter. A risk engine a health ministry trusts, running on records traceable to the kader who took them, cannot — and that is the part this page is too short to do justice to.
DOK is the commercial engine of the platform and it is shipping today — an Indonesian clinical intelligence that reads the labs, X-rays and ECGs a patient brings, writes the note, checks the ICD-10 code against the patient's own results, and pre-checks the BPJS claim before it is submitted.
Dihitung dari kreatinin ini. Tidak tercetak di laporan.
The platform is deployed today with real health workers, real clinicians and real partners — which is a different conversation from a roadmap.
Growth tracked at the Posyandu against WHO standards — weight-for-age, height-for-age and weight-for-height — with malnutrition classified and referred from the same screen the measurement was taken on.
A working platform across five products and three care layers, already in the field — built by a team small enough to still be moving quickly.
Draws the thing on a whiteboard, then writes the code that makes it true.
Decides whether a model's answer would survive a real consultation — and sends it back until it would.
Turns a national protocol into something a screen can actually ask, in the order a clinician asks it.
The reason a Posyandu in Timor trusts software it never asked for.
Holds the gap between a plan written in Jakarta and a health post that has to run it on a Friday.
Owns the servers, the GPUs and the 3am pager. Nothing ships until it stays up.
Owns how Indonesia hears about all of this.
Turns a working platform into signed clinics.
First voice a doctor hears after a trial begins.