AssemClinic
A clinic group management system: several branches, one patient record, and the insurance and accounting running underneath it.
How it works
A patient registered in Riyadh books a follow-up in Jeddah, and the doctor there opens the whole history. Reception checks them in and the file opens itself, the insurance eligibility check goes out, and the invoice is waiting before anyone types anything.
The doctor signs the note. The system prices what was done, takes the consumables off that branch's shelf, and builds the insurance claim from the codes already on the encounter. The cashier takes the payment, the ledger posts, the doctor's commission accrues on what was actually collected, and the patient gets a recall six months later.
It runs on eleven separate services, each with its own database, talking through events rather than calling each other. That is why a slow insurer never holds up reception, and why the claims side can be busy without the appointment book noticing.
What is inside
- Several branches sharing one patient record, with cross-branch access recorded and justified
- NPHIES eligibility and claims built as FHIR R4, with a denial dashboard by insurer, doctor and procedure
- ZATCA Phase 2 invoicing, chained per branch, with its own device registration
- Stock that comes off the shelf from the procedure, first-expiring-first-out
- Payroll with GOSI, and doctor commission computed on collections rather than billings
- A recall engine that brings patients back, with the revenue attributed to it