Perinatal mental health documentation: consent, infant PHI, and AI scribes

Perinatal mental health is one of the fastest-growing therapy subspecialties. Perinatal mood and anxiety disorders — PMADs — affect approximately one in five pregnant and postpartum individuals, a rate that has received substantially more clinical and public attention since 2022 as screening protocols became more widespread and the stigma around maternal mental health began to shift. Postpartum Support International certification, dedicated PMAD training curricula, and a growing body of evidence-based perinatal interventions have created a cohort of therapists who specialize in this population.

What the clinical training in perinatal mental health does not typically address in depth is the documentation complexity that AI-assisted note drafting introduces in this subspecialty specifically. Perinatal sessions present a PHI problem that is categorically different from any other outpatient therapy population: the session audio routinely contains health information about a person who is not the identified patient, who has not signed a consent form, and whose own HIPAA status is complicated by the fact that they may not yet have been born when the session took place.

What a perinatal session actually contains

Consider what a typical perinatal therapy session includes. A client at 28 weeks pregnant discusses her anxiety about a recent amniocentesis result — the test came back with a chromosome finding the perinatologist has described as "likely benign but uncertain." She describes the finding in detail, names the specific chromosome involved, and processes her fear that the baby may have a condition requiring surgical intervention after birth. She describes conversations with her partner about what they would do if the diagnosis is confirmed. She discusses her own childhood experience with a sibling who had a similar finding and required multiple corrective procedures.

This session contains, in a single recording: the client's mental health disclosures (anxiety, grief, fear), the fetus's potential medical diagnosis (named and described in detail), the partner's responses and stated position on a sensitive medical decision, and the sibling's childhood medical history (a third party who also did not consent to appear in a therapy session). The session audio that a cloud AI scribe would receive is not "a therapy session about maternal anxiety." It is a document of a specific child's prenatal genetic finding, retained by a cloud vendor the pregnant client has never interacted with directly.

Postpartum sessions add another layer. By four to six weeks postpartum, many clients attending perinatal mental health therapy bring the infant to sessions — either because they lack childcare or because the therapist specifically works with mother-infant dyads as part of the perinatal treatment model. The session audio now includes the infant's vocalizations, the mother and therapist naming the infant repeatedly, and the mother's descriptions of the infant's health: feeding difficulties, weight gain trajectory, sleep patterns, whether the NICU stay ended with a clean discharge or required follow-up appointments, any diagnoses or concerns the pediatrician has raised.

The infant is identifiable in this audio. The infant's name, age (weeks postpartum is specific), and health status are all present. The infant is, at this point, an independently living person with their own HIPAA-covered medical records at the pediatrician and the hospital — and their health information is now also embedded in the mother's therapy session audio, being processed by a cloud vendor under the terms of a consent form the mother signed when she agreed to AI-assisted note drafting for herself.

The consent structure and where it gets complicated

HIPAA authorizes covered entities to use and disclose PHI for treatment, payment, and healthcare operations without specific authorization from the patient. An AI scribe that produces a therapy note is part of healthcare operations — the creation of a clinical record. The BAA between the therapist and the cloud scribe vendor authorizes the vendor to receive and process PHI for this purpose.

The mother's session content is clearly within scope. She is the patient; the therapist is the covered entity; the cloud vendor is the business associate. The consent and authorization structure works as intended.

Where it becomes complicated is when the session audio contains health information about the infant — a separate individual with their own HIPAA-covered records. The mother, as the infant's parent, is the infant's HIPAA personal representative. A personal representative can authorize disclosures of the represented individual's PHI. But the mother's consent to AI-assisted documentation was presumably written around her own treatment, not around her role as the infant's personal representative authorizing the cloud vendor to receive and retain health disclosures about her baby that appear incidentally in session audio.

Is the mother's general consent to AI scribe services sufficient to cover cloud processing of her infant's health disclosures? Possibly — a healthcare attorney would likely say the consent is broad enough to sweep in incidental disclosures about third parties that appear in the course of the client's own treatment. But "possibly" and "a healthcare attorney would likely say" are not the same as a clean answer, and the more the session content focuses on the infant's health status rather than the mother's treatment, the weaker the argument becomes that this is simply an incidental disclosure.

This is not a purely theoretical concern. Perinatal therapists working with complicated perinatal diagnoses — a client who has received a prenatal diagnosis of a serious fetal condition and is processing that in weekly therapy sessions — may spend the majority of session time on the fetus's health situation. The session is still the mother's treatment. But the content is predominantly about the fetus. When a cloud vendor holds twelve weeks of session audio in which a specific chromosome finding, its clinical implications, and the family's decision-making process are discussed in detail, the framing of "incidental PHI about a third party" begins to strain.

CPS proceedings and the second-subpoena problem

Perinatal mental health records are disproportionately represented in child protective services proceedings compared to most therapy specialties. The PMAD population includes clients whose mental health crises — postpartum psychosis, severe postpartum depression with suicidal ideation, postpartum OCD with intrusive thoughts about harm — can intersect with CPS involvement, either voluntarily (the therapist and client working together to ensure the infant's safety) or involuntarily (a third-party report leading to an investigation).

In a CPS proceeding involving parental fitness, the therapist's records are often subpoenaed. The privilege analysis for mental health records in CPS cases varies by state — some states protect these records more robustly than others, and federal courts have generally not recognized a federal psychotherapist privilege in CPS proceedings the way they have in criminal proceedings post-Jaffee v. Redmond. But the therapist's records, whatever their ultimate discoverability, are the records the therapist controls — they contain the clinical note, not the raw session audio.

The cloud vendor subpoena problem is different. When a cloud AI scribe has processed the perinatal session audio, the vendor holds the raw audio file, the verbatim transcript, and the note draft in their infrastructure. A CPS attorney, guardian ad litem, or family court subpoenas the vendor directly — not the therapist. The therapist's privilege assertion does not automatically protect the vendor's copy. The vendor responds to the subpoena under their own legal counsel, under the commercial law of their jurisdiction, not under the psychotherapy privilege laws of the therapist's state.

This is the same dual-subpoena problem that family therapy records face in custody proceedings, applied to a population where the stakes of disclosure are particularly high: a CPS proceeding can result in loss of parental custody, and a perinatal client's mental health crisis documentation is exactly the content that parental fitness proceedings center on.

Substance use and 42 CFR Part 2 intersection

Perinatal mental health frequently intersects with substance use. Clients with histories of SUD who are pregnant or postpartum are often in perinatal mental health therapy alongside medication-assisted treatment. Clients who used substances during pregnancy — even intermittently, even substances they disclosed to their OB under the safe harbor provisions some states offer — may have that history reflected in their perinatal therapy records.

As the 42 CFR Part 2 explainer covers in detail, substance use disorder records that meet the federal definition of an SUD treatment record carry heightened privacy protections — restrictions on disclosure that go beyond HIPAA and that require specific consent from the patient even for disclosures to other treatment providers. When a perinatal therapy record contains SUD-adjacent disclosures, the interaction between HIPAA and 42 CFR Part 2 requires careful analysis. A cloud AI scribe vendor processing perinatal session audio that contains SUD history is receiving content that may be subject to Part 2 restrictions — and the standard BAA for an AI scribe is almost certainly not written to accommodate Part 2 compliance.

What cloud scribes receive from a perinatal session

To be specific about what cloud AI scribes actually receive from a perinatal session:

• The client's full session audio — including every disclosure about her mental health symptoms, her history, her relationship with the pregnancy or the infant, and any crisis content.
• Fetal or infant health disclosures — prenatal diagnoses discussed verbally in session, ultrasound or genetic findings, neonatal complications, pediatric diagnoses raised after birth, feeding or developmental concerns.
• The infant's identifying information — name, age (weeks postpartum is uniquely specific), and voice if the infant is present in the room during a postpartum session.
• Partner and co-parent disclosures — responses to the perinatal diagnosis, relationship dynamics, co-parenting capacity discussions, any domestic violence screening content that came up in the clinical conversation.
• Substance use and mental health crisis content — any SUD history, crisis episodes during the pregnancy or postpartum period, suicidal ideation, psychotic symptoms during postpartum psychosis episodes.

The vendor retains this content — audio, transcript, and note draft — for their stated retention period, typically 30 to 90 days. During that window, the content is on cloud infrastructure, accessible to the vendor's technical staff for operational purposes under the BAA's standard terms, and reachable by a valid subpoena from any party with standing in a proceeding involving the client or the infant.

On-device processing for perinatal mental health

For perinatal therapists, the architectural argument for on-device processing is particularly direct. The consent question — whether the mother's AI documentation consent covers cloud processing of the infant's health disclosures — resolves by the fact that no cloud vendor receives the audio. The vendor subpoena risk — the second, independently reachable data repository in CPS and custody proceedings — resolves because there is no vendor repository to subpoena. The 42 CFR Part 2 intersection — SUD content in perinatal records being processed under a BAA not designed for Part 2 compliance — resolves because the SUD content never leaves the therapist's device.

TherapyDraft processes perinatal session audio entirely on the therapist's Mac. Whisper.cpp transcribes the session locally; the on-device language model drafts the note from the session content. The audio, transcript, and draft never open a network socket. The infant's health disclosures, the fetal diagnosis, the partner's responses, the SUD history — all of it is processed and retained on the therapist's hardware, subject to whatever security and access controls the therapist maintains on their own device, not on a cloud vendor's infrastructure in a jurisdiction the therapist has no visibility into.

For perinatal therapists who already navigate heightened documentation sensitivity — awareness that their records may be subpoenaed in CPS proceedings, that their clients are making decisions about disclosing sensitive health information in contexts where it may have legal consequences — the architectural guarantee that no cloud vendor holds a copy is meaningfully different from a contractual promise that a vendor will handle it carefully. TherapyDraft's Solo plan ($49/month) supports SOAP, DAP, BIRP, and GIRP templates, and the perinatal therapist can configure a template that includes EPDS (Edinburgh Postnatal Depression Scale) score fields, safety plan status, and infant-related session documentation fields appropriate to dyadic and individual perinatal practice.

Further reading

• Can an AI therapy note be subpoenaed? A 2026 legal-risk explainer — how subpoenas reach cloud AI vendors directly, bypassing the therapist's privilege assertion and the BAA
• Family therapy records, custody disputes, and AI scribes — the dual-subpoena problem when session audio contains PHI on multiple individuals, and why cloud vendors are an independently reachable target
• Play therapy documentation and minor PHI — HIPAA's special rules for minor clients, parental representative access, and what AI scribes do with a child client's session audio
• 42 CFR Part 2 and AI scribes for addiction counseling — the federal SUD record protection standard and why cloud scribe BAAs are almost never written to accommodate it
• The 7 things Mentalyc, Upheal, and Blueprint actually send to their servers — a category-by-category breakdown of cloud scribe data flows, vendor retention windows, and what the BAA does not prevent

This post is educational commentary, not legal, clinical, or compliance advice. HIPAA, 42 CFR Part 2, state mental health privilege law, and child protective services statutes vary by jurisdiction and change over time. Consent requirements for AI-assisted documentation, vendor BAA scope, and subpoena exposure depend on the specific facts of each clinical and legal situation. Consult a licensed healthcare attorney for guidance specific to your practice, client population, state, and documentation workflow before making compliance decisions based on this content.