MEAT criteria is the documentation standard used to prove that a diagnosis was actively managed during a patient encounter. MEAT stands for Monitor, Evaluate, Assess, and Treat. For a diagnosis to count toward HCC risk adjustment, the medical record has to show at least one of those four elements. A code without MEAT support is a code that can be denied in an audit.
That makes MEAT the foundation of accurate, defensible risk adjustment. Here is what each element means, why MEAT matters for your RAF scores and RADV audits, and how to document it so your codes hold up.
Each letter is a way a provider can show a condition was addressed during the visit. Document at least one for every diagnosis you report:
A useful way to think about it: all four are past-tense actions. The note has to show something was actually done about the condition, not just that the condition exists. A standalone list of diagnoses with no supporting action does not meet MEAT and is not valid under CMS and HCC coding guidelines.
It determines whether a diagnosis counts. CMS maps documented diagnoses into Hierarchical Condition Categories (HCCs), and each HCC adds to a patient’s Risk Adjustment Factor (RAF) score, which drives Medicare Advantage payment. If a diagnosis is not MEAT-supported, it should not be coded, which means it does not raise the RAF and the reimbursement that should follow it is lost.
It protects you in a RADV audit. CMS runs Risk Adjustment Data Validation (RADV) audits to confirm that submitted diagnoses are supported in the medical record. With RADV audits expanding in scope and frequency in 2026, MEAT-supported documentation is what stands between a code and a recoupment. Unsupported diagnoses are the most common reason codes get rejected.
It has to happen every year. RAF scores reset annually. A chronic condition documented last year does not carry forward, so every diagnosis has to be re-documented with MEAT support each calendar year to keep counting. Missing a chronic condition one year quietly lowers the RAF and the funding.
It keeps scores accurate, not just high. ICD-10-CM codes carry different weights for similar conditions at different severities. MEAT documentation captures that severity, which prevents both underpayment (missed acuity) and overpayment (unsupported codes), the two errors that create lost revenue and audit risk respectively.
The simplest way to keep documentation audit-ready is to treat MEAT as a checklist for every diagnosis at every encounter. Here is what each element looks like in a note:
| Element | What to document |
|---|---|
| Monitor | Signs, symptoms, conditions, physical assessment results, disease progression or regression |
| Evaluate | Test results, medication effectiveness, response to treatment or procedure, surgical notes |
| Assess / Address | Ordered labs or procedures, discussion of management, review of history, counseling |
| Treat | Medications, procedures, therapies, referrals, and other treatment modalities |
Capture the full clinical picture in real time so nothing is missed: history of present illness, physical exam results, nursing assessment notes, and the medical decision-making process. And remember the rule that trips up the most audits: a diagnosis listed without any supporting monitoring, evaluation, assessment, or treatment is not valid, no matter how accurate the diagnosis itself is.
The documentation bar rose with V28. The V28 risk adjustment model reached 100% implementation for payment year 2026, replacing the older V24 model. V28 expanded the number of payment HCCs from roughly 86 to 115, and it reduced the set of ICD-10-CM codes that map to an HCC from about 9,797 to roughly 7,770. Some diagnoses that raised RAF under V24 no longer do.
The practical effect for documentation: with fewer codes qualifying and tighter support requirements, MEAT is more important than ever. Every reportable diagnosis needs clear, current, MEAT-supported evidence, and coding workflows need to be maintained against V28 rather than legacy V24 mappings.
Applying MEAT consistently across a full patient panel, every encounter, every year, is difficult to do by hand. Inferscience’s HCC Validator checks every diagnosis against MEAT criteria before submission and links each code to its supporting documentation, building a defensible, RADV-ready trail. Its HCC Assistant surfaces missed and suspected HCCs at the point of care with 98% coding accuracy, so conditions are captured and documented while the encounter is still open. Both run inside your EHR, and a 700-provider clinically integrated network has used Inferscience inside athenaOne since 2020.
Book a strategy call · Read the case study
What does MEAT stand for in medical coding?
MEAT stands for Monitor, Evaluate, Assess, and Treat. It is the documentation standard that shows a diagnosis was actively addressed during an encounter, which is required for the diagnosis to count toward HCC risk adjustment.
Does a diagnosis need all four MEAT elements?
No. A diagnosis needs at least one of the four elements documented to be considered supported. Documenting more than one makes the record stronger, but one clear MEAT element is the minimum.
Why is MEAT criteria important for RADV audits?
CMS RADV audits verify that submitted diagnoses are supported in the medical record. MEAT documentation is the evidence that supports each code. Diagnoses without MEAT support are the most common reason codes are rejected and payments recouped.
How does MEAT affect RAF scores?
Only MEAT-supported diagnoses should be coded, and each coded HCC raises the patient’s RAF score. Missing MEAT support means missing HCCs, a lower RAF, and lost Medicare Advantage funding.
Did MEAT requirements change under V28?
The MEAT standard itself is unchanged, but V28 (100% for payment year 2026) reduced the qualifying ICD-10-CM codes and expanded HCC categories to 115, so accurate, current MEAT documentation matters more than ever.
