You've been here before: your eating disorder PHP patient is making progress, the clinical team believes continued care is essential, but the payer's concurrent review comes back denied. The reason? "Medical necessity not demonstrated." You know the patient needs PHP-level care, but somehow your documentation didn't convince the utilization reviewer on the other end of the fax machine.
Winning concurrent review battles for eating disorder PHP programs requires more than good clinical care. It demands a sophisticated understanding of what payers actually look for when evaluating concurrent review eating disorder PHP medical necessity, how to document it in language that survives scrutiny, and when to escalate strategically. This guide gives you the tactical approach that high-performing programs use to protect patient access and program revenue.
Understanding Concurrent Review vs. Initial Authorization in Eating Disorder PHP
Concurrent review is fundamentally different from the initial authorization you secured at admission. Concurrent review is for extension of previously approved services like PHP while the patient remains admitted, based on current medical information to determine ongoing medical necessity and level of care, distinct from prospective review prior to service delivery.
Here's why this distinction matters for eating disorder programs: while your initial authorization may have been approved based on admission presentation (acute weight loss, medical instability, suicidal ideation), concurrent review asks a harder question. Does the patient still require this specific level of care right now, or could they step down to a less intensive setting?
Eating disorder PHP programs face more frequent concurrent review scrutiny than general mental health programs for two reasons. First, average lengths of stay are longer, typically 4-8 weeks compared to 2-3 weeks for mood or anxiety disorders. Second, payers remain skeptical about sustained medical necessity beyond the initial crisis stabilization, particularly when weight restoration appears on track or vital signs have normalized.
Understanding appropriate level of care criteria for eating disorders helps you frame your concurrent review submissions in terms payers recognize as medically necessary.
Clinical Indicators That Justify Continued PHP Stay for Eating Disorders
Payers evaluate eating disorder PHP medical necessity using specific clinical indicators. Your concurrent review documentation must address these explicitly, not assume the reviewer will infer medical necessity from general progress notes.
Weight Trajectory and Restoration Progress: Document current weight, percentage of ideal body weight or BMI, weekly weight change trend, and clinical rationale for continued PHP versus step-down. A patient at 82% IBW gaining 0.5 pounds weekly may still require PHP if they have a history of rapid decompensation at this weight threshold or demonstrate continued resistance to independent eating.
Vital Sign Stability: Cigna criteria include life-threatening complications of eating disorders, active general medical conditions requiring monitoring, and severity necessitating 24-hour psychiatric/medical interventions. Document orthostatic vital signs, heart rate trends, electrolyte values, and ECG findings when applicable. A patient with persistent bradycardia (HR 45-50) or orthostatic changes requires explicit documentation of why outpatient monitoring is insufficient.
Meal Completion Rates and Eating Behaviors: Quantify meal completion percentages, supplement needs, time required to complete meals, and behavioral interference. "Patient completed 60% of meals independently this week, required staff support for remaining 40%, with average meal time of 75 minutes" demonstrates ongoing need for structured support better than "patient struggling with meals."
Behavioral Risk Factors: Document purging frequency, exercise behaviors, body checking rituals, food restriction patterns, and any safety concerns. Include objective measures: "Patient engaged in purging 3 times this week, down from 8 times last week, but continues to require bathroom monitoring post-meals."
Psychiatric Comorbidity: Aetna considers medically necessary assessments including psychiatric evaluation for concurrent illness in eating disorders. Depression, anxiety, OCD, trauma symptoms, and suicidal ideation all strengthen medical necessity arguments when documented with severity indicators and functional impact.
Functional Impairment: Describe specific functional limitations that require PHP structure: inability to meal plan independently, need for real-time coaching during meals, requirement for immediate intervention when urges arise, or inability to maintain safety between sessions. Functional impairment is often the deciding factor between PHP and IOP.
Payer-Specific Concurrent Review Expectations
Not all payers review eating disorder PHP concurrent reviews the same way. Understanding these differences allows you to tailor your submission strategy.
UnitedHealthcare (UHC): Typically requests concurrent review every 5-7 days for eating disorder PHP. UHC reviewers focus heavily on objective medical indicators and often push for step-down once vital signs normalize, even if behavioral and psychological symptoms remain significant. Your documentation must explicitly connect behavioral symptoms to medical risk and functional impairment.
Aetna: Generally reviews every 7-10 days and places significant weight on psychiatric comorbidity and functional assessment. Aetna is more receptive to arguments about trauma processing, family system work, and relapse prevention when framed as medical necessity. Include specific examples of how PHP structure prevents immediate decompensation.
Blue Cross Blue Shield (BCBS): Review frequency and criteria vary significantly by state plan. Most BCBS plans review weekly and expect clear documentation of progress toward discharge criteria. They respond well to structured treatment planning that shows measurable progress while justifying continued need for current level of care.
Cigna: Cigna requires review and approval of eating disorder treatment within 48 hours of admission, including consideration of appropriateness for PHP level of care, and defines medical necessity based on interference with daily living requiring structured interventions and secondary conditions like life-threatening eating disorder complications. Expect frequent reviews (every 3-5 days initially) with close scrutiny of medical monitoring needs.
Humana: Reviews typically occur every 7 days with emphasis on whether less restrictive care could meet treatment needs. Humana reviewers often challenge continued PHP stay if the patient appears stable, so your documentation must proactively address why IOP would be insufficient given current clinical presentation.
Writing Concurrent Review Notes That Survive Scrutiny
The difference between approval and denial often comes down to documentation specificity. Vague clinical language gets denied. Precise, objective documentation that explicitly addresses medical necessity criteria gets approved.
Weak Documentation Example: "Patient continues to struggle with eating disorder behaviors and requires continued PHP care. Making some progress but not ready for step-down. Recommend continued PHP."
Strong Documentation Example: "Patient currently at 84% IBW (up from 81% at last review), demonstrates persistent bradycardia (HR 48-52 at rest), and completed 65% of meals independently this week with continued difficulty at dinner (required staff coaching for all 7 dinners, average meal time 90 minutes). Purging behaviors reduced from 6x to 2x this week. PHQ-9 score 18 (moderate-severe depression). Patient unable to implement meal plan independently in home environment during therapeutic passes this weekend, requiring parent intervention 4 of 6 meals. Medical necessity for PHP level continues based on: (1) cardiac monitoring needs given persistent bradycardia, (2) structured meal support requirement demonstrated by therapeutic pass performance, (3) behavioral intervention needs exceeding what can be provided in 3x weekly IOP structure. Step-down to IOP planned when patient demonstrates 3 consecutive days of independent meal completion >80% and HR consistently >55."
Notice the difference: the strong example provides objective data, quantifies behaviors, connects symptoms to level of care need, and includes specific step-down criteria. This documentation style makes it difficult for a reviewer to deny continued stay.
Incorporating principles from evidence-based treatment planning helps ensure your concurrent review documentation aligns with measurable clinical outcomes that payers recognize.
Leveraging Peer-to-Peer Review Strategically
When a concurrent review denial occurs or appears imminent, requesting a peer-to-peer review can be your most powerful tool. But timing and preparation matter.
When to Request Peer-to-Peer: Request immediately upon receiving an adverse determination or reduction in authorized days. Don't wait. Concurrent reviews for PHP extensions are conducted by experienced licensed staff, with same-day determinations (within 3 hours) for urgent cases, implying peer or physician review when medical necessity is assessed for authorization extensions.
Also request peer-to-peer proactively when you anticipate pushback: when you're requesting authorization beyond typical length of stay for your payer, when the patient's presentation doesn't fit typical eating disorder profiles, or when you're making a complex argument about medical necessity that may not be apparent from documentation alone.
Who Should Conduct It: Your medical director, program psychiatrist, or most senior clinician should conduct peer-to-peer reviews. The person on the call should have prescribing authority if possible, as this creates peer-level credibility with the reviewing physician. Ensure they've reviewed the complete chart, understand the specific denial rationale, and can speak to both medical and behavioral components of medical necessity.
Preparing for the 10-Minute Call: These conversations are brief. Prepare a structured presentation: patient demographics and diagnosis, admission presentation and initial medical necessity, progress to date with objective measures, current clinical status with specific medical necessity indicators, and explicit rationale for why step-down would be clinically inappropriate or unsafe at this time.
Anticipate the reviewer's likely objections and prepare responses. If vitals have stabilized, explain behavioral and functional indicators that still require PHP structure. If weight restoration is progressing, discuss psychological factors, family dynamics, or comorbid conditions that necessitate continued intensive treatment. Frame everything in terms of medical necessity and risk, not just clinical preference.
Invoking MHPAEA in Eating Disorder Concurrent Review
The Mental Health Parity and Addiction Equity Act (MHPAEA) requires payers to apply comparable medical necessity criteria to mental health and medical/surgical benefits. This becomes a powerful argument when payers apply stricter continued stay criteria to eating disorder PHP than to comparable medical conditions.
Here's how to make the parity argument effectively in concurrent review: Document when a payer is requiring more frequent reviews, more stringent step-down criteria, or different medical necessity standards for eating disorder PHP than they would for a comparable medical condition requiring similar intensity monitoring and intervention.
For example, if a patient with anorexia nervosa has persistent bradycardia, orthostatic instability, and electrolyte abnormalities requiring daily monitoring, compare this to a cardiac patient in a cardiac rehab program or a diabetic patient in an intensive diabetes management program. Would the payer require the same frequency of concurrent review? Would they push for step-down while objective medical indicators remained unstable?
When making an MHPAEA argument, document it explicitly in your concurrent review submission and peer-to-peer conversations. State: "We believe the criteria being applied to continued PHP authorization for this eating disorder patient are more restrictive than those applied to comparable medical conditions requiring similar monitoring and intervention intensity, which may constitute a parity violation under MHPAEA."
This language signals to the payer that you understand your rights and the patient's protections. It often results in more careful review and, in some cases, approval of continued stay to avoid parity complaints.
Building a Proactive UR System That Prevents Denials
The most successful eating disorder PHP programs don't just react to concurrent review requests. They build documentation and review systems that prevent denials before they happen.
Documentation Workflow: Implement a daily documentation protocol where clinicians capture the specific medical necessity indicators payers require: vital signs, weight, meal completion percentages, behavioral incidents, and functional status. This shouldn't be a separate "UR note" but rather integrated into your standard clinical documentation structure.
Understanding compliant documentation practices for eating disorder treatment ensures your clinical notes support both quality care and reimbursement needs.
Clinical Note Templates: Develop templates that prompt clinicians to document medical necessity indicators. Include fields for: current weight and percentage of goal, vital sign trends, meal completion data, behavioral incidents with frequency and severity, psychiatric symptom measures, functional assessment, progress toward treatment goals, and explicit justification for current level of care.
Internal Review Cadence: Conduct internal utilization review 24-48 hours before payer concurrent review is due. Have your UR coordinator or clinical director review documentation for medical necessity clarity and identify gaps before the payer sees them. This allows time to supplement documentation if needed.
Payer-Specific Tracking: Maintain a database of payer-specific concurrent review patterns: typical authorization periods, common denial reasons, successful appeal arguments, and reviewer tendencies. This institutional knowledge allows you to anticipate payer behavior and tailor submissions accordingly.
Multidisciplinary Input: Ensure concurrent review submissions reflect input from the full treatment team, including psychiatry, medical monitoring, nursing, therapy, and nutrition. The role of registered dietitians in documenting nutritional rehabilitation needs is particularly important for eating disorder medical necessity arguments.
Step-Down Criteria Transparency: Document specific, measurable step-down criteria in every concurrent review submission. This demonstrates treatment planning sophistication and shows the payer you're working toward appropriate discharge, not trying to keep the patient indefinitely. It also makes it harder for reviewers to argue the patient is ready for step-down when they clearly haven't met your documented criteria.
Protect Your Patients and Your Program
Concurrent review denials don't just impact your program's revenue. They disrupt patient care, force premature step-downs that increase relapse risk, and erode trust in the treatment process. Developing sophisticated concurrent review strategies protects both patient access and program sustainability.
The programs that consistently win concurrent review battles share common characteristics: they understand payer-specific expectations, document medical necessity explicitly and objectively, leverage peer-to-peer review strategically, invoke parity protections when appropriate, and build proactive systems that prevent denials before they occur.
If your eating disorder PHP program is struggling with concurrent review denials, it's time to upgrade your approach. The clinical care you're providing is medically necessary. Now you need the documentation and advocacy strategies to prove it to payers.
Ready to strengthen your utilization review process and reduce concurrent review denials? Forward Care specializes in helping behavioral health providers navigate complex payer relationships and optimize revenue cycle performance. Contact us today to learn how we can support your eating disorder program's financial sustainability while protecting patient access to care.
