Ambient AI scribe consent in India: what the law requires DPDP notice and consent, the vendor contract, retention, breach duties and the NMC rules, with a consent script.

If a clinic uses an ambient AI scribe that records the consultation, Indian law asks the doctor for four things: a notice and consent that meet sections 5 and 6 of the Digital Personal Data Protection Act, 2023; a written contract with the scribe vendor under section 8(2); erasure and breach duties under section 8 and the 2025 Rules; and the confidentiality that regulation 7.14 of the 2002 conduct regulations already imposes. The detailed DPDP obligations start eighteen months after the Rules were published on 13 November 2025, so a clinic buying a scribe today is preparing for mid-2027, while the professional duties apply now.

What an ambient scribe records

An ambient scribe is a microphone plus a model. It listens to the whole room for the visit and turns the audio into a draft note. It captures the patient's voice and history, the doctor's questions, and whatever the companion in the room says. Some products keep the audio, some only a transcript, and some send both to a server outside India. Section 2(x) of the DPDP Act defines processing as any automated operation on digital personal data and lists "collection, recording, organisation, structuring, storage" among the examples, and section 3 applies the Act to data collected in digital form or digitised later. The companion's words are personal data about the companion too.

Notice and consent under the DPDP Act

Section 4 allows processing only with the Data Principal's consent or for one of the legitimate uses in section 7. For a scribe, consent is the ground to plan for. Section 7(a) covers data the patient volunteers for a specified purpose, and a patient who came for a prescription did not volunteer a recording of the room. Section 7(f) covers "responding to a medical emergency involving a threat to the life or immediate threat to the health" of a person. That describes a collapse at the door rather than a routine OPD visit; ask a lawyer before relying on it for everyday recording.

Section 6(1) sets the standard: consent must be "free, specific, informed, unconditional and unambiguous with a clear affirmative action", limited to the data needed for the purpose. Section 6(3) requires the request in clear and plain language, in English or any Eighth Schedule language, with the contact details of a person who can answer the patient. Section 6(4) lets the patient withdraw as easily as she consented, and section 6(6) then requires the clinic and its processors to stop. Section 6(10) puts the burden of proof on the clinic: in a proceeding, it has to prove the notice was given and the consent obtained.

Section 5 requires a notice before or with every consent request, stating the personal data and the purpose, how the patient can exercise her rights, and how she can complain to the Data Protection Board. Rule 3 of the DPDP Rules, 2025 adds that the notice must stand on its own, give "an itemised description" of the data and the specific purpose, and give the means to withdraw. A line buried in the registration form will not do. For a child, section 9(1) asks for verifiable consent of the parent or lawful guardian first, which matters in a paediatric OPD. Our post on the DPDP Act for clinics covers the general duties.

The clinic is the Data Fiduciary, the vendor is the Data Processor

Section 2(i) defines a Data Fiduciary as the person who determines the purpose and means of processing. The clinic decided to record and chose the product, so the clinic is the fiduciary. The vendor processes on the clinic's behalf and is a Data Processor under section 2(k). Section 8(2) allows the clinic to use a processor "only under a valid contract", and section 8(1) keeps the fiduciary responsible "irrespective of any agreement to the contrary" for processing done on its behalf. If the vendor leaks the audio, the Board's questions come to the clinic.

Rule 6 sets the security floor: encryption or masking, access control, logs of who opened the data, and under rule 6(1)(f) a clause in the processor contract on security safeguards. Rule 6(1)(e) and rule 8(3) require those logs and the data behind them to be kept for one year. The contract needs clauses on each, and on what the vendor does when a patient withdraws consent.

Retention and erasure

Section 8(7) tells the fiduciary to erase personal data when the patient withdraws consent or when the specified purpose is no longer served, whichever is earlier, and to make its processor erase it too, unless a law requires retention. Once the doctor has approved the note, the audio has served its purpose, and no professional rule asks for the recording itself to be kept. The note is a medical record: regulation 1.3.1 of the 2002 regulations requires indoor records to be kept for three years, and regulation 1.3.2 requires copies within 72 hours of a request. The Third Schedule under rule 8(1) sets fixed erasure periods only for large e-commerce, gaming and social media platforms, so a clinic works from section 8(7) and the one-year log minimum. In practice: keep the audio for days, then only the approved note.

If the audio leaks

Section 8(6) requires the fiduciary to inform the Board and each affected Data Principal of a personal data breach. Rule 7(1) says the patient must be told without delay, in plain terms, what happened, what it means for her, what the clinic is doing and whom to contact. Rule 7(2) requires an initial description to the Board without delay and a detailed report within seventy-two hours of becoming aware. A vendor who finds the breach must tell the clinic fast enough for the clinic to meet that clock, and the contract should say so. Our post on what DPDP requires after a patient data breach has the steps.

The NMC rules that apply now

The DPDP duties above have a commencement date; the professional duties do not wait. Regulation 7.14 of the Indian Medical Council (Professional Conduct, Etiquette and Ethics) Regulations, 2002 says the doctor "shall not disclose the secrets of a patient that have been learnt in the exercise of his / her profession" except in court under the judge's orders, where there is a serious and identified risk to a specific person or community, or for notifiable diseases. Regulation 2.2 adds that confidences about a patient's personal or domestic life "should never be revealed". A recording sent to a vendor's server is a disclosure the doctor has to justify; consent plus a contract is how. The NMC's Registered Medical Practitioner (Professional Conduct) Regulations, 2023 were held in abeyance by the amendment notification of 23 August 2023, so the 2002 text remains operative; our guide to the professional conduct regulations covers the rest of it.

The NMC's Guidelines on Ethical Advertising and Public Communication, public notice R-13014/01/2024-Ethics of 6 October 2026, are about advertising, but clause 7.2(d) is written broadly: "Any use of patient information as input for an AI system shall comply with applicable privacy, confidentiality, data-protection and professional-ethics requirements." Clause 7.4 bars sharing patient data that can be identified publicly. Read with regulation 7.14, feeding a consultation to an AI system is a professional-ethics question as much as a technical one. Our post on the NMC advertising guidelines covers the rest of the notice.

What the ICMR guidelines add

The ICMR's Ethical Guidelines for Application of Artificial Intelligence in Biomedical Research and Healthcare (2023) are an ethics framework, not law. Three of its principles bear on a scribe. Autonomy: patients "should be fully informed about the use of AI technologies" and "must have complete autonomy to choose or reject AI technologies". Data privacy: identifiable patient data "should preferably be anonymized unless keeping it in an identifiable format is essential". Accountability: AI for health "should always be appropriately supervised", with a human in the loop. For a scribe that means the doctor reads and signs the note; the machine does not file it.

A consent script and signage

Consent under section 6 needs a clear affirmative action, so a spoken yes recorded in the note or a tick on a form is the minimum, and the notice comes first. A script for the desk or the doctor, in the patient's language:

"Doctor uses a recording tool that listens during the consultation and writes the notes. The recording goes to [vendor name] and is deleted after [N] days; the notes stay in your file here. You can say no and the doctor will type the notes instead, and you can withdraw later by telling the desk. Do you agree to the recording today?"

• Put the same text on an A4 notice at the desk and in the consultation room, in English and the local language, with the name and phone number of the person who answers data questions (section 6(3), rule 9).
• Ask the companion too, or have them step out while it records.
• Record the yes: a tick box on the registration form or a dated line in the visit note. Section 6(10) makes the clinic prove it.
• Keep a no-recording path ready every day, with no change in fee or waiting time: the doctor types, or dictates after the patient leaves.

Vendor checklist

Ask these in writing before the trial and keep the answers with the contract. Our security questions for clinic software under DPDP cover the rest of the stack.

1. Where does the audio go? Name the country and every sub-processor: speech engine, language model, cloud host.
2. What is kept and for how long: audio, transcript, note? Who can delete it, and does deletion reach every copy and backup?
3. Is any recording or transcript used to train the model? The answer should be a written no, or a written opt-out switched on for the clinic.
4. Who at the vendor can listen to a recording, under what approval, and is each access logged for one year (rule 6(1)(c) and (e))?
5. Is there an off-switch the doctor controls in the room, and a per-patient skip for the patient who says no?
6. How quickly does the vendor tell the clinic of a breach, so the clinic can meet the 72-hour report under rule 7(2)?
7. Does the contract name the clinic as Data Fiduciary and the vendor as Data Processor, with the security clauses rule 6(1)(f) expects, and a deletion date for when the clinic stops paying?