At about 3 a.m. on 18 October 2026, staff at Kamalnayan Bajaj Hospital in Chhatrapati Sambhajinagar found they could not generate bills. The hospital management information system had stopped, and all nine servers were inaccessible. Medical Dialogues reported that a ransom note later claimed the files were encrypted and sensitive data stolen. Billing, insurance claims and benefits under government health schemes all slowed down.

Now picture the same night after 13 May 2027. Rule 7 of the DPDP Rules would require the hospital to inform the Data Protection Board without delay. A detailed report would have to follow within 72 hours. Each affected patient would also need to hear from the hospital, without delay, about what happened. None of that is possible if nobody can say what sat on those nine servers, or whose records they held.

This is why data discovery is the first DPDP task for any hospital. Every later duty assumes you know where personal data lives. In healthcare, that map runs far beyond the HIS. It reaches imaging archives, insurer mailboxes, telemedicine platforms and doctors' phones. With roughly six months left on the 18-month clock, this article shows where to look and what to record.

Why health data raises the stakes

The DPDP Act has no separate category of sensitive personal data. A discharge summary and a delivery address attract the same baseline duties under Section 8. Health data still changes the risk for a hospital in practical ways.

Scale and sensitivity. Section 10(1)(a) names "the volume and sensitivity of personal data processed" as the first factor for notifying a Significant Data Fiduciary. A hospital chain holding years of patient records fits that description closely. An SDF must appoint a Data Protection Officer based in India and engage an independent data auditor. It must also run periodic Data Protection Impact Assessments. Designation needs a government notification, so large chains should plan for it now.

Penalty exposure. The Act's Schedule sets its highest ceilings for the failures that discovery helps prevent. As LiveLaw summarised in September, security-safeguard failures can attract up to ₹250 crore. Breach-notification and children's-data failures sit in ₹200 crore tiers.

Patient trust. A leaked password can be reset. A leaked HIV result or psychiatric note cannot. Patients who doubt a hospital's discretion may hold back information their doctors need.

The systems everyone lists first

Most hospital inventories start with the core clinical and financial systems. That is the right place to begin. Where the Clinical Establishments Act applies, Rule 9(iv) of the 2012 Central Government Rules already expects electronic records. It requires establishments to maintain and provide electronic medical or health records of every patient. The Supreme Court quoted the rule in full in a November 2022 order.

The difficulty is that each core system leaks copies into places nobody tracks.

SystemWhat it holdsWhere copies escape
HIS or HMISRegistration, admissions, billing, dischargeReporting databases, old instances after upgrades
EMRClinical notes, diagnoses, ordersFree-text fields with names and phone numbers
LISOrders, results, sample barcodesReport PDFs sent by email and portals
PACSImages and DICOM headersTeaching folders, CDs, modality workstations
PharmacyPrescriptions, dispensing recordsStandalone software outside the HIS
Billing and TPA deskClaims, policy numbers, estimatesClaim files in shared mailboxes

Radiology deserves a closer look. Every DICOM image file carries a header with attributes such as Patient's Name (0010,0010), Patient ID and birth date. The DICOM standard's Annex E on attribute confidentiality lists a long series of such fields, from allergies to the referring physician. It also warns that cleaning the header does not de-identify the image itself. Names burned into the pixel data need separate handling. A folder of "anonymised" teaching scans can still identify patients.

Where patient data hides

The core systems are where data is supposed to live. Discovery proves its value in the places nobody listed. Look hard at these six.

Scanned admission and consent forms. Admission desks scan forms, ID proofs and consent sheets into PDFs. Those files often land on shared drives or in document systems outside the HIS. Once scanned, they are digital personal data like any other record.

TPA and insurer email. Cashless claims move as email attachments. Discharge summaries, itemised bills and investigation reports go to third-party administrators and insurers. Copies then sit in Sent folders and shared mailboxes for years. Billing teams also keep local copies to chase rejected claims.

WhatsApp and personal phones. A 2021 pilot study in the Indian Dermatology Online Journal surveyed 119 dermatologists. Nearly 73% photographed patients on personal smartphones. Of those who answered, 86.3% shared images in professional WhatsApp groups. Only 14.4% routinely recorded consent in the clinical record. The sample is small, but most clinicians will recognise the pattern. Section 8(1) holds a Data Fiduciary responsible for processing "by it or on its behalf". A hospital should treat images taken during its care as its own responsibility.

Telemedicine records. The FAQs on the Telemedicine Practice Guidelines tell doctors to keep phone, email, chat and video interaction logs. Doctors must also retain the reports, images and documents used in each consultation. Those records usually sit on a vendor's platform outside the HIS.

Shared drives and spreadsheets. Quality teams, infection control and MIS staff build spreadsheets from HIS exports. Discharge registers, readmission lists and incident logs often carry names and UHIDs. Few of them appear in any system inventory.

Research and audit datasets. Rule 16 exempts processing necessary for research, archiving or statistical purposes. The exemption applies only when processing follows the standards in the Second Schedule. An extract copied to a researcher's laptop without those safeguards gets no cover from Rule 16. Discovery should find every such extract and record which standard it meets.

Data your processors hold

Hospitals outsource more data handling than most boards realise. Reference labs process samples. Transcription vendors handle dictated notes. Revenue-cycle agencies work claims. Cloud HIS vendors, appointment apps and teleconsultation platforms host records for the hospital.

Section 8(1) makes the hospital responsible for processing done on its behalf by a Data Processor. Section 8(2) requires a valid contract with each processor. Rule 6(1)(f) requires that contract to provide for reasonable security safeguards. Section 8(7)(b) requires the hospital to cause its processors to erase data when its own erasure duty arises.

Discovery here means mapping each outbound flow: which partner, which data, which system and which contract. Some partners may be Data Fiduciaries in their own right, such as a reference lab issuing its own reports. Record which role each one plays.

This matters because patients can ask. Under Section 11(1)(b), a patient can seek the identities of all other fiduciaries and processors her data was shared with. "All" is a demanding word when vendor lists live separately with procurement, IT and individual departments.

Classification that matters under DPDP

Information security teams already label data as confidential or restricted. Those labels help with access control. They don't answer DPDP questions, as we explained in common DPDP misreadings. For a hospital, four tags do most of the work.

TagWhy it matters
Patient or staffStaff records may rest on Section 7(i) employment uses. Patient records rest on consent or uses such as Section 7(f) emergencies.
Child or adultThe Fourth Schedule relief covers only health services to the child.
Retention lawSection 8(7) allows retention only where another law requires it.
Shared withNeeded for Section 11(1)(b) requests and Section 8(7)(b) erasure.

Retention needs the same care. Regulation 1.3.1 of the 2002 medical ethics regulations requires physicians to keep indoor patients' records for three years from the start of treatment. Regulation 1.3.2 requires records to be issued within 72 hours of a request. Three years is a floor. Other laws may set longer periods for particular record types. Map each record type to the specific law that justifies keeping it. Records held without such a law face erasure under Section 8(7) once their purpose ends.

How discovery feeds every later duty

Notice and consent. You cannot describe data you haven't found. A notice drafted from the HIS data dictionary will miss what the insurance desk and imaging archive collect.

Rights requests. Section 11(1)(a) gives a patient the right to a summary of her personal data and the processing around it. A rights request workflow can only search systems it knows exist.

Retention and erasure. Erasure under Section 8(7) has to reach every copy, including those held by vendors. An undiscovered spreadsheet is an erasure failure waiting to happen.

Security. Rule 6(1)(a) expects measures such as encryption, masking or tokenisation. Rule 6(1)(c) expects logs and monitoring that can detect unauthorised access. You cannot encrypt or monitor a store nobody knows about.

Breach reporting. Rule 7(1) requires the notice to each patient to describe the breach and its likely consequences for her. Rule 7(2)(b) requires detailed information to reach the Board within 72 hours. Both depend on knowing which records sat on the affected system.

Discovery as a standing control

A discovery exercise finished in December will start going stale by spring. Hospitals add data stores all the time. A new CT scanner arrives with its own workstation. A department signs up for a teleconsultation app. A new TPA joins the panel. A research team pulls an extract for a study. An acquired clinic brings its own software.

Treat discovery as a recurring control with clear triggers. Re-scan on a fixed cycle. Add a discovery check to every procurement, vendor onboarding and research approval. Report coverage to the Board through continuous assessment and reporting, alongside other compliance measures. The first full scan takes the longest. Later scans mostly catch drift.

A checklist built on one question

Start with a question patients will be able to put to you from 13 May 2027. If a patient asked for every record you hold on them, how many systems would you need to search? Work through these checks to answer it honestly.

CheckOwnerEvidence to keep
List every system holding patient data, including modality and pharmacy softwareCIOSystem register with owners
Scan shared drives, mailboxes and document stores for UHIDs and report PDFsCISOScan results and clean-up log
Inspect DICOM headers and burned-in text in teaching and research foldersRadiology head and ITSample checks, de-identification method
Record every processor and partner, with data shared and contract statusProcurement and DPOVendor register, security clauses
Tag records as patient or staff, child or adultDPOClassification rules, coverage report
Map each record type to the law that sets its retentionMedical records and legalRetention schedule with citations
Set rules for clinical images on phones and messaging appsMedical directorPolicy, approved tool, training records
Run a mock access request for one patient across all systemsDPOSystems searched, time taken

The last check is the honest test. If the team can name every system before the search begins, the inventory is working. If they find new stores during the search, the inventory isn't finished. A DPDP gap assessment gives that first pass a structure and a deadline.

The patient's question is the test

Hospitals digitised care one system at a time, and patient data followed every new system. The DPDP Act does not ask hospitals to undo that. It asks them to know it. Every duty that follows, from a breach notice to an erasure request, rests on that knowledge. Find the data first, and the rest of the programme has something solid to stand on.

Sources

  1. Medical Dialogues, "Cyberattack hits 9 servers at Chhatrapati Sambhajinagar Hospital, FIR registered", 28 October 2026. Link
  2. DPDPA.com, "Rule 7 of DPDP Rules 2025: Intimation of personal data breach", text of the Rules notified November 2025. Link
  3. DPDPA.com, "Rule 6 of DPDP Rules 2025: Reasonable security safeguards", text of the Rules notified November 2025. Link
  4. DPDPA.com, "Rule 16 of DPDP Rules 2025: Exemption from Act for research, archiving or statistical purposes", text of the Rules notified November 2025. Link
  5. DPDPA.com, "Fourth Schedule, DPDP Rules 2025", text of the Rules notified November 2025. Link
  6. DPDPA.com, "Section 8 DPDPA: General obligations of Data Fiduciary", text of the Act, 2023. Link
  7. DPDPA.com, "Section 10 DPDPA: Additional obligations of Significant Data Fiduciary", text of the Act, 2023. Link
  8. DPDPA.com, "Section 11 DPDPA: Right to access information about personal data", text of the Act, 2023. Link
  9. DPDPA.com, "Section 7 DPDPA: Certain legitimate uses", text of the Act, 2023. Link
  10. LiveLaw, "Compliance Without Court: What DPDPA Board's Vacancy Means For May 2027", 10 September 2026. Link
  11. Supreme Court of India, "Record of Proceedings, Writ Petition (Civil) No. 648/2020", 3 November 2022. Link
  12. DICOM Standards Committee, "DICOM PS3.15 2026b, Annex E: Attribute Confidentiality Profiles", 2026. Link
  13. Indian Dermatology Online Journal, "Clinical Photography in Dermatology: Perception and Behavior of Dermatologists, A Pilot Study", July 2021. Link
  14. Board of Governors in supersession of the Medical Council of India, "FAQs on Telemedicine Practice Guidelines", April 2020. Link
  15. National Medical Commission, "Code of Medical Ethics Regulations, 2002", amended up to October 2016. Link
  16. Khaitan & Co, "Indian Computer Emergency Response Team Direction: Paradigm Shift in Cyber Incident Reporting", 30 April 2022. Link