Law and data protection
Patient data in AI tools: GDPR rules for Heilpraktiker
This article was created with AI.
A guide by sicherAI. We offer an AI service for Heilpraktiker practices. How we write these guides
In short
A Heilpraktiker in Germany can enter patient data into ChatGPT or another AI tool only if several conditions are met. Patient data usually count as health data under Article 9 GDPR. The practice then needs a legal basis and an exception under Article 9(2) GDPR (explicit consent can serve as both), a data processing agreement with the provider and, where needed, a release from the duty of confidentiality. The simplest route is to give the AI nothing that could identify a person.
Contents
What is a Heilpraktiker, and which rules apply?
Heilpraktiker are non-medical practitioners licensed under the German Heilpraktikergesetz. Some hold a licence limited to the field of psychotherapy. When either group uses an AI tool with patient data, the General Data Protection Regulation (GDPR) and the German Civil Code apply.
Section 1 of the Heilpraktikergesetz requires official permission (Erlaubnis) for anyone who wants to practise Heilkunde, the practice of medicine, without a medical licence. The City of Munich calls the restricted form “a licence to practise as a non-medical practitioner, limited to the field of psychotherapy”.
The GDPR is a regulation of the European Union and, according to the sentence that follows Article 99, “directly applicable in all Member States”. When your practice decides to use an AI tool for a task that involves patient data, the practice is the controller: the party that “determines the purposes and means of the processing of personal data” (Article 4(7)).
Sections 630a to 630h of the German Civil Code also apply: they govern the treatment contract between a practitioner and a patient. The Federal Government’s bill for these sections names Heilpraktiker expressly among the health professions they are meant to cover (Bundestag printed paper 17/10488 of 15 August 2012, page 11).
Why does the GDPR treat patient data as special?
Patient data usually reveal something about a person’s health, and processing such data “shall be prohibited” (Article 9(1) GDPR) unless one of the ten exceptions in Article 9(2) applies.
Article 4(15) defines data concerning health as “personal data related to the physical or mental health of a natural person, including the provision of health care services, which reveal information about his or her health status”. Recital 35 adds “information about the natural person collected in the course of the registration for, or the provision of, health care services”. So booking details and appointment letters can count as health data when they identify the patient.
The first exception is that “the data subject has given explicit consent to the processing of those personal data for one or more specified purposes” (Article 9(2)(a)). This guide does not assess which of the other nine could apply to a particular practice.
Under Article 9 GDPR, health data is a special category. The simplest route is to give the AI nothing that could identify a person.
What happens to the text you type into a chat app?
The text you type into an online chat app goes to its provider. With some accounts, the provider handles the text only on your behalf; with others, it may also use the text for its own purposes, such as training its models. The account and its contract decide which applies, not the name of the tool. A personal account without a data processing agreement (Article 28(3) GDPR) is usually not suitable for patient data.
The provider works on your behalf
A processor is a body that “processes personal data on behalf of the controller” (Article 4(8) GDPR). Article 28(3) requires this processing to be governed by “a contract or other legal act under Union or Member State law”. That contract is the data processing agreement, in German Auftragsverarbeitungsvertrag or AVV.
The provider also uses your input for itself
A provider that decides for itself to use your input, for example to develop its models, determines purposes of its own. For that use it is a controller in its own right (Article 4(7) GDPR), and a data processing agreement does not cover it.
What OpenAI states for ChatGPT
As of 6 November 2026, OpenAI’s EU privacy policy (updated 24 August 2026) names OpenAI Ireland Limited as the controller for people who live in the European Economic Area (EEA). It states that “we may use Content you provide us to improve our Services, for example to train the models that power ChatGPT”, and it links to instructions for opting out. The policy does not apply to content that OpenAI processes on behalf of customers of its business offerings. For those customers, OpenAI publishes a data processing addendum, effective 1 January 2026, under which it “acts as a Data Processor on the Customer’s behalf”. Provider terms change. Read the current version before you rely on it.
Is the patient’s consent enough?
A patient’s consent is not enough on its own. Explicit consent can lift the prohibition under Article 9(2)(a) GDPR and can also be a legal basis under Article 6(1)(a). A practice that relies on it still needs a data processing agreement with the provider, information for patients and, where needed, a release from the duty of confidentiality.
Consent must be “freely given, specific, informed and unambiguous” (Article 4(11) GDPR), and for health data it must also be explicit (Article 9(2)(a)). In its guidelines on consent, the European Data Protection Board (EDPB) explains that “the data subject must give an express statement of consent” and names a written statement as an obvious way to achieve this (paragraph 93). A written statement also lets your practice demonstrate later that the patient has consented, as Article 7(1) requires.
Patients must also be told about “the recipients or categories of recipients of the personal data, if any” (Article 13(1)(e)). Article 4(9) counts a processor as a recipient, because it covers disclosure “whether a third party or not”.
The release from the duty of confidentiality answers a different question from GDPR consent, even when a practice asks for both together. Six large Heilpraktiker associations adopted a joint code of conduct, the Berufsordnung für Heilpraktiker (BOH). Under its Article 3(4), confidential patient data may be passed on only if the patient has released the practitioner from the duty of confidentiality. The BOH does not say whether that covers AI input under a data processing agreement.
Based on paragraph 64 of the EDPB guidelines and Article 13 GDPR, consent for an AI tool should make clear:
- that your practice is responsible for the processing
- who will receive the data, by name or specific category of recipient (Article 13(1)(e))
- the specific purpose, for example drafting appointment letters
- which types of data will be entered
- where relevant, whether the data will be used for automated decision-making (Article 22(2)(c) GDPR)
- whether data will go to a third country, meaning a country outside the EEA, and the possible risks if there is neither a European Commission adequacy decision nor appropriate safeguards
- that the patient can withdraw consent at any time, and how
Ask for consent before the first task that uses the patient’s data (EDPB guidelines, paragraph 90), and keep the written statement with your treatment documentation.
Important: A patient can withdraw consent at any time, and withdrawing must be as easy as giving it (Article 7(3) GDPR). Withdrawal does not make earlier processing unlawful. Note the withdrawal in your practice software, so that nobody enters that person’s details into the AI tool again.
How can you use AI without identifying anyone?
Remove every detail that could identify the patient before you type. Even then, treat the text as personal data as long as you or anyone else could reasonably link it back to that patient.
A date of birth, an address, an unusual job or a rare family situation can identify someone as well as a name can, especially in combination. Recital 26 GDPR asks whether a person can be identified with “all the means reasonably likely to be used, such as singling out”.
Pseudonymisation, as defined in Article 4(5) GDPR, means that data “can no longer be attributed to a specific data subject without the use of additional information”, which has to be kept separately. Recital 26 states that pseudonymised data which “could be attributed to a natural person by the use of additional information should be considered to be information on an identifiable natural person”. For your practice, which can link them back to the patient, pseudonymised data therefore remain personal data. Only truly anonymous information falls outside the GDPR (Recital 26).
Article 5(1)(c) adds the principle of data minimisation: personal data must be “limited to what is necessary in relation to the purposes for which they are processed”. Before each prompt, work through these steps:
- Check whether the task needs patient details at all; a text about your opening hours does not.
- Write the task without names, dates of birth or contact details.
- Use a neutral placeholder such as ‘Patient A’ instead.
- Leave out rare details that would let someone work out who is meant.
- Add the real details afterwards in your practice software, outside the AI tool.
Fictional example: A Heilpraktiker in Hamburg wants help with a letter that moves an appointment to a later date. She replaces the name with ‘Patient A’ and leaves out the date of birth and the address. Once the draft is finished, she adds the real details in her practice software.
What does your duty of confidentiality mean for AI tools?
Your duty of confidentiality comes mainly from your treatment contract and your association’s code of conduct. So keep names out of your prompts.
Like every contract, your treatment contract is subject to section 241(2) of the German Civil Code. Under that section, an obligation may oblige each party “to take account of the rights, legal interests and other interests of the other party”.
The Bund Deutscher Heilpraktiker (BDH) describes the large associations’ joint code of conduct, the Berufsordnung für Heilpraktiker (BOH), as a self-commitment that a Heilpraktiker accepts by joining one of the issuing associations. It is not a statute. Article 3 of the BOH, headed “Schweigepflicht nach BGB” (duty of confidentiality under the Civil Code), requires Heilpraktiker to keep silent about everything entrusted to them or made accessible to them in their professional work.
Your duty of confidentiality does not bind the provider itself. A contract, such as a confidentiality agreement, can.
Where an AI task does need identifying details, any release and consent should cover that use expressly.
What should you check before using an AI tool?
Check the contract, the place of processing, the use of your input and what your patients have been told, before any patient information goes into an AI tool.
Article 28(2) GDPR calls a company that a provider uses for parts of its service “another processor”; the usual industry term is sub-processor.
Fictional example: Before anyone types in patient information to draft appointment letters, a practice owner asks the AI provider for its data processing agreement and its list of sub-processors. The owner checks that the agreement covers the plan the practice actually uses and files both in the practice’s data protection folder.
Some AI tools can record or transcribe a conversation. Only record a conversation if the person has agreed beforehand. Section 201 of the German Criminal Code protects “the privately spoken words of another” against recording without authorisation.
- Your practice has concluded a data processing agreement under Article 28(3) GDPR for the account it uses.
- You know which sub-processors the provider uses and how it informs you about changes (Article 28(2) GDPR).
- You know whether the data stay within the European Economic Area or go to a third country outside it, and on what basis under Chapter V GDPR.
- You know whether the provider uses your input to train its models and what the contract says.
- Your patients know, before you start, that an AI provider receives the data and for what purpose.
- Where you rely on consent, it is explicit, documented and as easy to withdraw as to give.
- Where a task needs identifying details, you have the patient’s release or your association says you need none.
- You have checked whether the task works without details that identify a patient, and you enter only what it needs.
- If a tool records or transcribes conversations, the patient has agreed before the recording starts.
Frequently asked questions
Does the patient’s consent to treatment also cover the AI tool?
Not automatically. Explicit consent under Article 9(2)(a) GDPR applies only to the “specified purposes” it names, so the use of the AI tool has to be one of them. If the request is part of a written form that also covers other matters, such as the treatment contract, Article 7(2) GDPR requires it to be “clearly distinguishable from the other matters”.
Do the same rules apply to a Heilpraktiker limited to psychotherapy?
Yes. The GDPR applies to every practice that processes patient data, whatever the scope of its licence. A licence limited to the field of psychotherapy is still a licence under the Heilpraktikergesetz, so the rules on the treatment contract in the German Civil Code apply in the same way.
What if a patient refuses the use of an AI tool?
Handle that patient’s tasks without the AI tool, or enter only details that identify no one. Making the treatment depend on a yes puts the consent in doubt. When assessing whether consent is freely given, Article 7(4) GDPR takes “utmost account” of whether a contract is made conditional on consent to processing that the contract does not need.
Is the location of the provider’s servers relevant?
Yes. A transfer of personal data to a third country, outside the European Economic Area, may take place only under the conditions of Chapter V GDPR, for example on the basis of an adequacy decision of the European Commission under Article 45. The place of processing does not replace a data processing agreement or a legal basis for health data.
Sources
- Publications Office of the European Union: Regulation (EU) 2016/679 (General Data Protection Regulation), English text (eur-lex.europa.eu), accessed
- Federal Ministry of Justice and Consumer Protection and Federal Office of Justice (gesetze-im-internet.de): Gesetz über die berufsmäßige Ausübung der Heilkunde ohne Bestallung (Heilpraktikergesetz), § 1 (www.gesetze-im-internet.de), accessed
- City of Munich (Landeshauptstadt München): Heilpraktiker licence in the field of psychotherapy (stadt.muenchen.de), accessed
- Federal Ministry of Justice and Consumer Protection and Federal Office of Justice (gesetze-im-internet.de): German Civil Code (BGB), English translation (with amendments up to the Act of 10 August 2021) (www.gesetze-im-internet.de), accessed
- Deutscher Bundestag: Entwurf eines Gesetzes zur Verbesserung der Rechte von Patientinnen und Patienten, Drucksache 17/10488 (dserver.bundestag.de), accessed
- OpenAI: EU Privacy Policy (openai.com), accessed
- OpenAI: OpenAI Data Processing Addendum (openai.com), accessed
- European Data Protection Board: Guidelines 05/2020 on consent under Regulation 2016/679, version 1.1 (www.edpb.europa.eu), accessed
- Heilpraktiker associations, published by Bund Deutscher Heilpraktiker e.V.: Berufsordnung für Heilpraktiker (BOH) (www.bdh-online.de), accessed
- Bund Deutscher Heilpraktiker e.V.: Berufsordnung für Heilpraktiker: Reine Selbstverpflichtung (www.bdh-online.de), accessed
- Federal Ministry of Justice and Consumer Protection and Federal Office of Justice (gesetze-im-internet.de): German Criminal Code (StGB), English translation (with amendments up to the Act of 7 November 2024) (www.gesetze-im-internet.de), accessed
ChatGPT is a trademark of OpenAI.
About this guide
- Publisher
- sicherAI (see imprint)
- Our interest
- We offer an AI service for Heilpraktiker practices and use models from several makers, including some named in our guides. The guide contains no rankings. Statements about other providers rest on the sources listed.
- How it was made
- This article was created with AI.
- Sources as of
- Legal position as of
- Limits
- This guide provides general information. It is not legal advice for your individual case.
- Report an error
- Contact us using the details in our imprint.