Updated:
Templates: generative AI policy and 20 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
Related pages: Roadmap, Patient data checklist, Checklist: AI vendors and documents.
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, PPS numbers, medical record 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 that "__" has approved in writing for that data type (see clause 3). 3. Approved tools and permitted data Only tools on the approved list kept by "__" (owner: __). For each approved tool the list states which data types may be entered, following our data classification, and states where the tool stores and processes data and whether the provider keeps or re-uses it. 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. Generative AI can state fictitious content as fact, so 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. Where AI-generated content is shown to others, label it as AI-generated. 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, including the data input restrictions and how to report an incident, and are re-trained after significant updates. Owner: __. Review date: __.
Basis of the template
- The data input rules follow the Data Protection Commission’s AI guidance (personal data typed into AI tools can raise security and data protection risks; know where it goes and whether it is retained or re-used) and GDPR Article 9 (health data is special category data).
- Human review of output follows HIQA’s January 2026 draft (AI should augment, not replace, human judgement; clinical staff remain responsible) and the AI for Care strategy’s “human in the loop” principle.
- The rest is the author’s proposal.
2. Twenty questions for a vendor
Print it and take it to the vendor presentation. Write the answers down.
TWENTY QUESTIONS FOR AN AI VENDOR (DRAFT) Write the answers down and attach them to the contract. Status and rules 1. Do you treat this product as a medical device? Which conformity route applies, and may we see the CE-marking details? 2. What is the intended purpose statement, and does our planned use match it? 3. Do you see the product as a high-risk AI system under the EU AI Act (Article 6(1) or Annex III)? Why or why not? 4. Which functions are AI-enabled, and what type of model is used? 5. How was the solution validated, on which data sets, and what are its limits? 6. Does your product interact directly with patients? How does it tell them they are talking to an AI system? Oversight and updates 7. What do your instructions for use say about human oversight, and what training does an overseer need? 8. How will we be told before an update reaches our wards, and can we delay it? 9. How is an update rolled back, and who tells our staff? 10. What logs does the system keep, who controls them, and for how long? Patient data 11. What personal data does the system use, where does it go and who can see it, including sub-processors and cloud providers? 12. Do you retain our data or re-use it to train or fine-tune a model? On what basis? 13. Who is controller and who is processor for this service, and where is that written in the contract? 14. Can the system support access and deletion requests for personal data held in it? 15. How many hours until you tell us of a breach, and who answers at night? 16. How is data erased when the contract ends, including logs, backups and sub-processors? Operations 17. Will you help us with our data protection impact assessment, with the documentation we need? 18. Which decisions affecting patients will the output feed into, and does a person make the final decision? 19. What does the exit plan look like, including return or erasure of data? 20. What is your support commitment and escalation path for safety issues?
Basis of the template
- Questions 1–6: MDR Article 2(1) and Annex VIII rule 11, AI Act Articles 6 and 50(1).
- Questions 7–10: AI Act Article 26(1), (2), (5) and (6); HPRA’s page on field safety corrective actions (software updates).
- Questions 11–17: the DPC’s AI guidance and GDPR Articles 33 and 35.
- 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 the final decision about your treatment. A member of our staff reviews what it produces. We tell you which of your information the tool uses and why. You can ask us about it and about alternatives. Questions: __ (name or office, phone, email).
Basis of the template
- HIQA’s draft and the AI for Care strategy stress transparency about when, where and why AI is used in care; the draft also says the service should explain the tool’s role.
- 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.
AI / DATA / DEVICE INCIDENT RECORD (DRAFT) Date and time discovered: __ Discovered by: __ Reported to: __ What happened (one sentence, no patient names): __ Systems, devices and data involved (type of data, approximate number of individuals): __ Kind of incident (tick): AI tool error or safety issue __ Medical device event __ Personal data breach __ Software update problem __ Containment done: __ By: __ Time: __ Reporting clocks (check the current text of each document; keep the rows that apply): - Personal data breach: controller notifies the Data Protection Commission without undue delay and, where feasible, within 72 hours of becoming aware, unless unlikely to result in a risk (GDPR Article 33). Notified on: __ - Breach likely to result in a high risk to people: tell the people affected without undue delay (GDPR Article 34). Done on: __ - Serious incident with a device (death, serious deterioration in health, serious public health threat): report to HPRA (online form, devicesafety@hpra.ie, post or phone). HPRA sets no hospital deadline; our own target: __ . Reported on: __ - Serious incident with a high-risk AI system: inform the provider first, then the importer or distributor and the market surveillance authorities; suspend use if there is a risk (AI Act Article 26(5)). Done on: __ Affected individuals notified: who sends: __ Method: __ Sent on: __ Vendor involved: __ (contact: __, 24-hour line: __) Recorded: __ (who contacted whom, and when).
Basis of the template
- The clocks come from GDPR Articles 33 and 34, HPRA’s reporting page and AI Act Article 26(5). Check each document for later revisions; this page does not state Irish statutes, which were not read.
Sources and date checked
- European Union — Regulation (EU) 2024/1689 (Artificial Intelligence Act), Official Journal L, 12.7.2024 (opens in a new tab)
- European Union — Regulation (EU) 2016/679 (General Data Protection Regulation) (opens in a new tab)
- European Union — Regulation (EU) 2017/745 (Medical Device Regulation), as published in the Official Journal on 5.5.2017 (opens in a new tab)
- Data Protection Commission (Ireland) — AI, Large Language Models and Data Protection (18 July 2024) (opens in a new tab)
- HPRA — Reporting medical device & IVD safety issues (for hospitals and healthcare professionals) (opens in a new tab)
- HPRA — Managing field safety corrective actions (for hospitals) (opens in a new tab)
- HIQA — Draft National Guidance for the Responsible and Safe use of AI in Health and Social Care Services, for public consultation (January 2026, PDF) (opens in a new tab)
Sources checked November 15, 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.