Eating disorder co-treatment and dual cloud AI scribe archives: when the therapist and registered dietitian each use a different vendor, five adversarial proceedings reach both archives independently

Standard eating disorder outpatient treatment in 2026 is a multi-provider enterprise. The American Psychiatric Association's practice guidelines and the Academy for Eating Disorders' Medical Care Standards Guide both identify collaborative treatment by a mental health clinician and a registered dietitian nutritionist as the baseline standard of care for outpatient eating disorder treatment. The treatment plan for a client with anorexia nervosa, bulimia nervosa, or binge eating disorder working with an outpatient team typically assigns the therapist responsibility for the psychological and behavioral components — cognitive distortions, emotion regulation, body image work, trauma history where relevant, interpersonal functioning — and the RD responsibility for the nutritional rehabilitation components: medical nutrition therapy, meal planning, weight restoration targets, behavioral work around food exposure and flexibility, and medical monitoring of nutritional status across the treatment course.

What this means in practice is that the same client generates clinical records at two separate provider relationships, often at two separate practices, with two separate intake structures, and — if each provider uses a cloud AI scribe — two separate BAA relationships with potentially different vendors and two independently held vendor archives. The therapist's session documentation and the RD's session documentation are not duplicates. The therapist's sessions capture what the client says about their emotional relationship with food, their body image, their behavioral patterns around eating, the psychological dynamics driving the eating disorder, and the treatment progress from the mental health perspective. The RD's sessions capture what the client reports about actual dietary intake, weight, physical symptoms, the content of meal planning discussions, the client's implementation of nutritional goals, and the RD's clinical reasoning about nutritional status and level-of-care criteria. The two documentation streams together constitute a more comprehensive contemporaneous record of the eating disorder treatment than either provider's sessions alone.

In 2026, a significant proportion of both therapists and RDs in private practice use cloud AI scribes. The market largely draws from the same vendor pool — Mentalyc, Upheal, Blueprint, Freed, Supanote — used across multiple health professions that document patient interactions with verbatim detail. When a therapist and an RD co-treating the same eating disorder client each subscribe to a cloud AI scribe, each creates an independent vendor archive of the sessions they document. Those archives are separately held by each vendor under separate BAA relationships, each accessible through independent legal process directed at each respective vendor. The co-treatment relationship that was designed to provide comprehensive clinical coverage for the client also creates a dual-archive structure that five categories of adversarial proceedings can use to reconstruct the treatment from both professional angles simultaneously.

What the dual-archive structure looks like — and why it differs from single-provider documentation

When a therapist uses a cloud AI scribe, the vendor archive holds session audio, verbatim or near-verbatim transcripts, note drafts, and session metadata. In eating disorder treatment, the therapist's sessions contain the client's disclosures about food-related cognitions, restriction behaviors, purging frequency, body image preoccupations, emotional triggers, interpersonal dynamics affecting the eating disorder, and the therapist's clinical reasoning about treatment direction and, when relevant, step-up criteria. That session content is already highly sensitive in insurance and legal contexts. The therapist's vendor archive is a separately accessible custodian of that content, reachable through legal process directed at the vendor independent of anything the therapist produces through normal records channels.

The RD's vendor archive is different in content but parallel in structure. The RD's sessions with the same client capture the medical nutrition therapy relationship: the client's reported intake for the preceding week, specific weight measurements discussed in session, the RD's assessment of weight restoration progress against target, electrolyte or vital sign concerns the client mentions, meal planning revisions, the client's behavioral progress with food exposure tasks, the RD's assessment of whether the client is medically appropriate for continued outpatient level of care, and any concerns the RD has about the pace of weight restoration or the adequacy of nutritional intake. That content is clinical documentation of the medical nutrition therapy relationship — a distinct professional record from the therapist's clinical file but documenting the same eating disorder treatment and, often, much of the same client-disclosed information about food behaviors.

The structural difference between a single-provider cloud AI scribe situation and the co-treatment dual-archive situation is that there are now two separately subpoenable custodians documenting the same clinical relationship from two professional angles. Adversarial proceedings that previously would have directed legal process at one vendor can direct it at two. The reconstruction of the eating disorder treatment available through both archives together goes well beyond what either provider chose to document in their formal progress notes — capturing the verbatim content of each provider's sessions with the client, including clinical reasoning, expressed uncertainties, discussions of step-up criteria, and mentions of inter-provider communication that the formal note summarized but did not reproduce in full.

Proceeding 1 — insurance concurrent utilization management reaching both documentation streams

Eating disorder treatment at outpatient intensity — or at IOP or PHP — routinely involves insurance concurrent utilization management. UM reviewers assess ongoing medical necessity at regular intervals, requesting clinical documentation from treating providers to confirm that the client continues to meet criteria for the authorized level of care. Under HIPAA's healthcare operations and payment exception at 45 CFR 164.501, covered entities may disclose PHI to payors for payment purposes, which includes utilization review. The UM reviewer's contact with each treating provider's documentation reaches, through normal claims and payment processes, information generated by both the therapist and the RD.

In a co-treatment relationship where both providers use cloud AI scribes, the notes submitted to UM are vendor-assisted notes — generated from the same session audio that resides in each vendor's archive. The UM reviewer who contests medical necessity and escalates to a coverage dispute gains access, through discovery in any subsequent litigation, to both vendors as independent sources of contemporaneous session-level documentation. The UM reviewer's internal assessment of whether the client met step-up criteria may have been based partly on what the therapist's notes said about behavioral severity and partly on what the RD's notes said about medical stability and weight trajectory — documentation streams that came from two separate vendor archives holding two independent records of the same treatment period. The level-of-care decision is the most legally exposed moment in eating disorder documentation — and in co-treatment, that decision is documented from two sides simultaneously.

Proceeding 2 — level-of-care coverage litigation with two independent subpoena targets

When an insurer denies PHP or IOP level-of-care coverage and the client or provider challenges the denial through an administrative appeal or a civil lawsuit, discovery in the coverage litigation reaches beyond each provider's formal clinical file. Rule 45 subpoenas — or state court equivalents — directed at non-party business entities in possession of relevant documents can reach the therapist's cloud AI scribe vendor and the RD's cloud AI scribe vendor as two separate non-party custodians. Under HIPAA's judicial proceedings exception at 45 CFR 164.512(e), each vendor may respond to qualifying subpoenas with satisfactory assurances that notice was provided to the affected individual.

The two vendor archives provide coverage litigants with a reconstruction of the co-treatment that is more complete than what either provider's formal progress notes document. The therapist's vendor archive holds the psychological and behavioral documentation: the client's session-by-session disclosures about restriction behaviors, the therapist's assessment of behavioral severity, any expressed clinical concern about step-up criteria, and the reasoning the therapist documented around why the client was or was not appropriate for a higher level of care. The RD's vendor archive holds the medical nutrition therapy documentation: specific weight measurements discussed in session, the RD's assessment of weight restoration progress, concerns about medical stability, and the RD's clinical reasoning about whether the client met or approached step-up criteria from the nutrition perspective. Together, those two archives give both sides of the coverage litigation a verbatim contemporaneous record of the co-treatment team's full knowledge of the client's status during the dispute period — including content that neither provider chose to put in the formal progress note submitted to the insurer.

Proceeding 3 — malpractice following catastrophic medical outcome

Eating disorders carry the highest mortality rate of any psychiatric condition. Catastrophic medical outcomes — sudden cardiac death from electrolyte imbalance, refeeding syndrome complications during weight restoration, multi-organ failure in severe anorexia nervosa — generate malpractice litigation when they occur in clients receiving outpatient co-treatment. Plaintiff's counsel in eating disorder malpractice cases focuses on the level-of-care decision and on what each member of the co-treatment team knew about the client's medical status at each point in the treatment. The question is not just what each provider documented in their formal clinical notes, but what each provider said and reasoned during sessions with the client — the contemporaneous knowledge state that the clinical note summarizes and selects from.

In a co-treatment malpractice case, plaintiff's counsel serves Rule 45 subpoenas on the therapist's cloud AI scribe vendor and separately on the RD's cloud AI scribe vendor. Each vendor's archive is an independently subpoenable source of contemporaneous session-level evidence. The therapist's vendor archive may contain sessions in which the client mentioned physical symptoms, the therapist noted the client's stated weight or medical concerns, or the therapist documented a discussion about contacting the RD or recommending medical evaluation. The RD's vendor archive may contain sessions in which the RD documented specific weight measurements, electrolyte concerns the client mentioned, cardiac symptoms the client reported, or the RD's reasoning about whether to recommend escalating the frequency of medical monitoring. Together, the two archives reconstruct the co-treatment team's full contemporaneous knowledge — including any discussions, clinical concerns, or expressed uncertainties that neither provider put in their formal progress note but that the scribe's session transcript preserved verbatim.

Proceeding 4 — licensing board investigation under the health oversight exception

When a complaint is filed about an eating disorder co-treatment — alleging inadequate monitoring, inappropriate level-of-care decisions, failure to coordinate care between the therapist and the RD, or contradictory clinical recommendations — the relevant licensing boards may investigate. A complaint against the therapist triggers the state psychology, social work, or counseling board's investigation. A complaint against the RD triggers the state dietetics or nutrition board's investigation. Both boards have health oversight authority under HIPAA 45 CFR 164.512(b) to access PHI relevant to the investigation without patient authorization.

In co-treatment cases where the complaint concerns the adequacy of coordinated care — for example, a family alleging that the therapist and the RD gave contradictory guidance about weight restoration targets, or that neither provider responded adequately to escalating medical indicators — both boards may investigate the same treatment period in parallel. Each board reaches the respective provider's cloud AI scribe vendor archive through the health oversight exception. The therapist's board investigation reaches the therapist's vendor archive; the RD's board investigation reaches the RD's vendor archive. The two investigations may proceed simultaneously, with neither board having visibility into what the other board is finding in the other provider's archive. The client may be unaware that either investigation is underway. The therapist may not know that the dietetics board is separately investigating the RD's contribution to the co-treatment. The dual-archive structure means that a single complaint about the co-treatment relationship can produce two parallel regulatory proceedings, each accessing a different vendor's records of the same clinical period, without either provider or the client having a unified view of what both investigations are reaching.

Proceeding 5 — minor consent and parental access in adolescent eating disorder co-treatment

Adolescent eating disorder treatment frequently involves the same multi-provider structure: a therapist providing individual therapy and an RD providing medical nutrition therapy. When the minor patient has consented to mental health treatment under a state minor consent statute — which many states permit for outpatient mental health services beginning at age 12 to 14 — the therapist's records may be shielded from parental access under state law. Where state law gives the minor control over the mental health treatment decision, the parent's HIPAA personal representative authority at 45 CFR 164.502(a) may be limited or denied for the therapist's clinical file.

That protection does not automatically extend to the RD's records. State minor consent statutes for mental health treatment may not encompass medical nutrition therapy or dietetic counseling, which are licensed under separate state practice acts as distinct health professions with their own consent frameworks. A parent seeking access to their minor child's eating disorder treatment records may be denied access to the therapist's clinical file — and to the therapist's cloud AI scribe vendor archive — while retaining full personal representative access under HIPAA to the RD's session documentation and the RD's vendor archive. The parent's attorney who discovers that the therapist's records are protected under a minor consent framework has an alternative access route through the RD's vendor. The RD's vendor archive documents the same eating disorder treatment period in the nutrition counseling register — a record that often captures the same client disclosures about food behaviors, the same treatment timeline, and the same clinical milestones as the therapy record, but documented from the medical nutrition therapy relationship that the minor consent statute does not shield from parental access. The dual-archive structure creates a consent asymmetry that parents' attorneys in adolescent eating disorder custody or treatment-decision disputes can navigate by routing toward the unprotected provider's vendor rather than the protected one.

Why on-device processing eliminates the therapist's contribution to the dual-archive structure

The dual-vendor-archive problem is a structural consequence of two providers each choosing cloud-based documentation tools. The therapist controls one side of that structure — their own documentation choices. The RD's documentation choices are independent.

A therapist who processes session audio on-device — using local transcription and note drafting without transmitting audio or transcripts to cloud infrastructure — creates no vendor archive on the therapist's side of the co-treatment. There is no therapist-side vendor to subpoena in coverage litigation. There is no therapist-side archive for malpractice plaintiff's counsel to reach through Rule 45 process. There is no therapist-side vendor for a licensing board to access through the health oversight exception. There is no therapist-side archive for a parent's attorney to circumvent minor consent protections by reaching directly. The therapist's clinical documentation exists in the therapist's own clinical file, under the therapist's professional custody, accessible only through process directed at the therapist — the same structure that has always existed for therapist records in the pre-cloud-scribe environment.

The RD's documentation choices remain independent. If the RD uses a cloud AI scribe, the RD's vendor archive remains a separately accessible custodian of the nutrition counseling sessions. Coverage litigants, malpractice plaintiffs, licensing boards, and parents' attorneys who know to look for the RD's vendor can still reach that archive through appropriate process. But the reconstruction of the co-treatment available through dual-vendor-archive subpoena strategy now reaches one archive instead of two. The therapist's clinical file is available through process directed at the therapist, not through a vendor the therapist has no visibility into. The verbatim session transcript that distinguishes the vendor archive from the formal progress note — the content the therapist chose not to reproduce in the clinical note — does not exist as a separately accessible document at a vendor the therapist did not create and cannot monitor.

The business associate agreement the therapist signed with a cloud AI scribe vendor does not prevent the vendor from responding to valid legal process, does not give the therapist visibility into when the vendor receives process, and does not allow the therapist to assert privilege on behalf of the vendor's records in a proceeding the therapist has no notice of. On-device processing eliminates the need for that agreement entirely — there is no business associate relationship to maintain, because there is no cloud-processing vendor relationship. The architectural choice collapses the dual-archive structure to a single-custodian structure for the therapist's sessions, regardless of what the RD has chosen for the RD's sessions. For therapists in eating disorder co-treatment teams, that is the only part of the dual-archive structure they control — and it is the part that on-device processing eliminates at the source.

Further reading

• Eating disorder therapy notes: sensitive diagnoses, insurance disclosure, and the cloud AI scribe problem — the foundational analysis of why eating disorder session content warrants particular documentation care, including insurance underwriting risk, self-pay strategies, and minor consent frameworks
• Eating disorder level-of-care decisions and AI scribes — how the LOC consultation creates insurance dispute and malpractice exposure in the multi-disciplinary team context; the dual-archive analysis above extends that framework to the ongoing co-treatment relationship rather than the LOC consultation itself
• Can an AI therapy note be subpoenaed? — the foundational legal framework for how cloud AI scribe vendors receive and respond to civil and criminal subpoenas as non-party record holders, applicable to both the therapist-side and RD-side archives in the co-treatment structure
• What is a BAA, actually — and what it does NOT cover — the structural limits of business associate agreements, including why a signed BAA does not prevent the vendor from responding to valid legal process and does not give the therapist visibility into the vendor's production decisions in proceedings the therapist has no notice of
• CBT progress notes and insurance utilization review — the broader payment operations framework through which insurer UM departments access clinical documentation, applicable to both the therapist's and the RD's submission streams in the co-treatment concurrent review context

This post is educational commentary, not legal, clinical, regulatory, or compliance advice. The legal analysis of HIPAA exceptions, civil discovery rules, licensing board investigative authority, and minor consent frameworks involves complex statutory and regulatory provisions that vary by jurisdiction, provider type, payer contract terms, and the specific facts of any proceeding. Whether a particular cloud AI scribe vendor archive is accessible in a specific insurance dispute, malpractice claim, licensing investigation, or parental access proceeding depends on the applicable law in the relevant jurisdiction, the vendor's BAA terms and data retention practices, the legal authority of the accessing party, and other fact-specific considerations not fully addressed here. State minor consent statutes vary substantially in scope and application to different licensed health professions. The analysis in this post illustrates structural exposure categories for therapists who participate in eating disorder co-treatment relationships and is not intended to characterize the outcome of any specific proceeding or to constitute legal, clinical, or compliance guidance for any particular situation. Consult a licensed healthcare attorney familiar with your jurisdiction's mental health records law and the applicable professional practice statutes before making documentation or technology decisions in eating disorder co-treatment contexts.