Hospital AI Lab Practical information on medical AI for Irish hospitals

Updated:

New AI tool, patient data: when do we need an impact assessment?

Before an AI tool goes live on patient data, GDPR Article 35 may require a data protection impact assessment. When, who is involved, and the 72-hour breach clock.

“Do we need a DPIA for this?” is one of the first questions a project team asks the data protection officer. The honest answer sits in two articles of the GDPR, and in a short note from Ireland’s Data Protection Commission.

Why patient data is special

Article 9(1) places data concerning health among the special categories of personal data whose processing is prohibited unless a condition in Article 9(2) applies. Condition (h) covers processing necessary for medical diagnosis, the provision of health or social care or treatment, or the management of health or social care systems and services, on the basis of Union or Member State law or under a contract with a health professional. Article 9(3) adds that such data should be processed by or under the responsibility of a professional subject to professional secrecy.

When an impact assessment is required

Article 35(1) says that where processing, in particular using new technologies, is likely to result in a high risk to people’s rights and freedoms, the controller must carry out an assessment before the processing. Article 35(3)(b) names processing on a large scale of special categories of data. A hospital rolling out an AI tool across many patients’ records is close to that description, though whether a given project meets it is a judgement for your data protection officer. Article 35(2) asks the controller to seek the officer’s advice.

The Data Protection Commission’s guidance on AI says an assessment may be needed, especially where the technology or processing is new to the organisation, where data sets are combined or where data about vulnerable people is used. It adds that doing one can be good practice anyway.

If the tool is a high-risk AI system under the AI Act, Article 26(9) says deployers use the information the provider gives under Article 13 to help carry out their GDPR impact assessment where applicable. Ask your vendor for that information early.

The breach clock

If something goes wrong, Article 33(1) asks the controller to notify the supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware, unless the breach is unlikely to result in a risk to people’s rights and freedoms. The processor must tell the controller without undue delay (Article 33(2)). Write the vendor’s alert time, in hours, into the contract.

Key takeaways

  • Health data is special category data; Article 35 requires an impact assessment before high-risk processing, naming large-scale use of special category data.
  • Involve your data protection officer, and use the provider’s information for the assessment.
  • A personal data breach has a 72-hour clock for the controller. This is general information, not legal advice; Irish statutes were not read for this post.

Sources: Regulation (EU) 2016/679 (GDPR) (Articles 9, 33 and 35); Regulation (EU) 2024/1689, Article 26(9); Data Protection Commission, AI, Large Language Models and Data Protection (18 July 2024). Read on 15 November 2026.

This article is part of a series

All series

← Blog