Most mid-sized hospitals run on a patchwork: an OPD register at reception, a separate lab notebook, a pharmacy on a standalone billing machine, doctor shares worked out on a calculator at month end, and no single person who can say what the hospital actually earned yesterday. Nothing is wrong with any one piece — the problem is that none of them talk to each other.
Other vendors sell the pharmacy, the lab and the reporting as three separate purchases. With Ayriq HMS, the whole system is the product — on the three-month plan exactly as on the annual one.
These are the real screens from a working deployment, not mockups — shown with demonstration data rather than a hospital's actual patients or accounts. Click any image to enlarge.
Most cloud hospital systems stop being a hospital system the moment the internet drops. Ayriq HMS keeps accepting registrations, bills and lab entries offline, then reconciles automatically — and flags genuine conflicts instead of quietly overwriting one branch with another.
"Ask Aliya" answers patient questions and books appointments over WhatsApp, on the channel patients already use. It is given read-only access to a hand-picked set of safe fields — never patient identity data, never raw database access.
Every prescription and fee receipt prints with a signed QR code. Scan it and the document's authenticity is confirmed against the hospital's own server — which makes forged receipts and altered prescriptions a solved problem.
A hospital website with online booking, and an Android app for patients, ship as part of the platform — not as two more projects to commission, budget for and integrate later.
Not against a straw man. These are the actual options a hospital owner in Pakistan weighs up: a local vendor's one-time licence, an international cloud platform, or an open-source stack with an integrator.
| Capability | Ayriq HMS | Local HMS vendor (one-time licence) |
International cloud HMIS | Open-source stack (Bahmni / OpenMRS) |
|---|---|---|---|---|
| OPD + IPD in one system | Built in | Usually | Yes | Yes (Bahmni) |
| Pharmacy with batch & expiry tracking | Built in | Often a paid add-on | Higher tier | Via Odoo in Bahmni; add-on for OpenMRS |
| Laboratory with editable reference ranges | Built in | Varies by vendor | Yes | Built in for Bahmni; add-on for OpenMRS |
| Doctor revenue sharing & payouts | Built in | Rarely | Rarely — not a local practice | Not available |
| Keeps working offline / through power cuts | Yes — offline-first with sync | No | No — needs connectivity | Partial in Bahmni; none in OpenMRS |
| Multi-branch sync with conflict detection | Yes | No | Enterprise tier | Manual / custom build |
| Patient mobile app | Included | Separate project | Separate tier | Not available |
| Hospital website + online booking | Included | Separate project | No | Not available |
| AI assistant on WhatsApp | Included | No | No | Not available |
| QR-verifiable prescriptions & receipts | Yes | No | No | Not available |
| Priced in PKR, no currency exposure | Yes | Yes | No — billed in USD | Free licence, paid integrator |
| Upfront cost to start | None — 14-day free trial | PKR 45,000–50,000+ one-time | Monthly from day one | No licence fee; implementation cost |
| Realistic time to go live | Days | Weeks | Weeks | Months, with in-house technical staff |
| Who fixes it at 9pm on a Sunday | Us, on WhatsApp | Depends on the vendor | A ticket queue in another timezone | You, or your integrator |
Comparison compiled September 2026 from publicly available vendor material and published open-source feature documentation. Local-vendor pricing reflects the commonly quoted range for hospital and clinic software in Pakistan; specific vendors price to the hospital's size and module list, so treat it as an indication rather than a quote. Where a competitor's capability genuinely varies, we have written "varies" rather than guessing.
Per hospital, per branch, in Pakistani rupees. Hosting, updates, backups and support are in the price — there is no separate server bill and no per-user licence to count.
Migrating them is part of setup. We take whatever you have — registers, Excel files, an old system's export — and load your patients, doctors, services and price lists so that day one is not day zero.
Most hospitals are live within days, not months. Reception and pharmacy are the first to train because they touch it most; each role only has to learn its own screens.
The system keeps running locally and keeps accepting work. When the connection returns it syncs on its own, and anything genuinely conflicting is flagged for a human rather than silently overwritten.
You do. It is your hospital's data, it is exportable, and if you ever leave we hand it over rather than hold it hostage.
Then you are probably better served by one of our smaller products — Ayriq Labs for a standalone laboratory, or our pharmacy system for a standalone pharmacy. Tell us your situation and we will point you at the right one, including when that is not the biggest one.
No. Add as many staff accounts as the hospital needs; the price is per branch, not per login.
Within reason, yes — fee structures, services, doctor share rules and price lists are all configuration, not code. Genuinely bespoke work is quoted separately and honestly.
The system locks to a renewal screen after a short grace period. Your data is not deleted, and it is waiting for you if you come back.
A demo is a 30-minute call where we walk through the live system — your workflow, your fee structure, your questions. No slide deck, no obligation, and we will tell you if Ayriq HMS is the wrong fit for you.
Give us thirty minutes. Worst case, you leave knowing exactly what a proper system would change.