Skip to content
FibonacciAestheticsLog inTry it free

Practice regulations

The GDPR in an aesthetic medicine practice: privacy notice, record of processing activities and who is responsible for what

GDPR in an aesthetic medicine practice: health data, controller and processor, privacy notice, records, consent, DPO and patient requests.

The Fibonacci editorial teamUpdated on 15 min read

Smartphone showing a padlock icon
In this article
  1. 1. Health data: what it is and when you may process it
  2. 2. Controller and processor: who is responsible for what
  3. 3. The privacy notice
  4. 4. The record of processing activities
  5. 5. Consent: when it is needed and when it is not
  6. 6. Data protection officer and impact assessment
  7. 7. Security and access
  8. 8. When a patient asks for their data
  9. If data is lost or gets out
  10. The practice checklist

For an aesthetic medicine practice, the GDPR boils down to a few things you need to have in writing and be able to explain out loud. Health data is a special category of data, and you do not need the patient's consent in order to treat them. The data controller is the practice; the practice management software, the cloud provider and whoever carries out maintenance are processors, under a written contract. You need a privacy notice, the record of processing activities (even for a sole practitioner, according to the Garante), security measures proportionate to the risk, and a reply within one month to anyone who asks for their data. The data protection officer and the impact assessment, for a sole practitioner, as a rule are not required.

Below is each point, with the article and the source, and what it means for the clinical record.

1. Health data: what it is and when you may process it

The regulation defines «data concerning health» as personal data related to the physical or mental health of a person, including the provision of health care services, which reveal information about their health status (art. 4, point 15 (opens in a new tab)). In an aesthetic practice these are the clinical record, the medical history, the reports, the clinical photographs, the consent forms.

The principle is a prohibition: Article 9(1) prohibits processing, among other things, data concerning health. The exceptions are in paragraph 2. The one that matters to those providing care is point (h): processing necessary for the purposes of preventive medicine, diagnosis, the provision of health care or treatment, on the basis of Union or Member State law or under a contract with a health professional. Paragraph 3 adds the condition: the data must be processed by a professional subject to professional secrecy, or under their responsibility, or by another person also bound by secrecy.

This is why, the Garante explains, consent is not the basis for treating. Explicit consent is instead required, among the other cases the Garante lists, for processing by healthcare professionals for commercial purposes (clarifications of 7 March 2019 (opens in a new tab)). In the practice the distinction falls on photographs: the clinical photograph is part of the care, the same photograph used for the website or for social media is separate processing. The two are recorded as separate things; the article on privacy consent for treating and the page on photographs and privacy go into the detail.

2. Controller and processor: who is responsible for what

The controller is the one who determines the purposes and means of the processing; the processor is the one who processes data on behalf of the controller (art. 4, points 7 and 8). In your practice the controller is you, or the company that runs the practice. The suppliers that process data on your behalf are processors: the practice management software, the cloud service where the data sits, whoever sends the emails or SMS.

Article 28 sets out what is expected from this relationship. The controller uses only processors providing sufficient guarantees, and the processing is governed by a contract or another written legal act (paragraphs 1, 3 and 9) setting out the subject matter, duration, nature and purpose of the processing, the type of data and the categories of data subjects. The contract provides in particular that the processor:

  • processes the data only on documented instructions from the controller;
  • adopts the security measures in Article 32;
  • does not engage another processor without written authorisation, specific or general;
  • assists the controller in responding to requests from data subjects;
  • at the end of the service deletes or returns the data, at the controller's choice;
  • makes available the information necessary and allows audits, including inspections.

In practice: ask for the contract, read it, and keep the signed copy. Fibonacci acts as processor for the practice, which remains the controller: patient requests go to the doctor, not to the supplier, and the software is there to help you respond (security and data, privacy). Where the data physically sits is a separate topic: where patient data sits.

The people who work with you are part of the picture too. A Garante decision of 10 July 2025 concerns an occupational medicine centre, not an aesthetic clinic, but the facts are instructive: a doctor's secretary had forwarded to the patient's employer a message the patient had written only to the doctor. The Garante challenged the communication of data, including health data, without a valid legal basis and against the principle of minimisation, and fined the company 30,000 euros for the set of violations found (decision of 10 July 2025 (opens in a new tab)). The lesson for the front desk is simple: patient messages are not forwarded to anyone unless someone has decided, in writing, that they can be.

3. The privacy notice

Article 13 lists what you must tell the patient at the moment the data is collected. Paragraph 1: identity and contact details of the controller, contact details of the data protection officer if there is one, purposes and legal basis of the processing, recipients or categories of recipients, any transfer to a third country. Paragraph 2: the retention period, or the criteria for determining it; the rights of access, rectification, erasure, restriction, objection and portability; the right to withdraw consent, where the processing is based on consent; the right to lodge a complaint with a supervisory authority; whether providing the data is a statutory or contractual requirement, and the consequences of refusing.

Article 12(1) requires the information to be provided in a concise, transparent, intelligible and easily accessible form, using clear and plain language. The Garante adds that, for organisations with many activities, information may be given progressively: to all patients what concerns ordinary services, to those affected by particular services (for example online delivery of reports or research) what concerns the specific service.

The item that almost every copied privacy notice forgets is retention. The Garante points out that for healthcare documentation the legal system already sets retention periods, which the GDPR has not changed, and cites some: indefinite retention for clinical records with reports (a circular from the Ministry of Health of 1986) and at least ten years for radiological imaging documentation. Where no rule fixes the period, the controller decides, so that data is not kept longer than necessary, and states it in the privacy notice, even just as a criterion. Which period applies to a self-employed doctor's clinical record is covered in the article on retention of the clinical record.

4. The record of processing activities

This is the document that is most often missing. Article 30 requires every controller to keep a record of processing activities carried out under its responsibility, in writing, including in electronic form, with the following information:

  • name and contact details of the controller (and of the data protection officer, if there is one);
  • purposes of the processing;
  • categories of data subjects and of personal data;
  • categories of recipients;
  • transfers to third countries, if any;
  • envisaged time limits for erasure, where possible;
  • general description of the security measures, where possible.

A practice record can fit in a table. An example to adapt, with the items from Article 30:

ProcessingPurposeData subjects and dataRecipientsErasureSecurity measures
Clinical recordPatient carePatients: personal details, medical history, treatments, clinical photographs, consent formsDoctors and authorised staff; the practice management software supplier, as processorAccording to the criteria set out in the privacy noticeRole-based access, two-factor authentication, access log
DiaryOrganising appointmentsPatients: personal details, contact details, date and timeFront desk; the practice management software supplier(to be defined)Role-based access
Promotional photographsPractice communication, only with explicit consentPatients who have given consent(to be defined)On withdrawalConsent for each photograph, revocable

If there are no transfers to third countries, write it down: an empty cell does not say whether the processing does not exist or whether you have not thought about it.

For treating, it is not needed. It is needed, according to the Garante's list, for processing by healthcare professionals for commercial purposes, and in an aesthetic practice for photographs used outside care (teaching, promotion): each with its own consent, revocable. In Fibonacci every photograph declares its purpose (clinical, teaching or promotional), and consent to the use of images follows the individual photograph: withdrawing the promotional use of one does not affect the others. Consent to medical treatment, the one under Italian Law 219/2017, is a different matter and is covered in the article on informed consent.

6. Data protection officer and impact assessment

Article 37 makes the designation of a data protection officer (DPO) mandatory, for what matters here, where the core activities of the controller consist of processing, on a large scale, special categories of data (paragraph 1, point (c)). The Garante applies the rule as follows: a public health authority yes; a private hospital, a nursing home or a residential care home generally falls within the concept of large scale; the individual healthcare professional working in self-employed practice on an individual basis is not required, because, according to recital 91, their processing is not on a large scale (clarifications of 7 March 2019 (opens in a new tab)).

The same recital 91 applies to the data protection impact assessment. Article 35 requires it where a processing operation is likely to result in a high risk, and in particular for processing on a large scale of special categories of data (paragraph 3, point (b)). The recital says that the processing of personal data by an individual physician or other health care professional should not be considered large scale, and that in such cases the assessment should not be mandatory.

For a practice with several doctors or for a polyclinic the picture changes: the Garante cites as an example that a private hospital as a rule falls within large scale, as an example that does not, the individual professional, and an associated practice is neither one nor the other. The question becomes how many patients and how much data. It is worth writing down how you answered and why, and reviewing it when the practice grows. If you designate a DPO, their contact details go in the privacy notice (art. 13) and in the record (art. 30).

7. Security and access

Article 32 requires the controller and the processor to implement technical and organisational measures appropriate to the risk: among others, where appropriate, pseudonymisation and encryption, the ability to ensure confidentiality, integrity, availability and resilience of the systems, the ability to restore the data after an incident, and a process for regularly testing the effectiveness of the measures. There is no closed list: the right measure depends on the risk.

A decision of 22 February 2024 shows what the Garante looks at, even though it concerns a large public health authority and not a practice. The South Tyrol Health Authority was fined 75,000 euros in total, 25,000 for each of the three proceedings, because the health dossier allowed staff who were not treating the patient to consult their data, and there were no automatic alerts for anomalous access. The Garante points out that access must be limited to the staff involved in the care process, for the time it takes, and that the controller must have systems to monitor access and detect anomalies (decision of 22 February 2024 (opens in a new tab)). Translated for a practice: different roles for different people, and a log of who opens what.

This is how Fibonacci works. Every invited team member has mandatory two-factor authentication, which cannot be switched off. The role decides what the person sees: the administrator, the doctors who see the whole practice, a doctor for one location, the front desk (patients and diary, without opening clinical records), and a doctor who sees only their own patients. The role is changed with Cambia ruolo, takes effect from the next login and is kept in the log. When a team member leaves, Rimuovi accesso cuts off access immediately, including sessions already open; the clinical data remains attributed to them, because a report does not change author. Removal cannot be undone from the interface, and there is no temporary suspension (users and permissions).

The access log answers the question «who has seen my record?». Only the practice administrator can open it. For each row it shows when, who, what (creation, reading, update, deletion), on what and with what outcome. You can filter by clinical or system activity, by action and by outcome; you can export to CSV with the rows on screen. The rows cannot be modified or deleted, and are linked to each other so that tampering is visible; there is no button for the integrity check and you request it from support. The traces remain for as long as the clinical documentation remains, and remain even after a patient is deleted, without their name. Photographs are encrypted at rest and every time they are opened it is a logged access.

8. When a patient asks for their data

The controller responds to requests under Articles 15 to 22 without undue delay and, in any event, at the latest within one month of receipt; the period may be extended by two months, where necessary taking into account the complexity or the number of requests, and the controller must inform the data subject of the extension and the reasons within the first month (art. 12(3)). If the controller does not act on the request, it gives the reasons within one month and informs the data subject that they may lodge a complaint with the authority and seek a judicial remedy (paragraph 4). The request is free of charge, except for those that are manifestly unfounded or excessive (paragraph 5).

Access (art. 15) gives the right to obtain confirmation of the processing, the data and information about the processing. The Garante fined the medical centre mentioned above 30,000 euros also because it had not responded within the deadline to a request for access to the record, and because it had refused to give the authority the documents needed to verify the response, citing data protection reasons that the Garante found to be non-existent (decision of 10 July 2025 (opens in a new tab)).

In Fibonacci, from the Altro menu on the patient record there are three exports: Esporta PDF (personal details, medical history, treatments, prescriptions, tests, consent forms and access history), Esporta CSV (the same content in a spreadsheet) and Esporta in FHIR, a ZIP with the data in the FHIR R4 standard, the decrypted photographs and the reports, and a file with the SHA-256 fingerprint of each file: the format is designed for data portability. The copies are handed over through suitable channels: photographs are health data and are not sent by ordinary messaging (patients).

On erasure, Article 17(3) excludes the right where the processing is necessary for compliance with a legal obligation (point (b)) or for the establishment, exercise or defence of legal claims (point (e)). It is not an automatic execution, and it is not an automatic refusal: the request is assessed, and the reasoned response is written down. Non-clinical data, such as a contact detail, can be erased.

If data is lost or gets out

Article 4 defines a personal data breach as a breach of security leading to the destruction, loss, alteration, unauthorised disclosure of, or access to, the data. Article 33 requires the controller to notify it to the Garante without undue delay and, where feasible, within 72 hours of becoming aware of it, unless it is unlikely to result in a risk to people; the processor informs the controller without undue delay. The details are in the article on the first 72 hours.

The practice checklist

  • I know who the data controller is, and I have stated it in the privacy notice
  • I have a written contract with every supplier that processes data on my behalf (practice management software, cloud, email)
  • The privacy notice states purposes, legal basis, recipients, retention, rights and complaints, in plain language
  • The record of processing activities exists, is up to date and I can make it available to the Garante
  • For treating I do not ask for privacy consent; I do ask for it, for each photograph, for uses outside care
  • I have decided and written down whether a data protection officer and an impact assessment are needed
  • Every team member has their own role and their own access; when they leave, access is closed the same day
  • I know how to export a patient's data and who responds, within one month, to their request
  • I know what to do if data gets out of the practice, and that the deadline for notifying starts from when I become aware of it

What Fibonacci does for this

This is how it looks in Fibonacci, with sample data:

The access log in Fibonacci, with sample data

Sources

  1. Regulation (EU) 2016/679 (GDPR), Articles 4, 9, 12, 13, 15, 17, 28, 30, 32, 33, 35, 37 and recital 91 (EUR-Lex) (opens in a new tab)
  2. Garante privacy, clarifications on health data, 7 March 2019 [9091942] (opens in a new tab)
  3. Garante privacy, provision of 10 July 2025 [10168519], access to health documentation and communication to third parties (opens in a new tab)
  4. Garante privacy, provision of 22 February 2024 [10001279], health dossier, accesses and security measures (opens in a new tab)

These articles explain what regulations and guidelines require and what is documented in the medical record. They are not legal or tax advice on your situation and do not say how to treat a patient.

Try Fibonacci in your practice for 15 days, no credit card needed

Within one working day we call you: together we set up your practice and import your data.

Try it free

Read next

All articles