If your clinic keeps patient details on a computer, a phone or in the cloud, India's data protection law now applies to you. The DPDP Act (Digital Personal Data Protection Act, 2023) has its operating rules in place, and the deadline is closer than it feels. This guide explains what matters for a small practice, in plain language, without legal jargon.
This is a general guide, not legal advice. For specific questions, especially about exemptions, speak to a lawyer.
What has actually changed
The Act was passed in August 2023. The DPDP Rules, 2025 were published in the Gazette on 13 November 2025 (G.S.R. 846(E)). They start in phases: the rule on consent managers starts on 13 November 2026, and most duties that matter to a clinic, including notices, security safeguards, breach reporting and patient requests, start on 13 May 2027.
Patient records are personal data, and health details are among the most sensitive kind. A clinic that decides why and how they are used is what the law calls a Data Fiduciary. The patient is the Data Principal.
What to do before 13 May 2027
The Gazette does not itself type the later calendar dates. It says some rules start on publication, Rule 4 starts one year later, and most of the rest start eighteen months later (G.S.R. 846(E), Rule 1(2) to 1(4); the Act is started on the same three steps by G.S.R. 843(E)). Counted from 13 November 2025, those later dates are 13 November 2026 and 13 May 2027.
Already in force (from 13 November 2025). Rules 1, 2 and 17 to 21, and the Act provisions that set up the Data Protection Board, started on publication. They do not, by themselves, put the notice, consent and breach duties on a clinic.
13 November 2026 (Rule 4; Act section 6(9)). This is the start date for registration of Consent Managers with the Board. A Consent Manager is a registered company that can sit between a person and organisations as a single place to give, manage or withdraw consent. It is not a form every clinic has to file on that date. Our reading of section 6(7) of the Act: a patient may give, manage, review or withdraw consent through a Consent Manager. The Act does not, on that wording, require a clinic to use a Consent Manager, or to connect to one, by 13 November 2026. Who can register is set out in Part A of the First Schedule to the Rules: a company incorporated in India, with a net worth of not less than two crore rupees, among other conditions. Clinic notice and consent duties start on 13 May 2027.
13 May 2027 (Rules 3, 5 to 16, 22 and 23, and the main duties in the Act). This is the date that matters for a clinic. Our reading of what to have in place by then, in plain words:
- A clear, separate notice that can be understood on its own, listing the data you collect, the purpose, and how a patient can withdraw consent, use their rights, or complain to the Board (Rule 3). The sample wording later on this page is a starting point, not a finished legal notice.
- A way to collect consent for the purposes you have described, and to honour a withdrawal. For a child, Rule 10 asks for verifiable consent of a parent or guardian, and treats an adult as a person who has completed 18 years.
- Reasonable security safeguards (Rule 6), including separate logins, some control over who can see a record, backups, and a written processor term with your software vendor (the vendor questions below follow Rule 6(1)(f)).
- A written breach habit that matches Rule 7: tell affected patients without delay, in plain language, with what happened, what it could mean for them, what you have done, what they can do, and who to contact; tell the Board without delay; and send the Board a detailed report within 72 hours of becoming aware, or within a longer period the Board allows if you ask in writing.
- A public contact for data questions (Rule 9). This can be you, or a named person. A Data Protection Officer is a stricter duty for Significant Data Fiduciaries, which the existing FAQ already treats as unlikely for a small clinic.
- A way for a patient to make a request, and a grievance period you have published that is no longer than 90 days (Rule 14(3)).
- A retention approach. Rule 8(1) and the Third Schedule set a three-year / 48-hour erasure clock for certain large e-commerce, online-gaming and social-media platforms. A solo clinic is not in that list. Rule 8(3) asks for processing logs to be kept for at least one year and then erased, unless another law requires you to keep them longer. Our reading: medical-record duties under other law can require a longer period for OPD notes, so do not treat one year as a date to delete charts. Decide a period with your lawyer, and do not keep stray copies in chats and downloads with no reason.
This is our reading of the Act and Rules, not legal advice. Start the practical checklist below well before May 2027; the 90-day habit plan later on this page is a way to begin, not a substitute for the legal date.
What it means for a small clinic
You do not need a compliance department. You need a few clear habits:
- Tell patients what you collect and why. The Rules require a separate, clear consent notice explaining the specific purpose.
- Collect only what you need. A phone number for follow-up makes sense. An unrelated ID document usually does not.
- Protect what you hold. The law expects reasonable security safeguards.
- Report breaches. If patient data is exposed, affected people must be told promptly, in plain language, with contact details for help.
- Respond to patients' requests. Patients can ask to see, correct or, in some cases, erase their data. Rule 14(3) asks you to publish, and keep to, a grievance response period of no more than 90 days.
- Publish a contact for data queries. This can be you or a named person on your team.
What the penalties look like
The Act sets ceilings, not fixed amounts:
| Failure | Maximum penalty |
|---|---|
| Not keeping reasonable security safeguards | Up to ₹250 crore |
| Not reporting a breach, or breaching children's data duties | Up to ₹200 crore |
| Other violations | Up to ₹50 crore |
Real penalties depend on the seriousness and circumstances, and a small clinic is unlikely to see the top figures. The important point is that security safeguards carry the heaviest weight.
A practical checklist for your clinic
Use this as a starting point and tick items off over the next few months.
Know your data
- List where patient data lives: your EMR, phones, WhatsApp chats, paper files, email attachments, lab-report folders.
- Note who can see each one.
Collect with clarity
- Add a short consent notice at registration, in the patient's language, explaining what you collect and why.
- Remove fields you never use.
Control access
- Give each staff member their own login. Never share one password at reception.
- Limit what each role can see. A receptionist rarely needs full clinical notes.
- Remove access the day someone leaves.
Secure it
- Use screen locks and strong passwords on every device.
- Keep backups, and check they can be restored.
- Avoid sending records over personal email or unprotected chat groups.
- Keep software updated.
Plan for a bad day
- Decide in advance who does what if a phone is lost or an account is hacked.
- Keep a simple written log of any incident.
Handle requests and deletion
- Know how to find, correct and export one patient's data.
- Decide how long you keep records, and do not keep data indefinitely without a reason.
Where WhatsApp and photos fit in
Many clinics run on WhatsApp: prescriptions sent to patients, reports received from them, photos of wounds. That is convenient, but it spreads patient data across personal phones. Two habits help:
- Send prescriptions from a clinic account or system, not from a staff member's personal phone where possible. See how to create a digital prescription.
- Do not leave reports and images only in chat history. Store them in the patient's record so you can find, correct or remove them when asked.
Questions to ask your clinic software vendor
Doctors have been asking online whether cheap clinic apps pass patient data to pharmacies or advertisers. You do not have to guess. Under the DPDP Act, your clinic is the Data Fiduciary: you decide why patient data is collected and how it is used. Your software vendor is a Data Processor that handles the data on your behalf. The Act says a clinic may use a processor only under a valid contract (Section 8(2)), and you stay responsible for what the vendor does with your patients' data. The Rules also expect that contract to cover reasonable security safeguards (Rule 6(1)(f)).
Start with the price
If a clinic app is free or very cheap, ask how the vendor makes money. Subscription fees are easy to understand. If the answer is vague, ask directly whether any revenue comes from pharmacies, labs, advertisers or data partners.
Ten questions to ask
- How do you make money? Is it only our subscription, or are there other sources?
- Do you share patient data with pharmacies, labs or advertisers? Ask for the answer in writing and in the contract.
- Where is our data stored? Which company hosts it, in which country, and how is it backed up?
- Which of your staff can see our patients' records, and when? Ask whether support access needs your permission.
- Is access logged? Can we see who signed in and who opened a patient record?
- Can we export all our data at any time? In what format, and does it cost extra?
- What happens when we leave? How and when is our data deleted, and will you confirm it in writing? Our reading: Rule 6(1)(e) also expects the logs, and the personal data needed to investigate unauthorised access, to be kept for one year unless another law says otherwise, so ask how the vendor balances the two.
- How fast will you tell us about a breach? Our reading: the clinic has to tell affected patients without delay, tell the Data Protection Board without delay, and send the Board a detailed report within 72 hours (Rule 7), so the vendor needs to tell you well inside that window.
- If you offer an AI scribe, how long is consultation audio kept, and who processes it? Ask whether audio or notes go to any outside AI service, and whether they are used to train models.
- Can every staff member have a separate login with limited access? A receptionist should not need full clinical notes.
Red flags
- No written answer on data sharing, or a refusal to put it in the contract.
- No contract or data terms at all, only a click-through sign up.
- "We can't tell you where the data is stored."
- No way to export your full data, or export only at a high fee.
- One shared login for the whole clinic.
- No clear answer on how long audio or deleted records are kept.
A short vendor checklist
- Written contract or data terms that name the vendor as processing data on our behalf
- Written answer on sharing with pharmacies, labs and advertisers
- Hosting company and country known
- Vendor staff access explained
- Sign-in or access logs available to us
- Full export tested once
- Deletion process on exit confirmed
- Breach notice timeline agreed
- Audio retention known (if using an AI scribe)
- Separate login for every staff member
The same questions belong on your EMR checklist. Software with separate logins and records in one place makes several of these easier, but it does not take the duty off the clinic.
Medabha lets the clinic owner export patients, visits and prescriptions as CSV files when you need them.
Our reading of the Act and Rules, not legal advice. Please check the contract wording with a lawyer.
AI scribes and recorded audio
If you use an AI medical scribe, consultation audio is personal data too. Tell patients when recording is on, use it only for documentation, and ask the vendor how long audio is kept and who can access it. Medabha's AI scribe records only when you press record, shows an indicator the whole time, and does not use consult audio or notes to train foundation models.
In the product as it stands today, recording starts only when you press record, and a recording indicator stays on while it is running. Visit audio is kept after you sign, so you can play it back; deleting it automatically on signing is not a per-clinic setting yet. Medabha does not store a separate patient-consent record for the recording itself. You still need to tell the patient a scribe is in use and get their agreement. From 13 May 2027, our reading is that this sits under the notice and consent duties in Rule 3, and under Rule 10 if the patient is a child. Ask your vendor (and us) how long audio is kept, who transcribes it, and whether it is used to train models. Not legal advice.
Children's data
The Act has stronger duties for data about children, including a role for a parent or guardian. Paediatric and family practices should read this part carefully with their lawyer.
From 13 May 2027, Rule 10 asks for verifiable consent of a parent or guardian before a child's personal data is processed, and it treats an adult as a person who has completed 18 years. Our reading: if you see children, walk this part through with your lawyer, including how you will record that a parent agreed to a scribe recording.
A simple 90-day plan
- Days 1 to 30: map where data lives, give every staff member their own login, and start a consent notice at registration.
- Days 31 to 60: clean up shared chats and personal-phone storage, check backups and write a one-page incident plan.
- Days 61 to 90: review vendors with the questions above, publish a contact for data queries and decide your retention approach.
What a simple consent notice can say
The Rules ask for a clear, separate notice that explains the specific purpose. It does not need to be long. A registration notice might say:
We collect your name, age, phone number and health details to treat you, keep your records, send prescriptions and remind you about follow-ups. Only our clinic team can see them. You can ask to see, correct or delete your data by contacting [name and number]. This notice is available in [language].
Have your lawyer check the wording, put it where patients will actually see it, and keep a record that it was shown.
What to do if something goes wrong
A lost phone with patient chats, a hacked email account or a report sent to the wrong number can all count as a breach. Act in this order:
- Contain it. Change passwords, sign out lost devices and stop the sharing.
- Write down what happened. Note what data was involved, how many patients, when it occurred and when you found out.
- Tell the people affected, without delay, in plain language: a description of the breach (what it was, how far it went, when it happened); what it could mean for them; what you have done and are doing; what they can do to protect themselves; and who they can contact (Rule 7(1)).
- Tell the Data Protection Board without delay, with the nature, extent, timing, location and likely impact, and send the Board the detailed report Rule 7(2)(b) lists within 72 hours of becoming aware, or within a longer period the Board allows if you ask in writing. Speak to your lawyer about the exact wording and timing.
- Fix the cause, so the same gap is closed.
Having this page ready before an incident makes the real thing far less stressful.
Common mistakes to avoid
- Sharing one login across the front desk, so nobody can tell who opened what.
- Keeping old patient data forever in chat apps and downloads folders.
- Assuming the vendor handles everything. You remain responsible for your patients' data.
- Treating consent as a one-time signature. Patients can withdraw it, and your process should allow for that.
The bottom line
The DPDP Act is not a reason to panic, but it is a reason to stop treating patient data casually. Clear consent, separate logins, sensible storage and a plan for breaches cover most of what a small clinic needs. Starting now, well before 2027, turns a legal deadline into a normal part of running a trusted practice.
For how a clinic workspace can keep records in one place, see clinic management software and our note on maintaining patient history digitally. You can also read Medabha's data policy.
Want to work through this as a team? Use our free DPDP Act checklist for clinics.
Frequently asked questions
Does the DPDP Act apply to a small clinic?
The Act applies to anyone who decides why and how digital personal data is processed, and a clinic that keeps patient names, phone numbers and records on a computer or phone does exactly that. Ask a lawyer about any exemption you think might apply, rather than assuming one does.
When do clinics have to comply?
The Rules were published on 13 November 2025 (G.S.R. 846(E)). Rules 1, 2 and 17 to 21 started that day. Rule 4, on registration of Consent Managers, starts one year after publication, which counted from that date is 13 November 2026. Most clinic duties, including notice (Rule 3), security (Rule 6), breach intimation (Rule 7), children's data (Rule 10) and grievance periods (Rule 14), start eighteen months after publication, which counted from that date is 13 May 2027. It is safer to begin now. Not legal advice.
Do I need to register as a Consent Manager before 13 November 2026?
No. Rule 4 is about organisations that want to be registered Consent Managers for other people. A Consent Manager has to meet conditions in the First Schedule and apply to the Data Protection Board. A solo clinic that collects its own patients' data is not, on our reading, asked to register as a Consent Manager on that date. Not legal advice.
Does 13 November mean my clinic must use a Consent Manager?
No. 13 November 2026 is when a company that wants to act as a Consent Manager can apply to the Data Protection Board for registration (Rule 4 and section 6(9) of the Act). Our reading of section 6(7) of the Act: a patient may give, manage, review or withdraw consent through a Consent Manager. A clinic that is a Data Fiduciary is not required to use one, or to connect to one, on that date. Most clinic duties, including notice and consent, start on 13 May 2027. Not legal advice.
What are the penalties?
The Act allows penalties of up to ₹250 crore for failing to keep reasonable security safeguards and up to ₹200 crore for not reporting a breach. Actual penalties depend on the case, but the ceilings show how seriously the law treats safeguards.
Do I need a Data Protection Officer?
The Rules require every organisation to publish contact details for data queries, which can be a designated person. Stricter duties, including a Data Protection Officer, apply to organisations designated as Significant Data Fiduciaries, which is unlikely for a small clinic.
Does using clinic software make me compliant?
No. Software can make good practice easier, through access controls and audit trails, but compliance is about how the clinic collects, uses, protects and deletes data.
Try Medabha in your own clinic
AI medical scribe, WhatsApp prescriptions, specialty charts and a built-in clinic website, set up in minutes.
Start 14-day free trial Prefer a walkthrough? Book a demoNo card needed.
This article is general information about clinic software and documentation workflows, not medical, legal or regulatory advice. Check current requirements with the relevant authority before making compliance decisions.