DPDP for healthcare providers
Patients share health data because they have to. The Act does not create a separate category for health data, but it expects safeguards that match the harm a leak would cause, and few leaks cause more harm than this one. Most gaps in hospitals and clinics are practical: reports sent on WhatsApp, shared logins at the nursing station, records that go to labs and TPAs with nothing in writing, and old files nobody owns.
Emergencies, patients who cannot consent, and records other rules require
Emergency treatment does not wait for consent. The Act allows processing without consent to respond to a medical emergency involving a threat to life or an immediate threat to health (s. 7(f)). Record that this was the basis. Once the patient can decide, ongoing care returns to the normal notice and consent route.
For a child, consent comes from a parent or lawful guardian, and it must be verifiable (s. 9(1)). For an adult with a disability who has a lawful guardian, the guardian consents. The Rules exempt clinical establishments and healthcare professionals from parts of the children’s-data duties, for providing health services only. Use the exemption for care itself, not for marketing or research. Under legal review: The exact scope of the Fourth Schedule exemption for clinical establishments should be confirmed for each use.
Some records carry their own confidentiality duties under other laws, such as the Mental Healthcare Act, 2017 and the HIV and AIDS (Prevention and Control) Act, 2017; the DPDP Act adds to them rather than replacing them. Under legal review: The confidentiality provisions of these Acts and how they sit with the DPDP Act should be confirmed. Other rules decide how long medical records are kept: professional conduct regulations for doctors and, in many states, clinical establishment rules. The Act then expects those records to be protected for that period and erased after it. Under legal review: The record-keeping period that applies to each provider depends on the professional and state rules in force and should be confirmed.
- Emergency
- Treat first; record the basis (s. 7(f)); move to notice and consent once the patient can decide.
- Child or patient with a guardian
- Verifiable consent from the parent or lawful guardian, recorded with the registration.
- Retention
- As long as medical record rules require, then erased.
The three roles, in a worked case
The Act gives three roles. The Data Principal is the person the data is about. The Data Fiduciary decides why and how it is used, and carries the duties. A Data Processor handles it on the fiduciary’s behalf, under a contract. The same business can be a fiduciary for some data and a processor for other data.
The case
Rahul’s father is admitted to a multi-speciality hospital. His blood samples go to an outside laboratory, his scans are read remotely by a teleradiology firm, the hospital runs a cloud-hosted records system, and the bill is settled with an insurer through a third-party administrator (TPA).
| Role under the Act | In this case |
|---|---|
| Data Principal | Rahul’s father. Rahul is also a Data Principal, for the attendant and next-of-kin details he gives. |
| Data Fiduciary | The hospital, for the treatment record. The insurer is a separate fiduciary for the claim. |
| Data Processor | The records-system vendor, acting for the hospital; the teleradiology firm, where it reports only for the hospital on its instructions, though its radiologists keep their own professional duties. The TPA usually acts for the insurer under its own IRDAI licence; record its role. The outside lab may be a processor or a fiduciary in its own right, depending on the arrangement. Write it down. |
When the lab sends a report directly to the patient under its own name, it is usually acting as a fiduciary and owes its own notice.
What a hospital or clinic holds, and where it goes
| Kind of data | Examples |
|---|---|
| Identity and contact | Name, age, address, phone, emergency contact, ID or health-ID numbers |
| Clinical records | History, diagnoses, prescriptions, procedure notes, discharge summaries |
| Diagnostics | Samples and results, scans and images, ECGs, pathology and radiology reports |
| Insurance and billing | Policy and claim details, pre-authorisations, bills, payment records |
| Especially sensitive | Mental health, HIV status, reproductive health, records of staff and well-known patients |
| About others | Family history, details of attendants and next of kin |
| Staff | Doctors’, nurses’ and visiting consultants’ registrations, rosters and system accounts |
Where it comes in
- Front-desk registration and appointment booking
- Consultation notes and prescriptions
- Sample collection and imaging
- Insurance pre-authorisation and claim forms
- Telemedicine calls and patient apps
- Pharmacy dispensing and home visits
Where it goes
| From | To | What and why |
|---|---|---|
| Patient | Front desk and hospital information system | Registration details and reason for visit |
| Doctor | Outside laboratory or imaging centre | Test request with clinical details |
| Imaging system | Teleradiology provider | Scans for reporting, sometimes outside India |
| Lab or hospital | Patient | Reports, which should go through a protected channel |
| Hospital | TPA and insurer | Clinical and bill details for a claim the patient asked for |
| Telemedicine platform | Doctor and patient | Video sessions, notes and e-prescriptions |
| Clinic system | Health-information exchange | Records linked to a health ID, only with the patient’s consent |
Where hospitals and clinics are most exposed
| Severity | Risk | Why it matters |
|---|---|---|
| Critical | Reports sent as plain attachments on WhatsApp or email | A message to a wrong number, or a forwarded one, cannot be recalled. |
| Critical | Shared logins in the hospital system | Nobody can tell who opened which record, so misuse cannot be traced. |
| High | Labs, TPAs and platforms with no written terms | Full records leave the hospital with nothing saying how they may be used. |
| High | Staff browsing records they do not need | Records of colleagues, relatives and well-known patients are opened out of curiosity. |
| High | Consent for children not recorded | Paediatric records with no record of who consented for the child. |
| Medium | Telemedicine sessions recorded without telling the patient | Recordings kept on a platform nobody reviewed. |
| Medium | Records with no retention rule | Old records kept forever, or destroyed before the rules allow. |
Who else handles the data
You answer for what your processors do with the data (s. 8(1)), and you need a valid contract with each (s. 8(2)). Some vendors are fiduciaries in their own right; the table says where that is common.
| Vendor | Data they handle | What the contract should cover |
|---|---|---|
| Hospital or clinic software vendor | All patient records | Access by role; hosting location; vendor staff access only on request; deletion at contract end |
| Outside laboratories and imaging centres | Samples, results, images | Data terms or a clear fiduciary arrangement; protected report delivery |
| Teleradiology and remote reporting | Scans and reports | Where reports are read; transfers outside India checked; no retention after reporting |
| Telemedicine platform | Calls, notes, prescriptions | Who decides the purpose; recording rules; storage location |
| TPAs (for insurers) | Claim and clinical details | Only what the claim needs, for claims the patient asked for |
| Messaging providers | Phone numbers, reminders, report links | No clinical detail in message text; links that expire |
42 controls written for hospitals and clinics, on top of 66 common ones
Alongside the common controls, the healthcare assessment asks about clinical realities: how reports reach patients, individual logins and role-based access, restricted records, emergencies and consent on someone’s behalf, labs and teleradiology, TPAs and insurers, telemedicine, connected devices and imaging systems, downtime procedures, and medical record retention.
| Module | What is checked |
|---|---|
| Organisation and role mapping |
|
| Data inventory and purpose |
|
| Notice and transparency |
|
| Consent and lawful basis |
|
| Data Principal rights |
|
| Children and guardians |
|
| Data quality |
|
| Retention and deletion |
|
| Security safeguards |
|
| Breach response |
|
| Processors and vendors |
|
| Data sharing and disclosure |
|
| Transfer and storage location |
|
| Records and evidence |
|
| Access control |
|
| Incident testing |
|
| Policy and training |
|
Six of the questions you will be asked
Questions ask what you actually do, not whether you have a policy. Each answer maps to one control.
-
HC-01 Critical
Are reports and prescriptions sent to patients through a protected channel, rather than staff members' personal WhatsApp or email?
Why it is asked: A report sent to a wrong number or forwarded from a personal phone cannot be recalled. The DPDP Act has no separate category for health data; this applies its general duty in a healthcare setting.
-
HC-02 Critical
Can each member of staff see only the patient records their role needs?
Why it is asked: Most health data misuse is by insiders looking at records they have no reason to see.
-
HC-28 High
Are especially sensitive records (mental health, HIV status, reproductive health) restricted further than ordinary records?
Why it is asked: The DPDP Act has no special category, but reasonable safeguards match the harm a leak would cause, and other laws set confidentiality duties for these records.
-
HC-15 Medium
When you treat in an emergency without consent, do you record that the emergency was the basis, and move ongoing care onto the normal notice and consent route once the patient can decide?
Why it is asked: Processing to respond to a medical emergency is a legitimate use without consent, but only for the emergency.
-
HC-34 High
Is patient data shared with insurers and TPAs only for claims the patient has asked for, and limited to what the claim needs?
Why it is asked: Sharing for a claim is a specific purpose; sending more than the claim needs goes beyond it.
-
HC-13 Medium
Before a teleconsultation, are patients told which platform is used, whether the session is recorded, and how records are kept?
Why it is asked: A notice must accompany consent; recording a consultation is a use the patient should know about.
All 42 questions written for hospitals and clinics
- HC-08 Have you agreed in writing, with visiting consultants, outside labs, imaging centres and referral partners, who decides how patient data is used for each service?
- HC-09 Have you identified every group whose data you hold: patients, attendants and caregivers, next of kin, emergency contacts, staff and visiting doctors?
- HC-10 Does your registration form collect only what treatment, billing and legal duties need, leaving out details such as religion, caste or full ID numbers unless a law requires them?
- HC-11 Do you know where old patient data sits: scanned registers, retired software, old PCs, archived images and discs?
- HC-03 At registration, are patients told what you collect and why, with reminders and health offers asked about separately?
- HC-12 Are clinical photographs and case details used for teaching, publications or social media only with the patient's specific consent, and identifying features removed?
- HC-15 When you treat in an emergency without consent, do you record that the emergency was the basis, and move ongoing care onto the normal notice and consent route once the patient can decide?
- HC-16 Can patients get a copy of their records and a list of who received them, with identity checked before anything is released?
- HC-17 Can patients have their details corrected, with clinical entries amended rather than overwritten, so the original stays visible?
- HC-18 Before results, prescriptions or procedures, do staff confirm the patient with two identifiers, and are duplicate records merged?
- HC-19 Is data sent to insurers, TPAs and referral partners checked for accuracy, and are corrections passed on?
- HC-06 Do you keep patient records for the period medical record-keeping rules require, and then delete them?
- HC-20 Are old PCs, phones, USB drives and diagnostic equipment with stored patient data wiped before disposal, return or service?
- HC-01 Are reports and prescriptions sent to patients through a protected channel, rather than staff members' personal WhatsApp or email?
- HC-22 Are patient records encrypted in the hospital or clinic system, its backups, and on laptops and phones that hold patient data?
- HC-24 Are connected medical devices and imaging systems (PACS, analysers) on a separate network, with default passwords changed and updates applied?
- HC-31 Do you keep an offline or immutable backup of patient records, and a paper downtime procedure for when systems are locked?
- HC-02 Can each member of staff see only the patient records their role needs?
- HC-23 Do shared computers at nursing stations, front desks and labs lock automatically and require each person's own login?
- HC-26 Do accounts for visiting consultants, locums, students and agency staff expire when their placement ends?
- HC-27 Is two-step sign-in required for remote access to the records system, imaging viewers and email?
- HC-28 Are especially sensitive records (mental health, HIV status, reproductive health) restricted further than ordinary records?
- HC-29 Do you regularly review who opened which patient records, especially those of staff, well-known patients and sensitive cases?
- HC-30 When a report, prescription or record goes to the wrong person, is it logged as an incident and notified to the Board and the patient?
- HC-05 Are labs, telemedicine platforms, pharmacies and other partners that receive patient data bound by written data terms?
- HC-32 Does your hospital or clinic software contract cover where data is hosted, when the vendor's staff may access it, immediate breach notice, and return of all data at exit?
- HC-33 Before a vendor gets access to patient data, do you check its security, hosting location and who can access the data?
- HC-34 Is patient data shared with insurers and TPAs only for claims the patient has asked for, and limited to what the claim needs?
- HC-35 Do you log each release of patient data outside the facility: to referrers, insurers, other hospitals and authorities?
- HC-36 Are requests for patient data from police, courts and health authorities checked by a named person, limited to what is required, and logged?
- HC-37 Do you know where your records system, imaging archive, telemedicine platform and backups store data?
- HC-38 Where reports are read abroad (teleradiology) or patient data is processed overseas, have the transfers been checked against any government restriction?
- HC-39 Do you keep signed consent forms and records of releases so you can show what each patient agreed to and what was shared?
- HC-40 Is there a written policy covering photographing patients or records, discussing patients on messaging groups, and using personal phones for patient data?
- HC-41 Do employees, students, interns and volunteers sign a confidentiality undertaking before they see patient data?
- HC-04 For children and patients who cannot consent for themselves, do you record consent from a parent or lawful guardian, and check the guardian's appointment where one is claimed?
- HC-42 Where you rely on the exemption for clinical establishments for children's data, have you recorded it, and is children's data used only for health services under it?
- HC-07 Before linking a patient to a national health ID or sharing records through a health-information exchange, do you take their explicit consent?
- HC-13 Before a teleconsultation, are patients told which platform is used, whether the session is recorded, and how records are kept?
- HC-43 Is your telemedicine platform or patient app secured: encrypted sessions, verified patient identity before records are shown, and no recordings on staff personal devices?
- HC-44 Is CCTV kept out of consultation, examination and procedure areas, with footage viewable only by named people and overwritten after a set period?
- HC-45 Do home-visit staff use locked, managed devices for patient data, and avoid keeping patient lists or photos on personal phones?
Evidence that may be asked for
A “yes” is self-declared until something shows it. These are the documents and records that usually do. Your own result lists what each control needs.
- Registration notice and consent wording, with a completed sample
- User list for the hospital or clinic system showing individual logins and roles
- Access log extract for a sample patient record, and the last review of unusual access
- Report delivery method, with a screenshot of the protected link or portal
- Data terms or agreements with labs, teleradiology, telemedicine and software vendors
- Claim-sharing procedure with TPAs, showing what is sent and on whose request
- Retention schedule aligned with medical record-keeping rules
- Breach plan, including how patients are told
What makes evidence good enough · How the Evidence Room keeps it
First actions, in the order they usually make sense
Stop sending reports as open attachments; use expiring links or a portal
Give every staff member their own login and remove shared accounts
Restrict mental health, HIV and reproductive health records further
Add consent for children and guardians to registration
Sign data terms with labs, teleradiology, telemedicine and software providers
Set retention periods by record type and a destruction routine
Train front-desk and nursing staff on what may be shared and how
Your own result orders these by your answers and the law’s dates. How to plan remediation.
The reports a hospital or clinic usually needs
In healthcare the result is read by management, by accreditation and quality teams, and by partner insurers and corporate clients who send patients.
| Report | Who reads it | What it shows |
|---|---|---|
| Executive and Board Summary | Hospital management, trustees or the promoter | Open gaps on patient data by severity, with what is in force today and what follows on 13 May 2027. |
| Remediation Report | The medical superintendent, IT and the quality team | Every gap as a task with an owner, such as front desk, IT, nursing or the lab. |
| Evidence index | Quality and accreditation audits | The documents and records held against each control, with their review dates. |
Start the healthcare readiness check
The 42 questions above, plus the common ones, answered in your browser. You see your gaps, their severity and your first actions straight away. It is free and needs no account.
The law behind the healthcare controls
Every section of the Act and rule of the Rules that the healthcare controls rely on. Read them in plain language in the DPDP Act and the DPDP Rules guides, or in the official text linked from those pages.
Digital Personal Data Protection Act, 2023
| Section | About | Parts cited |
|---|---|---|
| s. 2 | Definitions | s. 2(i) s. 2(j) s. 2(k) |
| s. 4 | Grounds for processing | s. 4(1) |
| s. 5 | Notice | s. 5(1) |
| s. 6 | Consent | s. 6(1) s. 6(10) |
| s. 7 | Certain legitimate uses | s. 7(d) s. 7(e) s. 7(f) |
| s. 8 | General duties of the Data Fiduciary | s. 8(1) s. 8(2) s. 8(3)(a) s. 8(3)(b) s. 8(4) s. 8(5) s. 8(6) s. 8(7)(a) s. 8(7)(b) |
| s. 9 | Children's data | s. 9(1) s. 9(4) |
| s. 11 | Right to information | s. 11(1) s. 11(1)(b) |
| s. 12 | Right to correction and erasure | s. 12(1) s. 12(2) |
| s. 16 | Transfer outside India | s. 16(1) s. 16(2) |
| s. 17 | Exemptions | s. 17(1)(c) |
Digital Personal Data Protection Rules, 2025
| Rule | About | Parts cited |
|---|---|---|
| r. 3 | Notice | r. 3 |
| r. 6 | Reasonable security safeguards | r. 6(1)(a) r. 6(1)(b) r. 6(1)(c) r. 6(1)(d) r. 6(1)(f) r. 6(1)(g) |
| r. 7 | Breach intimation | r. 7(1) r. 7(2) |
| r. 10 | Verifiable consent for children | r. 10(1) |
| r. 11 | Persons with disability | r. 11(1) |
| r. 12 | Exemptions for children's data | r. 12(1) |
| r. 14 | Rights of Data Principals | r. 14(1) |
| r. 15 | Transfer outside India | r. 15 |