Updated:
Templates: generative AI policy and 21 vendor questions
“We don’t know where to start writing” is a common problem for hospitals. Here are four drafts: press the button, copy, and replace “__” with your own details.
These are the author’s drafts, not legal advice and not a version that is ready to copy as is. Adapt them to the size, systems and contracts of your hospital, and show them to counsel or your compliance office before they become documents.
Contents
- 1. Generative AI use policy
- 2. Twenty-one questions for a vendor
- 3. Text for patients
- 4. Incident record
Related pages: Roadmap, Patient data checklist, Checklist: records and AI vendors.
1. Generative AI use policy
A page you can hand to staff. Replace "__" with your hospital’s details.
GENERATIVE AI USE POLICY, "__" HOSPITAL (DRAFT) 1. Purpose Sets rules for staff of "__" when they use generative AI tools (chatbots, summarising tools, translation tools). 2. What must NOT be entered - Patient names, registration or UHID numbers, dates of birth, addresses, phone numbers, or the content of patient records. - Images or recordings that could identify a patient. - Contracts, or restricted financial and personnel data. Exception: a tool the data protection officer (or the person named in clause 5) has approved in writing, under a written contract with the vendor. 3. Approved tools Only tools on the approved list kept by "__" (owner: __). Using an unapproved tool for work is not allowed. 4. Review of output A person is responsible for every AI-generated text used in work. Check facts, numbers and names against the source before use. AI output is never entered in a patient record until the responsible clinician has reviewed and approved it. 5. Reporting If patient information was entered into an unapproved tool, report it the same day to __ (name, phone __). Do not try to delete it yourself first. 6. Training Staff who use AI tools are trained on this policy, and the training is recorded. Owner: __. Review date: __.
Basis of the template
- The ban on entering patient information into unapproved tools rests on the DPDP Act’s rules that the hospital is responsible for processing done on its behalf and may engage a processor only under a valid contract (sections 8(1) and 8(2)).
- The rest is the author’s proposal.
2. Twenty-one questions for a vendor
Print it and take it to the vendor presentation. Write the answers down.
TWENTY-ONE QUESTIONS FOR AN AI VENDOR (DRAFT) Write the answers down and attach them to the contract. Device status 1. Do you treat this product as a medical device under the Medical Devices Rules, 2017? If not, why not? 2. If yes, which risk class (A, B, C or D), and which licence or permission do you hold for this software and this intended use? May we see it? 3. What is the intended use statement, and does our planned use match it? 4. Is the software a stand-alone product or part of another device? If part of a device, whose licence covers it? 5. Do you have an Algorithm Change Protocol, and which changes does it cover? 6. How will we be told before an update reaches our wards, and can we delay it? 7. How is an update rolled back, and who tells our staff? Performance and monitoring 8. On which patients was the tool tested, and how does that compare with ours, including languages and regions? 9. Which performance figures do you monitor after go-live, how often, and will you share them with us? 10. How do you address AI bias and cybersecurity risks, and what do you ask us to watch for? Patient data 11. For what purposes will you process our patient data, and nothing else? Will you use it to improve your own product? 12. Will you sign a written contract that makes you our data processor before any patient data is shared? May we see your standard form? 13. Which sub-processors (cloud, model providers) will touch the data, where is it processed, and are they bound to the same terms? 14. What security safeguards do you apply, described so that we can compare them with section 8(5) of the DPDP Act? 15. How and how fast do you tell us of a personal data breach, and who answers at night? 16. How is data erased when consent is withdrawn or the contract ends, including in logs, backups and by your sub-processors? 17. How does your tool support our notice and consent in English and in the patient’s language? Operations 18. Who at our hospital gets more work with this tool, and who reviews its output? 19. What does the exit plan look like, including return or erasure of data? 20. Which decisions affecting patients will the tool’s output feed into, and who checks the completeness, accuracy and consistency of the data it uses? 21. What is your support commitment and escalation path for safety issues?
Basis of the template
- Questions 1–7: CDSCO’s Guidance Document on Medical Device Software (CDSCO/MD/GD/MDSW/01/2026) and the Medical Devices Rules, 2017, Rule 4.
- Questions 11–17 and 20: sections 4, 6, 8(1)–(7) of the DPDP Act, 2023.
- The other questions are the author’s proposals, not legal requirements.
3. Text for patients
A short example of how to tell a patient that the hospital uses an AI tool. Match it to your actual practice.
TEXT FOR PATIENTS: OUR USE OF AN AI TOOL (EXAMPLE) "__" hospital uses an AI tool for __ (for example: drafting discharge summaries, which a clinician then checks). The tool does not make decisions about your treatment. A member of our staff reviews what it produces. We process your personal data for this purpose only. Before we ask for your consent we give you a notice that says which data and why, how to exercise your rights and how to complain to the Data Protection Board. You can read this notice in English or in __ (language). You can withdraw your consent at any time as easily as you gave it. Questions: __ (name or office, phone, email).
Basis of the template
- The notice and consent content follows sections 5 and 6 of the DPDP Act, 2023.
- The wording is the author’s example, not required language.
4. Incident record
Turn the procedure into one fillable page and keep it where people will find it at night and on weekends.
PERSONAL DATA INCIDENT RECORD (DRAFT) Date and time discovered: __ Discovered by: __ Reported to: __ What happened (one sentence, no patient names): __ Systems and data involved (type of data, approximate number of patients): __ Was it unauthorised processing, accidental disclosure, acquisition, sharing, use, alteration, destruction or loss of access? __ Did it compromise confidentiality, integrity or availability? __ Containment done: __ By: __ Time: __ Who decides whether this is a personal data breach: __ Intimation to the Data Protection Board: who files: __ Form and deadline as set in the current Rules: __ Filed on: __ Intimation to each affected patient: who sends: __ Method: __ Sent on: __ Vendor involved: __ (contact: __, 24-hour line: __) Recorded: __ (who contacted whom, and when).
Basis of the template
- DPDP Act 2023, section 2(u) (definition of a personal data breach) and section 8(6) (intimation to the Board and each affected person). The deadline and form are in the Rules, which this site could not open; fill them in from the current Rules.
Sources and date checked
- CDSCO — Guidance Document on Medical Device Software (Doc No. CDSCO/MD/GD/MDSW/01/2026) (opens in a new tab)
- CDSCO — Medical Devices Rules, 2017 (full text) (opens in a new tab)
- Gazette of India (Extraordinary), 11 Aug 2023 — The Digital Personal Data Protection Act, 2023 (No. 22 of 2023), copy hosted by PRS Legislative Research (opens in a new tab)
Sources checked November 7, 2026. Rules and procedures change, so rely on the current text on the official source page.
The material on this site is general information for education. It does not replace diagnosis or medical advice for a specific patient, and it is not legal advice or a purchasing recommendation. For rules and policy, rely on the primary official sources.