The 60 day RTH clock, and why most hospitals lose it

Why the start date is the trap

Most facilities measure the window from the day the claim lands in a work queue. PhilHealth measures it from receipt of notice. The gap between those two dates is dead time that nobody owns, and in a busy department it routinely runs to two or three weeks.

That means a claim that feels like it has 45 days left may actually have 25. Teams working by perceived urgency rather than actual expiry lose the oldest claims first, which are usually the ones that have already been touched twice.

Where the remaining days go

Four predictable sinks, in rough order of how much time each consumes.

• Waiting on a physician signature from someone now off rotation or on leave
• Re-reading the chart to work out what the deficiency code actually refers to
• Routing between billing, medical records and the clinical department with no owner
• Batching for a weekly re-filing run, which alone can cost six days

How to run the backlog properly

Sort by days remaining, never by peso value. A large claim with fifty days left is safe. A small one with eight days is about to become zero.

Related PhilHealth RTH claims, the complete recovery guide

1. 01Record the receipt date on every RTH claim, separately from the date it entered your queue
2. 02Sort the open list by days remaining and work the top of it first
3. 03Group by deficiency code, because one root cause usually explains a large cluster
4. 04Escalate anything signature-dependent immediately, since that depends on a human schedule
5. 05Re-file continuously rather than in a weekly batch

Where the sixty days actually go

Almost never in the correction itself. Most RTH corrections are a matter of hours of work once the right person has the right information in front of them.

The days go to routing, which is its own version of the same gap: the fix is known, and it never reaches the claim in time. The notice arrives and is logged. It waits to be triaged. It is assigned to a queue. Someone opens it and finds the fix needs a document from records, or a signature from a consultant who is not in this week. It goes back into a queue in a different shape. Each handoff costs days, and none of them is anybody's fault.

Which is why a process fix beats a reminder. Reminders speed up the step somebody is already doing. The delay is in the gaps between steps.

The correction takes hours. The routing takes weeks. Only one of those is worth optimizing.

A workable internal deadline

Set your own clock at thirty days, not sixty, and treat the second thirty as the buffer it needs to be.

A single internal deadline at day thirty gives you a full month of slack for the two things that reliably run long: a document that has to come from another department, and a signature that has to come from a clinician. Teams working to the real sixty day limit have no slack at all, and discover it in week eight.

Track one number weekly: the count of open RTH claims past day thirty. Not the total, not the value, just the count past the internal deadline. It is a single figure, it fits in a standing meeting, and it moves before the money does.

What to do when the window has already gone

Nothing recovers that claim. The route closed and there is no appeal on the same grounds.

What is still worth an hour is reading the expired ones as a set. Group them by deficiency reason and by where they stalled. The pattern in a batch of expired claims is the most honest process audit a revenue team will ever get, because nobody was performing for it.

The output should be at most two changes. An expired claim that produces a change that prevents ten future ones has paid for itself, which is the only useful way to think about money that is already gone.

What removes the clock entirely

Every hour spent on this backlog is remedial work on a claim that should never have been returned. The deficiency was created at coding time, when the clinician who wrote the note was still reachable and the patient was still admitted.

Catching the omission before submission removes the clock. There is no 60 day window to manage on a claim that was correct when it left the building.