Clear access, preserved history and practical recovery. These are part of the product, not optional extras.
Database row policies scope clinical records to the signed-in clinic. Composite keys reject references to another clinic’s patients. Company accounts manage subscriptions and onboarding without access to the clinical workspace.
Finalized notes are locked. Corrections are appended with an author and reason. Issued prescriptions retain their original instructions; released reports cannot be edited through the app.
Staff receive role-based access. Passwords use Argon2id; sessions use HttpOnly cookies. Two-step sign-in supports authenticator apps and recovery codes, and is required for company accounts in production.
Money is stored in integer paisa. Voids retain a reason. A full refund creates a linked outgoing entry. Payment and dispensing retries use request keys to prevent duplicate entries.
Reminders require consent and contain a visit date, without clinical notes. Released reports can be shared through an expiring link. The clinic can revoke that access. Anyone holding a valid link can read the report.
Deployment includes encrypted, authenticated database backup and restore scripts. The hosting team must schedule them, keep a separate copy and rehearse recovery. Backup frequency and hosting details belong in the clinic’s service agreement.
Before using live patient records, agree on hosting, retention, staff access and support. Chautari does not claim an NMC certification or IRD approval. Your clinic remains responsible for clinical decisions and lawful record handling.
Read the privacy notice →See the records, roles and recovery process in a demo.