If your patients' personal data has been lost, altered, disclosed or accessed by someone who should not have had access, you have a data breach. The controller, that is you, notifies the Garante without undue delay and, where possible, within 72 hours of becoming aware of it, unless it is unlikely to present a risk to people's rights and freedoms. If the risk to patients is high, you also inform them directly. In any case the breach is recorded in an internal register, whether or not notification is required.
What a breach is
The GDPR (art. 4, point 12) defines it as a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, personal data transmitted, stored or otherwise processed. The definition does not concern cyber-attacks alone. The European guidelines (EDPB 9/2022) give examples of loss such as a device containing a copy of the customer database being lost or stolen, or the only copy of a set of data being encrypted by ransomware, or encrypted with a key the controller no longer has.
In a medical practice the concrete cases take this form:
- a phone, tablet or laptop with patient photos or folders is lost or stolen;
- an email with a report or a photo reaches the wrong person;
- a member of staff opens patient folders they are not treating;
- encryption software (ransomware) makes the data unreadable, and the copy does not exist or does not work;
- a former member of staff keeps their credentials and continues to access.
The last one is a common case: what the Garante has sanctioned in health records deals with access that was authorised but not for care purposes.
Losing a phone with patient photos: is it a breach?
Yes, in the sense that it is a loss of personal data. Whether it must also be notified depends on the risk, and here encryption matters.
The European guidelines give two opposite examples. With an unencrypted USB stick that is lost, it is often impossible to establish whether anyone has accessed the data. The case must still be notified, because there is a reasonable degree of certainty that there has been a breach of availability: the controller is «aware» at the moment they realise they have lost it.
With a mobile device securely encrypted, used by the controller and staff, the situation changes. If the encryption key remains in the secure possession of the controller and that is not the only copy of the data, the data is inaccessible to whoever finds it, and the breach is unlikely to present a risk to patients: it is not notified to the Garante, but it stays in the register. If it then emerges that the key was compromised or the software vulnerable, the risk changes and notification may become required.
The same guidelines warn about token encryption. A device may be encrypted when switched off but not in stand-by; some products have default keys that every customer must change to make them effective; encryption that is adequate today may not be in a few years' time. If you do not notify because you believed the device was encrypted and it was not, you breach art. 33.
When you are «aware»
The 72 hours start from when the controller has a reasonable degree of certainty that a security incident compromising personal data has occurred (EDPB). Not from when you know everything. The focus must be on the immediate investigation: establishing whether the data has been compromised and, if so, remedying it and notifying.
If the breach occurs at a supplier, for example the practice management system, art. 33, para. 2 applies: the processor informs the controller without undue delay after becoming aware. According to the guidelines, the controller is considered «aware» when the processor tells them. This is why it is worth knowing in advance how long the supplier takes to alert you: you will find this among the questions in where the patient's data is kept.
What to do, in order
| Step | What | Reference |
|---|---|---|
| 1 | Stop what is ongoing: remove access from a compromised account, block the lost device, halt the sending | Art. 32 |
| 2 | Write down immediately the moment you became aware | Art. 33, para. 1 |
| 3 | Establish what happened: which data, of how many patients, whether it was encrypted, for how long | Art. 33, para. 3 |
| 4 | Assess the risk to patients | EDPB, part 3 |
| 5 | Notify the Garante, if the risk is not unlikely | Art. 33, para. 1 |
| 6 | Inform patients, if the risk is high | Art. 34 |
| 7 | Write everything in the breach register | Art. 33, para. 5 |
The risk assessment
The guidelines set out the factors to weigh: the type of breach, the nature and sensitivity of the data, how easy it is to identify people, the severity of the consequences, the characteristics of the people and those of the controller, the number of people involved. Two points apply to a doctor. Health data can cause harm on its own, and a combination of data is generally more sensitive than a single item. And, citing the very case, a medical organisation processes special categories of data, so there is a greater threat to the data subjects than, for example, a newspaper's mailing list.
There are also cases where the risk is mitigated. If a piece of data is sent by mistake to a «trusted» recipient, with whom there is an ongoing relationship and who can reasonably be expected not to read it and to return or destroy it, the controller may take this into account.
Notification to the Garante
Since 1 July 2021 notification is made using an online procedure in the Garante's online services portal. The Garante's 2019 provision sets out the information to be provided in an attached form. The notification, under art. 33, para. 3, contains at least:
- the nature of the breach, including, where possible, the categories and approximate number of data subjects and of data records concerned;
- the name and contact details of the data protection officer or another point of contact;
- the likely consequences;
- the measures taken or proposed to remedy and mitigate the effects.
If you do not have all the information straight away, you can provide it in successive phases, without further undue delay (para. 4): better a complete notification halfway through than no notification at all.
When to inform patients
Art. 34 provides that, where the breach is likely to result in a high risk to people's rights and freedoms, the controller communicates it to the data subject without undue delay. The communication uses plain and clear language, describes the nature of the breach and contains at least contact details, likely consequences and measures, as in the notification.
It is not required if the data was protected in such a way as to be unintelligible to anyone not authorised (encryption, for example), if you have taken measures that avert the high risk, or if it would involve disproportionate effort: in that case a public communication or similar measure is made. The Garante may nevertheless ask you to inform patients, if it considers a high risk likely.
The threshold for informing patients is higher than that for notifying the Garante: not all breaches have to be communicated to patients. The purpose of the notice, the guidelines say, is to give specific information on the steps people can take to protect themselves.
The internal register
Art. 33, para. 5 requires you to document any breach, including the circumstances, consequences and measures taken, so that the Garante can verify compliance with the rule. The guidelines add that the register must be kept regardless of whether notification is required, and recommend setting one up. The GDPR does not state how long to keep it.
An example row, with fictitious data:
| Field | Example |
|---|---|
| Date and time you became aware | 12/11, 9:40 |
| What happened | Practice phone lost in a taxi, with clinical photos of patients in the gallery |
| Data involved | Photos of patients, names in the files; estimated number: to be verified |
| Was the device encrypted and locked? | Yes / no (state how you verified it) |
| Is there another copy of the data? | Yes / no |
| Risk assessed | High / not unlikely / unlikely, with the reason |
| Notification to the Garante | Yes, on the day and at the time / no, because |
| Communication to patients | Yes / no, because |
| Remedy | Remote wipe, password change, device recovered |
What to prepare beforehand
The real work is beforehand. Art. 32 requires the ability to restore data promptly after an incident and to verify the effectiveness of measures regularly. In a practice this means three things.
Trails. If a member of staff opens a folder they should not, you must be able to see it. In Fibonacci the access log shows when, who, what and on which record, with filters by clinical activity, type of action and outcome; it is visible to the practice administrator and can be exported to CSV. The rows cannot be modified or deleted, and each is linked to the previous one, so any tampering would show. The integrity check does not have a button: it is done on the server and the result is requested from support. If the log turned out to be altered, it would not be an ordinary report but a security incident, to be reported immediately.
Backups. Backups also serve to prevent ransomware from turning into permanent loss. Fibonacci performs them daily, encrypted, with a periodic restore test.
Access. A member of staff who leaves loses access the same day. In Fibonacci «Remove access» ends access immediately, including sessions already open, and the operation stays in the log. Accounts have mandatory two-factor authentication.
The wider picture of where the data is kept is on the security and data page.
A checklist to keep printed out
- Who, in the practice, must be alerted first if something happens? They have a number to answer on
- I know how to stop an access: I have written down who can do it
- The practice management system supplier has told me in writing how long it takes to alert me to a breach
- I have a breach register, even an empty one, with an example row
- Phones and laptops with patient data have screen lock and encryption active, and I know how I verified it
- I have a template communication to patients, in plain language
- I know where notification to the Garante is made and who fills it in




