Platform
Solutions
Company
Pricing
Register nowSign in

Partial hospitalization

A PHP program where attendance and billing finally agreed

Group-heavy days, per-diem billing, and three separate records of who was actually in the room. The disagreements between them were costing more than the no-shows.

ProbityCarePHP program, 28 daily censusComposite scenario
Level of care
Partial hospitalization
Size
28 average daily census
Payer mix
Commercial, Medicare
Focus
Group documentation and per-diem claims

The situation

Attendance was taken on a printed roster, notes were written that evening, and the claim was built the following week from whichever list the biller could find. When a payer questioned a day, the program had a sign-in sheet, a set of notes, and a claim that did not quite match any of them.

The clinical cost was worse than the billing cost. Twelve group notes per session, written under time pressure, drifted toward identical — which is the finding a reviewer is trained to look for.

What changed

  1. Attendance became the billing recordPresent, late, excused, absent — timestamped per participant, on the session that generates the claim.
  2. Group content written once, response written per personShared clinical content and individual response became separate fields rather than one box that gets duplicated.
  3. Per-diem minimums checked on the dayWhether a day met the payer's service requirement is answered before the claim, not after the denial.
  4. Continued-stay reviews surfaced on scheduleUtilization review stopped discovering expiring authorizations from a remittance.

Results

Three measures, before and after.

Per-diem days denied on attendance
9.1%changed to1.4%

Roster, note and claim now come from the same event.

Group notes above similarity threshold
31%changed to6%

Separating shared content from individual response did most of the work.

Time to document a 12-person group
55 minchanged to18 min

Writing the shared portion once is where the hour goes.

How to read these numbers

This is a composite scenario, modelled on the workflows this product was designed against with a clinic director and a revenue cycle management firm. It is not a named customer engagement, and we will replace it with one when a program is ready to publish under its own name.

The takeaway

Three records of the same session will always disagree eventually. The fix is having one.

If that describes your program, the fastest way to find out whether this holds is thirty minutes with your own workflows rather than a slide deck.

1.4%per-diem days denied on attendance

Get started

Start today, or take a look first.

Create an account in minutes. Or book a 30-minute walkthrough.

Register now