Reading path, PHL-DRG basics, 02 of 6
CC and MCC markers, the codes that set your payment tier
Published 2026-08-05 · last reviewed 2026-08-10 · 3 min read
CC stands for complication or comorbidity and MCC for major complication or comorbidity. They are secondary ICD-10 codes that raise a DRG case into a higher severity tier. Omitting a single MCC on a case that clinically warrants one can reduce reimbursement by more than a hundred thousand pesos.
| Fact | Figure | Source |
|---|---|---|
| CC | Complication or comorbidity, raises severity | PhilHealth DRG Implementation Manual |
| MCC | Major complication or comorbidity, raises it further | PhilHealth DRG Implementation Manual |
| Codes per claim | Up to 12 secondary diagnoses | PhilHealth circulars |
Why one code changes the number so much
Because the tier, not the itemized cost, determines payment. A severe dengue admission coded as A91 alone reads to the payment engine as dengue without warning signs. The same admission with R57.8 added reads as an infectious disease case with a major complication.
Both describe the same patient. Only one describes the patient who actually needed a PICU bed and aggressive fluid resuscitation for fourteen hours.
The codes most often omitted
These four recur across Philippine facilities, and each leaves a clear textual signature that is already sitting in your charts.
- R57.8, other shock, on severe dengue with circulatory collapse and plasma leakage
- J96.0, acute respiratory failure, on pneumonia with hypoxemia or respiratory support
- R57.0, cardiogenic shock, on myocardial infarction requiring vasopressor support
- J69.0, aspiration pneumonitis, on stroke following a failed swallow assessment
Why the same diagnosis can pay two different amounts
Two patients arrive with the same principal diagnosis. One is discharged after an uncomplicated stay. The other develops a complication, is managed in critical care, and goes home a week later. Under a case rate system those two claims pay the same. Under a severity-adjusted system they should not, and the mechanism that separates them is the secondary diagnosis list.
That is the entire purpose of the CC and MCC distinction. It is the payer asking, in the only language a claim has, whether this admission consumed the resources of a routine case or a complicated one. A claim that does not answer that question gets treated as routine by default.
Default is the important word. There is no penalty for omission and no query raised. The chart recorded a complication, the claim never said so, and the gap between them is paid at the lower rate.
There is no penalty for omitting severity. The claim just quietly pays as though the complication never happened.
Related PHL-DRG for hospital CFOs, how your payment tier is actually decided
Where the evidence usually is
In the narrative, not the problem list. That holds consistently enough across facilities that you can treat it as a rule rather than an observation.
The findings that carry weight are the ones a clinician records as part of describing what happened: a blood pressure trend, a lactate, an oxygen requirement, a fluid resuscitation, a transfer to a higher level of care. Each of those is a clinical fact with a code attached, and each of them is usually written as a sentence rather than entered as a diagnosis.
So you are not searching for diagnoses somebody missed. You are searching for conditions the chart already describes that nobody converted into a code, which is a different reading task and a faster one once your team knows to do it.
The line you do not cross
A marker is supportable when the record documents the clinical condition it represents. It is not supportable because the case felt severe, because the patient stayed a long time, or because you would prefer the higher tier.
This matters more than any recovery argument in this guide. A code the chart does not support is not a recovery, it is an exposure, and PhilHealth can act against an accreditation over a pattern of them. The correct response to a severe admission with thin documentation is to improve the documentation going forward, never to code past what the clinician wrote.
Where the guide and the patient record disagree, the record governs. Every time.
How to find them without adding headcount
The evidence is in the clinical abstract, phrased in clinician language rather than coding language. A chart that says cold clammy extremities with narrow pulse pressure is describing shock without ever using the word.
The practical approach is a pre-submission check that reads the narrative, computes standardized risk scores from the recorded vitals, and flags the case when documented severity and coded severity disagree. That check has to run before submission, because after discharge the clinician who wrote the note is no longer available to clarify it.
What to do this week
- Sample ten complex admissions and count how many carry a CC or MCC code
- Cross-check the four codes above against your most common complex presentations
- Move the check upstream of submission, not into the RTH backlog
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
This guide is part 02 of the PHL-DRG basics reading path. Next: Coding all twelve secondary diagnoses.
