- clinical AI
- informed consent
Must you tell clients you use AI? Yes, and here is the wording
Yes, but the reason decides what you write. Wherever you practise, three things hold. Whether or not your law uses the word “AI”, the question that matters most is who, besides you, receives what your client said in session. Recording is a separate act that needs its own permission. And a vendor that reuses session content for its own purposes is no longer just your tool. A clause that says “I use AI tools” discloses none of them; one that names who receives what, for how long, and whether they train on it discloses all three. This is practice documentation, not legal advice; check the specifics where you practise.
What circulates: “tell them if you record”, or “the APA says so”
Two shortcuts circulate in Spanish, and neither reaches the real question. The first discusses disclosure only where there is a microphone. That is what we read, in October 2026, on the transcription page of a Mexican software product for physicians: that it is the physician’s job to inform the patient before switching on the recording and to obtain their consent. True for recording, and silent about the tool that never records but receives the session record you typed and returns a draft note. That text leaves your computer exactly as audio would.
The second ties disclosure to the APA. The Spanish psychology news site Infocop summarised the APA’s 2025 guidance as «La APA insiste en que, en el caso de que se utilicen herramientas de IA en alguna parte de la evaluación, tratamiento o documentación, los y las pacientes deben ser plenamente informados/as» (“the APA insists that if AI tools are used in any part of assessment, treatment or documentation, patients must be fully informed”). The original document does speak of an “ethical obligation to obtain informed consent” about “relevant AI tools”. But it also says it “does not represent official APA policy” and that its considerations “do not reflect standards that are mandatory”; it suggests, without requiring, adding to written consent “when, how, and the type of AI tool(s)” you use; and it separates minor uses, such as predictive text while writing notes, from those needing fuller discussion. Sound guidance; not the source of a legal duty.
Mexico as the worked example: four articles that never say “AI”
Whatever your jurisdiction, check three dials: how specific consent to health data must be, how the law treats a processor acting for you, and what changes when a vendor uses the data for itself. Mexico exposes all three, because its federal data-protection law, in force since March 2025, does not contain the words “artificial intelligence” once, and still, on our reading, produces the duty:
- Article 8. For sensitive data, which include «estado de salud presente o futuro» (present or future health status, article 2, section VI), the data controller «deberá obtener el consentimiento expreso y por escrito» (must obtain express, written consent) by handwritten or electronic signature or another authentication mechanism.
- Article 2, section IV. Consent is a «Manifestación de la voluntad libre, específica e informada» (a free, specific and informed expression of will): about the real processing, not a generic one.
- Article 14. The privacy notice must disclose «la existencia y características principales del tratamiento» (the existence and main characteristics of the processing) so that the person «pueda tomar decisiones informadas» (can make informed decisions).
- Article 35. Data going to third parties «distintos de la persona encargada» (other than the processor) require a privacy notice that «contendrá una cláusula en la que se indique si la persona titular acepta o no la transferencia» (contains a clause stating whether the data subject accepts the transfer).
The hinge is the vendor’s role, which we set out in is it safe to use AI with patient information?. A company that processes data only «por cuenta del responsable» (on the controller’s behalf) is a «persona encargada», a processor (article 2, section XII), and handing it data is not a transfer (section XX). A vendor that uses the content for itself, to train its models for instance, has stopped acting on your behalf, and that flow falls under article 35; the health-care exception in article 36, section II, covers transfers needed for «la prestación de asistencia sanitaria» (the provision of health care), which training a commercial model is not. Both points are our reading of the definitions, not an official criterion. Transferring without the consent the law requires is an infraction (article 58, section XIII) carrying a fine of 200 to 320,000 UMA, the reference unit Mexican law uses for fines (article 59, section III), and for sensitive data penalties «podrán incrementarse hasta por dos veces» (may be increased up to twofold; section IV).
For a genuine processor, our reading is this: a client who signed so you could keep their clinical record has not given specific, informed consent to a company processing their session content, and who sees the data is a “main characteristic” of the processing. Mexican ethics agree. The FENAPSIME code, one of Mexico’s psychology ethics codes, says psychologists «Solo revelarán la información con el consentimiento de las personas» (will disclose information only with the person’s consent). APA Standard 4.02(a) of the Ethics Code asks you to discuss “the foreseeable uses of the information generated through their psychological activities”, and 4.02(b) to revisit the discussion “as new circumstances may warrant”.
The counter-argument: a 2011 regulation that says you need not tell
The best argument that no notice is needed is article 53 of the 2011 regulation under the earlier law:
«Las remisiones nacionales e internacionales de datos personales entre un responsable y un encargado no requerirán ser informadas al titular ni contar con su consentimiento.»
That is: hand-offs to a processor need neither disclosure nor consent. Two limits. First, whether it still applies is an open question: it implements the 2010 law, now repealed; the 2025 decree (transitory article Décimo Segundo) ordered the executive to issue «las adecuaciones correspondientes a los reglamentos» (the corresponding adjustments to the regulations) within ninety calendar days, and as of November 2026 we located neither that adjustment nor any official criterion on article 53. Second, it protects only a real processor: the same article turns the processor into a controller when it uses the data «con una finalidad distinta a la autorizada» (for a purpose other than the one authorised), and article 51 requires the relationship to rest on «cláusulas contractuales u otro instrumento jurídico» (contractual clauses or another legal instrument). If you paste notes into a consumer chatbot, the question is what its terms say: if they reserve the right to use your content for the vendor’s own purposes, for that use it is not your processor.
Neither limit defeats the argument where the vendor is a genuine processor. Nor does it help to say the 2025 law is stricter: the regulation itself already required free, specific and informed consent (article 12) and disclosure of «la existencia y características principales del tratamiento» (article 23), and still exempted these hand-offs. That is why we do not rest the duty on the statute alone. The upshot: in that one scenario the legal duty is arguable; in every other scenario it is not, and the ethics codes never drew that distinction.
The US contrast: the law lets you share, so the duty comes from elsewhere
The United States gets there by another route. Under HIPAA, 45 CFR § 164.502(e)(1)(i) provides that “a covered entity may disclose protected health information to a business associate” if it “obtains satisfactory assurance that the business associate will appropriately safeguard the information”, documented in a written contract (§ 164.502(e)(2)): the business associate agreement. Nothing in that standard asks for the client’s authorisation. One exception matters to therapists: if what you feed a tool is “psychotherapy notes” in HIPAA’s sense, § 164.508(a)(2) requires “an authorization for any use or disclosure of psychotherapy notes”, with narrow exceptions, so get advice before assuming a business associate agreement covers it.
Otherwise the duty to tell comes from ethics (Standards 4.02 and 4.03). At least one state has also passed a statute that names AI outright: Illinois’ Wellness and Oversight for Psychological Resources Act, signed in August 2025, according to the state regulator “prohibits anyone from using AI to provide mental health and therapeutic decision-making, while allowing the use of AI for administrative and supplementary support services”, with fines of up to $10,000 for confirmed violations. The release summarises the Act and does not reproduce its text; if you see Illinois clients, read the Act itself (HB 1806) before relying on this summary.
What the tool does decides what you disclose
| What the tool does | What you owe (Mexico’s articles in parentheses) | Where it goes |
|---|---|---|
| Predictive text that runs on your device and sends no text to a vendor | Nothing specific. If the text goes to a vendor, you are in the next row | — |
| Receives your typed session record and returns a draft; vendor acts only for you | On our reading: describe the processing (art. 14) and obtain specific consent (arts. 2-IV, 8). Ethics: APA Standard 4.02 | Privacy notice and signed consent |
| Records or transcribes the session | All of the above, plus audio as a new data item in the notice (art. 15-II) and, as ethics, permission to record (APA Standard 4.03) | Notice and a separate recording authorisation |
| Vendor keeps or uses content for its own purposes | A transfer: acceptance clause in the notice (art. 35) and express consent | Notice with a yes/no box, and consent |
The clinical side of recording, and what is known about how it affects what clients say, is in recording a therapy session. The last row is a question for your vendor before your client; the full list is in that same guide. A promise never to train “external” AI models leaves the vendor’s own models unaddressed; ask for the sentence without the adjective.
What the disclosure must say
The APA guidance asks you to know how client data are used, stored and shared, and to tell clients. As a clause, seven items:
- What it does and does not do. Drafts a note from your record; does not diagnose or decide.
- What data it receives. Typed text, audio, transcript, identifiers. Mexico’s article 15, section II, requires flagging the sensitive ones.
- Who runs it, and in what role. The vendor’s name, and that it acts only on your behalf.
- What it keeps. Whether audio is deleted once transcribed, and how long text is held; Mexico’s article 12 sets the yardstick at the «mínimo indispensable» (indispensable minimum).
- Whether it trains on the content. If it does, you are in transfer territory.
- Who is accountable. You review, correct and sign every note; the method is in reviewing an AI draft in 90 seconds.
- How to refuse and withdraw. Mexico’s article 7 puts the revocation mechanism in the notice; the APA guidance wants clients to know whom to contact.
Where each piece goes
In Mexico these are three documents, as the privacy notice guide explains, and the split is worth copying wherever you practise. The privacy notice informs: data, purposes, the existence of a processor, any transfer clause, the revocation route. The signed consent authorises: give AI its own box, separate from the general authorisation, so that saying no costs the client exactly as much as saying yes. The conversation in session makes it genuinely informed and goes in your note; the whole document is in the informed consent guide.
Existing clients and minors. If you adopt a tool mid-treatment, Standard 4.02(b) gives the rule: talk again, get the signature before first use, and do not run earlier sessions through the tool. With minors, the people holding parental authority consent and you seek the young client’s assent; the details are in informed consent with minors.
Three clauses to adapt
Examples, not templates: every bracket and every promise about the vendor must describe your actual tool; a bracket you cannot fill is a question for your vendor.
1. Consent: a tool that drafts from your typed notes.
“I authorise [clinician] to use [tool], a service provided by [vendor], to draft notes of my sessions from my clinician’s written notes. The vendor receives those notes and acts only on my clinician’s behalf: it does not use them for its own purposes or to train its models, and it keeps [what] for [how long]. My clinician reviews, corrects and signs every note. I understand that I can decline without any change to my care, and withdraw this authorisation at any time by writing to [contact]. ☐ I authorise ☐ I do not authorise”
2. Audio variant, in a separate box.
“I also authorise audio recording of my sessions so that [tool] can produce a transcript. The audio is deleted [when]; the transcript [is kept where and for how long, or is deleted once the note is written]. I can ask for the recording to stop at any point in a session. ☐ I authorise ☐ I do not authorise”
3. Paragraph for the privacy notice.
“To draft the notes in your record I use [tool], provided by [vendor], which processes your data solely on my behalf and on my instructions, as a processor. This processing requires your express written consent, which you can withdraw at any time by writing to [contact]. I do not transfer your data to third parties for purposes other than your care.”
If your vendor does use the data for itself, those promises are false: correct the first clause, replace the notice’s last sentence with a transfer clause the client can accept or decline, and ask yourself whether you want that tool.
If the client says no
- Nothing about their care changes. Consent that is not free is not consent (Mexico’s article 2, section IV), and making therapy conditional on the tool empties it. The APA guidance names the obvious alternative: care without AI from the same clinician.
- Switch the tool off for that client, so a setting prevents it, not your memory.
- Accept a partial yes. Yes to text, no to audio is valid; that is why the boxes are separate.
- Note it: what you explained, what they decided, the date.
- If they withdraw later, Mexico’s article 7 says consent «podrá ser revocado en cualquier momento sin que se le atribuyan efectos retroactivos» (may be revoked at any time, without retroactive effect): what was processed before was lawful, what follows is not. Switch the tool off, ask the vendor to delete what it holds for that client, and keep the confirmation. Signed notes stay in the record, which Mexican clinicians must keep (NOM-004, clause 5.4); on our reading, article 25, section VII, does not require erasing them either.
- If a tool ever assessed the client on its own, with no human involved and with significant effects, article 26, section II, gives them a right to object to automated processing that analyses or predicts their health.
When a client asks in session, the answer fits in three sentences:
“It’s your choice, and it changes nothing about your treatment. If you’d rather not, I write your notes myself, as always. And if you say yes and change your mind later, just tell me and I’ll switch it off.”
Making “no” easy to honour is also a design question: in gesell.ai, AI is off by default for each client, nothing from their record goes to the model until you record their authorisation on their profile, and you can always continue without AI.
References
- Cámara de Diputados — Ley Federal de Protección de Datos Personales en Posesión de los Particulares (in force; last amended DOF 14-11-2025)
- Cámara de Diputados — Reglamento de la Ley Federal de Protección de Datos Personales en Posesión de los Particulares (DOF 21-12-2011)
- American Psychological Association — Ethical Principles of Psychologists and Code of Conduct (2017)
- American Psychological Association — Ethical Guidance for AI in the Professional Practice of Health Service Psychology (2025)
- FENAPSIME — Código de ética de las y los psicólogos mexicanos (2018)
- eCFR — 45 CFR § 164.502, uses and disclosures of protected health information: general rules
- eCFR — 45 CFR § 164.508, uses and disclosures for which an authorization is required
- Illinois Department of Financial and Professional Regulation — Gov. Pritzker Signs Legislation Prohibiting AI Therapy in Illinois (4 August 2025)
Ready to spend less time on documentation?
gesell.ai turns your session notes into professional clinical documentation — SOAP, DAP, BIRP, or GIRP — and generates treatment plans with SMART goals.
Try gesell.aiHave a question about your practice?
How to document a case, which format suits you, or how Gesell fits your practice: write to us and we will answer.
About the author
Gesell Team
Clinical and product content written by the gesell.ai team together with certified clinical psychologists.