Insights
Electronic medical records in Uganda work when EMR is not a standalone product
Buying a standalone EMR and a standalone HIS is how hospitals in high-income markets create interface projects. Facilities in Uganda rarely have a health-information exchange team. The record has to be the system.
In HospitalMgr the patient record is the hub: list, cases, symptoms, diagnosis, treatment, documents. Prescriptions, laboratory requests, scan orders, IPD admissions, antenatal files, dental examinations, and invoices hang off that hub. EMR is not a separate SKU.
Clinicians still need familiar functions: write notes, order tests, see allergies in pharmacy, print. Administrators need admission, discharge, transfer, and bed lists. HospitalMgr’s IPD module covers admissions, bed list, bed category, and patient services. Occupancy is a report, not a rumour.
Diagnostics are coordinated, not bolted. Lab has requests, samples, templates, delivery. Radiology has orders, categories, templates, reports. That is enough for most small-to-mid hospitals without pretending to be a full LIS/RIS multinational.
When AI assist arrives facility-wide, it will read the same tenant settings: a default model, encrypted provider keys, and monthly token caps. That is safer than pasting a personal OpenAI key into a browser extension.
Clinical modules people forget to budget
Antenatal (registration, vitals, labs, ultrasounds, follow-up alerts). Birth reports. Operation reports. Dental plans. Ambulance bookings. These are not “phase two nice-to-haves” if they are already happening on paper in your facility.
IPD without a second product
Admissions, bed list, bed category, patient services, occupancy. The same hospital_id as OPD. Transfer is a status, not a WhatsApp photo of a file.
AI later, keys now
When a facility turns on assist, HospitalMgr already has a catalog, encrypted provider keys, and a monthly token cap per tenant. That is configuration, not a side chatbot with a personal API key.