Simple enough for the front desk. Strong enough for the nation. Everything the paper system loses (history, time, trust), Tamam keeps. One offline-first record that follows the patient through every visit.
One patient identity carried across every facility, product and level of care.
Full clinical work continues through power cuts and network gaps, then syncs.
National reports are generated from the same records, not retyped at month end.
Every one of these was documented inside South Sudanese facilities before a line of the platform was written. None of them is solved by digitising a form: each needed a specific mechanism, and each mechanism works with the power off and the network down.
One patient record, held on the device and replicated when a connection appears: searchable by name, hospital number, geocode, QR card or fingerprint.
HMISCMSPPSHow it works ›The chart opens with vitals, diagnoses, prescriptions, results and the plan from every previous visit already there.
HMISCMSPPSHow it works ›Check-in assigns acuity, triage derives RED / YELLOW / GREEN from ETAT vitals, and the live queue sorts itself by urgency.
HMISCMSHow it works ›Prescribing runs interaction, allergy and duplicate checks against the patient's active medicines, and dispensing writes back to the same record.
HMISCMSPMSHow it works ›Results release straight into the chart, critical values require two-eyes confirmation and message the ordering clinician, and unreviewed results breach a visible SLA.
LISHMISRISHow it works ›Live stock status, batch and expiry tracking with first-expiry-first-out, reorder alerts and a printable purchase order, plus an append-only two-signature register for controlled medicines.
PMSHMISHow it works ›Referral bundles a transfer package of the record; accepting it opens an intake encounter with handover notes, and completion sends a structured outcome back.
HMISCMSHow it works ›Every visit tallies as it happens, data-quality scoring runs before export, and DHIS2-ready reports (Monthly HMIS 105, Weekly Epi, Immunization Coverage) are generated, not retyped.
HMISCMSHow it works ›The patient is registered once, or found again by name, hospital number, geocode, QR card or fingerprint. No folder has to be located.
Vitals are entered at the triage station and ETAT criteria assign RED, YELLOW or GREEN. The queue re-sorts itself by urgency rather than arrival order.
The chart opens with the patient's history already in it: past diagnoses, medicines, results and the plan left by the last clinician.
Lab and imaging orders leave the encounter electronically, arrive on the bench worklist, and return validated results into the same chart.
Interaction, allergy and duplicate checks run against the active medicine list; pharmacy dispenses against the electronic prescription and records the batch.
Admission opens ward and bed management on the same record. A referral bundles a transfer package and returns a structured outcome to the referring clinician.
Every visit tallies as it happens. Data-quality scoring runs before export, and Monthly HMIS 105, Weekly Epi and Immunization Coverage reports are generated in DHIS2-ready form.
A named hospital department is not presented as a complete specialist module until its clinical forms, permissions, safety controls and reports are ready for use.
Patient registration, appointment and triage queues, department-linked worklists, consultation, laboratory and radiology order-to-result workflows, pharmacy, inpatient wards, billing, referrals, audit logs and offline-first synchronization.
Admission-deposit collection and refunds, haemodialysis sessions, dental charting, theatre and anaesthesia workflows, optical dispensing, cardiac diagnostics, restricted mental-health notes, and dermatology photography and procedures.
The record lives on the facility device. Registration, triage, consultation, dispensing and reporting all continue offline; changes replicate both ways when bandwidth returns.
Designed for facilities where 13% have reliable power: no work is lost to a cut, and the device resumes where the shift stopped.
Accounts are issued by facility administrators against a role. Every view and change is stamped, and logging out clears the local copy from the device.