It's a little before three in the morning at the emergency entrance of a multi-specialty hospital. A man in his sixties is wheeled in with chest pain, and his son reaches the registration counter a few minutes later. Within ten minutes the son has given his name, mobile number and relationship. He has handed over his Aadhaar card for photocopying. He has signed the consent for an angiography and an undertaking to pay the bill.

By morning his number sits in the hospital information system (HIS), the billing module, the insurance desk's email thread and a nursing-station WhatsApp group. A visitor pass with his photograph hangs around his neck. In most HIS builds he exists as a few fields on his father's record, under a heading like next of kin.

Under the Digital Personal Data Protection Act, 2023 (DPDP Act), he is a Data Principal in his own right. He's owed his own notice, his own purpose limits and his own erasure date. Most of the Act's operative provisions, including Sections 4 to 17, apply from 13 May 2027. Yet most hospital DPDP programmes we review in our healthcare work start and end with the patient. The attendant doesn't appear in the data map at all.

Two roles, one person at the counter

The attendant plays two roles, often in the same minute. Separating them is the first design decision for your admission process.

In the first role, he acts for the patient. Section 2(j) brings the parents or lawful guardian of a child within the meaning of Data Principal. It does the same for the lawful guardian of a person with disability, acting on her behalf. A mother admitting her eight-year-old is the Data Principal for the child's data as well as her own.

That second limb is narrower than most hospitals assume. Under Rule 11 of the DPDP Rules, 2025, the hospital has to verify that a court, a designated authority or a local level committee appointed the guardian. The last two operate under the Rights of Persons with Disabilities Act, 2016 and the National Trust Act, 1999.

So the son signing for his unconscious father is usually not his father's guardian in DPDP terms. Hospitals routinely accept a relative's signature on clinical consent, and they'll keep doing so. That signature gives him no standing over his father's data rights. The only DPDP route for that is nomination under Section 14, made by the father before he lost capacity.

In the second role, he is an individual handing over his own data. His mobile number, his ID, his signature, his face on CCTV and his UPI handle on the deposit receipt all belong to him. Storing them inside the patient's file doesn't turn them into patient data.

Most admissions mix both roles on a single form. This is how the data splits:

What the attendant providesWhose data it isRole
Patient's history and insurance cardPatientActing for the patient
Child's details, given by a parentChild, with the parent inside the definitionActing for the patient
Name, mobile and relationshipAttendantOwn data
ID copy and photo for the passAttendantOwn data
Signature on the payment undertakingAttendantOwn data
Image on ward and corridor CCTVAttendantOwn data

The admission desk is where the file starts

Front-office teams collect attendant data because the forms ask for it, and the forms rarely get reviewed. In a typical inpatient admission, attendant details turn up in these places:

  • the registration form or HIS screen
  • the general consent and high-risk procedure consent forms
  • the financial responsibility or deposit undertaking
  • the attendant pass, often with a photograph
  • the insurance desk's cashless request
  • the discharge contact and the feedback call list

Paper offers no shelter. Section 3(a) covers personal data collected on paper and digitised later. The signed form that gets scanned into the records system at discharge falls within the Act from that point. We've covered this in our piece on paper records and scanned documents.

If your team has already traced where patient data sits across hospital systems, run the same exercise for attendants. List them as a separate category of Data Principal in your data map, with their own purposes and systems named.

Language matters at this desk too. Many attendants travel from another state and can't read the form's language. Section 5(3) requires the hospital to offer the notice in English or any language in the Eighth Schedule. Our note on consent for people who cannot read the form covers how to do that at a busy counter.

The ID-copy problem

Ask a front-office manager why the attendant's Aadhaar gets photocopied. The answers are usually security and the payment undertaking. Few can point to a rule that requires a copy.

Section 6(1) limits consent to the personal data necessary for the specified purpose. The Act illustrates this with a telemedicine app whose consent is read down to exclude the user's contact list. A colour copy of both sides of an Aadhaar card is hard to defend if the purpose is confirming who signed an undertaking.

The Aadhaar rules add their own layer. Regulation 5 of the Aadhaar Sharing of Information Regulations, 2016 applies to anyone collecting an Aadhaar number or a document that carries it. The collector must tell the holder the purpose and whether giving it is mandatory. It must also explain any alternatives and take consent for collection, storage and use. Regulation 6(5) bars keeping the number or document longer than that purpose needs.

Very few attendant pass systems meet these conditions. Fixing it doesn't need a project. Accept any government photo ID and check it against the person standing there. Record the ID type and the last four digits, then hand the card back. Where a copy is truly needed, black out the Aadhaar number before it goes into the file.

Emergency admissions and Section 7(f)

Section 7(f) is the clause hospitals reach for at 3 a.m. It permits processing to respond to a medical emergency that threatens life or poses an immediate threat to health. The threat can be to the Data Principal or to "any other individual".

That wording covers the attendant. The hospital can take the son's number to reach him about his father's emergency without stopping for a consent form. No one should hand a frightened relative a privacy notice before the cath lab opens.

But 7(f) is tied to responding to the emergency. It doesn't stretch to the deposit reminder the next morning or the feedback SMS after discharge. It certainly doesn't cover a health-check offer three months later. For the attendant's own data, those uses need notice and consent.

There's a second consequence that few hospitals have spotted. Sections 11 and 12 grant access, correction and erasure where the Data Principal gave consent, including data voluntarily shared under Section 7(a). Data held only under Section 7(f) falls outside that wording. So the ground recorded against each field decides which rights the attendant can later use. Your HIS has to know which is which.

When the attendant is the guardian

Children are the clearest case. A parent admitting a child sits inside the Data Principal definition for the child's data under Section 2(j). Section 9(1) normally requires verifiable parental consent before any processing of a child's data. The Rules switch that off for hospitals in one situation.

Part A of the Fourth Schedule exempts clinical establishments where processing is restricted to providing health services to the child. The exemption runs only to the extent needed to protect her health. So the paediatric ward needn't run a Rule 10 identity check on a parent before treatment begins.

The exemption stops at health services. Enrolling the child in a birthday-wishes programme or a parenting newsletter brings Section 9(1) back. And Section 9(2), which bars processing likely to harm a child's well-being, applies throughout.

Adults who can't decide for themselves are harder. The relative who signs for an unconscious patient is usually neither a Rule 11 guardian nor a Section 14 nominee. His access to the patient's records runs through medical law instead. Regulation 1.3.2 of the 2002 medical ethics regulations requires records to be issued within 72 hours when the patient or an authorised attendant asks. That route predates the DPDP Act and still works. It just isn't a DPDP right.

The practical answer is to offer nomination at admission. Section 14 lets a Data Principal nominate someone to exercise her rights on death or incapacity. The Act defines incapacity as unsoundness of mind or infirmity of body. A planned admission for surgery is the natural moment to ask. Build nomination into the same rights request process that handles access and erasure.

Where attendant data travels

Attendant data rarely stays at the counter. This is the path it most often takes in a multi-specialty hospital.

The insurance leg moves fastest. The Part C cashless request form used by insurers and third-party administrators (TPAs) asks for the contact number of the attending relative. Its hospital declaration records whether the patient or a representative signed. Business Today reported in May 2024 that IRDAI's master circular requires insurers to decide cashless requests within an hour. Final discharge authorisation must come within three hours. At that pace the attendant's details reach the insurer before anyone thinks about notice. So the notice has to be ready at the desk.

Two duties follow. Section 8(3) requires accuracy, completeness and consistency where data is disclosed to another Data Fiduciary. A wrong mobile number passed to an insurer is a compliance problem as well as a service one. Where the attendant's data rests on consent, Section 11(1)(b) lets him ask which Data Fiduciaries and Data Processors received it. Your TPA records should answer that in one lookup. We've set out the contract side in third-party vendor compliance under the DPDP Act.

Family WhatsApp groups and visitor CCTV need a decision too. Section 4 allows processing only on consent or a listed legitimate use. Section 7(i) is written for employees and doesn't reach visitors. No clause in Section 7 names premises security. So decide the ground for visitor CCTV and ward updates on purpose, and write down why. A DPIA covering the admission process is a sensible place to work it through.

Retention after discharge

Some attendant data stays with the medical record. The signed consent and the payment undertaking form part of the indoor-patient file. Regulation 1.3.1 requires indoor records to be kept for three years from the start of treatment. Section 8(7) permits retention that another law requires, so those signatures stay with the file.

Everything else needs an end date. The visitor-pass database, the ID copies, the ward WhatsApp group, the feedback list and the CCTV archive serve purposes that end soon after discharge. Section 8(7) requires erasure once it's reasonable to assume the purpose is no longer served. For Aadhaar copies, Regulation 6(5) points the same way.

Two cautions apply. Rule 8(3) requires a Data Fiduciary to keep personal data, traffic data and logs for at least a year. It does so for the purposes listed in the Seventh Schedule. Agree its reading with counsel before you set a 30-day purge. And Section 8(7)(b) requires processors to erase as well, which covers the visitor-management vendor and the messaging platform.

Breach response works the same way. Section 8(6) requires intimation to each affected Data Principal, and Rule 7 sets out what that intimation must say. If an HIS breach exposes attendant records, those attendants are owed a notice just like the patients. You can only send it if you know which records are theirs.

A working checklist for the admission desk

Most of this can be done before 13 May 2027 without new software. Start with the form and the consent and notice design, then work outwards.

StepOwnerWhat good looks like
Map attendant dataDPO with front officeAttendants listed as their own category, systems named
Split the formFront office and legalSeparate patient and attendant sections, each with a notice
Fix the ID practiceFront office and securityCheck, record type and last four digits, return the card
Record the groundHIS teamA ground field per attendant item, 7(f) flagged
Check guardianshipMedical recordsGuardian papers checked against Rule 11
Offer nominationAdmissionsSection 14 nomination offered at planned admissions
Log TPA sharingInsurance deskEvery disclosure logged by recipient
Set end datesDPO and ITErasure dates for passes, ID copies, groups and CCTV

If you're starting from a blank page, a DPDP gap assessment that walks the attendant's path will size the work quickly.

The person in the plastic chair

Hospitals already accept that the attendant matters. The 2002 medical ethics regulations name the authorised attendant as someone who can ask for the patient's records. The DPDP Act asks for the same recognition of the attendant's own data. He came in to help someone else. Give him his own notice and his own end date, and one of the quieter gaps in hospital compliance closes.

Sources

  1. Legislative Department, India Code, "The Digital Personal Data Protection Act, 2023 (as on 19 November 2025)", 19 November 2025. Link
  2. MYND Integrated Solutions, DPDP Wiki, "Children's data and persons with disability under the DPDP Act", 9 September 2026. Link
  3. MYND Integrated Solutions, DPDP Wiki, "The DPDP Rules, 2025 explained: what each rule does", 9 September 2026. Link
  4. Unique Identification Authority of India, "The Aadhaar (Sharing of Information) Regulations, 2016, updated as on 21.08.2025", 21 August 2025. Link
  5. National Medical Commission, "Code of Medical Ethics Regulations, 2002, amended up to 8 October 2016", 8 October 2016. Link
  6. Zurich Kotak General Insurance, "Request for Cashless Hospitalisation for Health Insurance Policy, Part C, ZK 24-25 v1", 2024. Link
  7. Business Today, "Hospitals and health insurers cannot take you for a ride over claims. Here's what is new", 30 May 2024. Link