Skip to content

Claims recovery

Every PhilHealth claim denial reason, and how to prevent each one

Published 2026-08-02 · last reviewed 2026-08-10 · 4 min read

PhilHealth claims are denied or returned for four root causes: coding mismatches between the chart and the claim, incomplete or unsigned documentation, eligibility and coverage problems, and filing errors such as late submission. Coding and documentation account for the large majority, and both are preventable before submission.

Key facts
FactFigureSource
Inpatient claims ungroupable under DRGAbout 10 percentPIDS, 2018 to 2023 study
Most common preventable causeICD-10 and documentation mismatchPhilHealth circulars
Secondary diagnoses now required per DRG claimUp to 12PhilHealth DRG Implementation Manual

Coding and documentation mismatches

This is the largest category and the one most worth fixing, because the evidence needed to prevent it is already in your own records.

  • ICD-10 code on the claim does not match the diagnosis in the clinical record
  • A documented complication has no corresponding secondary diagnosis code
  • Diagnosis is not covered by the benefit package as coded, though the actual condition may be
  • Clinical abstract is incomplete, illegible or does not support the coded severity
  • Procedure codes do not reconcile with the itemized billing

Incomplete or unsigned documentation

These are pure process failures, and they share one signature: the fix requires a person who has already moved on.

  • Missing physician signature on required forms
  • Unsigned or missing Claim Form 2 or Claim Form 5
  • Missing itemized billing statement
  • Mandatory fields left empty, including patient priority subgroup
  • Obstetric risk factors not recorded on maternity claims

Eligibility and coverage problems

Largely catchable at admission rather than at billing, which is where most facilities currently discover them.

Related PhilHealth RTH claims, the complete recovery guide

  • Member contributions not current at the time of admission
  • Dependent not properly declared or registered
  • Benefit already consumed within the applicable period
  • Service excluded from the applicable package

Filing and administrative errors

Small in number, total in effect. A claim filed one day late is worth the same as a claim never filed.

  • Filed beyond the prescribed period
  • RTH claim not corrected within the 60 calendar day window
  • Duplicate submission of an existing claim
  • Submitted through a channel or version no longer accepted, such as a retired eClaims version

Denied and returned are not the same thing

The distinction decides what you can still do, and teams that blur it lose recoverable money. A returned claim has a remediable defect and a window to fix it. A denied claim has been decided against on substance, and the route is a formal appeal on different grounds and a different timetable.

Treating a return as a denial means writing off money that was collectable. Treating a denial as a return means burning the window on a resubmission that cannot succeed, then discovering the appeal deadline has also gone. Both errors are common and both come from a queue that does not separate the two.

Sort them on arrival. Different owner, different process, different clock.

A return is a deadline. A denial is an argument. They are not the same problem.

Why coding and documentation cause most of it

Eligibility problems are usually visible before submission and filing errors are usually systemic and therefore fixable once. Coding and documentation deficiencies are neither, because they originate in a narrative written by a clinician under time pressure and are then read by a coder under different time pressure.

The failure is almost never that nobody knew the rule. It is the gap between the chart and the claim: the evidence supporting a code exists in prose, and the claim can only read a field. A chart describing cold clammy extremities and a narrow pulse pressure is describing shock, and nowhere does it use the word. A coder scanning for codeable terms will not find it, because it is not there to find.

That is the whole reason this category resists training as a solution. The information was captured. It was captured in a form the claim cannot read.

How to find your own top three causes this week

Do not start with a policy review. Start with your last hundred returned claims, which you already have.

Tabulate them by stated deficiency reason, then read the ten most recent of the largest category in full. The stated reason tells you the category. Reading ten of them tells you the mechanism, and the mechanism is what you can actually change. Most hospitals find that two or three mechanisms account for the majority, and that at least one is a single missing field in one form.

The output is not a report. It is a list of at most three changes, each of which is a change to a step somebody performs, not a change to how carefully they perform it.

Which of these should you fix first

Rank by frequency multiplied by peso impact, not by how annoying each one feels. For most Philippine hospitals that calculation lands on the same answer: missing secondary diagnosis codes.

They are frequent because the evidence lives in free text narrative that a coder must read and interpret under time pressure. They are expensive because under PHL-DRG a missing CC or MCC marker does not just risk a return, it silently places the claim in a lower payment tier even when it is accepted.

What to do this week

  • Export last quarter's deficiency codes and rank them by frequency times peso value
  • Check what share of your returns trace to a missing secondary diagnosis
  • Move eligibility verification to admission, where it costs minutes instead of weeks

About this guide

This is general information for hospital revenue and coding teams. It is not clinical advice, not legal advice, and not a reimbursement guarantee. It does not create a professional relationship of any kind.

Code only what the treating clinician documented. A code that the chart does not support is not a recovery, it is an exposure, and PhilHealth can act against an accreditation over it. Where this guide and the patient record disagree, the record governs, every time.

PhilHealth circulars, PHL-DRG groupings and eClaims requirements change. Verify anything here against the current issuance before you act on it, and confirm with your own coding lead, your compliance officer, or counsel.

Sources

Every guide here is free. When your team is ready to go deeper, Academy is being built for that.

See the reading path

Related reading