MEAT Criteria for Risk Adjustment: The Documentation Standard Every HCC Coder Must Know

What MEAT Stands For

MEAT is the documentation standard used to validate that a diagnosis was legitimately addressed during a patient encounter. It stands for:

For a diagnosis to be valid for HCC risk adjustment, at least one MEAT element must be documented in the encounter note. CMS and RADV auditors use MEAT as the primary framework for determining whether a submitted diagnosis was genuinely managed during the visit or was simply listed in the medical record without clinical engagement.

Why MEAT Matters for Risk Adjustment

Every HCC diagnosis submitted to CMS for risk adjustment must meet two criteria:

1. The ICD-10 code must be supported by the medical record — the condition must be documented

2. The condition must have been addressed during the encounter — MEAT documentation proves this

Without MEAT documentation, a RADV (Risk Adjustment Data Validation) audit will deny the diagnosis — even if the condition is real, even if the patient genuinely has the disease, and even if the ICD-10 code is technically correct. The audit question is not "does this patient have diabetes?" but "did the provider address diabetes during this specific encounter?"

This is the most common source of HCC denials in RADV audits: conditions that are listed in the problem list or assessment but have zero documentation of monitoring, evaluation, assessment, or treatment in the encounter note.

MEAT Documentation Examples by Condition

Diabetes (E11.x) — HCC 37/38 under V28

Passing MEAT example:

> A1C reviewed today: 7.8%, up from 7.2% in January. Patient reports occasional hypoglycemic episodes with current insulin regimen. Increased Lantus from 20 units to 24 units at bedtime. Will recheck A1C in 3 months. Diabetic foot exam performed — no ulcers, intact sensation bilaterally.

This note hits all four MEAT elements: A1C monitoring, evaluation of hypoglycemic episodes, assessment of glycemic control, and treatment adjustment.

Failing MEAT example:

> Problem list: Type 2 diabetes mellitus with chronic complications

> Assessment: Diabetes — stable

This note fails MEAT because "stable" without context does not demonstrate monitoring, evaluation, or treatment. An auditor cannot determine that the provider actually engaged with the diabetes diagnosis during this visit.

Heart Failure (I50.x) — HCC 224/225/226 under V28

Passing MEAT example:

> Patient with known HFrEF, EF 30% on last echo 6 months ago. Denies orthopnea or PND. Weight stable at 185 lbs. BNP today 450 (previously 380). Continue carvedilol 25mg BID, lisinopril 20mg daily. Repeat echo ordered to reassess EF. Continue 2g sodium diet.

Failing MEAT example:

> CHF — continue current medications

COPD (J44.x) — HCC 280 under V28

Passing MEAT example:

> COPD with FEV1 45% predicted on last PFTs. Patient using albuterol rescue inhaler 3-4x/week, up from 1-2x/week last visit. Added Spiriva 18mcg daily. Smoking cessation counseling provided — patient interested in Chantix. Flu vaccine administered today.

Failing MEAT example:

> COPD — patient has an inhaler

Common MEAT Documentation Failures

1. Problem List Without Engagement

Listing a condition in the problem list or past medical history does not satisfy MEAT. The condition must be addressed in the current encounter's assessment and plan — or in the HPI, exam, or orders — with evidence that the provider actively managed it.

2. "Stable" Without Context

Documenting a condition as "stable" or "unchanged" can satisfy MEAT — but only if there is context showing how stability was determined. "Diabetes — stable" alone fails. "Diabetes — A1C 6.8% stable on current regimen, continue metformin" passes because it shows the basis for the stability assessment.

3. Copied Forward Notes

When EHR templates copy forward prior notes, the current encounter may contain documentation that was not actually reviewed or updated by the provider. RADV auditors specifically look for copy-forward patterns: identical text across multiple encounters, timestamps that do not match the visit date, and lab values that do not change between visits.

4. Missing Treatment or Monitoring Plan

A diagnosis documented in the assessment without any corresponding plan item — no medication mentioned, no lab ordered, no follow-up scheduled — raises red flags during audit. Even a simple "continue current treatment, reassess at next visit" provides a minimal MEAT element.

MEAT vs TAMPER

Some organizations use TAMPER as an alternative or supplement to MEAT:

TAMPER covers the same ground as MEAT with slightly more granularity. Both frameworks answer the same question: "Was this condition managed during this encounter?" Organizations that pass MEAT audits will also pass TAMPER audits, and vice versa. The key is consistent application of whichever framework your organization uses.

How to Use MEAT in Chart Reviews

When reviewing charts for risk adjustment coding, apply MEAT as a checklist for every diagnosis you intend to submit:

1. Find the diagnosis in the encounter note — assessment/plan section is the primary location, but HPI, exam, and orders also count

2. Identify at least one MEAT element — is there monitoring, evaluation, assessment, or treatment documented?

3. Confirm the MEAT element is specific to this encounter — not copied from a prior visit, not a generic template

4. Verify clinical plausibility — does the documentation make clinical sense for this patient? A 25-year-old with documented CKD stage 4 should trigger a query, not a submission

Use the HCC Buddy encoder to verify the ICD-10 code maps to an HCC under the current model year. If the code does not map to an HCC, there is no RAF value in submitting it for risk adjustment — focus your MEAT review on conditions that carry HCC weight.

Provider Education for MEAT Compliance

Risk adjustment coders cannot fix documentation after the fact. Accurate MEAT documentation starts with the provider. Effective provider education programs include:

The goal is not to teach providers to "code" — it is to teach them to document what they are already doing. Most providers already monitor, evaluate, assess, and treat chronic conditions. The documentation failure is that they do not write it down in a way that meets audit standards.