Eating disorder level-of-care decisions and AI scribes: when insurance reviewers, malpractice plaintiffs, and treatment teams all want the same records

Eating disorders carry the highest mortality rate of any psychiatric condition. The clinical decision about level of care — whether a client can continue in outpatient therapy, should move to intensive outpatient or partial hospitalization, needs residential treatment, or requires medical inpatient stabilization — is the pivot point on which medical outcomes and legal liability both turn. Get it wrong in one direction and the client is under-resourced for the severity of their illness; get it wrong in the other direction and insurance will deny the claim and the client faces catastrophic out-of-pocket costs. This is not a routine documentation moment. It is the clinical record's most consequential page.

This post addresses a documentation risk specific to the LOC decision — distinct from the broader question of eating disorder therapy notes and insurance disclosure generally. The focus here is on what happens when a cloud AI scribe is running during the verbal LOC consultation: what the vendor captures, who wants that record, and how the multi-disciplinary team structure of eating disorder treatment creates a third-party custody problem that is more complex than any other clinical specialty covered in this series.

What level of care means in eating disorder treatment

Eating disorder treatment uses a five-level continuum of care that is unique in psychiatric practice in its integration of medical and behavioral criteria. The five levels — outpatient, intensive outpatient (IOP), partial hospitalization (PHP), residential, and inpatient medical stabilization — correspond to progressively higher medical acuity, behavioral severity, and inability to interrupt eating disorder behaviors in less structured environments.

Medical instability criteria. The clinical criteria for LOC escalation are anchored in measurable medical parameters. Inpatient medical stabilization is typically indicated by a resting heart rate below 50 beats per minute, orthostatic blood pressure changes of 20+ mmHg systolic or 10+ mmHg diastolic on standing, clinically significant electrolyte abnormalities (hypokalemia, hypophosphatemia, hypomagnesemia), QTc prolongation on ECG, or weight at or below 75% of ideal body weight. These are not abstract clinical judgments — they are specific numbers, verbally communicated in the LOC consultation, that insurance reviewers will later scrutinize in coverage determinations and that malpractice plaintiff's attorneys will examine when a client suffers a cardiac event.

Behavioral and functional criteria. The residential and PHP thresholds involve behavioral indicators that are disclosed by the client and assessed by the treatment team: restriction levels (what the client is eating and not eating per day), purging frequency and method, compensatory behaviors (excessive exercise, laxative use, water loading), the client's ability to interrupt behaviors without external structure, family environment factors that enable or sustain the eating disorder, and psychiatric co-morbidities including suicidality and mood disorder severity. Each of these is verbally discussed in the LOC consultation — named, quantified, and assessed against criteria.

The clinical guidelines and the payer criteria divergence. American Psychiatric Association practice guidelines, the Academy for Eating Disorders Medical Care Standards Guide, and the Society for Adolescent Health and Medicine criteria represent clinical consensus. Payers apply different criteria — typically the Milliman Care Guidelines or their own proprietary medical necessity criteria — that frequently authorize lower levels of care than clinical consensus would support. This gap between clinical and payer criteria is the structural driver of eating disorder coverage disputes: the clinician recommends residential, the payer approves PHP, the LOC decision becomes the subject of an administrative appeal or coverage litigation. The LOC consultation documentation — what the treatment team assessed, what criteria they applied, what specific medical and behavioral indicators they identified — is the evidentiary foundation of that dispute.

What a cloud AI scribe captures during a LOC consultation

The LOC consultation in eating disorder treatment is typically a verbal exchange: a session with the client to review current status, a treatment team discussion (in person, by phone, or by video), a conversation with the client's family when the client is a minor, and sometimes a call with the prescribing physician or RD to confirm medical parameters. When a cloud AI scribe is running during any portion of this exchange, the vendor captures a verbatim record of:

• The specific vital signs, weight measurements, and lab values mentioned aloud — the treating physician saying "her resting heart rate was 46 this morning and her potassium came back at 3.1" is captured verbatim, not summarized
• The client's own account of current behaviors: restriction levels, purging frequency, exercise behaviors, and how they have changed since the last clinical contact — stated in the client's own words, which may be more specific than what the formal note records
• The treatment team's expressed uncertainties: whether the client meets residential criteria, whether the family can provide adequate supervision at PHP, whether the client's denial of severity makes accurate behavioral self-report unreliable
• Disagreements within the treatment team about the appropriate LOC — the therapist recommending residential while the RD believes PHP is sufficient, or the prescribing physician clearing for lower LOC while the therapist believes the behavioral severity warrants escalation
• Family session content at LOC transition points, often involving a minor client whose parents are legally authorized to make the LOC decision — including the parents' disclosed concerns, resistance, or financial constraints that may be influencing the LOC recommendation
• The insurance pre-authorization discussion: conversations in which the clinical team talks through how to present the LOC request to the payer, what criteria to emphasize, and what the expected payer response is

As documented in the cloud data-flow explainer, the vendor retains raw audio, intermediate transcript, and generated note drafts. For an eating disorder LOC consultation, this means the vendor's servers hold the most complete record of the clinical team's verbatim assessment — a record that may contain more specific medical detail, more candid clinical uncertainty, and more behavioral specificity than the formal clinical note that goes into the chart.

The multi-disciplinary team custody problem

Eating disorder treatment is unusual in psychiatry and mental health in consistently deploying a multi-disciplinary team. A client in residential or PHP treatment is typically seen by a therapist, a registered dietitian, a prescribing physician or psychiatrist, and a medical internist or pediatrician. Each team member maintains their own clinical documentation. In 2026, each may use a different cloud AI scribe tool from a different vendor.

When the treatment team holds a case conference — a weekly team meeting, a crisis LOC consultation, a discharge planning session — multiple clinicians may each have their own AI scribe running simultaneously. The result is not one independent vendor archive of the treatment team discussion. It is potentially four or five independent vendor archives, each held by a different cloud vendor in a different jurisdiction, each separately reachable by legal process directed at that vendor. The therapist's cloud AI scribe vendor, the RD's cloud AI scribe vendor, and the prescribing physician's cloud AI scribe vendor all hold verbatim audio of the same treatment team conversation. Each is a distinct legal entity. Each receives its own subpoena. The clinical team's privilege assertions over their own records do not extend to any of these vendors.

This is the third-party custody problem specific to multi-disciplinary eating disorder treatment: the number of independently subpoenable archives multiplies with the number of team members using cloud AI scribes. A BAA between any individual team member and their vendor does not consolidate or limit the other vendors' independent record holdings.

The insurance dispute path

Coverage disputes over eating disorder LOC — particularly denials of residential treatment and PHP — are among the most frequently litigated healthcare coverage disputes in the United States. Following the Mental Health Parity and Addiction Equity Act (MHPAEA) and its enforcement strengthening under the 2020 final rules, insurance companies face increasing scrutiny of how they apply medical necessity criteria to mental health conditions relative to analogous physical health conditions. Eating disorder advocates and legal teams have been particularly active in parity litigation.

In administrative appeals and coverage litigation, the record at issue is the clinical basis for the LOC determination: what medical and behavioral indicators supported the recommendation, what criteria the clinician applied, and whether the payer's denial met the parity standard. As the utilization review post explains, insurance companies have broad rights to clinical record review in the coverage decision context. In coverage litigation, discovery rights extend to any party holding relevant records — including cloud AI scribe vendors who retained session audio from the LOC consultation.

The payer's interest in the vendor's verbatim session audio is straightforward: the formal clinical note records the clinician's final LOC recommendation and the supporting criteria. The vendor's verbatim audio may reveal the path to that recommendation — expressed uncertainties, lower clinical acuity initially assessed and then revised, or family financial constraints that the clinical team discussed as a factor in the LOC recommendation. In coverage litigation, the gap between the clinical note and the verbatim session audio can be dispositive.

The malpractice exposure from under-treatment

Eating disorders produce medical emergencies in outpatient and lower-LOC settings. Sudden cardiac death from QT prolongation and electrolyte imbalance can occur in patients who appeared medically stable at the most recent clinical contact. Refeeding syndrome — a potentially fatal shift in fluid and electrolyte balance during nutritional rehabilitation — can develop rapidly during outpatient weight restoration in patients whose prior starvation left them at risk for hypophosphatemia. Esophageal complications of chronic purging include Mallory-Weiss tears and, in rare cases, Boerhaave syndrome. These medical catastrophes can occur in patients who were assessed as appropriate for outpatient or IOP levels of care.

When a patient suffers a medical catastrophe at a lower LOC, and the family pursues a malpractice claim, the LOC decision is the primary litigation target. Plaintiff's counsel needs to establish: what medical indicators existed at the time of the LOC determination, whether the clinical team's assessment was adequate for the documented medical picture, and whether continued outpatient management was defensible against applicable clinical guidelines. As the subpoena explainer documents, subpoenas to cloud AI scribe vendors can reach the treatment team's verbatim audio independently of what the clinicians themselves produce. The vendor's session archive of the LOC consultation — including expressed team uncertainties, the specific vital signs discussed, and the clinical reasoning verbally articulated — is directly probative of whether the standard of care was met.

On-device processing and the single-custodian LOC record

When session audio is processed entirely on the clinician's device — transcribed by Whisper.cpp running on Apple Silicon, drafted by an on-device language model, never uploaded to cloud infrastructure — the LOC consultation has one custodian: the clinician. There is no vendor holding a verbatim archive of the treatment team's discussion of vital sign thresholds, behavioral severity, or clinical uncertainty. The clinician's formal treatment note is the primary record of what was assessed and decided. There is no independently reachable third-party archive from which insurance discovery or malpractice plaintiff subpoenas can extract the verbatim content of the LOC consultation before the clinician's own privilege and record-management decisions are reached.

For clinicians working in multi-disciplinary eating disorder settings — especially those where the treatment team coordinates on high-acuity LOC decisions with medical precision — the question of how many independent vendor archives exist of each team consultation is a structurally different problem than it is in solo outpatient practice. On-device processing by each team member reduces the number of independently held vendor archives to zero for any given team member's usage, regardless of what tools other team members are using.

Further reading

• Eating disorder therapy notes, sensitive diagnoses, and the cloud AI scribe problem — the foundational post on eating disorder records: sensitive diagnoses, insurance disclosure risk, minor consent, self-pay decisions, and why eating disorder records carry heightened stakes beyond the standard HIPAA analysis
• CBT progress notes, insurance utilization review, and what auditors actually read — how insurance utilization review and coverage determination processes access clinical records, and what the payer's auditor is looking for when reviewing treatment records
• The 7 things Mentalyc, Upheal, and Blueprint actually send to their servers — the request-by-request data flow behind cloud AI scribes, the artifact tiers retained on vendor infrastructure, and what the vendor's archive contains beyond the finished note
• Can an AI therapy note be subpoenaed? A 2026 legal-risk explainer — how civil and criminal subpoenas reach cloud AI vendors as separate custodians and what the clinician cannot control about the vendor's response
• What is a BAA, actually — and what it does NOT cover — the structural limits of business associate agreements: why a signed BAA does not prevent a vendor's records from being subpoenaed and why the BAA chain does not consolidate multiple vendors' independently held archives

This post is educational commentary, not legal, clinical, regulatory, or compliance advice. Eating disorder level-of-care criteria, insurance medical necessity standards, parity enforcement mechanisms, and the scope of discovery rights in coverage litigation and malpractice proceedings vary significantly by state, jurisdiction, payer, and clinical setting. The interaction between HIPAA, therapist-client privilege, and third-party vendor subpoena obligations is fact-specific and jurisdiction-specific. Consult a licensed healthcare attorney and a qualified legal professional before making documentation or technology decisions for a practice that regularly handles clients at elevated medical risk due to eating disorder severity.