← All news and guides
Data protection

DPDP for Healthtech and Diagnostics: A Patient-Data Engineering Checklist

Patient data under the DPDP Act: consent and medical emergencies, children's data, report retention, sharing with labs and insurers, and a checklist.

Mono Team ·

Rows of glass slides and labelled sample racks on a steel lab bench in a diagnostics lab, a microscope out of focus behind them.

DPDP compliance for healthtech and diagnostics means treating patient data like any other personal data under the Act, then layering the health rules you already follow on top. The DPDP Act has no separate category for health data, so the same duties apply: a clear notice, consent or a listed legitimate use, reasonable security, breach reporting, and deletion once the purpose is over, unless a law requires you to keep the record. Two things matter more in health: the exemptions for medical emergencies and for children's care, and the medical record rules that keep reports for years. The duties start on 13 May 2027.

This checklist is for telemedicine apps, diagnostic labs, clinic and hospital software, and health platforms that move patient data between them.

What is different about patient data under DPDP

Less than you might expect. The Act treats all personal data alike, so a blood report and an email address carry the same legal duties. There are no extra consent rules for health data and no list of sensitive data types, unlike GDPR's special categories or the SPDI Rules under the IT Act, which name medical records and apply until 13 May 2027.

Health data still needs more care in practice, for three reasons:

  • The harm is greater. A leaked diagnosis or test result can hurt a person far more than a leaked phone number. When it sets a penalty, the Data Protection Board weighs the gravity of the breach and the type and nature of the data affected (Section 33), and the ceiling for failing to take reasonable security safeguards is ₹250 crore.
  • Other rules apply too. The Telemedicine Practice Guidelines, 2020, the Indian Medical Council (Professional Conduct, Etiquette and Ethics) Regulations, 2002 and, if you are connected to it, the Ayushman Bharat Digital Mission (ABDM) and its Health Data Management Policy. The DPDP Act applies in addition to these laws (Section 38).
  • Records must last. Medical record rules ask you to keep reports and case notes for set periods, which shapes your retention schedule and your answer to erasure requests.
A pharmacy counter in an Indian neighbourhood at night, rows of medicine boxes on lit shelves behind an empty glass counter.

Consent remains the main basis. It must be free, specific, informed, unconditional and unambiguous, and limited to the data needed for the purpose (Section 6). Withdrawal must be about as easy as giving consent.

Section 7 lists the legitimate uses that do not need consent. Four matter most in health:

  • Data given voluntarily for a stated purpose (Section 7(a)), where the patient has not said they object. A patient who shares symptoms to book a consultation is one example.
  • A medical emergency "involving a threat to the life or immediate threat to the health" of the patient or any other individual (Section 7(f)).
  • Treatment or health services during an epidemic, outbreak of disease or other threat to public health (Section 7(g)).
  • Safety and assistance during a disaster or a breakdown of public order (Section 7(h)).

The emergency use is narrow. It covers responding to the emergency, not every later use of the data. Record when you rely on it and why, so the use can be explained afterwards.

The Telemedicine Practice Guidelines ask for the patient's consent to the consultation itself. Consent is implied when the patient starts the consultation, and explicit consent is needed when a health worker, doctor or caregiver starts it. Explicit consent can be an email, text, or a spoken statement, and the doctor records it in the patient record (Guidelines 3.4).

That is consent to be treated by telemedicine. DPDP consent is consent to the processing of personal data for a stated purpose. Your app needs both, captured separately. A tick for the consultation does not cover using the data for product analytics, a research dataset or marketing.

Children's data

Under the DPDP Act a child is anyone under 18. Before processing a child's personal data you need verifiable consent from a parent or lawful guardian (Section 9(1), Rule 10). Tracking, behavioural monitoring and advertising targeted at children are not allowed (Section 9(3)), and nor is processing likely to harm a child's well-being (Section 9(2)).

Rule 12 and the Fourth Schedule exempt some health providers from Sections 9(1) and 9(3), with conditions:

WhoExemption applies whenSource
A clinical establishment, mental health establishment or healthcare professionalExemption applies when: Processing is restricted to providing health services to the child, to the extent necessary for the protection of her healthSource: Fourth Schedule, Part A, item 1
An allied healthcare professionalExemption applies when: Processing is restricted to supporting a treatment and referral plan recommended by such a professional for the child, to the extent necessary for the protection of her healthSource: Fourth Schedule, Part A, item 2

Three limits follow from the text. The exemption is from parental consent and the tracking rule, not from Section 9(2) on harm. It covers health services, not marketing, analytics or product features around them. And the terms take their meaning from other laws, such as the Clinical Establishments (Registration and Regulation) Act, 2010 and the National Commission for Allied and Healthcare Professions Act, 2021. Whether a platform that connects patients to doctors is itself one of these classes is a question for your lawyers. Build parental consent for everything outside the exemption, and flag records of under-18s so the right rules apply.

Reports, images and retention

The DPDP Act asks you to erase personal data once the purpose is over, unless a law requires you to keep it (Section 8(7)). The same exception applies to a patient's erasure request (Section 12(3)). For health records, several rules ask you to keep them:

  • Telemedicine. The doctor must keep a log of the teleconsultation, such as call, chat and video records, the patient records, reports, images and diagnostics used, and prescription records, for the period prescribed from time to time (Guidelines 3.7.2).
  • Indoor patients. The 2002 Regulations ask doctors to keep indoor patients' medical records for three years from the start of treatment, and to give copies within 72 hours when the patient asks (Regulations 1.3.1 and 1.3.2).
  • State and sector rules. Clinical establishment rules, accreditation standards and state laws may set other periods. List each one with its source.
  • The DPDP floor. Rule 8(3) has every Data Fiduciary keep personal data, traffic data and processing logs for at least one year, for purposes listed in the Rules.

A diagnostics business holds more than reports. Sample barcodes, requisition forms, instrument outputs, radiology images in a PACS, home-collection addresses, and phone numbers in a call-centre CRM all have different purposes. Give each its own retention entry. The report a doctor relies on may need years. The home-collection address does not.

Backups and image archives are where deletion usually fails. Write down how long backups are kept, and make sure erased records are not restored into live systems. Our DPDP implementation work sets up these deletion jobs.

Sharing with doctors, labs and insurers

A diagnostics lab bench with racks of capped sample tubes in different colours, a centrifuge and a pipette under bright white light.

Patient data moves between many parties: referring doctors, partner labs, collection franchises, pharmacies, insurers and third-party administrators. For each one, decide whether it processes data on your behalf, which makes it your Data Processor, or decides its own purposes, which makes it a Data Fiduciary in its own right. You stay responsible for your processors (Section 8(1)), and need a valid contract with each (Section 8(2)).

RecipientLikely roleWhat to control
Referring or treating doctorLikely role: Fiduciary for their own treatment recordsWhat to control: Send results only to the doctor the patient named; log the share
Partner or reference labLikely role: Processor when it tests samples for youWhat to control: Contract with security terms; a sample ID instead of the full profile where possible
Home-collection partner or franchiseLikely role: ProcessorWhat to control: Only the address, time slot and tests; access removed after collection
Insurer or third-party administratorLikely role: Fiduciary for its own claim decisionsWhat to control: Consent or a recorded basis per share; only the documents the claim needs
Cloud, LIS, PACS and messaging vendorsLikely role: ProcessorWhat to control: Security terms (Rule 6(1)(f)), storage location, retention and deletion
ABDM network, if you are connectedLikely role: Governed by ABDM's consent frameworkWhat to control: Follow the ABDM consent flow for records shared through it

The roles above are a starting point for your lawyers to confirm. Report delivery deserves special care: a report sent to the wrong WhatsApp number or email address is a personal data breach.

If you are connected to the Ayushman Bharat Digital Mission (ABDM), a patient can give consent in two places, and they are not the same consent. ABHA, the Ayushman Bharat Health Account, was earlier known as the Health ID. It is a 14-digit number, and ABDM says joining is voluntary. Records move through ABDM's Health Information Exchange and Consent Manager (HIE-CM), which ensures that health data linked to an ABHA "is shared with HIU by the HIP only when the owner of the ABHA gives consent". The Health Information Provider (HIP) creates the record; the Health Information User (HIU) asks to see it. ABDM says it does not store medical records itself. Providers create and keep them.

QuestionABDM consentDPDP consent
What it coversABDM consent: Sharing selected linked health records from a HIP to a HIU over the ABDM networkDPDP consent: Your processing of the patient's personal data for each purpose in your notice, on or off ABDM
Who runs itABDM consent: The HIE-CM built by the National Health AuthorityDPDP consent: You, the Data Fiduciary, directly or through a Consent Manager registered with the Data Protection Board (Section 2(g))
Scope and durationABDM consent: Can be limited to some records and to a fixed period, after which the HIU loses access through ABDMDPDP consent: Specific to a stated purpose, and limited to the data that purpose needs (Section 6(1))
WithdrawalABDM consent: ABDM lets the patient manage and revoke consentDPDP consent: Must be about as easy as giving it, and processing stops within a reasonable time (Section 6(4) and 6(6))
ProofABDM consent: Logged by the HIE-CMDPDP consent: You must be able to prove the notice and consent if challenged (Section 6(10))

What this means for your systems:

  • ABDM consent does not replace your DPDP notice and consent. It covers one exchange of records. It does not cover product analytics, research datasets or marketing on the same data.
  • Records you pull stay your responsibility. ABDM's own guide notes that a provider may download and keep a record during the consent window. Once a report sits in your system, your DPDP duties apply to it: security, retention and erasure.
  • The HIE-CM is not a DPDP Consent Manager. Under the Act, a Consent Manager is a person registered with the Data Protection Board. The HIE-CM is a separate system under ABDM, so do not treat one as standing in for the other.
  • Link the two records. Store the ABDM consent reference against your own consent record for the same patient, so you can show which consent covered which share.

Access logs

Rule 6(1)(c) asks for logs, monitoring and review that show who accessed personal data, so that unauthorised access can be detected and investigated. Rule 6(1)(e) asks you to keep those logs for one year, unless another law requires otherwise. In a health system, that means:

  • Log every view, not just every change. Who opened which patient record or report, when, and from where.
  • Break-glass access. Emergency access to a record the user would not normally see, with a reason entered and an alert sent for review.
  • Review unusual access. A staff member looking up a relative or a well-known patient, bulk exports, and access outside working hours.
  • Keep health data out of the log lines. Record the record ID, not the diagnosis or the report text.

Our Rule 6 checklist lists each safeguard with its evidence, and our guide to one-year log retention covers the cloud settings.

Breach notice

After a personal data breach, tell each affected patient and the Data Protection Board without delay, then send the Board a detailed report within 72 hours (Rule 7). There is no size or risk threshold. CERT-In requires cyber incidents to be reported within 6 hours, so one runbook should cover both.

The notice to patients must say what happened, the likely consequences, what you are doing about it, what they can do to protect themselves, and who to contact. Prepare templates in the languages your patients use, before you need them.

Patient-data engineering checklist

Use this against each app, lab system and partner that holds patient data.

AreaWhat to checkEvidence
Data mapWhat to check: Every system and partner that holds patient data, including LIS, PACS, CRM, messaging and backupsEvidence: A data map with owners
NoticeWhat to check: A notice at each collection point, in plain language, with withdrawal and complaint routesEvidence: Versioned notices
ConsentWhat to check: DPDP consent per purpose, separate from consent to a teleconsultationEvidence: Consent log with notice version and time
Legitimate usesWhat to check: Emergency and other Section 7 uses recorded with the reasonEvidence: A log of each use and its basis
ChildrenWhat to check: Under-18 records flagged; parental consent outside the Fourth Schedule exemptionEvidence: Parental consent records; exemption note checked by lawyers
RetentionWhat to check: A period for each record type, with the rule behind itEvidence: Retention schedule and deletion logs
ErasureWhat to check: Requests reach every system; retained records flagged with the law that requires themEvidence: Request log with each step and its date
SharingWhat to check: Each recipient's role decided; processors under contract; report delivery checkedEvidence: Partner register; contracts flagged for legal review
SecurityWhat to check: Encryption, access control and masking on systems with patient dataEvidence: Control register and access reviews
Access logsWhat to check: Views logged, break-glass reviewed, logs kept one yearEvidence: Log settings and review records
BreachWhat to check: One runbook for the Board, patients and CERT-In, with templatesEvidence: Tested runbook and drill record

A DPDP gap assessment runs this checklist against your systems and ranks the gaps by risk. Everything else we do is on our DPDP compliance page, and the DPDP Act explained covers each duty in more depth.

This article is general information, not legal advice. Medical record and sector rules vary by state and by type of provider, and our partner law firm confirms which apply to you.

Sources: Digital Personal Data Protection Act, 2023, Sections 6 to 9, 12, 33 and 38. Digital Personal Data Protection Rules, 2025, Rules 6, 7, 8, 10 and 12 and the Fourth Schedule (G.S.R. 846(E), 13 November 2025). Telemedicine Practice Guidelines, Board of Governors in supersession of the Medical Council of India, 25 March 2020, paras 3.4 and 3.7. Indian Medical Council (Professional Conduct, Etiquette and Ethics) Regulations, 2002, Regulations 1.3.1 and 1.3.2. National Health Authority, A brief guide on Ayushman Bharat Digital Mission (ABDM) and its various building blocks, version 1.1, Chapters 3, 4 and 6. Last reviewed 18 November 2026.

FAQ

Is health data sensitive personal data under the DPDP Act?

No. The DPDP Act has no separate category of sensitive personal data. Health data carries the same duties as other personal data. When setting a penalty, the Data Protection Board weighs the gravity of the breach and the type and nature of the data affected, and other health rules still apply alongside the Act.

Do hospitals and clinics need consent to treat a patient in an emergency under DPDP?

Not for the data processing. Section 7(f) of the DPDP Act allows processing without consent to respond to a medical emergency involving a threat to the life or an immediate threat to the health of the patient or another person. It covers the emergency response, so later uses of the data need their own basis.

Do diagnostic labs need parental consent to test a child?

A clinical establishment or healthcare professional is exempt from the DPDP parental consent and tracking rules when processing is restricted to providing health services to the child, to the extent necessary for her health (Rule 12 and the Fourth Schedule). The exemption does not cover marketing or analytics, and the definitions come from other laws, so confirm with your lawyers that it fits your business.

Can a patient ask a lab to delete their test reports under DPDP?

They can ask, and the lab must erase the data unless a law requires it to keep it. Medical record rules may require reports to be kept for a set period. The lab should keep only those records, restrict access to them, and tell the patient why and for how long.

When does a healthtech company have to report a data breach under DPDP?

Without delay to each affected patient and the Data Protection Board, followed by a detailed report to the Board within 72 hours (Rule 7). There is no size threshold. CERT-In separately requires cyber incidents to be reported within 6 hours. These DPDP duties start on 13 May 2027.

Find out where your patient data falls short.