DPDP Act Compliance Checklist for Pharma and Healthcare Marketing
A compliance lead reading about the DPDP Act is almost always working backwards from a single date. The Rules were notified in November 2025, the substantive obligations commence in May 2027, and a programme has been scoped to fill the gap. That programme is necessary and it is also not the most urgent thing on the desk.
The reason is that data protection is not the only law that governs a message to a doctor or a patient in India, and it is the one with the longest runway. A promotional SMS or voice call to an Indian mobile number has been governed by the telecom commercial communication regulations since 2018, substantially tightened on 12 February 2025. Pharmaceutical promotion to healthcare professionals has been governed by the Uniform Code for Pharmaceutical Marketing Practices since it was issued on 12 March 2024, with an annual self-declaration and a Department of Pharmaceuticals complaint process behind it. Hospital advertising has been governed by the professional conduct rules since 6 October 2026. All three bind today. The DPDP Act's substantive machinery does not.
The practical consequence is a sequencing error that is easy to make and expensive to unwind. A team that spends eighteen months building a consent architecture for 2027 while its medical representatives send unregistered promotional messages from ordinary mobile numbers has optimised the wrong risk. The telecom rules carry disconnection of telecom resources for up to two years for the clearest version of that mistake, and five valid complaints inside ten days is the threshold that triggers action.
So this page is organised as four checklists rather than one. The commercial communication list, which is overdue. The HCP data list, which is where the doctor database question sits. The patient data list, which is where hospitals carry the most exposure. And the institutional list, which is the Rule 13 and consent manager build that genuinely belongs on the 2027 timeline.
One boundary before starting. The pharmaceutical marketing code itself is covered in full on our UCPMP 2024 compliance guide, the hospital advertising rules on our NMC ethical advertising guidelines page, and the campaign level application of those rules in AI campaigns for health checkup packages. None of that is restated here.
How reliable is this page, stated up front The provisions below come from published analyses of the DPDP Rules 2025 and from secondary descriptions of the Act, not from our own reading of the gazetted text. Two attempts to retrieve the official documents while writing this page were unsuccessful, which is stated here rather than hidden in a footnote. Rule and section numbers in secondary summaries are not always reliable, and we found three points on which reputable sources disagreed. Each disagreement is flagged at the point of use and listed again in limitations. Verify every clause number against the gazetted notice and take a legal view before acting on this page. The direction of each obligation is not in doubt. The numbering is the part to check. |
Three regimes, three clocks
The DPDP Act does not operate alone, and sequencing the regimes correctly is the single most useful thing a compliance lead can do in the first week. Commercial communication to Indian mobile numbers is governed by the telecom regulations, in force since 2018 and substantially amended on 12 February 2025, with obligations that sit on the sender and consequences that reach telecom resources. Pharmaceutical promotion is governed by the marketing code issued on 12 March 2024, with an annual self-declaration and a two layer complaint process under the Department of Pharmaceuticals. Hospital and practitioner advertising is governed by the professional conduct guidelines of 6 October 2026. Data protection is governed by the DPDP Act 2023 and the Rules notified on 13 November 2025, whose substantive provisions commence on 13 May 2027. A programme that treats these as one workstream will miss the near deadlines, because the DPDP date is the one that gets written on the board slide. Treat them as three lists with three owners, and start with the one that is already overdue.
The commencement table, which is the only date table you need
Commencement is phased and the phases do not divide the way a project plan would. The institutional and Board provisions came first, the consent manager framework sits alone at twelve months, and everything a marketing function recognises as an obligation arrives at eighteen.
| Regime | In force from | What it governs | Who should own it |
|---|---|---|---|
| Telecom commercial communication rules, as amended | Amendment made 12 February 2025, gazetted 18 February 2025, with provisions commencing thirty and sixty days later | Promotional and service SMS and voice calls to Indian mobile numbers. Headers, content templates, consent registration, number series, opt-out | Marketing operations, with the telecom aggregator. Not legal, and not the DPDP project |
| UCPMP 2024 | Issued 12 March 2024 | Gifts, hospitality, travel, samples, brand reminders, CME sponsorship and promotional claims to healthcare professionals | Compliance, with the commercial head and the CEO who signs the self-declaration |
| NMC professional conduct and advertising guidelines | 6 October 2026 | Hospital and practitioner advertising, testimonials, endorsements and identifiable patient data | Hospital marketing. Covered on our dedicated page rather than here |
| DPDP Act 2023 | Enacted August 2023, operative through the Rules | The substantive duties: lawful basis, notice, security, breach, retention, rights | The Data Protection Officer or the nominated compliance owner |
| DPDP Rules 2025, first tranche | On publication, 13 November 2025. Reported as Rules 1, 2 and 17 to 21 | The Data Protection Board, its procedure, appeals to the Appellate Tribunal | Legal. Nothing for marketing to do |
| DPDP Rules 2025, consent managers | 13 November 2026. Reported as Rule 4 | Registration of consent managers, the net worth and interoperability conditions, their obligations | A build or buy decision, and it is live before the rest |
| DPDP Rules 2025, main tranche | 13 May 2027. Reported as Rules 3, 5 to 16, 22 and 23 | Notice, security safeguards, breach reporting, retention, children's data, Significant Data Fiduciary duties, rights, cross-border, government requests | The eighteen month programme. This is the date on everyone's slide |
One source disagreement to note here rather than later. Most published analyses give 13 May 2027 for the main tranche, counting eighteen months from a 13 November 2025 publication. One source we consulted gives 14 May 2027, and the government press release on the Rules is dated 14 November 2025 rather than 13 November. The difference is a day and it does not change a plan, but it is the kind of detail that should be taken from the gazette rather than from a blog, including this one.
What the Act does not contain, which matters more than what it does
Three absences in the DPDP Act shape a healthcare compliance programme more than any individual obligation, and all three are commonly got wrong in sector content.
| The assumption | The position | What follows |
|---|---|---|
| Health data is sensitive personal data under the Act | Reported as incorrect. Two of the three sector analyses we read state that the Act creates no separate sensitive or special category of personal data | There is no higher consent standard for a diagnosis than for a phone number. Sensitivity enters through the factors the Board weighs when setting a penalty, which is a different mechanism with a different consequence |
| There is a healthcare exemption | Narrow and specific rather than general. The legitimate uses cover a medical emergency, an epidemic or public health threat, and a disaster. The children's provisions carry a listed exemption for clinical establishments | Routine care is not exempt and marketing is nowhere near exempt. Reading the emergency clause as a healthcare carve-out is the commonest error in this area |
| Anonymised data takes you outside the Act | Only if it is genuinely anonymous. The analyses are explicit that coded data stays personal data where the key to re-identification is retained, and that removing names from an image does not anonymise it | Your research and AI training positions rest on an anonymisation claim that somebody technical has to defend. Most claims we have seen are pseudonymisation described as anonymisation |
| Consent is the only route | No. Section 7 lists certain legitimate uses, including the specified purpose for which a person voluntarily provided their data | Mapping which of your processing rests on consent and which on a legitimate use is the first real piece of work, and it is analysis rather than tooling |
| A processor agreement transfers the risk | It does not. The analyses are consistent that contractual delegation does not absolve the fiduciary, and that labs, third party administrators, insurers and cloud record vendors are processors whose handling remains your liability | Your vendor list is your risk register. Count the processors before counting anything else |
The first row is worth dwelling on because it changes how a policy should be written. A healthcare organisation that drafts its DPDP policy around a sensitive data category is writing to a framework the Indian statute does not use. The practical reading is that every field is personal data, the obligations are uniform, and the consequence of a failure involving clinical detail is heavier because the Board may weigh the nature of the data when it sets the amount. Write the policy to the uniform standard and let the risk register carry the sensitivity.
DPDP checklist for HCP marketing
A compliant HCP marketing programme in India needs four things that most programmes do not currently have, and only one of them is a DPDP artefact. First, a lawful basis recorded against every contact, which in practice means either consent captured under the Act's standard or the Section 7(a) legitimate use with the specified purpose written down. Second, explicit consent registered through the telecom consent registry for any promotional SMS or voice call, because consent held privately in your CRM is not what the telecom regulations ask for. Third, a registered header and a registered content template for each message type, with promotional voice calls originating from the 140 number series. Fourth, an opt-out in every promotional message and a suppression rule that bars any further consent request for ninety days after somebody opts out. The DPDP layer adds the notice requirement from 13 May 2027, the rights handling, the retention schedule and the breach runbook. The sequencing point is that a programme can be perfect on DPDP and still be unlawful today, because the telecom rules are in force and they govern the act of sending rather than the act of holding.
The checklist, with the owner and the clock against each line
Every line below belongs to somebody and has a date. A checklist without those two columns becomes a policy document, which is the usual fate of DPDP readiness work.
| Check | What good looks like | Owner | Due |
|---|---|---|---|
| 1. Lawful basis per contact | A field on the record, not a folder of forms. Consent, Section 7(a) voluntarily provided, or no basis, which means suppress | DPO with commercial | Before 13 May 2027, and before any new campaign |
| 2. Purpose written against each list | The specified purpose as the doctor would have understood it. Monograph request is not newsletter subscription | Marketing operations | Now. It is a documentation exercise, not a build |
| 3. Registered header per message type | Promotional, service and transactional headers distinguished and registered | Marketing ops with the aggregator | Overdue |
| 4. Registered content templates | Every template registered before use. An unregistered sender's commercial message is reportedly unsolicited commercial communication by definition | Marketing ops | Overdue |
| 5. Explicit consent in the consent registry | Consent verified from the recipient in a robust and verifiable manner and recorded by the consent registrar, rather than a tick box in your own database | Marketing ops with the aggregator | Overdue |
| 6. 140 series for promotional voice | All promotional calls from the designated series. Reported consequence for using an ordinary ten digit number is disconnection of telecom resources for up to two years | Tele-calling and inside sales | Overdue, and the highest severity line on this list |
| 7. Opt-out in every promotional message | Present, functional, and honoured in the sending system rather than in a mailbox | Marketing ops | Overdue |
| 8. Ninety day suppression after opt-out | No consent request for ninety days unless the person opts back in sooner. A rule in the platform, not a note in a process document | Marketing ops | Overdue |
| 9. Rule 3 notice for consent based processing | Itemised description of the data, the specified purposes, and a link to withdraw consent as easily as it was given, exercise rights and complain to the Board | DPO with legal | 13 May 2027 |
| 10. Withdrawal as easy as giving | One click, same channel, propagated to every downstream system including the representative's tablet | DPO with IT | 13 May 2027 |
| 11. Rights request handling | A route published on the site, a named contact, and the ability to find every copy of a record. Reported outer limit for grievances is ninety days | DPO | 13 May 2027 |
| 12. Retention schedule by data class | Published, defensible, and separate from the marketing permission question | DPO with records | 13 May 2027 |
| 13. Breach runbook | Intimation to affected people without delay and a detailed report to the Board inside seventy two hours. Rehearsed once | DPO with security | Write it now, regardless of commencement |
| 14. Processor agreements | Every agency, aggregator, data vendor and CRM host under terms that allocate DPDP obligations and breach liability | Legal with procurement | Start now. Contract cycles are long |
| 15. UCPMP alignment on the same contact | The marketing code governs what you may offer the doctor. Data law governs whether you may reach them. Both apply to the same email | Compliance | Live since March 2024 |
Lines three to eight are the ones to take to a meeting this week. Each is live, each sits with marketing operations rather than with legal, and none of them appears on a typical DPDP readiness plan because the DPDP Act does not mention them. A compliance lead who delivers the 2027 programme on time and leaves those six lines open has delivered the less urgent half of the job.
Section 7(a), and why a business card is not a subscription
Section 7(a) of the Act is the provision that Indian B2B marketing leans on hardest and reads least carefully. The clause permits processing for the specified purpose for which the data principal has voluntarily provided her personal data, where she has not indicated that she does not consent to that use. Read quickly, it sounds like a general permission for anything a person handed over data for. Read with its own illustrations, it is considerably narrower.
The statute's second illustration under 7(a) is the operative one and it is unusually direct. A person messages a broker asking for help finding rented accommodation and shares her data for that purpose. The broker may process it to identify and tell her about available accommodation. She then tells the broker she no longer needs help, and the illustration states that the broker shall cease to process her personal data. Two things follow from a single example: the permission is bounded by the purpose as the person framed it, and it terminates on request without any formal withdrawal mechanism being invoked.
| How the data arrived | Does 7(a) plausibly cover this? | What it does not cover |
|---|---|---|
| A doctor fills a form at your conference booth to receive a product monograph | Plausibly yes, for sending the monograph. The purpose was specified by the doctor's own request | The quarterly newsletter, the new product launch mailer, the webinar invitation. Different purposes, none of them specified |
| A doctor requests a medical information response | Plausibly yes, for answering the query and for any pharmacovigilance follow up required by law | Adding the record to a commercial targeting segment |
| A doctor registers for your CME programme | Plausibly yes, for running the programme and for what the programme's own notice described | Promoting an unrelated brand to the attendee list. The commonest misuse of a CME database |
| A representative notes a doctor's number from a prescription pad or a clinic board | No. Nothing was voluntarily provided to you | Everything. This is the single most common provenance in Indian field data and it has no basis at all |
| You bought the record from a data vendor | No, not under 7(a). The doctor provided nothing to you | Everything, unless another basis exists. Addressed in the next section |
| A doctor opted in on your portal with a notice covering commercial communication | Not 7(a) at all. This is consent, and it should be recorded and withdrawable as consent | Anything the notice did not describe |
The fourth row is the uncomfortable one for most field organisations. A number collected by observation was not voluntarily provided to the company, and no amount of CRM hygiene converts it into a lawful basis. The practical fix is not deletion in every case, because some of those contacts can be converted through a genuine opt-in, but the fix has to start with marking the provenance rather than with assuming it.
The field data provenance exercise
Pick one therapy area and one region, pull every HCP record your representatives work, and try to answer one question for each: how did this contact detail reach us?
In most organisations the answer is unrecorded for the majority of records. That is the finding, and it is more useful than any gap assessment a consultant will sell you, because it tells you the size of the remediation rather than the shape of the obligation.
Record provenance as a field going forward, with the date and the purpose. Retrofitting it later is not possible, and from 13 May 2027 the notice obligation makes the question considerably harder to avoid.
The telecom layer, which governs the sending rather than the holding
Commercial communication rules and data protection rules answer different questions, and conflating them is why so many Indian marketing programmes are confident and non-compliant at the same time. Data protection asks whether you may hold and process the record. The telecom regulations ask whether you may transmit a promotional message to that number. A lawful basis under the DPDP Act is not an answer to the second question.
| Requirement, as described in published analyses | What it means operationally | Confidence |
|---|---|---|
| Senders register as principal entities and use registered headers | A header per message category, reportedly suffixed to mark promotional, service, transactional or government traffic | Well attested across sources |
| Content templates registered before use | No ad hoc copy. A message outside a registered template is reportedly treated as unsolicited commercial communication | Well attested |
| Explicit consent recorded by a consent registrar | Consent verified from the recipient in a robust and verifiable manner, held in the telecom consent register rather than privately. Explicit digital consent can reportedly override a blocked preference | Attested, and the digital consent acquisition facility is reported as delayed in adoption |
| Promotional voice calls from the 140 series | Robocalls and auto-dialer promotional calls included, with pre-declaration of auto-dialer use to the originating provider | Attested |
| Service and transactional voice calls from a designated series | One source consulted gives 160 and another gives 1600. The series number should be confirmed with your aggregator before anything is procured | Low. Sources conflict and we have not resolved it |
| Mandatory opt-out in every promotional message | In the message itself, honoured in the platform | Attested |
| Ninety day bar on consent requests after an opt-out | A suppression window enforced by the system, not by the campaign manager | Attested |
| Service message consent validity of seven days | Short lived by design. One source we read attributes the seven day limit to transactional messages instead, which is a material difference | Low. Sources conflict |
| Complaint threshold of five valid complaints in ten days | The practical trigger. Previously reported as ten in seven days, so the threshold has tightened | Attested |
| Disconnection and blacklisting for using undesignated numbers | Reported as up to two years of disconnection of telecom resources. The severe end of the scale | Attested |
Two honest caveats about this table. The regulations are telecom instruments and our sources are secondary commentary on them, with two internal conflicts we could not resolve and have marked as low confidence. The financial penalties in those regulations are also reported as falling on the access providers rather than on the sender, which is why a marketing team can be out of compliance for a long time without hearing about it. What reaches the sender is header suspension, number disconnection and blacklisting, which arrive without warning and stop campaigns dead.
Where this intersects with the marketing code is worth one sentence. The marketing code governs what you may offer a healthcare professional, and our UCPMP 2024 compliance guide covers gifts, samples, brand reminders and CME in full. Data law and telecom law govern whether you may reach that professional at all, and no amount of code compliance answers that. The same email can satisfy the marketing code and breach two other regimes simultaneously, which is the reason these three lists need three owners.
What does the DPDP Act mean for doctor databases?
Read this section knowing that Multiplier AI sells a doctor data platform, which makes us the wrong people to ask and the right people to be held to an answer. The position as we understand it is this. A doctor's professional details are personal data under the Act, because they relate to an identifiable natural person, and nothing about a professional context removes that. The Act does not apply to personal data that the data principal has made publicly available, or that another person was under a legal obligation to make publicly available, which is the provision every data vendor in India now cites. That exclusion is real and it is much narrower than the use being made of it. A State Medical Council register entry published because the law requires publication is a plausible fit for the second limb. A mobile number from a conference delegate list, a prescription pad or a purchased file is not, because nobody published it under a legal obligation and the doctor did not make it public. And the decisive point, which the vendor pages skip, is that the exclusion is about whether the Act governs the data. It says nothing whatsoever about whether you may lawfully send the message, which is governed by the telecom regulations and, for pharmaceutical promotion, by the marketing code. A database can sit entirely outside the DPDP Act and every message you send from it can still be unlawful.
The publicly available exclusion, and the four questions it does not answer
The exclusion has two limbs and almost all the commercial interest attaches to the second. The first covers personal data the person has made or caused to be made publicly available themselves, with the illustration being an individual posting on social media. The second covers data that any other person was under a legal obligation to make publicly available, which is the limb a regulator's register falls under if it falls anywhere.
What the commentary we read is careful about is that the exclusion attaches to the data and its provenance, not to the convenience of the person holding it. The analysis we found most useful made three points worth repeating. Companies should establish how the information entered the public domain and whether the circumstances actually fit the exclusion. Data obtained by unauthorised access or by circumventing a restriction raises separate legal questions and is not treated as covered. And the Act does not expressly say that aggregation, enrichment, profiling or commercialisation removes data from the exclusion, so those activities should not be treated as an automatic trigger for coverage either.
| Source of a doctor record | Does the exclusion plausibly reach it? | Reasoning |
|---|---|---|
| A State Medical Council or National Medical Commission register entry | Plausibly yes, for the fields the register publishes | Published because law requires publication, which is the second limb. Name, registration number, qualification and year of registration are the register's own fields |
| A hospital's own public consultant listing | Arguable, and weaker | Published voluntarily by the hospital rather than under a legal obligation, and published by the hospital rather than by the doctor. Neither limb fits cleanly |
| A doctor's own public professional profile | Plausibly yes for what they chose to publish | First limb, made publicly available by the data principal. The scope is what they published, not what you inferred from it |
| A personal mobile number from a conference delegate list | No | Not published under a legal obligation and not made public by the doctor. The commonest field in Indian HCP databases and the least defensible |
| A number transcribed from a prescription pad or clinic signage | No | Visible is not published. No limb of the exclusion is engaged |
| A record bought from a data vendor | Depends entirely on the vendor's provenance, which you are now responsible for understanding | The exclusion follows the data, so buying it does not create coverage and does not create an exclusion either. Ask the vendor field by field |
| A prescribing behaviour estimate or a derived segment | No, and this is the clearest case | An inference you created was never publicly available by anybody. One analysis we read treats prescriber data processed for commercial analytics as requiring consent from the professional |
| An email address appended by a third party enrichment service | Almost certainly not | Appended rather than published. If the service cannot tell you where it came from, assume no exclusion applies |
The seventh row is the one that should change a commercial plan. A register entry may be outside the Act, and the segment you built from it is not the register entry. The moment you attach a specialty inference, a prescribing estimate, a decile, a propensity score or an engagement history to that record, you are processing personal data you created and the exclusion has nothing to say about it. Which is to say that the more valuable your database is, the less of it the exclusion protects.
What the exclusion still does not permit
Four separate questions sit behind may I use this doctor database, and the publicly available exclusion answers only the first. Teams that stop at the first answer are the ones who will be surprised.
| The question | Governed by | Answer if the data is publicly available |
|---|---|---|
| May I hold and process this record? | The DPDP Act | Possibly outside the Act for the published fields. This is the only question the exclusion answers |
| May I send a promotional SMS or make a promotional call to this number? | The telecom commercial communication regulations | Unaffected. Registered header, registered template, consent in the consent registry and the designated number series are still required |
| May I offer this doctor what I am planning to offer? | The UCPMP 2024 and, for practitioners, the professional conduct rules | Unaffected. Gifts, hospitality and inducements are a different regime with a different complaint process |
| May I use this doctor's name or image in my material? | The marketing code and the professional conduct guidelines | Unaffected, and reportedly restricted. One source states that using healthcare professionals' names in promotional material is prohibited under the code |
| May I claim the exclusion without being able to show provenance? | Practically, no | An exclusion you cannot evidence is a position you cannot hold in an inquiry. Record where each field came from |
The second row is the sentence we would put on a wall if we were running a pharmaceutical commercial team. Data protection law and commercial communication law are not alternatives and compliance with one is not evidence about the other. A legal team can conclude correctly that a register derived database sits outside the DPDP Act, and the campaign running on it can still be stopped by a telecom provider next month.
What the exclusion still does not permit
Four separate questions sit behind may I use this doctor database, and the publicly available exclusion answers only the first. Teams that stop at the first answer are the ones who will be surprised.
| The question | Governed by | Answer if the data is publicly available |
|---|---|---|
| May I hold and process this record? | The DPDP Act | Possibly outside the Act for the published fields. This is the only question the exclusion answers |
| May I send a promotional SMS or make a promotional call to this number? | The telecom commercial communication regulations | Unaffected. Registered header, registered template, consent in the consent registry and the designated number series are still required |
| May I offer this doctor what I am planning to offer? | The UCPMP 2024 and, for practitioners, the professional conduct rules | Unaffected. Gifts, hospitality and inducements are a different regime with a different complaint process |
| May I use this doctor's name or image in my material? | The marketing code and the professional conduct guidelines | Unaffected, and reportedly restricted. One source states that using healthcare professionals' names in promotional material is prohibited under the code |
| May I claim the exclusion without being able to show provenance? | Practically, no | An exclusion you cannot evidence is a position you cannot hold in an inquiry. Record where each field came from |
The second row is the sentence we would put on a wall if we were running a pharmaceutical commercial team. Data protection law and commercial communication law are not alternatives and compliance with one is not evidence about the other. A legal team can conclude correctly that a register derived database sits outside the DPDP Act, and the campaign running on it can still be stopped by a telecom provider next month.
The provenance record, which is the only artefact that survives an inquiry
Every position in this section depends on being able to say where a field came from, which means the deliverable is a provenance record rather than a policy. The structure below is what we would want to be able to produce at short notice, and it is a database design decision rather than a compliance document.
| Field to record | Why it matters | Where teams get it wrong |
|---|---|---|
| Source of each contact field, not of the record | The name may be from a register and the mobile number from a delegate list. They have different positions and need separate marks | One source field for the whole record, which collapses the only distinction that matters |
| Date of acquisition | Fixes which regime applied and supports a retention clock | Overwritten on every refresh, destroying the original date |
| The purpose stated at the point of collection | The thing Section 7(a) is bounded by. Without it there is no way to say what the permission covers | Not captured at all, because the form did not ask |
| The notice version shown | From 13 May 2027 the notice content is prescribed, so the version matters | No versioning. The notice is edited in place on the website and the history is gone |
| Consent state, channel by channel | Email, SMS, voice and messaging apps are governed differently. A single consent flag cannot represent them | A single boolean, which is the most common HCP database design in India |
| Consent registry reference where applicable | The telecom rules expect consent recorded by a registrar, so the reference is the evidence | Held only in the aggregator's system, with no link back to the CRM record |
| Withdrawal and opt-out events with timestamps | Supports the ninety day suppression rule and the erasure duty | Recorded in a mailbox or a spreadsheet rather than in the system that sends |
| Vendor and contract reference for purchased records | You inherit the provenance question when you buy the file. The contract is where you put the warranty | No field, because purchased records are merged into the main table on load |
Row five is where most remediation projects actually fail. A single consent flag cannot express a doctor who accepted email, never consented to SMS, and asked a representative to stop calling. Splitting that one field into four is a schema change, which means it needs an engineer and a release, which means it needs to start considerably earlier than a 2027 deadline suggests.
Our own position, stated plainly
We sell doctor data and analytics to pharmaceutical companies, so the conclusion above is against our commercial interest in two places. We have said that the publicly available exclusion is narrower than the industry treats it, and that the derived fields which make a database valuable are the fields the exclusion does not reach.
We have also said that a clean DPDP position does not permit a single message, which undercuts the way this category is usually sold.
What we think is actually defensible is a provenance recorded database with per-channel consent state and a documented purpose against every list. That is harder to build and considerably easier to defend, and it is the product question rather than the compliance question. Our wider approach is described on the GenAI doctor data platform page.
The patient side, where hospitals carry the most exposure
Hospitals face a harder version of the same problem than pharmaceutical companies do, for a structural reason: the hospital already holds everything. A pharmaceutical company has to acquire a doctor's details before it can misuse them. A hospital has a complete clinical record, a phone number, a billing history and an admission form signed at the worst moment of somebody's year. The temptation to treat that as a marketing asset is enormous, and the single piece of paper that is supposed to authorise it is the weakest document in the estate.
Bundled admission consent, which is the largest single hospital exposure
Almost every Indian hospital uses one admission consent form that covers treatment, maintenance of electronic records, sharing with group entities, research, personalised recommendations and promotional offers. The analysis we found most useful on the healthcare sector names that pattern directly and calls it bundled consent, and its conclusion is that it should be replaced with purpose specific notices and granular choices. The reason is the specificity requirement: consent has to be specific to the purpose, and broad wording such as other purposes does not meet it.
| Purpose currently bundled into one form | Where it should sit | Why the separation matters |
|---|---|---|
| Treatment and clinical care | Clinical consent, governed by the professional and clinical establishment rules | The care relationship does not depend on a marketing choice, and bundling implies it does |
| Maintenance of the medical record | Retention schedule, with the legal retention duty stated | Required by other law, so it is not a choice the patient can meaningfully decline. Presenting it as one is misleading |
| Sharing with labs, imaging and third party administrators | Processor arrangements, disclosed in the notice | These are operational necessities of the episode, not optional extras, and the patient should be told who they are |
| Insurance and claims submission | A separate, express permission. One analysis notes that the insurance regulator's 2024 master circular requires express consent each time medical records are shared, and that standing authorisations do not satisfy it | Two regulators, two standards, and the stricter one governs |
| Research and teaching | A separate choice, and only inside the research exemption's conditions | Withdrawable, and distinct from care. A patient declining research must still receive identical treatment |
| Personalised recommendations and health content | A separate marketing choice, default off | This is marketing wearing a clinical word. Naming it honestly is most of the fix |
| Promotional offers, camps and package campaigns | A separate marketing choice, default off, with per-channel options | The purpose #61 was written about. Without this box, a checkup campaign has no basis |
| Group entity and partner sharing | A separate choice naming the entities | Group is not a purpose. A patient cannot consent specifically to an unnamed list of companies |
Splitting the form is a one week piece of work and it is the highest return action available to a hospital compliance function. The reason it does not happen is that nobody owns the admission form: it belongs to the front office, it was drafted by a lawyer years ago, and marketing has never been asked about it. Finding the owner is usually harder than drafting the replacement.
The notice obligation, which arrives on 13 May 2027 and should be drafted now
Reported Rule 3 prescribes what a notice must contain, and the contents are more demanding than the one line privacy statement most hospital and pharmaceutical forms carry. Three requirements recur across every analysis we read.
| Reported requirement | What it means in a hospital or pharma context | Difficulty |
|---|---|---|
| Independently understandable, in clear and plain language | The notice must stand alone, which rules out the common approach of a clause buried inside a consent form the patient signs for treatment | Low. It is a drafting job |
| An itemised description of the personal data | Itemised, not categorised. Name, phone, diagnosis codes, imaging, billing, insurance identifiers, each listed rather than described as your health information | High. Most organisations do not know what they hold |
| The specified purposes, with a specific description of the goods or services provided or enabled | Purpose by purpose rather than a single omnibus statement | Medium. It depends on the purpose mapping being done first |
| A communication link to withdraw consent as easily as it was given, exercise rights, and complain to the Board | A working route, not an email address. Withdrawal that is harder than giving does not meet the standard | High. It is a product build and it needs a release |
| Availability in English and the scheduled languages | One analysis describes the notice being available in English and in up to twenty two languages on request | Medium, and underestimated. Translation of an itemised notice is not a trivial exercise |
The itemised description is the requirement that forces the real work, and it is why data discovery comes before drafting. A hospital cannot itemise what it holds until somebody has looked across the hospital information system, the laboratory system, the imaging archive, the billing system, the call recordings, the WhatsApp exports and the three spreadsheets that the outreach team actually runs on. That inventory is the project. The notice is the output.
Care to marketing, which is the boundary this page exists to draw
Consent taken for treatment does not support a marketing message, and every sector analysis we read says so in some form. The clearest formulation we found is that patient data gathered for care cannot be reused for marketing or research without fresh consent, and that secondary use requires a fresh legal justification which in practice usually means fresh consent.
| The communication | Basis it usually runs on today | Basis it actually needs |
|---|---|---|
| Appointment reminder for a booked appointment | The care relationship | Plausibly fine. Service communication tied to the episode the patient initiated |
| Discharge follow up call about recovery | The care relationship | Plausibly fine as clinical follow up. The line is crossed when the call carries an offer |
| Annual health checkup package offer | The admission consent form | A marketing basis the admission form does not provide. This is the gap #61 identified and deferred to this page |
| Camp invitation to everyone who attended last year | A list in a spreadsheet | Marketing consent, per channel, plus the telecom requirements for the sending route |
| Birthday or festival greeting with a hospital brand message | Nobody has ever asked | Marketing consent. It is promotional whatever the sentiment attached to it |
| Vaccination due reminder for a child | The paediatric record | Genuinely arguable and worth a legal view. Public health framing does not automatically make it a legitimate use, and the children's provisions add a second layer |
| Satisfaction survey after discharge | The care relationship | Plausibly fine as service quality, and it becomes marketing the moment it routes to a review request. Covered in #62 |
| Re-engagement campaign to lapsed patients | The clinical database | No basis in most hospitals. The purpose is acquisition and the data was given for care |
Row three is the one that funds most hospital marketing departments in India, which is why this analysis is unwelcome. The honest position is that a checkup package offer sent to a clinical database on the strength of an admission signature is marketing on a basis that was never given. The remedy is unglamorous and entirely available: ask patients separately, at a calm moment, with a real choice, and accept a smaller and lawful list. How that list is then worked is covered in hospital CRM and AI and AI patient engagement and retention in hospitals.
Processors, third parties and the ABDM question
A hospital's data protection risk is mostly other people's systems, and the sector analyses are unanimous that contracting it away does not work. Labs, third party administrators, insurers and cloud record vendors are processors, and their handling remains the hospital's liability. On the pharmaceutical side the same applies to contract research organisations, data management vendors, cloud providers, analytics firms, pharmacovigilance service providers and medical information vendors.
| Relationship | Likely role | The contract point to check |
|---|---|---|
| Diagnostic lab receiving a referral | Processor for the referred test, controller for its own records | Purpose limitation. Does the lab market to your patients from its copy? |
| Third party administrator or insurer | Separate fiduciary once the claim is theirs | Express consent for each sharing event, given the insurance regulator's position on standing authorisations |
| Cloud hospital information system vendor | Processor | Erasure propagation. Can the vendor actually erase on instruction, including from backups? |
| Marketing agency with access to patient lists | Processor, and the highest risk relationship on this list | Whether they should hold the list at all. Most should receive a segment, never the record |
| Telecom aggregator sending your messages | Processor, and the holder of your consent registry references | Consent evidence. Can you retrieve the consent record if the Board asks? |
| Contract research organisation | Processor or joint, depending on the actual data flow | Role allocation by flow rather than by label. One analysis is explicit that roles follow the flow |
| Data vendor supplying HCP records | Source, and your provenance problem | Field level provenance warranties, and an indemnity that means something |
| ABDM health information user | A separate fiduciary with its own basis | The consent artefact covers the exchange and nothing beyond it |
The Ayushman Bharat Digital Mission deserves its own paragraph because it is frequently misread as a compliance shortcut. The better analysis we read is that the mission and the DPDP Act regulate different things and sit alongside each other rather than one displacing the other. An ABDM consent artefact authorises a specific exchange between a health information provider and a health information user, and it is confined to that transaction. Using a diagnostic report afterwards for research, model training, promotion or insurer disclosure needs its own basis under the Act, and participation in the mission does not discharge the hospital's wider duties. The health data management policy itself requires participants to comply with other applicable laws.
One claim to treat with caution. A vendor source we read asserts that the mission's consent plumbing maps neatly onto the consent manager route under the Rules, and therefore that existing artefacts are reusable. That is an assertion with no primary citation behind it, and it would be a convenient conclusion for anybody selling consent infrastructure. The possibility is interesting and the planning assumption should be that you will need your own consent record.
Children's data, and the exemption that is narrower than it sounds
Children's data carries the heaviest obligations in the Act and a listed exemption that healthcare providers will be tempted to over-read. Verifiable parental or guardian consent is required for under eighteens, with the same route for a person with a disability through a lawful guardian. The exemption, reported as sitting in the Fourth Schedule, lists classes of entity and ties them to purposes.
| Reported element | What is listed | The limit on it |
|---|---|---|
| Exempted classes, Part A | Clinical establishments and mental health establishments. Healthcare professionals and allied healthcare professionals. Educational institutions, creches and child day care caregivers, and transport providers engaged by educational institutions | The class gets you into the exemption and the purpose decides whether it applies |
| Permitted purposes for those classes | Protection of a child's health. Educational activity tracking, safety related monitoring, and travel safety tracking for the education related classes | Protection of health, not communication about health. A reminder campaign is not obviously inside it |
| Part B purposes | Powers exercised in a child's interest under law, subsidies and benefits, creating an email only child account, real time location for safety, keeping detrimental content away from children, and confirming that a person is not a child | Permitted only as necessary for the stated purpose |
| What the exemption does not touch | The prohibition on processing detrimental to a child's wellbeing | Still applies in full. One analysis is explicit that the ban on detrimental processing survives the exemption |
| Verification method | Reportedly identity and age checks against reliable details already held, or through a digital locker or an authorised virtual token | A build, not a checkbox. Twelve months is not long for it |
The paediatric reading we would defend is narrow. A children's hospital treating a child relies on the exemption for the care itself, because that is protection of the child's health. A vaccination due reminder is closer to the line than it looks, and a package promotion to a paediatric list is clearly outside it. The penalty band for children's data obligations is reported at up to 200 crore rupees, which is the same band as a breach reporting failure, and considerably more than the catch-all. Paediatric marketing is therefore the highest penalty exposure in a hospital marketing function and almost nobody treats it that way.
The five obligations with hard edges
Most of the DPDP Act is principle and most of a compliance programme is judgement, but five obligations have edges sharp enough to fail an audit on. Each one below has either a number, a deadline or a named artefact attached, which makes them the places to start and the places a board will ask about.
Retention against erasure, and why a legal duty to keep is not a permission to use
Retention is the obligation healthcare gets most confused about, because two duties point in opposite directions and both are real. The Act requires erasure when the specified purpose is no longer served or consent is withdrawn, whichever is earlier, unless retention is necessary for compliance with another law. Healthcare has a great deal of other law.
| Record class | Reported retention duty | Instrument, as cited in the sources |
|---|---|---|
| Inpatient or indoor record | Three years from the commencement of treatment | Code of Medical Ethics Regulations 2002, regulation 1.3.1, cited by two of our sources |
| Indoor record on request | Produced within seventy two hours to the patient, an authorised attendant or a legal authority | Same regulation, cited by one source |
| Outpatient record | Genuinely unsettled. One source says typically three years, another says there is no single uniform national figure | Sources conflict. Take a view and document it |
| Clinical trial records | Five years after completion of the trial | New Drugs and Clinical Trials Rules 2019, rule 13(1) and (2), cited by one source |
| Telemedicine records | The period prescribed from time to time, with no fixed figure given | Telemedicine Practice Guidelines 2020, paragraph 3.7.2 onwards |
| Medico-legal, termination of pregnancy, minors | Longer, with no figure any source would state | Not stated in any source we read. This is the gap to take to counsel |
| Imaging | Not addressed in any source consulted | Nothing. A real gap in the published guidance |
| Processing logs and traffic data | Reportedly a minimum of one year before erasure, for specified purposes | Rule 8, with one source citing a schedule we could not confirm. Flagged in limitations |
One correction worth making loudly, because sector content gets it backwards. The Rules' three year inactivity erasure rule, with its forty eight hour advance warning to the person before deletion, reportedly applies to specified large platforms: e-commerce entities and social media intermediaries above twenty million Indian users and online gaming intermediaries above five million. A hospital is not in that list. Hospitals are bound by the general erasure duty, not by the inactivity clock, and a vendor telling a hospital it must delete after three years of inactivity has read the wrong provision.
The point that actually matters for marketing is the one most easily missed. A mandatory retention duty overrides the erasure duty for the period of the duty and authorises nothing else. Keeping an inpatient record for three years because the ethics regulations require it creates no permission to market from it, to analyse it commercially, or to include it in a campaign segment. The retained set and the marketable set are two different populations, and a hospital should be able to demonstrate that its campaign tooling reads only from the second.
One caveat on the 2002 regulations
Our sources cite the Code of Medical Ethics Regulations 2002 for the three year inpatient retention period, and none of them states whether those regulations remain in force in their original form. The National Medical Commission has issued professional conduct instruments since, including the guidelines of 6 October 2026 that our NMC ethical advertising guidelines page covers.
Confirm the current instrument and the current period before publishing a retention schedule on your website. A published schedule citing a superseded regulation is worse than no published schedule.
Breach notification, which has no stated threshold
Breach reporting is the obligation most likely to catch an organisation that is otherwise doing reasonably well, for one reason: there appears to be no severity threshold. One analysis we read states the point directly, that on a strict reading any personal data breach must be reported. For a hospital that means a mis-addressed patient mailing, a WhatsApp group with the wrong member, or a lost laptop with a clinic list on it.
| Reported obligation | Timing | What to prepare |
|---|---|---|
| Intimation to each affected data principal | Without delay | A template in plain language covering the nature of the breach, the likely consequences, the steps taken and a contact point |
| Notification to the Data Protection Board | Without delay | The channel, the authorised signatory, and a standing decision about who may send it at midnight |
| Detailed report to the Board | Within seventy two hours of becoming aware, reportedly extendable by the Board | The report format, pre-drafted. Seventy two hours is not enough time to design one |
| Describing the breach and the remediation | In the detailed report | A technical narrative somebody can write under pressure, and an incident log that supports it |
| No stated threshold | Applies to any personal data breach on a strict reading | A decision rule for what counts as a breach, written before you need it and reviewed by counsel |
| ABDM incident channel, if you participate | Not stated in the Rules sources | One vendor source says to notify the National Health Authority through the mission's channel. Confirm independently |
Seventy two hours is the figure to design around and it is shorter than it sounds, because the clock reportedly starts on becoming aware rather than on confirming. A hospital that learns of a problem on a Friday evening has a weekend inside the window. The deliverable is a runbook with named people, a pre-approved report format and a rehearsal, and it is worth building now regardless of commencement, because the drafting is the slow part and the obligation does not get easier with notice.
The penalty Schedule, which has seven entries and not four
Penalties are the most quoted and least accurately quoted part of the Act. The Schedule reportedly carries seven entries, and most summaries list the four largest and stop, which leaves out the one a marketing function is most likely to encounter.
| Reported breach | Maximum | Where a healthcare or pharma team meets it |
|---|---|---|
| Failure to take reasonable security safeguards, under section 8(5) | 250 crore rupees | The headline band. An unsecured database, a public bucket, an agency with a copy of the patient list |
| Failure to notify a breach to the Board or to affected people, under section 8(6) | 200 crore rupees | The band you reach by handling the first failure badly, which is the commonest escalation pattern |
| Breach of the additional obligations for children, under section 9 | 200 crore rupees | Paediatric lists and anything marketed to under eighteens. The largest unrecognised marketing exposure |
| Breach of Significant Data Fiduciary obligations, under section 10 | 150 crore rupees | Only once designated. No designations in the sources we consulted |
| Breach of a data principal's duties, under section 15 | Ten thousand rupees | Not your exposure. It applies to the individual, and it is in the Schedule |
| Breach of a voluntary undertaking | Up to the extent applicable to the original breach | After a settlement. Worth knowing before accepting one |
| Breach of any other provision of the Act or the rules | 50 crore rupees | The catch-all, and the realistic band for marketing failures. Notice, consent, purpose limitation, retention and rights all land here |
The last row is the correction this section exists to make. A number of published summaries list a separate fifty crore penalty for rights violations, and the Schedule we saw has no such entry: rights failures fall into the catch-all alongside everything else not separately listed. Cross-border transfer failures appear to have no dedicated entry either. The practical reading is that the marketing function's most likely failures sit in a fifty crore band rather than a two hundred and fifty crore one, except for children's data, where they sit in the second highest band in the Schedule.
On how the amount is actually set, our sources were weaker than we wanted. Two separate lists of the factors appeared in the same article, which is a sign that neither was taken from the statute. The factors common to both were the nature, gravity and duration of the breach, the type and sensitivity of the data, repetition, and mitigation. Treat the detail as unverified and the direction as clear: cooperation and remediation reduce the number, and the sensitivity of clinical data increases it.
GET ACTIONABLE AI AND HEALTHCARE INSIGHTS THAT HELP YOU STAY AHEAD IN A FAST-CHANGING PHARMA WORLD
Significant Data Fiduciary status, which is a twelve month build
Designation as a Significant Data Fiduciary is discretionary, nobody had been designated in the sources we read, and a large hospital chain or a top ten pharmaceutical company is an obvious candidate. The obligations reported under Rule 13 are not policy documents.
| Reported obligation | What it actually requires | Lead time |
|---|---|---|
| A Data Protection Officer based in India | Answerable to the board of directors or equivalent, and the primary grievance contact | A hire or a role change with a reporting line most organisations do not have |
| Independent data auditor | Compliance audits by an auditor who is not you | Procurement, then a first audit that will find things |
| Annual data protection impact assessment | At least once every twelve months, with significant observations reported to the Board | The first one is the long one, because it depends on the data inventory existing |
| Algorithmic due diligence | Ensuring that algorithmic and technical measures do not risk data principals' rights | The obligation most relevant to anybody using AI on patient or prescriber data, and the least specified |
| Localisation of specified personal data | Sources disagree. One describes transfer outside India as requiring government approval, another describes a power to require specified data and associated traffic data to remain in India on a committee's recommendation | Architecture. Unmovable at short notice |
The algorithmic due diligence line is the one to read twice if you are deploying AI on health data. An obligation to ensure that algorithmic measures do not create a risk to data principals' rights is broad, unspecified and audited annually, which means the defensible position is a documented one. That governance question is the subject of a dedicated page in this library rather than this one.
Consent managers, the decision that is live on 13 November 2026
Consent managers are the only part of the Rules that commences a full year before the rest, which makes them the first real decision rather than the last. A consent manager is reportedly an Indian company registered with the Board, with a minimum net worth of two crore rupees, providing an accessible, transparent and interoperable platform through which a person can give, manage, review and withdraw consent. It acts solely for the data principal, must not access the personal data passing through it, cannot subcontract its obligations, and reportedly keeps consent records for at least seven years.
| Route | What it gives you | What it costs you |
|---|---|---|
| Use a registered consent manager | An interoperable, certified record of consent that somebody else maintains, with the seven year retention obligation sitting on them | Dependency, integration work, and a third party in the consent path. Also a market that barely exists yet |
| Build your own consent record | Control, and no dependency on an immature market | You carry the evidence burden, the withdrawal propagation and the audit trail. Most organisations underestimate the last one |
| Do nothing until 2027 | Nothing | The eighteen month window is the whole point. A consent architecture decided in April 2027 will not be built by May |
Our recommendation, which is deliberately boring, is to build the internal consent record regardless. A consent manager may become the interface a patient or doctor uses, and it will not relieve you of knowing what you were permitted to do, when, by whom and through which channel. Every organisation needs that record; only some will need a consent manager. Build the one you certainly need first.
Where AI earns its place in a DPDP programme
Four jobs inside a DPDP programme are genuinely too large for a human team and one is genuinely unsuitable for a model, and knowing which is which is most of the value. The four are discovery, which means finding where personal data actually lives across hospital systems, CRMs, call recordings, representative tablets and the spreadsheets nobody declared. Classification, which means deciding field by field what is personal data, what is clinical, and what is a derived inference you created rather than received. Consent reconciliation, which means resolving the contradictions between what the admission form says, what the CRM holds, what the telecom consent registry records and what a representative was told verbally. And rights request triage, which means finding every copy of one person's record across every system inside the response window, which is the obligation most likely to expose how little anybody knows about the estate. The unsuitable job is choosing a lawful basis, which is a legal judgement with a named owner, and the hard constraint is that none of this work should involve personal data leaving your environment to be summarised by a public assistant. The output you want from AI here is a map and a reconciliation, not a document.
| The job | Why a team cannot do it by hand | What good output looks like |
|---|---|---|
| Discovery across systems | A mid sized hospital has personal data in twenty or more places and an inventory of four. The gap is in exports, recordings, attachments and local files | A ranked inventory with owner, system, volume and field level detail, refreshed rather than produced once |
| Field level classification | Thousands of columns, inconsistent naming, free text that hides clinical detail inside a comments field | A classification per field with a confidence score, and a queue of ambiguous cases for a human |
| Consent state reconciliation | Four systems hold four answers for the same person and none is authoritative. Reconciling a million records manually is not a project, it is a decade | A single resolved consent state per person per channel, with the conflicts logged rather than silently overwritten |
| Rights request triage | Finding every copy of one record inside a response window, across systems with different identifiers | A retrieval that returns every match with its system and its basis, assembled for a human to check and send |
| Free text risk scanning | Clinical detail sits in comment fields, call transcripts and chat logs that nobody classified as clinical | A flagged subset for review, and a rule that stops those fields reaching marketing tooling |
| Choosing a lawful basis | Not a volume problem. A judgement problem | Nothing. This is a named human decision, recorded with the reasoning, and a model's suggestion is not a defence |
The environment constraint is not a footnote and it is where most of this work will go wrong first. Patient feedback text, call transcripts and complaint records are personal data and some of them are clinical, and consent for care did not include pasting them into a public assistant to be summarised. Run the classification inside your own environment, with role based access, retention limits and an audit log. If you use a vendor, the processing terms matter considerably more than the dashboard, and the questions to ask are where the text goes and who can read it. The same point applied to feedback analysis in patient feedback and online reputation management, and it applies with more force here because the dataset is larger and less curated.
What to report, and what not to report
A DPDP programme reported on readiness percentage will produce a readiness percentage and very little else. The metrics below are the ones that cannot be gamed, because each of them is a count of something that either exists or does not.
| Stop reporting | Start reporting | Why |
|---|---|---|
| Percentage readiness against a framework | Number of systems in the inventory with a named owner | Readiness is a judgement and an inventory is a count. The second one finds the shadow systems |
| Policies published | Share of HCP and patient records with recorded provenance | A policy is a day's work and provenance is the real remediation. This number starts low and is the honest baseline |
| Consent captured | Share of contacts with a resolved consent state per channel | Captured counts forms. Resolved counts contradictions settled, which is the actual problem |
| Training completed | Number of marketing lists with a documented purpose and basis | Training is attendance. A list without a documented purpose cannot be sent to, whoever attended what |
| Nothing | Time to retrieve one person's complete record across systems | The rights request rehearsal, and the single most diagnostic number in the programme. Most organisations have never measured it |
| Nothing | Breach runbook rehearsals completed, and time to draft the report in the last rehearsal | Seventy two hours is the obligation. A rehearsal is the only evidence you can meet it |
| Nothing | Count of commercial communication templates registered and headers in use | The overdue regime, reported alongside the future one so it does not fall off the slide |
The fifth row is the metric to put in front of a board, because it converts an abstract obligation into an operational fact. Pick one real patient or one real doctor, ask the team to produce every copy of that person's data with the basis on which it is held, and time it. The number will be embarrassing the first time and it is the only measure in this list that cannot be improved by writing something.
Limitations, and what would change our mind
| Limitation | Why it matters | How it is handled here |
|---|---|---|
| We could not retrieve the gazetted Rules or the Act | Every rule number, section number and figure on this page comes from secondary analyses. Two retrieval attempts failed while writing | Stated at the top of the page and again here. Readers are told to verify against the gazette. The direction of each obligation is consistent across sources; the numbering is not verified |
| Three source disagreements remain unresolved | The commencement date differs by one day between sources. The voice call series is given as 160 by one source and 1600 by another. The seven day consent validity is attributed to service messages by one source and transactional by another | Each flagged at the point of use and marked low confidence. None of them changes a plan, and all three should be confirmed with a primary source or an aggregator |
| The cross-border position is described two different ways | One source reads the Act as permitting transfer only to notified jurisdictions, which is an allow-list. Others read it as a power to restrict transfer to specified countries, which is a block-list | Stated as unresolved rather than picked. The difference decides whether a global CRM is lawful by default or by permission, so it matters and we will not guess |
| Schedule numbering for the retention rule is uncertain | One analysis cites the Third Schedule for the large platform classes and another cites a Seventh Schedule for the log retention purposes | Described without the schedule number where we were unsure. The substance is consistent |
| The 2002 ethics regulations may have been superseded | Our retention figures for inpatient records rest on a 2002 instrument and no source stated whether it remains in force unamended | Flagged in its own callout. A hospital should confirm the current instrument before publishing a retention schedule |
| The telecom analysis is secondary and sender-focused obligations are thinly reported | The financial penalties in those regulations reportedly fall on access providers, so the sender-side consequences are described rather than enumerated | Described as attested or low confidence, source by source. Confirm with your telecom aggregator, who has commercial reason to know |
| No Significant Data Fiduciary designations are reflected | The sources consulted predate any designation, and a designation would change a large hospital chain's obligations substantially | Stated as of the sources. Check for designations before relying on the section |
| We sell doctor data and AI services to pharma and hospitals | We benefit if organisations build data governance and HCP data programmes | Declared twice, in the doctor database section and in the closing box. Note that the page tells you the exclusion our category relies on is narrower than our category treats it |
What would change our mind. A published Data Protection Board decision in a health or pharmaceutical matter would replace most of the inference on this page with a rule, and it is the single development to watch. Clear guidance on whether a professional register entry sits inside the publicly available exclusion would settle a question on which an entire Indian data industry is currently relying on a reading. A Significant Data Fiduciary designation of a hospital chain or a pharmaceutical company would turn the Rule 13 section from contingency planning into a project. And primary confirmation of the voice call series and the consent validity period would let us remove two low confidence rows from a table that compliance teams will act on.
Conclusion: fix the regime that is already live, then build for 2027
The DPDP Act is a serious statute with serious penalties and it is not the most urgent thing on a pharmaceutical or hospital marketing compliance desk today. The telecom commercial communication rules bind now, carry consequences that reach telecom resources rather than balance sheets, and sit almost entirely outside the DPDP project plans being drawn up across the industry. The pharmaceutical marketing code has been live since March 2024 with an annual self-declaration behind it. The hospital advertising guidelines have been live since October 2026. Three regimes, three clocks, and the one with a 2027 date is the one getting the attention.
On the DPDP work itself, the sequence that survives contact with reality starts with discovery rather than with policy. Find where personal data lives, itemise it, record provenance field by field, resolve consent state per channel per person, then write the notice. A notice drafted before the inventory exists will describe an organisation that does not exist, and the itemised description requirement makes that visible.
Two findings on this page are worth carrying away even if nothing else is. The Act creates no separate sensitive data category, so writing a healthcare policy around one is writing to a framework the Indian statute does not use, and the sensitivity of clinical data enters through the penalty calculation instead. And the publicly available exclusion that the Indian data industry relies on answers only whether the Act governs your database, not whether you may send a single message from it. Those two points together dispose of most of what is confidently said about data protection in Indian healthcare marketing.
The conclusion a marketing lead will not enjoy is that the lawful list is smaller than the current one. A hospital that asks patients separately for marketing permission will end up with fewer contacts than its clinical database holds, and a pharmaceutical company that records provenance honestly will find a significant share of its field data has none. Both of those are findings rather than failures, and both are considerably better discovered by your own team in 2026 than by a regulator later. The remaining contribution of a marketing function here is to know exactly which names it may contact, through which channel, for which purpose, and to be able to prove it in an afternoon.
Frequently Asked Questions For DPDP Act Compliance Checklist for Pharma and Healthcare Marketing
The Act requires a lawful basis for every HCP and patient record you process, a prescribed notice, honouring withdrawal and rights requests, a retention schedule and breach reporting, with the substantive Rules reportedly commencing 13 May 2027. It does not, on its own, decide whether you may send a message. A promotional SMS or voice call to an Indian mobile number is governed by the telecom commercial communication regulations, in force now, which require registered headers and content templates, consent recorded through the telecom consent registry and the designated number series. The practical effect on a pharmaceutical marketing function is therefore two programmes rather than one: an overdue commercial communication fix and an eighteen month data governance build. Verify all clause references against the gazetted text.
The Rules were reportedly notified on 13 November 2025 with a phased commencement. Published analyses describe Rules 1, 2 and 17 to 21 taking effect on publication, Rule 4 on consent managers at twelve months, which is 13 November 2026, and Rules 3, 5 to 16, 22 and 23 at eighteen months, which is 13 May 2027. The main tranche is the one that carries notice, security safeguards, breach reporting, retention, children's data, Significant Data Fiduciary duties, rights and cross-border provisions. One source gives 14 May 2027 rather than 13 May, and the government press release on the Rules is dated 14 November 2025, so take the exact dates from the gazette.
Reportedly no, and this is the most consequential misunderstanding in Indian healthcare compliance content. Two of the three sector analyses we read state that the Act creates no separate sensitive or special category of personal data, so a diagnosis and a mobile number are subject to the same consent standard. Sensitivity enters through the factors weighed when a penalty amount is set, not through a higher standard of processing. The practical consequence is that a healthcare policy drafted around a sensitive data category is written to a framework the Indian statute does not use. Write to the uniform standard and carry the sensitivity in the risk register instead.
No, not without a separate basis, and every sector analysis we read says so. The clearest formulation is that data gathered for care cannot be reused for marketing or research without fresh consent, because the specified purpose was care. The single admission form covering treatment, records, group sharing, research, personalised recommendations and promotional offers is bundled consent and will not survive the specificity requirement. The fix is to split that form into purpose specific choices with marketing defaulted off and per-channel options, which is a week of work and the highest return action available to a hospital compliance function.
A doctor's professional details are personal data, and the exclusion for publicly available data is narrower than the industry treats it. The Act reportedly does not apply to data the person made publicly available themselves, or that another person was under a legal obligation to publish, which gives a plausible argument for a State Medical Council register entry and no argument at all for a mobile number from a delegate list, a prescription pad or an unexplained purchased file. Critically, the exclusion decides whether the Act governs the data and says nothing about whether you may send a message, which the telecom regulations and the pharmaceutical marketing code govern. The derived fields that make a database commercially valuable, such as prescribing estimates and segments, were never publicly available by anybody.
No. Section 7(a) covers the specified purpose for which somebody voluntarily provided their data, and the statute's own illustration shows how narrow that is. In the illustration a person asks a broker for help finding accommodation, the broker may process the data for that purpose, and once she says she no longer needs help the broker shall cease processing. Applied to pharma, a doctor who requested a product monograph gave you a basis to send the monograph and not to add them to a newsletter. A number a representative copied from a clinic board was never voluntarily provided to you and has no basis under 7(a) at all. The other legitimate uses cover medical emergencies, epidemics and disasters, which are not marketing situations.
The Schedule reportedly has seven entries: up to 250 crore rupees for failing to take reasonable security safeguards, 200 crore for failing to notify a breach, 200 crore for the additional obligations relating to children, 150 crore for Significant Data Fiduciary duties, ten thousand rupees for a data principal's own duties, an amount matching the original breach for breaking a voluntary undertaking, and 50 crore for any other provision. The last entry matters most for marketing, because notice, consent, purpose limitation, retention and rights failures land there rather than in the headline band. Several published summaries list a separate fifty crore penalty for rights violations, and the Schedule we saw has no such entry. Children's data is the exception where a marketing failure reaches the second highest band.
Reportedly without delay to each affected person and to the Data Protection Board, with a detailed report to the Board within seventy two hours of becoming aware, extendable by the Board. One analysis notes that no reporting threshold appears, so on a strict reading any personal data breach is in scope, including a mis-addressed patient mailing or a messaging group with the wrong member. The clock reportedly starts on becoming aware rather than on confirming, which means a Friday evening discovery spends its weekend inside the window. Write the runbook, pre-draft the report format, name the people who may send it out of hours, and rehearse it once. Seventy two hours is not enough time to design a process.
They override it for the period of the legal duty and they authorise nothing else, which is the distinction that matters. The Act requires erasure when the purpose ends or consent is withdrawn, unless retention is necessary for compliance with another law, and healthcare has a good deal of such law: one source cites three years from the commencement of treatment for inpatient records under the 2002 ethics regulations, and five years after completion for clinical trial records under the 2019 trials rules. Keeping a record because the law requires it creates no permission to market from it, analyse it commercially or include it in a campaign segment. The retained population and the marketable population are different sets, and a hospital should be able to show its campaign tooling reads only from the second.
Probably not immediately, and the decision is live from 13 November 2026 rather than 2027, which makes it the first real choice. A consent manager is reportedly an Indian company registered with the Board, with a minimum net worth of two crore rupees, providing an interoperable platform for giving, managing, reviewing and withdrawing consent, which must not access the data passing through it and reportedly keeps records for at least seven years. Our recommendation is to build the internal consent record regardless, because a consent manager may become the interface and will not relieve you of knowing what you were permitted to do, when, by whom and through which channel. Every organisation needs that record. Only some will need a consent manager.
No. The better analysis is that the Ayushman Bharat Digital Mission and the DPDP Act regulate different things and sit alongside each other. A mission consent artefact authorises a specific exchange between a health information provider and a health information user and is confined to that transaction, so using a diagnostic report afterwards for research, model training, promotion or insurer disclosure needs its own basis. The health data management policy itself requires participants to comply with other applicable laws, and participation does not discharge a hospital's wider duties. One vendor source claims the mission's consent plumbing maps onto the consent manager route, which is an assertion with no primary citation behind it and should not be a planning assumption.
Two things this month, neither of which is a policy. First, ask marketing operations to show you the registered headers, the registered content templates and where consent for promotional SMS and voice is recorded, because that regime is live and the consequence for using an ordinary ten digit number for commercial calls is reportedly disconnection of telecom resources for up to two years. Second, pick one therapy area or one clinic, take every contact record, and try to answer how each contact detail reached you. The share you cannot answer is the size of your remediation, and it is a more useful number than any readiness assessment. The third action, once those are underway, is the data inventory that the notice obligation will require from 13 May 2027.
GET ACTIONABLE AI AND HEALTHCARE INSIGHTS THAT HELP YOU STAY AHEAD IN A FAST-CHANGING PHARMA WORLD
Let's Discuss Your Requirements