EbunOS keeps a small hospital's patients, money, stock and tasks on one laptop in the building. It is built from the hospital's own paper forms, so the record looks the way the staff already work, and a task closes only when the record shows the thing was done.
Built inside a working private hospital in Ogun State, September–October 2026, from its forms and on its floor. EbunOS is not yet the record at any hospital.
What it does
Every module works on its own and with the others. A hospital switches on what it uses; nothing recorded is ever lost when a module is switched off.
Patients, sign-ins and the staff file, payers and the price book, every payment out with the owner's OK and the petty-cash box, the tasks, the audit log, the backup with a locked copy off site and a standby laptop ready to take over, and the settings — every rule with its source.
Reception and the queue, triage, the consultation note (SF-139), prescriptions, bills, payers and HMO claims with each HMO's own rules, the price book, the daily journal for the accountant.
Dispensing, walk-in sales, stock and deliveries, orders, the controlled-drug book, the treatment room, and the allergy and dose check on every prescription.
Admissions and the bed board, drug orders and the drug chart (SF-118), observations with NEWS2 and timed escalation, fluid balance, notes and handover, consent and refusal, discharge in full.
The test menu with the lab's own ranges and critical limits, requests from the consultation, the ward and walk-ins, results with flags, critical-value calls, quality control, results from the analysers.
Antenatal care and the card, the community ANC and its referrals, labour charted on the Labour Care Guide (or the partograph, SF-79, where the hospital keeps it) with the caesarean decision record, the birth, the newborn, going home, postnatal visits.
Ultrasound and X-ray requests, the images kept beside the record (from the machine by DICOM, or uploaded), the reports and corrections, the critical-findings call, the hand-off to a reporting partner.
The staff file with an alert before a licence or certificate runs out, the duty rota and its gaps.
Operations booked, the surgical safety checklist read aloud and typed, the times, the operative note, recovery with its observations and discharge criteria, the theatre register and the autoclave log.
The national schedule loaded from its official file, each child's doses due and given, the vaccines from stock, defaulters traced, the monthly register and its counts.
Sign-ins for the cleaners and the guard that never open a clinical record: cleaning checked by someone else, waste and its hand-over, power and water, visitors and the security log; repairs given as jobs to a contractor or a member of staff and signed off, the contractors' papers, the equipment and its services.
The kitchens that cook for the hospital and their menus, each dish at the kitchen's price with the hospital's mark-up; diets and nil by mouth; each meal time's order sent to the kitchen on WhatsApp — beds and dishes, never a name — and what came, on the patient's bill; companions' and staff meals as the hospital decides.
Staff paid by the month, visiting doctors by the session, casual workers by the day; Nigeria's income tax over the year, the pension and NHF, advances and the hospital's own deductions within the law's limits; prepared and approved as each hospital decides; paid through the expenses ledger; payslips printed, on WhatsApp or in EbunOS; what is owed to the tax office and the pension administrators; and a catch-up when income tax, the pension or NSITF was left off for a while — the arrears month by month from the months already paid, an estimate of the penalties, and the schedules to settle them.
Part of the core: the library of protocols and procedures, each in force once the medical director signs it; the compliance calendar; incidents, complaints, findings and their actions; a private disciplinary record on each staff file, step by step; the management and clinical governance meetings, with agendas from the records; the risk register.
Part of the core: staff ask in their own words and get the hospital's library back — the sections that match, found on the laptop; and, when an owner switches it on, a short answer an AI is told to write from those documents only, each point with its source. A question holding a registered person's name, hospital number, phone or email is refused before anything is sent.
How it is built
The hospital's forms register, 143 forms from SF-01 to SF-142, is inside the program. Each screen is built from the form the staff already fill, and 47 of the forms print from the record with the hospital's own header and version mark.
378 rules, from the lab's critical-value call to the ward's drug-round times, each shown with the form or protocol it comes from. Where the forms give no number, EbunOS proposes one, marks it so, and waits for a doctor to confirm.
When a critical lab value is found, a task is raised for the lab with a 30-minute clock. It does not close when someone ticks it; it closes when the record shows who was told, when, and that they read the value back.
EbunOS runs on the hospital's own laptop, with or without the internet, and the tablets reach it over the building's Wi-Fi. Every night a locked copy goes off site; a second laptop, when the hospital has one, keeps a copy every quarter hour and takes over in minutes if the first one dies; a practice copy with pretend patients is there for training; every release updates the records in numbered steps with a backup first. What it keeps is the hospital's own way of working — written down, kept, and handed on to whoever comes next — so the building keeps its bearings when the people who know the way are away.
As of 5 November 2026, release 3.11.0.
The counts are of the program as built and tested. Hospitals whose record is EbunOS: none yet. Each hospital brings EbunOS in beside its paper: the staff keep their forms, and EbunOS is checked against them every evening for two weeks before anything is switched over.
Milestones
The front desk, the pharmacy and stock, bills and HMO claims, the tasks, the practice copy. Grown out of a spreadsheet system built for a four-bed hospital.
With automatic tests on every change, and each release kept as a numbered update that runs on a hospital's existing records.
Releases 1.3 to 1.9: admissions and the drug chart, observations with NEWS2, discharge in full, consent and the incident register, the laboratory, each HMO's rules, antenatal care through to postnatal visits, one patient story and the forms printed from the record.
Releases 2.0 to 2.2.2: every rule a setting with its source, ICD-10 and ICD-11, LOINC, the analyser link, the FHIR record and the NHMIS return, ultrasound and X-ray with the DICOM link, outpatient prescribing and the treatment room, the procedure note, the transfusion record and the drug reaction report.
Releases 2.4 to 2.6: the country pack for Benin and every screen in French; everything EbunOS uses from others credited on its About screen; an owner who is not a doctor runs the hospital without opening a clinical record; WHO's ICD-11 is the diagnosis code in every country, offline, in English and French; and when one person acts, the person who needs to know is told — the prescriber of a line not dispensed, the doctor of a rejected sample or an HMO's decline, the nurse who asked for a cleaning — and a specimen sent to another laboratory is chased until its result is back.
Release 2.7: clinics on set days with booked sessions, a list for each day and a call to every patient who did not come; patients enrolled for regular review; a clinic or a diagnostic centre set up with only the modules it uses; and one page for the owner with the day's and the month's numbers, without a patient's name.
Release 2.8: every payment out recorded with its receipt and never changed; the owner's OK above a line the owner sets; the petty-cash box counted against its book; cash paid from the drawer taken off at the evening count; and, with the building switched on, the contractors and their papers, the equipment and its services, each repair given as a job and signed off.
Release 2.9: the kitchens and their menus, each dish priced at the kitchen's price with the hospital's mark-up; a patient's diet and nil by mouth; the nurse's order for each meal sent to the kitchen on WhatsApp without a patient's name; what came recorded, and a meal served on the patient's bill; companions' and staff meals as each hospital decides; what is owed to each kitchen.
Release 3.0: staff paid by the month, visiting doctors by the session and casual workers by the day; income tax over the year under the Nigeria Tax Act 2025, the pension and NHF, advances and loans within the Labour Act's limits, staff meals taken from pay; who prepares and who approves as each hospital decides; payslips printed, on WhatsApp or in EbunOS; what is paid over, and the journal.
Release 3.1: the hospital's registration, permits, lease and contracts with their signed copies and a reminder before each runs out; letters to regulators followed up; the owner's monthly report on one printed page; and an inspection pack that shows what an inspector will ask for, in green or red.
Release 3.1.1: the bank or POS statement put in as the bank gives it, checked whole, and each line matched to the payment, sale or expense EbunOS recorded, or explained. What was recorded and is on no statement is listed.
Release 3.2: a second laptop keeps a fresh copy of the records every quarter hour over the hospital's Wi-Fi, locked on the way, with the pictures and the keys. If the main laptop dies, the standby takes over in minutes; a laptop going for repair hands over first, so nothing is lost. Never two main laptops at once.
Release 3.3: tomorrow's reminders, a missed visit, a child's vaccines due, and "please come back, or call us", sent by hand from the hospital's own phone on WhatsApp or by SMS, in words the owner confirms, to patients who agreed to be contacted, and never about their care. Each message kept as it was sent. A patient's message or call recorded and given to the person who answers it.
Release 3.4: leave recorded with who approved it and the paper behind it, paid by its rule (maternity as the Labour Act requires); someone who left and came back keeps both stretches; a pay change from a day within the month; a warning below the national minimum wage; and the files each office asks for from the approved months: the year's PAYE return for each state, each person's tax deduction card, the pension schedule for each administrator, NSITF and ITF, a leaver's statement, and the HR papers to print.
Release 3.5: eleven clinical protocols EbunOS proposes, each adopted by a doctor of the hospital with every point to decide answered and signed, then reviewed each year; their bedside checklists ticked on the patient's record; the hospital's own policies and SOPs on a register with their versions and review dates; audits, drills and checks on a calendar, with what was found and the action that followed; and complaints and feedback recorded, acknowledged and answered on time, those about a patient's care kept to the few who should read them.
Release 3.5.1: a patient registered twice is proposed for a merge from her page; a doctor reads the two side by side and merges them with their own password, or not; everything moves to one record, the allergies of both kept; the old number on a paper card still leads to her; and a merge can be undone until her care carries on under it.
Release 3.5.2: 210 drafts — clinical protocols, nursing procedures, policies, SOPs and manuals — each with its doses and thresholds checked against its source, and each in force only once the person it names has read it and signed it for the hospital; where a rule has a standard (WHO, the national guideline, SATS), EbunOS proposes the standard and shows it, and a hospital that sets its own less safe value writes why, beside it; and ORANGE at triage, a doctor within ten minutes.
Release 3.5.3: every clinical protocol and nursing procedure checked against current guidance and dated; where the guidance has moved, the draft says what changed, what it said before, what it says now and why — written for the doctor trained on the older way; a protocol already signed stays as signed until a doctor reads the newer draft and signs it again.
Release 3.5.4: a labour is charted as the protocols already said — each centimetre with its own time limit in place of the old alert and action lines, the second stage timed, every reading checked against its alert value, and the woman's supportive care recorded; an alert is said as the reading is typed and goes to the senior midwife or the doctor, the baby's and the severe ones to the doctor at once; a labour already under way keeps its chart.
Release 3.5.5: while an outbreak alert is on, every page says it in one line and triage asks each patient with a fever or a symptom about travel and contact; a yes with a fever or a symptom is RED, the doctor now, with isolation first and the notification task. The alert ends by itself on its date unless a doctor or the owner renews it. The first: Ebola (Bundibugyo virus), after Nigeria's imported case.
Release 3.6: a private disciplinary record on each staff file that follows the hospital's own procedure step by step — the facts first, a written query with time to answer, the reply, the hearing, the outcome in writing with its reasons, the appeal — printing each letter and reminding when a step is late; it never decides, and it refuses the unfair shortcuts. The management meeting, the clinical governance meeting and the quarterly review, each with an agenda drawn from the records, signed minutes and decisions that become actions; a risk register; a staff code of conduct.
Release 3.7: staff ask a question in their own words; the laptop finds the sections of the hospital's library that answer it, what is in force there first. With the owner's key, an AI is told to write a short answer from those documents only, each point linked to its source, a draft called a draft and never a decision; a question holding a registered person's name, hospital number, phone or email is refused before anything is sent.
Release 3.8: a hospital that ran its payroll for a while without income tax, the pension or NSITF works out what it owes from the months it already paid — person by person and month by month, under the same rules the payroll uses — with an estimate of the penalties and interest to the day it means to pay, called an estimate. It is approved like a month's pay, paid through the expenses ledger, and printed as schedules for the state tax office, each pension administrator and NSITF.
Release 3.9: a hospital reads the national health facility list it downloads itself and keeps the facilities around it, with their type, place and distance; the referral and transfer boxes offer them as staff type, and the hospital adds its own, across the border too.
Release 3.10: a new installation runs as a 30-day trial; after it, or after a licence's grace, the hospital's own tools (payroll, expenses, the bank, settings) become read-only until the licence is renewed, while patient care never stops and every record can still be read and printed. The owner accepts the licence terms once, and the program ships compiled.
Release 3.11: a hospital's price list, drugs, staff and suppliers go in at once from its own Excel list or EbunOS's workbook, each line checked before anything is saved; with the owner's assistant switched on, a photo of the paper list can be read into the same check, for a person to confirm line by line.
ebunos.com and the Nigerian and African web addresses registered; EbunOS Technologies Limited registered on 9 October 2026 (RC 9924055), with two non-executive directors; the trademark filed in Nigeria.
Two weeks alongside paper, with an evening comparison of patients, money and stock, then the go-live gate. Then the cloud copy, and the assistant features — every one a draft a person confirms. Benin's country pack and the French screens are built; Togo, Ghana, Côte d'Ivoire and Senegal follow, each with its own forms and currency.
From the floor
When a hospital's parallel run begins, the person who runs it will write short notes here about what the days are like: what went smoothly, what the staff asked for, what EbunOS got wrong and how it was fixed. The notes are written from the practice copy, with pretend patients; nothing from a patient's record is ever shown.
Data protection
On the hospital's own laptop, in the building. There is no account with us, no central copy and nothing sent to us: EbunOS Technologies Limited never sees a patient's record. A cloud copy is planned for later; it will be the hospital's choice, locked with the hospital's own key.
One person, one sign-in. Every opening of a record is written down with who and when; a restricted record needs a reason. HIV status is never stored, only the date of a test (SF-113). An export of a record is recorded with its reason and its recipient. The nightly backup is a locked copy. Nothing leaves the laptop unless a person sends it.
The website sets no cookies and has no analytics; the demo sets only the cookies it needs: your sign-in, the demo hospital (and so the language) you choose, and a thirty-second note after a save. No visitor log is kept by us. The demo holds pretend patients only and is put back the way it was every night; nothing typed in it is kept, and the demo keeps no visitor's address. An email you send us is kept to answer it, nothing more.
Registration with the Nigeria Data Protection Commission where the Act requires it, a data-protection impact assessment of the program, and a named person for data protection are on the company's list before the first hospital goes live. This page will say when each is done. None of this is legal advice: a hospital takes its own.
Contact
For a hospital that wants to see EbunOS, a partner, or a question about the work:
tee@ebunos.com
The demo opens with pretend patients and resets itself every night. Nothing you type in it is kept.