CPC Pathway Team · Coding · 2026-10-01
"I've heard of MEAT but don't know how to apply it." That's the exact gap between knowing a definition and being able to read a real chart note and say, confidently, whether a diagnosis actually qualifies. Here's what MEAT looks like in real documentation, not just as an acronym on a slide.
| What | Detail |
|---|---|
| What MEAT Stands For | Monitor, Evaluate, Assess, Treat |
| Minimum Requirement | At least 1 MEAT element per diagnosis, per encounter |
| Strongest Documentation | 2 or more MEAT elements per condition |
| 2026 Update | CMS-HCC V28 model reached 100% implementation for payment year 2026 |
| Biggest Compliance Failure | Copy-forward problem lists with no updated MEAT evidence that year |
| Related Framework | TAMPER (Treatment, Assessment, Monitor, Plan, Evaluate, Referral) |
| Where MEAT Actually Lives | The progress note for that encounter — not the problem list alone |
MEAT criteria are the evidence standard auditors use to decide whether a diagnosis reported for HCC risk adjustment was actually, actively managed at that specific encounter — not just carried forward on a list from a previous visit.
A diagnosis sitting alone on a problem list, with nothing in that visit's note referencing it, does not meet MEAT and is not valid for risk adjustment purposes. The moment you start reading real chart language instead of the acronym in isolation, the standard becomes much easier to apply consistently.
Labs, vitals, or recurring checks tied to the condition. Real example: "A1c stable at 7.2, continue current regimen."
Imaging, lab values, or clinical findings connected to the condition. Real example: "Echo reviewed, EF 40%."
A statement of the condition's current status or a discussion of management. Real example: "CKD stage 3, discussed protein restriction."
A medication change, referral, or new management plan. Real example: "Increased lisinopril to 20mg daily."
Only one MEAT element is technically required per diagnosis per encounter for it to be reportable. But documentation that covers two or more elements gives significantly stronger protection if the chart is later pulled for a RADV (Risk Adjustment Data Validation) audit. A standalone problem-list entry with no supporting MEAT language anywhere in that visit's note fails the standard entirely, regardless of how clinically real the condition is.
If a diagnosis only appears in a static problem list carried over visit to visit, it hasn't met MEAT yet — regardless of how long the patient has had the condition.
"Diabetes" is a noun. "A1c reviewed, stable, continue metformin" is Monitor and Treat in action. The difference between naming a condition and documenting activity around it is exactly what auditors are trained to distinguish.
If the answer requires pointing to something from a previous visit, it doesn't hold up. MEAT evidence has to come from the current encounter's own documentation.
Scenario: A Medicare Advantage patient with diabetic nephropathy is seen for a routine follow-up.
| Documentation | Outcome | Why |
|---|---|---|
| The Distractor | Problem list: "Diabetic nephropathy" — no other mention in the note | Fails MEAT — the HCC is not supportable and could be invalidated on audit |
| The Correct Approach | "Diabetic nephropathy: eGFR reviewed at 52 (Evaluate). Continue current ACE inhibitor dose (Treat). Recheck labs in 3 months (Monitor)." | Three MEAT elements documented in one encounter — a well-supported, audit-defensible HCC |
The clinical reality (the patient does have diabetic nephropathy) is identical in both versions. Only the second one can actually be reported and survive a RADV review.
The CMS-HCC V28 risk adjustment model reached full, 100% implementation for payment year 2026, completing the phase-out of the older V24 model. The underlying MEAT documentation standard hasn't changed, but V28's revised condition categories and coefficients make accurate, current-year documentation even more consequential — a diagnosis that doesn't clearly meet MEAT carries more financial and compliance risk under the new model than it did under V24.
Notice that "Treat" so often means a medication or dosage change. Coders coming from a B.Pharm background tend to read that line of a chart note faster and more confidently than most, since it's the exact clinical judgment pharmacists already make daily — one more reason HCC/risk-adjustment coding is a natural specialty to grow into.
Risk Adjustment Data Validation audits are how CMS verifies that reported HCC diagnoses are actually supported by medical record documentation. Without valid MEAT evidence, an HCC found during a RADV audit can be invalidated and the associated payment recouped.
TAMPER (Treatment, Assessment, Monitor/Medicate, Plan, Evaluate, Referral) is a related six-element framework some organizations use instead. MEAT remains the more commonly referenced standard in CMS guidance and industry training.
A note that says a condition is "stable" still meets MEAT if it's paired with an actual verb in motion — "stable, continue current regimen" is both Monitor and Treat. "Stable" alone, with no plan attached, is weaker and worth flagging for clarification.
MEAT stands for Monitor, Evaluate, Assess, and Treat — the four types of clinical evidence auditors look for to confirm a diagnosis was actively managed during an encounter.
At least one MEAT element is required per diagnosis per encounter. Documentation covering two or more elements provides a stronger defense if the chart is audited.
No. A standalone problem-list entry with no supporting MEAT documentation elsewhere in that visit's note does not meet the standard and is not valid for risk adjustment reporting.
The HCC can be invalidated during a RADV (Risk Adjustment Data Validation) audit, and the associated payment can be recouped from the health plan or provider.
Both are documentation frameworks for HCC risk adjustment. MEAT (4 elements) is the more commonly referenced standard in CMS guidance; TAMPER (6 elements) is a related framework used by some organizations instead.
The V28 risk adjustment model reached full, 100% implementation for payment year 2026, completing its phase-in over the older V24 model. MEAT documentation standards remain the same, but accuracy matters even more under the revised model.
Test yourself on scenarios like the one above inside the domain quiz simulator, built to sharpen exactly this kind of documentation judgment.
Practice in the Quiz Simulator →© 2026 FabNotices · CPC Pathway. Compliance standards reflect current CMS/AAPC guidance; always confirm specifics against your organization's compliance policy and current CMS publications.