A log shows what was done through the software. On its own it is not DPDP compliance.
Send us a question about a record or a billing change you want to be able to trace, and a real person from our team will answer it.
Ask us on WhatsAppEvery clinic eventually has the same argument: a bill total is lower than expected, a patient's phone number changed, a prescription was approved by someone who was not the treating doctor. An audit log, a record of who did what and when, settles it with facts. This post explains what an audit trail should capture in a clinic, what CuraVerto's audit log records today, how it connects to the accountability ideas in India's Digital Personal Data Protection Act 2023, and what it does not do.
An audit log records who acted, what they did, to which record, and when.
Patient records, money, and access are where disputes start.
One row per action: the clinic, the acting user, the action, the record affected and a timestamp.
The list is not exhaustive of every click in the product, and we would rather you know that than assume it.
The audit table rejects any update or delete of an existing row, so corrections are new entries.
A user with the admin role can open the activity log for their own clinic, newest entries first.
The view is scoped to that clinic's tenant, so one clinic never sees another's entries.
An audit log supports DPDP accountability. It is not, on its own, compliance.
The DPDP Act 2023 places obligations on a Data Fiduciary, which includes a clinic that decides why and how patient data is processed. Being able to show what happened to personal data, and who did it, supports the accountability the Act expects, for example when responding to a patient's request or investigating an incident. An audit log is a useful piece of evidence for that. It is not, on its own, compliance. Consent, notice, retention, breach handling and processor agreements are separate obligations that no log can satisfy. For a full walkthrough, see the DPDP post below, and take the free readiness check to see where your own clinic stands.
Three limits to know before you rely on any audit log.
Each CuraVerto audit entry records the clinic, the acting user, an action name, the type and identifier of the affected record, a details field that holds before and after snapshots where the action supplies them, the IP address and browser user agent where available, and a timestamp.
Not through CuraVerto. The audit table rejects updates and deletes of existing rows at the database level, so a correction appears as a new entry rather than a change to an old one.
Audit Logs is a CuraVerto ART and HMS plan feature: ART is ₹50,000 per year and HMS is ₹10,000 per sanctioned bed per year, excluding GST. It is not part of the CMS plan at ₹25,000.
No. It helps a clinic show who did what to personal data, which supports accountability, but DPDP compliance also covers consent, notice, retention, breach response and processor arrangements. CuraVerto's audit log is one supporting tool, not a compliance certificate.
CuraVerto's Audit Logs record who acted, on which record and when, in an append-only trail your clinic administrator can filter. It is part of the ART plan at ₹50,000 per year and the HMS plan at ₹10,000 per sanctioned bed per year, excluding GST.
Prefer not to use WhatsApp? Leave your number and we will call.