Reading path, PHL-DRG basics, 06 of 6
Shadow billing explained, what your hospital must file right now
Published 2026-08-03 · last reviewed 2026-08-10 · 3 min read
Shadow billing is a PhilHealth simulation in which hospitals generate hypothetical DRG-format claims alongside their regular claims, while continuing to be paid under the existing case rate system. Participation is mandatory for inpatient facilities capable of eClaims submission, and it requires up to 12 secondary diagnoses per case.
| Fact | Figure | Source |
|---|---|---|
| Who must participate | Inpatient facilities capable of eClaims submission | PhilHealth circulars |
| Secondary diagnoses per claim | Up to 12 | PhilHealth DRG Implementation Manual |
| Payment during shadow billing | Existing case rate system continues | PhilHealth circulars |
| Required form | Claim Form 5 for DRG shadow billing | PhilHealth advisories |
What is shadow billing
It is a parallel run. You submit your normal claim and get paid the normal way, and you also submit a DRG-format version of the same case that nobody pays you for. PhilHealth uses the second one to calibrate the payment system before switching it on for real.
The phrase most people miss is that it is a simulation for PhilHealth, but a live diagnostic for you. Your shadow claims are the first honest picture of what your documentation will be worth under DRG.
Why it matters more than it sounds
Because your shadow claims are a preview of your future revenue. If a case that consumed critical care resources codes as a Tier 1 admission in shadow billing, it will pay as a Tier 1 admission after the transition.
Facilities treating shadow billing as an administrative chore are burning the one free rehearsal they get. Facilities reading their shadow output as a documentation audit are finding gaps while it still costs nothing to find them.
What shadow billing is actually measuring
It is not measuring whether your coders can fill in a different form. It is measuring the gap between your chart and your claim, under a system that pays on severity instead of on diagnosis.
Those are different capabilities. A team can be excellent at the current form and still produce documentation that grades every admission as routine, because under case rates nothing ever asked it not to. The parallel run is the first time anybody sees the answer.
Which means a poor shadow result is not a verdict on your coders. It is a verdict on a documentation habit that the previous payment model never penalized, and habits are changed by changing what a form asks for, not by asking people to try harder.
Shadow billing measures your documentation, not your coders. They are not the same thing.
Related PHL-DRG for hospital CFOs, how your payment tier is actually decided
The three numbers to pull from your shadow output
- 01Tier distribution. What share of your shadow claims land in the lowest severity tier. If it is far above what your case mix would predict, your documentation is the reason, not your patients
- 02Secondary diagnosis count per claim. The average number actually filed against the twelve permitted. Most facilities discover they are using two or three
- 03Tier movement on review. Take fifty shadow claims, have a senior coder re-read the full chart, and count how many move up a tier on evidence that was already written down. That percentage is your recoverable gap, and it is the only one of the three a CFO will act on
Why the rehearsal is free and the performance is not
During shadow billing a wrong answer costs nothing. You submit the DRG-format claim, nobody pays it, and you find out what your documentation looks like under the new rules with no financial consequence at all.
After the transition the same wrong answer is a payment. Every admission graded routine because the chart never said otherwise pays as routine, permanently, with no notice, no query and no opportunity to correct.
That asymmetry is the entire argument for treating the parallel run as a diagnostic rather than an administrative chore. It is the only period in which being wrong is free.
What to do with your shadow billing data
Compare tiers, not totals. The number that matters is how often a case lands in a lower severity tier than the chart supports.
- 01Pull a sample of complex admissions where the patient clearly deteriorated
- 02Read the clinical abstract and list every complication documented in the narrative
- 03Check how many of those complications have a corresponding secondary code on the shadow claim
- 04Every gap you find is a payment tier you will lose after transition
What to do this week
- Treat your shadow claims as a documentation audit, not a filing chore
- Sample your most complex cases first, because that is where tier loss concentrates
- Fix the pattern, not the case, because the same omission repeats across hundreds of claims
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
- PhilHealth Circular 2023-0014, Implementation of Shadow Billing for the Transition to Diagnosis-Related Groups
- PhilHealth Tamang Sagot for Circular 2023-0014
- PhilHealth Advisory 2025-0028, Claim Form 5 for DRG shadow billing
- PhilHealth Circular 2022-0016, Governing Policies on Transitioning the Provider Payment Mechanism from All Case Rates to Diagnosis-Related Groups
- PhilHealth downloads, claim forms and provider references
That is the last guide in the PHL-DRG basics reading path. When your team is ready to go further, Academy is being built for that.
