Updated:
Checklist: AI vendors and documents
When a vendor offers AI software, three questions come up together: are we a deployer with our own duties, is it a regulated medical device or a high-risk AI system, and what changes when the tool is updated. This page puts them in one place, each with its basis.
In short: a hospital that uses an AI system is a deployer under the EU AI Act; software can be a medical device under the MDR, which HPRA applies in Ireland without approving products; and HIQA’s guidance and the Department of Health’s strategy keep a person in charge and ask for governance, transparency and an inventory of AI tools.
- This is not an official checklist. It is the author’s list built from the documents cited; each item gives its basis.
- The documents cited do not decide whether a particular product is a medical device or a high-risk AI system. That depends on its intended purpose; ask the vendor in writing.
- HIQA’s final guidance PDF could not be opened; its January 2026 draft is cited and marked as a draft.
- Items marked “author’s recommendation” are not requirements.
A. Which rules apply to this hospital?
Three sets of rules meet in a hospital AI project. Write down which of them your tool touches.
| No. | What to check | Basis |
|---|---|---|
| 1 | You have recorded that the hospital is a deployer: a person or body using an AI system under its authority. Deployers have their own duties under the AI Act, separate from the vendor’s. | AI Act Article 3 (definition of deployer, as quoted in HIQA’s draft); HIQA draft guidance (January 2026), Principle 1 |
| 2 | You have asked whether any in-house development makes the hospital a provider of an AI system or the manufacturer of a medical device. HIQA’s draft says it would then carry provider obligations under the AI Act and manufacturer obligations under the MDR or IVDR. | HIQA draft guidance (January 2026), Principle 1; MDR Article 5(5) |
| 3 | You have checked the dates: the AI Act applies from 2 August 2026 in general, and Article 6(1) (AI in products such as medical devices) from 2 August 2027, as published. Check whether EU amendments changed them. | AI Act Article 113 |
B. Is it a medical device, and is it high-risk?
HPRA monitors devices in Ireland but does not approve them, so the evidence has to come from the vendor.
| No. | What to check | Basis |
|---|---|---|
| 4 | The vendor has said in writing whether it treats the product as a medical device and why. The MDR’s definition names software intended by the manufacturer for a medical purpose such as diagnosis, prediction, prognosis or treatment. | MDR Article 2(1); HPRA overview for hospitals |
| 5 | If it is a device, the vendor states the class and its reasoning. Rule 11 puts software that informs diagnostic or therapeutic decisions in class IIa, and in IIb or III if the decision could cause serious or irreversible harm. | MDR Annex VIII, rule 11 (text as published in 2017) |
| 6 | You have asked how the vendor sees Article 6(1) of the AI Act: an AI system is high-risk when it is a product (or safety component) covered by Annex I legislation such as the MDR and must undergo third-party conformity assessment. | AI Act Article 6(1), Annex I Section A points 11 and 12 |
| 7 | For uses outside devices, you have checked whether the tool is in Annex III, for example evaluating eligibility for public healthcare services or emergency healthcare patient triage. | AI Act Annex III point 5(a) and (d) |
C. What the vendor must show
Ask for these in writing and keep the answers with the contract.
| No. | What to check | Basis |
|---|---|---|
| 8 | The instructions for use say how human oversight is meant to work, and you can assign it to people with the competence, training, authority and support the AI Act asks for. | AI Act Article 26(1) and (2) |
| 9 | The vendor tells you how its system informs people that they are interacting with AI, where it talks to patients directly, unless that is obvious. | AI Act Article 50(1) |
| 10 | The vendor describes validation, data sets and the limits of the tool in writing. (Author’s recommendation; HIQA’s draft also stresses documentation for explainability, traceability and auditability.) | HIQA draft guidance (January 2026), Principle 1 (author’s recommendation) |
D. Updates, incidents and reporting
Updates change a tool after you approved it. Ask how they reach you before signing.
| No. | What to check | Basis |
|---|---|---|
| 11 | There is a documented process to receive, review and pass on manufacturer field safety notices to clinical, technical and procurement staff, including notices that involve software updates. | HPRA, Managing field safety corrective actions |
| 12 | The incident card says who reports serious device incidents to HPRA (death, serious deterioration in health or a serious public health threat), by online form, email, post or phone, and who tells the vendor. HPRA sets no hospital deadline. | HPRA, Reporting medical device & IVD safety issues |
| 13 | For high-risk AI systems, the deployer monitors operation, informs the provider and the market surveillance authority of risks, suspends use if needed, reports serious incidents, and keeps logs it controls for at least six months. | AI Act Article 26(5) and (6) |
E. What the hospital does itself
A vendor’s paperwork does not replace the hospital’s own governance.
| No. | What to check | Basis |
|---|---|---|
| 14 | A list of authorised AI tools is kept, someone is assigned to maintain the inventory, and risk assessments follow existing risk management procedures. (HIQA’s January 2026 draft gives these as examples; the final text may differ.) | HIQA draft guidance (January 2026), Principle 1 |
| 15 | Staff who use the tool are trained before go-live, including its limits, and workers have been told where the AI Act requires it. | AI Act Articles 4 and 26(7) |
Next
Frequently asked questions
- Does a vendor’s CE mark mean the tool is right for our hospital?
- No. HPRA says it monitors devices on the Irish market and does not approve them, and the AI Act and HIQA’s draft both put duties on the hospital as deployer: oversight, monitoring, logs, training and transparency to patients. The vendor’s validation is a starting point for your own testing.
- A vendor says its product is not a medical device. What do we do?
- Ask for the reasoning in writing, tied to the intended purpose the manufacturer states. The MDR’s definition turns on that intended medical purpose. Then ask whether the product could still be high-risk under Annex III of the AI Act. Take the answers to your regulatory team.
- Which dates matter for AI in medical devices?
- As published in the Official Journal, the AI Act applies generally from 2 August 2026, and Article 6(1) (AI in products covered by the MDR or IVDR that need third-party conformity assessment) with its corresponding obligations from 2 August 2027. We did not read later EU amendments, so check the current text.
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) 2017/745 (Medical Device Regulation), as published in the Official Journal on 5.5.2017 (opens in a new tab)
- HPRA — Overview of medical device & IVD regulation for hospitals (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.