Skip to content
  1. Home
  2. Blog
  3. Patient data breach at a clinic: what the DPDP Act requires

Compliance

Patient data breach at a clinic: what the DPDP Act requires Who to tell, by when, what to say, and a 10-step plan for the day it happens.

A phone with the clinic's WhatsApp is lost, a laptop is stolen from the cabin, a staff member forwards a patient list, or a vendor writes to say its server was accessed. Each of these is a personal data breach under the DPDP Act. The duties that follow are specific, and the clock starts when you find out.

Vitels TeamEditorial team, Vitels

Published · Last reviewed · 5 min read

In short
  • Section 8(6) of the DPDP Act, 2023: "In the event of a personal data breach, the Data Fiduciary shall give the Board and each affected Data Principal, intimation of such breach". A clinic is the Data Fiduciary; its patients are Data Principals.
  • Rule 7 of the DPDP Rules, 2025: tell each affected patient "without delay" what happened, its likely consequences, what you are doing, what they can do, and whom to contact. Tell the Board "without delay" and send a detailed report "within seventy-two hours of becoming aware of the breach".
  • Penalties in the Schedule to the Act go up to ₹200 crore for failing to give notice of a breach and ₹250 crore for failing to take reasonable security safeguards. Section 8 and rule 7 come into force eighteen months after 13 November 2025.

When patient data is breached, the DPDP Act, 2023 requires the clinic to inform two parties: the Data Protection Board of India and every affected patient. Rule 7 of the DPDP Rules, 2025 sets the timing and content. Patients are told without delay, in plain language, through their registered contact. The Board gets a first intimation without delay and a detailed report within 72 hours of the clinic becoming aware of the breach. These duties begin when section 8 of the Act and rule 7 come into force, which is eighteen months after the notifications of 13 November 2025. Preparing now costs a page of paper; doing it for the first time on the day costs far more.

What counts as a personal data breach at a clinic?

Section 2(u) of the Act defines it widely: "any unauthorised processing of personal data or accidental disclosure, acquisition, sharing, use, alteration, destruction or loss of access to personal data, that compromises the confidentiality, integrity or availability of personal data". Three things in that definition surprise clinics. It is not limited to hacking. "Accidental disclosure" covers a receptionist sending the wrong patient's report. And "loss of access" covers ransomware or a vendor outage that locks you out of records, even if nobody read them.

Common OPD incidents and whether they meet section 2(u), DPDP Act, 2023
IncidentBreach under 2(u)?Why
Report sent to the wrong patient on WhatsAppYesAccidental disclosure
Clinic phone or laptop with patient data lost or stolenYesLoss of access and possible acquisition; encryption under rule 6(1)(a) limits what a finder can read
Staff member copies the patient list for a side businessYesUnauthorised processing and sharing
Software vendor reports unauthorised access to its serversYes, for your patients' dataThe vendor is your Data Processor; section 8(1) keeps you responsible
Ransomware locks the clinic PCYesLoss of access affecting availability
Paper OPD register stolenOutside the Act unless the data was digitalSection 3 applies the Act to digital personal data and to data digitised later

Whom must the clinic tell, and what must it say?

Rule 7(1) covers patients. On becoming aware of a breach the Data Fiduciary shall, "to the best of its knowledge, intimate to each affected Data Principal, in a concise, clear and plain manner and without delay, through her user account or any mode of communication registered by her":

  • "(a) a description of the breach, including its nature, extent and the timing of its occurrence;"
  • "(b) the consequences relevant to her, that are likely to arise from the breach;"
  • "(c) the measures implemented and being implemented by the Data Fiduciary, if any, to mitigate risk;"
  • "(d) the safety measures that she may take to protect her interests; and"
  • "(e) business contact information of a person who is able to respond on behalf of the Data Fiduciary, to queries, if any, of the Data Principal."

For a clinic, "mode of communication registered by her" is usually the mobile number at registration. An SMS or WhatsApp message to that number, in the language the patient reads, meets the wording.

Rule 7(2) covers the Board. First, "without delay, a description of the breach, including its nature, extent, timing and location of occurrence and the likely impact". Then, "within seventy-two hours of becoming aware of the breach, or within such longer period as the Board may allow on a request made in writing": updated and detailed information; "the broad facts related to the events, circumstances and reasons leading to the breach"; measures implemented or proposed to mitigate risk; "any findings regarding the person who caused the breach"; remedial measures to prevent recurrence; and "a report regarding the intimations given to affected Data Principals". Under section 27(1)(a) the Board may then "direct any urgent remedial or mitigation measures", inquire, and impose a penalty.

What are the penalties?

Penalties in the Schedule to the DPDP Act, 2023 relevant to a breach (section 33(1))
Breach ofPenalty may extend to
Section 8(5): reasonable security safeguards to prevent personal data breach₹250 crore
Section 8(6): notice of a personal data breach to the Board or affected Data Principal₹200 crore
Any other provision of the Act or the rules₹50 crore

These are ceilings. Section 33(1) lets the Board impose a penalty "if the Board determines on conclusion of an inquiry that breach ... is significant", after giving an opportunity of being heard. A clinic that had safeguards and notified properly is in a different position from one that hid the breach, and the two duties carry separate penalties.

A 10-step breach response plan for a small clinic

  1. Write down the time you became aware. The 72-hour period in rule 7(2)(b) runs from here.
  2. Contain it: change passwords, log the lost device out of WhatsApp and the clinic software, revoke the leaving staff member's login, ask the wrong recipient to delete the message.
  3. Find out what data, how many patients and since when. Write it down as you learn it; you will need nature, extent, timing and location for the Board.
  4. If a vendor is involved, ask them in writing for their account of the breach and the list of affected records. Section 8(1) keeps you responsible for what your Data Processor does.
  5. Send the Board the first intimation without delay: what happened, how many patients, when, where, likely impact.
  6. Tell each affected patient on their registered number, covering the five points in rule 7(1). Keep it short and in the patient's language.
  7. Name one person in the clinic who answers patient calls about it, and put their number in the message.
  8. Within 72 hours, send the Board the detailed report under rule 7(2)(b), including the list of intimations sent to patients. If you need longer, ask the Board in writing before the 72 hours end.
  9. If the breach involved theft or a crime, file a police complaint and keep a copy with the breach file.
  10. Fix the cause and record what you changed: new passwords, separate logins, encrypted phone, a different way of sending reports. That is your evidence of reasonable safeguards under section 8(5).

Keep one folder, paper or digital, with the timeline, the messages to patients, the Board submissions and the fixes. Rule 6(1)(e) asks for logs to be kept a year in any case.

Questions

Is the 72-hour breach deadline in force now?

Rule 7 of the DPDP Rules, 2025 and section 8 of the Act come into force eighteen months after the 13 November 2025 notifications (rule 1(4) and G.S.R. 843(E)). Plan for it now so the first breach is not also the first rehearsal.

Do I have to tell patients if only a few records were exposed?

Yes. Section 8(6) and rule 7(1) say "each affected Data Principal". There is no minimum number.

My software vendor had the breach. Is it still my duty?

Yes. Section 8(1) makes the Data Fiduciary responsible for processing done on its behalf by a Data Processor, and section 8(6) puts the duty to notify on the Data Fiduciary.

Sources

  1. Digital Personal Data Protection Act, 2023 (No. 22 of 2023), Gazette of India, 11 August 2023, sections 2(u), 3, 8(1), 8(5), 8(6), 27(1)(a), 33(1) and the Schedule (accessed 30 Oct 2026)
  2. Ministry of Electronics and Information Technology, Digital Personal Data Protection Rules, 2025, G.S.R. 846(E), 13 November 2025, rules 1, 6(1)(e) and 7 (accessed 30 Oct 2026)
  3. Ministry of Electronics and Information Technology, G.S.R. 843(E), 13 November 2025 (commencement of provisions of the DPDP Act, 2023) (accessed 30 Oct 2026)

This is operational guidance for clinics, not legal or tax advice. Confirm with your state authority, council or CA.

Drafted with AI assistance; every fact checked against the sources listed; reviewed by the Vitels team.

  1. 1 You
  2. 2 Your clinic

Who should we call?

Your name and the number we can reach you on.

One more step, all of it optional.