Medicare Partial Hospitalization Certification: The 18th-Day Recertification and the 20-Hour Week Reviewers Check
Table of Contents
A Medicare partial hospitalization program lives or dies on one sentence in each chart: a physician statement that, without this level of care, the patient would need inpatient psychiatric treatment. Everything else in the PHP file, from the 20-hour week to the recertification signatures, exists to prove that sentence was true on the day it was signed and stayed true for every day billed. When a medical reviewer requests a PHP record, that is the chain they follow, and it is where well-run programs most often come up short.
This guide is written for PHP owners, clinical directors and compliance leads who bill Medicare, whether hospital-based or through a community mental health center. It is operational guidance rather than legal advice. Confirm the current requirements against CMS’s own manuals before changing policy.
The PHP Certification Rule in One Paragraph
Medicare partial hospitalization certification, in brief: Medicare pays for partial hospitalization only when a physician certifies, at admission, that the patient would otherwise require inpatient psychiatric care and needs at least 20 hours per week of therapeutic services, and the program must then recertify that need for the first time as of the 18th day of partial hospitalization services and at least every 30 days after that. Each recertification has to show more than a signature: it should document how the patient is responding to treatment, which symptoms still place the patient at risk of hospitalization, and what the team is doing to move the patient toward discharge. The certification and recertification rules sit in 42 CFR 424.24, the scope of PHP services is in 42 CFR 410.43, and CMS explains both in Chapter 6 of the Medicare Benefit Policy Manual.
You can read the regulatory text directly in the eCFR version of 42 CFR 424.24 and the eCFR version of 42 CFR 410.43. CMS’s narrative guidance is in the Medicare Benefit Policy Manual, Chapter 6 (Hospital Services Covered Under Part B), and payment structure is described on the CMS hospital outpatient prospective payment system pages.
What a Reviewer Pulls First
A PHP record request from a Medicare contractor is not read front to back. Reviewers tend to go straight to three documents and test whether they agree with each other.
The first is the initial certification. They check that it exists, that it is signed and dated by an eligible practitioner, that it was completed at or near admission, and that it actually states the inpatient-alternative rationale rather than a generic “patient meets criteria” line.
The second is the treatment plan. Medicare expects PHP services to be furnished under an individualized written plan established and periodically reviewed by a physician, with goals that connect to the reason for admission. A plan cloned from an intake template with the patient’s name swapped in reads exactly like what it is.
The third is the attendance and service log. This is where the 20-hour week stops being a phrase in the certification and becomes arithmetic. If the certification says the patient needs at least 20 hours of therapeutic services a week and the log shows twelve, the reviewer now has a documented contradiction, and the program has to explain it.
Where PHP Files Break: The Usual Causes
The same handful of failure points come up again and again when we review PHP charts before an audit.
- The day-count mismatch: The rule counts the 18th day of partial hospitalization services, but scheduling systems count calendar days from admission, so the recertification reminder fires late for patients who attend five days a week and early for those who miss days.
- The rubber-stamp recertification: The physician signs a one-line “continues to require PHP” form that says nothing about response to treatment, current risk or discharge planning, which is the content CMS expects a recertification to carry.
- The attendance gap nobody escalated: A patient drops to three days a week for transportation or work reasons, the team keeps billing the PHP per diem, and no one documents whether PHP is still the right level of care.
- The signature that came later: The certification or recertification is signed days or weeks after the date it is supposed to cover, often in a batch, and the EHR audit trail shows it.
- The plan that never changes: Treatment plan reviews are documented on schedule but the goals, interventions and discharge criteria are identical from week one to week six.
The Inconvenient Truth About the 20-Hour Week
Most operators read the 20-hour requirement as a scheduling target: build a program day long enough, five days a week, and the requirement is met. That is only half of it. The certification is a statement about what the patient needs, and the attendance log is evidence of what the patient actually received. Reviewers compare the two.
A patient who is certified as needing 20 or more hours a week and who consistently attends far less is a clinical question, not just a billing one. Either the patient’s need has changed, in which case a step-down to intensive outpatient or standard outpatient may be appropriate, or something is getting in the way of attendance, in which case the treatment team should be documenting what it is doing about it. The worst version of the file is the one where attendance falls off and the chart is silent.
The practical fix is a weekly attendance review that flags any patient below the threshold and requires a short clinical note: why attendance dropped, whether PHP is still the right level of care, and what changes are being made. That note is what turns an attendance gap from an audit finding into evidence of active clinical management.
What a Defensible Recertification Contains
A recertification should read like a short clinical argument, not a checkbox. At minimum, it should cover:
- The patient’s response to the specific interventions delivered since the last certification, with concrete examples from group and individual work.
- The psychiatric symptoms that continue to place the patient at risk of inpatient hospitalization, described in current terms rather than copied from the admission note.
- The treatment goals for coordinating services and moving toward discharge, including the anticipated next level of care.
- A signature and date from the certifying practitioner, completed on or before the day it is due.
Who may sign certifications has been an area of regulatory change in recent payment rules, so confirm in the current Medicare Benefit Policy Manual which practitioner types your program may use before relying on anyone other than a physician.
Something You Can Do This Week
Pull every active Medicare PHP patient on today’s census. For each one, write down three things on a single sheet: the admission date, the number of PHP service days attended to date, and the date of the most recent signed certification or recertification. Any patient at or past their 18th service day without a signed recertification, or more than 30 days past their last one, is an open exposure on every claim since the due date. Then pull the last four weeks of attendance for each patient and flag anyone below 20 hours in any week without a clinical note explaining it.
That review usually takes a compliance lead an afternoon. It is the same check a reviewer will run, done before they ask.
Building It Into Operations
The durable fix is to change what triggers the work. Recertification reminders should be driven by the PHP service-day count, not by a calendar offset from admission, and should fire a few service days before day 18 so the physician has time to see the patient and write something substantive. The 30-day recertifications should follow the same logic. Weekly attendance review belongs on the treatment team agenda, not in the billing office. And the recertification template should prompt for response to treatment, ongoing risk and discharge goals, so that a rushed physician still produces a usable document.
Programs that build this into their compliance operations stop treating PHP documentation as a scramble before audits. If you do not have a dedicated compliance lead to own the calendar and the chart audits, a fractional compliance officer can run the review cycle and train the clinical team on what reviewers actually test.
Where to Start
If your PHP has not been audited against the certification chain recently, start with the census review above and then work back through closed charts from the last year. Our behavioral health consultants review PHP and IOP files against Medicare documentation requirements and help programs rebuild templates and workflows around them. Call (888) 458-6619 to talk through your program’s PHP documentation, or to schedule a pre-audit chart review.
Questions about a specific claim or a pending record request? Reach our team directly at (888) 458-6619. This article is general operational guidance and not legal advice; always confirm current requirements with CMS and your Medicare Administrative Contractor.



