Your clinic’s whole day, on one record.
Registration to billing — patients, prescribing, dispensing and laboratory results, without re-typing between departments.
Access to patient records is logged.
Today
Front desk
2
Waiting
1
In consult
3
Labs pending
Queue
- 01A. Sharmacompleted
- 02R. Gurungin consultation
- 03S. Poudelwaiting
Modules
Buy only what you need
A module you have not bought is refused by the API, not just hidden from the interface.
Clinic
Registration, scheduling, consultations and prescribing.
Pharmacy
Batch stock, expiry, dispensing and procurement.
Laboratory
Catalogue, samples, results and verification.
Hospitalsoon
Wards, beds, admissions and nursing.
How it works
One record follows the patient
Every step writes to the same record, so each department starts where the last one finished.
- 1
Register
One record from the first visit.
- 2
Schedule
Booked or walk-in.
- 3
Consult
Notes, vitals, diagnosis.
- 4
Dispense
Prescription to counter.
- 5
Bill
One invoice, one payment.
Security
Built for patient data
Sensitive by default, so these are architecture decisions rather than features added later.
Tenant-isolated
Scope comes from the session, never the request.
Permission-based
Access by permission, not job title.
Append-only audit
Views and changes can never be rewritten.
Hardened sign-in
Argon2id, revocable sessions, optional 2FA.
Questions
What people ask first
Straight answers, including the ones that are not flattering.
Do we have to buy every module?
No. Packages are per module and combine on one organization — start with the clinic and add the pharmacy or the laboratory when you need them. A module you have not bought is refused by the API, not merely hidden from the screen.
Who can see a patient's record?
Only people in your organization who hold the matching permission, and every view is written to the audit trail. Platform staff cannot open a clinical record at all — support access is a separate, time-limited grant that is not built yet.
Can we bring existing patient data across?
Not automatically. There is no bulk import yet, so records are entered through the application during onboarding. That is a real limitation, and it is on the roadmap rather than quietly implied.
Where does the data live?
In PostgreSQL, with medical files in S3-compatible object storage. Files are never public: they are served through authorization-checked signed URLs that expire.
Can we try it before deciding?
Yes. Send the form below and we will set up an organization for you to work in with your own workflow.
Get started
Request a demo
Tell us what you run and we will walk you through it on your own workflow. No price list — packages are shaped around the modules you actually need.
- Already a customer?
- Sign in from the button above.
- Setting up a team?
- We will provision your organization and staff accounts.
- Need only one module?
- Start with the clinic and add the rest later.