What does MEAT stand for in HCC coding?

MEAT stands for Monitor, Evaluate, Assess or Address, and Treat. Risk-adjustment teams use it as a documentation-review mnemonic. It is not an official ICD-10-CM rule, a CMS regulation, a minimum reporting threshold, or a guarantee that a diagnosis is reportable. Apply the official coding guidance and the applicable program and payer rules to the full record.

Is MEAT a CMS requirement or a coder convention?

MEAT is a coder convention. CMS RADV checks whether diagnoses submitted for risk adjustment are supported in the enrollee's medical records. CMS does not make the four MEAT letters a universal pass-or-fail test. Use the mnemonic to organize a review, then verify the code, date of service, provider and encounter eligibility, authentication, and applicable guidance.

What is the difference between MEAT and TAMPER?

MEAT and TAMPER are training frameworks used by some coding and compliance teams. Neither replaces the ICD-10-CM classification, Official Guidelines, CMS instructions, or payer policy, and neither guarantees that a diagnosis will validate. Follow the framework your organization has approved and confirm the underlying record requirements separately.

Does a chronic condition need MEAT evidence at every visit?

There is no blanket CMS rule that every chronic condition needs one MEAT element at every visit or exactly one MEAT-supported visit per year. For a diagnosis submitted for risk adjustment, verify that an eligible record in the applicable data-collection period supports it, then apply the current program and payer requirements. Do not carry a diagnosis forward automatically.

What is the most common MEAT failure in HCC audits?

Copied or carried-forward text is a review signal, not an automatic audit result. Check whether the full record for the date of service supports the diagnosis and code under the applicable rules. Do not treat a problem-list entry as automatic support, and do not treat a sentence containing one MEAT verb as automatic validation.

Does AI scribe output count as MEAT documentation?

The current CMS RADV materials reviewed here do not create a separate MEAT pass-or-fail rule for scribe text. Apply the valid-record, provider, encounter, authentication, diagnosis-support, and coding requirements in the instructions for the applicable audit.

How does HCC Buddy help with MEAT documentation?

HCC Buddy uses MEAT as an educational review checklist beside source-labeled model results. It does not decide whether a diagnosis is reportable, guarantee RADV validation, or replace the official code set, CMS instructions, payer policy, a compliant query process, or coder judgment.

Risk Adjustment Documentation · Hub

MEAT Documentation Review Mnemonic

MEAT, Monitor, Evaluate, Assess or Address, and Treat, is an industry documentation-review mnemonic used by coders. It is not an ICD-10-CM coding rule, a CMS regulation, a minimum reporting threshold, or an automatic RADV result. Use it to organize a review, then apply the official classification, CMS instructions, payer policy, and the facts documented for the date of service.

HCC Buddy keeps this reference next to the HCC coding software hub and the MEAT review deep dive, which walks chart-review examples. This page stays the short reference; the blog stays the worked examples.

CMS says RADV verifies whether diagnoses submitted for risk adjustment are supported in the enrollee's medical records. Neither the RADV program page nor the ICD-10-CM Official Guidelines turns the four MEAT letters into a federal coding standard. Review the current CMS RADV program page and the FY2026 ICD-10-CM Official Guidelines before turning a checklist result into a coding decision.

Quick answer

Use MEAT to ask whether the record shows monitoring, evaluation, assessment or addressing, or treatment relevant to the diagnosis under review. A single matching word is not automatic support, and the absence of a recognizable MEAT element is not a standalone CMS deletion rule. Start with the full record and the official ICD-10-CM classification, then check the requirements for the program, payment year, encounter, provider, and payer.

What each MEAT letter means in practice

M, Monitor

Monitoring can include documented review of labs, symptoms, vitals, imaging, or other findings linked to the condition. For example, an A1c trend may help show that diabetes was considered during the encounter. A lab result alone does not establish a diagnosis or make a code reportable. Read it with the provider's documentation and the full record for E11.9, Type 2 diabetes without complications.

E, Evaluate

Evaluation can describe how a diagnosed condition is responding to management, such as controlled, improving, or worsening. Those words are useful only in context. They do not independently establish the diagnosis, ICD-10-CM specificity, encounter eligibility, or RADV outcome.

A, Assess

Assessment or addressing can include the provider's current diagnostic statement, severity, status, or clinical reasoning. Use that documentation with the Alphabetic Index, Tabular List, and Official Guidelines to choose the supported ICD-10-CM code. Never query for, or select, specificity because one HCC would carry a different coefficient. See the HCC hierarchy and trumping rules for how model hierarchy is applied after coding.

T, Treat

Treatment can include medication management, procedures, counseling, referrals, or another documented plan linked to the diagnosis. A medication name, refill, or referral does not by itself establish a diagnosis or its code. Status codes may be relevant without active treatment, so do not use the T in MEAT as a universal reporting threshold.

What CMS RADV materials actually say

CMS describes MA RADV as its process for confirming that diagnoses submitted by a Medicare Advantage organization for risk adjustment are supported in the enrollee's medical records. CMS may collect overpayments when submitted diagnoses are unsupported. That source does not name MEAT as the rule or define a one-letter documentation threshold. Read the current CMS RADV program page.

The ICD-10-CM Official Guidelines explain that accurate coding depends on complete documentation and review of the entire record. They do not convert Monitor, Evaluate, Assess or Address, and Treat into a separate federal coding standard. Use the current FY2026 Official Guidelines with the code set and other instructions that apply to the encounter.

MEAT can help a reviewer spot where to read more closely. It cannot establish a diagnosis, select a code, determine encounter eligibility, or predict an audit result by itself.

Using MEAT during a documentation review

Start with the diagnosis submitted and the full medical record for the applicable data-collection period. Check the current instructions for the provider, encounter, record, authentication, and coding requirements. MEAT can help organize what the record says about the diagnosis, but the mnemonic does not replace the ICD-10-CM Official Guidelines.

A copied problem-list entry, a medication, a referral, or a single checklist word is not an automatic result. Review the clinical statement in context and apply the instructions for the audit or reporting program at issue. For current CMS audit developments, use the 2026 RADV audit expansion and payment year 2020 RADV that covers 471 contracts as background, then return to the controlling CMS instructions.

Proposed policies must stay labeled as proposals. For example, the proposed ban on unlinked chart reviews for MA plans does not become a current reporting rule unless CMS finalizes it. Coders can also review the RADV audit prep guide and the broader CMS-HCC V28 model overview while keeping model mapping, documentation support, and audit procedure as separate questions.

MEAT vs TAMPER, which framework to teach providers

Different health systems and coding vendors teach different documentation frameworks. The two most common are MEAT (four letters: Monitor, Evaluate, Assess, Treat) and TAMPER (six letters: Treatment, Assessment, Monitor/Medicate, Plan, Evaluate, Referral). TAMPER breaks Treatment into two pieces, the acute treatment and the follow-up referral, and explicitly names "Plan" as a separate element.

Comparison point	MEAT	TAMPER
Elements	4: Monitor, Evaluate, Assess, Treat	6: Treatment, Assessment, Monitor/Medicate, Plan, Evaluate, Referral
How treatment is handled	One Treat element	Split into acute Treatment and follow-up Referral
Plan named separately	No	Yes
What it is	A review aid taught by coding and compliance teams; not CMS authority
Replaces MDM, ICD-10-CM, CMS instructions, or payer policy	No, for both frameworks

Both frameworks are review aids. Neither one substantiates a diagnosis or guarantees an audit result by itself. The AAPC risk adjustment MEAT brief is an industry reference, not CMS authority. Follow your organization's approved framework and test the underlying record separately against official guidance and payer policy.

TAMPER's explicit Referral and Plan labels may help an internal reviewer locate relevant documentation. A referral alone does not establish the referred diagnosis, make a code reportable, or guarantee validation. Read the provider's diagnostic statement and the rest of the record.

Where MDM sits (and does not)

Medical Decision Making is an E/M coding construct. It does not replace diagnosis-code support or risk-adjustment requirements. MEAT and TAMPER do not replace MDM, the ICD-10-CM classification, CMS instructions, or payer policy. Keep those decisions separate.

Using the checklist without turning it into a coding rule

The same mnemonic may point to different chart language for a chronic condition, an acute condition, a status, or a resolved condition. The ICD-10-CM classification and the record, not the mnemonic, decide the code.

Chronic progressive conditions

Diabetes (E11.x), heart failure (I50.x), CKD (N18.x), and COPD (J44.x) may be monitored, evaluated, assessed, or treated in different ways. A phrase such as "continue current regimen" has meaning only with the condition, date-of-service record, and provider context around it. See the condition-specific guides for examples, then verify the official rules for diabetes, heart failure, CKD, and COPD for condition-specific MEAT patterns.

Acute conditions

Acute MI, stroke, pulmonary embolism, and exacerbations have code-specific timeframes and instructions. Do not keep an acute code active, or replace it with a history code, based on MEAT alone. Follow the provider's current diagnosis and applicable ICD-10-CM guidance. For example, verify J44.1 COPD with acute exacerbation against the documented current encounter status instead of assuming an exacerbation continues.

Status codes (Z-codes)

Amputation, ostomy, transplant, and other status codes can be relevant even when no treatment occurs. Code a status only when the current record and applicable ICD-10-CM guidance support reporting it. Do not invent an annual MEAT statement or infer a status from an old problem-list entry.

Resolved or "history of" conditions

Active, resolved, remission, and personal-history concepts have condition-specific ICD-10-CM instructions. Select the code supported by the provider's documentation and those instructions, then check that exact code's current model mapping. Do not use the presence or absence of treatment as the only test for active disease.

Five checks before a diagnosis is submitted

Separate carried-forward text from current support. Review the full date-of-service record. A problem-list entry is not an automatic pass, and adding one sentence merely to satisfy a mnemonic does not guarantee support.
Unspecified codes when specificity is available. Assign the most specific code the record supports. An E11.9 when the chart supports E11.22 (diabetes with diabetic CKD) can be used only when the documentation and ICD-10-CM instructions support it. If a compliant clarification is needed, use the provider-query templates and re-encode with the specified code through the HCC Buddy encoder.
Status codes inferred or carried forward. Verify that the current record supports the status and that reporting it is appropriate for the encounter. Do not add a status because it mapped previously or because an annual sweep is expected.
"History of" vs active-condition confusion. Use the condition-specific ICD-10-CM instructions and current provider documentation to distinguish active disease, remission, and personal history. Review the top ten commonly miscoded HCCs and verify the date-of-service record.
V24 vs V28 category drift. Mapping and documentation are separate decisions. Some codes mapped under historical PY2025 V24 but not CY2026 V28, and some current V28 codes have multiple HCC rows. Code the documented condition correctly even when no payment HCC results. See the V24 vs V28 comparison and check each code's status in the ICD-10 to HCC mapping tool.

MEAT provider-query templates

Provider queries must be compliant under AHIMA and ACDIS query guidelines: non-leading, based on the record, and open-ended enough to allow the provider to clarify without being steered to a specific code. Use a query only when the record needs clarification under the applicable coding rules. Do not query simply to add a MEAT element or change an HCC mapping.

Clarify current status

The chart documents [condition]. Based on today's encounter, can you indicate whether this condition is stable, improving, or worsening on the current treatment plan?

Clarify documented specificity

The documentation notes [unspecified condition]. If clinically appropriate, can you document the specific type or severity (e.g., controlled vs uncontrolled, with or without complications) to support the most accurate ICD-10 assignment?

Clarify current relevance

[Condition] appears on the problem list but is not addressed in today's note. Can you document any monitoring performed (labs, vitals, symptom review) or indicate whether the condition is no longer present?

Full templates are in the provider-query templates guide. The AHIMA/ACDIS rules of neutrality apply to all of them.

RADV MEAT checklist

Run this on the date-of-service record before a diagnosis is submitted or a chart is pulled for an audit. Every line is a question about the record, not a scoring rule. Print it, or use the full 2026 RADV, MEAT, and Strength of Evidence checklist when the review covers a whole sample.

Valid record. The note is for a face-to-face or eligible telehealth encounter, in the data-collection period, from an acceptable provider type and facility.
Authenticated. The note carries the provider's signature and credentials, or an accepted electronic authentication, with a date.
Diagnosis stated by the provider. The provider documents the condition as a current diagnosis in the assessment or plan, not only on a problem list, a lab result, or a scribe summary.
Monitor. The note records signs, symptoms, or disease progression for this condition on this date.
Evaluate. The note records a test result, an exam finding, or a response to treatment that the provider reviewed.
Assess or address. The provider states the condition's status: stable, improving, worsening, or under discussion with the patient.
Treat. The note records a medication, therapy, referral, or other management tied to the condition.
Specificity and mapping. The code assigned is the most specific one the record and the ICD-10-CM instructions support, and its V28 status was checked rather than assumed.

One MEAT line is enough to organize the review; it is not enough on its own to validate a diagnosis, and a missing line is not a CMS deletion rule. Items 1 through 3 and 8 are where audits are actually lost.

What is an example of HCC coding?

A note excerpt that supports a specific code, with the MEAT elements marked. The diagnosis is type 2 diabetes with diabetic chronic kidney disease, which the provider must link explicitly.

[Monitor] Type 2 diabetes mellitus with diabetic CKD stage 3a. Reports no hypoglycemic episodes. A1c 7.8 percent, down from 8.4.
[Evaluate] eGFR 52 today, stable against 54 six months ago. Urine albumin-to-creatinine ratio reviewed.
[Assess] Diabetes improving on current regimen; kidney disease stable, attributed to the diabetes.
[Treat] Continue metformin, add SGLT2 inhibitor for renal protection, repeat A1c and renal panel in 3 months.

The stated link between the diabetes and the kidney disease is what supports E11.22 with the N18.31 stage code, rather than E11.9. Whether either code maps to a payment HCC under V28 is a separate check in the ICD-10 to HCC mapping tool; the excerpt shows documentation support, not a payment result.

Free MEAT-included cheat sheet

The HCC Buddy cheat sheet includes a printable MEAT quick-reference alongside the V28 decision tree and the top 20 HCC categories. No email for the preview, the full PDF is gated by email.

Get the cheat sheet

Frequently Asked Questions

Related coding tools

ICD-10-CM Encoder

Check current CY2026 V28 beside a historical PY2025 V24 reference, with the CMS source label.

ICD-10 to HCC mapping

Type an ICD-10-CM code and check its source-labeled current V28 mapping status.

CMS-HCC V28

The 2026 model deep dive, what changed, what pays, what to update.

RAF member requirements

A V28 PY2026 result requires the complete diagnosis set and member details; otherwise no score is shown.

Payer Guidelines Library

Search the public guideline library. Personal payer PDFs are managed separately in Ask Buddy.

HCC Buddy Chrome Extension

MEAT reminders and HCC mapping inside your EHR.

Built for HCC coders. Official rules stay separate from training aids.

Coder-first workflow · 2026 CMS V28 current · References current CMS RADV materials and FY2026 ICD-10-CM Official Guidelines