Insights
Hospital software roles that match the counter — not a shared admin password
Most failed HIS projects in Uganda do not fail on features. They fail because everyone logs in as admin. A pharmacist can open payroll. A locum doctor can restore last week’s backup. HospitalMgr is built the other way: screens map to grants.
Configuration holds roles and permissions. You grant view, create, edit, print, or export per module. A doctor can work the patient list without a delete grant. A receptionist can register without seeing accounting journals. A lab technician can deliver a report without editing the medicine master.
Login logs exist so the in-charge can answer who signed in and when. That is not decoration. Public facilities and mission hospitals need it for the same reason hotels and microfinance sites already did in other Digital Monster products.
Multi-hospital groups get a second wall: hospital_id. Staff of site A do not browse site B’s patients because the tenant is the facility, not a filter in Excel.
Roles we see on day one
Administrator, doctor, nurse, pharmacist, receptionist, accountant, laboratory technician. You can split further — pharmacy sales versus stock, laboratory tests versus templates — without a custom fork.
What must stay locked
Backup restore, hospital profile, AI settings and encrypted API keys, role catalogues. Those are configuration. They are not a favour we leave on a sticky note.
How to ask in a demo
Create a pharmacist. Try to open payroll. Create a doctor. Try to delete a role. If both succeed, you are buying a shared password with a dashboard.