GDPR Roles in Healthcare: Who Is Responsible for Patient Data

18 November 2026
1794925284765_care-team-reviewing-shared-patient-record-access

 

In a French medical practice, the GDPR assigns four roles: controller, processor, joint controller and data protection officer (DPO). The role of each party is not decided by a job title or a contract heading. It follows from who decides why and how patient data are used. A practitioner who runs the practice is generally the controller for patient data. A service that acts only on the practitioner’s instructions, such as an outsourced medical telephone secretariat, is a processor. Two or more parties who take linked decisions together, as in a multidisciplinary health center, may be joint controllers. A DPO is required only in defined situations.

This guide explains each role in plain terms, shows how to identify it for appointment scheduling, patient calls and records, and lists the written arrangements that follow. It is written for general practitioners, specialists, paramedical professionals and health center teams.

ClicFone
Keep Patient Calls Moving
 
ClicFone combines qualified human tele-secretaries with AI support for appointment management and patient communication in healthcare practices.

Visit

Key Takeaways

  • The role depends on the activity: the party that decides the purposes and means of a processing operation is its controller, the party that acts on that party’s instructions is its processor.
  • A written contract between controller and processor is required, and joint controllers must document how they share their obligations.
  • Individual practices need a DPO only when their activity involves large-scale processing; multidisciplinary health centers and shared patient records are typical cases where it applies.
  • Hosting health data in France is governed by a specific rule of the Public Health Code, in addition to the GDPR.
  • Outsourcing phone reception does not transfer responsibility: the practitioner remains the controller and chooses a processor that offers appropriate guarantees.

Table of Contents

The four roles in one paragraph each

Controller

The French data protection authority, the CNIL, defines the controller as the person or organization that determines both the purposes and the means of a processing operation, in other words why personal data are used and how. In a practice, this is the physician, the dentist, the physiotherapist or the nurse who decides to collect patient data to provide care and organizes how the data are kept. In a health center operated by a legal entity, the entity may hold that role.

Processor

A processor handles personal data on behalf of the controller and must follow the controller’s instructions. According to the same CNIL guidance of 6 June 2025, a processor may choose suitable technical means, provided it stays within the objectives set by the controller. Typical examples in a practice are the provider of the appointment software, an IT maintenance company and a telephone answering service that books and moves appointments for the practitioner.

Joint controllers

When several parties actively take linked decisions on the purposes and means of the same processing, they may be joint controllers. The CNIL notes that they must document the allocation of their obligations transparently and make the arrangement available to the people concerned, here the patients.

Data protection officer

The DPO is not a party to the processing. The DPO is a person with specialized knowledge who informs and advises the organization and its staff, monitors compliance, advises on and checks impact assessments, and serves as contact for the supervisory authority. The CNIL’s DPO guidance adds that the DPO must not have a conflict of interest with other duties.

How to identify the role: a functional test

The CNIL’s approach is functional. It does not matter what a contract says if the facts differ. For each processing activity, two questions settle the role:

  1. Who decides why the data are used, and how the processing is organized?
  2. Does the party act only for another and on that party’s instructions?

A party that decides the purposes and means itself is a controller. A party that acts only on another’s instructions is a processor. Parties that make linked, joint decisions about purposes and means may be joint controllers. The test is applied activity by activity, so the same organization can be controller for one operation and processor for another.

A short worked example. A general practitioner decides that patients may book by phone, that calls are answered between 8 a.m. and 8 p.m., and that appointments are entered in the practice calendar. The purpose (organizing care) and the means (a phone line and a shared agenda) are the practitioner’s decisions. A telephone secretariat that answers those calls, follows the practitioner’s booking rules and enters appointments is acting on instructions: it is a processor. The practitioner remains the controller.

How the roles apply to everyday activities

 
 
 
Activity Usual role of the practitioner or practice Usual role of the service provider
Patient medical record Controller Processor if a software publisher or host stores it on the practice’s behalf
Appointment scheduling by phone Controller Processor if the secretariat only follows the practice’s rules
Calendar platform used for booking Controller of the practice’s patient agenda Depends on the activity: processor for the practice’s own data
Care coordination inside a team Controller, or joint controllers in a shared structure Processor for hosting or software
 
 
 

The table is an application of the CNIL’s functional test, not a ruling for every situation. A provider that uses the data for its own purposes would be acting outside a processor’s role, which is why the written instructions matter.

Appointment scheduling and patient calls

A patient who phones to book gives a name, a phone number and often a reason for the visit, which is health information. The practitioner decides what the secretariat may ask, how urgent requests are handled and where the information is entered. Those decisions belong to the controller. For the practice, this means the call-handling script, the escalation rules for urgent situations and the retention of any call data should be defined by the practitioner and written down. Our guide to GDPR steps for medical calls goes through the practical sequence for French clinics.

Records and the care team

Shared records raise the question of who may see what. In its 2025 draft recommendation on electronic patient records, the CNIL describes the care team as the professionals taking part in the same patient’s care, through diagnosis, treatment, disability compensation, pain relief, prevention of loss of autonomy or coordination. The draft states that the team is not fixed, and that the concept determines which professionals may access a record, which data they may see and the conditions for exchange and sharing.

This document was a draft submitted for consultation until 16 May 2025. Its care-team discussion is therefore proposed guidance, and practices should check the CNIL site for the final text before relying on it.

Health centers and shared structures

In a maison de santé, several professionals may use the same agenda, the same patient file and the same reception. Where they jointly decide how this shared processing is organized, they may be joint controllers. The practical consequence is a document: who informs patients, who answers access requests, who handles a breach. The CNIL expects this allocation to be transparent and available to patients, so a short, dated internal agreement, kept with the processing register, is the minimum.

Written arrangements that follow from each role

The CNIL states that a controller must check the guarantees offered by a processor and establish a written contract or other binding instrument defining its obligations. For a practice using a telephone secretariat, the contract is the place to record:

  • the subject, duration and nature of the processing (answering calls, booking, rescheduling);
  • the categories of data and the people concerned (patients, callers, practice staff);
  • the instruction that the provider acts only on documented instructions from the practice;
  • confidentiality commitments for the people who handle the calls;
  • security measures and what happens in case of a breach;
  • the return or deletion of data when the service ends.

Our article on the data processing agreement for a medical answering service details these clauses, and the page on protecting health data in an outsourced medical secretariat covers security practice.

Beyond the contract, the CNIL’s page on formalities for health-data processing, updated 22 May 2024, lists what organizations must do: document the processing internally, formalize the roles and responsibilities of those involved, inform people and respect their rights, and carry out an impact assessment where it is justified. Few practices need all of this at full scale, but each item has a simple version: a processing register, a signed role agreement, an information notice at reception and on the website, and a note on whether an impact assessment is required.

If calls are recorded or analyzed, the controller decides the purpose, the information given to the caller and the retention period. The pages on call recording rules, call analytics and making verbal consent auditable set out how French clinics handle each case.

When a DPO is required

The CNIL answers this specifically for health professionals. Individual practices, pharmacies and medical biology laboratories must appoint a DPO only when their activity involves large-scale processing. It gives networks, multidisciplinary health centers, health centers and records shared among professionals as examples of that scale.

The general rule in the CNIL’s DPO guidance covers three situations: public authorities or bodies (with an exception for courts acting in their judicial capacity), organizations whose core activities involve large-scale regular and systematic monitoring, and organizations whose core activities involve large-scale processing of sensitive data, which includes health data.

For a solo practitioner or a small group, the usual position is therefore no mandatory DPO, but the obligations of a controller remain. For a health center with shared records, the question deserves a documented answer. The DPO must have specialized knowledge and no conflict of interest, so the practice manager who also decides on the processing is not a suitable choice.

When a DPO is required

Hosting health data: an additional French rule

France adds a layer to the GDPR. Article L1111-8 of the Public Health Code, in force in its current version from 1 July 2025, provides that a decree specifies the roles and responsibilities of the host and of the party that entrusts the data, the obligation to store data within the EU/EEA, and the contractual provisions addressing the risk of transfer to third countries or unauthorized access.

The Conseil d’État, in its 19 June 2020 interim ruling, referred to the same article to recall that a host may use entrusted data only to perform the hosting and must return the data at the end of the hosting, without keeping a copy. For a practice, the consequence is concrete: any provider that stores health data for the practice, whether software, call platform or recording archive, must be able to state where the data are hosted and what happens to them at the end of the contract.

A short role audit for a practice

  1. List the processing activities: patient records, appointments, phone calls, reminders, billing, team communication.
  2. For each, write down who decides why and how data are used.
  3. Identify every external party that handles the data and check that it acts only on instructions.
  4. Confirm a written contract exists for each processor, and a written allocation exists for each joint-controller situation.
  5. Check where health data are hosted and what the contract says about return or deletion.
  6. Decide, and record, whether a DPO is required given the scale of processing.
  7. Review the file whenever a tool, a provider or the team changes.

The audit takes an afternoon for a small practice and is the document a patient request or an inspection would start from.

Why outsourcing reception to a specialized team fits the processor model

Why outsourcing reception to a specialized team fits the processor model

The phone is where a large share of a practice’s patient data first appears. A secretariat dedicated to health professionals handles those calls on instructions that the practitioner sets, which matches the processor role as the CNIL describes it. The practitioner keeps the decisions on purposes and means, and the provider carries out the booking work within them.

ClicFone’s service combines trained human tele-secretaries with AI support, working with calendar platforms such as Doctolib, LibreRDV, Maiia and CalenDoc, and is designed to maintain compliance with medical confidentiality standards. Practices that want to see how this fits their organization can start with the ClicFone call-handling service.

ClicFone

For practices planning the change, the five medical scheduling rules and one-week pilot plan show how to define the instructions the secretariat will follow, which is the same document that supports the controller-processor contract.

Our perspective

After more than 15 years in medical telephone answering, we have seen that the roles are clearest when the practitioner writes down the instructions. A booking script, a list of urgent situations, a rule for what is asked of a caller and a rule for what is entered in the agenda: these four documents define the processing, and they are what a processor works from.

Our service is built around qualified human tele-secretaries trained for healthcare, supported by AI for continuity at any hour, and synchronized with the calendar platforms practitioners already use. We designed it to keep medical confidentiality at the center of every call, because patients phone with questions that concern their health and expect discretion.

We recommend that every practice, from a solo general practitioner to a multidisciplinary team, treat the phone as part of its data governance and not only as a reception task. A clear division of roles, a written contract and instructions that are easy to follow give practitioners the time they want to spend with patients.

Rudolph Thierry

FAQ

Is a doctor who uses an answering service still the controller?

Yes, in the usual case. The practitioner decides why patient data are collected and how appointments are organized, and the service acts on those instructions. The CNIL’s functional test places the party that acts only on another’s instructions in the processor role, and the controller has to establish a written contract with it.

Do all health professionals need a DPO?

No. According to the CNIL, individual practices, pharmacies and medical biology laboratories must appoint a DPO only when their activity involves large-scale processing. Networks, multidisciplinary health centers and records shared among professionals are examples it gives of that scale.

Are the members of a maison de santé joint controllers?

Possibly, for the processing they organize together, such as a shared agenda or shared record. The test is whether they take linked, joint decisions on purposes and means. If so, they must document how they divide their obligations and make that arrangement available to patients.

What must the contract with a processor contain?

The CNIL requires a written contract or other binding instrument that defines the processor’s obligations, after the controller has checked the processor’s guarantees. In practice it covers the nature and duration of the processing, the data and people concerned, instructions, confidentiality, security, breach handling and the return or deletion of data at the end.

Does the GDPR alone govern where health data are stored?

No. In France, Article L1111-8 of the Public Health Code also applies to hosting health data. It provides for a decree specifying the roles of host and data originator, storage obligations in the EU/EEA and contractual provisions on third-country transfers and unauthorized access.

Sources

author avatar
LibreRDV-ClicFone Télésecrétariat
ClicFone Télésecrétariat depuis 2010 au service des professionnels de la santé. Permanence téléphonique 7h/20h. Secrétariat téléphonique à distance pour médecins, paramédicaux ou autres praticiens de la santé. Secrétariat humain, empathique et formé aux agendas Doctolib, Maiia, CalenDoc ou LibreRDV mais aussi synchronisé avec Google Agenda, Calendly et Cal.com
Voir tous les articles