4 min read

Nasscom and MeitY Announce DPDP Readiness Workshops For May 2027 Deadline

Nasscom and MeitY have scheduled nationwide DPDPA readiness workshops to help organizations operationalize data governance, contract updates, and incident response before the May 13, 2027 enforcement deadline.

Written byVipul Abhishek· Former Advocate, Supreme Court of India

Last updated:

What happened

In October 2026, Nasscom published Volume 8, Issue 10 of its Government Policy and Engagement Monthly Mailer. The trade association announced a nationwide workshop series in direct collaboration with the Ministry of Electronics and Information Technology (MeitY). The initiative prepares the IT-ITeS industry for the Digital Personal Data Protection Act, 2023. The publication confirmed that main operational duties under the Act are scheduled for May 13, 2027. The workshops evaluate compliance across data governance structures, contract updates, technological systems, records management, and incident response readiness.

Does the DPDP Act apply here?

The scheduled May 13, 2027 enforcement applies to all entities processing digital personal data within India. General Counsel at large healthcare enterprises process high volumes of patient records. This volume makes them primary candidates for Significant Data Fiduciary (SDF) designation under the DPDP Act. The Act governs patient health records, diagnostic data, and employee files, but excludes anonymised data and corporate intellectual property. HealthTech platforms cannot adopt the same broad compliance frameworks as consumer apps. They need specific operational mapping to handle verifiable data flows without incurring massive outside counsel spend on ambiguous assessment projects.

Legal implications under DPDP

Section 4 of the Digital Personal Data Protection Act, 2023 specifies that consent is the primary basis for processing, except where Section 7 legitimate uses apply. Healthcare fiduciaries must implement itemised notices and maintain consent records as detailed in the DPDP Rules, 2025. The MeitY readiness workshops focus heavily on contract updates. Large enterprises must amend vendor agreements to allocate liability for processor failures. The Rules, 2025 require that any personal data breach triggers an intimation to affected Data Principals without delay. Fiduciaries must then submit a detailed incident report to the Data Protection Board of India within 72 hours. Defensibility during an audit depends directly on how quickly a legal team retrieves system records and processor logs.

Could this happen to you

The workshops indicate that MeitY expects full operational readiness rather than mere paper compliance. If a hospital network or diagnostic platform fails an audit after May 13, 2027, the regulator will demand immediate proof of governance structures and breach response mechanisms. A processor breach exposing patient histories invites intense regulatory scrutiny. General Counsel face severe litigation risk and potential penalties up to 250 crore rupees if processor contracts lack strict indemnity and limitation of liability clauses. A healthcare organization must prove it can isolate compromised systems and notify the DPBI within the 72-hour window. Manual tracking spreadsheets fail under this time pressure.

What companies should do in the next 30 days

1. Identify your high-risk data flows. Legal teams must direct the IT department to map patient data processing to specific vendor systems and output a clear data inventory document.

2. Review vendor contracts. The General Counsel must draft data processing addendums requiring vendors to notify the enterprise of a breach within 24 hours to satisfy the 72-hour regulatory window.

3. Update consent notices. Compliance leads must replace legacy privacy policies with the itemised notice format required by the DPDP Rules, 2025.

4. Establish incident response protocols. Draft a breach response playbook that defines who drafts the DPBI notification and who holds authority to engage outside counsel.

What to watch

Exactly 203 days remain until the DPDP hard compliance deadline of 13 May 2027. Section 18 of the Act establishes the Data Protection Board of India. Legal teams should monitor central government notifications finalizing the location of the Board headquarters. The Nasscom and MeitY workshops will reveal how regulators interpret processor accountability in enterprise environments. Evaluate your current defensibility and contract gaps using a soft self-assessment tool before scheduling expensive outside counsel review. Map your patient data flows at https://www.complydp.com/audit-preview to identify where your operational gaps exist today.

Sources

Frequently asked questions

Does the May 2027 compliance deadline apply to healthcare enterprises?

Yes. The May 13, 2027 deadline applies to all entities processing digital personal data within India. Healthcare enterprises process high volumes of patient data and are strong candidates for Significant Data Fiduciary designation, requiring strict operational compliance.

What happens if a healthcare vendor experiences a data breach?

Under the DPDP Rules, 2025, the fiduciary must intimate affected Data Principals without delay and submit a detailed report to the Data Protection Board within 72 hours. General Counsel must ensure vendor contracts include strict indemnity and mandatory 24-hour notification clauses to avoid penalties up to 250 crore rupees.

How does the DPDP Act treat medical diagnostic data?

The DPDP Act governs medical diagnostic data as digital personal data when processed in digital form. Consent is the primary basis for processing, except where Section 7 legitimate uses apply, requiring healthcare providers to use itemised notices per the Rules, 2025.

Should we hire outside counsel for DPDP operational readiness?

Legal teams should handle initial data flow mapping and self-assessment internally to control outside counsel spend. Once the internal data inventory is clear, outside counsel can review specific contract clauses and liability allocations for defensibility.